| Architecture Flow |
Architecture Flow Description |
|
alarm acknowledge |
Confirmation that alarm was received, instructions and additional information for the alarm initiator, and requests for additional information. |
|
alarm notification |
Notification of activation of an audible or silent alarm by a traveler in a public area or by a transit vehicle operator using an on-board device. |
|
alerts and advisories |
Assessments (general incident and vulnerability awareness information), advisories (identification of threats or recommendations to increase preparedness levels), and alerts (information on imminent or in-progress emergencies). This flow also provides supporting descriptive detail on incidents, threats, and vulnerabilities to increase preparedness and support effective response to threats against the surface transportation system. |
|
archive coordination |
Catalog data, meta data, published data, and other information exchanged between archives to support data synchronization and satisfy user data requests. |
|
archive requests |
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 |
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. |
|
archived data product requests |
A user-specified request for archived data products (i.e. data, meta data, or data catalogs). The request also includes information that is used to identify and authenticate the user and support electronic payment requirements, if any. |
|
archived data products |
Raw or processed data, meta data, data catalogs and other data products provided to a user system upon request. The response may also include any associated transaction information. |
|
audit data |
Information to support a tax audit. |
|
bad tag list |
List of invalid transit user tags which may have previously failed a fare payment transaction. |
|
broadcast traveler information |
General traveler information that contains traffic and road conditions, link travel times, incidents, advisories, restrictions, transit service information, weather information, parking information, and other related traveler information. |
|
care facility status |
Information regarding facility type and capabilities, facility status, and its ability to admit new patients. |
|
care facility status request |
Request for information regarding care facility availability and status. |
|
compliance review report |
Report containing results of carrier compliance review, including concomitant out-of-service notifications, carrier warnings/notifications. The information may be provided as a response to a real-time query of proactively by the source. The query flow is not explicitly shown. |
|
credential application |
Application for commercial vehicle credentials. Authorization for payment is included. |
|
credentials information |
Response containing full vehicle fuel tax and registration credentials information. "Response" may be provided in reaction to a real-time query or a standing request for updated information. The query flow is not explicitly shown. |
|
credentials status information |
Credentials information such as registration, licensing, insurance, check flags, and electronic screening enrollment data. A unique identifier is included. Corresponds to the credentials portion of CVISN "snapshots." The status information may be provided as a response to a real-time query or as a result of a standing request for updated information (subscription). This may also include information about non-U.S. fleets for use by U.S. authorities, and information regarding U.S. fleets made available to Mexican and Canadian authorities. The query flow is not explicitly shown. |
|
current asset restrictions |
Restrictions levied on transportation asset usage based on infrastructure design, surveys, tests, or analyses. This includes standard facility design height, width, and weight restrictions, special restrictions such as spring weight restrictions, and temporary facility restrictions that are imposed during maintenance and construction. |
|
cv driver record |
Information typically maintained by a state driver licensing agency about a driver of a commercial vehicle including driver identification data, license data, permit data, and driving history details. |
|
cv driver record request |
A request for information about a commercial vehicle driver. |
|
CVC override mode |
This flow represents the tactile or auditory interface with ITS equipment containing the manual override of automated pass/pull-in decisions generated by the Commercial Vehicle Check station. |
|
CVO inspector information |
This flow represents the visual or auditory interface with ITS equipment containing credential, safety, and preclearance information and instructions to the commercial vehicle inspector. |
|
CVO inspector input |
This flow represents the tactile or auditory interface with ITS equipment containing requests from the commercial vehicle inspector to operate the commercial vehicle inspection station. |
|
CVO weight and presence |
Physical attribute of commercial vehicle that can be measured (for example, weight, number of axels, axel spacing, etc.). |
|
demand response passenger and use data |
Data collected on board a demand response vehicle relating to the picking up and discharging of passengers. |
|
demand responsive transit plan |
Plan regarding overall demand responsive transit schedules and deployment. |
|
demand responsive transit request |
Request for paratransit support. |
|
electronic lock data |
Notification to roadside (via transponder) of the presence and status of electronic cargo locks. |
|
electronic lock data request |
Request from roadside for data regarding presence and status of electronic cargo locks. |
|
emergency acknowledge |
Acknowledge request for emergency assistance and provide additional details regarding actions and verification requirements. |
|
emergency archive data |
Logged emergency information including information that characterizes identified incidents (routine highway incidents through disasters), corresponding incident response information, evacuation information, surveillance data, threat data, and resource information. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information. |
|
emergency data request |
A request for additional information or a control command issued by the emergency response agency in response to an emergency request for assistance from a traveler. |
|
emergency dispatch requests |
Emergency vehicle dispatch instructions including incident location and available information concerning the incident. |
|
emergency dispatch response |
Request for additional emergency dispatch information and provision of en route status. |
|
emergency notification |
An emergency request for assistance automatically initiated by a vehicle or originated by a traveler using an in-vehicle or personal device. |
|
emergency plan coordination |
Information that supports coordination of emergency management plans, continuity of operations plans, emergency response and recovery plans, evacuation plans, and other emergency plans between agencies. This includes general plans that are coordinated prior to an incident and shorter duration tactical plans that are prepared during an incident. |
|
emergency traffic control information |
Status of a special traffic control strategy or system activation implemented in response to an emergency traffic control request, a request for emergency access routes, a request for evacuation, a request to activate closure systems, a request to employ driver information systems to support public safety objectives, or other special requests. Identifies the selected traffic control strategy and system control status. |
|
emergency traffic control request |
Special request to preempt the current traffic control strategy in effect at one or more signalized intersections or highway segments, activate traffic control and closure systems such as gates and barriers, activate safeguard systems, or use driver information systems. For example, this flow can request all signals to red-flash, request a progression of traffic control preemptions along an emergency vehicle route, request a specific evacuation traffic control plan, request activation of a road closure barrier system, or place a public safety or emergency-related message on a dynamic message sign. |
|
emergency transit schedule information |
Information on transit schedule and service changes that adapt the service to better meet needs of responders and the general public in an emergency situation, including special service schedules supporting evacuation. |
|
emergency transit service request |
Request to modify transit service and fare schedules to address emergencies, including requests for transit services to evacuate people from and/or deploy response agency personnel to an emergency scene. The request may poll for resource availability or request pre-staging, staging, or immediate dispatch of transit resources. |
|
emergency transit service response |
Response indicating changes to transit service, fares, and/or restrictions that will be made and status of transit resources to be deployed to support emergency response and/or evacuation. |
|
emergency vehicle tracking data |
The current location and operating status of the emergency vehicle. |
|
environmental conditions data |
Current road conditions (e.g., surface temperature, subsurface temperature, moisture, icing, treatment status) and surface weather conditions (e.g., air temperature, wind speed, precipitation, visibility) as measured and reported by fixed and/or mobile environmental sensors and aggregated by the data collector. Attributes relating to the data collection (and aggregation) are also included. |
|
environmental conditions data status |
Status of the data quality of environmental conditions data provided by a data contributor. Includes not only status by sensor, but statistical data regarding the quality checking of data provided. |
|
environmental probe data |
Data from vehicle safety and convenience systems that can be used to estimate environmental conditions, including measured air temperature, exterior light status, wiper status, sun sensor status, rain sensor status, traction control status, anti-lock brake status, and other collected vehicle system status and sensor information. The collected data is reported along with the location, heading, and time that the data was collected. Both current data and snapshots of recent events (e.g., traction control or anti-lock brake system activations) may be reported. |
|
environmental sensor data |
Current road conditions (e.g., surface temperature, subsurface temperature, moisture, icing, treatment status) and surface weather conditions (e.g., air temperature, wind speed, precipitation, visibility) as measured and reported by fixed and/or mobile environmental sensors. Operational status of the sensors is also included. |
|
environmental sensors control |
Data used to configure and control environmental sensors. |
|
equipment availability |
An inventory of the maintenance and construction equipment available at the storage facility. This flow includes the type of equipment, enough descriptive information to indicate its suitability for use, and its current status. This flow may contain information for a specific type of equipment or include all equipment available at the facility. |
|
equipment maintenance status |
Current status of field equipment maintenance actions. |
|
evacuation coordination |
Coordination of information regarding a pending or in-process evacuation. Includes evacuation zones, evacuation times, evacuation routes, forecast network conditions, and reentry times. |
|
evacuation information |
Evacuation instructions and information including evacuation zones, evacuation times, and reentry times. |
|
event plans |
Plans for major events possibly impacting traffic. |
|
fare collection data |
Fare collection information including the summary of on-board fare system data and financial payment transaction data. |
|
fare management information |
Transit fare information and transaction data used to manage transit fare processing on the transit vehicle. |
|
field device status |
Reports from field equipment (sensors, signals, signs, controllers, etc.) which indicate current operational status. |
|
field equipment status |
Identification of field equipment requiring repair and known information about the associated faults. |
|
highway control status |
Current traffic control equipment status that indicates operational status and right-of-way availability to the non-highway transportation mode at a multimodal crossing. |
|
hri advisories |
Notification of Highway-Rail Intersection equipment failure, intersection blockage, or other condition requiring attention, and maintenance activities at or near highway rail intersections. |
|
hri control data |
Data required for HRI information transmitted at railroad grade crossings and within railroad operations. |
|
hri operational status |
Status of the highway-rail grade crossing equipment including both the current state or mode of operation and the current equipment condition. |
|
hri request |
A request for highway-rail intersection status or a specific control request intended to modify HRI operation. |
|
hri status |
Status of the highway-rail intersection equipment including both the current state or mode of operation and the current equipment condition. |
|
incident command information coordination |
Information that supports local management of an incident. It includes resource deployment status, hazardous material information, traffic, road, and weather conditions, evacuation advice, and other information that enables emergency or maintenance personnel in the field to implement an effective, safe incident response. |
|
incident information |
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. |
|
incident information for rail_ud |
Incident information provided to Rail Operations regarding vehicle or roadway incidents that would impact Rail Operations. |
|
incident report |
Report of an identified incident including incident location, type, severity and other information necessary to initiate an appropriate incident response. |
|
incident response coordination |
Incident response procedures and current incident response status that are shared between allied response agencies to support a coordinated response to incidents. This flow provides current situation information, including a summary of incident status and its impact on the transportation system and other infrastructure, and current and planned response activities. This flow also coordinates a positive hand off of responsibility for all or part of an incident response between agencies. |
|
incident response status |
Status of the current incident response including a summary of incident status and its impact on the transportation system, traffic management strategies implemented at the site (e.g., closures, diversions, traffic signal control overrides), and current and planned response activities. |
|
incident status |
Information gathered at the incident site that more completely characterizes the incident and provides current incident response status. |
|
infrastructure monitoring sensor control |
Data used to configure and control infrastructure monitoring sensors. |
|
infrastructure monitoring sensor data |
Data read from infrastructure-based sensors that monitor the condition or integrity of transportation infrastructure including bridges, tunnels, interchanges, pavement, culverts, signs, transit rail or guideway, and other roadway infrastructure. Includes sensor data and the operational status of the sensors. |
|
interactive traveler information |
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. |
|
ISP coordination |
Coordination and exchange of transportation information between centers. This flow allows a broad range of transportation information collected by one ISP to be redistributed to many other ISPs and their clients. |
|
local signal preemption request |
Direct control signal or message to a signalized intersection that results in preemption of the current control plan and grants right-of-way to the requesting vehicle. |
|
local signal priority request |
Request from a vehicle to a signalized intersection for priority at that intersection. |
|
maint and constr dispatch information |
Information used to dispatch maintenance and construction vehicles, equipment, and crews and information used to keep work zone crews informed. This information includes routing information, traffic information, road restrictions, incident information, environmental information, decision support information, maintenance schedule data, dispatch instructions, personnel assignments, alert notifications, and corrective actions. |
|
maint and constr dispatch status |
Current maintenance and construction status including work data, operator status, crew status, and equipment status. |
|
maint and constr equipment repair status |
Current maintenance and repair status of the maintenance and construction vehicle fleet and other support equipment. This information includes a record of all maintenance and repair activities performed. |
|
maint and constr fleet information |
Information supporting maintenance of the maintenance and construction vehicle fleet and other support equipment. This information includes vehicle status and diagnostic information, vehicle utilization, and coordination of when vehicles will be available for preventative and corrective maintenance. |
|
maint and constr resource coordination |
Request for road maintenance and construction resources that can be used in the diversion of traffic (cones, portable signs), clearance of a road hazard, repair of ancillary damage, or any other incident response. |
|
maint and constr resource request |
Request for road maintenance and construction resources that can be used in the diversion of traffic (cones, portable signs), clearance of a road hazard, repair of ancillary damage, or any other incident response. The request may poll for resource availability or request pre-staging, staging, or immediate dispatch of resources. |
|
maint and constr resource response |
Current status of maintenance and construction resources including availability and deployment status. General resource inventory information covering vehicles, equipment, materials, and people and specific resource deployment status may be included. |
|
maint and constr vehicle conditions |
Vehicle diagnostics information that is collected, filtered, and selectively reported by a maintenance and construction vehicle. The information includes engine temperature, mileage, tire wear, brake wear, belt wear, and any warnings or alarms concerning the operational condition of the vehicle and ancillary equipment. |
|
maint and constr vehicle location data |
The current location and related status (e.g., direction and speed) of the maintenance/construction vehicle. |
|
maint and constr vehicle operational data |
Data that describes the maintenance and construction activity performed by the vehicle. Operational data includes materials usage (amount stored and current application rate), operational state of the maintenance equipment (e.g., blade up/down, spreader pattern), vehicle safety status, and other measures associated with the operation of a maintenance, construction, or other special purpose vehicle. Operational data may include basic operational status of the vehicle equipment or a more precise record of the work performed (e.g., application of crack sealant with precise locations and application characteristics). |
|
maint and constr vehicle system control |
Configure and control data that supports remote control of on-board maintenance and construction vehicle systems and field equipment that is remotely controlled by the vehicle. For example, the data can be used to adjust material application rates and spread patterns. |
|
maint and constr work plans |
Future construction and maintenance work schedules and activities including anticipated closures with anticipated impact to the roadway, alternate routes, anticipated delays, closure times, and durations. |
|
maintenance materials storage status |
The amount and availability of maintenance materials in storage facilities. |
|
maintenance status_ud |
Current maintenance status of vehicle. |
|
multimodal crossing status |
Indication of operational status and pending requests for right-of-way from equipment supporting the non-highway mode at multimodal crossings. |
|
multimodal information |
Schedule information for alternate mode transportation providers such as train, ferry, air and bus. |
|
multimodal information request |
Information request for alternate mode transportation providers such as train, ferry, air and bus. |
|
multimodal service data |
Multimodal transportation schedules and other service information. |
|
parking demand management request |
Request to change the demand for parking facility use through pricing or other mechanisms. |
|
parking demand management response |
Response to parking demand management change requests indicating level of compliance with request. |
|
parking information |
General parking information and status, including current parking availability. |
|
parking lot data request |
Request for parking lot occupancy, fares, and availability. The request can be a subscription that initiates as-needed information updates as well as a one-time request for information. |
|
parking lot reservation confirmation |
Confirmation for parking lot reservation. |
|
parking reservations request |
Reservation request for parking lot. |
|
pass/pull-in |
Command to commercial vehicle to pull into or bypass inspection station. |
|
patient status |
Information that supports assessment of the patient's condition. Information could include general categorization of patient status, patient vital signs, pertinent medical history, and emergency care information. |
|
payment |
Payment of some kind (e.g., toll, parking, fare) by traveler which, in most cases, can be related to a credit account. |
|
payment request |
Request for payment from financial institution. |
|
personal transit information |
General and personalized transit information for a particular fixed route, flexible route, or paratransit system. |
|
port traffic conditions_ud |
|
|
qualified environmental conditions data |
Current road conditions (e.g., surface temperature, subsurface temperature, moisture, icing, treatment status) and surface weather conditions (e.g., air temperature, wind speed, precipitation, visibility) that has had quality checks performed on it and has been formatted and consolidated by the Clarus system. Attributes relating to the data collection (and aggregation) are also included. |
|
rail incident information_ud |
Information from Rail Operations on rail related incidents and the response actions being taken by Rail. |
|
rail incident response status |
Status of the rail system’s response to current incidents. |
|
railroad advisories |
Real-time notification of railway-related incident or advisory. |
|
railroad schedules |
Train schedules, maintenance schedules, and other information from the railroad that supports forecast of HRI closures. |
|
remote surveillance control |
The control commands used to remotely operate another center's sensors or surveillance equipment so that roadside surveillance assets can be shared by more than one agency. |
|
request for payment |
Request to deduct cost of service from user's payment account. |
|
request for right-of-way |
Forwarded request from signal prioritization, signal preemption, pedestrian call, multi-modal crossing activation, or other source for right-of-way. |
|
request for tag data_ud |
Request for tag information including credit identity, stored value card cash, etc. |
|
request for vehicle measures |
Request for vehicle performance and maintenance data collected by onboard sensors. |
|
request tag data |
Request for tag information including credit identity, stored value card cash, etc. |
|
resource coordination |
Coordination of resource inventory information, specific resource status information, resource prioritization and reallocation between jurisdictions, and specific requests for resources and responses that service those requests. |
|
resource deployment status |
Status of resource deployment identifying the resources (vehicles, equipment, materials, and personnel) available and their current status. General resource inventory information and specific status of deployed resources may be included. |
|
resource request |
A request for resources to implement special traffic control measures, assist in clean up, verify an incident, etc. The request may poll for resource availability or request pre-staging, staging, or immediate deployment of resources. Resources may be explicitly requested or a service may be requested and the specific resource deployment may be determined by the responding agency. |
|
road network conditions |
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. |
|
road network probe data request_ud |
A request for road network probe data, generally containing route usage, travel times, environmental conditions, and other aggregated data collected from probe vehicles. |
|
road network traffic probe data |
Aggregated route usage, travel times, and other aggregated data collected from probe vehicles that can be used to estimate current traffic conditions. |
|
road weather information |
Road conditions and weather information that are made available by road maintenance operations to other transportation system operators. |
|
roadway information system data |
Information used to initialize, configure, and control roadside systems that provide driver information (e.g., dynamic message signs, highway advisory radio, beacon systems). This flow can provide message content and delivery attributes, local message store maintenance requests, control mode commands, status queries, and all other commands and associated parameters that support remote management of these systems. |
|
roadway information system status |
Current operating status of dynamic message signs, highway advisory radios, beacon systems, or other configurable field equipment that provides dynamic information to the driver. |
|
roadway maintenance status |
Summary of maintenance fleet operations affecting the road network. This includes the status of winter maintenance (snow plow schedule and current status). |
|
roadway treatment system control |
Control data for remotely located, automated devices, that affect the roadway surface (e.g. de-icing applications). |
|
roadway treatment system status |
Current operational status of automated roadway treatment devices (e.g., anti-icing systems). |
|
route restrictions |
Information about routes, road segments, and areas that do not allow the transport of security sensitive hazmat cargoes or include other restrictions (such as height or weight limits). |
|
safeguard system control_ud |
Data that controls safeguard systems (remotely controlled equipment used to mitigate the impact of incidents on transportation infrastructure, such as blast shields, exhaust systems, etc.). |
|
safety inspection record |
Record containing results of commercial vehicle safety inspection. |
|
safety inspection request |
Request for safety inspection record. |
|
safety status information |
Safety information such as safety ratings, security ratings or flags, inspection summaries, and violation summaries. A unique identifier is included. Corresponds to the safety and security portion of CVISN "snapshots." The status information may be provided as a response to a real-time query or as a result of a standing request for updated information (subscription). This may also include information about non-U.S. fleets for use by U.S. authorities, and information regarding U.S. fleets made available to Mexican and Canadian authorities. The query flow is not explicitly shown. |
|
secure area sensor control |
Information used to configure and control threat sensors (e.g., thermal, acoustic, radiological, chemical), object, motion and intrusion detection sensors. The provided information controls sensor data collection, aggregation, filtering, and other local processing. |
|
secure area sensor data |
Data provided by threat sensors (e.g., thermal, acoustic, radiological, chemical), and intrusion, motion, and object detection sensors in secure areas indicating the sensor's operational status, raw and processed sensor data, and alarm indicators when a threat has been detected. |
|
secure area surveillance control |
Information used to configure and control audio and video surveillance systems used for transportation infrastructure security in secure areas. The provided information controls surveillance data collection, aggregation, filtering, and other local processing. |
|
secure area surveillance data |
Data collected from surveillance systems used to monitor secure areas. Includes video, audio, processed surveillance data, equipment operational status, and alarm indicators when a threat has been detected. |
|
selected routes |
Routes selected based on route request criteria. |
|
signal control data |
Information used to configure and control traffic signal systems. |
|
signal control status |
Status of surface street signal controls including operating condition and current operational state. |
|
storage facility request |
Request for information about the equipment and/or materials available at a maintenance storage facility. |
|
suggested route |
Suggested route for a dispatched emergency or maintenance vehicle that may reflect current network conditions and the additional routing options available to en route emergency or maintenance vehicles that are not available to the general public. |
|
tag data |
Unique tag ID and related vehicle information. |
|
tax filing |
Commercial vehicle tax filing data. Authorization for payment is included. |
|
threat information coordination |
Sensor, surveillance, and threat data including raw and processed data that is collected by sensor and surveillance equipment located in secure areas. |
|
track status |
Current status of the wayside equipment and notification of an arriving train. |
|
traffic archive data |
Information describing the use and vehicle composition on transportation facilities and the traffic control strategies employed. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information. |
|
traffic flow |
Raw and/or processed traffic detector data which allows derivation of traffic flow variables (e.g., speed, volume, and density measures) and associated information (e.g., congestion, potential incidents). This flow includes the traffic data and the operational status of the traffic detectors. |
|
traffic images |
High fidelity, real-time traffic images suitable for surveillance monitoring by the operator or for use in machine vision applications. This flow includes the images and the operational status of the surveillance system. |
|
traffic information coordination |
Traffic information exchanged between TMC’s. Normally would include incidents, congestion data, traffic data, signal timing plans, and real-time signal control information. |
|
traffic operator data |
Presentation of traffic operations data to the operator including traffic conditions, current operating status of field equipment, maintenance activity status, incident status, video images, security alerts, emergency response plan updates and other information. This data keeps the operator appraised of current road network status, provides feedback to the operator as traffic control actions are implemented, provides transportation security inputs, and supports review of historical data and preparation for future traffic operations activities. |
|
traffic operator inputs |
User input from traffic operations personnel including requests for information, configuration changes, commands to adjust current traffic control strategies (e.g., adjust signal timing plans, change DMS messages), and other traffic operations data entry. |
|
traffic probe data |
Vehicle data that is used to determine traffic conditions. In a basic implementation, the data could be limited to time stamped unique identifiers that can be used to measure a vehicle’s progress through the network. In more advanced implementations, the vehicle may report current position, speed, and heading and snapshots of recent events including route information, starts and stops, speed changes, and other information that can be used to estimate traffic conditions. |
|
traffic sensor control |
Information used to configure and control traffic sensor systems. |
|
transaction status |
Response to transaction request. Normally dealing with a request for payment. |
|
transit and fare schedules |
Transit service information including routes, schedules, and fare information. |
|
transit archive data |
Data used to describe and monitor transit demand, fares, operations, and system performance. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information. |
|
transit fare and passenger status |
Information provided from the traveler location that supports fare payments, passenger data, and associated record-keeping. |
|
transit fare coordination |
Fare and pricing information shared between local/regional transit organizations. |
|
transit fare information |
Information provided by transit management that supports fare payment transactions and passenger data collection. |
|
transit incident information |
Information on transit incidents that impact transit services for public dissemination. |
|
transit information request |
Request for transit operations information including schedule and fare information. The request can be a subscription that initiates as-needed information updates as well as a one-time request for information. |
|
transit information user request |
Request for special transit routing, real-time schedule information, and availability information. |
|
transit multimodal information |
Transit schedule information for coordination at modal interchange points. |
|
transit operations status |
Presentation of information to transit operations personnel including accumulated schedule and fare information, ridership and on-time performance information, emergency response plans, transit personnel information, maintenance records, and other information intended to support overall planning and management of a transit property. |
|
transit request confirmation |
Confirmation of a request for transit information or service. |
|
transit schedule adherence information |
Dynamic transit schedule adherence and transit vehicle location information. |
|
transit schedule information |
Current and projected transit schedule information used to initialize the transit vehicle with a vehicle assignment, monitor schedule performance, and develop corrective actions on-board. |
|
transit service coordination |
Schedule coordination information shared between local/regional transit organizations. |
|
transit traveler information |
Transit information prepared to support transit users and other travelers. It contains transit schedules, real-time arrival information, fare schedules, alerts and advisories, and general transit service information. |
|
transit vehicle conditions |
Operating conditions of transit vehicle (e.g., engine running, oil pressure, fuel level and usage). |
|
transit vehicle loading data |
Data collected on board the transit vehicle relating to passenger boarding and alighting. |
|
transit vehicle location data |
Current transit vehicle location and related operational conditions data provided by a transit vehicle. |
|
transit vehicle operator information |
Transit service instructions, wide area alerts, traffic information, road conditions, and other information for both transit and paratransit operators. |
|
transit vehicle schedule performance |
Estimated times of arrival and anticipated schedule deviations reported by a transit vehicle. |
|
transportation system status |
Current status and condition of transportation infrastructure (e.g., tunnels, bridges, interchanges, TMC offices, maintenance facilities). In case of disaster or major incident, this flow provides an assessment of damage sustained by the surface transportation system including location and extent of the damage, estimate of remaining capacity and necessary restrictions, and time frame for repair and recovery. |
|
traveler information for media |
General traveler information regarding incidents, unusual traffic conditions, transit issues, or other advisory information that has been desensitized and provided to the media. |
|
traveler profile |
Information about a traveler including equipment capabilities, personal preferences, and traveler alert subscriptions. |
|
traveler request |
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 |
Acknowledgement by the driver/traveler of acceptance of a trip plan with associated personal and payment information required to confirm reservations. |
|
trip plan |
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 |
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. |
|
video surveillance control |
Information used to configure and control video surveillance systems. |
|
weather information |
Accumulated forecasted and current weather data (e.g., temperature, pressure, wind speed, wind direction, humidity, precipitation, visibility, light conditions, etc.). |
|
work plan coordination |
Coordination of work plan schedules and activities between maintenance and construction organizations or systems. This information includes the work plan schedules and comments and suggested changes that are exchanged as work plans are coordinated and finalized. |
|
work plan feedback |
Comments and suggested changes to proposed construction and maintenance work schedules and activities. This information influences work plan schedules so that they minimize impact to other system operations and the overall transportation system. |
|
work zone information |
Summary of maintenance and construction work zone activities affecting the road network including the nature of the maintenance or construction activity, location, impact to the roadway, expected time(s) and duration of impact, anticipated delays, alternate routes, and suggested speed limits. This information may be augmented with images that provide a visual indication of current work zone status and traffic impacts. |
|
work zone status |
Current work zone status including current location (and future locations for moving work zones), impact to the roadway, required lane shifts, expected time(s) and duration of impact, anticipated delays, alternate routes, and suggested speed limits. |
|
work zone warning notification |
Notification of a work zone emergency or safety issue. This flow identifies that a work zone emergency or safety issue has occurred so that warnings may be generated by more than one system in the work zone. |
|
work zone warning status |
Status of a work zone safety monitoring and warning devices. This flow documents system activations and includes additional supporting information (e.g., an image) that allows verification of the alarm. |
(PDF Version)