1. Universal Data Element Framework (UDEF) The Semantic DNS and a Disaster Response Pilot Use Case Ron Schuldt, Chair The Open Group UDEF Forum December 6, 2005

2. Agenda The Problem The UDEF The Open Group UDEF participants UDEF current status The problem and associated UDEF business value What the UDEF is and what it is not A brief description of the UDEF A metadata managed architecture that UDEF supports UDEF – Like A Semantic DNS The UDEF Disaster Response Pilot Use Case A brief description of a UDEF pilot to support disaster response teams Video clip of the UDEF disaster response pilot demo as of December 1, 2005

3. The Problem

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

5. Problem – Internal Perspective 111-222-333 Though semantically equal, the following are 4 different XML tag names App BApp C App A Other Apps Legacy Data Conflicting semantic overlaps between back-office systems

6. The Legacy Applications Issue Across the globe there are millions of legacy applications that need to be Web enabled – in preparation for Web Services and SOA -XML and associated W3C standards address the syntax requirements but an adopted semantics standard does not exist yet Users of the legacy applications consistently resist changing the names of the fields -The semantics solution needs to be non-intrusive to the application user

7. The UDEF

8. l The Open Group Staff l Lockheed Martin l Unicorn l Safyre Solutions l IBM l Raytheon l Boeing l Capgemini l SICoP l BEA Systems l Adobe l Contivo l Cemantica l OMG l OAGi l NDIA-AFEI l GEIA l CompTIA l W3C Semantic Web l RosettaNet l POSC l SWIFT l Dublin Core Metadata l Global Exchange Services l Chevron Texaco l Proctor & Gamble l Northrop Grumman l SAIC l ManTech l MITRE l Envision l Metamatrix l Ericsson l DLA l Canadian Government l Penn State University The Open Group UDEF Participants And others

9. UDEF Current Status As of May 2005, UDEF Officially Adopted by The Open Group Goal - establish the UDEF as the universally-used categorization system for data Develop and maintain the UDEF as an open standard Advocate and promote it Put in place a technical infrastructure to support it Implement a Registry for it, and Set up education programs to train information professionals in its use. Actual UDEF Trees are Viewable Online http://www.opengroup.org/udefinfo/defs.htm UDEF Pilot Submitted to Federal Semantic Interoperability Community of Practice (SICoP) To enable manufacturing industry to support disaster response teams Live UDEF Disaster Response use case demo shown October 20, 2005 at The Open Group Semantic Interoperability Conference in Houston – captured on video – updated on December 1, 2005

10. The Goal Current Point-to-Point Approach --- n(n-1) Global Semantics Standard Approach --- 2n $$ Savings Global Semantics Standard 0 50 100 150 200 250 300 350 400 1234567891011121314151617181920 Reduce Requirements and Design-Time Phase Semantics Analysis Time and Cost

11. UDEF Value Proposition Typical Interface Build Tasks l Analyze and document the business requirements. l Analyze and document the data interfaces (design time) u Compare data dictionaries u Identify gaps u Identify disparate forms of representation l Perform data transformations as required at run time u Transform those data that require it API 1 Sys 1 API 2 Sys 2 UDEF ID Sys 2 Data NamesSys 1 Data Names UID Part Price Part UOM Ship Qty Part Ser Part Descr Part Num PO Line Num Ship To ID Ship From Bus ID Business Id Accept Loc Date Ship PO Num Part UID Prod Unit Price Prod Unit Qty Ship Prod Ser Prod Descr Prod Number Order Line Ship To Code Ship From Code Company Code Accept Point Ship Dt Order ID 9_54.8 9_1.2.1 9_1.18.4 9_10.11 9_1.1.31.8 9_9.14.14 9_9.35.8 d.t.2_1.17.8 a.a.v.3_6.35.8 3_6.35.8 3_6.35.8 i.0_1.1.71.4 9_1.32.6 d.t.2_13.35.8 Reduces dependency on system expert Allows automated compare UDEF Value Reduce design time labor Step toward automated transform

12. UDEF – Is and Is Not UDEF Is Not …… A software application However, software applications need to adopt UDEF within their APIs Another data standard It acts as the glue to tie data standards together Another ontology It could help build the bridge between ontologies UDEF Is …… A “loose coupling” method for integrating semantics across disparate systems Allows automation to help align disparate systems – thereby reducing the design-time phase that is typically manual A standards compliant rules- based naming convention Conforms to ISO/IEC 11179 and to ebXML Core Components Evolving to become a global open standard – a Semantic DNS

13. 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 Event 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 11179-5 Naming Convention and Supports ebXML UDEF names follow the rules of English – qualifiers precede the word they modify ISO 11179-5 Naming Convention

14. ISO/IEC 11179 – Data Element Concept Data Element Concept Data Element Value Domain ObjectClass PropertyRepresentation Core Data Element Application Data Element UDEF Maps Data Element Concepts

15. Creating UDEF IDs UDEF Trees 17 Object Class Trees18 Property Trees EntityAssetDocumentAmountCode …… Order ChangeWork Technical t Purchase 201 a bcd Type Defined … Region… 41 … 1 33 66 … Purchase Order Document_Type Code has UDEF ID = d.t.2_33.4 See http://www.opengroup.org/udefinfo/defs.htmhttp://www.opengroup.org/udefinfo/defs.htm

16. Example Mappings 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 Organizations cannot avoid multiple data standards ** Need global semantics standard **

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

18. UDEF – Like A Semantic DNS

19. Like A Semantic DNS Emergency Management Inventory Transportation Geographic Location Electrical Goods A Few Example Domain Ontologies UDEF Domain Concept Service

20. Realizing The UDEF Registry UDEF Registry in Unicorn UDEF Term UDEF Object UDEF Property Unicorn Semantic Mapping Semantic Class Mapping Semantic Property Mapping

21. UDEF Disaster Response Pilot Use Case

22. l The Open Group Staff l Lockheed Martin l Unicorn l Safyre Solutions UDEF Pilot Participants

23. Pilot Summary Natural disaster response team shows up lacking batteries to operate GPS system and walkie-talkie for 200 search and rescue workers – need eight hundred 9-volt batteries to even begin the search and rescue effort Assumes that UDEF has been adopted globally and that UDEF IDs are exposed at company portals Goal – determine if resources might be available nearby within a manufacturer’s or supplier’s inventory Uses two UDEF tags (IDs) to locate available resources in a battery manufacturer’s inventory near the response team command center – an ad hoc query since formal interface not previously defined Use UDEF ID tags to support semantic integration of disparate procurement applications that use different purchase order semantics Two vendors currently involved – Unicorn and Safyre Solutions

24. UDEF Disaster Response Architecture HTTP/XML NineVolt.Lithium.Battery.PRODUCT_Inventory.QUANTITY a.a.aj.9_36.11 NineVolt.Lithium.Battery.PRODUCT_Postal.Zone.CODE a.a.aj.9_1.10.4 Two UDEF IDs in outbound message Open Group Global UDEF Registry/Repository Battery Manufacturers’ Industry UDEF Registry

25. UDEF Disaster Response Video

26. UDEF – Like A Semantic DNS Index Domain Ontologies UDEF Domain Concept Service

27. 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 The OPEN GROUP UDEF Forum Web Site http://www.opengroup.org/udef/ Videos of the live UDEF Disaster Response Pilot demo http://www.opengroup.org/udefinfo/demo0511/demos.htmhttp://www.opengroup.org/udefinfo/demo0511/demos.htm Oct 20, 2005 http://www.opengroup.org/projects/udef/doc.tpl?CALLER=index.tpl&gdid=9189http://www.opengroup.org/projects/udef/doc.tpl?CALLER=index.tpl&gdid=9189 Dec 1, 2005 For Possible Follow-up Implementations - Contact Dr. Chris Harding – c.harding@opengroup.orgc.harding@opengroup.org Ron Schuldt – ron.l.schuldt@lmco.comron.l.schuldt@lmco.com Loren Osborn – loren.osborn@unicorn.comloren.osborn@unicorn.com Al Slater – aslater@safyre.comaslater@safyre.com