Transit Management Center --> Traffic Management Center:
transit system data
Definitions
transit system data (Information Flow): Current transit system operations information indicating current transit routes and fares, the level of service on each route, and the progress of individual vehicles along their routes for use in forecasting demand and estimating current transportation network performance.
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.
Traffic Management Center (Destination Physical Object): The 'Traffic Management Center' monitors and controls traffic and the road network. It represents centers that manage a broad range of transportation facilities including freeway systems, rural and suburban highway systems, and urban and suburban traffic control systems. It communicates with ITS Roadway Equipment and Connected Vehicle Roadside Equipment (RSE) to monitor and manage traffic flow and monitor the condition of the roadway, surrounding environmental conditions, and field equipment status. It manages traffic and transportation resources to support allied agencies in responding to, and recovering from, incidents ranging from minor traffic incidents through major disasters.
Included In
This Triple is in the following Service Packages:
This triple is associated with the following Functional Objects:
- TMC Multi-Modal Coordination
- TMC Traffic Network Performance Evaluation
- Transit Center Multi-Modal Coordination
This Triple is described by the following Functional View Data Flows:
- transit_fare_direct_details
- transit_running_data_for_demand
- transit_services_changes_response
- transit_services_for_demand
This Triple has the following triple relationships:
None |
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)
- 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)
Selected Solution
Solution Description
ITS Application Entity
Development needed |
Click gap icons for more info.
|
||
Mgmt
Development needed |
Facilities
OASIS AMQP |
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 | 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 | Low | |
Basis | Coordination information between transit and traffic agencies, if compromised, has no obvious impact. | Coordination information between transit and traffic agencies needs to be correct, or trip errors (improper dispatch, lack of service) may occur. | Some dynamism in this flow, depending on the level of interactivity and coordination, this might be Low. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | False |