Interface: FAX Website - Central Transit Management Server

FAX Website to Central Transit Management Server Interface Diagram

Architecture Flow Definitions

archive requests  (Planned)  Applicable ITS Standards

A request to a data source for information on available data (i.e. "catalog") or a request that defines the data to be archived. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one-time response from the recipient.

archive status  (Planned)  Applicable ITS Standards

Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified.

emergency traveler information  (Planned)  Applicable ITS Standards

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.

emergency traveler information request  (Planned)  

Request for alerts, evacuation information, and other emergency information provided to the traveling public.

incident information  (Planned)  Applicable ITS Standards

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.

interactive traveler information  (Planned)  

Traveler information provided in response to a traveler request. The provided information includes traffic and road conditions, advisories, incidents, payment information, transit services, parking information, weather information, and other travel-related data updates and confirmations.

multimodal information  (Planned)  Applicable ITS Standards

Schedule information for alternate mode transportation providers such as train, ferry, air and bus.

parking information  (Planned)  Applicable ITS Standards

General parking information and status, including current parking availability.

road network conditions  (Planned)  Applicable ITS Standards

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.

traffic images  (Planned)  Applicable ITS Standards

High fidelity, real-time traffic images suitable for surveillance monitoring by the operator or for use in machine vision applications.

transit service information  (Planned)  Applicable ITS Standards

Transit service information including routes, schedules, and fare information as well as dynamic transit schedule adherence and transit vehicle location information.

travel services information  (Planned)  

Travel service information and reservations for tourist attractions, lodging, dining, service stations, emergency services, and other services and businesses of interest to the traveler.

travel services request  (Planned)  

Request for travel service information including tourist attractions, lodging, restaurants, service stations, and emergency services. The request identifies the type of service, the area of interest, optional reservation request information, parameters that are used to prioritize or filter the returned information, and sorting preferences.

traveler alerts  (Planned)  

Traveler information alerts reporting congestion, incidents, adverse road or weather conditions, parking availability, transit service delays or interruptions, and other information that may impact the traveler. Relevant alerts are provided based on traveler-supplied profile information including trip characteristics and preferences.

traveler archive data  (Planned)  Applicable ITS Standards

Data associated with traveler information services including service requests, facility usage, rideshare, routing, and traveler payment transaction data. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information.

traveler profile  (Planned)  

Information about a traveler including equipment capabilities, personal preferences, and traveler alert subscriptions.

traveler request  (Planned)  

A request for traveler information including traffic, transit, toll, parking, road weather conditions, event, and passenger rail information. The request identifies the type of information, the area of interest, parameters that are used to prioritize or filter the returned information, and sorting preferences.

trip confirmation  (Planned)  

Acknowledgement by the driver/traveler of acceptance of a trip plan with associated personal and payment information required to confirm reservations.

trip plan  (Planned)  

A travel itinerary identifying a route and associated traveler information and instructions identifying recommended modes and transfer information, ride sharing options, and transit and parking reservation information.

trip request  (Planned)  

Request for trip planning services that identifies the trip origin, destination(s), timing, preferences, and constraints. The request may also include a request for transit and parking reservations and ridesharing options associated with the trip.