< < ST09 : ST10 : SU01 > >

ST10: Low Emissions Zone Management

The Low Emissions Zone Management service package supports the operation of a low emissions zone that is responsive to real-time traffic and environmental conditions. Low emissions zones are geographic areas that seek to restrict or deter access by specific categories of high-polluting vehicles into the area to improve the air quality within the geographic area. The service package uses data collected from vehicles using connected vehicle technologies and from roadside equipment as input to the system. The Low Emissions Zone Management service package supports the geo-fencing of a cordon that may be scalable and moveable (e.g., created for a day, removable, flexible in its boundaries) and would be less dependent on conventional ITS infrastructure. The service package would establish parameters including the types of vehicles permitted to enter the zone, exemptions for transit vehicles, emissions criteria for entering the zone, fees or incentives for vehicles based on emissions data collected from the vehicle, and geographic boundaries for the low emissions zone. The service package would also include electronic toll collection functions that support payments of fees or collection of incentives for registered vehicles using connected vehicle technologies. Finally, this service package provides information about the low emissions zone to traveler information centers, including information about criteria for entering the zone, expected fees and incentives, current and predicted traffic conditions, and geographic boundaries of the zone.

Relevant Regions: Australia, Canada, European Union, and United States

Enterprise

Development Stage Roles and Relationships

Installation Stage Roles and Relationships

Operations and Maintenance Stage Roles and Relationships
(hide)

Source Destination Role/Relationship
Connected Vehicle Roadside Equipment Maintainer Connected Vehicle Roadside Equipment Maintains
Connected Vehicle Roadside Equipment Manager Connected Vehicle Roadside Equipment Manages
Connected Vehicle Roadside Equipment Owner Connected Vehicle Roadside Equipment Maintainer System Maintenance Agreement
Connected Vehicle Roadside Equipment Owner Connected Vehicle Roadside Equipment Manager Operations Agreement
Connected Vehicle Roadside Equipment Owner Driver Application Usage Agreement
Connected Vehicle Roadside Equipment Owner Emissions Management Center Maintainer Maintenance Data Exchange Agreement
Connected Vehicle Roadside Equipment Owner Emissions Management Center Owner Information Exchange and Action Agreement
Connected Vehicle Roadside Equipment Owner Emissions Management Center User Service Usage Agreement
Connected Vehicle Roadside Equipment Owner Emissions Management Operator Application Usage Agreement
Connected Vehicle Roadside Equipment Owner ITS Roadway Equipment Maintainer Maintenance Data Exchange Agreement
Connected Vehicle Roadside Equipment Owner ITS Roadway Equipment Owner Information Exchange and Action Agreement
Connected Vehicle Roadside Equipment Owner ITS Roadway Equipment User Service Usage Agreement
Connected Vehicle Roadside Equipment Owner Traffic Management Center Maintainer Maintenance Data Exchange Agreement
Connected Vehicle Roadside Equipment Owner Traffic Management Center Owner Information Exchange and Action Agreement
Connected Vehicle Roadside Equipment Owner Traffic Management Center User Service Usage Agreement
Connected Vehicle Roadside Equipment Owner Traffic Operations Personnel Application Usage Agreement
Connected Vehicle Roadside Equipment Owner Vehicle Maintainer Maintenance Data Exchange Agreement
Connected Vehicle Roadside Equipment Owner Vehicle Owner Information Exchange and Action Agreement
Connected Vehicle Roadside Equipment Owner Vehicle User Service Usage Agreement
Connected Vehicle Roadside Equipment Supplier Connected Vehicle Roadside Equipment Owner Warranty
DMV Maintainer DMV Maintains
DMV Manager DMV Manages
DMV Owner DMV Maintainer System Maintenance Agreement
DMV Owner DMV Manager Operations Agreement
DMV Owner Payment Administration Center Maintainer Maintenance Data Exchange Agreement
DMV Owner Payment Administration Center Owner Information Exchange Agreement
DMV Owner Payment Administration Center User Service Usage Agreement
DMV Owner Payment Administrator Application Usage Agreement
DMV Supplier DMV Owner Warranty
Driver Vehicle Operates
Emissions Management Center Maintainer Emissions Management Center Maintains
Emissions Management Center Manager Emissions Management Center Manages
Emissions Management Center Manager Emissions Management Operator System Usage Agreement
Emissions Management Center Owner Connected Vehicle Roadside Equipment Maintainer Maintenance Data Exchange Agreement
Emissions Management Center Owner Connected Vehicle Roadside Equipment Owner Information Provision Agreement
Emissions Management Center Owner Connected Vehicle Roadside Equipment User Service Usage Agreement
Emissions Management Center Owner Emissions Management Center Maintainer System Maintenance Agreement
Emissions Management Center Owner Emissions Management Center Manager Operations Agreement
Emissions Management Center Owner Enforcement Center Maintainer Maintenance Data Exchange Agreement
Emissions Management Center Owner Enforcement Center Owner Information Provision Agreement
Emissions Management Center Owner Enforcement Center User Service Usage Agreement
Emissions Management Center Owner Event Promoter System Maintainer Maintenance Data Exchange Agreement
Emissions Management Center Owner Event Promoter System Owner Information Exchange Agreement
Emissions Management Center Owner Event Promoter System User Service Usage Agreement
Emissions Management Center Owner ITS Roadway Equipment Maintainer Maintenance Data Exchange Agreement
Emissions Management Center Owner ITS Roadway Equipment Owner Information Provision Agreement
Emissions Management Center Owner ITS Roadway Equipment User Service Usage Agreement
Emissions Management Center Owner Payment Administration Center Maintainer Maintenance Data Exchange Agreement
Emissions Management Center Owner Payment Administration Center Owner Information Exchange Agreement
Emissions Management Center Owner Payment Administration Center User Service Usage Agreement
Emissions Management Center Owner Payment Administrator Application Usage Agreement
Emissions Management Center Owner Traffic Management Center Maintainer Maintenance Data Exchange Agreement
Emissions Management Center Owner Traffic Management Center Owner Information Exchange Agreement
Emissions Management Center Owner Traffic Management Center User Service Usage Agreement
Emissions Management Center Owner Traffic Operations Personnel Application Usage Agreement
Emissions Management Center Owner Transit Management Center Maintainer Maintenance Data Exchange Agreement
Emissions Management Center Owner Transit Management Center Owner Information Exchange Agreement
Emissions Management Center Owner Transit Management Center User Service Usage Agreement
Emissions Management Center Owner Transportation Information Center Maintainer Maintenance Data Exchange Agreement
Emissions Management Center Owner Transportation Information Center Owner Information Provision Agreement
Emissions Management Center Owner Transportation Information Center User Service Usage Agreement
Emissions Management Center Supplier Emissions Management Center Owner Warranty
Emissions Management Operator Emissions Management Center Operates
Enforcement Center Maintainer Enforcement Center Maintains
Enforcement Center Manager Enforcement Center Manages
Enforcement Center Owner Enforcement Center Maintainer System Maintenance Agreement
Enforcement Center Owner Enforcement Center Manager Operations Agreement
Enforcement Center Supplier Enforcement Center Owner Warranty
Event Promoter System Maintainer Event Promoter System Maintains
Event Promoter System Manager Event Promoter System Manages
Event Promoter System Owner Emissions Management Center Maintainer Maintenance Data Exchange Agreement
Event Promoter System Owner Emissions Management Center Owner Information Exchange Agreement
Event Promoter System Owner Emissions Management Center User Service Usage Agreement
Event Promoter System Owner Emissions Management Operator Application Usage Agreement
Event Promoter System Owner Event Promoter System Maintainer System Maintenance Agreement
Event Promoter System Owner Event Promoter System Manager Operations Agreement
Event Promoter System Owner Traffic Management Center Maintainer Maintenance Data Exchange Agreement
Event Promoter System Owner Traffic Management Center Owner Information Exchange Agreement
Event Promoter System Owner Traffic Management Center User Service Usage Agreement
Event Promoter System Owner Traffic Operations Personnel Application Usage Agreement
Event Promoter System Supplier Event Promoter System Owner Warranty
Financial Center Maintainer Financial Center Maintains
Financial Center Manager Financial Center Manages
Financial Center Owner Financial Center Maintainer System Maintenance Agreement
Financial Center Owner Financial Center Manager Operations Agreement
Financial Center Owner Payment Administration Center Maintainer Maintenance Data Exchange Agreement
Financial Center Owner Payment Administration Center Owner Information Exchange Agreement
Financial Center Owner Payment Administration Center User Service Usage Agreement
Financial Center Owner Payment Administrator Application Usage Agreement
Financial Center Supplier Financial Center Owner Warranty
ITS Roadway Equipment Maintainer ITS Roadway Equipment Maintains
ITS Roadway Equipment Manager ITS Roadway Equipment Manages
ITS Roadway Equipment Owner Connected Vehicle Roadside Equipment Maintainer Maintenance Data Exchange Agreement
ITS Roadway Equipment Owner Connected Vehicle Roadside Equipment Owner Information Exchange and Action Agreement
ITS Roadway Equipment Owner Connected Vehicle Roadside Equipment User Service Usage Agreement
ITS Roadway Equipment Owner Emissions Management Center Maintainer Maintenance Data Exchange Agreement
ITS Roadway Equipment Owner Emissions Management Center Owner Information Exchange and Action Agreement
ITS Roadway Equipment Owner Emissions Management Center User Service Usage Agreement
ITS Roadway Equipment Owner Emissions Management Operator Application Usage Agreement
ITS Roadway Equipment Owner ITS Roadway Equipment Maintainer System Maintenance Agreement
ITS Roadway Equipment Owner ITS Roadway Equipment Manager Operations Agreement
ITS Roadway Equipment Owner Traffic Management Center Maintainer Maintenance Data Exchange Agreement
ITS Roadway Equipment Owner Traffic Management Center Owner Information Exchange and Action Agreement
ITS Roadway Equipment Owner Traffic Management Center User Service Usage Agreement
ITS Roadway Equipment Owner Traffic Operations Personnel Application Usage Agreement
ITS Roadway Equipment Supplier ITS Roadway Equipment Owner Warranty
ITS Roadway Payment Equipment Maintainer ITS Roadway Payment Equipment Maintains
ITS Roadway Payment Equipment Manager ITS Roadway Payment Equipment Manages
ITS Roadway Payment Equipment Manager Light Vehicle Driver System Usage Agreement
ITS Roadway Payment Equipment Owner ITS Roadway Payment Equipment Maintainer System Maintenance Agreement
ITS Roadway Payment Equipment Owner ITS Roadway Payment Equipment Manager Operations Agreement
ITS Roadway Payment Equipment Owner Light Vehicle Driver Application Usage Agreement
ITS Roadway Payment Equipment Owner Light Vehicle OBE Maintainer Maintenance Data Exchange Agreement
ITS Roadway Payment Equipment Owner Light Vehicle OBE Owner Information Exchange and Action Agreement
ITS Roadway Payment Equipment Owner Light Vehicle OBE User Service Usage Agreement
ITS Roadway Payment Equipment Owner Payment Administration Center Maintainer Maintenance Data Exchange Agreement
ITS Roadway Payment Equipment Owner Payment Administration Center Owner Information Exchange and Action Agreement
ITS Roadway Payment Equipment Owner Payment Administration Center User Service Usage Agreement
ITS Roadway Payment Equipment Owner Payment Administrator Application Usage Agreement
ITS Roadway Payment Equipment Supplier ITS Roadway Payment Equipment Owner Warranty
Light Vehicle Driver ITS Roadway Payment Equipment Operates
Light Vehicle Driver Light Vehicle OBE Operates
Light Vehicle OBE Maintainer Light Vehicle OBE Maintains
Light Vehicle OBE Manager Light Vehicle Driver System Usage Agreement
Light Vehicle OBE Manager Light Vehicle OBE Manages
Light Vehicle OBE Owner ITS Roadway Payment Equipment Maintainer Maintenance Data Exchange Agreement
Light Vehicle OBE Owner ITS Roadway Payment Equipment Owner Expectation of Data Provision
Light Vehicle OBE Owner ITS Roadway Payment Equipment User Service Usage Agreement
Light Vehicle OBE Owner Light Vehicle Driver Application Usage Agreement
Light Vehicle OBE Owner Light Vehicle Driver Vehicle Operating Agreement
Light Vehicle OBE Owner Light Vehicle OBE Maintainer System Maintenance Agreement
Light Vehicle OBE Owner Light Vehicle OBE Manager Operations Agreement
Light Vehicle OBE Owner Payment Administration Center Maintainer Maintenance Data Exchange Agreement
Light Vehicle OBE Owner Payment Administration Center Owner Expectation of Data Provision
Light Vehicle OBE Owner Payment Administration Center User Service Usage Agreement
Light Vehicle OBE Owner Payment Administrator Application Usage Agreement
Light Vehicle OBE Owner Payment Administrator Vehicle Operating Agreement
Light Vehicle OBE Owner Payment Device Maintainer Maintenance Data Exchange Agreement
Light Vehicle OBE Owner Payment Device Owner Expectation of Data Provision
Light Vehicle OBE Owner Payment Device User Service Usage Agreement
Light Vehicle OBE Supplier Light Vehicle OBE Owner Warranty
Other Payment Administration Centers Maintainer Other Payment Administration Centers Maintains
Other Payment Administration Centers Manager Other Payment Administration Centers Manages
Other Payment Administration Centers Owner Other Payment Administration Centers Maintainer System Maintenance Agreement
Other Payment Administration Centers Owner Other Payment Administration Centers Manager Operations Agreement
Other Payment Administration Centers Owner Payment Administration Center Maintainer Maintenance Data Exchange Agreement
Other Payment Administration Centers Owner Payment Administration Center Owner Information Exchange Agreement
Other Payment Administration Centers Owner Payment Administration Center User Service Usage Agreement
Other Payment Administration Centers Owner Payment Administrator Application Usage Agreement
Other Payment Administration Centers Supplier Other Payment Administration Centers Owner Warranty
Payment Administration Center Maintainer Payment Administration Center Maintains
Payment Administration Center Manager Payment Administration Center Manages
Payment Administration Center Manager Payment Administrator System Usage Agreement
Payment Administration Center Owner DMV Maintainer Maintenance Data Exchange Agreement
Payment Administration Center Owner DMV Owner Information Exchange Agreement
Payment Administration Center Owner DMV User Service Usage Agreement
Payment Administration Center Owner Emissions Management Center Maintainer Maintenance Data Exchange Agreement
Payment Administration Center Owner Emissions Management Center Owner Information Exchange Agreement
Payment Administration Center Owner Emissions Management Center User Service Usage Agreement
Payment Administration Center Owner Emissions Management Operator Application Usage Agreement
Payment Administration Center Owner Enforcement Center Maintainer Maintenance Data Exchange Agreement
Payment Administration Center Owner Enforcement Center Owner Information Provision Agreement
Payment Administration Center Owner Enforcement Center User Service Usage Agreement
Payment Administration Center Owner Financial Center Maintainer Maintenance Data Exchange Agreement
Payment Administration Center Owner Financial Center Owner Information Exchange Agreement
Payment Administration Center Owner Financial Center User Service Usage Agreement
Payment Administration Center Owner ITS Roadway Payment Equipment Maintainer Maintenance Data Exchange Agreement
Payment Administration Center Owner ITS Roadway Payment Equipment Owner Information Provision Agreement
Payment Administration Center Owner ITS Roadway Payment Equipment User Service Usage Agreement
Payment Administration Center Owner Light Vehicle Driver Application Usage Agreement
Payment Administration Center Owner Light Vehicle OBE Maintainer Maintenance Data Exchange Agreement
Payment Administration Center Owner Light Vehicle OBE Owner Information Provision Agreement
Payment Administration Center Owner Light Vehicle OBE User Service Usage Agreement
Payment Administration Center Owner Other Payment Administration Centers Maintainer Maintenance Data Exchange Agreement
Payment Administration Center Owner Other Payment Administration Centers Owner Information Exchange Agreement
Payment Administration Center Owner Other Payment Administration Centers User Service Usage Agreement
Payment Administration Center Owner Payment Administration Center Maintainer System Maintenance Agreement
Payment Administration Center Owner Payment Administration Center Manager Operations Agreement
Payment Administration Center Owner Personal Information Device Maintainer Maintenance Data Exchange Agreement
Payment Administration Center Owner Personal Information Device Owner Information Provision Agreement
Payment Administration Center Owner Personal Information Device User Service Usage Agreement
Payment Administration Center Supplier Payment Administration Center Owner Warranty
Payment Administrator Payment Administration Center Operates
Payment Device Maintainer Payment Device Maintains
Payment Device Manager Payment Device Manages
Payment Device Owner Light Vehicle Driver Application Usage Agreement
Payment Device Owner Light Vehicle OBE Maintainer Maintenance Data Exchange Agreement
Payment Device Owner Light Vehicle OBE Owner Information Provision and Action Agreement
Payment Device Owner Light Vehicle OBE User Service Usage Agreement
Payment Device Owner Payment Device Maintainer System Maintenance Agreement
Payment Device Owner Payment Device Manager Operations Agreement
Payment Device Supplier Payment Device Owner Warranty
Personal Information Device Maintainer Personal Information Device Maintains
Personal Information Device Manager Personal Information Device Manages
Personal Information Device Owner Payment Administration Center Maintainer Maintenance Data Exchange Agreement
Personal Information Device Owner Payment Administration Center Owner Information Provision and Action Agreement
Personal Information Device Owner Payment Administration Center User Service Usage Agreement
Personal Information Device Owner Payment Administrator Application Usage Agreement
Personal Information Device Owner Personal Information Device Maintainer System Maintenance Agreement
Personal Information Device Owner Personal Information Device Manager Operations Agreement
Personal Information Device Supplier Personal Information Device Owner Warranty
Traffic Management Center Maintainer Traffic Management Center Maintains
Traffic Management Center Manager Traffic Management Center Manages
Traffic Management Center Manager Traffic Operations Personnel System Usage Agreement
Traffic Management Center Owner Connected Vehicle Roadside Equipment Maintainer Maintenance Data Exchange Agreement
Traffic Management Center Owner Connected Vehicle Roadside Equipment Owner Information Provision Agreement
Traffic Management Center Owner Connected Vehicle Roadside Equipment User Service Usage Agreement
Traffic Management Center Owner Emissions Management Center Maintainer Maintenance Data Exchange Agreement
Traffic Management Center Owner Emissions Management Center Owner Information Exchange Agreement
Traffic Management Center Owner Emissions Management Center User Service Usage Agreement
Traffic Management Center Owner Emissions Management Operator Application Usage Agreement
Traffic Management Center Owner Event Promoter System Maintainer Maintenance Data Exchange Agreement
Traffic Management Center Owner Event Promoter System Owner Information Exchange Agreement
Traffic Management Center Owner Event Promoter System User Service Usage Agreement
Traffic Management Center Owner ITS Roadway Equipment Maintainer Maintenance Data Exchange Agreement
Traffic Management Center Owner ITS Roadway Equipment Owner Information Provision Agreement
Traffic Management Center Owner ITS Roadway Equipment User Service Usage Agreement
Traffic Management Center Owner Traffic Management Center Maintainer System Maintenance Agreement
Traffic Management Center Owner Traffic Management Center Manager Operations Agreement
Traffic Management Center Supplier Traffic Management Center Owner Warranty
Traffic Operations Personnel Traffic Management Center Operates
Transit Management Center Maintainer Transit Management Center Maintains
Transit Management Center Manager Transit Management Center Manages
Transit Management Center Owner Emissions Management Center Maintainer Maintenance Data Exchange Agreement
Transit Management Center Owner Emissions Management Center Owner Information Exchange Agreement
Transit Management Center Owner Emissions Management Center User Service Usage Agreement
Transit Management Center Owner Emissions Management Operator Application Usage Agreement
Transit Management Center Owner Transit Management Center Maintainer System Maintenance Agreement
Transit Management Center Owner Transit Management Center Manager Operations Agreement
Transit Management Center Supplier Transit Management Center Owner Warranty
Transportation Information Center Maintainer Transportation Information Center Maintains
Transportation Information Center Manager Transportation Information Center Manages
Transportation Information Center Owner Transportation Information Center Maintainer System Maintenance Agreement
Transportation Information Center Owner Transportation Information Center Manager Operations Agreement
Transportation Information Center Supplier Transportation Information Center Owner Warranty
Vehicle Characteristics Maintainer Vehicle Characteristics Maintains
Vehicle Characteristics Manager Vehicle Characteristics Manages
Vehicle Characteristics Owner Vehicle Characteristics Maintainer System Maintenance Agreement
Vehicle Characteristics Owner Vehicle Characteristics Manager Operations Agreement
Vehicle Characteristics Supplier Vehicle Characteristics Owner Warranty
Vehicle Maintainer Vehicle Maintains
Vehicle Manager Driver System Usage Agreement
Vehicle Manager Vehicle Manages
Vehicle Owner Connected Vehicle Roadside Equipment Maintainer Maintenance Data Exchange Agreement
Vehicle Owner Connected Vehicle Roadside Equipment Owner Expectation of Data Provision
Vehicle Owner Connected Vehicle Roadside Equipment User Service Usage Agreement
Vehicle Owner Vehicle Maintainer System Maintenance Agreement
Vehicle Owner Vehicle Manager Operations Agreement
Vehicle Supplier Vehicle Owner Warranty
Weather Service System Maintainer Weather Service System Maintains
Weather Service System Manager Weather Service System Manages
Weather Service System Owner Emissions Management Center Maintainer Maintenance Data Exchange Agreement
Weather Service System Owner Emissions Management Center Owner Information Provision Agreement
Weather Service System Owner Emissions Management Center User Service Usage Agreement
Weather Service System Owner Emissions Management Operator Application Usage Agreement
Weather Service System Owner Weather Service System Maintainer System Maintenance Agreement
Weather Service System Owner Weather Service System Manager Operations Agreement
Weather Service System Supplier Weather Service System Owner Warranty

Functional

This service package includes the following Functional View PSpecs:

Physical Object Functional Object PSpec Number PSpec Name
Connected Vehicle Roadside Equipment RSE Emissions Monitoring 1.5.10 Collect Vehicle Emissions Messages
RSE Low Emissions Zone Application 1.1.1.6 Collect Vehicle Roadside Safety Data
1.5.10 Collect Vehicle Emissions Messages
1.5.12 Manage Eco Roadway Usage in Roadway
3.2.6 Manage Check-in and Check-out
3.2.8 Provide Automated Lane Changing
RSE Traffic Monitoring 1.1.2.6 Process Collected Vehicle Safety Data
1.1.6 Collect Vehicle Traffic Surveillance Data
1.1.7 Collect Vehicle Environmental Data
1.2.7.15 Process Intersection Safety Data
1.2.7.4 Process In-vehicle Signage Data
6.7.3.3 Provide Short Range Traveler Information
9.3.3.5 Manage Speeds at Roadside
RSE Traveler Information Communications 1.1.1.6 Collect Vehicle Roadside Safety Data
1.1.2.6 Process Collected Vehicle Safety Data
1.2.7.4 Process In-vehicle Signage Data
1.2.7.7 Process Vehicle Safety and Environmental Data for Output
1.5.10 Collect Vehicle Emissions Messages
2.8.4.6 Exchange Border Clearance Roadside Information
6.7.3.3 Provide Short Range Traveler Information
9.2.3.8 Collect Connected Vehicle Field Equipment Status
9.3.3.5 Manage Speeds at Roadside
Emissions Management Center Emissions Connected Vehicle Monitoring 1.5.1 Provide Emissions Operations Personnel Interface
1.5.11 Process Connected Vehicle Emissions Data
1.5.2 Process Pollution Data
1.5.3 Manage Pollution State Data Store
1.5.7 Manage Emissions and Pollution Reference Data Stores
1.5.8 Manage Emissions Archive Data
1.5.9 Manage Emissions State Data Store
5.4.8 Process Emissions Violations
Emissions Data Management 1.5.1 Provide Emissions Operations Personnel Interface
1.5.11 Process Connected Vehicle Emissions Data
1.5.2 Process Pollution Data
1.5.3 Manage Pollution State Data Store
1.5.6 Process Vehicle Emissions Data
1.5.7 Manage Emissions and Pollution Reference Data Stores
1.5.9 Manage Emissions State Data Store
5.4.8 Process Emissions Violations
Emissions Zone Management 1.5.1 Provide Emissions Operations Personnel Interface
1.5.2 Process Pollution Data
ITS Roadway Equipment Roadway Basic Surveillance 1.1.1.1 Process Traffic Sensor Data
1.1.1.7 Process Road User Protection
1.1.2.11 Control Dynamic Lanes
1.2.7.16 Process Signal Control Conflict Monitoring
1.2.7.2 Monitor Roadside Equipment Operation
1.2.7.8 Provide Device Interface to Other Roadway Devices
1.3.1.3 Process Traffic Images
9.2.3.6 Collect Field Equipment Status for Repair
9.3.3.1 Collect Vehicle Speed
Roadway Emissions Monitoring 1.2.7.2 Monitor Roadside Equipment Operation
1.2.7.8 Provide Device Interface to Other Roadway Devices
1.2.7.9 Process Roadway Information Data
1.5.4 Detect Vehicle Emissions Levels
1.5.5 Detect Pollution and Noise Levels
Roadway Traffic Information Dissemination 1.2.7.1 Process Indicator Output Data for Roads
1.2.7.2 Monitor Roadside Equipment Operation
1.2.7.5 Process Indicator Output Data for Freeways
1.2.7.8 Provide Device Interface to Other Roadway Devices
1.2.7.9 Process Roadway Information Data
ITS Roadway Payment Equipment Roadway Payment Support 7.1.1.1 Read Vehicle Payment Data for Tolls
7.1.1.10 Determine Advanced Toll Bill
7.1.1.2 Calculate Vehicle Toll
7.1.1.5 Bill Driver for Tolls
7.1.3 Obtain Toll Violator Image
7.6.1.3 Bill Driver for Road Use Charges
7.6.2 Support Road Use Charging
7.6.7 Collect Road Use Charging Equipment Status
Light Vehicle OBE Light Vehicle Payment Service 3.1.8 Process Light Vehicle Road Use Data
6.7.5.2 Provide Light Vehicle Driver with Personal Travel Information
6.7.5.3 Provide Light Vehicle Driver Information Interface
7.1.4 Provide Driver Toll Payment Interface
7.1.7 Provide Payment Device Interface for Tolls
7.2.3 Provide Driver Parking Lot Payment Interface
7.2.5 Provide Payment Device Interface for Parking
7.4.4.3 Process Vehicle Electric Charging Payments
7.5.1 Provide Vehicle Payment Device Interface
7.6.3 Provide Driver Road Use Charging Payment Interface
7.6.4 Provide Payment Device Interface for Road Use Charging
Payment Administration Center PAC Road Pricing Administration 7.6.1.2 Calculate Vehicle Road Use Payment Charges
7.6.1.4 Manage Road Use Charging Price Data
7.6.1.5 Manage Road Use Charges Processing
7.6.5 Exchange Road Use Charging Data with Other Payment Administration
7.6.6.1 Provide Road Use Charging Services User Interface
7.6.8 Provide Road Use Charging Enforcement Interface
Personal Information Device Personal Interactive Traveler Information 6.8.1.1.1 Determine Personal Portable Device Guidance Method
6.8.1.1.2 Provide Personal Portable Device Dynamic Guidance
6.8.3.1 Get Traveler Personal Request
6.8.3.2 Provide Traveler with Personal Travel Information
6.8.3.3 Provide Traveler Personal Interface
6.8.3.4 Update Traveler Personal Display Map Data
6.8.3.5 Provide Traveler Transit Services Interface
6.8.3.6 Provide Personal Safety Messages
6.8.3.7 Manage Traveler Personal Social Media Interface
7.5.3 Provide Personal Payment Device Interface
7.6.6.3 Provide Road Use Charging Services Personal Interface
Traffic Management Center TMC Basic Surveillance 1.1.2.1 Process Traffic Data for Storage
1.1.2.2 Process Traffic Data
1.1.2.3 Update Data Source Static Data
1.1.2.5 Process Vehicle Situation Data
1.1.2.8 Process Roadway Environmental Data
1.1.3 Generate Predictive Traffic Model
1.1.4.1 Retrieve Traffic Data
1.1.4.2 Provide Traffic Operations Personnel Traffic Data Interface
1.1.5 Exchange Data with Other Traffic Centers
1.2.6.1 Maintain Traffic and Sensor Static Data
1.2.8 Collect Traffic Field Equipment Fault Data
1.3.1.1 Analyze Traffic Data for Incidents
1.3.2.1 Store Possible Incident Data
1.3.2.5 Provide Current Incidents Store Interface
1.3.2.6 Manage Traffic Routing
1.3.4.2 Provide Traffic Operations Personnel Incident Interface
1.3.4.5 Process Video Data
TMC Incident Dispatch Coordination 1.1.4.1 Retrieve Traffic Data
1.1.5 Exchange Data with Other Traffic Centers
1.3.2.1 Store Possible Incident Data
1.3.2.2 Review and Classify Possible Incidents
1.3.2.3 Review and Classify Planned Events
1.3.2.6 Manage Traffic Routing
1.3.3.1 Respond to Current Incidents
1.3.4.1 Retrieve Incident Data
1.3.4.2 Provide Traffic Operations Personnel Incident Interface
1.3.4.3 Provide Media Incident Data Interface
1.3.4.4 Manage Resources for Incidents
1.3.5 Manage Incident Response Planning and Traffic Management Decision Support
1.3.6 Traffic Disaster Response Control
1.3.7 Traffic Evacuation Control
TMC In-Vehicle Signing Management 1.2.4.3 Output In-vehicle Signage Data
1.2.4.4 Output Roadway Information Data
1.2.8 Collect Traffic Field Equipment Fault Data
1.3.2.1 Store Possible Incident Data
1.5.13 Manage Emissions-Based Control Zone
TMC Traffic Information Dissemination 1.1.4.1 Retrieve Traffic Data
1.1.4.2 Provide Traffic Operations Personnel Traffic Data Interface
1.1.4.3 Provide Direct Media Traffic Data Interface
1.2.1 Select Strategy
1.2.4.3 Output In-vehicle Signage Data
1.2.4.4 Output Roadway Information Data
1.2.8 Collect Traffic Field Equipment Fault Data
1.3.1.1 Analyze Traffic Data for Incidents
1.3.2.1 Store Possible Incident Data
1.3.2.2 Review and Classify Possible Incidents
1.3.2.5 Provide Current Incidents Store Interface
1.3.2.6 Manage Traffic Routing
1.3.4.2 Provide Traffic Operations Personnel Incident Interface
1.3.4.5 Process Video Data
Transit Management Center Transit Center Multi-Modal Coordination 4.1.4 Collect and Process Transit Vehicle Data
4.1.5.1 Manage Transit Vehicle Operations
4.1.5.2 Manage Transit Vehicle Deviations
4.2.1.2 Generate Transit Schedules
4.2.1.3 Produce Transit Service Data for External Use
4.2.1.4 Provide Transit Operations Personnel Interface for Services Generation
4.2.1.7 Provide Interface for Other Transit Management Data
4.2.1.8 Provide Interface for Transit Service Raw Data
Transportation Information Center TIC Data Collection 6.2.1 Collect Misc Traveler Information
6.2.2 Collect Traffic Data
6.2.3 Collect Transit Operations Data
6.2.4 Collect Multimodal Data
6.2.5 Collect Situation and Sensor Data From Vehicles
6.2.6 Collect Emergency Traveler Data
6.5.4 Process Travel Services Provider Data
6.6.2.3 Provide Route Segment Data for Other Areas
7.4.2 Collect Price Data for Traveler Information Use
Vehicle Vehicle Basic Safety Communication 3.1.1 Produce Collision and Crash Avoidance Data
3.1.3 Process Vehicle On-board Data
3.1.4 Communicate with Remote Vehicles
3.1.6 Provide Vehicle Acceleration and Deceleration Inputs
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.2 Provide Driver Information Interface
Vehicle Eco-Driving Assist 3.1.3 Process Vehicle On-board Data
3.1.6 Provide Vehicle Acceleration and Deceleration Inputs
6.7.3.1 Provide Driver with Personal Travel Information
6.7.3.2 Provide Driver Information Interface
Vehicle Emissions Monitoring 3.1.3 Process Vehicle On-board Data
3.1.7 Process Vehicle Emissions Status
3.2.3.5.1 Process General Vehicle Sensor Data
6.7.1.4 Update Vehicle Navigable Map Database
Vehicle Traveler Information Reception 3.1.3 Process Vehicle On-board Data
3.1.4 Communicate with Remote Vehicles
3.2.3.3 Process Data for Vehicle Actuators
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 Diagrams: Low Emissions Zone Operations Fee Collection
PNG Diagrams: Low Emissions Zone Operations Fee Collection


Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object Class Description
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.
DMV Center The 'DMV' is a specific (state) public organization responsible for registering vehicles, e.g., the Department of Motor Vehicles.
Driver Vehicle The 'Driver' represents the person that operates a vehicle on the roadway. Included are operators of private, transit, commercial, and emergency vehicles where the interactions are not particular to the type of vehicle (e.g., interactions supporting vehicle safety applications). The Driver originates driver requests and receives driver information that reflects the interactions which might be useful to all drivers, regardless of vehicle classification. Information and interactions which are unique to drivers of a specific vehicle type (e.g., fleet interactions with transit, commercial, or emergency vehicle drivers) are covered by separate objects.
Emissions Management Center Center The 'Emissions Management Center' provides the capabilities for air quality managers to monitor and manage air quality. These capabilities include collecting emissions data from distributed emissions sensors (included in ITS Roadway Equipment) and directly from connected vehicles. The sensors monitor general air quality and also monitor the emissions of individual vehicles on the roadway. The measures are collected, processed, and used to support environmental monitoring applications.
Emissions Management Operator Center The 'Emissions Management Operator' represents personnel that monitor, operate, and manage emissions monitoring and management systems. These personnel monitor system operation and monitor collected emissions and air quality information and direct system operation through data and command inputs.
Enforcement Center Center The 'Enforcement Center' represents the systems that receive reports of violations detected by various ITS facilities including individual vehicle emissions, lane violations, toll violations, CVO violations, etc.
Event Promoter System Center 'Event Promoter System' represents Special Event Sponsors that have knowledge of events that may impact travel on roadways or other modal means. Examples of special event sponsors include sporting events, conventions, motorcades/parades, and public/political events. These promoters interface to the ITS to provide event information such as date, time, estimated duration, location, and any other information pertinent to traffic movement in the surrounding area.
Financial Center Center The 'Financial Center' represents the organization that handles electronic fund transfer requests to enable the transfer of funds from the user of the service to the provider of the service. The functions and activities of financial clearinghouses are covered by this physical object.
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. 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.
ITS Roadway Payment Equipment Field 'ITS Roadway Payment Equipment' represents the roadway components of a toll collection system. It provides the capability for vehicle operators to pay tolls without stopping their vehicles. It supports use of locally determined pricing structures and includes the capability to implement various variable pricing policies. Typically, transactions are accompanied by feedback to the customer and a record of the transactions is provided to a back office system (e.g., the Payment Administration Center).
Light Vehicle Driver Vehicle The 'Light Vehicle Driver' represents the person that operates a light vehicle on the roadway. This physical object covers the interactions that are specific to light, passenger vehicles. See also the 'Driver' physical object that covers interactions that are shared by operators of light, transit, commercial, and emergency vehicles where the interactions are not particular to the type of vehicle.
Light Vehicle OBE Vehicle The 'Light Vehicle OBE' includes traveler-oriented capabilities that apply to passenger cars, trucks, and motorcycles that are used for personal travel. The rules vary by jurisdiction, but generally light vehicles are restricted in their weight and the maximum number of passengers they can carry. In ARC-IT, the Light Vehicle OBE represents vehicles that are operated as personal vehicles that are not part of a vehicle fleet and are not used commercially; thus, the choice between the various vehicle subsystems should be based more on how the vehicle is used than how much the vehicle weighs. See also the 'Vehicle' subsystem that includes the general safety and information services that apply to all types of vehicles, including light vehicles.
Other Payment Administration Centers Center Representing another Payment Administration Center, 'Other Payment Administration Centers' is intended to provide a source and destination for ITS information flows between payment administration functions. This interface allows reconciliation of toll charges and other payments across different agencies by allowing the exchange of information about clients who have incurred charges in jurisdictions other than their own (billing) customer service center. This interface enables apportioning charges and 'reciprocity' between participating customer service centers.
Payment Administration Center Center The 'Payment Administration Center' provides general payment administration capabilities and supports the electronic transfer of funds from the customer to the transportation system operator or other service provider. Charges can be recorded for tolls, vehicle-mileage charging, congestion charging, or other goods and services. It supports traveler enrollment and collection of both pre-payment and post-payment transportation fees in coordination with the financial infrastructure supporting electronic payment transactions. The system may establish and administer escrow accounts depending on the clearinghouse scheme and the type of payments involved. It may post a transaction to the customer account, generate a bill (for post-payment accounts), debit an escrow account, or interface to a financial infrastructure to debit a customer designated account. It supports communications with the ITS Roadway Payment Equipment to support fee collection operations. As an alternative, a wide-area wireless interface can be used to communicate directly with vehicle equipment. It also sets and administers the pricing structures and may implement road pricing policies in coordination with the Traffic Management Center.
Payment Administrator Center The 'Payment Administrator' represents the person(s) that manage the back office payment administration systems for electronic toll, VMT road use payment, and other services paid for from a vehicle. It monitors the systems that support the electronic transfer of funds from the customer to the system operator. It monitors customer enrollment and supports the establishment of escrow accounts depending on the clearinghouse scheme and the type of payments involved. It also establishes and administers the pricing structures and policies.
Payment Device Personal The 'Payment Device' enables the electronic transfer of funds from the user of a service (I.e. a traveler) to the provider of the service. Potential implementations include smart cards that support payment for products and services, including transportation services and general purpose devices like smart phones that support a broad array of services, including electronic payment. In addition to user account information, the payment device may also hold and update associated user information such as personal profiles, preferences, and trip histories.
Personal Information Device Personal The 'Personal Information Device' provides the capability for travelers to receive formatted traveler information wherever they are. Capabilities include traveler information, trip planning, and route guidance. Frequently a smart phone, the Personal Information Device provides travelers with the capability to receive route planning and other personally focused transportation services from the infrastructure in the field, at home, at work, or while en-route. Personal Information Devices may operate independently or may be linked with vehicle on-board equipment. This subsystem also supports safety related services with the capability to broadcast safety messages and initiate a distress signal or request for help.
Traffic Management Center Center The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters.
Traffic Operations Personnel Center 'Traffic Operations Personnel' represents the people that operate a traffic management center. These personnel interact with traffic control systems, traffic surveillance systems, incident management systems, work zone management systems, and travel demand management systems. They provide operator data and command inputs to direct system operations to varying degrees depending on the type of system and the deployment scenario.
Transit Management Center Center The 'Transit Management Center' manages transit vehicle fleets and coordinates with other modes and transportation services. It provides operations, maintenance, customer information, planning and management functions for the transit property. It spans distinct central dispatch and garage management systems and supports the spectrum of fixed route, flexible route, paratransit services, transit rail, and bus rapid transit (BRT) service. The physical object's interfaces support communication between transit departments and with other operating entities such as emergency response services and traffic management systems.
Transportation Information Center Center The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service.
Vehicle 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, 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.
Vehicle Characteristics Vehicle 'Vehicle Characteristics' represents the external view of individual vehicles of any class from cars and light trucks up to large commercial vehicles and down to micromobility vehicles (MMVs). It includes vehicle physical characteristics such as height, width, length, weight, and other properties (e.g., magnetic properties, number of axles) of individual vehicles that can be sensed and measured or classified. This physical object represents the physical properties of vehicles that can be sensed by vehicle-based or infrastructure-based sensors to support vehicle automation and traffic sensor systems. The analog properties provided by this terminator represent the sensor inputs that are used to detect and assess vehicle(s) within the sensor's range to support safe AV operation and/or responsive and safe traffic management.
Weather Service System Center The 'Weather Service System' provides weather, hydrologic, and climate information and warnings of hazardous weather including thunderstorms, flooding, hurricanes, tornadoes, winter weather, tsunamis, and climate events. It provides atmospheric weather observations and forecasts that are collected and derived by the National Weather Service, private sector providers, and various research organizations. The interface provides formatted weather data products suitable for on-line processing and integration with other ITS data products as well as Doppler radar images, satellite images, severe storm warnings, and other products that are formatted for presentation to various ITS users.

Includes Functional Objects:

Functional Object Description Physical Object
Emissions Connected Vehicle Monitoring 'Emissions Connected Vehicle Monitoring' collects emissions data reported by passing vehicles and uses this data to support air quality management and planning. Coordination with traffic management supports air quality-responsive management of traffic. Emissions Management Center
Emissions Data Management 'Emissions Data Management' collects and stores air quality and vehicle emissions information by remotely monitoring and controlling area wide and point sensors. General air quality measures are distributed as general traveler information and also may be used in demand management programs. Collected roadside emissions are analyzed and used to detect, identify, and notify concerned parties regarding vehicles that exceed emissions standards. Emissions Management Center
Emissions Zone Management 'Emissions Zone Management' identifies existing and potential emissions hot spots and coordinates with transportation agencies and their systems to establish low emissions zones to manage air quality in these areas. Through this coordination, the geographic boundary, restrictions, and pricing for the low emissions zone are established and adjusted. Emissions Management Center
Light Vehicle Payment Service 'Light Vehicle Payment Service' supports vehicle payments including VMT- and zone-based payments and payments for other services including fuel/charging services, tolls, and parking. To support VMT-based payment, this application tracks the location of the vehicle at specific times and reports this VMT data along with vehicle identification. A variety of pricing strategies are supported, including strategies that include credits or incentives that reward desired driving patterns and behavior. The onboard equipment supports secure short range communications with connected vehicle roadside equipment to support secure payments. Light Vehicle OBE
PAC Road Pricing Administration 'PAC Road Pricing Administration' enables payment for road use based on VMT, vehicle type, vehicle emissions, or other parameters. It establishes a price schedule based on these parameters that may vary by time, location or zone, vehicle type, and/or vehicle behavior. Pricing strategies may also include incentives that allow reimbursement of fees previously paid for good behavior (e.g., VMT reductions, economical driving behavior, avoidance of peak periods or congested zones). It receives vehicle data (e.g., time stamped roadways used by the vehicle since the last transmission) and computes the total cost to the vehicle owner for payment. Based on owner preference, this cost is either billed to the owner or requested from an in-vehicle payment instrument. Payment for use of roadways not operated by the specific instance of the VMT Payment Administration that the vehicle is registered with, will be reconciled. Payment violations can be reported to Enforcement Agencies when appropriate. Finally, vehicle owners can interact with this object using personal devices or public terminals to setup and edit account preferences for owned vehicles, get account reports, and make payments. Payment Administration Center
Personal Interactive Traveler Information 'Personal Interactive Traveler Information' provides traffic information, road conditions, transit information, yellow pages (traveler services) information, special event information, and other traveler information that is specifically tailored based on the traveler's request and/or previously submitted traveler profile information. It also supports interactive services that support enrollment, account management, and payments for transportation services. The interactive traveler information capability is provided by personal devices including personal computers and personal portable devices such as smart phones. Personal Information Device
Roadway Basic Surveillance 'Roadway Basic Surveillance' monitors traffic conditions using fixed equipment such as loop detectors and CCTV cameras. ITS Roadway Equipment
Roadway Emissions Monitoring 'Roadway Emissions Monitoring' monitors emissions and general air quality and communicates the collected information back to the Emissions Management Center where it can be monitored, analyzed, and used. This functional object supports point monitoring of individual vehicle emissions as well as general monitoring of standard air quality measures. ITS Roadway Equipment
Roadway Payment Support 'Roadway Payment Support' represents the equipment that works in conjunction with the RSE to detect vehicles and identify and process violators when the RSE is used to support electronic payment. Various fee structures and payment strategies are supported including strategies that support reimbursements or credits that incentivize desired driving behavior. ITS Roadway Payment Equipment
Roadway Traffic Information Dissemination 'Roadway Traffic Information Dissemination' includes field elements that provide information to drivers, including dynamic message signs and highway advisory radios. ITS Roadway Equipment
RSE Emissions Monitoring 'RSE Emissions Monitoring' collects emissions data from passing vehicles that are equipped with short range communications capability and have the capability to collect and report emissions data. The collected data includes current emissions as measured or calculated by on-board equipment. The functional object collects the provided data, aggregates and filters the data based on provided configuration parameters, and sends the collected information back to a center for processing and distribution. Connected Vehicle Roadside Equipment
RSE Low Emissions Zone Application 'RSE Low Emissions Zone Application' provides information to vehicles regarding low emissions zones and checks vehicle profiles on entry to a designated low emissions zone to verify they are in compliance with the parameters established for the zone. Connected Vehicle Roadside Equipment
RSE Traffic Monitoring 'RSE Traffic Monitoring' monitors the basic safety messages that are shared between connected vehicles and distills this data into traffic flow measures that can be used to manage the network in combination with or in lieu of traffic data collected by infrastructure-based sensors. As connected vehicle penetration rates increase, the measures provided by this application can expand beyond vehicle speeds that are directly reported by vehicles to include estimated volume, occupancy, and other measures. This object also supports incident detection by monitoring for changes in speed and vehicle control events that indicate a potential incident. Connected Vehicle Roadside Equipment
RSE Traveler Information Communications 'RSE Traveler Information Communications' includes field elements that distribute information to vehicles for in-vehicle display. The information may be provided by a center (e.g., variable information on traffic and road conditions in the vicinity of the field equipment) or it may be determined and output locally (e.g., static sign information and signal phase and timing information). This includes the interface to the center or field equipment that controls the information distribution and the short range communications equipment that provides information to passing vehicles. Connected Vehicle Roadside Equipment
TIC Data Collection 'TIC Data Collection' collects transportation-related data from other centers, performs data quality checks on the collected data and then consolidates, verifies, and refines the data and makes it available in a consistent format to applications that support operational data sharing between centers and deliver traveler information to end-users. A broad range of data is collected including traffic and road conditions, transit data, emergency information and advisories, weather data, special event information, traveler services, parking, multimodal data, and toll/pricing data. It also shares data with other transportation information centers. Transportation Information Center
TMC Basic Surveillance 'TMC Basic Surveillance' remotely monitors and controls traffic sensor systems and surveillance (e.g., CCTV) equipment, and collects, processes and stores the collected traffic data. Current traffic information and other real-time transportation information is also collected from other centers. The collected information is provided to traffic operations personnel and made available to other centers. Traffic Management Center
TMC Incident Dispatch Coordination 'TMC Incident Dispatch Coordination' formulates and manages an incident response that takes into account the incident potential, incident impacts, and resources required for incident management. It provides information to support dispatch and routing of emergency response and service vehicles as well as coordination with other cooperating agencies. It provides access to traffic management resources that provide surveillance of the incident, traffic control in the surrounding area, and support for the incident response. It monitors the incident response and collects performance measures such as incident response and clearance times. Traffic Management Center
TMC In-Vehicle Signing Management 'TMC In-Vehicle Signing Management' controls and monitors RSEs that support in-vehicle signing. Sign information that may include static regulatory, service, and directional sign information as well as variable information such as traffic and road conditions can be provided to the RSE, which uses short range communications to send the information to in-vehicle equipment. Information that is currently being communicated to passing vehicles and the operational status of the field equipment is monitored by this application. The operational status of the field equipment is reported to operations personnel. Traffic Management Center
TMC Traffic Information Dissemination 'TMC Traffic Information Dissemination' disseminates traffic and road conditions, closure and detour information, incident information, driver advisories, and other traffic-related data to other centers, the media, and driver information systems. It monitors and controls driver information system field equipment including dynamic message signs and highway advisory radio, managing dissemination of driver information through these systems. Traffic Management Center
Transit Center Multi-Modal Coordination 'Transit Center Multi-Modal Coordination' supports transit service coordination between transit properties and coordinates with other surface and air transportation modes. As part of service coordination, it shares schedule and trip information, as well as transit transfer cluster (a collection of stop points, stations, or terminals where transfers can be made conveniently) and transfer point information between Multimodal Transportation Service Providers, Transit Agencies, and ISPs. An interface to Traffic Management also supports demand management strategies. Transit Management Center
Vehicle Basic Safety Communication 'Vehicle Basic Safety Communication' exchanges current vehicle characteristics, location, and motion (including past and intended maneuver) information with other vehicles in the vicinity, uses that information to calculate vehicle paths, and warns the driver when the potential for an impending collision is detected. If available, map data is used to filter and interpret the relative location and motion of vehicles in the vicinity. Information from on-board sensors (e.g., radars and image processing) are also used, if available, in combination with the V2V communications to detect non-equipped vehicles and corroborate connected vehicle data. This object represents a broad range of implementations ranging from basic Vehicle Awareness Devices that only broadcast vehicle location and motion and provide no driver warnings to advanced integrated safety systems that coordinate maneuvers and may, in addition to warning the driver, provide collision warning information to support automated control functions that can support control intervention. Vehicle
Vehicle Eco-Driving Assist 'Vehicle Eco-Driving Assist' provides customized real-time driving advice to drivers, allowing them to adjust behaviors to save fuel and reduce emissions. This advice includes recommended driving speeds, optimal acceleration and deceleration profiles based on prevailing traffic conditions, and local interactions with nearby vehicles, i.e., processing Basic Safety Messages (BSMs) to determine position and speed of vehicles that are between the host vehicle and the intersection. When approaching and departing signalized intersections, it uses intersection geometry information, the relative position and speed of vehicles ahead of it, and signal phase movement information to provide speed advice to the driver so that the driver can adapt the vehicle's speed to pass the next traffic signal on green, decelerate to a stop in the most eco-friendly manner, or manage acceleration as the vehicle departs from a signalized intersection. It also provides feedback to drivers on their driving behavior to encourage them to drive in a more environmentally efficient manner. It may also support vehicle-assisted strategies, where the vehicle automatically implements the eco-driving strategy (e.g., changes gears, switches power sources, or reduces its speed in an eco-friendly manner as the vehicle approaches a traffic signal or queue). Vehicle
Vehicle Emissions Monitoring 'Vehicle Emissions Monitoring' directly measures or estimates current and average vehicle emissions and makes this data available to the driver and connected vehicle infrastructure systems. Vehicle
Vehicle Traveler Information Reception 'Vehicle Traveler Information Reception' receives advisories, vehicle signage data, and other driver information of use to all types of vehicles and drivers and presents this information to the driver using in-vehicle equipment. Information presented may include fixed sign information, traffic control device status (e.g., signal phase and timing data), advisory and detour information, warnings of adverse road and weather conditions, travel times, and other driver information. Vehicle

Includes Information Flows:

Information Flow Description
access violation notification Notification that an individual vehicle or user has committed an access violation. The flow identifies the nature of the violation and the time and location where the violation was recorded.
actuate secure payment Initiation of a payment action, ideally based on an encrypted token or biometric marker. Such a payment action could be a simple validation that the secure token allows the user access to the travel resource, or it could be the initiation of a payment transaction.
air quality sensor control Data used to configure and control area pollution and air quality sensors.
air quality sensor data Measured air quality data, including measured levels of atmospheric pollutants including ozone, particulate matter, carbon monoxide, and nitrogen oxides, and operational status of the sensors.
authorization request Request to determine if a transportation user is authorized to use a particular transportation resource.
authorization response Notification of status of authorization request.
controlled zone application info Application parameters and thresholds used to manage low emissions zones and other special management zones with restricted vehicle access. This flow also supports remote control of the application so the application can be taken offline, reset, or restarted.
controlled zone application status Application status reported by the RSE for low emissions zones or other special management zones with restricted vehicle access. This includes current operational state, status of the RSE, and a record of system operation.
driver information Regulatory, warning, guidance, and other information provided to the driver to support safe and efficient vehicle operation.
driver input Driver input to the vehicle on-board equipment including configuration data, settings and preferences, interactive requests, and control commands.
driver updates Information provided to the driver including visual displays, audible information and warnings, and haptic feedback. The updates inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment.
emissions monitoring application information Data used to configure and control roadside equipment applications that monitor emissions-related data reported by passing vehicles. The parameters include identification of the emissions-related data to be monitored and thresholds for aggregating, filtering, and reporting the collected data.
emissions monitoring application status Emissions monitoring application status reported by the RSE. This includes current operational state and status of the RSE and a record of emissions data collected.
emissions operator input Input from the system operator including nominal emissions data compliance (reference) levels for each sector of an urban area.
emissions operator presentation Presentation of information to the operator supporting both area-wide air quality monitoring and vehicle emissions monitoring. Includes both reference and current pollution status details for a given geographic area.
emissions sensor control Data used to configure and control vehicle emissions sensors.
emissions situation data Emissions-related data as measured and reported by connected vehicles. This flow carries aggregated and filtered data including average and current emissions reported by vehicles as well as associated data (vehicle profiles and speeds) that can be used to estimate aggregate emissions.
emissions violation notification Notification to enforcement agency of a detected vehicle emissions violation. This information flow identifies the vehicle and documents the emissions violation.
event confirmation Confirmation that special event details have been received and processed.
event plans Plans for major events possibly impacting traffic.
license request Request supporting registration data based on license plate read during violation or at the scene of an incident.
light vehicle driver input Driver input to the light vehicle on-board equipment including configuration data, settings and preferences, interactive requests, and control commands.
light vehicle driver updates Information provided to the light vehicle driver including visual displays, audible information and warnings, and haptic feedback. The updates inform the driver about current conditions, potential hazards, and the current status of vehicle on-board equipment.
low emissions zone coordination Coordination of geographic boundaries, time period, fee structure, and restrictions for a low emissions zone. This flow supports negotiation between centers that establishes low emissions zone parameters based on air quality and transportation needs, as constrained by infrastructure and transportation services that are available to manage the defined zone and applicable laws and regulations.
low emissions zone operations information Information on the state of transportation system operations within the low emissions zone including emissions zone parameters, traffic and road conditions within the zone, advisories, incidents, transit service information, weather information, parking information, and other related data.
low emissions zone operations information for public Information on the state of transportation system operations within the low emissions zone including emissions zone parameters, traffic and road conditions within the zone, advisories, incidents, transit service information, weather information, parking information, and other related data. This version includes no detailed operational data (e.g., where the emissions sensors are located) that might be used to subvert the operation.
low emissions zone parameters The geographic boundaries, time period, and fee structure for a low emissions zone. This flow also provides the specific restrictions that are in place for the zone including admittance requirements and rules and restrictions for driving within the zone.
noise data Measured acoustic noise data, including measures of sound intensity and frequency range, over time.
payment administration requests Personnel inputs that control system operations, including requests to change toll fees, confirmation that alerts should be provided to toll operators, management of VMT charge policies and management of VMT account processing, etc.
payment coordination Coordinate apportionment charges between jurisdictions (e., federal government, states, various jurisdictions that might be public or private within a state). Apportionment reconciliation includes either sharing information about mileage or zone-based charges in other jurisdictions (so that the Other Payment Administration subsystems can make appropriate charges), or sharing revenue collected. When sharing revenue, this flow also includes charging rate policies
payment information presentation Presentation of information to personnel including revenues, reports, operational status information, and alert information.
payment instructions Information provided to configure and support fixed point payment operations including pricing information, user account information, and operational parameters used to control equipment that controls access, collects payment, and detects and processes violations.
payment methods financial institution A list of valid payment methods accepted by a financial center.
payment request Request for payment from financial institution or related financial service requests (e.g., balance inquiry)
payment transactions Detailed list of transactions including violations. Each transaction includes the date/time, vehicle/customer, and transaction amount. Additional information is included to support delayed payment and violation processing.
payment violation notification Notification to enforcement agency of a toll, parking, or transit fare payment violation.
registration Registered owner of vehicle and associated vehicle information.
request for payment Request to deduct cost of service from user's payment account.
road network conditions Current and forecasted traffic information, road and weather conditions, and other road network status. Either raw data, processed data, or some combination of both may be provided by this flow. Information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements) in effect is included.
road use charges Road use charges per link.
road use history A vehicle's road use history that records where the vehicle has traveled over time. Optionally includes vehicle speeds as well as distance traveled for some applications. Information is accurate enough to distinguish between adjacent roads, adjacent lanes, and identify direction of travel on the roads.
roadway dynamic signage data Information used to initialize, configure, and control dynamic message signs. This flow can provide message content and delivery attributes, local message store maintenance requests, control mode commands, status queries, and all other commands and associated parameters that support remote management of these devices.
roadway dynamic signage status Current operating status of dynamic message signs.
settlement Information exchanged to settle charges and distribute or debit accounts appropriate to the authorized charges.
traffic detector control Information used to configure and control traffic detector systems such as inductive loop detectors and machine vision sensors.
traffic detector data Raw and/or processed traffic detector data which allows derivation of traffic flow variables (e.g., speed, volume, and density measures) and associated information (e.g., congestion, potential incidents). This flow includes the traffic data and the operational status of the traffic detectors
traffic operator data Presentation of traffic operations data to the operator including traffic conditions, current operating status of field equipment, maintenance activity status, incident status, video images, security alerts, emergency response plan updates and other information. This data keeps the operator appraised of current road network status, provides feedback to the operator as traffic control actions are implemented, provides transportation security inputs, and supports review of historical data and preparation for future traffic operations activities.
traffic operator input User input from traffic operations personnel including requests for information, configuration changes, commands to adjust current traffic control strategies (e.g., adjust signal timing plans, change DMS messages), and other traffic operations data entry.
traffic situation data Current, aggregate traffic data collected from connected vehicles that can be used to supplement or replace information collected by roadside traffic detectors. It includes raw and/or processed reported vehicle speeds, counts, and other derived measures. Raw and/or filtered vehicle control events may also be included to support incident detection.
transit and fare schedules Transit service information including routes, schedules, and fare information. This also includes on-demand service information.
traveler payment information Information provided for payment of road use charges, tolls or parking fees including identification that can be used to identify the payment account or source and related vehicle and service information that are used to determine the type and price of service requested. The information exchange normally supports an account debit to pay fees, but an account credit may be initiated where pricing strategies include incentives.
traveler payment request Request for information supporting payments. For fee structures that include incentives, the request may support either an account debit or an account credit or reimbursement.
user account reports Reports on services offered/provided and associated charges.
user account setup Billing information, vehicle information (or registration information), and requests for reports. Also includes subsequent account changes.
vehicle characteristics The physical or visible characteristics of individual vehicles that can be used to detect, classify, and monitor vehicles and imaged to uniquely identify vehicles.
vehicle emissions data Measured emissions of specific vehicles comprised of exhaust pollutants including hydrocarbons, carbon monoxide, and nitrogen oxides.
vehicle entries and exits Information exchanged between an RSE and ITS Roadway Equipment that supports detection of non-equipped vehicles in an automated lane, low emissions zone, or other facility where V2I communications is used to monitor vehicles at entry or exit points. This exchange also supports identification of non-equipped vehicles where an RSE is used for payment collection. This generic exchange can be implemented by any approach that compares vehicle detections with V2I communications by the RSE to identify vehicles that are not equipped or are otherwise unable to communicate with the RSE.
vehicle location and motion for surveillance Data describing the vehicle's location in three dimensions, heading, speed, acceleration, braking status, and size. This flow represents monitoring of basic safety data ('vehicle location and motion') broadcast by passing connected vehicles for use in vehicle detection and traffic monitoring applications.
vehicle payment information Information provided for payment of tolls, parking, and other transportation fees including identification that can be used to identify the payment account or source and related vehicle and service information that are used to determine the type and price of service requested. This flow supports one-time payments that may not be associated with a service account. See also 'actuate secure payment'. The information exchange normally supports an account debit to pay fees, but an account credit may be initiated where pricing strategies include incentives.
vehicle profile Information about a vehicle such as vehicle make and model, fuel type, engine type, size and weight, vehicle performance and level of control automation, average emissions, average fuel consumption, passenger occupancy, or other data that can be used to classify vehicle eligibility for access to specific lanes, road segments, or regions or participation in cooperative vehicle control applications.
vehicle reported emissions Current and average vehicle emissions data as measured by vehicle diagnostics systems and reported by the vehicle.
vehicle signage application info In-vehicle signing application configuration data and messaging parameters. This flow provides a list of regulatory, warning, and information messages to be displayed and parameters that support scheduling and prioritizing messages to be issued to passing vehicles. This flow also supports remote control of the application so the application can be taken offline, reset, or restarted.
vehicle signage application status In-vehicle signing application status reported by the RSE. This includes current operational state and status of the RSE and a log of messages sent to passing vehicles.
vehicle signage data In-vehicle signing data that augments regulatory, warning, and informational road signs and signals. The information provided would include static sign information (e.g., stop, curve warning, guide signs, service signs, and directional signs) and dynamic information (e.g., local traffic and road conditions, restrictions, vehicle requirements, work zones, detours, closures, advisories, and warnings).
vehicle signage local data Information provided by adjacent field equipment to support in-vehicle signing of dynamic information that is currently being displayed to passing drivers. This includes the dynamic information (e.g., local traffic and road conditions, work zone information, lane restrictions, detours, closures, advisories, parking availability, etc.) and control parameters that identify the desired timing, duration, and priority of the signage data.
weather information Accumulated forecasted and current weather data (e.g., temperature, pressure, wind speed, wind direction, humidity, precipitation, visibility, light conditions, etc.).

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor Goal
A. Support the economic vitality of the metropolitan area, especially by enabling global competitiveness, productivity, and efficiency; Improve freight network
E. Protect and enhance the environment, promote energy conservation, improve the quality of life, and promote consistency between transportation improvements and State and local planned growth and economic development patterns; Protect/Enhance the Environment
G. Promote efficient system management and operation; Improve efficiency

Associated Objective Categories

Objective Category
Environment: Clean Air and Climate Change
System Efficiency: Cost of Congestion
System Efficiency: Energy Consumption

Associated Objectives and Performance Measures

Objective Performance Measure
Reduce carbon dioxide (CO2) emissions to X percent below year Y by year Z. Carbon dioxide emissions - tons per day
Reduce emissions of coarse particulates (PM10) by X percent by year Y. Course particular (PM10) levels - micrograms per cubic meter
Reduce emissions of coarse particulates (PM10) by X percent by year Y. Course particulate (PM10) emissions - tons per day
Reduce emissions of fine particulates (PM2.5) by X percent by year Y. Fine particulate (PM2.5) emissions - tons per day
Reduce emissions of fine particulates (PM2.5) by X percent by year Y. Fine particulate (PM2.5) levels - micrograms per cubic meter
Reduce excess fuel consumed due to congestion by X percent by year Y. Excess fuel consumed (total or per capita).
Reduce the annual monetary cost of congestion per capita for the next X years. Cost (in dollars) of congestion or delay per capita.
Reduce total energy consumption per capita for transportation by X percent by year Y. Total energy consumed per capita for transportation.
Reduce total fuel consumption per capita for transportation by X percent by year Y. Total fuel consumed per capita for transportation.

 
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
01 Traffic Operations need to be able to collect environmental, traffic, and emissions data in order to determine whether a low emissions zone should be set up. Emissions Connected Vehicle Monitoring 02 The center shall control roadside equipment applications that monitor emissions-related data reported by passing vehicles.
Roadway Basic Surveillance 01 The field element shall collect, process, digitize, and send traffic sensor data (speed, volume, and occupancy) to the center for further analysis and storage, under center control.
04 The field element shall return sensor and CCTV system operational status to the controlling center.
Roadway Emissions Monitoring 02 The field element shall collect vehicle emissions data from passing vehicles.
05 The field element shall provide emissions sensor equipment operational status to the center.
RSE Emissions Monitoring 01 The field element shall collect emissions data including current emissions as measured or calculated by on-board equipment, from passing connected vehicles that have the capability to collect and report emissions data.
02 The field element shall aggregate and filter the collected data from the connected vehicles based on provided configuration parameters
03 The field element shall send the collected information back to a center for processing and distribution.
RSE Low Emissions Zone Application 01 The field element shall provide center current operational state and a record of system operation.
RSE Traffic Monitoring 01 The field element shall communicate with on-board equipment on passing vehicles to collect current vehicle position, speed, and heading and a record of previous events (e.g., starts and stops, link travel times) that can be used to determine current traffic conditions.
TIC Data Collection 17 The center shall collect emissions information, including information from low emission zone operations.
TMC Basic Surveillance 01 The center shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements under remote control of the center.
07 The center shall remotely control devices to detect traffic.
Vehicle Basic Safety Communication 06 The vehicle shall exchange location and motion information with roadside equipment and nearby vehicles.
Vehicle Emissions Monitoring 02 The vehicle shall provide the vehicle emissions information to infrastructure systems.
02 Traffic Operations need to be able to set up a low emissions zone in order to reduce emissions within the zone. TMC Incident Dispatch Coordination 06 The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters, traveler information service providers, media, border crossings, and rail operations centers.
TMC Traffic Information Dissemination 14 The center shall provide operators information on the state of transportation system operations within the low emissions zone.
03 Traffic Operations needs to be able to inform drivers, both pre-trip and en route, about low emissions zone operation and the restrictions or fees for driving into the low emissions zones. Roadway Traffic Information Dissemination 01 The field element shall include dynamic message signs for dissemination of traffic and other information to drivers, under center control; the DMS may be either those that display variable text messages, or those that have fixed format display(s) (e.g. vehicle restrictions, or lane open/close).
03 The field element shall provide operational status for the driver information systems equipment (DMS, HAR, etc.) to the center.
04 The field element shall provide fault data for the driver information systems equipment (DMS, HAR, etc.) to the center for repair.
05 The field element shall provide dynamic message sign information to roadside equipment for transmission to connected vehicles to support in-vehicle signing.
RSE Low Emissions Zone Application 02 The field element shall provide vehicle low emission zone parameter information.
RSE Traveler Information Communications 10 The field element shall provide traveler low emission zone restriction information including zone boundaries and fees.
TMC Incident Dispatch Coordination 06 The center shall receive inputs concerning upcoming events that would effect the traffic network from event promoters, traveler information service providers, media, border crossings, and rail operations centers.
TMC In-Vehicle Signing Management 07 The center shall format and output low emission zone information to field equipment that supports in-vehicle signage communications.
TMC Traffic Information Dissemination 11 The center shall provide drivers low emission zone restriction or fees information.
Vehicle Eco-Driving Assist 06 The vehicle shall receive low emission zone restriction parameters from a field element.
Vehicle Traveler Information Reception 09 The vehicle shall receive low emission zone restriction information.
04 Emissions Management Operations need to be able to monitor emissions hot spots and coordinate with Traffic Operations for the establishment of low emission zones. Emissions Data Management 01 The center shall collect, analyze, and store vehicle emissions data collected from connected vehicle and roadside sensors.
02 The center shall collect, analyze, and store wide area pollution data collected from connected vehicles and roadside sensors.
03 The center shall configure and control emissions and air quality sensors located in the field.
04 The center shall maintain a database of pollution reference data including acceptable and tolerable emissions and pollution levels for the area served by the center.
05 The center shall provide the measured and/or estimated emissions collected from mobile sources to traffic management.
06 The center shall establish violation parameters, detect emissions violators, obtain the vehicle registration data from the appropriate State Department of Motor Vehicles (DMV) office, and then provide the capability to send violation information to a law enforcement agency.
07 The center shall distribute air quality information to the media, traveler information service providers, and traffic management centers. This information may be used for information to travelers or part of demand management programs.
Emissions Zone Management 02 The center shall coordinate with traffic and transit management to establish low emission zone parameters based on air quality and transportation need.
TMC Traffic Information Dissemination 13 The center shall receive low emission zone information from emission management.
Transit Center Multi-Modal Coordination 10 The center shall coordinate with emission management to establish low emission zone parameters based on air quality and transportation need.
05 Payment Operations need to be able to collect fees from drivers for entry into a low emissions zone. Light Vehicle Payment Service 08 The vehicle shall receive and present to the vehicle operator the actual cost of low emission zone entry when requested by the vehicle operator.
PAC Road Pricing Administration 02 The center shall provide the status of an electronic payment transaction provided directly to the driver via sign or other roadside infrastructure.
03 The center shall notify enforcement agency of a low emission zone entry payment violation.
Personal Interactive Traveler Information 21 The personal traveler interface shall provide payment information for use of a low emission zone.
Roadway Payment Support 07 The field element shall read data from passing vehicles to support low emission zone entry fee payment transactions.
08 The field element shall send a record of the low emission zone entry fee transactions to the payment administration center.
06 Drivers need to be able to set up accounts and pay fees for the ability to operate their vehicles in a low emissions zone. PAC Road Pricing Administration 01 The center shall set up accounts for drivers to pay for low emission zone entry fees.
Personal Interactive Traveler Information 19 The personal traveler interface shall provide the ability for a traveler to set up and modify a user account for a regional electronic payment system.

Related Sources

Document Name Version Publication Date
AERIS Transformative Concepts Draft 7/13/2011
Dynamic Low Emissions Zones: Operational Concept Final v1.1 8/1/2012


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
Connected Vehicle Roadside Equipment Moderate Moderate Moderate Class 2
DMV High High Moderate Class 4
Emissions Management Center Moderate High Moderate Class 3
Enforcement Center Moderate Moderate Moderate Class 2
Event Promoter System Moderate High Moderate Class 3
Financial Center Moderate Moderate Moderate Class 2
ITS Roadway Equipment Moderate Moderate Moderate Class 2
ITS Roadway Payment Equipment High High High Class 5
Light Vehicle OBE High High High Class 5
Other Payment Administration Centers Moderate High Moderate Class 3
Payment Administration Center High High High Class 5
Payment Device Moderate Moderate High Class 5
Personal Information Device High High Moderate Class 4
Traffic Management Center Moderate High Moderate Class 3
Transit Management Center Moderate Moderate Moderate Class 2
Transportation Information Center Low Low Moderate Class 1
Vehicle Moderate Moderate Moderate Class 2
Vehicle Characteristics  
Weather Service System Low Moderate Low Class 1



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
Basis Basis Basis
Connected Vehicle Roadside Equipment Emissions Management Center controlled zone application status Moderate Moderate Low
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. If this is compromised, it could send unnecessary maintenance workers, or cause the appearance of excessive traffic violations, leading to further unnecessary investigation. 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. Additionally, there is a message received notification, which means that RSE can ensure that all intersection safety issues are delivered.
Connected Vehicle Roadside Equipment Emissions Management Center emissions monitoring application status Moderate Moderate Low
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. If this is compromised, it could send unnecessary maintenance workers, or worse report plausible data that is erroneous. 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 Emissions Management Center emissions situation data Low Moderate Low
Probably not sensitive information, no harm in this data being captured by unintended party. This flow does not correlate specific vehicles with any emissions data. At least some guarantee of correctness should be had with this data. It could be used to modify transit/traffic strategies over a large area ("its a code ORANGE day out there, don't run") that change behavior for a large number of people. This could be MODERATE if emissions information is critical to decision making.
Connected Vehicle Roadside Equipment ITS Roadway Equipment vehicle entries and exits Moderate Moderate Moderate
Directly observable data, but it is aggregated at the field device and also transmitted between devices; if a cyber-attacker were able to remotely monitor this feed, they might use this information to cause chaos. While this can be corroborated visually, the ITS RE may rely on this information to make mobility-related decisions with significant consequences, so the data must be of reasonable quality and availability.. While this can be corroborated visually, the ITS RE may rely on this information to make mobility-related decisions with significant consequences, so the data must be of reasonable quality and availability..
Connected Vehicle Roadside Equipment Traffic Management Center controlled zone application status Moderate Moderate Low
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. If this is compromised, it could send unnecessary maintenance workers, or cause the appearance of excessive traffic violations, leading to further unnecessary investigation. 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. Additionally, there is a message received notification, which means that RSE can ensure that all intersection safety issues are delivered.
Connected Vehicle Roadside Equipment Traffic Management Center traffic situation data Moderate Moderate Low
Aggregated messages may have more privacy implications than individual ones, especially if an attacker can attack more than one RSE-to-TMC connection at once. only limited adverse effect if raw/processed connected vehicle data is bad/compromised; DISC: NYC believes this to be MODERATE: As investigation might be triggered if RF quality is reported as low, this data should be trusted. RES: Agree wih NYC. only limited adverse effect of info is not timely/readily available. NYC: This data is purely for statistical purposes so low availability does not harm the [RSE RF Monitoring] application.
Connected Vehicle Roadside Equipment Traffic Management Center vehicle signage application status Moderate Moderate Low
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. DISC: WYO believes this to be LOW If this is compromised, it could send unnecessary maintenance workers, or cause the appearance of excessive traffic violations, leading to further unnecessary investigation. 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. Additionally, there is a message received notification, which means that RSE can ensure that all intersection safety issues are delivered.
Connected Vehicle Roadside Equipment Vehicle low emissions zone parameters Not Applicable Moderate Moderate
This information is intentionally broadcast and is intended for public consumption. Emissions zone information should have its integrity protected to avoid misinformation or confusion that could result from incorrect data dissemination. Important for low emissions zone operations; without accurate and timely information, travelers may be unaware of the restrictions in place for these areas.
Connected Vehicle Roadside Equipment Vehicle vehicle signage data Low Moderate Moderate
This data is intentionally transmitted to everyone via a broadcast. It is meant to augment other signage data, and by definition is meant to be shared with everyone. These signs are meant to augment other visual cues to the driver. They should be accurate, but any inaccuracies should be corrected for by other means. These notifications are helpful to a driver, but if the driver does not receive this notification immediately, there should still be other visual cues.
DMV Payment Administration Center registration Moderate Moderate Moderate
Will contain PII of driver and/or vehicle owner. Not HIGH because this affects a small number of individuals, and because safety of life is not likely a concern for this flow. Registration/ownership information needs to be correct, the lack of correctness may lead to false paths which have a nontrivial cost. Real-time decisions may be made based on this information.
Driver Vehicle driver input Moderate High High
Data included in this flow may include origin and destination information, which should be protected from other's viewing as it may compromise the driver's privacy. Commands from from the driver to the vehicle must be correct or the vehicle may behave in an unpredictable and possibly unsafe manner Commands must always be able to be given or the driver has no control.
Emissions Management Center Connected Vehicle Roadside Equipment controlled zone application info Moderate Moderate Low
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. If this is compromised, it could send unnecessary maintenance workers, or cause the appearance of excessive traffic violations, leading to further unnecessary investigation. 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. Additionally, there is a message received notification, which means that RSE can ensure that all intersection safety issues are delivered.
Emissions Management Center Connected Vehicle Roadside Equipment emissions monitoring application information Moderate Moderate Low
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.
Emissions Management Center Emissions Management Operator emissions operator presentation Moderate High High
Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
Emissions Management Center Enforcement Center access violation notification Moderate High Moderate
May contain PII of a black listed user account, and/or vehicle identification. Given the potential for PII to be involved, this needs to be correct and unalterable to avoid confusion or malfeasance. Availability is at least MODERATE since the information has potential legal (or at least traffic law) implications that would otherwise involve a far less prompt and possibly manpower intensive interaction.
Emissions Management Center Enforcement Center emissions violation notification Moderate Moderate Moderate
Contains PII and intended to be used for enforcement. Thus privacy implications that, while they may affect only a single individual at a time, could yield significant negative consequences to that individual. Violation information needs to be correct or the vehicle may be improperly penalized, or not when it should be. This is probably not a severe consequence however, so MODERATE. More or less important depending on the context. Could even be LOW if areas of minimal import, depending on local policies.
Emissions Management Center Event Promoter System low emissions zone operations information Moderate Moderate Low
While this information may eventually be public, it may contain details of emissions zone operations that could be used to abuse emissions zone systems. Emissions zone information should have its integrity protected to avoid misinformation or confusion that could result from incorrect data dissemination. Probably not a huge impact if this information cannot be updated frequently, thus LOW.
Emissions Management Center ITS Roadway Equipment air quality sensor control Moderate Moderate Low
Control flows, even for seemingly innocent devices, should be kept confidential to minimize attack vectors. While an individual installation may not be particularly impacted by a cyberattack of its sensor network, another installation might be severely impacted, and different installations are likely to use similar methods, so compromising one leads to compromising all. Control flows, even for seemingly innocent devices, should have MODERATE integrity at minimum, just to guarantee that intended control messages are received. Incorrect, corrupted, intercepted and modified control messages can or will result in target field devices not behaving according to operator intent. The severity of this depends on the type of device, which is why some devices are set MODERATE and some HIGH. Control flow availability is related to the criticality of being able to remotely control the device. For most devices, this is MODERATE. For purely passive devices with no incident relationship, this will be LOW. All devices should have default modes that enable them to operate without backhaul connectivity, so no device warrants a HIGH.
Emissions Management Center ITS Roadway Equipment emissions sensor control Moderate Moderate Low
Control flows, even for seemingly innocent devices, should be kept confidential to minimize attack vectors. While an individual installation may not be particularly impacted by a cyberattack of its sensor network, another installation might be severely impacted, and different installations are likely to use similar methods, so compromising one leads to compromising all. Control flows, even for seemingly innocent devices, should have MODERATE integrity at minimum, just to guarantee that intended control messages are received. Incorrect, corrupted, intercepted and modified control messages can or will result in target field devices not behaving according to operator intent. The severity of this depends on the type of device, which is why some devices are set MODERATE and some HIGH. Control flow availability is related to the criticality of being able to remotely control the device. For most devices, this is MODERATE. For purely passive devices with no incident relationship, this will be LOW. All devices should have default modes that enable them to operate without backhaul connectivity, so no device warrants a HIGH.
Emissions Management Center Payment Administration Center low emissions zone coordination Moderate Moderate Low
While this information may eventually be public, it may contain details of emissions zone operations that could be used to abuse emissions zone systems. Emissions zone information should have its integrity protected to avoid misinformation or confusion that could result from incorrect data dissemination. Probably not a huge impact if this information cannot be updated frequently, thus LOW. If the priority of the low emission zone is high (to the jurisdiction in question) this could be MODERATE.
Emissions Management Center Payment Administration Center low emissions zone operations information Moderate Moderate Low
While this information may eventually be public, it may contain details of emissions zone operations that could be used to abuse emissions zone systems. Emissions zone information should have its integrity protected to avoid misinformation or confusion that could result from incorrect data dissemination. Probably not a huge impact if this information cannot be updated frequently, thus LOW.
Emissions Management Center Traffic Management Center low emissions zone coordination Moderate Moderate Low
While this information may eventually be public, it may contain details of traffic demand information that could be used to abuse the roadway network. Configuration functions should have their integrity protected to avoid misconfiguration which could result in revenue or operational losses. Probably not a huge impact if this information cannot be updated frequently, thus LOW. If the priority of the low emission zone is high (to the jurisdiction in question) this could be MODERATE.
Emissions Management Center Traffic Management Center low emissions zone operations information Moderate Moderate Low
While this information may eventually be public, it may contain details of emissions zone operations that could be used to abuse emissions zone systems. Emissions zone information should have its integrity protected to avoid misinformation or confusion that could result from incorrect data dissemination. Probably not a huge impact if this information cannot be updated frequently, thus LOW.
Emissions Management Center Transit Management Center low emissions zone coordination Moderate Moderate Low
While this information may eventually be public, it may contain details of transit operations that could be used to abuse transit systems. Configuration functions should have their integrity protected to avoid misconfiguration which could result in revenue or operational losses. Probably not a huge impact if this information cannot be updated frequently, thus LOW. If the priority of the low emission zone is high (to the jurisdiction in question) this could be MODERATE.
Emissions Management Center Transit Management Center low emissions zone operations information Moderate Moderate Low
While this information may eventually be public, it may contain details of emissions zone operations that could be used to abuse emissions zone systems. Emissions zone information should have its integrity protected to avoid misinformation or confusion that could result from incorrect data dissemination. Probably not a huge impact if this information cannot be updated frequently, thus LOW.
Emissions Management Center Transportation Information Center low emissions zone operations information for public Low Moderate Moderate
Generally, center-originating flows destined for a TIC don't contain any personal or confidential information, and are eventually intended for some kind of public consumption. Important for low emissions zone operations; without accurate and timely information, travelers may be unaware of the restrictions in place for these areas. Important for low emissions zone operations; without accurate and timely information, travelers may be unaware of the restrictions in place for these areas.
Emissions Management Operator Emissions Management Center emissions operator input Moderate High High
Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
Event Promoter System Emissions Management Center event plans Moderate High Moderate
This will include PII of the event contact person, which should be protected from casual viewing. This flow will also include details of the planned event, which in some circumstances might not be entire public information and so again, should not be casually viewable. Personal contact information needs to be correct, but so do the details of the planned event because of the potential severity of the event's impact. Generally the more significant the potential impact of the event, the higher this should be, but never below MODERATE. There should be other mechanisms for getting this information, otherwise it would match integrity.
Event Promoter System Traffic Management Center event plans Moderate High Moderate
This will include PII of the event contact person, which should be protected from casual viewing. This flow will also include details of the planned event, which in some circumstances might not be entire public information and so again, should not be casually viewable. Personal contact information needs to be correct, but so do the details of the planned event because of the potential severity of the event's impact. Generally the more significant the potential impact of the event, the higher this should be, but never below MODERATE. There should be other mechanisms for getting this information, otherwise it would match integrity.
Financial Center Payment Administration Center payment methods financial institution Moderate Moderate Low
Payment methods should be widely disseminated and contain no information that could cause harm if exposed. Payment methods need to be correct so payment information can be exchanged. Could be LOW, as this should have redundancies and be able to tolerate significant latency. Payment methods need to be correct so payment information can be exchanged. Could be LOW, as this should have redundancies and be able to tolerate significant latency.
Financial Center Payment Administration Center settlement Moderate Moderate Moderate
This may include PII and will include status information about a payment that could be used by a criminal for a variety of purposes, including identity theft, financial theft, or location-based activities, as the status is predictivie of what the account holder is doing and where they are doing it. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
ITS Roadway Equipment Connected Vehicle Roadside Equipment vehicle entries and exits Moderate Moderate Moderate
Directly observable data, but it is aggregated at the field device and also transmitted between devices; if a cyber-attacker were able to remotely monitor this feed, they might use this information to cause chaos. While this can be corroborated visually, the RSE may rely on this information to make mobility-related decisions with significant consequences, so the data must be of reasonable quality and availaability.. While this can be corroborated visually, the RSE may rely on this information to make mobility-related decisions with significant consequences, so the data must be of reasonable quality and availability.
ITS Roadway Equipment Connected Vehicle Roadside Equipment vehicle signage local data Low Moderate Moderate
This data is intentionally transmitted to everyone via a broadcast. It is meant to augment other signage data, and by definition is meant to be shared with everyone. This information impacts the vehicle signage data sent to neighboring ASDs and should be trusted to avoid sending wrong information. DISC: WYO believes this to be HIGH. The system should know if these messages are not received.
ITS Roadway Equipment Driver driver information Not Applicable High Moderate
This data is sent to all drivers and is also directly observable, by design. 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 Emissions Management Center air quality sensor data Not Applicable Moderate Low
Probably not sensitive information, no harm in this data being captured by unintended party. At least some guarantee of correctness should be had with this data. It could be used to modify transit/traffic strategies over a large area ("its a code ORANGE day out there, don't run") that change behavior for a large number of people. This could be MODERATE if emissions information is critical to decision making.
ITS Roadway Equipment Emissions Management Center noise data Low Moderate Low
Probably not sensitive information, no harm in this data being captured by unintended party. At least some guarantee of correctness should be had with this data in case it is used for any analysis. If purely informative, could be LOW. Probably little impact if this is not available.
ITS Roadway Equipment Emissions Management Center vehicle emissions data Moderate Moderate Low
Contains vehicle identity, which should be protected from casual viewing, and maps that to various emissions parameters. As this may imply legal issues (over-emitting etc.), the data should be kept confidential to protect the vehicle owner. As this contains information that could be used to grant permitting (emissions passing) or issue penalites (over-emitting), a corruption of this data could result in the wrong action being taken, revenue lost or inappropriately gained, permit incorrectly granted or denied. Could be MODERATE for those areas where emissions are high priority items. Generally LOW given that most emissions testing is done in person now. As systems come to rely on remote sensing, this may become MODERATE.
ITS Roadway Equipment Traffic Management Center roadway dynamic signage status Moderate Moderate Moderate
Device status information should not be available, as those with criminal intent may use this information toward their own ends. Data is intended to feed dissemination channels, either C-ITS messages or DMS or other channels, so it should generally be correct as it is distributed widely and any forgery or corrupted data will have widespread impact. Failure of this flow affects traveler information dissemination, the importance of which varies with the data contained in the flow and the scenario. Could be LOW in many instances.
ITS Roadway Equipment Traffic Management Center traffic detector data Low Moderate Moderate
No impact if someone sees the data Some minimal guarantee of data integrity is necessary for all C-ITS flows. THEA believes this to be LOW.only limited adverse effect if raw/processed traffic detector data is bad/compromised; DISC: WYO believes this to be HIGH Only limited adverse effect of info is not timely/readily available, however without this information it will be difficult to perform traffic management activities, thus MODERATE. If not used for management, may be LOW.
ITS Roadway Payment Equipment Light Vehicle OBE road use charges Moderate Moderate Moderate
Intended for the end user, so does not generally need to be concealed based on its content. However, could reasonably include localized information which if intercepted implies location of the end user, which is personal and should be protected. This material is used to support end user routing with an understanding of travel times and costs. Loss, corruption or forgery are likely to implact small numbers of users and have a moderate impact on revenues. This material is used to support end user routing with an understanding of travel times and costs. Loss, corruption or forgery are likely to implact small numbers of users and have a moderate impact on revenues.
ITS Roadway Payment Equipment Payment Administration Center authorization request Moderate Moderate Moderate
Contains an identifier linked to an individual or specific device, and thus PII by definition. Compromise of one secureID would likely impact only one user, but the nature of this flow requires that the same algorithm be used for every user; algorithm compromise would harm every user, which would have widespread impact. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
ITS Roadway Payment Equipment Payment Administration Center payment transactions Moderate Moderate Moderate
Contains PII and intended to be used for enforcement. Thus privacy implications that, while they may affect only a single individual at a time, could yield significant negative consequences to that individual. Violation information needs to be correct or the commercial vehicle may be improperly penalized, or not when it should be. This is probably not a severe consequence however, so MODERATE. More or less important depending on the context. Could even be LOW if areas of minimal import, depending on local policies.
ITS Roadway Payment Equipment Payment Administration Center road use history High High Moderate
Contains vehicle identity, location and road use history. This is personal, tracking information that needs the highest levels of protection. Used as the basis for charging, any changes will have a direct impact on fees imposed and revenue collected. Inability to complete this flow will result in a failure of the road use charging system, which will require alternative mechanisms, or more likely delay payments. Payment delay is probably not a serious problem unless widespread and unable to be resolved. Could be LOW if alternative mechanisms for managing charges exist.
Light Vehicle Driver Light Vehicle OBE light vehicle driver input Moderate High High
Data included in this flow may include origin and destination information, which should be protected from other's viewing as it may compromise the driver's privacy. Commands from from the driver to the vehicle must be correct or the vehicle may behave in an unpredictable and possibly unsafe manner Commands must always be able to be given or the driver has no control.
Light Vehicle OBE ITS Roadway Payment Equipment actuate secure payment Moderate Moderate High
Contains an identifier linked to an individual or specific device, and thus PII by definition. Compromise of one secureID would likely impact only one user, but the nature of this flow requires that the same algorithm be used for every user; algorithm compromise would harm every user, which would have widespread impact. Payment related information needs to be correct or the user may be inconvenienced or defrauded. Contact/proximity payment mechanisms need to be very reliable or large numbers of users will be inconvenienced and the systems that use these interfaces (transit, parking etc.) will be hamstrung by interface failures.
Light Vehicle OBE ITS Roadway Payment Equipment road use history High High Moderate
Contains vehicle identity, location and road use history. This is personal, tracking information that needs the highest levels of protection. Used as the basis for charging, any changes will have a direct impact on fees imposed and revenue collected. Inability to complete this flow will result in a failure of the road use charging system, which will require alternative mechanisms, or more likely delay payments. Payment delay is probably not a serious problem unless widespread and unable to be resolved. Could be LOW if alternative mechanisms for managing charges exist.
Light Vehicle OBE Light Vehicle Driver light vehicle driver updates Not Applicable Moderate Moderate
This data is informing the driver about the safety of a nearby area. It should not contain anything sensitive, and does not matter if another person can observe it. This is the information that is presented to the driver. If they receive incorrect information, they may act in an unsafe manner. However, there are other indicators that would alert them to any hazards, such as an oncoming vehicle or crossing safety lights. If this information is not made available to the driver, then the system has not operated correctly.
Light Vehicle OBE Payment Administration Center actuate secure payment Moderate Moderate High
Contains an identifier linked to an individual or specific device, and thus PII by definition. Compromise of one secureID would likely impact only one user, but the nature of this flow requires that the same algorithm be used for every user; algorithm compromise would harm every user, which would have widespread impact. Payment related information needs to be correct or the user may be inconvenienced or defrauded. Contact/proximity payment mechanisms need to be very reliable or large numbers of users will be inconvenienced and the systems that use these interfaces (transit, parking etc.) will be hamstrung by interface failures.
Light Vehicle OBE Payment Administration Center road use history High High Moderate
Contains vehicle identity, location and road use history. This is personal, tracking information that needs the highest levels of protection. Used as the basis for charging, any changes will have a direct impact on fees imposed and revenue collected. Inability to complete this flow will result in a failure of the road use charging system, which will require alternative mechanisms, or more likely delay payments. Payment delay is probably not a serious problem unless widespread and unable to be resolved. Could be LOW if alternative mechanisms for managing charges exist.
Light Vehicle OBE Payment Administration Center user account setup High High Moderate
Contains user identification and transaction history, which if compromised could lead to identity or financial theft. Payment setup information, if corrupted, could lead the user to not properly pay for his trips or perhaps pay for others. If intercepted by a malicious actor, this could be manipulated to trick the user into taking action not in his own best interest. These exchanges can be delayed but eventually have to go through or accounts will not be properly updated, mostly impacting revenue collection.
Light Vehicle OBE Payment Administration Center vehicle payment information High High Moderate
Contains personal information, potentially including identity, payment information such as account numbers, location, and in some cases fraud detection data. All of this information is personal in nature and acceptable only for the intended destination to receive, as any 3rd party observation could lead to identity theft/compromise and/or payment method theft/compromise. This is information is used to process payment and/or detect fraud. Any losses, corruption or forgery has a direct impact on revenue collection, charges assessed and potentially legal action. This is information is used to process payment and/or detect fraud. Any losses, corruption or forgery has a direct impact on revenue collection, charges assessed and potentially legal action. Availability constrained to MODERATE the fact that alternative mechanisms and compromises exist to ameliorate not completing the flow.
Light Vehicle OBE Payment Device request for payment Moderate Moderate High
Contains charges and possibly balance or personal information. Charge information may or may not be public, and balance and personal information is not, though it may be displayed visually. Could be LOW if no personal or balance information and no identifier is not included in the flow. Payment related information needs to be correct or the user may be inconvenienced or defrauded. Contact/proximity payment mechanisms need to be very reliable or large numbers of users will be inconvenienced and the systems that use these interfaces (transit, parking etc.) will be hamstrung by interface failures.
Other Payment Administration Centers Payment Administration Center payment coordination Moderate High Moderate
Contains pricing and reconciliation information shared between agencies. If it includes road use charging information this is MODERATE, as road use charging data is vehicle and owner-specific and can be considered personal. A 3rd party observing this information might learn behavrioral patterns of the individual and use that information in the commission of a crime. If no road use charging information is included, this can be reduced to LOW. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. A delay in reporting this may cause a delay in payment processing, but this is not time critical.
Payment Administration Center DMV license request High Moderate Low
Contains PII and an indication that the person(s) identified in this flow has violated a toll. Release of this information would compromise the personal privacy of those involved. Inaccurate or corrupted information in this flow could lead to a mistaken understanding of the toll violator's identity. Real-time response may be required to deal with tolling and similar violations. The number of people affected is probably quite small, but if the load becomes great the availability may need to be raised to MODERATE.
Payment Administration Center Emissions Management Center low emissions zone coordination Moderate Moderate Low
While this information may eventually be public, it may contain details of emissions zone operations that could be used to abuse emissions zone systems. Configuration functions should have their integrity protected to avoid misconfiguration which could result in revenue or operational losses. Probably not a huge impact if this information cannot be updated frequently, thus LOW. If the priority of the low emission zone is high (to the jurisdiction in question) this could be MODERATE.
Payment Administration Center Enforcement Center payment violation notification Moderate Moderate Moderate
Contains PII and intended to be used for enforcement. Thus privacy implications that, while they may affect only a single individual at a time, could yield significant negative consequences to that individual. Violation information needs to be correct or the commercial vehicle may be improperly penalized, or not when it should be. This is probably not a severe consequence however, so MODERATE. More or less important depending on the context. Could even be LOW if areas of minimal import, depending on local policies.
Payment Administration Center Financial Center payment request Moderate Moderate Moderate
Contains account and related information that is personal and if compromised could financially impact the owner of the account. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
Payment Administration Center ITS Roadway Payment Equipment authorization response Moderate Moderate Moderate
While this may not contain any PII, it does expose behavior. While an observer in place may assume payment activity, there is no sound reason to not conceal this information. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
Payment Administration Center ITS Roadway Payment Equipment payment instructions Moderate Moderate Moderate
This includes control information that can be considered sensitive and competitive, so it should be protected from viewing for competitive reasons. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
Payment Administration Center ITS Roadway Payment Equipment road use charges Moderate Moderate Moderate
Intended for the end user, so does not generally need to be concealed based on its content. However, could reasonably include localized information which if intercepted implies location of the end user, which is personal and should be protected. This material is used to support end user routing with an understanding of travel times and costs. Loss, corruption or forgery are likely to implact small numbers of users and have a moderate impact on revenues. This material is used to support end user routing with an understanding of travel times and costs. Loss, corruption or forgery are likely to implact small numbers of users and have a moderate impact on revenues.
Payment Administration Center Light Vehicle OBE access violation notification Moderate High Moderate
May contain PII of a black listed user account, and/or vehicle identification. Given the potential for PII to be involved, this needs to be correct and unalterable to avoid confusion or malfeasance. Availability is at least MODERATE since the information has potential legal (or at least traffic law) implications that would otherwise involve a far less prompt and possibly manpower intensive interaction.
Payment Administration Center Light Vehicle OBE road use charges Moderate Moderate Moderate
Intended for the end user, so does not generally need to be concealed based on its content. However, could reasonably include localized information which if intercepted implies location of the end user, which is personal and should be protected. This material is used to support end user routing with an understanding of travel times and costs. Loss, corruption or forgery are likely to implact small numbers of users and have a moderate impact on revenues. This material is used to support end user routing with an understanding of travel times and costs. Loss, corruption or forgery are likely to implact small numbers of users and have a moderate impact on revenues.
Payment Administration Center Other Payment Administration Centers payment coordination Moderate High Moderate
Contains pricing and reconciliation information shared between agencies. If it includes road use charging information this is MODERATE, as road use charging data is vehicle and owner-specific and can be considered personal. A 3rd party observing this information might learn behavrioral patterns of the individual and use that information in the commission of a crime. If no road use charging information is included, this can be reduced to LOW. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. A delay in reporting this may cause a delay in payment processing, but this is not time critical.
Payment Administration Center Payment Administrator payment information presentation Moderate High High
Individual payment change requests are unlikely to have any significant systematic impact, but may contain PII and should thus be eyes-only for the operator. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
Payment Administration Center Personal Information Device access violation notification Moderate High Moderate
May contain PII of a black listed user account, and/or vehicle identification. Given the potential for PII to be involved, this needs to be correct and unalterable to avoid confusion or malfeasance. Availability is at least MODERATE since the information has potential legal (or at least traffic law) implications that would otherwise involve a far less prompt and possibly manpower intensive interaction.
Payment Administration Center Personal Information Device traveler payment request Moderate Moderate Moderate
While this may not contain any PII, it does expose behavior. While an observer in place may assume payment activity, there is no sound reason to not conceal this information. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability. Payment flows must all have some integrity protection and consistent availability to prohibit forgery and instill confidence in the payment process. Repurcussions of roadway payment are individually fairly small, collectiviely significant but probably never catastrophic. Thus MODERATE for both integrity and availability.
Payment Administration Center Personal Information Device user account reports High High Moderate
Contains user identification and transaction history, which if compromised could lead to identity or financial theft. Payment history information, if corrupted, could lead the user to take action he or she should not take. If intercepted by a malicious actor, this could be manipulated to trick the user into taking action not in his own best interest. There should be other mechanisms to retrieve this information, but if the flow has low reliability users will lose confidence and not use it. MODERATE for that reason only.
Payment Administrator Payment Administration Center payment administration requests Moderate High High
Individual payment change requests are unlikely to have any significant systematic impact, but may contain PII and should thus be eyes-only for the operator. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
Payment Device Light Vehicle OBE actuate secure payment Moderate Moderate High
Contains an identifier linked to an individual or specific device, and thus PII by definition. Compromise of one secureID would likely impact only one user, but the nature of this flow requires that the same algorithm be used for every user; algorithm compromise would harm every user, which would have widespread impact. Payment related information needs to be correct or the user may be inconvenienced or defrauded. Contact/proximity payment mechanisms need to be very reliable or large numbers of users will be inconvenienced and the systems that use these interfaces (transit, parking etc.) will be hamstrung by interface failures.
Personal Information Device Payment Administration Center traveler payment information High High Moderate
Contains personal information, potentially including identity, payment information such as account numbers and location. All of this information is personal in nature and acceptable only for the intended destination to receive, as any 3rd party observation could lead to identity theft/compromise and/or payment method theft/compromise. This is information is used to process payment and/or detect fraud. Any losses, corruption or forgery has a direct impact on revenue collection, charges assessed and potentially legal action. This is information is used to process payment . Any losses, corruption or forgery has a direct impact on revenue collection, charges assessed and potentially legal action. Availability constrained to MODERATE the fact that alternative mechanisms and compromises exist to ameliorate not completing the flow.
Personal Information Device Payment Administration Center user account setup High High Moderate
Contains user identification and matching vehicle information, which if compromised could lead to identity theft or remote tracking. Payment setup information, if corrupted, could lead the user to not properly pay for his trips or perhaps pay for others. If intercepted by a malicious actor, this could be manipulated to trick the user into taking action not in his own best interest. There should be other mechanisms to provide this information, but if the flow has low reliability users will lose confidence and not use it. MODERATE for that reason only.
Traffic Management Center Connected Vehicle Roadside Equipment controlled zone application info Moderate Moderate Low
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. If this is compromised, it could send unnecessary maintenance workers, or cause the appearance of excessive traffic violations, leading to further unnecessary investigation. 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. Additionally, there is a message received notification, which means that RSE can ensure that all intersection safety issues are delivered.
Traffic Management Center Connected Vehicle Roadside Equipment vehicle signage application info Moderate Moderate Moderate
Control flows, even for seemingly innocent devices, should be kept confidential to minimize attack vectors. While an individual installation may not be particularly impacted by a cyberattack of its sensor network, another installation might be severely impacted, and different installations are likely to use similar methods, so compromising one leads to compromising all. If this is compromised, it could send unnecessary maintenance workers, or cause the appearance of excessive traffic violations, or not properly communicate areas where maintenance workers are operating for example. Not HIGH because regardless of the application, this flow alone does not directly drive injury or damage. DISC: WYO believes this to be HIGH. Control flow availability is related to the criticality of being able to remotely control the device. For most devices, this is MODERATE. This data should be received in a timely manner after it is sent. This will determine which lanes are blocked off for emergency vehicle use in incident management applications. For purely passive devices with no incident relationship, this will be LOW. All devices should have default modes that enable them to operate without backhaul connectivity, so no device warrants a HIGH.
Traffic Management Center Emissions Management Center low emissions zone coordination Moderate Moderate Low
While this information may eventually be public, it may contain details of traffic demand information that could be used to abuse the roadway network. Configuration functions should have their integrity protected to avoid misconfiguration which could result in revenue or operational losses. Probably not a huge impact if this information cannot be updated frequently, thus LOW.
Traffic Management Center Emissions Management Center road network conditions Low Moderate Moderate
No harm should come from seeing this data, as it is eventually intended for public consumption. While accuracy of this data is important for decision making purposes, applications should be able to corroborate the data in many instances. Thus MODERATE generally. Depends on the application; if mobility decisions that affect large numbers of travelers are made based on this data, then it is MODERATE. In more modest circumstances, it may be LOW.
Traffic Management Center Event Promoter System event confirmation Moderate High Moderate
Confirmation flow should match the ratings of the flow providing information in the first place. Confirmation flow should match the ratings of the flow providing information in the first place. Confirmation flow should match the ratings of the flow providing information in the first place.
Traffic Management Center ITS Roadway Equipment roadway dynamic signage data Moderate Moderate Moderate
Device control information should not be available, as those with criminal intent may use this information toward their own ends. Data is intended to feed dissemination channels, either C-ITS messages or DMS or other channels, so it should generally be correct as it is distributed widely and any forgery or corrupted data will have widespread impact. Occasional outages of this flow will delay dissemination of the data to travelers (the eventual end user) which could have significant impacts on travel, both safety and mobility impacts.
Traffic Management Center ITS Roadway Equipment traffic detector control Moderate Moderate Low
Control flows, even for seemingly innocent devices, should be kept confidential to minimize attack vectors. While an individual installation may not be particularly impacted by a cyberattack of its sensor network, another installation might be severely impacted, and different installations are likely to use similar methods, so compromising one leads to compromising all. DISC: THEA, WYO believe this to be LOW: encrypted, authenticated, proprietary; but should not cause severe damage if seen Control flows, even for seemingly innocent devices, should have MODERATE integrity at minimum, just to guarantee that intended control messages are received. Incorrect, corrupted, intercepted and modified control messages can or will result in target field devices not behaving according to operator intent. The severity of this depends on the type of device, which is why some devices are set MODERATE and some HIGH.. From THEA: should be accurate and not be tampered with; could enable outside control of traffic sensors but should not cause severe harm, but could cause issues with traffic sensor data received and be detrimental to operations Control flow availability is related to the criticality of being able to remotely control the device. For most devices, this is MODERATE. For purely passive devices with no incident relationship, this will be LOW. All devices should have default modes that enable them to operate without backhaul connectivity, so no device warrants a HIGH.. From THEA: want updates but delayed information will not be severe; should be able to operate from a previous/default control/config. DISC: WYO believes this to be MODERATE
Traffic Management Center Traffic Operations Personnel traffic operator data Moderate Moderate Moderate
Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. 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.
Traffic Operations Personnel Traffic Management Center traffic operator input Moderate High High
Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
Transit Management Center Emissions Management Center low emissions zone coordination Moderate Moderate Low
While this information may eventually be public, it may contain details of transit operations that could be used to abuse transit systems. Configuration functions should have their integrity protected to avoid misconfiguration which could result in revenue or operational losses. Probably not a huge impact if this information cannot be updated frequently, thus LOW.
Transit Management Center Emissions Management Center transit and fare schedules Low Moderate Moderate
Does not contain any personal or confidential information. While accuracy of this data is important for decision making purposes, the greatest impact if manipulated or incorrect data would be financial and likely limited in scope. For example, making all options appear less expensive than an attacker's route of fiduciary interest, driving revenue to his route. This is undesireable and significant, but not catastrophic. Thus MODERATE generally. While accuracy of this data is important for decision making purposes, applications should be able to function without frequent updates. Thus MODERATE generally, though it could be LOW depending on the level of projected updates.
Vehicle Connected Vehicle Roadside Equipment vehicle location and motion for surveillance Not Applicable Moderate Moderate
This is directly observable data; DISC: WYO believes this to be MODERATE Incorrect information here could lead to the system not functioning properly. If they are unable to properly detect all vehicles crossing the border, it would lead to confusion. There are other factors, such as visual indicators, of vehicles crossing the border, which can be used to help mitigate contradicting information. DISC: THEA believes this should be HIGH: "BSM info needs to be accurate and should not be tampered with" WYO believes this to be HIGH This information must be available in a timely manner for the system to act upon it. The system can operate correctly if some messages are missed, but overall a majority of them should be received.; WYO believes this to be LOW
Vehicle Connected Vehicle Roadside Equipment vehicle profile Low Moderate Moderate
Includes no PII and probably includes information that could be observed, so no need for obfuscation. As this information will be used to determine the vehicle's ability to access services or be charged usage fees, it must be correct and not easily forgeable. This flow enables various services; if the flow is not available the vehicle may not be able to use those services, and also may be charged incorrectly.
Vehicle Connected Vehicle Roadside Equipment vehicle reported emissions Moderate Moderate Moderate
Contains PII describing the vehicle and its operating characteristics, which if observed could be used against the vehicle owner. Applications relying on this data will not function properly if the data is incorrect, so it must be protected commensurate to the value of the application. Initially MODERATE, unlikely to be set to HIGH unless emissions operations are the highest priority. Important for low emissions zone operations; without accurate and timely information, applications relying on this data will not function. While initially MODERATE, could be LOW if the priority for emissions-related applications are similarly low.
Vehicle Driver driver updates Not Applicable Moderate Moderate
This data is informing the driver about the safety of a nearby area. It should not contain anything sensitive, and does not matter if another person can observe it. This is the information that is presented to the driver. If they receive incorrect information, they may act in an unsafe manner. However, there are other indicators that would alert them to any hazards, such as an oncoming vehicle or crossing safety lights. If this information is not made available to the driver, then the system has not operated correctly.
Weather Service System Emissions Management Center weather information Low Moderate Low
Typically intended for public distribution. While there are many sources of weather information, some guarantee of correctness is justifiable to keep confidence in provided service. There should be other sources of this data. It does need to be reliable however; weather can change quickly, and depending on the destination and its operational strategies, timely response may be important.

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.

Name Title Physical Object
CTI 4001 RSU Roadside Unit (RSU) Standard Connected Vehicle Roadside Equipment
ITE 5201 ATC Advanced Transportation Controller ITS Roadway Equipment
ITE 5202 ATC Model 2070 Model 2070 Controller Standard ITS Roadway Equipment
ITE 5301 ATC ITS Cabinet Intelligent Transportation System Standard Specification for Roadside Cabinets ITS Roadway Equipment
ITE 5401 ATC API Application Programming Interface Standard for the Advanced Transportation Controller ITS Roadway Equipment
NEMA TS 8 Cyber and Physical Security Cyber and Physical Security for Intelligent Transportation Systems Emissions Management Center
ITS Roadway Equipment
ITS Roadway Payment Equipment
Payment Administration Center
Traffic Management Center
NEMA TS2 Traffic Controller Assemblies Traffic Controller Assemblies with NTCIP Requirements ITS Roadway Equipment
NEMA TS4 Hardware Standards for DMS Hardware Standards for Dynamic Message Signs (DMS) With NTCIP Requirements ITS Roadway Equipment




System Requirements

System Requirement Need
001 The system shall control roadside equipment applications that monitor emissions-related data reported by passing vehicles. 01 Traffic Operations need to be able to collect environmental, traffic, and emissions data in order to determine whether a low emissions zone should be set up.
002 The system shall collect, analyze, and store vehicle emissions data collected from connected vehicle and roadside sensors. 04 Emissions Management Operations need to be able to monitor emissions hot spots and coordinate with Traffic Operations for the establishment of low emission zones.
003 The system shall collect, analyze, and store wide area pollution data collected from connected vehicles and roadside sensors. 04 Emissions Management Operations need to be able to monitor emissions hot spots and coordinate with Traffic Operations for the establishment of low emission zones.
004 The system shall configure and control emissions and air quality sensors located in the field. 04 Emissions Management Operations need to be able to monitor emissions hot spots and coordinate with Traffic Operations for the establishment of low emission zones.
005 The system shall maintain a database of pollution reference data including acceptable and tolerable emissions and pollution levels for the area served by the center. 04 Emissions Management Operations need to be able to monitor emissions hot spots and coordinate with Traffic Operations for the establishment of low emission zones.
006 The system shall provide the measured and/or estimated emissions collected from mobile sources to traffic management. 04 Emissions Management Operations need to be able to monitor emissions hot spots and coordinate with Traffic Operations for the establishment of low emission zones.
007 The system shall establish violation parameters, detect emissions violators, obtain the vehicle registration data from the appropriate State Department of Motor Vehicles (DMV) office, and then provide the capability to send violation information to a law enforcement agency. 04 Emissions Management Operations need to be able to monitor emissions hot spots and coordinate with Traffic Operations for the establishment of low emission zones.
008 The system shall distribute air quality information to the media, traveler information service providers, and traffic management centers. This information may be used for information to travelers or part of demand management programs. 04 Emissions Management Operations need to be able to monitor emissions hot spots and coordinate with Traffic Operations for the establishment of low emission zones.
009 The system shall coordinate with traffic and transit management to establish low emission zone parameters based on air quality and transportation need. 04 Emissions Management Operations need to be able to monitor emissions hot spots and coordinate with Traffic Operations for the establishment of low emission zones.
010 The system shall set up accounts for drivers to pay for low emission zone entry fees. 06 Drivers need to be able to set up accounts and pay fees for the ability to operate their vehicles in a low emissions zone.
011 The system shall provide the status of an electronic payment transaction provided directly to the driver via sign or other roadside infrastructure. 05 Payment Operations need to be able to collect fees from drivers for entry into a low emissions zone.
012 The system shall notify enforcement agency of a low emission zone entry payment violation. 05 Payment Operations need to be able to collect fees from drivers for entry into a low emissions zone.
013 The system shall collect emissions information, including information from low emission zone operations. 01 Traffic Operations need to be able to collect environmental, traffic, and emissions data in order to determine whether a low emissions zone should be set up.
014 The system shall monitor, analyze, and store traffic sensor data (speed, volume, occupancy) collected from field elements under remote control of the center. 01 Traffic Operations need to be able to collect environmental, traffic, and emissions data in order to determine whether a low emissions zone should be set up.
015 The system shall remotely control devices to detect traffic. 01 Traffic Operations need to be able to collect environmental, traffic, and emissions data in order to determine whether a low emissions zone should be set up.
016 The system shall receive inputs concerning upcoming events that would effect the traffic network from event promoters, traveler information service providers, media, border crossings, and rail operations centers. 02 Traffic Operations need to be able to set up a low emissions zone in order to reduce emissions within the zone.
03 Traffic Operations needs to be able to inform drivers, both pre-trip and en route, about low emissions zone operation and the restrictions or fees for driving into the low emissions zones.
017 The system shall format and output low emission zone information to field equipment that supports in-vehicle signage communications. 03 Traffic Operations needs to be able to inform drivers, both pre-trip and en route, about low emissions zone operation and the restrictions or fees for driving into the low emissions zones.
018 The system shall provide drivers low emission zone restriction or fees information. 03 Traffic Operations needs to be able to inform drivers, both pre-trip and en route, about low emissions zone operation and the restrictions or fees for driving into the low emissions zones.
019 The system shall receive low emission zone information from emission management. 04 Emissions Management Operations need to be able to monitor emissions hot spots and coordinate with Traffic Operations for the establishment of low emission zones.
020 The system shall provide operators information on the state of transportation system operations within the low emissions zone. 02 Traffic Operations need to be able to set up a low emissions zone in order to reduce emissions within the zone.
021 The system shall coordinate with emission management to establish low emission zone parameters based on air quality and transportation need. 04 Emissions Management Operations need to be able to monitor emissions hot spots and coordinate with Traffic Operations for the establishment of low emission zones.
022 The system shall collect, process, digitize, and send traffic sensor data (speed, volume, and occupancy) to the center for further analysis and storage, under center control. 01 Traffic Operations need to be able to collect environmental, traffic, and emissions data in order to determine whether a low emissions zone should be set up.
023 The system shall return sensor and CCTV system operational status to the controlling center. 01 Traffic Operations need to be able to collect environmental, traffic, and emissions data in order to determine whether a low emissions zone should be set up.
024 The system shall return sensor and CCTV system operational status to the controlling center. 01 Traffic Operations need to be able to collect environmental, traffic, and emissions data in order to determine whether a low emissions zone should be set up.
025 The system shall collect vehicle emissions data from passing vehicles. 01 Traffic Operations need to be able to collect environmental, traffic, and emissions data in order to determine whether a low emissions zone should be set up.
026 The system shall provide emissions sensor equipment operational status to the center. 01 Traffic Operations need to be able to collect environmental, traffic, and emissions data in order to determine whether a low emissions zone should be set up.
027 The system shall read data from passing vehicles to support low emission zone entry fee payment transactions. 05 Payment Operations need to be able to collect fees from drivers for entry into a low emissions zone.
028 The system shall send a record of the low emission zone entry fee transactions to the payment administration center. 05 Payment Operations need to be able to collect fees from drivers for entry into a low emissions zone.
029 The system shall include dynamic message signs for dissemination of traffic and other information to drivers, under center control; the DMS may be either those that display variable text messages, or those that have fixed format display(s) (e.g. vehicle restrictions, or lane open/close). 03 Traffic Operations needs to be able to inform drivers, both pre-trip and en route, about low emissions zone operation and the restrictions or fees for driving into the low emissions zones.
030 The system shall provide operational status for the driver information systems equipment (DMS, HAR, etc.) to the center. 03 Traffic Operations needs to be able to inform drivers, both pre-trip and en route, about low emissions zone operation and the restrictions or fees for driving into the low emissions zones.
031 The system shall provide fault data for the driver information systems equipment (DMS, HAR, etc.) to the center for repair. 03 Traffic Operations needs to be able to inform drivers, both pre-trip and en route, about low emissions zone operation and the restrictions or fees for driving into the low emissions zones.
032 The system shall provide dynamic message sign information to roadside equipment for transmission to connected vehicles to support in-vehicle signing. 03 Traffic Operations needs to be able to inform drivers, both pre-trip and en route, about low emissions zone operation and the restrictions or fees for driving into the low emissions zones.
033 The system shall collect emissions data including current emissions as measured or calculated by on-board equipment, from passing connected vehicles that have the capability to collect and report emissions data. 01 Traffic Operations need to be able to collect environmental, traffic, and emissions data in order to determine whether a low emissions zone should be set up.
034 The system shall aggregate and filter the collected data from the connected vehicles based on provided configuration parameters 01 Traffic Operations need to be able to collect environmental, traffic, and emissions data in order to determine whether a low emissions zone should be set up.
035 The system shall send the collected information back to a center for processing and distribution. 01 Traffic Operations need to be able to collect environmental, traffic, and emissions data in order to determine whether a low emissions zone should be set up.
036 The system shall provide center current operational state and a record of system operation. 01 Traffic Operations need to be able to collect environmental, traffic, and emissions data in order to determine whether a low emissions zone should be set up.
037 The system shall provide vehicle low emission zone parameter information. 03 Traffic Operations needs to be able to inform drivers, both pre-trip and en route, about low emissions zone operation and the restrictions or fees for driving into the low emissions zones.
038 The system shall communicate with on-board equipment on passing vehicles to collect current vehicle position, speed, and heading and a record of previous events (e.g., starts and stops, link travel times) that can be used to determine current traffic conditions. 01 Traffic Operations need to be able to collect environmental, traffic, and emissions data in order to determine whether a low emissions zone should be set up.
039 The system shall provide traveler low emission zone restriction information including zone boundaries and fees. 03 Traffic Operations needs to be able to inform drivers, both pre-trip and en route, about low emissions zone operation and the restrictions or fees for driving into the low emissions zones.
040 The system shall provide the ability for a traveler to set up and modify a user account for a regional electronic payment system. 06 Drivers need to be able to set up accounts and pay fees for the ability to operate their vehicles in a low emissions zone.
041 The system shall provide payment information for use of a low emission zone. 05 Payment Operations need to be able to collect fees from drivers for entry into a low emissions zone.
042 The system shall exchange location and motion information with roadside equipment and nearby vehicles. 01 Traffic Operations need to be able to collect environmental, traffic, and emissions data in order to determine whether a low emissions zone should be set up.
043 The system shall receive low emission zone restriction parameters from a field element. 03 Traffic Operations needs to be able to inform drivers, both pre-trip and en route, about low emissions zone operation and the restrictions or fees for driving into the low emissions zones.
044 The system shall provide the vehicle emissions information to infrastructure systems. 01 Traffic Operations need to be able to collect environmental, traffic, and emissions data in order to determine whether a low emissions zone should be set up.
045 The system shall receive and present to the vehicle operator the actual cost of low emission zone entry when requested by the vehicle operator. 05 Payment Operations need to be able to collect fees from drivers for entry into a low emissions zone.
046 The system shall receive low emission zone restriction information. 03 Traffic Operations needs to be able to inform drivers, both pre-trip and en route, about low emissions zone operation and the restrictions or fees for driving into the low emissions zones.