1 / 52

SIEC Meeting Thursday, June 19, 2014

SIEC Meeting Thursday, June 19, 2014. State of Washington State Interoperability Executive Committee. Agenda. Welcome and Introductions a. Roll call and introductions b. Review and modify agenda c. Video interviews d. Approval of April 17 Meeting Minutes.

jered
Télécharger la présentation

SIEC Meeting Thursday, June 19, 2014

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SIEC MeetingThursday, June 19, 2014 State of Washington State Interoperability Executive Committee

  2. Agenda Welcome and Introductions a. Roll call and introductions b. Review and modify agenda c. Video interviews d. Approval of April 17 Meeting Minutes

  3. Washington State Patrol Narrowbanding Project ReportRobert SchwentWashington State Patrol

  4. WSP Narrowbanding Project Update to the Washington State Interoperability Executive Committee June 19, 2014

  5. WSP Districts

  6. Project Overview • Within Budget • Project 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

  7. Project Status • 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.

  8. Project Status • 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

  9. Project Status • 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 Schwent Electronic Services Division Commander Washington State Patrol Washington Statewide Interoperability Coordinator Robert.schwent@wsp.wa.gov (360) 534-0601

  11. SIEC Advisory Workgroup Report andRebanding ReportJose Zuniga, Department of Corrections for Michael Marusich

  12. Communications Lessons from the SR530 LandslideBill Schrier

  13. Introduction

  14. 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

  15. 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

  16. 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

  17. 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

  18. 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?

  19. Department of Natural Resources Radio Systems BriefingAnton DammCommunications Systems Director

  20. 2014 DNR Radio Systems Briefing

  21. 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

  22. 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

  23. 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

  24. ESINet (Statewide 911) Outage of April 10, 2014Sigfred “Ziggy” Dahl

  25. WA STATE E911 OFFICE ESInet Outage of 04.10.2014 • Agenda • Timeline • Terminology to be used - Analogies • What was supposed to happen • What (actually) happened • What steps have been taken (to prevent similar occurrence) • Observations 27

  26. WA STATE E911 OFFICE ESInet Outage of 04.10.2014 • Timeline (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 28

  27. WA STATE E911 OFFICE EO THE PLAYERS: ACD LNG PGM IP-SR 911 Caller 911 Call Takers IP Analog IP TDM CAMA • 911 Caller • End Office (EO) • Legacy Network Gateway (LNG) • IP – Selective Router • PSAP • Call Taker PSAP 29

  28. WA STATE E911 OFFICE EO WHAT WAS SUPPOSED TO HAPPEN: ACD LNG PGM IP-SR Englewood 911 Caller 911 Call Takers IP Analog IP TDM CAMA IP-SR Miami PSAP • Caller dials 911 • LNG • IP-SR • PSAP (PGM) 30

  29. WA STATE E911 OFFICE EO WHAT DID HAPPEN: ACD LNG PGM I’m OK IP-SR Englewood 911 Caller CALLS FAIL 911 Call Takers IP Analog IP TDM IP-SR Miami CAMA PSAP • 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 31

  30. WA STATE E911 OFFICE EO WHAT STEPS HAVE BEEN TAKEN: ACD LNG PGM 911 Caller 911 Call Takers IP-SR Englewood IP Analog IP TDM CAMA PSAP IP-SR Miami • Short-term • Medium-Term • Long-term 32

  31. WA STATE E911 OFFICE EO OBSERVATIONS: ACD LNG PGM IP-SR Englewood 911 Caller 911 Call Takers IP Analog IP TDM CAMA PSAP IP-SR Miami • 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? 33

  32. WA STATE E911 OFFICE QUESTIONS? 911 Call Takers 911 Caller Sigfred “Ziggy” Dahl State E911 Coordinator WA Military Department Emergency Management Division sigfred.dahl@mil.wa.gov 253-512-7468 34

  33. Washington OneNet (WON) StatusBill SchrierShelley Westall

  34. 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

  35. 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

  36. Washington OneNet (WON) http://ocio.wa.gov\onenet OneNet@ocio.wa.gov

  37. WON Initial Consultation Checklist Update

  38. Checklist Requirements • Governance Body • Governing Documentation • Authorization (RCW, executive order) • By-Laws • Membership List • Organizational Chart • Photos & Bios • Narrative of decision making process

  39. Washington State Governance Structure

  40. Proposed Attendees:

  41. Additional Attendees: Suggestions for attendees?

  42. Consultation Scheduling – Proposed • Requested date: Thursday, October 16, 2014 • Proposed alternate dates: Thursday, October 9, 2014 Thursday, October 23, 2014

  43. 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.

  44. 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

  45. Initial Consultation Meeting Proposed Agenda • Introductions • State Update • FirstNet Update • Consultation Process • Roles & Responsibilities • Eligible Users • Coverage • Joint Outreach Planning • Next Steps

  46. SIEC Workplan and Task ListBill Schrier

  47. 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

  48. 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

More Related