Transit Management Center --> Media:
transit information for media

Definitions

transit information for media (Information Flow): Report of transit schedule deviations for public dissemination through the media.

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.

Media (Destination Physical Object): 'Media' represents the information systems that provide traffic reports, travel conditions, and other transportation-related news services to the traveling public through radio, TV, and other media. Traffic and travel advisory information that are collected by ITS are provided to this object. It is also a source for traffic flow information, incident and special event information, and other events that may have implications for the transportation system.

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:

This Triple has the following triple relationships:

None

Communication Solutions

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

Selected Solution

Data for Distribution (TBD) - Apache Kafka

Solution Description

This solution is used within the U.S.. It combines standards associated with Data for Distribution (TBD) with those for Apache Kafka. The Data for Distribution (TBD) standards include a placeholder for upper-layer standards necessary to define the data (elements and structures) necessary to complete a solution for the information flow based on data distribution technologies. The data standard will need to include a specific customization for the desired data distribution technology used (e.g., Kafka, DDS, etc.).. The Apache Kafka standards include lower-layer open source code that supports data distribution of specific types of data.

ITS Application Entity
Mind the gap

Development needed
Click gap icons for more info.
Mgmt

Apache Zookeeper
Facilities
Mind the gapMind the gap

Apache Kafka
Apache Zookeeper
Security

IETF RFC 8446
TransNet

IP Alternatives
IETF RFC 9293
Access

Internet Subnet Alternatives
TransNet TransNet

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Access Access

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

ITS Application ITS Application

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Mgmt Mgmt

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Facility Facility

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

Security Security

TempBCL2 TempSTDL2

TempBCL3 TempSTDL3

TempBCL4 TempSTDL4

TempBCL5 TempSTDL5

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 Moderate
Basis This information is intended for distribution to all members of the traveling public. Transit information needs to be accurate, as it will be used by travelers to make decisions regarding their travel. Inaccurate or corrupted data could reduce overall mobility and certainly impact individual drivers. There should be other means for getting this information, but as this is the 'source flow' for a wide area broadcast with a huge potential distribution, the breadth of the impact covers all travelers.


Security Characteristics Value
Authenticable True
Encrypt False