< < PS11 : PS12 : PS13 > >

PS12: Disaster Response and Recovery

This service package enhances the ability of the surface transportation system to respond to and recover from disasters. It addresses the most severe incidents that require an extraordinary response from outside the local community. All types of disasters are addressed including natural disasters (hurricanes, earthquakes, floods, winter storms, tsunamis, etc.) and technological and man-made disasters (hazardous materials incidents, nuclear power plant accidents, and national security emergencies such as nuclear, chemical, biological, and radiological weapons attacks).

The service package supports coordination of emergency response plans, including general plans developed before a disaster as well as specific tactical plans with short time horizon that are developed as part of a disaster response. The service package provides enhanced access to the scene for response personnel and resources, provides better information about the transportation system in the vicinity of the disaster, and maintains situation awareness regarding the disaster itself. In addition, this service package tracks and coordinates the transportation resources - the transportation professionals, equipment, and materials - that constitute a portion of the disaster response.

The service package identifies the key points of integration between transportation systems and the public safety, emergency management, public health, and other allied organizations that form the overall disaster response. In this service package, the Emergency Management Center represents the federal, regional, state, and local Emergency Operations Centers and the Incident Commands that are established to respond to the disaster. The interface between the Emergency Management Center and the other centers provides situation awareness and resource coordination among transportation and other allied response agencies. In its role, traffic management implements special traffic control strategies and detours and restrictions to effectively manage traffic in and around the disaster. Maintenance and construction provides damage assessment of road network facilities and manages service restoration. Transit management provides a similar assessment of status for transit facilities and modifies transit operations to meet the special demands of the disaster. As immediate public safety concerns are addressed and disaster response transitions into recovery, this service package supports transition back to normal transportation system operation, recovering resources, managing on-going transportation facility repair, supporting data collection and revised plan coordination, and other recovery activities.

This service package builds on the basic traffic incident response service that is provided by TM08, the Traffic Incident Management service package. This service package addresses the additional complexities and coordination requirements that are associated with the most severe incidents that warrant an extraordinary response from outside the local jurisdictions and require special measures such as the activation of one or more emergency operations centers. Many users of ARC-IT will want to consider both TM08 and this service package since every region is concerned with both day-to-day management of traffic-related incidents and occasional management of disasters that require extraordinary response.

Disaster Response and Recovery is also supported by PS14, the "Disaster Traveler Information" service package that keeps the public informed during a disaster response. See that service package for more information.

Relevant Regions: Australia, Canada, European Union, and United States

Enterprise

Development Stage Roles and Relationships

Installation Stage Roles and Relationships

Operations and Maintenance Stage Roles and Relationships
(hide)

Source Destination Role/Relationship
Asset Management System Maintainer Asset Management System Maintains
Asset Management System Manager Asset Management System Manages
Asset Management System Owner Asset Management System Maintainer System Maintenance Agreement
Asset Management System Owner Asset Management System Manager Operations Agreement
Asset Management System Owner Emergency Management Center Maintainer Maintenance Data Exchange Agreement
Asset Management System Owner Emergency Management Center Owner Information Provision Agreement
Asset Management System Owner Emergency Management Center User Service Usage Agreement
Asset Management System Owner Emergency System Operator Application Usage Agreement
Asset Management System Supplier Asset Management System Owner Warranty
Emergency Management Center Maintainer Emergency Management Center Maintains
Emergency Management Center Manager Emergency Management Center Manages
Emergency Management Center Manager Emergency System Operator System Usage Agreement
Emergency Management Center Owner Emergency Management Center Maintainer System Maintenance Agreement
Emergency Management Center Owner Emergency Management Center Manager Operations Agreement
Emergency Management Center Owner Maint and Constr Center Personnel Application Usage Agreement
Emergency Management Center Owner Maint and Constr Management Center Maintainer Maintenance Data Exchange Agreement
Emergency Management Center Owner Maint and Constr Management Center Owner Information Exchange Agreement
Emergency Management Center Owner Maint and Constr Management Center User Service Usage Agreement
Emergency Management Center Owner Other Emergency Management Centers Maintainer Maintenance Data Exchange Agreement
Emergency Management Center Owner Other Emergency Management Centers Owner Information Exchange Agreement
Emergency Management Center Owner Other Emergency Management Centers User Service Usage Agreement
Emergency Management Center Owner Public Health System Maintainer Maintenance Data Exchange Agreement
Emergency Management Center Owner Public Health System Owner Information Exchange Agreement
Emergency Management Center Owner Public Health System User Service Usage Agreement
Emergency Management Center Owner Rail Operations Center Maintainer Maintenance Data Exchange Agreement
Emergency Management Center Owner Rail Operations Center Owner Information Exchange Agreement
Emergency Management Center Owner Rail Operations Center User Service Usage Agreement
Emergency Management Center Owner Traffic Management Center Maintainer Maintenance Data Exchange Agreement
Emergency Management Center Owner Traffic Management Center Owner Information Exchange Agreement
Emergency Management Center Owner Traffic Management Center User Service Usage Agreement
Emergency Management Center Owner Traffic Operations Personnel Application Usage Agreement
Emergency Management Center Owner Transit Management Center Maintainer Maintenance Data Exchange Agreement
Emergency Management Center Owner Transit Management Center Owner Information Exchange Agreement
Emergency Management Center Owner Transit Management Center User Service Usage Agreement
Emergency Management Center Owner Transit Operations Personnel Application Usage Agreement
Emergency Management Center Supplier Emergency Management Center Owner Warranty
Emergency System Operator Emergency Management Center Operates
Maint and Constr Center Personnel Maint and Constr Management Center Operates
Maint and Constr Management Center Maintainer Maint and Constr Management Center Maintains
Maint and Constr Management Center Manager Maint and Constr Center Personnel System Usage Agreement
Maint and Constr Management Center Manager Maint and Constr Management Center Manages
Maint and Constr Management Center Owner Emergency Management Center Maintainer Maintenance Data Exchange Agreement
Maint and Constr Management Center Owner Emergency Management Center Owner Information Exchange Agreement
Maint and Constr Management Center Owner Emergency Management Center User Service Usage Agreement
Maint and Constr Management Center Owner Emergency System Operator Application Usage Agreement
Maint and Constr Management Center Owner Maint and Constr Management Center Maintainer System Maintenance Agreement
Maint and Constr Management Center Owner Maint and Constr Management Center Manager Operations Agreement
Maint and Constr Management Center Owner Other Maint and Constr Mgmt Centers Maintainer Maintenance Data Exchange Agreement
Maint and Constr Management Center Owner Other Maint and Constr Mgmt Centers Owner Information Exchange Agreement
Maint and Constr Management Center Owner Other Maint and Constr Mgmt Centers User Service Usage Agreement
Maint and Constr Management Center Owner Traffic Management Center Maintainer Maintenance Data Exchange Agreement
Maint and Constr Management Center Owner Traffic Management Center Owner Information Exchange Agreement
Maint and Constr Management Center Owner Traffic Management Center User Service Usage Agreement
Maint and Constr Management Center Owner Traffic Operations Personnel Application Usage Agreement
Maint and Constr Management Center Supplier Maint and Constr Management Center Owner Warranty
Other Emergency Management Centers Maintainer Other Emergency Management Centers Maintains
Other Emergency Management Centers Manager Other Emergency Management Centers Manages
Other Emergency Management Centers Owner Emergency Management Center Maintainer Maintenance Data Exchange Agreement
Other Emergency Management Centers Owner Emergency Management Center Owner Information Exchange Agreement
Other Emergency Management Centers Owner Emergency Management Center User Service Usage Agreement
Other Emergency Management Centers Owner Emergency System Operator Application Usage Agreement
Other Emergency Management Centers Owner Other Emergency Management Centers Maintainer System Maintenance Agreement
Other Emergency Management Centers Owner Other Emergency Management Centers Manager Operations Agreement
Other Emergency Management Centers Supplier Other Emergency Management Centers Owner Warranty
Other Maint and Constr Mgmt Centers Maintainer Other Maint and Constr Mgmt Centers Maintains
Other Maint and Constr Mgmt Centers Manager Other Maint and Constr Mgmt Centers Manages
Other Maint and Constr Mgmt Centers Owner Maint and Constr Center Personnel Application Usage Agreement
Other Maint and Constr Mgmt Centers Owner Maint and Constr Management Center Maintainer Maintenance Data Exchange Agreement
Other Maint and Constr Mgmt Centers Owner Maint and Constr Management Center Owner Information Exchange Agreement
Other Maint and Constr Mgmt Centers Owner Maint and Constr Management Center User Service Usage Agreement
Other Maint and Constr Mgmt Centers Owner Other Maint and Constr Mgmt Centers Maintainer System Maintenance Agreement
Other Maint and Constr Mgmt Centers Owner Other Maint and Constr Mgmt Centers Manager Operations Agreement
Other Maint and Constr Mgmt Centers Supplier Other Maint and Constr Mgmt Centers Owner Warranty
Other Traffic Management Centers Maintainer Other Traffic Management Centers Maintains
Other Traffic Management Centers Manager Other Traffic Management Centers Manages
Other Traffic Management Centers Owner Other Traffic Management Centers Maintainer System Maintenance Agreement
Other Traffic Management Centers Owner Other Traffic Management Centers Manager Operations Agreement
Other Traffic Management Centers Owner Traffic Management Center Maintainer Maintenance Data Exchange Agreement
Other Traffic Management Centers Owner Traffic Management Center Owner Information Exchange Agreement
Other Traffic Management Centers Owner Traffic Management Center User Service Usage Agreement
Other Traffic Management Centers Owner Traffic Operations Personnel Application Usage Agreement
Other Traffic Management Centers Supplier Other Traffic Management Centers Owner Warranty
Other Transit Management Centers Maintainer Other Transit Management Centers Maintains
Other Transit Management Centers Manager Other Transit Management Centers Manages
Other Transit Management Centers Owner Other Transit Management Centers Maintainer System Maintenance Agreement
Other Transit Management Centers Owner Other Transit Management Centers Manager Operations Agreement
Other Transit Management Centers Owner Transit Management Center Maintainer Maintenance Data Exchange Agreement
Other Transit Management Centers Owner Transit Management Center Owner Information Exchange Agreement
Other Transit Management Centers Owner Transit Management Center User Service Usage Agreement
Other Transit Management Centers Owner Transit Operations Personnel Application Usage Agreement
Other Transit Management Centers Supplier Other Transit Management Centers Owner Warranty
Public Health System Maintainer Public Health System Maintains
Public Health System Manager Public Health System Manages
Public Health System Owner Emergency Management Center Maintainer Maintenance Data Exchange Agreement
Public Health System Owner Emergency Management Center Owner Information Exchange Agreement
Public Health System Owner Emergency Management Center User Service Usage Agreement
Public Health System Owner Emergency System Operator Application Usage Agreement
Public Health System Owner Public Health System Maintainer System Maintenance Agreement
Public Health System Owner Public Health System Manager Operations Agreement
Public Health System Supplier Public Health System Owner Warranty
Rail Operations Center Maintainer Rail Operations Center Maintains
Rail Operations Center Manager Rail Operations Center Manages
Rail Operations Center Owner Emergency Management Center Maintainer Maintenance Data Exchange Agreement
Rail Operations Center Owner Emergency Management Center Owner Information Exchange Agreement
Rail Operations Center Owner Emergency Management Center User Service Usage Agreement
Rail Operations Center Owner Emergency System Operator Application Usage Agreement
Rail Operations Center Owner Rail Operations Center Maintainer System Maintenance Agreement
Rail Operations Center Owner Rail Operations Center Manager Operations Agreement
Rail Operations Center Supplier Rail Operations Center Owner Warranty
Traffic Management Center Maintainer Traffic Management Center Maintains
Traffic Management Center Manager Traffic Management Center Manages
Traffic Management Center Manager Traffic Operations Personnel System Usage Agreement
Traffic Management Center Owner Emergency Management Center Maintainer Maintenance Data Exchange Agreement
Traffic Management Center Owner Emergency Management Center Owner Information Exchange Agreement
Traffic Management Center Owner Emergency Management Center User Service Usage Agreement
Traffic Management Center Owner Emergency System Operator Application Usage Agreement
Traffic Management Center Owner Maint and Constr Center Personnel Application Usage Agreement
Traffic Management Center Owner Maint and Constr Management Center Maintainer Maintenance Data Exchange Agreement
Traffic Management Center Owner Maint and Constr Management Center Owner Information Exchange Agreement
Traffic Management Center Owner Maint and Constr Management Center User Service Usage Agreement
Traffic Management Center Owner Other Traffic Management Centers Maintainer Maintenance Data Exchange Agreement
Traffic Management Center Owner Other Traffic Management Centers Owner Information Exchange Agreement
Traffic Management Center Owner Other Traffic Management Centers User Service Usage Agreement
Traffic Management Center Owner Traffic Management Center Maintainer System Maintenance Agreement
Traffic Management Center Owner Traffic Management Center Manager Operations Agreement
Traffic Management Center Supplier Traffic Management Center Owner Warranty
Traffic Operations Personnel Traffic Management Center Operates
Transit Management Center Maintainer Transit Management Center Maintains
Transit Management Center Manager Transit Management Center Manages
Transit Management Center Manager Transit Operations Personnel System Usage Agreement
Transit Management Center Owner Emergency Management Center Maintainer Maintenance Data Exchange Agreement
Transit Management Center Owner Emergency Management Center Owner Information Exchange Agreement
Transit Management Center Owner Emergency Management Center User Service Usage Agreement
Transit Management Center Owner Emergency System Operator Application Usage Agreement
Transit Management Center Owner Other Transit Management Centers Maintainer Maintenance Data Exchange Agreement
Transit Management Center Owner Other Transit Management Centers Owner Information Exchange Agreement
Transit Management Center Owner Other Transit Management Centers User Service Usage Agreement
Transit Management Center Owner Transit Management Center Maintainer System Maintenance Agreement
Transit Management Center Owner Transit Management Center Manager Operations Agreement
Transit Management Center Supplier Transit Management Center Owner Warranty
Transit Operations Personnel Transit Management Center Operates

Functional

This service package includes the following Functional View PSpecs:

Physical Object Functional Object PSpec Number PSpec Name
Emergency Management Center Emergency Incident Command 5.1.1.3 Collect Incident And Event Data
5.1.3 Communicate Emergency Status
5.1.4 Manage Emergency Response
5.3.2 Dispatch Vehicle
5.3.4 Assess Response Status
5.3.6 Maintain Vehicle Status
5.7.2 Provide Disaster Response Coordination
Emergency Response Management 5.1.1.3 Collect Incident And Event Data
5.1.2 Determine Coordinated Response Plan
5.1.3 Communicate Emergency Status
5.1.4 Manage Emergency Response
5.1.5 Manage Emergency Service Allocation Store
5.2 Provide Operator Interface for Emergency Data
5.3.1 Select Response Mode
5.7.1 Assess System Status For Disasters
5.7.2 Provide Disaster Response Coordination
5.7.3 Assess System Status For Evacuation
Maint and Constr Management Center MCM Incident Management 9.1.7 Process Road Network Information
9.2.2 Status Current M&C Activities and Transportation Infrastructure
9.2.3.4 Manage M&C Resource Needs
MCM Roadway Maintenance 9.1.4 Manage M&C Vehicle Fleet
9.2.1 Schedule M&C Activities
9.2.2 Status Current M&C Activities and Transportation Infrastructure
9.2.3.2 Determine Roadway M&C Needs
9.2.3.4 Manage M&C Resource Needs
9.2.3.5 Collect Roadside Equipment Status
9.2.5 Provide M&C Center Personnel Interface for Maint
9.2.6.3 Operate Infrastructure Monitoring Devices
9.2.8 Manage M&C Materials
Traffic Management Center TMC Incident Dispatch Coordination 1.1.4.1 Retrieve Traffic Data
1.1.5 Exchange Data with Other Traffic Centers
1.3.2.1 Store Possible Incident Data
1.3.2.2 Review and Classify Possible Incidents
1.3.2.3 Review and Classify Planned Events
1.3.2.6 Manage Traffic Routing
1.3.3.1 Respond to Current Incidents
1.3.4.1 Retrieve Incident Data
1.3.4.2 Provide Traffic Operations Personnel Incident Interface
1.3.4.3 Provide Media Incident Data Interface
1.3.4.4 Manage Resources for Incidents
1.3.5 Manage Incident Response Planning and Traffic Management Decision Support
1.3.6 Traffic Disaster Response Control
1.3.7 Traffic Evacuation Control
Transit Management Center Transit Center Security 4.1.5.3 Manage Transit Driver Authentication
4.2.1.7 Provide Interface for Other Transit Management Data
4.4.1 Provide Transit Security and Emergency Management
4.4.2 Coordinate Multiple Agency Responses to Transit Incidents
4.4.3 Generate Responses for Transit Incidents
4.4.4 Provide Transit Operations Personnel Security Interface

Physical

The physical diagram can be viewed in SVG or PNG format and the current format is SVG.
SVG Diagram
PNG Diagram


Display Legend in SVG or PNG

Includes Physical Objects:

Physical Object Class Description
Asset Management System Center 'Asset Management System' represents the systems that support decision-making for maintenance, upgrade, and operation of physical transportation assets. Asset management integrates and includes the pavement management systems, bridge management systems, and other systems that inventory and manage the highway infrastructure and other transportation-related assets. The types of assets that are inventoried and managed will vary, and may include the maintenance and construction vehicles and equipment as well as "soft" assets such as human resources and software. Asset management systems monitor the condition, performance, and availability of the infrastructure and evaluate and prioritize alternative reconstruction, rehabilitation, and maintenance strategies.
Emergency Management Center Center 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.
Emergency System Operator Center 'Emergency System Operator' represents the public safety personnel that monitor emergency requests, (including those from the E911 Operator) and set up pre-defined responses to be executed by an emergency management system. The operator may also override predefined responses where it is observed that they are not achieving the desired result. This also includes dispatchers who manage an emergency fleet (police, fire, ambulance, HAZMAT, etc.) or higher order emergency managers who provide response coordination during emergencies.
Maint and Constr Center Personnel Center The people that directly interface with a Maintenance and Construction Management Center. These personnel interact with fleet dispatch and management systems, road maintenance systems, incident management systems, work plan scheduling systems, and work zone management systems. They provide operator data and command inputs to direct system operations to varying degrees depending on the type of system and the deployment scenario.
Maint and Constr Management Center Center The 'Maint and Constr Management Center' monitors and manages roadway infrastructure construction and maintenance activities. Representing both public agencies and private contractors that provide these functions, this physical object manages fleets of maintenance, construction, or special service vehicles (e.g., snow and ice control equipment). The physical object receives a wide range of status information from these vehicles and performs vehicle dispatch, routing, and resource management for the vehicle fleets and associated equipment. The physical object participates in incident response by deploying maintenance and construction resources to an incident scene, in coordination with other center physical objects. The physical object manages equipment at the roadside, including environmental sensors and automated systems that monitor and mitigate adverse road and surface weather conditions. It manages the repair and maintenance of both non-ITS and ITS equipment including the traffic controllers, detectors, dynamic message signs, signals, and other equipment associated with the roadway infrastructure. Weather information is collected and fused with other data sources and used to support advanced decision support systems.

The physical object remotely monitors and manages ITS capabilities in work zones, gathering, storing, and disseminating work zone information to other systems. It manages traffic in the vicinity of the work zone and advises drivers of work zone status (either directly at the roadside or through an interface with the Transportation Information Center or Traffic Management Center physical objects.)

Construction and maintenance activities are tracked and coordinated with other systems, improving the quality and accuracy of information available regarding closures and other roadway construction and maintenance activities.
Other Emergency Management Centers Center 'Other Emergency Management Centers' provides a source and destination for information flows between various communications centers operated by public safety agencies, emergency management agencies, other allied agencies, and private companies that participate in coordinated management of transportation-related incidents, including disasters. The interface represented by this object enables emergency management activities to be coordinated across jurisdictional boundaries and between functional areas, supporting requirements for general networks connecting many allied agencies. It also supports interface to other allied agencies like utility companies that also participate in the coordinated response to selected highway-related incidents.
Other Maint and Constr Mgmt Centers Center Representing another Maintenance and Construction Management Center, 'Other Maint and Constr Mgmt Centers' is intended to provide a source and destination for ITS information flows between maintenance and construction management functions. It enables maintenance and construction operations to be coordinated across jurisdictions or between public and private sectors.
Other Traffic Management Centers Center Representing another Traffic Management Center, 'Other Traffic Management Centers' is intended to provide a source and destination for information exchange between peer (e.g. inter-regional) traffic management functions. It enables traffic management activities to be coordinated across different jurisdictional areas.
Other Transit Management Centers Center Representing another transit operations center, 'Other Transit Management Centers' is intended to provide a source and destination for information flows between peer transit management centers. It enables transit management activities to be coordinated across geographic boundaries or jurisdictions.
Public Health System Center 'Public Health System' represents the systems operated by hospitals or regional public health departments that can respond to requests for specific information regarding emergencies involving biohazards - such as biological attacks, hazardous materials spills, or other threats to public health. It can provide recommended courses of action to emergency management to improve the response, quarantining, or evacuation based on the type of hazard involved.
Rail Operations Center Center 'Rail Operations Center' represents the (usually) centralized control point for a substantial segment of a freight railroad's operations and maintenance activities. It is roughly the railroad equivalent to a highway Traffic Management Center. It is the source and destination of information that can be used to coordinate rail and highway traffic management and maintenance operations. It is also the source and destination for incident, incident response, disaster, or evacuation information that is exchanged with an Emergency Management Center. The use of a single object for multiple sources and destination for information exchange with railroads implies the need for a single, consistent interface between a given railroad's operations and maintenance activities and ITS.
Traffic Management Center Center 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.
Traffic Operations Personnel Center 'Traffic Operations Personnel' represents the people that operate a traffic management center. These personnel interact with traffic control systems, traffic surveillance systems, incident management systems, work zone management systems, and travel demand management systems. They provide operator data and command inputs to direct system operations to varying degrees depending on the type of system and the deployment scenario.
Transit Management Center Center 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.
Transit Operations Personnel Center 'Transit Operations Personnel' represents the people that are responsible for fleet management, maintenance operations, and scheduling activities of the transit system. These different roles represent a variety of individuals in the transit industry. Within the transit industry the person responsible for fleet management is known by many names: Street Supervisor, Starter, Dispatcher, Supervisor, Traffic Controller, Transportation Coordinator. This person actively monitors, controls, and modifies the transit fleet routes and schedules on a day to day basis (dynamic scheduling). The modifications will take account of abnormal situations such as vehicle breakdown, vehicle delay, detours around work zones or incidents (detour management, connection protection, and service restoration), and other causes of route or schedule deviations. Transit operations personnel are also responsible for demand responsive transit operation and for managing emergency situations within the transit network such as silent alarms on board transit vehicles, or the remote disabling of the vehicle. In addition the Transit Operations Personnel may be responsible for assigning vehicle operators to routes, checking vehicle operators in and out, and managing transit stop issues. This object also represents the personnel in the transit garage that are responsible for maintenance of the transit fleets, including monitoring vehicle status, matching vehicles with operators, and maintenance checking of transit vehicles. Finally, it represents the people responsible for planning, development, and management of transit routes and schedules.

Includes Functional Objects:

Functional Object Description Physical Object
Emergency Incident Command 'Emergency Incident Command' provides tactical decision support, resource coordination, and communications integration for Incident Commands that are established by first responders at or near the incident scene to support local management of an incident. It supports communications with public safety, emergency management, transportation, and other allied response agency centers, tracks and maintains resource information, action plans, and the incident command organization itself. Information is shared with agency centers including resource deployment status, hazardous material information, traffic, road, and weather conditions, evacuation advice, and other information that enables emergency or maintenance personnel in the field to implement an effective, safe incident response. It supports the functions and interfaces commonly supported by a mobile command center. Emergency Management Center
Emergency Response Management 'Emergency Response Management' provides the strategic emergency response capabilities and broad inter-agency interfaces that are implemented for extraordinary incidents and disasters that require response from outside the local community. It provides the functional capabilities and interfaces commonly associated with Emergency Operations Centers. It develops and stores emergency response plans and manages overall coordinated response to emergencies. It monitors real-time information on the state of the regional transportation system including current traffic and road conditions, weather conditions, special event and incident information. It tracks the availability of resources and assists in the appropriate allocation of these resources for a particular emergency response. It also provides coordination between multiple allied agencies before and during emergencies to implement emergency response plans and track progress through the incident. It also coordinates with the public through the Emergency Telecommunication Systems (e.g., Reverse 911). It coordinates with public health systems to provide the most appropriate response for emergencies involving biological or other medical hazards. Emergency Management Center
MCM Incident Management 'MCM Incident Management' supports maintenance and construction participation in coordinated incident response. Incident notifications are shared, incident response resources are managed, and the overall incident situation and incident response status is coordinated among allied response organizations. Maint and Constr Management Center
MCM Roadway Maintenance 'MCM Roadway Maintenance' provides overall management and support for routine maintenance on a roadway system or right-of-way. Services managed include landscape maintenance, hazard removal (roadway debris, dead animals), routine maintenance activities (roadway cleaning, grass cutting), and repair and maintenance of non-ITS equipment on the roadway (e.g., signs, gantries, cabinets, guard rails, etc.). Environmental conditions information is also received from various weather sources to aid in scheduling routine maintenance activities. See also MCM Field Equipment Maintenance for maintenance of ITS field equipment. Maint and Constr Management Center
TMC Incident Dispatch Coordination 'TMC Incident Dispatch Coordination' formulates and manages an incident response that takes into account the incident potential, incident impacts, and resources required for incident management. It provides information to support dispatch and routing of emergency response and service vehicles as well as coordination with other cooperating agencies. It provides access to traffic management resources that provide surveillance of the incident, traffic control in the surrounding area, and support for the incident response. It monitors the incident response and collects performance measures such as incident response and clearance times. Traffic Management Center
Transit Center Security 'Transit Center Security' monitors transit vehicle operator or traveler activated alarms received from on-board a transit vehicle. It supports transit vehicle operator authentication and provides the capability to remotely disable a transit vehicle. It also includes the capability to alert operators and police to potential incidents identified by these security features. Transit Management Center

Includes Information Flows:

Information Flow Description
asset damage assessment Information indicating the damage sustained by transportation assets, derived from aerial surveillance, field reports, inspections, tests, and analyses.
emergency operations input Emergency operator input supporting call taking, dispatch, emergency operations, security monitoring, and other operations and communications center operator functions.
emergency operations status Presentation of information to the operator including emergency operations data, supporting a range of emergency operating positions including call taker, dispatch, emergency operations, security monitoring, and various other operations and communications center operator positions.
emergency plan coordination Information that supports coordination of emergency management plans, continuity of operations plans, emergency response and recovery plans, evacuation plans, and other emergency plans between agencies. This includes general plans that are coordinated prior to an incident and shorter duration tactical plans that are prepared during an incident.
emergency traffic control information Status of a special traffic control strategy or system activation implemented in response to an emergency traffic control request, a request for emergency access routes, a request for evacuation, a request to activate closure systems, a request to employ driver information systems to support public safety objectives, or other special requests. Identifies the selected traffic control strategy and system control status.
emergency traffic control request Special request to preempt the current traffic control strategy in effect at one or more signalized intersections or highway segments, activate traffic control and closure systems such as gates and barriers, activate safeguard systems, or use driver information systems. For example, this flow can request all signals to red-flash, request a progression of traffic control preemptions along an emergency vehicle route, request a specific evacuation traffic control plan, request activation of a road closure barrier system, or place a public safety or emergency-related message on a dynamic message sign.
emergency traffic coordination Coordination supporting disaster response including evacuation and reentry. Includes coordination of special traffic control strategies that support efficient evacuation and reentry while protecting and optimizing movement of response vehicles and other resources responding to the emergency.
emergency transit schedule information Information on transit schedule and service changes that adapt the service to better meet needs of responders and the general public in an emergency situation, including special service schedules supporting evacuation.
emergency transit service request Request to modify transit service and fare schedules to address emergencies, including requests for transit services to evacuate people from and/or deploy response agency personnel to an emergency scene. The request may poll for resource availability or request pre-staging, staging, or immediate dispatch of transit resources.
emergency transit service response Response indicating changes to transit service, fares, and/or restrictions that will be made and status of transit resources to be deployed to support emergency response and/or evacuation.
incident command information coordination Information that supports local management of an incident. It includes resource deployment status, hazardous material information, traffic, road, and weather conditions, evacuation advice, and other information that enables emergency or maintenance personnel in the field to implement an effective, safe incident response.
incident information 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.
incident response coordination Incident response procedures and current incident response status that are shared between allied response agencies to support a coordinated response to incidents. This flow provides current situation information, including a summary of incident status and its impact on the transportation system and other infrastructure, and current and planned response activities. This flow also coordinates a positive hand off of responsibility for all or part of an incident response between agencies.
incident response status Status of the current incident response including a summary of incident status and its impact on the transportation system, traffic management strategies implemented at the site (e.g., closures, diversions, traffic signal control overrides), and current and planned response activities.
maint and constr center personnel input User input from maintenance and construction center personnel including routing information, scheduling data, dispatch instructions, device configuration and control, resource allocations, alerts, incident and emergency response plan coordination.
maint and constr operations information presentation Presentation of maintenance and construction operations information to center personnel. This information includes maintenance resource status (vehicles, equipment, and personnel), work schedule information, work status, road and weather conditions, traffic information, incident information and associated resource requests, security alerts, emergency response plans and a range of other information that supports efficient maintenance and construction operations and planning.
maint and constr resource coordination Request for road maintenance and construction resources that can be used in the diversion of traffic (cones, portable signs), clearance of a road hazard, repair of ancillary damage, or any other incident response.
maint and constr resource request Request for road maintenance and construction resources that can be used in the diversion of traffic (cones, portable signs), clearance of a road hazard, repair of ancillary damage, or any other incident response. The request may poll for resource availability or request pre-staging, staging, or immediate dispatch of resources.
maint and constr resource response Current status of maintenance and construction resources including availability and deployment status. General resource inventory information covering vehicles, equipment, materials, and people and specific resource deployment status may be included.
public health request Request for specific information or recommended response concerning an emergency involving biological or other medically related emergency.
public health response Specific information or recommendation on how to treat or respond to an emergency involving biological or other medically related emergency.
rail incident response status Status of the rail system's response to current incidents.
rail system status assessment Assessment of damage sustained by rail lines and associated railroad infrastructure including location and extent of the damage, impact on current operations and necessary restrictions, and time frame for repair and recovery.
resource coordination Coordination of resource inventory information, specific resource status information, resource prioritization and reallocation between jurisdictions, and specific requests for resources and responses that service those requests.
resource deployment status Status of resource deployment identifying the resources (vehicles, equipment, materials, and personnel) available and their current status. General resource inventory information and specific status of deployed resources may be included.
resource request A request for resources to implement special traffic control measures, assist in clean up, verify an incident, etc. The request may poll for resource availability or request pre-staging, staging, or immediate deployment of resources. Resources may be explicitly requested or a service may be requested and the specific resource deployment may be determined by the responding agency.
road network conditions Current and forecasted traffic information, road and weather conditions, and other road network status. Either raw data, processed data, or some combination of both may be provided by this flow. Information on diversions and alternate routes, closures, and special traffic restrictions (lane/shoulder use, weight restrictions, width restrictions, HOV requirements) in effect is included.
road network status assessment Assessment of damage sustained by the road network including location and extent of the damage, estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame for repair and recovery.
traffic operator data Presentation of traffic operations data to the operator including traffic conditions, current operating status of field equipment, maintenance activity status, incident status, video images, security alerts, emergency response plan updates and other information. This data keeps the operator appraised of current road network status, provides feedback to the operator as traffic control actions are implemented, provides transportation security inputs, and supports review of historical data and preparation for future traffic operations activities.
traffic operator input User input from traffic operations personnel including requests for information, configuration changes, commands to adjust current traffic control strategies (e.g., adjust signal timing plans, change DMS messages), and other traffic operations data entry.
transit operations personnel input User input from transit operations personnel including instructions governing service availability, schedules, emergency response plans, transit personnel assignments, transit maintenance requirements, and other inputs that establish general system operating requirements and procedures.
transit operations status Presentation of information to transit operations personnel including accumulated schedule and fare information, ridership and on-time performance information, emergency response plans, transit personnel information, maintenance records, and other information intended to support overall planning and management of a transit property.
transit service coordination Schedule coordination or AVL information shared between local/regional transit organizations. This includes coordination of connections and control parameters between transit properties as well as coordination of transit-related maintenance activities.
transit system status assessment Assessment of damage sustained by the public transportation system including location and extent of the damage, current operational status including an estimate of remaining capacity and necessary restrictions, and time frame for repair and recovery.
transportation system status 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.

Goals and Objectives

Associated Planning Factors and Goals

Planning Factor Goal
B. Increase the safety of the transportation system for motorized and nonmotorized users; Reduce fatalities and injuries
C. Increase the security of the transportation system for motorized and nonmotorized users; Improve security
F. Enhance the integration and connectivity of the transportation system, across and between modes, for people and freight; Enhance integration and connectivity
G. Promote efficient system management and operation; Improve efficiency

Associated Objective Categories

Objective Category
Emergency/Incident Management: Inter-Agency Coordination
Security: Terrorism, Natural Disasters, and Hazardous Material Incidents

Associated Objectives and Performance Measures

Objective Performance Measure
At least X percent of transportation operating agencies have a plan in place for a representative to be at the local or State Emergency Operations Center (EOC) to coordinate strategic activities and response planning for transportation during emergencies by year Y. X percent of transportation operating agencies that have a plan in place for a representative to be at the local (city or county) EOC or State EOC to coordinate strategic activities and response planning for transportation during emergencies.
Increase percentage of incident management agencies in the region that (participate in a multi-modal information exchange network, use interoperable voice communications, participate in a regional coordinated incident response team, etc.) by X percent in Y years. Number of agencies in the region with interoperable voice communications.
Increase percentage of incident management agencies in the region that (participate in a multi-modal information exchange network, use interoperable voice communications, participate in a regional coordinated incident response team, etc.) by X percent in Y years. Number of participating agencies in a regional coordinated incident response team.
Increase percentage of incident management agencies in the region that (participate in a multi-modal information exchange network, use interoperable voice communications, participate in a regional coordinated incident response team, etc.) by X percent in Y years. Percentage of incident management agencies in region participating in multi-modal information exchange network.
Reduce exposure due to Hazmat & homeland security incidents Homeland security incident response time
Reduce exposure due to Hazmat & homeland security incidents Number of Hazmat incidents
Reduce exposure due to Hazmat & homeland security incidents Number of homeland security incidents

 
Since the mapping between objectives and service packages is not always straight-forward and often situation-dependent, these mappings should only be used as a starting point. Users should do their own analysis to identify the best service packages for their region.

Needs and Requirements

Need Functional Object Requirement
01 Emergency Management needs to support integration between transportation systems and the public safety, emergency management, public health, and other allied organizations that form the overall disaster response. Emergency Incident Command 04 The center shall share incident command information with other public safety agencies including resource deployment status, hazardous material information, rail incident information, evacuation advice as well as traffic, road, and weather conditions.
Emergency Response Management 01 The center shall provide strategic emergency response capabilities provided by an Emergency Operations Center for large-scale incidents and disasters.
13 The center shall provide the capability for center personnel to provide inputs to the management of incidents, disasters and evacuations.
14 The center shall collect information about the status of the recovery efforts for the infrastructure during disasters.
18 The center shall retrieve information from public health systems to increase preparedness for, and implement a response to biological, chemical, radiation, and other public health emergencies.
MCM Incident Management 02 The maintenance center shall exchange alert information and status with emergency management centers. The information includes notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction. The information may include the alert originator, the nature of the emergency, the geographic area affected by the emergency, the effective time period, etc.
03 The maintenance center shall exchange incident and threat information with emergency management centers as well as traffic management centers; including notification of existence of incident and expected severity, location, time and nature of incident.
TMC Incident Dispatch Coordination 01 The center shall exchange alert information and status with emergency management centers. The information includes notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction for distribution to the public. The information may include the alert originator, the nature of the emergency, the geographic area affected by the emergency, the effective time period, and information and instructions necessary for the public to respond to the alert. This may also identify specific information that should not be released to the public.
03 The center shall support requests from emergency management centers to remotely control sensor and surveillance equipment located in the field, provide special routing for emergency vehicles, and to provide responding emergency vehicles with signal preemption.
Transit Center Security 08 The center shall receive threat information and status on the integrity of the transit infrastructure.
02 Emergency Management needs to support coordination of emergency response plans issued by various agencies in order plan for regional response to disasters. Emergency Incident Command 02 The center shall provide incident command communications with public safety, emergency management, transportation, and other allied response agency centers.
Emergency Response Management 04 The center shall develop, coordinate with other agencies, and store emergency response plans.
05 The center shall track the availability of resources and coordinate resource sharing with allied agency centers including traffic, maintenance, or other emergency centers.
MCM Incident Management 04 The maintenance center shall coordinate planning for incidents with emergency management centers - including pre-planning activities for disaster response, evacuation, and recovery operations.
TMC Incident Dispatch Coordination 02 The center shall coordinate planning for incidents with emergency management centers - including pre-planning activities for disaster response, evacuation, and recovery operations.
Transit Center Security 07 The center shall coordinate the response to security incidents involving transit with other agencies including Emergency Management, other transit agencies, media, traffic management, and traveler information service providers.
03 Emergency Management needs to be able to track and coordinate the transportation professionals, equipment, and materials that constitute the disaster response in order to respond to and recover from disasters. Emergency Response Management 02 The center shall manage coordinated inter-agency responses to and recovery from large-scale emergencies. Such agencies include traffic management, transit, maintenance and construction management, rail operations, and other emergency management agencies.
10 The center shall provide the capability to request transit resource availability from transit centers for use during disaster and evacuation operations.
MCM Roadway Maintenance 02 The center shall respond to requests from emergency management and traffic management centers for hazard removal, field equipment repair, and other roadway maintenance.
09 The center shall dispatch and route maintenance and construction vehicle drivers and support them with route-specific environmental, incident, advisory, threat, alert, and traffic congestion information.
10 The center shall manage an interface with center personnel to accept vehicle systems control information and remotely control maintenance and construction vehicle on-board equipment.
TMC Incident Dispatch Coordination 05 The center shall share resources with allied agency centers to implement special traffic control measures, assist in clean up, verify an incident, etc. This may also involve coordination with maintenance centers.
04 Emergency Management needs to be able to provide to other regional centers information about the transportation system in the vicinity of the disaster. Emergency Incident Command 02 The center shall provide incident command communications with public safety, emergency management, transportation, and other allied response agency centers.
Emergency Response Management 03 The center shall provide the capability to implement response plans and track progress through the incident by exchanging incident information and response status with allied agencies.
TMC Incident Dispatch Coordination 07 The center shall provide road network conditions and traffic images to emergency management centers, maintenance and construction centers, and traveler information service providers.
09 The center shall exchange road network status assessment information with emergency management and maintenance centers including an assessment of damage sustained by the road network including location and extent of the damage, estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame for repair and recovery.
11 The center shall receive inputs from emergency management and transit management centers to develop an overall status of the transportation system including emergency transit schedules in effect and current status and condition of the transportation infrastructure.
Transit Center Security 05 The center shall receive information pertaining to a wide-area alert such as weather alerts, disaster situations, or child abductions. This information may come from Emergency Management or from other Alerting and Advisory Systems.

Related Sources

Document Name Version Publication Date
ITS User Services Document 1/1/2005
R.E.S.C.U.M.E. (Response, Emergency Staging and Communications, Uniform Management, and Evacuation) ConOps Final 11/19/2012
R.E.S.C.U.M.E. Report on Functional and Performance Requirements, and High-Level Data and Communication Needs Final 2/7/2013


Security

In order to participate in this service package, each physical object should meet or exceed the following security levels.

Physical Object Security
Physical Object Confidentiality Integrity Availability Security Class
Asset Management System Moderate Moderate Moderate Class 2
Emergency Management Center High High High Class 5
Maint and Constr Management Center High High High Class 5
Other Emergency Management Centers High High High Class 5
Other Maint and Constr Mgmt Centers Moderate Moderate Moderate Class 2
Other Traffic Management Centers Moderate High High Class 5
Other Transit Management Centers Moderate Moderate Moderate Class 2
Public Health System High High High Class 5
Rail Operations Center High High High Class 5
Traffic Management Center High High High Class 5
Transit Management Center High High High Class 5



In order to participate in this service package, each information flow triple should meet or exceed the following security levels.

Information Flow Security
Source Destination Information Flow Confidentiality Integrity Availability
Basis Basis Basis
Asset Management System Emergency Management Center asset damage assessment Moderate Moderate Moderate
Status of transportation assets is generally observable information, however this flow consolidates it all in one place. A person of nefarious intent could use this as their own damage assessment tool. Status of the transportation infrastructure should be accurate and timely or inappropriate maintenance actions taken, costing time and/or money and impacting system performance. Status of the transportation infrastructure should be accurate and timely or inappropriate maintenance actions taken, costing time and/or money and impacting system performance.
Emergency Management Center Emergency System Operator emergency operations status Moderate High High
Emergency system controls should not be casually viewable as they impact the availability of emergency services, which if known could be leveraged for illegal activity. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
Emergency Management Center Maint and Constr Management Center emergency plan coordination High High High
Evacuation plans are distributed between many transportation centers, but the end user implications are parcelled out as-needed. Unintended distribution of this informationtan may facilitate examination of emergency planning, which in the hands of an actor bent on initiating a disaster, provides a roadmap for how to cause as much damage as possible. Consequently, this information should be protected to the maximum extent possible to forstall such unlikely but potentially devastating attacks. Evacuation and disaster response planning information, if corrupted could lead to incorrect actions taken in response to emergency or disaster, which could have catastrophic consequences. Emergency response plans that aren't properly exchanged may lead differing agencies to take actions that do not synchronize well with other agencies, and result in substantial losses as a result.
Emergency Management Center Maint and Constr Management Center incident information High Moderate Moderate
This data contains all of the information regarding the incident. This could include personal information regarding persons involved in the incident. It could also include sensitive information regarding special events or closures. 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 M&CMC has received a message.
Emergency Management Center Maint and Constr Management Center incident response status Moderate Moderate Moderate
This flow implies details of an incident, which could be used by an attacker as intelligence gathering and target assessment. If this data is incorrect or unavailable then maintenance assets may not be appropriately assigned, resulting in inefficient use of maintenance assets and higher overall downtime in the incident locale. If this data is incorrect or unavailable then maintenance assets may not be appropriately assigned, resulting in inefficient use of maintenance assets and higher overall downtime in the incident locale.
Emergency Management Center Maint and Constr Management Center maint and constr resource request Moderate Moderate Moderate
This flow implies details of an incident, which could be used by an attacker as intelligence gathering and target assessment. If this data is incorrect or unavailable then maintenance assets may not be appropriately assigned, resulting in inefficient use of maintenance assets and higher overall downtime in the incident locale. This flow enables the response to work zones and incidents; depending on the use, the requirements may be LOW. Generally however we assume it is used for incident response and clean-up, which can have a significant impact, thus MODERATE.
Emergency Management Center Maint and Constr Management Center transportation system status Low High Moderate
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.
Emergency Management Center Other Emergency Management Centers emergency plan coordination High High High
Evacuation plans are distributed between many transportation centers, but the end user implications are parcelled out as-needed. Unintended distribution of this information may facilitate examination of emergency planning, which in the hands of an actor bent on initiating a disaster, provides a roadmap for how to cause as much damage as possible. Consequently, this information should be protected to the maximum extent possible to forstall such unlikely but potentially devastating attacks. Evacuation and disaster response planning information, if corrupted could lead to incorrect actions taken in response to emergency or disaster, which could have catastrophic consequences. Emergency response plans that aren't properly exchanged may lead differing agencies to take actions that do not synchronize well with other agencies, and result in substantial losses as a result.
Emergency Management Center Other Emergency Management Centers incident command information coordination Moderate Moderate Moderate
Will include incident-specific information that could be used by a hostile attacker to target emergency resources, or to avoid those resources in the commission of a crime. Since this is used to coordinate emergency response, if this flow is unavailable, incorrect or corrupted the response may not be appropriate, comprimising safety and mobility. Since this is used to coordinate emergency response, if this flow is unavailable, incorrect or corrupted the response may not be appropriate, comprimising safety and mobility.
Emergency Management Center Other Emergency Management Centers incident response coordination Moderate Moderate Moderate
Will include incident-specific information that could be used by a hostile attacker to target emergency resources, or to avoid those resources in the commission of a crime. Since this is used to coordinate emergency response, if this flow is unavailable, incorrect or corrupted the response may not be appropriate, comprimising safety and mobility. Since this is used to coordinate emergency response, if this flow is unavailable, incorrect or corrupted the response may not be appropriate, comprimising safety and mobility.
Emergency Management Center Other Emergency Management Centers resource coordination Moderate Moderate Moderate
Suggests maintenance and incident response planning, which is predictive of asset allocation. This information could be used by an attacker to solicit and identify targets. If this data is incorrect or unavailable then maintenance assets may not be appropriately assigned, resulting in inefficient use of maintenance assets and higher overall downtime in the incident locale. This flow enables the response to work zones and incidents; depending on the use, the requirements may be LOW. Generally however we assume it is used for incident response and clean-up, which can have a significant impact, thus MODERATE.
Emergency Management Center Other Emergency Management Centers transportation system status Low High Moderate
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.
Emergency Management Center Public Health System public health request High High High
Data includes a suggestion of a biological catastrophe, which has tremendous potential impact and would be of great interest to an attacker. As such, this information needs to be protected in content and integrity at the highest level, and given the impact of the request/response, delivered in as timely fashion as possible. Data includes a suggestion of a biological catastrophe, which has tremendous potential impact and would be of great interest to an attacker. As such, this information needs to be protected in content and integrity at the highest level, and given the impact of the request/response, delivered in as timely fashion as possible. Data includes a suggestion of a biological catastrophe, which has tremendous potential impact and would be of great interest to an attacker. As such, this information needs to be protected in content and integrity at the highest level, and given the impact of the request/response, delivered in as timely fashion as possible.
Emergency Management Center Rail Operations Center emergency plan coordination High High High
Evacuation plans are distributed between many transportation centers, but the end user implications are parcelled out as-needed. Unintended distribution of this information may facilitate examination of emergency planning, which in the hands of an actor bent on initiating a disaster, provides a roadmap for how to cause as much damage as possible. Consequently, this information should be protected to the maximum extent possible to forstall such unlikely but potentially devastating attacks. Evacuation and disaster response planning information, if corrupted could lead to incorrect actions taken in response to emergency or disaster, which could have catastrophic consequences. Emergency response plans that aren't properly exchanged may lead differing agencies to take actions that do not synchronize well with other agencies, and result in substantial losses as a result.
Emergency Management Center Rail Operations Center incident information High Moderate Moderate
This data contains all of the information regarding the incident. This could include personal information regarding persons involved in the incident. It could also include sensitive information regarding special events or closures. 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 Rail Operations Center has received a message.
Emergency Management Center Rail Operations Center incident response status Moderate Moderate Moderate
This flow implies details of an incident, which could be used by an attacker as intelligence gathering and target assessment. If this data is incorrect or unavailable then maintenance assets may not be appropriately assigned, resulting in inefficient use of maintenance assets and higher overall downtime in the incident locale. If this data is incorrect or unavailable then maintenance assets may not be appropriately assigned, resulting in inefficient use of maintenance assets and higher overall downtime in the incident locale.
Emergency Management Center Rail Operations Center transportation system status Low High Moderate
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.
Emergency Management Center Traffic Management Center emergency plan coordination High High High
Evacuation plans are distributed between many transportation centers, but the end user implications are parcelled out as-needed. Unintended distribution of this information may facilitate examination of emergency planning, which in the hands of an actor bent on initiating a disaster, provides a roadmap for how to cause as much damage as possible. Consequently, this information should be protected to the maximum extent possible to forstall such unlikely but potentially devastating attacks. Evacuation and disaster response planning information, if corrupted could lead to incorrect actions taken in response to emergency or disaster, which could have catastrophic consequences. Emergency response plans that aren't properly exchanged may lead differing agencies to take actions that do not synchronize well with other agencies, and result in substantial losses as a result.
Emergency Management Center Traffic Management Center emergency traffic control request Moderate High Moderate
These requests could be used to track the specific route that an emergency vehicle is planning on taking. False requests here could bring the traffic system to a standstill by making all of the lights red. Additionally, the system must be able to trust these requests, and know that they came from an authorized source. These messages are important for the system to operate properly. Additionally, the system must know if messages are not received so that it can act accordingly.
Emergency Management Center Traffic Management Center incident information High Moderate Moderate
This data contains all of the information regarding the incident. This could include personal information regarding persons involved in the incident. It could also include sensitive information regarding special events or closures. 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 TMC has received a message.
Emergency Management Center Traffic Management Center incident response status Moderate Moderate Moderate
This flow implies details of an incident, which could be used by an attacker as intelligence gathering and target assessment. If this data is incorrect or unavailable then maintenance assets may not be appropriately assigned, resulting in inefficient use of maintenance assets and higher overall downtime in the incident locale. If this data is incorrect or unavailable then maintenance assets may not be appropriately assigned, resulting in inefficient use of maintenance assets and higher overall downtime in the incident locale.
Emergency Management Center Traffic Management Center resource request Moderate Moderate Moderate
This flow implies details of an incident, which could be used by an attacker as intelligence gathering and target assessment. If this data is incorrect or unavailable then maintenance assets may not be appropriately assigned, resulting in inefficient use of maintenance assets and higher overall downtime in the incident locale. This flow enables the response to work zones and incidents; depending on the use, the requirements may be LOW. Generally however we assume it is used for incident response and clean-up, which can have a significant impact, thus MODERATE.
Emergency Management Center Traffic Management Center transportation system status Low High Moderate
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.
Emergency Management Center Transit Management Center emergency plan coordination High High High
Evacuation plans are distributed between many transportation centers, but the end user implications are parcelled out as-needed. Unintended distribution of this information may facilitate examination of emergency planning, which in the hands of an actor bent on initiating a disaster, provides a roadmap for how to cause as much damage as possible. Consequently, this information should be protected to the maximum extent possible to forstall such unlikely but potentially devastating attacks. Evacuation and disaster response planning information, if corrupted could lead to incorrect actions taken in response to emergency or disaster, which could have catastrophic consequences. Emergency response plans that aren't properly exchanged may lead differing agencies to take actions that do not synchronize well with other agencies, and result in substantial losses as a result.
Emergency Management Center Transit Management Center emergency transit service request High High High
Transit status report and emergency situation data is distributed as needed to those that need to know. Interception by an unintended recipient enables abuse, particularly for an actor interested in disturbing the emergency situation further. if this information is corrupted the EMC or Transit Management Center may take action not consistent with the actual situation, which in an emergency situation could have significant effects. if this information is corrupted the EMC or Transit Management Center may take action not consistent with the actual situation, which in an emergency situation could have significant effects.
Emergency Management Center Transit Management Center incident information High Moderate Moderate
This data contains all of the information regarding the incident. This could include personal information regarding persons involved in the incident. It could also include sensitive information regarding special events or closures. 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 Transit Management Center has received a message.
Emergency Management Center Transit Management Center incident response status Moderate Moderate Moderate
This flow implies details of an incident, which could be used by an attacker as intelligence gathering and target assessment. If this data is incorrect or unavailable then maintenance assets may not be appropriately assigned, resulting in inefficient use of maintenance assets and higher overall downtime in the incident locale. If this data is incorrect or unavailable then maintenance assets may not be appropriately assigned, resulting in inefficient use of maintenance assets and higher overall downtime in the incident locale.
Emergency Management Center Transit Management Center transportation system status Low High Moderate
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.
Emergency System Operator Emergency Management Center emergency operations input Moderate High High
Emergency system controls should not be casually viewable as they impact the availability of emergency services, which if known could be leveraged for illegal activity. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
Maint and Constr Center Personnel Maint and Constr Management Center maint and constr center personnel input High High High
Direct interactions between personnel and systems in a backoffice environment are effectively protected by physical means, so long as the interaction is in a dedicated facility. If this interaction is virtual (i.e. ,the MCMC is not directly in front of the MCMC Personnel, like in a cloud-based system) then the user's input requires some degree of obfuscation depending on sensitivity of information. Given that this could include information about compromised or ineffectual systems, including security systems, the potential for damage is high. Thus, HIGH. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
Maint and Constr Management Center Emergency Management Center emergency plan coordination High High High
Evacuation plans are distributed between many transportation centers, but the end user implications are parcelled out as-needed. Unintended distribution of this information may facilitate examination of emergency planning, which in the hands of an actor bent on initiating a disaster, provides a roadmap for how to cause as much damage as possible. Consequently, this information should be protected to the maximum extent possible to forstall such unlikely but potentially devastating attacks. Evacuation and disaster response planning information, if corrupted could lead to incorrect actions taken in response to emergency or disaster, which could have catastrophic consequences. Emergency response plans that aren't properly exchanged may lead differing agencies to take actions that do not synchronize well with other agencies, and result in substantial losses as a result.
Maint and Constr Management Center Emergency Management Center maint and constr resource response Moderate Moderate Moderate
This flow implies details of an incident, which could be used by an attacker as intelligence gathering and target assessment. If this data is incorrect or unavailable then maintenance assets may not be appropriately assigned, resulting in inefficient use of maintenance assets and higher overall downtime in the incident locale. This flow enables the response to work zones and incidents; depending on the use, the requirements may be LOW. Generally however we assume it is used for incident response and clean-up, which can have a significant impact, thus MODERATE.
Maint and Constr Management Center Emergency Management Center road network status assessment Moderate High High
Damage assessment information should be concealed from observation. An attacker may use this information to identify weak points or discover the results of an attack. Damage assessment information needs to be delivered accurately and promptly so the Emergency Management Center can react as swiftly and appropriately as possible. In case of emergency, this could have significant safety and mobility impact. Damage assessment information needs to be delivered accurately and promptly so the Emergency Management Center can react as swiftly and appropriately as possible. In case of emergency, this could have significant safety and mobility impact.
Maint and Constr Management Center Maint and Constr Center Personnel maint and constr operations information presentation Not Applicable Moderate Moderate
System maintenance flows should have some protection from casual viewing, as otherwise imposters could gain illicit control over field equipment Information presented to backoffice system operators must be consistent or the operator may perform actions that are not appropriate to the real situation. The backoffice system operator should have access to system operation. If this interface is down then control is effectively lost, as without feedback from the system the operator has no way of knowing what is the correct action to take.
Maint and Constr Management Center Other Maint and Constr Mgmt Centers maint and constr resource coordination Moderate Moderate Moderate
This flow implies details of an incident, which could be used by an attacker as intelligence gathering and target assessment. If this data is incorrect or unavailable then maintenance assets may not be appropriately assigned, resulting in inefficient use of maintenance assets and higher overall downtime in the incident locale. This flow enables the response to work zones and incidents; depending on the use, the requirements may be LOW. Generally however we assume it is used for incident response and clean-up, which can have a significant impact, thus MODERATE.
Maint and Constr Management Center Traffic Management Center maint and constr resource response Moderate Moderate Moderate
This flow implies details of an incident, which could be used by an attacker as intelligence gathering and target assessment. If this data is incorrect or unavailable then maintenance assets may not be appropriately assigned, resulting in inefficient use of maintenance assets and higher overall downtime in the incident locale. This flow enables the response to work zones and incidents; depending on the use, the requirements may be LOW. Generally however we assume it is used for incident response and clean-up, which can have a significant impact, thus MODERATE.
Maint and Constr Management Center Traffic Management Center road network status assessment Moderate High High
Damage assessment information should be concealed from observation. An attacker may use this information to identify weak points or discover the results of an attack. Damage assessment information needs to be delivered accurately and promptly so the Emergency Management Center can react as swiftly and appropriately as possible. In case of emergency, this could have significant safety and mobility impact. Damage assessment information needs to be delivered accurately and promptly so the Emergency Management Center can react as swiftly and appropriately as possible. In case of emergency, this could have significant safety and mobility impact.
Other Emergency Management Centers Emergency Management Center emergency plan coordination High High High
Evacuation plans are distributed between many transportation centers, but the end user implications are parcelled out as-needed. Unintended distribution of this information may facilitate examination of emergency planning, which in the hands of an actor bent on initiating a disaster, provides a roadmap for how to cause as much damage as possible. Consequently, this information should be protected to the maximum extent possible to forstall such unlikely but potentially devastating attacks. Evacuation and disaster response planning information, if corrupted could lead to incorrect actions taken in response to emergency or disaster, which could have catastrophic consequences. Emergency response plans that aren't properly exchanged may lead differing agencies to take actions that do not synchronize well with other agencies, and result in substantial losses as a result.
Other Emergency Management Centers Emergency Management Center incident command information coordination Moderate Moderate Moderate
Will include incident-specific information that could be used by a hostile attacker to target emergency resources, or to avoid those resources in the commission of a crime. Since this is used to coordinate emergency response, if this flow is unavailable, incorrect or corrupted the response may not be appropriate, comprimising safety and mobility. Since this is used to coordinate emergency response, if this flow is unavailable, incorrect or corrupted the response may not be appropriate, comprimising safety and mobility.
Other Emergency Management Centers Emergency Management Center incident response coordination Moderate Moderate Moderate
Will include incident-specific information that could be used by a hostile attacker to target emergency resources, or to avoid those resources in the commission of a crime. Since this is used to coordinate emergency response, if this flow is unavailable, incorrect or corrupted the response may not be appropriate, comprimising safety and mobility. Since this is used to coordinate emergency response, if this flow is unavailable, incorrect or corrupted the response may not be appropriate, comprimising safety and mobility.
Other Emergency Management Centers Emergency Management Center resource coordination Moderate Moderate Moderate
Suggests maintenance and incident response planning, which is predictive of asset allocation. This information could be used by an attacker to solicit and identify targets. If this data is incorrect or unavailable then maintenance assets may not be appropriately assigned, resulting in inefficient use of maintenance assets and higher overall downtime in the incident locale. This flow enables the response to work zones and incidents; depending on the use, the requirements may be LOW. Generally however we assume it is used for incident response and clean-up, which can have a significant impact, thus MODERATE.
Other Emergency Management Centers Emergency Management Center transportation system status Low High Moderate
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. 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.
Other Maint and Constr Mgmt Centers Maint and Constr Management Center maint and constr resource coordination Moderate Moderate Moderate
This flow implies details of an incident, which could be used by an attacker as intelligence gathering and target assessment. If this data is incorrect or unavailable then maintenance assets may not be appropriately assigned, resulting in inefficient use of maintenance assets and higher overall downtime in the incident locale. This flow enables the response to work zones and incidents; depending on the use, the requirements may be LOW. Generally however we assume it is used for incident response and clean-up, which can have a significant impact, thus MODERATE.
Other Traffic Management Centers Traffic Management Center emergency traffic coordination Moderate High High
This can potentially include sensitive information, such as response information to emergencies. if this information is corrupted or not available the Traffic Management Center may take action not consistent with the actual situation, which in an emergency situation could have significant effects. if this information is corrupted or not available the Traffic Management Center may take action not consistent with the actual situation, which in an emergency situation could have significant effects.
Other Transit Management Centers Transit Management Center transit service coordination Moderate Moderate Moderate
Coordination between transit systems is generally not sensitive, however this flow may include information related to serving individual connection protection requests that are sensitive. If this information is not timely or correct, transit agencies may not properly coordinate, leaving some users unserved. If this information is not timely or correct, transit agencies may not properly coordinate, leaving some users unserved.
Public Health System Emergency Management Center public health response High High High
Data includes a suggestion of a biological catastrophe, which has tremendous potential impact and would be of great interest to an attacker. As such, this information needs to be protected in content and integrity at the highest level, and given the impact of the request/response, delivered in as timely fashion as possible. Data includes a suggestion of a biological catastrophe, which has tremendous potential impact and would be of great interest to an attacker. As such, this information needs to be protected in content and integrity at the highest level, and given the impact of the request/response, delivered in as timely fashion as possible. Data includes a suggestion of a biological catastrophe, which has tremendous potential impact and would be of great interest to an attacker. As such, this information needs to be protected in content and integrity at the highest level, and given the impact of the request/response, delivered in as timely fashion as possible.
Rail Operations Center Emergency Management Center emergency plan coordination High High High
Evacuation plans are distributed between many transportation centers, but the end user implications are parcelled out as-needed. Unintended distribution of this information may facilitate examination of emergency planning, which in the hands of an actor bent on initiating a disaster, provides a roadmap for how to cause as much damage as possible. Consequently, this information should be protected to the maximum extent possible to forstall such unlikely but potentially devastating attacks. Evacuation and disaster response planning information, if corrupted could lead to incorrect actions taken in response to emergency or disaster, which could have catastrophic consequences. Emergency response plans that aren't properly exchanged may lead differing agencies to take actions that do not synchronize well with other agencies, and result in substantial losses as a result.
Rail Operations Center Emergency Management Center rail incident response status Moderate Moderate Moderate
This flow implies details of an incident, which could be used by an attacker as intelligence gathering and target assessment. If this data is incorrect or unavailable then maintenance assets may not be appropriately assigned, resulting in inefficient use of maintenance assets and higher overall downtime in the incident locale. If this data is incorrect or unavailable then maintenance assets may not be appropriately assigned, resulting in inefficient use of maintenance assets and higher overall downtime in the incident locale.
Rail Operations Center Emergency Management Center rail system status assessment Moderate Moderate Moderate
Status of transportation assets is generally observable information, however this flow consolidates it all in one place. A person of nefarious intent could use this as their own damage assessment tool. Status of the transportation infrastructure should be accurate and timely or inappropriate maintenance actions taken, costing time and/or money and impacting system performance. Status of the transportation infrastructure should be accurate and timely or inappropriate maintenance actions taken, costing time and/or money and impacting system performance.
Traffic Management Center Emergency Management Center emergency plan coordination High High High
Evacuation plans are distributed between many transportation centers, but the end user implications are parcelled out as-needed. Unintended distribution of this information may facilitate examination of emergency planning, which in the hands of an actor bent on initiating a disaster, provides a roadmap for how to cause as much damage as possible. Consequently, this information should be protected to the maximum extent possible to forstall such unlikely but potentially devastating attacks. Evacuation and disaster response planning information, if corrupted could lead to incorrect actions taken in response to emergency or disaster, which could have catastrophic consequences. Emergency response plans that aren't properly exchanged may lead differing agencies to take actions that do not synchronize well with other agencies, and result in substantial losses as a result.
Traffic Management Center Emergency Management Center emergency traffic control information Moderate High Moderate
This can potentially include sensitive information, such as response information to emergencies. Invalid messages could lead to an unauthorized user gaining transit signal priority at an intersection. This could also be used to bring traffic to a standstill, which could lead to a large financial impact on the community. These messages are important to help with the transit signal priority application. Without them, it will not work. However, if these signals are not received, the Emergency Vehicle can still navigate through the intersection using Lights and Sirens. The TMC should have an acknowledgement of the receipt of a message.
Traffic Management Center Emergency Management Center resource deployment status Moderate Moderate Moderate
This details resource allocation, which if intercepted by a hostile actor could be used to identify weak points or resource-related targets. If this data is incorrect, corrupted or unavailable then maintenance assets may not be appropriately assigned, resulting in inefficient use of maintenance assets and higher overall downtime in the incident locale. If this data is incorrect, corrupted or unavailable then maintenance assets may not be appropriately assigned, resulting in inefficient use of maintenance assets and higher overall downtime in the incident locale.
Traffic Management Center Emergency Management Center road network conditions Low Moderate Moderate
No harm should come from seeing this data, as it is eventually intended for public consumption. While accuracy of this data is important for decision making purposes, applications should be able to corroborate the data in many instances. Thus MODERATE generally. Depends on the application; if mobility decisions that affect large numbers of travelers are made based on this data, then it is MODERATE. In more modest circumstances, it may be LOW.
Traffic Management Center Emergency Management Center road network status assessment Moderate High High
Damage assessment information should be concealed from observation. An attacker may use this information to identify weak points or discover the results of an attack. Damage assessment information needs to be delivered accurately and promptly so the Emergency Management Center can react as swiftly and appropriately as possible. In case of emergency, this could have significant safety and mobility impact. Damage assessment information needs to be delivered accurately and promptly so the Emergency Management Center can react as swiftly and appropriately as possible. In case of emergency, this could have significant safety and mobility impact.
Traffic Management Center Maint and Constr Management Center maint and constr resource request Moderate Moderate Moderate
This flow implies details of an incident, which could be used by an attacker as intelligence gathering and target assessment. If this data is incorrect or unavailable then maintenance assets may not be appropriately assigned, resulting in inefficient use of maintenance assets and higher overall downtime in the incident locale. This flow enables the response to work zones and incidents; depending on the use, the requirements may be LOW. Generally however we assume it is used for incident response and clean-up, which can have a significant impact, thus MODERATE.
Traffic Management Center Maint and Constr Management Center road network status assessment Moderate High High
Damage assessment information should be concealed from observation. An attacker may use this information to identify weak points or discover the results of an attack. Damage assessment information needs to be delivered accurately and promptly so the Emergency Management Center can react as swiftly and appropriately as possible. In case of emergency, this could have significant safety and mobility impact. Damage assessment information needs to be delivered accurately and promptly so the Emergency Management Center can react as swiftly and appropriately as possible. In case of emergency, this could have significant safety and mobility impact.
Traffic Management Center Other Traffic Management Centers emergency traffic coordination Moderate High High
This can potentially include sensitive information, such as response information to emergencies. if this information is corrupted or not available the Traffic Management Center may take action not consistent with the actual situation, which in an emergency situation could have significant effects. if this information is corrupted or not available the Traffic Management Center may take action not consistent with the actual situation, which in an emergency situation could have significant effects.
Traffic Management Center Traffic Operations Personnel traffic operator data Moderate Moderate Moderate
Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. Information presented to backoffice system operators must be consistent or the operator may perform actions that are not appropriate to the real situation. The backoffice system operator should have access to system operation. If this interface is down then control is effectively lost, as without feedback from the system the operator has no way of knowing what is the correct action to take.
Traffic Operations Personnel Traffic Management Center traffic operator input Moderate High High
Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
Transit Management Center Emergency Management Center emergency plan coordination High High High
Evacuation plans are distributed between many transportation centers, but the end user implications are parcelled out as-needed. Unintended distribution of this information may facilitate examination of emergency planning, which in the hands of an actor bent on initiating a disaster, provides a roadmap for how to cause as much damage as possible. Consequently, this information should be protected to the maximum extent possible to forstall such unlikely but potentially devastating attacks. Evacuation and disaster response planning information, if corrupted could lead to incorrect actions taken in response to emergency or disaster, which could have catastrophic consequences. Emergency response plans that aren't properly exchanged may lead differing agencies to take actions that do not synchronize well with other agencies, and result in substantial losses as a result.
Transit Management Center Emergency Management Center emergency transit schedule information Low High High
Eventually the information contained within this flow will be disseminated to the public, so there should be little harm if it were observed. Emergency-related data needs to be correct or safety-affecting decisions may have severe negative consequences. if this information is corrupted the EMC or Transit Management Center may take action not consistent with the actual situation, which in an emergency situation could have significant effects.
Transit Management Center Emergency Management Center emergency transit service response High High High
Transit status report and emergency situation data is distributed as needed to those that need to know. Interception by an unintended recipient enables abuse, particularly for an actor interested in disturbing the emergency situation further. if this information is corrupted the EMC or Transit Management Center may take action not consistent with the actual situation, which in an emergency situation could have significant effects. if this information is corrupted the EMC or Transit Management Center may take action not consistent with the actual situation, which in an emergency situation could have significant effects.
Transit Management Center Emergency Management Center transit system status assessment Moderate Moderate Moderate
Status of transportation assets is generally observable information, however this flow consolidates it all in one place. A person of nefarious intent could use this as their own damage assessment tool. Status of the transportation infrastructure should be accurate and timely or inappropriate maintenance actions taken, costing time and/or money and impacting system performance. Status of the transportation infrastructure should be accurate and timely or inappropriate maintenance actions taken, costing time and/or money and impacting system performance.
Transit Management Center Other Transit Management Centers transit service coordination Moderate Moderate Moderate
Coordination between transit systems is generally not sensitive, however this flow may include information related to serving individual connection protection requests that are sensitive. If this information is not timely or correct, transit agencies may not properly coordinate, leaving some users unserved. If this information is not timely or correct, transit agencies may not properly coordinate, leaving some users unserved.
Transit Management Center Transit Operations Personnel transit operations status Moderate High High
Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.
Transit Operations Personnel Transit Management Center transit operations personnel input Moderate High High
Backoffice operations flows should have minimal protection from casual viewing, as otherwise imposters could gain illicit control or information that should not be generally available. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system. Backoffice operations flows should generally be correct and available as these are the primary interface between operators and system.

Standards

The following table lists the standards associated with physical objects in this service package. For standards related to interfaces, see the specific information flow triple pages.

Name Title Physical Object
NEMA TS 8 Cyber and Physical Security Cyber and Physical Security for Intelligent Transportation Systems Traffic Management Center




System Requirements

System Requirement Need
001 The system shall provide incident command communications with public safety, emergency management, transportation, and other allied response agency centers. 04 Emergency Management needs to be able to provide to other regional centers information about the transportation system in the vicinity of the disaster.
02 Emergency Management needs to support coordination of emergency response plans issued by various agencies in order plan for regional response to disasters.
002 The system shall share incident command information with other public safety agencies including resource deployment status, hazardous material information, rail incident information, evacuation advice as well as traffic, road, and weather conditions. 01 Emergency Management needs to support integration between transportation systems and the public safety, emergency management, public health, and other allied organizations that form the overall disaster response.
003 The system shall provide strategic emergency response capabilities provided by an Emergency Operations Center for large-scale incidents and disasters. 01 Emergency Management needs to support integration between transportation systems and the public safety, emergency management, public health, and other allied organizations that form the overall disaster response.
004 The system shall manage coordinated inter-agency responses to and recovery from large-scale emergencies. Such agencies include traffic management, transit, maintenance and construction management, rail operations, and other emergency management agencies. 03 Emergency Management needs to be able to track and coordinate the transportation professionals, equipment, and materials that constitute the disaster response in order to respond to and recover from disasters.
005 The system shall provide the capability to implement response plans and track progress through the incident by exchanging incident information and response status with allied agencies. 04 Emergency Management needs to be able to provide to other regional centers information about the transportation system in the vicinity of the disaster.
006 The system shall develop, coordinate with other agencies, and store emergency response plans. 02 Emergency Management needs to support coordination of emergency response plans issued by various agencies in order plan for regional response to disasters.
007 The system shall track the availability of resources and coordinate resource sharing with allied agency centers including traffic, maintenance, or other emergency centers. 02 Emergency Management needs to support coordination of emergency response plans issued by various agencies in order plan for regional response to disasters.
008 The system shall provide the capability to request transit resource availability from transit centers for use during disaster and evacuation operations. 03 Emergency Management needs to be able to track and coordinate the transportation professionals, equipment, and materials that constitute the disaster response in order to respond to and recover from disasters.
009 The system shall provide the capability for center personnel to provide inputs to the management of incidents, disasters and evacuations. 01 Emergency Management needs to support integration between transportation systems and the public safety, emergency management, public health, and other allied organizations that form the overall disaster response.
010 The system shall collect information about the status of the recovery efforts for the infrastructure during disasters. 01 Emergency Management needs to support integration between transportation systems and the public safety, emergency management, public health, and other allied organizations that form the overall disaster response.
011 The system shall retrieve information from public health systems to increase preparedness for, and implement a response to biological, chemical, radiation, and other public health emergencies. 01 Emergency Management needs to support integration between transportation systems and the public safety, emergency management, public health, and other allied organizations that form the overall disaster response.
012 The system shall exchange alert information and status with emergency management centers. The information includes notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction. The information may include the alert originator, the nature of the emergency, the geographic area affected by the emergency, the effective time period, etc. 01 Emergency Management needs to support integration between transportation systems and the public safety, emergency management, public health, and other allied organizations that form the overall disaster response.
013 The system shall exchange incident and threat information with emergency management centers as well as traffic management centers; including notification of existence of incident and expected severity, location, time and nature of incident. 01 Emergency Management needs to support integration between transportation systems and the public safety, emergency management, public health, and other allied organizations that form the overall disaster response.
014 The system shall respond to requests from emergency management and traffic management centers for hazard removal, field equipment repair, and other roadway maintenance. 03 Emergency Management needs to be able to track and coordinate the transportation professionals, equipment, and materials that constitute the disaster response in order to respond to and recover from disasters.
015 The system shall dispatch and route maintenance and construction vehicle drivers and support them with route-specific environmental, incident, advisory, threat, alert, and traffic congestion information. 03 Emergency Management needs to be able to track and coordinate the transportation professionals, equipment, and materials that constitute the disaster response in order to respond to and recover from disasters.
016 The system shall manage an interface with center personnel to accept vehicle systems control information and remotely control maintenance and construction vehicle on-board equipment. 03 Emergency Management needs to be able to track and coordinate the transportation professionals, equipment, and materials that constitute the disaster response in order to respond to and recover from disasters.
017 The system shall exchange alert information and status with emergency management centers. The information includes notification of a major emergency such as a natural or man-made disaster, civil emergency, or child abduction for distribution to the public. The information may include the alert originator, the nature of the emergency, the geographic area affected by the emergency, the effective time period, and information and instructions necessary for the public to respond to the alert. This may also identify specific information that should not be released to the public. 01 Emergency Management needs to support integration between transportation systems and the public safety, emergency management, public health, and other allied organizations that form the overall disaster response.
018 The system shall coordinate planning for incidents with emergency management centers - including pre-planning activities for disaster response, evacuation, and recovery operations. 02 Emergency Management needs to support coordination of emergency response plans issued by various agencies in order plan for regional response to disasters.
019 The system shall support requests from emergency management centers to remotely control sensor and surveillance equipment located in the field, provide special routing for emergency vehicles, and to provide responding emergency vehicles with signal preemption. 01 Emergency Management needs to support integration between transportation systems and the public safety, emergency management, public health, and other allied organizations that form the overall disaster response.
020 The system shall share resources with allied agency centers to implement special traffic control measures, assist in clean up, verify an incident, etc. This may also involve coordination with maintenance centers. 03 Emergency Management needs to be able to track and coordinate the transportation professionals, equipment, and materials that constitute the disaster response in order to respond to and recover from disasters.
021 The system shall provide road network conditions and traffic images to emergency management centers, maintenance and construction centers, and traveler information service providers. 04 Emergency Management needs to be able to provide to other regional centers information about the transportation system in the vicinity of the disaster.
022 The system shall exchange road network status assessment information with emergency management and maintenance centers including an assessment of damage sustained by the road network including location and extent of the damage, estimate of remaining capacity, required closures, alternate routes, necessary restrictions, and time frame for repair and recovery. 04 Emergency Management needs to be able to provide to other regional centers information about the transportation system in the vicinity of the disaster.
023 The system shall receive inputs from emergency management and transit management centers to develop an overall status of the transportation system including emergency transit schedules in effect and current status and condition of the transportation infrastructure. 04 Emergency Management needs to be able to provide to other regional centers information about the transportation system in the vicinity of the disaster.
024 The system shall receive information pertaining to a wide-area alert such as weather alerts, disaster situations, or child abductions. This information may come from Emergency Management or from other Alerting and Advisory Systems. 04 Emergency Management needs to be able to provide to other regional centers information about the transportation system in the vicinity of the disaster.
025 The system shall coordinate the response to security incidents involving transit with other agencies including Emergency Management, other transit agencies, media, traffic management, and traveler information service providers. 02 Emergency Management needs to support coordination of emergency response plans issued by various agencies in order plan for regional response to disasters.
026 The system shall receive threat information and status on the integrity of the transit infrastructure. 01 Emergency Management needs to support integration between transportation systems and the public safety, emergency management, public health, and other allied organizations that form the overall disaster response.