data harmonization for single windows · objective: to integrate malaysia’s ucustoms system with...

CrimsonLogic Copyright 2014 (Private) CrimsonLogic Copyright 2014 Private & Confidential

All rights reserved. „CrimsonLogic‟ and the Shell Device are trade marks of CrimsonLogicPte Ltd. All information contained in this presentation is disclosed to you on the basis of a prospective business relationship and is proprietary to CrimsonLogic Pte Ltd and may not be used, disclosed or reproduced without the prior written consent of CrimsonLogic.

CrimsonLogic

All rights reserved. „CrimsonLogic‟ and the Shell Device are trade marks of CrimsonLogicPte Ltd. All information contained in this presentation is disclosed to you on the basis of a prospective business relationship and is proprietary to CrimsonLogic Pte Ltd and may not be used, disclosed or reproduced without the prior written consent of CrimsonLogic.

1

Data Harmonization for Single Windows Using the WCO Data Model Presented by: Mr. Ian Hogg Trade Facilitation Centre of Excellence Trade Sector Group

CrimsonLogic Pte. Ltd.

CrimsonLogic Copyright 2014 (Private) 2

AGENDA

1. Introduction

2. Our Approach

- UNECE Recommendation No. 34

- WCO Data Model v3.3+

3. Case Study

- Royal Oman Police

4. What‟s Next?


Introduction


ABOUT US

• Singapore company – established in 1988

• End-to-end eGovernment solutions provider

Trade Facilitation

Judiciary & Law

Healthcare Management

Government & Citizen

• We specialise in implementing:

Single Windows

Customs Management Systems

Port Community Systems

Free Trade Zone Systems


TRADE FACILITATION PROJECTS

Consultancy Single Window

System Port Community

System

Customs Management

System Free Trade Zone

System ASP Services

Canada

USA

Mexico

Jamaica

Panama Trinidad and Tobago

Chile

Saudi Arabia

Ghana

Mozambique Madagascar

Kenya Sri Lanka

India

Mongolia

Tajikistan

Qatar Oman

China

Bangladesh

Singapore

Brunei

Papua New Guinea

Brazil

Peru

Greece

Ivory

Coast

Vietnam

Mauritius

Japan


REMINDER: WHAT IS A SINGLE WINDOW?

UNECE Recommendation No. 33, July 2005

A Single Window is a facility that allows parties

involved in trade and transport to lodge

standardized information and documents with

a single entry point to fulfill all import, export,

and transit-related regulatory requirements. If

information is electronic, then individual data

elements should only be submitted once.

Source: www.unece.org/cefact/recommendations/rec_index.html


WHAT IS DATA HARMONIZATION?

UNECE Recommendation No. 34, December 2010

Following the simplification and standardisation

process described in the Recommendation

guidelines, a government should be able to

reduce the regulatory and official information

requirements through the elimination or

duplication of submissions and the removal of

redundant data elements. The outcome of the

process should be a more efficient and

effective exchange of information between

Trade and Government.”

Source: www.unece.org/cefact/recommendations/rec_index.html


WHAT IT MEANS … IN PRACTICAL TERMS

It is more than just “mapping” to the WCO Data Model

• We identify the government stakeholders of a Single Window

• Customs

• Permit Issuing Agencies • Other Government Agencies • Port Authorities • Financial Institutions

• We analyze and harmonize the documents and data sources of these stakeholders

• Customs Declarations • Licences • Permits • Certificates • Others e.g. financial and statistical reports

• We produce a standardized data set to facilitate Government-to-Government exchange


Our Approach UNECE Recommendation No. 34


AN ITERATIVE 4-STEP APPROACH

CAPTURE

… data sources, such as Customs

declarations, permits, licenses etc.

DEFINE

… every data element, including its name,

definition, format etc.

ANALYZE

... the complete data set, identifying and removing duplicate

data elements

RECONCILE

… against international

standards, such as UN/CEFACT, WCO

etc.


STEP 1: CAPTURE

Prepare a national trade data inventory of current government agency data and

information requirements from automated systems and documents to cover all

requirements for the international trade procedures related to import, export and

transit.

What we do

• Identify the relevant stakeholders, such as;

• Customs

• Other Government Agencies / Permit Issuing Agencies

• Any others with data requirements e.g. Finance, Statistics etc.

• Interview the stakeholders

• To understand their business processes

• To capture their document / data requirements

• Create an inventory of data sources i.e. documents and systems


STEP 2: DEFINE

Prepare a record giving the name, definition and representation (text, format or

code) of each data element; also when the information is required (for release,

declaration, pre or post control) and the legal base allowing the relevant agency

to demand, collect, view and retain (archive) the information.

What we do

• Record a comprehensive inventory of data elements, including;

• A unique reference

• The name of the ministry e.g. Ministry of Finance, Ministry of Agriculture etc.

• The name of the department e.g. Customs, Quarantine etc.

• The name of the data source e.g. Import Declaration, Cargo Manifest etc.

• The name of the data element i.e. the label on the document

• The data type e.g. text, decimal, date, code etc.

• The format or code list (if known) e.g. ISO Country Code, UN/LOCODE


STEP 3: ANALYZE

Prepare an analysis of the information requirement and data element, establishing

whether its need is essential and its use can be demonstrated. While information is

identified by name, the meaning (what information is communicated by the data

element) and context are more important. The process of analyzing the

information consists of gathering together similar data element names and having

a full understanding of the definition of each data element and the information

requirements.

What we do

• Identify and remove duplicate data elements

• Create a final data set by assigning unique references to each data element

• Cross-reference the unique data elements to the original data sources


STEP 4: RECONCILE

Prepare a consolidation of the defined and analyzed trade data listing through the

process of reconciliation. This involves the agreement to use one data element

name with a common definition and (or) common coding, and reconciled

primarily with the international standards of the United Nations Trade Data

Elements Directory (UNTDED) and the UN/CEFACT Recommended Code List.

Should the team identified other reference data models for the Single Window

development, the data elements could be further mapped to other standards

such as UN/EDIFACT set of Directories (Electronic Data Interchange for

Administration, Commerce and transport), World Customs Organization (WCO)

Data Model and UN/CEFACT Core Component Library (CCL).

What we do

• Map the final set of data elements to the WCO Data Model

• Identify local data elements which are not available in the WCO Data Model

• Document these data elements as potential candidates to submit to the WCO

• Create a standardized data set, in compliance with the WCO Data Model


Our Approach WCO Data Model v3.3+


INFORMATION PACKAGES

The output from the Data Harmonization exercise, i.e. the final data set, is the basis

of our “Information Packages” - used to generate WCO compliant XML messages.


DECLARATION RESPONSE LPCO INTER-GOV

GOODS DECLARATION

CARGO REPORT

Import

CONVEYANCE REPORT

eTIR

Export

Transit

Export

Import

GUARANTEE

EU CoO

CITES


SOFTWARE TOOLS


DATA MAINTENANCE REQUESTS (DMRS)


DERIVED INFORMATION PACKAGES


Case Study Royal Oman Police


PROJECT: OMAN ICMS & ESW

“The Directorate General of Customs of the

Royal Oman Police in the Sultanate of Oman

is in the process of developing a new

Customs system and Single Window based

on international best practices, and using

WCO Data Model version 3.3 as the basis for

the messaging and data components.

CrimsonLogic is providing valuable

assistance and expertise as we engage with

our partner government agencies to capture

and document their requirements and in

developing a standardized data set for Oman.

The challenge lies in capturing all of the

requirements and accurately documenting

the processes and data involved in their

„business-to-government‟ (B2G) processes.”

Colonel Yahya Al-Maimani

Customs Project Director

Directorate General of Customs

Royal Oman Police

WCO News

February 2014

Scope In the original requirements, the Royal Oman Police called for what they called an “Enterprise Data Model (EDM)”.

During the project, we agreed with the customer that we would develop a “Standardized Data Set” consisting of all of the data elements required for cargo clearance.

Objectives

The main objectives of carrying out Data Harmonization for this project were: • To create a national data set for cargo clearance

• To capture requirements of all border control agencies

• To align them with the WCO Data Model v3.3

• To build a WCO compliant National Single Window


SUMMARY OF RESULTS

The initial Data Harmonization exercise in Oman took a total duration of 6 months and the results of this exercise were as follows:

CAPTURE

… data sources, such as Customs

declarations, permits, licenses etc.

DEFINE

… every data element, including its name,

definition, format etc.

ANALYZE

... the complete data set, identifying and

removing duplicate data elements

RECONCILE

… against international standards, such as

UN/CEFACT, WCO etc.

In the first phase, we identified 16 permit issuing agencies and/or departments and 110 documents

We identified almost 3783 data elements on 100 data sources –

the remaining were considered to be out of scope

After mapping the data elements to the WCO Data

Model v3.3, we were able to identify 200 unique data elements

The initial data set was used to design the Single Window system, including the user interfaces, the

interfaces to the agencies and the data to be submitted by traders



The standardized data set was then entered into a tool to develop WCO compliant information packages, in order to generate XML schemas as part of the system development.

DECLARATION LPCO RESPONSE

Import

LICENCE

PERMIT

CERTIFICATE

OTHER

Export

Transit

Master Manifest

House Manifest


INTER-GOV DECLARATION LPCO RESPONSE

GOODS DECLARATION

CARGO REPORT

Base Information Package

Oman Derived Information Package

Oman My Information Package

WCO


MORE INFORMATION: WCO NEWS

In February 2014, CrimsonLogic shared our experiences of carrying out Data Harmonization in Oman in an article that was published in the WCO News.

In this article, we shared that we were able to identify 200 data elements, and we were able to map 190 of these to the WCO Data Model v3.3. For the remaining data elements, CrimsonLogic has been

helping the Royal Oman Police to submit their requirements to the WCO, to be included in a future version of the WCO Data Model. In January 2014, five of the data elements were accepted by the WCO‟s Data Model Project Team (DMPT).

The magazine can be downloaded from the WCO website: http://www.wcoomd.org/en/media/wco-news-magazine/latest.aspx

http://www.wcoomd.org/en/media/wco-news-magazine/latest.aspx







What‟s Next?


MALAYSIA UCUSTOMS

Why is WCO Data Model v3.4 important for Malaysia? NATIONAL: INTER AGENCIES

Objective: To integrate all agencies involved in cargo clearance into Malaysia’s uCustoms system

• Permit Issuing Agencies

• Other Government Agencies

• Port Authorities

• Financial

• Others

REGIONAL: ASEAN SINGLE WINDOW (ASW)

Objective: To integrate Malaysia’s uCustoms system with the other National Single Windows in ASEAN

INTERNATIONAL: GLOBAL CUSTOMS COMMUNITY

Objective: To integrate Malaysia’s uCustoms system with the other Customs Authorities around the world

• Brunei Darussalam

• Cambodia

• Indonesia

• Lao PDR

• Myanmar

• Philippines

• Singapore

• Thailand

• Vietnam

• Globally Networked Customs • WCO Data Model • WCO SAFE Framework

data harmonization for single windows · objective: to integrate malaysia’s ucustoms system with...

Documents