Emergency Communications “ The Four legs of effective emergency communications ”

1. Emergency Communications“The Four legs of effective emergency communications” GSC9/Joint_028 Dan Bart, Senior Vice President, Standards and Special Projects, TIA Co-Chair, ANSI HSSP Emergency Communications Workshop NIST December 14-15, 2005 1

2. Mission To enhance the global competitiveness of U.S. business and the American quality of life by promoting and facilitating voluntary consensus standards and conformity assessment systems and ensuring their integrity. A Private- and Public-Sector Partnership Since 1918 ANSI is not a government agency or a standards developer.

3. A Federation of members representing . . . • Academia • Individuals • Government • Manufacturing • Trade Associations • Professional Societies • Service Organizations • Standards Developers • Consumer and Labor Interests • and many more. Bringing the Private and Public Sectors Together Since 1918

4. ANSI is . . . • an “umbrella” organization for the U.S. voluntary consensus standards community • a private-sector led and public-sector supported standards coordination body • a not-for-profit organization • ANSI is not . . . • a standards developer • a government agency

5. Background:HS Standards Coordination Needed • The National Strategy for Homeland Security (2002)identified the need for standards to support homeland security (HS) and emergency preparedness • Fourteen critical infrastructure areas were noted • January 2, 2003 Report for Congress states:“Neither the federal government, nor the nongovernmental sector presently has a comprehensive, consolidated program for developing new preparedness standards.”

6. Response: ANSI-HSSP • February 5, 2003: Formation of ANSI-HSSP announced • Facilitate the development and enhancement of homeland security standards • Serve as private/public sector forum for standards issues that cut cross-sector • Co-chairs provided by industry and government • A forum for information sharing on HS standards issues • Does not itself develop standards • Not a “gatekeeper” for access to DHS or other agencies

7. ANSI-HSSP Structure • Lead by ANSI-HSSP Co-Chairs • Steering Committee • Comprised of Government Agencies, ANSI SDOs, non-ANSI SDOs, and Companies (ANSI members and non-ANSI) • Advisory Group (TAG) to US Experts to ISO Security Advisory Group (SAG) • Full Panel: Nearly 100 organizational participants

8. ANSI-HSSP – Participation • Participation on the HSSP is open to all affected interests (ANSI and non-ANSI members) • Federal, State and Local governments • Industry representatives • Trade Associations and Professional Societies • Standards Developers (ANSI and non-ANSI) • Fora/Consortia • Academia • Consumer interests • ANSI HSSP uses Plenary Meetings and Workshops • Biological and Chemical Threat Agents • Enterprise Power Security and Continuity • Perimeter Security Standardization • Training Programs for First Response to WMD events

9. ANSI HSSP WORKSHOP ON EMERGENCY COMMUNICATIONS (December 2004, Chicago) • The term “Emergency Communications” means different things to different people or organizations • To some, it is only TELE-communications • To others it is the “content” of the message or communication, not the media or facilities used, i.e., the “water” not the “pipes” • To some, “emergency communications” only come from GOVERNMENT • Many believe emergency communications must cut cross-sector and cross-technology areas to be effective and harmonized, and to send an unambiguous, important communication • Must also consider persons with disabilities in sending and receiving emergency communications • Must also consider citizens for whom the primary language is not English • What does it mean in the TELECOM Sector and for the ANSI HSSP Emergency Communications Workshop and breakout groups??

10. EMERGENCY COMMUNICATIONS • The major communications sector standards organizations gather periodically at an event called Global Standards Collaboration or GSC • Those organizations who participate on a regular, recurring basis are called “Participating Standards Organizations” or PSOs, and currently consist of: • TIA and ATIS (USA); ETSI (EU); ISACC (Canada); TTA (Korea); TTC and ARIB (Japan); ACIF (Australia), and CCSA (China). • ITU-T and ITU-R also participate regularly • Other groups have also been invited and most have participated: ANSI, JTC-1, IETF, ATMF, IEEE, SCTE, APT, CITEL, IEC, ISO, ITSA, etc. • Next GSC in Chicago in May/June 2006, hosted by TIA • www.gsc.etsi.org

11. Global Standards collaboration (GSC)RESOLUTION GSC-8/1: Emergency Communications (Ottawa 2003) • Concludes • that emergency communications can be partitioned into concerns covering communication (1) from citizens to authorities and/or organizations providing emergency services, (2) between such authorities, (3) from such authorities to citizens and (4) amongst affected citizens; • that it is important for PSOs, authorities and/or organizations providing emergency services in countries across the world to continue to collaborate in the development of technical standards, and to share information on emerging technologies and services that can be used for emergency communications;

12. Resolution GSC-10/02: (Joint) Emergency Communications (Sophia-Antipolis 2005) Resolves: • to establish a continuing area of work on “emergency communications” to further encourage cooperation and the sharing of information among SDOs, ITU, and others working on standardization activities relating to communications in emergency situations, in particular addressing • communications from individuals/organizations* to authorities • communications between and among authorities • communications from authorities to individuals/organizations • communications amongst affected individuals/organizations. including, but not limited to, developing standards applicable to existing and future systems for: • technical means for delivery of early warnings or alerts • priority access to emergency call access numbers; • provision of location information; • suitable technologies for use in networks dedicated to public protection and disaster relief communications; • interoperability between public networks and networks dedicated to emergency communications; • priority access by emergency services personnel to communications services; * Use of the term “individuals/organizations” is intentionally broad and intended to include citizens, non-citizens and visitors, employer-to-employee emergency communications, as well as employer-to-employer, and also encompasses the unique concerns for persons with disabilities and those individuals who may not be fluent in the language(s) or dialects in use in the locus of the emergency or disaster.

13. Resolution GSC-10/02: (Joint) Emergency Communications (Sophia Antipolis 2005) Resolves: • to encourage ongoing cooperation and collaboration among national, regional and international activities that relate to emergency communications, such as Project MESA and to provide forums to collect aggregated government users’ needs at the local, state or provincial, or national/international level; • to encourage PSOs to support ongoing national activity and cooperation between industry, PSOs, administrations and authorities in the establishment of emergency communications and harmonize terminology used, for example, use of the term “emergency communications” and not “emergency telecommunications” in order to embrace and include the widest range of new systems, services, and technologies and not just “telecommunications”; • to draw to the attention of PSOs the need to examine the characteristics of providing emergency communications over packet-based networks, including Next-Generation Networks; and • to enhance collaborative efforts at the international level to make most efficient use of resources and enable a timely and focused approach in the global deployment of systems and solutions.

14. Types of Emergency Communications • Indiv/Org-to-Indiv/Org: An individual communicating an emergency to another individual or private organization via available options (e.g., ONSTAR-like message, amateur radio, mobile and land-line communications, broadcast and mass media, Internet, email lists, faxes, information services, and word of mouth). • Indiv/Org-to-Government: An individual communicating an emergency message to appropriate authorities via available options (e.g., E9-1-1/1-1-2 call to Public Safety Answering Point (PSAP), amateur radio, and mobile communications (with or without location services). • Government-to-Government: Governmental authorities communicating to each other, other agencies and appropriate National Security / Emergency Preparedness (NS/EP)-designated private industry concerns and coordinators (i.e., using all forms of communications services, private radio, Commercial Mobile Radio Services, e-mail/messaging alerts, etc.). • Government-to-Indiv/Org: Government or authorized officials communicating alerts or details of an emergency to individuals and organizations via available options (e.g., Governmental mass media alerts, citizen accessible radio services and common channels, highway alerts, voluntary private sector alert services [localized and national], e-mail/voice-mail and word of mouth).

15. Individuals/Organizations to Government Authorities and/or orgs providing emergency services Note: The previous term “Citizens” included Private Individuals or organizations. TSP (NS/EP) Restoration Services Amongst and between affected individuals Includes Employer-to- Employee and Employer- to- Employer Between Government Authoritiesand/or orgs providing emergency services. Also GETS and WPS From Government Authorities and/or orgs providing emergency servicesto individuals/organizations

16. Legend: I/OtoI/O Emergency Communications GtoI/O GtoG I/OtoG As per GSC Resolutions on Emergency Communications (2003, 2004, 2005). Telecom & Radio Services Broadcast MediaServices Internet Other

17. Implementation Example: National Emergency Telecommunications Services (U.S. NS/EP Services Structure) Note: This graphic model of U.S. ETS and services provided is intended as a visual example; not as an official consensus or decision.

18. Types of Emergency Communications (Services and Support) “On-Star”-like service, SASvE, CtoCvPSTN/CMRS, ARS, GMDSS, CtoCvS Broadcast news affiliates, Shortwave radio notification, Print media GASvE, GASvS, GASvH, ARS, GMDSS, TsecEmCom, NCAS, etc. Web access, Information services CtoCvWoM EBS (TV & Radio), Broadcast news affiliates, Amber Alerts, Print media ETS, GETS, WPS, NETS, PRS, CMRS, PSAP, TSP, GMDSS, SatService, TsecEmCom, WPSvSatCom, IPSvSatCom, CWIN, PSWIN, SAFECOM, AGILE, TDR/PPDR, ATIS, TIA TR-8, Project MESA, etc. PSECS, NCAS, TSP CATV, SatCom, TsecEmCom, GtoCvWoM Intra-Gov’t broadcast ENA, PSTN, PSAP, PACA, ARS, LAES & location ID component, TSP, GMDSS TsecEmCom, IPS, IPSvCable,TSP EBS (TV & Radio), Broadcast news affiliates, ARS, Shortwave radio notification VoIP/ENA, IPS, TSP WoM, ??, I/OtoI/O GtoI/O GtoG I/OtoG Note: Acronyms used and their placement are not necessarily approved, but try to visually show the kinds of Emergency Communications that are available and being used.

19. ARS: Amateur Radio Services CATV: Cable Television Citizen: Includes private individuals or organizations CMRS: Commercial Mobile Radio Services CtoCvS: Citizen to Citizen via SMS/text CtoCvWoM: Citizen to Citizen via Word of Mouth CWIN: CIP & Cyber Warning Information Network Emergency Communications: Encompassing of all forms and services available to governments and citizens Emergency Telecommunications: Including telecommunication infrastructure transmission & reception and the variety of emergency and priority communications services concerning public, dedicated and private telecommunications networks (i.e., NS/EP ETS) ENA: Emergency Number Access (i.e., 9-1-1, E9-1-1, E1-1-2, E1-1-9, etc.) EBS: Emergency Broadcasting System ETS: Emergency Telecommunications Service (NS/EP) GASvE: Government Alert Service via Email GASvH: Government Alert Service via Highway GASvS: Government Alert Service via SMS GETS: Government Emergency Telecommunications Service (NS/EP) GMDSS: Global Maritime Distress and Safety System Government: Appropriate authority and/or organizations providing emergency or other response services (NS/EP) IPS: Internet Priority Service (NS/EP) LAES: Lawfully Authorized Electronic Surveillance (NS/EP) NCAS: National Cyber Alert System NETS: Nationwide Emergency Telecommunications Service (NS/EP) NS/EP: National Security/Emergency Preparedness Project MESA: Public Safety Int’l Partnership for Broadband Capabilities, Mobility for Emergency and Safety Applications PRS: Private Radio Services (e.g., P25, Tetra) PSAP: Public Safety Answering Point PSECS: Public Schools Emergency Communications System PSWIN: Public Safety Wireless Network PSTN: Public Switched Telephone Network SAFECOM/AGILE: US Government programs addressing public safety communications issues (i.e., interoperability) SASvE: School Alert Service via Email TsecEmCom: Transportation-sector Emergency Communication systems (e.g., Amber Alert on Highway Sign TDR: Telecommunications for Disaster Relief (ITU-T) TSP: Telecommunications Service Priority (NS/EP) VoIP: Voice over Internet Protocol WPS: Wireless Priority Service Terms and Acronyms Used: Note: Acronyms used are not necessarily approved, but an attempt to visually show the kinds of Emergency Communications that are available and being used.

20. Emergency Communications area NOT reviewed in the ANSI HSSP workshop, since being addressed in other places • Government-to-Government (GtoG): Governmental authorities communicating to each other, other agencies and appropriate National Security / Emergency Preparedness (NS/EP)-designated private industry concerns and coordinators (i.e., using all forms of telecommunications services, private radio, Commercial Mobile Radio Services, e-mail/messaging alerts, etc.) • “Interoperability” is the ability of two or more organizations to communicate and share information (voice, data, images, and video) in real or near real time • There are numerous other activities and Workshopsaddressing government-to-government communications and interoperability including activities such as: • NIST/DHS Public Safety Interoperability Workshops • SAFECOMM Office of DHS • AGILE (Advanced Generation of Interoperability for Law Enforcement) Program • Project 25 and other work in TIA TR-8 • National Public Safety Telecommunications Council (NPSTC) • Public Safety Wireless Advisory Committee (PSWAC) • National Task Force on Interoperability • APCO, NASTD, FLEWUG, and other User Organizations’ activities • Internationally at ITU, Project MESA, GSC, etc. • To name a few

21. Alliance for Telecommunications Industry Solutions (ATIS) American National Standards Institute Association of Public-Safety Communications Officials (APCO) BearingPoint Bell Mobility BSA, Webelos 2 Den Leader from Pack 1071 Cingular Wireless Emergency Services Interconnection Forum (ESIF) ETSI EMTEL Presentation Gallaudet University IHS/Global Industry Canada Intrado Kontek Industries Lockheed Martin Lucent Technologies Motorola, Inc. National Electrical Manufacturers Association (NEMA) NFPA 1600 Technical Committee National Institute of Standards and Technology (NIST) National Emergency Number Association (NENA) Network Reliability and Interoperability Council (NRIC) Pacific Northwest National Labs Send Word Now Communications Society of Cable Telecommunications Engineers (SCTE) Telecommunications Industry Association (TIA) The JED Group, LLP The Safe America Foundation Underwriters Laboratories (UL) Urban Health Inc US Department of Homeland Security – FEMA US Department of Homeland Security – S and T Directorate Verizon Wireless Emergency Response Team (WERT) Western Suburban Consolidated Dispatch Center Wheelock, Inc. Organizations Present at ANSI HSSP EC and Citizen prep Workshops in 2004

22. Citizen Preparedness needs during HSSP WS were identified: • Unpredictability of events and resources available (e.g., which communications methods will be knocked out and how will relays work?) • Family members or friends with disabilities (e.g., hearing, sight, etc.) • Language barriers (reaching non-English speakers) • Knowing who in your neighborhood is a ham/CB/etc., operator that could assist with emergency communications • Know what your Employer policies are for reaching employees • Have an “out of area” contact point family can use to relay messages • Pre-programmed messages in cell phones (e.g., SMS) that can be sent (“Help,” “I’m ok,” etc.) • All emergency phone numbers of schools, work, neighbors, should be in your phone NOW! • What are your alternates to using 911 (i.e., citizens being able to communicate with citizens when 911 is down) or to report the emergency? • Program your phone for non-emergency numbers for police, fire, EMS, etc.

23. Government-to-I/O Issues Discussed, also the need for citizen PREPAREDNESS • The public safety agency (or other government body) comes back to the public with alerts or warning messages or other governmental emergency information. • What needs to be sent out, • By whom will it be sent, and • Under what circumstances? • What is measurement of success of the emergency communications? • Emergency Communications will often take place during time of extreme stress on resources. • Are you prepared to receive the messages? • Redundant service providers and equipment, line-powered phones, some form of back-up power, NOAA Radio, AM/FM Portable and batteries. • Do you have a GO BAG? • Boy Scouts/Cub Scouts/Girl Scouts are trained to BE PREPARED!

25. “BE PREPARED” • Review NFPA 1600 checklist • Did you prepare for Y2K? • Food, Water, Shelter, Medicine, Money? • Back up power and lighting? Warmth, cooking? • “Shelter in place” at work and school? Rx’s? • Copies of Emergency Numbers, Meeting Place • Know resources in the Neighborhood, do you know a “Ham” i.e., Amateur Radio operator • Work is a “function” not a “place,” telecommute? • Gas mask? NOAA radio? FRS/GMRS? CB? • DHS and Ready.gov, Red Cross, FEMA and other resources • Have a plan and rehearse with the family, neighbors, and co-workers, update lists.

26. Summary • ANSI HSSP participants provide the base of expertise and ANSI will continue to rely on them to be active in HSSP workshops and bring key issues/needs to the Panel’s attention • A good deal of progress has been made, but there is much work still to be done • For further information or questions, please visit the ANSI-HSSP website (http://www.ansi.org/hssp) or contact the ANSI-HSSP Secretary, Matt Deane (212-642-4992, mdeane@ansi.org)