Transport Canada
www.tc.gc.ca
Home > Transport Canada > Innovation > Intelligent Transportation Systems > Architecture
> ITS Architecture for Canada Version 2.0
> Physical Architecture
> Entities
>Emissions Management
Innovation
Browse Resources
Innovation Contact Information
Browse By Mode
Browse By Subject
About Us
This subsystem 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.
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
Inputs/Outputs: Architecture Flows and Data Flows
- archive requests - 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:
- archive status - 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:
- registration - Registered owner of vehicle and associated vehicle information.
Data Flows:
- emissions archive data - 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:
- license request - Request supporting registration data based on license plate read during violation.
Data Flows:
- pollution data display - 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:
- air quality information - Aggregated region-wide measured air quality data and possible pollution incident information.
Data Flows:
- map update request - Request for a map update which could include a new underlying map or map layer updates.
Data Flows:
Emissions Management > Media
- air quality information - Aggregated region-wide measured air quality data and possible pollution incident information.
Data Flows:
- pollution data parameters - User input from the system operator including nominal pollution data compliance (reference) levels for each sector of an urban area.
Data Flows:
- map updates - Map update which could include a new underlying static or real-time map or map layer(s) update.
Data Flows:
- volume weather information - Accumulated forecasted and current weather data (e.g., temperature, pressure, wind speed, wind direction, humidity, precipitation, visibility, light conditions, etc.).
Data Flows:
- area pollution 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.
Data Flows:
- vehicle emissions data - Measured emissions of specific vehicles comprised of exhaust pollutants including hydrocarbons, carbon monoxide, and nitrogen oxides.
Data Flows: