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.

Roadside Lighting

The Roadside Lighting application is a connected vehicle version of the automated roadside lighting systems that uses the presence of vehicles based on V2I communications as an input to control of roadside lighting systems. The application can use the presence of vehicles to alter roadside lighting levels, and can use environmental data obtained from the vehicles as an input to support adjustment of the lighting based on adverse weather conditions such as fog, rain, or snow.

Enterprise
Functional
Physical
A-Interconnect
Communications
Requirements
Sources
Security

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:

Roadside Lighting Operations Stage
	Vehicle Owner	Driver	Vehicle OBE Owner	Roadway Owner	RSE Owner	RSE Operator	ITS Roadway Equipment Owner	ITS Roadway Operator	Traffic Manager	Traffic Operations Personnel	RSE Lighting System Support Provider	RSE Traffic Monitoring Provider	Vehicle Basic Safety Provider	Vehicle Environmental Monitoring Provider
Vehicle Owner		Vehicle Usage Agreement	Vehicle OBE Usage Agreement										Application Usage Agreement	Application Usage Agreement
Driver	Vehicle Usage Agreement
Vehicle OBE Owner	Vehicle OBE Usage Agreement				Expectation of Data Provision
Roadway Owner					Service Delivery Agreement
RSE Owner			Expectation of Data Provision	Service Delivery Agreement		Operations Agreement	Information Provision Agreement		Information Exchange and Action Agreement		Application Usage Agreement	Application Usage Agreement
RSE Operator					Operations Agreement
ITS Roadway Equipment Owner					Information Provision Agreement			Operations Agreement	Information Exchange and Action Agreement
ITS Roadway Operator							Operations Agreement
Traffic Manager					Information Exchange and Action Agreement		Information Exchange and Action Agreement			Employment Agreement
Traffic Operations Personnel									Employment Agreement
RSE Lighting System Support Provider					Application Usage Agreement
RSE Traffic Monitoring Provider					Application Usage Agreement
Vehicle Basic Safety Provider	Application Usage Agreement
Vehicle Environmental Monitoring Provider	Application 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 Manager	The entity responsible for the monitoring of and reaction to emissions.
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.
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.
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 Lighting System Control 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 Lighting System Control 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 Lighting System Control 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.
RSE Deployer	The entity responsible for the deployment, operations and maintenance of roadside equipment.
RSE Lighting System Support 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 Lighting System Support 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 Lighting System Support 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 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.
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 Lighting System Control 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 Lighting System Control 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 Lighting System Control 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 Center Passenger Counting 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 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 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.
Vehicle 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.
Vehicle 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.
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.

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.
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.
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 Lighting System Control	"Roadway Lighting System Control" includes field equipment that controls lighting systems for transportation facilities and infrastructure. It includes the sensors, lighting controllers, and supporting field equipment that monitors and controls lighting systems. The equipment supports control based on sensed local conditions, stored timing plans, and remote commands from a center. It monitors lighting system status and reports status to the controlling center.
RSE Development System	The system used in a backoffice environment to develop and test the roadside equipment.
RSE Installation System	The system used to install and configure the roadside equipment.
RSE Lighting System Support	"RSE Lighting System Support" uses V2I communications to monitor vehicle presence and collect environmental information from passing connected vehicles. The collected data is processed and filtered and provided as an input to support adjustment of roadside lighting systems.
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 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.
TMC Lighting System Control	"TMC Lighting System Control" provides the capability for traffic managers to monitor and manage the electrical lighting systems along the roadside. This capability includes implementing control plans for lighting systems that may be activated by time-of-day plans or by activating changes to the lighting based on traffic or incidents.
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.
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 Environmental Monitoring	"Vehicle Environmental Monitoring" collects data from on-board sensors and systems related to environmental conditions and sends the collected data to the infrastructure as the vehicle travels. The collected data is a byproduct of vehicle safety and convenience systems and includes ambient air temperature and precipitation measures and status of the wipers, lights, ABS, and traction control 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.

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.
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.
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.
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 and Action 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. This also includes a specification for action that shall, should or may be taken by one party in response to this information.
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.
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.
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.3	Process Environmental Sensor Data	Pspec
1.1.2	Process and Store Traffic Data	Collection
1.1.2.2	Process Traffic Data	Pspec	- TMC Traffic Surveillance
1.1.2.5	Process Traffic Situation and Sensor Data	Pspec	- TMC Traffic Surveillance - TMC Lighting System Control
1.1.2.6	Process Collected Vehicle Safety Data	Pspec	- RSE Lighting System Support - RSE Traffic Monitoring
1.1.2.8	Process Roadway Environmental Data	Pspec	- TMC Traffic Surveillance - TMC Lighting System Control
1.1.4	Display and Output Traffic Data	Collection
1.1.4.2	Provide Traffic Operations Personnel Traffic Data Interface	Pspec	- TMC Traffic Surveillance
1.1.6	Collect Vehicle Traffic Surveillance Data	Pspec	- RSE Traffic Monitoring
1.1.7	Collect Vehicle Environmental Data	Pspec	- RSE Lighting System Support - RSE Traffic Monitoring
1.2	Provide Device Control	Collection
1.2.4	Output Control Data	Collection
1.2.4.6	Manage Lighting System	Pspec	- TMC Lighting System Control
1.2.7	Provide Roadside Control Facilities	Collection
1.2.7.11	Control Lighting System	Pspec	- Roadway Lighting System Control
1.2.8	Collect Traffic Field Equipment Fault Data	Pspec	- TMC Traffic Surveillance
1.3	Manage Incidents	Collection
1.3.1	Traffic Data Analysis for Incidents	Collection
1.3.1.1	Analyze Traffic Data for Incidents	Pspec	- TMC Traffic Surveillance
1.3.1.3	Process Traffic Images	Pspec	- Roadway Basic Surveillance
3.1	Monitor Vehicle Status	Collection
3.1.3	Process Vehicle On-board Data	Pspec	- Vehicle Environmental Monitoring - Vehicle Basic Safety

Includes Data Flows:

Source Pspec	Data Flow	Destination Pspec
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 Environmental Data	vehicle_env_sensor_data_for_traffic	Process Roadway Environmental Data
Collect Vehicle Environmental Data	vehicle_env_sensor_status_for_traffic	Process Roadway Environmental 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_situation_data_for_traffic	Process Traffic Situation and Sensor Data
Collect Vehicle Traffic Surveillance Data	vehicle_situation_data_at_border	Process Traffic Situation and Sensor Data
Collect Vehicle Traffic Surveillance Data	vehicle_traffic_situation_data_configuration	Process Vehicle On-board Data
Control Lighting System	lighting_system_device_status	Collect Traffic Field Equipment Fault Data
Control Lighting System	lighting_system_status	Manage Lighting System
Manage Lighting System	lighting_system_control	Control Lighting System
Manage Lighting System	lighting_system_data_collection_configuration	Process Collected Vehicle Safety Data
Manage Lighting System	lighting_system_status_to_operator	Provide Traffic Operations Personnel Traffic Data Interface
Process Collected Vehicle Safety Data	vehicle_env_sensor_data_for_lighting	Control Lighting System
Process Collected Vehicle Safety Data	vehicle_traffic_data_for_lighting	Control Lighting System
Process Collected Vehicle Safety Data	lighting_system_roadside_sensor_status	Manage Lighting System
Process Collected Vehicle Safety Data	vehicle_env_sensor_data_for_roadside	Process Environmental Sensor Data
Process Collected Vehicle Safety Data	vehicle_env_data_for_center	Process Roadway Environmental Data
Process Collected Vehicle Safety Data	vehicle_traffic_data_for_center	Process Traffic Situation and Sensor Data
Process Collected Vehicle Safety Data	local_travel_times_data_for_traffic	Process Traffic Situation and Sensor Data
Process Environmental Sensor Data	environmental_sensor_status	Collect Traffic Field Equipment Fault Data
Process Environmental Sensor Data	environmental_sensor_data_for_roadside_safety	Process Collected Vehicle Safety Data
Process Environmental Sensor Data	environment_sensor_data	Process Roadway Environmental Data
Process Environmental Sensor Data	environmental_sensor_status	Process Roadway Environmental Data
Process Roadway Environmental Data	env_sensor_control_to_roadway	Process Environmental Sensor Data
Process Roadway Environmental Data	env_sensor_status_for_traffic_operator	Provide Traffic Operations Personnel Traffic Data Interface
Process Traffic Data	unusual_data	Analyze Traffic Data for Incidents
Process Traffic Images	traffic_image_data	Analyze Traffic Data for Incidents
Process Traffic Images	video_device_status	Collect Traffic Field Equipment Fault Data
Process Traffic Sensor Data	incident_analysis_data	Analyze Traffic Data for Incidents
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_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 On-board Data	vehicle_env_sensor_data	Collect Vehicle Environmental 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_roadside_control_event_data	Process Collected Vehicle Safety Data
Process Vehicle On-board Data	vehicle_occupants_detected	Process Traffic Sensor 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	lighting_system_activation_request_from_operator	Manage Lighting System
Provide Traffic Operations Personnel Traffic Data Interface	env_sensor_control_by_traffic_operator	Process Roadway Environmental 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

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 Diagram
PNG Diagram

Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object	Class	Description
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.
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.
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
Roadway Basic Surveillance	"Roadway Basic Surveillance" monitors traffic conditions using fixed equipment such as loop detectors and CCTV cameras.	ITS Roadway Equipment
Roadway Lighting System Control	"Roadway Lighting System Control" includes field equipment that controls lighting systems for transportation facilities and infrastructure. It includes the sensors, lighting controllers, and supporting field equipment that monitors and controls lighting systems. The equipment supports control based on sensed local conditions, stored timing plans, and remote commands from a center. It monitors lighting system status and reports status to the controlling center.	ITS Roadway Equipment
RSE Lighting System Support	"RSE Lighting System Support" uses V2I communications to monitor vehicle presence and collect environmental information from passing connected vehicles. The collected data is processed and filtered and provided as an input to support adjustment of roadside lighting systems.	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
TMC Lighting System Control	"TMC Lighting System Control" provides the capability for traffic managers to monitor and manage the electrical lighting systems along the roadside. This capability includes implementing control plans for lighting systems that may be activated by time-of-day plans or by activating changes to the lighting based on traffic or incidents.	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 Environmental Monitoring	"Vehicle Environmental Monitoring" collects data from on-board sensors and systems related to environmental conditions and sends the collected data to the infrastructure as the vehicle travels. The collected data is a byproduct of vehicle safety and convenience systems and includes ambient air temperature and precipitation measures and status of the wipers, lights, ABS, and traction control systems.	Vehicle OBE

Includes Information Flows:

Information Flow	Description
environmental situation data	Aggregated and filtered vehicle environmental data collected from vehicle safety and convenience systems including measured air temperature, exterior light status, wiper status, sun sensor status, rain sensor status, traction control status, anti-lock brake status, and other collected vehicle system status and sensor information. This information flow represents the aggregated and filtered environmental data sets that are provided by the RSE to the back office center. Depending on the RSE configuration and implementation, the data set may also include environmental sensor station data collected by the RSE.
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.
lighting management application info	Application parameters and thresholds. This flow also supports remote control of the application so the application can be taken offline, reset, or restarted.
lighting management application status	Lighting management application status reported by the RSE. This includes current operational state and status of the RSE and a record of system operation.
lighting system control data	Information used to configure and control roadside lighting systems.
lighting system status	Status of roadside lighting controls including operating condition and current operational state.
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 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.
traffic situation data	Current, aggregate traffic data collected from connected vehicles that can be used to supplement or replace information collected by roadside traffic detectors. It includes raw and/or processed reported vehicle speeds, counts, and other derived measures. Raw and/or filtered vehicle control events may also be included to support incident detection.
vehicle environmental data	Data from vehicle safety and convenience systems that can be used to estimate environmental conditions, including measured air temperature, exterior light status, wiper status, sun sensor status, rain sensor status, traction control status, anti-lock brake status, and other collected vehicle system status and sensor information. The collected data is reported along with the location, heading, and time that the data was collected. Both current data and snapshots of recent events (e.g., traction control or anti-lock brake system activations) may be reported.
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.

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 Diagram
PNG Diagram

Application Triples

Communications Diagram(s)	Source	Destination	Information Flow
	ITS Roadway Equipment	Traffic Management Center	lighting system status
	ITS Roadway Equipment	Traffic Management Center	traffic flow
	Roadside Equipment	ITS Roadway Equipment	environmental situation data
	Roadside Equipment	Traffic Management Center	environmental situation data
	Roadside Equipment	Traffic Management Center	lighting management application status
	Roadside Equipment	ITS Roadway Equipment	traffic situation data
	Roadside Equipment	Traffic Management Center	traffic situation data
	Traffic Management Center	Roadside Equipment	lighting management application info
	Traffic Management Center	ITS Roadway Equipment	lighting system control data
None: Human interface	Traffic Management Center	Traffic Operations Personnel	traffic operator data
	Traffic Management Center	ITS Roadway Equipment	traffic sensor control
None: Human interface	Traffic Operations Personnel	Traffic Management Center	traffic operator input
	Vehicle Databus	Vehicle OBE	host vehicle status
	Vehicle OBE	Roadside Equipment	vehicle environmental data
	Vehicle OBE	Roadside Equipment	vehicle location and motion for surveillance

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.
N1.001		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.
N3.119	Roadside lighting systems need to be able to adjust their light levels based on the presence of vehicles in the road section	3.228	Roadside lighting systems shall adjust their lighting levels based on the measured presence of vehicles on the roadway segment.
N3.120	Roadside lighting systems need to be able to adjust their light levels based on the weather conditions in the road section	3.229	Roadside lighting systems shall adjust the lighting levels in a roadway segment based upon information received from vehicles regarding hazardous weather conditions such as fog, rain, and snow.

Related Sources

National ITS Architecture Services

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
Source	Destination	Information Flow	Basis	Basis	Basis
Security levels have not been defined yet.