Transportation leadership you can trust.

presented to

Safety Data Analysis Tools Workshop

presented by

Eric ZieringCambridge Systematics, Inc.

March 27, 2006

Data WarehousesApplications and Alternatives

2

A Little Background

Cambridge Systematics: Leading transportation consulting and full software/IT firm

Recent safety-related software/IT projects:

• Commercial Vehicles: Leader in CVISN: credentialing & electronic screening systems

• TransXML – Data interchange standards for transportation – Prime; Lead in the Safety Business Area

• Massachusetts Traffic Records Contractor

3

Data Warehouse - Overview

A repository for safety-related data

Typically assembled by compiling information from many participating agencies and organizations

Key challenges are in integrating and creating linkages across the data.

Fundamental infrastructure for value-added applications that tap into the data warehouse.

4

Safety Portal

Point of access to the Data Warehouse

Practical tool for safety evaluation and planning

• Tabular retrieval

• Map-based retrieval

• Analytic models

Central point for communication for a statewide (regional, multi-state corridor) safety community

5

6

7

8

9

10

11

12

13

14

15

16

17

Things to Consider – Alternatives

Crucial Issue: Linking of information from varied sources

Basics generally contained in the crash records file (MMUCC or NHTSA/TransXML standard)

Advanced analysis requires additional linkages:

• Incident ID: crash, EMT

• Driver license/ID: Citations & other driver records

• Location: crash, characterstics of roadway, pavement, guard rails, etc., traffic and characterstics

• Other Personal ID: linkages to medical records; patient IDs

Planning applications go one step further

18

Things to Consider - Project Planning

User Needs Assessment

• Which user communities are important?

• Which capabilities are essential?

• Which features drive data quality?

Incremental Implementation – Roll out in phases.

• Encourage evolution of needs and system design

Invest in manageability

• Build a system that can be readily maintained and updated

19

Things to Consider – Technical Issues

Hardware and hosting (web, Intra/Internet, security)

Choice of operating system and database

Crucial Documentation (beyond user guides)

• System Design and database documentation

• Disaster recovery plans

• System administrator documentation

• Transition plan

20

Things to Consider – Administrative Issues

Intra-Agency Legal Agreements (Liability, DPPA, etc.)

Controlling Access to Data

• Public Records

• Limits on Personal or Highly Personal Information

Tighter Linking of diverse databases increased administrative controls

And one more thing…

21

One More Thing…

Your data warehouse will soon be obsolete…

• Internet enablies live integration of diverse databases

• “Web Services” – each system accepts requests from many applications to deliver records, tables, and other information

• Many issues will disappear: redundancy, scheduling updates, security and administration

Plan for next generation of primary systems; design and build incrementally

Transportation leadership you can trust.

presented to

Safety Data Analysis Tools Workshop

presented by

Eric ZieringCambridge Systematics, Inc.

March 27, 2006

Data WarehousesApplications and Alternatives