AASHTO Transportation Safety Information Management System (TSIMS) Phase 1 Summary

Transcription

1 AASHTO Transportation Safety Information Management System (TSIMS) Phase 1 Summary Presented by: Hank Mycko Litton PRC, Manager of TSIMS System Architecture & Design

2 TSIMS Goals Create a nationally recognized integrated information management system that will address needs, shared by all states, to capture, manage, and effectively utilize the full array of traffic safety information. Provide a Set of Basic Data Capture, Imaging Processing, Workflow, and Data Analysis Services Integrate Data Currently Maintained in Legacy Systems with New TSIMS Data Provide a Uniform Data Platform for Traffic Safety Information Enable Each Installation to Choose from a Set of Compatible Modules that Best Meet Its Requirements Facilitate Future Development of Shared Applications and Migration of Legacy Systems 2

3 Phased Development Approach Phase 1 Definition Phase 2 Develop Phase 3 Deploy Gather System Requirements JAD Sessions State Focus Meetings Evolve the Conceptual TSIMS Design Identify Existing Compatible Products Prototype Key TSIMS Components for Participant Evaluation & Feedback Detailed Design Specification TSIMS Data Model Code TSIMS Modules Integration Test Pilot State Implementation Full Deployment Enhancements Maintenance 3

4 Phase I Participating States Washington, Kansas, Utah, Texas, Louisiana, Mississippi, Indiana, Tennessee, Georgia, South Carolina, Maine, Massachusetts, New York, Pennsylvania, Maryland 4

5 Litton PRC Team Litton PRC Complex Systems Integration SEI CMM Level 5 and ISO 9001/2 37 Years in the Public Safety Community AASHTO Member States Technical Advisory Groups Other Stakeholders IMERGE Consulting Document Management and Workflow SPECTRUM MAXIMUS Prime Contractor for TxDoT CRIS Analysis and Data Model Texas Transportation Institute Traffic Safety Engineering Advanced Vehicle Technology ALERT 5

6 Enhancing The TSIMS Team Two New Firms Added to the Team GeoDecisions,, Inc Leader in Providing Spatial Solutions to the Transportation Industry Specializing in Strategic Planning and GIS Application Development Worked with more than 20 state government and transportation agencies Current projects include PennDOT, DelDOT, Florida DOT, Oklahoma DOT, Nebraska DOR, and Kansas DOT TransDecisions Corp. Existing LRS Translation Product Route Measure, Marker Offset, Link-Node Methods Current Users Include Delaware DOT, Iowa DOT, OK DOT Dr. Julian J. Ray, CTO & Founder of TransDecisions Corp. Credits include LRSEDIT and HPMS/NHPN Integration Project, both for FHWA 6

7 Phase 1 Work Plan Task 1 Kickoff Meeting Final Work Plan Procedures Schedule TAGs Briefing Task 2 JAD Sessions Requirements Candidate Products Working Papers Task 4 Detailed Design Functional Design Data Model Architecture Phase 2 Work Plan Phase 2 Estimate Task 5 Prototype Working Prototype Presentations Task 3 Product Survey Product Evaluation Report 7

8 Phase 1 Kickoff Meeting Established scope and primary focus of Phase 1 activities Defined TSIMS to be: Comprehensive Crash Records System Database Data Capture Reporting Integration Mechanism to support Linkage to Legacy Databases Tool and utilities to support Data Analysis & Reporting Providing interfaces to existing sophisticated analysis packages (e.g., SAS) Most important product of Phase 1 is a Working Prototype 8

9 Phase 1 JAD Summary Activities Kick-Off Meeting Regional JAD Sessions New York Texas Louisiana State Visits Mississippi Kansas Electronic Meeting System Participation 102 Individuals 10 States NHTSA FHWA Representation Transportation Health Safety Law Enforcement Results 212 System Requirements 2,585 Comments, Concerns & Clarifications 9

10 TSIMS Requirements Traceability TSIMS Requirements Requirement Type Functional Subtype: Data Capture Requirement Description Data capture capabilities should allow for minimal self-correcting input such that contradictory information could not be entered. Various "flags" should be incorporated into the system to warn the data input person that contradictory, incomplete, or incorrect information has been entered. [ #192; F10710] Source Text/Source Description will the system reject the entire crash report? this aspect of the system is a definite must!!! The more edits you place up-front during data entry, the better the accuracy of the data. It may be frustrating at first for the end user, but once accustomed to the system, shouldn't be an issue. due to the nature of data, judgment calls will need to be made for the decision of what edits to put in place. seen too many systems that "warn" of data problems/errors, but still allow the data onto the file, which causes more of a mess than stopping the end user up-front. Mandatory that edits be in place to reasonably insure accuracy. Data capture capabilities should allow for minimal self-correcting input such that contradictory information could not be entered. Various "flags" should be incorporated into the system to warn the data input person that contradictory, incomplete, or incorrect information has been entered. Agree 100% Louisiana JAD Session This is probably the most critical aspect of any data entry system. If the data is not clean, it is Source Name Louisiana JAD Session Texas JAD Session Texas JAD Session Texas JAD Session Louisiana JAD Session 10

11 TSIMS Data Dictionary Based on Existing Standards and Best Practices MMUCC ANSI D.20 Augmented by superset of elements contained on State Uniform Crash Reports Texas Louisiana New York TSIMS Objective Create a compressive data dictionary such that over 90% of data elements used by any state are defined within TSIMS TSIMS will NOT require any additional data collection requirements 11

12 Data Dictionary Traceability Target Element Name Element Description TSIMS - Condition of Driver Two-character field with selections from A through K. L is free-form text which is next coded element Louisiana Crash Report Condition of Driver TSIMS - Condition of Driver - Remarks Louisiana Crash Report Condition of Driver - Remarks TSIMS - Condition of Driver and Pedestrian Louisiana Crash Report Condition of Driver and Pedestrian Free-form text allowing the officer to enter any additional information not available to select from "Condition of Driver" element. Two-character coded field. First field for Driver and second field for pedestrian if applicable. Options to select for both fields from A through L. MMUCC Driver Condition TSIMS - Contributing Circumstances, Driver Chris Driver Contributing Factor D.20 Contributing Circumstances, Driver MMUCC Contributing Circumstances, Driver New York State Contributing Factors - Human The actions of the driver which may have contributed to the crash. 12

13 Phase 1 Design Question - What is TSIMS? Remote Crash Database TSIMS Crash Data Internet Capture Subsystem Forms-based Data Entry Document Scanner Automated Recognition TSIMS Data Translator External System Interface Subsystem TSIMS Information Broker 1 Location Reference Workflow Management Crash Driver Vehicle TSIMS Database Roadway EMS Image Database Data Verification State Reporting TSIMS Reporting Federal Module Reporting Internet Crash Legacy Information Systems Driver Vehicle Roadway EMS High-Hazard Location Analysis? TSIMS Data Analysis Module GIS Analysis Ad Hoc Inquiry Internet File Export 13

14 Phase 1 Product Functional Design Document Functional Description of TSIMS Capabilities Crash Data Capture Interfaces with External Systems Analysis & Reporting Integration Scenarios Identification of Preliminary Software Components Data Capture Subsystem Workflow Management Subsystem Image & Document Management Subsystem Location Reference Subsystem External System Interface Subsystem Data Warehouse Data Analysis & Reporting Subsystem Product Evaluation Summary 14

15 Phase 1 Product Survey Re-Focused as part of the Phase 1 Priorities set at the Kickoff Meeting Evaluate Fewer Products Evaluate Products within the context of the Prototype Prove the Concept Demonstrate that the TSIMS Architecture and Design will support integration of existing products Demonstrate that TSIMS Functionality can be implemented via Existing Products Establish the Parameters for TSIMS Compatibility Configurable Products Standard Interface Methods Advanced Technologies Product Choices 15

16 Existing Product Support Areas Data Capture Products Mobile Data Capture Paper Forms Processing Document Management Systems Workflow Enterprise Application Interface (EAI) Analysis & Reporting Generalized Database Query Products GIS-based Analysis 16

17 Phase 1 Prototype Development Initial Prototype Delivery Look & Feel of TSIMS Prototype Delivery # 2 TSIMS the Movie Prototype Delivery #3 On the Road with TSIMS Presented at the AASHTO IS Subcommittee Meeting (5/16) Final Delivery Prototype v.4 Later this after noon 17

18 Phase 1 Resource Allocation 28% 1% 44% 27% JAD Design Prototype Product Survey 18

19 Conclusion Phase 1 Completed On Schedule Within Budget With Support from Product Vendors and Corporate Senior Management Phase 1 Objectives Accomplished Working TSIMS Prototype In Excess of that Originally Conceived Preliminary Design Provides Sufficient Detail to Plan and Estimate Phase 2 Phase 2 Workplan,, including Technical Approach, Milestone Schedule, and Cost Estimates 19