1 / 22

A UDEF-Based Approach to Semantics Equivalency December 2004 EIDX/CompTIA Conference

A UDEF-Based Approach to Semantics Equivalency December 2004 EIDX/CompTIA Conference. Ron Schuldt Lockheed Martin December 1, 2004. Problem – Global Perspective. Each organization is attempting to set its own semantics standard Each must interface with organizations they do not control.

gertrude-lehmann
Download Presentation

A UDEF-Based Approach to Semantics Equivalency December 2004 EIDX/CompTIA Conference

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. A UDEF-Based Approach to Semantics Equivalency December 2004 EIDX/CompTIA Conference Ron Schuldt Lockheed Martin December 1, 2004

  2. Problem – Global Perspective Each organization is attempting to set its own semantics standard Each must interface with organizations they do not control Elec Banks Chem Aero DoD Trans Organization NASA DHS Other Ship Retail The problem is the lack of common semantics and schema between organizations

  3. Derived XML Schema Requirements • XML Schema “Structure” Requirements • All new XML Schema used or built by an organization must conform to W3C XML and XML Schema specifications • http://w3.org/TR/2004/REC-xml11-20040204/ • http://w3.org/XML/Schema#dev • Adopt global naming convention standard – ISO/IEC 11179-5 • http://isotc.iso.ch/livelink/livelink/fetch/2000/2489/Ittf_Home/PubliclyAvailableStandards.htm • Adopt United Nations XML schema naming and design rules • http://www.disa.org/cefact-groups/atg/downloads/index.cfm • XML Schema “Payload” Requirements • Adopt global set of basic data representation terms and their definitions – e.g., Amount, Date, Name, Quantity • Tables 8-1 and 8-3 in United Nations Core Components Technical Specification (CCTS) – ISO 15000-5 • Adopt global and industry XML schema “payload” standards whenever possible before building organization unique XML schema – see example list on next slide

  4. Example “Payload” Standards • OAGIS – Open Applications Group http://www.openapplications.org/ • Participants - ERP and middleware vendors and end users • Example payloads – RFQ, purchase order, invoice, bill of material • HL7 - Health Care http://www.hl7.org/ • Participants – health care providers across the globe • Example payload – health records • ACORD – XML for the Insurance Industry http://www.acord.org/ • Participants – insurance providers across the globe • Example payload – insurance claim • XBRL – Business Reporting - Accounting http://www.xbrl.org/ • Participants – accounting firms across the globe • Example payload – financial reports to SEC • EIA-836 – Configuration Management Data Exchange and Interoperabilityhttp://63.249.145.5/836/default.htm • Participants – DoD and aerospace and defense industry (AIA and GEIA) • Example payload – engineering change

  5. Derived XML Schema Requirements • XML Schema “Infrastructure Support” Requirements • Organization adopted and internally developed XML schema must be easily discovered for reuse – requires a centralized registry/repository • Use Universal Data Element Framework (UDEF) as means to index the points of intersection between various XML schema “payloads” and XML instances AND to improve data understandability

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

  7. XML Schema “Standards” Stack XML Schema “Infrastructure Support” Standards Cross Standard Semantics and Metadata Alignment – UDEF, RDF, OWL XML Schema “Payload” Standards Organization Specific Implementation Conventions (subsets & extensions) OAGIS ACORD XBRL HL7 EIA-836 PLCS Others …. XML Schema “Structure” Standards ISO/IEC 11179-5, ebXML CCTS, UN Naming and Design Rules W3C – XML, XML Schema

  8. UDEF Basic Data Types • Amount - Amount • Binary Object (Graphic, Picture, Sound, Video) – Graphic, Picture, Sound, Video • Code - Code • Date Time (Date, Time) – Date, Date Time, Time • Identifier – Identifier • Indicator – Indicator • Measure – Measure • Numeric (Value, Rate, Percent) – Value, Rate, Percent • Quantity – Quantity • Text (Text, Name) – Text, Name UDEF Naming Convention UDEF Property ebXML Agreement on Basic Data Types is Fundamental to Interoperability

  9. UDEF Objects Establish Context UDEF Naming Convention Entity Enterprise B Enterprise A Place Laws-Rules Program Product Product Process Document Environment Person Asset Liability Plant Mineral Animal Condition Resources Basic Objects Applicable to Any Enterprise

  10. UDEF Ontology UDEF Trees 16 Object Class Trees 18 Property Trees 0 1 2 1 4 Entity Asset Document … Amount … Code … t 1 66 33 Order … Region … Type Defined a b c d Technical Purchase Work Change … Purchase Order Document_Type Code has UDEF ID = d.t.2_33.4 See http://www.udef.org/

  11. UDEF Structured IDs are the Key • PDM Sys A • Part No • OAGIS 7.1 • ItemX • X12 (EDI) • Product/Service ID • STEP AP 203 • Product ID • PDM Sys B • Part Num • RosettaNet • ProprietaryProductIdentifier • EDIFACT • Item Number • xCBL • PartID 9_9.35.8 UDEF Universal Identifier Product(9)_Manufacturer(9).Assigned (35).Identifier(8) N (N-1) mapping effort instead becomes a 2N mapping effort Computers can readily handle UDEF IDs that are similar to IP addresses

  12. Example – UDEF Use With XML • UDEF derived intelligent ID is the “key” to systems integration • Mapping to UDEF is a rules-based approach to determine semantic equivalence Two different systems with need to exchange purchase order data – live demo at May 2003 EIDX meeting System A (xCBL 3.x Format) UDEF Name Purchase Order Document_Identifier UDEF ID = d.t.2_8 System B (OAGIS 7.x Format) • Optional UDEF IDs applied only when aligning ANY two systems for the first time (design time) – stored as an alias within each system • Non-intrusive – does not require change to data element names • Leverage the UDEF Web Service to generate a gap analysis report • http://xml.eidx.org:8080/udef/servlet/UdefReport1

  13. Systems Interface - Gap Analysis Challenge: Minimize Effort To Semantically Align Systems API 1 API 2 Sys A Sys B Sys A Data Names UDEF ID Sys B Data Names Gap Note: UDEF ID is included in the system API’s as an alias Semantic Alignment Solution: Automate Semantic Gap Analysis with Web Service ** Significant Productivity Gain **

  14. A Metadata Managed Architecture Interfaces to Back-Office Systems Vendors with Canonical Models Run Time EAI Transformation Engines UDEF-Indexed Metadata Registries Global UDEF Registry Internet Std Schema Use Matrices Design Time • Data Dictionary • Mapping Matrices • Std XML Schema Interface Developers Extend Matrices Software Vendors with UDEF ID APIs Build/Extend Schema UDEF-Indexed Metadata Registry/Repository UDEF Change Board Web Public Data Modelers And Apps Developers • Centralized metadata registry/repository • Enables reuse to reduce costs • Encourages standardization

  15. EID 194532636 Original Part Number 1234 Serial Number 786950 DoD’s Unique ID (UID) . . . the set of data for tangible assets that is globally unique and unambiguous, ensures data integrity and data quality throughout life, and supports multi-faceted business applications and users. UID is . . . Extracted from DoD’s “UID Overview – 29 July” presentation

  16. UID In The Supply Chain Product Data Supply Chain Unique Items UID ** Item Markings Enterprise UN194532636200H0028003896 EI 194532636 PN 200H0028 SN 003896* Prime List of Hardware UIDs PN 200H0028 Delivery to Govt End Item Specs End Item (Optional) Item Markings EI 040535536 PN 210H0611 SN 006392* UN040535536210H0611006392 Tier 1 PN 210H0611 List of Hardware UIDs Delivery to Govt Subassembly Specs Spares (Optional) Item Markings EI 080907280 PN 216H1439 SN 020890* Tier 2 PN 216H1439 UN080907280216H1439020890 Delivery to Govt List of Hardware UIDs Component Specs Spares Item Markings (Optional) EI 083949107 PN 218H2861 SN 105742* Tier 3 PN 218H2861 UN083949107218H2861105742 Delivery to Govt Part Specs **UN = Issuing Agency Code for DUNS * Serialized within the part number using DUNS UID = Unique Identifier; EI = Enterprise Identifier PN = Part Number; SN = Serial Number Spares Extracted from DoD’s “UID Overview – 29 July” presentation

  17. UDEF Offers Additional UID Metadata Product Data Supply Chain Unique Items UID ** Item Markings Enterprise UN194532636200H0028003896 EI 194532636 PN 200H0028 SN 003896* Prime PN 200H0028 End Item Specs • Manufacturer EnterpriseDUNS AssignedIdentifier -- ah.3_5.35.8 • Weapon SystemProductManufacturer AssignedIdentifier – a.ai.9_9.35.8 Weapon SystemProductGlobally UniqueIdentifier – a.ai.9_54.8 • Manufacturer EnterpriseDUNS AssignedIdentifier -- ah.3_5.35.8 • Part ProductManufacturer AssignedIdentifier – g.9_9.35.8 Part ProductGlobally UniqueIdentifier – g.9_54.8 Item Markings EI 083949107 PN 218H2861 SN 105742* Tier N PN 218H2861 UN083949107218H2861105742 Delivery to Govt Part Specs **UN = Issuing Agency Code for DUNS * Serialized within the part number using DUNS UID = Unique Identifier; EI = Enterprise Identifier PN = Part Number; SN = Serial Number Spares Extracted from DoD’s “UID Overview – 29 July” presentation

  18. DoD End-to-End Procurement Mapping • AIA effort by Raytheon, Lockheed Martin and Northrop Grumman - based on actual DoD procurement of a Raytheon spare part • Mapped all fields in five documents plus Central Contractor Registration to both the UDEF and to OAGIS 8.0 XML standard • RFQ, Response to RFQ, Purchase Order, DD250, Invoice • DD250 includes the 16 fields required to support UID

  19. UDEF Example Mappings Examples From DoD Purchase Order Mapped to UDEF and OAGIS 8.0 UDEF Name SysName OAGIS XML Path Name UDEF ID DPASPriority Purchase Order Document Government Assigned Priority Code PurchaseOrder/Header/Priority d.t.2_1.4.31.4 DateOfOrder Purchase Order Document Date PurchaseOrder/Header/DocumentDateTime d.t.2_6 PurchaseOrder/Header/Parties/ SoldToParty/PartyID/ID IssuedByDODAACBuyer Enterprise Defense Logistics Agency Assigned Identifier q.3_6.35.8 • UDEF names are unambiguous • UDEF names cross-referenced and indexed by UDEF IDs to a table would allow interfaces to be built without being dependent on availability of the “system expert”

  20. UDEF In The Press "The need for UDEF is massive and inescapable, and the bigger the enterprise, the greater the need," Mark Gibbs, Consultant and Columnist for Network World, March 29, 2004 edition of Network World, article titled “B2B standard targets integration” http://www.nwfusion.com/news/2004/0329udef.html Mark Gibbs implies that bigger enterprises have more trading partners and more back-office systems that need to be integrated (internally and with their partners) and therefore have a greater need for the UDEF

  21. AIA’s Radar Screen of Standards Endorse Monitor Boost Aero EIA 836 ebXML SCOR STEP X12 EDI SOAP X.509 PKI UDEF GTPA UDDI Adopted OAGIS XML GECA SAML XML Candidate Participate in Development Explore Use Track

  22. For Additional Information • ISO/IEC 11179 – Specification and standardization of data elements • http://isotc.iso.ch/livelink/livelink/fetch/2000/2489/Ittf_Home/PubliclyAvailableStandards.htm • Article published at ebXML Forum – an online free publication – compares UDEF to ebXML Core Components • http://www.ebxmlforum.org/articles/ebFor_20040306.html • UDEF.ORG Web Site • http://www.udef.org/ Ron Schuldt – 303-977-1414 or ron.l.schuldt@lmco.com

More Related