< < PT17 : ST01 : ST02 > >

ST01: Emissions Monitoring

This service package monitors individual vehicle emissions and provides general air quality monitoring using distributed sensors to collect the data. The collected information is transmitted to the Emissions Management Center for processing. Both area wide air quality monitoring and point emissions monitoring are supported by this service package. For area wide monitoring, this service package measures air quality, identifies sectors that are non-compliant with air quality standards, and collects, stores and reports supporting statistical data. For point emissions monitoring, this service package collects data from on-board diagnostic systems and measures tail pipe emissions to identify vehicles that exceed emissions standards and/or clean vehicles that could be released from standard emissions tests, depending on policy and regulations. Summary emissions information or warnings can also be displayed to drivers. The gathered information can be used to implement environmentally sensitive travel demand management (TDM) programs, policies, and regulations.

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
Basic Transit Vehicle Maintainer Basic Transit Vehicle Maintains
Basic Transit Vehicle Manager Basic Transit Vehicle Manages
Basic Transit Vehicle Owner Basic Transit Vehicle Maintainer System Maintenance Agreement
Basic Transit Vehicle Owner Basic Transit Vehicle Manager Operations Agreement
Basic Transit Vehicle Owner Transit Vehicle OBE Maintainer Maintenance Data Exchange Agreement
Basic Transit Vehicle Owner Transit Vehicle OBE Owner Expectation of Data Provision
Basic Transit Vehicle Owner Transit Vehicle OBE User Service Usage Agreement
Basic Transit Vehicle Supplier Basic Transit Vehicle Owner Warranty
Basic Vehicle Maintainer Basic Vehicle Maintains
Basic Vehicle Manager Basic Vehicle Manages
Basic Vehicle Owner Basic Vehicle Maintainer System Maintenance Agreement
Basic Vehicle Owner Basic Vehicle Manager Operations Agreement
Basic Vehicle Owner Vehicle Maintainer Maintenance Data Exchange Agreement
Basic Vehicle Owner Vehicle Owner Expectation of Data Provision
Basic Vehicle Owner Vehicle User Service Usage Agreement
Basic Vehicle Supplier Basic Vehicle Owner Warranty
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 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 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
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 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 Media Maintainer Maintenance Data Exchange Agreement
Emissions Management Center Owner Media Owner Information Provision Agreement
Emissions Management Center Owner Media User Service Usage Agreement
Emissions Management Center Owner Traffic Management Center Maintainer Maintenance Data Exchange Agreement
Emissions Management Center Owner Traffic Management Center Owner Information Provision Agreement
Emissions Management Center Owner Traffic Management Center User Service 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
ITS Roadway Equipment Maintainer ITS Roadway Equipment Maintains
ITS Roadway Equipment Manager ITS Roadway Equipment Manages
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 Supplier ITS Roadway Equipment Owner Warranty
Media Maintainer Media Maintains
Media Manager Media Manages
Media Owner Media Maintainer System Maintenance Agreement
Media Owner Media Manager Operations Agreement
Media Supplier Media Owner Warranty
Traffic Management Center Maintainer Traffic Management Center Maintains
Traffic Management Center Manager Traffic Management Center Manages
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
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
Transit Vehicle OBE Maintainer Transit Vehicle OBE Maintains
Transit Vehicle OBE Manager Transit Vehicle OBE Manages
Transit Vehicle OBE Owner Transit Management Center Maintainer Maintenance Data Exchange Agreement
Transit Vehicle OBE Owner Transit Management Center Owner Expectation of Data Provision
Transit Vehicle OBE Owner Transit Management Center User Service Usage Agreement
Transit Vehicle OBE Owner Transit Vehicle OBE Maintainer System Maintenance Agreement
Transit Vehicle OBE Owner Transit Vehicle OBE Manager Operations Agreement
Transit Vehicle OBE Supplier Transit Vehicle OBE 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 Maintainer Vehicle Maintains
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 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
ITS Roadway Equipment 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
Transit Management Center Transit Center Emissions Monitoring 4.1.4 Collect and Process Transit Vehicle Data
Transit Vehicle OBE Transit Vehicle Emissions Monitoring 4.1.1 Process On-Board Systems Data
4.1.2 Determine Transit Vehicle Service Status
Vehicle 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 Environmental Monitoring 3.1.3 Process Vehicle On-board Data
3.2.3.2 Manage Platoon Following
3.2.3.3 Process Data for Vehicle Actuators
3.2.3.5.1 Process General Vehicle Sensor Data
3.2.4 Process Sensor Data for Automatic Vehicle Operations
6.7.1.3 Process Vehicle Location Data
6.7.1.4 Update Vehicle Navigable Map Database
6.7.3.1 Provide Driver with Personal Travel Information
6.7.3.2 Provide Driver Information Interface
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 Diagram
PNG Diagram


Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object Class Description
Basic Transit Vehicle Vehicle The 'Basic Transit Vehicle' represents the transit vehicle that hosts the on-board equipment that provides ITS functions. It includes a specialized and extended databus that is subject to different vehicle databus standards and hosts a broad range of components that are unique to a transit vehicle including the farebox and associated electronics, passenger counters, and transit security systems. The Transit Vehicle may represent a bus, paratransit vehicle, light rail vehicle, or other vehicle designed to carry passengers.
Basic Vehicle Vehicle 'Basic Vehicle' represents a complete operating vehicle. It includes the vehicle platform that interfaces with and hosts ITS electronics and all of the driver convenience and entertainment systems, and other non-ITS electronics on-board the vehicle. Interfaces represent both internal on-board interfaces between ITS equipment and other vehicle systems and other passive and active external interfaces or views of the vehicle that support vehicle/traffic monitoring and management. External interfaces may also represent equipment that is carried into the vehicle (e.g., a smartphone that is brought into the vehicle). Internal interfaces are often implemented through a vehicle databus, which is also included in this object. Note that 'Vehicle' represents the general functions and interfaces that are associated with personal automobiles as well as commercial vehicles, emergency vehicles, transit vehicles, and other specialized vehicles.
Connected Vehicle Roadside Equipment Field 'Connected Vehicle Roadside Equipment' (CV RSE) represents the Connected Vehicle roadside devices that are used to send messages to, and receive messages from, nearby vehicles using Dedicated Short Range Communications (DSRC) or other alternative wireless communications technologies. Communications with adjacent field equipment and back office centers that monitor and control the RSE are also supported. This device operates from a fixed position and may be permanently deployed or a portable device that is located temporarily in the vicinity of a traffic incident, road construction, or a special event. It includes a processor, data storage, and communications capabilities that support secure communications with passing vehicles, other field equipment, and centers.
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.
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.
Media Center 'Media' represents the information systems that provide traffic reports, travel conditions, and other transportation-related news services to the traveling public through radio, TV, and other media. Traffic and travel advisory information that are collected by ITS are provided to this object. It is also a source for traffic flow information, incident and special event information, and other events that may have implications for the transportation system.
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.
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.
Transit Vehicle OBE Vehicle The 'Transit Vehicle On-Board Equipment' (OBE) resides in a transit vehicle and provides the sensory, processing, storage, and communications functions necessary to support safe and efficient movement of passengers. The types of transit vehicles containing this physical object include buses, paratransit vehicles, light rail vehicles, other vehicles designed to carry passengers, and supervisory vehicles. It collects ridership levels and supports electronic fare collection. It supports a traffic signal prioritization function that communicates with the roadside physical object to improve on-schedule performance. Automated vehicle location enhances the information available to the transit operator enabling more efficient operations. On-board sensors support transit vehicle maintenance. The physical object supports on-board security and safety monitoring. This monitoring includes transit user or vehicle operator activated alarms (silent or audible), as well as surveillance and sensor equipment. The surveillance equipment includes video (e.g. CCTV cameras), audio systems and/or event recorder systems. It also furnishes travelers with real-time travel information, continuously updated schedules, transfer options, routes, and fares. A separate 'Vehicle OBE' physical object supports the general vehicle safety and driver information capabilities that apply to all vehicles, including transit vehicles. The Transit Vehicle OBE supplements these general capabilities with capabilities that are specific to transit vehicles.
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.
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
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 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 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
Transit Center Emissions Monitoring 'Transit Center Emissions Monitoring' collects and/or estimates current transit fleet emissions and forecasts future fleet emissions in the context of overall air quality measures for the region. The collected, estimated, and forecast emissions is monitored and forwarded to other agencies to more effectively manage transit operations to reduce emissions. Transit Management Center
Transit Vehicle Emissions Monitoring 'Transit Vehicle Emissions Monitoring' directly measures or estimates vehicle emissions and provides current and average emissions measures to the Transit Management Center. Transit Vehicle OBE
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 Environmental Monitoring 'Vehicle Environmental Monitoring' collects data from on-board sensors and systems related to environmental conditions and sends the collected data to the infrastructure as the vehicle travels. The collected data is a byproduct of vehicle safety and convenience systems and includes ambient air temperature and precipitation measures and status of the wipers, lights, ABS, and traction control systems. Vehicle
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
air quality information Aggregated region-wide measured air quality data and possible pollution incident information.
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.
driver information Regulatory, warning, guidance, and other information provided to the driver to support safe and efficient vehicle operation.
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.
host transit vehicle status Information provided to the ITS on-board equipment from other systems on the Transit Vehicle Platform.
host vehicle status Information provided to the ITS on-board equipment from other systems on the vehicle platform. This includes the current status of the powertrain, steering, and braking systems, and status of other safety and convenience systems. In implementations where GPS is not integrated into the Vehicle On-Board Equipment, the host vehicle is also the source for data describing the vehicle's location in three dimensions (latitude, longitude, elevation) and accurate time that can be used for time synchronization across the ITS environment.
mobile source emissions data Measured and/or estimated emissions at point locations from mobile sources including cars and light trucks, heavy trucks and buses. Where applicable, this flow may also include emissions measures or estimates from non-road engines and portable equipment at the location.
transit emissions data Aggregate and/or summarized transit emissions data, including greenhouse gas (GHG) and criteria air pollutant emissions for one or more vehicles in the transit fleet.
transit vehicle emissions Greenhouse Gas (GHG) and criteria air pollutant emissions reported by a transit vehicle.
vehicle emissions data Measured emissions of specific vehicles comprised of exhaust pollutants including hydrocarbons, carbon monoxide, and nitrogen oxides.
vehicle environmental data Data from vehicle safety and convenience systems that can be used to estimate environmental and infrastructure conditions, including measured air temperature, exterior light status, wiper status, sun sensor status, rain sensor status, traction control status, anti-lock brake status, vertical acceleration and other collected vehicle system status and sensor information. The collected data is reported along with the location, heading, and time that the data was collected. Both current data and snapshots of recent events (e.g., traction control or anti-lock brake system activations) may be reported.
vehicle reported emissions Current and average vehicle emissions data as measured by vehicle diagnostics systems and reported by the vehicle.
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 situation data parameters A request for vehicle situation data that includes parameters used to control the data that is reported and the flow of data reported by the vehicle. This flow identifies the type of data/snapshots that are requested and reporting parameters such as snapshot frequency, filtering criteria (data thresholds for reporting), and reporting interval.
weather information Accumulated forecasted and current weather data (e.g., temperature, pressure, wind speed, wind direction, humidity, precipitation, visibility, light conditions, etc.).
wide area air quality data Region-wide air quality data reported by subregions. Includes current data and forecasts.

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor Goal
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

Associated Objective Categories

Objective Category
Environment: Clean Air and Climate Change

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

 
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 Emissions Management needs to be able to measure wide area pollution data in order to monitor wide area pollution levels. Emissions Connected Vehicle Monitoring 01 The center shall collect emissions data reported by passing connected vehicles.
Emissions Data Management 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.
Roadway Emissions Monitoring 07 The field element shall provide area-wide pollution sensor equipment operational status to the center.
08 The field element shall provide area-wide pollution sensor equipment fault indication to the center for repair.
09 The field element shall include air quality sensors, often distributed geographically, that detect area-wide levels of pollution, under center control.
Vehicle Environmental Monitoring 02 The vehicle shall monitor the status of vehicle convenience and safety systems (wiper status, headlight status, traction control system status) that can be used to measure environmental conditions and record snapshots of significant events in these systems.
04 The vehicle shall transmit environmental probe data to field equipment located along the roadway using short range communications.
02 Emissions Management needs to be able to measure vehicle emissions data collected from individual vehicles at the roadside in order to identify high emitting vehicles. Emissions Data Management 01 The center shall collect, analyze, and store vehicle emissions data collected from connected vehicle and roadside sensors.
03 The center shall configure and control emissions and air quality sensors located in the field.
Roadway Emissions Monitoring 01 The field element shall include emissions sensors that detect levels of emissions from individual vehicles, under center control.
02 The field element shall collect vehicle emissions data from passing vehicles.
03 The field element shall analyze collected vehicle emissions data against reference data to determine whether or not a vehicle is violating the acceptable levels of emissions, and shall return this analysis to a center for possible enforcement action.
05 The field element shall provide emissions sensor equipment operational status to the center.
06 The field element shall provide emissions sensor equipment fault indication to the center for repair.
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.
05 The field equipment shall provide probe data collection parameters to nearby vehicles.
Transit Center Emissions Monitoring 01 The center shall collect current transit fleet emissions and forecasts future fleet emissions.
02 The center shall provide the collected and forecast emissions information to other agencies.
Transit Vehicle Emissions Monitoring 01 The transit vehicle shall measure or estimate vehicle emissions.
02 The transit vehicle shall transmit current and average emissions measures to the Transit Management Center.
Vehicle Emissions Monitoring 01 The vehicle shall directly measures or estimates current and average vehicle emissions.
02 The vehicle shall provide the vehicle emissions information to infrastructure systems.
03 Emission Management needs to be able to provide summary emission information or warning to drivers. Roadway Emissions Monitoring 04 The field element shall display summary emissions information or warnings to passing drivers via a driver information system (such as portable messages signs, field to vehicle communications to in-vehicle signing systems, etc.), if the emissions level detected by the emissions sensor indicates a vehicle is violating the acceptable levels of emissions.
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).
RSE Emissions Monitoring 04 The field element shall provide vehicle informational road signs and signals, local traffic and road conditions, detours, advisories, and warnings information.
RSE Traveler Information Communications 01 The field element shall distribute traveler information including traffic and road conditions or upcoming work zones to passing vehicles using short range communications, under center control.
02 The field element shall distribute advisory information, such as evacuation information, wide-area alerts, incident information, work zone intrusion information, recommended speed limit and other special information to passing vehicles using short range communications, under center control.
03 The field element shall distribute indicator and fixed sign information, including static sign information (e.g., stop, curve warning, guide signs, service signs, and directional signs) and dynamic information (e.g., current signal states and local conditions warnings identified by local environmental sensors) to equipment on-board vehicles under center control.
04 The field element shall return system operational status to the controlling center.
Vehicle Traveler Information Reception 02 The vehicle shall receive advisory information, such as evacuation information, proximity to a maintenance and construction vehicle, wide-area alerts, work zone intrusion information, variable speed limits, tunnel entrance restrictions, and other special information.
03 The vehicle shall receive indicator and fixed sign information including static sign information (e.g., stop, curve warning, guide signs, service signs, and directional signs) and dynamic information (e.g., current signal and traffic meter states and local conditions warnings identified by local environmental sensors).
04 The vehicle shall store a translation table for road sign and message templates used for in-vehicle display.
05 The vehicle shall present the received information to the driver in audible or visual forms without impairing the driver's ability to control the vehicle in a safe manner.
06 The vehicle shall present to the driver a visual display of static sign information or dynamic roadway conditions information
07 The vehicle shall be capable of providing to the driver an audible presentation of static sign information or dynamic roadway conditions information
04 Emissions Management needs to be able to provide wide area pollution information to the media, traveler information centers, and other transportation centers in order to support traveler information and transportation operations. Emissions Data Management 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.
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.
05 Emissions Management needs to be able to send information about vehicles with excessive emissions to the appropriate Department of Motor Vehicles (DMV) or law enforcement. Emissions Data 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.

Related Sources

Document Name Version Publication Date
ITS User Services Document 1/1/2005


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
Basic Transit Vehicle  
Basic Vehicle  
Connected Vehicle Roadside Equipment Moderate Moderate Moderate Class 2
Emissions Management Center Moderate Moderate Moderate Class 2
Enforcement Center Moderate Moderate Moderate Class 2
ITS Roadway Equipment Moderate Moderate Moderate Class 2
Media Not Applicable Low Low Class 1
Traffic Management Center Moderate Moderate Moderate Class 2
Transit Management Center Moderate Moderate Moderate Class 2
Transit Vehicle OBE Moderate Moderate Moderate Class 2
Transportation Information Center Not Applicable Low Low Class 1
Vehicle Moderate Moderate Moderate Class 2
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
Basic Transit Vehicle Transit Vehicle OBE host transit vehicle status Moderate Moderate Moderate
This can include some sensitive data. However, other data, such as vehicle location and motion will then be broadcast. There also may be proprietary information included in this. DISC THEA believes this to be LOW: "sensor data is not confidential; harm should not come from seeing status." This is used later on to determine whether a vehicle should request priority at an intersection. If this information is incorrect the vehicle may make false requests. All other flows that use the data from this flow have a MODERATE integrity requirement, therefore, this must also have a MODERATE integrity requirement. DISC: THEA believes this should be HIGH: "sensor data needs to be accurate and should not be tampered with." This information would need to be available immediately for the application to work.DISC: THEA believes this should be HIGH: "sensor data must be consistently available to feed BSMs broadcast at 10Hz, notifications, etc.."
Basic Vehicle Vehicle host vehicle status Low Moderate High
Unlikely that this includes any information that could be used against the originator. This can be MODERATE or HIGH, depending on the application: This is used later on to determine whether a vehicle is likely going to violate a red light or infringe a work zone. This needs to be correct in order for the application to work correctly. Since this monitors the health and safety of the vehicle and that information is eventually reported to the driver, it should be available at all times as it directly affects vehicle and operator safety.
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 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.
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.
Connected Vehicle Roadside Equipment Vehicle vehicle situation data parameters Low Moderate Moderate
This isn't exactly a control flow, more like a 'suggestion flow', as the vehicle will always decide what to send. Probably no need for obfuscation. Info should be accurate and should not be tampered so that the vehicle only discloses the correctly requested data Parameters should be timely and readily available, but would not have severe/catastrophic consequences if not
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 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 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 Media air quality information Not Applicable Moderate Low
This flow does not contain any personal or confidential information, and the data contained is eventually intended for public consumption. Information for general distribution should have at least some guarantee that it was correctly transmitted. If this information were incorrect, people could be exposed to higher levels of pollution than they would intend, which could be harmful to people with medical conditions such as asthma. Not a key flow for any service package. If an application is developed that relies on this flow, may change to MODERATE.
Emissions Management Center Traffic Management Center mobile source emissions data Low Moderate Moderate
Probably not sensitive information, no harm in this data being captured by unintended party if this flow does not correlate specific vehicles with any emissions data. If specific vehicles are associated with data, this would be MODERATE. 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. While the source flows from RSEs are considered LOW, this is an aggregated flow, so the impact of an outage is larger. If this flow exists, it is probably used for decision-making and any loss of this flow has an impact.
Emissions Management Center Traffic Management Center wide area air quality data Moderate Moderate Low
While this information may eventually be public, it may contain details of an emissions incident that could require further investigation; third party observation of this information could hamper that investigation. Emissions incident 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 traffic management in the area is reactive to emissions and pollution in general, this may be increased to MODERATE.
Emissions Management Center Transit Management Center wide area air quality data Moderate Moderate Moderate
While this information may eventually be public, it may contain details of an emissions incident that could require further investigation; third party observation of this information could hamper that investigation. Since this is the basis for issuing air quality alerts, and may be used to restrict certain kinds of vehicular traffic in severe conditions, it must be correct and timely or significant inconvenience or negative pollution effects may occur. Since this is the basis for issuing air quality alerts, and may be used to restrict certain kinds of vehicular traffic in severe conditions, it must be correct and timely or significant inconvenience or negative pollution effects may occur.
Emissions Management Center Transportation Information Center air quality information Not Applicable Moderate Low
This flow does not contain any personal or confidential information, and the data contained is eventually intended for public consumption. Information for general distribution should have at least some guarantee that it was correctly transmitted. If this information were incorrect, people could be exposed to higher levels of pollution than they would intend, which could be harmful to people with medical conditions such as asthma. Not a key flow for any service package. If an application is developed that relies on this flow, may change to MODERATE.
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.
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 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.
Transit Management Center Emissions Management Center transit emissions data Low Moderate Low
Probably not sensitive as the data is aggregated. If considered competitive this may be MODERATE. 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. This flow is LOW however because it is not in the critical path for a typical low emissions zone application. If iarchitected so this flow is in the critical path, then this should be MODERATE.
Transit Vehicle OBE Transit Management Center transit vehicle 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 Connected Vehicle Roadside Equipment vehicle environmental data Low Moderate Low
Little abusive potential for capturing the information in this flow as designed. Could be moderate if this contains PII related information, but considered for now to not include any PII; DISC: WYO believes Vehicle to Center versions of this flow to be MODERATE as center penetrations could more easily garner aggregate user data that might be used for mischief. Some minimal guarantee of data integrity is necessary for all C-ITS flows. DISC THEA believes this to be LOW: Data should be accurate and not tampered with but should be able to cope with some bad data in traffic/environmental condition monitoring; aggregate data; can also receive data from ITS RE; DISC: WYO believes this to be MODERATE data should be timely and readily available, but limited adverse effect; aggregate data; can also receive data from ITS RE; DISC: WYO believes this to be MODERATE
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.
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 Dedicated Short-Range Communications Roadside Unit Specifications (FHWA-JPO-17-589) Connected Vehicle Roadside Equipment
ITE ATC Advanced Transportation Controller ITS Roadway Equipment
ITE ATC API Application Programming Interface Standard for the Advanced Transportation Controller ITS Roadway Equipment
ITE ATC ITS Cabinet Intelligent Transportation System Standard Specification for Roadside Cabinets ITS Roadway Equipment
ITE ATC Model 2070 Model 2070 Controller Standard ITS Roadway Equipment
NEMA TS 8 Cyber and Physical Security Cyber and Physical Security for Intelligent Transportation Systems Emissions Management Center
ITS Roadway Equipment
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 collect emissions data reported by passing connected vehicles. 01 Emissions Management needs to be able to measure wide area pollution data in order to monitor wide area pollution levels.
002 The system shall collect, analyze, and store vehicle emissions data collected from connected vehicle and roadside sensors. 02 Emissions Management needs to be able to measure vehicle emissions data collected from individual vehicles at the roadside in order to identify high emitting vehicles.
003 The system shall collect, analyze, and store wide area pollution data collected from connected vehicles and roadside sensors. 01 Emissions Management needs to be able to measure wide area pollution data in order to monitor wide area pollution levels.
004 The system shall configure and control emissions and air quality sensors located in the field. 01 Emissions Management needs to be able to measure wide area pollution data in order to monitor wide area pollution levels.
02 Emissions Management needs to be able to measure vehicle emissions data collected from individual vehicles at the roadside in order to identify high emitting vehicles.
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 needs to be able to provide wide area pollution information to the media, traveler information centers, and other transportation centers in order to support traveler information and transportation operations.
006 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 05 Emissions Management needs to be able to send information about vehicles with excessive emissions to the appropriate Department of Motor Vehicles (DMV) or law enforcement.
007 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 needs to be able to provide wide area pollution information to the media, traveler information centers, and other transportation centers in order to support traveler information and transportation operations.
008 The system shall collect current transit fleet emissions and forecasts future fleet emissions. 02 Emissions Management needs to be able to measure vehicle emissions data collected from individual vehicles at the roadside in order to identify high emitting vehicles.
009 The system shall provide the collected and forecast emissions information to other agencies. 02 Emissions Management needs to be able to measure vehicle emissions data collected from individual vehicles at the roadside in order to identify high emitting vehicles.
010 The system shall include emissions sensors that detect levels of emissions from individual vehicles, under center control. 02 Emissions Management needs to be able to measure vehicle emissions data collected from individual vehicles at the roadside in order to identify high emitting vehicles.
011 The system shall collect vehicle emissions data from passing vehicles. 02 Emissions Management needs to be able to measure vehicle emissions data collected from individual vehicles at the roadside in order to identify high emitting vehicles.
012 The system shall analyze collected vehicle emissions data against reference data to determine whether or not a vehicle is violating the acceptable levels of emissions, and shall return this analysis to a center for possible enforcement action. 02 Emissions Management needs to be able to measure vehicle emissions data collected from individual vehicles at the roadside in order to identify high emitting vehicles.
013 The system shall display summary emissions information or warnings to passing drivers via a driver information system (such as portable messages signs, field to vehicle communications to in-vehicle signing systems, etc.), if the emissions level detected b 03 Emission Management needs to be able to provide summary emission information or warning to drivers.
014 The system shall provide emissions sensor equipment operational status to the center. 02 Emissions Management needs to be able to measure vehicle emissions data collected from individual vehicles at the roadside in order to identify high emitting vehicles.
015 The system shall provide emissions sensor equipment fault indication to the center for repair. 02 Emissions Management needs to be able to measure vehicle emissions data collected from individual vehicles at the roadside in order to identify high emitting vehicles.
016 The system shall provide area-wide pollution sensor equipment operational status to the center. 01 Emissions Management needs to be able to measure wide area pollution data in order to monitor wide area pollution levels.
017 The system shall provide area-wide pollution sensor equipment fault indication to the center for repair. 01 Emissions Management needs to be able to measure wide area pollution data in order to monitor wide area pollution levels.
018 The system shall include air quality sensors, often distributed geographically, that detect area-wide levels of pollution, under center control. 01 Emissions Management needs to be able to measure wide area pollution data in order to monitor wide area pollution levels.
019 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 r 03 Emission Management needs to be able to provide summary emission information or warning to drivers.
020 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. 02 Emissions Management needs to be able to measure vehicle emissions data collected from individual vehicles at the roadside in order to identify high emitting vehicles.
021 The system shall provide probe data collection parameters to nearby vehicles. 02 Emissions Management needs to be able to measure vehicle emissions data collected from individual vehicles at the roadside in order to identify high emitting vehicles.
022 The system shall aggregate and filter the collected data from the connected vehicles based on provided configuration parameters 02 Emissions Management needs to be able to measure vehicle emissions data collected from individual vehicles at the roadside in order to identify high emitting vehicles.
023 The system shall send the collected information back to a center for processing and distribution. 02 Emissions Management needs to be able to measure vehicle emissions data collected from individual vehicles at the roadside in order to identify high emitting vehicles.
024 The system shall provide vehicle informational road signs and signals, local traffic and road conditions, detours, advisories, and warnings information. 03 Emission Management needs to be able to provide summary emission information or warning to drivers.
025 The system shall distribute traveler information including traffic and road conditions or upcoming work zones to passing vehicles using short range communications, under center control. 03 Emission Management needs to be able to provide summary emission information or warning to drivers.
026 The system shall distribute advisory information, such as evacuation information, wide-area alerts, incident information, work zone intrusion information, recommended speed limit and other special information to passing vehicles using short range communic 03 Emission Management needs to be able to provide summary emission information or warning to drivers.
027 The system shall distribute indicator and fixed sign information, including static sign information (e.g., stop, curve warning, guide signs, service signs, and directional signs) and dynamic information (e.g., current signal states and local conditions wa 03 Emission Management needs to be able to provide summary emission information or warning to drivers.
028 The system shall return system operational status to the controlling center. 03 Emission Management needs to be able to provide summary emission information or warning to drivers.
029 The system shall measure or estimate vehicle emissions. 02 Emissions Management needs to be able to measure vehicle emissions data collected from individual vehicles at the roadside in order to identify high emitting vehicles.
030 The system shall transmit current and average emissions measures to the Transit Management Center. 02 Emissions Management needs to be able to measure vehicle emissions data collected from individual vehicles at the roadside in order to identify high emitting vehicles.
031 The system shall directly measures or estimates current and average vehicle emissions. 02 Emissions Management needs to be able to measure vehicle emissions data collected from individual vehicles at the roadside in order to identify high emitting vehicles.
032 The system shall provide the vehicle emissions information to infrastructure systems. 02 Emissions Management needs to be able to measure vehicle emissions data collected from individual vehicles at the roadside in order to identify high emitting vehicles.
033 The system shall monitor the status of vehicle convenience and safety systems (wiper status, headlight status, traction control system status) that can be used to measure environmental conditions and record snapshots of significant events in these systems 01 Emissions Management needs to be able to measure wide area pollution data in order to monitor wide area pollution levels.
034 The system shall transmit environmental probe data to field equipment located along the roadway using short range communications. 01 Emissions Management needs to be able to measure wide area pollution data in order to monitor wide area pollution levels.
035 The system shall receive advisory information, such as evacuation information, proximity to a maintenance and construction vehicle, wide-area alerts, work zone intrusion information, variable speed limits, tunnel entrance restrictions, and other special i 03 Emission Management needs to be able to provide summary emission information or warning to drivers.
036 The system shall receive indicator and fixed sign information including static sign information (e.g., stop, curve warning, guide signs, service signs, and directional signs) and dynamic information (e.g., current signal and traffic meter states and local 03 Emission Management needs to be able to provide summary emission information or warning to drivers.
037 The system shall store a translation table for road sign and message templates used for in-vehicle display. 03 Emission Management needs to be able to provide summary emission information or warning to drivers.
038 The system shall present the received information to the driver in audible or visual forms without impairing the driver's ability to control the vehicle in a safe manner. 03 Emission Management needs to be able to provide summary emission information or warning to drivers.
039 The system shall present to the driver a visual display of static sign information or dynamic roadway conditions information 03 Emission Management needs to be able to provide summary emission information or warning to drivers.
040 The system shall provide to the driver an audible presentation of static sign information or dynamic roadway conditions information 03 Emission Management needs to be able to provide summary emission information or warning to drivers.