OF ROAD ACCIDENT DATA SYSTEM (RADMS) ORDER NO.himachalservices.nic.in/hpridc/iMAAPHPRADMS... · 2.1...

CONSULTANCY SERVICES FOR THE PROVISION OF A ROAD ACCIDENT DATA MANAGEMENT SYSTEM (RADMS) ‐ VARIATION ORDER NO. 3 ‐ Maintenance and Training Completion Report ‐ Quarter 2 from Oct 2016 to Dec 2016

RPN

Report details

Report prepared for:

Project/customer reference:

Copyright: © TRL Limited

Report date:

Report status/version:

Quality approval:

Subu Kamal

(Project Manager)

Abhilash Kishore

(Technical Reviewer)

Disclaimer

This report has been produced by TRL Limited (TRL) under a contract with HPRIDC. Any views expressed in this report are not necessarily those of HPRIDC.

The information contained herein is the property of TRL Limited and does not necessarily reflect the views or policies of the customer for whom this report was prepared. Whilst every effort has been made to ensure that the matter presented in this report is relevant, accurate and up‐to‐date, TRL Limited cannot accept any liability for any error or omission, or reliance on part or all of the content in another context.

When purchased in hard copy, this publication is printed on paper that is FSC (Forest Stewardship Council) and TCF (Totally Chlorine Free) registered.

Contents amendment record

This report has been amended and issued as follows:

Version Date Description Editor Technical Reviewer

1.0 06‐01‐2017 First Version Reva Dileep Abhilash Kishore

Document last saved on: 11‐01‐2017 16:23

Document last saved by: Reva Dileep

i RPN

Table of Contents

1 Executive Summary 2

2 Introduction 3

2.1 Himachal Pradesh Road Accident Database Management System (RADMS) 3

2.2 Objectives & Scope of RADMS project 3

2.3 Key stakeholders 4

2.4 Background for this report 5

2.5 Scope of this report 6

3 Summary of activities made in the Quarter from October ‐December 2016 7

3.1 Meeting with the Stakeholders – December 2016 8

3.2 RADMS Server Health Check Summary – December 2016 9

3.3 Highlights on Accident Data 10

4 Training Completion Report ‐ Oct 2016 to Dec 2016 17

4.1 Training in RADMS for Himachal Pradesh Public Works Department 18

4.2 Training in RADMS for Department of Police 22

5 Project Risk Register 28

6 Operational Support and Maintenance Summary 29

6.1 Reports Generated on Request for Stakeholders 29

6.2 Inquiry Call Logs 31

6.3 Support and Maintenance Call Logs 31

6.4 Escalation Calls from Consultant 31

7 Key Tasks and Milestones 31

7.1 Tasks completed in 1st Quarter 31

7.2 Tasks completed in the 2nd Quarter 32

7.3 Planned Tasks for the 3rd Quarter 32

Appendix A Inquiry Call Logs 34

2 RPN

1 Executive Summary

In order to improve road safety in Himachal Pradesh, the Himachal Road and Infrastructure

Development Corporation (HPRIDC) sought to establish a road accident database

management system (RADMS), which will help in recording, analysing and reporting

information on road accidents occurring in the state. Transport Research Laboratory Ltd.

(UK), together with their local partner Experion Technologies India Pvt. Ltd., was chosen as

the Consultant to develop and implement this system, with the supporting funds for the

project coming from the World Bank.

The project commenced in March 2014 and has progressed over the 33 months, meeting all

the milestones and producing deliverables, as agreed in the project schedule. The RADMS

application is live and fully operational. The Consultant had completed the four quarters of

support and maintenance of RADMS, by 31st March 2016, and continued the operational

support activities in the months of April 2016, May 2016 and June 2016, completing the 5th

quarter as a good will gesture to the customer stakeholders. The customers have renewed

the Operational Support and Software Support / Maintenance for one more year (July 2016

– June 2017).

This report is part of the series of Quarterly Health Check and Operational Support /

Software Maintenance Reports to be submitted by the Consultant to the Client,

summarising the support activities made in the second quarter of the project support as per

the renewed support and maintenance quarter. During the second quarter of ‘Health Check

Operational Support and Software Support / Maintenance’ (Oct 2016 – Dec 2016), the

Consultant supported the customers for the queries and issues that they faced in using the

RADMS application and conducted all the planned software support / maintenance

technical activities. The Consultant also conducted a number of meetings with the

stakeholders to update them on the progress, plans, and dependencies for the project.

Consultant experts from TRL and Experion travelled to Shimla and met all the key

stakeholders of the project to understand the latest updates and concerns. In addition to

this, the Consultant support team provided trainings to several customer stakeholders.

The particulars of the health check and maintenance activities, support activities, refresher

trainings to the stakeholders are given in detail in this report.

3 RPN

2 Introduction

2.1 Himachal Pradesh Road Accident Database Management System (RADMS)

RADMS application a platform for the various stakeholder departments, such as the public

works department, police and health department, to look into the road accident data

scientifically and arrive at targeted solutions to improve road safety in the state. HPIRDC has

obtained financial support from the World Bank to implement the system.

2.2 Objectives & Scope of RADMS project

The primary objective of the RADMS project was to improve road safety outcomes in

Himachal Pradesh by providing access to timely, complete and relevant information on road

accidents.

In order to assist the stakeholders responsible for road safety improvement in Himachal

Pradesh to identify hazardous locations and trends in road accidents and to monitor safety

performance of the roads in the State, the customer stakeholders has requested the

Consultant to continue the support and maintenance of iMAAP RADMS application for

another year starting from Jul 2016 to Jun 2017. The use of the RADMS system will enable

stakeholders to plan more efficient strategies to reduce the number and severity of road

accidents and their impact on human lives. Consultant’s Support Team shall provide support

to resolve problems encountered during the usage of RADMS application. Application

Support Services proposed by the Consultant shall involve the following:

Consultant shall deploy a computer literate project assistant having exposure to

iMAAP RADMS system, for necessary coordination and assistance at Shimla (HP).

Consultant shall deploy a technical resource having exposure to the technical details

of the iMAAP RADMS system, at Shimla (HP).

Monitor the support e‐mails from HPSRP and respond to the problems reported by

HPSRP with the ticket number for the support request.

Analyse the issues reported by HPSRP. Suggest work‐around for defects, if there are

logical work around solutions available. Some defects may not have logical work‐

around and need to be fixed in the RADMS version in production server. These cases

will be informed to HPSRP.

Resolving problems in the production environment using access provided by DIT to

the RADMS servers. This will include:

o Rectifying data inconsistencies in production database arising due to RADMS

software problems

o Resolving problems due to incorrect application settings/configuration

related to application deployment

4 RPN

o Resolving defects / bugs in the iMAAP RADMS application.

Promoting RADMS defect fixes or change requests using direct access provided by

DIT to the RADMS servers, as per the scheduled monthly onsite maintenance

schedule. If there is a delay in providing adequate access to the DIT production

servers to the Consultant support team, subsequent delays will be there in resolving

the issue.

A senior resource from the Consultant’s product engineering & technical group will

visit the customer once in every quarter. This resource will conduct quarterly onsite

server health check activities. This health check process will include the following

sub‐activities:

Verification of CPU usage, Memory usage and HDD Space usage for

Application Server

Database Server

Verification of RADMS application health

Verification of RADMS user access statistics

Verification of availability of GIS services

Backup RADMS Application and Database

Shrink database log files

Recycle IIS Application Pool

Remove temporary application files

Providing monthly support and maintenance reports to HPSRP

Quarterly refresher training on iMAAP RADMS application to stakeholders for 3

hours.

2.3 Key stakeholders

The key stakeholders of the RADMS project are:

Stake Holders Key Functions

Public Works Department (PWD)

> Engaged in planning, construction and maintenance of roads, bridges, ropeways and buildings.

> Headed by the Engineer‐in‐Chief located at PWD Headquarters at Shimla

> Key Stakeholders responsible for overall management of the project.

Himachal Pradesh Road Infrastructure Development Corporation (HPRIDC)

> Headed by a Chief Engineer‐cum‐Project Director (CE‐PD)

> Project Implementation Unit (PIU) for the RADMS Project

> Role of the PIU is to ensure that the RADMS project is effectively implemented.

Himachal Pradesh Police > HP Police traffic wing, headed by an officer of the rank of

5 RPN

Traffic

Inspector General of Police (IGP) is responsible for traffic management and enforcement of traffic rules in the state.

> Manages the road accident statistics for the whole of Himachal Pradesh and it owns the accident data from 2001 onwards.

State Crime Records Bureau (SCRB)

> Acts as the hub for all crime‐related information relevant to the Police. It collects, collates and analyses data related to offences.

> SCRB also supplies information about the crime situation of the State to the National Crime Records Bureau and uses the Crime & Criminal Information System (CCIS) and Common Integrated Police Application (CIPA) to manage information.

Transport Department > Nodal agency which is responsible for issuing of driving licenses, registration of vehicles and collection of related taxes.

> Two software solutions in use – Vahan and Sarathi

> Vahan is used for Registration of Vehicles, Permit Issuance and other related activities. Sarathi is used for issuance of Various Types of Driving/Learner/Conductor Licenses and related activities.

Department of Health and Family Welfare

> Implementing agency of all health programmes initiated by the state and central governments.

> Directly oversees and manages the functioning of hospitals and health centres in both rural and urban areas.

2.4 Background for this report

Transport Research Laboratory Ltd. (UK), together with their partner Experion Technologies

India Pvt. Ltd., was chosen as the Consultant to develop and implement the road accident

database management system for Himachal Pradesh. TRL implemented the system through

customisation of their off‐the‐shelf crash data software iMAAP, as iMAAP RADMS. The

project commenced in March 2014 and has progressed over the last thirty months. RADMS

application was live in production from March 2015. The contract was renewed for the

purpose of Operational Support and Maintenance from July 2016 to June 2017.

The implementation in two police districts Shimla and Mandi was completed by the

Consultant in the month of March 2015. The remaining districts started using the system

from August 2015. The Consultant started the maintenance and support of the iMAAP

RADMS application on 1st April 2015 and is continuing till date, as per the renewed contract.

6 RPN

As a part of this new contract, the Operational Support and Software Support /

Maintenance was renewed further for a period of one year from July 2016 to June 2017.

2.5 Scope of this report

This report is the second in the series of quarterly maintenance reports, summarising the

maintenance and support activities done during the second quarter of the Operational

Support and Software Support / Maintenance renewed (July 2016 to June 2017); from 1st

October 2016 to 31st December 2016.

7 RPN

3 Summary of activities made in the Quarter from October ‐December 2016

The Consultant has undertaken a number of activities in the second quarter of operational

support of the project. These activities are summarised below:

iMAAP RADMS is live and implemented in Himachal Pradesh (HP). The total number

of accident records collected up to 31st December 2016 amounts to 4903. We are

very thankful to the Police as well as ADMC for this exemplary achievement.

On 7th and 8th December 2016 meetings were conducted by the Consultant

Management Team with the Stakeholders to get the customer feedback as well as to

address the issues and concerns, if any, on ground.

15 User Ids were created for the Nodal Officers of the Health Department and 4 User

Ids for the Himachal Road Transport Corporation (HRTC) on request. With this, the

much needed involvement from the Department of Health can be fulfilled in the

RADMS application.

The Quick Reference Guide and the access credentials were intimated to the various

Nodal Officers of the Health Department, through their E‐mail Ids. The training

session is also planned for the Health Department in first week Jan 2017 as per

confirmation from health department.

Monthly Status Reports were submitted for the month of October 2016, November

2016 and December 2016.

A total of 18 ad‐hoc reports were prepared by the Consultants on request from

various stakeholders in the Quarter October 2016 to December 2016. These were

created based on good will and in addition to the contractual obligations of the

Consultant.

o Reports prepared for Police Department – 9

o Reports prepared for Public Works Department – 8

o Detailed report on Black Spots in HP on request from HPRIDC

Refresher Training was conducted for Police Department at ADMC, Shimla by the

Consultant on 17th November 2016.

Refresher Training was conducted for the PWD at Nirman Bhavan, Shimla by the

Consultant on 29th December 2016.

Refresher Training was conducted for Police Department at ADMC, Shimla by the

Consultant on 30th December 2016.

8 RPN

3.1 Meeting with the Stakeholders – December 2016

The Consultant Management Team conducted meetings with the stakeholders at Shimla on 7th and 8th December 2016. The major discussions included during the meeting:

Sl.

No. Discussion Topics Management Strategy Adopted

1

Requirement of more

detailed maps to be

rolled out in the

application.

As per the contract “Digital maps covering the major state road network

of the State are to be arranged by HPSRP”. As Client did not possess the

latest updated digitized maps of HP, the use of Open Street Map (OSM) in

the iMAAP RADMS application was agreed upon and confirmed by

customer stakeholders after detailed discussions during the

implementation of the application. Thus, OSM was chosen as the GIS map

for this project considering the lack of availability of better maps from the

client side. However, since the Consultant understands the practical

issues on the ground, efforts were taken to look up at the various

industry standard maps available and HERE maps was identified to have

better coverage of HP roads than Open Street Map and Google Maps.

HERE maps provides 50000 map transactions free every month. The

Consultant has spent considerable effort to integrate HERE maps into the

RADMS application (as a good will gesture) to support the customer

stakeholders. HERE maps with better road data is already available in the

application.

2

Populating the black

spots in the National

Highways and other

roads using the system.

The detailed black spot report for the National Highways in the state of

HP was prepared using the iMAAP RADMS, by the experts from TRL UK

Team and Experion India Team. This was submitted on 19th December

2016

3

SARATHI and VAHAN

web services are not

working in RADMS

Firewall settings at the DIT were restricting access to the VAHAN and

SARATHI web services. The Application was encountering an exception

while trying to fetch the license details from the SARATHI web service.

The technical consultant, also visited DIT office to check the web services

issue. Request has been shared with DIT to enable the appropriate ports

for RADMS to access the web services for VAHAN and SARATHI. DIT has

enabled the ports. There were no changes required in the RADMS

application ‐ the issue with DIT firewall settings was rectified. Please note

that this issue was not related to RADMS application or the Consultant,

and were rather due to the disabling of certain ports by DIT team.

4

Participation of health

department to collect

health data for casualties

and entering the same to

the system

After highlighting the issue in the formal letters to PWD, the nodal

officers were assigned with user ids and passwords to access the

application and enter the details of the accident victims. Training session

is planned on 4th January 2017 and data entry is expected to progress

subsequently.

9 RPN

Figure 1: Meeting with the Stakeholders

3.2 RADMS Server Health Check Summary – December 2016

Quarterly health check was done in the RADMS production server at DIT. The summary in

given the following sections.

3.2.1 Health Check – December 2016

3.2.1.1 Verification Time

The verification was run on 06‐Dec‐2016 at 12:00 PM to 12:40 PM IST. RADMS production

server at DIT was verified, and the maintenance/support activities were conducted.

3.2.1.2 Resource Usage

The resource usage in the server were within the control limits and no specific action was

needed to optimize the resource usage.

Parameter Utilization Status

CPU Usage 1%

Memory Usage 59%

Used HDD Space 136.4 GB out of 450 GB

3.2.1.3 Application Instances & Health

The health of the application instances was normal and no specific action was needed to

optimize the application health.

RADMS Instance URL Status

Imaapradms http://hpimaapradms.hp.gov.in/imaapradms/

RADMS Instance Accidents Vehicles Injured

10 RPN

3.2.1.4 I

nstance Databases & Size

3.3 Highlights on Accident Data

The following sections explain various statistics and findings from the accident data

collected. Two districts – Shimla and Mandi were using the application from 23rd February

2015 and other districts by 1st August 2015. All statistics in this section are based on data

from 23rd February 2015 to 31st December 2016, except for the Section 3.2.3 Accident Data

Analysis from RADMS, wherein the data is chosen from 1st August 2015 to 31st December

2016. This is chosen as the baseline, for comparison across the various parameters queried

to generate the report after all districts started using RADMS application for accident

reporting.

NB: ‐ All accident data and statistics in this report are taken as on 5th January 2017.

3.3.1 Live accident data status

Twenty eight (28) police stations from the police districts of Shimla and Mandi are using

iMAAP RADMS to collect accident data, from 23rd Feb 2015 and from 1st August 2015

remaining seventy seven (77) police stations from other districts are also using iMAAP

RADMS. In case of any accident, the police personnel of these police stations take the

mobile tablets which has the iMAAP RADMS application installed in it, to the accident site.

Using the RADMS application, the police personnel captures various parameters of the

accident which will include GPS coordinates of the accident location and pictures of the

accident site.

The following table shows the count of number of accidents, vehicles and injured persons as

per the data collected in the RADMS system from 23rd February 2015 to 31st December 2016.

3.3.2 Quality of the Live Accident Data

Police personnel in the 105 police stations are using the iMAAP RADMS application to

capture accident records and they have captured 4903 accident records. Out of the 4903

accidents records, 104 records has data quality issues, which implies a good quality data of

around 98% which is quite good. The actual data entry from the police stations are further

Imaapradms 4903 7077 10801

Accident 4903

Vehicles involved 7077

Injuries 10801

Deaths 1940

11 RPN

validated and corrected by the Consultant’s operational team and ADMC police team to

improve the quality of data multiple folds. Some of the images attached to accidents cannot

add value for accident data analysis. It is recommended that the Police team collect proper

accident images against all the accident records so that further analysis / study can be

conducted on this.

3.3.3 Accident Data Analysis

This section gives an overview of the various aspects of the accident data collected during

the live usage of iMAAP RADMS. The data considered includes the input available from 105

police stations in all districts, during the period 1st August 2015 to 31st December 2016. This

is chosen as the baseline for comparison across the various parameters queried to generate

the report, which otherwise would lead to biased analysis. The charts and summaries shown

in this section were produced using iMAAP RADMS.

3.3.3.1 ‘District’‐wise split up of Accidents

Figure 2 shows the number of accidents reported in all districts (4476). The major share of

accidents are in Kangra (717), Shimla (712) and Mandi (650). The three districts have a

combined percentage of 46.45%.

Total Accidents Recorded 4903

Total Accidents with adequate data quality 4799

Percentage of Accident records with adequate data quality 97.88%

12 RPN

Figure 2: ‘District’‐wise split of accident data

3.3.3.2 ‘Accident time’‐ wise split up of Accidents

Figure 3 shows the number of accidents with respect to the time of occurrence. The peak is

identified from 5 ‐ 9 pm, during which 1254 accidents i.e., more than one fourth of the total

accidents are reported.

13 RPN

Figure 3: ‘Accident Time’‐wise split of accident data

3.3.3.3 ‘Police station’‐wise split up of accidents

Figure 4 shows the number of accidents that has been reported in various police stations in

all police districts. The police stations that top the charts are: Paonta Sahib (160), Una (134),

Balh (118), Nurpur (107), Sadar Bilaspur (107). The least number of accidents are recorded

at Bagga (3), and Udayapur (3).

Figure 4: Police station‐wise split of accident data

3.3.3.4 ‘Accident severity’‐wise split up of Accidents

The chart given in Figure 5 shows the number of accidents with respect to accident severity.

NHs, SHs and Link Roads have more number of severe accidents, of which NHs top the list.

Total of 548 fatal and 522 grievous accidents were reported in National Highways, whereas

State Highways had 371 fatalities and 277 grievous accidents. The low percentage of

accidents in city roads may be attributed to reduced speeds due to the heavy traffic.

14 RPN

Figure 5: ‘Accident Severity’‐wise split of accident data

3.3.3.5 ‘License type’‐wise split up of Accidents

The chart in Figure 6 shows the number of accidents with respect to license type.

Figure 6: ‘License type’‐wise split of accident data

3.3.3.6 ‘Collision type’‐wise split up of Accidents

The chart given in Figure 7 shows the number of accidents with respect to collision type.

With this classification, one can identify specific defects or shortcomings in the physical

features of the road, the modification of which after proper identification of the accident

spots from the database should help to reduce the casualties pertaining to the cause.

15 RPN

From the chart, it can be understood that out of 4476 Accidents, 1023 accidents fall in ‘Head

on’ collisions. Approximately 40% of these ‘Head On’ collisions have occurred in the last

three months. 885 accidents were in ‘ran off the road’ category; 864 accidents involved

cases wherein pedestrians were hit.

Figure 7: ‘Collision type’‐wise split of accident data

3.3.3.7 ‘Class of Injured person’‐wise split up of Accidents

Figure 8 shows the number of injured person with respect to ‘Injury Class’. From the chart, it

can be understood that out of 9752 persons involved in accidents, 1169 were ‘pedestrians’

means more than 11% of the total persons injured were pedestrians.

Figure 8: Injured person classes‐wise split of accident data

In the quarter October ‐ December 2016, a total of 808 accidents were recorded. Amongst

these accident records, it was found that only 496 records had accident images recorded.

This constitutes only 61% of the reported accidents in the quarter. The quality of the images

16 RPN

attached were also found to be insufficient. Only 30% of the total accidents had good

quality of images uploaded.

Figure 9: Images in Accident Records

Nearly 50% of the recorded images were of average or poor quality wherein the accident

sites were not clearly captured or were not captured at all. The statistics are recorded in

Figure 9. In many of the accident records, the images of the damaged vehicle and the

registration number plates were only recorded, and the accident site images were not

captured. The images captured should comply to the following standards as per the SOP:‐

1. The general incident scene, showing junction/road type, surface, skid marks and any

features which might have contributed to the accident occurrence

2. The main resting place of vehicles involved. Also, it is acceptable to capture the point

where vehicles left the road if it cannot be safely reached.

3. Damage to vehicle/property

4. In case of poor visibility (night time, fog, heavy rain, etc.), the Investigating Officer

will be required to return to the site and capture the appropriate photos when the

visibility is better

The purpose of the accident image to be recorded in the database is to identify the accident

cause and the conditions of the road wherein the accident occurred, which assist in further

analysis of the accident. This will help the stakeholders to identify the short comings in the

infrastructure and give more insight into the cause of the accident. The Figure 10 shows

example of accident record with good quality of images uploaded.

No Images 39%

Images Uploaded61%

0%0%

No Images Images Uploaded

17 RPN

Figure 10: Accident Reference No: 29112016‐96‐223412, FIR No: 317/16 reported at Una Police Station, Una

4 Training Completion Report ‐ Oct 2016 to Dec 2016

This section covers the details of training programs held in various parts of Himachal

Pradesh. The training programs were to ensure that the key stakeholders at HP understand

18 RPN

the details of the iMAAP RADMS application’s comprehensive data capture, data analysis

and data reporting capabilities. Following training programs were conducted:

Training Name Training Location Date

Training in RADMS for Police Department Shimla 17th November 2016

Refresher Training in iMAAP RADMS for Nodal Officers (Road Safety), HP PWD

Nirman Bhavan, Shimla

29th December 2016

Refresher Training in iMAAP RADMS for Police Department PHQ [ADMC], Shimla 30th December 2016

4.1 Training in RADMS for Himachal Pradesh Public Works Department

One day Refresher Training for iMAAP RADMS to the Nodal Officers (Road Safety) of HP

PWD was conducted on 29th December 2016 at Nirman Bhavan, Shimla. The training was

aimed at improving the awareness of the nodal officers from the road safety wing in the

PWD on the use of iMAAP RADMS tablet application. It specifically concentrated on the

fields that are to be filled by the department personnel and their queries were responded to.

Meeting started with a brief introduction by Mr. Rohit Thakur (EE PWD). This was followed

by a brief history of iMAAP application by the consultant. Then an overview and

introduction was given on the general aspects of the applications and it purpose. The

following points were included as part of the introduction:

Overview on TRL

Precedents & Similar Work Experience

What is iMAAP?

RADMS – Project Objective

Mobile Data Collection – Importance of Data

Advantages of having a data collection system

Introduction to Road Accident Data Management System:

What are the benefits

Collecting the data

Analysing And Reporting

As part of the web application training the following were discussed one after the other:

Login

Department

19 RPN

User Role

User Account

Password Policy

News Feed

Shared Query

Severity Configuration

Publish Reports

CBA

Black spot Type

Black spot Parameters

Public Dashboard

Add accident record

Edit Accident Record

Delete Accident Record

Print

Query Builder

Cluster analysis

Stick Analysis

Black spot analysis

Cross tabulation

User defined report

Standard report

A demo was given from the data in web application.

The session was interactive, and the following queries were raised by the participants:

1. When a query is run, is it permanent? Would they be able to see all the accidents

after a query run is completed?

2. How does black spot analysis assist their work?

3. How can they retrieve their password if they forget it? Will their account be

deactivated?

4. In cluster analysis is it possible to make a report of particular cluster? Print of that

location and accidents in that cluster can be take?

20 RPN

All the queries were answered one after the other. Mr. Rohit Thakur pointed out the fact that many of the officers are not familiar with the application and urged the nodal officers to use the application and make best use of it. The session concluded with vote of thanks from the Consultant.

21 RPN

Figure 11: Refresher Training for the PWD on 29th December 2016

22 RPN

4.2 Training in RADMS for Department of Police

4.2.1 Training for iMAAP RADMS to Police Department ‐ Traffic, Tourist and Railways at Shimla on 17th November 2016

Training session on the use of iMAAP RADMS tablet and web application was conducted for

the Investigating Officers (IOs), Department of Police at Shimla on 17th November 2016. A

total of 13 IOs attended the training session. The presentation started with a briefing on the

importance of RADMS and emphasized on data collection using iMAAP RADMS Application.

ASI Hari Dutt briefed about the functioning of Accident Data Management Cell and TRL as

well. This was followed with the presentation by the Consultant.

The Consultant gave a short introduction and background of the project. The Consultant

gave a quick overview on the following points:

What is iMAAP?

RADMS – Project Objective

Mobile Data Collection – Importance of Data

Advantages of having a data collection system

Changes needed in Accident reporting process

The Consultant presented the accident report form (ARF) and discussed each field in detail

with the participants. The Consultant presented the general usage of tablets to the

participants. The topics covered were:

Turning the tablet on and off

Charging the tablet device

Daily Routine – Charging, On/Off, Synchronize

Ensuring Good care of the tablet device

Storage of Tablet Devices at police stations

Process to be followed when Tablet Devices are not available in the police station

Responsibility of the Tablet Devices allocated to a police station

Troubleshooting steps

Warranty coverage

The Consultant presented the mobile data collection in tablets to the participants. The topics covered were:

Features of iMAAP Tablet Application

Collect ‘New Accident Information‘ using iMAAP Tablet Application

23 RPN

Synchronize accident record from tablet to central database

Search Accident Records

Edit accident record using iMAAP Tablet Application

Delete accident record from iMAAP Tablet Application

User Login

Use of the accident data in iMAAP web application

The Consultant briefed the participants on the following points in iMAAP web application:

Introduction to Road Accident Data Management System

o What are the benefits

o Collecting the data

o Analysing And Reporting

Discussion on the Accident Report Form

o Discussion of the fields

o How to describe an accident

Application training

o Login

o Department

o User Role

o User Account

o Password Policy

o News Feed

o Shared Query

o Severity Configuration

o Publish Reports

o CBA

o Blackspot Type

o Blackspot Parameters

o Public Dashboard

o Add accident record

o Edit Accident Record

o Delete Accident Record

o Print

24 RPN

o Query Builder

o Cluster analysis

o Stick Analysis

o Black spot analysis

o Cross tabulation

o User defined report

o Standard report

The demo exercise using a dummy record filling in the tablet application was conducted for

the IOs. The process of offline and online syncing were discussed. The session was

interactive and the participants cleared their doubts on the working of GPS, use of the

accident records, syncing of accident data etc.

The training ended with vote of thanks from the Consultant.

25 RPN

Figure 12: Training for the Police Department on 17th November 2016

4.2.2 Refresher Training for iMAAP RADMS to Police Department ‐ Traffic, Tourist and Railways at Shimla on 30th December 2016

Refresher Training session on the use of iMAAP RADMS tablet and web application was

conducted for the IOs, of the ADMC, Department of Police at Shimla on 30th December 2016.

The refresher training was aimed at improving the efficiency of the work carried out at the

ADMC, and reinforce their skills in using the application for data capturing, monitoring and

analysis. Three members from the ADMC attended the training session.

The Consultant gave a brief introduction and background of the project. The general usage

of tablets were also discussed briefly.

The Consultant discussed the following points in iMAAP web application in detail:

Brief Introduction to Road Accident Data Management System

Discussion on the Accident Report Form

Application training

o General use

o Shared Query

o Severity Configuration

o Publish Reports

o CBA

o Black Spot Type

o Black Spot Parameters

o Public Dashboard

26 RPN

o Add, edit, delete accident records

o Print

o Query Builder

o Cluster analysis

o Stick Analysis

o Black Spot analysis

o Cross tabulation

o User defined reports

o Standard reports

The importance of recording quality data, and the consistent follow ups with the IOs on

ground was emphasized upon. The need to record the images properly the points that

needs to kept in mind while taking the images were discussed.

The black spot analysis was discussed in detail, and how it could be put to use to reduce

accidents at the stretches identified. The session was interactive and the participants

cleared their doubts on the use the various types of analysis modules in the application.

They also got clarity on how the query is run so as to filter the accidents to obtain the

conditions as per the black spot definition.

The ADMC personnel were thankful for the monthly review and constant support received

from the consultant operational team on board and expressed their appreciation in the

efforts put for continuing the monthly training sessions.

27 RPN

Figure 13: Training for the Police Department on 30th December 2016

28 RPN

5 Project Risk Register

The project risk register has been updated based on the progress made and the activities

completed on December 2016. The updated register are given below.

Sl.

No.

Description Risk Impact Risk Management Strategy Risk

Owner

Status

1 Inadequate or

missing data in

key crash data

fields captured by

Police, such as

Location data

H

Limited usage of

GIS analyses

features in iMAAP

PWD to ensure capture of key

information including location

fields using iMAAP, for future

data.

PWD/

TRL

Live

2

Modifying firewall

configurations are

leading to

connectivity

issues.

M

Fetching the

driver

information from

VAHAN and

SARATHI is

getting affected,

thus affecting the

quality of the

accident data

DIT to inform the consultants

whenever a change in firewall

configuration occurs. After

various discussions with the

DIT issue is resolved as of

now.

PWD/

TRL

Closed.

3

System is slow

due to bandwidth

and speed issues

at a site

M

Perceived

benefits of using

the application

cannot be

materialized due

to slow

connectivity.

Bandwidth / internet access /

latency speeds will be tested,

and if there is a concern ‐ the

client will be informed that

this will potentially be an

issue and will be advised to

enhance their infrastructure.

PWD/

TRL

Live

4

Participation of

health

department to

collect health

data for

casualties and

entering the same

to the system

H

Limited usage of

health data in

iMAAP

This risk is highlighted in the

numerous formal letters to

PWD. The nodal officers are

assigned with user ids and

passwords to access the

application and enter the

details of the accident victims.

Training and data entry to

progress.

PWD/

Health

Depart

ment/

TRL

Live

5

Uploading of the

photographs of

accident spot in

the RADMS

M

Limited

understanding of

the accident

condition and the

road

infrastructure

Police personnel should be

given due guidelines on how

to take the relevant

photographs. Statistics on

quality is taken on daily basis

and follow up calls are made

PWD Live

29 RPN

to bring in adequate data.

6 Operational Support and Maintenance Summary

6.1 Reports Generated on Request for Stakeholders

The following reports were prepared by the Consultant Support team on request from

various stakeholders using the iMAAP RADMS application. Please note that these reports

were created by the Consultant team considering the need of the customer stakeholders,

and were done outside the scope of the contractual scope of the Consultant:

October 2016:

Report on accident severity in all districts and accident according to type of vehicle

as requested by Additional SP of PHQ.

Report of all district accident factor chart, severity, collision type, severity of injured

type as requested by Law Branch of PHQ.

Report on accident severity with respect to all districts as requested by ADMC

Report on accident in all districts due to vehicle type and fatalities in all districts

factor wise as requested by Executive Engineer, PWD.

Report on accident factor district wise as requested by Executive Engineer, PWD.

November 2016:

Report on District vs. Vehicle Type wise as requested by ADMC.

Report on Accident Severity vs. District as requested by ADMC.

Report on Accident Severity vs. Police Stations as requested by Executive Engineer,

PWD. The report included the police stations, location value and road type as the

fields.

Report on Summary details of accidents in Theog Police Station as requested by

Executive Engineer, PWD. This included the police stations, road type, road

description, FIR number and details of casualties involved in accidents.

December 2016:

Report on summary of accidents in NH from 1st April 2016 to 31st October 2016 of

each police station separately, which included the following details FIR No., District,

Police Station Name, Road Type, Road Name, Collision Type, Accident Factor and

Severity of Injured. This report was prepared as requested by the Executive Engineer,

PWD.

30 RPN

Report on summary details of accidents on SH, Link Roads, Border Roads and City

Roads from 1st April 2016 to 31st October 2016 for all Police Stations. Summary

print for each police station was taken separately, which included the following

details: FIR No., District, Police Station Name, Road Type, Road Name, Collision Type,

Accident Factor and Severity of Injured. This report was prepared as requested by

the Executive Engineer, PWD.

Report on summary details of accidents on NH from 1st August 2015 to 31st March

2016 for all Police Stations. Summary print for each police station was taken

separately, which included the following details, FIR No., District, Police Station

Name, Road Type, Road Name, Collision Type, Accident Factor and Severity of

Injured. This report was prepared as requested by the Executive Engineer, PWD.

Report on summary details of accidents on SH, Link Roads, Border Roads and City

Roads from 1st August 2015 to 31st March 2016 for all Police Stations. Summary

print for each police station was taken separately, which included the following

details, FIR No., District, Police Station Name, Road Type, Road Name, Collision Type,

Accident Factor and Severity of Injured. This report was prepared as requested by

the Executive Engineer, PWD.

Report on Accident Severity vs. Area Type from 1st January 2016 to 15th December

2016 of Urban, Rural, Semi‐Urban, Uninhabited area of whole state. This report was

requested by Additional SP, TTR.

Report on Vehicle Type vs. Accident Severity from 1st January 2016 to 15th

December 2016 of whole state, in which all vehicle types are included‐LMV, LGV,

HGV, MMV, Motor Cycle/Scooter Moped, Auto Rickshaw, Motor Car, Jeep, Taxi, Bus

Tempo, Truck, Tractor, Other Motor Vehicle, Null. This report was requested by

Additional SP, TTR.

Report on Class of Injured Person vs. Severity of Injured person and Area Type from

1st January 2016 to 15th December 2016 of whole state in which in Class of Injured

person includes ‐ Driver, Passenger, Pedestrian, Others and in Severity of Injured

person includes ‐ Fatal, Grievous, Injury Needing Hospitalisation and in Area Type ‐

Urban, Rural, Semi‐Urban, Uninhabited area. This report was requested by

Additional SP, TTR.

Report on Driver Age vs. Driver Injury Severity from 1st January 2016 to 15th

December 2016 of whole state in which Driver Age is taken as different ages groups

viz. 11‐15 ,16‐20,21‐25,26‐30,31‐35,36‐40,41‐45,46‐50,51‐55,56‐60 and in Driver

Injury Severity as Fatal and Grievous were included.

Experts from TRL UK Team and Experion India team prepared the detailed report on

Black spots in the National Highways within the state was populated for the period

1st August 2015 to 30th November 2016 on request from the HPRIDC. This report

included:‐

31 RPN

o The detailed list of 13 Black spots identified using the iMAAP RADMS application.

o List of all accidents involving Fatal & Grievous Injuries in National Highways in HP

from 1st August 2015 and 30th November 2016.

o List of all accidents involving Fatal & Grievous Injuries in Shimla‐Parwanoo

National Highway Section in HP between 1st August 2015 and 30th November

2016.

6.2 Inquiry Call Logs

Four calls regarding application usage was received, and the same is listed in Appendix A.

6.3 Support and Maintenance Call Logs

No support or maintenance call logs were registered of this month.

6.4 Escalation Calls from Consultant

The Consultant support team and ADMC members made several follow up calls with the

investigating officers of different police stations, requesting them to enter the missing

records if the accident records are not synchronised or if the accident data is not having the

expected data quality. In the month of October, November and December, 160 calls, 257

calls and 206 calls were made respectively.

7 Key Tasks and Milestones

This section of the report summarises the key tasks completed and the milestones achieved

during the second quarter of the support. The key activities and milestones planned for the

next quarter is also listed here.

7.1 Tasks completed in 1st Quarter

Support and Maintenance activities for the live iMAAP RADMS application.

Assist the police in collection and verification of road accident data from all police

stations, through implementation of iMAAP RADMS.

Renew the maintenance and support contract

Refresher training to investigating officers at various station zones.

Migrate the application from Consultant server to DIT server.

Provide monthly onsite server health checks.

Project discussions with PWD.

Project discussions with Police Department.

32 RPN

Project discussions with Health Department.

Submission of 1st Quarterly Maintenance and Training Report – July‐Sept 2016.

7.2 Tasks completed in the 2nd Quarter




Create access credentials for the Nodal Officers from the Health Dept. to input the

details in the Injury Section of the Accident Data Record.

Provide the Quick Reference Guides for the Nodal Officers from the Health

Department.

Refresher trainings for the PWD and Police Department.

Quarterly health check in DIT servers.

Consultant Management Team visit in the month of December 2016 for project

discussions with various stakeholders viz. the PWD, the Police Department and the

Health Department.

Create reports on request from various stakeholders.

Submission of Monthly Status Reports October 2016, November 2016, December

2016.

Submission of 2nd Quarterly Maintenance and Training Report – Oct‐Dec 2016.

7.3 Planned Tasks for the 3rd Quarter




Conduct training sessions and assist Nodal Officers from the Health Dept. to input

the details in the Injury Section of the Accident Data Record.

Conduct monthly refresher trainings for the PWD, Police and Health Department.

Assist the stakeholders during World Bank visit.

Quarterly health check in DIT servers.

Project discussions with PWD.

Project discussions with Police Department.

Project discussions with Health Department.

33 RPN

Submit the Monthly Status Reports and the Quarterly Maintenance and Training

Report.

34 RPN

Appendix A Inquiry Call Logs

Sl.

No. District

Police

Station Call By

Call

Timestamp Issue Details Resolution Provided

Resolution

Timestamp

Resolved

By

1 Hamirpur Barsar HC Hansraj 28‐10‐2016

3:30PM

How to sync accident

records online

through iMAAP

tablet application?

Go to "iMAAP RADMS tablet application" and click

on main menu button. Then click on "sync from

mobile". Select accident record and click on "online

sync icon". It will ask you for synchronising accident

record click on ok. Another message will be flash on

screen for successful synchronisation of record. Click

on "ok".

28‐10‐2016

3:55PM

Dikshit

2 Bilaspur Barmana HC

Amarjeet

Singh

28‐10‐2016

4:15PM


records online

through iMAAP

tablet application?

Go to "iMAAP RADMS tablet application" and click

on main menu button. Then click on "sync from





on "ok".

28‐10‐2016

4:33PM

Dikshit

3 Shimla Jhakri Constable

Jai Gopal

16‐11‐2016

10:40AM

Q1. How to sync

accident records

online through

iMAAP tablet

application?

Ans 1. Go to "iMAAP RADMS tablet application" and

click on main menu button. Then click on "sync from





on "ok".

16‐11‐2016

11:35AM

Dikshit

35 RPN

4 Lahul &

Spiti

Kaza Constable

Ramesh

9‐12‐2016

2:00PM


records offline from

tablet?

Ans1. Click on main menu and then click on Sync

from Mobile. Select the record and click on offline

icon (consist of one outside arrow) after that you will

find two message flashing on your tablet and click on

ok. Attach your tablet with your computer, open

iMAAP RADMS application. Login in application click

on tablet sync and open Zip file from tablet and

upload it. After that click on refresh then click on

“update synchronise result to tablet”, it will ask for a

file name give a file name and save this file on

desktop. After this copy that file to RADMS folder

inside tablet. Disconnect your table go to dashboard

and click on update now icon. Your record will be

vanished from tablet.

9‐12‐2016

2:30PM

Dikshit

TRL Crowthorne House, Nine Mile Ride, Wokingham, Berkshire, RG40 3GA, United Kingdom T: +44 (0) 1344 773131 F: +44 (0) 1344 770356 E: [email protected] W: www.trl.co.uk

II Quarterly Report ‐Oct 2016 to Dec 2016

OF ROAD ACCIDENT DATA SYSTEM (RADMS) ORDER NO.himachalservices.nic.in/hpridc/iMAAPHPRADMS... · 2.1...

Documents

Transcript of OF ROAD ACCIDENT DATA SYSTEM (RADMS) ORDER NO.himachalservices.nic.in/hpridc/iMAAPHPRADMS... · 2.1...