Emergency Management Center --> Transit Management Center:
transportation system status
Definitions
transportation system status (Information Flow): Current status and condition of transportation infrastructure (e.g., tunnels, bridges, interchanges, TMC offices, maintenance facilities). In case of disaster or major incident, this flow provides an assessment of damage sustained by the surface transportation system including location and extent of the damage, estimate of remaining capacity and necessary restrictions, and time frame for repair and recovery.
Emergency Management Center (Source Physical Object): The 'Emergency Management Center' represents systems that support incident management, disaster response and evacuation, security monitoring, and other security and public safety-oriented ITS applications. It includes the functions associated with fixed and mobile public safety communications centers including public safety call taker and dispatch centers operated by police (including transit police), fire, and emergency medical services. It includes the functions associated with Emergency Operations Centers that are activated at local, regional, state, and federal levels for emergencies and the portable and transportable systems that support Incident Command System operations at an incident. This Center also represents systems associated with towing and recovery, freeway service patrols, HAZMAT response teams, and mayday service providers.
It manages sensor and surveillance equipment used to enhance transportation security of the roadway infrastructure (including bridges, tunnels, interchanges, and other key roadway segments) and the public transportation system (including transit vehicles, public areas such as transit stops and stations, facilities such as transit yards, and transit infrastructure such as rail, bridges, tunnels, or bus guideways). It provides security/surveillance services to improve traveler security in public areas not a part of the public transportation system.
It monitors alerts, advisories, and other threat information and prepares for and responds to identified emergencies. It coordinates emergency response involving multiple agencies with peer centers. It stores, coordinates, and utilizes emergency response and evacuation plans to facilitate this coordinated response. Emergency situation information including damage assessments, response status, evacuation information, and resource information are shared The Emergency Management Center also provides a focal point for coordination of the emergency and evacuation information that is provided to the traveling public, including wide-area alerts when immediate public notification is warranted.
It tracks and manages emergency vehicle fleets using real-time road network status and routing information from the other centers to aid in selecting the emergency vehicle(s) and routes, and works with other relevant centers to tailor traffic control to support emergency vehicle ingress and egress, implementation of special traffic restrictions and closures, evacuation traffic control plans, and other special strategies that adapt the transportation system to better meet the unique demands of an emergency.
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:
- Emergency Evacuation Support
- Emergency Response Management
- Emergency Secure Area Sensor Management
- Transit Center Security
This Triple is described by the following Functional View Data Flows:
- disaster_transportation_system_status_for_transit
- evacuation_transportation_system_status_for_transit
- infrastructure_integrity_status_for_transit
This Triple has the following triple relationships:
None |
Communication Solutions
-
(None-Data) - Secure Internet (ITS) (32)
-
(None-Data) - Apache Kafka (36)
-
(None-Data) - OMG DDS (36)
-
(None-Data) - OASIS MQTT (42)
-
(None-Data) - OASIS AMQP (45)
Selected Solution
![](../../images/flags/au.png)
![](../../images/flags/eu.png)
![](../../images/flags/us.png)
Solution Description
ITS Application Entity
![]() Development needed ![]() |
Click gap icons for more info.
|
||
Mgmt
|
Facilities
Development needed ![]() |
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 | High | Moderate | |
Basis | The data contained within this flow is also deliverd to a TIC, and center-originating flows destined for a TIC don't contain any personal or confidential information, and are eventually intended for some kind of public consumption. If this instance of the flow includes more information than went to the TIC, this could be MODERATE. | Emergency-related data needs to be correct or safety-affecting decisions may have severe negative consequences. | MODERATE only because alternative mechanisms for receiving this data should be available. Could be HIGH if this is the only mechanism. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | False |