ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
Expert GroupCR numberCR versionCR SupplierTitle / short descriptionIssue date
[dd.mm.yyyy]
Approved / Withdrawn / RejectedDate of decision
[dd.mm.yyyy]
Description of changeAffected parts of the standard Implemented in standard versionComment
2
ERI001AcceptedISRS corrections1.0
3
ERI002NLISRS usage of PAS message01.06.2004AcceptedAdd a section describing the usage of ERINOT messages when exchanging notification between RIS authorities1.0
4
ERI003NLHAN segment01.06.2004AcceptedAdd an extra HAN-Segment (SRS message specification)1.0
5
ERI004NLXML adaption01.06.2004AcceptedThe ERI working group will adapt XML as a an extra supported message type that can be used for exchange of voyage data between authorities1.0
6
ERI005NLUnique Hull ID01.06.2004AcceptedAll ships in inland waterways become a unique number (European Identification Number) which they are using for electronic reporting1.0
7
ERI006BEAir Draught01.06.2004AcceptedThe air draught will be included in the SRS 1.0 message for electronic reporting1.0
8
ERI007BEContainer Type01.06.2004AcceptedThe “container type” will be included in the SRS 1.0 message for electronic reporting1.0
9
ERI008SKCorrection in the XSD of the ERINOT 1.2 message (v1.2d_draft)18.03.2009AcceptedCorrection ERINOT XSD1.0
10
ERI009VTT EGShip Type Code VTT06.05.2009RejectedNew ERI (sub-)codes are proposed1.0
11
ERI010ATAlignment of vessel types, based on UN Recommendation 2825.05.2009AcceptedAlignment Vessel Types1.0
12
ERI011SKCorrection in the XSD of the ERINOT 1.2 message (v1.2e_draft)21.07.2009AcceptedCorrection ERINOT XSD1.0
13
ERI012ERI-SecretariatSubstitution of the Term of Reference ERI07.05.2010AcceptedSubstitution of the Term of Reference ERI1.0
14
ERI013ERI-SecretariatSubstitution of maintenance procedures reference data25.05.2010AcceptedSubstitution of maintenance procedures reference data1.0
15
ERI014SKCorrection in the XSD of the ERINOT 1.2 message (v1.2f_draft)03.09.2009AcceptedRemove message type POS VER in the XSD1.0
16
ERI015ERI-SecretariatModification of the length parameters of the data-element NSTR-code09.01.2011AcceptedModification of the length parameters of the data-element NSTR-code1.0
17
ERI016ERI-SecretariatAmendments to Annex 2 of the ERI Terms of Reference02.11.2011AcceptedAmendments to Annex 2 of the ERI Terms of Reference1.0
18
ERI017ERI-SecretariatCorrection in the XSD of the ERINOT 1.2 message (v1.2h_draft)09.11.2011AcceptedCorrection ERINOT XSD - ContainerType1.0
19
ERI018NLAmendments to PAXLST MIG01.02.2012AcceptedAmendments to PAXLST MIG1.0
20
ERI019ERI-SecretariatAmendments DGS segment of the ERINOT12.10.2012AcceptedAmendments DGS segment of the ERINOT1.0
21
ERI020HUAmendments to PAXLST MIG14.11.2012AcceptedAmendments to PAXLST MIG1.0
22
ERI021ERI-SecretariatAmendments to UN Recommendation 2802.03.2013AcceptedAmendments to UN Recommendation 281.0
23
ERI022ERI-SecretariatAmendments ADN table in the ERDMS29.04.2014AcceptedAmendments ADN table in the ERDMS1.0
24
ERI023ERI-SecretariatSupport of national languages in ERDMS29.04.2014AcceptedSupport of national languages in ERDMS1.0
25
ERI024ATChange of data elements30.04.2014RejectedChange of data elements1.0
26
ERI025ERI-SecretariatAmendments to the RIS Index Encoding Guide09.01.2011AcceptedAmendments to the RIS Index Encoding Guide1.0
27
ERI026ERI-SecretariatAmendments to Annex 2 of the ERI Terms of Reference01.11.2014AcceptedAmendments to Annex 2 of the ERI Terms of Reference1.0
28
ERI027ERDMS Data ManagerAdopt tank container types in all ERI related systems01.09.2014AcceptedAdopt tank container types in all ERI related systems1.0
29
ERI028SKUse of XSD enumerations in the ERDMS09.10.2014AcceptedUse of XSD enumerations in the ERDMS1.0
30
ERI029SKChange of XSD type for "Tonnage"19.11.2014RejectedChange of XSD type for "Tonnage"1.0
31
ERI030BTBExtend UN recommendation 28 to add new vessel type codes02.11.2011AcceptedThe reason to add this new code is to ensure that these vessels can configure their AIS correct and report correctly their voyage by means of electronic reporting.
32
ERI031IVS 90, NLChange “Tonnage” format in messages from N.5 to N.631.03.2016Accepted
This change is important to bring the message definitions (max format) of tonnages in line with the requirements of the operational RIS users/systems and the definitions from the Hull database.
ERI XSD
33
ERI032Rijkswaterstaat, NLUpdate ERI Encoding Guidle to recognize reporting application08.11.2016Pending
This encoded information can be used to identify the reporting application more easily in national infrastructure and in particular the mailbox services (besides the specification of EU164), for statistical purposes and grouping of messages in the various mailboxes.ERI Encoding Guide
34
ERI033Rijkswaterstaat, NLERINOT: Amendment Of Language Of Dangerous Goods26.04.2017Accepted11.05.2017It is proposed that all information exchange of dangerous goods between authorities will be done in the English language.ERI Encoding Guide
35
ERI034ERI-SecretariatERIVOY: End Of Voyage25.10.2017AcceptedThe submitter of a message for electronic ship reporting can provide information related to a voyage to various actors but the end of a voyage cannot be notified. It is proposed to enable the possibility to indicate the end of a voyage. Therefore it is proposed to include a new function code which indicates the end of a voyage.
36
ERI035ERI-SecretariatERINOT: Adding Verified Gross Mass (VGM)25.10.2017AcceptedThe proposal is to add an additional MEA segment to the Group 13, this MEA segment should contain preferable the Verified Gross Mass or the Gross Mass.
37
ERI036Germany
ERINOT: Value range of new LNG indicator field31.5.2019Accepted06.06.2019Instead of the fixed value “Powered by LNG” it is proposed to use a binary value in TDT RFF (7) 1154 to enable an explicit specification, whether the vessel/convoy is powered by LNG or not
38
ERI037Germany and FranceERINOT: Interruption and restart of voyages21.5.2019Accepted06.06.2019The proposal foresees to modify the ERI standard so that both these events (interruption and restart of voyges) can be communicated when implementing electronic voyage reporting between authorities.
39
ERI038RIS COMEX PartnersPAXLST: Amendments RIS COMEX19.11.2019Accepted26.11.2019The proposal foresees to add additonal data fields to PAXLST to fulfil reporting obgligations idenfied by the COMEX project. PAXLST XSD
40
ERI039RIS COMEX PartnersERINOT: Nominal Engine Power11.11.2019Pending
The proposal foresees to add a new simple type item “NominalPower” to the “Vessel” information in the section specifying the “Barges” to cover the required data field "Total engine power used for forward propulsion".ERINOT XSD
41
ERI040RIS COMEX Partners, SWINg ProjectERIVOY: Activity and ETD at Route Points25.11.2019Accepted26.11.2019The Romanian Voyage Request foresees for cargo and passenger transports to report all stopping points including timing and location information as well as the function of the stopping point. These data items are also required by the Belgian project SWINg for safety reasons (e.g. bunkering & de-gassing) and in order to optimize the planning of the authorities.
ERIVOY XSD
42
ERI041SWINg ProjectERINOT: Add MMSI of a barge as extra identification25.11.2019Pending
The proposal suggests to add an extra data element “MMSI” to “Barge” with representation n9.ERINOT XSD
43
ERI042SWINg ProjectERINOT: Change InvoiceNumber into VAT number 25.11.2019Pending
The proposal suggests to replace InvoiceNumber by the name VAT Number to avoid misleading.ERINOT XSD
44
ERI043SWINg ProjectERINOT: Inert gas indication for tank vessels25.11.2019Pending
The proposal foresees to add an indication whether an inert gas is in the tanks of a tank vesselERINOT XSD
45
ERI044SWINg ProjectERINOT: Additional emergency phone number for a vessel25.11.2019Pending
It is proposed to add a data field for an emergency phone number for a vessel, in order to reach the captain of the vessel (even when he is not on board) in case of emergency situations.ERINOT XSD
46
ERI045SWINg ProjectERINOT: Vessel operator email and telephone25.11.2019Pending
Use "MessageSender" attributes to contact the party that will operates the vessel via e-mail address or telephone number, in order to ensure operational excellence for all parties involved. This e.g. to send a voyage permit.ERINOT XSD
47
ERI046SWINg ProjectERINOT: Fuel type indicator25.11.2019Pending
Instead of the fixed value “Powered by LNG”, “Powered by Hydrogen”, … it is proposed to use a code value in TDT RFF (7) 1154 to enable an explicit specification, by which fuel type the vessel/convoy is powered.ERINOT XSD
48
ERI047V1RIS COMEX PartnersERINOT: Previous vessel name and nationality11.12.2019Pending
In order to enable reporting of the DAVID FORMS by the means of ERI, 2 new simple type items “PreviousVesselName” and PreviousNationality” are proposed to be added to the section “TransportDetails.ERINOT XSD
49
ERI048V2RIS COMEX PartnersPAXLST: Additional visa information11.12.2019Withdrawn
In order to enable reporting of the DAVID FORMS by the means of ERI,the proposal suggests that visa related information can be specified in the section “Documents” under a new complex type item “Visa” including “TypeOfVisa”, “VisaNumber”, “Issuing Country” and “VisaExpiryDate”.PAXLST XSD
50
ERI049V1RIS COMEX PartnersCargo Type Code and Good Items Structure ERINOT10.06.2020Pending
In order to exchange voyage information between various authorities the ERINOT-message is used. Based on a mapping process of the reporting requirements found by the project RIS COMEX and the standardized ERI-messages a number of data fields was identified that is currently not covered by any of the ERI-messages. The following ERINOT related missing data field was identified:ERINOT XSD
51
ERI050V1Germany
Remarks, findings, proposals, amendments in ERINOT XML draft 1.3
14.10.2020PendingUpdate of ERINOT XSD 1.3 draftERINOT XSD
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100