Arc Hydro in Florida SFWMD Arc Hydro Developments

Arc Hydro in Florida SFWMD Arc Hydro Developments Date: November 4, 2005

Topics n Arc Hydro Implementation Scope and Approach Project Management Approach n Current Arc Hydro Pilot Efforts n Process Framework n Discussion & Next Steps n

Implementation Scope & Approach

Arc Hydro for South Florida Hydroperiod Estimation Enhanced Arc Hydro Framework for South Florida Operations Decision Support System Existing Arc Hydro Framework Regional Simulation Model Flood Hydrology & Hydraulics

Arc Hydro Enhanced Database (AHED) • Implement Water Control Units in geodatabase • Structures • Waterbody subtypes • Waterbody Canal. Segments • Multiple inflows/outflows for catchments and waterbodies • Links to time series sources • Data structure to support multiple scales; project indexing • Record level metadata

Project Management Approach

SFWMD – Project Management Framework Components n n n n Use a prototype-to-pilot-to-production approach Engage IT Work Intake process Assign Project Sponsors Establish formal Project Charter and Project Management Plan prior to engaging work Utilize Project Management Institute (PMI) principles Receive formal approval from CIO with IT Steering Committee (advisory body) support Execute project plan with an established System Development Life Cycle (SDLC) Provide consistent status reporting and performance metrics

Work Stream Approach n Arc Hydro Implementation is comprised of 4 distinct, inter-dependent work streams n Work Stream 1 – Implement AHED Pilot Work Stream 2 – AHED Data Preparation n Work Stream 3 – Maintain Alignment w/ Project Level Tasks n Work Stream 4 – Enterprise Implementation n

Work Stream Release Plan FY 05 1 Q 2 Q FY 06 3 Q 4 Q WS 1 - Pilot Jan 1 Q 2 Q 3 Q FY 07 4 Q 1 Q 3 Q 4 Q Dec - design complete - data validation testing D 1 WS 2 – Data Preparation D 2 Jul Sep Dec Mar R 1 R 2 R 3 R 4 Jan Aug - work stream release D 4 Apr WS 4 – Enterprise Rollout - dependency milestone D 3 Jun - negotiate vendor contract - release package 2 Q Jan Apr Jul

Arc Hydro Pilot Effort

Arc Hydro Pilot Components Populating the pilot dataset n Development and deployment of five pilot tools n Process development n Process Framework design n Process definition n Template and form design n Team formation n Process implementation n

Arc Hydro Pilot Delivery Plan FY 06 JUL Feature Relationship Builder AUG SEP OCT NOV DEC JAN FEB MAR 9. 13 Metadata Maintenance H&H Watershed Atlas 10. 14 11. 21 Water Quality Tool 12. 23 Rainfall by Watershed Pilot Dataset Population * Each effort includes development, test, deployment, and training tasks. 2. 8 11. 23 APR

Arc Hydro Pilot Process Design & Implementation

Key Components of our Process Definition Efforts Use existing processes where available n Engage a collaborative design process involving key stakeholders n Identify and document those processes unique to maintaining an enterprise geodatabase n Build work intake process to include AHED Steering Committee review and approval n Expect AHED Steering Committee prioritization of all requests against District wide needs n

Benefits of Process Framework n n n Maintain integrity of Enterprise Geographic Data Ensure most important work is addressed at District level Appropriately prioritize and assign Arc Hydro work requests Cross-functional awareness of high impact changes Ensure stable database environment for ever growing numbers of District users Coordinate concurrent editing efforts from multiple business units and projects

Process Definition Team Members Core Members and Role n Project Manager – Lakin Flowers n Database Owner – Maryam Mashayekhi n Database Admin – Ram Jadvani n System Admin – Tracie Streltzer n CERP – Michele Maierhofer n GIS Data Team Management – Tim Minter n GIS Data Team – Matt Hinton n HESM - Suelynn Dignard n HESM – Rachelle Grein n IT Helpdesk – Tony Vitani n n Data Stewards n Cindy Whelan – Water Supply n Bonnie Rose – Water Resources - Kissimmee n n Data Stewards n Yao Yan – ERA Water Quality n Terri Bennett – Operations Engineering Process Facilitator n IT Business Analyst – Stacey Greene

Process Framework

Key Processes n Umbrella Process n n Work Intake Major Processes n n n Add Modify Delete Records Schema Changes and Tool Development Infrastructure Upgrade Data Replication Project Data to AHED Outside Tool Integration n Sub Processes n n n Backup and Restore Promotion to Production Versioning Change Control Communications Historical Archive

Work Intake Process n Serves as the intake point for all Arc Hydro requests n Secures appropriate approvals before work activities begin n Prioritizes requests across all business units and projects Delivers an Impact and Level of Effort Assessment early in request delivery process n Interfaces with existing IT PMO, IT Steering Committee and Technical Review team processes n

Work Intake Process

Add / Modify / Delete Records See Appendix n n n n Content changes Features In Service Features Out Service Boundary Changes Minor Data Changes Adding New Features Mass Data Changes to Project Owned Shared Data Scenario: • Structure survey reveals a structure that has gone out of service • Operations needs to reclassify portions of Lake Okeechobee from Sub Type Marsh to Lake • A new canal is dredged and put into service • Aerial photography survey and analysis discovers that a canal segment’s vector data is off by a certain degree

Schema Changes and Tool Development See Appendix n n n New Tools Modifications to Existing Tools Data Schema Changes Feature Class Level Changes Mass Data Changes Scenario: • Water Quality wants a new report added to the Water Quality Load Tool • A new tool request is made to support a Water Supply project

Infrastructure Upgrade Software Upgrades n Oracle n Arc. GIS n Citrix Hardware Upgrades n Servers n PC’s See Appendix Scenario: • District upgrading to Arc. GIS v 9. 1 • Oracle Server upgrade

Data Replication See Appendix Includes: n Data Exported on a onetime or regular basis from AHED production to Project Database Does Not Include: n Data Steward requests for versioned database for edits Scenario: • Operations requests a recurring data extract for input into their Operational Decision Support System (ODSS) • Water Quality ERA requests a onetime data extract for preparation of the South Florida Environmental Report

Project Data to AHED Includes: n Data Imported on a one-time or regular basis from Project Database to AHED Production Scenario: • Operations has redefined and modified their boundaries for Water Control Catchments (WCC’s). New feature layer data needs to be uploaded to AHED.

Outside Tool Integration Includes: n The requested integration of tools developed for a Projects’ use by outside contractors n The modification of an existing AHED based tool by outside contractors See Appendix Scenario: • A District Project hires an internal contractor to develop a tool which will access the AHED database • A project has secured a contract with a consulting firm to develop an application as part of a larger project and would like to point it to the AHED database • The District would like to utilize a tool developed for another Water Management District

Promotion to Production n n Used by all Major processes that affect Production environment Builds in Quality Assurance points and activities Ensures appropriate communication between users and key staff Requires Metadata Maintenance Implements Change Control and Backup and Recovery processes

Versioning n n n Used by all data editing and schema change processes Provides data stewards with personal copies of AHED Geo. Database to edit records Reconciles outstanding versions into a Staging environment prior to Promotion to Production Ensures adequate backup and recovery plan before the integration of new or edited data Requires Record Level Metadata Maintenance

Other Sub-processes n Use Existing IT Processes n n n n User Account Management Backup and Restore Requests Archive Requests Communications IT Change Control Code Management via SERENA Designed by Arc Hydro Process team Metadata Maintenance n Processes specific to Pilot Tools n

Next Steps n n n n Complete Pilot Database population Look for alternatives to acquire additional District-wide datasets Complete delivery of pilot tools – allow business to use tools to drive out additional lessons-learned Finalize process elements n Resolve distributed Hydro. ID Management across the enterprise – finalize data replication processes n Cross-functional Feature class Boundary change consistency Form Arc Hydro governance teams n AHED Steering Committee, AHED Assessment Team Implement processes as standard operating procedures Maintain alignment with department-level Arc Hydro related activities