1. EPA Enterprise Architecture Enterprise Architecture at the US Environmental Protection Agency John Sullivan, OEI, and Brian Burch, CBP

2. Enterprise Architecture at EPA2 EPA’s Enterprise Architecture: Evolving in an Evolving World

3. Enterprise Architecture at EPA3 Environmental Information Exchange Network An Internet and standards based method for exchanging environmental information between partners!

4. Enterprise Architecture at EPA4 New Strategic Plan Keystone of the Architecture Clean Air Clean and Safe Water Safe Food Preventing Pollution Better Waste Management Reduce Global Risks Expand Right to Know Sound Science Greater Compliance Effective Management Clean Air and Global Climate Clean and Safe Water Land Preservation & Restoration Healthy Communities & Ecosystems Compliance & Env. Stewardship 2003 Plan Simplified goal structure Same basic content Greater specificity of objectives and performance measures Include cross-goal strategies 1997 Strategic Plan2003 Strategic Plan

5. Enterprise Architecture at EPA5 EPA’s Business Reference Model

6. Enterprise Architecture at EPA6 The EPA BRM extends the FEA BRM Services to Citizens Mode of Delivery Support Delivery of Services Mgt of Gov. Resources EPA Business Reference Model FEA Business Reference Model v.2.0

7. Enterprise Architecture at EPA7 EPA Data Architecture Identifies key info objects 12/02 Target Data Model is a taxonomy Represents data types essential to EPA ‘Services for Citizens’ Separate Administrative Data Model supports other levels of the BRM Now moving toward Strategic Information Model EPA Target Data Model SourcesSubstancesFacilities Environmental Stressors Environmental Activities Populations Information References Places

8. Enterprise Architecture at EPA8 Strategic Information Model Identifies key info needed by Strategic Plan

9. CORE REFERENCE MODEL

10. Enterprise Architecture at EPA10 EPA’s Application Architecture Designed to integrate data A long term commitment to rebuild key Agency applications Built on shared common services –Data Collection –Data Processing –Data Storage –Data Access –Metadata Registries Provides EPA’s Exchange Network “node”

11. Enterprise Architecture at EPA11 ODS (Nat’l Prog) Processing EAI EPA’s Application Architecture: Built for Sharing (w/examples) EPA Portal Identity Mgt Access Mgt Environmental PortletAdministrative PortletScience Portlet GEOSASBOREINS Regional Mart Children’s Health MercuryLead Air Perf Metrics CDX FRSSRS ETL WaterWaste Pest & Toxics Enfor & Comp Admin Queries Out Data Marts Framework for Business Warehouses Data Processing Data In R e g i s t r i e s Business Intel (Appl & Tools AIR SDWS FED AQSICMSIFMS

12. Enterprise Architecture at EPA12 Emissions Reporting (based on TPA) Web Server Single Integrated System NODE DET TPA Catalog EPA NODE (CDX) RCRAInfo Reporting (based on TPA) National Emissions Inventory Database Internet RCRAInfo EPAState Environmental Department State systems may or may not be integrated. How the Exchange Network pieces fit together

13. Enterprise Architecture at EPA13 “Blueprint for aligning our IT infrastructure to meet our business needs”

14. Enterprise Architecture at EPA14 “Blueprint for aligning our IT infrastructure to meet our business needs” Clean Bay C2K commitments

15. Enterprise Architecture at EPA15 “Blueprint for aligning our IT infrastructure to meet our business needs” Our  partnership Partnership includes anyone with data, information, knowledge, systems related to the Bay

16. Enterprise Architecture at EPA16 “Blueprint for aligning our IT infrastructure to meet our business needs” Data, information, knowledge, systems

17. Enterprise Architecture at EPA17 “Blueprint for aligning our IT infrastructure to meet our business needs” Action plan

18. Enterprise Architecture at EPA18 We (the partnership – anyone with data, information, knowledge, systems related to the Bay) have specific commitments to clean the Bay (10-fold increase in oysters, decrease rate of harmful sprawl by 30%) We (the partnership) need to share data, information, knowledge, systems to effectively track our progress towards the commitments and a clean Bay The IT architecture is our (the partnership’s) plan to cooperatively develop and share data, information, knowledge, systems to support the commitments

19. Enterprise Architecture at EPA19 Current EPA/CBP/State Architecture State CBP EPA DB’s Apps Eyes My WS DCR DSS Apps Wsp BayAtlas COMET Apps EF Surf WME CIMS Standards EPA Standards Issues: Dual Submissions Dual Standards Data Versioning, timeliness, multiple “answers” EPA CBP States

20. Enterprise Architecture at EPA20 Leveraging EPA’s Architecture and Infrastructure State DB’s Apps Eyes My WS DCR DSS EPA CDX DB’s State/EPA ECOS Standards Apps EF Surf WME CBP DB’s Apps Wsp BayAtlas COMET EPA CBP States Leverage: State/EPA data EPA knowledge

21. Enterprise Architecture at EPA21 CBP Services CBP’s Conceptual Infrastructure State DB’s Apps Eyes My WS DCR DSS EPA CDX DB’s State/EPA ECOS Standards Apps EF Surf WME DB’s Apps Wsp BayAtlas COMET State/CIMS or existing Standards EPA CBP States

22. Enterprise Architecture at EPA22 CBP Services CBP’s Conceptual Architecture Other Ag & Orgs DB’s Apps ? States DB’s Apps EF Surf WME DB’s Apps Wsp BayAtlas COMET CIMS or existing Standards EPA CBP States Other Agencies & Orgs

23. Enterprise Architecture at EPA23 Leveraging EPA’s Architecture: Supporting C2K Data flows –STORET critical –PCS –TRI Information/knowledge –Indicators –Status & trends –Interpretations Geospatial blueprint –Accurate, timely land cover data

24. Enterprise Architecture at EPA24 Making it happen EPA: –CDX availability (STORET, etc.) –Beyond data States: –Submit data via CDX CBP –Infrastructure to support non-EPA exchanges

25. EPA Enterprise Architecture Contacts: John Sullivan, EPA Chief Architect: sullivan.john@epa.gov, 202-566-0328sullivan.john@epa.gov Brian Burch, Chesapeake Bay Program, burch.brian@epa.gov, 410-267-5736burch.brian@epa.gov