Parent Service Package: MC09
< < MC09.2 : MC09.3 : MC10.1 > >

MC09.3: C-ITS Vehicle Monitoring

Data from the general vehicle population is used to monitor infrastructure condition. In this implementation, C-ITS communications is used to collect vertical acceleration data and other probe data from participating vehicles that may be used to monitor pavement condition.

Relevant Regions:

Enterprise
Functional
Physical
Goals and Objectives
Needs and Requirements
Sources
Security
Standards
System Requirements

Enterprise

Development Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
Asset Management System Developer	Asset Management System	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.
Connected Vehicle Roadside Equipment Developer	Connected Vehicle Roadside Equipment	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.
Connected Vehicle Roadside Equipment Developer	Maint and Constr Management Center Developer	Application Interface Specification (hide) 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.
Maint and Constr Management Center Developer	Asset Management System Developer	Application Interface Specification (hide) 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.
Maint and Constr Management Center Developer	Connected Vehicle Roadside Equipment Developer	Application Interface Specification (hide) 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.
Maint and Constr Management Center Developer	Maint and Constr Management Center	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.
Vehicle Developer	Connected Vehicle Roadside Equipment Developer	Application Interface Specification (hide) 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.
Vehicle Developer	Vehicle	Develops (hide) An Enterprise creates the target Resource or Document. The Enterprise that engineers a traffic signal controller (ITS Roadway Equipment), or designs a vehicle (Basic Vehicle) or authors a technical standard will have the Develops role.

Installation Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
Asset Management System Installer	Asset Management System	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Asset Management System Owner	Asset Management System Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Asset Management System Owner	Asset Management System Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Connected Vehicle Roadside Equipment Installer	Connected Vehicle Roadside Equipment	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Connected Vehicle Roadside Equipment Owner	Connected Vehicle Roadside Equipment Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Connected Vehicle Roadside Equipment Owner	Connected Vehicle Roadside Equipment Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Maint and Constr Management Center Installer	Maint and Constr Management Center	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Maint and Constr Management Center Owner	Maint and Constr Management Center Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Maint and Constr Management Center Owner	Maint and Constr Management Center Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.
Vehicle Installer	Vehicle	Installs (hide) An Enterprise performs the initial delivery, integration and configuration of the target Resource. This might be a system integrator, a state DOT Enterprise performing its own installation, or a device supplier that performs on-site installation.
Vehicle Owner	Vehicle Installer	Installation Agreement (hide) An agreement whereupon one party installs a system on behalf of a second party.
Vehicle Owner	Vehicle Verifier	Verification Agreement (hide) An agreement for one party to verify that a system owned by the second party operates according to the system's design.

Operations and Maintenance Stage Roles and Relationships
(hide)

Source	Destination	Role/Relationship
Asset Management System Maintainer	Asset Management System	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Asset Management System Manager	Asset Management System	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Asset Management System Manager	Asset Management System Operator	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Asset Management System Operator	Asset Management System	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
Asset Management System Owner	Asset Management System Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Asset Management System Owner	Asset Management System Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Asset Management System Supplier	Asset Management System Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Connected Vehicle Roadside Equipment Maintainer	Connected Vehicle Roadside Equipment	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Connected Vehicle Roadside Equipment Manager	Connected Vehicle Roadside Equipment	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Connected Vehicle Roadside Equipment Manager	Connected Vehicle Roadside Equipment Operator	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Connected Vehicle Roadside Equipment Operator	Connected Vehicle Roadside Equipment	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
Connected Vehicle Roadside Equipment Owner	Connected Vehicle Roadside Equipment Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Connected Vehicle Roadside Equipment Owner	Connected Vehicle Roadside Equipment Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Connected Vehicle Roadside Equipment Owner	Maint and Constr Center Personnel	Application Usage Agreement (hide) 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.
Connected Vehicle Roadside Equipment Owner	Maint and Constr Management Center Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Connected Vehicle Roadside Equipment Owner	Maint and Constr Management Center Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Connected Vehicle Roadside Equipment Owner	Maint and Constr Management Center User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Connected Vehicle Roadside Equipment Supplier	Connected Vehicle Roadside Equipment Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Driver	Vehicle	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
Maint and Constr Center Personnel	Maint and Constr Management Center	Operates (hide) A Human that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This is the person at the console or behind the wheel.
Maint and Constr Management Center Maintainer	Maint and Constr Management Center	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Maint and Constr Management Center Manager	Maint and Constr Center Personnel	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Maint and Constr Management Center Manager	Maint and Constr Management Center	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Maint and Constr Management Center Owner	Asset Management System Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Maint and Constr Management Center Owner	Asset Management System Operator	Application Usage Agreement (hide) 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.
Maint and Constr Management Center Owner	Asset Management System Owner	Information Provision Agreement (hide) An agreement where one party agrees to provide information to another party. This is a unidirectional agreement.
Maint and Constr Management Center Owner	Asset Management System User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Maint and Constr Management Center Owner	Connected Vehicle Roadside Equipment Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Maint and Constr Management Center Owner	Connected Vehicle Roadside Equipment Operator	Application Usage Agreement (hide) 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.
Maint and Constr Management Center Owner	Connected Vehicle Roadside Equipment Owner	Information Exchange Agreement (hide) An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement.
Maint and Constr Management Center Owner	Connected Vehicle Roadside Equipment User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Maint and Constr Management Center Owner	Maint and Constr Management Center Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Maint and Constr Management Center Owner	Maint and Constr Management Center Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Maint and Constr Management Center Supplier	Maint and Constr Management Center Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.
Vehicle Maintainer	Vehicle	Maintains (hide) An Enterprise administers the hardware and software that comprise the target Resource. The entity that takes the ‘maintains’ role typically is delegated authority by the entity with the “Owns” or "Manages" roles, depending on the environment. The maintainer interacts with the target Resource so as to keep that Resource in the Operational state.
Vehicle Manager	Driver	System Usage Agreement (hide) An agreement granting operational use of a system to a Human with the operates role responsible for management of the system.
Vehicle Manager	Vehicle	Manages (hide) The Enterprise that is accountable for performing actions with a Resource, typically in support of one of the key operations-related roles (operates, installs, maintains). This authority is typically delegated by the Enterprise with the "Owns" role, and commonly accomplished by delegation to Human E-Objects with the "operates", "installs" or "maintains" roles, depending on the context.
Vehicle Owner	Connected Vehicle Roadside Equipment Maintainer	Maintenance Data Exchange Agreement (hide) An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Vehicle Owner	Connected Vehicle Roadside Equipment Operator	Application Usage Agreement (hide) 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.
Vehicle Owner	Connected Vehicle Roadside Equipment Owner	Expectation of Data Provision (hide) 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.
Vehicle Owner	Connected Vehicle Roadside Equipment User	Service Usage Agreement (hide) An agreement between the provider of a service and a user. Stipulates the terms and conditions of service usage.
Vehicle Owner	Vehicle Maintainer	System Maintenance Agreement (hide) An agreement for one party to maintain the operational status of a system on behalf of the party with ownership control of the system.
Vehicle Owner	Vehicle Manager	Operations Agreement (hide) An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
Vehicle Supplier	Vehicle Owner	Warranty (hide) A guarantee or promise made by one entity to another, that provides assurance of the functionality and performance of a subsystem.

Functional

This service package includes the following Functional View PSpecs:

Physical Object	Functional Object	PSpec Number	PSpec Name
Connected Vehicle Roadside Equipment	RSE Infrastructure Monitoring	1.1.1.6	Collect Vehicle Roadside Safety Data
		1.1.2.6	Process Collected Vehicle Safety Data
		1.1.7	Collect Vehicle Environmental Data
		1.2.7.7	Process Vehicle Safety and Environmental Data for Output
Maint and Constr Management Center	MCM Infrastructure Monitoring	9.2.3.7	Process Environmental Probe Data for Maintenance
		9.2.5	Provide M&C Center Personnel Interface for Maint
		9.2.6.3	Operate Infrastructure Monitoring Devices
		9.2.6.4	Collect Infrastructure Data
Vehicle	Vehicle Environmental Monitoring	3.1.3	Process Vehicle On-board Data
		3.2.3.2	Manage Platoon Following
		3.2.3.3	Process Data for Vehicle Actuators
		3.2.3.5.1	Process General Vehicle Sensor Data
		3.2.4	Process Sensor Data for Automatic Vehicle Operations
		6.7.1.3	Process Vehicle Location Data
		6.7.1.4	Update Vehicle Navigable Map Database
		6.7.3.1	Provide Driver with Personal Travel Information
		6.7.3.2	Provide Driver Information Interface

Physical

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
Asset Management System	Center	'Asset Management System' represents the systems that support decision-making for maintenance, upgrade, and operation of physical transportation assets. Asset management integrates and includes the pavement management systems, bridge management systems, and other systems that inventory and manage the highway infrastructure and other transportation-related assets. The types of assets that are inventoried and managed will vary, and may include the maintenance and construction vehicles and equipment as well as "soft" assets such as human resources and software. Asset management systems monitor the condition, performance, and availability of the infrastructure and evaluate and prioritize alternative reconstruction, rehabilitation, and maintenance strategies.
Connected Vehicle Roadside Equipment	Field	'Connected Vehicle Roadside Equipment' (CV RSE) represents the Connected Vehicle roadside devices (i.e., Roadside Units (RSUs)) equipped with short range wireless (SRW) communications technology, as well as any other supporting equipment that leverage the RSU and are not described by other objects (e.g., a local roadside processor). CVRSE are used to send messages to, and receive messages from, nearby vehicles and personal devices equipped with compatible communications technology. 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.
Maint and Constr Center Personnel	Center	The people that directly interface with a Maintenance and Construction Management Center. These personnel interact with fleet dispatch and management systems, road maintenance systems, incident management systems, work plan scheduling systems, and work zone 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.
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.
Vehicle	Vehicle	This 'Vehicle' physical object is used to model core capabilities that are common to more than one type of Vehicle. It provides the vehicle-based general sensory, processing, storage, and communications functions that support efficient, safe, and convenient travel. Many of these capabilities (e.g., see the Vehicle Safety service packages) apply to all vehicle types including personal vehicles (including motorcycles), commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle includes the common interfaces and functions that apply to all motorized vehicles. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle. Both one-way and two-way communications options support a spectrum of information services from basic broadcast to advanced personalized information services. Advanced sensors, processors, enhanced driver interfaces, and actuators complement the driver information services so that, in addition to making informed mode and route selections, the driver travels these routes in a safer and more consistent manner. This physical object supports all six levels of driving automation as defined in SAE J3016. Initial collision avoidance functions provide 'vigilant co-pilot' driver warning capabilities. More advanced functions assume limited control of the vehicle to maintain lane position and safe headways. In the most advanced implementations, this Physical Object supports full automation of all aspects of the driving task, aided by communications with other vehicles in the vicinity and in coordination with supporting infrastructure subsystems.

Includes Functional Objects:

Functional Object	Description	Physical Object
MCM Infrastructure Monitoring	'MCM Infrastructure Monitoring' monitors the condition of pavement, bridges, tunnels, associated hardware, and other transportation-related infrastructure (e.g., culverts). It monitors the infrastructure, collecting data from both fixed and vehicle-based sensors. In addition to specialized infrastructure monitoring sensors, it also monitors the broader population of equipped vehicles for vertical acceleration data and other situation data that may be used to determine current pavement condition.	Maint and Constr Management Center
RSE Infrastructure Monitoring	'RSE Infrastructure Monitoring' collects environmental situation (probe) data from passing vehicles that are equipped with short range communications capability with particular focus on measures that may indicate infrastructure condition. The collected data includes current environmental conditions as measured by on-board sensors (e.g., ambient temperature and precipitation measures) and current status of vehicle systems that can be used to infer infrastructure condition (e.g., status of ABS, traction control systems, vertical acceleration measures) as reported by the vehicle. This functional object also supports short range communications with maintenance and construction vehicles, providing local control and monitoring of infrastructure sensors.	Connected Vehicle Roadside Equipment
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

Includes Information Flows:

Information Flow	Description
asset status update	Changes to status of pavement, bridges, signs and other assets resulting from maintenance or construction activities or infrastructure monitoring. The updates may include changes in installation information, materials information, vendor/contractor information, condition, and current maintenance status. In addition to infrastructure asset updates, the information provided may also include status of the maintenance and construction support assets, including vehicle and equipment utilization and repair records.
environmental monitoring application info	Environmental 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.
environmental monitoring application status	Environmental monitoring application status reported by the RSE. This includes current operational state and status of the RSE and a record of system operation.
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.
infrastructure situation data	Aggregated and filtered vehicle data collected from vehicle safety and convenience systems that are indicative of infrastructure condition including traction control status, anti-lock brake status, accelerometer 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.
maint and constr operations information presentation	Presentation of maintenance and construction operations information to center personnel. This information includes maintenance resource status (vehicles, equipment, and personnel), work schedule information, work status, road and weather conditions, traffic information, incident information and associated resource requests, security alerts, emergency response plans and a range of other information that supports efficient maintenance and construction operations and planning.
vehicle environmental data	Data from vehicle safety and convenience systems that can be used to estimate environmental and infrastructure conditions, including measured air temperature, exterior light status, wiper status, sun sensor status, rain sensor status, traction control status, anti-lock brake status, vertical acceleration 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.

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor	Goal

Associated Objective Categories

Objective Category

Associated Objectives and Performance Measures

Objective	Performance Measure

Since the mapping between objectives and service packages is not always straight-forward and often situation-dependent, these mappings should only be used as a starting point. Users should do their own analysis to identify the best service packages for their region.

Needs and Requirements

Need		Functional Object	Requirement

Related Sources

Document Name	Version	Publication Date
None

Security

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

Physical Object Security
Physical Object	Confidentiality	Integrity	Availability	Security Class
Asset Management System
Connected Vehicle Roadside Equipment
Maint and Constr Management Center
Vehicle

In order to participate in this service package, each information flow triple should meet or exceed the following security levels.

Information Flow Security
Source	Destination	Information Flow	Confidentiality	Integrity	Availability
Source	Destination	Information Flow	Basis	Basis	Basis
Connected Vehicle Roadside Equipment	Maint and Constr Management Center	environmental monitoring application status	Moderate	Moderate	Low
Connected Vehicle Roadside Equipment	Maint and Constr Management Center	environmental monitoring application status	This information could be of interest to a malicious individual who is attempting to determine the best way to accomplish a crime. As such it would be best to not make it easily accessible. May be LOW in some cases.	Control parameters need to be correct and not corrupted so that the owner of the RSE and the receiver of the RSE's data get what they need from it.	A delay in reporting this may cause a delay in necessary maintenance, but (a) this is not time-critical and (b) there are other channels for reporting malfunctioning.
Connected Vehicle Roadside Equipment	Maint and Constr Management Center	environmental situation data	Low	Moderate	Moderate
Connected Vehicle Roadside Equipment	Maint and Constr Management Center	environmental situation data	Little to no impact if this data is observed	Only limited adverse effect if environmental data from vehicle safety and convenience systems is bad/compromised; can cope with some bad data; DISC: WYO believes this to be MODERATE HIGH. Changed from THEA's LOW inferring severity of weather data in Wyoming	Only limited adverse effect of info is not timely/readily available. DISC: WYO believes this to be MODERATE. Changed from THEA's LOW inferring severity of weather data in Wyoming
Connected Vehicle Roadside Equipment	Maint and Constr Management Center	infrastructure situation data	Moderate	Moderate	High
Connected Vehicle Roadside Equipment	Maint and Constr Management Center	infrastructure situation data	Field situation data should include only directly observable data. However, this information flow could include a huge volume, and could be highly aggregated and/or valuable. Some protection of this information is justified given the scope of the data and the knowledge that could be gleaned by illicit observation of this flow.	Situation data will be used for a variety of decision-making purposes, so it should have some error checking, as any corruption could lead to sub-optimal choices. While any given instance of this flow is not critical, the aggregation of all will be significant.	This could be the primary source of field situation data for many centers. Given this potential reliance, HIGH is warranted. If in a particular area the data is "nice to have but not necessary" this might be lowered to MODERATE or even LOW, depending on the data types and uses for that data by subscribers.
Maint and Constr Management Center	Asset Management System	asset status update	Moderate	Moderate	Low
Maint and Constr Management Center	Asset Management System	asset status update	Linked to the asset inventory, so the same concerns with this flow as that one, namely that when placed in one spot becomes a "one stop shop" for a nefarious person looking for infrastructure targets. Given the narrow focus of this flow it might be LOW, except that it infers information about specific targets.	Infrastructure information should be correct or maintenance assets may be inappropriately assigned.	While this changes more than other asset flows, the impact should still be minimal.
Maint and Constr Management Center	Connected Vehicle Roadside Equipment	environmental monitoring application info	Moderate	Moderate	Low
Maint and Constr Management Center	Connected Vehicle Roadside Equipment	environmental monitoring application info	This is a control flow, so should be obfuscated to make it more difficult for a 3rd party to manipulate the RSE.	Control parameters need to be correct and not corrupted so that the owner of the RSE and the receiver of the RSE's data get what they need from it.	This information probably does not need to be changed very often, and if it is not available then likely the flow it controls (emissions data flows to the DDS/EMC) are down as well.
Maint and Constr Management Center	Maint and Constr Center Personnel	maint and constr operations information presentation	Not Applicable	Moderate	Moderate
Maint and Constr Management Center	Maint and Constr Center Personnel	maint and constr operations information presentation	System maintenance flows should have some protection from casual viewing, as otherwise imposters could gain illicit control over field equipment	Information presented to backoffice system operators must be consistent or the operator may perform actions that are not appropriate to the real situation.	The backoffice system operator should have access to system operation. If this interface is down then control is effectively lost, as without feedback from the system the operator has no way of knowing what is the correct action to take.
Vehicle	Connected Vehicle Roadside Equipment	vehicle environmental data	Low	Moderate	Low
Vehicle	Connected Vehicle Roadside Equipment	vehicle environmental data	Little abusive potential for capturing the information in this flow as designed. Could be moderate if this contains PII related information, but considered for now to not include any PII; DISC: WYO believes Vehicle to Center versions of this flow to be MODERATE as center penetrations could more easily garner aggregate user data that might be used for mischief.	Some minimal guarantee of data integrity is necessary for all C-ITS flows. DISC THEA believes this to be LOW: Data should be accurate and not tampered with but should be able to cope with some bad data in traffic/environmental condition monitoring; aggregate data; can also receive data from ITS RE; DISC: WYO believes this to be MODERATE	data should be timely and readily available, but limited adverse effect; aggregate data; can also receive data from ITS RE; DISC: WYO believes this to be MODERATE

Standards

The following table lists the standards associated with physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages. These pages can be accessed directly from the SVG diagram(s) located on the Physical tab, by clicking on each information flow line on the diagram.

Name	Title	Physical Object
CTI 4001 RSU	Roadside Unit (RSU) Standard	Connected Vehicle Roadside Equipment
NEMA TS 8 Cyber and Physical Security	Cyber and Physical Security for Intelligent Transportation Systems	Maint and Constr Management Center

System Requirements

No System Requirements