TI01: Broadcast Traveler Information
This service package provides a digital broadcast service that disseminates traveler information to all equipped travelers within range. It collects traffic conditions, advisories, general public transportation, toll and parking information, incident information, roadway maintenance and construction information, air quality and weather information, and broadcasts the information to travelers using technologies such as FM subcarrier, satellite radio, cellular data broadcasts, and Internet streaming technologies.
This service package also provides location-specific or situation-relevant information to travelers in vehicles using Dedicated Short Range Communications (DSRC) infrastructure supporting mobility service packages for connected vehicles. DSRC is used to deliver real-time traveler information including travel times, incident information, road conditions, and emergency traveler information to vehicles as they pass connected vehicle roadside equipment along their route. This service package provides public information that is available to all equipped vehicles in the vicinity of the roadside equipment.
Relevant Regions: Australia, Canada, European Union, and United States
- Enterprise
- Functional
- Physical
- Goals and Objectives
- Needs and Requirements
- Sources
- Security
- Standards
- System Requirements
- Implementations
Enterprise
Development Stage Roles and Relationships
Installation Stage Roles and Relationships
Operations and Maintenance Stage Roles and Relationships
(hide)
Source | Destination | Role/Relationship |
---|---|---|
Border Inspection System Maintainer | Border Inspection System | Maintains |
Border Inspection System Manager | Border Inspection System | Manages |
Border Inspection System Owner | Border Inspection System Maintainer | System Maintenance Agreement |
Border Inspection System Owner | Border Inspection System Manager | Operations Agreement |
Border Inspection System Owner | TIC Operator | Application Usage Agreement |
Border Inspection System Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
Border Inspection System Owner | Transportation Information Center Owner | Information Exchange and Action Agreement |
Border Inspection System Owner | Transportation Information Center User | Service Usage Agreement |
Border Inspection System Supplier | Border Inspection System Owner | Warranty |
Connected Vehicle Roadside Equipment Maintainer | Connected Vehicle Roadside Equipment | Maintains |
Connected Vehicle Roadside Equipment Manager | Connected Vehicle Roadside Equipment | Manages |
Connected Vehicle Roadside Equipment Owner | Connected Vehicle Roadside Equipment Maintainer | System Maintenance Agreement |
Connected Vehicle Roadside Equipment Owner | Connected Vehicle Roadside Equipment Manager | Operations Agreement |
Connected Vehicle Roadside Equipment Owner | Driver | Application Usage Agreement |
Connected Vehicle Roadside Equipment Owner | Personal Information Device Maintainer | Maintenance Data Exchange Agreement |
Connected Vehicle Roadside Equipment Owner | Personal Information Device Owner | Information Exchange and Action Agreement |
Connected Vehicle Roadside Equipment Owner | Personal Information Device User | Service Usage Agreement |
Connected Vehicle Roadside Equipment Owner | TIC Operator | Application Usage Agreement |
Connected Vehicle Roadside Equipment Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
Connected Vehicle Roadside Equipment Owner | Transportation Information Center Owner | Information Exchange and Action Agreement |
Connected Vehicle Roadside Equipment Owner | Transportation Information Center User | Service Usage Agreement |
Connected Vehicle Roadside Equipment Owner | Traveler | Application Usage Agreement |
Connected Vehicle Roadside Equipment Owner | Vehicle Maintainer | Maintenance Data Exchange Agreement |
Connected Vehicle Roadside Equipment Owner | Vehicle Owner | Information Exchange and Action Agreement |
Connected Vehicle Roadside Equipment Owner | Vehicle User | Service Usage Agreement |
Connected Vehicle Roadside Equipment Supplier | Connected Vehicle Roadside Equipment Owner | Warranty |
Driver | Vehicle | Operates |
Emergency Management Center Maintainer | Emergency Management Center | Maintains |
Emergency Management Center Manager | Emergency Management Center | Manages |
Emergency Management Center Owner | Emergency Management Center Maintainer | System Maintenance Agreement |
Emergency Management Center Owner | Emergency Management Center Manager | Operations Agreement |
Emergency Management Center Owner | TIC Operator | Application Usage Agreement |
Emergency Management Center Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
Emergency Management Center Owner | Transportation Information Center Owner | Information Provision Agreement |
Emergency Management Center Owner | Transportation Information Center User | Service Usage Agreement |
Emergency Management Center Supplier | Emergency Management Center Owner | Warranty |
Emissions Management Center Maintainer | Emissions Management Center | Maintains |
Emissions Management Center Manager | Emissions Management Center | Manages |
Emissions Management Center Owner | Emissions Management Center Maintainer | System Maintenance Agreement |
Emissions Management Center Owner | Emissions Management Center Manager | Operations Agreement |
Emissions Management Center Owner | TIC Operator | Application Usage Agreement |
Emissions Management Center Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
Emissions Management Center Owner | Transportation Information Center Owner | Information Provision Agreement |
Emissions Management Center Owner | Transportation Information Center User | Service Usage Agreement |
Emissions Management Center Supplier | Emissions Management Center Owner | Warranty |
Event Promoter System Maintainer | Event Promoter System | Maintains |
Event Promoter System Manager | Event Promoter System | Manages |
Event Promoter System Owner | Event Promoter System Maintainer | System Maintenance Agreement |
Event Promoter System Owner | Event Promoter System Manager | Operations Agreement |
Event Promoter System Owner | TIC Operator | Application Usage Agreement |
Event Promoter System Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
Event Promoter System Owner | Transportation Information Center Owner | Information Provision Agreement |
Event Promoter System Owner | Transportation Information Center User | Service Usage Agreement |
Event Promoter System Supplier | Event Promoter System Owner | Warranty |
Maint and Constr Management Center Maintainer | Maint and Constr Management Center | Maintains |
Maint and Constr Management Center Manager | Maint and Constr Management Center | Manages |
Maint and Constr Management Center Owner | Maint and Constr Management Center Maintainer | System Maintenance Agreement |
Maint and Constr Management Center Owner | Maint and Constr Management Center Manager | Operations Agreement |
Maint and Constr Management Center Owner | TIC Operator | Application Usage Agreement |
Maint and Constr Management Center Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
Maint and Constr Management Center Owner | Transportation Information Center Owner | Information Provision Agreement |
Maint and Constr Management Center Owner | Transportation Information Center User | Service Usage Agreement |
Maint and Constr Management Center Supplier | Maint and Constr Management Center Owner | Warranty |
Media Maintainer | Media | Maintains |
Media Manager | Media | Manages |
Media Owner | Media Maintainer | System Maintenance Agreement |
Media Owner | Media Manager | Operations Agreement |
Media Supplier | Media Owner | Warranty |
Other Transportation Information Centers Maintainer | Other Transportation Information Centers | Maintains |
Other Transportation Information Centers Manager | Other Transportation Information Centers | Manages |
Other Transportation Information Centers Owner | Other Transportation Information Centers Maintainer | System Maintenance Agreement |
Other Transportation Information Centers Owner | Other Transportation Information Centers Manager | Operations Agreement |
Other Transportation Information Centers Owner | TIC Operator | Application Usage Agreement |
Other Transportation Information Centers Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
Other Transportation Information Centers Owner | Transportation Information Center Owner | Information Exchange Agreement |
Other Transportation Information Centers Owner | Transportation Information Center User | Service Usage Agreement |
Other Transportation Information Centers Supplier | Other Transportation Information Centers Owner | Warranty |
Parking Management Center Maintainer | Parking Management Center | Maintains |
Parking Management Center Manager | Parking Management Center | Manages |
Parking Management Center Owner | Parking Management Center Maintainer | System Maintenance Agreement |
Parking Management Center Owner | Parking Management Center Manager | Operations Agreement |
Parking Management Center Owner | TIC Operator | Application Usage Agreement |
Parking Management Center Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
Parking Management Center Owner | Transportation Information Center Owner | Information Provision Agreement |
Parking Management Center Owner | Transportation Information Center User | Service Usage Agreement |
Parking Management Center Supplier | Parking Management Center Owner | Warranty |
Payment Administration Center Maintainer | Payment Administration Center | Maintains |
Payment Administration Center Manager | Payment Administration Center | Manages |
Payment Administration Center Owner | Payment Administration Center Maintainer | System Maintenance Agreement |
Payment Administration Center Owner | Payment Administration Center Manager | Operations Agreement |
Payment Administration Center Owner | TIC Operator | Application Usage Agreement |
Payment Administration Center Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
Payment Administration Center Owner | Transportation Information Center Owner | Information Provision Agreement |
Payment Administration Center Owner | Transportation Information Center User | Service Usage Agreement |
Payment Administration Center Supplier | Payment Administration Center Owner | Warranty |
Personal Information Device Maintainer | Personal Information Device | Maintains |
Personal Information Device Manager | Personal Information Device | Manages |
Personal Information Device Manager | Traveler | System Usage Agreement |
Personal Information Device Owner | Personal Information Device Maintainer | System Maintenance Agreement |
Personal Information Device Owner | Personal Information Device Manager | Operations Agreement |
Personal Information Device Supplier | Personal Information Device Owner | Warranty |
Surface Transportation Weather Service Maintainer | Surface Transportation Weather Service | Maintains |
Surface Transportation Weather Service Manager | Surface Transportation Weather Service | Manages |
Surface Transportation Weather Service Owner | Surface Transportation Weather Service Maintainer | System Maintenance Agreement |
Surface Transportation Weather Service Owner | Surface Transportation Weather Service Manager | Operations Agreement |
Surface Transportation Weather Service Owner | TIC Operator | Application Usage Agreement |
Surface Transportation Weather Service Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
Surface Transportation Weather Service Owner | Transportation Information Center Owner | Information Provision Agreement |
Surface Transportation Weather Service Owner | Transportation Information Center User | Service Usage Agreement |
Surface Transportation Weather Service Supplier | Surface Transportation Weather Service Owner | Warranty |
TIC Operator | Transportation Information Center | Operates |
Traffic Management Center Maintainer | Traffic Management Center | Maintains |
Traffic Management Center Manager | Traffic Management Center | Manages |
Traffic Management Center Owner | TIC Operator | Application Usage Agreement |
Traffic Management Center Owner | Traffic Management Center Maintainer | System Maintenance Agreement |
Traffic Management Center Owner | Traffic Management Center Manager | Operations Agreement |
Traffic Management Center Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
Traffic Management Center Owner | Transportation Information Center Owner | Information Provision Agreement |
Traffic Management Center Owner | Transportation Information Center User | Service Usage Agreement |
Traffic Management Center Supplier | Traffic Management Center Owner | Warranty |
Transit Management Center Maintainer | Transit Management Center | Maintains |
Transit Management Center Manager | Transit Management Center | Manages |
Transit Management Center Owner | TIC Operator | Application Usage Agreement |
Transit Management Center Owner | Transit Management Center Maintainer | System Maintenance Agreement |
Transit Management Center Owner | Transit Management Center Manager | Operations Agreement |
Transit Management Center Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
Transit Management Center Owner | Transportation Information Center Owner | Information Provision Agreement |
Transit Management Center Owner | Transportation Information Center User | Service Usage Agreement |
Transit Management Center Supplier | Transit Management Center Owner | Warranty |
Transportation Information Center Maintainer | Transportation Information Center | Maintains |
Transportation Information Center Manager | TIC Operator | System Usage Agreement |
Transportation Information Center Manager | Transportation Information Center | Manages |
Transportation Information Center Owner | Connected Vehicle Roadside Equipment Maintainer | Maintenance Data Exchange Agreement |
Transportation Information Center Owner | Connected Vehicle Roadside Equipment Owner | Information Provision Agreement |
Transportation Information Center Owner | Connected Vehicle Roadside Equipment User | Service Usage Agreement |
Transportation Information Center Owner | Driver | Application Usage Agreement |
Transportation Information Center Owner | Media Maintainer | Maintenance Data Exchange Agreement |
Transportation Information Center Owner | Media Owner | Information Provision Agreement |
Transportation Information Center Owner | Media User | Service Usage Agreement |
Transportation Information Center Owner | Other Transportation Information Centers Maintainer | Maintenance Data Exchange Agreement |
Transportation Information Center Owner | Other Transportation Information Centers Owner | Information Exchange Agreement |
Transportation Information Center Owner | Other Transportation Information Centers User | Service Usage Agreement |
Transportation Information Center Owner | Personal Information Device Maintainer | Maintenance Data Exchange Agreement |
Transportation Information Center Owner | Personal Information Device Owner | Information Provision Agreement |
Transportation Information Center Owner | Personal Information Device User | Service Usage Agreement |
Transportation Information Center Owner | Transportation Information Center Maintainer | System Maintenance Agreement |
Transportation Information Center Owner | Transportation Information Center Manager | Operations Agreement |
Transportation Information Center Owner | Traveler | Application Usage Agreement |
Transportation Information Center Owner | Traveler Support Equipment Maintainer | Maintenance Data Exchange Agreement |
Transportation Information Center Owner | Traveler Support Equipment Owner | Information Provision Agreement |
Transportation Information Center Owner | Traveler Support Equipment User | Service Usage Agreement |
Transportation Information Center Owner | Vehicle Maintainer | Maintenance Data Exchange Agreement |
Transportation Information Center Owner | Vehicle Owner | Information Provision Agreement |
Transportation Information Center Owner | Vehicle User | Service Usage Agreement |
Transportation Information Center Supplier | Transportation Information Center Owner | Warranty |
Traveler | Personal Information Device | Operates |
Traveler | Traveler Support Equipment | Operates |
Traveler Support Equipment Maintainer | Traveler Support Equipment | Maintains |
Traveler Support Equipment Manager | Traveler | System Usage Agreement |
Traveler Support Equipment Manager | Traveler Support Equipment | Manages |
Traveler Support Equipment Owner | Traveler Support Equipment Maintainer | System Maintenance Agreement |
Traveler Support Equipment Owner | Traveler Support Equipment Manager | Operations Agreement |
Traveler Support Equipment Supplier | Traveler Support Equipment Owner | Warranty |
Vehicle Maintainer | Vehicle | Maintains |
Vehicle Manager | Driver | System Usage Agreement |
Vehicle Manager | Vehicle | Manages |
Vehicle Owner | Vehicle Maintainer | System Maintenance Agreement |
Vehicle Owner | Vehicle Manager | Operations Agreement |
Vehicle Supplier | Vehicle Owner | Warranty |
Weather Service System Maintainer | Weather Service System | Maintains |
Weather Service System Manager | Weather Service System | Manages |
Weather Service System Owner | TIC Operator | Application Usage Agreement |
Weather Service System Owner | Transportation Information Center Maintainer | Maintenance Data Exchange Agreement |
Weather Service System Owner | Transportation Information Center Owner | Information Provision Agreement |
Weather Service System Owner | Transportation Information Center User | Service Usage Agreement |
Weather Service System Owner | Weather Service System Maintainer | System Maintenance Agreement |
Weather Service System Owner | Weather Service System Manager | Operations Agreement |
Weather Service System Supplier | Weather Service System Owner | Warranty |
Functional
This service package includes the following Functional View PSpecs:
Physical
The physical diagram can be viewed in SVG or PNG format and the current format is SVG.SVG Diagram
PNG Diagram
Includes Physical Objects:
Physical Object | Class | Description |
---|---|---|
Border Inspection System | Field | 'Border Inspection System' represents data systems used at the border for the inspection of people or goods. It supports immigration, customs (trade), agricultural, and FDA inspections as applicable. It includes sensors and surveillance systems to identify and classify drivers and their cargo as they approach a border crossing, the systems used to interface with the back-office administration systems and provide information on status of the crossing or events. |
Connected Vehicle Roadside Equipment | Field | 'Connected Vehicle Roadside Equipment' (CV RSE) represents the Connected Vehicle roadside devices that are used to send messages to, and receive messages from, nearby vehicles using Dedicated Short Range Communications (DSRC) or other alternative wireless communications technologies. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers. |
Driver | Vehicle | The 'Driver' represents the person that operates a vehicle on the roadway. Included are operators of private, transit, commercial, and emergency vehicles where the interactions are not particular to the type of vehicle (e.g., interactions supporting vehicle safety applications). The Driver originates driver requests and receives driver information that reflects the interactions which might be useful to all drivers, regardless of vehicle classification. Information and interactions which are unique to drivers of a specific vehicle type (e.g., fleet interactions with transit, commercial, or emergency vehicle drivers) are covered by separate objects. |
Emergency Management Center | Center | The 'Emergency Management Center' represents systems that support incident management, disaster response and evacuation, security monitoring, and other security and public safety-oriented ITS applications. It includes the functions associated with fixed and mobile public safety communications centers including public safety call taker and dispatch centers operated by police (including transit police), fire, and emergency medical services. It includes the functions associated with Emergency Operations Centers that are activated at local, regional, state, and federal levels for emergencies and the portable and transportable systems that support Incident Command System operations at an incident. This Center also represents systems associated with towing and recovery, freeway service patrols, HAZMAT response teams, and mayday service providers. It manages sensor and surveillance equipment used to enhance transportation security of the roadway infrastructure (including bridges, tunnels, interchanges, and other key roadway segments) and the public transportation system (including transit vehicles, public areas such as transit stops and stations, facilities such as transit yards, and transit infrastructure such as rail, bridges, tunnels, or bus guideways). It provides security/surveillance services to improve traveler security in public areas not a part of the public transportation system. It monitors alerts, advisories, and other threat information and prepares for and responds to identified emergencies. It coordinates emergency response involving multiple agencies with peer centers. It stores, coordinates, and utilizes emergency response and evacuation plans to facilitate this coordinated response. Emergency situation information including damage assessments, response status, evacuation information, and resource information are shared The Emergency Management Center also provides a focal point for coordination of the emergency and evacuation information that is provided to the traveling public, including wide-area alerts when immediate public notification is warranted. It tracks and manages emergency vehicle fleets using real-time road network status and routing information from the other centers to aid in selecting the emergency vehicle(s) and routes, and works with other relevant centers to tailor traffic control to support emergency vehicle ingress and egress, implementation of special traffic restrictions and closures, evacuation traffic control plans, and other special strategies that adapt the transportation system to better meet the unique demands of an emergency. |
Emissions Management Center | Center | The 'Emissions Management Center' provides the capabilities for air quality managers to monitor and manage air quality. These capabilities include collecting emissions data from distributed emissions sensors (included in ITS Roadway Equipment) and directly from connected vehicles. The sensors monitor general air quality and also monitor the emissions of individual vehicles on the roadway. The measures are collected, processed, and used to support environmental monitoring applications. |
Event Promoter System | Center | 'Event Promoter System' represents Special Event Sponsors that have knowledge of events that may impact travel on roadways or other modal means. Examples of special event sponsors include sporting events, conventions, motorcades/parades, and public/political events. These promoters interface to the ITS to provide event information such as date, time, estimated duration, location, and any other information pertinent to traffic movement in the surrounding area. |
Maint and Constr Management Center | Center | The 'Maint and Constr Management Center' monitors and manages roadway infrastructure construction and maintenance activities. Representing both public agencies and private contractors that provide these functions, this physical object manages fleets of maintenance, construction, or special service vehicles (e.g., snow and ice control equipment). The physical object receives a wide range of status information from these vehicles and performs vehicle dispatch, routing, and resource management for the vehicle fleets and associated equipment. The physical object participates in incident response by deploying maintenance and construction resources to an incident scene, in coordination with other center physical objects. The physical object manages equipment at the roadside, including environmental sensors and automated systems that monitor and mitigate adverse road and surface weather conditions. It manages the repair and maintenance of both non-ITS and ITS equipment including the traffic controllers, detectors, dynamic message signs, signals, and other equipment associated with the roadway infrastructure. Weather information is collected and fused with other data sources and used to support advanced decision support systems. The physical object remotely monitors and manages ITS capabilities in work zones, gathering, storing, and disseminating work zone information to other systems. It manages traffic in the vicinity of the work zone and advises drivers of work zone status (either directly at the roadside or through an interface with the Transportation Information Center or Traffic Management Center physical objects.) Construction and maintenance activities are tracked and coordinated with other systems, improving the quality and accuracy of information available regarding closures and other roadway construction and maintenance activities. |
Media | Center | 'Media' represents the information systems that provide traffic reports, travel conditions, and other transportation-related news services to the traveling public through radio, TV, and other media. Traffic and travel advisory information that are collected by ITS are provided to this object. It is also a source for traffic flow information, incident and special event information, and other events that may have implications for the transportation system. |
Other Transportation Information Centers | Center | Representing another Transportation Information Center, this object is intended to provide a source and destination for ITS information flows between peer information and service provider functions. It enables cooperative information sharing between providers as conditions warrant. |
Parking Management Center | Center | The 'Parking Management Center' manages one or more parking lots by providing configuration and control of field infrastructure, user account management and interfaces with financial systems to manage payment. This p-object takes the back office portion of the Parking Management System's functionality as it was defined in ARC-IT 8.3 and prior. |
Payment Administration Center | Center | The 'Payment Administration Center' provides general payment administration capabilities and supports the electronic transfer of funds from the customer to the transportation system operator or other service provider. Charges can be recorded for tolls, vehicle-mileage charging, congestion charging, or other goods and services. It supports traveler enrollment and collection of both pre-payment and post-payment transportation fees in coordination with the financial infrastructure supporting electronic payment transactions. The system may establish and administer escrow accounts depending on the clearinghouse scheme and the type of payments involved. It may post a transaction to the customer account, generate a bill (for post-payment accounts), debit an escrow account, or interface to a financial infrastructure to debit a customer designated account. It supports communications with the ITS Roadway Payment Equipment to support fee collection operations. As an alternative, a wide-area wireless interface can be used to communicate directly with vehicle equipment. It also sets and administers the pricing structures and may implement road pricing policies in coordination with the Traffic Management Center. |
Personal Information Device | Personal | The 'Personal Information Device' provides the capability for travelers to receive formatted traveler information wherever they are. Capabilities include traveler information, trip planning, and route guidance. Frequently a smart phone, the Personal Information Device provides travelers with the capability to receive route planning and other personally focused transportation services from the infrastructure in the field, at home, at work, or while en-route. Personal Information Devices may operate independently or may be linked with vehicle on-board equipment. This subsystem also supports safety related services with the capability to broadcast safety messages and initiate a distress signal or request for help. |
Surface Transportation Weather Service | Center | The 'Surface Transportation Weather Service' represents the providers of value-added sector-specific meteorological services. These providers utilize National Weather Service data and predictions, road condition information and local environmental data provided by traffic management or maintenance organizations, and their own models to provide surface transportation related weather observations and forecasts including pavement temperature and conditions. |
TIC Operator | Center | This 'TIC Operator' represents the person or people that monitor and manage traveler information services provided by the Transportation Information Center. |
Traffic Management Center | Center | The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters. |
Transit Management Center | Center | The 'Transit Management Center' manages transit vehicle fleets and coordinates with other modes and transportation services. It provides operations, maintenance, customer information, planning and management functions for the transit property. It spans distinct central dispatch and garage management systems and supports the spectrum of fixed route, flexible route, paratransit services, transit rail, and bus rapid transit (BRT) service. The physical object's interfaces support communication between transit departments and with other operating entities such as emergency response services and traffic management systems. |
Transportation Information Center | Center | The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service. |
Traveler | Personal | The 'Traveler' represents any individual who uses transportation services. The interfaces to the traveler provide general pre-trip and en-route information supporting trip planning, personal guidance, and requests for assistance in an emergency that are relevant to all transportation system users. It also represents users of a public transportation system and addresses interfaces these users have within a transit vehicle or at transit facilities such as roadside stops and transit centers. |
Traveler Support Equipment | Field | 'Traveler Support Equipment' provides access to traveler information at transit stations, transit stops, other fixed sites along travel routes (e.g., rest stops, merchant locations), and major trip generation locations such as special event centers, hotels, office complexes, amusement parks, and theaters. Traveler information access points include kiosks and informational displays supporting varied levels of interaction and information access. At transit stops this might be simple displays providing schedule information and imminent arrival signals. This may be extended to include multi-modal information including traffic conditions and transit schedules to support mode and route selection at major trip generation sites. Personalized route planning and route guidance information can also be provided based on criteria supplied by the traveler. It also supports service enrollment and electronic payment of transit fares. In addition to the traveler information provision, it also enhances security in public areas by supporting traveler activated silent alarms. |
Vehicle | Vehicle | This 'Vehicle' physical object is used to model core capabilities that are common to more than one type of Vehicle. It provides the vehicle-based general sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. Many of these capabilities (e.g., see the Vehicle Safety service packages) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle includes the common interfaces and functions that apply to all motorized vehicles. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle. Both one-way and two-way communications options support a spectrum of information services from basic broadcast to advanced personalized information services. Advanced sensors, processors, enhanced driver interfaces, and actuators complement the driver information services so that, in addition to making informed mode and route selections, the driver travels these routes in a safer and more consistent manner. This physical object supports all six levels of driving automation as defined in SAE J3016. Initial collision avoidance functions provide 'vigilant co-pilot' driver warning capabilities. More advanced functions assume limited control of the vehicle to maintain lane position and safe headways. In the most advanced implementations, this Physical Object supports full automation of all aspects of the driving task, aided by communications with other vehicles in the vicinity and in coordination with supporting infrastructure subsystems. |
Weather Service System | Center | The 'Weather Service System' provides weather, hydrologic, and climate information and warnings of hazardous weather including thunderstorms, flooding, hurricanes, tornadoes, winter weather, tsunamis, and climate events. It provides atmospheric weather observations and forecasts that are collected and derived by the National Weather Service, private sector providers, and various research organizations. The interface provides formatted weather data products suitable for on-line processing and integration with other ITS data products as well as Doppler radar images, satellite images, severe storm warnings, and other products that are formatted for presentation to various ITS users. |
Includes Functional Objects:
Functional Object | Description | Physical Object |
---|---|---|
Personal Traveler Information Reception | 'Personal Traveler Information Reception' receives formatted traffic advisories, road conditions, traffic regulations, transit information, broadcast alerts, and other general traveler information broadcasts and presents the information to the traveler. The traveler information broadcasts are received by personal devices including personal computers and personal portable devices such as smart phones. | Personal Information Device |
RSE Traveler Information Communications | 'RSE Traveler Information Communications' includes field elements that distribute information to vehicles for in-vehicle display. The information may be provided by a center (e.g., variable information on traffic and road conditions in the vicinity of the field equipment) or it may be determined and output locally (e.g., static sign information and signal phase and timing information). This includes the interface to the center or field equipment that controls the information distribution and the short range communications equipment that provides information to passing vehicles. | Connected Vehicle Roadside Equipment |
TIC Connected Vehicle Traveler Info Distribution | In support of connected vehicle applications, 'TIC Connected Vehicle Traveler Info Distribution' disseminates traveler information including traffic and road conditions, incident information, maintenance and construction information, event information, transit information, parking information, and weather information. Location-specific or situation-relevant traveler information is sent to short range communications transceivers at the roadside. | Transportation Information Center |
TIC Data Collection | 'TIC Data Collection' collects transportation-related data from other centers, performs data quality checks on the collected data and then consolidates, verifies, and refines the data and makes it available in a consistent format to applications that support operational data sharing between centers and deliver traveler information to end-users. A broad range of data is collected including traffic and road conditions, transit data, emergency information and advisories, weather data, special event information, traveler services, parking, multimodal data, and toll/pricing data. It also shares data with other transportation information centers. | Transportation Information Center |
TIC Traveler Information Broadcast | 'TIC Traveler Information Broadcast' disseminates traveler information including traffic and road conditions, incident information, maintenance and construction information, event information, transit information, parking information, and weather information. The same information is broadcast to all equipped traveler interface systems and vehicles. | Transportation Information Center |
Traveler Information Reception | 'Traveler Information Reception' receives formatted traffic advisories, road conditions, transit information, broadcast alerts, and other general traveler information broadcasts and presents the information to the traveler with a public traveler interface. It includes the receiver and public display device such as a large display monitor or other public display. | Traveler Support Equipment |
Vehicle Traveler Information Reception | 'Vehicle Traveler Information Reception' receives advisories, vehicle signage data, and other driver information of use to all types of vehicles and drivers and presents this information to the driver using in-vehicle equipment. Information presented may include fixed sign information, traffic control device status (e.g., signal phase and timing data), advisory and detour information, warnings of adverse road and weather conditions, travel times, and other driver information. | Vehicle |
Includes Information Flows:
Information Flow | Description |
---|---|
air quality information | Aggregated region-wide measured air quality data and possible pollution incident information. |
alternate mode information | Schedule information for alternate mode transportation providers such as air, ferry, and passenger-carrying heavy rail. This also includes details of incidents and other service disruptions that have occurred in the alternative mode. This also includes measures of service demand that supports assessment of their impact on the road network. |
border crossing status information | Port of entry status including current wait-times, lane configuration and status including closures and restrictions, and notification of incidents at the border |
broadcast traveler information | General traveler information that contains traffic and road conditions, link travel times, incidents, advisories, restrictions, vehicle requirements, work zones, transit service information, weather information, parking information, and other related traveler information. |
current infrastructure 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. |
driver input | Driver input to the vehicle on-board equipment including configuration data, settings and preferences, interactive requests, and control commands. |
driver updates | Information provided to the driver including visual displays, audible information and warnings, and haptic feedback. The updates inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment. |
event information | Special event information for travelers. This would include a broader array of information than the similar "event plans" that conveys only information necessary to support traffic management for the event. |
incident information for public | Report of current desensitized incident information prepared for public dissemination. |
local traveler information | Traveler information including traffic, road, and weather conditions for a particular locality. This flow includes the location-specific traveler information and time effectivity of the information. |
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. |
parking information | General parking information and status, including current parking availability, parking pricing, and parking space availability information, including features like number and type of electric charging spots. |
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. |
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 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. |
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). |
TIC operations information presentation | Presentation of information to the TIC Operator including current operational status, parameters for broadcast information settings, route selection controls, and travel optimization algorithms. |
TIC operator input | User input from the TIC system operator including requests to monitor current system operation and inputs to affect system operation including tuning and performance enhancement parameters to traveler information algorithms. |
toll data | Current toll schedules for different types of vehicles as well as advanced toll payment information. |
traffic control information | Represents the flow of traffic control and status information between centers. This is reporting only, not actual control. This specifically includes the current state of any demand management strategies that have been implemented. |
traffic image meta data | Meta data that describes traffic images. Traffic images (video) are in another flow. |
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. Meta data that describes the images is contained in another flow. |
transit and fare schedules | Transit service information including routes, schedules, and fare information. This also includes on-demand service information. |
transit incident information | Information on transit incidents that impact transit services for public dissemination. |
transit schedule adherence information | Dynamic transit schedule adherence and transit vehicle location information. |
transit service information | Transit service information including routes, schedules, and fare information as well as dynamic transit schedule adherence and transit vehicle location information. |
transportation weather information | Current and forecast road conditions and weather information (e.g., surface condition, flooding, wind advisories, visibility, etc.) associated with the transportation network. This information is of a resolution, timeliness, and accuracy to be useful in transportation decision making. |
traveler information application info | Traveler information and associated parameters, filters, and thresholds that control the RSE's distribution of the traveler information to passing vehicles. This flow also supports remote control of the application so the application can be taken offline, reset, or restarted. |
traveler information application status | Application status reported by the RSE. This includes current operational state and status of the RSE and a record of traveler information distribution. |
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 input | User input from a traveler to summon assistance, request travel information, make a reservation, or request any other traveler service. |
traveler interface updates | Visual or audio information (e.g., routes, messages, guidance, emergency information) that is provided to the traveler. |
weather information | Accumulated forecasted and current weather data (e.g., temperature, pressure, wind speed, wind direction, humidity, precipitation, visibility, light conditions, etc.). |
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. |
Goals and Objectives
Associated Planning Factors and Goals
Planning Factor | Goal |
---|---|
A. Support the economic vitality of the metropolitan area, especially by enabling global competitiveness, productivity, and efficiency; | Improve freight network |
B. Increase the safety of the transportation system for motorized and nonmotorized users; | Reduce fatalities and injuries |
D. Increase the accessibility and mobility of people and for freight; | Reduce congestion |
E. Protect and enhance the environment, promote energy conservation, improve the quality of life, and promote consistency between transportation improvements and State and local planned growth and economic development patterns; | Protect/Enhance the Environment |
F. Enhance the integration and connectivity of the transportation system, across and between modes, for people and freight; | Enhance integration and connectivity |
G. Promote efficient system management and operation; | Improve efficiency |
I. Improve the resiliency and reliability of the transportation system and reduce or mitigate stormwater impacts of surface transportation; | Improve resiliency and reliability |
J. Enhance travel and tourism. | Support travel and tourism |
Associated Objective Categories
Associated Objectives and Performance Measures
Needs and Requirements
Need | Functional Object | Requirement | ||
---|---|---|---|---|
01 | Traveler Information needs to be able to collect timely, accurate, and reliable traffic, transit, and other road conditions data from multiple sources in order to broadcast the latest conditions affecting travelers. | TIC Connected Vehicle Traveler Info Distribution | 01 | The center shall collect traveler information for distribution including traffic and road conditions, incident information, maintenance and construction information, event information, transit information, parking information, and weather information. |
TIC Data Collection | 01 | The center shall collect, process, and store traffic and highway condition information, including incident information, detours and road closures, event information, recommended routes, and current speeds on specific routes. | ||
03 | The center shall collect, process, and store maintenance and construction information, including scheduled maintenance and construction work activities and work zone activities. | |||
04 | The center shall collect, process, and store transit routes and schedules, transit transfer options, transit fares, and real-time schedule adherence information. | |||
05 | The center shall collect, process, and store parking information, including location, availability, and fees. | |||
06 | The center shall collect, process, and store toll fee information. | |||
07 | The center shall collect, process, and store current and forecast road conditions and surface weather conditions. | |||
08 | The center shall collect, process, and store event information. | |||
09 | The center shall collect, process, and store air quality information. | |||
02 | Traveler Information needs to be able to inform as much of the traveling public as possible using any available broadcast media to increase mobility and safety through better information. | RSE Traveler Information Communications | 01 | The field element shall distribute traveler information including traffic and road conditions or upcoming work zones to passing vehicles using short range communications, under center control. |
04 | The field element shall return system operational status to the controlling center. | |||
TIC Connected Vehicle Traveler Info Distribution | 02 | The center shall distribute location relevant traveler information to short range communications equipment at the roadside. | ||
03 | The center shall provide the capability for a system operator to monitor connected vehicle system operation and control the type and update frequency of traveler information that is distributed. | |||
TIC Traveler Information Broadcast | 01 | The center shall disseminate traffic and highway condition information to travelers, including incident information, detours and road closures, event information, recommended routes, and current speeds on specific routes. | ||
02 | The center shall disseminate maintenance and construction information to travelers, including scheduled maintenance and construction work activities and work zone activities. | |||
03 | The center shall disseminate transit routes and schedules, transit transfer options, transit fares, and real-time schedule adherence information to travelers. | |||
04 | The center shall disseminate parking information to travelers, including location, availability, and fees. | |||
05 | The center shall disseminate toll fee information to travelers. | |||
06 | The center shall disseminate weather information to travelers. | |||
07 | The center shall disseminate event information to travelers. | |||
08 | The center shall disseminate air quality information to travelers. | |||
09 | The center shall provide traffic and incident data to the media. | |||
10 | The center shall provide the capability for a system operator to control the type and update frequency of broadcast traveler information. | |||
03 | Travelers need access to timely, accurate, and reliable traffic, transit, and other travel conditions in order to make informed decisions about their travel. | Personal Traveler Information Reception | 01 | The personal traveler interface shall receive traffic information from a center and present it to the traveler. |
02 | The personal traveler interface shall receive transit information from a center and present it to the traveler. | |||
03 | The personal traveler interface shall receive event information from a center and present it to the traveler. | |||
06 | The personal traveler interface shall provide broadcast traveler information in audio or manual form. | |||
07 | The personal traveler interface shall present information to the traveler in audible or visual forms, consistent with a personal device. | |||
Traveler Information Reception | 01 | The public interface for travelers shall receive traffic information from a center and present it to the traveler. | ||
02 | The public interface for travelers shall receive transit information from a center and present it to the traveler. | |||
03 | The public interface for travelers shall receive event information from a center and present it to the traveler. | |||
06 | The public interface for travelers shall provide the capability for digitized map data to act as the background to the information presented to the traveler. | |||
07 | The public interface for travelers shall support traveler input in audio or manual form. | |||
08 | The public interface for travelers shall present information to the traveler in audible or visual forms consistent with a kiosk, including those that are suitable for travelers with hearing or vision physical disabilities. | |||
09 | The public interface for travelers shall store frequently requested displayed data. | |||
Vehicle Traveler Information Reception | 01 | The vehicle shall receive traveler information including traffic and road conditions, incident information, maintenance and construction information, event information, transit information, parking information, and weather information. | ||
05 | The vehicle shall present the received information to the driver in audible or visual forms without impairing the driver's ability to control the vehicle in a safe manner. | |||
22 | The vehicle shall receive formatted traffic information from a center and present it to the driver. | |||
23 | The vehicle shall receive transit information from a center and present it to the driver. | |||
24 | The vehicle shall receive event information from a center and present it to the driver. |
Related Sources
Document Name | Version | Publication Date |
---|---|---|
ITS User Services Document | 1/1/2005 | |
Dynamic Eco-Lanes: Operational Concept | Final v1.1 | 8/1/2012 |
Vision and Operational Concept for Enabling Advanced Traveler Information Services (Enable ATIS) | Final | 5/13/2012 |
Security
In order to participate in this service package, each physical object should meet or exceed the following security levels.
In order to participate in this service package, each information flow triple should meet or exceed the following security levels.
Information Flow Security | |||||
---|---|---|---|---|---|
Source | Destination | Information Flow | Confidentiality | Integrity | Availability |
Basis | Basis | Basis | |||
Border Inspection System | Transportation Information Center | border crossing status information | Low | Moderate | Low |
This is all public information which is mostly available through public information channels. | Some minimal guarantee of data integrity is necessary for all C-ITS flows. A flaw in this information will not cause much, if any harm. A higher integrity will allow this information to be of more use, but is not required for security reasons. DISC: Original V2I analysis classified this as LOW. | Without this information there will not be any direct problem. A higher availability will allow this information to be more useful; however it is not a requirement. | |||
Connected Vehicle Roadside Equipment | Personal Information Device | local traveler information | Not Applicable | Moderate | Low |
This data is intentionally transmitted to everyone via a broadcast. It can also be determined via other visual indicators. | Some minimal guarantee of data integrity is necessary for all C-ITS flows. Flaws in this information will have a minimal effect on systems receiving it. All of the information can be verified through other means, and in a worst case scenario will only cause slightly increased traffic in the general proximity of the RSE. | All of the information provided through this flow will be available from other sources and no systems will directly rely upon it. | |||
Connected Vehicle Roadside Equipment | Transportation Information Center | traveler information application status | Moderate | Moderate | Low |
This information could be of interest to a malicious individual who is attempting to determine the best way to accomplish a crime. As such it would be best to not make it easily accessible. | If this is compromised, it could send unnecessary maintenance workers, or cause the appearance of excessive traffic violations, leading to further unnecessary investigation. | A delay in reporting this may cause a delay in necessary maintenance, but (a) this is not time-critical and (b) there are other channels for reporting malfunctioning. Additionally, there is a message received notification, which means that RSE can ensure that all intersection safety issues are delivered. | |||
Connected Vehicle Roadside Equipment | Vehicle | local traveler information | Not Applicable | Moderate | Low |
This data is intentionally transmitted to everyone via a broadcast. It can also be determined via other visual indicators. | Some minimal guarantee of data integrity is necessary for all C-ITS flows. Flaws in this information will have a minimal effect on systems receiving it. All of the information can be verified through other means, and in a worst case scenario will only cause slightly increased traffic in the general proximity of the RSE. DISC: Original V2I analysis classified this as LOW. | All of the information provided through this flow will be available from other sources and no systems will directly rely upon it. | |||
Driver | Vehicle | driver input | Moderate | High | High |
Data included in this flow may include origin and destination information, which should be protected from other's viewing as it may compromise the driver's privacy. | Commands from from the driver to the vehicle must be correct or the vehicle may behave in an unpredictable and possibly unsafe manner | Commands must always be able to be given or the driver has no control. | |||
Emergency Management Center | Transportation Information Center | incident information for public | Low | Moderate | Moderate |
Generally, center-originating flows destined for a TIC don't contain any personal or confidential information, and are eventually intended for some kind of public consumption. | Minor discrepancies in this data should not have a catastrophic effect, but it should be reasonably controlled and accurate. | A few missed messages should not have a significant effect. However, most messages should make it through and the EMC should be able to know if the TIC has received a message. | |||
Emissions Management Center | Transportation Information Center | air quality information | Not Applicable | Moderate | Low |
This flow does not contain any personal or confidential information, and the data contained is eventually intended for public consumption. | Information for general distribution should have at least some guarantee that it was correctly transmitted. If this information were incorrect, people could be exposed to higher levels of pollution than they would intend, which could be harmful to people with medical conditions such as asthma. | Not a key flow for any service package. If an application is developed that relies on this flow, may change to MODERATE. | |||
Event Promoter System | Transportation Information Center | event information | Moderate | High | Moderate |
Confirmation flow should match the ratings of the flow providing information in the first place. | Confirmation flow should match the ratings of the flow providing information in the first place. | Confirmation flow should match the ratings of the flow providing information in the first place. | |||
Maint and Constr Management Center | Transportation Information Center | current infrastructure restrictions | Low | High | High |
Generally, center-originating flows destined for a TIC don't contain any personal or confidential information, and are eventually intended for some kind of public consumption. | If incorrect or unavailable this could result in a vehicle being somewhere it should not be due to infrastructure restrictions, which could have an impact on the infrastruture and the vehicle, including potential incidents (consider a large vehicle with narrow or height-restricted roadway). | If incorrect or unavailable this could result in a vehicle being somewhere it should not be due to infrastructure restrictions, which could have an impact on the infrastruture and the vehicle, including potential incidents (consider a large vehicle with narrow or height-restricted roadway). | |||
Maint and Constr Management Center | Transportation Information Center | maint and constr work plans | Low | High | High |
This data is eventually intended for public dissemination, and is also shared with many centers. | If incorrect or unavailable this could result in a vehicle being somewhere it should not be due to work zone impacts, which could have an impact on the infrastruture and the vehicle, including potential incidents (consider a large vehicle with narrow or height-restricted roadway). | If incorrect or unavailable this could result in a vehicle being somewhere it should not be due to work zone impacts, which could have an impact on the infrastruture and the vehicle, including potential incidents (consider a large vehicle with narrow or height-restricted roadway). | |||
Maint and Constr Management Center | Transportation Information Center | roadway maintenance status | Low | Moderate | Moderate |
Roadway maintenance status data is distributed to a host of places including travelers, so there is no justification for obfuscation. | Road maintenance data is generally distributed to travelers through a TIC, so this needs to be accurate and available so that travelers can make appropriate decisions. Inappropriate decisions may significantly affect traffic and individual travel experiences. | Road maintenance data is generally distributed to travelers through a TIC, so this needs to be accurate and available so that travelers can make appropriate decisions. Inappropriate decisions may significantly affect traffic and individual travel experiences. | |||
Maint and Constr Management Center | Transportation Information Center | work zone information | Low | Moderate | Moderate |
Eventually intended for public distribution, so no need to obfuscate. | Information needs to be timely and correct so that appropriate actions are taken on the part of the receiver. Trip plans, corresponding maintenance actions, transit and emergency vehicle routes, etc.; DISC: WYO believes this to be HIGH. | Information needs to be timely and correct so that appropriate actions are taken on the part of the receiver. Trip plans, corresponding maintenance actions, transit and emergency vehicle routes, etc. | |||
Other Transportation Information Centers | Transportation Information Center | alternate mode information | Low | Moderate | Low |
Generally, center-originating flows destined for a TIC don't contain any personal or confidential information, and are eventually intended for some kind of public consumption. | Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. | While useful, there is little impact if this flow is not available. | |||
Other Transportation Information Centers | Transportation Information Center | incident information for public | Low | Moderate | Moderate |
Generally, center-originating flows destined for a TIC don't contain any personal or confidential information, and are eventually intended for some kind of public consumption. | Publicly shared data about planned incidents should be accurate and delivered in timely fashion so as to enable end users to react appropriately; otherwise, signficant mobility challenges may result. | Publicly shared data about planned incidents should be accurate and delivered in timely fashion so as to enable end users to react appropriately; otherwise, signficant mobility challenges may result. | |||
Other Transportation Information Centers | Transportation Information Center | parking information | Moderate | Moderate | Moderate |
Does not include PII, but does include usage information for a managed facility that implies a number of vehicles. While this is observable information, it could be considered competitive, and regardless is accessible without being physically present, which is its own barrier. | Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. | Most likely not a frequently updated flow. Typically MODERATE for applications with a high degree of commercial vehicle parking, but could be LOW otherwise. | |||
Other Transportation Information Centers | Transportation Information Center | road network conditions | Low | Moderate | Moderate |
No harm should come from seeing this data, as it is eventually intended for public consumption. | While accuracy of this data is important for decision making purposes, applications should be able to corroborate the data in many instances. Thus MODERATE generally. | Depends on the application; if mobility decisions that affect large numbers of travelers are made based on this data, then it is MODERATE. In more modest circumstances, it may be LOW. | |||
Other Transportation Information Centers | Transportation Information Center | traffic image meta data | Low | Moderate | Moderate |
Traffic image data is generally intended for public consumption, and in any event is already video captured in the public arena, so this must be LOW. | While accuracy of this data is important for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally. | While accuracy of this data is important for decision making purposes, applications should be able to function without it. Thus MODERATE generally. | |||
Other Transportation Information Centers | Transportation Information Center | traffic images | Low | Moderate | Low |
Traffic image data is generally intended for public consumption, and in any event is already video captured in the public arena, so this must be LOW. | Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. | While useful, there is no signficant impact if this flow is not available. | |||
Other Transportation Information Centers | Transportation Information Center | transit service information | Low | Moderate | Low |
Generally, center-originating flows destined for a TIC don't contain any personal or confidential information, and are eventually intended for some kind of public consumption. | Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. | While useful, there is no signficant impact if this flow is not available. | |||
Parking Management Center | Transportation Information Center | parking information | Moderate | Moderate | Moderate |
Does not include PII, but does include usage information for a managed facility that implies a number of vehicles. While this is observable information, it could be considered competitive, and regardless is accessible without being physically present, which is its own barrier. | Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. | Most likely not a frequently updated flow. Typically MODERATE for applications with a high degree of commercial vehicle parking, but could be LOW otherwise. | |||
Payment Administration Center | Transportation Information Center | toll data | Low | Moderate | Low |
Should be public information, little benefit to obscuring this information. | Since actors may use this information to plan their travels, it must be correct. Corruption or manipulation of this data may lead them to make suboptimal decisions, costing time and/or money. | This flow probably does not update often. The information within is distributed via many routes. | |||
Personal Information Device | Traveler | traveler interface updates | Not Applicable | Moderate | Moderate |
Personalized data that includes directions and guidance for an individual, but eventually evident anyway. | Should be accurate as the Traveler will be relying on this information for routing and related choices. Lack of accuracy will result in lack of confidence from the traveler as well as an unsatisfactory trip, leading to a negative feedback spiral. | Users expect their devices to work. If information is not presented to the operator, the relevant applications simply won't be used. | |||
Surface Transportation Weather Service | Transportation Information Center | transportation weather information | Low | Moderate | Moderate |
Typically intended for public distribution. | There are several mechanisms by which weather information gets to a traveler, though given that the TIC may be performing some data fusion and providing value-added information, this data should be exchanged with some protection on its contents. | There are several mechanisms by which weather information gets to a traveler, though given that the TIC may be performing some data fusion and providing value-added information, this data should be exchanged with some protection on its contents. | |||
TIC Operator | Transportation Information Center | TIC operator input | Moderate | High | High |
Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. | Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. | Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. | |||
Traffic Management Center | Transportation Information Center | incident information for public | Low | Moderate | Moderate |
Generally, center-originating flows destined for a TIC don't contain any personal or confidential information, and are eventually intended for some kind of public consumption. | Incident information will be used to make routing and other travel decisions. Corrupted information may have a significant impac t on travel plans and/or road network conditions. | Significant numbers of travelers serve as end users for the information in this flow; lack of availability has a significant effect on their travel decisions. | |||
Traffic Management Center | Transportation Information Center | road network conditions | Low | Moderate | Moderate |
No harm should come from seeing this data, as it is eventually intended for public consumption. | While accuracy of this data is important for decision making purposes, applications should be able to corroborate the data in many instances. Thus MODERATE generally. | Depends on the application; if mobility decisions that affect large numbers of travelers are made based on this data, then it is MODERATE. In more modest circumstances, it may be LOW. | |||
Traffic Management Center | Transportation Information Center | traffic control information | Low | Moderate | Moderate |
Generally, center-originating flows destined for a TIC don't contain any personal or confidential information, and are eventually intended for some kind of public consumption. | While accuracy of this data is important for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally. | While accuracy of this data is important for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally. | |||
Traffic Management Center | Transportation Information Center | traffic image meta data | Low | Moderate | Moderate |
Traffic image data is generally intended for public consumption, and in any event is already video captured in the public arena, so this must be LOW. | While accuracy of this data is important for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally. | While accuracy of this data is important for decision making purposes, applications should be able to function without it. Thus MODERATE generally. | |||
Traffic Management Center | Transportation Information Center | traffic images | Low | Moderate | Moderate |
Intended for widespread and public distribution, so no reason to conceal. | While accuracy of this data is important for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally. | While availability of imagery is useful for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally, though it could be LOW. | |||
Transit Management Center | Transportation Information Center | transit and fare schedules | Low | Moderate | Moderate |
Generally, center-originating flows destined for a TIC don't contain any personal or confidential information, and are eventually intended for some kind of public consumption. | While accuracy of this data is important for decision making purposes, the greatest impact if manipulated or incorrect data would be financial and likely limited in scope. For example, making all options appear less expensive than an attacker's route of fiduciary interest, driving revenue to his route. This is undesireable and significant, but not catastrophic. Thus MODERATE generally. | While accuracy of this data is important for decision making purposes, applications should be able to function without frequent updates. Thus MODERATE generally, though it could be LOW depending on the level of projected updates. | |||
Transit Management Center | Transportation Information Center | transit incident information | Low | Moderate | Moderate |
Generally, center-originating flows destined for a TIC don't contain any personal or confidential information, and are eventually intended for some kind of public consumption. | While accuracy of this data is important for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally. | While availability of this data is important for decision making purposes, applications should be able to function without it. Thus MODERATE generally. | |||
Transit Management Center | Transportation Information Center | transit schedule adherence information | Low | Moderate | Moderate |
Eventually intended for public consumption, so no need to obfuscate. | While accuracy of this data is important for decision making purposes, applications should be able to function without it. Thus MODERATE generally. | While accuracy of this data is important for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally. | |||
Transportation Information Center | Connected Vehicle Roadside Equipment | traveler information application info | Moderate | Moderate | Low |
This information could be of interest to a malicious individual who is attempting to determine the best way to accomplish a crime. As such it would be best to not make it easily accessible. | If this is compromised, it could send unnecessary maintenance workers, or cause the appearance of excessive traffic violations, leading to further unnecessary investigation. | A delay in reporting this may cause a delay in necessary maintenance, but (a) this is not time-critical and (b) there are other channels for reporting malfunctioning. Additionally, there is a message received notification, which means that RSE can ensure that all intersection safety issues are delivered. | |||
Transportation Information Center | Media | traveler information for media | Low | Moderate | Moderate |
This information is intended for distribution to all members of the traveling public. | Traffic information needs to be accurate, as it will be used by travelers to make decisions regarding their travel. Inaccurate or corrupted data could reduce overall mobility and certainly impact individual drivers. | There should be other means for getting this information, but as this is the 'source flow' for a wide area broadcast with a huge potential distribution, the breadth of the impact covers all travelers. | |||
Transportation Information Center | Other Transportation Information Centers | alternate mode information | Low | Moderate | Low |
Generally, center-originating flows destined for a TIC don't contain any personal or confidential information, and are eventually intended for some kind of public consumption. | Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. | While useful, there is little impact if this flow is not available. | |||
Transportation Information Center | Other Transportation Information Centers | incident information for public | Low | Moderate | Moderate |
Generally, center-originating flows destined for a TIC don't contain any personal or confidential information, and are eventually intended for some kind of public consumption. | Publicly shared data about planned incidents should be accurate and delivered in timely fashion so as to enable end users to react appropriately; otherwise, signficant mobility challenges may result. | Publicly shared data about planned incidents should be accurate and delivered in timely fashion so as to enable end users to react appropriately; otherwise, signficant mobility challenges may result. | |||
Transportation Information Center | Other Transportation Information Centers | parking information | Moderate | Moderate | Moderate |
Does not include PII, but does include usage information for a managed facility that implies a number of vehicles. While this is observable information, it could be considered competitive, and regardless is accessible without being physically present, which is its own barrier. | Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. | While useful, there is no signficant impact if this flow is not available. | |||
Transportation Information Center | Other Transportation Information Centers | road network conditions | Low | Moderate | Moderate |
No harm should come from seeing this data, as it is eventually intended for public consumption. | While accuracy of this data is important for decision making purposes, applications should be able to corroborate the data in many instances. Thus MODERATE generally. | condition info should be timely and readily available so that TMCs are aware of current traffic info, conditions, restrictions, etc. but should not have severe/catastrophic consequences if not | |||
Transportation Information Center | Other Transportation Information Centers | traffic image meta data | Low | Moderate | Moderate |
Traffic image data is generally intended for public consumption, and in any event is already video captured in the public arena, so this must be LOW. | While accuracy of this data is important for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally. | While accuracy of this data is important for decision making purposes, applications should be able to function without it. Thus MODERATE generally. | |||
Transportation Information Center | Other Transportation Information Centers | traffic images | Low | Moderate | Low |
Traffic image data is generally intended for public consumption, and in any event is already video captured in the public arena, so this must be LOW. | Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. | While useful, there is no signficant impact if this flow is not available. | |||
Transportation Information Center | Other Transportation Information Centers | transit service information | Low | Moderate | Low |
Generally, center-originating flows destined for a TIC don't contain any personal or confidential information, and are eventually intended for some kind of public consumption. | Generally transportation coordination information should be correct between source and destination, or inappropriate actions may be taken. | While useful, there is no signficant impact if this flow is not available. | |||
Transportation Information Center | Personal Information Device | broadcast traveler information | Not Applicable | Moderate | Low |
By definition this is publicly broadcast data. | The distribution of this data is intended to be very large, as such the impact of corrupted data will be significant. Probably not HIGH, as there are other distribution channels for this data. | There are multiple channels for the delivery of this information, so if this one is not available, others will work. | |||
Transportation Information Center | TIC Operator | TIC operations information presentation | Moderate | High | High |
Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. | Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. | Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. | |||
Transportation Information Center | Traveler Support Equipment | broadcast traveler information | Not Applicable | Moderate | Low |
By definition this is publicly broadcast data. | The distribution of this data is intended to be very large, as such the impact of corrupted data will be significant. Probably not HIGH, as there are other distribution channels for this data. | There are multiple channels for the delivery of this information, so if this one is not available, others will work. | |||
Transportation Information Center | Vehicle | broadcast traveler information | Not Applicable | Moderate | Moderate |
By definition this is publicly broadcast data. | The distribution of this data is intended to be very large, as such the impact of corrupted data will be significant. Probably not HIGH, as there are other distribution channels for this data. | There are multiple channels for the delivery of this information, so if this one is not available, others will work. DISC: WYO suggests this is LOW. | |||
Traveler | Personal Information Device | traveler input | Not Applicable | Moderate | Low |
This data is informing the vehicle of operational information that is relevant to the operation of the vehicle. It should not contain anything sensitive, and does not matter if another person can observe it. | While public, information must be correct or travelers may make incorrect decisions with regard to their travel plans. | Information is available through other means, though depending on the location this might not always be the case, in which case this would be MODERATE. | |||
Traveler | Traveler Support Equipment | traveler input | Not Applicable | Moderate | Low |
Publicly available information, while not directly observable, is intended for widespread distribution | While public, information must be correct or travelers may make incorrect decisions with regard to their travel plans. | Information is available through other means, though depending on the location this might not always be the case, in which case this would be MODERATE. | |||
Traveler Support Equipment | Traveler | traveler interface updates | Not Applicable | Moderate | Moderate |
Publicly available information, while not directly observable, is intended for widespread distribution | Should be accurate as the Traveler will be relying on this information for routing and related choices. Lack of accuracy will result in lack of confidence from the traveler as well as an unsatisfactory trip, leading to a negative feedback spiral. | Users expect their devices to work. If information is not presented to the operator, the relevant applications simply won't be used. | |||
Vehicle | Driver | driver updates | Not Applicable | Moderate | Moderate |
This data is informing the driver about the safety of a nearby area. It should not contain anything sensitive, and does not matter if another person can observe it. | This is the information that is presented to the driver. If they receive incorrect information, they may act in an unsafe manner. However, there are other indicators that would alert them to any hazards, such as an oncoming vehicle or crossing safety lights. | If this information is not made available to the driver, then the system has not operated correctly. | |||
Weather Service System | Transportation Information Center | qualified environmental conditions data | Low | Moderate | Low |
If this data were exposed there would be little to no harm, except that the exposure was not authorized and the sender had no knowledge of downstream data usage. That alone is difficult to judge as 'serious harm' so left at LOW. | Since the point of this particular flow is to provide data that is already quality checked, corruption of this data would have a significant negative impact on the users of this data. | This flow is used to help guide traveler actions. There should be other compensating flows and sources of this type of information if this one is not available, which justifies LOW. | |||
Weather Service System | Transportation Information Center | weather information | Low | Moderate | Moderate |
WYO believes this should be LOW or MODERATE depending on the application. | While there are many sources of weather information, some guarantee of correctness is justifiable to keep confidence in provided service. | There should be other sources of this data. It does need to be reliable however; weather can change quickly, and depending on the destination and its operational strategies, timely response may be important. |
Standards
The following table lists the standards associated with physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages.
Name | Title | Physical Object |
---|---|---|
CTI 4001 RSU | Dedicated Short-Range Communications Roadside Unit Specifications (FHWA-JPO-17-589) | Connected Vehicle Roadside Equipment |
System Requirements
System Requirement | Need | ||
---|---|---|---|
001 | The system shall collect traveler information for distribution including traffic and road conditions, incident information, maintenance and construction information, event information, transit information, parking information, and weather information. | 01 | Traveler Information needs to be able to collect timely, accurate, and reliable traffic, transit, and other road conditions data from multiple sources in order to broadcast the latest conditions affecting travelers. |
002 | The system shall distribute location relevant traveler information to short range communications equipment at the roadside. | 02 | Traveler Information needs to be able to inform as much of the traveling public as possible using any available broadcast media to increase mobility and safety through better information. |
003 | The system shall provide the capability for a system operator to monitor connected vehicle system operation and control the type and update frequency of traveler information that is distributed. | 02 | Traveler Information needs to be able to inform as much of the traveling public as possible using any available broadcast media to increase mobility and safety through better information. |
004 | The system shall collect, process, and store traffic and highway condition information, including incident information, detours and road closures, event information, recommended routes, and current speeds on specific routes. | 01 | Traveler Information needs to be able to collect timely, accurate, and reliable traffic, transit, and other road conditions data from multiple sources in order to broadcast the latest conditions affecting travelers. |
005 | The system shall collect, process, and store maintenance and construction information, including scheduled maintenance and construction work activities and work zone activities. | 01 | Traveler Information needs to be able to collect timely, accurate, and reliable traffic, transit, and other road conditions data from multiple sources in order to broadcast the latest conditions affecting travelers. |
006 | The system shall collect, process, and store transit routes and schedules, transit transfer options, transit fares, and real-time schedule adherence information. | 01 | Traveler Information needs to be able to collect timely, accurate, and reliable traffic, transit, and other road conditions data from multiple sources in order to broadcast the latest conditions affecting travelers. |
007 | The system shall collect, process, and store parking information, including location, availability, and fees. | 01 | Traveler Information needs to be able to collect timely, accurate, and reliable traffic, transit, and other road conditions data from multiple sources in order to broadcast the latest conditions affecting travelers. |
008 | The system shall collect, process, and store toll fee information. | 01 | Traveler Information needs to be able to collect timely, accurate, and reliable traffic, transit, and other road conditions data from multiple sources in order to broadcast the latest conditions affecting travelers. |
009 | The system shall collect, process, and store current and forecast road conditions and surface weather conditions. | 01 | Traveler Information needs to be able to collect timely, accurate, and reliable traffic, transit, and other road conditions data from multiple sources in order to broadcast the latest conditions affecting travelers. |
010 | The system shall collect, process, and store event information. | 01 | Traveler Information needs to be able to collect timely, accurate, and reliable traffic, transit, and other road conditions data from multiple sources in order to broadcast the latest conditions affecting travelers. |
011 | The system shall collect, process, and store air quality information. | 01 | Traveler Information needs to be able to collect timely, accurate, and reliable traffic, transit, and other road conditions data from multiple sources in order to broadcast the latest conditions affecting travelers. |
012 | The system shall disseminate traffic and highway condition information to travelers, including incident information, detours and road closures, event information, recommended routes, and current speeds on specific routes. | 02 | Traveler Information needs to be able to inform as much of the traveling public as possible using any available broadcast media to increase mobility and safety through better information. |
013 | The system shall disseminate maintenance and construction information to travelers, including scheduled maintenance and construction work activities and work zone activities. | 02 | Traveler Information needs to be able to inform as much of the traveling public as possible using any available broadcast media to increase mobility and safety through better information. |
014 | The system shall disseminate transit routes and schedules, transit transfer options, transit fares, and real-time schedule adherence information to travelers. | 02 | Traveler Information needs to be able to inform as much of the traveling public as possible using any available broadcast media to increase mobility and safety through better information. |
015 | The system shall disseminate parking information to travelers, including location, availability, and fees. | 02 | Traveler Information needs to be able to inform as much of the traveling public as possible using any available broadcast media to increase mobility and safety through better information. |
016 | The system shall disseminate toll fee information to travelers. | 02 | Traveler Information needs to be able to inform as much of the traveling public as possible using any available broadcast media to increase mobility and safety through better information. |
017 | The system shall disseminate weather information to travelers. | 02 | Traveler Information needs to be able to inform as much of the traveling public as possible using any available broadcast media to increase mobility and safety through better information. |
018 | The system shall disseminate event information to travelers. | 02 | Traveler Information needs to be able to inform as much of the traveling public as possible using any available broadcast media to increase mobility and safety through better information. |
019 | The system shall disseminate air quality information to travelers. | 02 | Traveler Information needs to be able to inform as much of the traveling public as possible using any available broadcast media to increase mobility and safety through better information. |
020 | The system shall provide traffic and incident data to the media. | 02 | Traveler Information needs to be able to inform as much of the traveling public as possible using any available broadcast media to increase mobility and safety through better information. |
021 | The system shall provide the capability for a system operator to control the type and update frequency of broadcast traveler information. | 02 | Traveler Information needs to be able to inform as much of the traveling public as possible using any available broadcast media to increase mobility and safety through better information. |
022 | The system shall distribute traveler information including traffic and road conditions or upcoming work zones to passing vehicles using short range communications, under center control. | 02 | Traveler Information needs to be able to inform as much of the traveling public as possible using any available broadcast media to increase mobility and safety through better information. |
023 | The system shall return system operational status to the controlling center. | 02 | Traveler Information needs to be able to inform as much of the traveling public as possible using any available broadcast media to increase mobility and safety through better information. |
024 | The system shall receive traffic information from a center and present it to the traveler. | 03 | Travelers need access to timely, accurate, and reliable traffic, transit, and other travel conditions in order to make informed decisions about their travel. |
025 | The system shall receive transit information from a center and present it to the traveler. | 03 | Travelers need access to timely, accurate, and reliable traffic, transit, and other travel conditions in order to make informed decisions about their travel. |
026 | The system shall receive event information from a center and present it to the traveler. | 03 | Travelers need access to timely, accurate, and reliable traffic, transit, and other travel conditions in order to make informed decisions about their travel. |
027 | The system shall provide the capability for digitized map data to act as the background to the information presented to the traveler. | 03 | Travelers need access to timely, accurate, and reliable traffic, transit, and other travel conditions in order to make informed decisions about their travel. |
028 | The system shall support traveler input in audio or manual form. | 03 | Travelers need access to timely, accurate, and reliable traffic, transit, and other travel conditions in order to make informed decisions about their travel. |
029 | The system shall present information to the traveler in audible or visual forms consistent with a kiosk, including those that are suitable for travelers with hearing or vision physical disabilities. | 03 | Travelers need access to timely, accurate, and reliable traffic, transit, and other travel conditions in order to make informed decisions about their travel. |
030 | The system shall store frequently requested displayed data. | 03 | Travelers need access to timely, accurate, and reliable traffic, transit, and other travel conditions in order to make informed decisions about their travel. |
031 | The system shall provide broadcast traveler information in audio or manual form. | 03 | Travelers need access to timely, accurate, and reliable traffic, transit, and other travel conditions in order to make informed decisions about their travel. |
032 | The system shall present information to the traveler in audible or visual forms, consistent with a personal device. | 03 | Travelers need access to timely, accurate, and reliable traffic, transit, and other travel conditions in order to make informed decisions about their travel. |
033 | The system shall receive traveler information including traffic and road conditions, incident information, maintenance and construction information, event information, transit information, parking information, and weather information. | 03 | Travelers need access to timely, accurate, and reliable traffic, transit, and other travel conditions in order to make informed decisions about their travel. |
034 | The system shall present the received information to the driver in audible or visual forms without impairing the driver's ability to control the vehicle in a safe manner. | 03 | Travelers need access to timely, accurate, and reliable traffic, transit, and other travel conditions in order to make informed decisions about their travel. |
035 | The system shall receive formatted traffic information from a center and present it to the driver. | 03 | Travelers need access to timely, accurate, and reliable traffic, transit, and other travel conditions in order to make informed decisions about their travel. |
036 | The system shall receive transit information from a center and present it to the driver. | 03 | Travelers need access to timely, accurate, and reliable traffic, transit, and other travel conditions in order to make informed decisions about their travel. |
037 | The system shall receive event information from a center and present it to the driver. | 03 | Travelers need access to timely, accurate, and reliable traffic, transit, and other travel conditions in order to make informed decisions about their travel. |
038 | The system shall provide data from the vehicle itself to the driver. This vehicle data may include vehicle conditions, environmental conditions, safety or position warnings. | 02 | Traveler Information needs to be able to inform as much of the traveling public as possible using any available broadcast media to increase mobility and safety through better information. |
039 | The system shall prioritize safety and warning messages to supersede advisory and broadcast messages. | 02 | Traveler Information needs to be able to inform as much of the traveling public as possible using any available broadcast media to increase mobility and safety through better information. |
040 | The system shall support driver input in audio or manual form. | 02 | Traveler Information needs to be able to inform as much of the traveling public as possible using any available broadcast media to increase mobility and safety through better information. |
041 | The system shall present information to the driver in audible or visual forms without impairing the driver's ability to control the vehicle in a safe manner. | 03 | Travelers need access to timely, accurate, and reliable traffic, transit, and other travel conditions in order to make informed decisions about their travel. |
042 | The system shall receive traveler information from Connected Vehicle Roadside Equipment. | 02 | Traveler Information needs to be able to inform as much of the traveling public as possible using any available broadcast media to increase mobility and safety through better information. |
Implementations
TI01.1 Wide Area Broadcast Implementation
Use wide area wireless communication to broadcast traveler information of general interest to all vehicles in a region.
Wide Area Broadcast Implementation Flows
Information Flow | Description | Inclusion Status |
---|---|---|
air quality information | Aggregated region-wide measured air quality data and possible pollution incident information. | At Least One |
alternate mode information | Schedule information for alternate mode transportation providers such as air, ferry, and passenger-carrying heavy rail. This also includes details of incidents and other service disruptions that have occurred in the alternative mode. This also includes measures of service demand that supports assessment of their impact on the road network. | Optional |
alternate mode information | Schedule information for alternate mode transportation providers such as air, ferry, and passenger-carrying heavy rail. This also includes details of incidents and other service disruptions that have occurred in the alternative mode. This also includes measures of service demand that supports assessment of their impact on the road network. | At Least One |
border crossing status information | Port of entry status including current wait-times, lane configuration and status including closures and restrictions, and notification of incidents at the border | At Least One |
broadcast traveler information | General traveler information that contains traffic and road conditions, link travel times, incidents, advisories, restrictions, vehicle requirements, work zones, transit service information, weather information, parking information, and other related traveler information. | Fundamental |
broadcast traveler information | General traveler information that contains traffic and road conditions, link travel times, incidents, advisories, restrictions, vehicle requirements, work zones, transit service information, weather information, parking information, and other related traveler information. | Optional |
current infrastructure 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. | At Least One |
driver input | Driver input to the vehicle on-board equipment including configuration data, settings and preferences, interactive requests, and control commands. | Optional |
driver updates | Information provided to the driver including visual displays, audible information and warnings, and haptic feedback. The updates inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment. | Optional |
event information | Special event information for travelers. This would include a broader array of information than the similar "event plans" that conveys only information necessary to support traffic management for the event. | At Least One |
incident information for public | Report of current desensitized incident information prepared for public dissemination. | Optional |
incident information for public | Report of current desensitized incident information prepared for public dissemination. | At Least One |
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. | At Least One |
parking information | General parking information and status, including current parking availability, parking pricing, and parking space availability information, including features like number and type of electric charging spots. | Optional |
parking information | General parking information and status, including current parking availability, parking pricing, and parking space availability information, including features like number and type of electric charging spots. | At Least One |
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. | At Least One |
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 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. | At Least One |
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 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. | Optional |
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). | At Least One |
TIC operations information presentation | Presentation of information to the TIC Operator including current operational status, parameters for broadcast information settings, route selection controls, and travel optimization algorithms. | Optional |
TIC operator input | User input from the TIC system operator including requests to monitor current system operation and inputs to affect system operation including tuning and performance enhancement parameters to traveler information algorithms. | Optional |
toll data | Current toll schedules for different types of vehicles as well as advanced toll payment information. | At Least One |
traffic control information | Represents the flow of traffic control and status information between centers. This is reporting only, not actual control. This specifically includes the current state of any demand management strategies that have been implemented. | At Least One |
traffic image meta data | Meta data that describes traffic images. Traffic images (video) are in another flow. | Optional |
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. Meta data that describes the images is contained in another flow. | Optional |
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. Meta data that describes the images is contained in another flow. | At Least One |
transit and fare schedules | Transit service information including routes, schedules, and fare information. This also includes on-demand service information. | At Least One |
transit incident information | Information on transit incidents that impact transit services for public dissemination. | At Least One |
transit schedule adherence information | Dynamic transit schedule adherence and transit vehicle location information. | At Least One |
transit service information | Transit service information including routes, schedules, and fare information as well as dynamic transit schedule adherence and transit vehicle location information. | At Least One |
transit service information | Transit service information including routes, schedules, and fare information as well as dynamic transit schedule adherence and transit vehicle location information. | Optional |
transportation weather information | Current and forecast road conditions and weather information (e.g., surface condition, flooding, wind advisories, visibility, etc.) associated with the transportation network. This information is of a resolution, timeliness, and accuracy to be useful in transportation decision making. | At Least One |
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. | Optional |
traveler input | User input from a traveler to summon assistance, request travel information, make a reservation, or request any other traveler service. | Optional |
traveler interface updates | Visual or audio information (e.g., routes, messages, guidance, emergency information) that is provided to the traveler. | Optional |
weather information | Accumulated forecasted and current weather data (e.g., temperature, pressure, wind speed, wind direction, humidity, precipitation, visibility, light conditions, etc.). | At Least One |
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. | At Least One |
Wide Area Broadcast Implementation Functional Objects
Back to Implementation List
TI01.2 C-ITS Local Broadcast Implementation
Use short range communications to broadcast traveler information only within the local area where that information is relevant.
C-ITS Local Broadcast Implementation Flows
Information Flow | Description | Inclusion Status |
---|---|---|
air quality information | Aggregated region-wide measured air quality data and possible pollution incident information. | At Least One |
alternate mode information | Schedule information for alternate mode transportation providers such as air, ferry, and passenger-carrying heavy rail. This also includes details of incidents and other service disruptions that have occurred in the alternative mode. This also includes measures of service demand that supports assessment of their impact on the road network. | At Least One |
alternate mode information | Schedule information for alternate mode transportation providers such as air, ferry, and passenger-carrying heavy rail. This also includes details of incidents and other service disruptions that have occurred in the alternative mode. This also includes measures of service demand that supports assessment of their impact on the road network. | Optional |
border crossing status information | Port of entry status including current wait-times, lane configuration and status including closures and restrictions, and notification of incidents at the border | At Least One |
current infrastructure 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. | At Least One |
driver input | Driver input to the vehicle on-board equipment including configuration data, settings and preferences, interactive requests, and control commands. | Optional |
driver updates | Information provided to the driver including visual displays, audible information and warnings, and haptic feedback. The updates inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment. | Optional |
event information | Special event information for travelers. This would include a broader array of information than the similar "event plans" that conveys only information necessary to support traffic management for the event. | At Least One |
incident information for public | Report of current desensitized incident information prepared for public dissemination. | Optional |
incident information for public | Report of current desensitized incident information prepared for public dissemination. | At Least One |
local traveler information | Traveler information including traffic, road, and weather conditions for a particular locality. This flow includes the location-specific traveler information and time effectivity of the information. | Optional |
local traveler information | Traveler information including traffic, road, and weather conditions for a particular locality. This flow includes the location-specific traveler information and time effectivity of the information. | Fundamental |
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. | At Least One |
parking information | General parking information and status, including current parking availability, parking pricing, and parking space availability information, including features like number and type of electric charging spots. | Optional |
parking information | General parking information and status, including current parking availability, parking pricing, and parking space availability information, including features like number and type of electric charging spots. | At Least One |
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. | At Least One |
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 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. | At Least One |
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 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. | Optional |
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). | At Least One |
TIC operations information presentation | Presentation of information to the TIC Operator including current operational status, parameters for broadcast information settings, route selection controls, and travel optimization algorithms. | Optional |
TIC operator input | User input from the TIC system operator including requests to monitor current system operation and inputs to affect system operation including tuning and performance enhancement parameters to traveler information algorithms. | Optional |
toll data | Current toll schedules for different types of vehicles as well as advanced toll payment information. | At Least One |
traffic control information | Represents the flow of traffic control and status information between centers. This is reporting only, not actual control. This specifically includes the current state of any demand management strategies that have been implemented. | At Least One |
traffic image meta data | Meta data that describes traffic images. Traffic images (video) are in another flow. | Optional |
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. Meta data that describes the images is contained in another flow. | At Least One |
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. Meta data that describes the images is contained in another flow. | Optional |
transit and fare schedules | Transit service information including routes, schedules, and fare information. This also includes on-demand service information. | At Least One |
transit incident information | Information on transit incidents that impact transit services for public dissemination. | At Least One |
transit schedule adherence information | Dynamic transit schedule adherence and transit vehicle location information. | At Least One |
transit service information | Transit service information including routes, schedules, and fare information as well as dynamic transit schedule adherence and transit vehicle location information. | Optional |
transit service information | Transit service information including routes, schedules, and fare information as well as dynamic transit schedule adherence and transit vehicle location information. | At Least One |
transportation weather information | Current and forecast road conditions and weather information (e.g., surface condition, flooding, wind advisories, visibility, etc.) associated with the transportation network. This information is of a resolution, timeliness, and accuracy to be useful in transportation decision making. | At Least One |
traveler information application info | Traveler information and associated parameters, filters, and thresholds that control the RSE's distribution of the traveler information to passing vehicles. This flow also supports remote control of the application so the application can be taken offline, reset, or restarted. | Fundamental |
traveler information application status | Application status reported by the RSE. This includes current operational state and status of the RSE and a record of traveler information distribution. | Fundamental |
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. | Optional |
traveler input | User input from a traveler to summon assistance, request travel information, make a reservation, or request any other traveler service. | Optional |
traveler interface updates | Visual or audio information (e.g., routes, messages, guidance, emergency information) that is provided to the traveler. | Optional |
weather information | Accumulated forecasted and current weather data (e.g., temperature, pressure, wind speed, wind direction, humidity, precipitation, visibility, light conditions, etc.). | At Least One |
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. | At Least One |
C-ITS Local Broadcast Implementation Functional Objects
Back to Implementation List