Mass Notification Overview

Transcription

1 Program Mass Notification Overview Concepts for Successful Planning and Implementation.

2 Course Outline Our mass notification overview will cover these topics. Definitions and Goals Drivers Why is this so important now? Customers / Stakeholders Codes and Standards Planning Phase Technologies Challenges Application Solutions Page 2

3 Program Definitions.

4 Definitions Common Terms Terminology continues to evolve as needs become more clearly defined and understood: Mass Notification System (MNS) Most commonly used reference to emergency communication, used by military in UFC-2002 Emergency Notification System (ENS) Refers primarily to one-way communications to individuals and/or groups Integrated Emergency Notification System (IEN) Emergency communications through multiple systems and technologies Emergency Communications System (ECS) Broad definition adopted by NFPA for new NFPA72 Chapter 24, 2010 Edition Page 4

5 GOAL - Effective Emergency Communications Inform or Notify Building occupants and key personnel are alerted to WHAT is happening and WHERE it is occurring Provide Instruction Notification is only effective if it gives direction on how to act or what to do Verify Critical communications require verification that messages are heard, understood and acted upon Page 5

6 Program Drivers.

7 Tragic Events Raise the Focus This single event contributed to the development of a need to increase force protection of our troops The UFC standards were developed as a result Khobar Tower Bombing, Saudi Arabia June 25, 1996 Page 7

8 Tragic Events Raise the Focus This event illustrated the need for defense from unexpected threats The Department of Homeland Security was created in response to this event and others leading up to it The fire alarm voice system was used by firefighters after the initial attacks Survivability in the design helped save many lives World Trade Center Attack New York September 11, 2001 Page 8

9 Tragic Events Raise the Focus This event brought to the forefront the need to be able to communicate during emergencies to a large diverse population The NFPA has used this and other events to help shape the direction of the codes to support effective and reliable Emergency Communication Systems Virginia Tech Campus Shooting Blacksburg, Virginia April 16, 2007 Page 9

10 Customer External/Internal Drivers Political Pressures Stakeholder Concerns Public Relations Fiscal Responsibility & Budget Constraints Traditional mission to provide a safe work, learning, living environment Administration Urgency to Develop an Emergency Response Plan Code Compliance & Enforcement Liability Concerns & Risk Management Tragic Current Events EG: Virginia Tech Page 10

11 Program Customers / Key Stakeholders.

12 Who are the players? Customer Industry Providers Regulatory Agencies Page 12

13 Customer Activity Customer Industry Providers Regulatory Agencies Page 13

14 Customer Ownership May Be Unclear Administration Owner? Communications Director / IT Facilities Director?? Security Director/ Safety Officer?? Fire Marshal Risk Manager Page 14

15 Example Hospital Who is the decision maker here? Who is the AHJ? Page 15

16 Example Public Spaces Dynamic conditions Control Tower Runway Control Room Terminal Cargo Facilities Transient Population Hangar Parking Garage Physical Plant Multiple groups in control Page 16

17 How do we reach them all? Program Copyright Siemens AG All rights reserved..

18 Program Codes and Standards.

19 Regulatory Agency Activity Customer Industry Providers Regulatory Agencies Page 19

20 Regulatory Drivers Impacting Designs National Building and Fire Codes (IBC & IFC) Locally Developed or Amended Building and Fire Codes Federal Laws and Regulations (e.g. OSHA) Government Regulations (e.g. CSA,DoD, ADA) User Requirements, Including Insurance Provisions (FM) UL Desktop Standard 2572 for MNS systems ULC S576 for MNS systems Page 20

21 Agencies Active in Code Development Unified Facilities Criteria (UFC ) Military applications (2002) National Fire Protection Association (NFPA) NFPA Edition Proposed new Chapter 24: Emergency Communications Systems New requirements are being incorporated into system designs Audibility Intelligibility Survivability Supervised Circuits Underwriters Laboratory (UL-2572) MNS product standards Page 21

22 Program Planning Phase.

23 MNS Planning Approach: Partnering Through the Process Consultative Design Approach: 1. Identify critical incidents for planning and perform Risk Analysis and address immediate need 2. Create definition of desired state 3. Prepare current assessment of readiness 4. Survey facility/campus for existing infrastructure 5. Perform gap analysis to identify needs 6. Set priorities based on factors of influence 7. Apply portfolio of technologies, products & services 8. Scale solutions to capital and expense budgets 9. Execute effective Emergency Response Plan 10. Monitor for changing influence factors over time Page 23

24 Risk Probability Are you at risk? Page 24

25 Credentials 10 years of hostile threat risk analysis (The speaker must have learned something!) Architect for the SecurITree threat modeling software Risk analysis techniques used by intelligence agencies defence aerospace manufacturers financial institutions health care nuclear power building safety & security Both hostile and happenstance risks Page 25

26 Security vs Risk Warm fuzzies vs Defensible choices Security and safety are mostly based on Standards Industry practices Subject matter expert opinions (and experiences) Risk = Probability x Impact Specific and relevant to defender Different stakeholders have different risks Uses and captures subject matter expert opinions Canadian Critical Infrastructure is a target! Oil, gas and energy attack plans were found in Osama bin Laden s compound To hurt the USA, hurt Alberta energy supplies Page 26

27 The Quadrants of Risk Impact? Obvious! Nothing to worry about here Obvious! If you haven t done something by now, you are probably dead! Probability Obvious! Experience will make it apparent when nuisances need fixing Where do we spend almost all of our time and effort? Quadrant II and Quadrant IV Mathematically equal Are they equally important? So, why do we focus on IV? You may or may not have to worry about quadrant II scenarios Page 27

28 Impact For where your treasure is, there will your heart be also. Absolute impact is easy Perceived impact is more relevant What are your values? Are you protecting the right stuff? Page 28

29 Probability Random events Mother nature, equipment failure, human error Statistics are usually helpful Hostile events High impact attacks are rare (quadrant II) BUT Risk Probability Statistics are not helpful Must understand your adversary Random events are usually more probable than hostile events Hostile events can be more damaging than random events Combined events Opportunistic threats Page 29

30 Know Thine Enemy Do you have what your adversary wants? Does your adversary have the capability? Motivation and capability determine significance of quadrant II scenarios Threat modeling Canadian Institution The case of the Canadian tech school Two interesting cases Case 1 probability fixed, impact can be changed Case 2 impact fixed, probability can be changed Cost of control is very low Page 30

31 Solutions Choose solutions that reduce risk (either probability or impact or both) Make probable attacks more difficult for the adversary Prepare ahead to lessen the impact of an attack Choose solutions that are cost effective Choose multi-purpose solutions E.g., if your values focus on people, then mass notification solutions may reduce both random and hostile risk Solutions may have non-security, non-safety benefits What about quadrant II? Page 31

32 Amenaza Technologies Limited th St SW, Suite 125 Calgary, AB Canada T3H 5Z9 Toll free: Terry Ingoldsby: International: Page 32

33 Industry Activity Customer Industry Providers Regulatory Agencies Page 33

34 Status of Industry Response Evolving discussion continues to define the market Potential providers positioning their respective offerings Some leading with their particular product or strength: Fire alarm companies presenting as fire alarm solution Security companies presenting as security solution Communication companies presenting as communication solution Technology companies approaching solely as integrators Some opportunistically entering the market Few companies will be long-term players: Large companies re-visit strategic fit over time Small companies may not be around Page 34

35 Program Technologies.

36 Device Groups: Multiple Layers of Technology The system must be able to address all groups to be effective! Mass Notification System Inside PA / Intercom Outside Giant Voice At Your Side PDAs Video Screens Loud Speakers Mobile Phones Fire Panels EMS / Police Laptops Personal Computers Video Screens SMS / MMS Telephones Sirens IM Chat LED Displays Radio broadcast Indoor radio systems Indoor pager systems Page 36

37 Inside Devices Fire voice speakers Flat panel displays LED displays PA / Intercom Network PCs Phone Systems Wired and wireless buttons Indoor camera systems Page 37

38 Typical System Architecture Fire INSIDE Page 38

39 Typical System Architecture Fire Tornado Hurricane Shooter INSIDE Page 39

40 Typical System Architecture Fire Tornado Hurricane Shooter MNS Server INSIDE Page 40

41 Typical System Architecture Fire Tornado Hurricane Shooter MNS Server INSIDE Page 41

42 Outside Devices What Is Outside? The Outside Components consist of the following: Omnidirectional Speaker Arrays Directional Speaker Arrays Page 42

43 Typical System Architecture Fire Tornado Hurricane Shooter MNS Server INSIDE OUTSIDE Page 43

44 At Your Side Devices Products Pagers Cell phones / Smart phones Personal s IM (Instant Message) Alerts Duress Alarms Hand-held Radios Page 44

45 Typical System Architecture Fire Tornado Hurricane Shooter MNS Server INSIDE OUTSIDE AT YOUR SIDE Page 45

46 Typical System Architecture Fire Tornado Hurricane Shooter MNS Server INSIDE OUTSIDE AT YOUR SIDE Page 46

47 Typical System Architecture Fire Tornado Hurricane Shooter Building trouble Security alert Urgent action MNS Server INSIDE OUTSIDE AT YOUR SIDE Page 47

48 Typical System Architecture Fire Tornado Hurricane Shooter Building trouble Security alert Urgent action MNS Server Weather closing Daily messaging Video INSIDE OUTSIDE AT YOUR SIDE Page 48

49 Inputs to MNS System Inside: Fire Alarm System 3 rd Party Fire Alarm Systems Non-fire Alarm Systems Push Button Wireless Panic Button Network PC PBX Phone Outside: Weather Alert Service Blue Light Emergency Stations Giant Voice System At Your Side: Cell phone Smart phone with web-access Home phone Paging system Blackberry client Treo client Via: Contact relay RS-232 TAP, SNPP, WCTP (paging protocols) Ethernet Internet Phone System Page 49

50 Hosted Messaging Page 50

51 I got the emergency text message 2 days later Lowest Level 1 (Mobile Text Messaging, Wireless Text Messaging) Not technically true SMS. Basically to mobile devices. Only 1-way, delivery delays, security issues, spam, server congestion Should not be relied on for emergency situations Medium Level 2 (SMS device to SMS device) 2-way messaging, improvement in delivery and security over Level 1 Retail technology - used for messaging between friends and relatives Messaging companies do not use level 2. Many do use Level 1 Highest Level 3 (Commerce Transactions) (INSIST ON THIS LEVEL) Speed, accuracy, and reliability is of utmost importance for carriers. Highest care taken. 1-to-many, 2-way, premium cost mostly offered as a subscription Level 3 messages have delivery priority over Levels 1 and 2 Page 51

52 Reach Anyone, Any Device, Anywhere Page 52

53 Program Challenges.

54 Challenges Identifying the decision makers in a facility Getting buy in from all stakeholders Risk Assessment Emergency Action Planning Financial Impact (Budgeting) Phased implementation (Master Planning) Ongoing evaluation (perpetual integration) Long term support Page 54

55 Program Application Solutions.

56 Involve Key Decision Makers to Solve the Issue Master Planning Consultative Approach Perpetual Evaluation Education Innovation Thought Leadership Community Awareness Benefit to the public Gap Analysis Integrated Solution Education Detailed discussions of the risks and needs Select decision makers per discipline Communication of the plan and schedule Use of existing infrastructure Adaptable solution for occupancy changes Select proven vendors that are driving the technology forward Page 56

57 Leverage Existing Infrastructure & Resources Fire Alarm Systems Paging Systems IT Networks Telephone Systems Construction Budgets Security Systems Scoreboards and Audio Systems Government Funding Page 57

58 Comprehensive Solutions need Multiple Technologies with a Clear Purpose User Interface for Web Access INSIDE Systems Enhance the capabilities of familiar systems Real-Time Vision & Security Enterprise Level Command & Control Capability Software GUI Knowledge Management INSIDE Comprehensive MNS Solution Real-Time Vision & Security Real-time vision for Safety, Security and Communication in the event of an emergency Integrated Data Systems Integrated Data Systems Architecture must be scalable to meet demanding needs OUTSIDE IT Infrastructure Automatic & Ad Hoc Messaging AT YOUR SIDE AT YOUR SIDE Additional methods of messaging Sharing data from separate systems enhancing their capabilities Broadcast messages to large areas Automatic messaging for planned events with flexibility for unplanned circumstances Personal devices can be utilized as an added level of protection Page 58

59 Program Mass Notification Overview Thank You!.