Worst ever fire season in BC was 2003 with 2500 fires Fires destroyed 334 structures and evacuated 45,000 people Three pilots lost their lives in.

Slides:



Advertisements
Similar presentations
Author: Thomas Maloney Near-Miss 24/7/365 Safety Calendar February 2009 Incident Command.
Advertisements

National Emergency Communications Plan Demonstrating Goal 2 By 2011, 75 percent of non-UASI jurisdictions are able to demonstrate response-level emergency.
Incident Command System
North Carolina Deployable Communication Assets
National Incident Management System Overview Briefing Fiscal Year (FY) 2006 Implementation.
Visual 3.1 Unified Command Unit 3: Unified Command.
Visual 3.1 Unified Command Unit 3: Unified Command.
Nebraska Interoperability: First Responder Webinar – July 26, 2011 Audio: Conference Number(s): Participant Code:
IS 700.a NIMS An Introduction. The NIMS Mandate HSPD-5 requires all Federal departments and agencies to: Adopt and use NIMS in incident management programs.
1 Executive Office of Public Safety. 2 National Incident Management System.
FLORIDA LAYERED PACKET NETWORK NETWORK STATUS AND RADIO MESSAGE SERVER SUPPORT Presented to N. FL. ARRL Section Meeting HamCation February 14, 2009 Orlando,
National Incident Management System
Mutual Aid and Interoperability CTC Presentation February 23, 2006 Chuck Miller Office of Enterprise Policy & Planning.
Nevada Communication Interoperability Plan Overview Developed by Nevada Communications Steering Committee Version 2.0 – Adopted April 6, 2006.
Incident Command System Basic Course
Disaster Communications System (DCS) Overview for State and Local Governments National Conference on Emergency Communications (NCEC) Panel 5: State and.
National Incident Management System Introduction and Overview NIMS.
4 Incident Command System. 4 Objectives (1 of 2) Describe the characteristics of the incident command system (ICS). Explain the organization of the ICS.
The National Incident Management System. Homeland Security Presidential Directive 5 To prevent, prepare for, respond to, and recover from terrorist attacks,
National Incident Management System. Homeland Security Presidential Directive – 5 Directed the development of the National Incident Management System.
EASTERN MICHIGAN UNIVERSITY Continuity of Operations Planning (COOP)
California Common Operating Picture (Cal COP) for Public Safety
22 October The National Incident Management System, The Incident Command System, Our Served Agencies, and Wisconsin ARES/RACES Why it is we do some.
Incident Command System (ICS)
Nursing Home Incident Command System
1 Introduction to the Incident Command System for Amateur Radio Operators Sharon Kennedy, AC7UK City of Hillsboro Emergency Manager voice: (503)
National Incident Management System Break-Out Session Al Fluman, Acting Director Incident Management Systems Division (IMSD), National Integration Center.
Nevada Communication Interoperability Plan Overview Developed by Nevada Communications Steering Committee Version 2.0 – Adopted April 6, 2006.
Arlington County, Virginia RACES David Jordan Department of Technology Services Chief Information Security Officer OEM Technical Liaison, Emergency Support.
NIMS FOR HOSPITALS AND HEALTH CARE FACILITIES DHS and DHHS 12 Sep 06.
Visual 2.1 G191: ICS/EOC Interface Workshop Unit 2: Incident Command System (ICS) Review.
The Impact of Evolving IT Security Concerns On Cornell Information Technology Policy.
State of Florida Emergency Support Function 6 1 EMERGENCY SUPPORT FUNCTION 6 - MASS CARE & EMERGENCY ASSISTANCE “Training for incoming EMAC personnel”
Presenter’s Name June 17, eNATOA SAFECOM and Public Safety: a post 9/11 effort for local interoperability SAFECOM Overview Ken Fellman Mayor, Arvada,
National Incident Management System (NIMS)
Incident Communications Interoperability Strategy Illinois Terrorism Task Force Communications Committee.
Verizon Florida, LLC Hurricane Season Preparation PSC Workshop – May 1, 2008.
NATIONAL INCIDENT MANAGEMENT SYSTEM Department of Homeland Security Executive Office of Public Safety.
NIMS Nutshell in a NATIONAL INCIDENT MANAGEMENT SYSTEM (NIMS): AN INTRODUCTION 1-hour version, October 2011.
CBIZ RISK & ADVISORY SERVICES BUSINESS CONTINUITY PLANNING Developing a Readiness Strategy that Mitigates Risk and is Actionable and Easy to Implement.
The member organizations of the National Public Safety Telecommunications Council are grateful to the Department of Homeland Security's Science and Technology.
1 Brian Carney National RECC Coordinator Regional Emergency Communications Coordination Working Groups (RECCWG) National.
Introduction to the Emergency Operations Center City of Santa Cruz 2011 EOC Training and Exercise.
National Emergency Communications Plan Update National Association of Regulatory Utility Commissioners Winter Committee Meeting February 16, 2015 Ron Hewitt.
DHS/ODP OVERVIEW The Department of Homeland Security (DHS), Office for Domestic Preparedness (ODP) implements programs designed to enhance the preparedness.
Developing Local and Regional Incident Management Teams Bob Koenig Incident Management Team Coordinator Texas Forest Service.
Incident Management System (IMS). The Incident Management System is a means to organize both small and large incidents. It provides for a specific structure.
EOC-centric Radio Linking and Connectivity Exercise May 03, 2017 (0930 to 1530)
NATIONAL INCIDENT MANAGEMENT SYSTEM (NIMS)
California Deployment of the Next Generation Incident Command System (NICS) as Situation Awareness & Collaboration Tool (SCOUT) Firescope Brief.
COOP Training, Testing, and Exercise (TT&E) Program January 30, 2014
National Emergency Communications Plan Goal 2
ARRL Field Organization for Emergency Communications
Incident Command System
2018 – 2020 Budget Presented by: Darryl Beaton
Indiana Department of Health
The COG “Cookbook” Course Lesson 1 - Introduction to COG Basics
The National Incident Management System
Continuity Guidance Circular Webinar
IS-700.A: National Incident Management System, An Introduction
Presented by: Chief Dave Dato Wauconda Fire Department
Mutual Aid Box Alarm System
Unit 6- IS 230 Fundamentals of Emergency Management
Interoperable Communications Technical Assistance Program
K9 Operations Leader (K9OL) Overview
Incident Communications Interoperability Strategy
Region 13 and the Healthcare Coalition of Southwestern PA
Emergency Telecommunications Cluster
Unified Command Unit 1.2.
Emergency & Crisis Management​ GROUP HSE RULE (CR-GR-HSE-701)
Presentation transcript:

Worst ever fire season in BC was 2003 with 2500 fires Fires destroyed 334 structures and evacuated 45,000 people Three pilots lost their lives in the line of duty Damages totaled $700 million 60+ fire departments responded plus 1000 forest firefighters Firestorm 2003 was a horrific event teaching many lessons. The 2004 government commissioned Filmon Report outlined the statistics and suggested action plans. To date, few of the key recommendations have been implemented – so much of the report content remains relevant to this day.

Specific to communications, we learned… Strategy for radio interoperability is required to link all responding agencies Existing radio systems were not expandable to manage load 60 fire departments responded, many use proprietary systems Some existing VHF channels could not be programmed into newer radios (W versus N-band) Some fire departments have inter-operable radios, but other F, P and A responders lack operational compatibility Amateur radio operators were invaluable but at times were an overlooked resource in the big picture No pre-plan for radio interoperability existed

Specific to AR communications, we learned… Emergency radio systems failed, but AR filled the gap in many instances AR not considered integral to emergency response system Involvement of AR was an after-thought in many cases AR was not assigned space in the EOC Filmon Report recommended… all EOC’s should include provision for AR operators including power / antenna space as needed. The AR systems should be regularly exercised as part of normal operations. AR = Amateur Radio

Based on the belief that a radio interoperability pre-plan is critical to the survivability of any community, action was needed to address building such a resource on Vancouver Island The Mid-Island Emergency Coordinators and Managers (MIECM) group embraced the notion of a radio interoperability pre-plan in September 2016 The plan is divided into both Amateur and Commercial The Multi-jurisdictional Radio Interoperability Project or MRIP is now at the deployment stage

Multijurisdictional Radio Interoperability Project Linking the MIECM and its operational partners V2.3CA dated March 24, 2017

MRIP - Operational Area

Project Vision Create an interoperable radio communication pre-plan within both the amateur and commercial spectrum to support the MIECM and its extended local jurisdiction emergency program partner activity through the development and implementation of a regionally-centric standardized approach to VHF & UHF radio frequency programming.  MIECM = Mid Island Emergency Coordinators and Managers (Vancouver Island)

What is ‘Interoperability’ BCEMS 2016 Ability of emergency personnel to communicate between jurisdictions, disciplines, and levels of government, using a variety of systems as needed and authorized. In the context of this definition, distinctions can be made between technical interoperability and functional interoperability Technical interoperability exists when two or more communications devices can send and receive information to and from each other. Functional interoperability exists when users have the leadership and support, standard operating procedures, technology, training, and regular usage to enable predictable and consistent communication. http://www2.gov.bc.ca/assets/gov/public-safety-and-emergency-services/emergency-preparedness-response-recovery/embc/bcems/bcems_guide_2016_final_fillable.pdf

MRIP – Key Objectives Develop a common amateur radio programming code-plug for all local jurisdictions to increase functional preparedness for mutual aid scenarios Develop an MIECM common use strategy for the EMBC frequencies Utilize the MIERCT to facilitate the data gathering, code-plug creation and ongoing data maintenance component of the project Develop an interoperability strategy for point-to- point EOC linking using either existing frequencies or a private trunked ‘fee for service’ radio initiative.

Emergency Communications Emergency communications typically consists of: Operability: the ability to establish and sustain communications in support of mission operations. Interoperability: the ability of emergency personnel to communicate between jurisdictions, disciplines, and levels of government, using a variety of systems, as needed and as authorized. Continuity of Communications: The ability of emergency response agencies to maintain communications in the event of damage to, or destruction of, the primary infrastructure. http://www.publicsafety.gc.ca/cnt/rsrcs/pblctns/ntrprblt-strtg/index-en.aspx

Communication Networks Each incident requires a communications plan (ICS205) which must reflect operational functionality to be effective and will include the following: Command Net: overall event control point linking supervisory personnel from Incident Commander down to and including division and group supervisors. Tactical Nets: site specific traffic established by agency, department, geographical area, or function for each branch, or for divisions and groups, depending upon hardware and frequency availability, and specific incident needs.

MIECM communication challenge Multi-jurisdictional area with no radio interoperability plan No pre-plan initiative to address mutual aid support No plan to coordinate radio resources during a large scale event or mutual aid scenario No common radio technology platform vision Massive volume of operational frequency data in both the amateur and commercial spectrum Multiple 911 service providers throughout the area Relocation of resources in a large scale event face immediate communication challenge arriving onsite Implementation of EMBC (VHF) frequencies is unknown

The work that needs to be done… Work required on the following initiatives: Creation of a multi-jurisdictional radio interoperability plan Standardization of a common radio technology platform Collect local jurisdictional radio frequency data within both the amateur and commercial spectrum (including SAR) Universal implementation of EMBC (VHF) frequencies Common use approach to utilization of EMBC frequencies Development of common radio code-plug throughout MIECM Development of radio programming update strategy Generate and share LOA for emergency use of existing (commercial) frequencies to support mutual aid scenarios

Island Communication radio sites Port Hardy Newcastle This private VHF / UHF radio network serves most Vancouver Island communities. Currently standalone nodes, but the vendor is planning to link all sites in the near future which has the potential to create an EOC-to-EOC interoperable commercial radio network for the MIECM and its local jurisdiction partners Washington Cokely Benson Ozzard Bruce

2017 Radio test scenarios #1: MIERCT will test point-to-point connectivity from Bamfield through Mt. Ozzard to both Port Alberni and Parksville EOC’s via the Mt. Arrowsmith repeater site.  This test very successful test took place on Thursday, February 09, 2017 Port Hardy Newcastle Washington Cokely #2: In advance of an Island Communications ‘fee for service’ trunked EOC connectivity model, inter-EOC testing will be conducted using commercial radio frequencies to determine viability in support of mutual aid scenarios. This test (Bamfield to Ozzard to both Port Alberni and Parksville EOC’s via the Mt. Cokely repeater site) has been discussed with the service provider and is awaiting local budget approval. Benson Ozzard Bruce

Linked (commercial) radio network High level radio sites create a robust network Standalone sites are good, but linked sites are even better Linked sites enable a private trunked network to evolve Network owner is planning to link all their radio sites Access would link all the MIECM partners Low monthly cost per radio plus annual ISED licence fee Many of our agency partners use this type of network to span the province on a daily basis

Common radio technology Vertex VX-4600 has been selected for the project Radio is ISED (aka IC) type approved Full spectrum (136 – 174 MHz) 50W VHF and (400 – 470 MHz) UHF 45W radio 512 channels / 32 zones User friendly software programmable Robust commercial feature set + 3 year warranty Dedicated 15-pin D-Sub rear port connector for TNC

Vertex VX-4600 VHF & UHF 15-pin rear port to connect TNC VHF UHF

CVRD (MRIP) Amateur Radio Kit

CVRD (MRIP) Amateur Radio Kit

CVRD (MRIP) Amateur Radio Kit

Value to local jurisdictions… Interoperability plan established before large scale event Common radio strategy for all partners / jurisdictions Creation of radio asset inventory for advance planning Agreement to openly share radio frequency information Implementation of common radio code-plug programming

Next steps… Approval in principle of the interoperability concept  Investigate implementation of linked radio network  Approval in principle to utilize common radio platform  Support for gathering radio frequency data in each area Support for common approach to EMBC frequencies  MIERCT committee would coordinate data gathering  MIERCT members would create base code plug Presentation of the base code plug to MIECM for approval Development of common use strategy  Program and deploy a VHF / UHF radio test package  Next steps with network owner (underway)

MRIP Contact For MRIP details, please contact: Paul B. Peters Emergency Telecommunications Coordinator Public Safety Division, Community Services Department Cowichan Valley Regional District 175 Ingram Street, Duncan, BC V9L 1N8 E-mail:  radio@cvrd.bc.ca Telephone:  250.715.6618