Review of Standards for Logistics Information … - Review...UN/CEFACT Recommendations • Total of 40 recommendations, of which 21 closely related to information sharing and data

Review of Standards for

Logistics Information Service Systems

Transport Division Bangkok, 10-11 December 2015

Content

• International Standards

• National Standards

• Key issues in Data Harmonization

• Challenges

International Standards

UN/CEFACT efforts

• UN/CEFACT • The subsidiary, intergovernmental body of the

UNECE Committee on Trade.

• Its principal focus is on facilitating national and international transactions, through the simplification and harmonization of processes, procedures and information flows.

• Its outputs includes recommendations, standards and technical specifications.

UN/CEFACT Recommendations

• Total of 40 recommendations, of which 21 closely related to information sharing and data exchange.

• Facilitation of Trade Procedures

• Harmonization of Documents

• UN/EDIFACT

• Codes

Recommendations on Facilitation of trade procedures

• Rec.4 National Trade Facilitation Organs; Arrangements at the national level to coordinate work on facilitation of trade procedures

• Rec.12 Measures to Facilitate Maritime Transport Documents Procedures

• Rec.13 Facilitation of Identified Legal Problems in Import Clearance Procedures

• Rec.15 Simpler Shipping Marks

• Rec.18 Facilitation Measures related to International Trade Procedures

Recommendations on Facilitation of trade procedures (continue)

• Rec.27 Pre-shipment Inspection

• Rec.33 Recommendation and Guidelines on establishing a Single Window

• Rec.34 Data Simplification and Standardization for International Trade

• Rec.35 Establishing a Legal Framework for an International Trade Single Window

• Rec.40 Consultation approaches Best Practices in Trade and Government Consultation on Trade Facilitation matters

Recommendations on Harmonization of documents

• Rec.1-2 United Nations Layout Key for Trade Documents

• Rec.6 Aligned Invoice Layout Key for International Trade

• Rec.11 Documentary Aspects of the International Transport of Dangerous Goods

• Rec.22 Layout Key for Standard Consignment Instructions

United Nations Layout Key for Trade Documents

• Trade Documents – Quotation, Order, Invoice etc.

• Materials Management Documents – Despatch Advice, Pick List, Packing List etc.

• Transport Documents – Bill of Lading, Shipping Instructions etc.

• Customs Documents – Export, Import, Transit Declarations, Cargo Reports etc.

• Other Regulatory Documents – Certificate of Origin, DGN etc.

Application example

• UNLK + UNECE Rec. Codes

Recommendations on UN/EDIFACT

• Rec.14 Authentication of Trade Documents by means other than signature

• Rec.25 Use of the United Nations Electronic Data Interchange for Administration, Commerce and Transport (UN/EDIFACT)

• Rec.26 Commercial Use of Interchange Agreements for Electronic Data Interchange (EDI)

• Rec.31 Electronic Commerce Agreement

• Rec.32 E-Commerce Self-Regulatory Instruments (Codes of Conduct)

Recommendations on Codes

• Rec.3 ISO Country Code: Code for Representation of Names of Countries

• Rec.5 Abbreviations of INCOTERMS: Alphabetic Code for INCOTERMS 2000

• Rec.7 Numerical Representation of Dates, Time and Periods of Time

• Rec.8 Unique Identification Code Methodology-UNIC

• Rec.9 Alphabetic Code for the Representation of Currencies

• Rec.10 Codes for the Identification of Ships

• Rec.16 UN/LOCODE: Code for Trade and Transport Locations

Recommendations on Codes(continue)

• Rec.17 PAYTERMS: Abbreviations for Terms of Payment

• Rec.19 Codes for Modes of Transport

• Rec.20 Codes for Units of Measure Used in International Trade

• Rec.21 Codes for Types of Cargo, Packages and Packaging Materials

• Rec.23 Freight Cost Code-FCC; Harmonization of the Description of Freight Costs and other Charges

• Rec.24 Trade and Transport Status Codes

• Rec.28 Codes for Types of Means of Transport

• Rec.29 Codes for Types of Cargo

(Merged with Recommendation 21)

Standards Codes

• Rec.3

• Country code (ISO 3166)

• Rec.9

• Currency code (ISO 4217)

Countries Name

Two-letter

alphabetic

Three-letter

alphabetic

Three-digit

numeric

China CN CHN 156

France FR FRA 250

Name of country

Alpha - 2 Country code (ISO 3166)

Alpha - 3 Currency code(s)

China CN CNY

United States US USD

Standards Codes(continue)

• Rec.7

• Dates, times, periods of time (ISO 8601)

• Calendar date:1994-05-10,19940510,94-05-10, 940510

• Ordinal date: 1994130

• Time of the day: 19940510T1000, 1994-05-10T1000, 199405101000

• Co-ordinated Universal Time (UTC):232030Z, 152746+0100 (or +01), 152746-0500 (or -05)

• Week: 1994 W 15, 199415

• Other periods of time: 1994/1996, 1994-02/04, 1994-02/1994-04,etc.

Standards Codes(continue)

• Rec.16

• Location code (UN/LOCODE), UN/EDIFACT Standard

LOCODE Name NameWoDiacritics SubDiv Function Status

Date IATA

Coordinates Remarks

CN PEK Beijing Shoudu International Apt

Beijing Shoudu International Apt

11 ---456-- AS 1407

CN BJX Beijingxizhan

Beijingxizhan 11 123----- AS 1407

CN SHG Shanghai Pt Shanghai Pt 31 1-3----- AS 1407

CN SFH Suifenhegongluzhan/Suifenhe

Suifenhegongluzhan/Suifenhe

23 --3----- AS 1401 4425N 13111E

US NYC New York New York NY 12345--- AI 0401 4042N 07400W

DE BER Berlin Berlin BE 12345--- AF 0207 5231N

01323E

Other codes

• Rec.23

• Freight cost code-FCC

Group Subgroup Detail Description Mode/Site Indicator

Duplicate Indicator

1 00 000 FREIGHT CHARGES

1 00 999 All freight charges

1 01 000 BASIC FREIGHT

1 01 021 Airfreight (FF) D1

1 02 000 FREIGHT CHARGE ALLOWANCE

1 02 002 Allowance - wool

2 00 000 GOODS HANDLING CHARGES

2 00 999 All goods handling charges

2 02 000 HANDLING EQUIPMENT HIRE CHARGES

Other Codes(continue)

• Rec.19

• codes for modes of transport

CI Code Name

#I 0 Transport mode not specified

I 1 Maritime transport

I 2 Rail transport

I 3 Road transport

I 4 Air transport

I 5 Mail

I 6 Multimodal transport

I 7 Fixed transport installation

I 8 Inland water transport

#I 9 Transport mode not applicable


• Rec.28

• Codes for Types of Means of Transport

Transport Mode

Code-A Code-B Name Description

1 50 General cargo vessel

Vessel designed to carry general cargo.

2 10 Train, railroad One or more rail wagons pulled or pushed by one or more locomotive units, or self-propelled, that move over rail tracks.

3 4 2 Van, light Automotive vehicle designed for light carriage.

4 00 0 Aircraft, type unknown

Aircraft of unknown type

5 00 0 Mail, type unknown

Mail of unknown type

6 0 Multimodal, type unknown

Multimodal transport of unknown type.


• Rec.21

• packaging codes

Code Name Description Numerical code

1A Drum, steel 34

1B Drum, aluminum 34

1F Container, flexible 93

2C Barrel, wooden 44 or 45

43 Bag, super bulk 64

4A Box, steel 21 to 25

6P Composite packaging, glass receptacle

23 or 24 or 25 or33 or 34 or 62 or 63

8A Pallet, wooden 24 or 25


• Rec.20

• codes for units of measurement

Group Number

Sector Group ID Quantity Level/ Category

Common Code

Name Symbol

01 Space and Time

18 length, breadth, height, thickness, radius etc.

1M DMT decimetre dm

01 19 1S CMT centimetre cm

01 20 1S 4H micrometre (micron)

µm

01 21 1S MMT millimetre mm

01 22 1M HMT hectometre hm

01 23 1S KTM kilometre km

01 24 1S KMT kilometre km

01 25 1S C45 nanometre nm


• Rec.24

• Trade and Transport Status Codes

Code Code Name Description

1 Arrival, completed The goods/consignment/equipment/means of transport has arrived.

2 Loading, authorized Authorization to load has been given.

35 Forwarded to destination The goods/consignment/equipment has been forwarded to a destination.

353 Delivery not completed, business closed on Saturday

The goods/consignment/equipment could not be delivered as the business was closed on Saturday.


• Rec.10

• Codes for the Identification of Ships

• IMO Ship Identification Number Scheme

• Structure: two parts

— Prefix “IMO”

— a variable seven-digit numeric number

(the Lloyd's Register number)

e.g. IMO 1234567


• Rec.17 PAYTERMS abbreviations

Group Abbreviations (Excerpt)

1- Documentary Credits 1.1.1 CREDOC – Unconfirmed, period of time for payment unspecified (1.1 Irrevocable) 1.2.1 RECREDOC – Period of time for payment Unspecified (1.2 Revocable)

2- Collections 2.1 COLLECT – Clean collection, 2.2.2 DOCOLLECT/nM – Period of time for payment stated

3- Payment by instalments PARTS

4- Other types of payment 4.1.1 AAAA/MM/JJ – Payment on a fixed date 4.1.2.2 CASH – Payment on delivery 4.1.3.4 FAC/nM; INV/nM – Payment at the end of a period following receipt of the invoice

5- Special arrangements 5.1 AGREE – Payment by agreement 5.2 HABIT – Payment on customary terms

6 – Without payment NOPAY


• Rec.5 INCOTERMS abbreviations

• Incoterms ® 2010

INCOTERMS FOR ANY MODE OR MODES OF TRANSPORT (Excerpt)

EX WORKS EXW (insert named place of delivery)

DELIVERED AT TERMINAL DAT (insert named terminal at port or place of destination)

FREE CARRIER FCA (insert named place of delivery)

DELIVERED AT PLACE DAP (insert named place of destination)

INCOTERMS FOR SEA AND INLAND WATERWAY TRANSPORT (Excerpt)

FREE ALONGSIDE SHIP FAS (insert named port of shipment)

COST AND FREIGHT CFR (insert named port of destination)

FREE ON BOARD FOB (insert named port of shipment)

COST, INSURANCE AND FREIGHT CIF (insert named port of destination)


• Rec.8

• unique identification code (UNIC)

• Code structure：a combination of three UNTDED data elements(1154, 3039, 3055)

XXX/XXXXXXXXXXXXX/XXXXXXXXXXXXXXXXX

Reference number

(1154, restricted to an..17)

Code list responsible agency,

coded

(3055, an..3)

Party identification, coded

(3039, restricted to an..13)


• Commodity code (Harmonized System)

• International Convention on the Harmonized Commodity Description and Coding System

• Application

• Customs tariffs

• Collection of international trade statistics

• Rules of origin

• Collection of internal taxes

• Transport tariffs and statistics

• …

UN/CEFACT Standards

• UN/EDIFACT

• UN/EDIFACT-ISO9735 (ISO/TC 154)

• UNTDED-ISO7372

• UN/LOCODE

• Core Components Library (UN/CCL)

• Business Requirement Specifications(BRS)

• Requirements Specification Mappings (RSM)

• XML Schemas

UN/TDED (ISO 7372- ISO/TC 154)

• The United Nations Trade Data Element Directory

• Volume I – Data Elements Directory (ISO 7372)

• Volume II – User Code List (UNCL)

• Volume III – Compendium of Trade Facilitate Recommendation

Tag UID

New Name Description repr. Old name

Notes Locations, Bridges

3050 Consignment. Route.Text

Description of a route to be used for the transport of goods.

an..512 Routes

CIM: an..38x3; L 24-26, P 45-82 (CIM 49) AWB: L 22, P 27-44 CIMP: (313):a3

3051 Consignment. Route.Code

Code specifying a route to be used for the transport of goods.

an..35 Route, coded

CIM: n..3; L 44, P 18-19 and L 50, P 18-19 and L 56,P 18-19 and on reverse of CIM form (CIM 54)

UNTDID

• United Nations Trade Data Interchange Directory

• Message type directory(EDMD)

• Segment directory (EDSD)

• Composite data element directory (EDCD)

• Data element directory (EDED)

• Code list (CL)

UNTDID (continue)

• UN/EDIFACT standard message ( UNSM, 196)

• Usually business Documents

• e.g. Bayplan/stowage plan occupied and empty locations message

Message Type : BAPLIE

Version : D

Release : 15A

Contr. Agency : UN

Revision : 7

Date : 2015-06-11

BAPLIE_D.15A.txt

UNTDID (continue)

• BAPLIE (D15A), Message structure

UN/EDIFACT syntax rules-ISO 9735

• ISO 9735 Electronic for administration, commerce and transport (EDIFACT) -- Application level syntax rules (Syntax version number: 4, Syntax release number: 1) Part 1- 10

• Part 1: Syntax rules common to all parts

• Part 2: Syntax rules specific to batch EDI

• Part 3: Syntax rules specific to interactive EDI

• Part 4: Syntax and service report message for batch EDI (message type -- CONTRL)

• Part 5: Security rules for batch EDI (authenticity, integrity and non-repudiation of origin)

UN/EDIFACT syntax rules-ISO 9735 (continue)

• ISO 9735 Electronic for administration, commerce and transport (EDIFACT) -- Application level syntax rules (Syntax version number: 4, Syntax release number: 1) Part 1- 10

• Part 6: Secure authentication and acknowledgement message (message type - AUTACK)

• Part 7: Security rules for batch EDI (confidentiality)

• Part 8: Associated data in EDI

• Part 9: Security key and certificate management message (message type- KEYMAN)

• Part 10: Syntax service directories

UN/CCL

• Correlative technical specifications • “Core Component Technical Specification” (ISO/TS

15000-5)。

• defines a meta-model and rules, the semantics of document artifacts

• the structure of the core components (BCCs and ASCCs making up ACCs)

• “Core Components Data Type Catalogue”

• Catalog and procedures for maintaining UN/CEFACT Core Data Types

• two categories of data Types (DTs)

— Core Data Type (CDT)

— Business Data Type (BDT)

UN/CCL (continue)

• Core Components Library • CC – ACC, BCC, ASCC

• Party as a CC has many attributes and can be reused to define many parties within a trade transaction

• BIE – ABIE, BBIE, ASBIE

• CI_ Trade_ Party is an ABIE (Aggregate Business Information Entity)

• Correlative technical specifications • “Core Components Data Type Catalogue”

• “Core Component Technical Specification” (ISO/TS 15000-5)。

UN/CCL (continue) )- BCC,ABCC,ASCC

UN/CCL (continue)- BBIE,ABIE,ASBIE

BRS, RSM

• Business Requirement Specifications(BRS) and Requirements Specification Mappings (RSM)

• Documentation templates based on UMM

• formalized deliverables : building blocks of business processes and information

• harmonization and standardization of data and process descriptions: across business application and technical solutions, can be used in paper documents, EDI message structures and e-business system

• BRS template documents user requirements in business terms as reusable UML artifacts or worksheets

• RSM template documents information requirements of business process in technical terms aligned to syntax specific solutions, using BRS output as the input.

XML Schemas Directories

• The following three parts are defined as XSD (XML Schemas Definition) , structure and contents, validation

• Code list, e.g.

• EDIFICASEU_PartyType_D10A.xsd

• IANA_CharacterSetCode_20101104.xsd

• ISO_ISO3AlphaCurrencyCode_20110218.xsd

• Data, e.g.

• AccountingEntryMessage_1p0.xsd

• CrossIndustrySupplyNotification_1p0.xsd

• MaterialSafetyDataSheet_5p0.xsd

• Identifier list, e.g. • ISO_ISOTwoletterCountryCode_SecondEdition2006VI-

8.xsd

• UNECE_FreightCostCode_4.xsd

• UNECE_PaymentTermsDescriptionIdentifier_D10A.xsd

UN/CEFACT Technical Specifications

• Core Components Data Type Catalogue

• Core Component Technical Specification

• Core Components Business Document Assembly

• UML Profile for Core Components

• UN/CEFACT Modelling Methodology (UMM)

• XML Naming and Design Rules

Core Components Business Document Assembly

• Builds on the UN/CEFACT Modeling Methodology (UMM)

• Business Document Assembly

• Rules for how a Message Assembly is named, defined and structured

• Business Context – Association of BIE and Message Assemblies

UML Profile for Core Components

• Define precise mappings from CCTS / UMM concepts to corresponding UML elements

• consists of stereotypes, tagged values and OCL constraints

• Implementation — an XMI Template file

• ensures consistent model exchange

• interchange of structurally and semantically valid information models

UN/CEFACT Modelling Methodology (UMM)

• design the business services that each business partner must provide in order to collaborate,

• based on Open-EDI reference model

• business semantics of a B2B partnership

• BOV: BDV, BRV, BTV, BSV

• define external and internal Business Collaboration Frameworks

• using a UML tool

• UMM WORKSHEET to capture relevant information

• UMM Data Types and Notation

• a set of predefined structure documents capturing the business domain knowledge.

XML Naming and Design Rules

• an architecture and set of rules to define, describe and use XML to express business information exchanges based on CCTS

• using for developing XML schema and schema documents

• using XML Schema to define the structure of business content

• Sections

• XML Schema Architecture

• General XML Schema Language Conventions

• XML Schema Files

• XML Instance Documents

ebXML（ISO/TC154 , ISO 15000）

• ebXML Message Service (OASIS’s responsibility, ISO 15000-1)

• ebXML Collaboration Protocol Profile and Agreement (OASIS’s responsibility, ISO 15000-2)

• ebXML Business Process Specification Schema (OASIS’s responsibility, ISO 15000-3)

• ebXML Registry (OASIS’s responsibility , ISO 15000-4)

• ebXML Core Components (UN/CEFACT’s responsibility,CCTS, , ISO 15000-5)

UBL (OASIS , ISO/IEC FDIS 19845)

• A suite of structured business objects

• reusable data components and common business documents in generic procurement and transportation contexts.

• in conformity with CCTS (Version 2.01)

• developed by an OASIS TC and a variety of industry data standards organizations

• support for XAdES and other advanced digital signature schemes based on XML DSig, internationally accepted EDI code lists

• Consists of

• a library of XML schemas for data components such as “Address”, “Item”, and “Payment”

• A set of XML schemas for common business documents such as “Order”, “Dispatch Advice”, and “Invoice”

International Maritime Organization (IMO)

• IMO Convention on Facilitation of International Maritime Traffic (FAL) • providing a firm legal framework for trade facilitation

measures, other conventions

• "Standards" and "Recommended Practices" on formalities, documentary requirements and procedures

• Standards • FAL Form1 General Declaration

• FAL Form2 Cargo Declaration

• FAL Form3 Ship’s Store Declaration

• FAL Form4 Crew’s Effects Declaration

• FAL Form5 Crew List

• FAL Form6 Passenger List

• FAL Form7 DG Manifest

IMO FAL Form1

International Maritime Organization (IMO)

(continue)

• Revised IMO Compendium on Facilitation and Electronic Business • Recommendation on FAL Forms in electronic format

(annotated with cross-references to UN/EDIFACT data codes)

• FAL Form 1- Message Implementation Guideline for CUSREP

• FAL Form 2 - Message Implementation Guideline for CUSCAR

• CUSCAR (On arrival or departure) Mapping Table

• FAL Form 3 – INVRPT or CUSCAR

• FAL Form 4 – Message Implementation Guideline for PAXLST

• PAXLST Mapping Table

• FAL Form 5 – Message Implementation Guideline for PAXLST

• PAXLST Mapping Table

• FAL Form 6 – Message Implementation Guideline for Passenger List (PAXLST)

• FAL Form 7– Message Implementation Guideline for IFTDGN

• IFTDGN Mapping Table

International Air Transportation Association (IATA)

• Cargo Interchange Message Procedures (Cargo-IMP)

• 77 messages, created as a handful of EDI messages, widely used in the air cargo industry, Message Specifications : embedded data elements, abbreviation codes, and enhanced search function printing capabilities

• Maintenance of the Cargo-IMP was stopped

• Cargo-XML Standards

• the table of Cargo-XML messages (next slide)

• Conversion Guidelines between Cargo-XML and CARGO-IMP (By IATA)

• based on the character set, data length, field occurrence, structure, semantics, and data types for both standards

International Air Transportation Association (IATA)(continue)

• Cargo-XML Standards

IATA Cargo-XML Manual and Toolkit (Specification and schemas)

International Air Transportation Association (IATA)(continue)

Feature comparison between Cargo-IMP and Cargo-XML

World Customs Organization (WCO)

• The International Convention on the Simplification and Harmonization of Customs Procedures (Kyoto)

• Main body of revised Convention

• General and Specific Annexes

• Standards

• Transitional Standards

• Recommended Practices

WCO Data Model Components

UN/ESCAP document

• Data Harmonization and Modelling Guide for Single Window Environment (ESCAP)

• step-by-step approach for data harmonization of electronic documents

• Capture data requirements of business documents identified through business processes analysis

• Define data in each document and the semantic of the data and the data formats

• Analyze data elements across various documents and organize them in a comparable manner

• Map data elements to reference data model

• Obtain the structure of an electronic document

UN/ESCAP document(continue)

• Business Process Analysis Guide to Simplify Trade Procedures(ESCAP)

• step-by-step approach of the implementation of Single Window, UML activity diagram

• 6 steps

— Define the project scope

— Develop a work plan and secure resources

— Acquire background information

— Conduct interviews and document captured data

— Analyze the “as-is” processes;

— Develop and propose recommendations

GS1/EPC Global

• EPC Information Services Standard (EPCIS, ISO/IEC 19987)

• data presentation and business rules in capturing and exchanging goods data, event-based supply chain visibility, Complementary to EDI (not replacement)

• data sharing Interfaces for capture and query of events

• Events: What, Where, When, and Why, record originated from RFID sensor reads and enterprise systems

• Core Business Vocabulary (CBV, ISO/IEC 19987)

• vocabulary elements and their values

GS1/EPC Global(continue)

• Three layers

• Abstract Data Model: CBV (not extensible)

• identifiers: Event Type names, Event Field names, Vocabulary names, Vocabulary Elements, and Master Data Attribute Name

• Data Definition: Core event types, Core Query XSD (event types)

• Service

• EPCIS standard XML events

• data definitions could be reused in an EDI framework

• a core set of data types and operations to be extended for industry-specific use

• six event types: EPCISEvent, ObjectEvent, AggregationEvent, QuantityEvent, TransactionEvent, TransformationEvent


• Core Business Vocabulary (CBV, ISO/IEC 19987Three layers)

• vocabulary elements and their values

• Standard Vocabulary elements

• Business Step, Disposition, Business Transaction Type, Source/Destination Type

• The templates for User Vocabulary elements • Object (EPC), Object Class (EPCClass), Location

(Read Point and Business Location), Business Transaction ID, Source/Destination ID, and Transformation ID


• CBV - Business Steps

Neal-Net

• Vessel Schedule Status and Container Status

• adopts EPCIS framework which is suitable for status sharing

• provides standardized query interface

• intentions to extend NEAL-NET to include other logistics and cargo status such as customs clearance status

Codes in national standards

Codes in national standards

• Most national standards adopt international widely accepted codes in their own standards

• Codes in UN/CEFACT Recommendations • Country code (ISO 3166)

• Currency code (ISO 4217)

• Dates, times, periods of time (ISO 8601)

• Location code (UN/LOCODE)

• Units of measurement code

• Mode of transport code

• Freight code

• Packaging code

• Commodity code (WCO Harmonized System)

• IMO Vessel ID number

Codes in national standards(continue)

• UNTDED Code lists are adopted in some national standards • LOGINK, PORT-MIS, SP- IDC, GCTS, PortNet, and

TradeNet

• Commodity code(WCO Harmonized System) • E-Port, PORT-MIS, SP- IDC, uTrade, PortNet, and

TradeNet;

• IMO Vessel ID number • LOGINK, E-Port, PORT-MIS, SP- IDC, GCTS, and

PortNet;

• In order to fit in national environment for special need in China, some customized codes added in LOGINK • transport status, service requirements, freight charge

and fee

Key issues on data harmonization

Data harmonization and Standardization

• Standardization • uniform business processes, well-defined practice

(benefits on cost and performance)

• individual business units

• Harmonization • alignment of national formalities, procedures,

documents, information, and operations to acceptable international commercial norms, practices and recommendations.

• prevention or elimination of differences in the technical content of standards having the same scope

• sets bounds to the degree of variation

• levels of standardization and harmonization • Strategic positioning, and Strategy

• Business processes

• Data

• Issues of standardization and mutual recognition

Business process harmonization

• Define templates: Rather than defining every single piece of a process, a template just defines the essential part of a standard and leaves a well defined degree of freedom for local adaptation.

• Where to start: Any process can be a starting point.

• Compliance with internationally accepted standards for electronic data exchange (for both business process and data)

• UN/CEFACT Draft Recommendation 34 (UN/CEFACT, 2009b).

• international conventions and standards should be applied (ADB and ESCAP, 2009)

Data harmonization

• Data model to support widespread interoperability

• to define core set of data, aligning the definition, representation, as well as the cardinality of data elements and define the structure of electronic messages.

• a single set of generic semantic rules

• a syntax independent representation and structure of data used in the electronic exchange, reusable data building block

• e.g. Buy-Ship-Pay Model

• data harmonization process • APEC ECSG (2009), consistent with UN/CEFACT Rec. 34

• data harmonization steps

Data harmonization (continue)

• Outputs

• a set of data dictionaries and message implementation guidelines

• a essential input for the technical Architecture of the system

• maintenance requirements • Inappropriate mappings of data elements

• New data requirements of business

• Newer version of the reference data model

Interoperability

• Technical interoperability (Syntax, interface)

• communication and technology for data sharing

• Communication interoperability: a set of communication protocols

• Data sharing technology: EDIFACT,XML

• Semantic interoperability – data harmonization

• data models comply with relevant international recommendations and standards to ensure semantic interoperability. • CCTS,UN/CLL, UN/TDED, UNLK

• WCO Data Model (G2G, G2B,B2G), supports all above in UN/EDIFACT and XML syntax

Other challenges

Other challenges

• Three layers challenges

• Data Architecture

• Application Architecture

• Legislative Architecture

Data alignment challenges

• harmonization of procedures and data of various national ministries

• with different international reference models

• UN Core Component approach (business-oriented reference data models)

• WCO Data Model 3 is a convergence version with UN Core Component approach

• or national reference model

• whether and how to align with other national and regional systems implementations

• Organization-specific, country-specific, industry-specific data elements ,codes, qualifiers, components, and messages.

• data mapping and integration between different information systems even more difficult

Application and Legislative challenges

• Application challenges

• Legacy systems would be difficult to align with other standards

• Legislative alignment challenges • Extensive differences in administrative rules and

requirements

• burden to both governments and the business community, serious barrier to the development of international trade.

• need to create an environment for interagency coordination and collaboration additional

Thank you Secretariat, Transport Division email: [email protected]