For Semantic Interoperability EDICOM 2012 AFACT TMC: Technology and Methodology Committee Hisanao Sugamata

AGENDA 1.Semantic Interoperability and Libraries 2.Core Component Libary 3.Message Assembly 4.Way Forward

Semantic Interoperability (1) Delivery Date The date of giving birth to a baby. The date of taking goods to the people they have been sent to. Supply chain contextHospital context

Semantic Interoperability (2) 手 紙 A thin soft paper used for cleaning yourself after you used the toilet. A message that is written down or printed on paper LetterToilet paper Japanese contextChinese context PaperHand

Common Semantic Libraries TDED EDIFACT Directory CCL Trade Data Element Directory which is maintained by Joint Maintenance Agency (TC154, UN/CEFACT, etc). Message, Segment, Data Element, Code directories used by EDIFACT standard messages, which is maintained by UN/CEFACT. Core Component Library based on ebXML Core Component Specification, which is maintained by UN/CEFACT.

Core Component Library

Windows Workflow XML-Schema … UN/CEFACT's Modeling Methodology (UMM) CCTS & CCL Functional Service View related standards Business Operational View related standards The Open-edi Reference Model ISO Business Transactions Business aspects of business transactions Information technology aspects of business transactions viewed as comply with covered by comply with transformed to Business Operational View Functional Service View

8 Party Company Identification Company Name Address Postal Code State City Street Buyer Seller コア構成要素 Data Model Core Component 注文 注文ヘッダー 買い手情報 … … 注文ヘッダー 買い手情報 … 売り手情報 注文ヘッダー 買い手情報 … Order Header Buyer Information … Seller Information 発注明細 … Order Details Order Form Business Information Entity (BIE) Core Component Product Information Quantity Unit Price

Data Modeling Technical Specifications Business Document Business Information Entity Core Component Data Type Catalogue Assemble Derived Used Used with Qualifier CCTS (Core Component Technical Specification) CCBDA (Core Component Business Document Assembly) DTC (Core Component Data Type Catalogue)

Core Component Types Aggregate Core Component Basic Core Component Association Core Component Core Data Type Content Component Core Data Type Supplementary Components With known business semantics Without business semantics SimpleComplex

ACC: Aggregate Core Component [Example] – Aggregate Core Component and properties Contract. DetailsACC Contract. Identification. IdentifierBCC Contract. Type. CodeBCC Contract. Issue. Date TimeBCC Contract. Price. AmountBCC Contract. Effective. PeriodASCC Contract. Performance. MetricsASCC

ASCC: Association Core Component [Example – Association Core Component Associating Core Component Contract. Details Identification. Identifier Type. Code Issue. Date Time Price. Amount Effective. Period Performance. Metrics Associated Core Component Period. Details Duration. Measure Start. Date Time Effective

BCC: Basic Core Component [Example] – Basic Core Component Basic Core Component Contract Type. Code Object Class Contract BCC Property Type. Code Property Term Type Representation Term Code Core Data Type Code Type

CDT: Core Data Type Core Data Type CDT Content Component CDT Supprimentary Components Amount Type Amount Content Value = 12 Amount. Currency. Code Value = EUR [Example – Core Data Type

Core Component Library (CCL-CC)

CC & BIE Relationship

ACC  ABIE (Context Driven) [Example] – ABIE with context driven Contract. Details Contract. Identification. Identifier Contract. Type. Code Contract. Issue. Date Time Contract. Price. Amount Contract. Effective. Period Contract. Performance. Metrics Trade_ Contract. Details Trade_ Contract. Identification. Identifier Trade_ Contract. Business_ Type. Code Trade_ Contract. Total_ Price. Amount Business Context ACC ABIE

ABIE: Aggregate Business Information Entity [Example – Association Business Information Entity Trade_ Contract. Actual_ Performance. Calculated_ Metrics ASBIE Object Class Trade_ Contract ASBIE Property Actual_ Performance. Calculated_ Metrics Property Term Actual_ Performance ASABIE Object Class Calcurated_ Metrics

ASBIE: Association Business Information Entity [Example – Aggregation Representation of ASBIE Associating BIE Trade_ Contract. Details Identification. Identifier Issue. Date Time Actual_ Performance. Calculated_ Metrics Associated BIE Calculated_ Metrics. Details Description. Text Reported. Quantity Measured. Percent Actual_ Performance

BBIE: Basic Business Information Entity [Example] – Basic Business Information Entity Basic Business Information Entity Trade_ Contract. Business Type. Code Object Class Trade_ Contract BBIE Property Business_ Type. Code Property Term Business_ Type Representation Term Code Business Data Type Business_ Code Type

BDT: Business Data Type Business Data Type BDT Content Component BDT Supprimentary Components EUR_ Amount Type Amount Content Value = 12 Amount. Currency. Code Restricted Value = EUR [Example – Business Data Type

Core Component Library (CCL-BIE)

Core Component Library (CCL-DT)

Conceptual Data Model Business Requirement Specification (BRS)

Conceptual Model (Schedule Calendar) Requirement Specification Mapping(RSM)

Canonical Model (Cost Data) Requirement Specification Mapping(RSM)

Data Modeling Workflow (UN/CEFACT) Gathering Requirements BRS Business Requirement Specification RSM Requirement Specification Mapping Data Definition  CCL Harmonized among Domains Harmonized In Library Harmonized Through Processes Approved By Stakeholders

28 Who develop UN/CEFACT CCL ebXML Core Component Specification Core Component Library Submission Based onRegistration Chemical Industry Electronics Industry Automobile Industry GS1 SWIFT Transportation Industry Governments WCO Agricultural Industry Harmonization

Message Assembly

BuyerSupplier Requesting Quotation Receiving RFQ Estimation Responding RFQ Receiving Quotation Preparing Order RFQ Quote EDI Business Process EDI Message B2B Collaboration

B2B Design Workflow Business Requirement Business Process Model Data Model Message Assembly Syntax Solution Messaging Service Operation Environment UMM UN/CEFACT Modeling Methodology CCTS Core Component Technical Specification XML OR EDIFACT ebMS ebXML Messaging Service UCM DT Catalogue CCBDA BDH Schema Directory CCL BRS RSM

CEFACT Architecture - Nada Reinprecht 32 Runtime engine Technology Transformations CCBDA – Business Document Assembly UMM - Business Process View UMM - Business Collaboration View UMM Business Transaction View UMM - Business Choreography View CCTS - Core Components CCL - Business Information Entities Library UMM - Information Entity UCM – Business Context UCM – Action/Intention BDH XML NDR - XML EDIFACT UCM – Run-time Context Communication layer Transport layer Semantics Services UMM - Business Entity View UN/CEFACT Technical Specification Architecture

CCBDA Conceptual Overview Core Component Business Document Assembly > Message Assembly > Message Business Information Entity ABIE Aggregate Business Information Entity ASMA ASMBIE ASBIE 1..* 0..*

Way Forward

We are on the same path (CC) but there exist many BIEs of this path. Do you want ineroperability ? This is how you achieve interoperability This results in interoperability We guarantee interoperability Here is an interoperable solution I will tell you how you achieve interoperability Thereby we ensure interoperability Do not listen to them if you want interoperability

Global Foundation and Community Specifications Communities of UseImplementations ‘Core’ Foundation 36

What we need ’core ‘ business process models ‘core’ components and code lists ‘core’ structures syntax libraries Global messaging protocols UNECE publications & recommendations UN/CEFACT Business process implementation guideline Business process implementation guideline Business component Implementation guideline Business component Implementation guideline Business document implementation guideline Implementation Guidelines Trade Facilitation Implementation guideline Business process modeling Business component modeling Business component modeling Business document modeling MDR for EDIFAC T Methodologies And Technologies NDR for XML International Laws WTO/UN recommendations Trade Agreements 37

MethodologiesContentImplementations ProcessBusiness processBusiness Process Methodology ‘core’ Business Process Models ‘community’ business processes SemanticsCore ComponentsCore Component Methodology ‘core’ component library ‘community’ components Content constraintsCore Component Methodology ‘core’ data types ‘core’ code lists ‘community’ data types ‘community’ code lists StructureDocument Structures Document Assembly Methodology ‘core’ structuresBusiness documents SyntaxFormatsUN/EDIFACT MDR XML NDR UN/EDIFACT Messages XML Schema for the above UN/EDIFACT MIGs Document Schemas Required technical framework 38  Under Discussion

Any Questions ? CONTACT SIPS : Supplychain Information Platform Study group General Secretariat : Hisanao Sugsamata