ATMS11-Emissions Monitoring and Management (Service Package*)

Description

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 subsystem 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 TDM programs, policies, and regulations.

Service Package Graphic

Emissions Data ManagementRoadway Emissions MonitoringRoadway Equipment CoordinationVehicle On-Board Diagnostics SystemEmissions Management OperatorRoadwayEmissions ManagementMediaTraffic ManagementVehicle CharacteristicsInformation Service ProviderMap Update ProviderEnvironmentWeather ServiceEnforcement AgencyOther RoadwayDriverVehiclevehicle diagnostics datavehicle signage datapollutant levelspollution data parametersair quality informationmap update requestmap updateswidearea statistical pollution informationpollution state data requestvehicle characteristicsair quality informationpollution data displayemissions sensor controlpollution sensor controlarea pollution datavehicle emissions dataweather informationemissions violation notificationroadway equipment coordinationdriver updates

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

Includes Architecture Flows:

Source Architecture Flow Destination In Graphic
Basic Vehicle basic vehicle measures Vehicle No
DMV registration Emissions Management No
Emissions Management license request DMV No
Emissions Management pollution data display Emissions Management Operator Yes
Emissions Management emissions violation notification Enforcement Agency Yes
Emissions Management air quality information Information Service Provider Yes
Emissions Management map update request Map Update Provider Yes
Emissions Management air quality information Media Yes
Emissions Management emissions sensor control Roadway Yes
Emissions Management pollution sensor control Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Roadway Yes
Emissions Management widearea statistical pollution information Traffic Management Yes
Emissions Management Operator pollution data parameters Emissions Management Yes
Environment pollutant levels Roadway Yes
Map Update Provider map updates Emissions Management Yes
Other Roadway roadway equipment coordination Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Roadway Yes
Roadway driver information Driver No
Roadway area pollution data Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Emissions Management Yes
Roadway vehicle emissions data Emissions Management Yes
Roadway roadway equipment coordination Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Other Roadway Yes
Roadway vehicle signage data Indicates that the associated architecture flow either has been or will be addressed by ITS Standards Vehicle Yes
Traffic Management pollution state data request Emissions Management Yes
Vehicle driver updates Driver Yes
Vehicle vehicle diagnostics data Roadway Yes
Vehicle Characteristics vehicle characteristics Roadway Yes
Weather Service weather information Emissions Management Yes
    - This icon indicates that the associated architecture flow either has been or will be addressed by ITS Standards. Select the architecture flow for more information on relevant standards activities.

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; Reduce environmental impacts

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.

Related ITS Applications of ITS Taxonomy

Classification Category ITS Application Area ITS Application(s)
Intelligent Infrastructure Freeway Management Surveillance Traffic

User Services related to this Service Package:

User Service
1.8 Travel Demand Management
1.9 Emissions Testing And Mitigation

Transaction Set Diagram

Note that this transaction set diagram (TSD) is only 1 of the 2 TSDs and so only a portion of the numbered items below refer to the TSD.
ATMS11 transaction set diagrams: Part 1, Part 2,



The source graphic, a Windows Metafile (WMF), for the TSDs can be downloaded here: TSD Part 1, TSD Part 2,

The following discusses how the National ITS Architecture provides the transportation service described by this service package. Each numbered item describes the operation of that portion of the service package identified with the corresponding number on the transaction set diagram.

  1. The Emissions Management Subsystem (EMMS) collects air quality information using distributed sensors. Environmental pollutant levels are monitored using sensors that provide area pollution data back to the EMMS. The EMMS controls the air quality sensors (pollution sensor control).

  2. The Emissions Management Subsystem (EMMS) also monitors emissions of passing vehicles. Passing vehicles may support this monitoring by collecting basic vehicle measures and providing vehicle diagnostics data that includes drive train performance and collected emissions data to the Roadway using Field-Vehicle Communications. The EMMS provides the current criteria of acceptable emission levels and control parameters (emissions sensor control) to the monitoring equipment on the Roadway. The equipment receives and/or measures emissions of passing vehicles and identifies vehicles (vehicle characteristics) that meet or exceed the acceptable standards. Vehicle emissions data is sent from the Roadway to the Emissions Management Subsystem.

  3. There are several ways to handle vehicles that exceed acceptable emissions levels. First, roadway equipment can be coordinated (roadway equipment coordination) to allow the emission equipment to cause a prescribed message to appear on a roadway information device (e.g., DMS) to notify the offending driver (driver information). This equipment coordination can be peer-to-peer, master-slave, or in other configurations. Second, Field-Vehicle Communications can be used to communicate emissions information to vehicles (vehicle signage data) which then present the information to their drivers (driver updates).

  4. Alternatively, emissions violations detected by the Emissions Management Subsystem may be sent to the DMV (license request) to determine the registered owner of the vehicle (registration). Violations (emissions violation notification) are reported to an Enforcement Agency.

  5. The Emissions Management Operator can request pollution data compliance levels for a specific region (pollution data parameters) from the Emissions Management Subsystem. The Emissions Management Subsystem responds with reference and/or current pollution status details (pollution data display) for the specified area.

  6. The Emissions Management Subsystem analyzes the results of the collected area pollution data, factors in the weather information provided by the Weather Service, and may choose to display the information on a map of the transportation network. To keep the base map up to date, map updates can be acquired from a Map Update Provider upon request (map update request), on a set schedule, or as revisions warrant it.

  7. Area-specific pollution information may be provided to the Traffic Management Subsystem (widearea statistical pollution information) upon request (pollution state data request). This information may be used by the TMS to assist in the implementation of environmentally sensitive Travel Demand Management (TDM) programs, policies, and regulations.

  8. Area-specific pollution information (air quality information) may also be provided to the Information Service Provider and the Media for dissemination to travelers.