Type: Environmental

Groups:
  • AERIS/ Sustainable Travel
Diagrams are based on the most recently available application concepts that the CVRIA team has access to, and do not necessarily reflect prototypes or other in-development activities.

Eco-Lanes Management

The Eco-Lanes Management application supports the operations of eco-lanes – dedicated lanes similar to high-occupancy vehicle (HOV) or high-occupancy toll (HOT) lanes, but optimized for the environment. The application employs communication technology to gather traffic and environmental information from multiple sources including infrastructure, vehicles, and other systems. The application then processes these data and determines whether an eco-lane should be created or decommissioned along a roadway. These decisions would be in response to real-time traffic and environmental conditions. While the eco-lanes would have the capability to be flexible and more dynamic, it is envisioned that these parameters would change only as needed to ensure that travelers do not become confused by a system that is too dynamic in nature. Travelers would need to assume some level of consistency with their trip and should not be surprised by constant changing of the eco-lane's parameters. The Eco-Lanes Management application establishes parameters and defines or geo-fences the eco-lanes boundaries. Eco-lanes parameters may include the types of vehicles allowed in the eco-lanes, emissions parameters for entering the eco-lanes, the number of lanes, and the start and end of the eco-lanes. The application also conveys this information about eco-lanes to traveler information centers so those centers can provide the information to travelers.

Enterprise

This is one way this application may be realized, but not the only way. There are other ways to build a given application and accomplish a stated objective.
The enterprise diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagrams: Installation Operations Maintenance Certification
PNG Diagrams: Installation Operations Maintenance Certification


Display Legend in SVG or PNG

Business Interaction Matrix:

Eco-Lanes Management Operations Stage
Vehicle OwnerDriverVehicle OBE OwnerRoadway OwnerRSE OwnerRSE OperatorITS Roadway Equipment OwnerITS Roadway OperatorTraffic ManagerEmissions ManagerInformation Service ProviderTraffic Operations PersonnelOther Traffic ManagerEnforcementTransit Fleet ManagerVehicle Basic Safety ProviderRSE Restricted Lanes Application ProviderVehicle Restricted Lanes Application ProviderVehicle Emissions Monitoring ProviderVehicle Roadside Information Reception Provider
Vehicle OwnerVehicle Usage AgreementVehicle OBE Usage AgreementApplication Usage AgreementApplication Usage AgreementApplication Usage AgreementApplication Usage Agreement
DriverVehicle Usage AgreementExpectation of Information Provision
Vehicle OBE OwnerVehicle OBE Usage AgreementExpectation of Information ProvisionExpectation of Data Provision
Roadway OwnerService Delivery Agreement
RSE OwnerService Delivery AgreementOperations AgreementInformation Exchange AgreementInformation Exchange AgreementInformation Exchange AgreementInformation Provision AgreementApplication Usage Agreement
RSE OperatorExpectation of Data ProvisionOperations AgreementOperations AgreementTraffic Management Agreement
ITS Roadway Equipment OwnerInformation Exchange AgreementOperations Agreement
ITS Roadway OperatorOperations AgreementOperations AgreementTraffic Management Agreement
Traffic ManagerInformation Exchange AgreementTraffic Management AgreementTraffic Management AgreementInformation Exchange AgreementInformation Provision AgreementEmployment AgreementInformation Exchange AgreementInformation Provision AgreementInformation Provision Agreement
Emissions ManagerInformation Exchange AgreementInformation Exchange AgreementInformation Provision Agreement
Information Service ProviderInformation Provision Agreement
Traffic Operations PersonnelEmployment Agreement
Other Traffic ManagerInformation Exchange Agreement
EnforcementInformation Provision AgreementInformation Provision AgreementInformation Provision Agreement
Transit Fleet ManagerInformation Provision Agreement
Vehicle Basic Safety ProviderApplication Usage Agreement
RSE Restricted Lanes Application ProviderApplication Usage Agreement
Vehicle Restricted Lanes Application ProviderApplication Usage Agreement
Vehicle Emissions Monitoring ProviderApplication Usage Agreement
Vehicle Roadside Information Reception ProviderApplication Usage Agreement

Includes Enterprise Objects:

Enterprise Object Description
Application Certification Entity The body that determines whether an application may be deployed and operated in the Connected Vehicle Environment. This entity's composition, the requirements it applies and the procedures it uses to verify those requirements may vary with application type. For example, applications with human safety component (crash avoidance, movement assistance etc.) may have stringent requirements and extensive testing in a variety of conditions, while applications that provide strictly mobility functionality may have far less testing requirements; possibly as little as just making sure the application doesn't interfere with any other applications.
Device Certification Entity The body that determines whether a device may be deployed and operated in the Connected Vehicle Environment. This entity's composition, the requirements it applies and the procedures it uses to verify those requirements may vary with device type.
Driver 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.
Emissions Connected Vehicle Monitoring Installer Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Emissions Connected Vehicle Monitoring Maintainer Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Emissions Connected Vehicle Monitoring Provider Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
Emissions Data Management Installer Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Emissions Data Management Maintainer Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Emissions Data Management Provider Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
Emissions Manager The entity responsible for the monitoring of and reaction to emissions.
Enforcement Agencies that are responsible for identifying and reporting violations of roadway regulations, including emissions, traffic violations, toll violations, etc.
Federal Regulatory Federal regulatory bodies that have legal authority to control and/or provide input to policies regulating transportation infrastructure and operations. This includes entities such as the Federal Communications Commission and US Department of Transportation.
Information Service Provider The "Information Service Provider" represents the owner of the Transportation Information Center. The Information Service Provider is responsible for collecting and disseminating information relevant to the traveling public.
ITS Certification Entity The body that determines whether an ITS device or application may be deployed and operated in the transportation environment. This entity's composition, the requirements it applies and the procedures it uses to verify those requirements may vary with device and application type. Typically not a formal body, assigned on a project-by-project basis depending on the type of infrastructure involved. Since ITS projects are locally-focused (typically state or smaller), the entities that are part of this body are typically those with operational jurisdiction where the ITS is installed (e.g., state or local DOTs, state or local maintenance managers etc.)
ITS Roadway Equipment Owner The entity that owns the Roadway ITS equipment.
ITS Roadway Operator The entity that operates the Roadway ITS equipment.
Other Traffic Manager Representing another Traffic Manager, "Other Traffic Manager" provides the source and destination for agreements and expectations between Traffic Managers, enabling traffic management activities to be coordinated across jurisdictional boundaries.
Roadway Basic Surveillance Installer Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Roadway Basic Surveillance Maintainer Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Roadway Basic Surveillance Provider Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
Roadway Dynamic Lane Management and Shoulder Use Installer Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Roadway Dynamic Lane Management and Shoulder Use Maintainer Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Roadway Dynamic Lane Management and Shoulder Use Provider Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
Roadway Emissions Monitoring Installer Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Roadway Emissions Monitoring Maintainer Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Roadway Emissions Monitoring Provider Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
Roadway Owner The owner of the roadway proximate to which roadside equipment will be/is installed.
Roadway Traffic Information Dissemination Installer Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Roadway Traffic Information Dissemination Maintainer Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Roadway Traffic Information Dissemination Provider Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
RSE Deployer The entity responsible for the deployment, operations and maintenance of roadside equipment.
RSE Environmental Monitoring Installer Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
RSE Environmental Monitoring Maintainer Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
RSE Environmental Monitoring Provider Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
RSE Operator The entity that operates roadside equipment in the transportation environment.
RSE Owner The owner of roadside equipment.
RSE Provider The "RSE Provider" is the entity that develops and (presumably) sells roadside equipment to other entities for deployment and research.
RSE Restricted Lanes Application Installer Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
RSE Restricted Lanes Application Maintainer Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
RSE Restricted Lanes Application Provider Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
RSE Traffic Monitoring Installer Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
RSE Traffic Monitoring Maintainer Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
RSE Traffic Monitoring Provider Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
RSE Traveler Information Communications Installer Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
RSE Traveler Information Communications Maintainer Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
RSE Traveler Information Communications Provider Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
State Regulatory State regulatory bodies that have legal authority to control and/or provide input to policies regulating vehicles, transportation infrastructure and operations. This includes entities like Departments of Motor Vehicles, property tax authorities and tolling agencies.
TMC Dynamic Lane Management and Shoulder Use Installer Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
TMC Dynamic Lane Management and Shoulder Use Maintainer Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
TMC Dynamic Lane Management and Shoulder Use Provider Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
TMC In-Vehicle Signing Management Installer Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
TMC In-Vehicle Signing Management Maintainer Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
TMC In-Vehicle Signing Management Provider Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
TMC Regional Traffic Management Installer Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
TMC Regional Traffic Management Maintainer Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
TMC Regional Traffic Management Provider Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
TMC Restricted Lanes CV Application Installer Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
TMC Restricted Lanes CV Application Maintainer Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
TMC Restricted Lanes CV Application Provider Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
TMC Traffic Information Dissemination Installer Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
TMC Traffic Information Dissemination Maintainer Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
TMC Traffic Information Dissemination Provider Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
TMC Traffic Surveillance Installer Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
TMC Traffic Surveillance Maintainer Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
TMC Traffic Surveillance Provider Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
Traffic Manager The entity responsible for the management of traffic, both freeway and arterial.
Traffic Operations Personnel 'Traffic Operations Personnel' represents the people that operate a traffic management center. These personnel interact with traffic control systems, traffic surveillance systems, incident management systems, work zone management systems, and travel demand management systems. They provide operator data and command inputs to direct system operations to varying degrees depending on the type of system and the deployment scenario.
Transit Fleet Manager The agency or organization that operates transit vehicles. This includes administration, routing, driver instruction, maintenance and any other responsibilities associated with the operations and maintenance of a transit system.
Vehicle Basic Safety Installer Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Vehicle Basic Safety Maintainer Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Vehicle Basic Safety Provider Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
Vehicle Emissions Monitoring Installer Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Vehicle Emissions Monitoring Maintainer Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Vehicle Emissions Monitoring Provider Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
Vehicle Manufacturer The entity that builds, assembles, verifies and validates the Vehicle in which the Vehicle OBE will eventually operate.
Vehicle OBE Manufacturer The entity that builds, assembles, verifies and validates the Vehicle OBE. This can be an OEM-equipped OBE, retrofit or aftermarket equipment.
Vehicle OBE Owner The entity, individual, group or corporation that owns the Vehicle On-Board equipment. This could be the same as the Vehicle Owner, but it could be a third part that licenses the use of the OBE to the Owner.
Vehicle Owner The individual, group of individuals or corporate entity that is identified as the registered owner of the Vehicle under state law.
Vehicle Restricted Lanes Application Installer Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Vehicle Restricted Lanes Application Maintainer Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Vehicle Restricted Lanes Application Provider Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
Vehicle Roadside Information Reception Installer Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Vehicle Roadside Information Reception Maintainer Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Vehicle Roadside Information Reception Provider Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.

Includes Resources:

Resource Description
Application Component Certification Requirements The requirements that define the functionality, performance and operational environment of an application component. Certification Requirements must be met in order for an application to be installed in the CVE.
Backoffice Service Development System The systems used to develop backoffice (center) hardware and software components of applications.
Backoffice Service Installation System The systems used to install and configure backoffice (center) hardware and software components.
Backoffice Service Maintenance System The systems used to maintain and upgrade backoffice (center) hardware and software components.
Device Certification Requirements The requirements that define the functionality, performance and operational environment of a connected vehicle device. Certification Requirements must be met in order for the device to be granted the credentials necessary to operate in the Connected Vehicle Environment.
Emissions Connected Vehicle Monitoring "Emissions Connected Vehicle Monitoring" collects emissions data reported by passing vehicles and uses this data to support air quality management and planning. Coordination with traffic management supports air quality-responsive management of traffic.
Emissions Data Management "Emissions Data Management" collects and stores air quality and vehicle emissions information by remotely monitoring and controlling area wide and point sensors. General air quality measures are distributed as general traveler information and also may be used in demand management programs. Collected roadside emissions are analyzed and used to detect, identify, and notify concerned parties regarding vehicles that exceed emissions standards.
Emissions Management 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 in CVRIA) 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.
Enforcement Center The 'Enforcement Center' represents the systems that receive reports of violations detected by various ITS facilities including individual vehicle emissions, lane violations, toll violations, CVO violations, etc.
Field Component Development System The system used in a backoffice environment to develop and test the field component of the application.
Field Component Installation System The system used to install a field component of a connected vehicle application.
Field Component Maintenance System The system used to install and configure changes and updates to the field component of the application. This system is capable of acquiring and reporting diagnostic information about the application's configuration and performance.
ITS Certification Requirements The requirements that define the functionality, performance and operational environment of an ITS device or ITS application. Applicability varies with jurisdictions, but typically devices and applications must meet pre-defined acceptance criteria prior to usage in the transportation environment.
ITS Field Component Development System The system used in a backoffice environment to develop and test the ITS field component of the application.
ITS Field Component Installation System The system used to install a field component of a connected vehicle application.
ITS Field Component Maintenance System The system used to install and configure changes and updates to the ITS field component of the application. This system is capable of acquiring and reporting diagnostic information about the application's configuration and performance.
ITS Roadway Equipment 'ITS Roadway Equipment' represents the ITS equipment that is distributed on and along the roadway that monitors and controls traffic and monitors and manages the roadway itself. In CVRIA, this physical object represents all of the other ITS field equipment that interfaces with and supports the Connected Vehicle Roadside Equipment (RSE). This physical object includes traffic detectors, environmental sensors, traffic signals, highway advisory radios, dynamic message signs, CCTV cameras and video image processing systems, grade crossing warning systems, and ramp metering systems. Lane management systems and barrier systems that control access to transportation infrastructure such as roadways, bridges and tunnels are also included. This object also provides environmental monitoring including sensors that measure road conditions, surface weather, and vehicle emissions. Work zone systems including work zone surveillance, traffic control, driver warning, and work crew safety systems are also included.
Mobile Component Development System The system used in a backoffice environment to develop and test the mobile component of the application.
Mobile Component Installation System The system that interacts with the Vehicle OBE other mobile device and installs the mobile component of the application.
Mobile Component Maintenance System The system used to configure changes and updates to the mobile component of the application. This system is capable of acquiring and reporting diagnostic information about the application's configuration and performance.
Other Traffic Management Centers Representing another Traffic Management Center, 'Other Traffic Management Centers' is intended to provide a source and destination for information exchange between peer (e.g. inter-regional) traffic management functions. It enables traffic management activities to be coordinated across different jurisdictional areas.
Roadside Equipment 'Roadside Equipment' (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.
Roadway Basic Surveillance "Roadway Basic Surveillance" monitors traffic conditions using fixed equipment such as loop detectors and CCTV cameras.
Roadway Dynamic Lane Management and Shoulder Use "Roadway Dynamic Lane Management and Shoulder Use" includes the field equipment, physical overhead lane signs and associated control electronics that are used to manage and control specific lanes and/or the shoulders. This equipment can be centrally controlled by a traffic management center or it can be autonomous and monitor traffic conditions and demand along the roadway and determine how to change the lane controls to respond to current conditions. Lane controls can be used to change the lane configuration of the roadway, reconfigure intersections and/or interchanges, allow use of shoulders as temporary travel lanes, designate lanes for use by special vehicles only, such as buses, high occupancy vehicles (HOVs), vehicles attending a special event, etc. and/or prohibit or restrict types of vehicles from using particular lanes. Guidance and information for drivers can be posted on dynamic message signs.
Roadway Emissions Monitoring "Roadway Emissions Monitoring" monitors emissions and general air quality and communicates the collected information back to the emissions management center where it can be monitored, analyzed, and used. This application object supports point monitoring of individual vehicle emissions as well as general monitoring of standard air quality measures.
Roadway Traffic Information Dissemination "Roadway Traffic Information Dissemination" includes field elements that provide information to drivers, including dynamic message signs and highway advisory radios.
RSE Development System The system used in a backoffice environment to develop and test the roadside equipment.
RSE Environmental Monitoring "RSE Environmental Monitoring" collects environmental situation (probe) data from passing vehicles that are equipped with short range communications capability. The collected data includes current environmental conditions as measured by on-board sensors (e.g., ambient temperature and precipitation measures), current status of vehicle systems that can be used to infer environmental conditions (e.g., status of lights, wipers, ABS, and traction control systems), and emissions measures reported by the vehicle. The application object collects the provided data, aggregates and filters the data based on provided configuration parameters, and sends the collected information back to a center for processing and distribution. This application object may also process the collected data locally and issue short-term road weather advisories for the road segment using short range communications.
RSE Installation System The system used to install and configure the roadside equipment.
RSE Maintenance System The system used to configure changes and updates to the roadside equipment. This system is capable of acquiring and reporting diagnostic information about the RSE's configuration and performance.
RSE Restricted Lanes Application The "RSE Restricted Lanes Application" uses short range communications to monitor and manage dynamic and static restricted lanes. It collects vehicle profile information from vehicles entering the lanes and monitors vehicles within the lanes, providing aggregate data to the back office center. It provides lane restriction information and signage data to the vehicles and optionally identifies vehicles that violate the current lane restrictions. These functions are performed based on operating parameters provided by the back office managing center(s).
RSE Traffic Monitoring "RSE Traffic Monitoring" monitors the basic safety messages that are shared between connected vehicles and distills this data into traffic flow measures that can be used to manage the network in combination with or in lieu of traffic data collected by infrastructure-based sensors. As connected vehicle penetration rates increase, the measures provided by this application can expand beyond vehicle speeds that are directly reported by vehicles to include estimated volume, occupancy, and other measures. This object also supports incident detection by monitoring for changes in speed and vehicle control events that indicate a potential incident.
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.
TMC Dynamic Lane Management and Shoulder Use "TMC Dynamic Lane Management and Shoulder Use" remotely monitors and controls the system that is used to dynamically manage travel lanes, including temporary use of shoulders as travel lanes. It monitors traffic conditions and demand measured in the field and determines when the lane configuration of the roadway should be changed, when intersections and/or interchanges should be reconfigured, when the shoulders should be used for travel (as a lane), when lanes should be designated for use by special vehicles only, such as buses, high occupancy vehicles (HOVs), vehicles attending a special event, etc. and/or when types of vehicles should be prohibited or restricted from using particular lanes. It controls the field equipment used to manage and control specific lanes and the shoulders. It also can automatically notify the enforcement agency of lane control violations.
TMC In-Vehicle Signing Management "TMC In-Vehicle Signing Management" controls and monitors RSEs that support in-vehicle signing. Sign information that may include static regulatory, service, and directional sign information as well as variable information such as traffic and road conditions can be provided to the RSE, which uses short range communications to send the information to in-vehicle equipment. Information that is currently being communicated to passing vehicles and the operational status of the field equipment is monitored by this application. The operational status of the field equipment is reported to operations personnel.
TMC Regional Traffic Management "TMC Regional Traffic Management" supports coordination between traffic management centers in order to share traffic information between centers as well as control of traffic management field equipment. This coordination supports wide area optimization and regional coordination that spans jurisdictional boundaries; for example, coordinated signal control in a metropolitan area or coordination between freeway operations and arterial signal control within a corridor.
TMC Restricted Lanes CV Application "TMC Restricted Lanes CV Application" manages dynamic lanes for connected vehicles. The application provides the back office functions and supports the TMC operator in establishing and managing dynamic lanes using communications to manage lane use for connected vehicles.
TMC Traffic Information Dissemination "TMC Traffic Information Dissemination" disseminates traffic and road conditions, closure and detour information, incident information, driver advisories, and other traffic-related data to other centers, the media, and driver information systems. It monitors and controls driver information system field equipment including dynamic message signs and highway advisory radio, managing dissemination of driver information through these systems.
TMC Traffic Surveillance "TMC Traffic Surveillance" remotely monitors and controls traffic sensors and surveillance (e.g., CCTV) equipment, and collects, processes and stores the collected traffic data. Current traffic information and other real-time transportation information is also collected from other centers. The collected information is provided to traffic operations personnel and made available to other centers.
Traffic Management 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 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 allow for communication between transit departments and with other operating entities such as emergency response services and traffic management systems.
Transportation Information 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.
Vehicle The conveyance that provides the sensory, processing, storage, and communications functions necessary to support efficient, safe, and convenient travel. These functions reside in general vehicles including personal automobiles, commercial vehicles, emergency vehicles, transit vehicles, or other vehicle types.
Vehicle Basic Safety "Vehicle Basic Safety" exchanges current vehicle location and motion information with other vehicles in the vicinity, uses that information to calculate vehicle paths, and warns the driver when the potential for an impending collision is detected. If available, map data is used to filter and interpret the relative location and motion of vehicles in the vicinity. Information from on-board sensors (e.g., radars and image processing) are also used, if available, in combination with the V2V communications to detect non-equipped vehicles and corroborate connected vehicle data. Vehicle location and motion broadcasts are also received by the infrastructure and used by the infrastructure to support a wide range of roadside safety and mobility applications. This object represents a broad range of implementations ranging from basic Vehicle Awareness Devices that only broadcast vehicle location and motion and provide no driver warnings to advanced integrated safety systems that may, in addition to warning the driver, provide collision warning information to support automated control functions that can support control intervention.
Vehicle Databus The 'Vehicle Databus' represents the interface to the vehicle databus (e.g., CAN, LIN, Ethernet/IP, FlexRay, and MOST) that may enable communication between the Vehicle OBE and other vehicle systems to support connected vehicle applications. The vehicle system statuses and/or sensor outputs available on the databus will vary based on the equipment installed on the vehicle and availability on databus. System statuses and sensor outputs may include select vehicle systems and sensors such as accelerometers, yaw rate sensors, and GPS derived location and timing information. In CVRIA, this physical object is used to represent the onboard interactions between the Vehicle OBE and the other systems included in a host vehicle.

Note that the vehicle databus interface is not standardized across all vehicle classes. Also, some Vehicle OBE implementations will not have access to the vehicle databus. See 'Vehicle OBE' for more information.
Vehicle Emissions Monitoring "Vehicle Emissions Monitoring" directly measures or estimates current and average vehicle emissions and makes this data available to the driver and connected vehicle infrastructure systems.
Vehicle OBE The Vehicle On-Board Equipment (OBE) provides the vehicle-based processing, storage, and communications functions necessary to support connected vehicle operations. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle OBE. This communication platform is augmented with processing and data storage capability that supports the connected vehicle applications.

In CVRIA, the Vehicle OBE includes the functions and interfaces that support connected vehicle applications for passenger cars, trucks, and motorcycles. Many of these applications (e.g., V2V Safety applications) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle OBE includes the common interfaces and functions that apply to all motorized vehicles.
Vehicle Restricted Lanes Application The "Vehicle Restricted Lanes Application" monitors and reports its own operating parameters and communicates with roadside equipment to safely enter, operate within, and exit eco-lanes and other controlled-access lanes.
Vehicle Roadside Information Reception "Vehicle Roadside Information Reception" receives advisories, vehicle signage data, and other driver information 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.

Includes Roles:

Role Description
Certifies An Enterprise verifies that a target Resource meets relevant performance, functional, environmental and quality requirements.
Constrains A Resource or Enterprise applies requirements, constraints and associated tests to another Resource.
Develops An Enterprise creates the target Resource or Document.
Installs An Enterprise performs the initial delivery, integration and configuration of the target Resource.
Maintains An Enterprise administers the hardware and software that comprise the target Resource.
Member An Enterprise is part of another larger, target Enterprise.
Operates An Enterprise controls the functionality and state of the target Resource. An Enterprise that Operates a resource is considered Responsible.
Owns An Enterprise has financial ownership and control over the Resource. An Enterprise that Owns a resource is considered Accountable.

Includes Coordination:

Coordination Type Description
Application Installation Data Information Sharing Data needed to install the application, including the application executable code and any configuration data. Unidirectional flow.
Application Interface Specification Agreement The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Application Maintenance Data Information Sharing Data used to facilitate the upgrade, patching and general health maintenance of an application component.
Application Performance Data Information Sharing Data used to characterize application performance, including such measures as availability, known errors and known uses.
Application Procurement Agreement Agreement An agreement whereupon one entity provides a copy of an application component to another entity. This component is capable of being installed and functioning, according to its requirements that passed through the application's certification process.
Application Usage Agreement Agreement An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Backoffice Component Installation Agreement Agreement An agreement that grants one party permission to install a backoffice application component on a center-based device controlled by the other party.
Backoffice Component Maintenance Agreement Agreement An agreement in which one entity maintains the operational status of the backoffice component of an application under the control of another entity. This maintenance may include routine and as-needed maintenance, such as software update and configuration, hardware replacement and related system administration activities.
Device Placement and Operations Agreement Agreement An agreement that enables the controller of a physical device to install it (so as to make it operational) at a fixed location controlled by another entity.
Employment Agreement Agreement An agreement between an individual and a corporation or government entity, whereupon the individual agrees to provide labor to the corporation/agency, which in turn compensates the employee. Stipulates level of compensation, working conditions, necessary equipment and training and expectations of employee performance.
Expectation of Data Provision Expectation An expectation where one party believes another party will provide data on a regular and recurring basis, and that that data will be useful to the receiver in the context of the receiver's application. This thus includes some expectation of data fields, timeliness, quality, precision and similar qualities of data.
Expectation of Information Provision Expectation An expectation where one party believes another party will provide it information whenever such information is likely relevant to the recipient.
Field Component Installation Agreement Agreement An agreement that grants one party permission to install a field application component on a roadside device controlled by the other party.
Field Component Maintenance Agreement Agreement An agreement in which one entity maintains the operational status of the field component of an application under the control of another entity. This maintenance may include routine and as-needed maintenance, such as software update and configuration, hardware replacement and related system administration activities.
Includes Includes Indicates that one component is entirely contained within another component.
Information Exchange Agreement Agreement An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Information Provision Agreement Agreement An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Installation Agreement Agreement An agreement whereupon one entity installs an application component on a device controlled by another entity.
Interface Description Agreement Documentation of the interface between two systems, where one system does not have an application component that is part of the application, but does provide and/or receive data and/or information that is used by or sourced from the application. In many cases this is an existing interface used by the application, so the description of the interface already exists and is imposed by the terminator.
Maintenance Agreement Agreement An agreement in which one entity maintains the operational status of a system under the control of another entity. This maintenance may include routine and as-needed maintenance, such as software update and configuration, hardware replacement and related system administration activities.
Maintenance Data Exchange Agreement Agreement An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Mobile Component Installation Agreement Agreement An agreement whereupon the controller of OBE gives another party permission to install, configure and make operational a component that enables the mobile portion of an application.
Mobile Component License Agreement Agreement An end-user license agreement allowing the operator of the mobile device to use the mobile application component that is part of the application in question.
Mobile Component Maintenance Agreement Agreement An agreement in which one entity maintains the operational status of the mobile component of an application under the control of another entity. This maintenance may include routine and as-needed maintenance, such as software update and configuration, hardware replacement and related system administration activities.
Operations Agreement Agreement An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
RSE Deployment Agreement Agreement Agreement to install, configure and make operational roadside equipment, between the provider of that equipment and the entity that controls access to the roadside. May define locations, expectation of power provision, backhaul responsibility and installation restrictions.
RSE Installation Data Information Sharing Data necessary to configure and make RSE operational. Uni-directional.
RSE Maintenance Data Information Sharing Data necessary to modify the operational configuration of RSE; assumes RSE is already configured. Uni-directional.
RSE Performance Data Information Sharing Data that includes metrics of RSE performance. Could include fields such as uptime, packets received/transmitted, distance vector from which packets received, as well as application-specific performance measures.
RSE Procurement Agreement Agreement An agreement whereupon one entity provides roadside equipment to another entity. The RSE is capable of being installed and functioning, according to its requirements that passed through the device's certification process.
Service Delivery Agreement Agreement A relationship where one party agrees to provide a service to the other party. This agreement may specify the expected performance of this service in terms of availability and/or actions/time-type performance specifications.
Traffic Management Agreement Agreement An agreement that stipulates how and under what conditions one entity will use its assets to inform and control traffic flow, under the guidance and/or direction of the other entity.
Vehicle Data Access Agreement Agreement An agreement whereby the party that controls access to on-board vehicle data grants another party the right and ability to access that data. Includes the conditions under which data may be accessed, and specifies the mechanisms, including physical and functional access methods, data formats and any other considerations necessary for the accessing party to acquire data. May also include caveats regarding responsibility for data quality and responsibility for use of the data.
Vehicle OBE Usage Agreement Agreement An agreement that grants one entity permission to use a Vehicle OBE that the other party controls.
Vehicle Procurement Agreement Agreement The exchange of a vehicle for compensation. One entity purchases the vehicle from the other.
Vehicle Usage Agreement Agreement An agreement between the owner of a vehicle and a prospective operator, whereupon the owner allows the operator to use the vehicle.
Warranty Agreement A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance over time of an application component.

Functional

Includes Processes:

Level Name Type Allocated to Application Object
1.1 Provide Traffic Surveillance Collection
1.1.1 Process Sensor Data Collection
1.1.1.1 Process Traffic Sensor Data Pspec - Roadway Basic Surveillance
1.1.1.6 Collect Vehicle Roadside Safety Data Pspec - RSE Traveler Information Communications
- RSE Restricted Lanes Application
- RSE Environmental Monitoring
1.1.2 Process and Store Traffic Data Collection
1.1.2.1 Process Traffic Data for Storage Pspec - TMC Traffic Surveillance
1.1.2.2 Process Traffic Data Pspec - TMC Traffic Surveillance
1.1.2.6 Process Collected Vehicle Safety Data Pspec - RSE Traveler Information Communications
- RSE Restricted Lanes Application
- RSE Environmental Monitoring
- RSE Traffic Monitoring
1.1.2.9 Monitor Dynamic Lanes Pspec - TMC Traffic Surveillance
- TMC Dynamic Lane Management and Shoulder Use
- TMC Restricted Lanes CV Application
1.1.2.10 Provide Dynamic Lane Management Pspec - TMC Traffic Information Dissemination
- TMC Dynamic Lane Management and Shoulder Use
- TMC Restricted Lanes CV Application
1.1.2.11 Control Dynamic Lanes Pspec - Roadway Basic Surveillance
- Roadway Dynamic Lane Management and Shoulder Use
1.1.3 Generate Predictive Traffic Model Pspec - TMC Traffic Surveillance
- TMC Regional Traffic Management
1.1.4 Display and Output Traffic Data Collection
1.1.4.1 Retrieve Traffic Data Pspec - TMC Traffic Information Dissemination
- TMC Traffic Surveillance
- TMC Dynamic Lane Management and Shoulder Use
- TMC Regional Traffic Management
1.1.4.2 Provide Traffic Operations Personnel Traffic Data Interface Pspec - TMC Traffic Information Dissemination
- TMC Traffic Surveillance
- TMC Dynamic Lane Management and Shoulder Use
- TMC Restricted Lanes CV Application
1.1.4.4 Update Traffic Display Map Data Pspec - TMC Traffic Surveillance
1.1.5 Exchange Data with Other Traffic Centers Pspec - TMC Traffic Surveillance
- TMC Regional Traffic Management
1.1.6 Collect Vehicle Traffic Surveillance Data Pspec - RSE Restricted Lanes Application
- RSE Environmental Monitoring
- RSE Traffic Monitoring
1.1.7 Collect Vehicle Environmental Data Pspec - RSE Restricted Lanes Application
- RSE Environmental Monitoring
- RSE Traffic Monitoring
1.2 Provide Device Control Collection
1.2.1 Select Strategy Pspec - TMC Traffic Information Dissemination
- TMC Traffic Surveillance
- TMC Restricted Lanes CV Application
1.2.4 Output Control Data Collection
1.2.4.1 Output Control Data for Roads Pspec - TMC Restricted Lanes CV Application
1.2.4.2 Output Control Data for Freeways Pspec
1.2.4.4 Output Roadway Information Data Pspec - TMC Traffic Information Dissemination
- TMC In-Vehicle Signing Management
1.2.7 Provide Roadside Control Facilities Collection
1.2.7.1 Process Indicator Output Data for Roads Pspec - Roadway Traffic Information Dissemination
1.2.7.4 Process In-vehicle Signage Data Pspec - RSE Traveler Information Communications
- RSE Restricted Lanes Application
- RSE Environmental Monitoring
- RSE Traffic Monitoring
1.2.7.5 Process Indicator Output Data for Freeways Pspec - Roadway Traffic Information Dissemination
- Roadway Dynamic Lane Management and Shoulder Use
1.2.7.7 Process Vehicle Safety and Environmental Data for Output Pspec - RSE Traveler Information Communications
- RSE Restricted Lanes Application
- RSE Environmental Monitoring
1.2.7.8 Provide Device Interface to Other Roadway Devices Pspec - Roadway Traffic Information Dissemination
- Roadway Basic Surveillance
- Roadway Dynamic Lane Management and Shoulder Use
- Roadway Emissions Monitoring
1.2.7.9 Process Roadway Information Data Pspec - Roadway Traffic Information Dissemination
- Roadway Dynamic Lane Management and Shoulder Use
1.2.8 Collect Traffic Field Equipment Fault Data Pspec - TMC Traffic Information Dissemination
- TMC Traffic Surveillance
- TMC In-Vehicle Signing Management
1.3 Manage Incidents Collection
1.3.1 Traffic Data Analysis for Incidents Collection
1.3.1.3 Process Traffic Images Pspec - Roadway Basic Surveillance
1.3.2 Review and Manage Incident Data Collection
1.3.2.1 Store Possible Incident Data Pspec - TMC Traffic Information Dissemination
- TMC Traffic Surveillance
- TMC Dynamic Lane Management and Shoulder Use
- TMC Restricted Lanes CV Application
- TMC In-Vehicle Signing Management
1.3.2.6 Manage Traffic Routing Pspec - TMC Traffic Surveillance
- TMC Regional Traffic Management
1.3.4 Provide Operator Interfaces for Incidents Collection
1.3.4.2 Provide Traffic Operations Personnel Incident Data Interface Pspec - TMC Traffic Information Dissemination
- TMC Traffic Surveillance
- TMC Dynamic Lane Management and Shoulder Use
- TMC Restricted Lanes CV Application
1.3.4.6 Process Video Data Pspec - TMC Traffic Information Dissemination
- TMC Traffic Surveillance
1.4 Manage Travel Demand Collection
1.4.1 Provide Traffic Operations Personnel Demand Interface Pspec - TMC Traffic Information Dissemination
- TMC Traffic Surveillance
- TMC Dynamic Lane Management and Shoulder Use
1.4.2 Collect Demand Forecast Data Pspec - TMC Traffic Information Dissemination
- TMC Traffic Surveillance
- TMC Restricted Lanes CV Application
- TMC Regional Traffic Management
1.4.4 Implement Demand Management Policy Pspec - TMC Traffic Information Dissemination
- TMC Restricted Lanes CV Application
1.5 Manage Emissions Collection
1.5.1 Provide Emissions Operations Personnel Interface Pspec - Emissions Data Management
- Emissions Connected Vehicle Monitoring
1.5.2 Process Pollution Data Pspec - Emissions Data Management
- Emissions Connected Vehicle Monitoring
1.5.3 Update Pollution Display Map Data Pspec - Emissions Data Management
- Emissions Connected Vehicle Monitoring
1.5.4 Manage Pollution State Data Store Pspec - Emissions Data Management
- Emissions Connected Vehicle Monitoring
1.5.5 Detect Vehicle Emissions Levels Pspec - Roadway Traffic Information Dissemination
- Roadway Emissions Monitoring
1.5.6 Detect Pollution Levels Pspec - Roadway Emissions Monitoring
1.5.7 Process Vehicle Emissions Data Pspec - Emissions Data Management
1.5.8 Manage Emissions and Pollution Reference Data Stores Pspec - Emissions Data Management
- Emissions Connected Vehicle Monitoring
1.5.10 Manage Emissions State Data Store Pspec - Emissions Data Management
- Emissions Connected Vehicle Monitoring
1.5.11 Collect Vehicle Emissions Messages Pspec - RSE Traveler Information Communications
- RSE Restricted Lanes Application
- RSE Environmental Monitoring
1.5.12 Process Connected Vehicle Emissions Data Pspec - Emissions Data Management
- Emissions Connected Vehicle Monitoring
1.5.13 Manage Eco Roadway Usage in Roadway Pspec - RSE Restricted Lanes Application
- RSE Environmental Monitoring
3.1 Monitor Vehicle Status Collection
3.1.3 Process Vehicle On-board Data Pspec - Vehicle Roadside Information Reception
- Vehicle Restricted Lanes Application
- Vehicle Basic Safety
- Vehicle Emissions Monitoring
3.1.7 Process Vehicle Emissions Status Pspec - Vehicle Emissions Monitoring
5.4 Provide Law Enforcement Allocation Collection
5.4.8 Process Emissions Violations Pspec - Emissions Data Management
- Emissions Connected Vehicle Monitoring
5.4.9 Process Roadside Emissions Violations Pspec - RSE Restricted Lanes Application
6.7 Provide Driver Personal Services Collection
6.7.3 Provide Traveler Services in Vehicle Collection
6.7.3.1 Get Driver Personal Request Pspec - Vehicle Roadside Information Reception
6.7.3.2 Provide Driver with Personal Travel Information Pspec - Vehicle Roadside Information Reception
- Vehicle Restricted Lanes Application
6.7.3.3 Provide Driver Information Interface Pspec - Vehicle Roadside Information Reception
- Vehicle Restricted Lanes Application
- Vehicle Basic Safety
7.6.1 Process VMT Payment Collection
7.6.1.1 Collect Road Use Charging Data Pspec - RSE Restricted Lanes Application
7.6.1.3 Bill Driver for Road Use Charges Pspec
7.6.3 Provide Driver Road Use Charging Payment Interface Pspec
7.6.4 Provide Payment Device Interface for Road Use Charging Pspec

Includes Data Flows:

Source Pspec Data Flow Destination Pspec
Bill Driver for Road Use Charges road_use_cost_data_from_roadside Provide Driver Road Use Charging Payment Interface
Bill Driver for Road Use Charges road_use_payment_request Provide Payment Device Interface for Road Use Charging
Bill Driver for Road Use Charges road_use_vehicle_payment_data_clear Provide Payment Device Interface for Road Use Charging
Collect Demand Forecast Data pollution_state_data_request Manage Pollution State Data Store
Collect Demand Forecast Data weather_service_information Provide Traffic Operations Personnel Traffic Data Interface
Collect Demand Forecast Data traffic_data_demand_request Retrieve Traffic Data
Collect Road Use Charging Data road_use_payment_movement_data Control Dynamic Lanes
Collect Traffic Field Equipment Fault Data indicator_fault_state Select Strategy
Collect Vehicle Emissions Messages vehicle_emissions_collection_data Manage Eco Roadway Usage in Roadway
Collect Vehicle Emissions Messages vehicle_emissions_data_for_monitoring Process Connected Vehicle Emissions Data
Collect Vehicle Emissions Messages emissions_violation_for_enforcement Process Roadside Emissions Violations
Collect Vehicle Emissions Messages vehicle_signage_emissions_testing_results Provide Driver with Personal Travel Information
Collect Vehicle Environmental Data vehicle_env_sensor_status_for_traffic Collect Traffic Field Equipment Fault Data
Collect Vehicle Environmental Data vehicle_env_probe_input_data Process Collected Vehicle Safety Data
Collect Vehicle Roadside Safety Data vehicle_safety_input_data Process Collected Vehicle Safety Data
Collect Vehicle Traffic Surveillance Data vehicle_traffic_roadside_equip_status Collect Traffic Field Equipment Fault Data
Collect Vehicle Traffic Surveillance Data vehicle_situation_data_raw Process Collected Vehicle Safety Data
Collect Vehicle Traffic Surveillance Data vehicle_traffic_situation_data_configuration Process Vehicle On-board Data
Control Dynamic Lanes shoulder_management_device_status Collect Traffic Field Equipment Fault Data
Control Dynamic Lanes lane_management_device_status Collect Traffic Field Equipment Fault Data
Control Dynamic Lanes lane_violation_notification_for_traffic Monitor Dynamic Lanes
Control Dynamic Lanes shoulder_violation_notification_for_traffic Monitor Dynamic Lanes
Control Dynamic Lanes dynamic_lane_assignment_message Process In-vehicle Signage Data
Control Dynamic Lanes shoulder_management_status Provide Dynamic Lane Management
Control Dynamic Lanes lane_management_status Provide Dynamic Lane Management
Detect Pollution Levels pollution_sensor_data Process Pollution Data
Detect Pollution Levels pollution_sensor_status Process Pollution Data
Detect Vehicle Emissions Levels vehicle_emissions_alert Process Emissions Violations
Detect Vehicle Emissions Levels individual_vehicle_emissions_for_signage Process In-vehicle Signage Data
Detect Vehicle Emissions Levels emissions_zone_message_from_roadway Process In-vehicle Signage Data
Detect Vehicle Emissions Levels individual_vehicle_emissions_for_display Process Roadway Information Data
Detect Vehicle Emissions Levels vehicle_emissions_sensor_data Process Vehicle Emissions Data
Detect Vehicle Emissions Levels vehicle_emissions_sensor_status Process Vehicle Emissions Data
Detect Vehicle Emissions Levels vehicle_emissions_message Provide Device Interface to Other Roadway Devices
Exchange Data with Other Traffic Centers other_traffic_center_data Generate Predictive Traffic Model
Exchange Data with Other Traffic Centers traffic_detour_control_from_other_traffic Manage Traffic Routing
Exchange Data with Other Traffic Centers traffic_detour_info_from_other_traffic Manage Traffic Routing
Exchange Data with Other Traffic Centers other_control_data_for_highways Output Control Data for Freeways
Exchange Data with Other Traffic Centers status_data_for_highways Output Control Data for Freeways
Exchange Data with Other Traffic Centers other_control_data_for_roads Output Control Data for Roads
Exchange Data with Other Traffic Centers status_data_for_roads Output Control Data for Roads
Exchange Data with Other Traffic Centers other_roadway_information_data Output Roadway Information Data
Exchange Data with Other Traffic Centers roadway_information_status Output Roadway Information Data
Exchange Data with Other Traffic Centers video_image_control_from_other_center Process Video Data
Exchange Data with Other Traffic Centers video_device_status_from_other_center Process Video Data
Exchange Data with Other Traffic Centers dynamic_lane_mgmt_control_from_other_traffic Provide Dynamic Lane Management
Exchange Data with Other Traffic Centers device_control_request_from_other_center Provide Traffic Operations Personnel Traffic Data Interface
Exchange Data with Other Traffic Centers other_TMC_cv_incidents Select Strategy
Exchange Data with Other Traffic Centers other_TMC_emergency_data Select Strategy
Exchange Data with Other Traffic Centers other_TMC_strategy_data Select Strategy
Generate Predictive Traffic Model unusual_congestion Collect Demand Forecast Data
Get Driver Personal Request vehicle_information_request_for_response Provide Driver with Personal Travel Information
Implement Demand Management Policy vehicle_parameters_for_roadway_usage Manage Eco Roadway Usage in Roadway
Implement Demand Management Policy emissions_zone_coordination_from_traffic Provide Emissions Operations Personnel Interface
Implement Demand Management Policy demand_management_result Provide Traffic Operations Personnel Demand Interface
Implement Demand Management Policy demand_overrides Select Strategy
Manage Eco Roadway Usage in Roadway vehicle_characteristics_for_collection Collect Vehicle Emissions Messages
Manage Eco Roadway Usage in Roadway eco_roadway_usage_status Control Dynamic Lanes
Manage Eco Roadway Usage in Roadway vehicle_emissions_characteristics_data Process Connected Vehicle Emissions Data
Manage Eco Roadway Usage in Roadway eco_roadway_configuration_information Provide Driver with Personal Travel Information
Manage Eco Roadway Usage in Roadway emissions_zone_parameters_for_driver Provide Driver with Personal Travel Information
Manage Eco Roadway Usage in Roadway emissions_zone_status Provide Emissions Operations Personnel Interface
Manage Emissions and Pollution Reference Data Stores roadside_emissions_state_acceptance_criteria Process Connected Vehicle Emissions Data
Manage Emissions and Pollution Reference Data Stores pollution_state_static_acceptance_criteria Process Pollution Data
Manage Emissions and Pollution Reference Data Stores vehicle_emissions_state_acceptance_criteria Process Vehicle Emissions Data
Manage Emissions and Pollution Reference Data Stores emissions_reference_data_output Provide Emissions Operations Personnel Interface
Manage Emissions and Pollution Reference Data Stores pollution_reference_data_output Provide Emissions Operations Personnel Interface
Manage Emissions State Data Store emissions_state_data_for_pollution_processing Process Pollution Data
Manage Emissions State Data Store emissions_state_data_output Provide Emissions Operations Personnel Interface
Manage Pollution State Data Store pollution_state_data Collect Demand Forecast Data
Manage Pollution State Data Store pollution_state_data_output Provide Emissions Operations Personnel Interface
Manage Traffic Routing traffic_detour_control_for_other_traffic Exchange Data with Other Traffic Centers
Manage Traffic Routing traffic_detour_info_for_other_traffic Exchange Data with Other Traffic Centers
Manage Traffic Routing freeway_control_request_for_detours Output Control Data for Freeways
Manage Traffic Routing roadway_control_request_for_detours Output Control Data for Roads
Manage Traffic Routing roadway_detours_and_closures_for_traffic Retrieve Traffic Data
Monitor Dynamic Lanes dynamic_lane_data Process Traffic Data
Output Control Data for Freeways indicator_status_for_highways_from_center Collect Traffic Field Equipment Fault Data
Output Control Data for Freeways control_data_for_highways Exchange Data with Other Traffic Centers
Output Control Data for Freeways other_status_for_highways Exchange Data with Other Traffic Centers
Output Control Data for Freeways freeway_control_response_for_detours Manage Traffic Routing
Output Control Data for Freeways reversible_lane_control_for_highways Process Indicator Output Data for Freeways
Output Control Data for Freeways indicator_control_data_for_traffic_metering Process Indicator Output Data for Freeways
Output Control Data for Freeways ramp_meter_data_for_signage Process In-vehicle Signage Data
Output Control Data for Freeways indicator_control_storage_data_for_highways Process Traffic Data for Storage
Output Control Data for Freeways indicator_input_storage_data_for_highways Process Traffic Data for Storage
Output Control Data for Freeways indicator_input_state_for_highways Select Strategy
Output Control Data for Roads indicator_status_for_roads_from_center Collect Traffic Field Equipment Fault Data
Output Control Data for Roads control_data_for_roads Exchange Data with Other Traffic Centers
Output Control Data for Roads other_status_for_roads Exchange Data with Other Traffic Centers
Output Control Data for Roads roadway_control_response_for_detours Manage Traffic Routing
Output Control Data for Roads reversible_lane_control_for_roads Process Indicator Output Data for Roads
Output Control Data for Roads indicator_control_data_for_signal_control Process Indicator Output Data for Roads
Output Control Data for Roads indicator_control_storage_data_for_roads Process Traffic Data for Storage
Output Control Data for Roads indicator_input_storage_data_for_roads Process Traffic Data for Storage
Output Control Data for Roads indicator_input_state_for_roads Select Strategy
Output Roadway Information Data other_roadway_information_status Exchange Data with Other Traffic Centers
Output Roadway Information Data roadway_information_data Exchange Data with Other Traffic Centers
Output Roadway Information Data dms_control_data Process Roadway Information Data
Output Roadway Information Data dms_wide_area_alert_information Process Roadway Information Data
Output Roadway Information Data har_wide_area_alert_information Process Roadway Information Data
Output Roadway Information Data dms_traffic_metering_data Process Roadway Information Data
Output Roadway Information Data dms_variable_speed_limit_data Process Roadway Information Data
Output Roadway Information Data dms_data Process Roadway Information Data
Output Roadway Information Data har_data Process Roadway Information Data
Output Roadway Information Data current_dms_data_displayed Process Traffic Data for Storage
Output Roadway Information Data roadway_info_operator_status Provide Traffic Operations Personnel Traffic Data Interface
Process Collected Vehicle Safety Data vehicle_traffic_data_for_lanes Control Dynamic Lanes
Process Collected Vehicle Safety Data vehicle_traffic_data_for_freeways Process Indicator Output Data for Freeways
Process Collected Vehicle Safety Data vehicle_traffic_data_for_roads Process Indicator Output Data for Roads
Process Collected Vehicle Safety Data vehicle_safety_data_indication Process Vehicle Safety and Environmental Data for Output
Process Collected Vehicle Safety Data roadway_geometry_location_data Process Vehicle Safety and Environmental Data for Output
Process Collected Vehicle Safety Data roadway_intersection_geometry_data Process Vehicle Safety and Environmental Data for Output
Process Connected Vehicle Emissions Data vehicle_emissions_roadside_collection_control Collect Vehicle Emissions Messages
Process Connected Vehicle Emissions Data vehicle_types_parameters Manage Eco Roadway Usage in Roadway
Process Connected Vehicle Emissions Data roadside_emissions_messages_state_collection Manage Emissions State Data Store
Process Connected Vehicle Emissions Data emissions_zone_operation_status_for_traffic Provide Dynamic Lane Management
Process Connected Vehicle Emissions Data roadside_emissions_data_collection_operator_status Provide Emissions Operations Personnel Interface
Process Connected Vehicle Emissions Data roadside_emissions_data_for_traffic Select Strategy
Process Indicator Output Data for Freeways reversible_lane_control_device_status_from_highways Collect Traffic Field Equipment Fault Data
Process Indicator Output Data for Freeways indicator_input_data_from_traffic_meters Output Control Data for Freeways
Process Indicator Output Data for Freeways signage_traffic_metering_data_from_roadway Process In-vehicle Signage Data
Process Indicator Output Data for Freeways dms_traffic_metering_data_from_roadway Process Roadway Information Data
Process Indicator Output Data for Freeways traffic_metering_data_for_roadside Process Vehicle Safety and Environmental Data for Output
Process Indicator Output Data for Freeways t_other_rw_fc_control_to_traffic_sensor Provide Device Interface to Other Roadway Devices
Process Indicator Output Data for Freeways t_other_rw_fc_to_fc Provide Device Interface to Other Roadway Devices
Process Indicator Output Data for Freeways t_other_rw_dms_traffic_metering_data_from_roadway Provide Device Interface to Other Roadway Devices
Process Indicator Output Data for Freeways t_other_rw_signage_traffic_metering_data_from_roadway Provide Device Interface to Other Roadway Devices
Process Indicator Output Data for Roads reversible_lane_control_device_status_from_roads Collect Traffic Field Equipment Fault Data
Process Indicator Output Data for Roads indicator_input_data_from_signals Output Control Data for Roads
Process Indicator Output Data for Roads roadside_signal_phase_indication Process Vehicle Safety and Environmental Data for Output
Process Indicator Output Data for Roads roadside_signal_phase_timing Process Vehicle Safety and Environmental Data for Output
Process Indicator Output Data for Roads roadside_signal_phase_response_state Process Vehicle Safety and Environmental Data for Output
Process Indicator Output Data for Roads roadside_signal_priority_preempt Process Vehicle Safety and Environmental Data for Output
Process Indicator Output Data for Roads t_other_rw_ic_control_to_traffic_sensor Provide Device Interface to Other Roadway Devices
Process Indicator Output Data for Roads signal_preemption_override Select Strategy
Process Indicator Output Data for Roads signal_priority_override Select Strategy
Process In-vehicle Signage Data vehicle_sign_status Collect Traffic Field Equipment Fault Data
Process In-vehicle Signage Data speed_vehicle_sign_status Collect Traffic Field Equipment Fault Data
Process In-vehicle Signage Data infrastructure_vehicle_sign_status Collect Traffic Field Equipment Fault Data
Process In-vehicle Signage Data stop_sign_gap_sign_status Collect Traffic Field Equipment Fault Data
Process In-vehicle Signage Data vehicle_signage_hri_data Provide Driver with Personal Travel Information
Process In-vehicle Signage Data vehicle_signage_individual_vehicle_speed Provide Driver with Personal Travel Information
Process In-vehicle Signage Data vehicle_signage_roadway_warning Provide Driver with Personal Travel Information
Process In-vehicle Signage Data vehicle_signage_alert_data Provide Driver with Personal Travel Information
Process In-vehicle Signage Data vehicle_signage_evacuation_data Provide Driver with Personal Travel Information
Process In-vehicle Signage Data vehicle_signage_output_data Provide Driver with Personal Travel Information
Process In-vehicle Signage Data vehicle_signage_speed_warning Provide Driver with Personal Travel Information
Process In-vehicle Signage Data vehicle_signage_barrier_message Provide Driver with Personal Travel Information
Process In-vehicle Signage Data vehicle_signage_emissions_message Provide Driver with Personal Travel Information
Process In-vehicle Signage Data vehicle_signage_traffic_data_message Provide Driver with Personal Travel Information
Process In-vehicle Signage Data vehicle_signage_traffic_metering_message Provide Driver with Personal Travel Information
Process In-vehicle Signage Data vehicle_signage_variable_speed_limit_message Provide Driver with Personal Travel Information
Process In-vehicle Signage Data vehicle_signage_reduced_speed_message Provide Driver with Personal Travel Information
Process In-vehicle Signage Data vehicle_signage_reduced_speed_zone_definition Provide Driver with Personal Travel Information
Process In-vehicle Signage Data vehicle_signage_reduced_speed_zone_timing Provide Driver with Personal Travel Information
Process In-vehicle Signage Data vehicle_signage_road_weather_advisory Provide Driver with Personal Travel Information
Process In-vehicle Signage Data vehicle_signage_infrastructure_restriction_ahead Provide Driver with Personal Travel Information
Process In-vehicle Signage Data vehicle_signage_infrastructure_restriction_warning Provide Driver with Personal Travel Information
Process In-vehicle Signage Data vehicle_signage_pedestrian_presence Provide Driver with Personal Travel Information
Process In-vehicle Signage Data vehicle_signage_intersection_infringement Provide Driver with Personal Travel Information
Process In-vehicle Signage Data vehicle_signage_rail_crossing_warning Provide Driver with Personal Travel Information
Process In-vehicle Signage Data vehicle_signage_stop_sign_gap_assist Provide Driver with Personal Travel Information
Process In-vehicle Signage Data vehicle_signage_work_zone_intrusion Provide Driver with Personal Travel Information
Process In-vehicle Signage Data vehicle_signage_work_zone_information Provide Driver with Personal Travel Information
Process In-vehicle Signage Data vehicle_signage_intersection_message Provide Driver with Personal Travel Information
Process In-vehicle Signage Data vehicle_signage_queue_warning Provide Driver with Personal Travel Information
Process In-vehicle Signage Data vehicle_signage_incident_work_zone Provide Driver with Personal Travel Information
Process In-vehicle Signage Data vehicle_signage_dynamic_lane_configuration Provide Driver with Personal Travel Information
Process In-vehicle Signage Data vehicle_signage_lane_closure_data Provide Driver with Personal Travel Information
Process In-vehicle Signage Data vehicle_signage_road_configuration_data Provide Driver with Personal Travel Information
Process In-vehicle Signage Data vehicle_signage_road_closure_data Provide Driver with Personal Travel Information
Process In-vehicle Signage Data vehicle_signage_road_diversion_data Provide Driver with Personal Travel Information
Process Pollution Data pollution_sensor_control Detect Pollution Levels
Process Pollution Data pollution_state_static_collection Manage Pollution State Data Store
Process Pollution Data wide_area_pollution_data Process Traffic Data for Storage
Process Pollution Data pollution_sensor_status_for_operator Provide Emissions Operations Personnel Interface
Process Pollution Data pollution_incident Store Possible Incident Data
Process Roadway Information Data dms_status Collect Traffic Field Equipment Fault Data
Process Roadway Information Data har_status Collect Traffic Field Equipment Fault Data
Process Roadway Information Data dms_status Output Roadway Information Data
Process Roadway Information Data har_status Output Roadway Information Data
Process Roadway Information Data dms_status_for_roadside Process Vehicle Safety and Environmental Data for Output
Process Traffic Data traffic_sensor_output_data Process Traffic Data for Storage
Process Traffic Data processed_traffic_data Process Traffic Data for Storage
Process Traffic Data strategy_data_for_dynamic_lane_management Provide Dynamic Lane Management
Process Traffic Data for Storage current_data_for_exchange Exchange Data with Other Traffic Centers
Process Traffic Data for Storage current_data_for_output Retrieve Traffic Data
Process Traffic Images video_device_status Collect Traffic Field Equipment Fault Data
Process Traffic Images dynamic_lane_video_image Monitor Dynamic Lanes
Process Traffic Images incident_video_image Process Video Data
Process Traffic Images video_device_status Process Video Data
Process Traffic Sensor Data traffic_sensor_data_for_road_use_payment Collect Road Use Charging Data
Process Traffic Sensor Data hov_sensor_status Collect Traffic Field Equipment Fault Data
Process Traffic Sensor Data multimodal_crossing_sensor_status Collect Traffic Field Equipment Fault Data
Process Traffic Sensor Data pedestrian_sensor_status Collect Traffic Field Equipment Fault Data
Process Traffic Sensor Data reversible_lane_sensor_status Collect Traffic Field Equipment Fault Data
Process Traffic Sensor Data traffic_sensor_status Collect Traffic Field Equipment Fault Data
Process Traffic Sensor Data traffic_data_for_vehicle_sensors Collect Vehicle Roadside Safety Data
Process Traffic Sensor Data dynamic_lane_sensor_data_to_roadway Control Dynamic Lanes
Process Traffic Sensor Data dynamic_lane_sensor_data Monitor Dynamic Lanes
Process Traffic Sensor Data local_sensor_data_for_highways Process Indicator Output Data for Freeways
Process Traffic Sensor Data local_sensor_data_for_roads Process Indicator Output Data for Roads
Process Traffic Sensor Data traffic_video_image Process Traffic Data
Process Traffic Sensor Data hov_sensor_data Process Traffic Data
Process Traffic Sensor Data multimodal_crossing_sensor_data Process Traffic Data
Process Traffic Sensor Data pedestrian_sensor_data Process Traffic Data
Process Traffic Sensor Data traffic_sensor_data Process Traffic Data
Process Traffic Sensor Data vehicle_characteristics_data Process Traffic Data
Process Traffic Sensor Data traffic_video_image_for_display Provide Traffic Operations Personnel Traffic Data Interface
Process Vehicle Emissions Data vehicle_emissions_sensor_control Detect Vehicle Emissions Levels
Process Vehicle Emissions Data vehicle_emissions_state_collection Manage Emissions State Data Store
Process Vehicle Emissions Data vehicle_emissions_sensor_status_for_operator Provide Emissions Operations Personnel Interface
Process Vehicle Emissions Status vehicle_status_details_for_emissions Collect Vehicle Emissions Messages
Process Vehicle On-board Data vehicle_speed_and_distance_for_road_use_payment Collect Road Use Charging Data
Process Vehicle On-board Data vehicle_location_for_road_use_payment Collect Road Use Charging Data
Process Vehicle On-board Data vehicle_identity_for_road_use_payment Collect Road Use Charging Data
Process Vehicle On-board Data vehicle_env_sensor_data Collect Vehicle Environmental Data
Process Vehicle On-board Data vehicle_roadside_location_data Collect Vehicle Roadside Safety Data
Process Vehicle On-board Data vehicle_roadside_speed_data Collect Vehicle Roadside Safety Data
Process Vehicle On-board Data vehicle_roadside_size_data Collect Vehicle Roadside Safety Data
Process Vehicle On-board Data vehicle_roadside_current_status_data Collect Vehicle Roadside Safety Data
Process Vehicle On-board Data vehicle_traffic_situation_data Collect Vehicle Traffic Surveillance Data
Process Vehicle On-board Data vehicle_traffic_probe_data_for_archive Collect Vehicle Traffic Surveillance Data
Process Vehicle On-board Data vehicle_characteristics_for_roadside Collect Vehicle Traffic Surveillance Data
Process Vehicle On-board Data vehicle_system_characteristics_for_roadside Collect Vehicle Traffic Surveillance Data
Process Vehicle On-board Data vehicle_roadside_surveillance_status_data Collect Vehicle Traffic Surveillance Data
Process Vehicle On-board Data vehicle_roadside_surveillance_location_data Collect Vehicle Traffic Surveillance Data
Process Vehicle On-board Data vehicle_roadside_surveillance_size_data Collect Vehicle Traffic Surveillance Data
Process Vehicle On-board Data vehicle_roadside_surveillance_speed_data Collect Vehicle Traffic Surveillance Data
Process Vehicle On-board Data vehicle_system_characteristics_for_emissions Manage Eco Roadway Usage in Roadway
Process Vehicle On-board Data vehicle_characteristics_for_emissions Manage Eco Roadway Usage in Roadway
Process Vehicle On-board Data vehicle_roadside_control_event_data Process Collected Vehicle Safety Data
Process Vehicle On-board Data vehicle_occupants_detected Process Traffic Sensor Data
Process Vehicle On-board Data host_vehicle_details_for_emissions Process Vehicle Emissions Status
Process Vehicle On-board Data vehicle_status_details_for_broadcast Provide Driver with Personal Travel Information
Process Vehicle Safety and Environmental Data for Output queue_warning_system_status Collect Traffic Field Equipment Fault Data
Process Vehicle Safety and Environmental Data for Output env_sensor_data_for_advisory_message Process In-vehicle Signage Data
Process Vehicle Safety and Environmental Data for Output vehicle_safety_and_roadway_data Process In-vehicle Signage Data
Process Vehicle Safety and Environmental Data for Output dms_data_from_roadside Process Roadway Information Data
Process Vehicle Safety and Environmental Data for Output dms_transit_vehicle_movement_message_from_roadside Process Roadway Information Data
Process Vehicle Safety and Environmental Data for Output roadside_safety_data_to_vehicle Process Vehicle On-board Data
Process Vehicle Safety and Environmental Data for Output vehicle_env_sensor_data_output Provide Driver with Personal Travel Information
Process Video Data video_image_control_to_other_center Exchange Data with Other Traffic Centers
Process Video Data video_device_status_to_other_center Exchange Data with Other Traffic Centers
Process Video Data incident_video_image_control Process Traffic Images
Process Video Data incident_video_image_for_traffic_operator Provide Traffic Operations Personnel Incident Data Interface
Process Video Data video_device_status_for_traffic_operator Provide Traffic Operations Personnel Incident Data Interface
Provide Device Interface to Other Roadway Devices f_other_rw_fc_to_fc Process Indicator Output Data for Freeways
Provide Device Interface to Other Roadway Devices f_other_rw_sensor_to_fc Process Indicator Output Data for Freeways
Provide Device Interface to Other Roadway Devices f_other_ic_collision_data Process Indicator Output Data for Roads
Provide Device Interface to Other Roadway Devices f_other_rw_sensor_to_ic Process Indicator Output Data for Roads
Provide Device Interface to Other Roadway Devices f_other_rw_data_for_signage Process In-vehicle Signage Data
Provide Device Interface to Other Roadway Devices f_other_rw_roadway_info_data Process Roadway Information Data
Provide Driver Information Interface vehicle_trip_planning_requests Get Driver Personal Request
Provide Driver Information Interface vehicle_display_type Provide Driver with Personal Travel Information
Provide Driver with Personal Travel Information vehicle_advisory_information Provide Driver Information Interface
Provide Driver with Personal Travel Information vehicle_traveler_information Provide Driver Information Interface
Provide Driver with Personal Travel Information vehicle_trip_planning_responses Provide Driver Information Interface
Provide Dynamic Lane Management shoulder_management_control Control Dynamic Lanes
Provide Dynamic Lane Management lane_management_control Control Dynamic Lanes
Provide Dynamic Lane Management dynamic_lane_mgmt_control_to_other_traffic Exchange Data with Other Traffic Centers
Provide Dynamic Lane Management dynamic_lane_configuration_for_signage Process In-vehicle Signage Data
Provide Dynamic Lane Management dynamic_lane_status_to_operator Provide Traffic Operations Personnel Traffic Data Interface
Provide Emissions Operations Personnel Interface emissions_zone_coordination_for_traffic_demand Implement Demand Management Policy
Provide Emissions Operations Personnel Interface emissions_zone_application_config_for_roadside Manage Eco Roadway Usage in Roadway
Provide Emissions Operations Personnel Interface emissions_reference_data_request Manage Emissions and Pollution Reference Data Stores
Provide Emissions Operations Personnel Interface emissions_reference_data_update Manage Emissions and Pollution Reference Data Stores
Provide Emissions Operations Personnel Interface pollution_reference_data_request Manage Emissions and Pollution Reference Data Stores
Provide Emissions Operations Personnel Interface pollution_reference_data_update Manage Emissions and Pollution Reference Data Stores
Provide Emissions Operations Personnel Interface emissions_state_data_output_request Manage Emissions State Data Store
Provide Emissions Operations Personnel Interface pollution_state_data_output_request Manage Pollution State Data Store
Provide Emissions Operations Personnel Interface roadside_emissions_data_collection_parameters Process Connected Vehicle Emissions Data
Provide Emissions Operations Personnel Interface pollution_sensor_control_parameters Process Pollution Data
Provide Emissions Operations Personnel Interface vehicle_emissions_sensor_control_parameters Process Vehicle Emissions Data
Provide Emissions Operations Personnel Interface request_pollution_map_display_update Update Pollution Display Map Data
Provide Payment Device Interface for Road Use Charging road_use_payment_collected Bill Driver for Road Use Charges
Provide Payment Device Interface for Road Use Charging road_use_payment_confirmation Bill Driver for Road Use Charges
Provide Payment Device Interface for Road Use Charging driver_vmt_payment_confirmation Provide Driver Road Use Charging Payment Interface
Provide Traffic Operations Personnel Demand Interface demand_data_update_request Collect Demand Forecast Data
Provide Traffic Operations Personnel Demand Interface demand_management_activate Implement Demand Management Policy
Provide Traffic Operations Personnel Incident Data Interface roadway_info_alert_data Output Roadway Information Data
Provide Traffic Operations Personnel Incident Data Interface incident_video_image_control_by_traffic_operator Process Video Data
Provide Traffic Operations Personnel Traffic Data Interface weather_service_information_request Collect Demand Forecast Data
Provide Traffic Operations Personnel Traffic Data Interface roadside_data_collection_configuration_data Collect Vehicle Traffic Surveillance Data
Provide Traffic Operations Personnel Traffic Data Interface device_control_request_to_other_center Exchange Data with Other Traffic Centers
Provide Traffic Operations Personnel Traffic Data Interface roadway_info_operator_input Output Roadway Information Data
Provide Traffic Operations Personnel Traffic Data Interface sensor_configuration_data Process Traffic Sensor Data
Provide Traffic Operations Personnel Traffic Data Interface infrastructure_sensor_control Process Traffic Sensor Data
Provide Traffic Operations Personnel Traffic Data Interface dynamic_lane_mgmt_control_from_operator Provide Dynamic Lane Management
Provide Traffic Operations Personnel Traffic Data Interface request_traffic_operations_data Retrieve Traffic Data
Provide Traffic Operations Personnel Traffic Data Interface hov_lane_restriction_data Retrieve Traffic Data
Provide Traffic Operations Personnel Traffic Data Interface reversible_lane_restriction_data Retrieve Traffic Data
Provide Traffic Operations Personnel Traffic Data Interface request_traffic_map_display_update Update Traffic Display Map Data
Retrieve Traffic Data traffic_data_for_demand Collect Demand Forecast Data
Retrieve Traffic Data roadway_info_traffic_data Output Roadway Information Data
Retrieve Traffic Data roadside_traffic_data_collection_configuration Process Collected Vehicle Safety Data
Retrieve Traffic Data traffic_road_weather_data_for_emissions Process Pollution Data
Retrieve Traffic Data traffic_data_for_emissions Process Pollution Data
Retrieve Traffic Data retrieved_traffic_operations_data Provide Traffic Operations Personnel Traffic Data Interface
Retrieve Traffic Data traffic_data_for_strategy Select Strategy
Select Strategy request_other_TMC_data Exchange Data with Other Traffic Centers
Select Strategy cv_incidents_for_other_TMC Exchange Data with Other Traffic Centers
Select Strategy emergency_data_for_other_TMC Exchange Data with Other Traffic Centers
Select Strategy signal_override_status Exchange Data with Other Traffic Centers
Select Strategy selected_strategy Generate Predictive Traffic Model
Select Strategy signal_system_timing_plan Process Indicator Output Data for Roads
Select Strategy signal_system_configuration Process Indicator Output Data for Roads
Select Strategy selected_strategy Process Traffic Data for Storage
Select Strategy intersection_roadside_sensor_configuration Process Vehicle Safety and Environmental Data for Output
Select Strategy video_camera_control_strategy Process Video Data
Select Strategy selected_dynamic_lane_strategy Provide Dynamic Lane Management

Physical

This is one way this application may be realized, but not the only way. There are other ways to build a given application and accomplish a stated objective.
The physical diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagrams: ITS Infrastructure and C2C Sharing Connected Vehicle Application
PNG Diagrams: ITS Infrastructure and C2C Sharing Connected Vehicle Application


Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object Class Description
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.
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 in CVRIA) 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.
Enforcement Center Center The 'Enforcement Center' represents the systems that receive reports of violations detected by various ITS facilities including individual vehicle emissions, lane violations, toll violations, CVO violations, etc.
ITS Roadway Equipment Field 'ITS Roadway Equipment' represents the ITS equipment that is distributed on and along the roadway that monitors and controls traffic and monitors and manages the roadway itself. In CVRIA, this physical object represents all of the other ITS field equipment that interfaces with and supports the Connected Vehicle Roadside Equipment (RSE). This physical object includes traffic detectors, environmental sensors, traffic signals, highway advisory radios, dynamic message signs, CCTV cameras and video image processing systems, grade crossing warning systems, and ramp metering systems. Lane management systems and barrier systems that control access to transportation infrastructure such as roadways, bridges and tunnels are also included. This object also provides environmental monitoring including sensors that measure road conditions, surface weather, and vehicle emissions. Work zone systems including work zone surveillance, traffic control, driver warning, and work crew safety systems are also included.
Other Traffic Management Centers Center Representing another Traffic Management Center, 'Other Traffic Management Centers' is intended to provide a source and destination for information exchange between peer (e.g. inter-regional) traffic management functions. It enables traffic management activities to be coordinated across different jurisdictional areas.
Roadside Equipment Field 'Roadside Equipment' (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.
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.
Traffic Operations Personnel Center 'Traffic Operations Personnel' represents the people that operate a traffic management center. These personnel interact with traffic control systems, traffic surveillance systems, incident management systems, work zone management systems, and travel demand management systems. They provide operator data and command inputs to direct system operations to varying degrees depending on the type of system and the deployment scenario.
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 allow for 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.
Vehicle Databus Vehicle The 'Vehicle Databus' represents the interface to the vehicle databus (e.g., CAN, LIN, Ethernet/IP, FlexRay, and MOST) that may enable communication between the Vehicle OBE and other vehicle systems to support connected vehicle applications. The vehicle system statuses and/or sensor outputs available on the databus will vary based on the equipment installed on the vehicle and availability on databus. System statuses and sensor outputs may include select vehicle systems and sensors such as accelerometers, yaw rate sensors, and GPS derived location and timing information. In CVRIA, this physical object is used to represent the onboard interactions between the Vehicle OBE and the other systems included in a host vehicle.

Note that the vehicle databus interface is not standardized across all vehicle classes. Also, some Vehicle OBE implementations will not have access to the vehicle databus. See 'Vehicle OBE' for more information.
Vehicle OBE Vehicle The Vehicle On-Board Equipment (OBE) provides the vehicle-based processing, storage, and communications functions necessary to support connected vehicle operations. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle OBE. This communication platform is augmented with processing and data storage capability that supports the connected vehicle applications.

In CVRIA, the Vehicle OBE includes the functions and interfaces that support connected vehicle applications for passenger cars, trucks, and motorcycles. Many of these applications (e.g., V2V Safety applications) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle OBE includes the common interfaces and functions that apply to all motorized vehicles.

Includes Application Objects:

Application Object Description Physical Object
Emissions Connected Vehicle Monitoring "Emissions Connected Vehicle Monitoring" collects emissions data reported by passing vehicles and uses this data to support air quality management and planning. Coordination with traffic management supports air quality-responsive management of traffic. Emissions Management Center
Emissions Data Management "Emissions Data Management" collects and stores air quality and vehicle emissions information by remotely monitoring and controlling area wide and point sensors. General air quality measures are distributed as general traveler information and also may be used in demand management programs. Collected roadside emissions are analyzed and used to detect, identify, and notify concerned parties regarding vehicles that exceed emissions standards. Emissions Management Center
Roadway Basic Surveillance "Roadway Basic Surveillance" monitors traffic conditions using fixed equipment such as loop detectors and CCTV cameras. ITS Roadway Equipment
Roadway Dynamic Lane Management and Shoulder Use "Roadway Dynamic Lane Management and Shoulder Use" includes the field equipment, physical overhead lane signs and associated control electronics that are used to manage and control specific lanes and/or the shoulders. This equipment can be centrally controlled by a traffic management center or it can be autonomous and monitor traffic conditions and demand along the roadway and determine how to change the lane controls to respond to current conditions. Lane controls can be used to change the lane configuration of the roadway, reconfigure intersections and/or interchanges, allow use of shoulders as temporary travel lanes, designate lanes for use by special vehicles only, such as buses, high occupancy vehicles (HOVs), vehicles attending a special event, etc. and/or prohibit or restrict types of vehicles from using particular lanes. Guidance and information for drivers can be posted on dynamic message signs. ITS Roadway Equipment
Roadway Emissions Monitoring "Roadway Emissions Monitoring" monitors emissions and general air quality and communicates the collected information back to the emissions management center where it can be monitored, analyzed, and used. This application object supports point monitoring of individual vehicle emissions as well as general monitoring of standard air quality measures. ITS Roadway Equipment
Roadway Traffic Information Dissemination "Roadway Traffic Information Dissemination" includes field elements that provide information to drivers, including dynamic message signs and highway advisory radios. ITS Roadway Equipment
RSE Environmental Monitoring "RSE Environmental Monitoring" collects environmental situation (probe) data from passing vehicles that are equipped with short range communications capability. The collected data includes current environmental conditions as measured by on-board sensors (e.g., ambient temperature and precipitation measures), current status of vehicle systems that can be used to infer environmental conditions (e.g., status of lights, wipers, ABS, and traction control systems), and emissions measures reported by the vehicle. The application object collects the provided data, aggregates and filters the data based on provided configuration parameters, and sends the collected information back to a center for processing and distribution. This application object may also process the collected data locally and issue short-term road weather advisories for the road segment using short range communications. Roadside Equipment
RSE Restricted Lanes Application The "RSE Restricted Lanes Application" uses short range communications to monitor and manage dynamic and static restricted lanes. It collects vehicle profile information from vehicles entering the lanes and monitors vehicles within the lanes, providing aggregate data to the back office center. It provides lane restriction information and signage data to the vehicles and optionally identifies vehicles that violate the current lane restrictions. These functions are performed based on operating parameters provided by the back office managing center(s). Roadside Equipment
RSE Traffic Monitoring "RSE Traffic Monitoring" monitors the basic safety messages that are shared between connected vehicles and distills this data into traffic flow measures that can be used to manage the network in combination with or in lieu of traffic data collected by infrastructure-based sensors. As connected vehicle penetration rates increase, the measures provided by this application can expand beyond vehicle speeds that are directly reported by vehicles to include estimated volume, occupancy, and other measures. This object also supports incident detection by monitoring for changes in speed and vehicle control events that indicate a potential incident. Roadside Equipment
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. Roadside Equipment
TMC Dynamic Lane Management and Shoulder Use "TMC Dynamic Lane Management and Shoulder Use" remotely monitors and controls the system that is used to dynamically manage travel lanes, including temporary use of shoulders as travel lanes. It monitors traffic conditions and demand measured in the field and determines when the lane configuration of the roadway should be changed, when intersections and/or interchanges should be reconfigured, when the shoulders should be used for travel (as a lane), when lanes should be designated for use by special vehicles only, such as buses, high occupancy vehicles (HOVs), vehicles attending a special event, etc. and/or when types of vehicles should be prohibited or restricted from using particular lanes. It controls the field equipment used to manage and control specific lanes and the shoulders. It also can automatically notify the enforcement agency of lane control violations. Traffic Management Center
TMC In-Vehicle Signing Management "TMC In-Vehicle Signing Management" controls and monitors RSEs that support in-vehicle signing. Sign information that may include static regulatory, service, and directional sign information as well as variable information such as traffic and road conditions can be provided to the RSE, which uses short range communications to send the information to in-vehicle equipment. Information that is currently being communicated to passing vehicles and the operational status of the field equipment is monitored by this application. The operational status of the field equipment is reported to operations personnel. Traffic Management Center
TMC Regional Traffic Management "TMC Regional Traffic Management" supports coordination between traffic management centers in order to share traffic information between centers as well as control of traffic management field equipment. This coordination supports wide area optimization and regional coordination that spans jurisdictional boundaries; for example, coordinated signal control in a metropolitan area or coordination between freeway operations and arterial signal control within a corridor. Traffic Management Center
TMC Restricted Lanes CV Application "TMC Restricted Lanes CV Application" manages dynamic lanes for connected vehicles. The application provides the back office functions and supports the TMC operator in establishing and managing dynamic lanes using communications to manage lane use for connected vehicles. Traffic Management Center
TMC Traffic Information Dissemination "TMC Traffic Information Dissemination" disseminates traffic and road conditions, closure and detour information, incident information, driver advisories, and other traffic-related data to other centers, the media, and driver information systems. It monitors and controls driver information system field equipment including dynamic message signs and highway advisory radio, managing dissemination of driver information through these systems. Traffic Management Center
TMC Traffic Surveillance "TMC Traffic Surveillance" remotely monitors and controls traffic sensors and surveillance (e.g., CCTV) equipment, and collects, processes and stores the collected traffic data. Current traffic information and other real-time transportation information is also collected from other centers. The collected information is provided to traffic operations personnel and made available to other centers. Traffic Management Center
Vehicle Basic Safety "Vehicle Basic Safety" exchanges current vehicle location and motion information with other vehicles in the vicinity, uses that information to calculate vehicle paths, and warns the driver when the potential for an impending collision is detected. If available, map data is used to filter and interpret the relative location and motion of vehicles in the vicinity. Information from on-board sensors (e.g., radars and image processing) are also used, if available, in combination with the V2V communications to detect non-equipped vehicles and corroborate connected vehicle data. Vehicle location and motion broadcasts are also received by the infrastructure and used by the infrastructure to support a wide range of roadside safety and mobility applications. This object represents a broad range of implementations ranging from basic Vehicle Awareness Devices that only broadcast vehicle location and motion and provide no driver warnings to advanced integrated safety systems that may, in addition to warning the driver, provide collision warning information to support automated control functions that can support control intervention. Vehicle OBE
Vehicle Emissions Monitoring "Vehicle Emissions Monitoring" directly measures or estimates current and average vehicle emissions and makes this data available to the driver and connected vehicle infrastructure systems. Vehicle OBE
Vehicle Restricted Lanes Application The "Vehicle Restricted Lanes Application" monitors and reports its own operating parameters and communicates with roadside equipment to safely enter, operate within, and exit eco-lanes and other controlled-access lanes. Vehicle OBE
Vehicle Roadside Information Reception "Vehicle Roadside Information Reception" receives advisories, vehicle signage data, and other driver information 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 OBE

Includes Information Flows:

Information Flow Description
air quality sensor control Data used to configure and control area pollution and air quality sensors.
air quality sensor data Measured air quality data, including measured levels of atmospheric pollutants including ozone, particulate matter, carbon monoxide, and nitrogen oxides, and operational status of the sensors.
current lane restrictions Information provided to an enforcement agency that defines the current enforceable lane restrictions. It defines the location, duration, and restrictions for lanes that are reserved for the exclusive use of certain types of vehicles (e.g., transit vehicles) or vehicles that meet other qualifications (e.g., number of occupants, low emissions criteria). It identifies the lane(s), the start and stop locations, start and end times, vehicle restrictions, and speed limits.
driver information Regulatory, warning, and guidance information provided to the driver while en route to support safe and efficient vehicle operation.
driver input Driver input to the vehicle on-board equipment including configuration data, settings and preferences, interactive requests, and control commands.
driver input information Driver input received from the driver-vehicle interface equipment via the vehicle bus. It includes configuration data, settings and preferences, interactive requests, and control commands for the connected vehicle on-board equipment.
driver update information Information provided to the driver-vehicle interface to inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment. The flow includes the information to be presented to the driver and associated metadata that supports processing, prioritization, and presentation by the DVI as visual displays, audible information and warnings, and/or haptic feedback.
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.
emissions sensor control Data used to configure and control vehicle emissions sensors.
emissions situation data Emissions-related data as measured and reported by connected vehicles. This flow carries aggregated and filtered data including average and current emissions reported by vehicles as well as associated data (vehicle profiles and speeds) that can be used to estimate aggregate emissions.
emissions violation notification Notification to enforcement agency of a detected vehicle emissions violation. This information flow identifies the vehicle and documents the emissions violation.
host vehicle status Information provided to the connected vehicle on-board equipment from other systems on the vehicle platform. This includes data from on-board sensors, the current status of the powertrain, steering, and braking systems, and status of safety and convenience systems. In implementations where GPS is not integrated into the Vehicle On-Board Equipment, the host vehicle is also the source for data describing the vehicle's location in three dimensions (latitude, longitude, elevation) and accurate time that can be used for time synchronization across the Connected Vehicle environment.
lane management control Information used to configure and control dynamic lane management systems.
lane management information System status of managed lanes including current operational state, violations, and logged information.
lane violation notification Notification to enforcement agency of detected lane entry violations, lane speed violations, or other dynamic lane violations. Lane entry violations may be issued for restricted vehicle types or vehicles that do not meet required emissions or passenger occupancy standards that enter a managed lane. This notification identifies the vehicle and documents the lane parameter that was violated.
restricted lanes application status Current RSE application status that is monitored by the back office center including the operational state of the RSE, current configuration parameters, and a log of lane use (aggregate profiles of vehicles that checked in to the lane and reported vehicle speeds in the lanes) and RSE communications activity.
restricted lanes parameters Information that defines the location, duration, and operating parameters for lanes that are reserved for the exclusive use of certain types of vehicles (e.g., transit vehicles) or vehicles that meet other qualifications (e.g., number of occupants, low emissions criteria). It identifies the lane(s), the start and stop locations, start and end times, vehicle restrictions, speed limits and platooning parameters.
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 information system data Information used to initialize, configure, and control roadside systems that provide driver information (e.g., dynamic message signs, highway advisory radio). This flow can provide message content and delivery attributes, local message store maintenance requests, control mode commands, status queries, and all other commands and associated parameters that support remote management of these systems.
roadway information system status Current operating status of dynamic message signs, highway advisory radios, or other configurable field equipment that provides dynamic information to the driver.
traffic flow Raw and/or processed traffic detector data which allows derivation of traffic flow variables (e.g., speed, volume, and density measures) and associated information (e.g., congestion, potential incidents). This flow includes the traffic data and the operational status of the traffic detectors.
traffic images High fidelity, real-time traffic images suitable for surveillance monitoring by the operator or for use in machine vision applications. This flow includes the images and meta data that describes the images.
traffic operator data Presentation of traffic operations data to the operator including traffic conditions, current operating status of field equipment, maintenance activity status, incident status, video images, security alerts, emergency response plan updates and other information. This data keeps the operator appraised of current road network status, provides feedback to the operator as traffic control actions are implemented, provides transportation security inputs, and supports review of historical data and preparation for future traffic operations activities.
traffic operator input User input from traffic operations personnel including requests for information, configuration changes, commands to adjust current traffic control strategies (e.g., adjust signal timing plans, change DMS messages), and other traffic operations data entry.
traffic sensor control Information used to configure and control traffic sensor systems.
vehicle emissions data Measured emissions of specific vehicles comprised of exhaust pollutants including hydrocarbons, carbon monoxide, and nitrogen oxides.
vehicle emissions monitoring parameters Data used to configure and control roadside equipment applications that monitor emissions-related data reported by passing vehicles. The parameters include identification of the emissions-related data to be monitored and thresholds for aggregating, filtering, and reporting the collected data.
vehicle entries and exits Information exchanged between an RSE and ITS Roadway Equipment that supports detection of non-equipped vehicles in an automated lane, low emissions zone, or other facility where V2I communications is used to monitor vehicles at entry or exit points. This exchange also supports identification of non-equipped vehicles where an RSE is used for payment collection. This generic exchange can be implemented by any approach that compares vehicle detections with V2I communications by the RSE to identify vehicles that are not equipped or are otherwise unable to communicate with the RSE.
vehicle location and motion for surveillance Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size. This flow represents monitoring of basic safety data ('vehicle location and motion') broadcast by passing connected vehicles for use in vehicle detection and traffic monitoring applications.
vehicle profile Information about a vehicle such as vehicle make and model, fuel type, engine type, average emissions, average fuel consumption, passenger occupancy, or other data that can be used to classify vehicle eligibility for access to specific lanes, road segments, or regions.
vehicle reported emissions Current and average vehicle emissions data as measured by vehicle diagnostics systems and reported by the vehicle.
vehicle signage application info In-vehicle signing application configuration data and messaging parameters. This flow provides a list of regulatory, warning, and information messages to be displayed and parameters that support scheduling and prioritizing messages to be issued to passing vehicles. This flow also supports remote control of the application so the application can be taken offline, reset, or restarted.
vehicle signage application status In-vehicle signing application status reported by the RSE. This includes current operational state and status of the RSE and a log of messages sent to passing vehicles.
vehicle signage data In-vehicle signing data that augments regulatory, warning, and informational road signs and signals. The information provided would include static sign information (e.g., stop, curve warning, guide signs, service signs, and directional signs) and dynamic information (e.g., current signal states, grade crossing information, local traffic and road conditions, detours, advisories, and warnings).
vehicle signage local data Information provided by adjacent field equipment to support in-vehicle signing of dynamic information that is currently being displayed to passing drivers. This includes the dynamic information (e.g., current signal states, grade crossing information, local traffic and road conditions, detours, advisories, parking availability, etc.) and control parameters that identify the desired timing, duration, and priority of the signage data.
vehicle violation notification Notification to an individual vehicle that it has committed a lane violation. The flow identifies the nature of the violation and the time and location where the violation was recorded.
video surveillance control Information used to configure and control video surveillance systems.
widearea statistical pollution information Aggregated region-wide measured emissions and air quality data.

Application Interconnect Diagram

This is one way this application may be realized, but not the only way. There are other ways to build a given application and accomplish a stated objective.
The application interconnect diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagrams: ITS Infrastructure and C2C Sharing Connected Vehicle Application
PNG Diagrams: ITS Infrastructure and C2C Sharing Connected Vehicle Application

Application Triples

Communications
Diagram(s)
Source Destination Information Flow
None: Human interface Driver Vehicle OBE driver input
Emissions Management Center ITS Roadway Equipment air quality sensor control
Emissions Management Center ITS Roadway Equipment emissions sensor control
Emissions Management Center Enforcement Center emissions violation notification
Emissions Management Center Roadside Equipment vehicle emissions monitoring parameters
Emissions Management Center Traffic Management Center widearea statistical pollution information
ITS Roadway Equipment Emissions Management Center air quality sensor data
None: Human interface ITS Roadway Equipment Driver driver information
ITS Roadway Equipment Traffic Management Center lane management information
ITS Roadway Equipment Traffic Management Center roadway information system status
ITS Roadway Equipment Traffic Management Center traffic flow
ITS Roadway Equipment Traffic Management Center traffic images
ITS Roadway Equipment Emissions Management Center vehicle emissions data
ITS Roadway Equipment Roadside Equipment vehicle entries and exits
ITS Roadway Equipment Roadside Equipment vehicle signage local data
Other Traffic Management Centers Traffic Management Center road network conditions
Roadside Equipment Emissions Management Center emissions situation data
Roadside Equipment Enforcement Center lane violation notification
Roadside Equipment Traffic Management Center restricted lanes application status
Roadside Equipment Vehicle OBE restricted lanes parameters
Roadside Equipment ITS Roadway Equipment vehicle entries and exits
Roadside Equipment Traffic Management Center vehicle signage application status
Roadside Equipment Vehicle OBE vehicle signage data
Roadside Equipment Vehicle OBE vehicle violation notification
Traffic Management Center Enforcement Center current lane restrictions
Traffic Management Center ITS Roadway Equipment lane management control
Traffic Management Center Enforcement Center lane violation notification
Traffic Management Center Roadside Equipment restricted lanes parameters
Traffic Management Center Transportation Information Center road network conditions
Traffic Management Center Transit Management Center road network conditions
Traffic Management Center Other Traffic Management Centers road network conditions
Traffic Management Center ITS Roadway Equipment roadway information system data
None: Human interface Traffic Management Center Traffic Operations Personnel traffic operator data
Traffic Management Center ITS Roadway Equipment traffic sensor control
Traffic Management Center Roadside Equipment vehicle signage application info
Traffic Management Center ITS Roadway Equipment video surveillance control
None: Human interface Traffic Operations Personnel Traffic Management Center traffic operator input
Vehicle Databus Vehicle OBE driver input information
Vehicle Databus Vehicle OBE host vehicle status
Vehicle OBE Vehicle Databus driver update information
None: Human interface Vehicle OBE Driver driver updates
Vehicle OBE Roadside Equipment vehicle location and motion for surveillance
Vehicle OBE Roadside Equipment vehicle profile
Vehicle OBE Roadside Equipment vehicle reported emissions

Requirements

Need Requirement
N1.001 Transportation agencies need to gather data from vehicles or infrastructure to support environmental monitoring. 1.001 All environmental applications shall collect data from mobile devices to support environmental monitoring, including ambient air quality, emissions, temperature, precipitation, and other road weather information.
1.002 All environmental applications shall collect data from infrastructure devices to support environmental monitoring, including ambient air quality, emissions, temperature, precipitation, wind speed, and other road weather information.
N1.003 Eco-Lanes Management needs to collect data for eco-lanes and regular lanes operations. 1.003 Eco-Lanes Management shall collect traffic data (e.g., volume, speed, occupancy, vehicle classification, incidents) for eco-lanes and regular lanes.
1.004 Eco-Lanes Management shall collect environmental data (e.g. ambient air quality, emissions, temperature, wind speed, and other road weather information).
1.005 Eco-Lanes Management shall collect data on the operational status of Connected Vehicle and ITS Roadway Equipment.
1.006 Eco-Lanes Management shall collect vehicle-specific data about individual vehicles' parameters (e.g., emissions, temperature, speed).
1.007 Eco-Lanes Management shall collect data entered by personnel operating the system.
N1.004 Eco-Lanes Management needs to process current and historical data from multiple sources in order to provide dynamic eco-lane operations. 1.008 Eco-Lanes Management shall synthesize traffic data from multiple sources (e.g., fixed sensors, connected vehicle roadway equipment, other centers) to provide traffic analyses aggregated at different levels (e.g., corridor and regional levels).
1.009 Eco-Lanes Management shall use historical and processed traffic data to predict traffic conditions aggregated at different levels (e.g., corridor, and regional levels). The Eco-Lanes System needs to collect traffic data from other systems, or produce and continually update, a predictive model of the traffic flow conditions on the road network.
1.010 Eco-Lanes Management shall synthesize environmental data from multiple sources (e.g., fixed sensors, connected vehicle roadside equipment, other centers) to provide emissions analyses aggregated at different levels (e.g., intersection, corridor, and regional levels). The Eco-Lanes System needs to process the environmental data being collected from sensors in the geographic area and from probe vehicles.
1.011 Eco-Lanes Management shall synthesize environmental data from multiple sources (e.g., fixed sensors, connected vehicle roadside equipment, other centers) to generate predicted emissions aggregated at different levels (e.g., intersection, corridor, and regional levels).
1.012 Eco-Lanes Management shall create and decommission Eco-Lanes. The system needs to use data collected from multiple sources (e.g., sensors, connected vehicle roadside equipment, and other centers) to determine whether current or predicted conditions meet the criteria for the eco-lane. Information from models that produce real-time and predicted traffic, environmental, and demand forecasts would be used to determine the geographic limits of the eco-lane, the number of lanes included in the eco-lane, as well as the criteria for vehicles entering the eco-lane.
1.013 Eco-Lanes Management shall use data collected from vehicles to determine violations for individual vehicles in the Eco-Lanes.
1.021 Eco-Lanes Management shall determine performance measures and make them available to the operator.
N1.005 Eco-Lanes Management needs to disseminate information pertinent to eco-lane operations. 1.014 Eco-Lanes Management shall disseminate traffic conditions to other centers to enable coordination of operational strategies for a corridor or a region.
1.015 Eco-Lanes Management shall provide traffic condition messages to vehicles for the eco-lanes and regular lanes.
1.016 Eco-Lanes Management shall disseminate environmental data (e.g., regional and/or local air quality, temperature, precipitation) to other centers.
1.017 Eco-Lanes Management shall provide parameters about the eco-lanes to vehicles.
1.018 Eco-Lanes Management shall provide individual vehicles notice of a violation.
1.019 Eco-Lanes Management shall notify enforcement agencies of a violation.
N1.007 Eco-Lanes Management needs to collect data to accurately know current and forecasted conditions in order to optimize eco-lane usage. 1.022 Eco-Lanes Management shall receive traffic conditions data.
1.023 Eco-Lanes Management shall receive environmental conditions data.
1.024 Eco-Lanes Management shall collect diagnostics data from onboard systems and onboard sensors located on the vehicle to obtain vehicle status and vehicle emissions data.
1.025 Eco-Lanes Management shall receive parameters about Eco-Lanes that have been created and decommissioned.
1.026 Eco-Lanes Management shall collect vehicle status data from other vehicles, including data that is currently in the SAE J2735 basic safety message (BSM) (e.g., data about the vehicle's location, heading, speed, acceleration, braking status, and size.
1.027 Eco-Lanes Management shall collect data from the driver so the driver can configure parameters of the system or override certain vehicle characteristics.
N1.008 Eco-Lanes Management needs to process current and forecasted conditions data, data from surrounding vehicles, data from the vehicle itself and driver inputs in order to allow the driver to optimize dynamic eco-lane strategies. 1.028 Eco-Lanes Management shall calculate estimates of tailpipe emissions and fuel consumption if this data cannot be collected directly from the vehicle.
1.029 Eco-Lanes Management shall determine if the vehicle meets the criteria for entering the Eco-Lanes.
N1.009 Eco-Lanes Management needs to provide actionable information and eco-lane direction to the driver to drive in a more environmentally friendly manner as well as broadcast vehicle information from the vehicle. 1.030 Eco-Lanes Management shall transmit vehicle status data or data that is currently included in the SAE J2735 basic safety message (BSM) (e.g., data about the vehicle's location, heading, speed, acceleration, braking status, and size).
1.031 Eco-Lanes Management shall broadcast environmental data messages based on data collected from sensors located on-board the vehicle, or data that it processed.
1.032 Eco-Lanes Management shall provide eco-lane parameters to the driver and inform the driver if his/her vehicle meets the criteria for entering the eco-lanes.
N1.010 A connected vehicle needs to receive information to determine if it is in a restricted lane, such as HOV, eco-lanes, transit, or emergency vehicle only lanes. 1.002 Eco-Lanes Management shall provide traffic condition messages to vehicles for the restricted eco-lanes and regular lanes.

Related Sources

  • Dynamic Eco-Lanes: Operational Concept, Final v1.1, 8/1/2012
  • SAE J3067- Candidate Improvements to Dedicated Short Range Communications (DSRC) Message Set Dictionary (SAE J2735)Using Systems Engineering Methods, 8/15/2014

Security

In order to participate in this application, each physical object should meet or exceed the following security levels.

Physical Object Security
Physical Object Confidentiality Integrity Availability Security Class
Security levels have not been defined yet.



In order to participate in this application, 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
Security levels have not been defined yet.