EUR-Lex Access to European Union law
This document is an excerpt from the EUR-Lex website
Document 32010R0164
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
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
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–154
(BG, ES, CS, DA, DE, ET, EL, EN, FR, IT, LV, LT, HU, MT, NL, PL, PT, RO, SK, SL, FI, SV)
No longer in force, Date of end of validity: 24/04/2022; Arna aisghairm le 32019R1744
|
6.3.2010 |
EN |
Official Journal of the European Union |
L 57/1 |
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
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 Article 5, paragraph 1, point (b), thereof,
Whereas:
|
(1) |
RIS should be developed and implemented in a harmonised, interoperable and open way. |
|
(2) |
The technical specifications for electronic ship reporting in inland navigation should be defined. |
|
(3) |
The technical specifications for electronic ship reporting should be based on the technical principles set out in Annex II to the Directive. |
|
(4) |
The technical specifications should take due account of the work carried out by relevant international organisations. Continuity shall be ensured with other modal traffic management services, in particular maritime vessel traffic management and information services. |
|
(5) |
They should also take due account of the work carried out by the expert group on electronic ship reporting which is composed of representatives of the authorities of the Member States responsible for the implementation of electronic ship reporting, and official members from other governmental bodies as well as observers from the industry. |
|
(6) |
The technical specifications should correspond to the current state of the art. Experiences gained from the application of Directive 2005/44/EC as well as future technical progress may make it necessary to amend the technical specifications. Amendments to the technical specifications should take due account of the work carried out by the expert group on electronic ship reporting. |
|
(7) |
The measures provided for in this Regulation are in accordance with the opinion of the Committee established pursuant to Article 7 of Council Directive 91/672/EEC of 16 December 1991 on the reciprocal recognition of national boatmasters’ certificates for the carriage of goods and passengers by inland waterways (2), |
HAS ADOPTED THIS REGULATION:
Article1
The technical specifications for electronic ship reporting in inland navigation are defined in the Annex.
Article 2
This Regulation shall enter into force on the day following its publication in the Official Journal of the European Union.
This Regulation shall be binding in its entirety and directly applicable in all Member States.
Done at Brussels, 25 January 2010.
For the Commission
The President
José Manuel BARROSO
(1) OJ L 255, 30.9.2005, p. 152.
(2) OJ L 373, 31.12.1991, p. 29.
ANNEX
TABLE OF CONTENTS
|
1. |
Part I: Message implementation manual convention |
|
1.1. |
Introduction |
|
1.2. |
UN/EDIFACT message structure |
|
1.2.1. |
Description of the segments and data elements |
|
1.2.2. |
Syntax |
|
1.2.2.1. |
Character sets |
|
1.2.2.2. |
Interchange structures |
|
1.2.2.3. |
Interchange |
|
1.2.2.4. |
Order of segments and groups of segments within a message |
|
1.2.2.5. |
Segment structure |
|
1.2.2.6. |
Data element structure |
|
1.2.2.7. |
Compressing |
|
1.2.2.8. |
Representation of numeric data element values |
|
1.3. |
Messages |
|
1.3.1. |
ERINOT |
|
1.3.2. |
PAXLST |
|
1.3.3. |
ERIRSP |
|
1.3.4. |
BERMAN |
|
1.4. |
Amendment procedures |
|
2. |
Part II: Codes and references |
|
2.1. |
Introduction |
|
2.2. |
Clarifications |
|
2.2.1. |
Terminology |
|
2.2.2. |
WCO and the HS |
|
2.3. |
Definitions |
|
2.4. |
Classifications and code descriptions |
|
2.4.1. |
Updating of codes and reference tables |
|
2.4.2. |
Descriptions of the code tables |
|
2.4.2.1. |
Vessel and convoy type |
|
2.4.2.2. |
Official ship number (OFS) |
|
2.4.2.3. |
IMO ship identification number |
|
2.4.2.4. |
Electronic reporting number (for ship identification) ERN |
|
2.4.2.5. |
Unique European vessel identification number |
|
2.4.2.6. |
Harmonised system code (HS) |
|
2.4.2.7. |
Combined Nomenclature (CN) |
|
2.4.2.8. |
Standard goods classification for transport statistics/revised (NST) 2000 |
|
2.4.2.9. |
UN dangerous goods number (UNDG) |
|
2.4.2.10. |
International maritime dangerous goods code (IMDG) |
|
2.4.2.11. |
ADN/R/D |
|
2.4.2.12. |
UN country code |
|
2.4.2.13. |
UN location code — UN/LOCODE |
|
2.4.2.14. |
Fairway section code |
|
2.4.2.15. |
Terminal code |
|
2.4.2.16. |
Freight container size and type code |
|
2.4.2.17. |
Container identification code |
|
2.4.2.18. |
Package type |
|
2.4.2.19. |
Handling instructions |
|
2.4.2.20. |
Purpose of call |
|
2.4.2.21. |
Nature of cargo |
|
2.5. |
Unique European vessel identification number |
|
2.6. |
Definition of the ERI vessel types |
|
2.7. |
Location codes |
|
2.7.1. |
Data elements |
|
2.7.2. |
Example |
Abbreviations
|
Appendices |
Message implementation manuals |
|
Appendix 1 |
(Dangerous) goods reporting (IFTDGN) — ERINOT |
|
Appendix 2 |
Passenger and crew list (PAXLST) |
|
Appendix 3 |
ERINOT response and receipt message (APERAK) — ERIRSP |
|
Appendix 4 |
Berth management port notification (BERMAN) |
1. PART I: MESSAGE IMPLEMENTATION MANUAL CONVENTION
1.1. Introduction
The technical specifications define the structure of four messages for electronic ship reporting in inland navigation, based on the UN/EDIFACT message structure (see also chapter 1.2) 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 messages are:
|
1. |
(Dangerous) goods reporting (IFTDGN) — ERINOT |
|
2. |
Passenger and crew lists (PAXLST) |
|
3. |
ERINOT response and receipt message (APERAK) — ERIRSP |
|
4. |
Berth management port notification (BERMAN) |
In the Appendices (message implementation manuals) the exact use of the messages, data elements and codes is defined in order to ensure a common understanding and usage of the messages.
The use of XML technology is another possibility. The standardisation of XML message definition for the purpose of electronic ship reporting in inland navigation is dealt with by the relevant working group supporting the Committee established pursuant to Article 7 of Council Directive 91/672/EEC of 16 December 1991 on the reciprocal recognition of national boatmasters’ certificates for the carriage of goods and passenger.
1.2. UN/EDIFACT message structure
The following elaborations are 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 the data elements are defined which are to be used in a message. Some data elements are combined to form composite data elements. The messages follow a fixed syntax as defined in ISO 9735.
A segment and a data element within a segment are either mandatory or conditional. Mandatory segments and/or data elements contain important data for a receiving application and shall be filled with sensible, in other words valid data. Conditional elements need not to be present in a message.
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.2.1. Description of the segments and data elements
In the message descriptions the following indicators are used:
Column 1 contains the name in form of the acronym (TAG) of the , represented by the hierarchy of segment names on higher levels. This indication is derived from the branching diagram.
Column 2 contains the name in form of the acronym (TAG) of the , the number of the and the number of the .
Column 3 indicates the on which the segment is situated in the branching diagram.
Column 4 indicates whether the segment or data element is (M) or (C).
Column 5 defines the of the data element.
Column 6 gives the UN/EDIFACT of the data element. The names of segments are written in bold upper cases, the names of composite data elements are written in normal upper cases and the names of data elements are written in normal lower cases.
Column 7 gives a of the data elements (fields). If a fixed value is to be used, the value is indicated in quotes.
1.2.2. Syntax
The full description of the data elements in the service segments is part of ISO 7372 Trade Data Elements Directory.
1.2.2.1. Character sets
For the characters in the sets below, the 7-bit codes in the basic code table in ISO 646 shall be used, unless the corresponding 8-bit codes in ISO 6937 and ISO 8859 or other bit codes are specifically agreed between the interchanging partners through the usage of the UNA segment.
Level A character set:
|
Description |
Code |
Remarks |
|
Letters |
upper case A to Z |
|
|
Numerals |
0 to 9 |
|
|
Space character |
|
|
|
Full stop |
. |
|
|
Comma |
, |
|
|
Hyphen/minus sign |
— |
|
|
Opening parenthesis |
( |
|
|
Closing parenthesis |
) |
|
|
Oblique stroke (slash) |
/ |
|
|
Equals sign |
= |
|
|
Apostrophe |
' |
Reserved for use as segment terminator |
|
Plus sign |
+ |
Reserved for use as segment tag and data element separator |
|
Colon |
: |
Reserved for use as component data element separator |
|
Question mark |
? |
Reserved for use as release character? immediately preceding one of the characters ' + : ? restores their normal meaning. For example, 10? + 10 = 20 means 10 + 10 = 20. Question mark is represented by ??. |
The following characters are also part of the level A character set.
|
Description |
Code |
|
Exclamation mark |
! |
|
Quotation mark |
" |
|
Percentage sign |
% |
|
Ampersand |
& |
|
Asterisk |
* |
|
Semi-colon |
; |
|
Less-than sign |
< |
|
Greater-than sign |
> |
1.2.2.2. Interchange structures
The service string advice, UNA, and the service segments UNB to UNZ shall appear in the order stated in an interchange. See chapter 1.2.2.3.
There may be several functional groups within an interchange.
A message consists of segments. The structures for segments and for data elements therein are shown in chapter 1.2.2.5.
1.2.2.3. Interchange
An interchanges consists of:
Service String Advice UNA Conditional
– – – – – – – – – – Interchange Header UNB Mandatory
| – – – – – – Message Header UNH Mandatory
| | User Data Segments described in the Annex implementation manual
| – – – – – – Message Trailer UNT Mandatory
– – – – – – – – – – Interchange Trailer UNZ Mandatory
1.2.2.4. Order of segments and groups of segments within a message
Message structure diagrams and the order of the segments following the processing rules can be found in the Appendices.
1.2.2.5. Segment structure
Segment Tag: Mandatory
Segment Code: Mandatory component data element
Component D.E. separator: Conditional
Nesting and repeating indication: Conditional component data element(s)
Data element separator: Mandatory
Simple or composite data elements: Mandatory or Conditional as specified in the relevant segments directory and implementation manual
Segment Terminator: Mandatory
1.2.2.6. Data element structure
Simple Data Element:
Mandatory or Conditional as specified in the relevant implementation guideline.
Composite Data Element:
In accordance with segments directory and as specified in the implementation manual.
Component data elements and Component data element separators:
Mandatory (see restriction below)
Data element separator: Mandatory (see restriction below)
Restriction:
There shall be no component data element separator after the last component data element in a composite data element and no data element separator after the last data element in a segment.
1.2.2.7. Compressing
In data elements for which the Data Elements Directory specifies variable length and in the case that there are no other restrictions, insignificant character positions shall be suppressed. In the case of insignificant characters, leading zeroes and trailing spaces shall be suppressed.
However, a single zero before a decimal sign is significant and a zero may be significant (e.g. to indicate a temperature) if so stated in the data elements specification of the implementation manuals.
When compressing messages, the following rules shall be followed.
(a) Exclusion of segments
Conditional segments containing no data shall be omitted (including their segment tags).
(b) Exclusion of data elements by omission
Data elements are identified by their sequential positions within the segment as stated in the Segment Directory. If a conditional data element is omitted and if it is followed by another data element, its position shall be indicated by retention of its data element separator.
Tag+DE+DE+++DE+DE+DE’
|_|_______________ These two data elements are omitted
(c) Exclusion of data elements by truncation
If one or more conditional data elements at the end of a segment are omitted, the segment may be truncated by the segment terminator, i.e. contiguous trailing data element separators are not required to be transmitted.
Tag+DE+DE+++DE' Using the example from 2.2.7 b, the last two data elements have been omitted and by '|____ the segment has been truncated.
(d) Exclusion of component data elements by omission
Component data elements are identified by their given sequential positions within a composite data element. If a conditional component data element is omitted and is followed by another component data element, its given position shall be represented by its component data element separator.
Tag+DE+CE:CE+CE:::CE'
|_|_____ Two component data elements omitted in the last composite data element.
(e) Exclusion of component data elements by truncation
One or more conditional component data elements at the end of a composite data element may be excluded by truncation by the data element separator or, if at the end of a segment, by the segment terminator.
Tag+DE+CE+CE' The last component data element in the first composite data element |___|___ has been omitted and also three component data elements in the last composite data element. In both cases the composite data elements have been truncated, indicated in the first case by the data element separator and in the second case by the segment terminator.
1.2.2.8. Representation of numeric data element values
(a) Decimal sign
The ISO representation for a decimal sign is the comma (,) but a point on the line (.) is allowed (see ISO 31-0: 1981). Both these characters are part of the Level A and B sets. When the service string advice, UNA, is used, its third character specifies the character used in the interchange. It is however strongly recommended to use as a default the (,) to represent a decimal sign under all circumstances. The decimal sign shall not be counted as a character of the value when computing the maximum field length of a data element. However, allowance shall be made for the character in transmission and reception. When a decimal sign is transmitted, there shall be at least one digit before and after the decimal sign. For values represented by integers only, neither a decimal sign nor decimal zeroes are used unless there is a need to indicate the degree of precision.
Preferred: 0,5 and 2 and 2,0 Not allowed: ,5 or .5 or 2, or 2.
(b) Triad separator
Triad separators shall not be used in interchange.
Allowed: 2500000 Not allowed: 2,500,000 or 2.500.000 or 2 500 000
(c) Sign
Numeric data element values shall be regarded as positive. Although conceptually a deduction is negative, it shall be represented by a positive value and such cases shall be indicated in the data elements directory. lf a value is to be indicated as negative, it shall in transmission be immediately preceded by a minus sign, e.g. -112. The minus sign shall not be counted as a character of the value when computing the maximum field length of a data element. However, allowance shall be made for the character in transmission and reception.
Legend:
Ref.
The numeric reference tag for the data element as stated in ISO 7372 UNTDED and, when preceded by S, reference for a composite data element used in service segments.
Name
|
|
Name of COMPOSITE DATA ELEMENT in capital letters |
|
|
Name of DATA ELEMENT in capital letters |
|
|
Name of Component data element in small letters |
Repr.
|
|
Data value representation: |
|
|
a — alphabetic characters |
|
|
n — numeric characters |
|
|
an — alphanumeric characters |
|
|
a3 — 3 alphabetic characters, fixed length |
|
|
n3 — 3 numeric characters, fixed length |
|
|
an3 — 3 alphanumeric characters, fixed length |
|
|
a..3 — up to 3 alphabetic characters |
|
|
n..3 — up to 3 numeric characters |
|
|
an..3 — up to 3 alphanumeric characters |
|
|
M — Mandatory element |
|
|
C — Conditional element. |
When the composite data element is used, a mandatory component data element in a conditional composite data element shall appear.
If in the message implementation manuals a smaller number is used than the ISO standard requires, then this shall be indicated within brackets. The remaining space in a data element shall be filled with space characters.
The usage indicators in the message implementation manuals are as follows:
|
UNSM Usage |
Usage |
Indicator in this message implementation manual |
|
Mandatory (M) |
Mandatory (M) |
mandatory (M) |
|
Conditional (C) |
Required (R) |
always required (M) |
|
Conditional (C) |
Advised (A) |
usage of e.g. a certain code set is strongly advised |
|
Conditional (C) |
Dependent (D) |
usage of the entity depends upon well defined conditions |
|
Conditional (C) |
Optional (O) |
usage is at the need or discretion of the sender of the message |
|
Conditional (C) |
Not Used (X) |
not to be used (n. a.) |
In the implementation manuals of the messages the usage indicators are used explicitly to ensure a uniform use within electronic ship reporting in inland navigation. Throughout the document reference is made to indicators (M, R, A, D, O and X) which are shown adjacent to data items and which dictate for the message the agreed usage of the entities.
In the following table the indicators and their respective uses are set out:
|
Status (S) Value |
Description |
Remark |
|
M |
Mandatory |
Indicates that this item is mandatory in the standard message. |
|
R |
Required |
Indicates that this entity shall be sent in this message implementation and use is here mandatory. |
|
A |
Advised |
Indicates that a recognised international code-set i.e. UN, ISO or ERI code set is highly recommended for use in this implementation over any local codes. |
|
D |
Dependent |
Indicates that the use of the entity depends upon a well-defined condition or set of conditions. These conditions shall be clearly specified in the relevant implementation guideline. |
|
O |
Optional |
Indicates that this entity is at the need or discretion of the sender of the message. |
|
X |
|
Not to be used in this message implementation (n. a.). |
1.3. Messages
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 as it has been developed within the PROTECT (1) organisation. The ERINOT message is based on the EDIFACT directory 98.B and the PROTECT implementation version 1.0.
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. |
The following message functions show what sort of message can be expected:
|
— |
new message (identifier ‘9’); |
|
— |
modification of message (identifier ‘5’); |
|
— |
cancellation of message (identifier ‘1’). |
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 ISPS terminals, customs, immigration, police.
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 for instance a RIS centre. The response messages with respect to the different functions (new, modification or cancellation) of the ERINOT message have all the same structure. 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 implementation manual is based on the guidelines as defined by the PROTECT group.
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.
The message incorporates the legal requirements regarding the notification of a ship to a port. It supports one request for the ship — be it for entering the port, berthing on arrival of the ship, leaving the berth on departure of the ship or shifting of berths for the ship within the port or for transiting only through the port area. The arrival and transit notification contains all details regarding the movement of the ship from outside the port area to the first berth in the port area or in case of transit to the point where the vessel is leaving.
Required additional services to be arranged for arrival at a berth can be specified. The estimated time of arrival (ETA) at the entry point and where required leaving point and previous place of call of the ship are required information elements.
1.4. Amendment procedures
Proposals for amendments to the message implementation manuals shall be sent together with an explanation, why the amendment is needed to the chairperson of the Electronic Reporting expert group.
The chairperson shall distribute the proposal to the members of the expert group as well as to the European Commission.
As regards the expert group, the relevant procedures as defined in the Terms of Reference for the Electronic Reporting expert group shall apply.
The European Commission will proceed with any amendment in accordance with the procedures established in the RIS Directive. In this context, due account shall be taken of the work of the expert group.
2. PART II: CODES AND REFERENCES
2.1. Introduction
In Part II the various codes and references which shall be used in electronic ship reporting for inland navigation are defined. The usage of codes and reference numbers does serve the purpose of unambiguousness. The use of codes and references will lead to less misinterpretations and easy translation into any language. Therefore the usage of codes and references is mandatory for those codes indicated in the messages and included here and strongly recommended whenever other data has to be interchanged between various computer applications and between parties using different languages provided that the relevant data element allows an existing and published code value. In the following, the definitions and descriptions of the used codes and references are described, for the actual code tables a reference will be made towards the relevant chapters of this Annex or where available an URL (Internet address) will be given.
2.2. Clarifications
2.2.1. Terminology
The following clarifications serve to ensure that the meaning of the used information elements in electronic ship reporting is clear and unambiguous and that through clear descriptions the maintenance of data and references is facilitated and ensured.
1. Data Dictionary
A data dictionary is in essence a centralised storage of information on data such as the meaning, the links with other data, the source, the usage, and the classification. The dictionary is used for the efficient planning, management and evaluation of the collection, recording and usage of data. The data dictionary or lexicon is primary and originally a book containing words arranged in alphabetical order with definitions, etymologies and other information.
2. Data Element Directory
A data element directory is in essence a book with directions listing names and particulars of a specific group of information elements. In information technology it is also a table with identification symbols and pointers to the matching data. The TDED (Trade Data Elements Directory) ISO 7372 has an adopted agreed set of standard data elements for various areas of application. It contains a number, a data element name, a description of the concept to explain the agreed meaning in order to determine the content of the information (data value) to be provided with the data element. A specification of the character representation of the data value, with indication of space (number of characters) is provided, together with the synonyms of data element names where appropriate and used.
3. Data repository
A data repository is in essence a place where things are stored, e.g. a warehouse. Quite often the term data warehouse is used to indicate the place of storage of common data. The data repository is used in the development of XML and ebXML to indicate the place of storage of the so called core components. The first catalogues of core components are available as draft proposals for standards, see also www.unece.org/cefact/. Under ebXML a repository item is associated with a set of standard metadata defined as attributes of the registry object class. These attributes reside outside of the actual repository and provide descriptive information about the repository item.
4. Glossary
A list and explanation of e.g. difficult technical terms, it is often described as a partial dictionary. The terms are often alphabetically listed to be used for reference in projects, books or studies.
5. Vocabulary
A list of words and often phrases, abbreviations etc. usually arranged in alphabetical order and defined or otherwise identified as in a dictionary or glossary.
2.2.2. WCO and the H.S.
The World Customs Organisation (WCO) has developed a number of standards and guidelines pertaining to the interchange of data in the area of goods and cargo declarations.
The WCO maintains the Harmonised System (HS) which provides a 6-digit classification system for goods and commodities, the HS is used for classifying goods covering over 5 000 descriptions of the products or groups of products most commonly produced and traded. The structure of this numeric system is such that it provides a legal and logical structure, which puts group's products or categories of products into headings, chapters and into sections.
It can be used by customs but is meant also for statistics, manufacturers, transport, import and export.
The structure is as follows:
|
XX |
Heading |
|
XXXX |
Harmonised System |
|
XXXX.XX |
HS Code |
For additional local use the code can be expanded as follows:
|
XXXX.XX.XX |
Code for Combined Nomenclature |
|
XXXX.XX.XX.XX |
Statistics number |
|
XXXX.XXXX.XXX |
TARIC code |
Moreover there are further local subdivisions of up to 21 positions to indicate e.g. the national tax code.
The Kyoto Convention of the WCO describes in detail the procedures and processes and the information elements for transit and import/export declarations.
2.3. Definitions
The following definitions (2) are used for the purpose of these technical specifications.
A traffic organisation service is a service to prevent the development of dangerous vessel traffic situations by managing traffic movements and to provide for the safe and efficient movement of vessel traffic within the VTS area.
Agent means any person mandated or authorised to act for or to supply information on behalf of the operator of the vessel.
Asynchronous message means a message that can be delivered by the sender without explicitly having to wait for the processing of the message by the receiver. The receiver decides when to process the message.
Barge means a vessel that has no propulsion of its own.
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. [ISO TC154/SC1]
Competent authority means the authorities and organisations authorised by the governments to receive and pass on information reported pursuant to this standard.
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, Sender).
Dangerous goods means (3) :
|
— |
goods classified in the UNDG Code, |
|
— |
goods classified in the ADN/ADNR 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.
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 E-mail 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.
Forwarder means the party arranging the carriage of goods including connecting services and/or associated formalities on behalf of shipper and consignee.
Implementation guidelines means a manual describing 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 and/or regular receipt or delivery of goods can take place, with permanent facilities used for goods movements associated with international trade/transport and used frequently for these purposes. The location should be recognised as such by a competent national body.
Logistics means the planning, execution and control of the movement and placement of people and/or goods and of the supporting activities related to such movement and placement within a system organised to achieve specific objectives.
Manifest means a document listing the specifications of goods including equipment loaded in a means of transport. A manifest often represents an accumulation of Bills of Lading for official and administrative purposes.
Means of transport: represents the type of vehicle used for the transport of goods such as barge, truck, vessel or train.
Message code: a unique six character alphabetic reference identifying a message type.
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.
Monitoring means to follow by means of any of various devices the progress and performance of vessels and to warn the responsible parties of any deviations from the expected, respectively planned performance.
Multimodal transport means the carriage of goods (containers) by at least two different modes of transport.
Nautical support is support given by tugboats or boatmen to assist in safe navigation and mooring.
Navigational information is information provided to the skipper on-board to support in on-board decision making.
Navigational support is support given by pilots on-board or in special circumstances on shore (pilotage from shore) to prevent the development of dangerous vessel traffic situations.
Operator means the owner or manager of the ship.
Polluting goods means (3):
|
— |
oils as defined in Annex I to the MARPOL Convention, |
|
— |
noxious liquid substances as defined in Annex II to the MARPOL Convention, |
|
— |
harmful substances as defined in Annex III to the MARPOL Convention. |
Procedure means the steps to be followed in order to comply with a formality, including the timing, format and transmission method for the submission of required information.
Qualifier means a data element whose value shall be expressed as a code that gives specific meaning to the function of another data element or a segment. [ISO 9735]
Radar means any of several systems or devices using transmitted and reflected radio waves for detecting a reflecting object, such as a vessel and determining its direction, distance, speed and heading. It can be used for navigation and detection.
Reference number serves to refer to or mention a relation or where applicable a restriction.
Risk (Customs) means the likelihood of an event that may occur in the international movement and trade of goods threatening the Community's security and safety, posing a risk to public health environment and consumers.
Risk management (Customs) means the systematic identification and implementation of all measures necessary for limiting exposure of risks. This includes activities such as collecting of data and information, analysing and assessing risk prescribing and taking action and regular monitoring and review of the process and its outcomes, based on international, Community and national sources and strategies.
Segment (EDI) 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. [ISO 9735]
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).
Shipper see consignor.
Single window means a facility that allows parties involved in trade and transport to lodge standardised information with a single entry point to fulfil all regulatory requirements. If information is electronic then individual data elements should only be submitted once (4).
Tag means a unique identifier for a segment or data element. [ISO 9735]
Tracing means the action of retrieving information concerning the whereabouts of cargo, cargo items, consignments or equipment.
Tracking means the function of maintaining status information, including current location, of cargo, cargo items, consignments or equipment (containers either full or empty).
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 UN/ECE in the UN Trade Data Interchange Directory (UNTDID) and are maintained under agreed procedures.
Vessel (synonym: ship) means an inland waterway vessel or sea-going ship. In inland navigation, this term includes also small crafts, ferry boats and floating equipment.
Vessel support services are services given to the skipper by e.g. bunker stations and repair organisation.
Vessel traffic monitoring means providing information orally as well as electronically as well as giving directions in interaction with and response to vessels in a traffic flow to optimise the smooth (efficient) and safe transport.
Vessel traffic services (VTS) means a service implemented by a competent authority, designed to improve the safety and efficiency of vessel traffic and to protect the environment. The service should have the capability to interact with the traffic and to respond to traffic situations developing in the area.
VTS area means the delineated, formally declared service area of the VTS. A VTS area may be subdivided in sub-areas or sectors.
VTS services means an information service, but also others, such as a navigational assistance service, or a traffic organisation service, or both.
2.4. Classifications and code descriptions
In order to minimise interpreting work to be done by the receivers of messages, classifications and code lists shall be used to the highest possible extent. Existing codes shall be used in order to avoid creating additional work on the assembling and maintenance of new code lists.
The following classifications shall be used in inland ship reporting:
|
1. |
Vessel and convoy type (UN Recommendation 28) |
|
2. |
Official ship number (OFS) |
|
3. |
IMO ship identification number (IMO) is the Lloyds Register as published for every seagoing vessel number without the letters LR |
|
4. |
ERI ship identification number |
|
5. |
ENI European navigation identification (unique European vessel number) |
|
6. |
Harmonised commodity description and coding system (HS, goods) |
|
7. |
Combined Nomenclature (CN, goods) |
|
8. |
Standard goods classification for transport statistics (goods) |
|
9. |
UN dangerous goods number (UNDG) |
|
10. |
International maritime dangerous goods code (IMDG) |
|
11. |
ADN/ADNR |
|
12. |
UN code for country and nationality |
|
13. |
UN code for trade and transport locations (UNLOCODE) |
|
14. |
Fairway section code |
|
15. |
Terminal code |
|
16. |
Freight container size and type code |
|
17. |
Container identification code |
|
18. |
Package type code |
|
19. |
Handling instructions |
|
20. |
Purpose of call |
|
21. |
Nature of cargo |
In the following, details and remarks on the application of these codes in inland navigation and user guidelines are given. The vessel and convoy type codes are depicted in various languages in the code tables. The combination of the elements of the above named codes 12 to 15 is defined in Chapter 2.7.
2.4.1. Updating of codes and reference tables
The need to maintain uniform codes and references and the strong requirement to keep the various tables stable and uniform, requires stringent procedures and processes for the maintenance, publication and usage of the various codes.
To facilitate the maintenance of all codes and reference tables used in electronic reporting messages, the codes and references are divided into six categories.
Category A
International codes and references maintained by an official organisation and used in a singular fashion. New or change codes will be published by the international organisation which also indicates at which time the new codes shall be implemented. The implementation of changes to the tables is coordinated by this organisation however for the reporting under the electronic ship reporting specifications, the ERI Expert Group shall indicate as from when the codes are to be used in the messages. Examples are the UNDG (5) IMDG (6) ADN/ADNR/D (7) and the HS/TARIC (8) codes.
Category B
International codes and references maintained by an recognised international organisation such as ISO or UNECE; the publication of changes to the tables takes place at regular intervals as a result of user requirements, the changes are coordinated by the user communities. Examples are the UN/LOCODES (9), the type of means of transport, transport mode, country and currency codes, freight costs and charges.
Category C
Business related codes and references maintained by a private respectively public-private organisation such as EAN, Lloyds, Protect. Examples are IMO numbers, EAN address codes.
Category D
Regional codes and references maintained by a public organisation for usage in a certain area. Examples are fairway section codes, ECDIS references.
Category E
National codes and references maintained by a public, respectively public private partnership. Examples are NST/R.
Category F
Standard codes and references used in the reporting and which are part of the standard message and described in the message as such. Changes should be coordinated by the controlling bodies. Examples are qualifiers, syntax codes, identifiers, function codes.
The international codes and references mentioned under Category A are generally originating from the shipper of the goods. The codes are to be supplied obligatory in accordance with the respective legal requirements and rules and regulations to enable and facilitate control by the competent authorities and emergency measures.
For all the other categories a subset consisting of the codes and references used in electronic reporting and other messages for inland waterway transport is often maintained by the controlling agency. In this way the harmonised use and implementation of new and changed entrees to these code tables can be executed in a coordinated way.
The controlling agency of the various messages can be found under UNH data element 0051 or in the message implementation manuals themselves or in the respective code tables as mentioned underneath.
2.4.2. Descriptions of the code tables
2.4.2.1. Vessel and Convoy Type
|
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 2002 |
|
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 as defined in chapter 6 |
|
SUCCINCT DESCRIPTION |
This 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 http://www.RISexpertgroups.org |
|
LANGUAGES |
English |
|
ADDRESS OF RESPONSIBLE AGENCY |
EC |
|
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 can 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) |
|
Annexes |
|
|
UNECE Recommendation No. 28: Codes for types of means of transport, Inland Navigation code list description in various languages as nationally required |
|
2.4.2.2. Official ship number (OFS)
|
FULL TITLE |
Official ship number |
|
ABBREVIATION |
OFS |
|
ORIGINATING AUTHORITY |
Central Commission for the Navigation of the Rhine (CCNR) |
|
LEGAL BASIS |
§ 2.18 Rheinschiffsuntersuchungsordnung |
|
CURRENT STATUS |
Operational |
|
IMPLEMENTATION DATE |
------ |
|
AMENDMENT |
------ |
|
STRUCTURE |
2-digit country code (an) |
|
|
5 digit register no. (an) |
|
|
Country codes: |
|
|
01 - 19 France |
|
|
20 - 39 The Netherlands |
|
|
40 - 49 Germany |
|
|
60 - 69 Belgium |
|
|
70 - 79 Switzerland |
|
|
80 - 99 Other countries |
|
SUCCINCT DESCRIPTION |
----- |
|
LINKED CLASSIFICATIONS |
----- |
|
USAGE |
Inland navigation |
|
MEDIA THROUGH WHICH AVAILABLE |
----- |
|
LANGUAGES |
----- |
|
ADDRESS OF RESPONSIBLE AGENCY |
Central Commission for the Navigation of the Rhine, 2, Place de la Republique, 67082 Strasbourg Cedex, FRANCE |
|
REMARKS |
This code is replaced by the European Vessel Identification Number as defined in the Rheinschiffsuntersuchungsordnung and Article 2.18 of Annex II to Directive 2006/87/EC (10). |
|
Example |
|
|
4112345 |
Germany, Gerda |
|
Usage in the implementation manuals |
TDT/C222/8213 |
|
|
EQD(1)/C237/8260 |
|
|
SGP/C237/8260 |
2.4.2.3. IMO ship identification number
|
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 |
International Maritime Organisation 4 Albert Embankment London SE1 7SR United Kingdom |
|
Example |
|
|
Vessel dwt 2774 |
Danchem East 9031624 |
|
Usage in the implementation manuals |
TDT/C222/8213 |
|
|
EQD(1)/C237/8260 |
|
|
SGP/C237/8260 |
2.4.2.4. Electronic reporting number (for ship identification) ERN
|
FULL TITLE |
Electronic reporting number (for ship identification) |
|
ABBREVIATION |
ERN |
|
ORIGINATING AUTHORITY |
Rijkswaterstaat, the Netherlands |
|
LEGAL BASIS |
----- |
|
CURRENT STATUS |
Operational |
|
IMPLEMENTATION DATE |
----- |
|
LIMIT OF OPERATIONAL LIFE |
----- |
|
AMENDMENT |
----- |
|
STRUCTURE |
8-digit number |
|
SUCCINCT DESCRIPTION |
----- |
|
LINKED CLASSIFICATIONS |
----- |
|
USAGE |
In electronic reporting for ships which do not have an OFS nor an IMO number |
|
MEDIA THROUGH WHICH AVAILABLE |
www.risexpertgroups.org |
|
LANGUAGES |
|
|
ADDRESS OF RESPONSIBLE AGENCY |
ERI-helpdesk@risexpertgroups.org |
|
REMARK |
This code will is replaced by the European vessel identification number as defined in Article 2.18 of Annex II to Directive 2006/87/EC. |
|
Example |
|
|
12345678 |
Renate |
|
Usage in the implementation guides |
TDT/C222/8213 |
|
|
EQD(1)/C237/8260 |
|
|
SGP/C237/8260 |
2.4.2.5. Unique European vessel identification number
|
FULL TITLE |
Unique European vessel identification number |
||||||
|
ABBREVIATION |
ENI |
||||||
|
ORIGINATING AUTHORITY |
European Union |
||||||
|
LEGAL BASIS |
Directive 2006/87/EC; Directive 2005/44/EC |
||||||
|
CURRENT STATUS |
----- |
||||||
|
IMPLEMENTATION DATE |
----- |
||||||
|
LIMIT OF OPERATIONAL LIFE |
----- |
||||||
|
AMENDMENT |
Continuously |
||||||
|
STRUCTURE |
8-digit-number |
||||||
|
SUCCINCT DESCRIPTION |
The unique European navigation identification or the unique European vessel identification number aims at assigning a permanent number to each hull for identifying purposes. |
||||||
|
LINKED CLASSIFICATIONS |
IMO number, ERN number, OFS 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 |
EU Member States and the contract parties to 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. See also Chapter 2.5. |
|
Example 12345678 |
|
|
Usage in the implementation manuals |
TDT, EQD (V1 and V2-V15) CNI/GID and CNI/GID/DGS, Tag 1311 |
2.4.2.6. Harmonised system code (HS)
|
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-1-2007 |
|
AMENDMENT |
In principle revised every five years. |
|
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 these are comparable internationally. |
|
LINKED CLASSIFICATIONS |
Combined Nomenclature (CN): full agreement on six-digit-level; |
|
|
NST/R on 3-digit level. |
|
USAGE |
Products |
|
MEDIA THROUGH WHICH AVAILABLE |
World Customs Organisation Rue de l’Industrie, 26-39 1040 Brussels, BELGIUM www.wcoomd.org Customs Cooperation Council, Brussels |
|
LANGUAGES |
Dutch, English, French, German etc. |
|
ADDRESS OF RESPONSIBLE AGENCY |
A subset of the codes used for electronic reporting will be maintained through the ERI expert group. |
|
REMARKS |
The HS classification is further disaggregated 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.4.2.7. Combined Nomenclature (CN)
|
FULL TITLE |
Combined Nomenclature |
|
ABBREVIATION |
CN |
|
ORIGINATING AUTHORITY |
EU Commission, Statistical Office EUROSTAT |
|
LEGAL BASIS |
EU Council, Regulation (EEC) No 2658/87 of 23 July 1987 |
|
CURRENT STATUS |
Operational |
|
IMPLEMENTATION DATE |
----- |
|
AMENDMENT |
Annual revisions at 1 January |
|
STRUCTURE |
8-digit numerical code: |
|
|
19 581 headings organised in five 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 |
|
|
Level 5: categories identified by eight-digit numerical codes |
|
SUCCINCT DESCRIPTION |
The Combined Nomenclature is the goods classification used within the EU for the purposes of foreign trade statistics. It is also used by the EU for customs duty purposes. The classification is based on the Harmonised System (HS) which it sub-divides where necessary for purposes of external trade, agricultural regulation and customs duties. The CN was introduced in 1988 together with the HS. |
|
LINKED CLASSIFICATIONS |
HS code: full agreement on six-digit-level NST/R on 3-digit level |
|
USAGE |
Products |
|
MEDIA THROUGH WHICH AVAILABLE |
http://ec.europa.eu/taxation_customs |
|
LANGUAGES |
all languages of the EU |
|
ADDRESS OF RESPONSIBLE AGENCY |
European Commission, DG TAXUD |
|
REMARKS |
----- |
|
Usage in the implementation manuals |
Indirectly through HS code |
2.4.2.8. Standard goods classification for transport statistics/revised (NST) 2000
|
FULL TITLE |
Nomenclature uniforme de marchandises pour les statistiques de transport/Standard goods classification for transport statistics/revised |
|
ABBREVIATION |
NST 2000 |
|
ORIGINATING AUTHORITY |
European Commission (Statistical Office/Eurostat) |
|
LEGAL BASIS |
EU regulation on statistics |
|
CURRENT STATUS |
----- |
|
IMPLEMENTATION DATE |
1.1.2007 |
|
AMENDMENT |
Regularly every two years |
|
STRUCTURE |
2 digit NST 2000 Level 1: a 2-digit CPA subdivision |
|
SUCCINCT DESCRIPTION |
HS Code in one way (HS > NST), Commodity Classification for Transport Statistics in Europe (CSTE) |
|
LINKED CLASSIFICATIONS |
Products HS Code in one way (HS > NST) |
|
USAGE |
Products |
|
MEDIA THROUGH WHICH AVAILABLE |
http://ec.europa.eu/comm/eurostat/ramon/nomenclatures/index.cfm?TargetUrl=LST_NOM_DTL&StrNom=NSTR_1967&StrLanguageCode=EN&IntPcKey |
|
LANGUAGES |
Dutch, English, French, German etc. |
|
ADDRESS OF RESPONSIBLE AGENCY |
Statistical Office of the European Communities Eurostat) Unit C2 Batiment BECH A3/112 2920 Luxembourg, LUXEMBOURG |
|
REMARKS |
----- |
(a) Standard goods classification for transport statistics/revised (NST/R)
|
FULL TITLE |
Nomenclature uniforme de marchandises pour les statistiques de transport/Standard goods classification for transport statistics/revised |
|
ABBREVIATION |
NST/R |
|
ORIGINATING AUTHORITY |
European Commission (Statistical Office/Eurostat) |
|
LEGAL BASIS |
------ |
|
CURRENT STATUS |
Operational, but presently under revision |
|
IMPLEMENTATION DATE |
1.1.1967 |
|
AMENDMENT |
Regularly every two years |
|
STRUCTURE |
3-digit numerical code. |
|
Level 1: 10 chapters, identified by one-digit numerical codes (0 to 9) |
|
|
Level 2: 52 groups identified by two-digit numerical codes |
|
|
Level 3: 176 headings identified by three-digit numerical codes |
|
|
SUCCINCT DESCRIPTION |
The NST/R was devised by Eurostat for the harmonisation of statistics on national and international transport in the Member States of the European Communities |
|
LINKED CLASSIFICATIONS |
Commodity Classification for Transport Statistics in Europe (CSTE), |
|
|
HS code in one way (HS > NST/R) |
|
USAGE |
Products |
|
MEDIA THROUGH WHICH AVAILABLE |
http://ec.europa.eu/comm/eurostat/ramon/nomenclatures/index.cfm?TargetUrl=LST_NOM_DTL&StrNom=NSTR_1967&StrLanguageCode=EN&IntPcKey= |
|
LANGUAGES |
Dutch, English, French, German etc. |
|
ADDRESS OF RESPONSIBLE AGENCY |
Statistical Office of the European Communities (Eurostat) Unit C2 Batiment BECH A3/112 2920 Luxembourg, LUXEMBOURG |
|
REMARKS |
----- |
|
Example |
|
|
729 |
Composite and other manufactured fertilisers |
|
321 |
Motor sprit |
|
Usage in the implementation manuals |
CNI/GID/FTX(2)/C108/4440 |
(b) Standard goods classification for transport statistics/revised — the Netherlands (NST/R NL)
|
FULL TITLE |
Standard goods classification for transport statistics/revised — the Netherlands |
|
ABBREVIATION |
NST/R-NL |
|
ORIGINATING AUTHORITY |
----- |
|
LEGAL BASIS |
----- |
|
CURRENT STATUS |
Operational |
|
IMPLEMENTATION DATE |
----- |
|
AMENDMENT |
Regularly every two years |
|
STRUCTURE |
4-digit numerical code |
|
SUCCINCT DESCRIPTION |
The NST/R-NL is based on the 3-digit NST/R classification of Eurostat |
|
LINKED CLASSIFICATIONS |
NST/R, HS Code in one way (HS > NST/R) |
|
USAGE |
Statistics |
|
MEDIA THROUGH WHICH AVAILABLE |
----- |
|
LANGUAGES |
Dutch |
|
ADDRESS OF RESPONSIBLE AGENCY |
----- |
|
REMARKS |
On level 4 not compatible with NST/R-FR and NST/R-DE |
|
Example |
|
|
7290 |
Mengmeststoffen en andere gefabriceerde meststoffen |
|
3210 |
Benzine |
|
Usage in the implementation manuals |
CNI/GID/FTX(2)/C108/4440 |
(c) Standard goods classification for transport statistics/revised — France (NST/R FR)
|
FULL TITLE |
Nomenclature uniforme de marchandises pour les statistiques de transport |
|
ABBREVIATION |
NST/R-FR |
|
ORIGINATING AUTHORITY |
----- |
|
LEGAL BASIS |
----- |
|
CURRENT STATUS |
Operational |
|
IMPLEMENTATION DATE |
----- |
|
AMENDMENT |
Regularly every two years |
|
STRUCTURE |
4-digit numerical code |
|
SUCCINCT DESCRIPTION |
The NST/R-FR is based on the 3-digit NST/R classification of Eurostat |
|
LINKED CLASSIFICATIONS |
NST/R, HS Code in one way (HS > NST/R) |
|
USAGE |
Waterway charges invoicing, statistics |
|
MEDIA THROUGH WHICH AVAILABLE |
----- |
|
LANGUAGES |
French |
|
ADDRESS OF RESPONSIBLE AGENCY |
----- |
|
REMARKS |
On level 4 not compatible with NST/R-NL and NST/R-DE |
|
Example |
|
|
7291 |
Engrais composés et autres engrais manufacturés |
|
3210 |
Essence de pétrole |
|
Usage in the implementation guidelines |
CNI/GID/FTX(2)/C108/4440 |
(d) Standard goods classification for transport statistics/revised — Germany (NST/R DE)
|
FULL TITLE |
Güterverzeichnis für den Verkehr auf deutschen Binnenwasserstraßen |
|
ABBREVIATION |
GV-Binnenwasserstraßen; NST/R-DE |
|
ORIGINATING AUTHORITY |
Wasser- und Schifffahrtsdirektion West, Münster |
|
LEGAL BASIS |
By order of the Ministry of Transport, Germany |
|
CURRENT STATUS |
Operational |
|
IMPLEMENTATION DATE |
1.1.1986 |
|
AMENDMENT |
Regularly every two years |
|
STRUCTURE |
4-digit numerical code |
|
Level 1: 10 chapters, identified by one-digit numerical code (0 to 9) |
|
|
Level 2: 52 groups identified by two-digit numerical codes |
|
|
Level 3: 176 headings identified by three-digit numerical codes |
|
|
Level 4: 1-digit amendment specific for invoicing and statistics |
|
|
SUCCINCT DESCRIPTION |
The ‘GV-Binnenwasserstraßen’ is based on the 3-digit NST/R classification of Eurostat and the ‘Güterverzeichnis 1969’ of the Statistisches Bundesamt |
|
LINKED CLASSIFICATIONS |
NST/R, HS Code in one way (HS > NST/R) |
|
|
Güterverzeichnis für die Verkehrsstatistik (GV) |
|
USAGE |
Waterway charges invoicing, Statistics |
|
MEDIA THROUGH WHICH AVAILABLE |
WSD West, Münster |
|
LANGUAGES |
German |
|
ADDRESS OF RESPONSIBLE AGENCY |
See above |
|
REMARKS |
On level 4 not compatible with NST/R-FR and NST/R-NL |
|
Example |
|
|
7290 |
Mineralische Mehrstoffnährdünger |
|
3210 |
Benzin |
|
Usage in the implementation manuals |
CNI/GID/FTX(2)/C108/4440 |
2.4.2.9. UN dangerous goods number (UNDG)
|
FULL TITLE |
UN Recommendations on the transport of dangerous goods Annex ‘Model Regulations’ Part 3 ‘Dangerous Goods List’ Appendix A ‘List of generic and NOS proper shipping names’ |
||||||||
|
ABBREVIATION |
UN Model Regulations; UNDG |
||||||||
|
ORIGINATING AUTHORITY |
UNECE |
||||||||
|
LEGAL BASIS |
----- |
||||||||
|
CURRENT STATUS |
Operational |
||||||||
|
IMPLEMENTATION DATE |
As of 1956, the model regulations 1996 |
||||||||
|
AMENDMENT |
|
||||||||
|
STRUCTURE |
4 digit numerical code |
||||||||
|
SUCCINCT DESCRIPTION |
The UN recommendations on the transport of dangerous goods address the following main areas:
|
||||||||
|
LINKED CLASSIFICATIONS |
IMDG code |
||||||||
|
USAGE |
Transport of dangerous goods |
||||||||
|
MEDIA THROUGH WHICH AVAILABLE |
http://www.unece.org/trans/danger/publi/unrec/ |
||||||||
|
LANGUAGES |
English |
||||||||
|
ADDRESS OF RESPONSIBLE AGENCY |
Transport Division United Nations Economic Commission for Europe Palais des nations CH–1211 Geneve 10 www.unece.org |
||||||||
|
REMARKS |
In this standard only the 4-digit UN number is used (not class and division) |
|
Example |
|
|
1967 |
Gas sample, non-pressurised, toxic |
|
Usage in the implementation manuals |
CNI/GID/DGS/C234/7124 |
2.4.2.10. 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.1.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 |
|
LANGUAGES |
Dutch, English, French, German |
|
ADDRESS OF RESPONSIBLE AGENCY |
International Maritime Organisation 4 Albert Embankment London SE1 7SR UNITED KINGDOM |
|
REMARKS |
For inland shipping the IMO code can be used as this code is often already known, where necessary an ADN/R code corresponding with the IMDG code should be inserted |
|
Example |
|
|
32 |
Flammable liquid, not otherwise specified (Ethanol) |
|
Usage in the implementation manuals |
CNI/GID/DGS/C205/8351 |
2.4.2.11. ADN/R/D
|
FULL TITLE |
Accord européen relatif au transport international des marchandises dangereuses par voie de navigation intérieure (du Rhin, du Danube) |
||
|
ABBREVIATION |
ADN/R/D |
||
|
ORIGINATING AUTHORITY |
Central Commission for the Navigation on the Rhine Commission du Danube UN Economic Commission for Europe |
||
|
LEGAL BASIS |
----- |
||
|
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 |
||
|
USAGE |
Transport of dangerous goods in inland navigation |
||
|
MEDIA THROUGH WHICH AVAILABLE |
www.ccr-zkr.org www.danubecom-intern.org http://www.unece.org/trans/danger/publi/adn/adn_treaty.html |
||
|
LANGUAGES |
Dutch, French, German |
||
|
ADDRESS OF RESPONSIBLE AGENCY |
Central Commission for the Navigation on the Rhine, 2, Place de la Republique, 67082 Strasbourg Cedex, FRANCE UN Economic Commission for Europe, Palais des Nations, CH–1211 Geneva 10, SWITZERLAND |
||
|
REMARKS |
The provisions of the ADN agreement, the European Agreement concerning the international carriage of dangerous goods by inland waterways (ADN) are applicable on the Rhine (ADNR) and on the Danube (ADND). The 2007 edition of ADR/RID/ADN is harmonised with the 14th revised edition of the UN Model Regulations and has entered into force on 1 January 2007. |
|
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.4.2.12. 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 of this standard |
|
MEDIA THROUGH WHICH AVAILABLE |
UNECE www.unece.org/locode |
|
LANGUAGES |
English |
|
ADDRESS OF RESPONSIBLE AGENCY |
http://www.unece.org/cefact |
|
REMARKS |
See Chapter 2.7 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.4.2.13. UN location code — UN/LOCODE
|
FULL TITLE |
UN code for trade and transport locations |
|
ABBREVIATION |
UN/LOCODE |
|
ORIGINATING AUTHORITY |
UNECE/CEFACT |
|
LEGAL BASIS |
UN/ECE Recommendation 16 |
|
CURRENT STATUS |
Operational |
|
IMPLEMENTATION DATE |
1980 |
|
AMENDMENT |
2006-2 |
|
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 (an5) |
|
|
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 of this standard. |
|
MEDIA THROUGH WHICH AVAILABLE |
www.unece.org/locode |
|
LANGUAGES |
English |
|
ADDRESS OF RESPONSIBLE AGENCY |
UNECE |
|
REMARKS |
See Chapter 2.7 for combination of elements in the location code |
|
Example |
|
|
BEBRU |
Belgium Brussels |
|
Usage in the implementation manuals |
TDT/LOC (1..9)/C517/3225 |
|
|
CNI/LOC(1..2) /C517/3225 |
|
See: |
This document and implementation manuals ‘Definition of the revised location and terminal code’ by Ministry of Transport and Public Works Traffic and Transport Advisory Service May 2002 |
2.4.2.14. 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 |
UNLOCODE |
|
USAGE |
Numbering of the waterways in a national network. This code is used as one element in the combined location code of this standard. |
|
MEDIA THROUGH WHICH AVAILABLE |
----- |
|
LANGUAGES |
----- |
|
ADDRESS OF RESPONSIBLE AGENCY |
National administrations of waterways. Coordination through the ERI expert group. |
|
REMARKS |
See Chapter 2.7 for combination of elements in the location code |
|
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 should be filled in with zeros |
|
Remark 2: |
See Chapter 2.7 for combination of elements in the location code |
2.4.2.15. Terminal code
|
FULL TITLE |
Terminal code |
|
ABBREVIATION FROM |
----- |
|
ORIGINATING FROM |
National waterway authorities |
|
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 |
UNLOCODE |
|
USAGE |
This code is used as one element in the combined location code of this standard. See Chapter 2.7 for combination of elements in the location code and rules for maintenance of the respective code sets |
|
MEDIA THROUGH WHICH AVAILABLE |
www.risexpertgroups.org |
|
LANGUAGES |
----- |
|
ADDRESS OF RESPONSIBLE AGENCY |
National administrations of waterways. Coordination through the ERI expert group. |
|
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 Chapter 2.7 for combination of elements in the location code |
|
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 should be filled in with zeros |
|
Remark 2: |
Each country will be responsible for its own data. Coordination and central distribution will be made by Rijkswaterstaat of the Netherlands |
|
Remark 3: |
At present, a terminal code is maintained by Bureau Telematica for Rijkswaterstaat |
2.4.2.16. Freight 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 1995-12-01 |
|
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 |
|
LANGUAGES |
English |
|
ADDRESS OF RESPONSIBLE AGENCY |
http://www.bic-code.org/ |
|
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 for size |
|
|
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.4.2.17. Container identification code
|
FULL TITLE |
Freight containers — coding, identification and marking |
|
ABBREVIATION |
ISO size type codes |
|
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 http://www.bic-code.org/ |
|
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.4.2.18. 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 |
|
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.4.2.19. 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.4.2.20. 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.4.2.21. 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.5. Unique European vessel identification number
|
— |
The unique European vessel identification number (ENI), in the following referred to as European vessel identification number is defined in Article 2.18 of Annex II to Directive 2006/87/EC. |
|
— |
Unless the craft possesses a European vessel identification number at the time when it needs a European vessel identification number to participate in river information services (RIS), it shall be assigned to that craft by the competent authority of the Member State in which the craft has been registered or has its home port. |
|
— |
As far as crafts from countries where an assignation of a European vessel identification number is not possible are concerned, the European vessel identification number shall be assigned by the competent authority of the Member State, where the vessel needs a European vessel identification number for the participation in RIS for the first time. |
|
— |
The competent authority shall issue a certificate, which documents the assignation of the European vessel identification number. |
|
— |
Only one single European vessel identification number can be assigned to one craft. The European vessel identification number is issued only once and remains unchanged throughout the whole lifetime of the craft. |
|
— |
The owner of a craft, or his representative, shall apply to the competent authority for assignment of the European vessel identification number. The owner or his representative shall also be responsible for having the European vessel identification number affixed to the craft. |
|
— |
Each Member State shall notify the Commission of the competent authorities responsible for assigning European vessel identification numbers. The Commission shall keep a register of those competent authorities and of competent authorities notified by third countries, and shall make the register available to the Member States. On request this register shall also be made available to competent authorities of third countries. |
|
— |
Each competent authority in accordance with the previous paragraph shall make all necessary arrangements in order to inform all other competent authorities listed in the register kept in accordance with the previous paragraph of each European vessel identification number it assigns as well as of data for the identification of the vessel set out in Appendix IV of Annex II of Directive 2006/87/EC. |
|
— |
These data may be made available to competent authorities of other Member States, Contracting States of the Mannheim Convention and, as far as an equivalent level of privacy is guaranteed, to third countries on the basis of administrative agreements in order to perform administrative measures for maintaining safety and ease of navigation. |
2.6. Definition of the ERI vessel types
|
USEV/C |
M |
Code Subdiv |
Name Description |
|
|
No |
8 |
00 |
0 |
Vessel, type unknown |
|
|
|
|
|
Vessel of unknown type. |
|
V |
8 |
01 |
0 |
Motor freighter |
|
|
|
|
|
Motorised vessel designed for carrying general cargo. |
|
V |
8 |
02 |
0 |
Motor tanker |
|
|
|
|
|
Motorised vessel designed for carrying cargo in tanks |
|
V |
8 |
02 |
1 |
Motor tanker, liquid cargo, type N |
|
|
|
|
|
Motorised vessel designed for carrying liquid cargo. |
|
V |
8 |
02 |
2 |
Motor tanker, liquid cargo, type C |
|
|
|
|
|
Motorised vessel designed for carrying special chemicals |
|
V |
8 |
02 |
3 |
Motor tanker, dry cargo |
|
|
|
|
|
Motorised vessel designed for carrying dry cargo as if liquid (e.g. cement) |
|
V |
8 |
03 |
0 |
Container vessel |
|
|
|
|
|
Vessel designed for carrying containers. |
|
V |
8 |
04 |
0 |
Gas tanker |
|
|
|
|
|
Vessel with tanks designed for carrying gas. |
|
C |
8 |
05 |
0 |
Motor freighter, tug |
|
|
|
|
|
Motorised vessel designed for carrying cargo and capable of towing. |
|
C |
8 |
06 |
0 |
Motor tanker, tug |
|
|
|
|
|
Motorised vessel designed for carrying liquid cargo and capable to tow. |
|
C |
8 |
07 |
0 |
Motor freighter with one or more ships alongside |
|
|
|
|
|
Motorised vessel designed for carrying general cargo that has one or more vessels alongside. |
|
C |
8 |
08 |
0 |
Motor freighter with tanker |
|
|
|
|
|
Motorised vessel designed for carrying general cargo alongside a vessel designed for carrying liquid cargo. |
|
C |
8 |
09 |
0 |
Motor freighter pushing one or more freighters |
|
|
|
|
|
Motorised vessel designed for carrying general cargo, pushing one or more vessels also designed for carrying general cargo. |
|
C |
8 |
10 |
0 |
Motor freighter pushing at least one tank-ship |
|
|
|
|
|
Motorised vessel designed for carrying general cargo, pushing at least one vessel designed to carry a liquid cargo. |
|
No |
8 |
11 |
0 |
Tug, freighter |
|
|
|
|
|
Vessel designed to push or pull another vessel that is also capable of carrying general cargo. |
|
No |
8 |
12 |
0 |
Tug, tanker |
|
|
|
|
|
Vessel designed to push or pull another vessel also capable of carrying liquid cargo. |
|
C |
8 |
13 |
0 |
Tug, freighter, coupled |
|
|
|
|
|
Vessel designed to push or pull another vessel that is also capable of carrying general cargo tied to one or more other vessels. |
|
C |
8 |
14 |
0 |
Tug, freighter/tanker, coupled |
|
|
|
|
|
Vessel designed to push or pull another vessel that is also capable of carrying either general or liquid cargo tied to one or more other vessels. |
|
V |
8 |
15 |
0 |
Freight barge |
|
|
|
|
|
Lighter designed for carrying general cargo. |
|
V |
8 |
16 |
0 |
Tank barge |
|
|
|
|
|
Lighter designed for carrying cargo in tanks |
|
V |
8 |
16 |
1 |
Tank barge, liquid cargo, type N |
|
|
|
|
|
Lighter designed for carrying liquid cargo. |
|
V |
8 |
16 |
2 |
Tank barge, liquid cargo, typec |
|
|
|
|
|
Lighter designed to carrying special chemicals |
|
V |
8 |
16 |
3 |
Tank barge, dry cargo |
|
|
|
|
|
Lighter designed for carrying dry cargo as if liquid (e.g. cement) |
|
V |
8 |
17 |
0 |
Freight barge with containers |
|
|
|
|
|
Lighter designed for carrying containers. |
|
V |
8 |
18 |
0 |
Tank barge, gas |
|
|
|
|
|
Lighter designed for carrying gas. |
|
C |
8 |
21 |
0 |
Pushtow, one cargo barge |
|
|
|
|
|
Vessel designed for pushing/towing, facilitating the movement of one cargo barge. |
|
C |
8 |
22 |
0 |
Pushtow, two cargo barges |
|
|
|
|
|
Combination designed for pushing/towing, facilitating the movement of two cargo barges |
|
C |
8 |
23 |
0 |
Pushtow, three cargo barges |
|
|
|
|
|
Combination designed for pushing/towing, facilitating the movement of three cargo barges |
|
C |
8 |
24 |
0 |
Pushtow, four cargo barges |
|
|
|
|
|
Combination designed for pushing/towing, facilitating the movement four cargo barges |
|
C |
8 |
25 |
0 |
Pushtow, five cargo barges |
|
|
|
|
|
Combination designed for pushing/towing, facilitating the movement of five cargo barges. |
|
C |
8 |
26 |
0 |
Pushtow, six cargo barges |
|
|
|
|
|
Combination designed for pushing/towing, facilitating the movement of six cargo barges. |
|
C |
8 |
27 |
0 |
Pushtow, seven cargo barges |
|
|
|
|
|
Combination designed for pushing/towing, facilitating the movement of seven cargo barges. |
|
C |
8 |
28 |
0 |
Pushtow, eight cargo barges |
|
|
|
|
|
Combination designed for pushing/towing, facilitating the movement of eight cargo barges. |
|
C |
8 |
29 |
0 |
Pushtow, nine cargo barges |
|
|
|
|
|
Combination designed for pushing/towing, facilitating the movement of nine or more cargo barges. |
|
C |
8 |
31 |
0 |
Pushtow, one gas/tank barge |
|
|
|
|
|
Combination designed for pushing/towing, moving one tanker or gas barge. |
|
C |
8 |
32 |
0 |
Pushtow, two barges at least one tanker or gas barge |
|
|
|
|
|
Combination designed for pushing/towing, moving two barges of which at least one tanker or gas barge. |
|
C |
8 |
33 |
0 |
Pushtow, three barges at least one tanker or gasbarge |
|
|
|
|
|
Combination designed for pushing/towing, moving three barges of which at least one is a tanker or gas barge. |
|
C |
8 |
34 |
0 |
Pushtow, four barges at least one tanker or gasbarge |
|
|
|
|
|
Combination designed for pushing/towing, moving four barges of which at least one tanker or gasbarge. |
|
C |
8 |
35 |
0 |
Pushtow, five barges at least one tanker or gasbarge |
|
|
|
|
|
Combination designed for pushing/towing, moving five barges of which at least one tanker of gasbarge. |
|
C |
8 |
36 |
0 |
Pushtow, six barges at least one tanker or gasbarge |
|
|
|
|
|
Combination designed for pushing/towing, moving six barges of which at least one tanker or gasbarge. |
|
C |
8 |
37 |
0 |
Pushtow, seven barges at least one tanker or gasbarge |
|
|
|
|
|
Combination designed for pushing/towing, moving seven barges of which at least one tanker or gasbarge. |
|
C |
8 |
38 |
0 |
Pushtow, eight barges at least one tanker or gasbarge |
|
|
|
|
|
Combination designed for pushing/towing, moving eight barges of which at least one tanker or gasbarge. |
|
C |
8 |
39 |
0 |
Pushtow, nine or more barges at least one tanker or gasbarge |
|
|
|
|
|
Combination designed for pushing/towing, moving nine or more barges of which at least one tanker or gasbarge. |
|
V |
8 |
40 |
0 |
Tug, single |
|
|
|
|
|
Vessel designed for pushing another vessel that is the only boat used for a tow. |
|
No |
8 |
41 |
0 |
Tug, one or more tows |
|
|
|
|
|
Vessel designed for pushing another vessel that is involved in one or more concurrent tows. |
|
C |
8 |
42 |
0 |
Tug, assisting a vessel or linked combination |
|
|
|
|
|
Vessel designed for pushing another vessel that is assisting one vessel or a combination of vessels or tugs and vessels. |
|
V |
8 |
43 |
0 |
Pushboat, single |
|
|
|
|
|
Vessel designed for pushing. |
|
V |
8 |
44 |
0 |
Passenger ship, ferry, red cross ship, cruise ship |
|
|
|
|
|
Vessels designed for carrying passengers in general. |
|
V |
8 |
44 |
1 |
Ferry |
|
|
|
|
|
Vessel designed for carrying passengers and/or vehicles on regular short voyages. |
|
V |
8 |
44 |
2 |
Red Cross ship Vessel designed for carrying sick and or disabled people |
|
V |
8 |
44 |
3 |
Cruise ship |
|
|
|
|
|
Vessel designed for carrying passengers accommodated on-board |
|
V |
8 |
44 |
4 |
Passenger ship without accommodation |
|
|
|
|
|
Vessel designed for carrying passengers but without accommodation such as cabins etc. |
|
V |
8 |
45 |
0 |
Service vessel, police patrol, port services |
|
|
|
|
|
Vessel designed to perform a specific dedicated service. |
|
V |
8 |
46 |
0 |
Vessel, work maintenance craft, floating derrick, cable-ship, buoy-ship, dredge. |
|
|
|
|
|
Vessel designed to perform a specific type of work. |
|
C |
8 |
47 |
0 |
Object, towed, not otherwise specified. |
|
|
|
|
|
An object in tow that is not otherwise specified. |
|
V |
8 |
48 |
0 |
Fishing boat |
|
|
|
|
|
Vessel designed for fishing. |
|
V |
8 |
49 |
0 |
Bunkership |
|
|
|
|
|
Vessel designed for carrying and delivering bunkers. |
|
V |
8 |
50 |
0 |
Barge, tanker, chemical |
|
|
|
|
|
Vessel designed to carry liquid or bulk chemicals. |
|
C |
8 |
51 |
0 |
Object, not otherwise specified. |
|
|
|
|
|
A floating object that is not otherwise specified. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Extra codes for maritime means of transport |
|
|
|
|
|
|
|
V |
1 |
50 |
0 |
General cargo vessel maritime |
|
|
|
|
|
Vessel designed to carry general cargo |
|
V |
1 |
51 |
0 |
Unit carrier maritime |
|
|
|
|
|
Vessel designed to carry containers |
|
V |
1 |
52 |
0 |
Bulk carrier maritime |
|
|
|
|
|
Vessel designed to carry bulk cargo |
|
V |
1 |
53 |
0 |
Tanker |
|
|
|
|
|
Vessel solely equipped with tanks for carrying cargo |
|
V |
1 |
54 |
0 |
Liquefied gas tanker |
|
|
|
|
|
Tanker designed to carry liquefied gas |
|
V |
1 |
85 |
0 |
Craft, pleasure longer than 20 meters |
|
|
|
|
|
Vessel designed for recreation longer than 20 meters |
|
V |
1 |
90 |
0 |
Fast ship |
|
|
|
|
|
Fast all purpose vessel |
|
V |
1 |
91 |
0 |
Hydrofoil |
|
|
|
|
|
Vessel with wing-like structure for skimming at high speed |
|
V |
1 |
92 |
0 |
Catamaran fast |
|
|
|
|
|
Fast vessel designed with two parallel hulls |
|
Source: UNECE. |
||||
2.7. Location codes
2.7.1. Data elements
The location code consists of the following separate elements:
|
Element No |
Description |
|
1 |
UN country code (2 digits) |
|
2 |
UN location code (3 digits) |
|
3 |
Fairway section No (5 digits) |
|
4 |
Terminal code or passage point code (5 digits) |
|
5 |
Fairway section hectometre (5 digits), in the database treated as an attribute to the fairway section number |
The requested location shall be always presented as a unique code. This can be accomplished in different ways depending on the purpose of reporting and the local situation.
The UNLOCODE always consists of the country and location code, together this combination makes the UNLOCODE code unique.
2.7.2. Example
|
Purpose |
Example |
Used Elements |
Code |
|||||||||
|
|
No |
Full text |
1 UN country code |
2 UN location code |
3 Fairway section number |
4 Terminal code |
5 Fairway hectometer |
1 |
2 |
3 |
4 |
5 |
|
Transport notice, invoice declaration |
||||||||||||
|
|
Place of departure/destination |
|
|
|
|
|
|
|
|
|
|
|
|
|
1 |
Germany; Mainz; Rhine; Frankenbach |
x |
x |
x |
X |
|
DE |
MAI |
03901 |
00FRB |
00000 |
|
|
2 |
The Netherlands; Rotterdam; Section 2552 (Oude Maas); Leuvehaven |
x |
x |
x |
X |
|
NL |
RTM |
02552 |
LEUVE |
00000 |
|
|
3 |
The Netherlands; Section 2552 (Oude Maas); km 2,2 |
x |
|
x |
|
x |
NL |
XXX |
05552 |
00000 |
00022 |
|
|
4 |
Germany; Rhine; km 502,3 |
x |
|
x |
|
x |
DE |
XXX |
03900 |
00000 |
05023 |
|
Traffic notice |
||||||||||||
|
|
Passage Point |
|
|
|
|
|
|
|
|
|
|
|
|
|
5 |
Germany; Rhine; km 502,3 |
x |
|
x |
|
x |
DE |
XXX |
03900 |
00000 |
05023 |
|
|
6 |
Germany; Oberwesel; Rhine; Traffic centre |
x |
x |
x |
X |
|
DE |
OWE |
03901 |
TRACE |
00000 |
|
|
7 |
Germany; Trier; Mose; lock |
x |
X |
x |
X |
|
De |
TRI |
03201 |
LOCK |
00000 |
Abbreviations
|
Abbreviations |
Description |
|
AND |
European Agreement concerning the international carriage of dangerous goods by inland waterways (EU Council Directive 94/95/EC) |
|
ADNR |
Réglement pour le transport de matières dangereuses sur le Rhin |
|
AIS |
Automatic identification system |
|
BERMAN |
Berth management (EDI message) |
|
CCNR |
Central Commission for the navigation on the Rhine |
|
CN |
Combined Nomenclature (on goods) of the harmonised system |
|
DWT |
Dead weight |
|
EAN |
European Article Numbering Association |
|
ECDIS |
Electronic chart display and information system |
|
EDI |
Electronic data interchange |
|
ENI |
European vessel identification number |
|
ERI |
Electronic reporting international |
|
ERINOT |
ERI notification (message) |
|
ERIRSP |
ERI response (message) |
|
ERN |
Electronic reporting number |
|
ETA |
Estimated time of arrival |
|
ETD |
Estimated time of departure |
|
FAL |
IMO facilitation convention |
|
GPS |
Global positioning system |
|
HS Code |
Harmonised commodity description and coding system of WCO |
|
HTML |
Hyper text markup language |
|
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 2000 |
Standard goods classification for transport statistics (to be used from 2007 onwards) |
|
NST/R |
Standard goods classification for transport statistics/revised |
|
OFS |
Official ship number |
|
PAXLST |
Passenger list (message) |
|
PROTECT |
International Organisation of North Europeans Ports dealing with dangerous goods message implementation |
|
PCS |
Port community system |
|
RIS |
River information services |
|
SCAC |
Standard carrier alpha code |
|
SOLAS |
Safety of Lives at Sea IMO Convention |
|
UN/CEFACT |
UN Centre for Trade Facilitation and Electronic Business |
|
UN/ECE |
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 |
|
VTS |
Vessel traffic services |
|
WCO |
World Customs Organisation |
|
XML |
Extended markup language |
(1) PROTECT: An organisation of a number of European seaports which have developed common implementation guidelines for standard messages. These guidelines form the basis of the implementation manuals in the technical specifications for electronic reporting.
(2) UN/EDIFACT Glossary, edited by UNECE (www.unece.org/trade/untdid/texts/d300_d.htm); Transport & Logistics Glossary, R&D projects in the framework of the European Framework Programmes for RTD — INDRIS (FP4), COMPRIS (FP5), MARNIS (FP6)
(3) Source: Directive 2002/59/EC.
(4) Source: UNECE recommendation 33.
(5) Changes to the codes are agreed and published through the UN every two years.
(6) Changes to the codes are published through the IMO every two years.
(7) Changes to the codes are agreed and published every two years through the respective responsible organisations.
(8) Changes to the full code set are published by the WCO every four years, the subset is adapted based on the Change Requests through the ERI group of experts.
(9) Implementation of new or changed codes to be co-ordinated by the ERI Expert Group.
(10) Directive of the European Parliament and the Council of 12 December 2006 laying down technical requirements for inland waterway vessels and repealing Council Directive 82/714/EEC (OJ L 389, 30.12.2006, p. 1).
Appendix 1
(Dangerous) Goods Reporting (IFTDGN) — ERINOT
TABLE OF CONTENTS
|
1. |
ERI notification message |
|
1.1 |
Segment table |
|
1.2. |
Branching diagram (ERI notification message) |
|
1.3. |
ERINOT message structure |
|
1.4. |
Dummy segments |
|
1.5. |
Empty vessels |
|
1.6. |
Container transport with non-dangerous goods |
|
1.7. |
Containers with unknown details on the goods or empty containers |
|
1.8. |
Exchanging information between RIS authorities |
|
1.9. |
Cancelling a notification |
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.1. The branching diagram of the ERINOT message is depicted in chapter 1.2.
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. Segment table
|
|
|
ERI |
||||||||||
|
Tag |
Name |
S |
R |
|
S |
|
R |
|
|
|
|
|
|
Message header |
M |
1 |
|
M |
|
1 |
|
|
|
|
|
|
|
Beginning of message |
M |
1 |
|
M |
|
1 |
|
|
|
|
|
|
|
Date/time/period |
C |
9 |
|
C |
|
0 |
|
|
|
|
|
|
|
Free text |
C |
9 |
|
C |
|
3 |
|
|
|
|
|
|
|
Handling instructions |
C |
1 |
|
D |
|
1 |
|
|
|
|
|
|
|
|
-------Segment Group 1------- |
C |
9 |
--- |
C |
|
3 |
--- |
--- |
--- |
--- |
--| |
|
Reference |
M |
1 |
|
M |
|
1 |
|
|
|
|
| |
|
|
Date/time/period |
C |
9 |
--- |
----- |
--- |
0 |
--- |
--- |
--- |
--- |
--| |
|
|
|
-------Segment Group 2------- |
C |
1 |
--- |
M |
|
1 |
--- |
--- |
--- |
--- |
--| |
|
Details of transport |
M |
1 |
|
M |
|
1 |
|
|
|
|
|
|
|
Reference |
C |
9 |
|
M |
|
9 |
|
|
|
|
|
|
|
Place/location identification |
C |
1 |
0 |
M |
|
9 |
|
|
|
|
|
|
|
Date/time/period |
C |
2 |
--- |
C |
--- |
2 |
--- |
--- |
--- |
--- |
--| |
|
|
|
-------Segment Group 3------- |
C |
9 |
--- |
M |
--- |
2 |
--- |
--- |
--- |
--- |
--| |
|
Name and address |
M |
1 |
|
M |
|
1 |
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
|
-------Segment Group 4------- |
C |
9 |
--- |
M |
--- |
2 |
--- |
--- |
--- |
| |
| |
|
Contact information |
M |
1 |
|
M |
|
1 |
|
|
|
| |
| |
|
|
Communication contact |
C |
9 |
--- |
C |
--- |
4 |
--- |
--- |
--- |
|-- |
--| |
|
|
|
-------Segment Group 5------- |
C |
999 |
--- |
M |
-1 |
9 |
--- |
--- |
--- |
| |
|
|
Equipment details |
M |
1 |
|
M |
|
1 |
|
|
|
| |
|
|
|
Measurements |
C |
9 |
--- |
M |
--- |
5 |
--- |
--- |
--- |
| |
|
|
|
|
-------Segment Group 6------- |
M |
999 |
--- |
M |
99 |
9 |
--- |
--- |
--- |
--- |
--| |
|
Consignment information |
M |
1 |
|
M |
|
1 |
|
|
|
|
| |
|
|
Handling instructions |
C |
1 |
|
D |
|
1 |
|
|
|
|
| |
|
|
Date/time/period |
C |
4 |
|
C |
|
2 |
|
|
|
|
| |
|
|
Place/location identification |
C |
4 |
|
C |
|
2 |
|
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
|
-------Segment Group 7------- |
C |
1 |
--- |
C |
|
0 |
--| |
|
|
|
| |
|
Details of transport |
M |
1 |
|
M |
|
1 |
| |
|
|
|
| |
|
|
Reference |
C |
9 |
--- |
C |
|
0 |
--| |
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
|
-------Segment Group 8------- |
C |
2 |
--- |
C |
|
2 |
--- |
--| |
|
|
| |
|
Name and address |
M |
1 |
|
M |
|
1 |
|
| |
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
|
|
| |
|
|
-------Segment Group 9------- |
C |
1 |
|
C |
|
0 |
--| |
| |
|
|
| |
|
Contact information |
M |
1 |
|
M |
|
1 |
| |
| |
|
|
| |
|
|
Communication contact |
C |
1 |
|
C |
|
0 |
--| |
| |
|
|
| |
|
|
Reference |
C |
1 |
|
C |
|
0 |
--- |
--| |
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
|
-------Segment Group 10----- |
M |
9 |
9- |
M |
9 |
9 |
--- |
--- |
--| |
|
| |
|
Goods item details |
M |
1 |
|
M |
|
1 |
|
|
| |
|
| |
|
|
Free text |
C |
2 |
|
C |
|
2 |
|
|
| |
|
| |
|
|
Package identification |
C |
1 |
|
C |
|
0 |
|
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
| |
|
|
-------Segment Group 11----- |
C |
9 |
9- |
C |
9 |
9 |
--- |
--| |
| |
|
| |
|
Split goods placement |
M |
1 |
|
M |
|
1 |
|
| |
| |
|
| |
|
|
Measurements |
C |
9 |
|
M |
|
2 |
--- |
--| |
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
|
| |
|
|
-------Segment Group 12----- |
M |
1 |
--- |
M |
--- |
--- |
--- |
--| |
| |
|
| |
|
Dangerous goods |
M |
1 |
|
M |
|
1 |
|
| |
| |
|
| |
|
|
Free text |
M |
9 |
|
M |
|
2 |
|
| |
| |
|
| |
|
|
Measurements |
M |
9 |
|
M |
|
1 |
|
| |
| |
|
| |
|
|
Place/location identification |
C |
99 |
|
C |
|
0 |
|
| |
| |
|
| |
|
|
Reference |
C |
9 |
|
C |
|
0 |
|
| |
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
| |
|
| |
|
|
-------Segment Group 13----- |
C |
99 |
|
C |
9 |
9 |
--| |
| |
| |
|
| |
|
Split goods placement |
M |
1 |
|
M |
|
1 |
| |
| |
| |
|
| |
|
|
Place/location identification |
C |
1 |
|
C |
|
1 |
| |
| |
| |
|
| |
|
|
Measurements |
C |
2 |
|
M |
|
2 |
--- |
--| |
--| |
--- |
--| |
|
|
Message trailer |
M |
1 |
|
|
|
|
|
|
|
|
|
|
1.2. Branching diagram (ERI notification message)
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 items details; HAN Handling instructions; LOC Place/location identification; MEA Measurements; NAD Name and address; PCI Package identification; RFF Reference; SGP Split goods placement; TDT Details of transport; UNH Message header; UNT Message trailer; SG Segment group; M Mandatory; C Conditional; Bases: UNTD98.B, PROTECT 1.0
1.3. 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 |
Mandatory Conditional |
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 |
|
|
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 |
|
|
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 |
|
C |
|
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 |
‘ERI12’, ERI Version 1.2 |
|
|
0068 |
|
O |
an..35 |
Common access reference |
The reference code 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 should 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 should be used. The transitional system should 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 |
|
|
4343 |
|
C |
an..3 |
Response type code |
AQ |
|
|
|
|
|
|
|
|
|
|
FTX (1) |
1 |
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 |
|
|
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 |
|
|
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) |
1 |
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 |
|
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 |
|
C |
an..3 |
Language, coded |
n.a. |
|
|
4447 |
|
C |
an..3 |
Text formatting, coded |
n.a. |
|
|
|
|
|
|
|
|
|
|
HAN(1) |
1 |
D |
|
|
|
|
|
C524 |
|
M |
|
HANDLING INSTRUCTIONS |
|
|
|
4079 |
|
M |
|
Handling instructions, coded |
Default ‘T’ T = Transit LLO = Loading LDI = Unloading TSP = Transit in the same port |
|
|
1131 |
|
C |
|
Code list qualifier |
n.a. |
|
|
3055 |
|
C |
|
Code list responsible agency, coded |
n.a. |
|
|
4078 |
|
C |
|
Handling instructions |
n.a. |
|
|
C218 |
|
C |
|
HAZARDOUS MATERIAL |
n.a. |
|
|
7419 |
|
C |
|
Hazardous material class code, identification |
n.a. |
|
|
1131 |
|
C |
|
Code list qualifier |
n.a. |
|
|
3055 |
|
C |
|
Code list responsible agency, coded |
n.a. |
|
|
7418 |
|
C |
|
Hazardous material class |
n.a. |
|
|
|
|
|
|
|
|
|
|
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. |
|
|
|
|
|
|
|
|
|
|
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. |
|
|
|
|
|
|
|
|
|
|
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 should 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. |
|
|
|
|
|
|
|
|
|
TDT |
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 UN/ECE 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 Part 2, Chapter 4.2.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 OFS or IMO indication, 8 digits for ERN indication and unique European vessel identification number |
|
|
1131 |
|
M |
an..3 |
Code list qualifier |
‘OFS’ for a Official Ship Number of CCNR system, see Part 2, Chapter 4.2.2 ‘IMO’ for an IMO-number, see Part 2, Chapter 4.2.3 ‘ERN’ for all other ships (Electronic Reporting International Number), see Part 2, Chapter 4.2.4 ‘ENI’ for a unique European vessel identification number, see Part 2, Chapter 4.2.5 |
|
|
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 Part 2, Chapter 4.2.12. 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 should be used. |
|
|
8281 |
|
|
an..3 |
Transport ownership |
n.a. |
|
|
|
|
|
|
|
|
|
TDT |
RFF (1) |
2 |
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 t 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) |
2 |
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) |
2 |
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 |
|
|
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) |
2 |
C |
|
REFERENCE |
Dimensions of the transport, the 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) |
2 |
M |
|
REFERENCE |
Dimensions of the transport, tonnage |
|
|
C506 |
|
M |
|
REFERENCE |
Reference |
|
|
1153 |
|
M |
an..3 |
Reference qualifier |
‘TON’ |
|
|
1154 |
|
M |
an..35 (n..5) |
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) |
2 |
C |
|
REFERENCE |
National voyage reference, Belgium |
|
|
C506 |
|
M |
|
REFERENCE |
Reference |
|
|
1153 |
|
M |
an..3 |
Reference qualifier |
‘GNB’ |
|
|
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) |
2 |
C |
|
REFERENCE |
National voyage reference, France |
|
|
C506 |
|
M |
|
REFERENCE |
Reference |
|
|
1153 |
|
M |
an..3 |
Reference qualifier |
‘GNF’ |
|
|
1154 |
|
M |
an..35 |
Reference number |
Government reference of France |
|
|
1156 |
|
|
an..6 |
Line number |
n.a. |
|
|
4000 |
|
|
an..35 |
Reference version number |
n.a. |
|
|
1060 |
|
|
an..6 |
Revision number |
n.a. |
|
|
|
|
|
|
|
|
|
TDT |
RFF (8) |
2 |
C |
|
REFERENCE |
National voyage reference, Germany |
|
|
C506 |
|
M |
|
REFERENCE |
Reference |
|
|
1153 |
|
M |
an..3 |
Reference qualifier |
‘GNG’ |
|
|
1154 |
|
M |
an..35 |
Reference number |
Government reference of Germany |
|
|
1156 |
|
|
an..6 |
Line number |
n.a. |
|
|
4000 |
|
|
an..35 |
Reference version number |
n.a. |
|
|
1060 |
|
|
an..6 |
Revision number |
n.a. |
|
|
|
|
|
|
|
|
|
TDT |
RFF (9) |
2 |
C |
|
REFERENCE |
National voyage reference, reserved 1 |
|
|
C506 |
|
M |
|
REFERENCE |
Reference |
|
|
1153 |
|
M |
an..3 |
Reference qualifier |
‘GN1’ |
|
|
1154 |
|
M |
an..35 |
Reference number |
Government reference, reserved 1 |
|
1 |
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) |
2 |
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 |
UN/ECE location code (Rec. 16), see Part 2, Chapter 4.2.13 |
|
|
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 Part 2, Chapter 4.2.15 |
|
|
1131 |
|
|
an..3 |
Code list qualifier |
n.a. |
|
|
3055 |
|
|
an..3 |
Code list responsible agency |
n.a. |
|
|
3222 |
|
|
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 Part 2, Chapter 4.2.14 |
|
|
1131 |
|
|
an..3 |
Code list qualifier |
|
|
|
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) |
2 |
C |
|
PLACE/LOCATION IDENTIFICATION |
Passage point that has already being 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 |
UN/ECE location code (Rec. 16) of the passage point (lock, bridge, traffic centre), see Part 2, Chapter 4.2.13 |
|
|
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. |
|
| ||||||