Emissions Management (Subsystem*)

This Emissions Management Subsystem (EMMS) operates at a fixed location and may co-reside with the Traffic Management Subsystem or may operate in its own distinct location depending on regional preferences and priorities. This subsystem provides the capabilities for air quality managers to monitor and manage air quality. These capabilities include collecting emissions data from distributed emissions sensors within the roadway subsystem. These sensors monitor general air quality within each sector of the area and also monitor the emissions of individual vehicles on the roadway. The sector emissions measures are collected, processed, and used to identify sectors exceeding safe pollution levels. This information is provided to traffic management to implement strategies intended to reduce emissions in and around the problem areas. Emissions data associated with individual vehicles, supplied by the Roadway Subsystem, is also processed and monitored to identify vehicles that exceed standards. This subsystem provides any functions necessary to inform the violators and otherwise ensure timely compliance with emissions standards.

Functionality
Inputs/Outputs
Security
Subsystem Interfaces Diagram
Terminator Interfaces Diagram

Subsystem Interfaces Diagram

This is a context diagram for the entity Emissions Management Subsystem that shows the interfaces to subsystems and every architecture flow that this entity sends or receives, as defined in the National ITS Architecture. A complete list of all architecture flows shown on this diagram, is available under the Inputs/Outputs section on this page.

Get the Source Graphic, a Enhanced Windows Metafile (EMF), in ZIP format.

Terminator Interfaces Diagram

Get the Source Graphic, a Windows Metafile (WMF), in ZIP format.

Security Considerations:

The Emissions Management Subsystem processes vehicle emissions data and regional air quality data that are generally not sensitive to public disclosure. Also, while air quality is extremely important to everyone, the services provided by the Emissions Management Subsystem are generally not mission critical and could be lost or delayed for short periods of time without serious implications for public safety or operational efficiency of the transportation system. In most cases, normal precautions that are taken to protect data integrity will also suffice here since the threat of inadvertent or malicious tampering with data is not particularly high. There are scenarios where the security associated with Emissions Management will be more significant. For example, data integrity and confidentiality are more significant if the specific emissions management system is identifying emissions/pollution violators and collecting personal information and evidence of infractions. This information is both sensitive and subject to tampering. In most cases, system availability will not be critical, but a specific system may require higher availability if the network of sensors and data collected are relied upon to detect and report dangerous levels of pollutants or other airborne materials in emergency situations.

Functionality: Equipment Packages* and PSpecs*

Emissions Data Collection (Equipment Package*)
PSpecs:
- 1.5.9-Manage Emissions Archive Data
Emissions Data Management (Equipment Package*)
PSpecs:
- 1.5.1-Provide Emissions Operations Personnel Interface
- 1.5.10-Manage Emissions State Data Store
- 1.5.2-Process Pollution Data
- 1.5.3-Update Pollution Display Map Data
- 1.5.4-Manage Pollution State Data Store
- 1.5.7-Process Vehicle Emissions Data
- 1.5.8-Manage Emissions and Pollution Reference Data Stores
- 5.4.8-Process Emissions Violations

Inputs/Outputs: Architecture Flows* and Data Flows*

Archived Data Management Emissions Management

archive requests (Architecture Flow*) - A request to a data source for information on available data (i.e. "catalog") or a request that defines the data to be archived. The request can be a general subscription intended to initiate a continuous or regular data stream or a specific request intended to initiate a one-time response from the recipient.
Data Flows*:
- emissions_archive_request
archive status (Architecture Flow*) - Notification that data provided to an archive contains erroneous, missing, or suspicious data or verification that the data provided appears valid. If an error has been detected, the offending data and the nature of the potential problem are identified.
Data Flows*:
- emissions_archive_status

DMV Emissions Management

registration (Architecture Flow*) - Registered owner of vehicle and associated vehicle information.
Data Flows*:
- fdmv-emissions_violation_state_identity
- fdmv-emissions_violation_vehicle_registration

Emissions Management Archived Data Management

emissions archive data (Architecture Flow*) - Air quality and vehicle emissions information that is collected by sensors or derived from models. Content may include a catalog of available information, the actual information to be archived, and associated meta data that describes the archived information.
Data Flows*:
- emissions_archive_data

Emissions Management DMV

license request (Architecture Flow*) - Request supporting registration data based on license plate read during violation.
Data Flows*:
- tdmv-emissions_violation_identity_code
- tdmv-emissions_violation_vehicle_license

Emissions Management Emissions Management Operator

pollution data display (Architecture Flow*) - 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.
Data Flows*:
- temo-pollution_data_display
- temo-vehicle_emissions_data

Emissions Management Enforcement Agency

emissions violation notification (Architecture Flow*) - Notification to enforcement agency of a detected vehicle emissions violation.
Data Flows*:
- tea-emissions_violation_data

Emissions Management Information Service Provider

air quality information (Architecture Flow*) - Aggregated region-wide measured air quality data and possible pollution incident information.
Data Flows*:
- current_traffic_pollution_data

Emissions Management Map Update Provider

map update request (Architecture Flow*) - Request for a map update which could include a new underlying map or map layer updates.
Data Flows*:
- tmup-request_pollution_display_update

Emissions Management Media

air quality information (Architecture Flow*) - Aggregated region-wide measured air quality data and possible pollution incident information.
Data Flows*:
- tm-pollution_data

Map Update Provider Emissions Management

map updates (Architecture Flow*) - Map update which could include a new underlying static or real-time map or map layer(s) update.
Data Flows*:
- fmup-pollution_display_update

Roadway Emissions Management

area pollution data (Architecture Flow*) - 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.
Data Flows*:
- pollution_sensor_data
- pollution_sensor_status
vehicle emissions data (Architecture Flow*) - Measured emissions of specific vehicles comprised of exhaust pollutants including hydrocarbons, carbon monoxide, and nitrogen oxides.
Data Flows*:

Traffic Management Emissions Management

pollution state data request (Architecture Flow*) - Aggregated emissions data information request.
Data Flows*:
- pollution_state_data_request

Weather Service Emissions Management

weather information (Architecture Flow*) - Accumulated forecasted and current weather data (e.g., temperature, pressure, wind speed, wind direction, humidity, precipitation, visibility, light conditions, etc.).
Data Flows*:
- fws-current_weather_observations
- fws-weather_forecasts