1. Bringing EEW to the West Coast
Jennifer Strauss

2. EEW 101

3. Point of this conversation is not to induce anxiety about imminent earthquake attacks, but rather to put the problem into the context of our plan. Buildings in California are, thankfully, much more robust than they were back then. We have coordination between important lifelines in many cities and understand their importance for resiliency. And earthquake early warning has come a long way since the musings of a doctor about a telegraph line.

4. Value-added & Redistribution Services
Partner Networks
RT data
Direct Users
Alert Streams
Sensors
Processing
Core System Partners
Public Alert Systems
(e.g., IPAWS)

5. ShakeAlert Joint Committee on Communication, Education & Outreach (JC-CEO)
Joint CEO Committee (CA, WA, OR, BC)
Coordinate Beta, Pilot, and CEO implementation
Social science R&D
Developing alert content
Messages (text, voice)
Sounds, signals, lights
Pre-event education and training
Integrate with other earthquake-related CEO programs.

6. ShakeAlert Roll-out Plan
Steps
Full Public Alerts
Geographically Limited Alerts
Expanded Alerts
Limited People
Automated Actions
Pilots
Pilots - selected fault tolerant use
Automated actions - wider industrial use, transportation
Limited people alerts - groups who can be trained
Expanded people alerts in public venues (no advance training)
Geographically limited public alerts (where network is dense)
Full public alerts via all available pathways

7. General User Needs Specific User Needs Fast reliable alerts Guidance
Alerts, funding, roadmap
Sense of Community
Specific User Needs
Magnitude, MMI, Maps
Depends on audience and alert distribution method
Application specific
General alerts may need less info than SCADA systems
Best Practices from other groups
Meat of the talk: what users want and what do we communicate to them

8. Lifelines coordination Code switching
Messaging
Part of emergency toolkit
System will not be perfect
Missed and false alerts
Estimations will not be perfect
M pretty good, MMI will be off
Not everything will benefit from EEW
Some of your ideas won’t work
Regulatory issues, cost
Lifelines coordination
Code switching
EM, scientists, public
Needs, wants, goals
There is no ‘one’ answer

9. CA Earthquake Early Warning
Ryan Arba
CA Governor’s Office of Emergency Services

10. Collaboration

11. What’s Been Done in CA 1980-2010: Research State Legislation:
Cal OES lead (SB 135)
Governance (SB 438)
Benefits Study completed
Business Plan
Startup Investment
FY 16-17: $10m
FY 18-19: $15m
FY 19-20: $16m (TBD)

13. Wireless Emergency Alert Test
Date: March 27, 2019
Location: Downtown Oakland
Objectives:
In partnership with USGS, test the network end to end, from the seismic laboratory to individual cellular phone handsets.
Measure the latency between test alert and receipt via survey designed in partnership by Cal OES and USGS
March 27, 11 a.m., Oakland, CA
Signal will originate from the test server in Pasadena, CA
Will travel through the FEMA IPAWS Gateway
Cell Phone towers will than transit the signal to a polygon in downtown Oakland
Measure the latency between test alert and receipt via survey

14. We Need You! Spread the word Download the app
Connect us to your organizations