Transit Management Center --> Other Transit Management Centers:
transit service coordination
This triple is bi-directional. See also
Other Transit Management Centers --> Transit Management Center: transit service coordination
Definitions
transit service coordination (Information Flow): Schedule coordination or AVL information shared between local/regional transit organizations. This includes coordination of connections and control parameters between transit properties as well as coordination of transit-related maintenance activities.
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.
Other Transit Management Centers (Destination Physical Object): Representing another transit operations center, 'Other Transit Management Centers' is intended to provide a source and destination for information flows between peer transit management centers. It enables transit management activities to be coordinated across geographic boundaries or jurisdictions.
Included In
This Triple is in the following Service Packages:
- PS12: Disaster Response and Recovery
- PS13: Evacuation and Reentry Management
- PT14: Multi-modal Coordination
- PT17: Transit Connection Protection
- TM09: Integrated Decision Support and Demand Management
This triple is associated with the following Functional Objects:
- Transit Center Connection Protection
- Transit Center Multi-Modal Coordination
- Transit Center Security
- Transit Evacuation Support
This Triple is described by the following Functional View Data Flows:
- totrm-individual_service_request
- totrm-transit_service_data
- totrm-transit_vehicle_locations_data_for_coordination
This Triple has the following triple relationships:
Relationship | Source | Destination | Flow |
---|---|---|---|
Request-Response | Other Transit Management Centers | Transit Management Center | transit service coordination |
Communication Solutions
- EU: SIRI - Secure Internet (ITS) (6)
- US: GTFS - Secure Internet (ITS) (13)
- US: TCIP - Secure Internet (ITS) (18)
- (None-Data) - Secure Internet (ITS) (43)
Selected Solution
Solution Description
ITS Application Entity
CEN 15531-5 CEN 15213-4 CEN 15531-3 CEN 12896-4 CEN 12896-6 |
Click gap icons for more info.
|
||
Mgmt
|
Facilities
CEN 15531-2 |
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 | 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 | Moderate | Moderate | |
Basis | Coordination between transit systems is generally not sensitive, however this flow may include information related to serving individual connection protection requests that are sensitive. | If this information is not timely or correct, transit agencies may not properly coordinate, leaving some users unserved. | If this information is not timely or correct, transit agencies may not properly coordinate, leaving some users unserved. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |