0 Enterprise Data Architecture Program Office of Environmental Information Enterprise Architecture...

16
1 Enterprise Data Architecture Program Office of Environmental Information Enterprise Architecture Team Overview Presentation for CIO Biweekly Kevin J. Kirby March 19, 2008

Transcript of 0 Enterprise Data Architecture Program Office of Environmental Information Enterprise Architecture...

1

Enterprise Data Architecture Program Office of Environmental Information

Enterprise Architecture Team

Overview Presentation forCIO Biweekly

Kevin J. KirbyMarch 19, 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.

4

Data DriversThe 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:

5

Data DriversThe 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

6

Holistic Program DesignHigh level operational model

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

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

INPUTS•Data Stewards•CPIC•Procurement•System Design

DATA ADVISORY COMMITTEE

•Develop Policy•Design Guidance

OUTPUTS•Obtain QIC approval•Distribute decisions to Data Stewards

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

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

Role ResponsibilitiesInformation 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.

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

EDA Program

EDA Products and Services

EPA Information

and Data Integration

Creating EPA Value-AddedInformation

EPA Info. & Product/ ServiceDelivery

EPA Information

and Data Collection

EDA Program PlanningData Stewardship & Governance

Data Policy Change Management

Communications & OutreachMetadata Management

Data Standards

Data Modeling & Semantics IT System Development Support

Training

Information Transformation & Exchange Management Support

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

Define / Publish the Enterprise Data Management Framework

Complete Data Intranet Site

Design program branding

Develop outreach materials

The EDA program will continue to grow the program and will engage in the following near-term activities

16

Contact Information

If you have any questions about the informationPresented, please contact one of the following individuals

John SullivanEPA Chief Architect202.566.0328 (office)

[email protected]

Kevin Kirby, EPAEnterprise Data Architect

202.566.1656 (office)[email protected]