1. USGS ShakeCast Delivering Earthquake Shaking Data To The People Who Need It Philip A. Naecker Chief Scientist Gatekeeper Systems pan@gatekeeper.com

2. Gatekeeper Systems ShakeCast Features and Architecture– June 2003 Slide 2 ShakeCast Features and Architecture u Project Origins u Project Team u Issues with Current Delivery of ShakeMaps u Project Goals and ShakeCast System Goals u ShakeCast Terminology u ShakeCast Features and Functions u Prototype u V1.0 u Futures u ShakeCast Architecture u Protocols and Transport u Database u Development Environment

3. Gatekeeper Systems ShakeCast Features and Architecture– June 2003 Slide 3 Project Origins u Success of ShakeMap Project u ShakeMaps are data rich u Recurrent difficulties utilizing ShakeMaps u Consumers have had difficulty with network configuration, firewalls, and data processing u Each consumer wants a different configuration of feed, requiring “hand holding” and creating a maintenance morass u Missed opportunities for data utilization u Significant risk that information system fragility might impact successful application of ShakeMaps in a major event

4. Gatekeeper Systems ShakeCast Features and Architecture– June 2003 Slide 4 ShakeCast Project Team u What eventually became the ShakeCast Team has been in conversation about these issues since 1998 u USGS: Dave Wald and Bruce Worden u Peter German u Consulting geologist, seismic data processing expert u Creator of the CUBE system u Robert Nigbor u USC Professor u Long involvement in practical applications of shaking data (e.g., Intel)

5. Gatekeeper Systems ShakeCast Features and Architecture– June 2003 Slide 5 Software Development Expertise u Gatekeeper Systems u In business since 1993 selling software for utilities u Specialize in high performance, high availability systems for large database, GIS, and Internet applications u Customers include large utilities and municipalities City of LA, Santa Barbara, PacifiCorp, Las Vegas Valley Water District, Georgia Power, Contra Costa County, etc.

6. Gatekeeper Systems ShakeCast Features and Architecture– June 2003 Slide 6 ShakeCast Software Development Team u Bruce Worden – ShakeMap Software Development u Phil Naecker u Civil Engineer, 10 years as engineering consultant focused on water and wastewater utilities u Built large high performance data management systems for business and engineering applications since 1971 u Steve Caine u 45 years experience building software u Founded firm that sold critical software systems to DOD and related agencies for over thirty years u Internet and Open Systems Expert u Dave Burke u 25 years experience building software u Exceptional competence at building complex systems

7. Gatekeeper Systems ShakeCast Features and Architecture– June 2003 Slide 7 ShakeCast Problem and Solution u Current Problems u ShakeCast Solution

8. Current Delivery of ShakeMaps u Custom solution for each organization u Unknown failure modes u Not built by experts u Not built using latest Internet technologies u Difficult to implement and maintain u Significant work for USGS and consumer u Not conducive to adding new data products or technologies u Each organization has home-grown notification system (or none at all)

9. Gatekeeper Systems ShakeCast Features and Architecture– June 2003 Slide 9 EQ Systems 2002 Seismic Processing ShakeMap Processing Instrument Network Public/ Private Networks Private Networks Archives Users Akamai Servers Public Networks Consumer Information System Private Networks FTP over Public Networks

10. Goals: ShakeCast Project u Provide rapid and reliable delivery of information about earthquake shaking to the people who need it u Initial audience focuses on utilities, large facility owners, municipalities, and news outlets u “Shaking Information” is broadly defined u Satisfy some of the needs for post-event activities such as refinement of response plans and after-the-fact response assessment by accurately recording who knew what when u Deliver an open technology platform for earthquake information delivery that facility managers and the USGS can depend on and feel comfortable in building upon

11. Gatekeeper Systems ShakeCast Features and Architecture– June 2003 Slide 11 EQ Systems 2003 Seismic Processing ShakeMap Processing Instrument Network Public/ Private Networks Private Networks Archives Users Distribution System Event Notification System Akamai Servers Processing and Notification Public Networks Consumer Information System Private Networks ShakeCast

12. Gatekeeper Systems ShakeCast Features and Architecture– June 2003 Slide 12 Goals: Data Delivery and Notification u Delivery and Notification Must Be Extremely Reliable u Multiple data sources u Multiple data paths u Robust testing protocols u Set and Forget Design u Fast Under All Load Conditions u Essentially no training required for proper installation and maintenance

13. Gatekeeper Systems ShakeCast Features and Architecture– June 2003 Slide 13 Goals: Other System Attributes u Firewall Friendly u System Must Be Complete u Functional “Out of the Box” in a few hours u Deliver data and most commonly-used tools u Extensible and Flexible u Able to integrate with more advanced tools u Customizable by organizations and individual users u Traceable and Auditable u System and usage audit logs, consistent timestamps u Objective and reproducible notification actions

14. Gatekeeper Systems ShakeCast Features and Architecture– June 2003 Slide 14 ShakeCast Features and Functions u Phased rollout of features u Functions provide infrastructure, not enforce policy on how ShakeMaps are used u Reliability and robustness are designed in from the beginning

15. Gatekeeper Systems ShakeCast Features and Architecture– June 2003 Slide 15 ShakeCast Technology Plan u Open source using widely used tools u Apache, Perl, Oracle, Windows, Internet Explorer u Heavily documented code and databases u Based on commodity technologies: u Internet and Web u Email and SMS pagers u Relational databases u Security and reliability designed in from the start

16. Gatekeeper Systems ShakeCast Features and Architecture– June 2003 Slide 16 ShakeCast Project Phases u Phase 1 - Prototype u Phase 2 – Reference System u Phase 2 – Open Source

17. Gatekeeper Systems ShakeCast Features and Architecture– June 2003 Slide 17 ShakeCast Phase 1 - Prototype u Funded by USGS u Purposes are proof of concept, demonstration u Implemented by Gatekeeper Systems and Bruce Worden u Due Summer 2003 u CalTrans will be first testbed organization u SBC/PacBell anxious to be next testbed u Basic functionality, no easy installation or customization, single hardware/software platform

18. Gatekeeper Systems ShakeCast Features and Architecture– June 2003 Slide 18 ShakeCast Phase 2 – Reference System u Shopping for funding now u Fully installable (goal is one hour if the server already has a web server and database) u Easily configurable u Multiple hardware/software platforms u Looking for early adopters u Expect network of dozens to hundreds of systems and tens of thousands of end users

19. Gatekeeper Systems ShakeCast Features and Architecture– June 2003 Slide 19 ShakeCast Phase 3 – Open Source u Shared development between user organizations u Enhancements to core system u Participation by universities u Commercialization and Extension u Integration with internal systems u Improved data for shaking estimates u Readily available sources for fragility estimates u Hoping for thousands of systems and millions of end users

20. Gatekeeper Systems ShakeCast Features and Architecture– June 2003 Slide 20 ShakeCast Terminology u Server: every ShakeCast machine is a server u Upstream/Downstream: direction of data flow, although complex network topologies are allowed u Parameters: measures of shaking generated by ShakeMap system u Products: data files, in various formats and multiple parameters, moved between ShakeCast machines u Grid File: ShakeMap grids containing the raw parameter data u Notification: Detailed electronic message about a specific event, system activity, or shaking level to a specific user or group of users

21. Gatekeeper Systems ShakeCast Features and Architecture– June 2003 Slide 21 ShakeCast Software Features u Reliably and automatically receive and process shaking data from ShakeMap u Let organizations and users define locations of interest (facilities) and set shaking thresholds (green, yellow, red) in multiple shaking metrics (acceleration, instrumental intensity, etc.) u Reliably deliver to end users electronic notification of facility damage estimates in a prioritized, customized, easy-to-use form u Make maps and reports from local servers available via the Web u Easily integrate with consumer’s other IT systems u Provide for end-to-end testing and upgrades

22. Gatekeeper Systems ShakeCast Features and Architecture– June 2003 Slide 22 Prototype Features u Receive, store and forward ShakeMaps and associated metadata in a reliable manner u Unpack ShakeMap grids into a relational structure u Notify users of shaking and ShakeCast activity u Email and pager u System administrator, ShakeCast developer, and end user events u Produce detailed log files of ShakeCast and user activity

23. Gatekeeper Systems ShakeCast Features and Architecture– June 2003 Slide 23 Prototype Features - Transport u Receive from multiple upstream ShakeCast and ShakeMap servers u Versioned products u HTTP push or HTTP polling/pull u Can transport not only shaking data but system metadata: i.e. product types, message types, etc. u Basic filtering for ShakeMap feed u Bounding rectangle u Peak grid values u Retry and basic error handling u Basic test suites

24. Gatekeeper Systems ShakeCast Features and Architecture– June 2003 Slide 24 Prototype Features – Notification u On events: map generated, errors, recall/cancel, product delivery u On ShakeMap parameters: magnitude, acceleration, etc. u On location-specific shaking for any ShakeMap parameter u On exceedence of facility fragility for any ShakeMap parameter (green, yellow, red) u Message format driven by easily customized templates, includes direct Web links

25. Gatekeeper Systems ShakeCast Features and Architecture– June 2003 Slide 25 Prototype Features - Database u Most configuration information, all ShakeMap data, and all user data is stored in the database u Support for both Access and Oracle u Site administrator can access database using standard SQL and other standard tools such as MS Access, Visual Basic, Perl, etc.

26. Gatekeeper Systems ShakeCast Features and Architecture– June 2003 Slide 26 Additional V1.0 Features u Consolidated notification u Professional documentation u Complete installation procedure with upstream registration u User configuration web pages u Full support for both Unix and NT u Deliver ShakeMap web pages locally u Enhanced error handling u Enhanced test procedures u Call out from ShakeCast to private scripts to invoke site-specific functions u Automated end-to-end testing

27. Gatekeeper Systems ShakeCast Features and Architecture– June 2003 Slide 27 Features Futures u Richer notification options u Support for multiple related events u More intelligent prioritization of messages u More complicated notification logic u Support for positive response (confirmation) u Richer web links with active web pages to help users manage large lists of facilities u More database platforms certified u Open source shared development environment u Upstream reporting of ShakeCast usage, server health and status, and test results

28. Gatekeeper Systems ShakeCast Features and Architecture– June 2003 Slide 28 ShakeCast Implementation u Implementation Principles u Use open and familiar tools and protocols u Follow path of least resistance for network and security managers u Open, readable, understandable source code u HTTP and HTTPS transport u Relational database for all data storage u NT Service/Unix Daemon for event loop processing

29. Gatekeeper Systems ShakeCast Features and Architecture– June 2003 Slide 29 Software Development Environment u NT and Unix (but could be anything) u Perl for CGI (but could be anything) u Standard SQL (and optional SQL-based tools) u Source code management in CVS (Web-based source management system designed for shared development) u No C, VB, Java or compiled languages required, providing short development cycles, transparency, portability

30. ShakeCast System Data Flow ShakeCast Server ShakeCast Server ShakeCast Server ShakeCast Server GIS Systems Control Systems Alarm Systems Data and Invocation Email System Paging System Users Notification Messages Web Pages ShakeCast Data and XML USGS Systems Private Systems ShakeMap Server ShakeMap Server http smtp Email/ Pager Messages http ftp/NFS

31. Gatekeeper Systems ShakeCast Features and Architecture– June 2003 Slide 31 Protocols and Transport Architecture u HTTP CGI scripts for response to ShakeCast requests u ShakeCast metadata encoded in simple XML u HTTP GETs for file delivery u Can easily use HTTPS if needed u Authenticated server-server exchange: u MD5 secured passwords for authentication u Separate passwords for each server pair u New CGI routines can be easily added u Use Apache HTTP server, but could use others

32. Gatekeeper Systems ShakeCast Features and Architecture– June 2003 Slide 32 Database Architecture u Fully normalized data model u High cardinality transaction data can be purged if necessary u Shared data elements have shared primary keys u Locally-generated data elements have locally- generated primary keys u Multiple database platforms possible u MS Access and Oracle currently supported u Can easily be extended to use Oracle Spatial or other high-end database features

33. Gatekeeper Systems ShakeCast Features and Architecture– June 2003 Slide 33 Questions and Answers ? ? ? ?