Traffic Management Center --> Transit Management Center:
transportation operational strategies
Definitions
transportation operational strategies (Information Flow): Operational strategies for each operating agency in a transportation corridor, downtown area, or other travel-impacted area, providing an integrated operations strategy for the freeways, tollways, arterials, transit services, parking facilities, and other transportation-related facilities in the area. These strategies can include dynamic adjustments to transit fares and tolls, parking fees and restrictions, dynamic lane restriction changes, and other active demand management strategies.
Traffic Management Center (Source 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.
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:
This triple is associated with the following Functional Objects:
This Triple is described by the following Functional View Data Flows:
- transit_corridor_operational_strategies
- transit_fare_direct_request
- transit_services_changes_request
- transit_services_demand_request
This Triple has the following triple relationships:
None |
Communication Solutions
- (None-Data) - Secure Internet (ITS) (43)
- (None-Data) - Apache Kafka (44)
- (None-Data) - OMG DDS (44)
- (None-Data) - OASIS MQTT (50)
- (None-Data) - OASIS AMQP (61)
Selected Solution
Solution Description
ITS Application Entity
Development needed |
Click gap icons for more info.
|
||
Mgmt
Development needed |
Facilities
Development needed 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 | 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 | No PII is involved. However this flow should contain coordinated response information: how various transportation related entities respond to different conditions. This type of information is block intelligence that could be useful to an attacker or criminal, and thus should not be distributed in the clear. | If this information is corrupted or modified, transportation management entities may not have well integrated plans for one or more operational scenarios, impacting mobility and safety in those conditions. Given that this data exchange is likely the product of personal work between agencies, and that follow up is likely, justify MODERATE and not HIGH. | Probably not updated often, but could contain large amounts of information; additionally in times of crisis may need some more update, so MODERATE justifiable. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | True |