United Nations Network of Experts for Paperless Trade and Transport in Asia and the Pacific

Data Harmonization for Single Window Environment

Module 4 Part 2 Introduction into Standards and Concepts for Electronic Trade Documents

Introduction into the WCO Data Model

Subregional Capacity Building Workshop on Data Harmonization for Trade Facilitation 6 – 7 December 2018 Kemerovo, Russian Federation Topics

 United Nations Layout Key (UNLK)  United Nations Trade Directory (UNTDED)  Data Models for Electronic Trade documents ◼ CCTS (Core Components Technical Specification)  World Customs Organization (WCO) Data Model

2 Data Model

Segment of XML Schema for CoO

3 CCTS (Core Components Technical Specification)

 CCTS is a methodology to describe the semantic and the logic structure of trade information independently from the implementation of a specific syntax for data interchange

 CCTS provides guidelines to identify, define, and name data elements with an aim to maximize the reuse of business information to support and enhance information interoperability across organizational borders and industries.

 Core Components (CC) ◼ Standardized data elements that are used for constructing electronic business documents/messages. ◼ Generic representations of information on UML object classes

4 Core Components Overview

5 Core Components and Class Diagram

Core Data Types (CDT) defines data type that a BCC may contain. Aggregate Core Component (ACC) represents Object Class.

Association Core Component (ASCC) represents a relation between Object Classes.

Basic Core Component (BCC) represents simple properties of Object Class.

6 CCTS Naming Convention

Naming Convention • A semantic Naming Convention is a set of rules for naming and defining data elements and structures to remove potential ambiguity by ensuring that separate data structures will not be defined with the same semantic meaning but with different names.

CCTS Naming Convention  The Dictionary Entry Name of any Core Component is unique.  Dictionary Entry Names consist of Object Class Terms Property Terms, Representation Terms, Qualifiers and Special Terms (like “Details” or “Type”). ◼ Terms are separated by a period (.) and a single space. ◼ Qualifiers are separated by an underscore (_) and a space ◼ Multiple words are separated by spaces  Dictionary Entry Names are ISO11179 compliant.

7 ISO/IEC 11179-5: Naming and Identification Principles

All Core Component naming conventions conform to the guidelines and principles described in the ISO/IEC 11179 Part 5: “Naming and Identification Principles”  ISO/IEC 11179 Part 5 uses a multi-part naming convention for data elements. Example: Tripartite Data Element Naming

Object Class + Property Term + Representation Term

the primary concept the distinguishing the form or or Object Class characteristic or Property Representation of the of the data element of the Object Class data element e.g. Product e.g. Cost e.g. Amount Document Estimated Arrival Code Process Price Transport Means Status Text

Examples of DEN: Product. Price. Amount Document. Status. Code Transport Means. Estimated Arrival. Date Time

8 ISO/IEC 11179 - Data Element Model

 Data Element Classification Structure has 3 major parts: ◼ Object Class: Represents an activity or object in a context  It essentially answers the question “What is this data element about?”  Examples: Organization, Address, Project ◼ Property Term: Further distinguishes the data element from other data elements of the same Object Class  Examples: Name, City, Start ◼ Representation Term: Describes the representation format of a data element  Examples: Text, Date, Code, Amount  The CCTS includes a list of Approved Representation Terms 9 ISO/IEC 11179 - Core Component Construct

Dictionary Entry Name BCC Person. Identification. Identifier

Object Class Term Property Term Representation Term

Conceptual Generic = BCC property Data Element Data Element

 Generic data elements are reusable across object classes. ◼ Project. Identification. Identifier ◼ Registration. Identification. Identifier ◼ Route. Identification. Identifier ◼ Service Charge. Identification. Identifier  Business Core Component properties are reusable across ACCs. ◼ Project. Details ◼ Registration. Details ◼ Route. Details ◼ Service Charge. Details

10 ISO/IEC 11179 - Core Component Construct Aggregate Core Component (ACC)

 A collection of related pieces of business information that together convey a distinct real-world object with a specific business meaning, independent of any specific business context  Aggregate Core Components (ACCs) represent Object Classes  Dictionary Entry Name (DEN) of an ACC = “Object Class Term” + “Details” which is a suffix appended to an object class to reflect that the ACC contains all relevant and generic properties of the particular real-world object.

Address Details ObjectGoods Class Term Representation Term

DEN: Address. Details

12 Basic Core Component (BCC)  A singular business characteristic/property of specific ACC that can be used in any business context

 Basic Core Components (BCCs) represent simple properties of ACCs or attributes of Object Classes  Dictionary Entry Name (DEN) of a BCC = “Object Class Term” + “Property Term” + “Representation Term” Goods Delivery Date Time

Object Class Term Property Term Representation Term DEN: Goods. Delivery. Date Time 13 Association Core Component (ASCC)

Association Core Components (ASCCs) represent complex properties of parent ACCs that associate two ACCs or relationships between Object Classes.

Dictionary Entry Name (DEN) of an ASCC = “Object Class Term” + “Property Term” + “Representation Term” where Representation Term of an ASCC is the Object Class Term of associated ACC

Person Residence Address

Object Class Term Property Term Object Class Term DEN: Person. Residence. Address 14 Examples of Multiple Core Components

Person. Details Aggregate Core Component Person. Name. Text Basic Core Component Person. Birth. Date Basic Core Component Person. Residence. Address Association Core Component Person. Official. Address Association Core Component

Address. Details Aggregate Core Component Address. Street. Text Basic Core Component Address. Post Code. Text Basic Core Component Address. Town. Text Basic Core Component Address. Country. Identifier Basic Core Component

15 Core Data Types

 Smallest piece of business information which defines the “type” of information or nature of content of a BCC: ◼ Primitive Type, e.g., decimal, integer, string, date, binary, etc. ◼ CDT Content Component e.g., Amount. Content ◼ CDT Supplementary Component(s) that carries essential extra definition to the content e.g., Amount. Currency. Code List Version Identifier

16 CCTS Core Data Types

Amount A number of monetary units specified in a currency where the unit of the currency is explicit or implied Code 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 together with relevant supplementary information. Identifier A character string to identify and distinguish uniquely, one instance of an object in an identification scheme from all other objects in the same scheme together with relevant supplementary information. Indicator A representation of a situation that has exactly two mutually exclusive Boolean values

Measure A numeric value determined by measuring an object along with the specified unit of measure. Numeric Numeric information that is assigned or is determined by calculation, counting, or sequencing. It does not require a unit of quantity or unit of measure. Quantity A counted number of non-monetary units possibly including fractions.

Text A character string (i.e. a finite set of characters) generally in the form of words of a language. Binary Object A set of finite-length sequences of binary objects.

Date Time A particular point in the progression of time together with the relevant supplementary information.

17 CCTS Core Data Types

18 Business Information Entity (BIE)

 A Business Information Entity (BIE) is a Core Component used in a specific business context

 The Data Type for a Business Information Entity may be the same as the Data Type for the Basic Core Component on which it is based, or it may be further restricted.

 Qualifier Term (word/words) ◼ used to define and differentiate a BIE from its associated CC and other BIEs. ◼ creates controlled vocabulary that has unique semantic within a specific context ◼ promotes “extension by restriction” ◼ added in front of an Object Class, a Property Term, or both

ACC ABIE

BCC BBIE

ASCC ASBIE

19 Context Categories

Context Category Description Example Business Process The type of business process as described in UN/CEFACT Ordering Catalogue of Common Business Processes Delivery Product Classification Factors influencing semantics that are the result of the Parts goods or services being exchanged, handled, or paid for, Consumer etc. Goods Industry Classification Semantic influences related to the industry or industries of Aerospace the trading partners Agriculture Geopolitical The location of the partners International Europe Official Constraints Legal and governmental influences on semantics, e.g., the US Law legislation that applies EU Law Business Process Role The actors conducting a particular business process as Buyer described in UN/CEFACT Catalogue of Common Business Seller Processes Supporting Role Semantic influences related to non-partner roles (e.g., data Shipping Agent required by a third-party shipper in an order response going from seller to buyer.) System Capabilities This context category exists to capture the limitations of EAN.UCC systems (e.g. an existing back office can only support an System address in a certain form) SAP 20 Business Context of Conceptual Core Components

21 Basic Business Information Entity (BBIE)

 Basic Business Information Entities (BBIEs) are reuses of BCCs  Dictionary Entry Name (DEN) of a BBIE = Qualifier Term(s) + BCC Object Class Term + Qualifier Term(s) + BCC Property Term + Qualifier Term(s) + BCC Representation Term

Partial Cost Period Total Amount Amount

Qualifier Term Object Class Term Qualifier Term Property Term Representation Term

Cost Total Amount Amount Underlying BCC Object Class Term Property Term Representation Term

DEN: Partial_ Cost. Period_ Total Amount. Amount

22 Building Block Aggregate Business Information Entity (ABIE)

 As with Aggregate Core Components, related Basic Business Information Entities are grouped together to form “Aggregate Business Information Entities (ABIEs)”  Aggregate Business Information Entities (ABIEs) are reuses of ACCs  Dictionary Entry Name (DEN) of an ABIE = Qualifier Term(s) + ACC Object Class Term + “Details”

Home Address Details Address Address Details Qualifier Term Object Class Term Representation Term

Address Details Underlying ACC Address Object Class Term Representation Term

DEN: Home_ Address. Details

24 Association Business Information Entity (ASBIE)

 When an Aggregate Business Information Entity is contained within another Aggregate Business Information Entity, an “Association Business Information Entity (ASBIE)” is used  Association Business Information Entities (ASBIEs) are reuses of ASCCs  Dictionary Entry Name (DEN) of an ASBIE = Qualifier Term(s) + ACC Object Class Term + Qualifier Term(s) + ACC Property Term + Qualifier Term(s) + ACC Object Class Term

Important Person Temporary Residence Address

Qualifier Term Object Class Term Qualifier Term Property Term Object Class Term

Person Residence Address Underlying ASCC Object Class Term Property Term Object Class Term

DEN: Important_ Person. Temporary_ Residence. Address

25 Examples of Multiple Business Information Entities

US_Person. Details Aggregate Business Information Entity US_ Person. Name. Text Basic Business Information Entity US_ Person. Birth. Date Basic Business Information Entity US_ Person. US_ Residence. US_ Address Association Business Information Entity US_ Person. US_ Official. US_ Address Association Business Information Entity

US_ Address. Details Aggregate Business Information Entity US_ Address. Street. Text Basic Business Information Entity US_ Address. ZIP_Post Code. Text Basic Business Information Entity US_ Address. Town. Text Basic Business Information Entity

26 Business Data Type (BDT)

BDT defines the “type” of information or nature of content of a BBIE

27 XML Naming and Resign Rule

XML Naming and Design Rule

This XML Naming and Design Rules specification defines an architecture and set of rules necessary to define, describe and use XML to consistently express business information exchanges. XML Schema Transition between CCTS and XML Schema The Structure of XML Schema

ReusableAggregateBusiness InformationEntitySchema

UnqualifiedDataTypeSchema QualifiedDataTypeSchema Root XML Schema Reusable ABIE XML Schema