Regional Architecture Logo
 

Send Your Comments

E-Mail

TMC Incident Detection Equipment Package

Architecture Geographic Scope

Description:

Remotely controls traffic and video sensors to support incident detection and verification; exchange information with other agencies including emergency management, maintenance and construction, alerting and advisory systems, event promoters, intermodal freight depots, and traveler information systems.

 

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 Lufkin District TMC

Functional Requirements:

1The center shall receive inputs from the Alerting and Advisory System concerning the possibility or occurrence of severe weather, terrorist activity, or other major emergency, including information provided by the Emergency Alert System.
2The center shall collect and store traffic flow and image data from the field equipment to detect and verify incidents.
3The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters, traveler information service providers, and intermodal freight depots.
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 support requests from emergency management centers to remotely control sensor and surveillance equipment located in the field.
6The center shall provide road network conditions and traffic images to emergency management centers to support the detection, verification, and classification of incidents.
7The center shall provide video and traffic sensor control commands to the field equipment to detect and verify incidents.
  

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.1TC shall include a Traffic Flow Optimization function to provide the capability to optimize traffic flow.
1.6.1.7Implementation of the Control function shall include strategies that account for at least the following:
1.6.1.7(a)Human factors.
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(e)Human operator support.
1.6.3.4.1Traffic Surveillance shall include a data process function to process the traffic data which are acquired.
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.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.3IM shall include a Response Implementation function to provide the services to implement a response coordinated with all appropriate agencies.
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.4IM shall provide the capability to Predict Hazardous Conditions, including the time and location of hazardous conditions that may cause an incident.
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.5RSEM shall include a Physical Security System (PSS) function.
5.1.3.5.2PSS shall allow system operators to monitor and control operation of the physical security system devices, including operator override.
5.1.3.5.3PSS shall provide current status of the system including readiness and activation to operators.
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(c)Review and update resource inventories
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.3Maintenance and Construction Operations shall provide a Work Zone Management and Safety (WZMS) function, which provides support for the effectiveness, safety, and efficiency of roadway operations during all work zone activities. This function includes interactions among Traffic Managers, Supervisors, Dispatchers, Field Crews, Construction Crews, Public Safety Organizations, Information Service Providers, and Travelers.
8.1.3.2WZMS shall support the management of data about work zones.
8.1.3.2.4WZMS shall provide information on work zone activities to other agencies, including but not limited to:
8.1.3.2.4(e)Traffic management systems
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(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.