1. FEA DRM
Management Strategy
11 October 2006
“Build to Share”

2. Agenda History Content Three Pillar Data Strategy Framework
Governance Strategy
Three Key Implementation Strategies
Three Strategic Goals and Outcomes

3. History Initially developed with FEA DRM
Underwent several iterations since December 2005
Coordinated review across Federal agencies
August 2006 – DAS reviewed and concurred with key strategies, goals and outcomes
September 2006 – FEA PMO accepted the final draft
Document publication is pending Karen Evan’s review and concurrence

4. Content Overall theme is about managing data as a national asset
Written for CIO’s, CFO’s, and Chief Architects
High level description of the three DRM concepts: Context, Description, and Info Sharing
Provides key implementation strategies, goals, outcomes, and sample measures
Answers five basic questions

5. The Five Questions About the FEA DRM
What is it?
Why is it important?
Who are the key players?
How will it work?
What are the strategic goals and outcomes?

6. FEA DRM Concepts
(What is the FEA DRM and
why is it important?)

7. FEA DRM Concept How do I exchange the data?
Data Sharing
Query Points and Exchange Packages
Data Description
Data
Data Context
Taxonomies
How do I exchange the data?
What does the data mean?
How do I find the data and access it?
Based on FEA DRM Version 2.0

8. FEA DRM Structure

9. Targets the Right Data to the Right Person
FEA DRM Value
Targets the Right Data to the Right Person
at the Right Time.

10. Three Pillar Data Strategy Framework
FEA DRM
Three Pillar Data Strategy Framework
(How will it work?)

11. The DRM Data Strategy Framework
Business &
Data Goals
drive
Information Sharing/Exchange
(Services)
Governance
Data Strategy
Data Architecture
(Structure)
The Rule: All 3
pillars are required
for an effective
data strategy.
This slide illustrates the Data Strategy Framework. As shown, it consists of Goals, and a data strategy of three components, that is of governance, structure, and services.
Data strategy starts with goals. These goals are business goals and are normally well outside the bounds of the data strategy itself. Business goals include things like “increase market share” and “decrease cycle time”. Business goals drive the data strategy and there are comprehensive methods of translating them into data management goals that support attainment of the business goals. Goals drive the data strategy.
Within the data strategy, we find ourselves dealing with the Structure of our data (which is where a lot of us live and never come up for air). We find ourselves dealing with Services that make the data available and with Governance which establishes procedures, sets standards, and generally specifies how everything fits and works together to meet the corporate goals, so maybe the arrow from Goals to Data Strategy needs to be two ended.
Goals drive; governance controls; structure defines; and services enable data strategy.
Special thanks to Laila Moretto and Forrest Snyder, MITRE Corp.

12. COI and LOB Implementation
Business &
Data Goals
drive
Information Sharing/Exchange
(Services)
Governance
Data Strategy
Data Architecture
(Structure)
Each COI or LOB will implement the
three pillar framework strategy and will
focus on business requirements.

13. Data Strategy Framework Sample Elements
Information Sharing/Exchange
(Services)
Data Architecture (Structure)
Governance
Oversight
Policy & Procedures
Processes and Practices
Education/Training
Issue Resolution
Metrics/Incentives
Data Transfer Standards
Pedigree
Authoritative Sources
Security/Protection Data
Discovery Data
Inventory
Definitions/Semantics
Structure
Syntax
Access Services
Brokering
Shared Spaces
Data Catalogs
Data Registries
Communities of Interest
Search
Mediation
Here, the items identified as areas to be addressed by the data strategy according to the components of the Data Strategy Framework. All three components are represented.
Use of specific elements depend on the goals

14. Mapping the Sample Elements of the Strategy Framework to the DRM
Data Context enables…
Data Description captures…
Data Sharing guides…

15. (Who are the key players?)
Governance Overview
(Who are the key players?)

16. Governance Strategy
Governance for DRM Implementation is centered around:
Data Architecture Subcommitee
Communities of Interest (COIs)
Lines of Business (LOBs)
Purpose: To advances the management of Federal data as a national asset; stewardship of the Federal Enterprise Architecture (FEA) Data Reference Model (DRM), FEA DRM Management Strategy; to promote the use and improvement of data and data standards across the Federal Government; to facilitate of community collaboration and information sharing using communities of interests, both federal and intergovernmental.

17. Governance Strategy (DAS)
Federal Data Architecture Subcommittee (DAS)
Chartered by Federal CIO Council
2 Co-chairs appointed by AIC
Membership Federal CIO representation
Various work groups
Member meetings monthly
Vision: Engage communications in advancing the management of Federal data as a valued national assets that supports the business of the Federal Government.
Key FY06/FY07 Activities/Deliverables
1. FEA DRM updates and revisions
2. Implementation strategies, best practices, and success stories
Establish an authoritative knowledge center for Federal data-
related issues and opportunities
Purpose: To advances the management of Federal data as a national asset; stewardship of the Federal Enterprise Architecture (FEA) Data Reference Model (DRM), FEA DRM Management Strategy; to promote the use and improvement of data and data standards across the Federal Government; to facilitate of community collaboration and information sharing using communities of interests, both federal and intergovernmental.

18. COI and LOB Implementation
Business &
Data Goals
drive
Information Sharing/Exchange
(Services)
Governance
Data Strategy
Data Architecture
(Structure)
Each COI or LOB will implement the
three pillar framework strategy and will
focus on business requirements.

19. Implementation Strategies (What are the strategic goals and outcomes?)
Three Key
Implementation Strategies
(What are the strategic goals and outcomes?)

20. Implementation Strategies
Guide agencies in developing mature data architectures and management practices integral to their enterprise architectures.
Create the ability for rapid information sharing, data standardization, and data re-use through the DRM.
3. Assist agencies in the use of the DRM in order to facilitate compliance with Executive Branch policy, legislation, legal mandates or decisions.

21. Sample Performance Measures
Goals, Outcomes, and
Sample Performance Measures

22. Goal #1
Guide agencies in developing mature data architectures and management practices integral to their enterprise architectures
Outcomes:
1. Agencies are following the Three Pillar Data Strategy
2. Agencies have evidence of their Three Pillar Data Strategy implementations that are consistent with the DRM abstract model.
Sample Performance Measures:
Increase in agency scores for the data architecture section of the OMB EA Assessment Framework.
Decrease in the time between data being collected in the field before it is uploaded into government databases.
Percentage of standard and/or ad hoc reports produced accurately and on time for internal and/or external stakeholders.

23. Goal #2
Outcomes:
1. Agencies enable business and customer results-driven and expedited information sharing through provisioning data services in accordance with the FEA DRM.
2. Agencies initiate or participate in COIs for existing cross-agency initiatives (Presidential E-Government initiatives and others); they have a formal data interoperability standard identified and recorded on a suitable platform.
3. Agencies initially identify and inventory data assets and formally appoint competent stewards for each data asset made available for sharing or reuse and exposed to the public.  These actions are in response to the E-Government Act of 2002, OMB M-06-02, and OMB Circular A-130 and are consistent with the FEA DRM version 2.0 services for data sharing.
4. Agencies initially identify and inventory data assets and formally appoint competent stewards for each data asset made available for sharing or reuse and exposed to the public. 
5. These actions are in response to: the E-Government Act of 2002,
OMB M-06-02, and OMB Circular A-130, and are consistent with the FEA DRM version 2.0 services for data sharing.
Goal 2: Create the ability for increased and expedited information sharing, data standardization, and data re-use through the evolving FEA DRM.

24. Goal #2 Sample Performance Measures:
Increase in the number of inter-agency data sharing interfaces.
Increase in the number of approved data standards used by two or more agencies.
Percent of available population using a collaboration environment supporting Federal data management activities (e.g., DRM registry, etc.).
Extent to which data or information is current (as measured in days since last update)
Increase in the amount of data captured from electronic processes (rather than paper processes).
Increase in agency adoption of approved E-Gov data standards (e.g., CHI).
Increase in the percentage of data elements for which standards and definitions exist in an enterprise data dictionary (i.e., increased Data Standardization).
Increase in the number of state/local governments exchanging data electronically with Federal agencies.
Increase in the number of hardcopy records digitized, indexed, and/or catalogued.
Goal 2: Create the ability for increased and expedited information sharing, data standardization, and data re-use through the evolving FEA DRM.

25. Goal #3
Goal 3: Promote agencies’ use of the FEA DRM to support Public Access to Government Information. The DAS will provide related information and develop guidance as required in support of the strategic outcomes.
Outcome:
1. Agencies provide data sharing services in accordance with the FEA DRM to facilitate public access to government information.
2. Agencies ensure security and privacy capabilities that promote public access and information protection.
Sample Performance Measures:
Increase in the number of publicly available web services providing data in machine-readable form.
Decrease in the amount of redundant data collected from citizens.
Decrease in the number of redundant data sources (i.e., data sources duplicating data already provided by other agencies).
Decrease in data request fulfillment time.
Decrease in the average processing time for inter-agency data transactions.
Increase in the number of unique visitors to cross-agency data exchanges / information sharing platforms (e.g., FirstGov.gov, Business.gov, Forms.gov, Export.gov, etc.).

26. Summary

27. Summary
The FEA DRM Mgmt Strategy answers five basic questions about the DRM.
DRM governance approach includes DAS, COIs, and LOBs to manage data as a national asset.
Agencies can implement the FEA DRM in many ways using the Data Strategy Framework
DRM Management Strategy provides 3 key strategies and goals.

28. Questions
Co-chair contact info:
Suzanne Acar:
Bryan Aucoin: