Event Promoter System --> Emissions Management Center:
event plans

Definition
Included In
Communication Solutions
Characteristics
Security

Definitions

event plans (Information Flow): Plans for major events possibly impacting traffic.

Event Promoter System (Source Physical Object): 'Event Promoter System' represents Special Event Sponsors that have knowledge of events that may impact travel on roadways or other modal means. Examples of special event sponsors include sporting events, conventions, motorcades/parades, and public/political events. These promoters interface to the ITS to provide event information such as date, time, estimated duration, location, and any other information pertinent to traffic movement in the surrounding area.

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:

ST10: Low Emissions Zone Management

This triple is associated with the following Functional Objects:

Emissions Zone Management

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

feps-event_information_for_emissions

This Triple has the following triple relationships:

None

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) - Apache Kafka

Solution Description

This solution is used within Canada and the U.S.. It combines standards associated with (None-Data) with those for Apache Kafka. The (None-Data) standards include an unspecified set of standards at the upper layers. The Apache Kafka standards include lower-layer open source code that supports data distribution of specific types of data.

ITS Application Entity Development needed			Click gap icons for more info.
Mgmt Apache Zookeeper	Facilities Development needed Apache Kafka Apache Zookeeper	Security IETF RFC 8446
	TransNet IP Alternatives IETF RFC 9293
	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	Historical
Spatial Context	Regional
Acknowledgement	True
Cardinality	Unicast
Initiator	Destination
Authenticable	True
Encrypt	True

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	Moderate	High	Moderate
Basis	This will include PII of the event contact person, which should be protected from casual viewing. This flow will also include details of the planned event, which in some circumstances might not be entire public information and so again, should not be casually viewable.	Personal contact information needs to be correct, but so do the details of the planned event because of the potential severity of the event's impact. Generally the more significant the potential impact of the event, the higher this should be, but never below MODERATE.	There should be other mechanisms for getting this information, otherwise it would match integrity.

Security Characteristics	Value
Authenticable	True
Encrypt	True

Event Promoter System --> Emissions Management Center:event plans