Other ISP (Terminator*)
Representing other distinct Information Service Providers, this terminator is intended to provide a source and destination for ITS data flows between peer information and service provider functions. It enables cooperative information sharing between providers as conditions warrant. In the Physical Architecture this terminator is a reciprocal Information Service Provider (ISP) Subsystem.
Inputs/Outputs: Architecture Flows* and Data Flows*
Information Service Provider
Other ISP
- emergency traveler information (Architecture Flow*) - Public notification of an emergency such as a natural or man-made disaster, civil emergency, or child abduction. This flow also includes evacuation information including evacuation instructions, evacuation zones, recommended evacuation times, tailored evacuation routes and destinations, traffic and road conditions along the evacuation routes, traveler services and shelter information, and reentry times and instructions.
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*: - multimodal information (Architecture Flow*) - Schedule information for alternate mode transportation providers such as train, ferry, air and bus.
Data Flows*: - parking information (Architecture Flow*) - General parking information and status, including current parking availability.
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*: - transit service information (Architecture Flow*) - Transit service information including routes, schedules, and fare information as well as dynamic transit schedule adherence and transit vehicle location information.
Data Flows*:
Other ISP
Information Service Provider
- emergency traveler information (Architecture Flow*) - Public notification of an emergency such as a natural or man-made disaster, civil emergency, or child abduction. This flow also includes evacuation information including evacuation instructions, evacuation zones, recommended evacuation times, tailored evacuation routes and destinations, traffic and road conditions along the evacuation routes, traveler services and shelter information, and reentry times and instructions.
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*: - multimodal information (Architecture Flow*) - Schedule information for alternate mode transportation providers such as train, ferry, air and bus.
Data Flows*: - parking information (Architecture Flow*) - General parking information and status, including current parking availability.
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*: - transit service information (Architecture Flow*) - Transit service information including routes, schedules, and fare information as well as dynamic transit schedule adherence and transit vehicle location information.
Data Flows*:
