Emergency Management Center --> Transportation Information Center:
incident information for public
Definitions
incident information for public (Information Flow): Report of current desensitized incident information prepared for public dissemination.
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.
Transportation Information Center (Destination 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.
Included In
This Triple is in the following Service Packages:
- CVO09: Freight-Specific Dynamic Travel Planning
- PS07: Incident Scene Safety Monitoring
- PS14: Disaster Traveler Information
- TI01: Broadcast Traveler Information
- TI02: Personalized Traveler Information
- TM08: Traffic Incident Management System
This triple is associated with the following Functional Objects:
- Emergency Early Warning System
- Emergency Incident Command
- Emergency Response Management
- TIC Data Collection
This Triple is described by the following Functional View Data Flows:
This Triple has the following triple relationships:
None |
Communication Solutions
-
EU: DATEX - DATEX Messaging (3)
-
US: TMDD - NTCIP Messaging (10)
-
(None-Data) - Secure Internet (ITS) (32)
-
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)
-
Data for Distribution (TBD) - OASIS AMQP (45)
Selected Solution
![](../../images/flags/us.png)
Solution Description
ITS Application Entity
![]() Development needed ![]() |
Click gap icons for more info.
|
||
Mgmt
Apache Zookeeper ![]() |
Facilities
![]() ![]() Apache Kafka ![]() Apache Zookeeper ![]() |
Security
IETF RFC 8446 ![]() |
|
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 | Moderate | |
Basis | Generally, 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. | Minor discrepancies in this data should not have a catastrophic effect, but it should be reasonably controlled and accurate. | A few missed messages should not have a significant effect. However, most messages should make it through and the EMC should be able to know if the TIC has received a message. |
Security Characteristics | Value |
---|---|
Authenticable | True |
Encrypt | False |