Agenda

1. United States Environmental Protection AgencyOffice of Environmental InformationEnterprise Data Architecture ProgramOverview PresentationMarch 2008

2. Agenda This presentation provides an overview of the Enterprise Data Architecture (EDA) program • The topics addressed in this briefing include: • EDA Program Vision and Goals • Drivers • Holistic Program Design • Stakeholder-Centric Structure • Governance Model • Key Roles and Responsibilities • Community of Interest • Value Chain • Strategy for Program Growth • Next Steps

3. EDA Program Vision and GoalsEPA’s approach to the program EPA has clearly defined its vision and goals for the EDA program, which serve as guiding principles influencing all aspects of the program • EPA’s EDA program vision: The EDA program seeks to maximize the value of enterprise data assets by improving accessibility, reusability, reliability, and overall quality. Through its defined governance framework and operational model, the EDA program will publish guidance and will leverage Data Stewards throughout the Agency to function as a proactive enterprise service organization. The EDA program will affect change by helping to solve critical data management issues and challenges facing EPA’s programs and their core data partners. • Key Points of emphasis: • Maximizing value • Improving access • Supporting reuse • Ensuring data is reliable • Optimizing quality

4. Data DriversThe impetus for developing an EDA program There are several legislative drivers for an EDA program which EPA has taken into consideration • Some of the key mandates driving the need for a formalized EDA program:

5. Data DriversThe impetus for developing an EDA program There are also business drivers that have influenced the development of the program to improve Agency operations • Business Driver 1: The development of Federal Enterprise Architecture (FEA) increased the importance of aligning initiatives with cross-agency missions and strategic goals • Business Driver II: Collaborative partners have a significant influence on data management and information sharing • Bi-directional dependence on data provided by/to external collaborators from various data sources The DRM can accelerate enterprise and joint action around new opportunities afforded by standardized approaches for accomplishing goals

6. Holistic Program DesignHigh level operational model The following graphic provides a high level operational model for the EDA program

7. Stakeholder-Centric StructureHigh level operational model The EDA program is designed to be highly stakeholder focused, with specific attention paid to interactions and engagement at all levels of the Agency

8. Governance ModelThe Role of the DAC The EDA program is governed by the Data Architecture Committee (DAC) • The Data Architecture Committee (DAC) serves as the steering committee and decision making body for all data-related matters within the Agency • INPUTS • Data Stewards • CPIC • Procurement • System Design • OUTPUTS • Obtain QIC approval • Distribute decisions to Data Stewards • DATA ADVISORY COMMITTEE • Develop Policy • Design Guidance

9. Key Roles and ResponsibilitiesData Stewards Data Stewards play an integral role in the program as liaisons from each of the program offices and cross-cutting initiatives • Tacticians. Work at the operational level • Representatives. Serve as liaisons between each program offices/initiative areas and the DAC • Communicators. Provide feedback and best practices from the program offices and initiatives to the DAC for incorporation in policies, guidance, etc. • Collaborators. Serve as active members of the Data Community of Interest (COI) for all Data Stewards • Leverage group successes and support the promulgation of best practices • Discuss issues and concerns that are relevant to the data architecture community – inform the DAC of these issues

10. Key Roles and ResponsibilitiesChief Data Architect The Chief Data Architect leads and provides oversight to EDA program operations by serving on the DAC and engaging with various stakeholder segments • Leader. Drives EDA program progress through the DAC • Facilitator. Encourages collaboration among Data Stewards and interaction with other agency stakeholders • Coordinator. Establishes strong working relationships with external stakeholders to coordinate and share best practices

11. Key Roles and ResponsibilitiesOther Significant Roles There are several other key stakeholder groups who play an integral part in the success of the EDA program

12. Key Roles and ResponsibilitiesEstablishing a Community of Interest The Data Architecture Community of Interest (COI) is an important forum for Data Stewards to meet on a regular basis and share their experiences • The Data Architecture COI is designed to: • Share best practices • Prioritize and communicate issues • Identify trends • Propose solutions • Collectively communicate feedback to the DAC • The Data Architecture COI will meet on a monthly basis at EPA HQ with call in capability for non-local Data Stewards

13. Value ChainThe necessary high level functions The EDA program, with a strong structure in place, is positioned to bring ongoing value to the Agency

14. Strategy for Program GrowthAligning with the EA segment approach The EDA program, with a strong structure in place, is positioned to bring ongoing value to the Agency

15. Strategy for Program GrowthNext Steps The EDA program will continue to grow the program and will engage in the following near-term activities • Define / Publish the Enterprise Data Management Framework • Complete Data Intranet Site • Design program branding • Develop outreach materials

16. Contact Information If you have any questions about the information presented today please contact one of the following individuals John Sullivan EPA Chief Architect 202.566.0328 (office) sullivan.john@epa.gov Kevin Kirby, EPA Enterprise Data Architect 202.566.1656 (office) kirby.kevin@epa.gov