Transcript Organizational Design

Universal Data Element Framework (UDEF)
OASIS – Universal Business Language
Ron Schuldt Senior Staff Systems Architect, Lockheed Martin
Sally Chan
Co-Chair, AIA Electronic Enterprise Working Group
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
Global
Canonical
Standard
400
400
350
350
300
300
250
250
200
200
150
150
100
100
50
50
0
$$
Savings
0
1
2
3
4
5
6
7
8
9
10 11 12 13 14 15 16 17 18 19 20
1
2
3
4
5
6
7
8
9
10 11 12 13 14 15 16 17 18 19
Page 3
The Interoperability Challenge
“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 transfer information between different
databases.” Quote from Ernst & Young Financial Analysis of “Enterprise Application
Integration – Constellar and British Power Achieving Business Benefit”
“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 and
Transport Services
95%
5%
Page 4
An Integration Cost Illustration
Total Services Spend
Software:
$1 million
Implementation:
$3-5 million
Data
integration:
$2-3.3 million
Data
transformation:
$1-1.7 million
If integration software costs
$1 million, implementation
will cost $3-5 million. (Gartner)
Two-thirds of the
implementation cost
involves data integration.
Data transformation
is one-third of the
implementation cost.
(AMR Research)
Page 5
The Standards Problem Summarized
Conflicting Overlaps
EIA-836
Config Mgmt
STEP (CAD) X12/EDIFACT (EDI)
Other XML Standards
Legacy Data
Though semantically equal, the following are 4 different XML tag names
<PARTNUMBER>111-222-333</PARTNUMBER>
<partNumber>111-222-333</partNumber>
<PartNumber>111-222-333</PartNumber>
<partnumber>111-222-333</partnumber>
As result, many industries including aerospace are defining their metadata
Page 6
(tag name) XML standards necessary for e-business – too many standards
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
Page 7
Example Overlaps
UDDI
AIA
Transactions
- Universal Unique ID (UUID)
- Globally unique
- Supports many ID codes
- 128 bit hexadecimal (8 char AN)
UDDI
EIA-836
- Organization ID
- Supports many ID codes
EIA836 Collaboration
» CAGE, DUNS, FSCM, etc.
- ID length not specified
STEP Collaboration
AIA EDI
- Originating Company ID Number
- Supports many ID codes
» CAGE, DUNS, FSCM, etc.
- ID length (10 char AN)
Example Overlaps
• Supplier ID
• Address
• Part Number
Page 8
The Universal Data Element Framework
(UDEF) and its Foundation
Universal Data Element Framework
Summary Description
The UDEF is a rules-based metadata naming convention that
follows the principles of ISO 11179 and supports the ebXML core
components naming convention. Once a data element concept
has been mapped to the UDEF, the data element can then be
assigned a UDEF derived intelligent unique ID. The UDEF was
officially adopted by the AIA Metadata Harmonization Project Team
in January 2002
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
Page 10
UDEF Background
CALS ISG - Developed UDEF
EIA- Applied UDEF
in the late 80s – early 90s
Industry
Ron Schuldt (Chair) - Lockheed Martin
Barbara Barman (Vice Chair) - Raytheon
Rob Bryant - DynCorp
Ruey Chen - David Taylor Research Center
Bob Hodges - Texas Instruments
Neal McNamara - Analysis & Technology Inc.
Bud Orlando - TRW
Madelyn van der Bokke - ASEC
George Walther - Lockheed Martin
in the mid 90s and 2002
Industry
Ron Schuldt (Chair) - Lockheed Martin
Rick Lang - Texas Instruments
Pam Stanfield - Lockheed Martin
Gary O’Hara - Hughes Space and Comm
Tony DiPerna - Ericsson Communications
Ken McTee - Texas Instruments
Cindy Hauer - Mevatec Corp
Fred Bahrs - CMstat Corporation
Doug Drury - ITT Federal Services
Lee LeClair - Texas Instruments
Government
Norma Kornwebel - PM JCALS
Dinah Beres - NAWC
Steve Waterbury - NASA
Government
Deborah 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
Page 11
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 12
UDEF Rules Based Naming Convention
Complies with ISO 11179 Naming Convention and Supports ebXML
Data Element
Object Class List
Name
Entity
Document
Enterprise
Object Class Term
Property Term
Place
Program
0...n qualifiers +
0..n qualifiers +
Product
1 or more reqd
1 reqd Property
Object Class
Process
+
Person
Asset
Law-Rule
Environment
Condition
Liability
Animal
Plant
Mineral
Example Data Element Names
Document Abstract Text
Enterprise Name
Product Price Amount
Property List
Amount
Code
Date
Date Time
Graphic
Identifier
Indicator
Measure
Name
Percent
Picture
Quantity
Rate
Text
Time
Value
Product Scheduled Delivery Date
Engineering Design Process Cost Amount
Names constructed follow the rules of English – modifiers precede the word they modify
Page 13
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 14
Data Element Fundamentals – ISO 11179
Object
Class
Property
Representation
Data
Element
Concept
UDEF Maps Data
Element Concepts
Data
Element
Core
Data
Element
Value
Domain
Application
Data
Element
Page 15
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 16
Data Element Concept per ISO 11179
Data Element Concept - definition
A concept that can be represented in the form of a data element,
described independently of any particular representation.
Page 17
Comparison to Data Model Terminology
Page 18
UDEF Objects – Establish Context
Entity
Enterprise B
Enterprise
A
Place
Laws-Rules
Program
Product
Process
Product
Document
Environment
Person
Asset
Resources
Condition
Page 19
UDEF Root Level Object & Property IDs
Property
Object
Entity = 0
Asset = 1
Document = 2
Enterprise = 3
Environment =
4
Person = 5
Law/Rule = 6
Place = 7
Process = 8
Product = 9
Program = 10
Condition = 11
Liability = 12
Animal = 13
Plant = 14
Mineral = 15
+
Amount = 1
Graphic = 2
Picture = 3
Code = 4
Date Time = 5
Date = 6
Indicator = 7
Identifier = 8
Percent = 9
Name = 10
Quantity = 11
Rate = 12
Measure = 13
Text = 14
Time = 15
Value = 16
Page 20
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 21
UDEF Property Definitions
Amount - always monetary
Code - a character string used to replace a definitive value
Date - a day within a particular calendar year (a type of date time)
Date Time - a particular point in the progression of time
Graphic - a diagram, graph, mathematical curve or similar representation
Identifier - a character string used to identify and distinguish uniquely
Indicator - 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 scene
Quantity - 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 language
Time – 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 22
Example Object Tree Extract
DOCUMENT
Agreement
Order
s
Instruction
t
License Work Change
c
Partner
a
b
b
u
Modification
Purchase
a
Technical
a
Equipment
c
a
a
Air Force
Limited Duration
a
a
Memorandum-Of
a
Manual
v
Work
b
Data
w
List
a
Technical
a
b
Contract
a
Rapid Action
Trading
Item
d
Modification
(2)
Manufacturing
a Requirements
Changed
e
Army
Alias c Revised
d
b
a
Controlling
b
Data
United States
a
a
a
United States
a
Contract
a
Page 23
Example Property Tree Extract
IDENTIFIER
Assigned 35
Action Designator
33
(8)
34
Reference
1
Vendor
1
NATO
10
Purchaser
Manufacturer
9
EAN-UCC
2
Air Force
Sender
4
DUNS
3
5
United States
1
UDDI
8
7
Defense Logistics
6
Page 24
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 25
Goal - UDEF IDs Become Global
Unique IDs (GUIDs)
UDEF ID = ebXML UID
EIA-836
X12 (EDI)
9_5.8
Product Part Identifier
Product/Service ID
9_9
Product Name
Product/Service Name
y.3_9
e.2_8
f.g.9_11
2_33.4
Vendor A
Part No
Entity (Supplier) Name
Supplier
Contract Document
Identifier
Component Product
Quantity
Buyer’s Contract
Number
Contract No
Document Type Code
Report Type Code
Doc Type
<ContractDocumentIdentifier DOC:GUID=“e.2_8”>123abc</ContractDocumentIdentifier>
<BuyersContractNumber DOC:GUID=“e.2_8”>123abc</BuyersContractNumber>
<ContractNo DOC:GUID=“e.2_8”>123abc</ContractNo>
Benefit – GUIDs eliminate the baggage associated with changing names
Page 26
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
1.
Object Type or Role
Object Class
Property Type
Property
Identify the applicable UDEF property word that characterizes the dominant
attribute (property) of the data element concept. For example, Name, Identifier,
Date, etc.
Page 28
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
Identifier
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.
Page 29
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
Document
3.
Property Type
Property
Identifier
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
Page 30
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
Document
4.
Property Type
N/A
Property
Identifier
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
Page 31
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
5.
Object Type or Role
Object Class
Purchase Order
Document
Property Type
N/A
Property
Identifier
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
Page 32
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
d.t.2_8
6.
Object Type or Role
Object Class
Purchase Order
Document
Property Type
N/A
Property
Identifier
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 33
UDEF Mapping – UBL Example
Data Element Concept Name
OrderItem Quantity
Data Element Concept Definition
The quantity of the items on this line item.
UDEF ID
1.
Object Type or Role
Object Class
Property Type
Property
Identify the applicable UDEF property word that characterizes the dominant
attribute (property) of the data element concept. For example, Name, Identifier,
Date, etc.
Page 34
UDEF Mapping – UBL Example
Data Element Concept Name
OrderItem Quantity
Data Element Concept Definition
The quantity of the items on this line item.
UDEF ID
Object Type or Role
Object Class
Property Type
Property
Quantity
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.
Page 35
UDEF Mapping – UBL Example
Data Element Concept Name
OrderItem Quantity
Data Element Concept Definition
The quantity of the items on this line item.
UDEF ID
Object Type or Role
Object Class
Product
3.
Property Type
Property
Quantity
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
Page 36
UDEF Mapping – UBL Example
Data Element Concept Name
OrderItem Quantity
Data Element Concept Definition
The quantity of the items on this line item.
UDEF ID
4.
Object Type or Role
Object Class
Property Type
Product
Ordered
Property
Quantity
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
Page 37
UDEF Mapping – UBL Example
Data Element Concept Name
OrderItem Quantity
Data Element Concept Definition
The quantity of the items on this line item.
UDEF ID
Object Type or Role
Line Item
5.
Object Class
Property Type
Product
Ordered
Property
Quantity
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
Page 38
UDEF Mapping – UBL Example
Data Element Concept Name
OrderItem Quantity
Data Element Concept Definition
The quantity of the items on this line item.
UDEF ID
b.i.9_13.11
6.
Object Type or Role
Line Item
Object Class
Property Type
Product
Ordered
Property
Quantity
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 39
UDEF Mapping Examples – Cont.
UDEF ID
d.t.2_2.35.8
g.9_9.35.8
b.i.9_13.11
UBL Dictionary
Entry Name
ebXML BBIE
Dictionary
Entry Name
Order. Purchaser
Assigned ID. Identifier
Order Document.
Customer. Identifier
Spare Part OrderItem.
Manufacturer Assigned
ID. Identifier
Spare Part Item.
Manufacturer.
Identifier
OrderItem. Quantity
Line Item.
Ordered. Quantity
ATA Business
Term
UDEF data
name
Customer Order
Number
Purchase
Order Document
Purchaser
Assigned
Identifier
Part Number
Part Product
Manufacturer
Assigned Identifier
Order Quantity
LineItem Product
Ordered Quantity
Page 40
Benefits/Features of the UDEF
Benefits 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
Page 42
Making UDEF Real in the Supply Chain
The UDEF Business Model
•
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?
– 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 industries
– Individual companies are already expending resources to accomplish these mappings
– Concept and architecture will be demonstrated and proven before deployment
•
Why is UDEF better than any other approach?
– 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 to Dewey Decimal system.
– Theoretically has infinite extensibility
– UDEF addresses the randomness issue associated with ebXML random UIDs
– It simplifies data integration across disparate systems
– Reduces 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
devoted to developing and maintaining the extract and update programs whose only purpose is to
transfer information between different databases.” Quote from Ernst & Young Financial Analysis of
Enterprise Application Integration – Constellar and British Power Achieving Business Benefit
Page 44
UDEF One Page Summary
Summary Description
The 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.
Canonical Model Name
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
Benefits of UDEF
•
•
•
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
Alias 1
Alias 2
Alias 3
.....
Alias n
Universal ID =
Map-to-UDEF Approach
UDEF
Name
UDEF ID
Page 45
Questions
?
?
?
?
?
?
?
?
?
?
Ron Schuldt – 303-977-1414 or [email protected]
Page 46