ITS Transit Standards Professional Capacity Building Program

Module 15: Emerging Evacuation Standards of Communication/Incident Management (ISO 19083)

HTML of the PowerPoint Presentation

(Note: This document has been converted from a PowerPoint presentation to 508-compliant HTML. The formatting has been adjusted for 508 compliance, but all the original text content is included, plus additional text descriptions for the images, photos and/or diagrams have been provided below.)

Slide 1:

(Extended Text Description: Welcome - Graphic image of introductory slide. A large dark blue rectangle with a wide, light grid pattern at the top half and bands of dark and lighter blue bands below. There is a white square ITS logo box with words "Standards ITS Training - Transit" in green and blue on the middle left side. The word "Welcome" in white is to the right of the logo. Under the logo box is the logo for the U.S. Department of Transportation, Office of the Assistant Secretary for Research and Technology.)

Slide 2:

Module: 15

Emerging Evacuation Standards of Communication/Incident Management (ISO 19083)

Slide 3:

Instructor

Dave Matta

U.S. Expert

ISO TC 204 Working Group 8 Public Transport and Emergency Services

Course Developer: Paula Okunieff

Slide 4:

Learning Objectives

• Describe the Elements of the Emergency Evacuation and Disaster Response and Recovery (EEDRR) Framework
• Explain roles and responsibilities of organizations (including Transit) in EEDRR
• Use Concept of Operations Template for specifying a Decision Support System (DSS)
• Review Characteristics of Transit Emergency Management Decision Support System

Slide 5:

Learning Objective 1

Describe the Elements of the Emergency Evacuation and Disaster Response and Recovery (EEDRR) Framework

Slide 6:

Emergency Evacuation and Disaster Response and Recovery (EEDRR) Framework Overview

Frequency and Impacts of Disasters

Weather Related Disasters Increasing (US)

• Disaster Declarations 1960 -1969 - 18 per year
• Declarations from 2000 - 2009 - 56 per year

Earthquake Threats (Worldwide)

• Number of Earthquakes
  • 1970-1999- 1588 per year
  • 2000-2012- 1813 per year
• Deaths Related to Earthquakes
  • 1970-1999- 34,120 per year
  • 2000-2012- 62,590 per year

Slide 7:

Emergency Evacuation and Disaster Response and Recovery (EEDRR) Framework Overview

Where is transit during a disaster?

Equipment and Facilities

• 2012 "Superstorm Sandy"- $6.2 Billion for repair and restoration of public transportation infrastructure

Slide 8:

Emergency Evacuation and Disaster Response and Recovery (EEDRR) Framework Overview

Where is transit during a disaster?

Equipment and Facilities

Service

• Hurricane Sandy triggered worst transit disaster in U.S. history
• More than half of the nation's daily transit riders were without service

Slide 9:

Emergency Evacuation and Disaster Response and Recovery (EEDRR) Framework Overview

Where is transit during a disaster?

Equipment and Facilities

Service

Ridership

• Carless in an evacuation (low income, tourist, guest worker)
• Service Interruption during Recovery

(Extended Text Description: This slide, entitled Emergency Evacuation and Disaster Response and Recovery (EEDRR) Framework Overview, A photo of buses in hurricane floodwater in the upper right. On the right side underneath the photo of the buses is a frontal view of a bus that reads STORM ROUTE. Underneath the photo of the bus that reads STORM ROUTE is a photo of people exiting a bus while carrying their belongings.)

Slide 10:

Emergency Evacuation and Disaster Response and Recovery (EEDRR) Framework Overview

U.S. Interest and Activities Based on Needs

• Literature Review
• Government Agencies
• Business Organizations
• International Standards Organization

Slide 11:

Emergency Evacuation and Disaster Response and Recovery (EEDRR) Framework Overview

Missing System Components in ITS

• Transit in National ITS Architecture Emergency Service Packages
• Data Exchange with Emergency Operations Center Standards
• Passenger Identification Standards
• Emergency Route / Schedule Standards

(Extended Text Description: This slide, entitled "Emergency Evacuation and Disaster Response and Recovery (EEDRR) Framework Overview" contains three images in circles at the bottom of the slide. The image on the left shows an Emergency Operations Center with a panel of images are projected for the use of emergency managers. The image in the middle shows Operations Control Center with several stations of staff using workstations to monitor transit operations. The image on the right shows people evacuating.)

Slide 12:

Emergency Evacuation and Disaster Response and Recovery (EEDRR) Framework Overview

Need for Communications and Standards

• Those without access to automobiles depend on Transit for mobility
• Poor or inadequate communications is a major roadblock to providing the proper emergency services during a disaster
• Infrequent occurrence and personnel turnover cause loss of knowledge for responding to disasters
• ITS technologies are a platform from which to overcome these roadblocks
• Standards can provide an organized, dependable response to an emergency by the transit industry

Slide 13:

ISO 19083 Standard Background

What is the ISO 19083?

International Standards Organization (ISO) technical report for developing the requirements for an:

Emergency Evacuation and Disaster Response and Recovery Decision Support System (EEDRR-DSS)

Purpose

• Present Framework and Concept of Operations for a decision support system to support transit planning for EEDRR
• Define information flows, data interchange requirements, message descriptions
• Support disaster drills and exercises

Slide 14:

ISO 19083 Standard Background

ISO 19083 Series of Standards

(Extended Text Description: This slide has the following text, with the text of Part 1 highlighted with a green box to give it emphasis:

Public transport — Emergency evacuation and disaster response and recovery

https://www.iso.org/standard/71510.html

Part 1: Standard's Framework and Concept of Operation for a Public Transport Decision Support System for Emergency Evacuation and Disaster Response and Recovery

Part 2: Information Flow between Decision Support Systems, Passenger Information Systems, Command and Control Systems, and Emergency Operation Centers during an evacuation/disaster

Part 3: Use Cases needed to support Disaster Drills/Exercises

)

Slide 15:

Emergency Evacuation and Disaster Response and Recovery (EEDRR) Framework Overview

What is the EEDRR Framework?

(Extended Text Description: This slide, entitled "Emergency Evacuation and Disaster Response and Recovery (EEDRR) Framework Overview" has 8 images and a legend. The legend describes a square as representing Actors. A yellow oval represents systems and other ovals represent communications networks for the ECS (Emergency control system), TIS (traveler information system) and PIS (passenger information system). The eight photographs depict actors. An emergency management center connects to the EEDRR Decision Support System (yellow oval), which in turn connects to the three Actors – Emergency Services, Traffic Management, and Transit. Each of these middle tier actors connect through their own communication network to their field personnel or clients. The Emergency Services actor connects through the ECS to first responders (depicted by firefighters). The Traffic Management connects through the TIS to the Car-Riding public (depicted as bumper to bumper traffic leaving on only one side of the interstate). The Transit actor is connected through the PIS to two actors, the carless public (shown as a parade of people walking) and recovery personnel (shown as a bus with Evacuation Route in its head sign). The Emergency Management actor is a photo of display panels with emergency personnel in a room. The Emergency Services actor is a different view of a EM room. The Traffic Management actor shows an operations center with a panel of displays showing video of traffic. The Transit actor shows an operations center with workstations showing different bus route lines and personnel staffing the workstations.)

Slide 16:

Emergency Evacuation and Disaster Response and Recovery (EEDRR) Framework Overview

EEDRR Scope

• Focus on ITS for ground transportation
  • Covers ground transportation for disaster
    • evacuation
    • response
    • recovery
• Does not cover:
  • Societal issues (sheltering, aid, security)
  • Railway (commuter and intercity rail)
  • Airports
• Foundation for developing a Decision Support System

Slide 17:

Emergency Evacuation and Disaster Response and Recovery (EEDRR) Framework Overview

EEDRR Purpose

Paradigm shift

• Transit is primary mobility agent for all transportation-related actions
  • Prepares
  • Responds
  • Recovers
• Uses common terminology to communicate
  • Standard language from ISO 22330 Security and resilience - Business continuity management systems -Guidelines for people aspects on business continuity

Slide 18:

Emergency Evacuation and Disaster Response and Recovery (EEDRR) Framework Overview

Primary Objective of EEDRR Framework

• Support Transit providers in design of a coordinated Decision Support System (DSS) to deliver Transportation Services
• This includes:
  • Moving people from harm’s way (evacuation)
  • Moving emergency responders into area (response)
  • Providing transportation for recovery efforts (recovery)
• Concern is needs overwhelm available transit resources
  • Coordination between multiple transit providers
  • Other resource i.e. school buses may fall under other entities
  • Agency to coordinate and deploy multiple suppliers

Slide 19:

Emergency Evacuation and Disaster Response and Recovery (EEDRR) Framework Overview

EEDRR Decision Support System Approach

• DSS computer-based information system that supports organizational decision-making activities
• Scope of organizational decision-making activities is organized in the Concept of Operations (CONOPS)
• Step 1 for the CONOPS
  • Understand your planning assumptions
  • Identify your needs

Slide 20:

Emergency Evacuation and Disaster Response and Recovery (EEDRR) Framework Overview

EEDRR Stakeholders

(Extended Text Description: This slide, entitled "Emergency Evacuation and Disaster Response and Recovery (EEDRR) Framework Overview" shows the EEDRR framework depicted as two large systems (represented as rectangles). The top system is called "External Networks." And the system under it is called the "Decision Support System." The External Networks includes four systems – Emergency Services Networks, Traffic Management Networks, Transit Management Networks, and Social Networks. The Decision Support System (DSS) has four arrows that link the DSS to each of the systems in the External Network. The DSS has three interconnecting subsystems – Interface Layer (data collection, command and control), Knowledge Layer (modeling, analysis, exercises, accreditation), and Cloud Infrastructure Services Layer.)

Slide 21:

Planning Assumptions

Planning Assumptions for Evacuation

Elements that factor into planning:

• Identify needs
• Calculate and analyze response times
• Assign resources

Slide 22:

Planning Assumptions

Needs Identification

Identify populations to be evacuated:

• Permanent residents and transient populations
• Public transit dependent permanent residents
• Special facility residents (e.g., hospitals, nursing homes)
• Schools

Where to acquire information:

• Surveys
• Patrons who are issued special media or use special services
• Ridership demographics

Slide 23:

Planning Assumptions

Planning Assumptions for Evacuation -Response Times

Estimate time to evacuate identified populations

• Calculate evacuation route timing for each population group
• Requires staging equipment, developing routes and technology

How

• Modeling software (e.g., flexible/dynamic scheduling software and traffic models for evacuation)

Slide 24:

Planning Assumptions

Planning Assumptions for Evacuation -Resource Assignments

Resource assignments based on total number of available

• Operators
• Buses / Vehicles
• Safe staging areas for vehicles and personnel
• Monitoring operations personnel and facilities

How

• Modeling software
• Trained operators
• Technology tools that are hardened for a disaster

Slide 25:

Other Key Considerations for Disaster Response and Recovery Efforts

Plan for the Unexpected

• Events with and without warning
• Critical infrastructure
  • Loss of % fleet
  • Fuel supply
  • Facilities
  • Communications
• Limits in disaster forecasting
• Environmental contamination
• Victim contamination
• Animals

Slide 26:

Other Key Considerations for Disaster Response and Recovery Efforts

Elements that factor into planning for disaster and response

• Interdependencies between shelters and transportation
• Interdependencies between response and recovery efforts
• Special needs populations

Slide 27:

Slide 28:

Question

Which of the following is a part of ISO 19083 standard?

Answer Choices

1. Sheltering, aid, and security
2. Railways, airports, and ports
3. Evacuation, response and recovery
4. Organizations, policies, and procedures

Slide 29:

Review of Answers

a) Sheltering, aid, and security
Incorrect. ISO 19083 pertains to transportation related activities see ISO 22300 Societal Security for these topics.

b) Railways, airports, and ports
Incorrect. ISO 19083 pertains to ground transportation. The reader is directed to ISO TC 20 SC 17 Airport infrastructure and ISO TC 269 Railway application for air and rail transportation issues associates with disasters. No ISO TC exist for Ports.

c) Evacuation, response and recovery
Correct! ISO 19083 Includes transportation related functions before, during and after for disasters.

d) Organizations, policies, and procedures
Incorrect. ISO 19083 pertains to the development of a decision support system that collects and analyzes ITS data.

Slide 30:

Learning Objective 2

Explain roles and responsibilities of organizations (including Transit) in EEDRR

Slide 31:

Agencies and Organizations Involved in a Regionally Supported EEDRR

Step 2 for CONOPS identifying the Actors

(Extended Text Description: This slide contains the following text, with section headers, from top to bottom, emphasized with a blue background, dark blue at the top progressing to light blue at the bottom:

Local

• City or County
• Examples – fire, police, EMS, public works, traffic department

Regional and State

• County, District or State
• Examples – state police, emergency management, military reserve, transportation department, transit, human services

National Agencies

• Federal and International
• Examples – Federal Emergency Management Administration, National Guard

Non-Governmental Organizations

• Examples – Red Cross, media

)

Slide 32:

Roles and Responsibilities

Stakeholder/ Actors Groups

• Emergency Management
  • Lead organization
• Emergency Services
  • First Responders
• Traffic Management
  • Car-riding public
• Transit
  • Primary mobility agent for all transportation-related actions

Slide 33:

Roles and Responsibilities

Disaster Response Phases and Activities

(Extended Text Description: A circle with six ordered activities with an arrow behind them going clockwise: 1. Advanced planning (update the plan); 2. Incident notification, 3. Activation and mobilization, 4. Evacuation operations, 5. Re-entry, 6. Debrief and assessment.)

Slide 34:

Roles and Responsibilities

Disaster Response Phases and Activities

Advanced Planning

• Transit role - planning and organization of transportation services for identified populations

Incident Notification

• Transit role - activate Transit Emergency Operations Center (EOC); alert personnel and identify equipment

Activation and mobilization

• Transit role - Transit briefed by EOC; identify needs -populations, route and time estimates, and resources

Slide 35:

Roles and Responsibilities

Disaster Response Phases and Activities

• Evacuation or Response Operations
  • Transit role - Deploy personnel and equipment as needed; move remaining vehicles and personnel outside of evacuation zone
• Re-Entry
  • Transit role - notification, activation, mobilization and operations for re-entry into the evacuation zone. Identify needs - evacuees, route and time estimates, resources required
• Debrief and Assessment
  • Transit role - Participate with all agencies involved to evaluate overall operations. Update planning assumption (see advanced planning)

Slide 36:

Roles and Responsibilities

Recovery Phases and Activities

Slide 37:

Roles and Responsibilities

Recovery Phases and Activities Roles

• Build partnerships, identify capacity needs and limitations
• Activate recovery teams, staging areas, mutual service needs/ agreements with other transit agencies
• Assess costs and mutual aid needs
• Identify recovery goals, coordinate with local/ regional organizations, and compile lessons learned

Slide 38:

Criteria for Using Transit

Using the National ITS Architecture Version 7.1

(Extended Text Description: Author's relevant notes: To show how a regional ITS architecture process brings different stakeholders together to agree on how they will interact to support different services. Transit can contribute if they are sitting at the table. When multiple transit agencies are sitting at the table, they can coordinate their activities to address issues such as evacuation and response services. There are four major categories of systems depicted by four rectangles: Travelers, Centers, Vehicles and Fields. These are interconnected through four ovals which represent types of communications networks: wide area wireless (mobile), fixed point – fixed point, vehicle – vehicle and field-vehicle communications networks. Three centers are circled in red to emphasize them: Traffic Management, Emergency Management and Transit Management.)

Slide 39:

Criteria for Using Transit

Finding Stakeholders in the Regional ITS Architecture

• Look for Emergency Management Service Packages (10 in all)
• Service Packages-represent slices of the Physical Architecture that address specific services like:

EM 2 - Emergency Routing

"This ... package supports routing of emergency vehicles and enlists support from the Traffic Management ... to facilitate travel along these routes. Routes may be determined by this ... package based on real-time traffic information and road conditions or routes may be provided by the Traffic Management ... on request. Vehicles are tracked and routes are based on current vehicle location. This equipment package may coordinate with the Traffic Management to provide preemption or otherwise adapt the traffic control strategy along the selected route"

Slide 40:

Criteria for Using Transit

(Extended Text Description: Author's relevant notes: The purpose of this slide is to show an example of the "reference" model for Emergency Routing for the National ITS Architecture. Regions will walk through the reference and tailor these to fit their region. Most regions only adopt some of the functions and interfaces shown in this diagram (see next page for an example). This is a generic or reference diagram from the National ITS Architecture. A diagram from a region will have names of organizations in each box. Notice, that even in this national model of emergency routing, there is little provision for carless populations, and there is little to no transit presence included in the services. The model includes four actors depicted as purple rectangles): Traffic Management, Emergency Management, Roadway and Emergency Vehicle exchanging data flows (depicted as arrows between the actors. Additionally, the actors also exchange data flows with end users (depicted as yellow ovals or grey rectangle) including emergency personnel, emergency system operator, care facility, rail operations, maintenance and construction management, map update provider and vehicle.)

Slide 41:

EEDRR in the Context of the Regional ITS Architecture

EEDRR Framework Related to EM Services

(Extended Text Description: Author's relevant notes: Example of an instance of Emergency Routing in a typical regional ITS architecture EM02 service. Three systems are included: public safety dispatch (an emergency management system), public safety vehicles (for emergency vehicle subsystem), and Traffic Signals (for roadway subsystem). Data flows between the public safety dispatch and public safety vehicles includes Emergency dispatch request and response; suggested route and emergency vehicle tracking data. The Public Safety Vehicles sends a signal preemption request to the traffic system. Additionally, the Public Safety Dispatch and Public Safety Vehicles exchange data flows with the Hospital (a care facility), requesting and responding to the care facility status and patient status. A legend that shows planned flow (dotted line) and existing flow (straight line) are also shown.)

Slide 42:

EEDRR in the Context of the Regional ITS Architecture

EEDRR Framework Related to EM Service with Transit

(Extended Text Description: Author's relevant notes: Example of an Emergency Routing architecture diagram for transit vehicles transporting carless populations to a shelter. Four systems are included: Transit Dispatch (transit management), transit vehicles (for transit vehicle subsystem), Signal Control (for Traffic Management) and Traffic Signals (for roadway subsystem). Data flows between the Transit dispatch and Transit vehicles includes transit dispatch request and response; suggested route and transit vehicle tracking data. The Transit Vehicles and Signal Control exchange data flows requesting and responding to signal preemption, and the Signal Control sends a control message to the Traffic Signal. Additionally, the Transit Dispatch exchange data flows with a Shelter (a care facility), requesting and responding to the care facility status. A legend that shows planned flow (dotted line) and existing flow (straight line) are also shown.)

Slide 43:

EEDRR in the Context of the Regional ITS Architecture

Transit Role Related to EM Services

• Transit not listed for evacuation services
• Human service transportation operators and paratransit services typically not included in the regional ITS architectures for evacuation services
• Transit has defined service schedules and routes for weather events; however EM / Fire has responsibility for evacuations

Slide 44:

Decision Support Concept of Operations

Using Systems Engineering to Describe Transit's Role in a Concept of Operations DSS

• Purpose of "ConOps"
  • Define a decision support tool that is repository of Preparations and Plans that provides checklists, modeling tools, inventories and information to support Disaster Response and Recovery activities
• Characteristics
  • Non-technical
  • Vision of stakeholder plans
  • Needs definition -- assessment data and modeling tools needed to implement response and recovery plans

Slide 45:

Decision Support Concept of Operations

Using Systems Engineering to Describe Transit's Role in a Concept of Operations DSS

• Obtain stakeholder agreement on who is responsible for developing the ConOps
• Manage stakeholder collaboration and needs
• Define the environment
• Derive high-level user requirements
• Provide criteria for validation of the completed Decision Support System

Slide 46:

Slide 47:

Question

What paradigm change does the EEDRR propose for emergency evacuation and disaster response and recovery?

Answer Choices

1. Transit is the primary mobility agent for all transportation-related actions
2. Transit supports emergency evacuations
3. Transit does not participate in disaster recovery
4. Emergency management relinquishes control of the Emergency Operations Center to Transit Emergency Manager

Slide 48:

Review of Answers

a) Transit is primary mobility agent for all transportation related actions
Correct! Transit has the most experience and the resources to move large numbers of people efficiently and in a timely manner which is paramount before, during and after a disaster.

b) Transit supports emergency evacuations
Incorrect. This does not represent a paradigm shift as it is what a majority of organizations currently practice.

c) Transit does not participate in disaster recovery
Incorrect. Transit should be a key player in transportation related recovery activities.

d) Emergency Managers relinquish control of the Emergency Operations Center
Incorrect. Emergency Managers will remain in charge of the Emergency Operations Center.

Slide 49:

Learning Objective 3

Developing a Concept of Operations

Slide 50:

Scope of the Transit - EEDRR Decision Support System

Developing the Concept of Operations

• Purpose is to develop the scope of the Decision Support System
• Outline
  • Operational Concepts
  • Needs
  • Operational environment
  • Actors
  • Roles and Responsibilities
  • Operational Scenarios
    • User-Oriented Operational Approach
    • High-Level Operational Requirements

Slide 51:

Scope of the Transit - EEDRR Decision Support System

(Extended Text Description: This slide contains the exact same text as slide #50, above, but with an arrow pointing to the text User-Oriented Operational Approach, which is also highlighted. The full text of the slide includes:

Developing the Concept of Operations

• Purpose is to develop the scope of the Decision Support System
• Outline
  • Operational Concepts
  • Needs
  • Operational environment
  • Actors
  • Roles and Responsibilities
  • Operational Scenarios
    • User-Oriented Operational Approach
    • High-Level Operational Requirements

)

Slide 52:

Scope of the Transit - EEDRR Decision Support System

Defining an Operational Approach

• Scope of Transportation Services
  • Buses, subway, light rail, bridges, tunnels, roads, highways, ferries, stations
• Command-Level Roles for response and recovery
• Primary Goals
  • Save lives
  • Preserve property
  • Evacuate or move people quickly and efficiently to safety
  • Move responders into and out of the affected areas
  • Provide resources (i.e., routes, services)

Slide 53:

Scope of the Transit - EEDRR Decision Support System

Defining an Operational Approach

Cognitive Processes

(Extended Text Description: This slide contains the following text, organized into three sections. The section titles are highlighted, in an increasing lighter shade of brown, moving down the slide from top to bottom. The full text of the slide includes:.

Assessment Develop Situational Awareness

• Identify, gather and prioritize information to understand situation
• Recognize context and predict future needs

Scheduling Synchronize Information and Resources

• Coordinate and communicate internally and externally
• Acquire, prioritize and allocate available assets to meet transportation needs of the public

Implementation Execute Actions and Decisions

• Recognize decision points
• Maintain mission priorities

)

Slide 54:

Scope of the Transit - EEDRR Decision Support System

Defining an Operational Approach

• Transit Roles by Phase

(Extended Text Description: This slide, entitled "Scope of the Transit – EEDRR Decision Support System" has two organizational charts. The first is for the Response Phase and the second is for the Recovery Phase. The Response Phase includes: Transit Emergency Manager, Transit Operations Coordinator, Transit Planning Coordinator, and Transit Logistics Coordinator. The Recovery Phase includes: Transit Recovery Manager, Transit Communications Coordinator, and Transit Project Manager.)

Slide 55:

Scope of the Transit - EEDRR Decision Support System

Defining an Operational Approach

(Extended Text Description: This slide, entitled "Scope of the Transit – EEDRR Decision Support System" has two Continuous Block Process graphics moving from left to right with arrows behind them. The first for the Response Phase Activities (which contains Activation, Operations, and Demobilization). The second for Recovery Phase Activities (which contains Assessment, Prioritization, Mitigation, and Infrastructure Repair).)

Slide 56:

Scope of the Transit - EEDRR Decision Support System

Detailed Transit Objectives

Phase	Role	Objectives
Activation	Transit Emergency Manager	1.1 Given an incident that requires a response from the Transit Emergency Manager, the user will immediately gather information to gain situation awareness.
Activation	Transit Emergency Manager	1.2 Given an incident that requires a response from the Transit Emergency Manager, the user will activate and staff the Transit EOC.
Operations	Transit Emergency Manager	2.1 Given an incident that requires a response from the Transit Emergency Manager, the user will maintain appropriate documentation during all phases of the response.

Slide 57:

Scope of the Transit - EEDRR Decision Support System

Operational

Approach

Template

OBJECTIVE:

1.2 Given an incident that requires a response from the PT Emergency Manager, the user will activate and staff the PT EOC.

TASK:

Identify and notify all personnel involved in the emergency response. CONDITION:

Inform each section and member assigned to respond to the emergency incident. STANDARD:

Given the emergency, the user (1) notifies the PT Coordinator assigned for responding to emergency incidents, [2] requests staffing lists, (3) designs a check-in process for each PT EOC department.

EXPECTED ACTIONS:

Call, email or meet with each PT EOC member working on the response effort. ENABLING REQUIREMENTS(ER)

1.2.1. When presented with the task of activating and staffing the PT EOC, the user notifies PT Coordinators who are responding to the incident.

1.2.2. When presented with the task of activating and staffing the PT EOC, the user designs a check-in procedure and distributes it to each department.

MEASUREMENT METHODS:

ER	Cognitive Process	Decision Support System Strategy	Performance Measure
1	CP3 - Implementation	Send an email or call using the address book	The user will notify PT Coordinators responding to the incident within 10 min of activation of the PT EOC
1.2.2	CP3 - Implementation	Retrieve/modify sample check-in for situation and email results	The user will design and implement a check-in procedure for each department within 30 min activation of the PT EOC

Slide 58:

Scope of the Transit - EEDRR Decision Support System

Developing Operational Requirements -Completing the Template

• Tasks - actions to be performed
• Condition - criteria for measuring how task will be performed
• Standard -guidelines for tasks
• Expected Actions - step by step activities
• Enabling Requirements - decision support requirements derived from objective
• Measurement Methods
  • Enabling Requirements - numbered requirement
  • Cognitive Process - assessment, scheduling, etc.
  • DSS Strategy - action or procedure to be performed by DSS tool
  • Performance Method - metric to measure DSS strategy

Slide 59:

Scope of the Transit - EEDRR Decision Support System

Developing Operational Requirements - Completing the Template Objective, Task, Condition, Standard

Objective	2.9 Given an incident that requires a response from a Transit Planning Coordinator, the user will support planning for Transit EOC response. [role: transit planning coordinator] [phase: response] [activity: operations]
Task	Develop evacuation routes
Condition	Develop routes and service schedule for transit vehicles to pick up populations and take them to safe locations.
Standard	Given the designated evacuation roads, bridges, tunnels, population pickup locations, and transit resources, the user maps path, number of transit vehicles, and operators needed to evacuate populations.

Slide 60:

Scope of the Transit - EEDRR Decision Support System

Developing Operational Requirements - Completing the Template Measurement Methods

Measurement Methods

ER	CP DSS Strategy	Performance Measures
2.9.1	Assessment Search in database using geographic areas	Data completeness, technical and timing performance measures
2.9.2	Assessment Access TOC assessment and evaluation path information	See above
2.9.3	Assessment Retrieve assessment from Transit logistics coordinator	See above
2.9.4	Scheduling Apply data from assessment and run modeling software	See above

Slide 61:

Scope of the Transit - EEDRR Decision Support System

Scenario Generation - 4 in ISO 19083

• Name / class of major events
• Define operational scenario using several types of entries
  • Name / Class
  • Casualties
  • Infrastructure Damage
  • Evacuation / Displaced Persons
  • Contamination
  • Economic Impact
  • Potential for Multiple Events Hazards
  • Recovery Time
  • Details
  • Service Disruptions
  • Transit Tasks

Slide 62:

Scope of the Transit - EEDRR Decision Support System

Example of Scenario Template for Events

Hazmat Scenario
Casualties	Zero death, one injury
Infrastructure Damage	Bus station windows broken, fire damage
Evacuations / Displaced Persons	600 people evacuated from nearby office buildings
Contamination	Ammonia spill, bleach spill
Economic Impact	Minimal
Potential for Multiple Event Hazardous	None
Recovery Time	Hours for the initial danger to pass, 1 to 2 days for cleanup
Details: A bus station employee accidentally knocks over a barrel of hazardous materials in an attempt to remove the barrels from a storage closet after a small fire breaks out. HAZMAT Teams are immediately dispatched and develop a Hot, Warm, and Cold Zone. Nearby buildings and residences should be evacuated, and all persons who were located in the Bus Station when the evacuation was ordered should be checked for contamination.
Service Disruptions: Train Service: Not affected. Air Travel: Not affected. Roads: The call for residents of nearby buildings to evacuate and the shutdown of the city streets cause traffic delays, which make it more difficult for emergency responders to reach their destinations during the first hour.
Transit Task: Preservation of the lives of drivers and passengers who may be exposed Decontamination of people and station Certification of decontamination of station Help in evacuation of the residential area Help in relocation of bus station commuters

Slide 63:

System Overview

EEDRR Decision Support Environment

• Why a Cloud Architecture?
• Cloud-based Architecture
  • Accessed from anywhere
  • Mobile
  • Stores scenarios and templates
  • Communicates with external partners
  • Analyzes "big data" from social networks

Slide 64:

System Overview

EEDRR Decision Support System Architecture

(Extended Text Description: This slide shows the EEDRR framework depicted as two large systems (represented as rectangles) as shown in slide #20. The top system is called "External Networks." And the system under it is called the "Decision Support System." The External Networks includes four systems – Emergency Services Networks, Traffic Management Networks, Transit Management Networks, and Social Networks. The Decision Support System (DSS) has four arrows that link the DSS to each of the systems in the External Network. The DSS has three interconnecting subsystems – Interface Layer (data collection, command and control), Knowledge Layer (modeling, analysis, exercises, and accreditation), and Cloud Infrastructure Services Layer.)

Slide 65:

Operational Impacts

Assess Operational Impact to Organization

• Acquire real time data including probe data
• Establish command and control
• Process data and devise an optimum strategy
• Coordinate / control evacuation, response, recovery efforts
• Test and update through exercises and lessons learned

Slide 66:

Slide 67:

Question

What is the purpose of developing a concept of operation for EEDRR?

Answer Choices

1. Find support for funding a system
2. Resolve labor issues associated with operating a system
3. Identify size of operational force needed for disasters
4. Develop the scope of a decision support system

Slide 68:

Review of Answers

a) Find funding for a system
Incorrect. Used to determine amount of funding for the system

b) Resolve labor issues associated with operating a system
Incorrect. Labor issue may be identified as a result of the scope but not resolved.

c) Identify size of operational force needed for disasters
Incorrect. Resource identification is a product of the system not the concept of operation.

d) Develop the scope of a decision support system
Correct. A fully developed concept of operations determines the scope of the decision support system.

Slide 69:

Learning Objective 4

Applying the DSS to Transit

Slide 70:

Identify the Information Flows in the EEDRR-DSS

Information Sharing and Communications in the EEDRR-DSS

(Extended Text Description: This slide shows the EEDRR framework depicted as two large systems (represented as rectangles) as shown in slide #20. The top system is called "External Networks." And the system under it is called the "Decision Support System." The External Networks includes four systems – Emergency Services Networks, Traffic Management Networks, Transit Management Networks, and Social Networks. The Decision Support System (DSS) has four arrows that link the DSS to each of the systems in the External Network. The DSS has three interconnecting subsystems – Interface Layer (data collection, command and control), Knowledge Layer (modeling, analysis, exercises, accreditation), and Cloud Infrastructure Services Layer.)

Slide 71:

Methods for Information Sharing

Emergency Communications Methods

• Key communications networks
  • Information Networks
  • Open Sources
• Private Sources
• Voice Networks
  • Emergency Communication
  • Cellular Communications
• Social Networks

(Extended Text Description: This slide shows the EEDRR framework depicted as two large systems (represented as rectangles) as shown in slide #20. The top system is called "External Networks." And the system under it is called the "Decision Support System." The External Networks includes four systems – Emergency Services Networks, Traffic Management Networks, Transit Management Networks, and Social Networks. The Decision Support System (DSS) has four arrows that link the DSS to each of the systems in the External Network. The DSS has three interconnecting subsystems – Interface Layer (data collection, command and control), Knowledge Layer (modeling, analysis, exercises, accreditation), and Cloud Infrastructure Services Layer.)

Slide 72:

Information Flow

Information Flow Needs

• Stimuli Type
• Time
• Stimuli Content
• Incoming and Outgoing Recipient(s)
• Response(s)/Feedback
• Performance Standard
• Consequences

(Extended Text Description: This slide, entitled "Information Flow" contains a graphic on the right side of the slide that represents the communication between External Networks and the Decision Support System. The box containing the words "Interface Layer (data collection, command and control)" is highlighted while the rest are grayed out. The graphic is the same as described on Slide 20.)

Slide 73:

EEDRR-DSS Characteristics

EEDRR-DSS Layers

(Extended Text Description: This slide, entitled "EEDRR-DSS Characteristics" has a graphic in the middle of the slide that contains three connected boxes of different colors that show the layers in a Decision Support System. The green box on top reads, "Interface Layer (data collection, command and control)". An arrow from the green box connects to the orange box in the middle. The orange box reads, "Knowledge Layer (modeling, analysis, exercises, accreditation)". An arrow from the orange box connects to the blue box on the bottom that reads, "Cloud Infrastructure Services Layer". This is a partial graphic of the EERDD framework described on Slide 20.)

Slide 74:

EEDRR-DSS Characteristics/Personality

(Extended Text Description: Author's relevant notes: This slide, entitled "EEDRR-DSS Characteristics" has a graphic that shows three boxes that show the characteristics of the layers in Decision Support Systems. These are the characteristics of the interface, knowledge and cloud infrastructure layers. The details and configuration will depend on Transit's relationship, role and responsibilities within the regional context, as well as the type of event that occurs. Information Providers, Information Management, and Information Distribution. Each box is color coded to correspond to the characteristics of the DSS layer – green is the External Network and Interface layer, orange is the Knowledge layer, and blue is the Cloud Infrastructure Services layer.)

Slide 75:

Slide 76:

Question

Which layer is NOT a layer in the EEDRR-DSS?

Answer Choices

1. Network Layer
2. Interface Layer
3. Knowledge Layer
4. Cloud Infrastructure Services Layer

Slide 77:

Review of Answers

a) Network Layer
Correct! The External Network is located outside the DSS.

b) Interface Layer
Incorrect. This layer supports the methods of information sharing among external network actors.

c) Knowledge Layer
Incorrect. This layer manages, aggregates and processes the information into solutions.

d) Cloud Infrastructure Service Layer
Incorrect. This layer distributes information using accessible infrastructure technologies.

Slide 78:

Module Summary

What We Have Learned

1. Reviewed Elements of the Emergency Evacuation and Disaster Response and Recovery (EEDRR) Framework and the ISO 19083-1 standard
2. Discussed transit roles and responsibilities during the disaster response and recovery phases of an emergency
3. Used the Concept of Operations Template for specifying a Decision Support System (DSS) for Transit Emergency Management
4. Reviewed Characteristics of a Transit Emergency Management Decision Support System Based on the ISO 19083 Part 1 standard

Based on the ISO 19083 Part 1 standard

Slide 79:

Thank you for completing this module.

Feedback

Please use the Feedback link below to provide us with your thoughts and comments about the value of the training.

Thank you