1. Enterprise Data Architecture Program Office of Environmental Information Enterprise Architecture Team Overview Presentation for CIO Biweekly Kevin J. Kirby March 19, 2008
I would like to thank you for taking the time to learn more about the development of EPA’s very own Enterprise Data Architecture program. Over the several months we have been strategizing and leveraging Federal best practices to create the optimal approach to program development and execution.
I am eager to hear your thoughts on our progress and hope that today’s briefing will be both informative and engaging.

2. The topics addressed in this briefing include:
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
Today I will address the program’s vision and goals and will walk you though the drivers that stirred us to action which include both legislative and business stimuli.
I will also present the high level structure of the program, and the selected governance model. These strategic components will be supplemented with a discussion on key roles and responsibilities as well as the development of a tactical level Community of Interest. Finally, I will address our longer-term strategy for growth and further program refinement.

3. EDA Program Vision and Goals EPA’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.
EPA faces challenges around: Information interoperability AND sharing
The Enterprise Data Architecture (EDA) program, as a part of the overall Enterprise Architecture (EA) program, has created a guiding vision to help meet these challenges that focuses on:
Value
Access
Reuse
Reliability and
Quality
Key Points of emphasis:
Maximizing value
Ensuring data is reliable
Improving access
Optimizing quality
Supporting reuse 2

4. Data Drivers The impetus for developing an EDA program
Legislative drivers for an EDA program
Some of the key mandates driving the need for a formalized EDA program:
Well, this is all fine and good, but what business does OEI have in meddling with programatic data.
There are several key mandates that drove the need for a formalized EDA program at EPA. Here I have outlined some of the most significant drivers from a compliance perspective.
Additional OMB and GSA Directives, Federal Laws and the FEA present other key mandates aimed to make government and corporate systems more efficient, resourceful, and secure. 3

5. Data Drivers The impetus for developing an EDA program
Business drivers influencing the EDA Program
The Federal Enterprise Architecture (FEA) increased the importance of aligning initiatives with cross-agency missions and strategic goals
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
In 2002, OMB led an initiative to discover more simple and efficient ways to align information and processes across government agencies with the creation of the Federal Enterprise Architecture (FEA).
The goal was to create a more cost effective and customer focused government.
As a result, EPA has focused on aligning initiatives with missions and strategic goals. This included data architecture and FEA’s DRM.
In addition to this business driver, there has also been a bi-directional dependence upon data provided by/to external collaborators from various data sources. Looking at the Agency’s Strategic Plan, there is an extensive list of collaborative partners 4

6. Holistic Program Design High level operational model
A high level operational model for the EDA program
This graphic provides a high level operational model of the EDA program.
It depicts the various levels at which stakeholders will engage, including grassroots efforts and decision making bodies.
At the base of the graphic lies the various cross cutting initiatives – from Pollution Prevention & Control to Enforcement & Compliance.
A Data Steward, who will operate within each of these layers, is selected to represent the focus area on all matters related to the EDA program. (This will often include feedback on the impact of policies and guidance as well as promoting best practices that are discovered within that area of focus.)
In addition to cross-cutting initiatives, Data Stewards will also selected by each program office to serve as a voice for data related issues within each domain.
They will be charged with promulgating best practice throughout their program offices. All Data Stewards will be encouraged to share among their peers in a data-focused Community of Interest (COI) that provide an opportunity for the group to raise feedback to the DAC for consideration and incorporation in policies, guidance, templates, etc.
The Data Advisory Committee (DAC) also receives inputs from the Data Stewards, either individually or through the COI, which informs their decision-making process. The outputs of the DAC will be influenced by several external factors including procurements, CPIC, system design, SLCM, and information sharing activities.
Beyond cascading communication down to the program offices and initiative areas, the DAC will also be responsible for providing data standards and authoritative standards. The outputs require support from the senior governing bodies (such as the EAWG, QIC, and IIS) prior to release, and will ultimately influence all aspects of the program. 5

7. Stakeholder-Centric Structure High 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
The EDA program needs to support a wide array of internal and external stakeholders.
Internally, the EDA program needs to manage relationships within the Mission Investment Solutions Division (MISD), including EA and the CPIC programs as well as the IT Policy & Training program.
In addition, the EDA program will manage relationships with other Office of Environmental Information (OEI) divisions focused on information exchange and collection (OIC) as well as information analysis and access (OIAA).
The EDA program must also manage relationships with governance bodies and working groups which cross multiple program offices and provide the Agency-wide perspective. These include the Quality Information Council (QIC), its Information Investment and Exchange Network Subcommittees (IIS & ENS), and the Enterprise Architecture Working Group (EAWG). These relationships are the most effective means to solidify the program.
It is very important for EDA Program leadership to attain the support of the senior members of each program office. To that end, the EDA Program will establish the Data Advisory Committee (DAC) that will take feedback under advisement and serve as a decision-making authority within the Agency’s data community.
The EDA program will also interact with external data collaborators in the same fashion as the internal programs. It will deliver technical services in support of improving exchange standards and techniques to improve overall exchange efficiency and data quality. In either scenario, program office leadership endorsement is critical. 6

8. Governance Model The 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
Purpose of the DAC
Issue policies and guidance
Provide templates and support materials
Obtain buy in and support on data and authoritative standards
Support the development and implementation of the EPA Enterprise Data Architecture Program
Leveraging senior data leaders from across the Agency, the EDA program will establish the Data Advisory Committee (DAC). The DAC will become a steering committee and decision making body, focusing on facilitating effective data management, minimizing data redundancies and overall promotion of reuse across the Agency. The purpose of the Data Advisory Committee (DAC) is to:
Issue policies and guidance to the data community that will align with the data architecture layer of EPA’s Enterprise Architecture (i.e., Data and Information Reference Model (DRM)
Obtain buy in and support on data and authoritative standards;
Provide templates and materials to support Modernization Blueprint activities,
Support the development and implementation of the EPA Enterprise Data Architecture Program used to produce and maintain EPA DRM and other data architecture artifacts, and
Serve as liaison between the Department and Agency/Offices on data and information architecture priorities.
INPUTS
Data Stewards
CPIC
Procurement
System Design
DATA ADVISORY COMMITTEE
Develop Policy
Design Guidance
OUTPUTS
Obtain QIC approval
Distribute decisions to Data Stewards 7

9. Key Roles and Responsibilities Data 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 and tactical levels
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
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
In addition to effective governance, the management of data requires distributed stewardship of core data at the Agency.
Therefore, the role of the Data Steward is critical to the success of the program.
Each program office will maintain a Data Steward who is responsible for addressing data related issues. These stewards are leveraged not only for their direct knowledge of the subject matter data but also for the efficiencies they have gained through direct management of their data.
As a group, Data Stewards from across the Agency will convene in regular Community of Interest (COI) sessions to tackle operational data challenges and share best practices.

10. Key Roles and Responsibilities Chief 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
The most visible member of the EDA program is the Chief Data Architect. Their responsibilities include leading, coordinating and facilitating interactions between the EDA program and its internal stakeholders.

11. Key Roles and Responsibilities Other Significant Roles
There are several other key stakeholder groups who play an integral
part in the success of the EDA program
Role
Responsibilities
Information Investment Subcommittee
Investment review is performed by the CPIC program, the EA program and ultimately by the governance authority provided to the IIS. It ensures compliance with policies and procedures, in addition to confirming EA compliance prior to approval for inclusion in the IT investment portfolio.
In addition to the IIS, the Quality Technology Subcommittee (QTS) reviews EA technical standards. They also address the technical feasibility of solution architectures and security layers of the target EA as well as the transition strategy and sequencing plan.
Program Leadership
Program offices are responsible for implementing the mission of their individual program. Goals and objectives are set, linking to the Agency’s strategic plan.
Chief Enterprise Architect
The chief architect is responsible for overseeing the IT portfolio for the Agency and meeting the compliance reporting requirements set forth internally and externally. The EAWG is facilitated by the chief architect and is designed to prioritize and support enterprise architecture efforts throughout the program offices.
The IIS ensures that all EDA efforts comply with relevant policies and procedures while the QTS reviews technical standards. These groups receive recommendations from the DAC for consideration and approval. These recommendations often arise from program leaders who share information through their Data Steward.
Additionally, the Agency’s Chief Architect, in concert with the EAWG, supports IT portfolio oversight and compliance.

12. Key Roles and Responsibilities Establishing 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
The data stewards will convene on a regular basis as a Community of Interest (COI) to collaborate and develop strategies that can be applied across the Agency. Feedback arising from these sessions will be elevated to the DAC for approval and distribution to all operationally focused data stakeholders.

13. Value Chain The necessary high level functions
The EDA program, with a strong structure in place, is positioned to
bring ongoing value to the Agency
The EDA program is designed to support the value chain addressed here. It will focus on the value gained through data collection, integration, and providing products/services for data architecture.
The value chain captures key high-level functions necessary to develop core products and services.

14. Strategy for Program Growth Aligning with the EA segment approach
The EDA program, with a strong structure in place, is positioned to bring ongoing value to the Agency
The EDA program’s approach to growing the data architecture is closely aligned with EPA’s approach to growing its target architecture through the continued use and development of segments within its enterprise architecture. Each segment addresses the architectural layers at a much more granular level than the Agency’s target architecture is intended to address business modernization and affect change from the bottom-up.

15. Strategy for Program Growth Next 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
In the coming months, the program will focus on informing and engaging stakeholders. As a first step, the program will (with you endorsement) publish the Enterprise Data Management Strategy. This will explain the program in far greater detail and will serve as a reference guide for stakeholders. Additionally, we are completing work on the EDA intranet site, which includes governance, resources, and outreach information. Finally, we will develop and issue the EDA brand as well as associated collateral.

16. Enterprise Data Architect
Contact Information
If you have any questions about the information
Presented, please contact one of the following individuals
Kevin Kirby, EPA
Enterprise Data Architect
(office)
John Sullivan
EPA Chief Architect
(office)
Thank you for your time today. I would be happy to answer any of your questions at this time.