Strengthening the Federal Enterprise Architecture FEA Data and Information Reference Model DRM

1
Strengthening the Federal Enterprise Architecture
(FEA) Data and Information Reference Model (DRM)

• Brand Niemann
• Chair, Web Services Work Group
• http//web-services.gov
• March 19, 2003

2
Overview

• 1. Suggestions for the Federal Enterprise
  Architecture (FEA) Data and Information Reference
  Model (DRM), January 22, 2003/Updated January 27,
  2003.
• Recommended that the Data and Statistics
  Development Line of Business (see next slide) be
  done with existing infrastructure (Federal
  Committee on Statistical Methodology)
• On March 13th, Commerce CIO Tom Pyke said that
  Mark Forman had agreed to this.
• 2. Include more standards than just XML and
  Process Knowledge Languages (e.g. ISO 11179 and
  ebXML)
• Content Management Languages.
• Software Modeling Languages.
• Semantic Technology Languages.
• See slide 4.

3
Briefing for Web-Enabled E-Gov Conference, Bob
Haycock, Acting Manager, FEA-PMO, February 10,
2003

• The Federal Government has a multi-billion dollar
  consolidation opportunity
• Citizen Centered Consolidation and Migration to
  the 24 E-Government Initiatives.
• Lines of Business Overlap and Leverage
  Assessment on IT Spending for Common Functions
  (focus on 6)
• Financial Management.
• Human Resources.
• Data and Statistics Development.
• Public Health Information.
• Criminal Investigations.
• Monetary Benefits.
• Office Automation and Infrastructure Leveraging
  Enterprise Licensing and Buying at Commercial
  Benchmarks or Less.
• This is being operationalized in the CIO
  Councils Architecture and Infrastructure
  Committee (AIC).

4
The Tree of Knowledge Technologies
Content Management Languages
Semantic Technology Languages
Process Knowledge Languages
AI Knowledge Representation
Software Modeling Languages
5
Overview

• 3. Provide a checklist for the review of new
  investment proposals
• Participation in cross-organization data
  management activities (e.g. Global Justice
  Information Network, Interagency Electronic
  Grants Committee, etc.)
• Statement of reusable components, metadata
  models, and registries that will be developed and
  contributed to the federation infrastructure and
  CIO Councils Component Repository.
• Piloting experience with Emerging technologies
  (e.g. XML Web Services).
• 4. Include related work
• Geospatial Data and Information Reference Model
  (GDIRM).
• Canadian Government Strategic Reference Model
  (GSRM) and ebXML Registry Version 3 (see next
  slides).
• Governance and Components Subcommittees (see
  slides 9-11)
• Government Data Reference Model (GDRM).
• Federation of Distributed Enterprise
  Architectures, Components, Metadata Models, and
  Registries
• XML Web Services Working Group Pilot Projects
  (see slides 12-14).
• Other.
• 5. Address detailed review comments received
  (provided separately without attribution).

6
Canadian "Federated Architecture Program" (FAP)

• Adoption of three constructs
• A framework for communication, planning design
• A business model Government Strategic
  Reference Model (GSRM)
• "e-Enablers"
• Common strategies, designs and open
  vendor-neutral standards
• Flexible, re-usable business architectural
  components
• Flexible, re-usable technology solutions

7
Canadian e-Enablers

• Information Management Strategy
• Create self-managing (i.e. "smart") data
• Adopt XML for all government data and
  documentation
• Use ebXML in the architectural framework for
  government business systems design
• Engage open vendor-neutral standards
• Implement a distributed ebXML registry/repository
  network across departments agencies

8
ebXML Registry Version 3
Federation SQL XML Queries
Secure
Standards Based
Federated Database / Directory
Cataloging Validation of any Content
Web Accessible
Content Management System
Web Server
ebXML Registry
Extensible
Knowledge Management System
Event Bus
Taxonomy Server
Content based publish/subscribe Event Notification
User defined relationships between content
User defined taxonomies, Content classification
9
The CIO Councils Architecture and
Infrastructure Committee

• Leadership
• John Gilligan, USAF CIO, Co-Chair
• Norman Lorentz, OMB CTO, Advisor and Acting
  Co-Chair
• Subcommittees
• Governance
• Provide policy guidance, advice, and assistance
  in the definition, design, and implementation of
  the Enterprise Architecture discipline and
  practice throughout the Federal Government.
• Robert Haycock, OMB, and John Przysucha, DOE
• Components
• Foster the identification, maturation, and use
  and reuse of Component-Based Architectures and
  Architecture Components in the Federal
  Government.
• Reynolds Cahoon, NARA, and Robert Haycock, OMB.
• EmergingTechnology
• Identify technologies with the potential to
  improve the value and quality of the FEA.
• Dawn Meyerriecks, CTO, DISA, and Mark Day, EPA,
  DCIO.

10
Mapping the Federal Enterprise Architecture Into
the CIOC/AIC

• FEA
• Performance Reference Model (PRM)
• Business Reference Model (BRM).
• Service Component Reference Model (SRM).
• Technical Reference Model (TRM).
• Data and Information Reference Model (DRM).
• Solution Architects Working Group (SAWG).

• AIC Subcommittees
• Governance.
• Governance.
• Components.
• Components.
• Components.
• Components.

11
Emerging Technology Working Groups

• Working Groups
• Public Key Encryption (PKI)
• Judith Spencer, GSA.
• XML
• Owen Ambur, DOI/FWS, and Marion Royal, GSA.
• Universal Access
• Susan Turnbull, GSA.
• XML Web Services.
• Brand Niemann, EPA.
• Relationship to Other Subcommittees
• The Governance and Components Subcommittee will
  request (procure) and the Emerging Technology
  Subcommittee will suggest (pilot).

12
Joint Governance, Components Emerging
Technology Subcommittees Pilot Projects
13
Joint Governance, Components Emerging
Technology Subcommittees Pilot Projects
(continued)
14
Joint Governance, Components Emerging
Technology Subcommittees Pilot Projects
(continued)
15
Example of Components Eforms

• XML Web Services WG Eforms for E-Gov Pilot
• Censuss GIDS.
• Cost Savings.
• Open Source.
• Vendor Support for Open Standards (XSD, XForms,
  and SVG)

• Components Subcommittee Process
• Target Agency Pilot.
• Provide Incentive.
• Create Sharable Item.
• Involve Industry.

An Enterprise Architecture Component is a
self-contained business process or service with
predetermined functionality that may be exposed
through a business or technology interface.
16
Example of Components Eforms

• Components Subcommittee Process
• Identification.
• Classification.
• Standardization.
• Publication.
• Utilization.

• XML Web Services WG Eforms for E-Gov Pilot
• eGrants SF424.
• eGrants(BRM XNS).
• XML Schema.
• XML Collaborator.
• XML Web Service.

An Enterprise Architecture Component is a
self-contained business process or service with
predetermined functionality that may be exposed
through a business or technology interface.
17
Example of Components Federation (loosely
coupled)

• Granularity
• Components
• Metadata Models
• Registries

• Examples
• Eforms (e.g. eGrants)
• Data Elements and XML Schema (e.g. DOD ISO 11179
  Registries)
• ebXML (e.g. GSA-NIST XML Registry)

E.g. Subcomponent of XML Schema to E-Gov Portal
(e.g. Geospatial One-Stop) to Complete Line of
Business (e.g. Data and Statistics Development,
Health Informatics, etc.).
E.g. The XML Collaborator Pilot is federating
components, metadata models, and registries by
supporting XML, ebXML, and UDDI standards.
18
Federated Data Management Metadata is Key

• Federated Data Management is an enormous
  challenge.
• Understanding the underlying metadata must take
  place before any integration efforts begin.
• Post-it notes
• Spreadsheets
• Registries ISO 11179, UDDI, ebXML
• Datatypes
• Attributes
• Structure
• Relationships
• Models

19
Design-Time Integration of Data Via Web Services
Architecture
(6) Map virtual XML Document to physical sources
using Schema in MOF repository
(3) Import modeled XML elements and types into
XML Registry
(2) Identify and model XML schema types
(4) Define XML Schema using registered elements
from MetaBase
XML Collaborator Registry
MetaBase MOF Repository
(5) Import XML Schema info MOF repository
(1) Import Physical Source Metadata
(8) Register WSDL in UDDI Registry
Web Service
(7) Create and Deploy Web Services for accessing
integrated data
Disparate Data Sources
20
How the pilots map to the Knowledge Architecture?
FEA Capabilities Advisor

• Intelligent search
• Capabilities search
• Composable Applications
• Dynamic web services discovery

Knowledge Enablement
MOF Integrator
Topic Maps
XML Collaborator
E-Forms
Information Integration
Agencies Content Managers
Agencies Databases and Systems
Information and Data Sources
21
Semantic FEA Capabilities Advisor

• A semantic engine, based on Ontology
  Technologies, that can advise different
  stake-holders on the capabilities that are being
  provided and developed to support the Federal
  Enterprise Architecture for e-Government.
• A system accessible through WEB Services that
  will allow agencies, other governments,
  businesses, and citizens to make queries about
  the FEA model and to find capabilities that
  support agency services.

Graphic from Dieter Fensel
22
Protégé-2000 Open Source Ontology Tool FEA
Model and Candidate Capability Cases