Ensure that Highway Patrol's CAD system operators enter key information needed by the transportation management center operators.
Experience from iFlorida Model Deployment
While deploying and operating these systems, FDOT did identify a number of lessons learned that other locales may find useful.
- Work with the Highway Patrol to ensure that practices are in place to enter key information needed by the DOT in the correct fields within the CAD system. The data needs of FHP were different from those of FDOT, so some data fields that were key to FDOT but not key to FHP were not always entered consistently. One example was the road name, which was sometimes entered in the FHP CAD system as part of the free text description rather than in the road name field. FHP cooperated closely with FDOT by encouraging its dispatchers to follow more stringent data entry requirements with respect to these fields.
- Provide mechanism to translate data from the FHP CAD system to values recognized by FDOT. An example was the incident type. Because FHP sometimes revised the list of acceptable values for incident types and their meanings, FHP instituted procedures to ensure that the tables used to translate FHP incident type values to FDOT values would be updated whenever such changes occurred.
- Implement methods to identify and recover dropped messages in case of event-driven messaging. A system that uses event-driven messaging should include methods for identifying and recovering from dropped messages.
Author: Robert Haas (SAC); Mark Carter (SAIC); Eric Perry (SAIC); Jeff Trombly (SAIC); Elisabeth Bedsole (SAIC): Rich Margiotta (Cambridge Systematics)
Published By: United States Department of Transportation Federal Highway Administration 1200 New Jersey Avenue, SE Washington, DC 20590
Source Date: 01/30/2009
EDL Number: 14480URL: http://ntl.bts.gov/lib/31000/31000/31051/14480.htm
Average User Rating