Type: Mobility

Groups:

Traffic Network

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.

Vehicle Data for Traffic Operations

The Vehicle Data for Traffic Operations (VDTO) application uses probe data information obtained from vehicles in the network to support traffic operations, including incident detection and the implementation of localized operational strategies. The implantation of incident detection enables transportation agencies to determine the location of potential incidents so the agencies can respond more quickly to the incident and mitigate any negative impacts to the transportation network. Vehicle data that can be used to detect potential incidents include changes in vehicle speeds indicating the disruption of traffic flow, when a vehicle's safety systems have been activated or deployed, or sudden vehicle turns or deceleration at a specific location (indicating a potential obstacle in the roadway). Operational strategies might include altering signal timing based on traffic flows or using vehicle data collected on the freeway mainline to employ speed harmonization or to optimize ramp metering rates.

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:

Vehicle Data for Traffic Operations Operations Stage
	Vehicle Owner	Driver	Vehicle OBE Owner	Roadway Owner	RSE Owner	RSE Operator	ITS Roadway Equipment Owner	ITS Roadway Operator	Traffic Manager	Information Service Provider	Maint and Constr Manager	RSE Traffic Monitoring Provider	Emergency Manager	RSE Situation Monitoring Provider	Vehicle Basic Safety Provider	Vehicle Situation Data 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				Service Delivery Agreement		Operations Agreement			Information Exchange Agreement			Application Usage Agreement		Application Usage Agreement
RSE Operator			Expectation of Data Provision		Operations Agreement
ITS Roadway Equipment Owner								Operations Agreement	Information Exchange Agreement
ITS Roadway Operator							Operations Agreement
Traffic Manager					Information Exchange Agreement		Information Exchange Agreement			Information Provision Agreement	Information Provision Agreement		Information Provision Agreement
Information Service Provider									Information Provision Agreement
Maint and Constr Manager									Information Provision Agreement
RSE Traffic Monitoring Provider					Application Usage Agreement
Emergency Manager									Information Provision Agreement
RSE Situation Monitoring Provider					Application Usage Agreement
Vehicle Basic Safety Provider	Application Usage Agreement
Vehicle Situation Data 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.
Emergency Manager	The "Emergency Manager" represents agencies charged with incident management, disaster response, and transportation environment security.
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.
Maint and Constr Manager	The organization responsible for maintenance and construction activities.
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 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 Situation 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 Situation 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 Situation 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 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 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.
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 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 Situation Data 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 Situation Data 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 Situation Data 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.

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.
Emergency Management Center	The 'Emergency Management Center' represents systems that support incident management, disaster response and evacuation, security monitoring, and other security and public safety-oriented ITS applications. It includes the functions associated with fixed and mobile public safety communications centers including public safety call taker and dispatch centers operated by police (including transit police), fire, and emergency medical services. It includes the functions associated with Emergency Operations Centers that are activated at local, regional, state, and federal levels for emergencies and the portable and transportable systems that support Incident Command System operations at an incident. This Center also represents systems associated with towing and recovery, freeway service patrols, HAZMAT response teams, and mayday service providers. It manages sensor and surveillance equipment used to enhance transportation security of the roadway infrastructure (including bridges, tunnels, interchanges, and other key roadway segments) and the public transportation system (including transit vehicles, public areas such as transit stops and stations, facilities such as transit yards, and transit infrastructure such as rail, bridges, tunnels, or bus guideways). It provides security/surveillance services to improve traveler security in public areas not a part of the public transportation system. It monitors alerts, advisories, and other threat information and prepares for and responds to identified emergencies. It coordinates emergency response involving multiple agencies with peer centers. It stores, coordinates, and utilizes emergency response and evacuation plans to facilitate this coordinated response. Emergency situation information including damage assessments, response status, evacuation information, and resource information are shared The Emergency Management Center also provides a focal point for coordination of the emergency and evacuation information that is provided to the traveling public, including wide-area alerts when immediate public notification is warranted. It tracks and manages emergency vehicle fleets using real-time road network status and routing information from the other centers to aid in selecting the emergency vehicle(s) and routes, and works with other relevant centers to tailor traffic control to support emergency vehicle ingress and egress, implementation of special traffic restrictions and closures, evacuation traffic control plans, and other special strategies that adapt the transportation system to better meet the unique demands of an emergency.
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 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.
Maint and Constr Management Center	The 'Maint and Constr Management Center' monitors and manages roadway infrastructure construction and maintenance activities. Representing both public agencies and private contractors that provide these functions, this physical object manages fleets of maintenance, construction, or special service vehicles (e.g., snow and ice control equipment). The physical object receives a wide range of status information from these vehicles and performs vehicle dispatch, routing, and resource management for the vehicle fleets and associated equipment. The physical object participates in incident response by deploying maintenance and construction resources to an incident scene, in coordination with other center physical objects. The physical object manages equipment at the roadside, including environmental sensors and automated systems that monitor and mitigate adverse road and surface weather conditions. It manages the repair and maintenance of both non-ITS and ITS equipment including the traffic controllers, detectors, dynamic message signs, signals, and other equipment associated with the roadway infrastructure. Weather information is collected and fused with other data sources and used to support advanced decision support systems. The physical object remotely monitors and manages ITS capabilities in work zones, gathering, storing, and disseminating work zone information to other systems. It manages traffic in the vicinity of the work zone and advises drivers of work zone status (either directly at the roadside or through an interface with the Transportation Information Center or Traffic Management Center physical objects.) Construction and maintenance activities are tracked and coordinated with other systems, improving the quality and accuracy of information available regarding closures and other roadway construction and maintenance activities.
MCM Environmental Information Collection	"MCM Environmental Information Collection" collects current road and weather conditions using data collected from environmental sensors deployed on and about the roadway. In addition to fixed sensor stations at the roadside, this application object also collects environmental information from sensor systems located on Maintenance and Construction Vehicles. It also collects current and forecast environmental conditions information that is made available by other systems. The application object aggregates the sensor system data and provides it, along with data attributes to other applications.
MCM Incident Management	"MCM Incident Management" supports maintenance and construction participation in coordinated incident response. Incident notifications are shared, incident response resources are managed, and the overall incident situation and incident response status is coordinated among allied response organizations.
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.
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 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 Situation Monitoring	"RSE Situation Monitoring" is a general application object that supports collection of traffic, environmental, and emissions data from passing vehicles. The data is collected, filtered, and forwarded based on parameters provided by the back office. Parameters are provided to passing vehicles that are equipped to collect and send situation data to the infrastructure in snapshots. In addition, this object collects current status information from local field devices including intersection status, sensor data, and signage data, providing complete, configurable monitoring of the situation for the local transportation system in the vicinity of the RSE.
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 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.
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 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 Situation Data Monitoring	"Vehicle Situation Data Monitoring" is the highest-level representation of the functionality required to collect traffic and environmental situation data by monitoring and storing the experience of the vehicle as it travels through the road network. Collected data is aggregated into snapshots that are reported when communications is available and with flow control based on parameters provided by the infrastructure. Note that this application object supports collection of data for areas remote from RSEs or other communications infrastructure.

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.
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.
Expectation of Action	Expectation	An expectation where one party expects another party to take a specific action, typically in response to data or information provided by the first party, but without any formal agreement.
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 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.
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 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.
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
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
1.1.2.6	Process Collected Vehicle Safety Data	Pspec	- RSE Traffic Monitoring
1.1.2.9	Monitor Dynamic Lanes	Pspec	- TMC Traffic Surveillance
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 Surveillance - TMC Regional Traffic Management
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 - RSE Situation Monitoring
1.2	Provide Device Control	Collection
1.2.2	Determine Road and Freeway State	Collection
1.2.2.1	Determine Indicator State for Freeway Management	Pspec
1.2.2.2	Determine Indicator State for Road Management	Pspec	- TMC Regional Traffic Management
1.2.6	Maintain Static Data for TMC	Collection
1.2.6.1	Maintain Traffic and Sensor Static Data	Pspec	- TMC Traffic Surveillance - TMC Regional Traffic Management
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.3	Process Traffic Images	Pspec
1.3.2	Review and Manage Incident Data	Collection
1.3.2.2	Review and Classify Possible Incidents	Pspec	- TMC Regional Traffic Management
1.3.2.6	Manage Traffic Routing	Pspec	- TMC Traffic Surveillance - TMC Regional Traffic Management
1.3.3	Respond to Current Incidents	Pspec
1.3.4	Provide Operator Interfaces for Incidents	Collection
1.3.4.6	Process Video Data	Pspec	- TMC Traffic Surveillance
3.1	Monitor Vehicle Status	Collection
3.1.3	Process Vehicle On-board Data	Pspec	- Vehicle Basic Safety - Vehicle Situation Data Monitoring
5.1	Provide Emergency Service Allocation	Collection
5.1.1	Detect and Verify Emergencies	Collection
5.1.1.3	Collect Incident And Event Data	Pspec
5.1.4	Manage Emergency Response	Pspec
5.3	Manage Emergency Vehicles	Collection
5.3.7	Provide Emergency Vehicle Route	Pspec
6.2	Collect Traveler Information Services Data	Collection
6.2.1	Collect Misc Traveler Information	Pspec
6.2.2	Collect Traffic Data	Pspec
6.2.6	Collect Emergency Traveler Data	Pspec
9.1	Manage M&C Vehicles	Collection
9.1.7	Process Road Network Information	Pspec	- MCM Incident Management
9.4	Manage Environmental Information	Collection
9.4.2	Collect Environmental Data	Pspec	- MCM Environmental Information Collection

Includes Data Flows:

Source Pspec	Data Flow	Destination Pspec
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
Determine Indicator State for Freeway Management	reversible_lane_signal_state_for_freeways	Collect Traffic Data
Determine Indicator State for Freeway Management	coordination_data_freeways_to_roads	Determine Indicator State for Road Management
Determine Indicator State for Freeway Management	highway_closures	Manage Traffic Routing
Determine Indicator State for Road Management	reversible_lane_signal_state_for_roads	Collect Traffic Data
Determine Indicator State for Road Management	coordination_data_roads_to_freeways	Determine Indicator State for Freeway Management
Determine Indicator State for Road Management	roadway_closures	Manage Traffic Routing
Generate Predictive Traffic Model	prediction_data	Collect Traffic Data
Generate Predictive Traffic Model	prediction_data	Determine Indicator State for Freeway Management
Generate Predictive Traffic Model	prediction_data	Determine Indicator State for Road Management
Generate Predictive Traffic Model	traffic_model_data_for_incident_calcs	Respond to Current Incidents
Maintain Traffic and Sensor Static Data	link_data_for_guidance	Collect Traffic Data
Manage Emergency Response	em_response_work_zone_safety_data_parameters	Process Collected Vehicle Safety Data
Manage Emergency Response	incident_response_status_from_emerg	Process Road Network Information
Manage Emergency Response	remote_video_image_control	Process Video Data
Manage Traffic Routing	roadway_detours_and_closures_for_traveler	Collect Traffic Data
Manage Traffic Routing	roadway_detours_and_closures_for_em_response	Manage Emergency Response
Manage Traffic Routing	emergency_route_response	Provide Emergency Vehicle Route
Manage Traffic Routing	roadway_detours_and_closures_for_em	Provide Emergency Vehicle Route
Manage Traffic Routing	roadway_detours_and_closures_for_traffic	Retrieve Traffic Data
Monitor Dynamic Lanes	dynamic_lane_data	Process Traffic 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 Traffic Data	strategy_data_for_highways	Determine Indicator State for Freeway Management
Process Traffic Data	strategy_data_for_roads	Determine Indicator State for Road Management
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	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	dynamic_lane_sensor_data	Monitor Dynamic Lanes
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_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
Process Video Data	incident_video_for_emergency_services	Manage Emergency Response
Process Video Data	incident_video_image_control	Process Traffic Images
Provide Emergency Vehicle Route	emergency_route_request	Manage Traffic Routing
Provide Traffic Operations Personnel Traffic Data Interface	roadside_data_collection_configuration_data	Collect Vehicle Traffic Surveillance 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	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
Respond to Current Incidents	incident_alert_details	Collect Incident And Event Data
Respond to Current Incidents	current_traffic_incident_response	Manage Emergency Response
Respond to Current Incidents	incident_response_clear	Manage Emergency Response
Respond to Current Incidents	incident_info_from_traffic	Process Road Network Information
Retrieve Traffic Data	traffic_incident_data	Collect Emergency Traveler Data
Retrieve Traffic Data	environmental_sensor_data_from_traffic_management	Collect Environmental Data
Retrieve Traffic Data	traffic_road_weather_data	Collect Misc Traveler Information
Retrieve Traffic Data	current_highway_network_state	Collect Traffic Data
Retrieve Traffic Data	current_road_network_state	Collect Traffic Data
Retrieve Traffic Data	traffic_data_for_traveler	Collect Traffic Data
Retrieve Traffic Data	traffic_video_for_traveler	Collect Traffic Data
Retrieve Traffic Data	traffic_data_for_em_response	Manage Emergency Response
Retrieve Traffic Data	roadside_traffic_data_collection_configuration	Process Collected Vehicle Safety Data
Retrieve Traffic Data	disaster_network_status_from_traffic_to_m_and_c	Process Road Network Information
Retrieve Traffic Data	road_network_info_from_traffic	Process Road Network Information
Retrieve Traffic Data	traffic_video_for_mcm	Process Road Network Information
Retrieve Traffic Data	traffic_data_for_emergency_services	Provide Emergency Vehicle Route
Retrieve Traffic Data	retrieved_traffic_operations_data	Provide Traffic Operations Personnel Traffic Data Interface
Review and Classify Possible Incidents	planned_events	Collect Traffic Data
Review and Classify Possible Incidents	planned_events	Generate Predictive Traffic Model
Review and Classify Possible Incidents	planned_events_for_em_response	Manage Emergency Response
Review and Classify Possible Incidents	planned_events_for_maint	Process Road Network Information

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
Emergency Management Center	Center	The 'Emergency Management Center' represents systems that support incident management, disaster response and evacuation, security monitoring, and other security and public safety-oriented ITS applications. It includes the functions associated with fixed and mobile public safety communications centers including public safety call taker and dispatch centers operated by police (including transit police), fire, and emergency medical services. It includes the functions associated with Emergency Operations Centers that are activated at local, regional, state, and federal levels for emergencies and the portable and transportable systems that support Incident Command System operations at an incident. This Center also represents systems associated with towing and recovery, freeway service patrols, HAZMAT response teams, and mayday service providers. It manages sensor and surveillance equipment used to enhance transportation security of the roadway infrastructure (including bridges, tunnels, interchanges, and other key roadway segments) and the public transportation system (including transit vehicles, public areas such as transit stops and stations, facilities such as transit yards, and transit infrastructure such as rail, bridges, tunnels, or bus guideways). It provides security/surveillance services to improve traveler security in public areas not a part of the public transportation system. It monitors alerts, advisories, and other threat information and prepares for and responds to identified emergencies. It coordinates emergency response involving multiple agencies with peer centers. It stores, coordinates, and utilizes emergency response and evacuation plans to facilitate this coordinated response. Emergency situation information including damage assessments, response status, evacuation information, and resource information are shared The Emergency Management Center also provides a focal point for coordination of the emergency and evacuation information that is provided to the traveling public, including wide-area alerts when immediate public notification is warranted. It tracks and manages emergency vehicle fleets using real-time road network status and routing information from the other centers to aid in selecting the emergency vehicle(s) and routes, and works with other relevant centers to tailor traffic control to support emergency vehicle ingress and egress, implementation of special traffic restrictions and closures, evacuation traffic control plans, and other special strategies that adapt the transportation system to better meet the unique demands of an emergency.
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.
Maint and Constr Management Center	Center	The 'Maint and Constr Management Center' monitors and manages roadway infrastructure construction and maintenance activities. Representing both public agencies and private contractors that provide these functions, this physical object manages fleets of maintenance, construction, or special service vehicles (e.g., snow and ice control equipment). The physical object receives a wide range of status information from these vehicles and performs vehicle dispatch, routing, and resource management for the vehicle fleets and associated equipment. The physical object participates in incident response by deploying maintenance and construction resources to an incident scene, in coordination with other center physical objects. The physical object manages equipment at the roadside, including environmental sensors and automated systems that monitor and mitigate adverse road and surface weather conditions. It manages the repair and maintenance of both non-ITS and ITS equipment including the traffic controllers, detectors, dynamic message signs, signals, and other equipment associated with the roadway infrastructure. Weather information is collected and fused with other data sources and used to support advanced decision support systems. The physical object remotely monitors and manages ITS capabilities in work zones, gathering, storing, and disseminating work zone information to other systems. It manages traffic in the vicinity of the work zone and advises drivers of work zone status (either directly at the roadside or through an interface with the Transportation Information Center or Traffic Management Center physical objects.) Construction and maintenance activities are tracked and coordinated with other systems, improving the quality and accuracy of information available regarding closures and other roadway construction and maintenance activities.
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.
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
MCM Environmental Information Collection	"MCM Environmental Information Collection" collects current road and weather conditions using data collected from environmental sensors deployed on and about the roadway. In addition to fixed sensor stations at the roadside, this application object also collects environmental information from sensor systems located on Maintenance and Construction Vehicles. It also collects current and forecast environmental conditions information that is made available by other systems. The application object aggregates the sensor system data and provides it, along with data attributes to other applications.	Maint and Constr Management Center
MCM Incident Management	"MCM Incident Management" supports maintenance and construction participation in coordinated incident response. Incident notifications are shared, incident response resources are managed, and the overall incident situation and incident response status is coordinated among allied response organizations.	Maint and Constr Management Center
RSE Situation Monitoring	"RSE Situation Monitoring" is a general application object that supports collection of traffic, environmental, and emissions data from passing vehicles. The data is collected, filtered, and forwarded based on parameters provided by the back office. Parameters are provided to passing vehicles that are equipped to collect and send situation data to the infrastructure in snapshots. In addition, this object collects current status information from local field devices including intersection status, sensor data, and signage data, providing complete, configurable monitoring of the situation for the local transportation system in the vicinity of the RSE.	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 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 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 Situation Data Monitoring	"Vehicle Situation Data Monitoring" is the highest-level representation of the functionality required to collect traffic and environmental situation data by monitoring and storing the experience of the vehicle as it travels through the road network. Collected data is aggregated into snapshots that are reported when communications is available and with flow control based on parameters provided by the infrastructure. Note that this application object supports collection of data for areas remote from RSEs or other communications infrastructure.	Vehicle OBE

Includes Information Flows:

Information Flow	Description
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.
incident information	Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system.
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.
situation data collection parameters	The parameters that are used to control the flow of situation data from the RSE. This flow identifies the type of data/snapshots that are requested from passing vehicles and reporting parameters such as snapshot frequency, filtering criteria (data thresholds for reporting), and reporting interval that control the type and volume of data reported to the back office center.
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 monitoring application info	Traffic monitoring application parameters and thresholds that control the filtering, aggregation, and range of measures that are collected, derived, and reported. This flow also supports remote control of the application so the application can be taken offline, reset, or restarted.
traffic monitoring application status	Traffic monitoring application status reported by the RSE. This includes current operational state and status of the RSE and a record of system operation.
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 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 situation data	This flow represents vehicle snapshots that may be provided by the vehicle to support traffic and environmental conditions monitoring. Snapshots are collected by the vehicle for specific events (e.g., when a sensor exceeds a threshold) or periodically and reported based on control parameters when communications is available. Traffic-related data includes snapshots of measured speed and heading and events including starts and stops, speed changes, and other vehicle control events. Environmental data may include 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.
vehicle situation data parameters	A request for vehicle situation data that includes parameters used to control the data that is reported and the flow of data reported by the vehicle. This flow identifies the type of data/snapshots that are requested and reporting parameters such as snapshot frequency, filtering criteria (data thresholds for reporting), and reporting interval.
video surveillance control	Information used to configure and control video surveillance systems.

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

Source	Destination	Information Flow
ITS Roadway Equipment	Traffic Management Center	traffic images
Roadside Equipment	Traffic Management Center	traffic monitoring application status
Roadside Equipment	Traffic Management Center	traffic situation data
Roadside Equipment	Vehicle OBE	vehicle situation data parameters
Traffic Management Center	Emergency Management Center	incident information
Traffic Management Center	Transportation Information Center	incident information
Traffic Management Center	Maint and Constr Management Center	incident information
Traffic Management Center	Transportation Information Center	road network conditions
Traffic Management Center	Emergency Management Center	road network conditions
Traffic Management Center	Maint and Constr Management Center	road network conditions
Traffic Management Center	Roadside Equipment	situation data collection parameters
Traffic Management Center	Roadside Equipment	traffic monitoring application info
Traffic Management Center	ITS Roadway Equipment	video surveillance control
Vehicle Databus	Vehicle OBE	host vehicle status
Vehicle OBE	Roadside Equipment	vehicle location and motion for surveillance
Vehicle OBE	Roadside Equipment	vehicle situation data

Requirements

Need		Requirement
N2.187	Vehicle Data for Traffic Operations (VDTO) needs to collect vehicle data to support incident detection.	2.397	Vehicle Data for Traffic Operations (VDTO) shall collect vehicle traffic probe data.
N2.188	VDTO needs to provide vehicle data to traveler information companies and traffic management agencies to support traffic operations.	2.398	VDTO shall accept requests for traffic vehicle data.
N2.188		2.399	VDTO shall provide traffic vehicle data to centers that request it.
N2.189	VDTO needs to collect vehicle data to support the implementation of operations strategies.	2.400	VDTO shall collect vehicle traffic probe data.
N2.190	VDTO needs to provide vehicle data to traffic management agencies to support the implementation of operations strategies.	2.401	VDTO shall accept requests for traffic vehicle data.
N2.190		2.402	VDTO shall provide traffic vehicle data to centers that request it.

Related Sources

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