1. Information meeting to bridge the railway and e-standards communities
Geneva, 21 Sept. 2011
CIM/SMGS and international standards for electronic trade and transport document and data exchange (UN and WCO)
Information meeting to bridge the railway and e-standards communities
Mario Apostolov, UNECE Regional Adviser on trade

2. CIM/SMGS and international document and data exchange standards
UN Layout Key for trade and transport documents

3. Рекомендация №1 ЕЭК: Формуляр-образец для торговых документов

4. Is the form aligned to the UNLK ?
If not, does it hurt electronic exchange ?

5. CIM/SMGS and international document and data exchange standards
UN Layout Key for trade and transport documents
Data alignment and harmonization
Create a data model
Establish a seamless flow of information among modes of transport, between B & G (B2G)
Single Window/Port Community Service environment

6. Rec. 20: Units of measurement
Rec.3: Country code ISO
Rec. 16:
UN/Locode
Rec. 16:
UN/Locode
Rec.3: Country code ISO
Rec. 20: Units of measurement

7. Mapping to the WCO Data Model: Results of the preliminary analysis (S
Mapping to the WCO Data Model: Results of the preliminary analysis (S.P. Sahu)
Preliminary, unverified work, needs to be explored further. Possible to convert this information into international standards; several attempts at making an e-consignment note A few EDIFACT adaptations of the railway consignment note, making mapping difficult.
A rough and preliminary examination of data requirements and documentation of CIM/ SGMS suggests that it is based entirely on paper processes.
Boxes cannot be considered as data elements. These could be a combination of data elements and placeholders for other documentation and references.
There are no standard descriptions of the business process at stuffing, loading, transshipment and intermediate locations.
It is not clear if and how Customs make use of these documents. In case Customs uses these documents, what is the Customs procedure involved?
The Document appears to be used for both transport and regulatory purposes. It would be ideal to separate the two and keep those pieces of information consistent with each other.
Complete digitization of this process may require a proper documentation of the business processes, data exchange contexts, exploration of data standards and code lists.
WCO Data Model can cover regulatory reporting. Freight aspects reflected in the consignment note, even though partially covered by the data model may not be adequate.

8. Railway information flows
EDIFACT
XML
Message Type : IFTMIN
Version : D
Release : 97A
Contr. Agency: UN
Revision : 7
Date :
SOURCE: Western European EDIFACT Board
Standardized; agreemts between countries
Not-standardized – much time, volume, resources

9. Rec. 34: Why harmonize data requirements ?
Ø unnecessary information
Build a Single Window environment
Establish electronic data interchange 9 9

10. Port Community System (Dakosy Hamburg): Import message platform

11. IMO/FAL data Certificates Customs data Railway data
Road transport data
IMO/FAL data

12. e-corridor / transit

13. Data in the FAL, CMR, SAD 31 PSC-RE ** 4412 Packaging condition
Values include "packed" or "repacked" 32
Container condition
Values include "new" or "original" 33
Basis for certification
Values include "original phytosanitary certificate" or "additional inspection"
FAL1
arrival or departure
1.1a
T005
8212
Name of ship
Name of a specific means of transport such as the vessel name
1.1b
T010
8179
Type of ship
Code specifying a type of means of transport.
1.2
T006
8213
IMO number
To identify a specific means of transport such as the International Maritime Organisation number of a vessel
1.3
240
Call sign
1.4
FAL2
149
voyage number
S.P.Sahu has included it (?) 2a
L054
3392, 3393, or 3225 (location.Identifier)
Port of arrival
Name or code identifying the port, airport or other type of location at which a means of transport is scheduled to arrive or has arrived
The use of Recommendation 16: The UN/LOCODE is recommended (text), 3393 (coded); or as suggested by Kenji Itoh in Japan: 3225 (location.Identifier) 2b
L053
3214, 3215, or 3225 (location.Identifier)
Port of departure
Name or code identifying the port, airport or other type of location from which a means of transport is scheduled to depart or has departed
The use of Recommendation 16: The UN/LOCODE is recommended (text), 3215 (coded). Or, as suggested by Kenji Itoh in Japan, 3225 (location.Identifier) 3a
172
2106 or 2107, or 2001 (Date.Date.Date Time)
Date - time of arrival
Date and or time of the arrival of means of transport (in figures and words or coded).
2106 (text) or 2107 (coded), or 2001 (Date.Date.Date Time) as suggested by Kenji Itoh in Japan. 3b
156
2280 or 2281 or 2001 (Date.Date.Date Time)
Date - time of departure
Date and or time of the departure of means of transport (in figures and words or coded)
2280 (text) or 2281 (coded) or 2001 (Date.Date.Date Time) as suggested by Kenji Itoh in Japan. 4
T014
8453
Flag State of ship
8453 (Transport Means. Registration Nationality.Identifier) coded
SAD 55; 8452 is the same thing but text only - the country's name - and a flag of vessel, nationality of vessel can be related to it, while 8453 is coded. We recommend the use of the UN country code. 5
R016
3408
Name of master
Name of the master of the vessel
Japan suggested 3036 (Party. Name.Text) 6
81A L L
3095 (for next port of call) or 3224 (Location. Name.Text)
Last port of call/Next port of call
To identify a port, airport or other type of location which is the next place that a means of transport is scheduled to call. Or 3224 (Location. Name.Text)
itinerary class 7a
1001
Certificate of registry (Port; date; number) port
1001 (Document.Type.Code) 7b
D002
2001
Certificate of registry (date)
2001: Date.Date.Date time. To identify the date on which a means of transport has been officially registered. 7c
D005
1004
Certificate of registry (number)
To identify the number under which a means of transport has been officially registered. 7d
D004
3411 ? or 3105 (Document.Issue Location. Idwentifier)
Certificate of registry (location)
3411: to identify the place at which a means of transport has been officially registered. or 3105 (Document.Issue Location. Idwentifier)

14. Data Harmonization of 3 documents
Durres, Sept. 2010
Data Harmonization of 3 documents
142 Data Elements
Set of 299
Data Elements
7 IMO FAL forms
Collect
110 Data Elements
SAD
47 Data Elements
CMR c.n.
Required = 299 data elements 14

15. Data Harmonization of 3 documents
Durres, Sept. 2010
Data Harmonization of 3 documents
64 Data Elements
Standardized
Data Set of the
9 documents
119
Data Elements
7 IMO FAL forms
harmonized
Standardization
and Data
Harmonization
16 Data Elements -2
Transit declaration
47 Data Elements-9
CMR c.n.
Standardization and Harmonization can reduce the data elements
from 299 to 119 required data elements 15

16. Rec. 34: Why harmonize data requirements ?
Ø unnecessary information
Build a Single Window environment
Establish electronic data interchange
Key steps in data harmonization
Capturing
Identifying and inventorying agencies requirements
Defining
The meaning – what information is conveyed
Analyzing
Comparing similar names and definitions
Reconciling
Agreement to use one name, definition, coding 16 16

17. Collect, Define, Analize, Align
HARMONIZE
STANDARDIZE
Currently agencies gather:
Port of unlading
Port of unloading
US Port of unlading
US Port of unloading
Foreign Port of unlading
Foreign Port of unloading
From the WCO Data Model:
Place of discharge,
Code in UNTDED: 3225
Port of
Unloading
Port codes
4-digit proprietary US
5 -digit Schedule ‘K’
proprietory CA
proprietory MX
UN/LOCOD
Recommendation16 UNECE 17 17

18. Why align data with international standards?
Eight cities with the name Odessa in the world:
In the USA:
US ODF (FL) in Canada:
US ODG (MO) CA ODE (ON)
US ODS (NY)
US OSD (TX) in Ukraine:
US ZGY (DE) UA ODS
US ZOA (NE)
…just try to send a container to Canada, using electronic data submission, to Odessa, Canada, without UN/LOCODE
The second column is the country subdivision code. 18

19. UNTDED semi-structured standard19 19

20. UNLK & TDED data element mapping
UID
Name
Definition
Repr.
Mapping
3246
Consignment.Delivery Location.Text
The place at which the cargo leaves
the custody of the carrier under the
terms and conditions of the transport
contract
an..256
UNLK: L 26, P 27-44 20 20

21. UNLK & TDED data element mapping
UID
Name
Definition
Repr.
Mapping
3246
Consignment.Delivery Location.Text
The place at which the cargo leaves
the custody of the carrier under the
terms and conditions of the transport
contract
an..256
UNLK: L 26, P 27-44
UID
Name
Definition
Repr.
Mapping
Coded
3247
Consignment.Delivery Location.Identifier
To identify the place at which the cargo
leaves the custody of the carrier under
the terms and conditions of the
transport contract
an..35
UNLK: L 25, P 36-44
UN Locode 21 21

22. Next steps: