Nevada Digital Government Summit Thursday, December 6 3:20 - 4:20 PM Emergency Communications Jim O’Brien, PhD Director, Clark County Office of Emergency Management and Homeland Security
Emergency Communications Natural disasters in recent months have shown more than ever the critical role of technology in business continuity and in the community as a whole. Communications, interoperability, quick response, information availability and public alerts are all vital concerns. This session will provide an overview of all state and local government emergency communications systems available in the state of Nevada.
Emergency Management • “Emergency” – both a noun and adjective
OVERVIEW …what we’ll cover • Our Vulnerabilities and Need for Communications …the situations and people who use it • The Types and Applications of Communication Systems…the old, the new, and the glue • Present Status and Direction…the problems and what we’re doing
IN NEVADA …we have Vulnerabilities and Need • EVERYDAY PS OPERATIONS – 95% of Communications USE • OCASIONAL Natural Disasters • Flash Floods • Earthquakes • Wildfires • POTENTIAL Man-caused Incidents • HazMat Incidents • Large Scale Accidents, e.g. Pepcon Explosion, Galaxy Crash • Terrorist Vulnerability
IN NEVADA …we need Vulnerabilities and Need • All three basic classes of communications in a large emergency: • OPERABILITY • INTEROPERABILITY • PUBLIC COMMUNICATION
IN NEVADA …we need Vulnerabilities and Need More INTEROPERABILITY, and the training to use it.
What is Interoperability? “Interoperability is the ability of appropriate officials and personnel to effectively communicate by radio across jurisdictions and with each other, when authorized, as needed and in real time.”
Interoperability Continuum - SAFECOM • Designed to help the public safety community and local, tribal, state and federal policy makers address critical elements for success as they plan and implement interoperability solutions. • Dimensions include: - Governance - Standard operating procedures (SOP) - Technology - Training and exercise - Usage, or how often is it employed
IN NEVADA …we have …challenges Vulnerabilities and Need Differing FrequencyBands in use VHF/150MHz UHF/450MHz 700/800MHzDiffering TechnologiesConventional & Trunking Wide and Narrowband Analog and Digital Differing Protocols Motorola Macom P25
Vulnerabilities and Need NCSC • 5 years old • Chartered by Executive Order • Charged to produce InterOp Plan • Representative body – 21 members • Represent:- Multi Disciplines- Multi Jurisdictions- Multi Levels of Government & NGOs
GOVERNANCE - ORGANIZATION CHART Governor DEM Homeland Security Commission CCOEM&HS Nevada Communications Steering Committee(NCSC) InterOp Comm Working Group User Groups, Disciplines Local, State Fed, Tribal Agencies, NGOsJurisdictions
Nevada Communication Interoperability PlanNCSC Established Existing Plan Overview - BACKGROUND 2002 - Communications Conference Held NCSC Established 2003 – Legislature : Create InterOp Plan 2004 - Planning Grant, consultant Survey, Recommendations 2005 - Plan v.1 Oct05SAFECOM Assistance 2006 – Plan v.2 Apr06
Nevada Communication Interoperability Plan Existing Plan Overview - BACKGROUND 2007 • DHS announces all states must create a State Communication Interoperability Plan (SCIP) by 3dec07 • NCSC starts work, many participants provide input to SCIP v.3 • SCIP Plan v.3 approved and submitted 3Dec07 !!!
Nevada Communication Interoperability Plan Existing Plan Overview NCIP Plan v.2 SCIP Plan v.3 NCIP Plan v.1 Oct05 Apr06 3Dec07
NV Radios by Proportion Washoe Clark * Note: Esmeralda, Lincoln not shown
Status and Direction Standard Operating Procedures • Needed to OPERATE effectively • Not in place throughout Nevada • ’06 grant funds - Initial Development • Must Be Accepted, Adopted, Used
SOP & Training Module – ’06 HSGP • To develop SOPs for use statewide by all public safety communications users • Develop common nomenclature, terms & definitions • Develop training materials & syllabus • Develop policies for jurisdictional adoption, and present • Lead agency: LV Metro Police Dept • Budget : $556,400
Engineering Module – ’06 HSGP • To complete technical data collection • Perform detailed engineering for interconnects & gateways • Produce comprehensive interoperable frequency plan statewide • Produce individual system-oriented integration plans • Lead agency: Dept of Information Technology • Budget: $556,400
Status and Direction Four Technology Methods in Plan: • Radio Caches • Gateways • Interconnects • Standards Convergence
Status and Direction Four Technical Methods in Plan: • Radio Caches- “swap radios” approach- Simple, easy to understand method- Basic contingency/backup provision • Gateways • Interconnects • Standards Convergence
Radio Cache Module – ’06 HSGP • Procure, maintain and hold available for use statewide, a cache of portable radios • Lead Agency: LV Metro Police Dept. • Budget: $500,000
Status and Direction Four Technical Methods in Plan: • Radio Caches • Gateways- “Cross-band” connected repeater- Creates one mutual aid channel- Fixed:Distributed on mtn top sites- Mobile: setup at incident site • Interconnects • Standards Convergence
Short-Term Gateways • Short-term proposal is to link the two main components of the Nevada radio system: • 700/800 MHz (Core Four) & 150 MHZ (rural) • Some gateways currently exist, but need to be expanded statewide. • Preliminary estimate for short-term: $2.4M • Cost does not include integration of other frequency bands.
Gateways & Interconnects Module – ’06 HSGP • To procure, install and implement interconnections among major radio systems and geographically distributed gateways among radio bands • Lead Agency: Nevada Department of Administration • Budget: $2,400,000
Status and Direction Four Technical Methods in Plan: • Radio Caches • Gateways • Interconnects- Similar to “shared channels”-Digital links btwn trunking systems- Multi “channels” provided btwn sys- All available through one radio • Standards Convergence
Core Systems – Short & Long-Term • By connecting the major trunked systems a single “virtual” system is created. • Nevada Shared Radio System (NSRS) • Southern NV Area Communication Council (SNACC) • Washoe County Regional Communication System (WCRCS) • Las Vegas Metropolitan Police (LVMPD) • [ability to connect addition core systems]
Status and Direction Four Technical Methods in Plan: • Radio Caches • Gateways • Interconnects • Standards Convergence – P25 and IP- Migration to one open standard - Different mfr radios work together- Long term gradual change-out and upgrade at normal replacement times
Status and Direction • Radio Caches • Gateways • Interconnects • Standards Convergence Technology Status- Detailed Engineering work funded w/ ’06- Engineering Consultant – CTA – 11Sep07
Status and DirectionTRAINING & EXERCISE • Training and Exercises ID’d in SCIP • Training Plan, Materials Development funded w/ ’06 HSGP grant • Delivery of Statewide Training and Exercise program part of PSIC grant • PSIC T&E request : $1.1M over 3yrs
Public Safety Interoperable Communications (PSIC) Grant Status and Direction • ‘One-Shot’, one-time Grant for developing Interoperable Communications • Nevada allocated $12.1M (total nationwide $964M) • Three year performance period • Application just submitted 3Dec07 for DHS/NTIA Approval
Status and Direction Grant Summary for Interoperable Communications • HSGP FFY06 - $6.1M thru Jun09 • HSGP FFY07 - $3.0M thru Jun10 • PSIC one-shot - $12.1M thru Sep10
Thank you Questions? “Patience and perseverance have a magical effect before which difficulties disappear and obstacles vanish.” John Quincy Adams
Nevada Communication Interoperability PlanExisting Plan Overview Mark Blomstrom – Blomstrom Consulting, Inc. Las Vegas Urban Area Program Manager
Nevada Communication Interoperability Plan Existing Plan Overview This Overview: • Brief Background and Process • Existing Plan Contents – “NCIP” v.2 • Q&A Later: • New Draft Plan – “SCIP” v.3 • Opportunity for Input to v.3
Nevada Communication Interoperability Plan Existing Plan Overview Why is this important ? Strategy NCIP/SCIP PLAN Investment ‘06 ‘07 PSIC ‘08
Nevada Communication Interoperability Plan Existing Plan Overview Definitions: • NCIP : “Nevada Communication Interoperability Plan” – v.1, v.2 • SCIP : “State Communication Interoperability Plan” – v.3 • TIC Plan : “Tactical Interoperable Communications Plan”
The Beginning • 2 years in the making by the Nevada Communications Steering Committee (NCSC). • NCSC stakeholders representing northern & southern NV, rural & urban, & state, county and local governments. • Prompted by AB441 legislation. • Developed with assistance from the SAFECOM office of the Department of Homeland Security. • A living document revised as conditions change.
Who are Public Safety Agencies? • Fire Services • Law Enforcement • Emergency Management • Government Administrative Services • Emergency Medical Services • Public Health • Health Care • HazMat • Private Industry • Volunteer Organizations • Public Safety Communication • Public Works
Statement of Principles • NCSC encourages & maintains a governance structure emphasizing transparency, accountability and collaboration. • NCSC encourages comprehensive focus on key success factors – governance, SOPs, technology, training and exercises. • NCSC reviews research on best practices/ lessons learned. • NCSC not to be controlled by the State – must remain representative of entire NV public safety community.
Nevada Communication Interoperability Plan Existing Plan Overview - CONTENTS • Governance • Standard Operating Procedures (SOPs) • Technology • Training and Exercise
Tech Standard for P25 • To move towards long-term convergence, a technical protocol/standard must be adopted. • P25 is an open system, developed nationally for over 15 years. • P25 establishes a common protocol, allowing radios from different vendors to effectively communicate. • P25 does not address radios operating in different frequency bands or issues such as standard operating procedures.
P25 Recommendations • Long–range plan includes long-term convergence of all radios within the state to digital, open standards technology, implementing current version of P25. • A phase-in timetable will be used. • Exemptions considered upon written notice showing good cause and approved by NV Homeland Security Commission.
Assumptions • “Capable” is defined as the ability to be quickly upgraded via the loading of a software program to actual P25 Common Air Interface operation. • “Capable” in this context does not mean the equipment must actually operating in P25 mode when purchased, rather that it be “capable” of simple upgrade to such operational mode at a future time. • In every case where purchase of P25 capability is mandated, the equipment is for capability to accommodate the most recently approved version of the P25 standard.