1 / 29

The OASIS Symposium on the Future of XML Vocabularies

The OASIS Symposium on the Future of XML Vocabularies. Multi-Layer XML Data Model for EPC/RFID Ash Parikh Robert Smik. Presentation Agenda. Introductions The Next-Gen Supply Chain What Makes XML Ideally Suited for EPC/RFID Data?

thao
Download Presentation

The OASIS Symposium on the Future of XML Vocabularies

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. The OASIS Symposium on the Future of XML Vocabularies Multi-Layer XML Data Model for EPC/RFID Ash Parikh Robert Smik

  2. Presentation Agenda • Introductions • The Next-Gen Supply Chain • What Makes XML Ideally Suited for EPC/RFID Data? • The Multi-Layer Data Model Vocabulary And Schemas For EPC/RFID • The MLDM and Other OASIS Standards – Working Together In The EPC/RFID Domain • Benefits of the MLDM • Q&A

  3. Introductions

  4. About Us • Speakers • Ash Parikh (ash.parikh@rainingdata.com) • Director of Development And Technology - Enterprise Applications Group, Raining Data Corporation • Robert Smik (robert.smik@rainingdata.com) • Lead Architect - Enterprise Applications Group, Raining Data Corporation • Raining Data Corporation • A Public XML, Web Services and Data Management Software Company • Over 30 Years of Successful Operating History • 22m+ Revenue Per Year • Public Company (RDTA) • Customers Successes Across All Industries • Active on Standards Bodies / Orgs • OASIS, EPCGlobal, W3C, MIT Auto-ID Labs,, JCP, CDISC, HL7

  5. The Next-Gen Supply Chain

  6. The Next-Gen Supply Chain Is… • The Next-Gen Supply Chain Is Made Up Of New Technologies That Provide A Greater Degree Of: • AUTOMATION • VISIBILITY • CONTROL • The Next-Gen Supply Chain Is Designed To Remove: • TIME, • COST, • COMPLEXITY …. Out Of The Equation

  7. Our Hypothesis • The Issue Is That Many Existing And Valuable Technologies And Standards Are Converging…. • Customer Relationship Management (CRM) + • Order Management Systems (OMS) + • Enterprise Resource Planning Systems (ERP) + • Web Services Definition Language (WSDL) + • Business Process Execution Language (BPEL) + • E-Business Xtensible Mark-up Language (ebXML) + • Automatic Identification and Capture (AIDC) + • Radio Frequency Identification Systems (RFID) + • Object Naming Service (ONS) + • Electronic Product Code (EPC) + • … • Supply Chain Planning (SCP) + • Supply Chain Event Management (SCEM) + • Supply Chain Integration (SCI) + • Supply Chain Execution Systems (SCES) + • Warehouse Management Systems (WMS) + • Manufacturing Resource Planning Systems (MRP) + • Transportation Management Systems (TMS) + • Global Trade Identification Number (GTIN) + • Global Location Number (GLN) + • Global Data Synchronization Network (GDSN) • Product Information Management(PIM) + • To Realize Real ROI, The Next-Gen Supply Chain Should Focus On Using These Technologies To Drive Visibility And Control Of: • Goods • Funds • Information

  8. Next-Gen Supply Chain And The Technology Evolution • The Opportunity: • 90% Of Real Gains In Deploying RFID/EPC Solutions Will Happen In The COLLABORATION Zone. • The Challenge: • Using XML And Web Services Technologies To Work Together In A Standards-Based Manner To Improve The Velocity And Flow Of Funds, Goods And Information Throughout Complex Global Supply Chains While Reducing Production, Distribution and Inventory Costs.

  9. What Makes XML Ideally Suited for EPC/RFID Data?

  10. XML’s Relevant Benefits For EPC/RFID • EPC/RFID Data and Supply-Chain Applications In The Domain: • Most of the EPC/RFID Standards Are XML-Based • Data Should Be Represented In An Hierarchical Structure • Involves Multiple Data Types – EPC, Sensor, Location, PO, ASN, ePedigree, etc. • Requires Querying and Transformation Of Data • XML And Related Technologies Such As XQuery, XSLT…: • XML Can Embed Multiple Data Types • XML Can Embed Existing Data • XML Can Represent Data In A Hierarchical Structure • XML Can Re-Use Technology And Enable Inter-System Integrations • XQuery Can Provide A Single Point Of Access To All Enterprise Systems • XQuery / XSLT Can Be Used To Transform Into and From Multiple Formats • XQuery Allows the Comparison And Aggregation Of Data • XML And Related Technologies Have Rapid Adoption By The Industry

  11. The Multi-Layer Data Model Vocabulary And Schemas For EPC/RFID A Joint Research Effort Between Raining Data Corporation And MIT Web Services WAN SIG Tentative Release Date July 2005

  12. The Next-Gen Supply Chain – EPC/RFID EPC NETWORK FUNCTIONAL STACK FEDERATED EPC NETWORK

  13. The Multi-Layer Data Model Layers COARSE GRAINED XML XML GRANULARITY OF INFORMATION AND EVENTS XQUERY FINE GRAINED

  14. APPLICATION LEVEL EVENT (ALE) INTERFACE • ALE – Main API Class will look like this: • define(specname:String, spec:ECSpec) :void • undefined(specName:String) :void • getECSpec(specName:String) : ECSpec • getECSpecNames() : List //returns a list of spec names • subscribe(specName:String, notificationURI:string) : void • unsubscribe(specName:String, notificationURI:string) : void • poll(specName:String) : ECReports • immediate(spec:ECSpec) : ECReports • getSubscribers(specName:String) : List //of notification URIS • getStandardVersion() : String • getVendorVersion() : String • <<extension point>> ECSpec details: readers: List //list of logical reader names boundaries: ECBoundarySpec reportSpecs: List //list of one or more ECReportSpec instances includeSpecInreport: Boolean ECBoundarySpec, specifies how the beginning and end of event cycles are to be determined: startTrigger : ECTrigger repeatPeriod : ECTime stopTrigger : ECTrigger duration : ECTime stableSetIntervals : ECTime <<extension point>>

  15. APPLICATION LEVEL EVENT – CONT. ECTime, denotes a span of time measured in physical time units: duration : long unit : ECTimeUnit  milliseconds ECReportSpec, specifies one report to be returned from executing an event cycle. An ECSpec contains a list of one or more ECReportSpec instances: reportName : string reportSet: ECReportSetSpec filter : ECFilterSpec group : ECGroupSpec output : ECReportOutputSpec reportIfEmpty : Boolean reportOnlyOnChange : Boolean ECReportSetSpec: CURRENT | ADDITIONS | DELETIONS ECFilterSpec, specifies what EPCs are to be included in the final report. IncludePatterns : List //list of epc patterns excludePatterns : List //list of epc patterns to exclude

  16. ObserveEvent Time = 1:23pm 15 Mar 2004 EPC = urn:epc:id:sgtin:0614141.100734.400 bizStep = shipping bizLocation = urn:epc:id:sgln:0614141.12345.0 Event field Event Data Master Data BizStep Vocabulary receivingshipping … bizLocationRequired = true… BizLocation Vocabulary urn:epc:id:sgln:0614141.12345.0urn:epc:id:sgln:0614141.33254.0urn:epc:id:sgln:0614141.33254.1… address = 123 Elm Stcity = AnytownpostalCode = 12345…… Master Data Vocabularies Master Data Attributes Event & Master Data

  17. Capture - Core Event Types • EPCISEvent - is intended to serve as a generic base class for all event types in this module as well as others. • ObjectEvent - represents an event that happened to one or more entities denoted by EPCs. Includes list of EPCs in this object. • AssociationEvent - represents an event that implies an association between one or more entities denoted by EPCs. Example: aggregation (different EPCs) • QuantityEvent - represents an event concerned with a specific quantity of entities sharing a common EPC class, but where the individual identities of the entities are not known. (Individual not reported)

  18. EPCIS Query Interface

  19. Schema For L1: Raw EPC/Sensor Data Feed Events

  20. Schema For L2: EPC Filtered Events

  21. Schema For L3: EPC Business Events

  22. Schema For L4: EPC Edge Events

  23. Schema For L5: EPC Coordination Events

  24. Schema For L6: Enterprise Application Events

  25. The MLDM And Other OASIS Standards – Working Together In The EPC/RFID Domain

  26. The OASIS Standards And The MLDM REQUIREMENTS AND CAPABILITIES OF THE WEB SERVICE/ TRADING PARTNER AGREM. CPPA BUSINESS PROCESS AND SERVICE ORCHESTRATION. WS-BPEL/eb BP DISCOVERY AND AGGREGATION ebXML REGISTRY TRANSACTIONS (ACID) ebMSH COORDINATION OF WORK BETWEEN WEB SERVICES ROUTING OF MESSAGES MESSAGE PAYLOAD SOAP EPC NETWORK AND MLDM FUNCTIONAL STACK OASIS WEB SERVICES STANDARDS STACK LOGICAL STACK

  27. Benefits Of The MLDM

  28. Benefits Of The MLDM • The MLDM Recommends A Standards-Based XML Model For Data And Metadata • It Can Be Used For Representing Information And The Flow Of Information In A Value Chain Covering All Domains • It Can Be Combined With Other XML-Based Standards To Enable 100% COLLABORATION Between Collaborators In The Value Chain • It Can Be Used To Represent And Model Events and Business Processes Ranging From Coarsest To Finest In Granularity

  29. The OASIS Symposium on the Future of XML Vocabularies Multi-Layer XML Data Model for EPC/RFID Ash Parikh Robert Smik

More Related