Discussion on the Federal Enterprise Architecture Data Reference Model FEADRM

1
Discussion on the Federal Enterprise Architecture
- Data Reference Model (FEA-DRM)

• By Brand Niemann, Owen Ambur, Jim Feagans,
• Craig Tanner, and Robert Chadduck
• Taxonomy Tuesdays
• Tuesday, May 24, 2005, 9 - 11 a.m.
• National Academies of Science
• 500 Fifth St N.W., Washington, D.C.

2
Overview

• 1. What is the FEA?
• 2. What is the DRM?
• 3. What is the new DRM Process?
• 4. What is the relationship between the DRM and
  Section 207 (d) of the eGov Act of 2002?
• 5. What is the first DRM Public Forum?
• 6. What is SICoPs role in the DRM?
• 7. What is the XML CoPs role in the DRM?
• Owen Ambur, Co-Chair of the XML CoP
• 8. What are the federated taxonomies in the DRM
  Volume 5
• Jim Feagans, Craig Tanner, and Robert Chadduck

3
1. What is the FEA?

• To facilitate efforts to transform the Federal
  Government to one that is citizen-centered,
  results-oriented, and market-based, the Office of
  Management and Budget (OMB) is developing the
  Federal Enterprise Architecture (FEA), a
  business-based framework for Government-wide
  improvement.
• The FEA is being constructed through a collection
  of interrelated reference models designed to
  facilitate cross-agency analysis and the
  identification of duplicative investments, gaps,
  and opportunities for collaboration within and
  across Federal Agencies.
• See http//www.whitehouse.gov/omb/egov/a-1-fea.htm
  l

4
1. What is the FEA?
See the Enterprise Architecture Reference Models
and the Assessment Framework at
http//www.whitehouse.gov/omb/egov/e-5-documents.h
tml. Data Reference Model (DRM) Volume 1.0
Release Document This document describes at an
aggregate level the data and information that
support government program and business line
operations. This model enables agencies to
describe the types of interaction and exchanges
that occur between the Federal Government and
citizens. See http//www.whitehouse.gov/omb/egov/d
ocuments/fea-drm1.PDF
5
2. What is the DRM?

• The DRM categorizes government information into
  greater levels of detail. It also establishes a
  classification for Federal data and identifies
  duplicative data resources. A common data model
  will streamline information exchange processes
  within the Federal government and between
  government and external stakeholders.
• Volume One of the DRM provides a high-level
  overview of the structure, usage, and
  data-identification constructs. This document
• Provides an introduction and high-level overview
  of the contents that will be detailed in Volumes
  1-4 of the model (see slide 9)
• Encourages Community of Interest development of
  the remaining volumes and
• Provides the basic concepts, strategy, and
  structure to be used in future development.
• The DRM is the starting point from which data
  architects should develop modeling standards and
  concepts. This volume establishes the foundation,
  which describes essential components, for
  subsequent DRM Volumes. These combined volumes
  support data classification - thus enabling
  horizontal and vertical information sharing.

See http//www.whitehouse.gov/omb/egov/a-5-drm.htm
l
6
2. What is the DRM?

• Table of Contents
• Executive Summary
• Overview of the DRM
• DRM Foundation
• Use of the DRM
• DRM Roadmap
• Glossary
• Footnotes
• List of Exhibits
• Exhibit A DRM Structure (see next slide)
• Exhibit B Outcomes of the DRM
• Exhibit C DRM Approach
• Exhibit D Information Exchange Package
• Exhibit E DRM Example (see next slide)
• Exhibit F DRM - Policy and Legislation
  Relationships
• Exhibit G DRM Collaboration Process
• Exhibit H Use of the DRM
• Exhibit I DRM Roadmap
• Exhibit J DRM Future Volume Topics

7
2. What is the DRM?
8
2. What is the DRM?

• Categorization of Data The DRM establishes an
  approach to the categorization of data through
  the use of a concept called Business Context. The
  business context represents the general business
  purpose of the data. The business context uses
  the FEA Business Reference Model (BRM) as its
  categorization taxonomy.
• Exchange of Data The exchange of data is enabled
  by the DRMs standard message structure, called
  the Information Exchange Package. The information
  exchange package represents an actual set of data
  that is requested or produced from one unit of
  work to another. The information exchange package
  makes use of the DRMs ability to both categorize
  and structure data.
• Structure of Data To provide a logical approach
  to the structure of data, the DRM uses a concept
  called the Data Element. The data element
  represents information about a particular thing,
  and can be presented in many formats. The data
  element is aligned with the business context, so
  that users of an agencys data understand the
  datas purpose and context. The data element is
  adapted from the ISO/IEC 11179 standard.

9
2. What is the DRM?

• Volume I Business Context, Core DRM Elements,
  Information Exchange Packages, Data Element
  Definition
• Volume II Use of the DRM in EA, Information
  Indexing, Federated Data Classification,
  Information Categories

• Volume III Security of Data, Data Patterns,
  Data Exchange Requirements.
• Volume IV Metadata Requirements, Data
  Structures, Data Standardization.

10
3. What is the new DRM Process?

• An Open Community of Practice
• Led by
• Michael Daconta, DHS, Metadata Program Manager.
• Susan Turnbull, GSA, Co-Chair of the AIC Emerging
  Technology Subcommittee.
• Andy Hoskinson, FEA-PMO, UNISYS Support
  Contractor.
• Support by Wiki Technology
• See http//colab.cim3.net/cgi-bin/wiki.pl?DataRefe
  renceModel
• See agency comments linked to document.
• Organized by a Success Strategy
• See http//colab.cim3.net/file/work/drm/DRM-Succes
  sStrategy.ppt
• Address data evolution, revise structure,
  information sharing use cases, formal taxonomies,
  XML CoP SICoP Profiles, Workshops/Public
  Forums.
• Three tiers of participation
• Public, Team, and Executive Committee.
• With a DRM Project Coordinator
• cheryl.manns_at_associates.dhs.gov

11
3. What is the new DRM Process?

• Change the volume strategy from the current plan
  by creating cohesive volumes around functional
  lines
• Volume 1. Overview
• LEAD Michael Daconta, DHS
• Volume 2. DRM Management Strategy
• LEAD Suzanne Acar, DOI
• Volume 3. Data Description
• LEAD Larry Fitzwater, EPA
• Volume 4. Data Sharing
• LEAD Bryan Aucoin, IC CIO
• Volume 5. Data Context
• LEAD James Feagans, DOJ
• Note Sections in each of the above volumes on
  Security Privacy

12
3. What is the new DRM Process?
Revised DRM Structure V0.2 - Requires
distinction between metamodel and model
13
3. What is the new DRM Process?

• OWL Listing
• lt?xml version"1.0"?gt ltrdfRDF xmlnsrdf"http//w
  ww.w3.org/1999/02/22-rdf-syntax-ns"
  xmlnsxsd"http//www.w3.org/2001/XMLSchema"
  xmlnsrdfs"http//www.w3.org/2000/01/rdf-schema"
  xmlnsowl"http//www.w3.org/2002/07/owl"
  xmlnsdaml"http//www.daml.org/2001/03/damloil"
  xmlns"http//www.owl-ontologies.com/unnamed.owl
  " xmlnsdc"http//purl.org/dc/elements/1.1/"
  xmlbase"http//www.owl-ontologies.com/unnamed.ow
  l"gt ltowlOntology rdfabout""/gt ltowlClass
  rdfID"Transportation"/gt ltowlClass
  rdfID"AirVehicle"gt ltrdfssubClassOf
  rdfresource"Transportation"/gt lt/owlClassgt
  ltowlClass rdfabout"GroundVehicle"gt
  ltrdfssubClassOf rdfresource"Transportation"/gt
  lt/owlClassgt ltowlClass rdfabout"Automobile"gt
  ltrdfssubClassOfgt ltowlClass rdfID"GroundVehicle
  "/gt lt/rdfssubClassOfgt Etc.

Transportation Class Hierarchy
Source Formal Taxonomies for the U.S.
Government, Michael Daconta, Metadata Program
Manager, US Department of Homeland Security,
XML.Com, http//www.xml.com/pub/a/2005/01/26/formt
ax.html
14
3. What is the new DRM Process?

• DRM Working Group Meeting, May 19, 2005
• OMB Presentation on Section 207 (d) of the E-Gov
  Act of 2002
• Data Management Strategy Presentation (see next
  slide)
• Discussion Items
• 1. XML Schema Strategy Overview
• 2. Adoption of the XML Schema
• 3. How taxonomies are represented in the XML
  Schema
• See slides 16-17.
• 4. Understanding the requirements for October 17,
  2005, deadline
• 5. Things missing from existing Schema (i.e.
  glossaries, searchable identifiers)
• 6. Level of detail in the management process
• 7. Explanation of Schema in a layered approach
• 8. Recommendation to collapse 5 volumes to 2
• Optional registration/funding requests
• 9. DRM goals and objectives (authoritative data
  sources and interoperability via unique
  identifiers)

15
3. What is the new DRM Process?
Outcome-based Data Management Strategy (Notional)
Collection
Registration
Harmonization Standardization
Measure

• Collection Each organization creates a DRM XML
  Document. Scope is info currently shared or plan
  to share in a year.
• Registration A DRM Registry that is either
  federated or centralized. Core.gov is a
  candidate.
• Harmonization Standardization Achieve
  semantic understanding to support the business
  requirement.
• Measure Were the business goals achieved?

16
3. What is the new DRM Process?

• Data Reference Model Taxonomy (draft)
• Data Description
• Data
• Structured Data
• Entity (0-M) (Entity Name, Attributes, Attribute
  Name, Datatype, Relationships, Relationship Name,
  Entity Referenced)
• Unstructured Data
• Resource (Title, Identifier, Date, Creator,
  Format, Description, Source, Subject, Type, Link
  to another resource, Link to taxonomy and node)
• Semi Structured Data
• Entity, Resource
• Data Sources (0-M)
• Data Source (0-M)
• Owning Agency, Steward, Location, Data Source
  Type, Point of Contact
• Data Sharing
• Exchanges (0-M)
• Exchange Package(0-M) (Sender, Recipient,
  Exchange Frequency, Classification, Transaction
  Type, Status, Confidentiality, Business Rules
  (0-M)-Business Rule Language, Entity References
  (0-M)-Entity Reference ID

17
3. What is the new DRM Process?

• Data Reference Model Taxonomy (continued)
• Data Description (continued)
• Data Sharing (continued)
• Data Access
• ..
• Data Context
• Taxonomies
• Taxonomy (0-M) Node (0-M) (Node Name, Node
  Definition, Node Children)
• FEA Mapping
• ..
• Data Standards (0-M)
• ..

18
4. What is the relationship between the DRM and
Section 207 (d) of the eGov Act of 2002?

• The FEA/PMO and OMB requested the two activities
  be integrated on May 19th.
• Recommendations for Section 207 (d) were
  submitted to OMB by the Categorization of
  Government Information Working Group last
  December 2004
• See http//www.cio.gov/documents/ICGI.html
• H.R. 2458, E-Government Act of 2002, Selected
  Portions of Interest to the XML Working Group
• http//xml.gov/documents/completed/eGovXML.htm
• See references to XML, directory (taxonomy of
  subjects), five pilot projects that integrate
  data elements, etc.

19
5. What is the first DRM Public Forum?

• Date June 13, 2005 Time 830 a.m.- 415 p.m.
  Location MITRE, McLean, VA Logistics Advance
  registration for clearance by security is
  required. and Contact susan.turnbull_at_gsa.gov,
  202-501-6214.
• DRAFT Agenda
• 830 a.m. - Check-in
• 845 a.m. - Welcome and Introduction Susan
  Turnbull, GSA, Emerging Technology Subcommittee
  Co-Chair and Architecture and Infrastructure
  Committee representative to DRM Working Group
• 900 a.m. - What We Need Data Reference Model
  Process Overview and Invitation to Participate in
  the FEA DRM Success Strategy - Michael Daconta,
  Meta Data Program Manager, Center of Excellence,
  DHS and Lead, DRM WG
• 945 a.m. - How Well Get There Business
  Management Strategy, including introduction to
  Candidate Use Cases - Michael Daconta, DHS,
  Suzanne Acar, DoI and Jim Feagans, DoJ
• 1015 a.m. - BREAK
• 1030 a.m. - How Well Get There Technical
  Management Strategy, including introduction to
  DRM Schema - Mike Daconta, DHS and Rick Jordan,
  FAA
• 1150 p.m. - LUNCH

20
5. What is the first DRM Public Forum?

• DRAFT Agenda (continued)
• 100 p.m. - How to Build Readiness Advancing
  Discernment and Value Through Implementation
  Profiles and Pilots Brand Niemann, EPA, Chair,
  Semantic Interoperability Community of Practice
• 300 p.m. - BREAK
• 315 p.m. - Why It Matters Reflections on
  Readiness and Relevance from Institutions and
  Initiatives Planning Early DRM Adoption
• National Infrastructure for Community Statistics
• National Health Information Network
• National Information Exchange Model
• National Institute for Standards and Technology
• National Archives and Records Administration
• 415 p.m. - ADJOURN

21
6. What is SICoPs role in the DRM?

• Brand Niemann, Chair, Semantic Interoperability
  Community of Practice
• The State of SICoP
• See http//web-services.gov/scope05162005.ppt,
  especially slides 44, 48, 60, 66, and 77.
• Develop Semantic Technology Profiles and Pilots
• Treat and integrate all three types of data
  (unstructured, semi-structured, and structured),
  using W3C Semantic Web Standards (RDF, OWL), to
  support machine processing and inferences
• See Data architectures future, Federal Computer
  Week, April 18, 2005, at http//fcw.com/article885
  82-04-18-05-Print
• New Ontology and Taxonomy Coordination Working
  Group (ONTAC WG)
• Suggest you invite WG Lead, Pat Cassidy,
  Ontologist, MITRE, to speak.
• See http//colab.cim3.net/cgi-bin/wiki.pl?WikiHome
  PagenidEU
• A SICoP member comment at the May 17th Workshop
• The DRM XML Schema and Taxonomy is reinventing
  RDF/OWL!
• Mike Daconta response Start simpler for
  agencies, but be consistent with RDF/OWL, and
  move towards that.

22
6. What is SICoPs role in the DRM?

• Strategic Directions
• June 3, 2004 Fourth Quarterly Emerging Technology
  Components Conference
• GAO Report The Federal Enterprise Architecture
  and Agencies Enterprise Architectures Are Still
  Maturing, May 19, 2004 (excerpts)
• The FEA is more akin to a classification scheme
  (taxonomy) for government operations than a true
  enterprise architecture.
• Since the term are not well-defined, GAO asks if
  the expected relationships between the FEA and
  agencies architecture is clear enough for
  agencies to map and align their architectures
  with the FEA.
• The agencies architectures may not provide
  sufficient content for driving implementation of
  system.

23
6. What is SICoPs role in the DRM?

• Strategic Directions (continued)
• June 3, 2004 Fourth Quarterly Emerging Technology
  Components Conference
• OMB Enterprise Architecture Assessment V 1.0
  Guidelines, May 15, 2004 (excerpt)
• Node Diagram Diagrams depicting the
  interdependencies between elements of the
  architecture. Node diagrams can be used to
  describe the interaction of business functions
  with technology components, the relationships of
  performance objectives to elements of the
  architecture, and other relationships.

24
6. What is SICoPs role in the DRM?

• Strategic Directions (continued)
• June 3, 2004 Fourth Quarterly Emerging Technology
  Components Conference
• Some recommendations
• Involve taxonomy (ontology) expertise in
  improving the FEA classification scheme
  (taxonomy) and its extension into the agencies.
  (This should also help the Line of Business Task
  Force work).
• See FEA Reference Model Ontology, FHA/NHIN
  Ontology Pilot, EPA Region 4 Pilot with Line of
  Sight Ontology, etc.
• Involve knowledge management expertise in
  building a comprehensive knowledge-base
  (repository) of enterprise architecture (OMB
  budget, solutions like SOA, Web Services, etc.)
• See Dynamic Knowledge Repository with FEA
  taxonomy, FEA Reference Model Ontology, etc.
  (next slide)
• Advancing Enterprise Architecture Maturity,
  Version 2.0, IAC EA SIG, January 2005, page 39
• The FEA Reference Models do not constitute a
  comprehensive EA methodology or approach by
  themselves. These FEA Reference Models, as
  populated, specifically serve mainly as
  mechanisms for identifying and coding initiatives
  via a common taxonomy and as checklists for
  coverage in an EA.

25
6. What is SICoPs role in the DRM?
See FEA Semantic Interoperability Repository in
the Best Practices Repository at
http//web-services.gov
26
7. What is the XML CoPs role in the DRM?

• Owen Ambur, Co-Chair of the XML CoP
• Emerging Technology.Gov
• http//et.gov/
• http//et.gov/component_info.aspx
• XML Schema for Agency Strategic Plans
• DRM XML Schema (see next slide)
• Etc.

27
7. What is the XML CoPs role in the DRM?

• Note Only Illustrative
• ltDataReferenceModelgt
• ltDataDescriptiongt
• ltDatagt lt/Datagt
• ltDataAssetsgtlt/DataAssetsgt
• lt/DataDescriptiongt
• ltDataSharinggt
• ltExchangesgt lt/Exchangesgt
• ltDataAccessgt lt/DataAccessgt
• lt/DataSharinggt
• ltDataContextgt
• ltTaxonomiesgt lt/Taxonomiesgt
• ltFeaMapgt lt/FeaMapgt
• ltDataStandardsgt lt/DataStandardsgt
• lt/DataContextgt
• lt/DataReferenceModelgt

28
8. What are the federated taxonomies in the DRM
Volume 5

• Jim Feagans, Craig Tanner, and Robert Chadduck
• Open Grid Services Architecture (OGSA) Use Cases
• See http//www.gridforum.org/documents/GWD-I-E/GFD
  -I.029v2.pdf