siec meeting thursday, june 19, 2014

SIEC MEETINGTHURSDAY, JUNE 19, 2014

State of WashingtonState Interoperability Executive Committee

Agenda

Welcome and Introductionsa. Roll call and introductions

b. Review and modify agenda

c. Video interviews

d. Approval of April 17 Meeting Minutes

Washington State Patrol Narrowbanding Project Report

Robert SchwentWashington State Patrol

WSP Narrowbanding Project

Update to the Washington State Interoperability Executive CommitteeJune 19, 2014

WSP Districts

5

Project Overview

6

Within BudgetProject completion scheduled for November 3, 2015

P25 conventional mode• Operational in Districts 3, 4, and 5

700MHz trunking• Centered in WSP Districts 1 and 2• All equipment is installed and operational• Coverage testing has been completed and maps are being prepared

VHF trunking• IWN Interzone Link completed• Capacity study completed

Project Status

7

Activities and Schedule:

Dropdown menus on the consoles for conventional resources• Motorola has presented a solution to this issue which WSP has tested and

approved.Emergency channel marker

• WSP has the need to broadcast the channel marker on multiple sites over a wide area.

• Motorola has presented a solution to this issue which WSP has tested and approved.

Activities are focused in WSP District 2 (King County)• Dispatch consoles• 700MHz trunking cutover• P25 conventional conversion• Training, training, training!• Cutover scheduled for early September

District 3 implementation of trunking and console changes will follow District 2 cutover.

Project Status

8

Outstanding Issues:

Coverage complaints• WSP is addressing areas with poor coverage through system optimization and in

some cases additional base stations.Interoperability with VHF conventional users in trunked areas

• Several options are being explored. This requirement, and the proposed solution will vary based on the primary area of operation.

P25 conventional data operations.FCC Waiver extension

Project Status

9

Interoperability Efforts:

WSP and Spokane Regional Emergency Communication System (SRECS) developing an Advanced System Key (ASK) sharing agreement.

ASK sharing agreement and Inter-subsystem Interconnection (ISSI) agreement between WSP and South Sound 911 in progress. WSP is also partnering on SR410 simulcast VHF project.

WSP and Clark Regional Emergency Services Agency (CRESA) working on cross programming, backup dispatching capabilities, and microwave connectivity.

700MHz Interoperability repeater project in Seattle.

10

Questions?

Bob SchwentElectronic Services Division CommanderWashington State PatrolWashington Statewide Interoperability [email protected](360) 534-0601

mailto:[email protected]

SIEC Advisory Workgroup Report and

Rebanding Report

Jose Zuniga, Department of Corrections for

Michael Marusich

Communications Lessons from the SR530 Landslide

Bill Schrier

Introduction

Introduction• March 22, 2014 at 10:37 AM• Snohomish County, North Fork Stillaguamish River

• Forty-three deaths, 49 homes destroyed• Debris field over one square mile• Up to 750 responders involved

Communications Successes 1• SERS coverage• Snohomish DEM – 2 comms vehicles• 800 MHz ICALL – 8CALL use• Karl Wright of SERS• System Key-Sharing Agreement• Snohomish EOC: ACS 160 shifts• Alaska Shield Exercise – USAR & MERS• Local radio caches – 50 or so radios

Communications Successes 2• MERS Cache – 200 - 800 MHz radios• DNR experienced Type II IMT activated • Search-and-rescue, esp. dogs• Cross-band Aircraft link; Port of Seattle• WSP and WSDOT normal operations

Lessons Learned - 1• Regional 800 MHz Operational Zones• Multiple radios – BK and Motorola• List of COML and COMT u• COML, COMT, AUXCOM training u• COML, COMT, AUXCOM certification u• COML “wildfire” and “all hazards”• 911 re-route• Time to Mobilize

Lessons Learned - 2• Increase radio caches?• Cache programming – FEMA vs Local• Inventory communications vehicles u• Create Field Operations Guide u• Prepare for volunteers• Train and Exercise for COMLs – annually? u

• Other?

Department of Natural Resources Radio Systems

Briefing

Anton DammCommunications Systems Director

2014 DNR Radio Systems Briefing

Supporting the wildland fire mission

• Conventional VHF narrowband land mobile radio• 53 Communication Sites, approximately 50% on DNR managed land• 83 Base Stations / Repeaters• 1,500 Portable Radios• 1,100 Mobile Radios• 7 Communication Centers (EOCs) – 2 are interagency with Federal

agencies• Staffing and equipment support for five Washington Incident Management Teams (Type 2) and staffing for national incident response through NWCG

Highly interoperable in wildland fire

● National Wildfire Coordinating Group (NWCG) approved portable radios and repeaters

● 2 Interagency (USFS/DOI/DNR) communication centers, co-located radios and frequency sharing between partners

● Initial attack agreements (including frequency use) with most County Fire Districts

● National emergency frequency coordination during wildland fire operations

Interagency Business Cooperation

DNR cooperates and shares resources between state, county and local agencies:● Subscriber maintenance for Washington State Parks● “State Repeater” maintenance for Washington DFW● DNR uses 3 segments of WSP Microwave backhaul -

more planned● Joint effort with WSP to solve digital coverage

issues● Multiple frequency, site and tower sharing

agreements with WSP, counties and municipalities

ESINet (Statewide 911) Outage of April 10, 2014

Sigfred “Ziggy” Dahl

27

WA STATE E911 OFFICE

ESInet Outage of 04.10.2014Agenda

• Timeline

• Terminology to be used - Analogies

• What was supposed to happen

• What (actually) happened

• What steps have been taken (to prevent similar occurrence)

• Observations

28


ESInet Outage of 04.10.2014Timeline (Sequence of events):

• Approximately 23:50 (9 April) our 911 Outage sequence begins *

• Approximately 01:55 (10 April) State Emergency Operations Center initiates call to SECO stating that ‘something unusual is happening with 911

• Various PSAPs around the state start to get calls from citizens reporting they ‘can’t get through on 911’ … begin to run their normal outage protocols

• Approximately 06:30-07:00 (10 April) PSAPs begin to report 911 working again

• Total time of Outage: Officially Reported to be 6 hours, 12 Minutes

• Total Number of affected 911 attempts: approximately 4300 in Washington State

• 2 Counties (Garfield and Skamania) reported no issues

29


EO

LNG IP-SR

PGM

ACD

Analog TDM IP IP

CAMA

PSAP

911Caller 911

Call Takers

• 911 Caller• End Office (EO)• Legacy Network Gateway (LNG)• IP – Selective Router • PSAP• Call Taker

THE PLAYERS:

30


WHAT WAS SUPPOSED TO HAPPEN:

• Caller dials 911• LNG• IP-SR • PSAP (PGM)

EO

LNG

PGM

ACD

Analog TDM IP IP

CAMA

PSAP

911Caller 911

Call Takers

IP-SR

Miami

IP-SR

Englewood

31


EO

LNG

PGM

ACD

Analog TDM IP IP

CAMA

PSAP

911Caller 911

Call Takers

WHAT DID HAPPEN:

CALLS FAIL

I’m OK

• 911 call arrived at LNG that had Englewood (IP-SR) as Primary• Call arrived at Englewood IP-SR• Eventually (seconds) the call leg between the LNG and the IP-SR timed out and

caller was provided with either “busy”, “ringback” or “fast busy” • BECAUSE the IP-SR did not realize it was failing (or had failed), it kept sending

messages (heartbeats) to the LNG that it was OK.• Once problem was determined, LNGs were manually instructed to send traffic

only to Miami

IP-SR

Englewood

IP-SR

Miami

32


WHAT STEPS HAVE BEEN TAKEN:

EO

LNG

PGM

ACD

Analog TDM IP IP

CAMA

PSAP

911Caller 911

Call Takers

• Short-term• Medium-Term• Long-term

IP-SR

Englewood

IP-SR

Miami

33


OBSERVATIONS:

EO

LNG

PGM

ACD

Analog TDM IP IP

CAMA

PSAP

911Caller 911

Call Takers

• Why did some calls continue to go through?• Why did the PAD seem to work for some PSAPs and not others?• Why did the 10-Digit PSTN number work?• Why did calls from some PBXs continue to go through?

IP-SR

Englewood

IP-SR

Miami

34


911Caller

911Call Takers

QUESTIONS?

Sigfred “Ziggy” DahlState E911 Coordinator

WA Military DepartmentEmergency Management Division

[email protected]

mailto:[email protected]

Washington OneNet (WON) Status

Bill SchrierShelley Westall

Brief WON Updates• Washington OneNet and FirstNet• Website: ocio.wa.gov/onenet• Twitter: twitter.com/waonenet• Blogs upcoming• Staffing• Subcontracting:

• public entities (cities, counties, fire dist.)• utilities, private utilities, transit• tribal nations

Timelines• April 30: FirstNet publishes checklist• June 3: Washington submits (#5 of 56)• August 13-14: Proposed stakeholder & technical committees kickoff

• October 16: SIEC + FirstNet + SCIP Kickoff

• Oct 2014 – 2015?: Design FirstNet WA• Early 2016?: Design final & to Governor

Washington OneNet (WON)

http://ocio.wa.gov\[email protected]

http://ocio.wa.gov/onenet

WON Initial Consultation Checklist Update

Thursday, June 19, 2014 State Interoperability Executive Committee

Checklist Requirements

• Governance Body• Governing Documentation

• Authorization (RCW, executive order)• By-Laws

• Membership List• Organizational Chart• Photos & Bios• Narrative of decision making process


Washington State Governance

Structure


Proposed Attendees:


Additional Attendees:

Suggestions for attendees?


Consultation Scheduling – Proposed

• Requested date: Thursday, October 16, 2014• Proposed alternate dates:

Thursday, October 9, 2014Thursday, October 23,

2014


Additional checklist items:

• Wireless Contract Vehicles• Outreach Plan• Potential Barriers –

. . With regard to specific legal barriers that may impede our ability to participate fully in the consultation process, without detailed information on the opt-in requirements we can only speculate on barriers. However, significant budget and legislative barriers may exist if the Governor is required to commit to funding. Additionally, with several potential user agencies under the direction of separately elected officials, there may be some barriers to their participation as well as questions about the Governor’s ability to “opt-in” for those agencies.


Consultation Meeting Discussion Topics

• Governance Process• Metropolitan / Rural / Tribal POCs• Eligible Users• Coverage• Public Safety Stakeholders• Public Safety Meetings & Events• Major State Events• State Specific Information


Initial Consultation Meeting Proposed

Agenda• Introductions• State Update• FirstNet Update• Consultation Process• Roles & Responsibilities• Eligible Users• Coverage• Joint Outreach Planning• Next Steps

SIEC Workplan and Task List

Bill Schrier

Budget Subcommittee• Shawn Berry, WSP • Bill Legg, WSDOT• Albert Kassell, DNR• Bill Schrier, OCIO• Jim Semmens, Gambling Commission• Jose Zuniga or designee, Corrections

Staff:• Robert Schwent, WSP and SWIC• Michael Marusich, OCIO, alternate SWIC

Topics: Budget Subcommittee• SWIC Staffing • SIEC Staffing – frequency coordination• COML/COMT/AUXCOMM lists, training, certification, exercises, meetings

• Field Operations Guides (FOG)• Statewide Communications Interoperability Plan (SCIP) and NECP

• Work with locals to prepare comms for next disaster, major incidents

Upcoming Items• WSDOT Radio Systems Briefing• PSERN (King County proposed network) Briefing, support - August

• FirstNet Kickoff – October• Consolidation Report Dispatch Centers review

• Interagency comms cooperation• Proposed FY 15-17 budget

Good of the OrderNext Meeting: August 21

Bill Schrier

siec meeting thursday, june 19, 2014

Documents

vhf conventional users

conventional resourcesmotorola

vhf project

p25 conventional data

implementation of trunking

introduction page

sharing agreement

system optimization