incident management systems - fefpa 2016/fefpa... · ims – incident management system ....
TRANSCRIPT
Incident Management Systems
aka MNS, ECS, et al
2
DEFINITIONS
STANDARDS
SUMMARY
Agenda
ASSESSING RISK
Definition(s)
ECS – Emergency Communication System
EAS – Employee Alarm System
MNS – Mass Notification System
ENS – Emergency Notification System
IMS – Incident Management System
Definition(s)
NFPA 72 National Fire Alarm and Signaling Code, 2013 Edition
3.3.87 Emergency Communications System.
A system for the protection of life by indicating the existence of an emergency situation and communicating information necessary to facilitate an appropriate response and action.
ECS – Emergency Communication System
Definition(s)
OSHA 3122-06R, 2004
OSHA 29 CFR 1910.165 Employee Alarm Systems
• 1910.165(b)(1)
– The employee alarm system shall provide warning for necessary emergency action as called for in the emergency action plan, or for reaction time for safe escape of employees from the workplace or the immediate work area, or both.
EAS – Employee Alarm System
Definition(s)
UFC 4-021-01, changed January 1, 2010
UFC 4-021-01
1.1 BACKGROUND
Mass Notification provides real-time information and instructions to people in a building, area, site, or installation using intelligible voice communications along with visible signal, text, and graphics, and possibly including tactile or other communication methods. The purpose of mass notification is to protect life by indicating the existence of emergency situation and instructing people of the necessary and appropriate response and action.
MNS – Mass Notification Systems
Incident Management System
“The combination of facilities, equipment, personnel, procedures and communications operating within a common organizational structure, designed to aid in the management of resources during incidents” - NFPA 1600 2013
Reference: http://www.ready.gov/business/implementation/incident
8
Incident Management
ERP Preparation & Training
Single Seat Command & Control
Distributed Intelligence
Effective Tools to enhance ERP
Standards
COMPANY CONFIDENTIAL
Combination
Systems
Interface with MNS
PA Systems Used for MNS
Chapter 24 – ECS Emergency Communications
Systems (ECS) Chapter 24
24.1
In - Building EVACS 24.2.1
In - Building MNS
24.2.2
Wide - Area MNS
24.2.3
Distributed Recipient MNS
24.2.4
Two-Way Radio Emergency Services ECS
24.3.2
Area of Refuge ECS 24.3.3
Elevator ECS 24.3.4
Two-Way Wired Emergency Services ECS
24.3.1
Performance Based Design
24.5
Information
Command and Control 24.4
One-Way Emergency Communications
Systems (ECS) 24.2
Two-Way
Emergency Communications Systems (ECS)
24.3
Public
Alert Measures
Public Radio – TV
MNS / IMS Priority Layers
DRMNS Ancilliary Systems SMS – Email – Computer
Pop-Ups - Apps
Exterior Emergency Voice Alarm
Communications Systems
IMMEDIATE – INTRUSIVE –SURVIVABLE
Emergency Voice Alarm Communications Systems
IMMEDIATE – INTRUSIVE – SURVIVABLE
NFPA 72
• 3.3.246 Risk Analysis:
– A process to characterize the likelihood, vulnerability, and magnitude of incidents associated with natural, technological, and manmade disasters and other emergencies that address scenarios of concern, their probability, and their potential consequences
• 24.4.3.14.1 (Voice Message Priority)
– The priority of mass notification messages shall be established using the emergency response plan
• 24.4.3.14.4
– When identified by the emergency response plan, messages from the mass notification system shall be permitted to take priority over fire alarm messages and signals
National Fire Alarm and SIGNALING Code
NFPA 72
• 7.3.6 Risk Analysis Documentation
• 7.3.8 Emergency Response Plan Documentation
• 7.3.9 Evaluation Documentation
– 7.3.9.1 Evaluation documentation, such as identified in 23.4.3.1 and 24.4.3.24.2, shall include a signed statement(s) by the person responsible for the design attesting to the evaluation and the resultant technical decision and deeming it reliable and acceptable for the particular application
– 7.3.9.2 A copy of the evaluation documentation shall be retained for the life of the system and be maintained with the documents required by 7.7.1.6
National Fire Alarm and SIGNALING Code
NPFA 72
• Figure A.7.8.2(g) RISK ANALYSIS CHECKLIST
– Part One: Identification of Assets or Operations at Risk
– Part Two: Determination of Facility Hazards
National Fire Alarm and SIGNALING Code
OSHA
• 1910.165(a) Scope and Application
– This section applies to all emergency employee alarms installed to meet a particular OSHA standard
• 1910.165(b) General Requirements
– …necessary emergency action…
• 1910.165(b)(3)
– The employee alarm shall be distinctive and recognizable as a signal to evacuate the work area or to perform actions designated under the emergency action plan.
• Sounds a lot like a RISK ASSESSMENT
29 CFR 1910 Employee Alarm System
UFC 4-021-01
• US Army: Army Corps of Engineers,
– (HQ USACE/CECW-CE)
• US Navy: Naval Facilities Engineering Command
– (NAVFACENGCOM HQ Code CHE)
• US Air Force: Air Force Civil Engineer Support Agency
– (HQ AFCESA/CEO)
• US Marine Corps
– (HQMC Code PS an dCode LFF-1)
• Other DOD Components – The office of the Deputy Secretary of Defense via the DOD committee on Fire Protection
Design and O&M: MNS / IMS
UFC 4-021-01
• Chapter 1: Background
– 1-5 Qualifications of Suppliers and Contractors
– 1-6 Security Engineering UFC Series
• Chapter 2: Overview of Systems
– 2-3 Life Safety Systems
– 2-5 Public Alert and Warning Systems
– 2-6.1 Wide Area MNS
– 2-6.2 Individual Building MNS
Design and O&M: Mass Notification Systems
UFC 4-021-01
• Chapter 3: Wide Area MNS
– 3-2 Requirements for System Designers
– 3-3 System Signals (Voice | Music | Tones)
– 3-5 Central Control Stations
– 3-6 HPSA
– 3-7 Communication Links
• Chapter 4/5: Individual Building MNS (New/Renovations)
– ACU – Autonomous Control Unit
– LOC – Local Operating Console
– Individual Branch Installation Block Diagrams
Design and O&M: Mass Notification Systems
UFC 4-021-01
• Chapter 6: SPECIAL CONSIDERATIONS
– 6-2 IMPLEMENTATION PLAN:
• Each DOD installation should establish an implementation plan that establishes a comprehensive approach to MNS that is acceptable to security, communications, and fire protection engineering personnel. Elements of an implementation plan should include a needs assessment, requirements definition, alternatives evaluation, system selection, and implementation schedule.
Sounds a lot like a RISK ASSESSMENT
Design and O&M: Mass Notification Systems
Standards Summary
• Each of the Standards reviewed seem to have a common theme: – Prepare for the Threat – Respond to the Threat – Recover from the Threat – Mitigate Future Threats
• How better to do this than through an – Integrated Incident Management System that captures any
and all inputs at a common location with a single seat of operation designed in coordination with the • Risk Assessment • Emergency Response Plan
EMERGENCY RESPONSE PLAN (ERP)
The ERP is based on vulnerability assessment and risk analysis of the facility.
An effective MNS must follow the established ERP.
Assessing Risk
• 1.1 Scope. – This standard shall establish a common set of criteria for all hazards
disaster/emergency management and business continuity programs, hereinafter referred to as “the program”.
• 1.2 Purpose. – This standard provides the fundamental criteria to develop, implement,
assess, and maintain the program for prevention, mitigation, preparedness, response, continuity, and recovery.
• 1.3 Application. – This document shall apply to public, not-for-profit, and nongovernmental
organizations (NGOs) and to private entities.
NFPA 1600 Standard on Disaster/Emergency Management and Business Continuity Programs
Assessing Risk
• Chapter 1: Administration
• Chapter 2: Referenced Publications
• Chapter 3: Definitions
• Chapter 4: Program Management
• Chapter 5: Planning
• Chapter 6: Implementation
• Chapter 7: Training and Education
• Chapter 8: Exercises and Tests
• Chapter 9: Program Maintenance and Improvement
NFPA 1600 Standard on Disaster/Emergency Management and Business Continuity Programs
Assessing Risk
• Annex A: Explanatory Material
• Annex B: Program Development Resources
• Annex C: Self-Assessment for Conformity with NFPA 1600, 2013 Edition
– Conforming; Partially Conforming; Nonconforming; Comments
• Annex D: Plan-Do-Check-Act (PDCA) Cycle – Figure D.1
• Annex E: Crosswalk between NFPA 1600, DRII, and CSA Z1600
• Annex F: NFPA 1600 2013 Edition as a Management System Standard
NFPA 1600 Standard on Disaster/Emergency Management and Business Continuity Programs
Assessing Risk
• Annex G: Maturity Models
• Annex H: APELL (Awareness and Preparedness for Emergencies at Local Level
• Annex I: Family Preparedness
• Annex J: Informational References
NFPA 1600 Standard on Disaster/Emergency Management and Business Continuity Programs
Assessing Risk
= X X + +
Risk Assessment – models
RISK MANAGEMENT ACTIONS
I m p a c t
Significant Considerable management
required
Must manage and monitor risk
Extensive management
essential
Moderate
Risks may be worth accepting with
monitoring
Management effort worthwhile
Management effort required
Minor Accept risks Accept, but monitor
risks Manage and
Monitor Risks
Low Medium High
Likelihood
Risk Assessment Models
Incident Management System
33
Incident Management Systems Single Seat Command & Control
Single Point of Command & Control
34
Resizable viewports keep
user informed! 5 viewport, dual screen example shown
Map Viewport Event Action Viewport
Event List Viewport
Browser Viewport Image Viewport
Graphic User Interface Flexibility
35
Remote Web Client Software
Bldg 1 FACP
Equipment Room
Graphic Command Interface
Bldg 2 FACP Bldg 3 FACP
Integrated Network with Existing Non-EST Panels
Paging
Unit
Bldg 4 FACP
EOC
Interconnectivity Across Brands
Incident Management
EVENT TYPES • Critical Monitoring • Manual Activation • Fire Detection • Security Breach • Building Controls • Custom Defined
Emergency Response Plan Management tool
EVENT RESPONSES • Intelligible Voice
Notification • Visual Signage • Computer / Email
notification • Remote Control
capabilities • Communication to First
Responders • Commands to other
systems
Automating the Emergency Response Plan for Life Safety
“When an emergency occurs, the first priority is always life safety. The second priority is the stabilization of the incident.” http://www.ready.gov/business/implementation/emergency
Summary
• Notification only part of solution
• Government guidance / standards development / code requirements
• Uniqueness of individual solutions
• Single seat of command and control main goal
• Technology advantage - not end all
• IMS = ERP Tool
37
Understanding Incident Management Systems Mike Browning