Geneva 21 Sept 2011 CIM SMGS and international standards

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 mario. apostolov@unece. org

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

Рекомендация № 1 ЕЭК: Формуляр-образец для торговых документов http: //www. unece. org/cefact/recommend ations/rec 01_01 cf 15. pdf

? LK N e. U th e? to ng ed ha gn xc i al ce m ni or ro f ct e le th s te I ur th si oe , d ot fn I

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 (B 2 G) • Single Window/Port Community Service environment

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

Mapping to the WCO Data Model: Results of the preliminary analysis (S. P. Sahu) 1. Preliminary, unverified work, needs to be explored further. Possible to convert this information into international standards; several attempts at making an e-consignment note https: //www. railcargo. at/de/E-Services/e-frachtbrief/Downloads/anwenderhandbuch. pdf. A few EDIFACT adaptations of the railway consignment note, making mapping difficult. 2. A rough and preliminary examination of data requirements and documentation of CIM/ SGMS suggests that it is based entirely on paper processes. 3. Boxes cannot be considered as data elements. These could be a combination of data elements and placeholders for other documentation and references. 4. There are no standard descriptions of the business process at stuffing, loading, transshipment and intermediate locations. 5. 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? 6. 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. 7. Complete digitization of this process may require a proper documentation of the business processes, data exchange contexts, exploration of data standards and code lists. 8. 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.

Railway information flows EDIFACT XML Message Type : IFTMIN sion ease Ver : D : 97 A Rel Contr. Agency: UN vision Date Re : 7 : 96 -12 -13 SOURCE: Western European EDIFACT Board Standardized; agreemts between countries Not-standardized – much time, volume, resources

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

Port Community System (Dakosy Hamburg): Import message platform

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

e-corridor / transit

Data in the FAL, CMR, SAD 31 PSC-RE ** * 4412 ** Packaging condition Values include "packed" or "repacked" 4412 ** Container condition Values include "new" or "original" ** ** Basis for certification Values include "original phytosanitary certificate" or "additional inspection" * 32 PSC-RE ** * * 33 PSC-RE ** * * FAL 1 arrival or departure 1. 1 a FAL 1 T 005 8212 Name of ship Name of a specific means of transport such as the vessel name 1. 1 b FAL 1 T 010 8179 Type of ship Code specifying a type of means of transport. 1. 2 FAL 1 T 006 8213 IMO number To identify a specific means of transport such as the International Maritime Organisation number of a vessel 1. 3 FAL 1 240 8213 Call sign 1. 4 FAL 2 149 voyage number S. P. Sahu has included it (? ) 2 a FAL 1 L 054 3392, 3393, or 3225 (locatio n. Identi fier) 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. 3392 (text), 3393 (coded); or as suggested by Kenji Itoh in Japan: 3225 (location. Identifier) 2 b FAL 1 L 053 3214, 3215, Port of departure Name or code identifying the port, airport or other The use of Recommendation 16: The UN/LOCODE is

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

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

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

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

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

UNTDED semi-structured standard

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

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

Next steps: • •