ATMS08-Traffic Incident Management System (Service Package*)

Description

This service package manages both unexpected incidents and planned events so that the impact to the transportation network and traveler safety is minimized. The service package includes incident detection capabilities through roadside surveillance devices (e.g. CCTV) and through regional coordination with other traffic management, maintenance and construction management and emergency management centers as well as rail operations and event promoters. Information from these diverse sources is collected and correlated by this service package to detect and verify incidents and implement an appropriate response. This service package supports traffic operations personnel in developing an appropriate response in coordination with emergency management, maintenance and construction management, and other incident response personnel to confirmed incidents. The response may include traffic control strategy modifications or resource coordination between center subsystems. Incident response also includes presentation of information to affected travelers using the Traffic Information Dissemination service package and dissemination of incident information to travelers through the Broadcast Traveler Information or Interactive Traveler Information service packages. The roadside equipment used to detect and verify incidents also allows the operator to monitor incident status as the response unfolds. The coordination with emergency management might be through a CAD system or through other communication with emergency field personnel. The coordination can also extend to tow trucks and other allied response agencies and field service personnel.

Service Package Graphic

Roadway Incident DetectionMCM Incident ManagementEmergency Response ManagementTMC Incident Dispatch Coordination/CommunicationRoadway Equipment CoordinationTMC Incident DetectionIncident CommandOn-board EV Incident Management CommunicationRoadwayTraffic ManagementMaintenance and Construction ManagementEmergency ManagementOther Emergency ManagementInformation Service ProviderEvent PromotersOther MCMOther RoadwayEmergency PersonnelTransit ManagementEmergency VehicleOther Traffic ManagementRail Operationsroad network conditionstraffic flowtraffic imagesvideo surveillance controltraffic sensor controlincident informationmaint and constr resource responseincident statuslogged vehicle routesincident informationincident informationresource deployment statusremote surveillance controlroad network conditionsincident informationincident response statusresource deployment statustraffic imagesincident informationmaint and constr resource requestincident informationmaint and constr resource requestincident response statusincident informationmaint and constr resource responseevent plansevent plansmaint and constr resource coordinationroadway equipment coordinationincident response coordinationincident command information coordinationincident command information presentationincident response statusincident informationincident informationincident response statusincident informationrail incident response statusincident command inputsdecision support informationincident informationroad network conditionsincident informationtraffic imagestraffic images

Get the Source Graphic, a Windows Metafile (WMF), in ZIP format.
About this Graphic

Includes Architecture Flows:

Source Architecture Flow Destination In Graphic
Border Inspection Systems border incident information Emergency Management No
Border Inspection Systems border incident information Traffic Management No
Border Inspection Systems remote surveillance control Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Traffic Management No
Emergency Management border incident response status Border Inspection Systems No
Emergency Management incident command information presentation Emergency Personnel Yes
Emergency Management emergency operations status Emergency System Operator No
Emergency Management decision support information Emergency Vehicle Yes
Emergency Management event confirmation Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Event Promoters No
Emergency Management incident information Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Information Service Provider Yes
Emergency Management incident information Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Maintenance and Construction Management Yes
Emergency Management incident response status Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Maintenance and Construction Management Yes
Emergency Management maint and constr resource request Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Maintenance and Construction Management Yes
Emergency Management map update request Map Update Provider No
Emergency Management incident information for media Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Media No
Emergency Management incident command information coordination Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Other Emergency Management Yes
Emergency Management incident response coordination Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Other Emergency Management Yes
Emergency Management incident information Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Rail Operations Yes
Emergency Management incident response status Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Rail Operations Yes
Emergency Management incident information Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Traffic Management Yes
Emergency Management incident response status Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Traffic Management No
Emergency Management remote surveillance control Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Traffic Management Yes
Emergency Management resource deployment status Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Traffic Management Yes
Emergency Management resource request Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Traffic Management No
Emergency Management incident information Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Transit Management Yes
Emergency Management incident response status Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Transit Management Yes
Emergency Personnel incident command inputs Emergency Management Yes
Emergency Personnel emergency personnel inputs Emergency Vehicle No
Emergency System Operator emergency operations inputs Emergency Management No
Emergency Vehicle incident status Emergency Management Yes
Emergency Vehicle emergency personnel information presentation Emergency Personnel No
Event Promoters event plans Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Emergency Management Yes
Event Promoters event plans Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Traffic Management Yes
Information Service Provider logged vehicle routes Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Traffic Management Yes
Maintenance and Construction Center Personnel maint and constr center personnel inputs Maintenance and Construction Management No
Maintenance and Construction Management incident information Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Emergency Management Yes
Maintenance and Construction Management maint and constr resource response Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Emergency Management Yes
Maintenance and Construction Management maint and constr operations information presentation Maintenance and Construction Center Personnel No
Maintenance and Construction Management maint and constr resource coordination Other MCM Yes
Maintenance and Construction Management incident information Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Traffic Management Yes
Maintenance and Construction Management maint and constr resource response Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Traffic Management Yes
Map Update Provider map updates Emergency Management No
Map Update Provider map updates Traffic Management No
Media external reports Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Traffic Management No
Other Emergency Management incident command information coordination Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Emergency Management Yes
Other Emergency Management incident response coordination Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Emergency Management Yes
Other MCM maint and constr resource coordination Maintenance and Construction Management Yes
Other Roadway roadway equipment coordination Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Roadway Yes
Other Traffic Management incident information Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Traffic Management Yes
Other Traffic Management road network conditions Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Traffic Management Yes
Other Traffic Management traffic images Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Traffic Management Yes
Rail Operations incident information Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Emergency Management Yes
Rail Operations rail incident response status Emergency Management Yes
Rail Operations railroad advisories Traffic Management No
Rail Operations railroad schedules Traffic Management No
Roadway roadway equipment coordination Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Other Roadway Yes
Roadway traffic flow Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Traffic Management Yes
Roadway traffic images Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Traffic Management Yes
Traffic traffic characteristics Roadway No
Traffic Management border incident information Border Inspection Systems No
Traffic Management traffic images Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Border Inspection Systems No
Traffic Management incident information Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Emergency Management Yes
Traffic Management incident response status Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Emergency Management Yes
Traffic Management resource deployment status Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Emergency Management Yes
Traffic Management resource request Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Emergency Management No
Traffic Management road network conditions Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Emergency Management Yes
Traffic Management traffic images Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Emergency Management Yes
Traffic Management event confirmation Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Event Promoters No
Traffic Management incident information Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Information Service Provider Yes
Traffic Management road network conditions Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Information Service Provider Yes
Traffic Management traffic images Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Information Service Provider Yes
Traffic Management incident information Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Maintenance and Construction Management Yes
Traffic Management maint and constr resource request Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Maintenance and Construction Management Yes
Traffic Management map update request Map Update Provider No
Traffic Management traffic information for media Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Media No
Traffic Management incident information Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Other Traffic Management Yes
Traffic Management road network conditions Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Other Traffic Management Yes
Traffic Management traffic images Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Other Traffic Management Yes
Traffic Management traffic sensor control Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Roadway Yes
Traffic Management video surveillance control Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Roadway Yes
Traffic Management traffic operator data Traffic Operations Personnel No
Traffic Management incident information Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Transit Management No
Traffic Operations Personnel traffic operator inputs Traffic Management No
    - This icon indicates that the associated architecture flow either has been or will be addressed by ITS Standards. Select the architecture flow for more information on relevant standards activities.

Associated Planning Factors and Goals

Planning Factor Goal
A. Support the economic vitality of the metropolitan area, especially by enabling global competitiveness, productivity, and efficiency; Support regional economic productivity and development
B. Increase the safety of the transportation system for motorized and nonmotorized users; Improve the safety of the transportation system
C. Increase the security of the transportation system for motorized and nonmotorized users; Improve the security of the transportation system
D. Increase the accessibility and mobility of people and for freight; Enhance mobility, convenience, and comfort for transportation system users
F. Enhance the integration and connectivity of the transportation system, across and between modes, for people and freight; Enhance the integration and connectivity of the transportation system
G. Promote efficient system management and operation; Increase operational efficiency and reliability of the transportation system

Associated Objective Categories

Objective Category
Arterial Management: Reliability
Emergency/Incident Management: Customer Satisfaction
Emergency/Incident Management: Incident Duration
Emergency/Incident Management: Inter-Agency Coordination
Emergency/Incident Management: Person Hours of Delay
Emergency/Incident Management: Training
Emergency/Incident Management: Use of Technology
Freeway Management: Reliability
Freight Management: Detours and Routing
Freight Management: Travel Time Reliability
Special Event Management: Entry/Exit Travel Times
Special Event Management: Multi-Agency Coordination and Training
Special Event Management: Use of Technology
System Efficiency: Cost of Congestion
System Efficiency: Delay
System Efficiency: Travel Time
System Reliability: Non-Recurring Delay
System Reliability: Planning Time Index
System Reliability: Travel Time 90th/95th Percentile
System Reliability: Travel Time Buffer Index
System Reliability: Variability
Travel Weather Management: Clearance Time (Weather-Related Debris)
Work Zone Management: Travel Time Reliability

Associated Objectives and Performance Measures

Objective Performance Measure
Annual rate of change in regional average commute travel time will not exceed regional rate of population growth through the year Y. Average commute trip travel time (minutes).
By Y (year), X percent of staff in region with incident management responsibilities will have completed the National Incident Management System (NIMS) Training and at least X percent of transportation responders in the region are familiar with the incident command structure (ICS). Percent of staff having completed NIMS training and percent of transportation responders familiar with ICS.
Decrease the average buffer index for (multiple routes or trips) by X percent over Y years. The buffer index represents the extra time (buffer) most travelers add to their average travel time when planning trips. This is the extra time between the average travel time and near-worst case travel time (95th percentile). The buffer index is stated as a percentage of the average travel time. Average buffer index or buffer time can be calculated using miles traveled as a weighting factor. Buffer time = 95th percentile travel time (min) – average travel time (min).
Decrease the buffer index for (specific travel routes) by X percent over the next Y years. The buffer index represents the extra time (buffer) most travelers add to their average travel time when planning trips. This is the extra time between the average travel time and near-worst case travel time (95th percentile). The buffer index is stated as a percentage of the average travel time. Average buffer index or buffer time can be calculated using miles traveled as a weighting factor. Buffer time = 95th percentile travel time (min) – average travel time (min).
Implement special event traffic signal timing plans at X percent of major special events each year beginning in year Y. Percent of major special events each year in which a special event traffic signal timing plan was implemented.
Improve average travel time during peak periods by X percent by year Y. Average travel time during peak periods (minutes).
Increase customer satisfaction with the region's incident management by X percent over Y years. Percentage of customers satisfied with region's incident management practices.
Increase number of ITS-related assets (e.g., roadside cameras, dynamic message signs, vehicle speed detectors) in use for incident and emergency detection by X in Y years. Number of ITS-related assets in use for incident detection.
Increase number of regional road miles covered by ITS-related assets (e.g., roadside cameras, dynamic message signs, vehicle speed detectors) in use for incident detection by X percent in Y years. Number of regional roadway miles covered by ITS-related assets in use for incident detection.
Increase percentage of incident management agencies in the region that (participate in a multi-modal information exchange network, use interoperable voice communications, participate in a regional coordinated incident response team, etc.) by X percent in Y years. Number of agencies in the region with interoperable voice communications.
Increase percentage of incident management agencies in the region that (participate in a multi-modal information exchange network, use interoperable voice communications, participate in a regional coordinated incident response team, etc.) by X percent in Y years. Number of participating agencies in a regional coordinated incident response team.
Increase percentage of incident management agencies in the region that (participate in a multi-modal information exchange network, use interoperable voice communications, participate in a regional coordinated incident response team, etc.) by X percent in Y years. Percentage of incident management agencies in region participating in multi-modal information exchange network.
Increase the number of agencies with special event management responsibilities that use interoperable communications by X percent in Y years. Number of agencies special event management responsibilities using interoperable communications.
Increase the number of corridors in the region covered by regional coordinated incident response teams by X percent in Y years. Number of TIM corridors in the region covered by regional coordinated incident response teams.
Increase the percent of major special events using ITS-related assets (e.g., roadside cameras, dynamic message signs, vehicle speed detectors) to detect and manage special event entry/exit bottlenecks and incidents by X percent in Y years. Percent of special events using ITS-related assets to detect and manage incidents/bottlenecks at entry/exit routes of the events.
Increase the percentage of special event stakeholder agencies participating in a regional event management team to X percent by year Y. Percent of stakeholder agencies participating agencies in a regional special event management team.
Provide freight operators with traveler alerts and alternate routes in the case of incidents, special events, weather, construction, and severe congestion at choke points on X percent of freight-significant routes by year Y. Percent of freight-significant routes where traveler alerts and alternate route information is provided in the case of incidents, special events, weather, construction, and severe congestion at choke points.
Reduce average time to clear event's exiting queue by X percent in Y years. Average time to clear event's exiting queue by year per event.
Reduce average time to complete clearing (interstates, freeways, expressways, all roads, main tracks, and main sidewalks) of weather-related debris after weather impact by X percent in Y years. Average time to clear selected surface transportation facilities of weather-related debris after weather impact.
Reduce average time to complete clearing (mode, hierarchy of facilities, or subarea of region) of weather-related debris after weather impact by X percent in Y years. Average time to clear selected surface transportation facilities of weather-related debris after weather impact.
Reduce average travel time into and out of the event by X percent in Y years. Average travel time away from selected special events to a set of locations over a year.
Reduce average travel time into and out of the event by X percent in Y years. Average travel time to selected special events from a set of locations in the area over a year.
Reduce buffer index on arterials during peak and off-peak periods by X percent in Y years. The buffer index (represents the extra time (buffer) travelers add to their average travel time when planning trips in order to arrive on-time 95 percent of the time).
Reduce buffer index on regional freight routes during peak and off-peak periods by X percent in Y years. Buffer Index on regional freight routes during peak and off-peak period.
Reduce buffer index on the freeway system during peak and off-peak periods by X percent in Y years. The buffer index (represents the extra time (buffer) travelers add to their average travel time when planning trips in order to arrive on-time 95 percent of the time).
Reduce buffer time index for travelers to multiple similar special events by X percent in Y years. Buffer time index for travelers to multiple similar special events.
Reduce delay associated with incidents on arterials by X percent by year Y. Hours of delay associated with incidents.
Reduce delay associated with incidents on the freeway system by X percent by year Y. Hours of delay associated with incidents.
Reduce hours of delay per capita by X percent by year Y. Hours of delay (person-hours).
Reduce hours of delay per capita by X percent by year Y. Hours of delay per capita.
Reduce hours of delay per driver by X percent by year Y. Hours of delay (person-hours).
Reduce hours of delay per driver by X percent by year Y. Hours of delay per driver.
Reduce mean incident clearance time per incident by X percent over Y years. (Defined as the time between awareness of an incident and the time the last responder has left the scene.) Mean incident clearance time per incident.
Reduce mean incident notification time (defined as the time between the first agency's awareness of an incident and the time to notify needed response agencies) by X percent over Y years (i.e., through "Motorist Assist" roving patrol programs, reduction of inaccurate verifications, etc.). Average incident notification time of necessary response agencies.
Reduce mean roadway clearance time per incident by X percent over Y years. (Defined as the time between awareness of an incident and restoration of lanes to full operational status.) Mean roadway clearance time per incident.
Reduce mean time for needed responders to arrive on-scene after notification by X percent over Y years. Mean time for needed responders to arrive on-scene after notification.
Reduce mean time of incident duration (from awareness of incident to resumed traffic flow) on transit services and arterial and expressway facilities by X percent in Y years. Mean time of incident duration.
Reduce non-special event VMT in the event area during events by X percent in Y years. Non-special event VMT in the event area during events over a year.
Reduce the 90th (or 95th) percentile travel times for each route selected by X percent over Y years. 95th or 90th percentile travel times for selected routes.
Reduce the annual monetary cost of congestion per capita for the next X years. Cost (in dollars) of congestion or delay per capita.
Reduce the average buffer time needed to arrive on-time for 95 percent of trips on (specified routes) by X minutes over Y years. The buffer index represents the extra time (buffer) most travelers add to their average travel time when planning trips. This is the extra time between the average travel time and near-worst case travel time (95th percentile). The buffer index is stated as a percentage of the average travel time. Average buffer index or buffer time can be calculated using miles traveled as a weighting factor. Buffer time = 95th percentile travel time (min) – average travel time (min).
Reduce the average of the 90th (or 95th) percentile travel times for (a group of specific travel routes or trips in the region) by X minutes in Y years. 95th or 90th percentile travel times for selected routes.
Reduce the average planning time for (specific routes in region) by X minutes over the next Y years. The planning time index represents the time that must be added to travel time at free-flow speeds or the posted speed limit to ensure on time arrivals for 95 percent of the trips. Planning time = 95th percentile travel time (minutes) – Travel time at free-flow speed or posted speed limit. Average planning time index or planning time can be computed using a weighted average over person miles traveled.
Reduce the average planning time index for (specific routes in region) by X (no units) over the next Y years. The planning time index represents the time that must be added to travel time at free-flow speeds or the posted speed limit to ensure on time arrivals for 95 percent of the trips. Planning time = 95th percentile travel time (minutes) – Travel time at free-flow speed or posted speed limit. Average planning time index or planning time can be computed using a weighted average over person miles traveled.
Reduce the person hours (or vehicle hours) of total delay associated with traffic incidents by X percent over Y years. Person hours (or vehicle hours) of delay associated with traffic incidents.
Reduce the variability of travel time on specified routes by X percent during peak and off-peak periods by year Y. Variance of travel time. Variance is the sum of the squared deviations from the mean. This can also be calculated as the standard deviation of travel time. Standard deviation is the square root of variance.
Reduce total person hours of delay (or travel-time delay per capita) by time period (peak, off-peak) caused by all transient events such as traffic incidents, special events, and work zones. Total person hours of delay during scheduled and/or unscheduled disruptions to travel.
Reduce total person hours of delay (or travel-time delay per capita) by time period (peak, off-peak) caused by scheduled events, work zones, or system maintenance by x hours in y years. Travel time delay during scheduled and/or unscheduled disruptions to travel.
Reduce total person hours of delay (or travel-time delay per capita) by time period (peak, off-peak) caused by unscheduled disruptions to travel. Total person hours of delay during scheduled and/or unscheduled disruptions to travel.
Reduce vehicle-hours of total delay in work zones caused by incidents (e.g., traffic crashes within or near the work zone). Vehicle-hours of delay due to incidents related to work zones.


 
Since the mapping between objectives and service packages is not always straight-forward and often situation-dependent, these mappings should only be used as a starting point. Users should do their own analysis to identify the best service packages for their region.

Related ITS Applications of ITS Taxonomy

Classification Category ITS Application Area ITS Application(s)
Intelligent Infrastructure Freeway Management Special Event Transportation Management
Intelligent Infrastructure Road Weather Management Traffic Control - Control Strategies Traffic Signal Control
Intelligent Infrastructure Traffic Incident Management Clearance & Recovery
Intelligent Infrastructure Traffic Incident Management Information Dissemination
Intelligent Infrastructure Traffic Incident Management Mobilization & Response Automatic Vehicle Location / Computer-Aided Dispatch

Response Routing
Intelligent Infrastructure Traffic Incident Management Surveillance & Detection Call Boxes

Detectors

Imaging/Video

Traveler Reported

Wireless Enhanced 9-1-1
Intelligent Infrastructure Transportation Management Centers Temporary TMCs Special Events

User Services related to this Service Package:

User Service
1.7 Incident Management
5.2 Emergency Vehicle Management
5.3 Disaster Response And Evacuation

Transaction Set Diagram

Note that this transaction set diagram (TSD) is only 1 of the 6 TSDs and so only a portion of the numbered items below refer to the TSD.
ATMS08 transaction set diagrams: Part 1, Part 2, Part 3, Part 4, Part 5, Part 6,



The source graphic, a Windows Metafile (WMF), for the TSDs can be downloaded here: TSD Part 1, TSD Part 2, TSD Part 3, TSD Part 4, TSD Part 5, TSD Part 6,

The following discusses how the National ITS Architecture provides the transportation service described by this service package. Each numbered item describes the operation of that portion of the service package identified with the corresponding number on the transaction set diagram.

  1. Incident information may be displayed on a map of the transportation network. The Traffic Management Subsystem and the Emergency Management Subsystem may use such maps to manage incidents. To keep the base map up to date, an update (map updates) can be acquired from a Map Update Provider. The update can be requested (map update request) when one is desired. Otherwise, the Map Update Provider could provide an update on a set schedule or as revisions warrant it.

  2. An incident can be a planned event. Event promoters can notify the Traffic Management Subsystem and/or the Emergency Management Subsystem of planned events (event plans). The details of the events such as time, location and expected crowd size can be provided to assist in preparing the response. If desired, a confirmation (event confirmation) that the event plans were received can be sent.

  3. The Traffic Management Subsystem can receive schedules of trains (railroad schedules) that have at-grade crossings so that street closures can be anticipated and travelers notified and/or response plans implemented. Additionally, the Traffic Management Subsystem can be notified by an Information Service Provider of routes to be taken by groups of vehicles, or special vehicles (logged vehicle routes) that might require specialized traffic control strategies.

  4. Equipment on the Roadway is constantly monitoring traffic conditions (traffic characteristics) such as volume, speed, density, etc. and can be analyzing the data to detect incidents. The Traffic Management Subsystem can control (traffic sensor control) and monitor (traffic flow) the sensors in or along the roadway. Roadway equipment can be coordinated (roadway equipment coordination) through peer-to-peer, master-slave or other configurations. Examples of this coordination might be between field masters and traffic sensors. The Traffic Operations Personnel apply control as part of traffic operator inputs, and receive outputs as part of traffic operator data.

  5. The Media may be monitoring traffic independently and may share information (external reports) including the identification of an incident with the Traffic Management Subsystem. Rail Operations may notify the Traffic Management Subsystem of railway-related incidents (railroad advisories) or notify the Emergency Management Subsystem of the same (incident information).

  6. The Emergency Management Subsystem may need to view and/or control (remote surveillance control) surveillance cameras and other equipment during an incident. The Traffic Management Subsystem controls the surveillance equipment (video surveillance control) and may place limits on their control by other agencies. The Traffic Management Subsystem receives traffic images from the surveillance equipment. The images are passed to the Traffic Operations Personnel (as part of traffic operator data). The Traffic Management Subsystem can provide the Emergency Management Subsystem with information on the current traffic conditions (road network conditions) and video images of the traffic (traffic images) to aid in the response to and management of the incident. Road network conditions and traffic images is also provided to the Information Service Provider to support monitoring by traveler information service providers and their clients. The Traffic Operations Personnel apply control as part of traffic operator inputs, and receive outputs as part of traffic operator data.

  7. Multiple Traffic Management Subsystems may share information (incident information, road network conditions and traffic images) including information on incidents and the response to them. The entire process is under the asynchronous monitoring (traffic operator data) and control (traffic operator inputs) of Traffic Operations Personnel.

  8. When an incident is detected, the Traffic Management Subsystem, the Maintenance and Construction Management Subsystem and the Emergency Management Subsystem will notify (incident information) the other subsystems and keep them updated throughout an extended incident. The Emergency Management Subsystem also exchanges incident information with Rail Operations. The Emergency Management and Traffic Management Subsystems also share incident information with the Information Service Provider Subsystem and the Transit Management Subsystem. The Emergency Management and Traffic Management Subsystems provides the Media with incident information that has been reviewed for public distribution (traffic information for media).

  9. Once an incident is detected and verified, incident response can begin. The incident response status is sent from the Emergency Management Subsystem to Traffic Management Subsystem, Maintenance and Construction Management Subsystem, Transit Management Subsystem, and Rail Operations. The Traffic Management Subsystem would also inform the Emergency Management Subsystem of its incident response status. In the case where the incident involves response by rail assets, then Rail Operations would inform Emergency Management Subsystem of its rail incident response status. The Emergency Management Subsystem may coordinate the response to incidents with Other Emergency Management (incident response coordination.) or may coordinate with Other Emergency Management the incident command assignment or status (incident command information coordination).

  10. A key to incident response is providing information to emergency vehicles by the Emergency Management Subsystem. The Emergency Systems Operator initiates the providing of information (as part of emergency operations inputs ). The Emergency Management Subsystem sends decision support information to the Emergency Vehicle Subsystem, which might contain information about the incident, information on dispatched resources, and ancillary information such as road and weather conditions. The information is forwarded to the Emergency Personnel with emergency personnel information presentation. The Emergency Personnel provide incident and dispatch status to the Emergency Vehicle Subsystem (as part of emergency personnel inputs). This incident status is sent to the Emergency Management Subsystem, where it is forwarded to the Emergency Systems Operator (as part of emergency operations status).

  11. Incident command posts may be set up at the scene of the incident to coordinate the overall incident response. The input of incident information and response status (described above) and the request for resources (described below) may be performed by Emergency Personnel on the scene. The architecture represents this as the interface between Emergency Management Subsystem and Emergency Personnel (incident command information presentation and incident command inputs).

  12. The next 3 steps are focused on incident management at or near international border crossings. Here the Border Inspection Systems participate in incident coordination along with the Traffic Management Subsystem and Emergency Management Subsystem, representing departments of transportation and public safety agencies with jurisdictions at or near the border.

  13. The Border Inspection Systems may view CCTV camera images (traffic images) that can be used to detect and verify traffic incidents at the border. The cameras may also be remotely controlled (remote surveillance control) with permission from the Traffic Management Subsystem.

  14. When an incident is identified at the border, information about the incident (border incident information) is shared between the Border Inspection System, Traffic Management Subsystem, and Emergency Management Subsystem. As public safety responds to the incident, the Border Inspection System and Traffic Management Subsystem are apprised of current response status (border incident response status and incident response status).

  15. To respond to an incident, the Emergency Management Subsystem may request resources (maint and constr resource request) such as cones, barricades, sand and help clearing roadway from the Maintenance and Construction Management Subsystem (MCMS). The request is initiated from the Emergency Systems Operator as part of emergency operations inputs. This request is presented to the Maintenance and Construction Center Personnel (maint and constr operations information presentation). With input from Maintenance and Construction Center Personnel (maint and constr center personnel inputs) and Other Maintenance and Construction (maint and constr resource coordination), a response to the resource request (maint and constr resource response) can be sent to the Emergency Management Subsystem. The response is presented to the Emergency Systems Operator as part of emergency operations status.

  16. In responding to an incident, the Emergency Management Subsystem may need assistance (resource request) from the Traffic Management Subsystem. This may be a request for service such as verifying incident location, implementing special traffic control, etc. or a specific request for resources such as cones, barriers, a front loader, etc. This request goes to the Traffic Operations Personnel (traffic operator data). If required, the Traffic Management Subsystem may request resources from the Maintenance and Construction Management Subsystem (maint and constr resource request). This request is initiated by the Traffic Operations Personnel as part of traffic operator inputs. This request is presented to the Maintenance and Construction Center Personnel (maint and constr operations information presentation). With input from Maintenance and Construction Center Personnel (maint and constr center personnel inputs) and Other Maintenance and Construction (maint and constr resource coordination), a response to the resource request (maint and constr resource response) can be sent back to the Traffic Management Subsystem, where it is provided to the Traffic Operations Personnel as part of traffic operator data. The Traffic Operations Personnel initiates a response to the request with traffic operator inputs. The Traffic Management Subsystem may then respond (resource deployment status) to the Emergency Management Subsystem on when the service will be implemented or the requested resource will arrive on the scene. Resource request and resource deployment status are bi-directional since the Traffic Management Subsystem may also request resources from the Emergency Management Subsystem.