A UDEFBased Approach to Semantics Equivalency December 2004

A UDEF-Based Approach to Semantics Equivalency December 2004 EIDX/Comp. TIA 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 Elec Banks Chem Aero Do. D NASA Trans Organization DHS Other Ship Retail The problem is the lack of common semantics and schema between organizations

Derived XML Schema Requirements XML Schema “Structure” Requirements • All new XML Schema used or built by an organization must conform to W 3 C XML and XML Schema specifications » http: //w 3. org/TR/2004/REC-xml 11 -20040204/ » http: //w 3. org/XML/Schema#dev • Adopt global naming convention standard – ISO/IEC 11179 -5 » http: //isotc. iso. ch/livelink/fetch/2000/2489/Ittf_Home/Publicly. Available. Standards. 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

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 • HL 7 - Health Care http: //www. hl 7. 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 Interoperability http: //63. 249. 145. 5/836/default. htm » Participants – Do. D and aerospace and defense industry (AIA and GEIA) » Example payload – engineering change

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

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

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 HL 7 EIA-836 PLCS …. XML Schema “Structure” Standards ISO/IEC 11179 -5, eb. XML CCTS, UN Naming and Design Rules W 3 C – XML, XML Schema Others

UDEF Basic Data Types • Amount - Amount • Binary Object (Graphic, Picture, Sound, Video) – Graphic, Picture, Sound, Video UDEF Naming Convention • 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 eb. XML UDEF Property Agreement on Basic Data Types is Fundamental to Interoperability

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

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

UDEF Structured IDs are the Key PDM Sys A PDM Sys B Part No Part Num OAGIS 7. 1 Rosetta. Net Item. X Proprietary. Product. Identifier 9_9. 35. 8 X 12 (EDI) EDIFACT Product/Service ID Item Number STEP AP 203 x. CBL Product ID Part. ID UDEF Universal Identifier Product(9)_Manufacturer(9). Assigned (35). Identifier(8) N (N-1) mapping effort instead becomes a 2 N mapping effort Computers can readily handle UDEF IDs that are similar to IP addresses

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 (x. CBL 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/Udef. Report 1

Systems Interface - Gap Analysis Challenge: Minimize Effort To Semantically Align Systems API 1 Sys A API 2 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 **

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

Do. D’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. . . EID 194532636 Original Part Number 1234 Serial Number 786950 Extracted from Do. D’s “UID Overview – 29 July” presentation

UID In The Supply Chain Product Data Supply Chain Item Markings Enterprise Prime Unique Items UN 194532636200 H 0028003896 EI 194532636 PN 200 H 0028 SN 003896* PN 200 H 0028 Delivery to Govt End Item Specs End Item Markings Tier 1 EI 040535536 PN 210 H 0611 SN 006392* PN 210 H 0611 Subassembly Specs Tier 2 PN 216 H 1439 EI 080907280 PN 216 H 1439 SN 020890* Component Specs Tier 3 Spares PN 218 H 2861 Part Specs UID = Unique Identifier; EI = Enterprise Identifier PN = Part Number; SN = Serial Number EI 083949107 PN 218 H 2861 SN 105742* * Serialized within the part number using DUNS Extracted from Do. D’s “UID Overview – 29 July” presentation (Optional) List of Hardware UIDs (Optional) UN 080907280216 H 1439020890 Delivery to Govt Item Markings List of Hardware UIDs UN 040535536210 H 0611006392 Delivery to Govt Item Markings UID ** Spares List of Hardware UIDs (Optional) UN 083949107218 H 2861105742 Delivery to Govt Spares **UN = Issuing Agency Code for DUNS

UDEF Offers Additional UID Metadata Product Data Supply Chain Item Markings Enterprise Prime Unique Items UID ** UN 194532636200 H 0028003896 EI 194532636 PN 200 H 0028 SN 003896* PN 200 H 0028 End Item Specs Manufacturer Enterprise DUNS Assigned Identifier -- ah. 3_5. 35. 8 Weapon System Product Manufacturer Assigned Identifier – a. ai. 9_9. 35. 8 Weapon System Product Globally Unique Identifier – a. ai. 9_54. 8 Manufacturer Enterprise DUNS Assigned Identifier -- ah. 3_5. 35. 8 Part Product Manufacturer Assigned Identifier – g. 9_9. 35. 8 Part Product Globally Unique Identifier – g. 9_54. 8 Item Markings Tier N PN 218 H 2861 Part Specs UID = Unique Identifier; EI = Enterprise Identifier PN = Part Number; SN = Serial Number EI 083949107 PN 218 H 2861 SN 105742* * Serialized within the part number using DUNS Extracted from Do. D’s “UID Overview – 29 July” presentation UN 083949107218 H 2861105742 Delivery to Govt Spares **UN = Issuing Agency Code for DUNS

Do. D End-to-End Procurement Mapping • AIA effort by Raytheon, Lockheed Martin and Northrop Grumman based on actual Do. D 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, DD 250, Invoice • DD 250 includes the 16 fields required to support UID

UDEF Example Mappings Examples From Do. D Purchase Order Mapped to UDEF and OAGIS 8. 0 UDEF Name UDEF ID Sys. Name DPASPriority OAGIS XML Path Name Purchase Order Document Government Assigned Priority Code Purchase. Order/Header/Priority d. t. 2_1. 4. 31. 4 Date. Of. Order Purchase Order Document Date Purchase. Order/Header/Document. Date. Time d. t. 2_6 Issued. By. DODAAC Buyer Enterprise Defense Logistics Agency Assigned Identifier q. 3_6. 35. 8 Purchase. Order/Header/Parties/ Sold. To. Party/Party. ID/ID • 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”

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 “B 2 B standard targets integration” http: //www. nwfusion. com/news/2004/0329 udef. 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

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

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