Class Objectives

Universal Data Element Framework (UDEF)

A Primer

Ron SchuldtCo-Chair, AIA Electronic Enterprise Working Group

September 2002

Page 2

Class Objectives

• Each student will– Understand the enterprise and supply chain integration

problem that drives the need for a solution– Understand why the UDEF can be beneficial to the enterprise– Understand what the UDEF is and the essential portion of the

international standard that it is based upon– Understand how to map data element concepts to the UDEF– Understand how the UDEF could be applied within the supply

chain of the enterprise

The Problem and Goal

Page 4

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

Page 5

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”

Page 6

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

Page 7

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

Page 8

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

Page 9

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

Page 11

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

Page 12

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 CmdC. H. VanLandingham - NOAA Nat’l Wea Svc

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

Page 13

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

Page 14

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

Page 15

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

Page 16

Data Element Fundamentals – ISO 11179

DataElementConcept

DataElement

ValueDomain

ObjectObjectClassClass

PropertyProperty RepresentationRepresentation

CoreData

Element

ApplicationData

Element

UDEF Maps Data Element Concepts

Page 17

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

Page 18

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

Page 19

Comparison to Data Model Terminology

Page 20

UDEF Objects – Establish Context

Person Asset

ProductProduct

Laws-Rules

Process

Document

Enterprise AEnterprise B

Program

Resources

Environment

Place

Entity

Condition

Page 21

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

Page 22

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)

Page 23

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

+

Page 24

Example Object Tree Extract

ENTERPRISE (3)

Remitterw

Receiver Supplier Exemptx y aa

Academic Largeac

Paymenta

Taxa

z

Smallab

Owned

Privately Publicly

a

a b

Owned

Privately Publicly

a

a b

Inspectiona

Paymenta

Examples of Enterprise “Role”

Examples of Enterprise “Type”

Page 25

Example Property Tree Extract

NAME

DivisionGiven System SubsystemFamily File

Electronic

Stage City

(10)

9 10 11 12 13 14 15 16

1

Department17

Examples of Name “Type”

Page 26

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”>

Page 27

Example Mappings

document-publication-datedocument-data-rights-expiration-datedocument-sheet-total-quantitydocument-sheet-size-codesoftware-product-version-identifierproduct-part-identifierreference-document-revision-identifierenterprise-division-address-textprogram-nameproduct-quantityenterprise-address-text

CM (EIA-836) Data Elements

2_5.62_1.2.6.62_1.8.112_1.6.4p.9_8.89_5.8aj.2_9.83_2.12.1410_109_113_12.14

Universal ID

Page 28

Additional Example Mappings

country codeinvoice number- assigned by issuerpurchase order type codepostal codelocation qualifierlocation identifiercontract effective dateexpiry date of import licenseitem number - productitem number - serviceprice

X12 & EDIFACT Data Elements

e.7_4bd.2_1.35.8d.t.2_33.47_1.10.47_20.33.47_8.4e.2_13.6a.be.2_6.69_8f.9_89_2.1

Universal ID

Page 29

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

Page 31

Preparation Steps

• Obtain for each data element concept– Its name

– Its definition

– Example instance(s) – if available

• Print UDEF object and property definitions• Print the UDEF mapping rules• Prepare a spreadsheet with the data element concept name and

definition as two columns. Add 5 additional columns for the UDEF– UDEF ID

– Type or Role of UDEF Object

– UDEF Object

– Type of UDEF Property

– UDEF Property

• Obtain latest version of the UDEF

Page 32

UDEF Mapping – EIA-836 Example

Data Element Concept Name

CAGE Code

Data Element Concept Definition

A Commercial and Government Entity (CAGE) code assigned and maintained by the US Government to identify an entity that designs, manufactures or supplies items.

UDEF ID Object Type or Role Object Class Property Type Property


Page 33



CAGE Code





Identifier

Page 34



CAGE Code





IdentifierEnterprise

Page 35



CAGE Code





IdentifierEnterprise Defense Logistics Assigned

Page 36



CAGE Code





IdentifierEnterprise Defense Logistics Assigned

Page 37



CAGE Code





3_6.35.8 IdentifierEnterprise Defense Logistics Assigned

Page 38

UDEF Mapping – Spec 2000 Example


Order Quantity


Order Quantity is the quantity (conforming to the Unit of Measure) originally ordered by the customer or subsequently revised for the specified Customer Order Number, Part Number, Specified Shipping Date and Ship To Code.



Page 39




Quantity


Order Quantity



Page 40




Product


Order Quantity



Quantity

Page 41




Product Ordered


Order Quantity



Quantity

Page 42





Order Quantity



QuantityProduct Ordered

Page 43




9_13.11


Order Quantity



QuantityProduct Ordered

Page 44

UDEF Mapping Examples – Cont.

Benefits/Features of the UDEF

Page 46

• 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

Page 48

AIA MHP Mapping Matrix Summary

UDEF IDUDEF Role or Type of Object

UDEF Object

UDEF Property

UDEF Type of Property

3_6.35.8 Enterprise IdentifierDefense Logistics Assigned

EIA-836 EDI (X12)Name Definition Valid Values

CAGE CodeA Commercial and Government Entity (CAGE) ...

5 alphanumeric character

Name

ah.3_10.35.8 Enterprise IdentifierNATO Assigned

NSCM CodeA standard NATO supply code ...

stringManufacturer

DE 98 + DE 66/ Code M4

DE 98/ Code M9 + DE 66/ Code 37

D

Sample Mapping Matrix Extract

Phase One Summary• Focus on four topics

• Enterprise Identification• Document Identification• Product Identification• Asset Identification

• Four standards – EIA-836, X12, STEP, UCC

• Goal – to understand the process and the necessary resources to proceed into second phase

• Target completion – August 2002

Phase Two Summary• In planning stages• Include additional standards such as

ATA Spec 2000• Require support from tool such as

Contivo• Require XMLization of the UDEF• Require UDEF transfer to non-profit• Require additional business process

experts – especially contracting and inbound/outbound logistics

• Target completion – November 2003

Page 49

Concept of UDEF Implementation

Transformation Engines

Interfaces to Legacy Systems

• Data Dictionary

• Mapping Matrices

• Std Data Models

UDEF Based MetadataRegistry/Repository

InterfaceDevelopers

Content Administrators

Run Time

Data Modelers

Design Time

Internet

UDEF Change Board

Global UDEF Registry

Vendors with Canonical Models

Software Vendors

With UDEF IDAPIs

Other MetadataRepositories

Administrator

WebPublic

Page 50

The UDEF Business ModelThe UDEF Business Model

1.1. What is the market size for a UDEF registry/repository solution?What is the market size for a UDEF registry/repository solution?- Companies and government organizations that have multiple back-office Companies and government organizations that have multiple back-office

systems supporting their B2B supply chains systems supporting their B2B supply chains - Majority of US Fortune 1000 have IT staffs and perform internal systems integration Majority of US Fortune 1000 have IT staffs and perform internal systems integration

efforts. At least 1,000 companies worldwide would adopt this approach within 5 yearsefforts. At least 1,000 companies worldwide would adopt this approach within 5 years- Many more will receive the benefits through the vendor productsMany more will receive the benefits through the vendor products

- Vendors who offer major applications and middleware (EAI) type applicationsVendors who offer major applications and middleware (EAI) type applications- At least 100 vendors/exchanges will adopt the UDEF within the next 5 years of public At least 100 vendors/exchanges will adopt the UDEF within the next 5 years of public

launchlaunch

2. 2. How much will it cost the .org to deploy a UDEF registry/repository?How much will it cost the .org to deploy a UDEF registry/repository?- Initial (Start-up) – Public launch 1Initial (Start-up) – Public launch 1stst Qtr 2004 – Selected .org will work jointly Qtr 2004 – Selected .org will work jointly

with AIA and EIDX at manpower level necessary to support launch targetwith AIA and EIDX at manpower level necessary to support launch target- Help build Web site and provide server – 0.25 people yearsHelp build Web site and provide server – 0.25 people years- Marketing and pilot support – 1.5 people yearsMarketing and pilot support – 1.5 people years- Selected .org will participate in pilot in 3Selected .org will participate in pilot in 3 rdrd Qtr 2003 Qtr 2003

- Ongoing production operations – Ongoing production operations – - Quality control manpower (to have apps listed) – at least self sustainingQuality control manpower (to have apps listed) – at least self sustaining- Maintain and administer Web site (fixed cost) 1.0 personMaintain and administer Web site (fixed cost) 1.0 person- Manage change process (administer change control board), approve bug fixes – 1.5 Manage change process (administer change control board), approve bug fixes – 1.5

people people - Add matrices as submitted by industry associations (assumes one of above will Add matrices as submitted by industry associations (assumes one of above will

accomplish)accomplish)- Training manpower – at least self sustainingTraining manpower – at least self sustaining- Marketing – to be determined by the .org to support AIA/EIDX minimum requirementsMarketing – to be determined by the .org to support AIA/EIDX minimum requirements

Page 51


3. 3. What is the cost recovery model for the .org hosted UDEFWhat is the cost recovery model for the .org hosted UDEF registry/repository?registry/repository?

- UDEF trees and matrices available freely on the Web but read only UDEF trees and matrices available freely on the Web but read only for this type of userfor this type of user

- Potential banner advertising from listed vendorsPotential banner advertising from listed vendors

- For annual subscription fee (two tier pricing – member vs non-For annual subscription fee (two tier pricing – member vs non-member) obtain electronic versions of the UDEF trees and mapping member) obtain electronic versions of the UDEF trees and mapping matrices and allowed to submit updates – also notified of updatesmatrices and allowed to submit updates – also notified of updates- Associations that represent an industry allowed to submit update inputs Associations that represent an industry allowed to submit update inputs

without requirement to become a subscriber (based on memorandum of without requirement to become a subscriber (based on memorandum of agreement)agreement)

- Consider company size as factor in pricingConsider company size as factor in pricing- Value add partners (examples Oracle and Exostar) – use licensing structureValue add partners (examples Oracle and Exostar) – use licensing structure

- To have value add products and associated companies listed that To have value add products and associated companies listed that are UDEF compliant pay a fee for quality checkare UDEF compliant pay a fee for quality check

- Provide training on UDEF use – one day courseProvide training on UDEF use – one day course

Page 52


4. Is this ready for prime-time? i.e. how do we know this is not just another standards 4. 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

5. Why is UDEF better than any other approach?5. 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. Similar used with the Internet for IP addresses. The structured IDs are computer friendly. Similar to Dewey Decimal system. 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 is 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 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

6. How will app vendors (Microsoft, IBM, Oracle, SAP, etc.) be tied in? Will they buy into 6. How will app vendors (Microsoft, IBM, Oracle, SAP, etc.) be tied in? Will they buy into this approach?this approach?

– They will embed the UDEF trees within their product’s APIs to lessen the time and They will embed the UDEF trees within their product’s APIs to lessen the time and expense of integrating their products within customer environmentsexpense of integrating their products within customer environments

– If app vendors believe that multiple industries and large (Global 500) companies will If app vendors believe that multiple industries and large (Global 500) companies will adopt this approach and require it in the vendor products then they will adopt itadopt this approach and require it in the vendor products then they will adopt it

Page 53

Global UDEF Registry

External

Conceptual

Physical

System A

External

Conceptual

Physical

System B

Registered NameRegistered Name

Contract_No

ContractNum ContractNo

Contract DOCUMENT IDENTIFIER

e.2_8

Registered Registered Universal IDUniversal IDRegistered Registered Universal IDUniversal ID

REGISTRATION SERVICEREGISTRATION SERVICE

AIA, EIDX and AFEI will work with .org to establish this service

Contract_Number

Page 54

Large Users


• Data Dictionary


• Std Data Models


Data ModelersContent

AdministratorsInterface

Developers

Design Time

Internet

UDEF Change Board

Global UDEF

Registry


Software Vendors

With UDEF IDAPIs

Other MetadataRepositoriesSTEP UDEF API…

Internet

Trading Partner

UDEF X12 STEP …


Trading Partner

Metadata

Page 55

Midrange Users

Internet

UDEF Change Board

Global UDEF

Registry


Software Vendors

With UDEF IDAPIs


UDEF X12 STEP …


• Data Dictionary


• Std Data Models


Data ModelersContent

AdministratorsInterface

Developers

Design Time

API UDEF

Internet

Trading Partner


Trading Partner

Metadata

Page 56

Small Users – Use Vendor APIs

Internet

UDEF Change Board

Global UDEF

Registry


Software Vendors

With UDEF IDAPIs


UDEF X12 STEP …


• Data Dictionary


• Std Data Models

Vendor SupportedUDEF APIs

Design Time

API UDEF

Internet

Trading Partner

Trading Partner

Metadata

Page 57

UDEF Proof-of-Concept Flow

Page 58

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

Page 59

Questions

? ?

?

?

???

?

?

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

Class Objectives

Documents

benefits http

middleware vendors http

insurance industry http

fpml financial products

acord xml

xml standards necessary

business benefitpage

aia electronic enterprise