1 / 59

Class Objectives

Universal Data Element Framework (UDEF) A Primer Ron Schuldt Co-Chair, AIA Electronic Enterprise Working Group September 2002. Class Objectives. Each student will Understand the enterprise and supply chain integration problem that drives the need for a solution

velma
Download Presentation

Class Objectives

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Universal Data Element Framework (UDEF)A Primer Ron SchuldtCo-Chair, AIA Electronic Enterprise Working GroupSeptember 2002

  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

  3. The Problem and Goal

  4. The Integration Problem & Goal Current Point-to-Point Approach --- n(n-1) Future UDEF Canonical Approach --- 2n Global Canonical Standard 400 350 300 $$ Savings 250 200 150 100 50 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

  5. 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 95% Application Integration “Semantics” Messaging and Transport Services 5%

  6. 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) Data transformation: $1-1.7 million An Integration Cost Illustration If integration software costs $1 million, implementation will cost $3-5 million. (Gartner) Software: $1 million Implementation: $3-5 million Total Services Spend

  7. 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 (tag name) XML standards necessary for e-business – too many standards

  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

  9. UDDI Example Overlaps • UDDI • Universal Unique ID (UUID) • Globally unique • Supports many ID codes • 128 bit hexadecimal (8 char AN) AIA Transactions • EIA-836 • Organization ID • Supports many ID codes • CAGE, DUNS, FSCM, etc. • ID length not specified EIA836 Collaboration 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

  10. The Universal Data Element Framework (UDEF) and its Foundation

  11. 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

  12. UDEF Background CALS ISG - Developed 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 Government Norma Kornwebel - PM JCALS Dinah Beres - NAWC Steve Waterbury - NASA EIA - Applied UDEF 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 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

  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

  14. UDEF Rules Based Naming Convention Complies with ISO 11179 Naming Convention and Supports ebXML Data Element Name Object Class List Entity Document Enterprise Place Program Product Process Person Asset Law-Rule Environment Condition Liability Animal Plant Mineral Property List Amount Code Date Date Time Graphic Identifier Indicator Measure Name Percent Picture Quantity Rate Text Time Value Object Class Term 0...n qualifiers + 1 or more reqd Object Class Property Term 0..n qualifiers + 1 reqd Property + Example Data Element Names Document Abstract Text EnterpriseName Product Price Amount Product Scheduled Delivery Date Engineering Design Process Cost Amount Names constructed follow the rules of English – modifiers precede the word they modify

  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

  16. Object Class Property Representation Data Element Concept Value Domain Data Element Core Data Element Application Data Element Data Element Fundamentals – ISO 11179 UDEF Maps Data Element Concepts

  17. Data Naming Fundamentals – ISO 11179 • ISO 11179 naming scheme has three major components: • Object Classidentifies the primary concept of a data element • Propertyidentifies the characteristics of the object class • ARepresentation Classcategorizes 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

  18. 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.

  19. Comparison to Data Model Terminology

  20. UDEF Objects – Establish Context Entity Enterprise B Enterprise A Place Laws-Rules Program Product Product Process Document Environment Person Asset Condition Resources

  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

  22. 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)

  23. UDEF Root Level Object & Property IDs 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 +

  24. Example Object Tree Extract ENTERPRISE (3) Remitter Receiver Supplier Exempt Academic Small Large w x y z aa ab ac Owned Owned Payment Payment Inspection Tax a a a a a a Privately Publicly Privately Publicly a b a b Examples of Enterprise “Role” Examples of Enterprise “Type”

  25. Example Property Tree Extract NAME (10) Stage City Family Given File Division System Subsystem Department 9 10 11 12 13 14 15 16 17 Electronic 1 Examples of Name “Type”

  26. Mapping to the UDEF • Identify the applicable UDEF property word that characterizes the dominant attribute (property) of the data element concept.For example, Name, Identifier, Date, etc. • 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. • 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 • 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 • 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 • Derive an intelligent UID based on the UDEF taxonomy that carries the UDEF inherited indexing scheme. For example <CustomerPersonLastName GUID=“as.5_5.10”>

  27. Example Mappings CM (EIA-836) Data Elements Universal ID document-publication-date document-data-rights-expiration-date document-sheet-total-quantity document-sheet-size-code software-product-version-identifier product-part-identifier reference-document-revision-identifier enterprise-division-address-text program-name product-quantity enterprise-address-text 2_5.6 2_1.2.6.6 2_1.8.11 2_1.6.4 p.9_8.8 9_5.8 aj.2_9.8 3_2.12.14 10_10 9_11 3_12.14

  28. Additional Example Mappings X12 & EDIFACT Data Elements Universal ID country code invoice number- assigned by issuer purchase order type code postal code location qualifier location identifier contract effective date expiry date of import license item number - product item number - service price e.7_4 bd.2_1.35.8 d.t.2_33.4 7_1.10.4 7_20.33.4 7_8.4 e.2_13.6 a.be.2_6.6 9_8 f.9_8 9_2.1

  29. UDEF ID = ebXML UID Vendor A EIA-836 X12 (EDI) 9_5.8 Product Part Identifier Product/Service ID Part No 9_9 Product Name Product/Service Name y.3_9 Supplier Entity (Supplier) Name Contract Document Identifier Buyer’s Contract Number Contract No e.2_8 Component Product Quantity f.g.9_11 2_33.4 Document Type Code Report Type Code Doc Type Goal - UDEF IDs Become Global Unique IDs (GUIDs) <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

  30. Mapping Data Element Concepts to the UDEF

  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

  32. UDEF ID Object Type or Role Object Class Property Type Property 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. • Identify the applicable UDEF property word that characterizes the dominant attribute (property) of the data element concept.For example, Name, Identifier, Date, etc.

  33. UDEF ID Object Type or Role Object Class Property Type Property 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. Identifier • 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.

  34. UDEF ID Object Type or Role Object Class Property Type Property 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. Identifier Enterprise • 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

  35. UDEF ID Object Type or Role Object Class Property Type Property 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. Defense Logistics Assigned Identifier Enterprise • 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

  36. UDEF ID Object Type or Role Object Class Property Type Property 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. Defense Logistics Assigned Identifier Enterprise • 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

  37. UDEF ID Object Type or Role Object Class Property Type Property 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. Defense Logistics Assigned Identifier 3_6.35.8 Enterprise • Derive an intelligent UID based on the UDEF taxonomy that carries the UDEF inherited indexing scheme. For example <CustomerPersonLastName GUID=“as.5_5.10”>

  38. UDEF ID Object Type or Role Object Class Property Type Property UDEF Mapping – Spec 2000 Example Data Element Concept Name Order Quantity Data Element Concept Definition 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. • Identify the applicable UDEF property word that characterizes the dominant attribute (property) of the data element concept.For example, Name, Identifier, Date, etc.

  39. UDEF ID Object Type or Role Object Class Property Type Property UDEF Mapping – Spec 2000 Example Data Element Concept Name Order Quantity Data Element Concept Definition 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. Quantity • 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.

  40. UDEF ID Object Type or Role Object Class Property Type Property UDEF Mapping – Spec 2000 Example Data Element Concept Name Order Quantity Data Element Concept Definition 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. Quantity Product • 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

  41. UDEF ID Object Type or Role Object Class Property Type Property UDEF Mapping – Spec 2000 Example Data Element Concept Name Order Quantity Data Element Concept Definition 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. Quantity Ordered Product • 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

  42. UDEF ID Object Type or Role Object Class Property Type Property UDEF Mapping – Spec 2000 Example Data Element Concept Name Order Quantity Data Element Concept Definition 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. Quantity Ordered Product • 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

  43. UDEF ID Object Type or Role Object Class Property Type Property UDEF Mapping – Spec 2000 Example Data Element Concept Name Order Quantity Data Element Concept Definition 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. Quantity Ordered 9_13.11 Product • Derive an intelligent UID based on the UDEF taxonomy that carries the UDEF inherited indexing scheme. For example <CustomerPersonLastName GUID=“as.5_5.10”>

  44. UDEF Mapping Examples – Cont.

  45. Benefits/Features of the UDEF

  46. 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

  47. Making UDEF Real in the Supply Chain

  48. EIA-836 EDI (X12) UDEF Property UDEF Object UDEF Role or Type of Object UDEF Type of Property UDEF ID Name Definition Valid Values Name D 5 alphanumeric character A Commercial and Government Entity (CAGE) ... Defense Logistics Assigned DE 98 + DE 66/ Code M4 Identifier CAGE Code Enterprise 3_6.35.8 A standard NATO supply code ... DE 98/ Code M9 + DE 66/ Code 37 NATO Assigned NSCM Code string Identifier Manufacturer Enterprise ah.3_10.35.8 AIA MHP Mapping Matrix Summary 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

  49. Concept of UDEF Implementation Other MetadataRepositories Vendors with Canonical Models Interfaces to Legacy Systems Run Time Web Public Transformation Engines Internet Global UDEF Registry Interface Developers Design Time • Data Dictionary • Mapping Matrices • Std Data Models Data Modelers Software Vendors With UDEF ID APIs Administrator UDEF Based Metadata Registry/Repository UDEF Change Board Content Administrators

  50. The UDEF Business Model • What is the market size for a UDEF registry/repository solution? • Companies and government organizations that have multiple back-office systems supporting their B2B supply chains • 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 years • Many more will receive the benefits through the vendor products • Vendors 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 launch 2. How much will it cost the .org to deploy a UDEF registry/repository? • Initial (Start-up) – Public launch 1st Qtr 2004 – Selected .org will work jointly with AIA and EIDX at manpower level necessary to support launch target • Help build Web site and provide server – 0.25 people years • Marketing and pilot support – 1.5 people years • Selected .org will participate in pilot in 3rd Qtr 2003 • Ongoing production operations – • Quality control manpower (to have apps listed) – at least self sustaining • Maintain and administer Web site (fixed cost) 1.0 person • Manage change process (administer change control board), approve bug fixes – 1.5 people • Add matrices as submitted by industry associations (assumes one of above will accomplish) • Training manpower – at least self sustaining • Marketing – to be determined by the .org to support AIA/EIDX minimum requirements

More Related