1 / 51

Designing Electronic Messages

UNESCAP / ECO TF Workshop. Designing Electronic Messages. SIPS : Supplychain Information Platform Study group General Secretariat : Hisanao Sugsamata hsedi@attglobal.net. AGENDA. Implementation Overview Design Data Model and Messages Design Syntax Dependent Messages

marisa
Télécharger la présentation

Designing Electronic Messages

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. UNESCAP / ECO TF Workshop Designing Electronic Messages SIPS : Supplychain Information Platform Study group General Secretariat : Hisanao Sugsamata hsedi@attglobal.net

  2. AGENDA • Implementation Overview • Design Data Model and Messages • Design Syntax Dependent Messages • Design Message Envelope

  3. Implementation Overview

  4. B2B Collaboration Business Process Buyer Supplier EDI Requesting Quotation Receiving RFQ RFQ Estimation EDI Receiving Quotation Responding RFQ Quote Preparing Order EDI Message

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

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

  7. UN/CEFACT TS & Libraries

  8. Design Data Model and Messages

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

  10. Business Requirement Specification (BRS-1) Business Domain View (Customs Domain): • Business Process Use Case

  11. Business Requirement Specification (BRS-2) Business Process Activity Diagram

  12. Business Requirement Specification (BRS-3) Conceptual Data Model

  13. Requirement Specification Mapping(RSM-1) Conceptual Model (Schedule Calendar)

  14. Requirement Specification Mapping(RSM-2) • Canonical Model (Cost Data)

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

  16. Core Component Technical Specification (CCTS )

  17. Core Component Business Document Assembly (CCBDA -1) Business Message Structure

  18. Core Component Business Document Assembly (CCBDA -2) Message Assembly Conceptual Overview

  19. <<InformationEntity>> Message Assembly ASMA 1..* 0..* <<InformationEntity>> Message Business Information Entity ASMBIE 0..* ASBIE Aggregate Business Information Entity Core Component Business Document Assembly (CCBDA -3) CCBDA Conceptual Overview

  20. CCBDA Metamodel

  21. Data Model Libraries TDED EDIFACT Directory CCL

  22. Core Component Library (CCL-CC)

  23. Core Component Library (CCL-BIE)

  24. Core Component Library (CCL-DT)

  25. Design Syntax Dependent Messages

  26. XML Message RSM BIE XML Schema XML Document

  27. XML Schema

  28. Design Message Envelope

  29. Business Document Header (BDH)

  30. BDH Use Case ■ An example of realization of interoperability with BDH. ［Sender］　　 ［ＡＳＰ or Cloud］ ［Receiver］ Registry Summary ＴＳＨ ＴＳＨ ＴＳＨ ＴＳＨ Non- dimensional ／ＸＭＬSyntax Non- dimensional ／ＸＭＬSyntax Static Information ＭＳＨ ＭＳＨ ＭＳＨ ＭＳＨ ＸＭＬsyntax Proprietary ＢＤＨ Proprietary ＢＤＨ ＢＤＨ ＢＤＨ ＢＤＨ ＢＤＨ ＢＤＨ Proprietary ＢＤ Proprietary ＢＤ Proprietary ＢＤ ＳＢＤ Proprietary ＢＤ Proprietary ＢＤ Proprietary ＢＤ From proprietary Application Message Binding Transport Bing Message Service Transport Service Translator Message Binding Transport Bing Messaging Translator TSH ：Transport Service Header MSH：Message Service Header BDH ：Business Document Header BD ： Business Document , SBD ： Standard Business Document

  31. Messaging Service Layer Registry Summary (CSP Other) Business Document Message Business Document Header Business Document Content (UN/CEFACT [ASMA], OAGi, UBL, Other) Transport (REST, other) Binding Message Header Business Document Message processing routing Auth. (SSO) ・・・ Business Document Content Profile of Message Body Organization Collaboration Business Document Header Connection Error Etc. SMTP Binding FTP Binding Etc. Binding HTTP Binding Transport Message IP Address Dialect in Specific Protocol such as HTTP Message Quality of Service

More Related