universal data element framework (udef) oasis – universal business language ron schuldt senior...

Universal Data Element Framework (UDEF)

OASIS – Universal Business Language

Ron Schuldt Senior Staff Systems Architect, Lockheed Martin

Co-Chair, AIA Electronic Enterprise Working Group Sally Chan Associate Technical Fellow, The Boeing Company

November 21, 2002

The Problem and Goal

The Integration Problem & Goal

Current Point-to-Point Approach --- n(n-1)

Future UDEF Canonical Approach --- 2n

0

50

100

150

200

250

300

350

400

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

$$

Savings

Global

Canonical

Standard

The Interoperability Challenge

95%

5%

“Interoperability required the entire interfaces between applications to be standardized. Only 5% of the interface is a function of the middleware choice. The remaining 95% is a function of application semantics.” Gartner Group

Application Integration“Semantics”

Messaging andTransport Services

““According to Gartner Group, 35-40% of all programming effort in a typical computing According to Gartner Group, 35-40% of all programming effort in a typical computing environment is devoted to developing and maintaining the extract and update environment is devoted to developing and maintaining the extract and update programs whose only purpose is to transfer information between different databases.” programs whose only purpose is to transfer information between different databases.” Quote from Ernst & Young Financial Analysis of “Quote from Ernst & Young Financial Analysis of “Enterprise Application Integration – Enterprise Application Integration – Constellar and British Power Achieving Business Benefit”Constellar and British Power Achieving Business Benefit”

An Integration Cost Illustration

Implementation:$3-5 million

Software:$1 million

If integration software costs

$1 million, implementation

will cost $3-5 million. (Gartner)

Two-thirds of the

implementation cost

involves data integration.Data

integration:$2-3.3 million Data transformation

is one-third of the

implementation cost. (AMR Research)

Datatransformation:$1-1.7 millionT

ota

l S

ervi

ces

Sp

end

The Standards Problem Summarized

<PARTNUMBER>111-222-333</PARTNUMBER>

<partNumber>111-222-333</partNumber>

<PartNumber>111-222-333</PartNumber>

<partnumber>111-222-333</partnumber>

Though semantically equal, the following are 4 different XML tag names

As result, many industries including aerospace are defining their metadata (tag name) XML standards necessary for e-business – too many standards

STEP (CAD) X12/EDIFACT (EDI)

EIA-836Config Mgmt

Other XML Standards

Legacy Data

Conflicting Overlaps

Small Sample of the “Other XML Standards”

• HL7 - Health Care http://www.hl7.org/ • IFX - Interactive Financial Exchange http://www.ifxforum.org/ • FPML – Financial Products http://www.fpml.org/ • SWIFT – Business Messages based on EDIFACT (for International

Trading Partners) http://www.swift.com/index.cfm• HR-XML – Human Resources and Benefits

http://www.hr-xml.org/channels/home.htm • OAG – ERP and Middleware Vendors http://www.openapplications.org/ • RosettaNet – IT and Electronic Components Industry

http://www.rosettanet.org/rosettanet/Rooms/DisplayPages/LayoutInitial • ACORD – XML for the Insurance Industry http://www.acord.org/ • XBRL – Business Reporting - Accounting http://www.xbrl.org/ • TranXML – Transportation XML http://www.transentric.com/default2.asp

http://www.hl7.org/

http://www.ifxforum.org/

http://www.fpml.org/

http://www.swift.com/index.cfm

http://www.hr-xml.org/channels/home.htm

http://www.openapplications.org/

http://www.rosettanet.org/rosettanet/Rooms/DisplayPages/LayoutInitial

http://www.acord.org/

http://www.xbrl.org/

http://www.transentric.com/default2.asp

Example Overlaps

UDDIUDDI

EIA836 CollaborationEIA836 Collaboration

STEP CollaborationSTEP Collaboration

Example OverlapsExample Overlaps

• Supplier IDSupplier ID

• AddressAddress

• Part NumberPart Number

AIA AIA TransactionsTransactions

UDDIUDDI

- Universal Unique ID (UUID)Universal Unique ID (UUID)

- Globally uniqueGlobally unique

- Supports many ID codesSupports many ID codes

- 128 bit hexadecimal (8 char AN)128 bit hexadecimal (8 char AN)

EIA-836EIA-836

- Organization IDOrganization ID


» CAGE, DUNS, FSCM, etc.CAGE, DUNS, FSCM, etc.

- ID length not specifiedID length not specified

AIA EDIAIA EDI

- Originating Company ID NumberOriginating Company ID Number


» CAGE, DUNS, FSCM, etc.CAGE, DUNS, FSCM, etc.

- ID length (10 char AN)ID length (10 char AN)

The Universal Data Element Framework (UDEF) and its Foundation

Current Business ProblemCurrent Business Problem• Point-to-point interfaces are the normPoint-to-point interfaces are the norm• Mappings are time consuming processMappings are time consuming process• Lack consistent naming conventionLack consistent naming convention• Lack standard data namesLack standard data names• System experts often retained to support Interface developmentSystem experts often retained to support Interface development

Summary DescriptionSummary Description

The UDEF is a The UDEF is a rules-based metadata naming conventionrules-based metadata naming convention that that follows the principles of ISO 11179 and supports the ebXML core follows the principles of ISO 11179 and supports the ebXML core components naming convention. Once a components naming convention. Once a data element conceptdata element concept has been mapped to the UDEF, the data element can then be has been mapped to the UDEF, the data element can then be assigned a UDEF assigned a UDEF derived intelligent unique IDderived intelligent unique ID. The UDEF was . The UDEF was officially adopted by the AIA Metadata Harmonization Project officially adopted by the AIA Metadata Harmonization Project Team in January 2002Team in January 2002

Universal Data Element FrameworkUniversal Data Element Framework

UDEF Background

CALS ISG - Developed UDEFin the late 80s – early 90sIndustryRon Schuldt (Chair) - Lockheed Martin Barbara Barman (Vice Chair) - RaytheonRob Bryant - DynCorpRuey Chen - David Taylor Research CenterBob Hodges - Texas InstrumentsNeal McNamara - Analysis & Technology Inc.Bud Orlando - TRWMadelyn van der Bokke - ASECGeorge Walther - Lockheed Martin

GovernmentNorma Kornwebel - PM JCALSDinah Beres - NAWCSteve Waterbury - NASA

EIA- Applied UDEFin the mid 90s and 2002IndustryRon Schuldt (Chair) - Lockheed Martin Rick Lang - Texas InstrumentsPam Stanfield - Lockheed MartinGary O’Hara - Hughes Space and CommTony DiPerna - Ericsson CommunicationsKen McTee - Texas InstrumentsCindy Hauer - Mevatec CorpFred Bahrs - CMstat CorporationDoug Drury - ITT Federal ServicesLee LeClair - Texas Instruments

GovernmentDeborah Cornelius - US Army Missile Cmd

C. H. VanLandingham - NOAA Nat’l Wea Svc

Today AFEI (formerly CALS ISG) holds the Intellectual Property Rights to the UDEF

Factors that Influenced UDEF Evolution• 1988 White Paper to OSD CALS Office and STEP Leadership

– Title - “PDES/STEP and CALS Scope Issue”– CALS committee created to address the issue working with STEP– Initial focus “product data” in context of “enterprise”

• 1990-1991 -- Air Force Regulation 4-29– Data Naming Principles (Prime Words and Class Words)

• 1993 -- DoD 8320.1-M-1– DoD-wide policy mandated standard list of Class Words

• 1994-1995 -- MIL-STD-2549 Config Mgmt Data Interface– Every data element named based on UDEF naming convention

• 1996-1998 -- ISO/IEC 11179– Prime and Class substituted with Object and Property

• 2001-2002 -- EIA-836 Config Mgmt Data Interchange and Interoperability– Every data containing tag mapped to the UDEF – in Annex D

• 2002 -- AIA and EIDX adoption– Within MHP and XRT projects – added mapping matrices

• 2002 -- ebXML Core Components Specification– ebXML representation words replaced DoD 8320.1-M-1 based property words

UDEF Rules Based Naming Convention

Data ElementName

Object Class Term

0...n qualifiers +1 or more reqd

Object Class

+

Example Data Element Names

Document Abstract Text

Enterprise Name

Product Price Amount

Product Scheduled Delivery Date

Engineering Design Process Cost Amount

Object Class ListEntityDocumentEnterprisePlaceProgramProductProcessPersonAssetLaw-RuleEnvironmentConditionLiabilityAnimalPlantMineral

Property Term

0..n qualifiers +1 reqd Property

Property ListAmountCodeDateDate TimeGraphicIdentifierIndicatorMeasureNamePercentPictureQuantityRateTextTimeValue

Complies with ISO 11179 Naming Convention and Supports ebXML

Names constructed follow the rules of English – modifiers precede the word they modify

ISO/IEC 11179

Part 1: Framework for the Specification and Standardization of Data Elements

Part 2: Classification for Data Elements

Part 3: Basic Attributes of Data Elements

Part 4: Rules and Guidelines for the Formulation of Data Definitions

Part 5: Naming and Identification Principles for Data Elements

Part 6: Registration of Data Elements

Data Element Fundamentals – ISO 11179

DataElementConcept

DataElement

ValueDomain

ObjectObjectClassClass

PropertyProperty RepresentationRepresentation

CoreData

Element

ApplicationData

Element

UDEF Maps Data Element Concepts

Data Naming Fundamentals – ISO 11179

ISO 11179 naming scheme has three major components:

1. Object Class identifies the primary concept of a data element

2. Property identifies the characteristics of the object class

3. A Representation Class categorizes the format of the data element

• For example, the property “date” can be represented in many different formats such as July 24, 2002 or 7-24-02 or 20020724

Data Element Concept per ISO 11179Data Element Concept per ISO 11179

A concept that can be represented in the form of a data element, described independently of any particular representation.

Data Element Concept - definition

Comparison to Data Model Terminology

UDEF Objects – Establish Context

Person Asset

ProductProduct

Laws-Rules

Process

Document

Enterprise AEnterprise B

Program

Resources

Environment

Place

Entity

Condition

UDEF Root Level Object & Property IDs

Entity = 0Asset = 1Document = 2Enterprise = 3Environment = 4Person = 5Law/Rule = 6Place = 7Process = 8Product = 9Program = 10Condition = 11Liability = 12Animal = 13Plant = 14Mineral = 15

Amount = 1Graphic = 2Picture = 3Code = 4Date Time = 5Date = 6Indicator = 7Identifier = 8Percent = 9Name = 10Quantity = 11Rate = 12Measure = 13Text = 14Time = 15Value = 16

+

Object Property

UDEF Object Definitions

Entity - Any concrete or abstract thing of interest, including associations among things Asset - Any data or information about any resource, other than human, which is used, consumed, or available for use/consumption by any process of an enterprise Document - Any data or information about any collection of data or information, regardless of format, which has definable boundaries and is so designated for one or more purposes Enterprise - Any data or information about any definable boundary collection of person and asset resources used to perform a collection of processes to create one or more products which are intended for use or consumption by outside entities Environment - Any data or information about any natural or man-made surrounding that is relevant to the enterprise Person - Any data or information about any person that is relevant to the enterprise Law-Rule - Any data or information about laws (natural or man-made) or policies that govern any process of the enterprise Place - Any data or information about any location that is relevant to the enterprise Process - Any data or information about a definable course of events distinguishable by its purpose or by its effect, whether natural, manual, automated or machine supported and which is relevant to the enterprise Product - Any data or information regarding something that is the result of a set of processes and which is intended to be used or consumed by activities outside of the enterprise Program - Any data or information about any definable collection of enterprises bound by a common set of objectives Condition - Any data or information that describes the state of something of interest to the enterprise

UDEF Property Definitions

Amount - always monetaryCode - a character string used to replace a definitive valueDate - a day within a particular calendar year (a type of date time)Date Time - a particular point in the progression of timeGraphic - a diagram, graph, mathematical curve or similar representationIdentifier - a character string used to identify and distinguish uniquelyIndicator - a list of two and only possible values (synonym for Boolean)Measure - a description of the attributes associated with a numeric value that is determined by measuring an object (Unit of Measure)Name - a word or phrase that distinctively designates a person, place, etc. (a type of text)Percent - a rate expressed in hundredths between two values with same UoM (a type of numeric)Picture - a visual representation of a person, object, or sceneQuantity - a number of non-monetary units - associated with objects (a type of numeric)Rate - a quantity or amount measured with respect to another quantity or amount (a type of numeric)Text - a character string generally in the form of words of a languageTime – the time within a (not specified) day (a type of date time)Value – numeric information that is assigned or determined by calculation, counting, or sequencing (a type of numeric)

Example Object Tree Extract

DOCUMENT

ManualOrderAgreement

Memorandum-Of

TechnicalChange

Rapid Action

Instruction Item

Data

Contract

ModificationWork

Modification Technical

Limited Duration

Equipment

List

Requirements

Data

Contract

Controlling

Alias

s t u v w

a

a b

ca

a

a

a

a

ab

a

a

ba

(2)

a

a

Partner

Trading

b

a

a

Armyc

United Statesa

Revisedd

United Statesa

Air Forceb

Changede

Purchased

Workb

Manufacturinga

Licensec

Example Property Tree Extract

IDENTIFIER (8)

Action Designator Assigned

Reference

Vendor

33 3435

1

1

Purchaser2

Sender3

Air Force4

United States1

DUNS5

Defense Logistics6

UDDI7

EAN-UCC8

Manufacturer9

NATO10

Mapping to the UDEF

1. Identify the applicable UDEF property word that characterizes the dominant attribute (property) of the data element concept. For example, Name, Identifier, Date, etc.

2. Identify the dominant UDEF object word that the dominant property (selected in step 1) is describing. For example, Person_Name, Product_Identifier, Document_Date, etc.

3. By reviewing the UDEF tree for the selected property identified in step 1, identify applicable qualifiers that are necessary to unambiguously describe the property word term. For example, Last Name

4. By reviewing the UDEF tree for the selected object identified in step 2, identify applicable qualifiers that are necessary to unambiguously describe the object word term. For example, Customer Person

5. Concatenate the object term and the property term to create a UDEF naming convention compliant name where it is recognized that the name may seem artificially long. For example, Customer Person_Last Name

6. Derive an intelligent UID based on the UDEF taxonomy that carries the UDEF inherited indexing scheme. For example <CustomerPersonLastName GUID=“as.5_5.10”>

Goal - UDEF IDs Become Global Unique IDs (GUIDs)

<ContractDocumentIdentifier DOC:GUID=“e.2_8”>123abc</ContractDocumentIdentifier>

<ContractNo DOC:GUID=“e.2_8”>123abc</ContractNo>

<BuyersContractNumber DOC:GUID=“e.2_8”>123abc</BuyersContractNumber>

Benefit – GUIDs eliminate the baggage associated with changing names

EIA-836 X12 (EDI)

Part No

Doc Type

Product Part Identifier

Product Name

Document Type Code

Product/Service ID

Product/Service Name

Entity (Supplier) Name

Contract Document Identifier

Report Type Code

Supplier

Vendor A

Contract NoBuyer’s Contract Number

Component Product Quantity

UDEF ID = ebXML UID

9_5.8

9_9

2_33.4

e.2_8

f.g.9_11

y.3_9

Mapping Data Element Concepts to the UDEF

UDEF Mapping – UBL Example

Data Element Concept Name

OrderId

Data Element Concept Definition

The OrderId element is a unique number assigned to the Order in respect to the parties assigning the number.

UDEF ID Object Type or Role Object Class Property Type Property




OrderId





Identifier



OrderId





IdentifierDocument




IdentifierDocument


OrderId



N/A




IdentifierDocumentPurchase Order


OrderId



N/A




d.t.2_8


OrderId



IdentifierDocumentPurchase Order N/A



OrderItem Quantity


The quantity of the items on this line item.






Quantity


OrderItem Quantity






Product Quantity


OrderItem Quantity






Product Ordered Quantity


OrderItem Quantity






QuantityProduct OrderedLine Item


OrderItem Quantity






b.i.9_13.11 QuantityProduct OrderedLine Item


OrderItem Quantity



UDEF Mapping Examples – Cont.

UDEF ID UBL Dictionary Entry Name

ebXML BBIE Dictionary Entry Name

ATA Business Term

UDEF data name

Order. Purchaser Assigned ID. Identifier

Order Document. Customer. Identifier

Customer Order Number

d.t.2_2.35.8

Part NumberSpare Part OrderItem. Manufacturer Assigned ID. Identifier

Spare Part Item. Manufacturer. Identifier

g.9_9.35.8

PurchaseOrder Document Purchaser Assigned Identifier

Part Product Manufacturer Assigned Identifier

Order QuantityLine Item. Ordered. Quantity

OrderItem. Quantityb.i.9_13.11 LineItem Product Ordered Quantity

Benefits/Features of the UDEF

• Based on ISO 11179 and ebXML standards• Infinitely extensible• UDEF IDs are language independent • Built in indexing for all XML catalogs

– Find entries more rapidly within large catalogs

• Enable faster alignment between disparate legacy systems – even for close matches

– Two hinge points (the object and the representation word)

• Reduce costs associated with interfacing systems within the business

• Provide foundation for standardized global XML namespace categories

– PER:GUID Person – all XML names with Person as the object– PRD:GUID Product – all XML names with Product as the object– ENP:GUID Enterprise – all XML names with Enterprise as the object– PRC:GUID Process – all XML names with Process as the object– PLC:GUID Place – all XML names with Place as the object– PRG:GUID Program – all XML names with Program as the object– etc

Benefits of the UDEF

Making UDEF Real in the Supply Chain

The UDEF Business ModelThe UDEF Business Model

• Is this ready for prime-time? i.e. how do we know this is not just another standards Is this ready for prime-time? i.e. how do we know this is not just another standards intellectual exercise, but rather, is something that industries will implement soon?intellectual exercise, but rather, is something that industries will implement soon?

– AIA and EIDX (a part of CompTIA) have already adopted the UDEF approach and are AIA and EIDX (a part of CompTIA) have already adopted the UDEF approach and are building UDEF based matrices for standards relevant to their respective industriesbuilding UDEF based matrices for standards relevant to their respective industries

– Individual companies are already expending resources to accomplish these mappingsIndividual companies are already expending resources to accomplish these mappings– Concept and architecture will be demonstrated and proven before deploymentConcept and architecture will be demonstrated and proven before deployment

• Why is UDEF better than any other approach?Why is UDEF better than any other approach?– UDEF structured IDs are an extension of the number.number.number approach already UDEF structured IDs are an extension of the number.number.number approach already

used with the Internet for IP addresses. The structured IDs are computer friendly. used with the Internet for IP addresses. The structured IDs are computer friendly. Similar to Dewey Decimal system. Similar to Dewey Decimal system.

– Theoretically has infinite extensibilityTheoretically has infinite extensibility– UDEF addresses the randomness issue associated with ebXML random UIDsUDEF addresses the randomness issue associated with ebXML random UIDs– It simplifies data integration across disparate systemsIt simplifies data integration across disparate systems– Reduces IT costs associated with building and maintaining data mapping applicationsReduces IT costs associated with building and maintaining data mapping applications

– ““According to Gartner Group, 35-40% of all programming effort in a typical computing environment According to Gartner Group, 35-40% of all programming effort in a typical computing environment is devoted to developing and maintaining the extract and update programs whose only purpose is to is devoted to developing and maintaining the extract and update programs whose only purpose is to transfer information between different databases.” transfer information between different databases.” Quote from Ernst & Young Financial Analysis of Quote from Ernst & Young Financial Analysis of Enterprise Application Integration – Constellar and British Power Achieving Business BenefitEnterprise Application Integration – Constellar and British Power Achieving Business Benefit

UDEF One Page Summary

Current Business Problem• Point-to-Point Interfaces are the Norm• Mappings are Time Consuming Process• Lack Consistent Naming Convention• Lack Standard Data Names• System Experts Often Retained to Support

Interface Development

Summary DescriptionThe Universal Data Element Framework (UDEF) is a rules based metadata naming convention that greatly accelerates data integration for large data integration projects. Once a data element concept has been mapped to the UDEF, the data element can then be assigned a UDEF derived intelligent unique ID.

• Depending on complexity, the time and effort required to analyze and map any pair of systems reduces substantially (potentially by order of magnitude) as the number of systems to be integrated increases beyond three or four (break even point)

• UDEF IDs add computer sensible intelligence to the names of elements within any system – thereby reducing dependence on requiring the system expert for mapping the system to any other system

• UDEF is gaining momentum as an e-business standard – adopted by AIA – gaining interest by other organizations

Benefits of UDEF

Alias 1 Alias 2 Alias 3 Alias n. . . . .

Universal ID =

Map-to-UDEF Approach

UDEF Name

UDEF ID

Canonical Model Name

Questions

? ?

?

?

???

?

?

?Ron Schuldt – 303-977-1414 or [email protected]

universal data element framework (udef) oasis – universal business language ron schuldt senior...

Documents

benefits http

id codescage

middleware vendors http

insurance industry http

id codes128

fpml financial products

acord xml

business benefitpage