OASIS SET Reference Implementation iSURF Interoperability Service Utility for CPFR© Prof. Dr. Asuman Dogac and Yildiray Kabak

Outline SET-TC Specifications and Framework iSURF Project Interoperability Service Utility (ISU) Demo Results

The Main Ideas of the SET Framework 1.If the document components of two different CCTS based standard share the same semantic properties: – Use this as an indication that they may be similar 2.Some explicitly defined semantic properties may imply further implicit semantic relationships: – Use a reasoner to obtain implicit relationships 3.Explicate semantics related with the different usages of document data types in different document schemas to obtain some desired interpretations by means of such informal semantics 4.For discovering the similarities of structurally different but semantically similar document artifacts, we provide further heuristics – About possible ways of organizing core components into compound artifacts

Semantic Properties of UN/CEFACT CCTS based Standards We explicate the CCTS based business document semantics – By “explicating”, we mean to define their semantic properties through a formal, machine processable language as an ontology The Core Components have the following semantic properties: – Core Component Data Types – Context – Code Lists – Object Class Term – Representation Term – The semantics that a BIE is based on a “Core Component”

Overview July 10, 2009Thesis Defense 5 Overall OWL Ontology Overall OWL Ontology Harmonized Ontology Harmonized Ontology Jess Facts Jess Facts Heurisitcs XSLT Generator XSLT

Upper Ontology Upper Ontology describes the generic entities in electronic business documents in terms of ontology classes July 10, Thesis Defense BCC ASCC ACC contains refersTo CC BBIE ASBIE ABIE containsrefersTo BIE Representation Term Object Class Term hasRT hasOCT CDT C.List hasDT possibleCodeList basedOn Context usedInContext hasOCT

Standards’ Upper Ontologies July 10, 2009Thesis Defense 7 Component ComponentRef Field contains refersTo OAGIS UBL.ABIE UBL.ASBIE UBL.BBIE contains refersTo UBL GS1.XML.ABIE GS1.XML.ASBIE GS1.XML.BBIE contains refersTo GS1 XML Upper Ontology BCC ASCC ACC contains refersTo CC BBIE ASBIE ABIE containsrefersTo BIE Representation Term Object Class Term hasRT hasOCT CDT C.List hasDT possibleCodeList basedOn Context usedInContext hasOCT

Document Schema Ontologies Document schema ontologies describe the actual document artifacts as the subclasses of the classes in the upper ontology July 10, Thesis Defense Component ComponentRef Field contains refersTo OAGIS UBL.ABIE UBL.ASBIE UBL.BBIE contains refersTo UBL GS1.XML.ABIE GS1.XML.ASBIE GS1.XML.BBIE contains refersTo GS1 XML Upper Ontology BCCBCC BCCBCC ASCCASCC ASCCASCC ACCACC ACCACC contains refersTo CC B BI E A S BI E A BI E containsrefersTo BI E Representation Term Object Class Term hasRThasRT hasRThasRT hasRThasRT hasRThasRT has OCT CDT C.List hasDT possibleCodeList basedOn Context usedInContext has OCT OAGIS Document Schema Ontology UBL Document Schema Ontology GS1 XML Document Schema Ontology UN/CCL Document Schema Ontology Address CountryCode ID PostalCode Address Country Identification Postbox NameAnd Address countryCode name postalCode Structured _Address CountryCode Identification Postcode Excel  XML Map  XML  OWL GDD  HTML  OWL Excel  XML Map  XML  OWL XSD  OWL

Explicate semantics related with the different usages of document data types Different document standards use CCTS Data Types differently For example, “Code.Type" in one standard is represented by “Text.Type" in another standard and yet with “Identier.Type" in another standard This knowledge in real world is expressed through class equivalences so that not only the humans but also the reasoner knows about it – Code.Type ≡ Text.Type – Name.Type ≡ Text.Type – Identier.Type ≡ Text.Type

July 10, Thesis Defense Heuristics to Discover Structurally Different Basic Document Components (BBIEs) Heuristics to Discover Structurally Different Association Document Component (ASBIE) and Basic Document Component Pairs (BBIE) Heuristics to Discover Structurally Different Association Document Component (ASBIE) and Basic Document Component Pairs (BBIE) Heuristics to Discover Structurally Different Association Document Components (ASBIEs) The ContainsSets of two aggregate document components have a nonnull intersection The ContainsSets of two aggregate document components have a nonnull intersection

iSURF: Research Objectives: Public Domain Tools Supporting SMEs for Collaborative Supply Chain Planning iSURF open Smart product Infrastructure for SMEs to collect real-time supply chain visibility data iSURF Service Oriented Collaborative Supply Chain Planning Process Definition and Execution Platform for the SMEs iSURF Semantic Interoperability Service Utility iSURF Global Data Synchronization and Transitory Collaboration Service Utility for dynamic transient supply chain relationships for the SMEs

iSURF ISU In order to optimize the overall profitability, the companies need to plan their future orders with their partners collaboratively – This requires collaborative planning within a supply chain and exchange of planning data There are various standard initiatives addressing the standardization of communication in exchanging the supply chain planning documents in different domains

Demo

Results Mappings between GS1 XML Plan documents and UBL CPFR© documents – Event, Exception Criteria, Exception Notification, Forecast, Forecast Revision, Performance History, Product Activity, Retail Event, Trade Item Information Request and Trade Item Location Profile On GS1 XML side, in these documents, there are 42 ABIEs and 75 BBIEs as a total – The methodology is able to find the corresponding UBL ABIE of 37 GS1 XML ABIEs and the corresponding UBL BBIE of 67 GS1 XML BBIEs – In other words, the success rate for ABIEs is % and for BBIEs it is % The false-positive ratio is about 10%