Transit Management Center --> Emissions Management Center:
transit emissions data

Definition
Included In
Communication Solutions
Characteristics
Security

Definitions

transit emissions data (Information Flow): 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 Management Center (Source Physical Object): 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.

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:

ST01: Emissions Monitoring

This triple is associated with the following Functional Objects:

This Triple is described by the following Functional View Data Flows:

transit_vehicle_emissions_data

This Triple has the following triple relationships:

Relationship	Source	Destination	Flow
Depends On	Transit Vehicle OBE	Transit Management Center	transit vehicle emissions

Communication Solutions

(None-Data) - Secure Internet (ITS) (43)
(None-Data) - Apache Kafka (44)
(None-Data) - OMG DDS (44)
(None-Data) - OASIS MQTT (50)
(None-Data) - OASIS AMQP (61)

Solutions are sorted in ascending Gap Severity order. The Gap Severity is the parenthetical number at the end of the solution.

Selected Solution

(None-Data) - OMG DDS

Solution Description

This solution is used within Canada and the U.S.. It combines standards associated with (None-Data) with those for OMG DDS. The (None-Data) standards include an unspecified set of standards at the upper layers. The OMG DDS standards include lower-layer standards that support secure data sharing and command operations between remote devices.

ITS Application Entity Development needed			Click gap icons for more info.
Mgmt OMG DDS	Facilities Development needed OMG DDS OMG DDS-RPC OMG DDSI-RTPS	Security OMG DDS-Security
	TransNet IETF RFC 768 IP Alternatives
	Access Internet Subnet Alternatives

Note that some layers might have alternatives, in which case all of the gap icons associated with every alternative may be shown on the diagram, but the solution severity calculations (and resulting ordering of solutions) includes only the issues associated with the default (i.e., best, least severe) alternative.

Characteristics

Characteristic	Value
Time Context	Recent
Spatial Context	Regional
Acknowledgement	True
Cardinality	Unicast
Initiator	Destination
Authenticable	True
Encrypt	False

Interoperability	Description
Regional	Interoperability throughout the geopolitical region is highly desirable, but if implemented differently in different transportation management jurisdictions, significant benefits will still accrue in each jurisdiction. Regardless, this Information Flow Triple should be implemented consistently within a transportation jurisdiction (i.e., the scope of a regional architecture).

Security

Information Flow Security
	Confidentiality	Integrity	Availability
Rating	Low	Moderate	Low
Basis	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.

Security Characteristics	Value
Authenticable	True
Encrypt	False

Transit Management Center --> Emissions Management Center:transit emissions data