1. Oregon Watershed Emergency Response System (OWERS) Proposal Mason, Bruce & Girard (MB&G) Eugene Water & Electric Board (EWEB) City of Salem April 29, 2015

2. PrepareRespondStewardMonitor Oregon Watershed Emergency Response System

3. OWERS At A Glance Enterprise, web-based, GIS application View, search, create GIS data Real-time access to framework data, USGS gauges, spill time-of-travel, incident reports/updates Integrated photos and documents (equipment lists, geographic response plans, incident reports) Offline mobile tool for data access and collection Leverages investments made by OGIC, OEM, EWEB, City of Salem, DEQ, MB&G, NSWC

4. Expected Project Benefits Develop and enhance framework data Improved access to framework data Enable effective stewardship of framework data Help to protect drinking water and agricultural water sources for 367,000 people Enhanced communication between emergency responders and other support services Support development and maintenance of geographic response plans Statewide application, implemented in 2 key watersheds

5. McKenzie River 178,000 water users Recognized leader in watershed emergency response North Santiam River Salem 189,829 water users 6 other communities use surface water from the river ~ 3,000 acres within Santiam Water Control District (agricultural irrigation district) * Clackamas River Already expressed interest as 3 rd implementation ~300,000 water users * Project Area

6. Framework Data Develop framework data – Where not yet created, aggregated or available Enhance framework data – Where there are data are not yet complete, have quality issues Improved access to framework data – Expose data as secured web services to appropriate users – Easy-to-use interface Enable effective stewardship of framework data – Greater access increases ownership – Easy editing of OWERS specific data (response plans, incident updates, equipment lists, etc.) – Ability to submit proposed edits to framework data – Where appropriate, data managers update framework data

7. Framework Data – Selected Examples Enhance: Drinking water protection areas - verify and improve the location data for drinking water and agricultural source intakes in both project watersheds. Emergency facilities – all spill response equipment supply locations. Develop: Emergency reference data stations – hydrologic measurement devices (e.g., stream gauges, water quality sampling devices, etc.). Emergency service zones/ Public safety response areas - Operational areas specific to fire, police, sheriff, state police and EMS responders. Evacuation routes - Designated evacuation routes. Heliports - Locations designated for the take-off and landing of helicopters.

8. Framework Data - List ElementDevelopEnhanceElementDevelopEnhance drinking water protection areas xrecreation sitesx irrigation districtsx citiesx oil spill geographic response areasx dam facilities x water control districtsx emergency facilities x water improvement districtsx emergency reference data stationsx watershed council boundaries xemergency service zonesx public lands ownership xevacuation routesx state-owned lands xhazardous materials sitesx digital elevation models xhealth care facilities x elevation contoursx public safety response areasx slopex public safety station locationsx geology xstate police post boundariesx soils xwildfire-related facilitiesx flood zones xbridges x inundation areas xheliportsx landslide zones xmilepointsx hydrologic units (1st-6th fields) xmileposts x water bodies xrailroads x water body shorelines xroad centerlines x water points xwater supply watersheds x watercourses x

9. Team Organization

10. McKenzie Watershed Emergency Response Systems (MWERS) Goal: to provide first responders with the tools they need to avoid confusion and implement response actions to stabilize an incident within the initial hours of a spill or chemical release.

11. Existing System (MWERS) Desktop mapping that requires users to be familiar with GIS; cannot share data easily Older ArcIMS website that allows partners to update their contact information and equipment inventories, but does not include ability from desktop application to run time-of-travel and critical resource reports.

12. EWEB’s Commitment EWEB has been trying to find a way to redesign MWERS as an entirely web-based application EWEB has already collected required GIS data to support OWERS in the McKenzie EWEB understands process for developing watershed-based data plan Implementing a system with statewide transferability would benefit EWEB, utilities, and state and local agencies EWEB’s committed match: $50,000 for software development

13. Schedule Task NameDurationStartFinish Oregon Watershed Emergency Response System489 daysFri 7/10/15Wed 5/24/17 1.0 Project Management486 daysFri 7/10/15Fri 5/19/17 2.0 Data Development and Enhancement486 daysFri 7/10/15Fri 5/19/17 2.1 Develop Data Requirements and Data Plan30 daysFri 7/10/15Thu 8/20/15 Deliver Data Plan0 daysThu 8/20/15 2.2 Support EWEB in Data Development and Enhancement Activities120 daysFri 8/21/15Thu 2/4/16 2.3 Support City of Salem in Data Development and Enhancement Activities251 daysFri 10/2/15Fri 9/16/16 Publish and Update Data as Web Services426 daysFri 10/2/15Fri 5/19/17 3.0 OWERS Software Development181 daysFri 7/10/15Fri 3/18/16 3.1 OWERS Development Environment and Application Framework30 daysFri 7/10/15Thu 8/20/15 3.2 Finalize OWERS Requirements Documents30 daysFri 8/21/15Thu 10/1/15 3.3 OWERS Software Development100 daysMon 10/12/15Fri 2/26/16 3.4 Final OWERS Hardening and Documentation15 daysMon 2/29/16Fri 3/18/16 Deliver OWERS v1.0 and Documentation0 daysFri 3/18/16 4.0 Implementation and Deployment Support308 daysMon 3/21/16Wed 5/24/17 4.1 Develop Training Materials30 daysMon 3/21/16Fri 4/29/16 Perform EWEB OWERS Training0 daysWed 5/4/16 4.2 User Communication and Check Ins90 daysThu 5/5/16Wed 9/7/16 4.3 EWEB Deployment and Communication Systems272 daysThu 5/5/16Fri 5/19/17 Perform City of Salem OWERS Training0 daysWed 10/5/16 4.4 User Communication and Check Ins90 daysThu 10/6/16Wed 2/8/17 4.5 City of Salem Deployment and Communication Systems162 daysThu 10/6/16Fri 5/19/17 Wrap Up Communication Systems and Final Deliverables0 daysWed 5/24/17 Publish Final Data to Web Services0 daysWed 5/24/17

14. “Application Development may be a stretch for funding source” Total Project $138,754; Funding Request $78,754 (no flow model) MB&G $10,000 EWEB $50,000

15. “WHY NOT A RAPTOR EXTENSION?” Analysis, Modeling, Content Management, Data Maintenance Framework, Map Viewer Data Web Services OWERS RAPTOR Flex AGS REST WMS, RSS, etc. ArcSDE, etc.

16. FOCUS, TECHNOLOGY, FUNCTIONALITY Analysis, Modeling, Content Management, Data Maintenance Framework, Map Viewer Data Web Services RAPTOROWERS Flex JS PHP Flex JS AGS SOE AGS REST WMS, RSS, etc. ArcSDE, etc. ArcSDE photos, docs MISC. REST

17. Additional Questions?