Unification & Simplification Through: C ooperation I nnovation O pportunity DOI Data Reference Model...

Unification & Simplification Through:• Cooperation• Innovation• Opportunity

DOI Data Reference Model Overview

May 10, 2005

2

“Achieving Information Excellence”

Presentation Contents

Background

DOI’s FEA DRM implementation strategy

DOI’s Data Infrastructure

DOI’s Data and Information Sharing

DOI DRM Implementation Examples

Summary

3


DOI DRM BackgroundInformation

4


Organizational Context

The Department of the Interior manages one of every five acres of land in the United States, providing opportunities for wilderness, wildlife protection, recreation, and resource development;

We supply water for much of the West so that farmers can grow food and people can turn on their taps;

We provide access to energy and minerals so that people can warm and cool their homes, and drive to their jobs;

We honor our special responsibilities to American Indians, Alaska Natives, and affiliated Island communities; and

We protect wildlife and improve the environment.

5


The Major Drivers

• Clinger Cohen Act

• OMB Circular A-130

• FEA PMO Guidance Documents

• Various Court Cases (e.g. Cobell vs Norton)

6


DOI’s Approach

Follow OMB’s model (i.e. 5 key federal lines of business)

Supplement FEA DRM with DOI level guidance

DOI’s internal driver is Modernization Blueprints– Worked by communities of practice– Provides decision support– Implementable

DOI follows ISO 11179– Supplement with lower level guidance– Not always easy to follow, but still a good reference– DOI established discrete representation classes– ISO 11179 helps DOI achieve semantic understanding of its data

7


Guidance Documents Department’s Data Resource Management Policy Draft enterprise data standardization procedures Representation Classes

Data Resource Management & Standardization Program

• Launched the Data Advisory Committee (DAC) June 2003• Launched various Tiger Teams

Enterprise Data Model Fully attributed Version 2 logical model produced and released December 2004

8 business functional areas plus geospatial Produced data subject areas and information classes Produced ERD

Formal Stewards Body Piloted stewardship roles with some business functional areas Launching Stewardship program 3rd quarter FY05

A Data Repository/RegistryCurrently using MS Access DB Will migrate to DOI’s Enterprise Architecture Repository when ready

DOI Data Architecture ComponentsDOI Data Architecture Components

8


The DOI Data Complexity Challenge(As of February 2003)

Same Data RequirementSame Data RequirementDifferent Functional/Business Needs and Different Data Descriptions

Records Management

Facility Management

Law Enforcement

Geospatial Indian Trust

FinanceFire Management

Recreation

Land Management

9


DOI Today

The DRM Program provides the governance, procedures and processes needed to ensure data quality and shareability across diverse domains.

The DRM Program provides the governance, procedures and processes needed to ensure data quality and shareability across diverse domains.

DOI DRM Core• Asset Master• Facility• Vendor

Finance

Wildland Fire

Recreation

•Materiel•Service•Activity

• Customer

•Alert •Closure

Communities of Practice (COP) form and create unique sets of shared data

Communities of Practice (COP) form and create unique sets of shared data

Nothing in place to prevent the creation of disparate data – redundant data and many data stovepipes

Nothing in place to prevent the creation of disparate data – redundant data and many data stovepipes

Each Business Line has unique dataEach Business Line has unique data

Reducing these characteristics: Increasing these characteristics:

10


Law Enforcement

Geospatial

Recreation

Indian Trust

FinanceFire Management

Shared & Distributed DataShared & Distributed Data(thru data standardization including(thru data standardization including

reuse of external standards)reuse of external standards) Records Management

Requires culture change, planning, and Requires culture change, planning, and implementationimplementationknow how to be effectiveknow how to be effective

Facility Management

LandManagement

THE DOI VISION:Enabling Business Lines with Shareable Data

11


DOI’s Implementation Strategyof the

FEA DRM

12


*SUBJECTAREA: Public Health

Business Sub-Functions:

Public Health Monitoring

Community of Practice

- Agencies that need to solve a common problem

- Agencies that need to share data - Agencies that perform similar processes

Topic of interest

*SUPER-TYPES: Categories of data used to perform business operations and shared by business functions

*INFORMATION EXCHANGE: Packages of meaningful data used as an input to decisions or generated as an output during process execution

Object Description

Relational Table

XML Schema

Facility

Location

Person

Disease

Business Process

External Request

Information Exchange

Information Exchange

*DATA ELEMENT DESCRIPTION

Agencies define their information and processing needs. This can be applied to the most granular level of information passed.

FEA DRM CONCEPTFEA DRM CONCEPT

13


DOI DRM Mapping to FEA DRMDOI DRM Mapping to FEA DRM(Illustration Example: RECREATION)(Illustration Example: RECREATION)

Physical Model

Schema(SQL)

CREATE TABLE RECAREA (RECAREA_ID CHAR(12) NOT NULL, RECAREA_NM VARCHAR(50) NOT NULL PRIMARY KEY (RECAREA_ID));CREATE UNIQUE INDEX XPKRECAREA ON RECAREA( RECAREA_ID ASC);

CREATE TABLE RECAREA_ACT (RECAREA_ID CHAR(12) NOT NULL, RECAREA_ACT_CD CHAR(2) NOT NULL, RECAREA_ACT_DESC VARCHAR(240) NULL, RECAREA_ACT_FEE VARCHAR(240) NULL);CREATE UNIQUE INDEX XPKRECAREA_ACT ON RECAREA_ACT( RECAREA_ID ASC, RECAREA_ACT_CD ASC);

*Information Exchange Package: PUBLIC RECREATION AMENITY REQUEST

*Subject Area: RECREATION

*Super Type: RECREATION AREA

XML Schema<?xml version="1.0" ?><xsd:Schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"><xs:element name="RecAreaActivity"> <xs:annotation> <xs:documentation>A recreational activity available at a Recreation Area. </xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="RecAreaActivityType" type="xs:string"> <xs:annotation> <xs:documentation>The code that denotes a specific kind

of Recreational Activity.</xs:documentation> </xs:annotation> </xs:element>

RECREATION-AREA

RECREATION-AREA DENTIFIER

RECREATION-AREA NAMERECREATION-AREA MAP URL TEXT

RECREATION-AREA IDENTIFIER (FK)RECREATION-ACTIVITY TYPE CODE

RECREATION-AREA-ACTIVITY DESCRIPTION TEXTRECREATION-AREA-ACTIVITY FEE DESCRIPTION TEXT

RECREATION-AREA-ACTIVITY

A1|AIR-HANG GLIDINGB1|BOATING-SAILINGB2|BOATING-CANOEINGB3|BOATING-KAYAKINGC1|CAMPING-CAMP SITESC2|CAMPING-FREE SPACEH1|HIKING-TRAILSH2|HIKING-FREE RANGES1|SWIMMING-LAKE, PONDS2|SWIMMING-POOL

DOMAIN:RECREATION-ACTIVITY TYPE CODE

Data Object:DOI Conceptual Data Entities (Standardized)

REGISTRY ENTRY:RECREATION-ACTIVITY TYPE CODE

DATA TYPE: CHARACTERLENGTH: 2DEFINITION:

The code that denotes a specific kind of Recreational Activity

CLASS WORD: CODE

METADATA REPOSITORYGlossary of Metadata

Data Property:DOI Conceptual Data Elements (Standardized)

Data Representation:

*Dat

a E

lem

ent

Des

crip

tio

n

DOI DRM uses term ‘Information Class’

*FEA DRM Components

14


PortalsPortals

External InterfacesExternal InterfacesExternal InterfacesExternal Interfaces

DeliveryDeliveryMechanismMechanism(e.g. XML)(e.g. XML)

Info Exchange/Info Exchange/Info SharingInfo Sharing

RequirementsRequirements

Data Data StandardizationStandardization

E-Gov ApplicationsE-Gov ApplicationsE-Gov ApplicationsE-Gov Applications

Legacy Migration PlansLegacy Migration Plans

XML Policy

DOI Lines of Business

Other Gov’tAgencies

DOI PartnersSynchronizationSynchronization& Implementation & Implementation

SupportSupport

Data Resource ManagementData Resource Management

Data Resource Management Policy

DOI Data Architecture FrameworkDOI Data Architecture Framework

15


Framework Components AmplifiedFramework Components Amplified(Sample products and services)(Sample products and services)

Data Data StandardizationStandardization

TransportTransportMechanismMechanism(e.g. XML)(e.g. XML)

Info Exchange/Info Exchange/Info SharingInfo Sharing

RequirementsRequirements

SynchronizationSynchronization& Implementation& Implementation

SupportSupport

• Interior Data Reference Model (DOI DRM)

• Common Data Standardization Procedures

• Data Repository

• Data Stewards Roster

• Interface Requirements

• Information Exchange Data Models

• Data Transformation Models

• Re-usable Reference Data Sets

• Information Exchange Packages

• Re-usable XML Tags & Schemas

• Replication Support

16


DOI Data Architecture Approach(Data Traceability)

BusinessArchitecture

Products

InformationRequirements

Identify andDefine

Structure &Standardize

ImplementedData Structures

OperationalSystems

Map, Assess,& Re-engineer

New Systems

RegisterMetadata

Interior Data Reference Model

Interior Metadata Repository

Data that is sharable & usable by multiple business units across the Enterprise

17


DOI Data Resource Management Goals

Reduce the life cycle cost of data through integration, standards, and the use of authoritative data sources

Provide a data reference model which addresses information important to the business of DOI

Provide a metadata registry to support data standardization and re-use

Provide a data resource management infrastructure to ensure data integrity, quality, and security

ISO 11179 facilitates the accomplishment of the first three goals.

ISO 11179 facilitates the accomplishment of the first three goals.

18


DOI DRM Activities and Roles

CoordinationCoordinationIs Is

KeyKey

Establish Data Requirements for Business Area

Bu

sin

ess

Rol

esB

usi

nes

s R

oles

Bu

sin

ess

Rol

esB

usi

nes

s R

oles

Data Integration Activities &Promote adopted data standards re-use

Information Distribution

Use Promoted Data and Systems

Identify Existing and Planned Data Sources

Identify Authoritative Sources for data

Implement Data Standards for Seamless Data Interchange

Promote Federal XML Schemas

Implement Adopted Data Standards in Systems

Architecture RolesArchitecture RolesArchitecture RolesArchitecture Roles

En

gineerin

g Roles

En

gineerin

g Roles

En

gineerin

g Roles

En

gineerin

g Roles

19


DOI Data Subject Area Mapping Process

Identify and Define Data Subject

Areas and Super Types 1

Existing Bureau and External Data Subject

Areas

DOI Data Architect and

DAC

Acquire System Artifacts and

SME Knowledge

2

• DEAR System Info.

• Database Schemas (Rec.)

Data Advisory Committee

(DAC)

DOI Data Architect and

DAC

Develop maps between Systems

and Subject Areas 3

• Artifacts• Data Subject Area Definitions

20


DOI DRM Entity Relationship DiagramDOI DRM Entity Relationship Diagram(Highly Shared Entities)(Highly Shared Entities)

Person-Name

IncidentEquipment

Organization-Association

Geospatial-Location

Country State

Capability

Tract

Location

Facility

Person-Association

Person

Organization

Descriptive-Location

Postal-Location

21


Geospatial Data Supporting the Business Lines

(What’s been documented so far in the DOI DRM)

Law EnforcementRecreation Indian TrustFinance

Fire Management

Best use of resources can be applied through Best use of resources can be applied through coordination of GIS data via the E-GIM initiative to the coordination of GIS data via the E-GIM initiative to the key business lines in the IEA. FGDC is a source.key business lines in the IEA. FGDC is a source.

Facility Management

• Recreation Area• Facility Location• Geospatial Location Data Set• Organization Location

• Organization Location

• Incident Location• Person Location• Evidence Location• Property Location• Geospatial Location Data Set• Org Location

• Public Land Survey System• Tract• Well Location• Geospatial Location Data Set• Organization Location

• Public Land Survey

System• Incident Location• Equipment Location• Geospatial Location Data Set• Organization Location

• Facility Location• Geospatial Location Data Set• Organization Location

22


DOI Data Architecture Role in Modernization Blueprints

Discovery of data sharing opportunities and redundancies begins by mapping systems to Data Subject Areas and Super Types.

Financial System A

Recreation System B

Fire Management

System C

Super Type A

Super Type B

Super Type C BRM Business

Need

Data Sharing Opportunitie

s

IdentifyCommon DataData Subject Area

AB

23


The DOI DRM Process

Recreation

Identify data requirementsIdentify data requirements

Law Enf.

Fire

Facility

XML Schemas / Exchange Packages / Database Schemas

Role of DOI DRM: Harmonize data

requirements across business lines & facilitate

data standardization

Role of DOI DRM: Harmonize data

requirements across business lines & facilitate

data standardization

Implement and use adopted data standards

and authoritative sources

Implement and use adopted data standards

and authoritative sources

Finance

IMARSRqmts

IMARSSystem/DOJ

Reporting

Source of harmonized information that can be

used by FBMS Master Data

Rec.govSystem

Fire Blueprint Implementation

External Data Standards – Candidates for Adoption

• NetWeaver• Master Data

Record

Original Sources:• JFMIP• USSGL• TFM• SFFAS

• GOS Fire Channel

24


DOI Data Infrastructure

25


Who Implements the Data Architecture?

DOI Data Advisory Committee (DAC)

– Represent the interest of their organization to help build enterprise perspective

– Bring the strengths of their knowledge and background to the group

– Vote on crucial enterprise matters pertaining to data

11 Voting Members of the DAC

Minerals Management Service (MMS)

U.S. Fish and Wildlife Service (FWS)

U.S. Geological Survey (USGS)

National Park Service (NPS)

Bureau of Reclamation (BOR)

Bureau of Indian Affairs (BIA)

National Business Center (NBC)

Bureau of Land Management (BLM)

Office of the Special Trustee (OST)

Office of Surface Mining (OSM)

Chaired By the Office of the Secretary (OS)

26


DOI Data Resource Management Roles and Relationships

DAC

DOI Data Architect

Principal Data Stewards

Bureau Data Architect

Database Administrator(DBA- provides access and designs/develops interfaces and connections)

DOI DataArchitecture

Guidance Body

Subject Matter Expert(SME - analyzes and defines data requirements)

Executive Sponsor

Appoints Principals &ensures adequate funding

Coordinates the creation or review of proposed data standardswith all business data stewards & Bureau Data Architects for a business line. Maintains current DOI dataStandards for their respective business line. Submits proposed dataStandards to DOI Data Architect for formal review process.

Coordinates implementation of newData standards with SME and DBAin systems supporting a business line. Ensures data security & dataquality requirements for each dataStandard.

Maintains & publishes the DOI DRMin coordination with Principal Data Stewards andBureau Data Architects.Promotes the Data Program.

Assists the DOI Data Architect in theimplementation of the Data Program among Bureaus in coordinationwith Principal Data Stewards and Business Data Stewards. MaintainsBureau unique data standards incoordination with business datastewards.

(Data Advisory Committee)

Business Data Steward

DOI E-GovTeam

27


Development of Formal Data Stewardship (Current Status)

Law Enforcement

Recreation

Indian TrustFinance

Fire Management

Records Management

C. GrymesC. Grymes J. GegenJ. Gegen??? S. HawkinsS. Hawkins

E-GIM Team E. McCeneyE. McCeney

Principal Data Steward for Each Business Line

Facility ManagementGeospatial

???

??????

28


DOI Data and

Information Sharing

29


The Data & Information Sharing ApproachThe Data & Information Sharing Approach

• Identify data and information most important to share

• Standardize the data in collaboration forums following Department procedures

• Publish and promote use of the official standard data

30

DOI Data Standardization Procedures Overview

Triggers(examples)

• Business Process Improvement Project• Modernization Blueprint Project• Info Exchange Project• E-Gov Project

• Review business references and artifacts• Include Principal Data Steward(s)

• Collect,• Identify,• Design, and• Document data requirements.

• Perform business and technical stewardship Coordination

• Develop, and• Submit Data Submission Package withconcurrence of Principal Data Steward

• Formally conduct cross-functional review, and• Adopt proposed data standards• Formal Review period: 3 weeks

• Resolve comments with Principal Data Steward(s)• Resolution period: 2 weeks

• Implement adopted data standards

KEY Points• Standardizing/ adopting data that is shared or exchanged.• Not always a single implementation of a standard

31


Some Rules Followed from ISO 11179

NAMING RULES RULES FOR DEFINITIONS

• Name is always unique

• Be clear, accurate, and self explanatory

• Name is always singular

• Always end with a representation term (i.e. class word)

• Include only alphabetic characters, and spaces

• Unless commonly used, spell out all acronyms

• Avoid circular reasoning (Don’t repeat the name in the definition)

• Describe the “what”, not the “how”, “when”, “where”, or “who”

• Data elements must have only one clear and concise meaning (Avoid multiple meanings/concepts)

• Have only one interpretation Avoid ambiguity

• Describe purpose & usefulness without using physical qualities

• Stated in the singular• Avoid abbreviations unless commonly understood

32


DOI Representation Class (Controlled Word List based on ISO 11179)

Amount Code Coordinate Date Identifier Measurement Name Number Quantity Rate Text Time

33


Data Architecture Communication(http://www.doi.gov/ocio/architecture/index.html)

Home | Feedback | Accessibility| Thursday, September 23, 2004

Interior Enterprise Architecture Step 3: Analysis

Interior Reference Models Return to IEA home

PRM | BRM | SRM | DRM | TRM

PRM

The Interior's PRM relates the business goals to the mission, and defines measurements to check whether the business is lined up with the mission.

DOI Strategic Plan

Supporting PRM Reports

DOI PRM Outcomes End Outcome Measures DOI PRM Intermediate Outcome Measures FEA PRM to DOI PRM End Outcome FEA PRM to DOI PRM Intermediate Outcome

BRM

The Interior's BRM is the business, the actual job the organization does. The BRM has to drive the SRM, DRM, and TRM; if you choose technology without looking at whether your business needs it, you'll end up with a lot of expensive junk. The BRM is itself driven by the PRM, because the business is useless if it doesn't accomplish the mission.

FEAPMO

Home of OMB

models

OMB reference models

PRM

BRM

SRM

TRM

DRM

Try out ABC

Try out the Activity

Based Costing management system, used to record architecture accomplishments.

PMB Home

About Hord Tipton

Overview

Strategic Plan

Progams

Enterprise Architecture

IT Capital Planning

Section 508

Records Management

Privacy

FOIA

Enterprise Licensing Agreements/Contracts

Government Paperwork Elimination Act - GPEA

DOI DRM Artifacts posted on Interior’s EA web page.High level Data Architecture (i.e. data subject areas)and data models are in the Department’s EA Repository (DEAR).

34


Interim DOI Data Repository(MS Access Database)

Easier to track data life cycle, search, sort, parse, and/or map data elements for analysis work with MS Access DB

35


Relationship of Interior DRM to otherInterior EA Components & Governance Teams

DRM

BRMLINES OF BUSINESSSubfunctions• Recreation• Finance• Law Enforcement

Recreation-AmenityRecreation-Amen Name

Recreation-Amen Description TextFacility Agency Code

Provides

TRM

SRM

Product NameErwinOracle XMLEtc.

Data MartsData WarehousesInformation SystemsKnowledge ManagementRecords Management

Interior Business Architecture Team(IBAT)

TRM Domain Arch. Teams

Data Advisory Committee(DAC)

PRM

Facility NameFacility Type Code

FacilityFacility Identifier

Interior Architecture Work Group (IAWG)

Subject AreaRECREATION

Interior Chief Technology Officer Council

INVESTMENT REVIEW BOARD (IRB)

36


DOI DRM Implementation Examples

37


DOI DRM Implementation - RecreationDOI DRM Implementation - RecreationRequirements & Challenges DOI DRM Role Outcomes

Needed a basis for data sharing among multiple Federal, State, Local &

Commercial parties

Needed a basis for data sharing among multiple Federal, State, Local &

Commercial parties

Share data from multiple business lines

Share data from multiple business lines

Translate data sharing to a database and XMLTranslate data sharing to a database and XML

Must be easily extensible to

accommodate new requirements

Must be easily extensible to

accommodate new requirements

Provided a basis for requirements gathering

and data analysis – Rapid Standardization


and data analysis – Rapid Standardization

Provided a mechanism for discussion and

validation amongst data sharing partners

Provided a mechanism for discussion and

validation amongst data sharing partners

Identification of data sharing opportunitiesIdentification of data sharing opportunities

Translation of conceptual analysis into

database and XML Schema

Translation of conceptual analysis into

database and XML Schema

All parties agree to data sharing requirements –

greatly increased collaboration

All parties agree to data sharing requirements –

greatly increased collaboration

Integrated data requirements and data sharing across business

lines

Integrated data requirements and data sharing across business

lines

Extensibility proven through inclusion of Trails data standard

Extensibility proven through inclusion of Trails data standard

Implemented database and XML Schema

Implemented database and XML Schema

38


DOI DRM Implementation – Law EnforcementDOI DRM Implementation – Law EnforcementRequirements & Challenges DOI DRM Role Outcomes

Needed to develop comprehensive set of data requirements for

new LE Systems Procurement

Needed to develop comprehensive set of data requirements for

new LE Systems Procurement

Provide an extensible standard for the

concept of an Incident, whether it is LE,

Emergency Management, Search &

Rescue, etc.

Provide an extensible standard for the

concept of an Incident, whether it is LE,

Emergency Management, Search &

Rescue, etc.

Must integrate with Department of Justice

XML Schema

Must integrate with Department of Justice

XML Schema


and data analysis


and data analysis

Model provided platform for integration of Justice

standards and DOI requirements

Model provided platform for integration of Justice

standards and DOI requirements

Inclusion of an extensible concept for

an “incident.”

Inclusion of an extensible concept for

an “incident.”

Provided a clear set of data requirements to be included in procurement

documents

Provided a clear set of data requirements to be included in procurement

documents

Justice XML data standards have been

included. Provides ability for data exchange using

emerging standard

Justice XML data standards have been

included. Provides ability for data exchange using

emerging standard

Model currently being extended to include

Emergency Management, Security

and Organizations

Model currently being extended to include

Emergency Management, Security

and Organizations

39


DOI DRM Implementation – Indian TrustDOI DRM Implementation – Indian Trust

Requirements & Challenges DOI DRM Role Outcomes

Needed to identify and analyze common data

across all Trust systems

Needed to identify and analyze common data

across all Trust systems

Provide data requirements for procurement of

modernized Trust systems

Provide data requirements for procurement of

modernized Trust systems

Needed to identify redundancies

Needed to identify redundancies

Provide a standard for reverse engineering and data standard gathering

Provide a standard for reverse engineering and data standard gathering

Provide a means to map data standards to

system records and fields and report on

redundancies

Provide a means to map data standards to

system records and fields and report on

redundancies

Served to provide a consistent set of data

requirements to be included in procurement

requirements

Served to provide a consistent set of data

requirements to be included in procurement

requirements

Provided a clear set of non-redundant, consistent data

standards across the Trust business line

Provided a clear set of non-redundant, consistent data

standards across the Trust business line

Most Trust systems were mapped to the DOI DRM

Trust data standard. Redundancies were easily

identified

Most Trust systems were mapped to the DOI DRM

Trust data standard. Redundancies were easily

identified

DOI DRM continues to provide sets of data

requirements as procurement proceeds

DOI DRM continues to provide sets of data

requirements as procurement proceeds

40


DOI DRM Implementation – Records MgmtDOI DRM Implementation – Records MgmtRequirements & Challenges DOI DRM Role Outcomes

Needed to identify the core data requirements necessary to conduct

the Records Management business

process

Needed to identify the core data requirements necessary to conduct

the Records Management business

process

Provide for possible data reference model

across the Federal Government

Provide for possible data reference model

across the Federal Government

Provide for future analysis of data

sharing opportunities and reduction of

redundancies

Provide for future analysis of data

sharing opportunities and reduction of

redundancies


and data analysis


and data analysis

DOI DRM Methods and Techniques provide a

flexible mechanism for data sharing analysis

DOI DRM Methods and Techniques provide a

flexible mechanism for data sharing analysis

DOI DRM Methods and Techniques are based on

ISO 11179 and other standards, ensuring a basis for Federal-wide

analysis

DOI DRM Methods and Techniques are based on

ISO 11179 and other standards, ensuring a basis for Federal-wide

analysis

With one analysis session, provided an extension to the DOI

DRM that clearly captures the core data

requirements for Records Management.

With one analysis session, provided an extension to the DOI

DRM that clearly captures the core data

requirements for Records Management.

Model to be used as a basis for analysis of data sharing and redundancies

Model to be used as a basis for analysis of data sharing and redundancies

Model has been circulated among

several Federal Agencies

Model has been circulated among

several Federal Agencies

41


Summary

DOI Data Architecture work is evolutionary and maps to the concepts in FEA DRM and ISO 11179

DOI DRM development tied to DOI EA priority business lines and validated by communities of practice

DOI DRM serves as the basis for database design, data integration, and XML artifacts (RECREATION initial proof-of-concept)

Effective Data Stewardship is critical to success

“I am careful not to confuse excellence with perfection. Excellence I can reach for, perfection is God’s business.”

---- Michael J. Fox

Unification & Simplification Through: C ooperation I nnovation O pportunity DOI Data Reference Model...

Documents

Transcript of Unification & Simplification Through: C ooperation I nnovation O pportunity DOI Data Reference Model...