the oasis symposium on the future of xml vocabularies
DESCRIPTION
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? - PowerPoint PPT PresentationTRANSCRIPT
The OASIS Symposium on the Future of XML Vocabularies
Multi-Layer XML Data Model for EPC/RFIDAsh Parikh
Robert Smik
2
IntroductionsThe Next-Gen Supply ChainWhat Makes XML Ideally Suited for EPC/RFID Data?The Multi-Layer Data Model Vocabulary And Schemas
For EPC/RFIDThe MLDM and Other OASIS Standards – Working
Together In The EPC/RFID DomainBenefits of the MLDMQ&A
Presentation Agenda
Introductions
4
Speakers
– Ash Parikh ([email protected])• Director of Development And Technology - Enterprise Applications Group, Raining Data Corporation
– Robert Smik ([email protected])• 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
About Us
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
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) +
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) + … To Realize Real ROI, The Next-Gen Supply Chain Should Focus On
Using These Technologies To Drive Visibility And Control Of:– Goods– Funds– Information
The Issue Is That Many Existing And Valuable Technologies And Standards Are Converging….
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.
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
The Multi-Layer Data Model Vocabulary
And Schemas For EPC/RFIDA 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
XM
L
The Multi-Layer Data Model Layers
XM
L
XQ
UE
RY
GR
AN
UL
AR
ITY
OF
INF
OR
MA
TIO
N A
ND
EV
EN
TS
FINE GRAINED
COARSE 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 namesboundaries: ECBoundarySpecreportSpecs: List //list of one or more ECReportSpec instancesincludeSpecInreport: Boolean
ECBoundarySpec, specifies how the beginning and end of event cycles are to be determined:startTrigger : ECTriggerrepeatPeriod : ECTimestopTrigger : ECTriggerduration : ECTimestableSetIntervals : ECTime<<extension point>>
15
APPLICATION LEVEL EVENT – CONT.ECTime, denotes a span of time measured in physical time units:duration : longunit : 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 : stringreportSet: ECReportSetSpecfilter : ECFilterSpecgroup : ECGroupSpecoutput : ECReportOutputSpecreportIfEmpty : BooleanreportOnlyOnChange : Boolean
ECReportSetSpec: CURRENT | ADDITIONS | DELETIONS
ECFilterSpec, specifies what EPCs are to be included in the final report.IncludePatterns : List //list of epc patternsexcludePatterns : List //list of epc patterns to exclude
16
Event & Master Data
BizStep Vocabularyreceivingshipping …
BizLocation Vocabularyurn:epc:id:sgln:0614141.12345.0urn:epc:id:sgln:0614141.33254.0urn:epc:id:sgln:0614141.33254.1…
Event Data
Master Data
bizLocationRequired = true…
address = 123 Elm Stcity = AnytownpostalCode = 12345……
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
Master Data Vocabularies Master Data Attributes
Event field
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 define(queryname:String, query:Query) Register query with EAGEPCIS
undefined(queryName:String) Remove the query by name
subscribe(queryName:String, dest:URI, SubscriptionControls controls) Register a subscriber for previously defined query
unsubscribe(queryName:String, dest:URI) Removes previously registered subscriptions
poll(queryName:String) : QueryResult Invokes a previously defined query
immediate(query:Query) : QueryResult Invokes a query as specified by the query parameter returning results
listQuerynames(): List Returns a list of all query names
listSubscriptions(queryName:String) : List Returns a list of all URIs currently subscribed to the specified named query
getQuery(queryName:String) : Query Returns the query associated with a specified name
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
The MLDM And Other OASIS Standards –
Working Together In The EPC/RFID
Domain
26
ebMSHebMSH
The OASIS Standards And The MLDM
SOAPSOAP
ebXML REGISTRYebXML REGISTRY
WS-BPEL/eb BPWS-BPEL/eb BP
OASIS WEB SERVICES STANDARDS STACK
MESSAGEPAYLOADMESSAGE
PAYLOAD
ROUTINGOF
MESSAGES
ROUTINGOF
MESSAGES
COORDINATION OF WORKBETWEEN
WEB SERVICES
COORDINATION OF WORKBETWEEN
WEB SERVICES
TRANSACTIONS(ACID)TRANSACTIONS
(ACID)
LOGICAL STACK
DISCOVERYAND
AGGREGATION
DISCOVERYAND
AGGREGATION
BUSINESS PROCESSAND
SERVICE ORCHESTRATION.
BUSINESS PROCESSAND
SERVICE ORCHESTRATION.
CPPACPPA
REQUIREMENTSAND CAPABILITIES OF THE
WEB SERVICE/TRADING PARTNER AGREM.
REQUIREMENTSAND CAPABILITIES OF THE
WEB SERVICE/TRADING PARTNER AGREM.
EPC NETWORK AND MLDM FUNCTIONAL STACK
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
The OASIS Symposium on the Future of XML Vocabularies
Multi-Layer XML Data Model for EPC/RFIDAsh Parikh
Robert Smik