The Performance Institute Presentation (13 Nov 03)

1
DOI Data Reference Model Overview May 10, 2005

2
Presentation Contents

• Background
• DOIs FEA DRM implementation strategy
• DOIs Data Infrastructure
• DOIs 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
DOIs Approach

• Follow OMBs model (i.e. 5 key federal lines of
  business)
• Supplement FEA DRM with DOI level guidance
• DOIs 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
DOI Data Architecture Components

• Guidance Documents
• Departments 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

8
The DOI Data Complexity Challenge(As of
February 2003)
Finance
Fire Management
Law Enforcement
Records Management
Facility Management
Geospatial
Indian Trust
Land Management
9
DOI Today
Reducing these characteristics
Increasing these characteristics
Each Business Line has unique data
Wildland Fire
Communities of Practice (COP) form and create
unique sets of shared data

• Alert
• Closure

DOI DRM Core

• Materiel
• Service
• Activity

• Asset Master
• Facility
• Vendor

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

• Customer

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

THE DOI VISION Enabling Business Lines with
Shareable Data
Recreation
Finance
Fire Management
Shared Distributed Data (thru data
standardization including reuse of external
standards)
Law Enforcement
Records Management
Facility Management
Land Management
Indian Trust
Geospatial
Requires culture change, planning, and
implementation know how to be effective
11
DOIs Implementation Strategyof theFEA DRM
12
FEA DRM CONCEPT
13
DOI DRM Mapping to FEA DRM(Illustration Example
RECREATION)
Subject Area RECREATION
DOI DRM uses term Information Class
Super Type RECREATION AREA
Information Exchange Package PUBLIC RECREATION
AMENITY REQUEST
Data Object DOI Conceptual Data Entities
(Standardized)
RECREATION-AREA
Data Element Description
Data Property DOI Conceptual Data Elements
(Standardized)
RECREATION-AREA-ACTIVITY
Data Representation
FEA DRM Components
14
DOI Data Architecture Framework
Data Resource Management
Portals
External Interfaces
E-Gov Applications


Legacy Migration Plans
Data Resource Management Policy
XML Policy
Other Govt Agencies
Info Exchange/ Info SharingRequirements
Delivery Mechanism (e.g. XML)
Synchronization Implementation Support
Data Standardization
DOI Partners
DOI Lines of Business
15
Framework Components Amplified (Sample products
and services)


Transport Mechanism (e.g. XML)
Info Exchange/ Info SharingRequirements
Synchronization Implementation Support
Data Standardization

• 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)
Top Down...
Business Architecture Products
Interior Metadata Repository
Interior Data Reference Model
Identify and Define
Structure Standardize
Map, Assess, Re-engineer
Implemented Data Structures
Information Requirements
Register Metadata
Operational Systems
New Systems
Bottom Up...
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.
18
DOI DRM Activities and Roles
Data Integration Activities Promote adopted
data standards re-use
Architecture Roles
Identify Authoritative Sources for data
Promote Federal XML Schemas
Identify Existing and Planned Data Sources
Implement Data Standards for Seamless Data
Interchange
Business Roles
Coordination Is Key
Engineering Roles
Establish Data Requirements for Business Area
Information Distribution
Implement Adopted Data Standards in Systems
Use Promoted Data and Systems
19
DOI Data Subject Area Mapping Process
20
DOI DRM Entity Relationship Diagram(Highly
Shared Entities)
21
Geospatial Data Supporting the Business
Lines (Whats been documented so far in the DOI
DRM)
Law Enforcement
Fire Management
Facility Management
Recreation
Indian Trust
Finance

• 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

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

• Organization
• Location

Best use of resources can be applied through
coordination of GIS data via the E-GIM initiative
to the key business lines in the IEA. FGDC is a
source.
22
DOI Data Architecture Role in Modernization
Blueprints
Identify Common Data
Data Subject Area A
B
Super Type A
Super Type B
Super Type C
BRM Business Need
Financial System A
Recreation System B
Data Sharing Opportunities
Fire Management System C
Discovery of data sharing opportunities and
redundancies begins by mapping systems to Data
Subject Areas and Super Types.
23
The DOI DRM Process
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

26
DOI Data Resource Management Roles and
Relationships
Appoints Principals ensures adequate funding
Maintains publishes the DOI DRM in coordination
with Principal Data Stewards and Bureau Data
Architects. Promotes the Data Program.
(Data Advisory Committee)
DOI Data Architecture Guidance Body
Coordinates the creation or review of proposed
data standards with all business data stewards
Bureau Data Architects for a business line.
Maintains current DOI data Standards for their
respective business line. Submits proposed
data Standards to DOI Data Architect for formal
review process.
Assists the DOI Data Architect in
the implementation of the Data Program among
Bureaus in coordination with Principal Data
Stewards and Business Data Stewards.
Maintains Bureau unique data standards
in coordination with business data stewards.
Business Data Steward
Coordinates implementation of new Data standards
with SME and DBA in systems supporting a business
line. Ensures data security data quality
requirements for each data Standard.
27
Development of Formal Data Stewardship (Current
Status)
Recreation
Finance
Law Enforcement
Indian Trust
Fire Management
???
S. Hawkins
C. Grymes
J. Gegen
???
Principal Data Steward for Each Business Line
E. McCeney
E-GIM Team
???
Facility Management
Records Management
Geospatial
28
DOI Data and Information Sharing
29
The 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

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

• Avoid circular reasoning
• (Dont 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

• 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

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.g
ov/ocio/architecture/index.html)
DOI DRM Artifacts posted on Interiors EA web
page. High level Data Architecture (i.e. data
subject areas) and data models are in the
Departments 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 other Interior EA
Components Governance Teams
36
DOI DRM Implementation Examples
37
DOI DRM Implementation - Recreation
Requirements Challenges
DOI DRM Role
Outcomes
Needed a basis for data sharing among multiple
Federal, State, Local Commercial parties
Provided a basis for requirements gathering and
data analysis Rapid Standardization
All parties agree to data sharing requirements
greatly increased collaboration
Provided a mechanism for discussion and
validation amongst data sharing partners
Integrated data requirements and data sharing
across business lines
Share data from multiple business lines
Must be easily extensible to accommodate new
requirements
Extensibility proven through inclusion of Trails
data standard
Identification of data sharing opportunities
Translation of conceptual analysis into database
and XML Schema
Translate data sharing to a database and XML
Implemented database and XML Schema
38
DOI DRM Implementation Law Enforcement
Requirements Challenges
DOI DRM Role
Outcomes
Needed to develop comprehensive set of data
requirements for new LE Systems Procurement
Provided a basis for requirements gathering and
data analysis
Provided a clear set of data requirements to be
included in procurement documents
Must integrate with Department of Justice XML
Schema
Justice XML data standards have been included.
Provides ability for data exchange using emerging
standard
Model provided platform for integration of
Justice standards and DOI requirements
Provide an extensible standard for the concept of
an Incident, whether it is LE, Emergency
Management, Search Rescue, etc.
Model currently being extended to include
Emergency Management, Security and Organizations
Inclusion of an extensible concept for an
incident.
39
DOI DRM Implementation Indian Trust
Outcomes
Requirements Challenges
DOI DRM Role
Outcomes
Needed to identify and analyze common data across
all Trust systems
Provide a standard for reverse engineering and
data standard gathering
Provided a clear set of non-redundant, consistent
data standards across the Trust business line
Provide a means to map data standards to system
records and fields and report on redundancies
Most Trust systems were mapped to the DOI DRM
Trust data standard. Redundancies were easily
identified
Needed to identify redundancies
Provide data requirements for procurement of
modernized Trust systems
Served to provide a consistent set of data
requirements to be included in procurement
requirements
DOI DRM continues to provide sets of data
requirements as procurement proceeds
40
DOI DRM Implementation Records Mgmt
Requirements Challenges
DOI DRM Role
Outcomes
Outcomes
With one analysis session, provided an extension
to the DOI DRM that clearly captures the core
data requirements for Records Management.
Provided a basis for requirements gathering and
data analysis
Needed to identify the core data requirements
necessary to conduct the Records Management
business process
DOI DRM Methods and Techniques provide a flexible
mechanism for data sharing analysis
Model to be used as a basis for analysis of data
sharing and redundancies
Provide for future analysis of data sharing
opportunities and reduction of redundancies
DOI DRM Methods and Techniques are based on ISO
11179 and other standards, ensuring a basis for
Federal-wide analysis
Model has been circulated among several Federal
Agencies
Provide for possible data reference model across
the Federal Government
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 Gods business. ----
Michael J. Fox
42
QUESTIONS
Suzanne Acar Interior Data Architect Department
of the Interior Office of the Chief Information
Officer Phone [phone] E-mail
suzanne_acar_at_ios.doi.gov