The FEA Data Reference Model

V2.0Michael C. Daconta, DRM Working Group

Lead

Susan Turnbull, AIC Representative

Mary McCaffery, FEA PMO Representative

2

Agenda

• Background• The Problem• The Solution:

Communities of Interest (COI)

• DRM Support to COIs• Agency

Implementation• Conclusion

3

Background• Three part working group

– DRM Volume 1.0 – Dec. 2004– Initial meeting: February 7th, 2005– Agency participation: 124 – Designated Agency Reps: 30

• Open working group– # of Documents on Wiki: 240– # participants in workshops: 543– Highly interactive– # vendor product demonstrations

on draft specifications: 4

• We are proud to present the product of your best data architects!

Public

Teams

Exec

Public

Teams

Exec

EO13356 HSPD-11

Wiki

4

The Problem“The biggest impediment to all-source analysis—to a greater likelihood of connecting the dots—is the human or systemic resistance to sharing information.”

- 9-11 Commission Report, Pg 416, July 22, 2004

“This area has received increased attention but the federal government still faces formidable challenges sharing information among stakeholders in an appropriate and timely manner to minimize risk.”

- GAO, “HIGH-RISK SERIES, An Update”, January 2005,

“Equally problematic, individual departments and agencies continue to act as though they own the information they collect, forcing other agencies to pry information from them.”

- Commission on Intelligence Capabilities of the US in regard to WMD, Pg 14. March 31, 2005

“Bush’s choice to run Information Sharing Environment draws criticism”- GCN Article, June 3, 2005

“Info Sharing still the missing link.”- Federal Computer Week Article, June 6, 2005

“Intelligence Changes Still Thwarted By Lack Of Information Sharing.”- Information Week Article, June 7, 2005

“This committee has long been concerned about the lack of information sharing and analysis within the government and among the relevant public and private sector parties.”

- Rep. Tom Davis, House Government Reform Committee. June 9, 2005.

“But we're not as convinced that information sharing between agencies, and the computer technology needed to analyze it, has improved.”

- Boston Herald editorial staff, Saturday, June 11, 2005

The DRM is a framework whose primary

purpose is to enable information sharing

and reuse across the federal government

via the standard description and discovery

of common data and the promotion of

robust data management practices.

5

Communities of Interest

• Definition: A collaborative group of users that must exchange information in pursuit of its shared goals, interests, missions, or business processes and therefore must have shared vocabulary for the information it exchanges. – DOD Directive 8320.2

6

The DRM is Business-Driven

COI

Org 2

Org 3Org 1

Agility

Increased Information Sharing

Common Understanding

Improved DiscoveryRapid Harmonization

Consistent Models

ScreeningEmergency ManagementLaw Enforcement

…Intelligence

COIs are bothIntra and Inter-Organization

BRM DRM

Cross-AgencyBusiness

Need

7

Data Integration and Interoperability

The DRM enables description of structured data in entity/attribute form. For example, the following are representations for “person” and “event” entities, along with their attributes, and the relationship between them:

In the US, the “personIdentifier” attribute could be the person’s Social Security Number (SSN).

Usage Example: Data Description

Caused

Person

personIdentifier: Integer fullName: String BirthDate: Date age: Integer address: String

etc.

Event

eventIdentifier: Integer eventType: String eventDate: Date eventTime: Time

etc.

8

Data Discovery and Authoritative Sources

The following example expands on the earlier “Data Description” usage example. It depicts a partial taxonomy that includes a “Person” entity, with several levels of categorization (subtopics) beneath it. Relationship types are specified to the left of each arrow – for example, “Private Person” (e.g. a retiree) is a type of “Person”. Although all relationships in this example are the same, that is not always the case.

Usage Example: Data Context

Party

Person Organization*

Government Person

IndustryPerson

PrivatePerson

The following example expands on the earlier “Data Description” usage example. It depicts a partial taxonomy that includes a “Person” entity, with several levels of categorization (subtopics) beneath it. Relationship types are specified to the left of each arrow – for example, “Private Person” (e.g. a retiree) is a type of “Person”. Although all relationships in this example are the same, that is not always the case.

Usage Example: Data Context

The following example expands on the earlier “Data Description” usage example. It depicts a partial taxonomy that includes a “Person” entity, with several levels of categorization (subtopics) beneath it. Relationship types are specified to the left of each arrow – for example, “Private Person” (e.g. a retiree) is a type of “Person”. Although all relationships in this example are the same, that is not always the case.

Usage Example: Data Context

Party

Person Organization*

Government Person

IndustryPerson

PrivatePerson

Party

Person Organization*

Government Person

IndustryPerson

PrivatePerson

9

Data Sharing of Fixed and Dynamic Business

TransactionsThis example is based on an existing implementation of the DRM at U.S. Department of the Interior (DOI), for the Recreation One Stop initiative. It depicts the sharing of data that resides in the Recreation Information Database (RIDB). A query point exists for this data asset, and it is a CGI (Common Gateway Interface) program.

Usage Example: Data Sharing

This example is based on an existing implementation of the DRM at U.S. Department of the Interior (DOI), for the Recreation One Stop initiative. It depicts the sharing of data that resides in the Recreation Information Database (RIDB). A query point exists for this data asset, and it is a CGI (Common Gateway Interface) program.

Usage Example: Data Sharing

RIDB

Query

Point

http://www.recreation.gov/detail.cfm?ID=1577

RecML Document

Query (Get String)

Response

RIDB

Query

Point

http://www.recreation.gov/detail.cfm?ID=1577

RecML Document

Query (Get String)

Response

10

DRM Architectural Pattern

11

How do I implement the Data Description Guidance?

• Define COIs

• Define Common Data– Conceptual Data

Model– Logical Data Model– Precise Definitions

• Register Common Data

COI Financial System A

COI Recreation System B

COI Fire Management System C

Information Class A BRM Business

Need

Data Sharing Opportunities

IdentifyCommon DataData Subject Area A B

Information Class B

Information Class C

Business ContextBusiness Context

12

How do I implement the Data Context Guidance?

• Create a Data Asset Inventory

• COIs categorize Data Assets

• Develop other contexts– Security– Privacy– Service

(Data Description) Entity (1) Subject Area and Information Class Context

RECREATION-AREA

RECREATION-AREA-NAME

Subject Area: RECREATION

Information Class: RECREATION INVENTORY

Bureau of Land Management

Business Area: Services for Citizens

Line of Business: Natural Resources

Sub-Function: Recreational Resource

Recreation Information Database (RIDB)

(2) Organization Context

(3) FEA-BRM Context (5) Data Asset

Context

(4) Service Context

Service: Get Recreation Inventory

13

How do I implement the Data Sharing Guidance?

• Only for COI participants

• Model Business Transactions

• Distinguish between fixed and dynamic transactions

• Provision Data Services

14

Next 20 Days• Due Nov 4: send comments

through your representative and/or http://red-team@cosine.cim3.net

• Contact Susan Turnbull to arrange on-site briefing or participation in virtual workshops: 10-noon Oct. 26, Nov. 1 and 3, 202-501-6214, susan.turnbull@gsa.gov

15

Strategic Dialogue

• Initial thoughts, reflections …– Implications of DRM for your setting?– Priorities for Harmonization through COIs in FY06?– Potential Pilots for Validation and Testing of DRM?– How COIs Can Reinforce Shared Mission Purposes?– Learning Opportunities for Staff?– Collaborative Roadmap for High Performance on EA

2.0 Framework?– How quickly can the DRM Architectural Pattern

improve shared understanding among business and technical perspectives?