This document is an excerpt from the EUR-Lex website
Document 32019R1744
Commission Implementing Regulation (EU) 2019/1744 of 17 September 2019 on technical specifications for electronic ship reporting in inland navigation and repealing Regulation (EU) No 164/2010
Commission Implementing Regulation (EU) 2019/1744 of 17 September 2019 on technical specifications for electronic ship reporting in inland navigation and repealing Regulation (EU) No 164/2010
Commission Implementing Regulation (EU) 2019/1744 of 17 September 2019 on technical specifications for electronic ship reporting in inland navigation and repealing Regulation (EU) No 164/2010
C/2019/6537
OJ L 273, 25.10.2019, p. 1–182
(BG, ES, CS, DA, DE, ET, EL, EN, FR, HR, IT, LV, LT, HU, MT, NL, PL, PT, RO, SK, SL, FI, SV)
In force
|
25.10.2019 |
EN |
Official Journal of the European Union |
L 273/1 |
COMMISSION IMPLEMENTING REGULATION (EU) 2019/1744
of 17 September 2019
on technical specifications for electronic ship reporting in inland navigation and repealing Regulation (EU) No 164/2010
THE EUROPEAN COMMISSION,
Having regard to the Treaty on the Functioning of the European Union,
Having regard to Directive 2005/44/EC of the European Parliament and of the Council of 7 September 2005 on harmonised river information services (RIS) on inland waterways in the Community (1), and in particular point (b) of Article 5(1) thereof,
Whereas:
|
(1) |
Electronic reporting in inland navigation should contribute to the safety and efficiency of inland navigation, by enabling electronic data interchange for reporting purposes to and between competent authorities and to facilitate electronic data interchange among the parties involved in inland waterway transport. Electronic reporting should help to avoid multiple reporting of the same data to competent authorities and other parties in the transport chain. |
|
(2) |
The development of harmonised river information services (RIS) laid down in Directive 2005/44/EC requires the establishment of technical specifications, including, inter alia, on electronic ship reporting. |
|
(3) |
The technical specifications for electronic ship reporting laid down in Commission Regulation (EU) No 164/2010 (2) specify the messages, data items, codes and references to be used in electronic reporting for enabling specific services and functions of RIS in line with Directive 2005/44/EC. |
|
(4) |
Technical specifications for electronic ship reporting should take due account of the technological progress and the experiences gained from their application, including the introduction of mandatory electronic reporting requirements on major rivers in Europe. For that reason, the technical specifications defined in Regulation (EU) No 164/2010 should be revised and clarified. |
|
(5) |
The revised technical specifications should take due account of the latest internationally adopted standards, guidelines and experiences gained as a result of their application, such as the relevant standards by the United Nations Economic Commission for Europe (UNECE), the Central Commission for the Navigation of the Rhine (CCNR) and other international bodies. In addition, the specific provisions of Directive (EU) 2016/1629 of the European Parliament and of the Council (3) and Commission Implementing Regulation (EU) 2018/2032 (4) should be considered. |
|
(6) |
The revised technical specifications should take due account of the requirement of compatibility with other modes of transport, in particular maritime transport. This should be achieved by making use of internationally standardised notification messages, accepted code lists and classifications and following guidelines as defined by the Protect (5) group. |
|
(7) |
Pursuant to Article 12(2) of Directive 2005/44/EC technical specifications should enter into force immediately after their publication and Member States should apply those specifications not later than 30 months after entry into force. |
|
(8) |
Taking into account the extent of required changes, Regulation (EU) No 164/2010 should be repealed. |
|
(9) |
The measures provided for in this Regulation are in accordance with the opinion of the Committee referred to in Article 11 of Directive 2005/44/EC, |
HAS ADOPTED THIS REGULATION:
Article 1
The technical specifications for electronic ship reporting in inland navigation shall be as set out in the Annex.
Article 2
Regulation (EU) No 164/2010 is repealed.
Article 3
This Regulation shall enter into force on the day following that of its publication in the Official Journal of the European Union.
It shall apply not later than 30 months after its entry into force.
This Regulation shall be binding in its entirety and directly applicable in all Member States.
Done at Brussels, 17 September 2019.
For the Commission
The President
Jean-Claude JUNCKER
(1) OJ L 255, 30.9.2005, p. 152.
(2) Commission Regulation (EU) No 164/2010 of 25 January 2010 on the technical specifications for electronic ship reporting in inland navigation referred to in Article 5 of Directive 2005/44/EC of the European Parliament and of the Council on harmonised river information services (RIS) on inland waterways in the Community (OJ L 57, 6.3.2010, p. 1).
(3) Directive (EU) 2016/1629 of the European Parliament and of the Council of 14 September 2016 laying down technical requirements for inland waterway vessels, amending Directive 2009/100/EC and repealing Directive 2006/87/EC (OJ L 252, 16.9.2016, p. 118).
(4) Commission Implementing Regulation (EU) 2018/2032 of 20 November 2018 amending Commission Regulation (EC) No 416/2007 of 22 March 2007 concerning the technical specifications for Notices to Skippers (OJ L 332, 28.12.2018, p. 1).
(5) Protect: an organisation of European seaports that have developed common implementation guidelines for electronic standard messages (www.protect-group.org).
ANNEX
TABLE OF CONTENTS
|
1. |
PART I: MESSAGE IMPLEMENTATION MANUAL CONVENTION | 3 |
|
1.1 |
Introduction | 3 |
|
1.2. |
UN/EDIFACT message structure | 4 |
|
1.3. |
Introduction to message types | 4 |
|
1.3.1. |
ERINOT | 4 |
|
1.3.2. |
PAXLST | 5 |
|
1.3.3. |
ERIRSP | 5 |
|
1.3.4. |
BERMAN | 5 |
|
2. |
PART II: CODES AND REFERENCES | 5 |
|
2.1. |
Introduction | 5 |
|
2.2. |
Definitions | 5 |
|
2.3. |
Classifications and code descriptions | 7 |
|
2.3.1. |
Vessel and Convoy Type (UN Recommendation 28) | 8 |
|
2.3.2. |
IMO ship identification number (IMO) | 9 |
|
2.3.3. |
ENI European navigation identification (unique European vessel number) | 10 |
|
2.3.4. |
Harmonised Commodity Description and Coding System (HS) including Combined Nomenclature | 12 |
|
2.3.5. |
Standard goods classification for transport statistics (NST) | 13 |
|
2.3.6. |
International maritime dangerous goods code (IMDG) | 14 |
|
2.3.7. |
Agreement on Dangerous Goods (ADN) | 15 |
|
2.3.8. |
UN country code | 17 |
|
2.3.9. |
UN location code (UN/LOCODE) | 19 |
|
2.3.10. |
Fairway section code | 20 |
|
2.3.11. |
Terminal code | 21 |
|
2.3.12. |
Container size and type code | 23 |
|
2.3.13. |
Container identification code | 24 |
|
2.3.14. |
Package type | 25 |
|
2.3.15. |
Handling instructions | 26 |
|
2.3.16. |
Purpose of call | 27 |
|
2.3.17. |
Nature of cargo | 29 |
|
2.4. |
Location codes | 30 |
|
2.5. |
List of abbreviations | 30 |
Appendices: Message Implementation Manuals
Appendix 1
| (Dangerous) goods reporting (IFTDGN) — ERINOT | 33 |
1. PART I: MESSAGE IMPLEMENTATION MANUAL CONVENTION
1.1 Introduction
These technical specifications define the structure of four messages for electronic ship reporting in inland navigation, based on the United Nations rules for Electronic Data Interchange for Administration, Commerce and Transport (UN/EDIFACT) (1) message structure and customised, where required, for the purpose of inland navigation.
In the case that electronic ship reporting in inland navigation is required by national or international law, these technical specifications shall be applied.
The exact use of the messages, data elements and codes are defined in the Appendices (Message Implementation Manuals) in order to ensure a common understanding and usage of the messages.
The messages are:
|
1. |
(Dangerous) goods reporting message (IFTDGN) — ERINOT |
|
2. |
Passenger and crew lists message (PAXLST) |
|
3. |
ERINOT response and receipt message (APERAK) — ERIRSP |
|
4. |
Berth management port notification message (BERMAN) |
For sharing of information the use of XML technology is another possibility apart from the UN/EDIFACT standards.
1.2. UN/EDIFACT message structure
The message structure is based on ISO 9735.
UN/EDIFACT messages are composed of segments. The structure of a message is described in a branching diagram indicating the position and the mutual relationship of the segments and segment groups.
For each segment data elements are defined: some data elements are combined to form composite data elements. A segment and a data element within a segment are either mandatory (M) or conditional (C). Mandatory segments and/or data elements contain important data for a receiving application and shall be filled with valid data.
Each message starts with two or three segments, the ‘interchange header’ (UNB) and the ‘message header’ (UNH). Where required, also the ‘service string advice’ (UNA) is used as a first segment to define which character sets are used in the message. Each message finishes with the segments ‘message trailer’ (UNT) and ‘interchange trailer’ (UNZ). Thus, each message is contained in one interchange, and an interchange contains only one single message.
1.3. Introduction to message types
As mentioned in section 1.1, the four message types are:
|
1. |
(Dangerous) goods reporting message (IFTDGN) — ERINOT |
|
2. |
Passenger and crew lists message (PAXLST) |
|
3. |
ERINOT response and receipt message (APERAK) — ERIRSP |
|
4. |
Berth management port notification message (BERMAN) |
In addition, messages can fulfill the following functions:
|
— |
new message (identifier ‘9’); |
|
— |
modification of message (identifier ‘5’); |
|
— |
cancellation of message (identifier ‘1’); |
|
— |
end of voyage (identifier ‘22’); |
|
— |
interruption of voyage (identifier ‘150’); |
|
— |
restart of voyage (identifier ‘151’). |
1.3.1. ERINOT
The ERI notification message (ERINOT) shall be used for the reporting of voyage related information and of information on dangerous and non-dangerous cargo carried on-board vessels sailing on inland waterways. The ERINOT message is a specific use of the UN/EDIFACT ‘International Forwarding and Transport Dangerous Goods Notification (IFTDGN)’ message. For the data and codes contained in the message applications based on these message specifications, use has been made of the UN Directory D98B.
The ERINOT message encompasses the following types:
|
— |
transport notification from vessel to authority (identifier ‘VES’), from ship to shore; |
|
— |
transport notification from carrier to authority (identifier ‘CAR’), from shore to shore; |
|
— |
passage notification (identifier ‘PAS’), from authority to authority. |
1.3.2. PAXLST
The PAXLST message is based on the UN/EDIFACT message PAXLST. It shall be used for the exchange of data in inland navigation between the captain/skipper or carrier and designated authorities such as customs, immigration, police or terminals falling under the International Ship and Port Facility Security (ISPS) Code, as defined in Regulation (EC) No 725/2004 of the European Parliament and of the Council (2).
The message shall be also used to transfer passenger/crew data from a designated authority in the country of departure to the appropriate authorities in the country of arrival of the means of transport.
1.3.3. ERIRSP
The ERI response message (ERIRSP) is derived from the UN/EDIFACT APERAK message. It may be generated by the system of the designated authority. The response to a ‘modification’ or a ‘cancellation’ contains information whether or not the ‘modification’ or ‘cancellation’ has been processed by the receiving system.
1.3.4. BERMAN
The Berth Management (BERMAN) message combines the pre-arrival notification, respectively general declaration, into one single notification which is based on the EDIFACT message BERMAN from the UN/EDIFACT D04B directory.
The BERMAN message shall be sent by vessels sailing on inland waterways before arriving at or departing from a berth or a port and provides information about the time of arrival and the services required to ensure a prompt handling, to support procedures and to facilitate controls.
2. PART II: CODES AND REFERENCES
2.1. Introduction
Codes and references, as defined in this Part, shall be used in electronic ship reporting for inland navigation. The use of codes and references serves the purpose of unambiguousness: it eliminates the possible misinterpretation and facilitates the translation of messages into other languages.
Therefore the usage of codes and references is mandatory for the data elements indicated in the message implementation manuals. Those codes and references are also available electronically in the European Reference Data Management System (ERDMS) operated by the Commission.
Those codes and references shall be used whenever data is interchanged between various computer applications and between parties using different languages, even beyond the message types in the subject of this Annex.
2.2. Definitions
For the purposes of this Annex, the following definitions shall apply.
Agent means any person mandated or authorised to act for or to supply information on behalf of the (transport) operator of the vessel.
Barge means a vessel that has no propulsion of its own.
Blue cones means signals that inland vessels carrying out transport operations involving dangerous substances are required to show pursuant to the European Agreement concerning the International Carriage of Dangerous Goods by Inland Waterways (ADN), namely one, two or three blue cones by day and one, two or three blue lights at night.
Carrier or transport operator means the person responsible for the carriage of goods, either directly or using a third party.
Cargo means any goods, wares, merchandise and articles carried on a ship. So ship carries cargo consisting of one or more consignments (with the necessary equipment) each consisting of one or more goods items.
Code means a character string used as an abbreviated means of (a) recording or identifying information (b) to represent or identify information using a specific symbolic form that can be recognised by a computer.
Common access reference means a common key to relate all subsequent transfers of data to the same business case or file (Data Element 0068 TDED). The common access reference shall be regarded as a common denominator (3) linking through a unique number documents, electronic messages and other communications with the same objective and characteristics.
A consignment means a separate identifiable number of goods transported from one consignor (port of loading) to one consignee (port of discharge) and identified and specified in one single transport document. A container as equipment shall in this context be seen as a separate identifiable packing unit for which separate bookings are done and as such shall be considered a single consignment.
Consignee means the party such as mentioned in the transport document by whom the goods, cargo or containers are to be received.
Consignor means the merchant by whom, in whose name or on whose behalf a contract of carriage of goods has been concluded with a carrier or any party by whom, in whose name or on whose behalf the goods are actually delivered to the consignee in relation to the contract of carriage (Synonyms: shipper, cargo sender).
Container means an item of equipment for transport purposes with the following characteristics:
|
1. |
a permanent character and accordingly strong enough to be suitable for repeated use; |
|
2. |
specially designed to facilitate the carriage of goods, by one or more modes and means of transport; |
|
3. |
fitted with devices permitting its ready handling, particularly from one mode of transport to another; |
|
4. |
so designed as to be easy to fill and to empty. |
The term container includes neither vehicles nor conventional packing.
Dangerous goods means the following categories, referred to in the relevant international instruments as defined in Directive 2002/59/EC of the European Parliament and of the Council (4):
|
— |
goods classified in the UNDG Code, |
|
— |
goods classified in the ADN Code, |
|
— |
goods classified in the IMDG Code, |
|
— |
dangerous liquid substances listed in the IBC Code, |
|
— |
liquefied gases listed in the IGC Code, |
|
— |
solids referred to in Appendix B of the BC Code. |
Data element means a unit of data which, in a certain context, is considered indivisible and for which the identification, description and value representation has been specified.
Deadweight tonnage (DWT) means the maximum displacement of a ship after deduction of the weight of the ship.
Displacement ton means a unit for measuring the displacement of ships equal to 35 ft3; this is approximately equal to the volume of a long ton (1 016,06 kg) of sea water.
EDI number means the electronic address of the sender or receiver of a message (e.g. the sender and receiver of the cargo). This may be an email address, an agreed identifier or e.g. a number of the European Article Numbering Association (EAN number).
Electronic data interchange (EDI) means the transfer of structured data by agreed standards from applications on the computer of one party to applications on the computer of another party by electronic means.
Goods means movable property, merchandise or wares.
Goods item means whole or part of the cargo (consignment) received from the shipper, including any packaging material such as pallets supplied by the shipper.
Gross tonnage (GRT) means the measure of the overall size of a vessel determined in accordance with the provisions of the international convention on measurement of vessels, usually expressed in register ton.
Gross weight means the weight (mass) of goods including packing, but excluding the carriers equipment expressed in whole kilograms.
Message implementation manual means a manual that describes in detail how a certain standard message will be implemented and which segments, data elements, codes and references will be used and how.
Location means any named geographical place, such as a port, an inland freight terminal, an airport, a container freight station, a terminal or any other place where customs clearance or regular receipt or delivery of goods can take place, with permanent facilities used for goods movements associated with international trade or transport and used frequently for those purposes. The location shall be recognised as such by a competent national body.
Means of transport means the type of vehicle used for the transport of goods such as barge, truck, vessel or train.
Metric ton means a unit of weight equivalent to 1 000 kg.
Mode of transport means a method of transport used for the conveyance of goods e.g. by rail, by road, by sea, by inland waterways.
Next port of call means the consecutive place (port of call) where a ship will arrive after having made a voyage. The term is used, by the master only, to indicate the subsequent competent authority in accordance with the applicable regulations.
Passage point means a defined distinguishable spot which serves as a marker to determine parts of a voyage of a vessel and triggering a certain action. It may take the form a virtual line perpendicular on the fairway axis running from side to side of the fairway.
Port of call means a place where a vessel actually drops anchor, moors or otherwise comes to rest for a certain period of time to execute any necessary operations related to ship, cargo or crew.
Qualifier means a data element whose value is expressed as a code that gives specific meaning to the function of another data element or a segment.
Reference number means a number that serves to refer to or mention a relation or where applicable a restriction.
Register ton means a unit of internal capacity of ships equal to 100 cubic feet (2,8317 m3).
Segment means a predefined and identified set of functionally related data elements values which are identified by their sequential positions within the set. A segment starts with a segment tag and ends with a segment terminator. It can be a service segment or a user data segment.
Segment code means a code which uniquely identifies each segment as specified in a segment directory.
Shipmaster means the person on-board of the ship being in command and having the authority to take all decisions pertaining to navigation and ship management. (Synonyms: captain, skipper, boat master).
Tag means a unique identifier for a segment or data element.
Transport notification means the announcement of an intended voyage of a ship to a competent authority.
UN/EDIFACT means the UN rules for Electronic Data Interchange for Administration, Commerce and Transport. They comprise a set of standards, directories and guidelines for the electronic interchange of structured data, and in particular that related to trade in goods or services between independent computerised information systems. Recommended within the framework of the UN, the rules are approved and published by the UNECE in the UN Trade Data Interchange Directory (UNTDID) and are maintained under agreed procedures.
Vessel traffic services (VTS) means services as defined in point 2.5 of the Annex to Commission Regulation (EC) No 414/2007 (5).
Voyage means the journey of a vessel between the port(s) of loading and the first port of discharge of a consignment.
2.3. Classifications and code descriptions
The following classifications shall be used in inland ship reporting:
|
1. |
Vessel and convoy type (UN Recommendation 28) |
|
2. |
IMO ship identification number (IMO) |
|
3. |
Unique European vessel identification number (ENI) |
|
4. |
Harmonised Commodity Description and Coding System (HS) including Combined Nomenclature |
|
5. |
Standard goods classification for transport statistics (NST) |
|
6. |
International maritime dangerous goods code (IMDG) |
|
7. |
European Agreement concerning the International Carriage of Dangerous Goods by Inland Waterways (ADN) |
|
8. |
UN country code |
|
9. |
UN location code (UN/LOCODE) |
|
10. |
Fairway section code |
|
11. |
Terminal code |
|
12. |
Container size and type code |
|
13. |
Container identification code |
|
14. |
Package type code |
|
15. |
Handling instructions |
|
16. |
Purpose of call |
|
17. |
Nature of cargo |
In the following, details and remarks on the application of those codes in inland navigation and user guidelines are given.
2.3.1. Vessel and convoy type (UN Recommendation 28)
|
FULL TITLE |
Codes for types of means of transport Annex 2, chapter 2.5: Inland water transport |
|
ABBREVIATION |
UN Recommendation 28 |
|
ORIGINATING AUTHORITY |
UNECE/CEFACT http://www.unece.org/cefact |
|
LEGAL BASIS |
UN Recommendation 28, ECE/Trade/276; 2001/23 |
|
CURRENT STATUS |
Operational |
|
IMPLEMENTATION DATE |
March 2001 |
|
AMENDMENT |
UN/CEFACT 2010 or most current one. |
|
STRUCTURE |
4-digit alphanumeric code: |
|
|
1 digit: ‘1’ for maritime navigation, ‘8’ for ‘inland navigation’ |
|
|
2 digits for vessel or convoy |
|
|
1 digit for subdivision |
|
SUCCINCT DESCRIPTION |
That recommendation establishes a common code list for the identification of the type of means of transport. It has a particular relevance to transport organisations and providers, customs and other authorities, statistical offices, forwarders, shippers, consignees and other parties concerned with transport. |
|
LINKED CLASSIFICATIONS |
UN Recommendation No 19 |
|
MEDIA THROUGH WHICH AVAILABLE |
http://www.unece.org/cefact/recommendations/rec_index.htm European Reference Data Management Service (ERDMS) operated by the European Commission (EC). |
|
LANGUAGES |
English |
|
ADDRESS OF RESPONSIBLE AGENCY |
UNECE |
|
REMARKS |
The main set of code values is governed by an international body (UNECE). To ensure harmonisation, one single set of code values representing also additional vessel types may be used by all RIS applications. |
|
Example |
|
|
8010 |
Motor freighter (Inland) |
|
1500 |
General cargo vessel (sea) |
|
Usage in the implementation manuals |
TDT/C228/8179 (convoy) |
|
|
EQD(B)/C224/8155 (vessel) |
2.3.2. IMO ship identification number (IMO)
|
FULL TITLE |
IMO ship identification number |
||||
|
ABBREVIATION |
IMO No |
||||
|
ORIGINATING AUTHORITY |
International Maritime Organisation/Lloyds |
||||
|
LEGAL BASIS |
IMO Resolution A.600(15), SOLAS chapter XI, regulation 3 |
||||
|
CURRENT STATUS |
Operational |
||||
|
IMPLEMENTATION DATE |
— |
||||
|
AMENDMENT |
Updated daily |
||||
|
STRUCTURE |
Lloyd’s Register of Shipping (LR) number (seven digits). |
||||
|
SUCCINCT DESCRIPTION |
The IMO Resolution aims at assigning a permanent number to each ship for identifying purposes. |
||||
|
LINKED CLASSIFICATIONS |
— |
||||
|
USAGE |
For seagoing ships |
||||
|
MEDIA THROUGH WHICH AVAILABLE |
www.ships-register.com |
||||
|
LANGUAGES |
English |
||||
|
ADDRESS OF RESPONSIBLE AGENCY |
|
|
Example |
|
|
Vessel dwt 2774 |
Danchem East 9031624 |
|
Usage in the implementation manuals. |
TDT/C222/8213 |
|
|
EQD(1)/C237/8260 |
|
|
SGP/C237/8260 |
2.3.3. Unique European vessel identification number (ENI)
|
FULL TITLE |
Unique European vessel identification number |
||||||
|
ABBREVIATION |
ENI |
||||||
|
ORIGINATING AUTHORITY |
European Union |
||||||
|
LEGAL BASIS |
Directive (EU) 2016/1629 of the European Parliament and of the Council (6) (Article 18, Article 2.18 of Annex V) |
||||||
|
CURRENT STATUS |
— |
||||||
|
IMPLEMENTATION DATE |
— |
||||||
|
LIMIT OF OPERATIONAL LIFE |
— |
||||||
|
AMENDMENT |
Continuously |
||||||
|
STRUCTURE |
8-digit-number |
||||||
|
SUCCINCT DESCRIPTION |
The unique European vessel identification number aims at assigning a permanent number to each vessel for identifying purposes. |
||||||
|
LINKED CLASSIFICATIONS |
IMO number |
||||||
|
USAGE |
In electronic ship reporting, tracking and tracing and certification of vessels for inland vessels. |
||||||
|
MEDIA THROUGH WHICH AVAILABLE |
|
||||||
|
LANGUAGES |
— |
||||||
|
ADDRESS OF RESPONSIBLE AGENCY |
European Union Member States and the Contracting Statesof the Mannheim Convention |
||||||
|
REMARK |
The unique European vessel identification number (ENI) consists of eight Arabic numerals. The first three digits are the code of the assigning competent authority. The next five digits are a serial number. |
|
Example |
|
|
12345678 |
|
|
Usage in the implementation manuals |
TDT, EQD (V1 and V2-V15) CNI/GID and CNI/GID/DGS, Tag 1311 |
2.3.4. Harmonised Commodity Description and Coding System (HS) including Combined Nomenclature
|
FULL TITLE |
Harmonised commodity description and coding system |
||||||
|
ABBREVIATION |
HS; Harmonised System |
||||||
|
ORIGINATING AUTHORITY |
World Customs Organisation |
||||||
|
LEGAL BASIS |
International Convention on the Harmonised Commodity Description and Coding System |
||||||
|
CURRENT STATUS |
Operational |
||||||
|
IMPLEMENTATION DATE |
1 January 2007 |
||||||
|
AMENDMENT |
In principle revised every five years. The latest version to be used. |
||||||
|
STRUCTURE |
7 466 headings, organised in four hierarchical levels |
||||||
|
|
Level 1: sections coded by Roman numerals (I to XXI) |
||||||
|
|
Level 2 chapters identified by two-digit numerical codes |
||||||
|
|
Level 3: headings identified by four-digit numerical codes |
||||||
|
|
Level 4: subheadings identified by six-digit numerical code |
||||||
|
SUCCINCT DESCRIPTION |
HS convention is a classification of goods by criteria based on raw material and the stage of production of commodities. HS is the heart of the whole process of harmonisation of international economic classifications being jointly conducted by the United Nations Statistics Division and Eurostat. Its items and sub-items are the fundamental terms on which industrial goods are identified in product classifications. Objectives: to harmonise (a) external trade classifications to guarantee direct correspondence; and (b) countries external trade statistics and to guarantee that those are comparable internationally. |
||||||
|
LINKED CLASSIFICATIONS |
Harmonised System (HS): full agreement on six-digit-level; Combined Nomenclature (CN) |
||||||
|
|
NST on 3-digit level |
||||||
|
USAGE |
Products |
||||||
|
MEDIA THROUGH WHICH AVAILABLE |
|
||||||
|
LANGUAGES |
All European Union official languages |
||||||
|
ADDRESS OF RESPONSIBLE AGENCY |
A subset of the codes used for electronic reporting will be maintained through the ERI Expert Group. European Reference Data Management Service (ERDMS) operated by the European Commission. |
||||||
|
REMARKS |
The HS classification is further subdivided at European Union level into a classification called Combined Nomenclature (CN) |
|
Example |
|
|
730110 |
Sheet piling of iron or steel |
|
310210 |
Mineral or chemical fertilisers, ammonium sulphate |
|
Usage in the implementation manuals |
CNI/GID/FTX(1)/C108/4440 CNI/GID/FTX(2)/C108/4440 |
2.3.5. Standard goods classification for transport statistics (NST)
|
FULL TITLE |
Nomenclature uniforme de marchandises pour les statistiques de transport/Standard goods classification for transport statistics/revised |
|||
|
ABBREVIATION |
NST 2007 |
|||
|
ORIGINATING AUTHORITY |
European Commission (Statistical Office/Eurostat) |
|||
|
LEGAL BASIS |
Commission Regulation (EC) No 1304/2007 (7) |
|||
|
CURRENT STATUS |
— |
|||
|
IMPLEMENTATION DATE |
1 January 2007 |
|||
|
AMENDMENT |
Regularly every two years. The latest version to be used |
|||
|
STRUCTURE |
2 digit NST 2007 Level 1: a 2-digit CPA subdivision |
|||
|
SUCCINCT DESCRIPTION |
Commodity Classification for Transport Statistics in Europe (CSTE) |
|||
|
LINKED CLASSIFICATIONS |
Harmonised commodity description and coding system (HS) Combined Nomenclature (CN) |
|||
|
USAGE |
Products |
|||
|
MEDIA THROUGH WHICH AVAILABLE |
http://ec.europa.eu/eurostat/ramon/nomenclatures/index.cfm?TargetUrl=LST_NOM_DTL&StrNom=NST_2007&StrLanguageCode=EN&IntPcKey=&StrLayoutCode=HIERARCHIC European Reference Data Management Service (ERDMS) operated by the European Commission. |
|||
|
LANGUAGES |
All European Union official languages |
|||
|
ADDRESS OF RESPONSIBLE AGENCY |
|
|||
|
REMARKS |
— |
2.3.6. International maritime dangerous goods code (IMDG)
|
FULL TITLE |
International maritime dangerous goods code |
||||
|
ABBREVIATION |
IMDG code |
||||
|
ORIGINATING AUTHORITY |
International Maritime Organisation IMO |
||||
|
LEGAL BASIS |
— |
||||
|
CURRENT STATUS |
Operational |
||||
|
IMPLEMENTATION DATE |
18 May 1965 |
||||
|
AMENDMENT |
1 January 2001 (30th amendment) approximately every 2 years |
||||
|
STRUCTURE |
2-digit numerical code: |
||||
|
1-digit numerical for class |
|||||
|
1-digit numerical for division |
|||||
|
SUCCINCT DESCRIPTION |
The IMDG code governs the vast majority of shipments of hazardous material by water. The code is recommended to governments for adoption as the basis for national regulations in conjunction with the SOLAS convention. |
||||
|
LINKED CLASSIFICATIONS |
The code is based on the UN Recommendations on the transport of dangerous goods (UNDG) |
||||
|
USAGE |
Maritime transport of dangerous and harmful goods |
||||
|
MEDIA THROUGH WHICH AVAILABLE |
www.imo.org European Reference Data Management Service (ERDMS) operated by the European Commission. (Included in the ADN table) |
||||
|
LANGUAGES |
Dutch, English, French, German |
||||
|
ADDRESS OF RESPONSIBLE AGENCY |
|
||||
|
REMARKS |
For inland shipping the IMO code may be used as this code is often already known, where necessary an ADN corresponding with the IMDG code shall be inserted |
|
Example |
|
|
32 |
Flammable liquid, not otherwise specified (Ethanol) |
|
Usage in the implementation manuals |
CNI/GID/DGS/C205/8351 |
2.3.7. Agreement on Dangerous Goods (ADN)
|
FULL TITLE |
European Agreement concerning the International Carriage of Dangerous Goods by Inland Waterways (ADN) |
||||||||||||
|
ABBREVIATION |
ADN |
||||||||||||
|
ORIGINATING AUTHORITY |
UN Economic Commission for Europe (English, French and Russian version of ADN) Central Commission for the Navigation of the Rhine (German version of ADN) |
||||||||||||
|
LEGAL BASIS |
Directive 2008/68/EC of the European Parliament and of the Council (8) |
||||||||||||
|
CURRENT STATUS |
Operational |
||||||||||||
|
IMPLEMENTATION DATE |
Operational |
||||||||||||
|
AMENDMENT |
Regularly every two years as indicated |
||||||||||||
|
STRUCTURE |
For goods on dry cargo vessel:
|
||||||||||||
|
|
For goods on tank vessels:
|
||||||||||||
|
SUCCINCT DESCRIPTION |
The ADN, the European Agreement concerning the International Carriage of Dangerous Goods by Inland Waterways which will replace the various regional agreements. |
||||||||||||
|
LINKED CLASSIFICATIONS |
ADN, ADR, RID |
||||||||||||
|
USAGE |
Transport of dangerous goods in inland navigation |
||||||||||||
|
MEDIA THROUGH WHICH AVAILABLE |
https://www.unece.org/trans/danger/publi/adn/adn_e.html www.ccr-zkr.org http://www.danubecommission.org/ European Reference Data Management Service (ERDMS) operated by the European Commission. |
||||||||||||
|
LANGUAGES |
English, French, German |
||||||||||||
|
ADDRESS OF RESPONSIBLE AGENCY |
|
||||||||||||
|
REMARKS |
The provisions of the European Agreement concerning the international carriage of dangerous goods by inland waterways (ADN) are applicable on all European waterways (including the Rhine and the Danube). The 2017 edition of ADR/RID/ADN is harmonised with the 20th revised edition of the UN Model Regulations and has entered into force on 1 January 2017. |
|
Example |
|
|
for dry cargo vessel: |
for tank vessel: |
|
1203; petrol; 3; F1; III; 3 |
1203; petrol; 3; III; |
|
Usage in the implementation manuals |
CNI/GID/DGS/C205/8078 |
2.3.8. UN country code
|
FULL TITLE |
International standard codes for the representation of the names of countries |
|
ABBREVIATION |
ISO 3166-1 |
|
ORIGINATING AUTHORITY |
International Organisation for Standardisation (ISO) |
|
LEGAL BASIS |
UN Recommendation 3 (codes for the representation of the names of countries) |
|
CURRENT STATUS |
Operational |
|
IMPLEMENTATION DATE |
1974 |
|
AMENDMENT |
As per ISO 3166-1 |
|
STRUCTURE |
Two-letter-alpha code (to be used in principle) |
|
Three-digit numeric code (alternatively) |
|
|
SUCCINCT DESCRIPTION |
ISO provides a unique two-letter code for each country listed, as well as a three-digit numeric code which is intended as an alternative for all applications that need to be independent of the alphabet. |
|
LINKED CLASSIFICATIONS |
UN/LOCODE |
|
USAGE |
This code is used as one element in the combined location code in chapter 2.4 of this Annex. |
|
MEDIA THROUGH WHICH AVAILABLE |
UNECE http://www.unece.org/cefact/locode/welcome.html European Reference Data Management Service (ERDMS) operated by the European Commission. |
|
LANGUAGES |
English |
|
ADDRESS OF RESPONSIBLE AGENCY |
http://www.unece.org/cefact |
|
REMARKS |
See chapter 2.4 of this Annex for the combination of the alpha country code with the location code. |
|
Example |
|
|
BE |
Belgium |
|
Usage in the implementation manuals |
ERINOT Message: |
|
|
TDT/C222/8453 |
|
|
NAD(1)/3207 |
|
|
NAD(2)/3207 |
|
|
ERIRSP Message |
|
|
NAD(1)/3207 |
2.3.9. UN location code (UN/LOCODE)
|
FULL TITLE |
UN code for trade and transport locations |
|
ABBREVIATION |
UN/LOCODE |
|
ORIGINATING AUTHORITY |
UNECE/CEFACT |
|
LEGAL BASIS |
UNECE Recommendation 16 |
|
CURRENT STATUS |
Operational |
|
IMPLEMENTATION DATE |
1980 |
|
AMENDMENT |
2018-2 (December 2018) |
|
STRUCTURE |
ISO 3166-1 country code (alpha 2-digit) followed by a space and a 3-digit-alpha code for the place names (5 digits) |
|
Place name (a..29) |
|
|
Subdivision ISO 3166-2, optional (a..3) |
|
|
Function, mandatory (an..5) |
|
|
Remarks, optional (an..45) |
|
|
Geographical coordinates (000N 0000 W, 000 S 00000 E) |
|
|
SUCCINCT DESCRIPTION |
UN recommends a five-letter alphabetic code for abbreviating the names of locations of interest to international trade, such as ports, airports, inland freight terminals, and other locations were customs clearance of goods can take place, and whose names need to be represented unambiguously in data interchange between participants in international trade. |
|
LINKED CLASSIFICATIONS |
UN country code |
|
USAGE |
This code is used as one element in the combined location code in chapter 2.4 of this Annex. |
|
MEDIA THROUGH WHICH AVAILABLE |
http://www.unece.org/cefact/locode/welcome.html European Reference Data Management Service (ERDMS) operated by the European Commission. |
|
LANGUAGES |
English |
|
ADDRESS OF RESPONSIBLE AGENCY |
UNECE |
|
REMARKS |
See also chapter 2.4 of this Annex. |
|
Example |
|
|
BEBRU |
Belgium Brussels |
|
Usage in the implementation manuals |
TDT/LOC (1..9)/C517/3225 |
|
|
CNI/LOC(1..2)/C517/3225 |
2.3.10. Fairway section code
|
FULL TITLE |
Fairway section code |
|
ABBREVIATION |
|
|
ORIGINATING AUTHORITY |
National administrations of waterways |
|
LEGAL BASIS |
— |
|
CURRENT STATUS |
operational |
|
IMPLEMENTATION DATE |
— |
|
AMENDMENT |
— |
|
STRUCTURE |
5-digit numerical code |
|
SUCCINCT DESCRIPTION |
The waterway network is divided into sections. These may be whole rivers and canals over several 100 km or small sections. The position of a location inside a section may be given by hectometre or by the name (code) of a terminal or passage point. |
|
LINKED CLASSIFICATIONS |
UN/LOCODE |
|
USAGE |
Numbering of the waterways in a national network. This code is used as one element in the combined location code in chapter 2.4 of this Annex. |
|
MEDIA THROUGH WHICH AVAILABLE |
European Reference Data Management Service (ERDMS) operated by the European Commission |
|
LANGUAGES |
— |
|
ADDRESS OF RESPONSIBLE AGENCY |
National administrations of waterways |
|
REMARKS |
See also Chapter 2.4 of this Annex. |
|
Example |
|
|
03937 |
Rhein, Rüdesheimer Fahrwasser |
|
02552 |
Oude Maas at Dordrecht |
|
Usage in the implementation manuals |
TDT/LOC/C517/3225 |
|
|
CNI/LOC/C517/3225 |
|
See: |
See this document and implementation manuals |
|
|
Definition of the revised location and terminal code |
|
Remark 1: |
If there is no fairway code available, the field shall be filled in with zeros. |
|
Remark 2: |
See also Chapter 2.4 of this Annex. |
2.3.11. Terminal code
|
FULL TITLE |
Terminal code |
|
ABBREVIATION FROM |
— |
|
ORIGINATING FROM |
National waterway authorities or user communities |
|
LEGAL BASIS |
— |
|
CURRENT STATUS |
Version 2, April 2000 |
|
IMPLEMENTATION DATE |
— |
|
AMENDMENT |
Regularly |
|
STRUCTURE |
Type of terminal (1-digit numeric) number of terminal (5-digit alphanumeric) |
|
SUCCINCT DESCRIPTION |
A further specification of the location of a terminal within the location of the port in the country. |
|
LINKED CLASSIFICATIONS |
UN/LOCODE |
|
USAGE |
This code is used as one element in the combined location code in chapter 2.4 of this Annex. |
|
MEDIA THROUGH WHICH AVAILABLE |
European Reference Data Management Service (ERDMS) operated by the European Commission. |
|
LANGUAGES |
— |
|
ADDRESS OF RESPONSIBLE AGENCY |
National administrations of waterways or respective user communities. |
|
REMARKS |
It is of the utmost importance that maintenance of the codes is done in such way that maximum stability and consistency is achieved to ensure that no changes are necessary apart from additions and deletions. See also chapter 2.4 of this Annex. |
|
Example |
|
|
LEUVE |
Leuvehaven at Rotterdam, NL |
|
Usage in the implementation guidelines |
TDT/LOC/C517/3225 |
|
|
CNI/LOC/C517/3225 |
|
See: |
Implementation manuals and this document |
|
|
Definition of the revised location and terminal code |
|
Remark 1: |
If there is no terminal code available, the field shall be filled in with zeros |
|
Remark 2: |
Each national RIS-authority will be responsible for its own data. |
2.3.12. Container size and type code
|
FULL TITLE |
Freight containers — coding, identification and marking |
|
ABBREVIATION |
— |
|
ORIGINATING AUTHORITY |
International Organisation for Standardisation (ISO) |
|
LEGAL BASIS |
ISO 6346, chapter 4 and annexes D and E |
|
CURRENT STATUS |
Operational |
|
IMPLEMENTATION DATE |
— |
|
AMENDMENT |
3rd edition 1 December 1995 |
|
STRUCTURE |
Container size: two alphanumeric characters(first for length, second for combination of height and width) |
|
|
Container type: two alphanumeric characters |
|
SUCCINCT DESCRIPTION |
Size and type codes established for each sort of containers |
|
LINKED CLASSIFICATIONS |
ISO 6346 coding identification and marking |
|
USAGE |
Whenever known and indicated in the commercial exchange of information |
|
MEDIA THROUGH WHICH AVAILABLE |
www.iso.ch/iso/en European Reference Data Management Service (ERDMS) operated by the European Commission. |
|
LANGUAGES |
English |
|
ADDRESS OF RESPONSIBLE AGENCY |
— |
|
REMARKS |
The size type codes are displayed on the containers and as such shall be used in the electronic reporting whenever available from other exchanged information e.g. during the booking. Size type codes shall be used as a whole i.e. the information shall not be broken into its component parts (ISO 6346:1995) |
|
Example |
|
|
42 |
Length: 40 ft.; height: 8 ft. 6 in.; width: 8 ft. |
|
Example for type |
|
|
GP |
General purpose container |
|
BU |
Dry bulk container |
|
Usage in the implementation manuals |
Where appropriate EQD segment |
2.3.13. Container identification code
|
FULL TITLE |
Freight containers — coding, identification and marking |
|
ABBREVIATION |
— |
|
ORIGINATING AUTHORITY |
International Organisation for Standardisation |
|
LEGAL BASIS |
ISO 6346, chapter 3, Annex A |
|
CURRENT STATUS |
Implemented throughout the world on all freight containers |
|
IMPLEMENTATION DATE |
1995 |
|
AMENDMENT |
— |
|
STRUCTURE |
Owner code: Three letters |
|
|
Equipment category identifier: one letter |
|
|
Serial number: six numerals |
|
|
Check digit: one numeral |
|
SUCCINCT DESCRIPTION |
The identification system is intended for general application, for example in documentation, control and communications (including automatic data processing systems), as well as for display on the containers themselves |
|
LINKED CLASSIFICATIONS |
ISO 668, ISO 1496, ISO 8323 |
|
USAGE |
— |
|
MEDIA THROUGH WHICH AVAILABLE |
www.iso.ch/iso/en |
|
LANGUAGES |
English |
|
ADDRESS OF RESPONSIBLE AGENCY |
Bureau International des Conteneurs (BIC), 167 rue de Courcelles, 75017 Paris, France, http://www.bic-code.org/ |
|
REMARKS |
— |
|
Example |
|
|
KNLU4713308 |
NEDLLOYD maritime freight container with serial number 471330, (8 is the check digit) |
|
Usage in the implementation manuals |
CNI/GID/DGS/SGP/C237/8260 |
2.3.14. Package type
|
FULL TITLE |
Codes for types of packages and packing materials |
|
ABBREVIATION |
UNECE Recommendation 21 |
|
ORIGINATING AUTHORITY |
UN/CEFACT |
|
LEGAL BASIS |
— |
|
CURRENT STATUS |
operational |
|
IMPLEMENTATION DATE |
August 1994 (ECE/TRADE/195) |
|
AMENDMENT |
Trade/CEFACT/2002/24 |
|
STRUCTURE |
2-character alphanumeric code value |
|
|
Code-value name |
|
|
2-digit numeric code value description |
|
SUCCINCT DESCRIPTION |
A numeric code system to describe the appearance of goods as presented for transport to facilitate identification, recording, handling, and establishing handling tariffs. |
|
LINKED CLASSIFICATIONS |
— |
|
USAGE |
— |
|
MEDIA THROUGH WHICH AVAILABLE |
www.unece.org/cefact European Reference Data Management Service (ERDMS) operated by the European Commission. |
|
LANGUAGES |
English, French, German |
|
ADDRESS OF RESPONSIBLE AGENCY |
— |
|
REMARKS |
The numeric code value is not used in this standard |
|
Example |
|
|
BG |
Bag |
|
BX |
Box |
|
Usage in the implementation manuals |
CNI/GID/C213/7065 |
2.3.15. Handling instructions
|
FULL TITLE |
Handling instruction description code |
|
ABBREVIATION |
UN/EDIFACT data element 4079 |
|
ORIGINATING AUTHORITY |
UN CEFACT |
|
LEGAL BASIS |
— |
|
CURRENT STATUS |
Operational |
|
IMPLEMENTATION DATE |
25 July 2005 |
|
AMENDMENT |
Trade/CEFACT/2005/ |
|
STRUCTURE |
Repr: an..3 |
|
|
Code-value name |
|
|
3-digit alpha code value description |
|
SUCCINCT DESCRIPTION |
An alpha code system to describe handling instructions for the tasks to be executed in a port to facilitate the handling of the vessel and establishing handling tariffs. |
|
LINKED CLASSIFICATIONS |
— |
|
USAGE |
un/edifact messages |
|
MEDIA THROUGH WHICH AVAILABLE |
www.unece.org/cefact |
|
LANGUAGES |
English |
|
ADDRESS OF RESPONSIBLE AGENCY |
— |
|
REMARKS |
The numeric code value is not used in this standard |
|
Example |
|
|
LOA |
Loading |
|
DIS |
Discharge |
|
RES |
Re-stow |
|
Usage in the implementation manuals |
LOC/HAN/C524/4079 |
2.3.16. Purpose of call
|
FULL TITLE |
Conveyance call purpose description code |
|
ABBREVIATION |
POC C525 |
|
ORIGINATING AUTHORITY |
UN CEFACT |
|
LEGAL BASIS |
— |
|
CURRENT STATUS |
Operational |
|
IMPLEMENTATION DATE |
25 July 2005 |
|
AMENDMENT |
Trade/CEFACT/2005 |
|
STRUCTURE |
Repr an..3 |
|
|
2-character numeric code value |
|
|
Code-value name |
|
SUCCINCT DESCRIPTION |
A numeric code system to describe the purpose of the call of the vessel to facilitate identification and recording |
|
LINKED CLASSIFICATIONS |
HAN |
|
USAGE |
edifact messages |
|
MEDIA THROUGH WHICH AVAILABLE |
www.unece.org/cefact |
|
LANGUAGES |
English |
|
ADDRESS OF RESPONSIBLE AGENCY |
— |
|
REMARKS |
The numeric code value is used in this standard |
|
Example |
|
|
1 |
Cargo operations |
|
23 |
Waste disposal |
|
Usage in the implementation manuals |
TSR/POC/C525/8025 |
2.3.17. Nature of cargo
|
FULL TITLE |
Cargo type classification code |
|
ABBREVIATION |
UN/EDIFACT 7085 cargo type |
|
ORIGINATING AUTHORITY |
UN CEFACT |
|
LEGAL BASIS |
— |
|
CURRENT STATUS |
Operational |
|
IMPLEMENTATION DATE |
25 July 2005 |
|
AMENDMENT |
Trade/CEFACT/2005 |
|
STRUCTURE |
an..3 |
|
|
2-character numeric code value |
|
|
Code-value name |
|
|
2-digit numeric code value description |
|
SUCCINCT DESCRIPTION |
A numeric code system to specify the classification of a type of cargo as transported to facilitate identification, recording, handling, and establishing tariffs. |
|
LINKED CLASSIFICATIONS |
HAN |
|
USAGE |
edifact messages |
|
MEDIA THROUGH WHICH AVAILABLE |
www.unece.org/cefact |
|
LANGUAGES |
English |
|
ADDRESS OF RESPONSIBLE AGENCY |
— |
|
REMARKS |
The numeric code value is used in these technical specifications |
|
Example |
|
|
5 |
Other non-containerised |
|
30 |
Cargo in bulk |
|
Usage in the implementation manuals |
TSR/LOC/HAN/C703/7085 |
2.4. Location codes
The ISRS Location Code is defined in Implementing Regulation (EU) 2018/2032.
2.5. List of abbreviations
|
Abbreviations |
Description |
|
ADN |
European Agreement concerning the International Carriage of Dangerous Goods by Inland Waterways (Directive 2008/68/EC of the European Parliament and of the Council of 24 September 2008 on the inland transport of dangerous goods) |
|
ADR |
European Agreement concerning the International Carriage of Dangerous Goods by Road (ADR) |
|
BERMAN |
Berth management (EDI message) |
|
CCNR |
Central Commission for the Navigation of the Rhine |
|
DWT |
Dead weight |
|
EDI |
Electronic data interchange |
|
ENI |
Unique European vessel identification number |
|
ERDMS |
European Reference Data Management Service |
|
ERI |
Electronic reporting international |
|
ERINOT |
ERI notification (message) |
|
ERIRSP |
ERI response (message) |
|
ETA |
Estimated time of arrival |
|
ETD |
Estimated time of departure |
|
HS Code |
Harmonised commodity description and coding system of WCO |
|
IFTDGN |
International forwarding and transport dangerous goods notification (message) |
|
IMDG |
International maritime dangerous goods code (number) |
|
IMO |
International Maritime Organisation |
|
IMO-FAL |
Convention on the Facilitation of International Maritime Traffic, 1965, with amendments |
|
ISO |
International Standardisation Organisation |
|
ISPS |
International ship and port facility security (code) |
|
LOCODE |
UNECE location code for ports and freight stations |
|
NST 2007 |
Standard goods classification for transport statistics (to be used from 2007 onwards) |
|
PAXLST |
Passenger list (message) |
|
PROTECT |
International Organisation of North Europeans Ports dealing with dangerous goods message implementation |
|
RID |
Regulations Concerning the International Carriage of Dangerous Goods by Rail (RID) |
|
RIS |
River information services |
|
SOLAS |
Safety of Lives at Sea IMO Convention |
|
TARIC |
Integrated Tariff of the European Communities |
|
UN/CEFACT |
UN Centre for Trade Facilitation and Electronic Business |
|
UNECE |
United Nations Economic Commission for Europe |
|
UN/EDIFACT |
Electronic data interchange for administration, commerce and transport |
|
UN/LOCODE |
United Nations location code |
|
UNDG |
United Nations dangerous goods (number) |
|
UNTDID |
United Nations trade data interchange directory |
|
URL |
Uniform resource allocator (Internet address) |
|
VTM |
Vessel traffic management |
|
WCO |
World Customs Organisation |
|
XML |
Extended markup language |
(1) Abbrevations used in this Annex are explained in the list in section 2.5.
(2) Regulation (EC) No 725/2004 of the European Parliament and of the Council of 31 March 2004 on enhancing ship and port facility security (OJ L 129, 29.4.2004, p. 6).
(3) The common denominator means an attribute that is common to all members of a category.
(4) Directive 2002/59/EC of the European Parliament and of the Council of 27 June 2002 establishing a Community vessel traffic monitoring and information system and repealing Council Directive 93/75/EEC (OJ L 208, 5.8.2002, p. 10).
(5) Commission Regulation (EC) No 414/2007 of 13 March 2007 concerning the technical guidelines for the planning, implementation and operational use of river information services (RIS) referred to in Article 5 of Directive 2005/44/EC of the European Parliament and of the Council on harmonised river information services (RIS) on inland waterways in the Community (OJ L 105, 23.4.2007, p. 1).
(6) Directive (EU) 2016/1629/EC of the European Parliament and of the Council of 14 September 2016 laying down technical requirements for inland waterway vessels, amending Directive 2009/100/EC and repealing Directive 2006/87/EC (OJ L 252, 16.9.2016, p. 118).
(7) Commission Regulation (EC) No 1304/2007 of 7 November 2007 amending Council Directive 95/64/EC, Council Regulation (EC) No 1172/98, Regulations (EC) No 91/2003 and (EC) No 1365/2006 of the European Parliament and of the Council with respect to the establishment of NST 2007 as the unique classification for transported goods in certain transport modes (OJ L 290, 8.11.2007, p. 14).
(8) Directive 2008/68/EC of the European Parliament and of the Council on the inland transport of dangerous goods (OJ L 260, 30.9.2008, p. 13).
Appendix 1
(Dangerous) Goods Reporting (IFTDGN) — ERINOT
1. ERI NOTIFICATION MESSAGE
The ERI notification message (ERINOT) is a specific use of the UN/EDIFACT ‘International Forwarding and Transport Dangerous Goods Notification (IFTDGN)’ message as it has been developed within the PROTECT organisation. The ERINOT message is based on EDIFACT directory 98.B and Protect version 1.0.
The segment table of ERINOT message is depicted in chapter 1.4. The branching diagram of the ERINOT message is depicted in chapter 1.5
To ensure the usage of the message also under special circumstances such as a convoy of ships, some extra qualifiers have been introduced for the RFF segments in the TDT group.
1.1 Field of application
The ERI notification message (ERINOT)shall be used by skippers and on behalf of skippers by transport operators and agents for the reporting of dangerous and non-dangerous cargo carried by inland waterway vessels.
The message supports the implementation — by means of EDI — of the following reporting needs:
|
— |
applicable police regulations either on Member States level or locally (eg. specific requirements in specific ports); |
|
— |
reporting requirements set by river commissions (eg. on the Rhine set by CCNR); |
|
— |
goods reporting for statistics purposes (Member States level or Eurostat). |
1.2 Principles
The ERINOT message is a specific standard implementation and use of the UN/EDIFACT ‘International Forwarding and Transport Dangerous Goods Notification (IFTDGN)’ message such as has been developed within the PROTECT seaports organisation.
This standard message implementation guideline has been accepted by the IMO for the reporting of dangerous goods to authorities. It has been designated as the message from the party responsible to report ‘dangerous’ goods to the authority performing the control and checks on conformance with the legal requirements. The message is conveying information on the ‘dangerous’ goods being loaded, discharged or in transit relating to a means of transport.
Where reporting is mandatory and if technically feasible, an ERI notification message is to be composed and sent to the competent authority for each inland waterway transport.
However all vessels are invited to report electronically to the competent authorities whenever possible. Where available, this may be done through a Single Window (1) to come to the envisioned reduction of procedures.
The notification message based on this standard message can be depicted as follows:
‘ERI (Electronic Reporting International) Notification Message’ with the following types:
|
— |
transport notification from vessel to authority from ship to shore; |
|
— |
transport notification from carrier to authority from shore to shore; |
|
— |
passage notification from authority to authority. |
1.3 Segment index (alphabetical sequence by tag)
|
BGM |
Beginning of message |
|
CNI |
Consignment information |
|
COM |
Communication contact |
|
CTA |
Contact information |
|
DGS |
Dangerous goods |
|
DTM |
Date/time/period |
|
EQD |
Equipment details |
|
FTX |
Free text |
|
GID |
Goods item details |
|
HAN |
Handling instructions |
|
LOC |
Place/location identification |
|
MEA |
Measurements |
|
NAD |
Name and address |
|
RFF |
Reference |
|
SGP |
Split goods placement |
|
TDT |
Details of transport |
|
UNH |
Message header |
|
UNT |
Message trailer |
1.4 Segment table
[S] Status, [R] Recurrence, [M] Mandatory, [C] Conditional, [D] Dependent on business rules
|
Pos |
Tag |
Name |
S |
R |
|
0010 |
UNH |
Message header |
M |
1 |
|
0020 |
BGM |
Beginning of message |
M |
1 |
|
0040 |
FTX |
Free text |
C |
3 |
|
0050 |
HAN |
Handling instructions |
D [1] |
1 |
|
|
|
|
|
|
|
0060 |
|
Segment Group 1 |
C |
3 |
|
0070 |
REF |
Reference |
M |
1 |
|
|
|
|
|
|
|
0090 |
|
Segment Group 2 |
M |
1 |
|
0100 |
TDT |
Details of transport |
M |
1 |
|
0110 |
RFF |
Reference |
M |
9 |
|
0120 |
LOC |
Place/location identification |
M |
9 |
|
0130 |
DTM |
Date/time/period |
M |
2 |
|
|
|
|
|
|
|
0140 |
|
Segment Group 3 |
M |
2 |
|
0150 |
NAD |
Name and address |
M |
1 |
|
|
|
|
|
|
|
0160 |
|
Segment Group 4 |
C |
1 |
|
0170 |
CTA |
Contact information |
M |
1 |
|
0180 |
COM |
Communication contact |
C |
4 |
|
|
|
|
|
|
|
0190 |
|
Segment Group 5 |
M |
99 |
|
0200 |
EQD |
Equipment details |
M |
1 |
|
0210 |
MEA |
Measurements |
M |
5 |
|
|
|
|
|
|
|
0220 |
|
Segment Group 6 |
M |
999 |
|
0230 |
CNI |
Consignment information |
M |
1 |
|
0240 |
HAN |
Handling instructions |
D [1] |
1 |
|
0250 |
DTM |
Date/time/period |
C |
2 |
|
0260 |
LOC |
Place/location identification |
C |
2 |
|
|
|
|
|
|
|
0300 |
|
Segment Group 8 |
C |
2 |
|
0310 |
NAD |
Name and address |
M |
1 |
|
|
|
|
|
|
|
0360 |
|
Segment Group 10 |
M |
99 |
|
0370 |
GID |
Goods item details |
M |
1 |
|
0380 |
FTX |
Free text |
C |
2 |
|
|
|
|
|
|
|
0400 |
|
Segment Group 11 |
C |
99 |
|
0410 |
SGP |
Split goods placement |
M |
1 |
|
0420 |
MEA |
Measurements |
M |
1 |
|
|
|
|
|
|
|
0430 |
|
Segment Group 12 |
M |
1 |
|
0440 |
DGS |
Dangerous goods |
M |
1 |
|
0450 |
FTX |
Free text |
D[5] |
7 |
|
4600 |
MEA |
Measurements |
M |
1 |
|
4700 |
LOC |
Place/location identification |
C |
0 |
|
0480 |
RFF |
Reference |
C |
0 |
|
|
|
|
|
|
|
0490 |
|
Segment Group 13 |
C |
99 |
|
0500 |
SGP |
Split goods placement |
M |
1 |
|
0510 |
LOC |
Place/location identification |
C |
1 |
|
0520 |
MEA |
Measurements |
D[6] |
2 |
|
0530 |
UNT |
Message trailer |
M |
1 |
|
Business rules |
|
|
D[1] |
The HAN-segment has to appear once, either in the vessel voyage details, on message level, or in the cargo details |
|
D[5] |
If mandatory by the applicable police regulations, this data shall be given in compliance with police regulations and then in accordance with the ADN |
|
D[6] |
The message shall contain at least one MEA-segment For the transport of liquid cargo the MEA with the measurement purpose qualifier ‘VOL’ shall be used For container transport the MEA with the measurement purpose qualifier ‘WT’ shall be used In case of a tank container both measurement purpose qualifiers are required |
|
D[USE 1] |
If the code is XXXXX, then this data-element shall be completed |
|
D[USE 2] |
If containers are carried, then this data shall be given |
|
D[USE 3] |
HS-code has preference |
|
D[USE 4] |
If the container type is known, then this data shall be given |
|
D[USE 5] |
If mandatory by the applicable police regulations, this data shall be given in compliance with police regulations and then in accordance with the ADN |
|
D[USE 6] |
The HAN-segment shall be present at least once |
|
D[USE 7] |
The transport equipment verified gross mass or estimated gross weight shall be given |
1.5. Branching diagram (ERI notification message)
2. ERINOT MESSAGE STRUCTURE
Table 1 defines the structure of the segments and the data elements of the ERI notification message.
Table 1: ERI notification message ERINOT
|
Segment Group |
Segment Composite data element (C) Data element TAG |
Level |
Status |
Format |
Name |
Description Qualifiers in quotation marks |
|
1 |
2 |
3 |
4 |
5 |
6 |
7 |
|
|
UNB |
0 |
M |
|
INTERCHANGE HEADER |
|
|
|
S001 |
|
M |
|
SYNTAX IDENTIFIER |
|
|
|
0001 |
|
M |
a4 |
Syntax identifier |
‘UNOA’ Controlling agency level A |
|
|
0002 |
|
M |
n1 |
Syntax version number |
‘2’ |
|
|
S002 |
|
M |
|
INTERCHANGE SENDER |
|
|
|
0004 |
|
M |
an..35 (an25) |
Sender identification |
Mailbox number or unique name or the unique identifier of a RIS-centre or traffic post |
|
|
0007 |
|
C |
an..4 |
Partner identification code qualifier |
n.a. |
|
|
0008 |
|
C |
an..14 |
Address for reverse routing |
n.a. |
|
|
S003 |
|
M |
|
INTERCHANGE RECIPIENT |
|
|
|
0010 |
|
M |
an..35 (an25) |
Recipient identification |
Mailbox number or unique name or the unique identifier of a RIS-centre or traffic post |
|
|
0007 |
|
C |
an..4 |
Partner identification code qualifier |
n.a. |
|
|
0014 |
|
C |
an..14 |
Routing address |
n.a. |
|
|
S004 |
|
M |
|
DATE/TIME OF PREPARATION |
|
|
|
0017 |
|
M |
n6 |
Date |
Generation date, YYMMDD |
|
|
0019 |
|
M |
n4 |
Time |
Generation time, HHMM |
|
|
0020 |
|
M |
an..14 |
Interchange control reference |
First 14 positions of the message reference number |
|
|
S005 |
|
|
|
RECIPIENTS REFERENCE, PASSWORD |
n.a |
|
|
0022 |
|
|
an..14 |
Recipient's reference/password |
n.a. |
|
|
0025 |
|
|
an2 |
Recipient's reference, password qualifier |
n.a. |
|
|
0026 |
|
|
an..14 |
Application reference |
n.a. |
|
|
0029 |
|
|
a1 |
Processing priority code |
n.a. |
|
|
0031 |
|
C |
n1 |
Acknowledgement request |
‘1’ = Sender requests acknowledgement, i.e. UNB and UNZ segments received and identified |
|
|
0032 |
|
|
an..35 |
Communications agreement id |
n.a. |
|
|
0035 |
|
C |
n1 |
Test indicator |
‘1’ = The interchange relates to a test message |
|
|
|
|
|
|
|
|
|
|
UNH |
0 |
M |
|
MESSAGE HEADER |
Identification, specification and heading of a message |
|
|
0062 |
|
M |
an..14 |
Message reference number |
First 14 positions of the message reference number |
|
|
S009 |
|
M |
|
MESSAGE IDENTIFIER |
|
|
|
0065 |
|
M |
an..6 |
Message type |
‘IFTDGN’, message type |
|
|
0052 |
|
M |
an..3 |
Message version number |
‘D’ |
|
|
0054 |
|
M |
an..3 |
Message release number |
‘98B’ |
|
|
0051 |
|
M |
an..2 |
Controlling agency |
‘UN’ |
|
|
0057 |
|
M |
an..6 |
Association assigned code |
‘ERI13’, ERI Version 1.3 |
|
|
0068 |
|
O |
an..35 |
Common access reference |
This unique reference code is meant to have a common denominator for all messages for the same voyage |
|
|
S010 |
|
|
|
STATUS OF THE TRANSFER |
n.a. |
|
|
0070 |
|
|
n..2 |
Sequence of transfers |
n.a. |
|
|
0073 |
|
|
a1 |
First and last transfer |
n.a. |
|
|
|
|
|
|
|
|
|
|
BGM |
0 |
M |
|
BEGINNING OF MESSAGE |
Identification of the type and function of the message |
|
|
C002 |
|
M |
|
DOCUMENT/MESSAGE NAME |
|
|
|
1001 |
|
M |
an..3 |
Document/message name code |
Type of message: ‘VES’, from vessel to RIS authority message ‘CAR’, from carrier to RIS authority message ‘PAS’, passage report from RIS authority to RIS authority (also see section 0) |
|
|
1131 |
|
|
an..3 |
Code list qualifier |
n.a. |
|
|
3055 |
|
|
an..3 |
Code list responsible agency |
n.a. |
|
|
1000 |
|
|
an..35 |
Document/message name |
n.a. |
|
|
C106 |
|
M |
|
DOCUMENT/MESSAGE IDENTIFICATION |
|
|
|
1004 |
|
M |
an..35 (an15) |
Document identifier |
Message reference number. This number shall be as unique as possible, both for sender and for receiver. If a message is received and then passed on to another receiver, the original message reference number shall be used. The transitional system shall in this case not generate another message reference number |
|
|
1056 |
|
|
an..9 |
Version |
n.a. |
|
|
1060 |
|
|
an..6 |
Revision number |
n.a. |
|
|
1225 |
|
M |
an..3 |
Message function code |
Function of message: ‘1’ = cancellation message ‘9’ = new message, (original) ‘5’ = modification message ‘22’ = Final transmission (End of voyage) ‘150’ = Interruption of voyage ‘151’ = Restart of voyage |
|
|
4343 |
|
C |
an..3 |
Response type code |
AQ |
|
|
|
|
|
|
|
|
|
|
FTX (1) |
0 |
C |
|
FREE TEXT |
To notify the number of persons on board and the number of blue cones |
|
|
4451 |
|
M |
an..3 |
Text subject code qualifier |
‘SAF’ for safety explanation |
|
|
4453 |
|
|
an..3 |
Free text function code |
n.a. |
|
|
C107 |
|
|
|
TEXT REFERENCE |
|
|
|
4441 |
|
|
an..17 |
Free text identification |
n.a. |
|
|
1131 |
|
|
an..3 |
Code list qualifier |
n.a. |
|
|
3055 |
|
|
an..3 |
Code list responsible agency |
n.a. |
|
|
C108 |
|
M |
|
TEXT LITERAL |
Text |
|
|
4440 |
|
M |
an..70 (n4) |
Free text |
Total number of persons on board (If the total number of persons is not known or indicated, this field shall be filled with ‘9999’) |
|
|
4440 |
|
C |
an..70 (an1) |
Free text |
‘0’, ‘1’, ‘2’, ‘3’ for number of cones (inland vessel) ‘B’ for red signal flag (maritime vessel) ‘V’ for special permit Note: Number of cones ‘0’ will indicate that this is the result of the system which calculated zero blue cones, if the field is left blank this will indicate that no data is available. |
|
|
4440 |
|
C |
an..70 (n4) |
Free text |
Number of passengers |
|
|
4440 |
|
|
an..70 |
Free text |
n.a. |
|
|
4440 |
|
|
an..70 |
Free text |
n.a. |
|
|
3453 |
|
|
an..3 |
Language, coded |
n.a. |
|
|
4447 |
|
|
an..3 |
Text formatting, coded |
n.a. |
|
|
|
|
|
|
|
|
|
|
FTX (2) |
0 |
C |
|
FREE TEXT |
To indicate whether the information in the message may be forwarded by the receiver to other authorities |
|
|
4451 |
|
M |
an..3 |
Text subject code qualifier |
‘ACK’ for ‘Privacy statement’ or ‘Confidential nature’ |
|
|
4453 |
|
|
an..3 |
Free text function code |
n.a. |
|
|
C107 |
|
|
|
TEXT REFERENCE |
|
|
|
4441 |
|
|
an..17 |
Free text identification |
n.a. |
|
|
1131 |
|
|
an..3 |
Code list qualifier |
n.a. |
|
|
3055 |
|
|
an..3 |
Code list responsible agency |
n.a. |
|
|
C108 |
|
M |
|
TEXT LITERAL |
|
|
|
4440 |
|
M |
an..70 (a1) |
Free text |
‘Y’ = Yes, ‘N’ = No |
|
|
4440 |
|
|
an..70 |
Free text |
n.a. |
|
|
4440 |
|
|
an..70 |
Free text |
n.a. |
|
|
4440 |
|
|
an..70 |
Free text |
n.a. |
|
|
4440 |
|
|
an..70 |
Free text |
n.a. |
|
|
3453 |
|
|
an..3 |
Language, coded |
n.a. |
|
|
4447 |
|
|
an..3 |
Text formatting, coded |
n.a. |
|
|
|
|
|
|
|
|
|
|
FTX(3) |
0 |
C |
|
FREE TEXT |
Reason for cancellation |
|
|
4451 |
|
M |
an..3 |
Text subject code qualifier |
‘ACD’ cancellation reason |
|
|
4453 |
|
|
an..3 |
Free text function code |
n.a. |
|
|
C107 |
|
M |
|
TEXT REFERENCE |
Text identification |
|
|
4441 |
|
M |
an..17 |
Free text identification |
‘CAM’ mistake in notification ‘CAO’ transport does not take place ‘CAV’ the main transport destination has changed ‘CHD’ the time of arrival has changed |
|
|
1131 |
|
|
an..3 |
Code list qualifier |
n.a. |
|
|
3055 |
|
|
an..3 |
Code list responsible agency |
n.a. |
|
|
C108 |
|
M |
|
|
Text |
|
|
4440 |
|
M |
an..70 |
Free text |
Free description of the reason |
|
|
4440 |
|
C |
an..70 |
Free text |
Free text for further explanation |
|
|
4440 |
|
C |
an..70 |
Free text |
Free text for further explanation |
|
|
4440 |
|
C |
an..70 |
Free text |
Free text for further explanation |
|
|
4440 |
|
C |
an..70 |
Free text |
Free text for further explanation |
|
|
3453 |
|
|
an..3 |
Language, coded |
n.a. |
|
|
4447 |
|
|
an..3 |
Text formatting, coded |
n.a. |
|
|
|
|
|
|
|
|
|
|
HAN(1) |
0 |
D[6] |
|
|
|
|
|
C524 |
|
M |
|
HANDLING INSTRUCTIONS |
|
|
|
4079 |
|
M |
an..3 |
Handling instructions, coded |
Default ‘T’ T = Transit LLO = Loading LDI = Unloading TSP = Transit in the same port |
|
|
1131 |
|
|
|
Code list qualifier |
n.a. |
|
|
3055 |
|
|
|
Code list responsible agency, coded |
n.a. |
|
|
4078 |
|
|
|
Handling instructions |
n.a. |
|
|
C218 |
|
|
|
HAZARDOUS MATERIAL |
n.a. |
|
|
7419 |
|
|
|
Hazardous material class code, identification |
n.a. |
|
|
1131 |
|
|
|
Code list qualifier |
n.a. |
|
|
3055 |
|
|
|
Code list responsible agency, coded |
n.a. |
|
|
7418 |
|
|
|
Hazardous material class |
n.a. |
|
|
|
|
|
|
|
|
|
GRP 1 |
RFF (1) |
1 |
C |
|
REFERENCE |
Reference to the message for which the current message is a replacement. Mandatory if the message is a modification or a cancellation message |
|
|
C506 |
|
M |
|
REFERENCE |
|
|
|
1153 |
|
M |
an..3 |
Reference qualifier |
‘ACW’ for reference number to previous message |
|
|
1154 |
|
M |
an..35 (an15) |
Reference number |
Message reference number from BGM, TAG 1004 of the message this message replaces |
|
|
1156 |
|
|
an..6 |
Line number |
n.a. |
|
|
4000 |
|
|
an..35 |
Reference version number |
n.a. |
|
|
1060 |
|
|
an..6 |
Revision number |
n.a. |
|
|
|
|
|
|
|
|
|
GRP 1 |
RFF (2) |
1 |
C |
|
REFERENCE |
Reference to transport document |
|
|
C506 |
|
M |
|
REFERENCE |
|
|
|
1153 |
|
M |
an..3 |
Reference qualifier |
‘FF’ for ‘freight forwarder's reference number’ |
|
|
1154 |
|
M |
an..35 |
Reference number |
Reference number of the transport document |
|
|
1156 |
|
|
an..6 |
Line number |
n.a. |
|
|
4000 |
|
|
an..35 |
Reference version number |
n.a. |
|
|
1060 |
|
|
an..6 |
Revision number |
n.a. |
|
|
|
|
|
|
|
|
|
GRP 1 |
RFF (3) |
1 |
C |
|
REFERENCE |
Reference to a test scenario |
|
|
C506 |
|
M |
|
REFERENCE |
|
|
|
1153 |
|
M |
an..3 |
Reference qualifier |
‘ADD’ for test number |
|
|
1154 |
|
M |
an..35 |
Reference number |
Test scenario identification, which shall be known at the receiving party |
|
|
1156 |
|
|
an..6 |
Line number |
n.a. |
|
|
4000 |
|
|
an..35 |
Reference version number |
n.a. |
|
|
1060 |
|
|
an..6 |
Revision number |
n.a. |
|
|
|
|
|
|
|
|
|
GRP 2 |
TDT |
1 |
M |
|
DETAILS OF TRANSPORT |
Specification of the means of transport, the naming vessel within a convoy (a single vessel without barge is also a convoy in this context) |
|
|
8051 |
|
M |
an..3 |
Transport stage code qualifier |
‘20’ for main carriage transport |
|
|
8028 |
|
C |
an..17 |
Conveyance reference number |
Voyage number, defined by sender of the message |
|
|
C220 |
|
M |
|
MODE OF TRANSPORT |
|
|
|
8067 |
|
M |
an..3 |
Mode of transport, coded |
‘8’ for Inland water transport, ‘1’ for maritime transport (see UNECE Rec. 19) |
|
|
8066 |
|
|
an..17 |
Mode of transport |
n.a. |
|
|
C228 |
|
M |
|
TRANSPORT MEANS |
|
|
|
8179 |
|
M |
an..8 (an4) |
Type of means of transport identification, convoy type |
Code for ship and convoy types of means of transport from UN/CEFACT Rec. 28, see Annex Part II, Chapter 2.3.1 |
|
|
8178 |
|
|
an..17 |
Type of means of transport |
n.a. |
|
|
C040 |
|
|
|
CARRIER |
n.a. |
|
|
3127 |
|
|
an..17 |
Carrier identification |
n.a. |
|
|
1131 |
|
|
an..3 |
Code list qualifier |
n.a. |
|
|
3055 |
|
|
an..3 |
Code list responsible agency |
n.a. |
|
|
3128 |
|
|
an..35 |
Carrier name |
n.a. |
|
|
8101 |
|
|
an..3 |
Transit direction, coded |
n.a. |
|
|
C401 |
|
|
|
EXCESS TRANSPORTATION INFORMATION |
|
|
|
8457 |
|
|
an..3 |
Excess transportation reason |
n.a. |
|
|
8459 |
|
|
an..3 |
Excess transportation responsibility |
n.a. |
|
|
7130 |
|
|
an..17 |
Customer authorisation number |
n.a. |
|
|
C222 |
|
M |
|
TRANSPORT IDENTIFICATION |
|
|
|
8213 |
|
M |
an..9 (an7..8) |
ID. of means of transport identification |
Vessel number: 7 digits for IMO indication or unique European vessel identification number (ENI) |
|
|
1131 |
|
M |
an..3 |
Code list qualifier |
‘IMO’ for an IMO-number, see Annex Part II, Chapter 2.3.2 ‘ENI’ for a unique European vessel identification number, see Annex Part II, Chapter 2.3.3 |
|
|
3055 |
|
|
an..3 |
Code list responsible agency |
n.a. |
|
|
8212 |
|
M |
an..35 |
Id. of the means of transport |
Name of the ship; If the name results in more than 35 positions, the name of the vessel is shortened |
|
|
8453 |
|
M |
an..3 |
Nationality of means of transport |
ISO two-alpha country code 3166-1, see Annex Part II, Chapter 2.3.8. If the nationality of the means of transport is not known, the 3-digit code of the competent authority which issued the European vessel identification number shall be used. |
|
|
8281 |
|
|
an..3 |
Transport ownership |
n.a. |
|
|
|
|
|
|
|
|
|
TDT |
RFF (1) |
1 |
M |
|
REFERENCE |
Dimensions of the transport, length |
|
|
C506 |
|
M |
|
REFERENCE |
|
|
|
1153 |
|
M |
an..3 |
Reference qualifier |
‘LEN’ = Length |
|
|
1154 |
|
M |
an..35 (n..5) |
Reference number |
Total length of the convoy in centimetres |
|
|
1156 |
|
|
an..6 |
Line number |
n.a. |
|
|
4000 |
|
|
an..35 |
Reference version number |
n.a. |
|
|
1060 |
|
|
an..6 |
Revision number |
n.a. |
|
|
|
|
|
|
|
|
|
TDT |
RFF (2) |
1 |
M |
|
REFERENCE |
Dimensions of the transport, width |
|
|
C506 |
|
M |
|
REFERENCE |
|
|
|
1153 |
|
M |
an..3 |
Reference qualifier |
‘WID’ |
|
|
1154 |
|
M |
an..35 (n..4) |
Reference number |
Total width of the convoy in centimetres |
|
|
1156 |
|
|
an..6 |
Line number |
n.a. |
|
|
4000 |
|
|
an..35 |
Reference version number |
n.a. |
|
|
1060 |
|
|
an..6 |
Revision number |
n.a. |
|
|
|
|
|
|
|
|
|
TDT |
RFF (3) |
1 |
M |
|
REFERENCE |
Dimensions of the transport, draught |
|
|
C506 |
|
M |
|
REFERENCE |
|
|
|
1153 |
|
M |
an..3 |
Reference qualifier |
‘DRA’ |
|
|
1154 |
|
M |
an..35 (n..4) |
Reference number |
Draught of the convoy in centimetres (If due to legal restriction this data cannot be submitted, the value of this field shall be ‘9999’) |
|
|
1156 |
|
|
an..6 |
Line number |
n.a. |
|
|
4000 |
|
|
an..35 |
Reference version number |
n.a. |
|
|
1060 |
|
|
an..6 |
Revision number |
n.a. |
|
|
|
|
|
|
|
|
|
TDT |
RFF (4) |
1 |
C |
|
REFERENCE |
Dimensions of the transport, height |
|
|
C506 |
|
M |
|
REFERENCE |
|
|
|
1153 |
|
M |
an..3 |
Reference qualifier |
‘HGT’ |
|
|
1154 |
|
M |
an..35 (n..4) |
Reference number |
Height of the convoy above the waterline in centimetres |
|
|
1156 |
|
|
an..6 |
Line number |
n.a. |
|
|
4000 |
|
|
an..35 |
Reference version number |
n.a. |
|
|
1060 |
|
|
an..6 |
Revision number |
n.a. |
|
|
|
|
|
|
|
|
|
TDT |
RFF (5) |
1 |
M |
|
REFERENCE |
Dimensions of the transport, tonnage |
|
|
C506 |
|
M |
|
REFERENCE |
Reference |
|
|
1153 |
|
M |
an..3 |
Reference qualifier |
‘TON’ |
|
|
1154 |
|
M |
an..35 (n..6) |
Reference number |
Maximum capacity of the convoy in metric tonnes |
|
|
1156 |
|
|
an..6 |
Line number |
n.a. |
|
|
4000 |
|
|
an..35 |
Reference version number |
n.a. |
|
|
1060 |
|
|
an..6 |
Revision number |
n.a. |
|
|
|
|
|
|
|
|
|
TDT |
RFF (6) |
1 |
C |
|
REFERENCE |
National voyage reference, Belgium, France, Germany |
|
|
C506 |
|
M |
|
REFERENCE |
Reference |
|
|
1153 |
|
M |
an..3 |
Reference qualifier |
‘GNB’ = Belgium ‘GNF’= France ‘GNG’ = Germany ‘GN1’ = reserved |
|
|
1154 |
|
M |
an..35 |
Reference number |
Government reference of Belgium |
|
|
1156 |
|
|
an..6 |
Line number |
n.a. |
|
|
4000 |
|
|
an..35 |
Reference version number |
n.a. |
|
|
1060 |
|
|
an..6 |
Revision number |
n.a. |
|
|
|
|
|
|
|
|
|
TDT |
RFF (7) |
1 |
C |
|
REFERENCE |
LNG installation indicator |
|
|
C506 |
|
M |
|
REFERENCE |
Reference |
|
|
1153 |
|
M |
an..3 |
Reference qualifier |
‘LNG’ |
|
|
1154 |
|
M |
an..35 (an1) |
Reference number |
‘Y’ = Yes |
|
|
1156 |
|
|
an..6 |
Line number |
n.a. |
|
|
4000 |
|
|
an..35 |
Reference version number |
n.a. |
|
|
1060 |
|
|
an..6 |
Revision number |
n.a. |
|
|
|
|
|
|
|
|
|
TDT |
LOC (1) |
1 |
M |
|
PLACE/LOCATION IDENTIFICATION |
Port of departure, the port where the transport starts |
|
|
3227 |
|
M |
an..3 |
Place/location qualifier |
‘5’ place of departure |
|
|
C517 |
|
M |
|
LOCATION IDENTIFICATION |
|
|
|
3225 |
|
M |
an..25 (an5) |
Place/location identification |
UNECE location code (Rec. 16), see Annex Part II, Chapter 2.3.9 |
|
|
1131 |
|
|
an..3 |
Code list qualifier |
n.a. |
|
|
3055 |
|
|
an..3 |
Code list responsible agency |
n.a. |
|
|
3224 |
|
C |
an..70 (an..17) |
Place/location |
Full name of the port location |
|
|
C519 |
|
C |
|
RELATED LOCATION ONE IDENTIFICATION |
|
|
|
3223 |
|
M |
an..25 (an..5) |
Related place/location one identification |
Terminal code, see Annex Part II, Chapter 2.3.11 |
|
|
1131 |
|
|
an..3 |
Code list qualifier |
n.a. |
|
|
3055 |
|
|
an..3 |
Code list responsible agency |
n.a. |
|
|
3222 |
|
D [Use 1] |
an..70 |
Related place/location one |
Full name of the terminal. |
|
|
C553 |
|
C |
|
RELATED LOCATION TWO IDENTIFICATION |
|
|
|
3233 |
|
M |
an..25 (an5) |
Related place/location two identification |
Fairway section code, see Annex Part II, Chapter 2.3.10 |
|
|
1131 |
|
|
an..3 |
Code list qualifier |
n.a. |
|
|
3055 |
|
|
an..3 |
Code list responsible agency |
n.a. |
|
|
3232 |
|
C |
an..70 (an..5) |
Related place/location two |
Fairway section hectometre |
|
|
5479 |
|
|
an..3 |
Relation |
n.a. |
|
|
|
|
|
|
|
|
|
TDT |
LOC (2) |
1 |
C |
|
PLACE/LOCATION IDENTIFICATION |
Passage point that has already been passed by the ship. This segment and the TDT/DTM(2) segment with qualifier 186 are mandatory for passage reports. |
|
|
3227 |
|
M |
an..3 |
Place/location qualifier |
‘172’ for passage point |
|
|
C517 |
|
M |
|
LOCATION IDENTIFICATION |
|
|
|
3225 |
|
M |
an..25 (an5) |
Place/location identification |
UNECE location code (Rec. 16) of the passage point (lock, bridge, traffic centre), see Annex Part II, Chapter 2.3.9 |
|
|
1131 |
|
|
an..3 |
Code list qualifier |
n.a. |
|
|
3055 |
|
|
an..3 |
Code list responsible agency |
n.a. |
|
|
3224 |
|
C |
an..70 (an..17) |
Place/location |
Full name of the passage point |
|
|
C519 |
|
C |
|
RELATED LOCATION ONE IDENTIFICATION |
|
|
|
3223 |
|
M |
an..25 (an..5) |
Related place/location one identification |
Passage point code |
|
|
1131 |
|
|
an..3 |
Code list qualifier |
n.a. |
|
|
3055 |
|
|
an..3 |
Code list responsible agency |
n.a. |
|
|
3222 |
|
|
an..70 |
Related place/location one |
n.a. |
|
|
C553 |
|
C |
|
RELATED LOCATION TWO IDENTIFICATION |
|
|
|
3233 |
|
M |
an..25 (an5) |
Related place/location two identification |
Fairway section code, see Annex Part II, Chapter 2.3.10 |
|
|
1131 |
|
|
an..3 |
Code list qualifier |
n.a. |
|
|
3055 |
|
|
an..3 |
Code list responsible agency |
n.a. |
|
|
3232 |
|
C |
an..70 (an..5) |
Related place/location two |
Fairway section hectometre |
|
|
5479 |
|
|
an..3 |
Relation |
n.a. |
|
|
|
|
|
|
|
|
|
TDT |
LOC (3) |
1 |
C |
|
PLACE/LOCATION IDENTIFICATION |
Next passage point |
|
|
3227 |
|
M |
an..3 |
Place/location qualifier |
‘61’ for next port of call |
|
|
C517 |
|
M |
|
LOCATION IDENTIFICATION |
|
|
|
3225 |
|
M |
an..25 (an5) |
Place/location identification |
UNECE location code (Rec. 16) of the passage point (lock, bridge, VTS centre), see Annex Part II, Chapter 2.3.9 |
|
|
1131 |
|
|
an..3 |
Code list qualifier |
n.a. |
|
|
3055 |
|
|
an..3 |
Code list responsible agency |
n.a. |
|
|
3224 |
|
C |
an..70 (an..17) |
Place/location |
Full name of the passage point |
|
|
C519 |
|
C |
|
RELATED LOCATION ONE IDENTIFICATION |
|
|
|
3223 |
|
M |
an..25 |
Related place/location one identification |
Passage point code |
|
|
1131 |
|
|
an..3 |
Code list qualifier |
n.a. |
|
|
3055 |
|
|
an..3 |
Code list responsible agency |
n.a. |
|
|
3222 |
|
|
an..70 |
Related place/location one |
n.a. |
|
|
C553 |
|
C |
|
RELATED LOCATION TWO IDENTIFICATION |
|
|
|
3233 |
|
M |
an..25 (an5) |
Related place/location two identification |
Fairway section code, see Annex Part II, Chapter 2.3.10 |
|
|
1131 |
|
|
an..3 |
Code list qualifier |
n.a. |
|
|
3055 |
|
|
an..3 |
Code list responsible agency |
n.a. |
|
|
3232 |
|
C |
an..70 (an..5) |
Related place/location two |
Fairway section hectometre |
|
|
5479 |
|
|
an..3 |
Relation |
n.a. |
|
|
|
|
|
|
|
|
|
TDT |
LOC (4..8) |
1 |
C |
|
PLACE/LOCATION IDENTIFICATION |
Further future passage points (information on intended route). At most five intermediate points on the route may be given. The order of passage shall be the order within the message. |
|
|
3227 |
|
M |
an..3 |
Place/location qualifier |
‘92’ for routing |
|
|
C517 |
|
M |
|
LOCATION IDENTIFICATION |
|
|
|
3225 |
|
M |
an..25 (an5) |
Place/location identification |
UNECE location code (Rec. 16) of the passage point (lock, bridge, traffic centre), see Annex Part II, Chapter 2.3.9 |
|
|
1131 |
|
|
an..3 |
Code list qualifier |
n.a. |
|
|
3055 |
|
|
an..3 |
Code list responsible agency |
n.a. |
|
|
3224 |
|
C |
an..17 |
Place/location |
Full name of the passage point |
|
|
C519 |
|
C |
|
RELATED LOCATION ONE IDENTIFICATION |
|
|
|
3223 |
|
M |
an..25 (an..5) |
Related place/location one identification |
Passage point code |
|
|
1131 |
|
|
an..3 |
Code list qualifier |
n.a. |
|
|
3055 |
|
|
an..3 |
Code list responsible agency |
n.a. |
|
|
3222 |
|
C |
an..70 |
Passage datetime |
YYMMDDHHMM as ‘201’ of DTM 2379 |
|
|
C553 |
|
C |
|
RELATED LOCATION TWO IDENTIFICATION |
|
|
|
3233 |
|
M |
an..25 (an5) |
Related place/location two identification |
Fairway section code, see Annex Part II, Chapter 2.3.10 |
|
|
1131 |
|
|
an..3 |
Code list qualifier |
n.a. |
|
|
3055 |
|
|
an..3 |
Code list responsible agency |
n.a. |
|
|
3232 |
|
C |
an..70 (an..5) |
Related place/location two |
Fairway section hectometre |
|
|
5479 |
|
|
an..3 |
Relation |
n.a. |
|
|
|
|
|
|
|
|
|
TDT |
LOC (9) |
1 |
M |
|
PLACE/LOCATION IDENTIFICATION |
Port of destination. This is the first port where the transport is bound. |
|
|
3227 |
|
M |
an..3 |
Place/location qualifier |
‘153’ for place of call |
|
|
C517 |
|
M |
|
LOCATION IDENTIFICATION |
|
|
|
3225 |
|
M |
an..25 (an5) |
Place/location identification |
UNECE location code (Rec. 16) of the port, see Annex Part II, Chapter 2.3.9 |
|
|
1131 |
|
|
an..3 |
Code list qualifier |
n.a. |
|
|
3055 |
|
|
an 3 |
Code list responsible agency |
n.a. |
|
|
3224 |
|
C |
an..70 (an..17) |
Place/location |
Full name of the port location |
|
|
C519 |
|
C |
|
RELATED LOCATION ONE IDENTIFICATION |
|
|
|
3223 |
|
M |
an..25 (an..5) |
Related place/location one identification |
Terminal code, see Annex Part II, Chapter 2.3.11 |
|
|
1131 |
|
|
an..3 |
Code list qualifier |
n.a. |
|
|
3055 |
|
|
an..3 |
Code list responsible agency |
n.a. |
|
|
3222 |
|
D [Use 1] |
an..70 |
Related place/location one |
Full name of the terminal |
|
|
C553 |
|
C |
|
RELATED LOCATION TWO IDENTIFICATION |
|
|
|
3233 |
|
M |
an..25 (an5) |
Related place/location two identification |
Fairway section code, see Annex Part II, Chapter 2.3.10 |
|
|
1131 |
|
|
an..3 |
Code list qualifier |
n.a. |
|
|
3055 |
|
|
an..3 |
Code list responsible agency |
n.a. |
|
|
3232 |
|
C |
an..70 (an..5) |
Related place/location two |
Fairway section hectometre |
|
|
5479 |
|
|
an..3 |
Relation |
n.a. |
|
|
|
|
|
|
|
|
|
TDT/LOC(1) |
DTM (1) |
2 |
C |
|
DATE/TIME/PERIOD |
Departure time (estimated) |
|
|
C507 |
|
M |
|
DATE/TIME/PERIOD |
|
|
|
2005 |
|
M |
an..3 |
Date or time or period function code qualifier |
‘133’ for departure date/time, estimated |
|
|
2380 |
|
M |
an..35 |
Date or time period value |
Value of departure time |
|
|
2379 |
|
M |
an..3 |
Date or time or period format code |
‘201’ for YYMMDDHHMM |
|
|
|
|
|
|
|
|
|
TDT/LOC(2) |
DTM (2) |
2 |
C |
|
DATE/TIME/PERIOD |
Passage time, as recorded by the traffic centre |
|
|
C507 |
|
M |
|
DATE/TIME/PERIOD |
|
|
|
2005 |
|
M |
an..3 |
Date or time or period function code qualifier |
‘186’ for departure time, actual |
|
|
2380 |
|
M |
an..35 |
Date or time period value |
Value of passage time: YYMMDDHHMM |
|
|
2379 |
|
M |
an..3 |
Date or time or period format code |
‘201’ for YYMMDDHHMM |
|
|
|
|
|
|
|
|
|
TDT/LOC(9) |
DTM (3) |
2 |
C |
|
DATE/TIME/PERIOD |
Estimated time of arrival at port of destination |
|
|
C507 |
|
M |
|
DATE/TIME/PERIOD |
|
|
|
2005 |
|
M |
an..3 |
Date or time or period function code qualifier |
‘132’ for arrival time, estimated |
|
|
2380 |
|
M |
an..35 |
Date or time period value |
Value of arrival time: YYMMDDHHMM |
|
|
2379 |
|
M |
an..3 |
Date or time or period format code |
‘201’ for YYMMDDHHMM |
|
|
|
|
|
|
|
|
|
GRP 3 |
NAD (1) |
1 |
M |
|
NAME and ADDRESS |
name and address of message sender |
|
|
3035 |
|
M |
an..3 |
Party function code qualifier |
‘MS’ for message sender |
|
|
C082 |
|
C |
|
PARTY IDENTIFICATION DETAILS |
|
|
|
3039 |
|
M |
an..35 |
Party identification |
Identification code. For notifications to the Port of Rotterdam this element is mandatory. ERI fills this element with ‘900000000’. |
|
|
1131 |
|
|
an..3 |
Code list qualifier |
n.a. |
|
|
3055 |
|
|
an..3 |
Code list responsible agency |
n.a. |
|
|
C058 |
|
|
|
NAME AND ADDRESS |
n.a. |
|
|
3124 |
|
|
an..35 |
Name and address line |
n.a. |
|
|
3124 |
|
|
an..35 |
Name and address line |
n.a. |
|
|
3124 |
|
|
an..35 |
Name and address line |
n.a. |
|
|
3124 |
|
|
an..35 |
Name and address line |
n.a. |
|
|
3124 |
|
|
an..35 |
Name and address line |
n.a. |
|
|
C080 |
|
M |
|
PARTY NAME |
|
|
|
3036 |
|
M |
an..35 |
Party name |
Sender name |
|
|
3036 |
|
|
an..35 |
Party name |
n.a. |
|
|
3036 |
|