Presentation is loading. Please wait.

Presentation is loading. Please wait.

Collision Recording And Sharing System (CRASH)

Similar presentations


Presentation on theme: "Collision Recording And Sharing System (CRASH)"— Presentation transcript:

1 Collision Recording And Sharing System (CRASH)
Pat Kilbey Head of Road Safety Statistics Unit Department for Transport Welcome - I am PK, head of road accident statistics branch, in the Department for Transport. Project funded by DfT, The National Police Improvement Agency is taking forward the work on behalf of the Department. Collection process - is a national paper-based system STATS19 recording - by individual legacy systems in most forces STATS19 validation processes - Data is either validated and collated in force, or forwarded to the LA, or other agency, for validation. It is then forwarded to DfT. The process is costly, bureaucratic and has issues regarding the timeliness and quality of data.

2 Vision Standard national electronic system for England and Wales to enable the secure Collection Management of collision investigations Validation Transmission and Storage of collision details. to meet police business needs and government statistical requirements Provide an optional mobile solution Importation and auto population of collision details Maximise - i.e.PNC, Gazeteer – electronic system – files cant be lost !! Mobile solution - so reports can be compiled and validated at the scene Maximise the automated importation of data from other systems and auto-populate the collision form One force reports 69% of initial collision reports contained inaccuracies. Another force reports 12% of injury classifications are incorrect STATS19 details require validation. Costly and bureaucratic. The current process does not produce timely or accurate reports STATS19 validation processes - Data is either validated and collated in force, or forwarded to the LA, or other agency, for validation. It is then forwarded to DfT. The process is costly, bureaucratic and has issues regarding the timeliness and quality of data. On rtc flanagan said – great NCRF one system – bad that is paper based – if electronic excellent

3 CRASH in general The system will deal with all aspects of a collision, including Initial details at collision scene Collision investigation Administration File management STATS19 completion Optional system with a back office and an optional mobile solution Front Office, Back Office and Mobile Device screens Flexible XML interface Investigation management – what was done and when – what needs to be done – tasks with reminders – set deadlines – letters Modular – managed in the back office fed by optional mobile solution Multi-tier – Oracle database, Business Logic, Presentation and Mobile Application layers XML – to support enquiries and data transfer

4 CRASH in general Once-only submission Single database Intelligence
Linked to national databases Accessible via Web browsers Centralised Support & Maintenance Annual operating costs Electronic transfer of validated STATS19 Once only - Alert the officer to missing or inaccurate data and validate before completion reduce bureaucracy. Flanagan – reduction in bureaucracy – once only entry – less validation effort Single database – of all collisions in E & W - Bichard Enquiry – national intelligence sharing Linked to national – such as PNC to reduce data entry and improve validation Accessible – hosted at Hendon Data Centre and accessible over CJX no server costs – therefore forces will incur no costs for hardware, software licences or proprietary software available on any force networked machine Hendon will deal with any issues The annual operating costs will be paid for through the annual PNC Service charge paid by each Force Elect tf of Stats19 – to DfT, Local Authorities, the Highways Agency and force back office and prosecution systems

5 CRASH in operation Officer attends collision with mobile device
GPS gives exact location of collision Officer inputs minimum data Addresses added from post codes Name checked on PNC VRM checked on PNC Police and statistics (NCRF and NCSR report forms integrated and only required fields displayed Printing at scene Officer receives warning if not submitted within specified time Mobile - i.e. PDA, MDT Name checked - and driving licence and insurance details added to report VRM - and MOT details added to report Context - Officer selects type of collision and device displays appropriate fields for investigation and STATS19 - Only required fields displayed - i.e. cycle, no D/L Printing - HORT1 and other driver details can be printed at scene

6 Other Features Interfaces:
GPS, PNC, Mapping, Case Preparation systems, PentiP, KeyACCIDENT and AccsMap Other features: Management process e.g. reminders - ‘paperless’ system Letters and forms Audit trail Merge duplicate reports Electronic transfer to other forces National collision details immediately available Local stats fields Training and Online Help GPS – location at scene PNC – driver and owner details warning markers Insurance and MOT details checked against DVLA, insurance and force intelligence databases Registration added and checked against MOT and DVLA allowing details to be added automatically Gazetteer - – address, name and location away from scene Case Prep - – NSPIS, Niche RMS and Consortia forces PentiP – DORS, HORT 1 and 2, FPN.’s Key Accident - – XML and fixed format file Management and reminders – to supervisors and officers, set process time limits, and issues reminders. Journal and tasking - allows the officer to record notes of the investigation and set tasks with reminders to the officer, or another person, Each Force can define their own template letters and forms with the fields they wish to include and a copy stored as an attachment eg Victim Support Attachments ???–store scanned images, photographs and other documents Audit - full details of all changes made to the report with the date, time, person making the change and identity of the device on which the change was made are recorded in an audit log, as are the details for each search and viewing of the record. Duplicates – can be merged Elect tf – collision reports can be tf from one force to another or can be accepted from other systems to and from other forces without need for rekeying

7 Digital Collision Recording - benefits
Quality improvements for statistics: Statistics fully integrated within police accident reporting Details e.g. personal, vehicle and location can be confirmed and the reports can be compiled and essential parts validated at the scene of the collision. Maximise the automated importation of data from other systems Drop down menus/help to ensure correct input eg severity classification Notify missing data and complete validation before final submission. Improved quality but also potential for access to a wider range of data without adding to the burden of data collection Mobile working at the scene of an accident, rather than having to fill in paper forms should improve the quality of the data used to monitor casualty rates while reducing the form filling burden on the police. Built-in validation checks before submission of records will help accuracy and completeness Payment of 3rd parties to validate data Officer and back office time

8 Progress & Plans The contract to develop the software has was awarded end of 2008 Clarification of requirements and design completed, software under development and an initial demonstration system produced Testing with 3 pilot forces in spring 2011 Roll-out to other forces starting mid 2011 Further information: NPIA Business Change Manager: Inspector Geoff Goodall: General: PatKilbey/David Wilson RSS, DfT website Newsletters Microsite – background, vision, project mandate, business requirements, conceptual architecture, Dft Newletter also can register to be notified by when the site is updated address - More information will be provided to local authorities during the year – letter workshops History Outline Business Case developed by DfT and PITO DfT obtained Ministerial approval to fund the project 1 Jan Implementation of new MG forms including new STATS19 requirements 2004 – 2007 – Project stagnated in PITO until advent of NPIA 2007 – Interim solution available from NPIA, developed by Sussex Police May 2008 – Home Office recognise value of mobile devices

9 Creation of a new record

10 Casualty record


Download ppt "Collision Recording And Sharing System (CRASH)"

Similar presentations


Ads by Google