Transit Management Center --> Transportation Information Center:
transit schedule adherence information

Definition
Included In
Communication Solutions
Characteristics
Security

Definitions

transit schedule adherence information (Information Flow): Dynamic transit schedule adherence and transit vehicle location information.

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.

Transportation Information Center (Destination Physical Object): The 'Transportation Information Center' collects, processes, stores, and disseminates transportation information to system operators and the traveling public. The physical object can play several different roles in an integrated ITS. In one role, the TIC provides a data collection, fusing, and repackaging function, collecting information from transportation system operators and redistributing this information to other system operators in the region and other TICs. In this information redistribution role, the TIC provides a bridge between the various transportation systems that produce the information and the other TICs and their subscribers that use the information. The second role of a TIC is focused on delivery of traveler information to subscribers and the public at large. Information provided includes basic advisories, traffic and road conditions, transit schedule information, yellow pages information, ride matching information, and parking information. The TIC is commonly implemented as a website or a web-based application service, but it represents any traveler information distribution service.

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:

transit_vehicle_deviations_details

This Triple has the following triple relationships:

Relationship	Source	Destination	Flow
Depends On	Transit Vehicle OBE	Transit Management Center	transit vehicle location data
Depends On	Transit Vehicle OBE	Transit Management Center	transit vehicle schedule performance

Communication Solutions

EU: SIRI - Secure Internet (ITS) (6)
US: GTFS real-time - Secure Internet (ITS) (10)
US: TCIP - Secure Internet (ITS) (18)
(None-Data) - Secure Internet (ITS) (43)
Data for Distribution (TBD) - Apache Kafka (44)
Data for Distribution (TBD) - OMG DDS (44)
(None-Data) - OASIS MQTT (50)
Data for Distribution (TBD) - OASIS MQTT (50)
Data for Distribution (TBD) - 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

Data for Distribution (TBD) - OMG DDS

Solution Description

This solution is used within Canada and the U.S.. It combines standards associated with Data for Distribution (TBD) with those for OMG DDS. 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 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 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	Moderate
Basis	Eventually intended for public consumption, so no need to obfuscate.	While accuracy of this data is important for decision making purposes, applications should be able to function without it. Thus MODERATE generally.	While accuracy of this data is important for decision making purposes, applications should be able to cfunction without it. Thus MODERATE generally.

Security Characteristics	Value
Authenticable	True
Encrypt	False

Transit Management Center --> Transportation Information Center:transit schedule adherence information