designing electronic messages unescap / eco tf workshop sips : supplychain information platform...
TRANSCRIPT
Designing Electronic Messages
UNESCAP / ECO TF Workshop
SIPS : Supplychain Information Platform Study groupGeneral Secretariat : Hisanao Sugsamata
AGENDA
1. Implementation Overview
2. Design Data Model and Messages
3. Design Syntax Dependent Messages
4. Design Message Envelope
Implementation Overview
Buyer Supplier
Requesting Quotation
ReceivingRFQ
Estimation
RespondingRFQ
Receiving Quotation
PreparingOrder
RFQ
Quote
EDI
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
UMMUN/CEFACT
ModelingMethodology
CCTSCore Component
TechnicalSpecificationXML
OR
EDIFACT
ebMSebXML
MessagingService
UCM
DT Catalogue
CCBDA
BDH
Schema
Directory
CCL
BRSRSM
CEFACT Architecture - Nada Reinprecht
6
Runtime engine
Technology Transformations
CCBDA – Business Document Assembly
UMM - Business Process View
UMM - Business Collaboration View
UMM Business Transaction ViewUMM - Business Choreography View
CCTS - Core Components
CCL - Business Information Entities Library
UMM - Information Entity
UCM – Business Context
UCM –Action/Intention
BDH
BDH
XML NDR - XML EDIFACT
UCM – Run-time Context
Communication layer
Transport layer
Sem
an
ticsS
ervices
UMM - Business Entity View
UN/CEFACT Technical Specification Architecture
UN/CEFACT TS & LibrariesCEFACTProvidesSpecifications
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/Business Process Library
BRSes/Business Process Libraries
Structure Document Models Message Assembly Template/Specification?
Message Library
Message Library(s)
Syntax Formats NDR Schemas Schemas
Implementation
Implementation Guidelines
Implementation Guideline Specification (profiling and variance)
Design Data Model and Messages
Data Modeling Workflow
(UN/CEFACT)
Gathering Requirements
BRSBusiness Requirement Specification
RSMRequirement Specification Mapping
Data Definition
Harmonizedamong
Domains
HarmonizedIn
Library
HarmonizedThroughProcesses
ApprovedBy
Stakeholders
Business Requirement Specification (BRS-1)
uc Customs
Supplier/Agent
«BusinessProcess»Arrival
«BusinessProcess»ClearanceHomeUse
«BusinessProcess»Conveyance
«BusinessProcess»Departure
«BusinessProcess»TransitArrival
«BusinessProcess»TransitDeparture
Customer/Agent
Transporter/Agent
Authority
CustomsProcesses
«BusinessProcess»OutrightExportation
«participates»
«participates»
«participates»
«participates»
«include»
«include»
«include»
«include»
«include»
«include»
«include»
uc CrossIndustryInv oi...
«BusinessProcess»TraditionalInv oice
Customer Supplier
«participates» «participates»
Business Domain View (Customs Domain):
Business Process Use Case
Business Process Activity Diagram
Business Requirement Specification (BRS-2)
class ConceptualModel
Inv oice
Deliv erySettlementAgreement
LineItem
Product
Seller Buyer
1issues
1..*1
receives
1..*1
requests
1
1
relates_to1..*
1
based_on
1..*
1..*
specifies
1
1
consists_of
1..*
Conceptual Data Model
Business Requirement Specification (BRS-3)
class Schedule Calendar
«ACC»Calendar. 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..*]
«ACC»Work Shift. Details
«BCC»+ Identification: Identifier. Type [0..*]+ Day: Code. Type [0..*]+ Name: Text. Type [0..1]
«ACC»Period. Details
«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..*]
«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..*]
+Reference 0..*
«ASCC»
+Effective 1
«ASCC»
+Associated
0..*«ASCC»
«ASCC»
+Specified 0..*
Conceptual Model (Schedule Calendar)
Requirement Specification Mapping(RSM-1)
class Cost Data
«ABIE»Project_ Cost. Details
«BBIE»+ Identification: Identifier. Type+ 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]
«ABIE»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]
«ABIE»Reporting_ Data Node. Details
«BBIE»+ Associated Cost_ Identification: Identifier. Type [0..*]+ Identification: Identifier. Type+ 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]
«BusinessInformationPayload»Cost Data. Details
«ABIE»Project_ 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] «ABIE»
Progress Monitored_ Project. Details
«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]+ Type: Code. Type [0..1]+ Authority_ Constraint: Indicator. Type [0..1]+ Sub-Project_ Identification: Identifier. Type [0..*]
«ABIE»Project_ Period. Details
«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]
«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»Project_ Note. Details
«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]
«ABIE»Progress Monitored_ Contract. Details
«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]
«ASMA»
0..*
«ASMA»
0..*
«ASMA» 0..*
«ASMA»
0..1
«ASMA»0..1
«ASMA»0..*
«ASBIE»
+Subordinate0..*
«ASBIE»
+Associated 0..*
«ASBIE»+Used 0..1
«ASBIE»
+Component
1..*
«ASMA»
0..1
«ASBIE»
+Contained
0..*
Canonical Model (Cost Data)
Requirement Specification Mapping(RSM-2)
Data Modeling Technical Specifications
BusinessDocument
BusinessInformation
Entity
CoreComponent
Data TypeCatalogue
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 Technical Specification
(CCTS )
Core Component Business Document Assembly
(CCBDA -1) Business Message Structure
Message Assembly Conceptual Overview
Core Component Business Document Assembly
(CCBDA -2)
<<InformationEntity>>
Message Assembly
<<InformationEntity>>
Message BusinessInformation Entity
ASMA
ASMBIE
0..*
Aggregate BusinessInformation Entity
ASBIE
0..*
1..*
CCBDA Conceptual Overview
Core Component Business Document Assembly
(CCBDA -3)
CCBDA Metamodel
Data Model Libraries
EDIFACTDirectory
TDED CCL
Core Component Library (CCL-CC)
UN00002809 ACC Produce. Details Products, such as grain, fruits,vegetables, poultry and livestock.
UN00002810 BCC Produce. Type. Code A code specifying a type ofproduce.
UN00002811 BCC Produce. Identification. Identifier A unique identifier for this produce.
UN00002812 BCC Produce. Name. Text A name, expressed as text, for thisproduce.
UN00002813 BCC Produce. Weight. Measure A measure of the weight (mass) ofthis produce.
UN00002814 BCC Produce. Use. Code A code specifying a use for thisproduce, such as for humanconsumption.
UN00002815 BCC Produce. Yield. Measure A measure of a yield of thisproduce, such as weight perhectare.
UN00002816 ASCC Produce. Applicable. Characteristic A characteristic applicable to thisproduce.
UN00002817 ASCC Produce. Specified. Batch A batch specified for this produce.
UN00005919 ASCC Produce. Certifying. Party A certifying party for this produce.UN00005920 ASCC Produce. Grower. Party A grower party for this produce.
Core Component Library (CCL-BIE)
UN01007705 ABIE Livestock Animal_ Product. Details A class of domesticated creaturesraised on a farm or ranch.
UN01007706 BBIE Livestock Animal_ Product. Common Species_ Name. Text The common species name,expressed as text, for this livestockanimal product.
UN01007707 BBIE Livestock Animal_ Product. Scientific Species_ Name. Text The scientific species name,expressed as text, for this livestockanimal product.
UN01007708 BBIE Livestock Animal_ Product. Description. Text The textual description of thislivestock animal product.
UN01007709 ASBIE Livestock Animal_ Product. Individual. Livestock Animal_Product Instance
The product instance of anindividual in this livestock animalproduct.
Core Component Library (CCL-DT)UN01008288 ABIE CI_ Workflow Object. Details An object used in the management
of the status changes in a CrossIndustry (CI) business process.
UN01008289 BBIE CI_ Workflow Object. Identification. Identifier The identifier of this CI workflowobject.
Identifier
UN01008290 BBIE CI_ Workflow Object. Status. Code The code specifying the status ofthis CI workflow object.
Workflow_ Status Code
UN01008291 BBIE CI_ Workflow Object. Previous_ Status. Code The code specifying the previousstatus of this CI workflow object.
Workflow_ Status Code
UDT000007 DT Code. Type A character string (letters, figuresor symbols) that for brevity and/orlanguage independence may beused to represent or replace adefinitive value or text of anattribute.
CC Code. Content A character string (letters, figuresor symbols) that for brevity and/orlanguage independence may beused to represent or replace adefinitive value or text of anattribute.
SC Code List. Identifier The identification of a list of codes.
SC Code List. Agency. Identifier An agency that maintains one ormore code lists.
SC Code List. Agency Name. Text The name of the agency thatmaintains the code list.
SC Code List. Name. Text The name of a list of codes.SC Code List. Version. Identifier The version of the code list.SC Code. Name. Text The textual equivalent of the code
content.SC Language. Identifier The identifier of the language used
in the corresponding text string.
SC Code List. Uniform Resource. Identifier The Uniform Resource Identifierthat identifies where the code list islocated.
SC Code List Scheme. Uniform Resource. Identifier The Uniform Resource identifierthat identifies where the code listscheme is located.
Design Syntax Dependent Messages
XML Message
RSM
BIE
XMLSchema
XMLDocument
XML Schema
Design Message Envelope
Business Document Header (BDH)
ＢＤＨＢＤＨ
ＳＢＤＳＢＤ
ＢＤＨＢＤＨ
ＭＳＨ
ＢＤＨＢＤＨ
TranslatorMessage BindingTransport Bing
From proprietary Application
［ Sender ］ ［ Receiver ］
ＴＳＨ
ＭＳＨ
ＴＳＨ
Message BindingTransport Bing
［ＡＳＰ or Cloud ］
Message ServiceTransport Service
ＢＤＨＢＤＨ
ＭＳＨ
ＴＳＨ
ＢＤＨＢＤＨ
ＭＳＨ
ＴＳＨ
TranslatorMessaging
ＸＭＬ syntax
■ An example of realization of interoperability with BDH.
ProprietaryＢＤ
ProprietaryＢＤ
ProprietaryＢＤ
ProprietaryＢＤ
ProprietaryＢＤ
ProprietaryＢＤ
TSH ： Transport Service HeaderMSH ： Message Service HeaderBDH ： Business Document Header BD ： Business Document , SBD ： Standard Business Document
ProprietaryＢＤＨ
Non- dimensional ／ＸＭＬ Syntax
ProprietaryＢＤＨ
Non- dimensional ／ＸＭＬ Syntax
Registry SummaryRegistry Summary
Static Information
BDH Use Case
Message
Header Business Document Messageprocessing routing Auth.(SSO)
Profile of Message Body Organization Collaboration Business Document
Content
Connection Error
Business Document Header
Etc.
Message
HTTPBinding
FTPBinding
SMTPBinding
Etc.Binding
・・・
Transport Message IP Address
Quality of Service
Dialect in Specific Protocol such as HTTP
Business Document MessageBusiness Document Content
(UN/CEFACT [ASMA], OAGi, UBL, Other)
Business Document Header R
eg
istry Su
mm
ary (C
SP
Oth
er)
Transport(REST, other)
Binding
Messaging Service Layer
Any Questions ?