Other Traffic Management (Terminator*)
Representing another Traffic Management center, system or subsystem, this terminator is intended to provide a source and destination for ITS data flows between peer (e.g. inter-regional) traffic management functions. It enables traffic management activities to be coordinated across different jurisdictional areas. In the Physical Architecture, this terminator is a reciprocal Traffic Management Subsystem (TMS).
Inputs/Outputs: Architecture Flows* and Data Flows*
Other Traffic Management
Traffic Management
- device control request (Architecture Flow*) - Request for device control action
Data Flows*: - device data (Architecture Flow*) - Data from detectors, environmental sensor stations, and traffic control devices including device inventory information.
Data Flows*: - device status (Architecture Flow*) - Status information from devices
Data Flows*: - emergency traffic coordination (Architecture Flow*) - Coordination supporting disaster response including evacuation and reentry. Includes coordination of special traffic control strategies that support efficient evacuation and reentry while protecting and optimizing movement of response vehicles and other resources responding to the emergency.
Data Flows*: - incident information (Architecture Flow*) - Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system.
Data Flows*: - road network conditions (Architecture Flow*) - Current and forecasted traffic information, road and weather conditions, and other road network status. Either raw data, processed data, or some combination of both may be provided by this architecture flow. Information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements) in effect is included along with a definition of the links, nodes, and routes that make up the road network.
Data Flows*: - traffic images (Architecture Flow*) - High fidelity, real-time traffic images suitable for surveillance monitoring by the operator or for use in machine vision applications.
Data Flows*:
Traffic Management
Other Traffic Management
- device control request (Architecture Flow*) - Request for device control action
Data Flows*: - device data (Architecture Flow*) - Data from detectors, environmental sensor stations, and traffic control devices including device inventory information.
Data Flows*: - device status (Architecture Flow*) - Status information from devices
Data Flows*: - emergency traffic coordination (Architecture Flow*) - Coordination supporting disaster response including evacuation and reentry. Includes coordination of special traffic control strategies that support efficient evacuation and reentry while protecting and optimizing movement of response vehicles and other resources responding to the emergency.
Data Flows*: - incident information (Architecture Flow*) - Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system.
Data Flows*: - road network conditions (Architecture Flow*) - Current and forecasted traffic information, road and weather conditions, and other road network status. Either raw data, processed data, or some combination of both may be provided by this architecture flow. Information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements) in effect is included along with a definition of the links, nodes, and routes that make up the road network.
Data Flows*: - traffic images (Architecture Flow*) - High fidelity, real-time traffic images suitable for surveillance monitoring by the operator or for use in machine vision applications.
Data Flows*:
