EDICOM 2012 For Semantic Interoperability 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 taking goods to the people they have been sent to. Supply chain context The date of giving birth to a baby. Hospital context
Semantic Interoperability (2) Hand 手 紙 Paper Letter Toilet paper A message that is written down or printed on paper A thin soft paper used for cleaning yourself after you used the toilet. Japanese context Chinese context
Common Semantic Libraries TDED Trade Data Element Directory which is maintained by Joint Maintenance Agency (TC 154, UN/CEFACT, etc). EDIFACT Directory Message, Segment, Data Element, Code directories used by EDIFACT standard messages, which is maintained by UN/CEFACT. CCL Core Component Library based on eb. XML Core Component Specification , which is maintained by UN/CEFACT.
Core Component Library
Business Transactions The Open-edi Reference Model ISO 14662 Business Operational View Business aspects of business transactions comply with UN/CEFACT's Modeling Business Operational Methodology (UMM) View related standards CCTS & CCL covered by viewed as transformed to Functional Service View Information technology aspects of business transactions comply with covered by Functional Service Windows Workflow View XML-Schema related standards …
Core Component Business Information Entity (BIE) Order Form 注 文 Order Header 注文ヘッダー Buyer Information 買い手情報 Buyer Seller Information 売り手情報 … Seller Data Model コア構成要素 Party Company Identification Company Name … Order Details 発注明細 … Product Information Address Postal Code State City Street Quantity 発注明細 Unit Price Core Component 8
Data Modeling Technical Specifications CCTS (Core Component Technical Specification) Business Document Assemble Business Information Entity Derived Core Component Used CCBDA (Core Component Business Document Assembly) Used with Qualifier Data Type Catalogue DTC (Core Component Data Type Catalogue)
Core Component Types Aggregate Core Component Basic Core Component Simple Complex Association Core Component With known business semantics Without business semantics Core Data Type Content Component Core Data Type Supplementary Components
![ACC: Aggregate Core Component [Example] – Aggregate Core Component and properties Contract. Details ACC](https://present5.com/presentation/da40b4843ca43da8a33afbf23ebc1e8d/image-11.jpg "ACC: Aggregate Core Component [Example] – Aggregate Core Component and properties Contract. Details ACC")
ACC: Aggregate Core Component [Example] – Aggregate Core Component and properties Contract. Details ACC Contract. Identification. Identifier BCC Contract. Type. Code BCC Contract. Issue. Date Time BCC Contract. Price. Amount BCC Contract. Effective. Period ASCC Contract. Performance. Metrics ASCC
ASCC: Association Core Component [Example – Association Core Component Associating Core Component Contract. Details Identification. Identifier Effective Type. Code Issue. Date Time Associated Core Component Price. Amount Period. Details Effective. Period Duration. Measure Performance. Metrics Start. Date Time
![BCC: Basic Core Component [Example] – Basic Core Component Contract Type. Code Object Class](https://present5.com/presentation/da40b4843ca43da8a33afbf23ebc1e8d/image-13.jpg "BCC: Basic Core Component [Example] – Basic Core Component Contract Type. Code Object Class")
BCC: Basic Core Component [Example] – 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 [Example – Core Data Type Amount Type CDT Content Component Amount Content Value = 12 CDT Supprimentary Components Amount. Currency. Code Value = EUR
Core Component Library (CCL-CC)
CC & BIE Relationship
![ACC ABIE (Context Driven) [Example] – ABIE with context driven ACC ABIE Contract. Details](https://present5.com/presentation/da40b4843ca43da8a33afbf23ebc1e8d/image-17.jpg "ACC ABIE (Context Driven) [Example] – ABIE with context driven ACC ABIE Contract. Details")
ACC ABIE (Context Driven) [Example] – ABIE with context driven ACC ABIE Contract. Details Contract. Identification. Identifier Business Contract. Type. Code Context 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
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 Actual_ Performance Trade_ Contract. Details Identification. Identifier Issue. Date Time Actual_ Performance. Calculated_ Metrics Associated BIE Calculated_ Metrics. Details Description. Text Reported. Quantity Measured. Percent
![BBIE: Basic Business Information Entity [Example] – Basic Business Information Entity Trade_ Contract. Business](https://present5.com/presentation/da40b4843ca43da8a33afbf23ebc1e8d/image-20.jpg "BBIE: Basic Business Information Entity [Example] – Basic Business Information Entity Trade_ Contract. Business")
BBIE: Basic Business Information Entity [Example] – 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 [Example – Business Data Type BDT Content Component BDT Supprimentary Components EUR_ Amount Type Amount Content Value = 12 Amount. Currency. Code Restricted Value = EUR
Core Component Library (CCL-BIE)
Core Component Library (CCL-DT)
Business Requirement Specification (BRS) Conceptual Data Model
Requirement Specification Mapping(RSM) Conceptual Model (Schedule Calendar)
Requirement Specification Mapping(RSM) Canonical Model (Cost Data)
Data Modeling Workflow (UN/CEFACT) Approved By Stakeholders Gathering Requirements BRS Business Requirement Specification Harmonized Through Processes Harmonized among Domains RSM Requirement Specification Mapping Data Definition CCL Harmonized In Library
Who develop UN/CEFACT CCL Harmonization Registration Automobile Industry Core Based on Component Submission Core Component Library eb. XML WCO Specification Agricultural Industry Chemical Industry GS 1 SWIFT Transportation Industry Governments Electronics Industry 28
Message Assembly
B 2 B Collaboration Business Process Buyer Supplier Requesting Quotation EDI RFQ Receiving Quotation Preparing Order EDI Message EDI Quote Receiving RFQ Estimation Responding RFQ
B 2 B Design Workflow BRS RSM Business Requirement UMM UN/CEFACT Modeling Methodology Business Process Model UCM DT Catalogue Data Model Schema XML CCTS Message Assembly Core Component Technical Specification OR EDIFACT Directory Syntax Solution CCBDA CCL BDH Messaging Service eb. MS Operation Environment eb. XML Messaging Service
UN/CEFACT Technical Specification Architecture UMM - Business Process View CCTS - Core Components UCM – Business Context UMM - Business Collaboration View CCL - Business Information Entities Library UMM - Business Entity View BDH Semantics UMM Business Transaction View UMM - Business Choreography View UCM –Action/Intention UMM - Information Entity XML NDR - XML CCBDA – Business Document Assembly Technology Transformations EDIFACT Runtime engine Services UCM – Run-time Context BDH Communication layer CEFACT Architecture - Nada Transport layer Reinprecht 32
Core Component Business Document Assembly CCBDA Conceptual Overview <<Information Entity>> Message Assembly 1. . * ASMA 0. . * <<Information Entity>> Message Business Information Entity ASMBIE 0. . * ABIE Aggregate Business Information Entity ASBIE
Way Forward
We are on the same path (CC) but there exist many BIEs of this path. This is how you achieve interoperability Thereby we ensure interoperability Do not listen to them if you want interoperability This results in interoperability I will tell you how you achieve interoperability Do you want ineroperability ? We guarantee interoperability Here is an interoperable solution
Global Foundation and Community Specifications ‘Core’ Foundation Communities of Use Implementations 36
What we need Global Trade Agreements Implementation Guidelines Methodologies And Technologies Trade Facilitation Implementation guideline International Laws WTO/UN recommendations UNECE publications UN/CEFACT & recommendations ’core ‘ business process models ‘core’ components and code lists ‘core’ structures syntax libraries messaging protocols Business process modeling Business process implementation guideline Business component modeling Business component Implementation guideline Business document modeling Business document implementation guideline MDR for EDIFAC T NDR for XML 37
Required technical framework Methodologies Semantics Structure Syntax Implementations Business process Business Process Methodology ‘core’ Business Process Models ‘community’ business processes Core Component Methodology ‘core’ component library ‘community’ components Content constraints Process Content Core Component Methodology ‘core’ data types ‘core’ code lists ‘community’ data types ‘community’ code lists Document Structures Document Assembly Methodology ‘core’ structures Business documents Formats UN/EDIFACT MDR XML NDR UN/EDIFACT Messages XML Schema for the above UN/EDIFACT MIGs Document Schemas Under Discussion 38
Any Questions ? CONTACT SIPS : Supplychain Information Platform Study group General Secretariat : Hisanao Sugsamata hsedi@attglobal. net
Скачать презентацию EDICOM 2012 For Semantic Interoperability AFACT TMC Technology
da40b4843ca43da8a33afbf23ebc1e8d.ppt