Type: Mobility

Groups:

Traffic Signals

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.

Emergency Vehicle Preemption

The Emergency Vehicle Preemption (EVP) application is a very high level of priority for emergency first responder vehicles. Historically, priority for emergency vehicles has been provided by special traffic signal timing strategies called preemption. The goal of EVP is to facilitate safe and efficient movement through intersections. As such, clearing queues and holding conflicting phases can facilitate emergency vehicle movement. For congested conditions, it may take additional time to clear a standing queue, so the ability to provide information in a timely fashion is important. In addition, transitioning back to normal traffic signal operations after providing EVP is an important consideration since the control objectives are significantly different.

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:

Emergency Vehicle Preemption Operations Stage
	Roadway Owner	RSE Owner	RSE Operator	ITS Roadway Equipment Owner	ITS Roadway Operator	Traffic Manager	Emergency Vehicle Manager	Emergency Personnel	EV On-Board En Route Support Provider	RSE Intersection Management Provider	Emergency Manager
Roadway Owner		Service Delivery Agreement
RSE Owner	Service Delivery Agreement		Operations Agreement	Information Exchange and Action Agreement						Application Usage Agreement
RSE Operator		Operations Agreement
ITS Roadway Equipment Owner		Information Exchange and Action Agreement			Operations Agreement	Information Exchange and Action Agreement
ITS Roadway Operator				Operations Agreement				Expectation of Data Provision
Traffic Manager				Information Exchange and Action Agreement							Information Exchange and Action Agreement
Emergency Vehicle Manager								Vehicle Usage Agreement	Application Usage Agreement		Expectation of Data Provision
Emergency Personnel					Expectation of Data Provision		Vehicle Usage Agreement
EV On-Board En Route Support Provider							Application Usage Agreement
RSE Intersection Management Provider		Application Usage Agreement
Emergency Manager						Information Exchange and Action Agreement	Expectation of Data Provision

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.
Emergency Fleet Manager	The entity that controls emergency vehicles and provides them for use in incident response.
Emergency Manager	The "Emergency Manager" represents agencies charged with incident management, disaster response, and transportation environment security.
Emergency Personnel	'Emergency Personnel' represents personnel that are responsible for police, fire, emergency medical services, towing, service patrols, and other special response team (e.g., hazardous material clean-up) activities at an incident site. These personnel are associated with the Emergency Vehicle during dispatch to the incident site, but often work independently of the Emergency Vehicle while providing their incident response services.
Emergency Routing 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.
Emergency Routing 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.
Emergency Routing 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.
Emergency Vehicle Manager	The enterprise that controls and manages emergency vehicle operations.
Emergency Vehicle Manufacturer	The entity that builds, assembles, verifies and validates the Emergency Vehicle in which the Emergency Vehicle OBE will eventually operate.
Emergency Vehicle OBE Manufacturer	The entity that builds, assembles, verifies and validates the Emergency Vehicle OBE. This can be an OEM-equipped OBE, retrofit or aftermarket equipment.
EV On-Board En Route Support Installer	Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
EV On-Board En Route Support Maintainer	Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
EV On-Board En Route Support Provider	Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
Federal Regulatory	Federal regulatory bodies that have legal authority to control and/or provide input to policies regulating transportation infrastructure and operations. This includes entities such as the Federal Communications Commission and US Department of Transportation.
ITS Certification Entity	The body that determines whether an ITS device or application may be deployed and operated in the transportation environment. This entity's composition, the requirements it applies and the procedures it uses to verify those requirements may vary with device and application type. Typically not a formal body, assigned on a project-by-project basis depending on the type of infrastructure involved. Since ITS projects are locally-focused (typically state or smaller), the entities that are part of this body are typically those with operational jurisdiction where the ITS is installed (e.g., state or local DOTs, state or local maintenance managers etc.)
ITS Roadway Equipment Owner	The entity that owns the Roadway ITS equipment.
ITS Roadway Operator	The entity that operates the Roadway ITS equipment.
Roadway Owner	The owner of the roadway proximate to which roadside equipment will be/is installed.
Roadway Signal Control Installer	Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Roadway Signal Control Maintainer	Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
Roadway Signal Control Provider	Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
RSE Deployer	The entity responsible for the deployment, operations and maintenance of roadside equipment.
RSE Intersection Management Installer	Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
RSE Intersection Management Maintainer	Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
RSE Intersection Management Provider	Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
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.
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 Signal Control Installer	Application Component Installers are specified more by role than by function. Installers are responsible for the installation of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
TMC Signal Control Maintainer	Application Component Maintainers are specified more by role than by function. Maintainers are responsible for the maintenance (configuration changes, patches and updates, hardware repairs) of the application component, which may require a support system, and may entail agreements and relationships between end users and application providers.
TMC Signal Control Provider	Application Component Providers are specified more by role than by function. Providers are responsible for the development of the application component, including initial creation, enhancement and bug fixes. Delivery of the application to the end user may require relationships with other entities (installers, maintainers) if the provider chooses not to fulfill those roles.
Traffic Manager	The entity responsible for the management of traffic, both freeway and arterial.

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.
Emergency Routing	"Emergency Routing" supports routing of emergency vehicles and enlists support from the Traffic Management Center to facilitate travel along these routes. Routes may be determined based on real-time traffic information and road conditions or routes may be provided by the Traffic Management Center on request. Vehicles are tracked and routes are based on current vehicle location. It may coordinate with the Traffic Management Center to provide preemption or otherwise adapt the traffic control strategy along the selected route.
Emergency Vehicle	The "Emergency Vehicle" represents a range of vehicles including those operated by police, fire, and emergency medical services, as well as incident response vehicles including towing and recovery vehicles and freeway service patrols.
Emergency Vehicle OBE	The Emergency Vehicle On-Board Equipment (OBE) resides in an emergency vehicle and provides the processing, storage, and communications functions that support public safety-related connected vehicle applications. It represents a range of vehicles including those operated by police, fire, and emergency medical services. In addition, it represents other incident response vehicles including towing and recovery vehicles and freeway service patrols. It includes two-way communications to support coordinated response to emergencies. In CVRIA, a separate 'Vehicle OBE' physical object supports the general V2V and V2I safety applications and other applications that apply to all vehicles, including emergency vehicles. The Emergency Vehicle OBE supplements these general capabilities with capabilities that are specific to emergency vehicles.
EV On-Board En Route Support	"EV On-board En Route Support" provides communications functions to responding emergency vehicles that reduce response times and improve safety of responding public safety personnel and the general public. It supports traffic signal preemption via short range communication directly with signal control equipment and sends alert messages to surrounding vehicles.
Field Component Development System	The system used in a backoffice environment to develop and test the field component of the application.
Field Component Installation System	The system used to install a field component of a connected vehicle application.
Field Component Maintenance System	The system used to install and configure changes and updates to the field component of the application. This system is capable of acquiring and reporting diagnostic information about the application's configuration and performance.
ITS Certification Requirements	The requirements that define the functionality, performance and operational environment of an ITS device or ITS application. Applicability varies with jurisdictions, but typically devices and applications must meet pre-defined acceptance criteria prior to usage in the transportation environment.
ITS Field Component Development System	The system used in a backoffice environment to develop and test the ITS field component of the application.
ITS Field Component Installation System	The system used to install a field component of a connected vehicle application.
ITS Field Component Maintenance System	The system used to install and configure changes and updates to the ITS field component of the application. This system is capable of acquiring and reporting diagnostic information about the application's configuration and performance.
ITS Roadway Equipment	'ITS Roadway Equipment' represents the ITS equipment that is distributed on and along the roadway that monitors and controls traffic and monitors and manages the roadway itself. In CVRIA, this physical object represents all of the other ITS field equipment that interfaces with and supports the Connected Vehicle Roadside Equipment (RSE). This physical object includes traffic detectors, environmental sensors, traffic signals, highway advisory radios, dynamic message signs, CCTV cameras and video image processing systems, grade crossing warning systems, and ramp metering systems. Lane management systems and barrier systems that control access to transportation infrastructure such as roadways, bridges and tunnels are also included. This object also provides environmental monitoring including sensors that measure road conditions, surface weather, and vehicle emissions. Work zone systems including work zone surveillance, traffic control, driver warning, and work crew safety systems are also included.
Mobile Component Development System	The system used in a backoffice environment to develop and test the mobile component of the application.
Mobile Component Installation System	The system that interacts with the Vehicle OBE other mobile device and installs the mobile component of the application.
Mobile Component Maintenance System	The system used to configure changes and updates to the mobile component of the application. This system is capable of acquiring and reporting diagnostic information about the application's configuration and performance.
Roadside Equipment	'Roadside Equipment' (RSE) represents the Connected Vehicle roadside devices that are used to send messages to, and receive messages from, nearby vehicles using Dedicated Short Range Communications (DSRC) or other alternative wireless communications technologies. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers.
Roadway Signal Control	"Roadway Signal Control" includes the field elements that monitor and control signalized intersections. It includes the traffic signal controllers, detectors, conflict monitors, signal heads, and other ancillary equipment that supports traffic signal control. It also includes field masters, and equipment that supports communications with a central monitoring and/or control system, as applicable. The communications link supports upload and download of signal timings and other parameters and reporting of current intersection status. It represents the field equipment used in all levels of traffic signal control from basic actuated systems that operate on fixed timing plans through adaptive systems. It also supports all signalized intersection configurations, including those that accommodate pedestrians. In advanced, future implementations, environmental data may be monitored and used to support dilemma zone processing and other aspects of signal control that are sensitive to local environmental conditions.
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 Intersection Management	"RSE Intersection Management" uses short range communications to support connected vehicle applications that manage signalized intersections. It communicates with approaching vehicles and ITS infrastructure (e.g., the traffic signal controller) to enhance traffic signal operations. Coordination with the ITS infrastructure also supports conflict monitoring to ensure the RSE output and traffic signal control output are consistent and degrade in a fail safe manner.
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.
TMC Signal Control	"TMC Signal Control" provides the capability for traffic managers to monitor and manage the traffic flow at signalized intersections. This capability includes analyzing and reducing the collected data from traffic surveillance equipment and developing and implementing control plans for signalized intersections. Control plans may be developed and implemented that coordinate signals at many intersections under the domain of a single traffic management center and are responsive to traffic conditions and adapt to support incidents, preemption and priority requests, pedestrian crossing calls, etc.
Traffic Management Center	The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters.
Vehicle OBE	The Vehicle On-Board Equipment (OBE) provides the vehicle-based processing, storage, and communications functions necessary to support connected vehicle operations. The radio(s) supporting V2V and V2I communications are a key component of the Vehicle OBE. This communication platform is augmented with processing and data storage capability that supports the connected vehicle applications. In CVRIA, the Vehicle OBE includes the functions and interfaces that support connected vehicle applications for passenger cars, trucks, and motorcycles. Many of these applications (e.g., V2V Safety applications) apply to all vehicle types including personal vehicles, commercial vehicles, emergency vehicles, transit vehicles, and maintenance vehicles. From this perspective, the Vehicle OBE includes the common interfaces and functions that apply to all motorized vehicles.

Includes Roles:

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

Includes Coordination:

Coordination	Type	Description
Application Installation Data	Information Sharing	Data needed to install the application, including the application executable code and any configuration data. Unidirectional flow.
Application Interface Specification	Agreement	The definition of an interface between two application components that operate on two distinct pieces of hardware. The Application Interface Specification is specific to the application in question.
Application Maintenance Data	Information Sharing	Data used to facilitate the upgrade, patching and general health maintenance of an application component.
Application Performance Data	Information Sharing	Data used to characterize application performance, including such measures as availability, known errors and known uses.
Application Procurement Agreement	Agreement	An agreement whereupon one entity provides a copy of an application component to another entity. This component is capable of being installed and functioning, according to its requirements that passed through the application's certification process.
Application Usage Agreement	Agreement	An agreement in which one entity that controls an application component's use gives the other entity the necessary tools and permission to operate that application or application component.
Backoffice Component Installation Agreement	Agreement	An agreement that grants one party permission to install a backoffice application component on a center-based device controlled by the other party.
Device Placement and Operations Agreement	Agreement	An agreement that enables the controller of a physical device to install it (so as to make it operational) at a fixed location controlled by another entity.
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.
Includes	Includes	Indicates that one component is entirely contained within another component.
Information Exchange and Action Agreement	Agreement	An agreement to exchange information, which may include data or control information; the exact information to be exchanged may vary from agreement to agreement. This also includes a specification for action that shall, should or may be taken by one party in response to this information.
Installation Agreement	Agreement	An agreement whereupon one entity installs an application component on a device controlled by another entity.
Maintenance Agreement	Agreement	An agreement in which one entity maintains the operational status of a system under the control of another entity. This maintenance may include routine and as-needed maintenance, such as software update and configuration, hardware replacement and related system administration activities.
Maintenance Data Exchange Agreement	Agreement	An agreement that states one entity will provide data related to maintenance of an application component to the other entity.
Mobile Component Installation Agreement	Agreement	An agreement whereupon the controller of OBE gives another party permission to install, configure and make operational a component that enables the mobile portion of an application.
Mobile Component License Agreement	Agreement	An end-user license agreement allowing the operator of the mobile device to use the mobile application component that is part of the application in question.
Operations Agreement	Agreement	An agreement where one entity agrees to operate a device or application on behalf of another, device/application controlling entity.
RSE Deployment Agreement	Agreement	Agreement to install, configure and make operational roadside equipment, between the provider of that equipment and the entity that controls access to the roadside. May define locations, expectation of power provision, backhaul responsibility and installation restrictions.
RSE Installation Data	Information Sharing	Data necessary to configure and make RSE operational. Uni-directional.
RSE Maintenance Data	Information Sharing	Data necessary to modify the operational configuration of RSE; assumes RSE is already configured. Uni-directional.
RSE Performance Data	Information Sharing	Data that includes metrics of RSE performance. Could include fields such as uptime, packets received/transmitted, distance vector from which packets received, as well as application-specific performance measures.
RSE Procurement Agreement	Agreement	An agreement whereupon one entity provides roadside equipment to another entity. The RSE is capable of being installed and functioning, according to its requirements that passed through the device's certification process.
Service Delivery Agreement	Agreement	A relationship where one party agrees to provide a service to the other party. This agreement may specify the expected performance of this service in terms of availability and/or actions/time-type performance specifications.
Vehicle Data Access Agreement	Agreement	An agreement whereby the party that controls access to on-board vehicle data grants another party the right and ability to access that data. Includes the conditions under which data may be accessed, and specifies the mechanisms, including physical and functional access methods, data formats and any other considerations necessary for the accessing party to acquire data. May also include caveats regarding responsibility for data quality and responsibility for use of the data.
Vehicle 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.6	Collect Vehicle Roadside Safety Data	Pspec	- RSE Intersection Management
1.1.2	Process and Store Traffic Data	Collection
1.1.2.6	Process Collected Vehicle Safety Data	Pspec	- RSE Intersection Management
1.2	Provide Device Control	Collection
1.2.1	Select Strategy	Pspec	- TMC Signal Control
1.2.4	Output Control Data	Collection
1.2.4.1	Output Control Data for Roads	Pspec	- TMC Signal Control
1.2.7	Provide Roadside Control Facilities	Collection
1.2.7.1	Process Indicator Output Data for Roads	Pspec	- Roadway Signal Control
1.2.7.2	Monitor Roadside Equipment Operation	Pspec	- Roadway Signal Control
1.2.7.3	Manage Local Signal Preemption Requests	Pspec	- RSE Intersection Management
1.2.7.5	Process Indicator Output Data for Freeways	Pspec	- Roadway Signal Control
1.2.7.7	Process Vehicle Safety and Environmental Data for Output	Pspec	- RSE Intersection Management
1.2.8	Collect Traffic Field Equipment Fault Data	Pspec	- TMC Signal Control
5.3	Manage Emergency Vehicles	Collection
5.3.3	Provide Emergency Vehicle Location	Pspec	- EV On-Board En Route Support
5.3.5	Provide Emergency Personnel Interface	Pspec	- EV On-Board En Route Support
5.3.6	Maintain Vehicle Status	Pspec	- Emergency Routing
5.3.7	Provide Emergency Vehicle Route	Pspec	- Emergency Routing

Includes Data Flows:

Source Pspec	Data Flow	Destination Pspec
Collect Traffic Field Equipment Fault Data	indicator_fault_state	Select Strategy
Collect Vehicle Roadside Safety Data	vehicle_safety_input_data	Process Collected Vehicle Safety Data
Manage Local Signal Preemption Requests	indicator_monitoring_suspend	Monitor Roadside Equipment Operation
Manage Local Signal Preemption Requests	indicator_override_for_highways	Process Indicator Output Data for Freeways
Manage Local Signal Preemption Requests	indicator_override_for_roads	Process Indicator Output Data for Roads
Monitor Roadside Equipment Operation	indicator_status_from_signals	Collect Traffic Field Equipment Fault Data
Monitor Roadside Equipment Operation	indicator_status_from_traffic_meters	Collect Traffic Field Equipment Fault Data
Monitor Roadside Equipment Operation	indicator_faults_from_signals	Collect Traffic Field Equipment Fault Data
Output Control Data for Roads	indicator_status_for_roads_from_center	Collect Traffic Field Equipment Fault Data
Output Control Data for Roads	indicator_control_configuration_data_for_signal_control	Monitor Roadside Equipment Operation
Output Control Data for Roads	reversible_lane_control_for_roads	Process Indicator Output Data for Roads
Output Control Data for Roads	indicator_control_data_for_signal_control	Process Indicator Output Data for Roads
Output Control Data for Roads	indicator_input_state_for_roads	Select Strategy
Process Collected Vehicle Safety Data	vehicle_traffic_data_for_freeways	Process Indicator Output Data for Freeways
Process Collected Vehicle Safety Data	vehicle_traffic_data_for_roads	Process Indicator Output Data for Roads
Process Collected Vehicle Safety Data	vehicle_safety_data_indication	Process Vehicle Safety and Environmental Data for Output
Process Collected Vehicle Safety Data	roadway_geometry_location_data	Process Vehicle Safety and Environmental Data for Output
Process Collected Vehicle Safety Data	roadway_intersection_geometry_data	Process Vehicle Safety and Environmental Data for Output
Process Indicator Output Data for Freeways	reversible_lane_control_device_status_from_highways	Collect Traffic Field Equipment Fault Data
Process Indicator Output Data for Freeways	indicator_response_data_for_highways	Monitor Roadside Equipment Operation
Process Indicator Output Data for Freeways	traffic_metering_data_for_roadside	Process Vehicle Safety and Environmental Data for Output
Process Indicator Output Data for Roads	reversible_lane_control_device_status_from_roads	Collect Traffic Field Equipment Fault Data
Process Indicator Output Data for Roads	indicator_response_data_for_roads	Monitor Roadside Equipment Operation
Process Indicator Output Data for Roads	indicator_input_data_from_signals	Output Control Data for Roads
Process Indicator Output Data for Roads	roadside_signal_phase_indication	Process Vehicle Safety and Environmental Data for Output
Process Indicator Output Data for Roads	roadside_signal_phase_timing	Process Vehicle Safety and Environmental Data for Output
Process Indicator Output Data for Roads	roadside_signal_phase_response_state	Process Vehicle Safety and Environmental Data for Output
Process Indicator Output Data for Roads	roadside_signal_priority_preempt	Process Vehicle Safety and Environmental Data for Output
Process Indicator Output Data for Roads	signal_preemption_override	Select Strategy
Process Indicator Output Data for Roads	signal_priority_override	Select Strategy
Process Vehicle Safety and Environmental Data for Output	queue_warning_system_status	Collect Traffic Field Equipment Fault Data
Process Vehicle Safety and Environmental Data for Output	signal_phase_indication_to_em_vehicle	Provide Emergency Vehicle Location
Process Vehicle Safety and Environmental Data for Output	signal_phase_response_state_to_em_vehicle	Provide Emergency Vehicle Location
Process Vehicle Safety and Environmental Data for Output	signal_phase_timing_to_em_vehicle	Provide Emergency Vehicle Location
Provide Emergency Personnel Interface	emergency_vehicle_enroute	Provide Emergency Vehicle Location
Provide Emergency Vehicle Location	em_vehicle_roadside_current_status_data	Collect Vehicle Roadside Safety Data
Provide Emergency Vehicle Location	em_vehicle_roadside_location_data	Collect Vehicle Roadside Safety Data
Provide Emergency Vehicle Location	em_vehicle_roadside_size_data	Collect Vehicle Roadside Safety Data
Provide Emergency Vehicle Location	em_vehicle_roadside_speed_data	Collect Vehicle Roadside Safety Data
Provide Emergency Vehicle Location	emergency_vehicle_tracking_data	Maintain Vehicle Status
Provide Emergency Vehicle Location	emergency_vehicle_preemptions	Manage Local Signal Preemption Requests
Provide Emergency Vehicle Location	emergency_vehicle_location_for_operator	Provide Emergency Personnel Interface
Provide Emergency Vehicle Route	emergency_vehicle_suggested_route	Provide Emergency Personnel Interface
Provide Emergency Vehicle Route	emergency_traffic_control_request	Select Strategy
Select Strategy	signal_system_timing_plan	Process Indicator Output Data for Roads
Select Strategy	signal_system_configuration	Process Indicator Output Data for Roads
Select Strategy	intersection_roadside_sensor_configuration	Process Vehicle Safety and Environmental Data for Output
Select Strategy	emergency_traffic_control_response	Provide Emergency Vehicle Route

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.
Emergency Personnel	Vehicle	'Emergency Personnel' represents personnel that are responsible for police, fire, emergency medical services, towing, service patrols, and other special response team (e.g., hazardous material clean-up) activities at an incident site. These personnel are associated with the Emergency Vehicle during dispatch to the incident site, but often work independently of the Emergency Vehicle while providing their incident response services.
Emergency Vehicle Databus	Vehicle	The 'Emergency Vehicle Databus' represents the vehicle databus that interfaces with on-board equipment on a public safety vehicle. It is a specialized and extended form of the Vehicle Databus that may be subject to different vehicle databus standards and hosts a broad range of components that are specific to emergency vehicles including the lightbar/siren and on-board apparatus that supports law enforcement, firefighting, and emergency medical services. As a specialized form of the Vehicle Databus, it also provides access to the general-purpose sensors (e.g., radars, cameras), GPS, drive train monitoring and control systems, and vehicle safety features that support connected vehicle applications. In CVRIA, the 'Emergency Vehicle Databus' is used to represent the onboard interactions between the Emergency Vehicle OBE and the other systems included in a host emergency vehicle.
Emergency Vehicle OBE	Vehicle	The Emergency Vehicle On-Board Equipment (OBE) resides in an emergency vehicle and provides the processing, storage, and communications functions that support public safety-related connected vehicle applications. It represents a range of vehicles including those operated by police, fire, and emergency medical services. In addition, it represents other incident response vehicles including towing and recovery vehicles and freeway service patrols. It includes two-way communications to support coordinated response to emergencies. In CVRIA, a separate 'Vehicle OBE' physical object supports the general V2V and V2I safety applications and other applications that apply to all vehicles, including emergency vehicles. The Emergency Vehicle OBE supplements these general capabilities with capabilities that are specific to emergency vehicles.
ITS Roadway Equipment	Field	'ITS Roadway Equipment' represents the ITS equipment that is distributed on and along the roadway that monitors and controls traffic and monitors and manages the roadway itself. In CVRIA, this physical object represents all of the other ITS field equipment that interfaces with and supports the Connected Vehicle Roadside Equipment (RSE). This physical object includes traffic detectors, environmental sensors, traffic signals, highway advisory radios, dynamic message signs, CCTV cameras and video image processing systems, grade crossing warning systems, and ramp metering systems. Lane management systems and barrier systems that control access to transportation infrastructure such as roadways, bridges and tunnels are also included. This object also provides environmental monitoring including sensors that measure road conditions, surface weather, and vehicle emissions. Work zone systems including work zone surveillance, traffic control, driver warning, and work crew safety systems are also included.
Roadside Equipment	Field	'Roadside Equipment' (RSE) represents the Connected Vehicle roadside devices that are used to send messages to, and receive messages from, nearby vehicles using Dedicated Short Range Communications (DSRC) or other alternative wireless communications technologies. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers.
Traffic Management Center	Center	The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters.

Includes Application Objects:

Application Object	Description	Physical Object
Emergency Routing	"Emergency Routing" supports routing of emergency vehicles and enlists support from the Traffic Management Center to facilitate travel along these routes. Routes may be determined based on real-time traffic information and road conditions or routes may be provided by the Traffic Management Center on request. Vehicles are tracked and routes are based on current vehicle location. It may coordinate with the Traffic Management Center to provide preemption or otherwise adapt the traffic control strategy along the selected route.	Emergency Management Center
EV On-Board En Route Support	"EV On-Board En Route Support" provides communications functions to responding emergency vehicles that reduce response times and improve safety of responding public safety personnel and the general public. It supports traffic signal preemption via short range communication directly with signal control equipment and sends alert messages to surrounding vehicles.	Emergency Vehicle OBE
Roadway Signal Control	"Roadway Signal Control" includes the field elements that monitor and control signalized intersections. It includes the traffic signal controllers, detectors, conflict monitors, signal heads, and other ancillary equipment that supports traffic signal control. It also includes field masters, and equipment that supports communications with a central monitoring and/or control system, as applicable. The communications link supports upload and download of signal timings and other parameters and reporting of current intersection status. It represents the field equipment used in all levels of traffic signal control from basic actuated systems that operate on fixed timing plans through adaptive systems. It also supports all signalized intersection configurations, including those that accommodate pedestrians. In advanced, future implementations, environmental data may be monitored and used to support dilemma zone processing and other aspects of signal control that are sensitive to local environmental conditions.	ITS Roadway Equipment
RSE Intersection Management	"RSE Intersection Management" uses short range communications to support connected vehicle applications that manage signalized intersections. It communicates with approaching vehicles and ITS infrastructure (e.g., the traffic signal controller) to enhance traffic signal operations. Coordination with the ITS infrastructure also supports conflict monitoring to ensure the RSE output and traffic signal control output are consistent and degrade in a fail safe manner.	Roadside Equipment
TMC Signal Control	"TMC Signal Control" provides the capability for traffic managers to monitor and manage the traffic flow at signalized intersections. This capability includes analyzing and reducing the collected data from traffic surveillance equipment and developing and implementing control plans for signalized intersections. Control plans may be developed and implemented that coordinate signals at many intersections under the domain of a single traffic management center and are responsive to traffic conditions and adapt to support incidents, preemption and priority requests, pedestrian crossing calls, etc.	Traffic Management Center

Includes Information Flows:

Information Flow	Description
driver information	Regulatory, warning, and guidance information provided to the driver while en route to support safe and efficient vehicle operation.
emergency personnel information presentation	Presentation of information to emergency personnel in the field including dispatch information, incident information, current road network conditions, device status, and other supporting information.
emergency personnel input	User input from emergency personnel in the field including dispatch coordination, incident status information, and remote device control requests.
emergency traffic control information	Status of a special traffic control strategy or system activation implemented in response to an emergency traffic control request, a request for emergency access routes, a request for evacuation, a request to activate closure systems, a request to employ driver information systems to support public safety objectives, or other special requests. Identifies the selected traffic control strategy and system control status.
emergency traffic control request	Special request to preempt the current traffic control strategy in effect at one or more signalized intersections or highway segments, activate traffic control and closure systems such as gates and barriers, activate safeguard systems, or use driver information systems. For example, this flow can request all signals to red-flash, request a progression of traffic control preemptions along an emergency vehicle route, request a specific evacuation traffic control plan, request activation of a road closure barrier system, or place a public safety or emergency-related message on a dynamic message sign.
emergency vehicle tracking data	The current location and operating status of the emergency vehicle.
host emergency vehicle status	Information provided to the Connected Vehicle on-board equipment from other systems on the Emergency Vehicle Platform.
intersection control status	Status data provided by the traffic signal controller including phase information, alarm status, and priority/preempt status.
intersection status	Current signal phase and timing information for all lanes at a signalized intersection. This flow identifies active lanes and lanes that are being stopped and specifies the length of time that the current state will persist for each lane. It also identifies signal priority and preemption status and pedestrian crossing status information where applicable.
local signal preemption request	Direct control signal or message to a signalized intersection that results in preemption of the current control plan and grants right-of-way to the requesting vehicle.
right-of-way request notification	Notice that a request has occurred for signal prioritization, signal preemption, pedestrian call, multi-modal crossing activation, or other source for right-of-way.
signal control commands	Control of traffic signal controllers or field masters including clock synchronization.
signal control status	Operational and status data of traffic signal control equipment including operating condition and current indications.
signal preemption request	Direct request for preemption to a traffic signal controller that results in preemption of the current control plan and grants right-of-way to the requesting vehicle. This flow identifies the required phase and timing of the preemption. This flow may also cancel the preemption request (e.g., when the requesting vehicle clears the intersection).
suggested route	Suggested route for a dispatched emergency or maintenance vehicle that may reflect current network conditions and the additional routing options available to en route emergency or maintenance vehicles that are not available to the general public.
vehicle location and motion	Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size.

Application Interconnect Diagram

This is one way this application may be realized, but not the only way. There are other ways to build a given application and accomplish a stated objective.

The application interconnect diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagram
PNG Diagram

Application Triples

Communications Diagram(s)	Source	Destination	Information Flow
	Emergency Management Center	Traffic Management Center	emergency traffic control request
	Emergency Management Center	Emergency Vehicle OBE	suggested route
None: Human interface	Emergency Personnel	Emergency Vehicle OBE	emergency personnel input
	Emergency Vehicle Databus	Emergency Vehicle OBE	host emergency vehicle status
None: Human interface	Emergency Vehicle OBE	Emergency Personnel	emergency personnel information presentation
	Emergency Vehicle OBE	Emergency Management Center	emergency vehicle tracking data
	Emergency Vehicle OBE	Roadside Equipment	local signal preemption request
	Emergency Vehicle OBE	Roadside Equipment	vehicle location and motion
None: Human interface	ITS Roadway Equipment	Emergency Personnel	driver information
	ITS Roadway Equipment	Roadside Equipment	intersection control status
	ITS Roadway Equipment	Traffic Management Center	right-of-way request notification
	ITS Roadway Equipment	Traffic Management Center	signal control status
	Roadside Equipment	Emergency Vehicle OBE	intersection status
	Roadside Equipment	ITS Roadway Equipment	signal preemption request
	Traffic Management Center	Emergency Management Center	emergency traffic control information
	Traffic Management Center	ITS Roadway Equipment	signal control commands

Requirements

Need		Requirement
N2.056	The Emergency Vehicle Preemption System needs to collect data for traffic signal system optimization for emergency vehicles.	2.131	The Emergency Vehicle Preemption System shall collect traffic data (e.g., volume, speed, occupancy, vehicle classification, incidents) for signalized intersections.
N2.057	The Emergency Vehicle Preemption System needs to collect data from emergency vehicles.	2.132	The Emergency Vehicle Preemption System shall collect emergency vehicle data (e.g., characteristics, position, route).
N2.058	The Emergency Vehicle Preemption System needs to process traffic and emergency vehicle data in order to provide emergency vehicle signal priority.	2.133	The Emergency Vehicle Signal Preemption System shall process traffic and emergency vehicle data in support of emergency vehicle signal priority.
N2.059	The Emergency Vehicle Preemption System needs to send emergency vehicle signal priority commands to the intersection.	2.134	The Emergency Vehicle Preemption System shall send weighted emergency vehicle signal priority commands to the intersection.

Related Sources

Multi-Modal Intelligent Traffic Signal System (MMITSS) ConOps, Draft v2.0, 9/14/2012
Multi-Modal Intelligent Traffic Signal System Final System Requirements Document, Final, 3/7/2013
Multi-Modal Intelligent Traffic Signal System- System Design, Fi nal, 6/26/2013

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
Emergency Management Center	Moderate	High	Moderate	Class 3
Emergency Personnel
Emergency Vehicle Databus
Emergency Vehicle OBE	Moderate	High	Moderate	Class 3
ITS Roadway Equipment	Low	High	Moderate	Class 3
Roadside Equipment	Low	High	Moderate	Class 3
Traffic Management Center	Moderate	High	Moderate	Class 3

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
Emergency Management Center	Emergency Vehicle OBE	suggested route	Moderate	High	Moderate
Emergency Management Center	Emergency Vehicle OBE	suggested route	It is important for this route to be kept confidential to prevent everyone from attempting to travel this route.	The emergency vehicle must receive an accurate Suggested Route. If the emergency vehicle is dispatched to an incorrect location it could lead to a significant delay in the vehicle responding to the emergency. This delay could lead to the loss of life or limb of a person. Therefore, if received, the suggested route must be trustworthy.	The alternative to use of a Suggested Route is that drivers select the route themselves. Without the Suggested Route the driver may get stuck in traffic or behind an accident that slows down their response time. This is a degradation of the business service being provided, and could lead to an emergency vehicle not responding to an incident in the quickest manner.
Emergency Management Center	Traffic Management Center	emergency traffic control request	Moderate	High	Moderate
Emergency Management Center	Traffic Management Center	emergency traffic control request	These requests could be used to track the specific route that an emergency vehicle is planning on taking.	False requests here could bring the traffic system to a standstill by making all of the lights red. Additionally, the system must be able to trust these requests, and know that they came from an authorized source.	These messages are important for the system to operate properly. Additionally, the system must know if messages are not received so that it can act accordingly.
Emergency Personnel	Emergency Vehicle OBE	emergency personnel input	Moderate	Moderate	Moderate
Emergency Personnel	Emergency Vehicle OBE	emergency personnel input	Some of the information, such as incident status information, is sensitive, and should be protected.	The system must know that these requests came from actual Emergency Personal. Additionally, incorrect information here may lead to the system responding incorrectly to the incident	These messages are important for the system to operate properly. Additionally, the system must know if messages are not received so that it can act accordingly.
Emergency Vehicle Databus	Emergency Vehicle OBE	host emergency vehicle status	Moderate	Moderate	Moderate
Emergency Vehicle Databus	Emergency Vehicle OBE	host emergency vehicle status	This could contain sensitive or proprietary information.	This is where the Emergency Vehicle OBE acquires GPS information, etc. This information is used elsewhere, leading to this rating.	This information needs to be mostly available to the system for this application to work.
Emergency Vehicle OBE	Emergency Management Center	emergency vehicle tracking data	Moderate	Moderate	Moderate
Emergency Vehicle OBE	Emergency Management Center	emergency vehicle tracking data	Emergency Vehicles give obvious visual and audio indicators about their location and operating status.	This information may be used to determine which emergency vehicle is dispatched, and having this information available could lead to a quicker response from the emergency vehicle.	This information may be used to determine which emergency vehicle is dispatched, and having this information available could lead to a quicker response from the emergency vehicle.
Emergency Vehicle OBE	Emergency Personnel	emergency personnel information presentation	Moderate	Moderate	Moderate
Emergency Vehicle OBE	Emergency Personnel	emergency personnel information presentation	Some of this information, such as incident information, is sensitive and should be protected.	This information could affect how the Emergency Personnel respond to the event, and should be as accurate as possible.	This information needs to be available for the Emergency Personnel in order for them to respond accurately to the system. If they do not acknowledge this information, dispatch needs to know, so they can attempt to contact the Emergency Personnel via another channel, such as radio.
Emergency Vehicle OBE	Roadside Equipment	local signal preemption request	Not Applicable	High	Moderate
Emergency Vehicle OBE	Roadside Equipment	local signal preemption request	It does not matter if someone is able to eavesdrop on this request. There will be many other more obvious indicators that the request was made, such as sirens and flashing lights on the emergency vehicle.	The system must be able to trust these requests. Emergency Vehicles should be able to send these requests and know that they are being operated on by the receiving system. Additionally, if an unauthorized vehicle is able to send these requests it could bring traffic to a standstill by disrupting signal coordination citywide.	The alternative to this request is existing mechanisms – such as using the sirens to stop traffic. The difference between the emergency signal preemption application and existing practice is not significant enough to justify a HIGH availability requirement.
Emergency Vehicle OBE	Roadside Equipment	vehicle location and motion	Low	Moderate	Moderate
Emergency Vehicle OBE	Roadside Equipment	vehicle location and motion	The location and motion information can be directly observable by monitoring the intersection. As such there is no issue with this being accessible by everyone in the area.	Incorrect information could lead to the system not operating properly. If the system does not properly know where the emergency vehicle is coming from and where it is heading, the system could incorrectly route traffic in an attempt to speed up the emergency vehicle. If it is making logic decisions based on incorrect data, this could prevent the emergency vehicle from navigating through the intersection quickly.	This data is required for the Emergency Vehicle Preemption to operate properly. If this data is not available, the emergency vehicle may not be able to travel through the intersection quickly enough. If an emergency vehicle is not able to get through the intersection quickly enough, it could prevent them from responding to the emergency in a timely manner. As discussed above, the difference between success and failure of this application is not catastrophic, but it is significant, so a moderate availability rating seems appropriate.
ITS Roadway Equipment	Emergency Personnel	driver information	Not Applicable	High	High
ITS Roadway Equipment	Emergency Personnel	driver information	This data is intentionally transmitted to everyone via a broadcast.	This is the primary signal trusted by the driver to decide whether to go through the intersection and what speed to go through the intersection at; if it's wrong, accidents could happen.	If the lights are out you have to get a policeman to direct traffic – expensive and inefficient and may cause a cascading effect due to lack of coordination with other intersections.
ITS Roadway Equipment	Roadside Equipment	intersection control status	Low	Moderate	Moderate
ITS Roadway Equipment	Roadside Equipment	intersection control status	This data is intentionally transmitted to everyone via a broadcast. It can also be determined via other visual indicators.	The vehicle will do more harm than an ordinary car if it runs the lights, and the driver may be under pressure to go fast in order to meet scheduled service, so the risk and impact of accidents from invalid messages might be slightly higher than for ordinary cars; however, the drivers are trained professionals and the vehicles are large and easy to spot, and will have lights and sirens, lowering the risk of accidents. Overall we do not see sufficient justification to raise the integrity requirement to HIGH.	Without this data, the RSE cannot broadcast it. However, this data is semi-predictable, so a few missed messages will not have a significant impact. Additionally, there are other indicators (such as the lights themselves) of the intersection status.
ITS Roadway Equipment	Traffic Management Center	right-of-way request notification	Low	High	Moderate
ITS Roadway Equipment	Traffic Management Center	right-of-way request notification	This can be reasonably guessed based on observing the ITS RE's environment. It is obvious when an emergency vehicle approaches an intersection.	Invalid messages could lead to an unauthorized user gaining Emergency Vehicle Preemption. This could also be used to bring traffic to a standstill, which could lead to a financial impact on the community.	Even if all of the Right-of-way Requests are not passed along from an ITS RE, the intersection will still operate as normal. There are other existing methods to assist an Emergency Vehicle safely traveling through an intersection, such as lights and sirens, which prevent this from being a HIGH.
ITS Roadway Equipment	Traffic Management Center	signal control status	Low	Moderate	Moderate
ITS Roadway Equipment	Traffic Management Center	signal control status	The current conditions of an ITS RE are completely observable, by design.	This influences the TMC response to a right-of-way request. It should be as accurate as the right-of-way request themselves.	The TMC will need the current status of the ITS RE in order to make an educated decision. If it is unavailable, the system is unable to operate. However, a few missed messages will not have a catastrophic impact.
Roadside Equipment	Emergency Vehicle OBE	intersection status	Not Applicable	Moderate	Moderate
Roadside Equipment	Emergency Vehicle OBE	intersection status	This data is intentionally transmitted to everyone via a broadcast.	If an emergency vehicle approaches an intersection at HIGH speed and is informed that it's safe to proceed when in fact cars on the cross street are proceeding themselves, the emergency vehicle could run the lights and get into an accident. We consider this a higher risk than the risk that a typical driver will get into a serious accident because the emergency vehicle may well be going at a higher speed. However, emergency vehicle drivers are trained professionals, and the emergency vehicle will likely also have its siren on, alerting vehicles on the cross street, so even though the risk is slightly higher than for non-emergency vehicles we do not consider the risk to life and limb to be direct enough to justify a HIGH rating.	Compared to regular drivers, emergency vehicle drivers are assumed to be more alert and so are less likely to make bad driving decisions on the basis of missing messages; however, if they do make bad driving decisions, the consequences are more serious, so the overall requirement level stays at a MEDIUM.
Roadside Equipment	ITS Roadway Equipment	signal preemption request	Not Applicable	High	Moderate
Roadside Equipment	ITS Roadway Equipment	signal preemption request	It does not matter if someone is able to eavesdrop on this request. There will be many other more obvious indicators that the request was made, such as sirens and flashing lights on the emergency vehicle.	The system must be able to trust these requests. Emergency Vehicles should be able to send these requests and know that they are being operated on by the receiving system. Additionally, if an unauthorized vehicle is able to send these requests it could bring traffic to a standstill by disrupting signal coordination citywide.	The alternative to this request is existing mechanisms – such as using the sirens to stop traffic. The difference between the emergency signal preemption application and existing practice is not significant enough to justify a HIGH availability requirement.
Traffic Management Center	Emergency Management Center	emergency traffic control information	Moderate	High	Moderate
Traffic Management Center	Emergency Management Center	emergency traffic control information	This can potentially include sensitive information, such as response information to emergencies.	Invalid messages could lead to an unauthorized user gaining transit signal priority at an intersection. This could also be used to bring traffic to a standstill, which could lead to a large financial impact on the community.	These messages are important to help with the transit signal priority application. Without them, it will not work. However, if these signals are not received, the Emergency Vehicle can still navigate through the intersection using Lights and Sirens. The TMC should have an acknowledgement of the receipt of a message.
Traffic Management Center	ITS Roadway Equipment	signal control commands	Not Applicable	High	Moderate
Traffic Management Center	ITS Roadway Equipment	signal control commands	The result of this will be directly observable.	Invalid messages could lead to an unauthorized user gaining control of an intersection. This could also be used to bring traffic to a standstill, which could lead to a large financial impact on the community.	These messages are important to help with the preemption application. Without them, it will not work. However, if these signals are not received, the Emergency Vehicle can still navigate through the intersection using Lights and Sirens. The TMC should have an acknowledgement of the receipt of a message.