UNESCAP / ECO TF Workshop
Designing Electronic Messages
SIPS : Supplychain Information Platform Study group
General Secretariat : Hisanao Sugsamata
hsedi@attglobal.net
AGENDA
1. Implementation Overview
2. Design Data Model and Messages
3. Design Syntax Dependent Messages
4. Design Message Envelope
Implementation Overview
B2B Collaboration
Business Process
Buyer
Supplier
Requesting
Quotation
EDI
RFQ
Receiving
Quotation
Preparing
Order
EDI Message
EDI
Quote
Receiving
RFQ
Estimation
Responding
RFQ
B2B Design Workflow
BRS
RSM
Business Requirement
UMM
UN/CEFACT
Modeling
Methodology
Schema
XML
UCM
Business Process Model
DT Catalogue
Data Model
CCTS
Message Assembly
Core Component
Technical
Specification
OR
EDIFACT
Directory
CCBDA
Syntax Solution
CCL
BDH
Messaging Service
ebMS
Operation Environment
ebXML
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
6
UN/CEFACT TS & Libraries
CEFACT
Provides
Specifications
CEFACT
Produces
Others
Produce
Types
Core Data Types
DTC
Data Type
Catalogue
Semantics
Core
Components
CCTS/UPCC
CC Library
Context
UCM
Context Graph
Context
Graphs
Business
Information
Entities
(including BDTs)
CCTS/UPCC+UCM
(UMM ,BRS, RSM)
BIE Library
BIE Library(s)
Business
Processes
Business
Processes
UMM, UCM, UPCC, BRS
Template
BRSes/Busine
ss Process
Library
BRSes/Busine
ss Process
Libraries
Structure
Document Models
Message Assembly
Template/Specification?
Message
Library
Message
Library(s)
Syntax
Formats
NDR
Schemas
Schemas
Implement
ation
Implementation
Guidelines
Implementation
Guideline Specification
(profiling and variance)
Design Data Model and Messages
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
Harmonized
In
Library
Business Requirement Specification (BRS-1)
Business Domain View (Customs Domain):
uc Customs
Business Process Use Case
uc CrossIndustryInv oi...
Business Requirement Specification (BRS-2)
Business Process Activity Diagram
Business Requirement Specification (BRS-3)
Conceptual Data Model
class ConceptualModel
Requirement Specification Mapping(RSM-1)
Conceptual Model (Schedule Calendar)
class Schedule Calendar
«ACC»
Calendar. Details
«ACC»
Work Shift. Details
«BCC»
+ Identification: Identifier. Type [0..*]
+ Name: Text. Type [0..*]
+ Description: Text. Type [0..*]
+ Start: Date. Type [0..*]
+ End: Date. Type [0..*]
+ Holiday: Date. Type [0..*]
+Associated
«ASCC»
0..*
«ASCC»
«ASCC»
«ACC»
Document. Details
«BCC»
+ Multiple Type: Indicator. Type [0..*]
+ Identification: Identifier. Type [0..*]
+ Type: Code. Type [0..*]
+ Name: Text. Type [0..*]
+ Purpose: Text. Type [0..1]
+ Description: Text. Type [0..*]
+ Issue: Date Time. Type [0..1]
+ Submission: Date Time. Type [0..1]
+ Receipt: Date Time. Type [0..1]
+ Control Requirement: Indicator. Type [0..1]
+ Attachment: Binary Object. Type [0..*]
+ Creation: Date Time. Type [0..1]
+ Status: Code. Type [0..*]
+ Copy: Indicator. Type [0..1]
+ Response: Date Time. Type [0..*]
+ Item Identification: Identifier. Type [0..1]
+ Remarks: Text. Type [0..*]
+Specified
0..*
+Effective 1
«ACC»
Period. Details
+Reference 0..*
«ASCC»
«BCC»
+ Identification: Identifier. Type [0..*]
+ Day: Code. Type [0..*]
+ Name: Text. Type [0..1]
«BCC»
+ Duration: Measure. Type [0..*]
+ Description: Text. Type [0..*]
+ Inclusive: Indicator. Type [0..1]
+ Start: Date Time. Type [0..1]
+ End: Date Time. Type [0..1]
+ Complete: Date Time. Type [0..1]
+ Open: Indicator. Type [0..1]
+ Identification: Identifier. Type [0..*]
+ Season: Code. Type [0..*]
+ Name: Text. Type [0..*]
+ Sequence: Numeric. Type [0..*]
Requirement Specification Mapping(RSM-2)
Canonical Model (Cost Data)
class Cost Data
«ABIE»
Proj ect_ Cost. Details
«BusinessInformationPayload»
Cost Data. Details
«BBIE»
+ Identification: Identifier. Type
0..* + Name: Text. Type [0..1]
+ Description: Text. Type [0..1]
+ Cost Management_ Type: Code. Type [0..1]
+ Cost Reporting_ Type: Code. Type [0..1]
+ Component: Amount. Type [0..1]
+ Effective: Date. Type [0..1]
+ Hours_ Component: Quantity. Type [0..1]
+ Equivalent Heads_ Component: Quantity. Type [0..1]
+ Material_ Component: Quantity. Type [0..1]
+ Material_ Component Name: Text. Type [0..1]
+ Recurring: Indicator. Type [0..1]
«ASMA»
«ABIE»
Proj ect_ Note. Details
«ASMA»
0..*
«BBIE»
+ Identification: Identifier. Type [0..1]
+ Name: Text. Type [0..1]
+ Content: Text. Type [0..1]
+ Creation: Date Time. Type [0..1]
+ Content Code: Code. Type [0..1]
«ASMA»
«ASMA»
0..1
+Associated
«ABIE»
Proj ect_ Period. Details
«ABIE»
Proj ect_ Person. Details
«BBIE»
+ Identification: Identifier. Type [0..1]
+ Name: Text. Type [0..1]
+ Given Name: Text. Type [0..1]
+ Middle Name: Text. Type [0..1]
+ Family Name: Text. Type [0..1]
+ Title: Text. Type [0..1]
+ Salutation: Text. Type [0..1]
+ Family Name Prefix: Text. Type [0..1]
+ Name Suffix: Text. Type [0..1]
+ Gender: Code. Type [0..1]
+ Language: Identifier. Type [0..1]
+ Maiden Name: Text. Type [0..1]
+ Preferred Name: Text. Type [0..1]
«ASMA»
0..1
«ASMA»
«ASMA»
0..1
«BBIE»
+ Duration: Measure. Type [0..1]
+ Inclusive: Indicator. Type [0..1]
+ Description: Text. Type [0..1]
+ Start: Date Time. Type [0..1]
+ End: Date Time. Type [0..1]
+ Complete: Date Time. Type [0..1]
+ Sequence: Numeric. Type [0..1]
+ Name: Text. Type [0..1]
0..*
«ASBIE»
«ABIE»
0..* Reported_ Hierarchical Structure. Details
«BBIE»
+ Identification: Identifier. Type
+ Name: Text. Type [0..1]
+ Description: Text. Type [0..1]
+ Type: Code. Type [0..1]
+ Planning Level: Code. Type [0..1]
«ASBIE»
«ABIE»
Cost Report_ Document. Details
«BBIE»
+ Creation: Date Time. Type [0..1]
+ Submission: Date Time. Type [0..1]
+ Description: Text. Type [0..1]
+ Security_ Type: Code. Type [0..1]
«ABIE»
Progress Monitored_ Proj ect. Details
0..*
«ABIE»
Progress Monitored_ Contract. Details
«ASBIE»
«BBIE»
+ Identification: Identifier. Type [0..1]
+ Plan_ Identification: Identifier. Type [0..1]
+ Type: Code. Type [0..*]
+ Completion: Percent. Type [0..1]
+ Funding_ Type: Code. Type [0..1]
+ Security_ Type: Code. Type [0..1]
+ Name: Text. Type [0..1]
+ Customer_ Name: Text. Type [0..1]
+ Description: Text. Type [0..1]
+ Issue: Date Time. Type [0..1]
+ Price: Amount. Type [0..*]
+ Target_ Price: Amount. Type [0..1]
+ Estimated Total_ Price: Amount. Type [0..1]
+ Initial Funding Target_ Price: Amount. Type [0..1]
+ Adjusted Funding Target_ Price: Amount. Type [0..1]
+ Ceiling_ Price: Amount. Type [0..1]
+ Estimated Ceiling_ Price: Amount. Type [0..1]
+ Extension: Indicator. Type [0..1]
+ Start: Date. Type [0..1]
+ Work_ Start: Date. Type [0..1]
+ Definitization_ Start: Date. Type [0..1]
+ Target_ Fee: Percent. Type [0..1]
+ Expected_ End: Date. Type [0..1]
+ Estimated_ End: Date. Type [0..1]
+ Planned_ End: Date. Type [0..1]
+ Last Item Delivery: Date. Type [0..1]
+ Over Target Baseline: Date. Type [0..1]
+ Original Negotiated_ Cost: Amount. Type [0..1]
+ Target Fee_ Cost: Amount. Type [0..1]
+ Negotiated_ Cost: Amount. Type [0..1]
+ Authorized Unpriced Work Estimated_ Cost: Amount. Type [0..1]
+ Cumulative Negotiated Changes_ Cost: Amount. Type [0..1]
+ Minimum Fee_ Cost: Amount. Type [0..1]
+ Maximum Fee_ Cost: Amount. Type [0..1]
+ Fixed Fee_ Cost: Amount. Type [0..1]
+ Original Award Fee_ Cost: Amount. Type [0..1]
+ Non Fee Bearing Cost_ Cost: Amount. Type [0..1]
+ Current Target_ Cost: Amount. Type [0..1]
+ Total Allocated Budget_ Cost.: Amount. Type [0..1]
+ Initial Funding Ceiling_ Cost: Amount. Type [0..1]
+ Adjusted Funding Ceiling_ Cost: Amount. Type [0..1]
+ Fiscal_ Funding Year: Identifier. Type [0..1]
+Subordinate
0..*
«ABIE»
Reporting_ Data Node. Details
«ASBIE»
+Used
0..1
«BBIE»
+ Identification: Identifier. Type [0..1]
+ Contract: Identifier. Type [0..1]
+ Project Portfolio: Identifier. Type [0..*]
+ Description: Text. Type [0..1]
+ Name: Text. Type [0..1]
+Contained
+ Type: Code. Type [0..1]
0..* + Authority_ Constraint: Indicator. Type [0..1]
+ Sub-Project_ Identification: Identifier. Type [0..*]
«BBIE»
+ Associated Cost_ Identification: Identifier. Type [0..*]
+ Identification: Identifier. Type
1..* + Variance Analysis Note_ Identification: Identifier. Type [0..*]
+ Parent Node_ Identification: Identifier. Type [0..*]
+ Data Structure_ Identification: Identifier. Type [0..1]
+ Cross Reference_ Identification: Identifier. Type [0..*]
+ Name: Text. Type [0..1]
+ Description: Text. Type [0..1]
+ Risk Level_ Description: Indicator. Type [0..1]
+ Hierarchical Level: Numeric. Type [0..1]
+ Earned Value_ Calculation Method: Code. Type [0..1]
+ Summary Exclusion: Indicator. Type [0..1]
+ Sequence: Numeric. Type [0..1]
+ Control Account_ Identification: Identifier. Type [0..1]
+ Work Package_ Identification: Identifier. Type [0..1]
+Component
«ASBIE»
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 Technical Specification
(CCTS )
Core Component Business Document Assembly
(CCBDA -1)
Business Message Structure
Core Component Business Document Assembly
(CCBDA -2)
Message Assembly Conceptual Overview
Core Component Business Document Assembly
(CCBDA -3)
CCBDA
Conceptual Overview
<<InformationEntity>>
Message Assembly
ASMA
1..*
0..*
<<InformationEntity>>
ASMBIE
Message Business
Information Entity
0..*
Aggregate Business
Information Entity
ASBIE
CCBDA
Metamodel
Data Model Libraries
TDED
EDIFACT
Directory
CCL
Core Component Library (CCL-CC)
UN00002809
ACC
Produce. Details
Products, such as grain, fruits,
vegetables, poultry and livestock.
A code specifying a type of
produce.
A unique identifier for this produce.
UN00002810
BCC
Produce. Type. Code
UN00002811
BCC
Produce. Identification. Identifier
UN00002812
BCC
Produce. Name. Text
UN00002813
BCC
Produce. Weight. Measure
UN00002814
BCC
Produce. Use. Code
UN00002815
BCC
Produce. Yield. Measure
UN00002816
ASCC
Produce. Applicable. Characteristic
UN00002817
ASCC
Produce. Specified. Batch
A name, expressed as text, for this
produce.
A measure of the weight (mass) of
this produce.
A code specifying a use for this
produce, such as for human
consumption.
A measure of a yield of this
produce, such as weight per
hectare.
A characteristic applicable to this
produce.
A batch specified for this produce.
UN00005919
UN00005920
ASCC
ASCC
Produce. Certifying. Party
Produce. Grower. Party
A certifying party for this produce.
A grower party for this produce.
Core Component Library (CCL-BIE)
UN01007705
ABIE
Livestock Animal_ Product. Details
A class of domesticated creatures
raised on a farm or ranch.
UN01007706
BBIE
UN01007707
BBIE
UN01007708
BBIE
UN01007709
ASBIE
Livestock Animal_ Product. Common Species_ Name. Text The common species name,
expressed as text, for this livestock
animal product.
Livestock Animal_ Product. Scientific Species_ Name. Text The scientific species name,
expressed as text, for this livestock
animal product.
Livestock Animal_ Product. Description. Text
The textual description of this
livestock animal product.
Livestock Animal_ Product. Individual. Livestock Animal_
The product instance of an
Product Instance
individual in this livestock animal
product.
Core Component Library (CCL-DT)
UN01008288
ABIE
CI_ Workflow Object. Details
An object used in the management
of the status changes in a Cross
Industry (CI) business process.
UN01008289
BBIE
CI_ Workflow Object. Identification. Identifier
UN01008290
BBIE
CI_ Workflow Object. Status. Code
UN01008291
BBIE
CI_ Workflow Object. Previous_ Status. Code
The identifier of this CI workflow
object.
The code specifying the status of
this CI workflow object.
The code specifying the previous
status of this CI workflow object.
UDT000007
Identifier
Workflow_ Status
Code
Workflow_ Status
Code
DT
Code. Type
CC
Code. Content
SC
Code List. Identifier
SC
Code List. Agency. Identifier
SC
Code List. Agency Name. Text
SC
SC
SC
Code List. Name. Text
Code List. Version. Identifier
Code. Name. Text
SC
Language. Identifier
SC
Code List. Uniform Resource. Identifier
SC
Code List Scheme. Uniform Resource. Identifier
A character string (letters, figures
or symbols) that for brevity and/or
language independence may be
used to represent or replace a
definitive value or text of an
attribute.
A character string (letters, figures
or symbols) that for brevity and/or
language independence may be
used to represent or replace a
definitive value or text of an
attribute.
The identification of a list of codes.
An agency that maintains one or
more code lists.
The name of the agency that
maintains the code list.
The name of a list of codes.
The version of the code list.
The textual equivalent of the code
content.
The identifier of the language used
in the corresponding text string.
The Uniform Resource Identifier
that identifies where the code list is
located.
The Uniform Resource identifier
that identifies where the code list
scheme is located.
Design Syntax Dependent Messages
XML Message
RSM
BIE
XML
Schema
XML
Document
XML Schema
Design Message Envelope
Business Document Header (BDH)
BDH Use Case
■ An example of realization of interoperability with BDH.
［Sender］
Non- dimensional
／ＸＭＬSyntax
［ＡＳＰ or Cloud］
ＴＳＨ
Registry
Summary
ＴＳＨ
Static Information
［Receiver］
ＴＳＨ
ＴＳＨ
ＭＳＨ
ＭＳＨ
Non- dimensional
／ＸＭＬSyntax
ＭＳＨ
ＭＳＨ
ＢＤＨ
ＢＤＨ
ＢＤＨ
ＢＤＨ
ＢＤＨ
ＢＤＨ
Proprietary
ＢＤＨ
Proprietary
ＢＤ
Proprietary
ＢＤ
Proprietary
ＢＤ
ＳＢＤ
Proprietary
ＢＤ
Proprietary
ＢＤ
Proprietary
ＢＤ
Proprietary
From proprietary
Application
Message Binding
Transport Bing
Message Service
Transport Service
Translator
ＸＭＬsyntax
Translator
Message Binding
Transport Bing
Messaging
TSH ：Transport Service Header
MSH：Message Service Header
BDH ：Business Document Header
BD ： Business Document
,
SBD ： Standard Business Document
Messaging Service Layer
Business Document Message
Business Document Content
(UN/CEFACT [ASMA], OAGi, UBL, Other)
Message
Header
processing
Profile of Message Body
Connection
routing
Auth.
・・・
(SSO)
Organization
Collaboration
Business Document Message
Business
Document Header
Business Document
Content
Etc.
Error
SMTP
Binding
FTP
Binding
Etc.
Binding
HTTP
Binding
Transport Message
IP Address
Quality of Service
Transport
(REST, other)
Binding
Dialect in Specific Protocol
such as HTTP
Message
Registry Summary (CSP Other)
Business
Document Header
Any Questions ?