Presentation is loading. Please wait.

Presentation is loading. Please wait.

A UDEF-Based Approach to Semantics Equivalency December 2004 EIDX/CompTIA Conference Ron Schuldt Lockheed Martin December 1, 2004.

Similar presentations


Presentation on theme: "A UDEF-Based Approach to Semantics Equivalency December 2004 EIDX/CompTIA Conference Ron Schuldt Lockheed Martin December 1, 2004."— 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 The problem is the lack of common semantics and schema between organizations DoD NASA DHS ShipRetail Trans Aero Chem Elec Banks Other Organization

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 All new XML Schema used or built by an organization must conform to W3C XML and XML Schema specifications » » Adopt global naming convention standard – ISO/IEC Adopt global naming convention standard – ISO/IEC » Adopt United Nations XML schema naming and design rules Adopt United Nations XML schema naming and design rules » XML Schema Payload Requirements Adopt global set of basic data representation terms and their definitions – e.g., Amount, Date, Name, Quantity 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 Adopt global and industry XML schema payload standards whenever possible before building organization unique XML schema – see example list on next slide 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 »Participants - ERP and middleware vendors and end users »Example payloads – RFQ, purchase order, invoice, bill of material HL7 - Health Care »Participants – health care providers across the globe »Example payload – health records ACORD – XML for the Insurance Industry »Participants – insurance providers across the globe »Example payload – insurance claim XBRL – Business Reporting - Accounting »Participants – accounting firms across the globe »Example payload – financial reports to SEC EIA-836 – Configuration Management Data Exchange and Interoperability »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 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 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 Data Element Name Object Class Term 0...n qualifiers + 1 or more required Object Class + Example UDEF-Based Data Element Names Document Abstract Text Enterprise Name Product Price Amount Product Scheduled Delivery Date Engineering Design Process Cost Amount UDEF Object Class List Entity Document Enterprise Place Program Product Process Person Asset Law-Rule Environment Condition Liability Animal Plant Mineral Property Term 0..n qualifiers + 1 required Property ebXML Property List Amount Code Date Date Time Graphic Identifier Indicator Measure Name Percent Picture Quantity Rate Text Time Value Sound Video An Instantiation of ISO Naming Convention and Supports ebXML UDEF names follow the rules of English – qualifiers precede the word they modify ISO Naming Convention

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

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 Agreement on Basic Data Types is Fundamental to Interoperability ebXML UDEF Property UDEF Naming Convention

9 UDEF Objects Establish Context PersonAsset Product Laws-Rules Process Document Enterprise A Enterprise B Program Resources Environmen t Plac e Entit y Condition Liability Anima l Plan t Minera l Basic Objects Applicable to Any Enterprise UDEF Naming Convention

10 UDEF Ontology UDEF Trees 16 Object Class Trees18 Property Trees EntityAssetDocumentAmountCode …… Order ChangeWork Technical t Purchase 201 a bcd Type Defined … Region… 41 … … Purchase Order Document_Type Code has UDEF ID = d.t.2_33.4 See

11 UDEF Structured IDs are the Key Computers can readily handle UDEF IDs that are similar to IP addresses 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_ UDEF Universal Identifier Product(9)_Manufacturer(9).Assigned (35).Identifier(8) N (N-1) mapping effort instead becomes a 2N mapping effort

12 Example – UDEF Use With XML UDEF Name Purchase Order Document_Identifier UDEF ID = d.t.2_8 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 System B (OAGIS 7.x Format) System A (xCBL 3.x Format) Two different systems with need to exchange purchase order data – live demo at May 2003 EIDX meeting UDEF derived intelligent ID is thekey to systems integration Mapping to UDEF is a rules-based approach to determine semantic equivalence

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

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

15 DoDs Unique ID (UID) UID is 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. EID Original Part Number1234 Serial Number Extracted from DoDs UID Overview – 29 July presentation

16 UID In The Supply Chain EI PN 200H0028 SN * Item Markings EI PN 218H2861 SN * Item Markings EI PN 210H0611 SN * EI PN 216H1439 SN * Prime Tier 1 Tier 2 Tier 3 Enterprise Supply ChainUnique ItemsProduct Data End Item Specs Subassembly Specs Component Specs Part Specs PN 210H0611 PN 200H0028 PN 216H1439 PN 218H2861 Item Markings UN H Delivery to Govt List of Hardware UIDs List of Hardware UIDs UID ** UN H UN H UN H List of Hardware UIDs Delivery to Govt (Optional) Spares End Item UID = Unique Identifier; EI = Enterprise Identifier PN = Part Number; SN = Serial Number * Serialized within the part number using DUNS **UN = Issuing Agency Code for DUNS Extracted from DoDs UID Overview – 29 July presentation

17 UDEF Offers Additional UID Metadata EI PN 200H0028 SN * Item Markings EI PN 218H2861 SN * Item Markings Prime Tier N Enterprise Supply ChainUnique ItemsProduct Data End Item Specs Part Specs PN 200H0028 PN 218H2861 Delivery to Govt UID ** UN H UN H Spares UID = Unique Identifier; EI = Enterprise Identifier PN = Part Number; SN = Serial Number * Serialized within the part number using DUNS **UN = Issuing Agency Code for DUNS Weapon System Product Manufacturer Assigned Identifier – a.ai.9_ Weapon System Product Globally Unique Identifier – a.ai.9_54.8 Manufacturer Enterprise DUNS Assigned Identifier -- ah.3_ Part Product Manufacturer Assigned Identifier – g.9_ Part Product Globally Unique Identifier – g.9_54.8 Extracted from DoDs 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 UDEF names are unambiguousUDEF 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 expertUDEF 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 DPASPriority Purchase Order Document Government Assigned Priority Code PurchaseOrder/Header/Priority SysName UDEF Name OAGIS XML Path Name DateOfOrder Purchase Order Document Date PurchaseOrder/Header/DocumentDateTime Examples From DoD Purchase Order Mapped to UDEF and OAGIS 8.0 IssuedByDODAAC Buyer Enterprise Defense Logistics Agency Assigned Identifier PurchaseOrder/Header/Parties/ SoldToParty/PartyID/ID UDEF ID d.t.2_ d.t.2_6 q.3_6.35.8

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 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 AIAs Radar Screen of Standards SCOR Monitor Participate in Development Development Endorse Explore Use X12 EDI STEP OAGIS XML Candidate Track SAML XML GTPA GECA Adopted EIA 836 ebXML X.509 PKI UDEF SOAP UDDI Boost Aero

22 For Additional Information ISO/IEC – Specification and standardization of data elements Article published at ebXML Forum – an online free publication – compares UDEF to ebXML Core Components UDEF.ORG Web Site Ron Schuldt – or


Download ppt "A UDEF-Based Approach to Semantics Equivalency December 2004 EIDX/CompTIA Conference Ron Schuldt Lockheed Martin December 1, 2004."

Similar presentations


Ads by Google