Regional Architecture Logo
 

Send Your Comments

E-Mail

TMC Incident Dispatch Coordination/Communication Equipment Package

Architecture Geographic Scope

Description:

Center-based capability to formulate an incident response that takes into account the incident potential, incident impacts, and/or resources required for incident management including proposing and facilitating the dispatch of emergency response and service vehicles as well as coordinating response with all appropriate cooperating agencies.

 

Included in:

City of Livingston Traffic Operations Center
City of Lufkin Traffic Operations Center
City of Nacogdoches Traffic Operations Center
Municipal or County Traffic Operations Center
TranStar and Other Texas Region TMCs
TxDOT Fort Worth TMC (TransVision)
TxDOT Lufkin District TMC

Functional Requirements:

1The center shall exchange alert information and status with emergency management centers. The information includes notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction for distribution to the public. The information may include the alert originator, the nature of the emergency, the geographic area affected by the emergency, the effective time period, and information and instructions necessary for the public to respond to the alert. This may also identify specific information that should not be released to the public.
2The center shall coordinate planning for incidents with emergency management centers - including pre-planning activities for disaster response, evacuation, and recovery operations.
3The center shall support requests from emergency management centers to remotely control sensor and surveillance equipment located in the field, provide special routing for emergency vehicles, and to provide responding emergency vehicles with signal preemption.
4The center shall exchange incident and threat information with emergency management centers as well as maintenance and construction centers; including notification of existence of incident and expected severity, location, time and nature of incident.
5The center shall respond to requests from emergency management to provide traffic management resources to implement special traffic control measures, assist in clean up, verify an incident, etc. This may also involve coordination with maintenance centers.
6The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters, traveler information service providers, media, and rail operations centers.
7The center shall provide road network conditions and traffic images to emergency management centers, maintenance and construction centers, and traveler information service providers.
8The center shall exchange road network status assessment information with emergency management and maintance centers including an assessment of damage sustained by the road network including location and extent of the damage, estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame for repair and recovery.
9The center shall coordinate information and controls with other traffic management centers.
10The center shall receive inputs from emergency management and transit management centers to develop an overall status of the transportation system including emergency transit schedules in effect and current status and condition of the transportation infrastructure.
11The center shall support an interface with a map update provider, or other appropriate data sources, through which updates of digitized map data can be obtained and used as a background for traffic incident management.
  

User Service Requirements (fully or partially addressed):

1.0TRAVEL AND TRAFFIC MANAGEMENT
1.6TRAFFIC CONTROL
1.6.0ITS shall include a Traffic Control (TC) function. Traffic Control provides the capability to efficiently manage the movement of traffic on streets and highways. Four functions are provided, which are, (1) Traffic Flow Optimization, (2) Traffic Surveillance, (3) Control, and (4) Provide Information. This will also include control of network signal systems with eventual integration of freeway control.
1.6.2TC shall include a Traffic Surveillance function.
1.6.2.2Traffic Surveillance shall include a data collect function to provide the capability to collect data for determining traffic flow and prediction.
1.6.2.2.1The data collect function shall provide the capability to quickly feedback traffic data to the control processes.
1.6.2.3Traffic Surveillance shall include a wide-area surveillance capability to include several jurisdictions.
1.6.2.3.2The wide-area surveillance shall cover a large number of roadway segments.
1.6.2.4TC shall provide the capability to acquire detailed traffic measurements at specific locations.
1.6.2.4.1Traffic Surveillance shall include a data process function to process the traffic data which are acquired.
1.6.2.5The wide area surveillance shall acquire sufficient data to provide the system with the knowledge of the existing conditions.
1.6.2.5.2The data process function shall process traffic data to generate near term predictions of traffic conditions.
1.6.3TC shall include a Device Control function.
1.6.3.4Device Control shall communicate control data to the following devices.
1.6.3.4.1Traffic Surveillance shall include a data process function to process the traffic data which are acquired.
1.6.3.5Device Control shall provide the operator with the capability to manually override the system's automatic controls.
1.6.3.6Device Control shall provide the operator the capability to adaptively change system response in order to provide a response that is coordinated with other TMCs responding to incidents.
1.6.4Device Control shall provide traffic control information to other elements of the ITS, including but not limited to the following:
1.6.4(a)In-vehicle navigation.
1.6.4(b)Trip planning.
1.6.4(c)Routing systems.
1.6.4(d)Fleet management systems.
1.7INCIDENT MANAGEMENT
1.7.0ITS shall include an Incident Management (IM) function. Incident Management will identify incidents, formulate response actions, and support initiation and ongoing coordination of those response actions. Four major functions are provided, which are, (1) Incidents Identification, (2) Response Formulation, (3) Response Implementation, and (4) Predict Hazardous Conditions.
1.7.1Incident Management shall provide an Incident Identification function to identify incidents.
1.7.1.1The Incident Identification function shall include the capability to identify predicted incidents.
1.7.1.1.1The Incident Identification function shall use information from the following types of sources, where available, to identify predicted incidents:
1.7.1.1.1(a)Traffic flow sensors.
1.7.1.1.1(b)Environmental sensors.
1.7.1.1.1(c)Public safety sources.
1.7.1.1.1(d)Media sources.
1.7.1.1.1(e)Weather information sources.
1.7.1.1.1(f)Transportation providers.
1.7.1.1.1(g)Sponsors of special events.
1.7.1.1.1(h)Hazardous condition prediction algorithms.
1.7.1.1.2The Incident Identification function shall determine at least the following characteristics of each predicted incident:
1.7.1.1.2(a)Type (including Terrain Hazards).
1.7.1.1.2(b)Extent.
1.7.1.1.2(c)Severity.
1.7.1.1.2(d)Location.
1.7.1.1.2(e)Expected duration.
1.7.1.1.3The Incident Identification function shall determine the expected traffic flow impact of each predicted incident.
1.7.1.2The Incident Identification function shall include the capability to identify existing (both planned and unplanned) incidents.
1.7.1.2.1The Incident Identification function shall use information from the following types of sources, where available, to identify existing incidents:
1.7.1.2.1(a)Traffic flow sensors.
1.7.1.2.1(b)Environmental sensors.
1.7.1.2.1(c)Public safety sources.
1.7.1.2.1(d)Media sources.
1.7.1.2.1(e)Weather information sources.
1.7.1.2.1(f)Transportation providers.
1.7.1.2.1(g)Travelers.
1.7.1.2.2The Incident Identification function shall determine and continuously monitor at least the following characteristics of each existing incident:
1.7.1.2.2(a)Type (including Terrain Hazards).
1.7.1.2.2(b)Extent.
1.7.1.2.2(c)Severity.
1.7.1.2.2(d)Location.
1.7.1.2.2(e)Expected duration.
1.7.1.2.3The Incident Identification function shall determine and continuously monitor the current and expected traffic flow impact of each existing incident.
1.7.2IM shall provide a Response Formulation function to formulate appropriate response actions to each identified incident and revise those actions when necessary.
1.7.2.1The Response Formulation function shall propose and facilitate the appropriate scheduling of those predicted incidents that can be scheduled to minimize incident potential, incident impacts, and/or the resources required for incident management.
1.7.2.2The Response Formulation function shall propose and facilitate the appropriate dispatch of emergency response vehicles to an incident.
1.7.2.3The Response Formulation function shall propose and facilitate the appropriate dispatch of service vehicles to an incident.
1.7.2.4The Response Formulation function shall propose and facilitate the appropriate dissemination of incident related information to travelers and potential travelers.
1.7.2.5The Response Formulation function shall propose and facilitate the appropriate control of traffic signals and other traffic control to reduce the traffic flow impact of an incident.
1.7.3IM shall include a Response Implementation function to provide the services to implement a response coordinated with all appropriate agencies.
1.7.3.1The Response Implementation function shall provide at least the following decision support capabilities needed to implement coordinated incident response actions by all participating institutions:
1.7.3.1(a)Response Implementation shall allow coordinated selection/determination of the procedures, including alternate routes, needed for resolution of each incident and provide the procedures to those agencies responding to the incident.
1.7.3.1(b)Response Implementation shall provide the status of all resources needed for incident resolution to those agencies responding to the incident.
1.7.3.2The Response Implementation function shall provide a link between Incident Management and all other user services necessary to implement incident response actions.
1.7.3.3The Response Implementation function shall provide the capability to disseminate information relating to response status to other agencies and user services.
1.7.4IM shall provide the capability to Predict Hazardous Conditions, including the time and location of hazardous conditions that may cause an incident.
1.8TRAVEL DEMAND MANAGEMENT
1.8.1TDM shall include a communications function.
1.8.1.4The communications function shall provide the capability to send information and data as needed to implement management and control strategies that respond to changing environments, conditions, and policy needs to include, but not limited to, the following:
1.8.1.4(a)Sensor data.
1.8.2TDM shall include a processing function.
1.8.2.3Strategies developed by the processing function shall include the guidance for the operation of physical systems that:
1.8.2.3(a)Monitor traffic.
1.8.2.3(d)Detect traffic.
1.10HIGHWAY RAIL INTERSECTION
1.10.0ITS shall include a Highway-Rail Intersection (HRI) function to control highway and rail traffic in at-grade HRIs. Two sub-services are supported: Standard Speed Rail Subservice which is applicable to light rail transit, commuter rail and heavy rail trains with operational speeds up to 79 miles per hour (MPH); and High Speed Rail Subservice which is applicable to all passenger and freight trains with operational speeds from 80 to 125 MPH.
1.10.2HRI shall provide interfaces between highway and rail management functions.
1.10.2.1HRI shall provide information management interfaces between highway and rail to coordinate traffic, demand and schedules.
4.5HAZARDOUS MATERIAL SECURITY AND INCIDENT RESPONSE
4.5.4HSIR shall include a HAZMAT Security (HS) function.
4.5.4.3HS shall include a Driver Authentication function (DA)
4.5.4.3.7DA shall include the capability to notify traffic management if an unauthorized driver attempts to operate the vehicle.
5.0EMERGENCY MANAGEMENT
5.1EMERGENCY NOTIFICATION AND PERSONAL SECURITY
5.1.3ENPS shall include a Remote Security and Emergency Monitoring (RSEM) function to create an environment of safety in secure areas.
5.1.3.4RSEM shall include a Monitor Alert Levels (MAL) function.
5.1.3.4.3MAL shall increase system preparedness as the likelihood of an incident increases, including:
5.1.3.4.3(a)Activating physical security systems and implementing security procedures
5.1.3.4.3(b)Adjusting parameters of surveillance and sensor devices.
5.1.5ENPS shall include a Protect Sensitive Traveler Information (PSTI) function to inhibit distribution of traveler information that is deemed to be sensitive.
5.1.5.1PSTI shall notify transportation operators and information providers when access to information from ITS surveillance and sensor systems must be restricted.
5.1.5.2The PSTI notification shall identify the geographic area, time, specific devices, and/or other information necessary to determine the traveler information that must be protected.
5.1.5.3PSTI shall restrict access to traveler information for the affected area until access restrictions are removed.
5.1.5.4PSTI shall notify transportation operators and information providers when traveler information access restrictions are removed.
5.3DISASTER RESPONSE AND EVACUATION
5.3.0ITS shall provide a Disaster Response and Evacuation (DRE) function that provides for effective, coordinated management of the surface transportation system during all types of disasters including natural disasters (hurricanes, earthquakes, floods, severe winter storms, tsunamis, etc.), terrorist acts, and other catastrophic events (e.g., nuclear power plant disasters). Two primary subservices are provided: (1) Disaster Response and (2) Evacuation Coordination. The Disaster Response Subservice provides support for planning, transportation management, resource sharing, and information coordination between transportation agencies and principal responding agencies (emergency management, public safety, and other allied agencies) to improve the effectiveness and safety of a disaster response. The Disaster Response Subservice consists of eight major functions: 1) Coordinate Response Plans, 2) Monitor Alert Levels, 3) Detect and Verify Emergency, 4) Assess Infrastructure Status, 5) Coordinate Response, 6) Critical Service Restoration, 7) Manage Area Transportation, and 8) Disaster Traveler Information. The Evacuation Coordination (EC) Subservice efficiently manages an evacuation and provides evacuees with the information they need during evacuation and subsequent reentry to the evacuated area. The Evacuation Coordination (EC) subservice includes four additional major functions: 9) Evacuation Planning Support, 10) Evacuation Traveler Information, 11) Evacuation Transportation Management, and 12) Evacuation Resource Sharing.
5.3.2Disaster Response shall provide a Monitor Alert Levels (MAL) function.
5.3.2.2MAL shall increase system preparedness as the alert level or the likelihood of a disaster increases, taking actions including:
5.3.2.2(a)Activating physical security systems and implementing security procedures,
5.3.2.2(c)Review and update resource inventories
5.3.2.2(g)Implement traffic management strategies and traffic control plans
5.3.5Disaster Response shall include a Manage Area Transportation (MAT) function that manages the transportation system in the vicinity of the disaster. Depending on the nature of the disaster and the status of the infrastructure, the following actions may be taken.
5.3.5.1Detours or alternative transportation resources, including transit systems, shall be identified to mitigate the transportation impacts of the disaster.
5.3.5.2Closures and detours shall be implemented. Closures may exclude all vehicles except for emergency vehicles or other special vehicles.
5.3.5.4Special traffic control strategies to manage traffic in the vicinity of the disaster shall be implemented to limit and/or manage traffic in the area to include signal timing modifications and special traffic signal modes used in conjunction with personnel manually directing traffic.
5.3.5.5Special traffic management strategies shall be implemented in surrounding areas to support efficient movement of personnel and resources into the disaster area.
5.3.7Disaster Response shall include a Coordinate Response (CR) function to coordinate the disaster response between transportation, public safety, emergency management, and other allied agencies. Information may be shared with individual agency centers, emergency operations centers, and unified command systems at the scene.
5.3.7.1CR shall provide information about the transportation system including:
5.3.7.1(c)Traffic management strategies in effect, including closures, detours, tolls, and HOV restrictions.
5.3.7.1(d)Routes for specific origins and destinations on request
5.3.11Evacuation Coordination shall provide an Evacuation Transportation Management (ETM) function to assist evacuation coordination personnel as they manage evacuation operations.
5.3.11.3ETM shall include a strategy selection function that maximizes efficiency during evacuation and reentry operations and supports the overall response plan of the principal responding agencies.
5.3.11.3.1The strategy shall integrate the control of freeways and surface streets.
5.3.11.4ETM shall provide the control of devices as required by the evacuation management plan, including:
5.3.11.4(a)traffic signals,
5.3.11.4(b)dynamic message signs,
5.3.11.4(c)ramp meters,
5.3.11.4(d)reversible lane signs,
5.3.11.4(e)turning restriction signs,
5.3.11.4(f)road closure devices,
5.3.11.4(g)lane closure devices,
5.3.11.4(h)HAR,
5.3.11.4(j)shoulder use signs.
5.3.11.12ETM shall implement special traffic control strategies including traffic diversions and closures if emergency termination of an in-process evacuation is required.
7.0INFORMATION MANAGEMENT
7.1ARCHIVED DATA FUNCTION
7.1.0ITS shall provide an Archived Data Function to control the archiving and distribution of ITS data. The Archived Data User Service provides the Historical Data Archive Repositories and controls the archiving functionality for all ITS data with five major functions: 1) the Operational Data Control function to manage operations data integrity; 2) the Data Import and Verification function to acquire historical data from the Operational Data Control function; 3) the Automatic Data Historical Archive function for permanently archiving the data; 4) the Data Warehouse Distribution function, which integrates the planning, safety, operations, and research communities into ITS and processes data products for these communities; and 5) the ITS Community Interface which provides the ITS common interface to all ITS users for data products specification and retrieval. ADUS helps achieve the ITS information goal of unambiguous interchange and reuse of data and information throughout all functional areas.
7.1.3The Archived Data Function shall include a Data Import and Verification (DIV) function to acquire historical data from the Operational Data Control function.
7.1.3.1DIV shall be capable of importing selected ITS Operational data from the ITS Operational Repositories.
7.1.3.1.9DIV shall be capable of importing data on ITS Physical Characteristics of Transportation Infrastructure to include:
7.1.3.1.9(d)Transportation facilities.
8.0MAINTENANCE AND CONSTRUCTION MANAGEMENT
8.1MAINTENANCE AND CONSTRUCTION OPERATIONS
8.1.0ITS shall provide Maintenance and Construction Operations (MCO) functions to support monitoring, operating, maintaining, improving and managing the physical condition of roadways, the associated infrastructure equipment, and the required resources. MCO shall focus on four major functions: 1) the Maintenance Vehicle Fleet Management function, to monitor and track locations and conditions of fleets of maintenance, construction, and specialized service vehicles; 2) the Roadway Management function, to monitor and forecast conditions and manage treatment of roadways during various travel conditions; 3) the Work Zone Management and Safety function, to support effective and efficient roadway operations during work zone activities; and 4) the Roadway Maintenance Conditions and Work Plan Dissemination function, to coordinate work plans and to communicate conditions. This User Service will utilize ITS systems and processes to support interchange of information among diverse groups of users, to improve efficiency and effectiveness of operational, maintenance, and managerial activities.
8.1.1Maintenance and Construction Operations shall provide a Maintenance Vehicle Fleet Management (MVFM) function to schedule and dispatch, monitor and track location, and monitor operational condition and maintenance requirements of public and contracted fleets of maintenance, construction, and specialized service vehicles. This function includes interactions among Traffic Managers, Supervisors, Dispatchers, Field Crews, Construction Crews, Vehicle Maintenance Crews, Equipment Maintenance Crews, Weather Services Organizations, and Information Service Providers.
8.1.1.6MVFM shall be capable of providing dispatchers and operators of maintenance, construction, and specialized service vehicles with information regarding potential and actual roadway problems.
8.1.1.6.1MVFM shall provide information to dispatchers and vehicle operators, including but not limited to:
8.1.1.6.1(a)Congestion
8.1.1.6.1(b)Incidents
8.1.2Maintenance and Construction Operations shall provide a Roadway Management (RWM) function to monitor traffic, road surface, and environmental conditions and forecast traffic and road surface conditions to support management of routine and hazardous road condition remediation and to communicate changes in conditions. This function includes interactions among Traffic Managers, Supervisors, Dispatchers, Field Crews, Construction Crews, Asset Managers, Planning Agencies, and Weather Services Organizations.
8.1.2.1RWM shall support a number of different services, including but not limited to:
8.1.2.1(c)Emergency activities (incident response, planning, alternate routing, etc.)
8.1.4Maintenance and Construction Operations shall provide a Roadway Maintenance Conditions and Work Plan Dissemination (RMCWPD) function to provide Intra- and Inter-agency coordination of work plans. This function includes interactions among Traffic Managers, Supervisors, Planning Agencies, Public Safety Organizations, and Information Service Providers.
8.1.4.1RMCWPD shall coordinate information on planned maintenance and construction activities, including work zone information, and unplanned remediation activities, such as inclement weather responses, so that routing, scheduling, and resource allocation can be accomplished.
8.1.4.2RMCWP shall support inter-agency coordination of response and scheduling of resources for significant events with broad impact, like natural disasters, major incidents, and large planned or seasonal events.
8.1.4.3RMCWPD shall coordinate information with other transportation agencies, including but not limited to:
8.1.4.3(a)Public Safety
8.1.4.3(b)Emergency Medical Management
8.1.4.3(d)Traffic Management
  
The detailed process and user service requirement traceability information on this page was extracted from the National ITS Architecture. Consult the National ITS Architecture web site for more information.

Last updated on 05-25-2005 using Ronald C. Ice and Associates Web Spinner Technology.