Achieving an Operational Office of Water Enterprise Architecture: FY2006-2007 Roadmap November 23, 2005 Achieving an Operational Office of Water Enterprise Architecture: FY2006-2007 Roadmap 11/23/05

Outline Overall Message Current Situation FY 2006 and 2007 Plans: Phase 1 – Baseline “As Is” Data Modeling Phase 2 – Strategic Planning and Target (“To Be”) Data Modeling Phase 3 – Alignment of Data Architecture with Enterprise Architecture Phase 4 – Implementation of Architecture Decision Tools and Plans Challenges Cross-EPA Coordination Achieving an Operational Office of Water Enterprise Architecture: FY2006-2007 Roadmap 11/23/05

Message OW has made achieving an operational enterprise architecture (EA) a top strategic priority Done through adoption of Goals/Action Plans by the OW ISC EA development will be done in conjunction and parallel with the EPA strategic planning process Modeling is at a conceptual level to facilitate movement from baseline (“as is”) to target (“to be”) architectures Schedule is anticipated for 18 months in four distinct phases Achieving an Operational Office of Water Enterprise Architecture: FY2006-2007 Roadmap 11/23/05

Deliverable/Achievement Phased Approach Phase Time Frame Deliverable/Achievement 1 – Baseline (“As Is”) Data Modeling Through April 2006 Baseline (“as is”) conceptual data entity model in Metis showing data similarities among 37 OW systems 2 – Strategic Planning and Target (“To Be”) Data Modeling Through September 2006 Target (“to be”) conceptual data model reflecting data consolidations, developed in parallel with OW IRM Strategic Plan 3 – Alignment of Data Architecture with Enterprise Architecture In time for Input into BY2008 CPIC Process Full Alignment of Target Data Architecture with OW EA, relating applications and data to business processes and strategy 4 – Implementation of Architecture Decision Tools and Plans Through September 2007 Use of architecture tools to align and monitor investments with target (“to be”) plans in upcoming CPIC phases Achieving an Operational Office of Water Enterprise Architecture: FY2006-2007 Roadmap 11/23/05

Phase 1 – Baseline (“As Is”) Data Modeling 37 systems to be modeled 15 systems have “monitoring” data commonality, a potential aggregation environment Current activities are building on strategic plan and work done starting in 2000 OW will model in Metis (ART) in concert with system owners Baseline (“as is”) data modeling will identify major entities and relationships at a conceptual level, facilitating opportunities for optimization Achieving an Operational Office of Water Enterprise Architecture: FY2006-2007 Roadmap 11/23/05

Phase 2 – Strategic Planning and Target (“To Be”) Data Modeling OW IRM Strategic Plan will be done in conjunction and parallel with target (“to be”) data architecture development ISC will use baseline (“as is”) results as a foundation for developing the OW target (“to be”) data model Results will identify opportunities and strategies for data integration and warehousing (e.g., integration of EPA water monitoring data) Achieving an Operational Office of Water Enterprise Architecture: FY2006-2007 Roadmap 11/23/05

Phase 3 – Alignment of Data Architecture with Enterprise Architecture OW data architecture will be aligned with enterprise architecture, and will illustrate how OW applications and data support business processes and strategy An initial use of this alignment will be to inform the BY2008 CPIC process to streamline processes and applications This effort will provide concrete tools (i.e., through ART) for portfolio managers to make informed investment decisions ART should be completely capable of supporting OW portfolio managers by BY2009 Achieving an Operational Office of Water Enterprise Architecture: FY2006-2007 Roadmap 11/23/05

Phase 4 – Implementation of Architecture Decision Tools and Plans Target architecture guides the reengineering of business processes and consolidation of applications/infrastructure to maximize efficiency OW will continually evaluate target architecture based on implementations, fostering innovation in meeting EPA business needs Were this environment present, more immediate response to events like Hurricane Katrina would be possible Implementation will yield clearer understanding of how leveraging information across the Federal government can occur Achieving an Operational Office of Water Enterprise Architecture: FY2006-2007 Roadmap 11/23/05

Challenges Challenge: Information knowledge repository is not complete The outcome of the modeling process will provide this repository Challenge: Maintenance of the ISC management construct The ISC management construct provides a consensus model necessary to the culture of the organization Challenge: Managing by portfolio using the target architecture Our objective is to achieve this for CPIC in BY2008 Achieving an Operational Office of Water Enterprise Architecture: FY2006-2007 Roadmap 11/23/05

Inter-Governmental Collaboration OW has evaluated OPPT and OSWER activities and has drawn lessons learned from them (e.g., prioritization of monitoring data, focusing on well understood segments) OW will work in partnership with OEI to achieve corporate level consistency OW relies on OEI to provide leadership on data management and standards OW will make lessons learned from this effort transparent and readily available Achieving an Operational Office of Water Enterprise Architecture: FY2006-2007 Roadmap 11/23/05