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
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
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
Core Data Type
Content Component
Core Data Type
Supplementary Components
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
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
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)
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.
CC & BIE Relationship
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
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
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)
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.
Business Requirement Specification (BRS)
Conceptual Data Model
class ConceptualModel
Requirement Specification Mapping(RSM)
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)
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 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
ebXML
WCO
Specification
Agricultural
Industry
Chemical
Industry
GS1
SWIFT
Transportation
Industry
Governments
Electronics
Industry
28
Message Assembly
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
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
Process
Semantics
Structure
Syntax
Methodologies
Content
Implementations
Business process
Business Process
Methodology
‘core’ Business Process
Models
‘community’ business
processes
Core Components
Core Component
Methodology
‘core’ component
library
‘community’
components
Content constraints
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