1 EPA Enterprise Architecture Enterprise Architecture at the U.S. EPA Wendy Blake-Coleman

Enterprise Architecture at EPA2 Agenda  Context and History of EPA Enterprise Architecture  EPA’s Enterprise Architecture Framework  Geospatial Blueprint –Implementing the Goals

Enterprise Architecture at EPA3 National Environmental Information Exchange Network Integrated EPA Information Network l Position EPA as a Nat'l Network Node l Establish internal information network l Address emerging information needs l Build corporate information management Partner Support l Support States capacity to participate in network l Support collaborative State knowledge/ technology sharing l Work with other partners State/EPA Exchange Network l Help create, sustain, and grow the network l Establish interagency management function l Provide infrastructure support l Establish information exchange protocols EPA’s Information Integration Initiative Formalized the Need for an Enterprise Architecture

Enterprise Architecture at EPA4 Environmental Information Exchange Network An Internet and standards based method for exchanging environmental information between partners!  States – Data Stewards  EPA – Data User  Partnership & Collaboration between Governments

Enterprise Architecture at EPA5 State Node Implementation Process May 2005 CA OR WA ID MT WY CO NM TX AK HI OK KS SD ND MN IA WI IN OH KY TN MS AL GA FL NC WV PA NY DE CT NH RI IL MO AR LA NV UT AZ OR NM MS WV PA NJ MA NH MD DC VA MI NM SC NE VT ME In Development Operational FL Not Yet Started

Enterprise Architecture at EPA6 EPA’s Enterprise Architecture: FEAF-enhanced Framework

Enterprise Architecture at EPA7 Current EA Program Established Target and Sequencing Plan  Maturing governance processes, developing policy, procedures, and guidance materials  Technology Road Map  Developing Solutions Architecture  Customized Metis implementation –Architecture Repository Tool (ART)

Enterprise Architecture at EPA8 Sequencing Plan for Implementing the Architecture FY 2003 Exchange Network node development Limited infrastructure shared services available Central Data Exchange Geospatial Blueprint System of Registries (FRS, SRS) FY 2004 Application migration schedule Proof of Concept built for shared services (shared data dictionaries, portal, identity management, business warehouse environment, situational analysis, and capabilities tools) CPICs with specific costs and dates for migration PMO established FY 2005 Fully functional shared services with program pilot FY 2006 Begin Full Migration to Target

Enterprise Architecture at EPA9 EPA Metadata Architecture – Existing Structure 9

Enterprise Architecture at EPA10 Geospatial Blueprint: EPA’s Geospatial EA Component

Enterprise Architecture at EPA11 Business Services Requiring Geospatial Analysis National Program Managers  Protecting drinking water supplies  Conducting analyses to help manage urban/suburban growth  Responding to oil spills and other emergency situations  Identifying sources of pollution for source water protection  Examining and allocating regional acid precipitation allowances  Conducting risk assessments  Analyzing health conditions against pollutant distribution  Modeling the distributions of invasive species  Identifying priority sites for cleanup and enforcement actions Research and Science  Conducting habitat assessments and risk analyses  Detecting and evaluating landscape patterns and changes  Conducting real-time environmental monitoring and sharing the data with appropriate partners  Studying the effects of urbanization, at various scales  Developing accuracy assessment protocols  Creating 3-D visualizations of specific sites or larger geographic areas  Analyzing the relationship between health and environmental contaminants Regional Offices Developing Total Maximum Daily Load (TMDL) assessments for water bodies Tracking toxic substances Cleaning up and monitoring Superfund sites Monitoring water quality Assessing children’s health Analyzing environmental justice situations Cleaning up hazardous waste sites Conducting environmental justice assessments Evaluating air emissions and ambient air concentrations Modeling watersheds and storm water drainage systems

Enterprise Architecture at EPA12 Geospatial Requirements: Business Architecture Goal 1: Improve EPA decision making by incorporating location based approaches, data, tools and knowledge into EPA business processes. Current Efforts include :  Inserting Location-Based analysis into our business workflow  Outreach to Program Managers  Solutions Architecture Guidance to Map Geospatial Components

Enterprise Architecture at EPA13 Digitize Project Location

Enterprise Architecture at EPA14 Geospatial Requirements: Data Architecture Goal 2: Provide EPA, its partners, and the public with the geospatial data they need to carry out EPA business processes and make environmental decisions. Current Efforts include:  Establish EPA’s National Geospatial Data Policy (June 05)  EPA Geospatial Metadata “template”/Business Rules/Architecture –Builds on FGDC Metadata Standards  Enterprise Data Solutions  Markeplace/Collaboration on Dataset Production

Enterprise Architecture at EPA15 EPA Metadata Arch – Existing Flow 15

Enterprise Architecture at EPA16 Geospatial Requirements: Application Architecture Goal 3: Provide EPA staff, partners, and the public with applications and web-services to access, manage, use, analyze, present, and interpret geospatial data to conduct business and make environmental decisions. Current Efforts include :  Reusable open and interoperable tools –EnviroMapper –Portal Development Efforts  Developing Geospatial Web Services for Data Access  Enterprise Licensing/Hosting/GOS

Enterprise Architecture at EPA17 Geospatial Requirements: Technology Architecture Goal 4: Design and implement an enterprise wide technical infrastructure that supports access, use, management, and delivery of distributed geospatial data, applications, and Web services in a seamless manner. Current Efforts include :  Geospatial needs incorporated into the EA  IT Road Map  Geospatial Data via the EPA Exchange Network  Geospatial Tools used in Portal Development  Grants

Enterprise Architecture at EPA18 Geospatial Requirements: Governance  Goal 5: Establish an effective governance structure for setting priorities for geospatial investments, coordinating geospatial efforts, and communicating how geospatial data and technologies are used within the Agency. Current Efforts include :  Geospatial Information Officer  Geospatial needs incorporated into the EA – Still a challenge!  Quality Information Council –GIS Work Group/Steering Committee – Subject Matter Experts  CPIC/Budget/Strategic Planning linkage

Enterprise Architecture at EPA19  CIO’s/OMB Formally acknowledge that Geospatial is a MAINSTREAM requirement  Help organizations realize that location-based analysis is a BUSINESS approach and not JUST a “technology”  Improve our ROI/GPRA/PART through program-level activities  DRM/SRM/TRM will help us with Interoperability and Sharing of data  Focus grants on unified approach to building partner capabilities Benefits of Geospatial Enterprise Architecture

1 EPA Enterprise Architecture EPA Contacts Wendy Blake-Coleman: Brenda Smith, Geospatial Information Officer: