Open Standards that Open Markets™ © Open Applications Group Copyright 2015 Open Applications Group, Inc. Semantics Refinement Methods and Tools Serm Kulvatunyou – NIST Michael Rowell – Oracle David Connelly – OAGi April 20, 2016

Open Standards that Open Markets™ Agenda Working Group Members Motivation Objective and Scope Current Status and Next Step Conclusion from the Last meeting Demo of prototype

Open Standards that Open Markets™ Working Group Members Serm Kulvatunyou, NIST – Chair Mike Rowell, Oracle – Co-Chair Steffen Fohn, ADP Jim Wilson, OAGi & AgGateWay Jeff Rice, Boeing Kevin Himka, Boeing Roger Hills, Boeing Jerry Gersgman, Boeing Yunsu Lee, NIST Jaehun Lee, NIST Hakju Oh, NIST Taehun Kim, NIST David Connelly, OAGi Scott Nieman, Land O’ Lakes Ian Hedges, E2Open Satish Ramanathan, Oracle Hyunbo Cho, Thira & POSTECH Kurt Kanaskie, Merck Kim Bartkus, HR-XML

Open Standards that Open Markets™ Motivations 4 © Open Applications Group, 2015 All Rights Reserved

Open Standards that Open Markets™ Problem: A Complex Standard Automotive AerospaceDefenseChemicalHigh-techConstruction Supply Chain – Material Management, Order Orchestration Front Office - CRM Operation – MOM, PLM, Project Management Back Office – Financials, Accounting, HCM Logistics – Transportation Management Edge Applications – Business Intelligence/Analytics, Demand Forecast A BOD can contain between 58 and 300k+ data fields!!!

Open Standards that Open Markets™ Need: Multiple Syntaxes Support Syntax Independent OAG Standard Production Rule for XML Schema Production Rule for JSON Schema Production Rule for OWL/RDF Schema OAG XML Schema Standard OAG JSON Schema Standard OAG RDF Schema Standard Model Cloud and Mobile Platform Cloud and Mobile Platform Enterprise Integration Platform Enterprise Integration Platform Business Intelligent Platform Model Driven Approach

Open Standards that Open Markets™ Problem: Manual Development “The OAGi Chief Architect will review all deliverables during the project to ensure maximum re-use and consistency of business content and technical architecture.” Project Definition Construct Review and Approval Publication

Open Standards that Open Markets™ Need: Life-cycle Management Functionality Gather Requirement Analyze Change/ New VerifyVersion Semantic Analysis Engine Requirement Import Guided, Model-based Formal Change Tracking

Open Standards that Open Markets™ Motivation Summary Better meta-data management for integration Simpler visualization (business user) Simpler implementation schemas (developer) More precise implementation schema More precise than existing Flatten & Filter Utility is giving Profile BOD for various syntaxes optimized for each specific environment E.g., JSON for mobile environment Different flavors of JSON – WADL, ODATA, etc. Atom for CRM Future proof for future syntaxes [Better traceability and life-cycle management of OAG standard] 9

Open Standards that Open Markets™ Objective and Scope Objective –To enable Model Driven Architecture in OAGIS utilizing CCTS method Scope –Design an RDBMS-, CCTS-based model for holding OAGIS content –Design the method to import OAGIS into the RDBMS model –Design the method to generate BIEs from the OAGIS-based CCs –Design the method to customize BIEs –Design the NDRs and method to generate standalone XML schemas from BIEs –Design the NDRs and method to generate standalone JSON schemas from CCs –Implement a POC software Future scope –Round trip export of OAGIS developer schemas –OWL/RDF model –OAGIS semantic content life-cycle management

Open Standards that Open Markets™ 11 OAGIS Model in RDBMS OAG Semantic Refinement Context OAG Syntax Specific Generation Syntax Selection OAGIS BOD EDI OAGIS BOD JSON (for Cloud & Mobile) Customer PO BOD in XML Schema (for Web Services) OAGIS BOD Atom (for Real-time Feeds) Supplier PO BOD in XML Schema (for Web Services) Customer Blanket PO BOD in XML Schema (for Web Services) Domain Expert Semantically Precise Message Definition (Restrict & Extend) Requirement Developer

Open Standards that Open Markets™ Current Status Completed V1 of User Requirement Analysis document (11/2014) Completed the system architecture design of the prototype, open source tool (11/2014) Completed the CCTS-based RDB model to hold the OAGIS and Profile BOD content, code list management implemented (05/2015) Completed documentation and implementation to import of the OAGIS 10.1 (05/2015) Completed the standalone XML schema design (05/2015) Completed data structure validation (not including doc) and fixes on the import (11/2015) Completed documentation and prototyping of the core BIE management functionalities (11/2015, to be demoed today) 12

Open Standards that Open Markets™ Current Status (Continue) Completed design of the BIE extension and CC management functionalities supporting the BIE extension (02/2016) Ongoing –Validate BDT and Code List import (Near Complete) –Implement the BIE extension and required CC management functionalities –JSON Schema generation => Model Generation –Document profile schema specification Plan –Alpha version available for initial testing by the next OAG meeting Issues –Several OAGIS “undocumented features” uncovered – resolved –MySQL too slow on Windows and Linux, Oracle XE has limit => Oracle DB Enterprise 13

Open Standards that Open Markets™ Highlight of the CC Management Functionality Create/Update CCs Add/Update associations UI Concurrency management –Components dependencies –Event notification –Types of events 14 © Open Applications Group, 2015 All Rights Reserved

Open Standards that Open Markets™ Discussion note from 05/2015 Meeting Database itself maybe useful New Semantic Roadmap WG REST-based API 15 © Open Applications Group, 2015 All Rights Reserved Discussion note from 11/2015 Meeting The tool can save time and travels in standard development Justtransform is interested in hosting the tool on Oracle Cloud Extension capability has more priority than JSON Additional use cases: –Where use –Impact analysis between standard releases –Usage analysis to improve the standard

Open Standards that Open Markets™ Summary Data in the database is still being validated The database should be ready with completely validated OAG data in the next 2-3 months, say July 2016 NIST will continue to prototype the BIE extension functions NIST is issuing an RFQ to harden the prototype 16 © Open Applications Group, 2015 All Rights Reserved

Open Standards that Open Markets™ 17

Open Standards that Open Markets™ Overview of CCS Modeling Methodology Core Component Business Information Entity Business Context Context Category Values Industry Context Category Business Process Context Category Electronics Manufacturing Sales Manufacturing Production Type Make-to-Stock Retail Assemble-To-Order

Open Standards that Open Markets™ Example 19 © Open Applications Group, 2015 All Rights Reserved Core Component Business Information Entity Business Context Bill of Materials Sales, Assemble-to-Order, Electronic Mfg Sales, Assemble-to-Order, Electronic Mfg Super BOM Bill of Materials Manufacturing, Assemble-to-Order, Electronic Mfg Manufacturing, Assemble-to-Order, Electronic Mfg Manufacturing BOM Bill of Materials Fulfillment, Assemble-to-Order, Electronic Mfg Fulfillment, Assemble-to-Order, Electronic Mfg Instance BOM Bill of Materials Sales, Retail Bundle Items, Specs, & Rules Items & Specs Items & Serial No. Items

Open Standards that Open Markets™ 20 © Open Applications Group, 2015 All Rights Reserved THE END

Open Standards that Open Markets™ XML Vs. JSON XML: 294 Chars JSON: 152 Chars

Open Standards that Open Markets™ Functional Requirements to CCS Mapping Syntax Independent BOD Semantic Restriction Syntax Independent, Context Specific Profile BOD Usage Situation Syntax Specific Generation Profile BOD in JSON Schema Profile BOD in XML Schema Core Component Business Context Business Information Entity

Open Standards that Open Markets™ Standalone Schema Design Local elements Anonymous type for: –ABIEs (e.g., BOD, Noun, Component) –BBIEs (i.e., Field) Global type for: –BDTs: Use GUID in the type name –Code lists: Use Agency ID, Scheme ID, and Version ID in the name Use the same OAGIS namespace No inheritance No xsd:group Unique BIE GUID Business context and CCTS documentation included 23

Open Standards that Open Markets™ Highlight of BIE Management Functionality For each context –Restrict fields –Assign data type restriction –Assign code list restriction –Assign business term –Customize description –Extension –Assign status, e.g., development, test, production –Give version number 24

Open Standards that Open Markets™ Database Model 25 Total 34 tables and 267 columns

Open Standards that Open Markets™ System Architecture 26 RDBMS (MySQL) RDBMS (MySQL) Storage Application Communication Presentation JRE (Oracle Java) Web Server & Web Container (Apache Tomcat) Web Browser (HTML, CSS, JQuery, JSF) Web Browser (HTML, CSS, JQuery, JSF) Java App (RCP) Java App (RCP) HTTP Semantic Refinement Application & Services OR

Open Standards that Open Markets™ Next Steps Fix bugs from OAGIS import that starts to surface Document standalone schema NDR and generation logic Prototype top-level ABIE (BOD) customization –Assign code list –BIE/CC-based extension Prototype the standalone generation Prototype other BIE management use cases Design JSON generation 27

Open Standards that Open Markets™ Check Sum Validation The number of entities in DB VS. XML Schema There are some mismatches due to: –Entities unused by any BOD ACC: 83 ASCCP and BCCP: 72 –xsd:Group –Entities with missing GUIDs 3 global elements with no GUID 2 attributes with no GUID 18 element references with no GUID 28

Open Standards that Open Markets™ Database Tables Import of the OAGIS data model Top-down import –Pros: Faster, easier to find references (compared to bottom-up) –Cons: Content unused by BODs are not imported Using Apache Xerces and Xpath to parse XML Schema Needed to modify Xerces to handle GUID & xsd:Group 29 ACC ASCC ASCCP Component.xsd Fields.xsd BCCP

Open Standards that Open Markets™ Design Choices for DB Interaction 30 To isolates details of database from a business logic No database specific information in the code Just need to know table names and operational methods in the interface or abstract class DAOFactory df = DAOFactory.getDAOFactory(); SRTDAO dao = df.getDAO(“ABIE"); dao.findObjects(); dao.insertObjects(SRTObject); dao.deleteObject(SRTObject); dao.updateObject(SRTObject); DAOFactory df = DAOFactory.getDAOFactory(); SRTDAO dao = df.getDAO(“ABIE"); dao.findObjects(); dao.insertObjects(SRTObject); dao.deleteObject(SRTObject); dao.updateObject(SRTObject);

Open Standards that Open Markets™ Content Validation Verification will be done through the export of OAGIS content Exporting OAGIS model is not in scope at this point, so we will validate only with OAGIS standalone schemas A batch program needs to be developed to export all OAGIS standalone BODs and compare them with the existing standalone BODs in the OAGIS distribution 31

Open Standards that Open Markets™ Issues GUID of BIEs IST BODs - Ignored Mismatches in the Check Sum validation –Entities unused by any BODs  to be determined in the OAGIS general group what to do with them Challenges in the Content Validation –If there is an error, possible causes can come one or more of the three sources: The OAGIS import code The standalone export code The standalone schema generator code which generates the standalone schemas in the OAGIS distribution 32