|
Triple
Emergency Management Center to Transportation Information Center: incident information
Flow Description
Notification of existence of incident and expected severity, location, time and nature of incident. As additional information is gathered and the incident evolves, updated incident information is provided. Incidents include any event that impacts transportation system operation ranging from routine incidents (e.g., disabled vehicle at the side of the road) through large-scale natural or human-caused disasters that involve loss of life, injuries, extensive property damage, and multi-jurisdictional response. This also includes special events, closures, and other planned events that may impact the transportation system. May also indicate incident strategies being implemented. This flow should coordinate incident response information as part of the info shared as the incident evolves,
|
|
Solutions
   Solution Description
This solution is used within the U.S. and Australia. It combines standards associated with (None-Data) with those for C-C: NTCIP Messaging. The (None-Data) standards include an unspecified set of standards at the upper layers. The C-C: NTCIP Messaging standards include lower-layer standards that support partially secure communications between two centres as commonly used in the US.
|
|
Triple Solution Gap
|
|
ITS Info
 
Development needed
 |
Click gap icons for more info.
|
||
|
Mgmt
|
Facility
|
Security
IETF RFC 5246
|
|
|
TransNet
|
|||
|
SubNet
Internet Subnet Alternatives
|
|||
