UN/CEFACT Evolution/Revolution Reference Data Models ... · 10/16/2018 · Reference Data Model: subset of the library UN/CEFACT Core Component Library (CCL) Subset of UN/CEFACT

UN/CEFACT Evolution/Revolution

Reference Data Models (Semantic Models)

Gerhard Heemskerk SCRDM Lead Editor

Sue Probert MMT RDM Lead Editor

Rolf Wessel SCRDM Project Lead

UN/CEFACT Forum Hanghzou, 16 October 2018

Agenda

• Principle of Reference Data Models• Mr. Gerhard Heemskerk, lead editor SCRDM

• Multi-Modal Transport RDM• Ms. Sue Probert, Chair UN/CEFACT , lead editor MMT

• Link between Supply Chain and Transport• Mr. Rolf Wessel, project lead SCRDM

UN/CEFACT Forum, Hangzhou 15-19 October 2018 2

Principle of UN/CEFACT Reference Data Models

Mr. Gerhard Heemskerk, lead editor SCRDM

Principle of

RDM


A new way to facilitate eBusiness communication

• A semantic model that suits more the data exchange requirements of the future such as for data pipelines as well as for traditional document based data exchanges.

• Reducing dependency on traditional documents by focussing more on process driven data and workflows.


A new way to facilitate the future

traditional documents & process driven data

5UN/CEFACT Forum, Hangzhou 15-19 October 2018

traditional infrastructure & super highways

What is a UN/CEFACT Reference Data Model?

• An exchange syntax neutral semantic model, a rich collection of

business artefacts (subset of library), contextualized for a specific

domain

• Based on:

• UN/CEFACT Core Component Library (CCL)

• UN/CEFACT BRSs (Business Requirement Specifications)

• UN/CEFACT principles of UN Layout Key

• UN Trade Data Element Directory

• UN/EDIFACT

• UN/CEFACT principles (harmonization, standardization simplification)


Benefits of UN/CEFACT Reference Data Models

• Efficient• to implement (restriction of artefacts used, not used principle)

• to maintain (restriction of same artefact instead of doc specific ones)

• to find, appropiate artifacts in one subset of the CCL (no redundancy)

• light weight message xsd’s (only needed re-usable BIEs, qDT’s, uDT’s)

• Trusted semantic model • international standardized & harmonized

• links to rich legacy of UN Key Layouts and UN/EDIFACT

• Enhances interoperability • sharing data e.g. Supply Chain (SCRDM) & Transport (MMT RDM)

• integrated international code lists (UNECE, UN/EDIFACT, ISO etc.)

• Future proof • a syntax neutral semantic model

• support information sharing, such as enabled by data pipelines


What is the evolution?

8

• Moving from document centric to process driven

artefacts

• Still supporting document centric & process driven

workflows and data exchange structures

• Introducing a standardized master message structure,

syntax-neutral data from which complete documents

and/or snippets can be created

UN/CEFACT Forum, Hangzhou 15-19 October 2018

Reference Data Model: subset of the library

UN/CEFACT Core Component Library (CCL)

Subset of UN/CEFACT Core Component Library

Master Message Structure

BusinessData Exchange

Structure(s)

Process Driven Artefacts(only Reference BIEs used)

Example: SCRDM Subset of CCL

Example: SCRDM CII (Invoice)


No more dependency on traditional documents

Header_ Trade Agreement.Details

Process driven artefact(Reference BIE)

Document Centric Process Driven

Above artifacts can only be used for specific documents

Same artifact can be used within different processes

and message structuresData contextualized for a process and/or a message structure

Master message structure Contextualized for

complete documents or snippets


Simplification: Supply Chain 40% less needed,than using document centric approach

11

Ob

jects

0

500

1000

1500

2000

2500

06A 06B 07A 07B 08A 08B 09A 09B 10A 11A 11B 12A 12B 13A 14A 14B 15A 15B 16A 16B 17A 17B

CCL Progress

ACCs ABIEs qDTs MessagesKey:ABIE - Aggregate Business Information EntitiesACC - Aggregate Core Component qDT – Qualified DataType

Versions

Supply Chain Management & ProcurementTransport & LogisticsAccounting and AuditAgriculturalEnvironmental Management Finance and Payment Travel and Tourism Insurance

123 Messages169 Code lists

1218 Businessartefacts

579 Core components


Multi Modal Transport Reference Data Model

Ms. Sue Probert, lead editor MMT RDM(Multi Modal Transport Reference Data Model)

MMT

RDM


The model behind the UN/CEFACT MMT RDM

13

The international Supply Chain Reference Model

SHIPBUY PAY

Prepare for

ExportExport Transport ImportPrepare for

Import

INVOLVES

Commercial

Procedures

•Establish Contract

•Order Goods

•Advise On Delivery

•Request Payment

•Packing

•Inspection

•Certification

•Accreditation

•Warehousing

Transport

Procedures

•Establish Transport

Contract

•Collect, Transport

and Deliver Goods

•Provide Waybills,

Goods Receipts

Status reports etc.

Regulatory Procedures

•Obtain Import/Export

Licences etc

•Provide Customs

Declarations

•Provide Cargo

Declaration

•Apply Trade Security

Procedures

•Clear Goods for

Export/Import

Financial Procedures

•Provide Credit

Rating

•Provide Insurance

•Provide Finance

•Execute Payment

•Issue Statements


Actors/Roles

Customer

Buyer

Final Consignee

Importer

Transport Services Buyer

Actors/Roles

Authority

Customs

OGAs

Certification Authority

Chamber of Commerce

Actors/Roles

Intermediary

Transport Services Provider

Carrier

Freight Forwarder

Bank

Customs Agent

Insurer

Actors/Roles

Supplier

Seller

Original Consignor

Exporter

Transport Services BuyerPurchase and

Supply

International

Identify Potential

Sales Partner

Establish

Agreement

(Sales)

Order(Sales)

Ship Pay(Sales)

Sales

Quotation

Sales

Order

Order

(Transport)

Ship

Transort

Services

Sales

InvoiceTransport Service

Contract

Border Clearance(s)

Import/Export

Declarations

Cargo and Trasnit

Reports

Origin and other

Certificates

Establish

Agreement

(Transport)

Pay

(Transport) )

Sales Contract

The Relationship betweenInternational Sales and Transport Service Contracts

14Copyright UNECE


Relationship Commercial and Logistical data

15

Trade. Details

Order. Identification.

Identifier

Shipment. Details

Shipment. Identification.

Identifier

Trade_ Packaging. Details

Trade_ Packaging.

Identification. Identifier

Trade item. Details

Trade Item.


Consignment. Details

Consignment.


Transport Movement. Details

Transport Movement. Stage.

Identifier

Transport Equipment. Details

Transport Equipment.


Transport_ Packaging. Details

Transport_ Packaging


Consignment Item. Details

Consignment Item.


1..*

1

1..*

1..*

1..*

1..*

1..*

1..*

1..*

0..*

1..*

1..*

1..*

1

1

1

1

11

1

0..*

10..*

0..*

0..*

0..*0..*

0..*

1..*

1..3

1..*

1..* 0..*

1

1..*Customs Item. Details (Trade)

Customs Item. Identification.

Identifier

1

1

1..*

Cargo Report. Details

Cargo Report Identification.

Identifier

1

Import/Export Declaration. Details

Declaration Identification.

Identifier

1

Transport Means. Details

Transport Means.


1..*

1

Customs Item. Details (Transport)

Customs Item. Identification.

Identifier

1..*

1..*1

1

1

1..*

Commercial Processes

Logistical ProcessesRe

gula

tory

Pro

cess

es

Buy/Ship/Pay – Cross Border Trade, Transport & Customs – Business Entity Overview


Using a common library and deriving messages

Supply Chain(BUY PAY)

Semantic model

e.g. Invoice

e.g. Order

e.g. Quotation

BUY PAY Master (Master message structure)

BUY SHIP PAY Semantic model

UN/CEFACT Core Component Library (CCL)

Based onBased onBased on

Based on

Multi Modal Transport(SHIP)

Semantic model

e.g.Bill of Lading

e.g. Booking

e.g. BayPlan

Based on

Based on Based on

Based on

Based on

BUY SHIP PAY Master(Master message structure)

Based on

Based on

16

164*123* 111*

1218*

Based on Based on

SHIP Master (1)

(Master message structure)

SHIP Master (2)

(Master message structure)


* No of ABIEs

BUY SHIP PAY master message structure

17

B

The ‘Common Master’ message structure

BUY SHIP PAY (BSP) semantic model

Library CCL

Based on

Based on

BUY SHIP PAY MASTER(master message structure)


BUY SHIP PAY Reference Data Model

18

CO

MP

LETE

LIB

RA

RY

UN

/CEF

AC

T C

CL

BUY SHIP PAY Semantic model

Library subset/restrictions

Based on


BUY SHIP PAY RDM – Contextualized

19

SCRDM Semantic model


MMTSemantic model


BU

Y SH

IP P

AY

Sem

anti

c m

od

elBased on


SCRDM & MMT (Trade Price contextualized)

20

SCRDMSemantic model

Trade Price subset/restriction

MMTSemantic model

Trade Price subset/restriction

SEM

AN

TIC

MO

DEL

TR

AD

E P

RIC

EBased on


Quotation

Invoice

1:1

1:1

1:1

1:1

1:1

1:1Order

1:1

1:1

1:1

1:1

1:1

1:1

0:1

1:1

Remittance Advice

1:1

1:1

1:1

1:1

21

Supply Chain – BUY PAY - subsettingSCRDM master message structure

Contextualized SCRDM messages structure


22

Bill of Lading /IFTMCS

Container BayPlan /BAPLIE

Pipeline Data Exchange Structure (CORE/SELIS)

C

Operational Manifest /IFCSUM

1:1

1:1

1:1

1:1

1:1

1:*

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:* 1:*

Contextualized MMT RDM messages structureMulti Modal Transport – SHIP - subsetting

MMT RDM master message structure


The MMT based E-CMR & IMO FAL message

eCMR IMO FAL


TDED and code lists linksEDIFACT

Data Element

24

Common TermShort name


Code List

Link between Supply Chain and Transport

Mr. Rolf Wessel, project lead editor SCRDM(Supply Chain Reference Data Model)

Link

Supply Chain and Transport


Supply Chain & Transport related projects

SCRDM- Extension of Cross Industry Invoice technical artefacts- Extension of Cross Industry Cataloguing, Quotation, Ordering,

Delivering and Remittance Advice technical artefacts- Extension of Cross Industry Cross Industry Scheduling- Cross Industry Invoice-BRS Repository- Proposed: Revised BRS Despatch & Receive process

General- Procedures for RDM & associated artefacts publication- Code Management Project- Proposed: CCBDA profiles Schema Project

MMT RDM- e-CMR- IMO FAL- Data Pipeline Carrier- Smart Containers

Finalized


BSPPublication Buy Ship Pay Reference Data Model ProjectProposed: Cross Industry Track &Trace

Publication

Finalized

Publication

Development

Proposed

Proposed

Finalized

Finalized

Development

Development

Development

Finalized

Finalized

Proposed

Supply Chain & Transport sharing same docs

White Paper• Concept outline of a Reference Data Model

BRS & CCBDA message structures (Supply Chain & Multi Model Transport)BRS (Business Requirements Specification)• Processes in the Supply Chain domain• Relations to Transport, Finance, Government domains• The actors and scenariosCCBDA message structures• Mapping business requirements to business information entities (Ref BIE)

Guideline• Executive summary• Philosophy behind the concept• Working process and methodology • Steps for using, updating and creating


Supply Chain & Transport simularity

• Processes

• Party Roles


Supply Chain Transport

Quoting products & services Booking Transport

Ordering products & services Ordering Transport

Confirming Order Confirmation Transport Order

Instructing Delivery/Handling Instructing Shipping

Despatching/Receiving products Picking up/Unloading goods

Invoicing goods & services Invoicing freight

Synchronizing & status on deliveries Synchronizing & status on transport

Supply Chain Transport

Buyer/Customer Final Consignee

Seller/Supplier Original Consignor

Buyer/Customer Transport Service Buyer

Invoice issuer Invoice Issuer

Invoicee Invoicee

Sales Agent Freight Forwarder

Buy

Ship

Pay

Supply Chain & Transport common language

Buy/Ship/Pay RDM

Supply Chain

RDM

Multi Modal

Transport RDM

Geographical CoordinateLogistics LocationLogistics PackageLogistics Transport EquipmentLogistics Transport Means

Logistics Transport MovementSupply Chain Consignment

Trade Delivery Terms (inco)

Transport Dangerous Goods

Trade PartyTrade ContactTrade AddressReferenced Documents

Logistics Service ChargeLogistics LabelDelivery InstructionsHandling Instructions

Logistics Shipping Marks

Shared Business Artefacts


Supply Chain & Transport optimizing planning

Demand Forecasting

Inventory Forecasting

Supply Instruction

SupplyNotification

Consumption

Reporting

Despatching

Receiving

Transport PlanningSupply Chain

Scheduling

Supply Chain Delivery

Reporting Status & Events

Reporting Status & Events

Transport &Logistics


Transport Movement

Thank you for your attention!

For further information:UNECE secretariat

- Chief, UN/CEFACT Unit : Lance Thompson: email: [email protected]

Supply Chain Management Reference Data Model (SCRDM)

- Project Lead : Rolf Wessel : email: [email protected]

- Lead Editor : Gerhard Heemskerk email: [email protected]

Multimodal Transport Data Reference Model (MMT RDM)- Lead Editor : Sue Probert

email : [email protected]


mailto:[email protected]

