Emissions Management Operator --> Emissions Management Center:
emissions operator input
Definitions
emissions operator input (Information Flow): Input from the system operator including nominal emissions data compliance (reference) levels for each sector of an urban area.
Emissions Management Operator (Source Physical Object): 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.
Emissions Management Center (Destination Physical Object): 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.
Included In
This Triple is in the following Service Packages:
This triple is associated with the following Functional Objects:
This Triple is described by the following Functional View Data Flows:
- femo-emissions_and_pollution_data_information_request
- femo-emissions_and_pollution_parameter_updates
This Triple has the following triple relationships:
Relationship | Source | Destination | Flow |
---|---|---|---|
Interactive | Emissions Management Center | Emissions Management Operator | emissions operator presentation |
Communication Solutions
No communications solutions identified.Characteristics
None defined |
Interoperability | Description |
---|---|
Not Applicable | Interoperability ratings don't apply per se to some types of interfaces like human interfaces. These interfaces may still benefit from associated standards (e.g., ergonomic and human factors standards for human interfaces), but the primary motive for these standards is not interoperability. |
Security
Information Flow Security | ||||
---|---|---|---|---|
Confidentiality | Integrity | Availability | ||
Rating | Moderate | High | High | |
Basis | 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. |