Enterprise Architecture at the U.S. EPA

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

2. Agenda • Context and History of EPA Enterprise Architecture • EPA’s Enterprise Architecture Framework • Geospatial Blueprint • Implementing the Goals Enterprise Architecture at EPA

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

4. Environmental InformationExchange Network • States – Data Stewards • EPA – Data User • Partnership & Collaboration between Governments An Internet and standards based method for exchanging environmental information between partners! Enterprise Architecture at EPA

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

6. EPA’s Enterprise Architecture:FEAF-enhanced Framework Enterprise Architecture at EPA

7. 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 EPA

8. Sequencing Plan for Implementingthe Architecture Enterprise Architecture at EPA

9. EPA Metadata Architecture – Existing Structure 9 Enterprise Architecture at EPA

10. Geospatial Blueprint:EPA’s Geospatial EA Component Enterprise Architecture at EPA

11. Business Services Requiring Geospatial Analysis • 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 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 Enterprise Architecture at EPA

12. 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 EPA

13. Digitize Project Location Enterprise Architecture at EPA

14. 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 EPA

15. EPA Metadata Arch – Existing Flow 15 Enterprise Architecture at EPA

16. Geospatial Requirements:Application Architecture Goal 3: Provide EPA staff, partners, and the public withapplications 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 EPA

17. 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 EPA

18. 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 EPA

19. Benefits of Geospatial Enterprise Architecture • 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 Enterprise Architecture at EPA

20. EPA Contacts Wendy Blake-Coleman: blake-coleman.wendy@epa.gov, 202-566-1709 Brenda Smith, Geospatial Information Officer: smith.brenda@epa.gov, 202-546-2034