If an agency is just beginning to collect data on TIM performance, incident data will likely need to be entered from scratch as incidents occur. Over a short period of time, however, the agency will have enough data to begin running queries on the data to determine performance.
In this case, the agency will need to develop a front-end interface for the database that allows for incident data to be entered into the database. The first figure below is a simple example of what an initial screen of a TIM performance measurement database might look like. This example shows the basic components of an initial screen – a quick view of the most recent incidents that have occurred, as well as the option of creating a new incident, searching for an incident or incidents, viewing incidents, or creating incident reports. If a user wants to enter information about a new incident, the user would click “create new incident,” which would take the user to a data entry screen. A basic example of what a data entry screen might look like in shown in the second figure below. This screen allows the user to enter all of the data elements and information shown in the model TIM performance measurement database schema diagram. As with the initial screen, an agency can create any design for the incident data entry screen. Click here to see an example of actual incident data entry screens used by the Las Vegas FAST traffic management center.