COMMISSION IMPLEMENTING REGULATION (EU) 2023/204
of 28 October 2022
laying down technical specifications, standards and procedures for the European Maritime Single Window environment pursuant to Regulation (EU) 2019/1239 of the European Parliament and of the Council
(Text with EEA relevance)
Article 1
Definitions
Article 2
Provisions for the harmonised interfaces
Article 3
Provisions for the maritime national single windows
Article 4
Other common services
Article 5
List of relevant information in the entry summary declaration
Article 6
Entry into force and application
ANNEX I
COMMON FUNCTIONALITIES OF THE GRAPHICAL USER INTERFACE AND CONTENT OF THE TEMPLATES OF THE HARMONISED DIGITAL SPREADSHEETS
List of ships This functionality shall allow consultation of:
A filter shall be provided to search the list by the following criteria:
|
||||||||||||
List of port calls The list of port calls shall be accessible for a certain period of time as specified in the national data retention rules. The following information shall at least be available: port of call, visit ID, identification of the ship, estimated and actual arrival and departure time of the ship. Using these criteria a filter shall be provided to search the list. |
||||||||||||
Port call overview The selected port call shall contain the information of the status of formalities and responses from authorities related to that port call including the clearance model (systematic or silent) applied by the maritime National Single Window. |
||||||||||||
Creation of a port call This functionality shall allow to create a port call by selecting a ship from the functionality ‘list of ships’ or by filling manually the ship’s identification information and the port of call from the information retrieved by the maritime national single window from the Common Location Database. With a creation of the port call, a Visit ID linked to the selected ship and to the port of call shall be provided. |
||||||||||||
Provision of a new formality This functionality shall allow declarants to provide a new formality for the port call selected from the list of port calls. In the case a ship’s identification information and particulars or records on ship reporting exemptions is required for the fulfilment of reporting obligations, the maritime National Single Window shall make available the relevant information from the EMSWe Ship Database, or alternatively from another relevant database in the graphical user interface by way of pre-filling the relevant fields. In case a location or port facility code is required for the fulfilment of reporting obligations, the maritime National Single Window shall make available the relevant information from the Common Location Database in the graphical user interface. In the case information on dangerous and polluting goods is required for the fulfilment of reporting obligations, the maritime National Single Window shall make available the relevant information from the Common Hazmat Database in graphical user interface by way of:
|
||||||||||||
Uploading information from spreadsheets When providing or updating one or more formalities, declarants shall be able to upload information from digital spreadsheets. The maritime National Single Window shall ensure that the version of the spreadsheet template is compliant to the latest version available or, during a transition period where a new version of the templates is issued, to one of the two latest consecutive versions of the spreadsheet templates. As a consequence, a version of the templates is phased out at the end date of the transition period. After uploading the spreadsheet file, the maritime National Single Window shall check that the format, cardinality and business rules of the data elements comply with those defined in the EMSWe data set. If a spreadsheet is not compliant with the versioning rules or with the requirements of the EMSWe data set, the maritime National Single Window shall reject the spreadsheet information and shall provide an error message with a clear indication of the reasons of the check failure. Following the successful passing of the maritime National Single Window checks, the data elements extracted from the spreadsheet shall replace previously filled-in data elements in the graphical user interface. Before submission, the graphical user interface shall provide the possibility to read, review and correct the information extracted from that spreadsheet. |
||||||||||||
Re-using existing formalities When preparing new formalities for a port call, declarants shall be able to re-use the available content of formalities related to the same ship which they have previously submitted to the same maritime National Single Window. |
||||||||||||
Save draft formalities Declarants shall be able to save draft formalities before submission. |
||||||||||||
Submission of formalities Declarants shall be able to submit formalities to the maritime National Single Window. Following the submission of the information, the maritime national single window shall display the results of the semantic checks performed at Member State level. |
||||||||||||
Management of formalities This functionality shall allow declarants to consult and update their previously submitted or draft formalities. When allowed, they shall be able to withdraw or invalidate their individual formalities. All formalities that have been submitted using the harmonised reporting interface module shall be also available in the graphical user interface. The graphical user interface shall display information (date and time of submission) of all such formalities, including responses from authorities. |
||||||||||||
Cancellation of a port call Declarants shall be able to cancel their previously created port call and withdraw or invalidate their previously submitted formalities associated to that port call. |
||||||||||||
Configuration of personal settings Declarants shall be able to configure additional personal information set at national level that is not managed by the EMSWe user registry and access management system. |
Content of spreadsheet templates
ANNEX II
TECHNICAL SPECIFICATIONS FOR MAKING ARRIVAL AND DEPARTURE TIMES PUBLICLY AVAILABLE
1.
Interface’s requirements
2.
Data set to be made publicly available
Category |
Information to provide |
Vessel information |
Ship IMO number Ship name |
Voyage Information |
Port of call, coded Date and time of arrival – estimated in local time Date and time of departure – estimated in local time |
Arrival Notification details |
Date and time of arrival – actual in local time |
Departure Notification details |
Date and time of departure – actual in local time |
Port call status |
Status of the port call (with values: Expected Arrival, Arrived, Departed, Cancelled) |
3.
Specifications for user to system interaction
3.1.
Search function
3.2.
Column sorting
4.
System to system interaction
5.
Non-functional requirements
5.1.
Web design
5.2.
Languages
ANNEX III
HARMONISED STRUCTURE FOR THE SUPPORT WEBSITE OF THE MARITIME NATIONAL SINGLE WINDOW
1.
Common functionalities of the online support website
1.1.
Language selection
1.2.
Search function
2.
Information structure of the online support website
3.
Accessibility
ANNEX IV
UNIFORM FORMAT FOR internet ADDRESSES
ANNEX V
TECHNICAL SPECIFICATIONS, STANDARDS AND PROCEDURES FOR THE SETTING UP OF THE EMSWE SHIP DATABASE
1.
EMSWe Ship Database overview
2.
Interfaces and services of the EMSWe Ship Database
2.1.
System to System interface
2.1.1.
Announcement service
2.1.2.
Ship Information Notification service
2.2.
Web interface
3.
Procedures for updating the information of EMSWe Ship Database
Ship identification information and particulars
Ship reporting exemption information
4.
Minimum system performance requirements
Timeframes for Data Availability: The EMSWe Ship Database shall be supported by data communication links and networks that allow them to transfer information between the two systems within 1 minute. |
Timeframes for Data Storage: The list of ship identification information and particulars and ship reporting exemptions shall be available in the EMSWe Ship Database without any time limitation. |
System Availability Requirements: The EMSWe Ship Database shall be maintained in operation at a minimum of 99 % over a period of one year, with the maximum permissible period of interruption being 12 hours. The information of the EMSWe Ship Database shall be recoverable to the fullest extent possible after a downtime period. Member States shall be informed in the event of a failure or a scheduled interruption. |
5.
Minimum system security measures
Identification: A reliable identification mechanism shall be implemented to uniquely identify the users of the EMSWe Ship Database with a unique user ID. |
Authentication : Authentication process for the system to system interface of the EMSWe Ship Database shall be based on recognised authentication methods by way of implementing 2-way SSL. For web user interface, users shall authenticate with a set of credentials. |
Authorisation : Users shall be authorised by applying access control measures to access the interfaces of the EMSWe Ship Database. Each access shall be recorded. Authorisations shall be reviewed on a regular basis. |
Traceability and accountability : The EMSWe Ship Database shall ensure the non-repudiation of actions performed by users through its interfaces. For this purpose, the EMSWe Ship Database shall keep track of any access, events and modifications of its data. The user identification, the time stamp and the action performed shall be recorded per each event. |
Integrity : The EMSWe Ship Database shall perform system integrity checks that prevent malicious events that may compromise its functionalities. |
ANNEX VI
TECHNICAL SPECIFICATIONS, STANDARDS AND PROCEDURES FOR THE SETTING UP OF THE COMMON LOCATION DATABASE
1.
Common Location Database overview
2.
Interfaces and services of the Common Location Database
2.1.
System to System interface
2.1.1.
Announcement service
3.
Procedures for updating the information of the Common Location Database
4.
Minimum system performance requirements
Timeframes for Data Availability: The Common Location Database shall be supported by data communication links and networks that allow them to transfer information between the two systems within 1 minute. |
Timeframes for Data Storage: The active location and port facility codes shall be available in the Common Location Database without any time limitation. Deactivated location and port facility codes shall be archived in the Common Location Database for a minimum of 5 years. |
System Availability Requirements: The Common Location Database shall be maintained in operation at a minimum of 99 % over a period of one year, with the maximum permissible period of interruption being 12 hours. The information of the Common Location Database shall be recoverable to the fullest extent possible after a downtime period. Member States shall be informed in the event of a failure or a scheduled interruption. |
5.
Minimum system security measures
Identification: A reliable identification mechanism shall be implemented to uniquely identify the users of the Common Location Database with a unique user ID. |
Authentication : Authentication process for the system to system interface of the Common Location Database shall be based on recognised authentication methods by way of implementing 2-way SSL. For web user interface, users shall authenticate with a set of credentials. |
Authorisation : Users shall be authorised by applying access control measures to access the interfaces of the Common Location Database. Each access shall be recorded. Authorisations shall be reviewed on a regular basis. |
Traceability and accountability : The Common Location Database shall ensure the non-repudiation of actions performed by users through its interfaces. For this purpose, the Common Location Database shall keep track of any access, events and modifications of its data. The user identification, the time stamp and the action performed shall be recorded per each event. |
Integrity : The Common Location Database shall perform system integrity checks that prevent malicious events that may compromise its functionalities. |
ANNEX VII
TECHNICAL SPECIFICATIONS, STANDARDS AND PROCEDURES FOR THE SETTING UP OF THE COMMON HAZMAT DATABASE
1.
Common Hazmat Database overview
2.
Interfaces of the Common Hazmat Database
2.1.
System to System interface
2.1.1.
Announcement service
2.2.
Web interface
3.
Procedures for updating the Common Hazmat Database
4.
Minimum system performance requirements
Timeframes for Data Availability: The Common Hazmat Database shall be supported by data communication links and networks that allow them to transfer information between the two systems within 1 minute. |
Timeframes for Data Storage: The information on dangerous and polluting goods shall be available in the Common Hazmat Database without any time limitation. |
System Availability Requirements: The Common Hazmat Database shall be maintained in operation at a minimum of 99 % over a period of one year, with the maximum permissible period of interruption being 12 hours. The information of the Common Hazmat Database shall be recoverable to the fullest extent possible after a downtime period. Member States shall be informed in the event of a failure or a scheduled interruption. |
5.
Minimum system security measures
Identification: A reliable identification mechanism shall be implemented to uniquely identify the users of the Common Hazmat Database with a unique user ID. |
Authentication : Authentication process for the system to system interface of the Common Hazmat Database shall be based on recognised authentication methods by way of implementing 2-way SSL. For web user interface, users shall authenticate with a set of credentials. |
Authorisation : Users shall be authorised by applying access control measures to access the interfaces of the Common Hazmat Database. Each access shall be recorded. Authorisations shall be reviewed on a regular basis. |
Traceability and accountability : The Common Hazmat Database shall ensure the non-repudiation of actions performed by users through its interfaces. For this purpose, the Common Hazmat Database shall keep track of any access, events and modifications of its data. The user identification, the time stamp and the action performed shall be recorded per each event. |
Integrity : The Common Hazmat Database shall perform system integrity checks that prevent malicious events that may compromise its functionalities. |
ANNEX VIII
INFORMATION IN THE ENTRY SUMMARY DECLARATION TO BE MADE AVAILABLE TO THE MARITIME NATIONAL SINGLE WINDOW
UCC DE No |
Data element/class name Data sub-element/sub-class name |
EMSWe Data Set No |
11 03 000 000 |
Goods item number |
DE-048-01 |
12 02 008 000 |
Additional information, Code |
DE-048-12 |
12 02 009 000 |
Additional information, Text |
DE-048-13 |
12 03 001 000 |
Supporting document, Reference number |
DE-048-14 |
12 03 002 000 |
Supporting document, Type |
DE-048-15 |
12 05 001 000 |
Transport document, Reference number |
DE-056-02 |
12 05 002 000 |
Transport document, Type |
DE-056-03 |
12 08 000 000 |
Reference number/UCR |
DE-047-14 |
13 02 016 000 |
Consignor, Name |
DE-058-01 |
13 02 017 000 |
Consignor, Identification number |
DE-058-02 |
13 02 028 000 |
Consignor, Type of person |
DE-058-03 |
13 02 018 023 |
Consignor, Address, Street |
DE-058-05 |
13 02 018 024 |
Consignor, Address, Street additional line |
DE-058-06 |
13 02 018 025 |
Consignor, Address, Number |
DE-058-07 |
13 02 018 026 |
Consignor, Address, P.O. Box |
DE-058-08 |
13 02 018 027 |
Consignor, Address, Sub-division |
DE-058-11 |
13 02 018 020 |
Consignor, Address, Country |
DE-058-12 |
13 02 018 021 |
Consignor, Address, Postcode |
DE-058-09 |
13 02 018 022 |
Consignor, Address, City |
DE-058-10 |
13 02 029 015 |
Consignor, Communication, Identifier |
DE-058-13 |
13 02 029 002 |
Consignor, Communication, Type |
DE-058-14 |
13 03 016 000 |
Consignee, Name |
DE-059-01 |
13 03 017 000 |
Consignee, Identification number |
DE-059-02 |
13 03 028 000 |
Consignee, Type of person |
DE-059-03 |
13 03 018 023 |
Consignee, Address, Street |
DE-059-05 |
13 03 018 024 |
Consignee, Address, Street additional line |
DE-059-06 |
13 03 018 025 |
Consignee, Address, Number |
DE-059-07 |
13 03 018 026 |
Consignee, Address, P.O. Box |
DE-059-08 |
13 03 018 027 |
Consignee, Address, Sub-division |
DE-059-11 |
13 03 018 020 |
Consignee, Address, Country |
DE-059-12 |
13 03 018 021 |
Consignee, Address, Postcode |
DE-059-09 |
13 03 018 022 |
Consignee, Address, City |
DE-059-10 |
13 03 029 015 |
Consignee, Communication, Identifier |
DE-059-13 |
13 03 029 002 |
Consignee, Communication, Type |
DE-059-14 |
13 13 016 000 |
Notify party, Name |
DE-062-01 |
13 13 017 000 |
Notify party, Identification number |
DE-062-02 |
13 13 028 000 |
Notify party, Type of person |
DE-062-03 |
13 13 018 023 |
Notify party, Address, Street |
DE-062-04 |
13 13 018 024 |
Notify party, Address, Street additional line |
DE-062-05 |
13 13 018 025 |
Notify party, Address, Number |
DE-062-06 |
13 13 018 026 |
Notify party, Address, P.O. box |
DE-062-07 |
13 13 018 027 |
Notify party, Address, Sub-division |
DE-062-10 |
13 13 018 020 |
Notify party, Address, Country |
DE-062-11 |
13 13 018 021 |
Notify party, Address, Postcode |
DE-062-08 |
13 13 018 022 |
Notify party, Address, City |
DE-062-09 |
13 13 029 015 |
Notify party, Communication, Identifier |
DE-062-12 |
13 13 029 002 |
Notify party, Communication, Type |
DE-062-13 |
13 14 031 000 |
Additional supply chain actor, Role |
DE-057-01 |
13 14 017 000 |
Additional supply chain actor, Identification number |
DE-057-02 |
15 03 000 000 |
Estimated date and time of arrival(1) |
DE-022-03 |
16 05 020 000 |
Place of delivery, Country |
DE-047-08 |
16 05 037 000 |
Place of delivery, Location |
DE-047-09 |
16 13 036 000 |
Place of loading, UN/LOCODE |
DE-047-01 |
16 13 020 000 |
Place of loading, Country |
DE-047-02 |
16 13 037 000 |
Place of loading, Location |
DE-047-03 |
16 14 036 000 |
Place of unloading, UN/LOCODE |
DE-047-04 |
16 14 020 000 |
Place of unloading, Country |
DE-047-05 |
16 14 037 000 |
Place of unloading, Location |
DE-047-06 |
16 16 037 000 |
Place of acceptance, Location |
DE-047-11 |
18 03 000 000 |
Total gross mass |
DE-047-16 |
18 04 000 000 |
Gross mass |
DE-048-03 |
18 05 000 000 |
Description of goods |
DE-048-04 |
18 06 003 000 |
Packaging, Type of packages |
DE-048-10 |
18 06 004 000 |
Packaging, Number of packages |
DE-048-09 |
18 06 054 000 |
Packaging, Shipping Marks |
DE-048-08 |
18 07 055 000 |
Dangerous goods, UN number |
DE-049-03 |
18 08 000 000 |
CUS code |
DE-048-07 |
18 09 056 000 |
Commodity code, Harmonized System sub-heading code |
DE-048-05 |
18 09 057 000 |
Commodity code, Combined nomenclature code |
DE-048-06 |
19 01 000 000 |
Container indicator |
DE-047-15 |
19 03 000 000 |
Mode of transport at the border |
DE-014-03 |
19 07 063 000 |
Transport equipment, Container identification number |
DE-051-01 |
19 07 064 000 |
Transport equipment, Container size and type identification |
DE-051-13 |
19 07 065 000 |
Transport equipment, Container packed status |
DE-051-03 |
19 08 017 000 |
Active border transport means, Identification number |
DE-005-03 |
19 08 067 000 |
Active border transport means, Type of means of transport |
DE-005-16 |
19 09 017 000 |
Passive border transport means, Identification number |
DE-065-04 |
19 09 067 000 |
Passive border transport means, Type of means of transport |
DE-048-11 |
19 10 068 000 |
Seal, Number of seals |
DE-051-04 |
19 10 015 000 |
Seal, Identifier |
DE-051-05 |