page 1 siec meeting thursday, february 15, 2015 state of washington state interoperability executive...

40
Page 1 SIEC MEETING THURSDAY, FEBRUARY 15, 2015 State of Washington State Interoperability Executive Committee

Upload: clemence-peters

Post on 13-Dec-2015

214 views

Category:

Documents


1 download

TRANSCRIPT

Page 1

SIEC MEETINGTHURSDAY, FEBRUARY 15, 2015

State of Washington

State Interoperability Executive Committee

Page 2

Agenda

• Welcome and Introductions• News and Information Roundtable• Revisions to the RCW creating the SIEC• Puget Sound Emergency Radio Network (PSERN)

possible SIEC action• Status of Statewide Communications

Interoperability Plan (SCIP) Update• Communications Order Model Practice - possible

SIEC action• Washington OneNet Status• Ongoing Projects• Good of the Order

Page 5

Revisions to the RCW

• RCW 43.41A.080

• Alignment and consolidation of information

technology organizations in State Government• Consolidated Technology Services

• Portions of Dept. of Enterprise Services

• Office of the CIO

• Appointment and duties of the SIEC unchanged

• Responsibilities of the Chief Information Officer

• Budget and staffing

Page 6

Puget Sound Emergency (((Radio Network))) (PSERN)

Marlin BlizinskyKing County

7

Puget Sound Emergency (((Radio Network)))

(PSERN)State Interoperability Executive Committee

February 19, 2015

Substantially completed in 1997

254 user agencies

About 17,000 radios on system ◦ Approximately 78% used by first responders

Known coverage issues

8

Today’s System

Today’s Motorola Land Mobile Radio System is wearing out at same time we are losing system support◦ System is aging; increasing repairs ◦ Vendor stopping all sales of spare parts and all repairs

of used parts by Jan 01, 2019◦ Ability to keep system running smoothly is at risk

Doesn’t cover everywhere people live, work or play or everywhere responders must respond

Capacity is strained during major events

The Problem…

9

Over 4 years 27 meetings attended by over 150 users +

system managers Interviews Meetings with police and fire chiefs Policy (Steering) Committee – 4 co-owners Technical work

◦ Subcommittee◦ Alternatives analysis◦ Helped draft RFP◦ Training ◦ Consultation

Defining Requirements

10

Objective, measureable requirements-based RFP; testing

Separate scoring of plan and costs

Puget Sound Emergency Radio Network (PSERN) Project will build a new 800 MHz P25 Phase 2 land mobile radio system with connections to regional systems

Executive has proposed a 9 year levy lid lift, $.07 per $1,000 assessed value to fund

◦ Budget w/o financing = $246 million◦ Financing = $27 million◦ Total = $273 million

Proposed Solution

11

Coverage Bounded Areas

Scope of Project Reuse 18 sites, acquire 28 new sites, and

improvements at all 46 sites Design, purchase and installation of:

◦ Radio site equipment◦ Backhaul network equipment including microwave

radios/MPLS and some leased fiber ◦ End user radios for all public agencies◦ Dispatch center equipment

User migration and training Testing, testing, testing Project close out/KCERCS decommissioning

13

Comparison of Networks

14

Current Network(KCERCS)

Future Network(PSERN)

Coverage 94%Held in front of mouth

97%*

On hip

Measured Coverage Areas

1 Every city + 3 roads + Entire County

Sites 28 56

Channel Capacity 17 – 27 Urban4 – 7 Rural

30 Urban10 Rural

Redundancy Non-geographic Geographic

Interoperability Improved w WSPNew with Pierce

County

Standards Based No Partial

Enhanced Features No Some

Modelled Radio Coverage

New vendor contract – Dec. 2014

Funding measure proposed – Dec. 2014

Architecture & Engineering contract - Dec. 2014

Possible ballot measure – 2015

Final Design/Implementation – 2015-2018

Timeline

16

New non-profit formed to run PSERN – Early 2018

User Migration/System Acceptance – 2018-2019

Transfer of ownership to non-profit – Early 2019

Project close-out 2020

Timeline

17

Current: informal “Steering Committee”◦ Eastside Public Safety Communications Agency

(EPSCA) ◦ Valley Communications Center (ValleyCom)◦ Seattle◦ King County

Implementation period◦ Oversight by Joint Board

EPSCA cities, ValleyCom cities, Seattle, KC Unanimous voting

◦ KC is lead agency for contracting, funding, implementation, and testing

18

Governance

Post implementation◦ New non-profit organization

Own, operate, and govern PSERN Formed 1 year before network is completed

$750,000 in budget 4 Board Members: EPSCA cities, ValleyCom cities,

Seattle, KC Unanimous voting

19

Governance

www.psern.org

Follow us on Twitter @radiomatters

David Mendel, PSERN Project Director, 206-

263-7942, [email protected]

Marlin Blizinsky, Governmental Relations

Officer, 206-263-8047,

[email protected]

For More Information

20

Questions?

21

Page 22

PSERN – SIEC Action?

“The SIEC agrees that King County’s existing public safety emergency network is aging and will lose all vendor support in 2019.  This poses a significant risk of future failure.  The SIEC endorses the Puget Sound Emergency Radio Network (PSERN) replacement plan as presented at the SIEC’s February 19 meeting as consistent with the SIEC’s 2005 Technical Implementation Plan (TIP) and current policies specifically including the RCW’s P25 technical requirements, and as vitally necessary for the continued safety of responders and the public in King County.”

Page 24

SCIP Revision • Original SCIP 2007

• Update workshops:• August 13-14, 2014, in Spokane

• February 12 at SeaTac

• System of Systems Approach unchanged

• But: interoperability, avoid duplication

• Field Operations Guide – systems, frequencies

• Potential changes to SIEC – “champions”

• Communications Unit Leadership, Training

• Importance of wireless data - FirstNet

• LMR Systems List

• Further revisions in progress

Page 27Page 27

Page 28Page 28

Data Collection Guidelines

NEXT MONTH?

Page 29Page 29

Committees

Page 30Page 30

Stakeholder CommitteeDRAFT - Mission Statement: Stakeholder Committee

 

The Washington OneNet (WON) Stakeholder Committee is comprised of state, local, and tribal officials and leaders who are subject matter experts in how their agencies operate both in response to daily incidents and during disasters. The stakeholder committee shall provide input on public policy; regulatory impediments; and political, cultural, and economic opportunities and barriers. This group will help define and identify potential users and establish network prioritization.

 

The committee will provide input to the SIEC, OneNet, and FirstNet regarding matters related to the design of a statewide, wireless, broadband network dedicated to public safety. This input will result in a State Plan for FirstNet in Washington.

 

The Stakeholder Committee will consider factors such as:

coverage maps (existing and needed)

incident types and locations, e.g. crimes, fires, 911 calls, electrical power and water outages

devices and device form factors

device capabilities (e.g.. printing)

types of users to be allowed access to the network;

cost of service, devices, apps and other cost factors

phased build-out of the network

governance and management of the network, including provisioning and training of users, apps and devices

which apps should be available on the network and which apps might be standardized for statewide use

Page 31Page 31

Technical Committee

DRAFT - Mission Statement: Technical Committee

 

The Washington OneNet Technical Committee serves as the state’s subject matter experts to advise and assist with designing FirstNet in Washington, including technical details necessary to deploy, operate, and manage the network.

 

The technical committee is comprised of industry and technology professionals from local, state, and tribal entities as well as, professionals from compatible commercial industries with an understanding of systems data interoperability. In order to address all aspects of an interoperable, statewide network, the technical committee will work closely with the SIEC, OneNet, FirstNet’s local team, and the stakeholder and operational committees to build a State Plan for FirstNet in Washington.

 

The technical committee will provide input on and consider factors such as:

throughput and bandwidth in general and specifically as they relate to coverage.

interface specifications and standards for the network and for devices.

evolution roadmap of LTE and FirstNet in Washington.

technical details of priority management.

deployables which potentially bring additional coverage during major incidents or bring coverage in remote areas; this specifically includes the potential use of evolved packet cores in remote areas.

application performance, behavior and testing.

  

Page 32Page 32

OperationalDRAFT - Mission Statement: Operational Committee

 

The Operational Committee will explore and make recommendations to the SIEC regarding operational aspects of FirstNet’s dedicated Public Safety Wireless Broadband Network in Washington State.

The Committee will consider such issues as network management/prioritization during critical incidents and normal use; availability and use of multi-disciplinary applications on the network; establishing operational guidelines when interfacing with local, state, federal, and military entities; other topics that might be referred to the Committee to take advantage of the experience, background, and training of its members.

The composition of the Operational Committee is predicated on the rationale that any event that may create the need to prioritize network access would likely be of a significant, critical nature and involve more than one of the below listed functions.

Draft representation criteria:

• Persons who are or would be in a position to make decisions for their• respective entities in situations of competing interests

• Persons who have ICS and Unified Command training

• Persons who have background and experience with large scale and • or significant incidents

Page 33Page 33

Tribal OutreachFirstNet Regional Tribal Summit

Proposed: Affiliated Tribes of Northwest Indians (ATNI)February 2-5, 2015Lincoln City, OR

Joint Session: Washington, Oregon & IdahoPotential Agenda Items:a. A lot of unique challenges in Indian Countryb. Relationship of tribal law enforcement to outside law enforcement and data/information sharing or not?c. Do most tribes use outside fire departments and paramedics? How do those responders communicate with

tribal public health?d. Sharing of data - electronic health records - between outside responders and tribal public healthe. What is the relationship between tribal leaders/responders and outside 911? Data sharing there?f. Also think of all the unique health challenges in Indian communities.g. Other problems include smuggling and cross-border law enforcement issues.h. Fisheries - is there a public safety hook here?i. Expanded group of responders in some tribes: public works, transportation, utilities, e.g. Yakama and Colville.

Page 34Page 34

Tribal Outreach

• Upcoming meeting with the Kalispel Tribe – Airway Heights, WA• Identify opportunities to partner on tribal technology events where

FirstNet/OneNet can advance our common interests.

Page 35Page 35

SCIP UpdateFollow-up Meeting

February 12, 2015

The Conference Center at Seattle-Tacoma International Airport

Small group working sessionInput from larger groupDraft to SIEC for final approval and adoption

Page 36Page 36

WASPC Fall Training TrainingPotential Synergies between FirstNet and WASPC 2015 Legislative Agenda

Data Interoperability:

Body-Worn Cameras Advancements in technology now enable law enforcement agencies to equip their officers with body-worn cameras. Body-worn cameras offer additional information regarding interactions between law enforcement officers and the public. The current state of laws impede, rather than encourage, law enforcement’s use of this technology. WASPC will work with the Legislature to craft legislation that removes barriers to law enforcement agencies’ use of body-worn cameras.

Page 37

Update for Ongoing Projects

Page 38

SIEC Advisory Workgroup Committee Report

Michael MarusichOffice of the Chief Information Officer

Page 39

SIEC Advisory WorkgroupSAW Status Report as of February 10, 2015

Page 40

Washington State Patrol Narrowbanding Project Report

Robert SchwentWashington State Patrol

Page 41

Page 42

Page 43

800 MHz RebandingProject Report

Michael MarusichOffice of the Chief Information Officer

Page 44

Upcoming Items 

DateTBDTBD

 

April 18April 18

April 18  Early 2017

 

Future Agenda Topics• Final Report on April 10th E-911 Outage.• Recommendations and Action Plan from the Statewide

Comms Interoperability Planning (SCIP) Workshop (Aug 13-14) with follow up on February 12, 2015

• Follow-up on SR530 Landslide Recommendations• Communications Order Model practice for radio

communications.• Cybersecurity Briefing (EMD)• Review and recommendation to the Governor on the State

Plan for FirstNet 

Page 45

Good of the Order

Next Meeting: April 16, 2015

Location:Camp Murray, WA