Link Type: Center to Center
Transportation Information Center --> Transit Management Center:
shared use status
Definitions
shared use status (Information Flow): Status of usage by shared use providers. Includes asset inventory and status. Could also include information on specific travelers to support multimodal trip planning.
Transportation Information Center (Source 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.
Transit Management Center (Destination 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.
Included In
This Triple is in the following Service Packages:
- None
This Triple is in the following Functional Objects:
- None
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
None |
Communication Solutions
-
EU: SIRI - Secure Internet (ITS) (3)
-
GBFS - Secure Internet (ITS) (3)
-
US: MDS - Secure Internet (ITS) (3)
- (None-Data) - Secure Internet (ITS) (32)
- (None-Data) - Apache Kafka (36)
- (None-Data) - OMG DDS (36)
-
Data for Distribution (TBD) - Apache Kafka (36)
-
Data for Distribution (TBD) - OMG DDS (36)
- (None-Data) - OASIS MQTT (42)
-
Data for Distribution (TBD) - OASIS MQTT (42)
- (None-Data) - OASIS AMQP (45)
-
Data for Distribution (TBD) - OASIS AMQP (45)
Selected Solution

Solution Description
ITS Application Entity
![]() GBFS ![]() |
Click gap icons for more info.
|
||
Mgmt
|
Facilities
IETF RFC 7159 ![]() IETF RFC 9110 ![]() IETF RFC 9112 ![]() |
Security
![]() ![]() |
|
TransNet
|
|||
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 | Source |
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 | Moderate | Moderate | |
Basis | Contains information for a specific traveler. If no specific traveler data is included, this could be LOW. | If this is corrupted or modified the initiator may not receive his shared use booking. | If this service is not available then the shared use item may not be reserved, lessening its utility and failing to provide the service the (PID) user needs. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |