Appendix B to Tender Specifications

Transcription

1 Ref. Ares(2015) /08/2015 Appendix B to Tender Specifications Enclosure 5 Technical documentation for scenario 2 - Link to SSN Central Hazmat Database Page 1 of 9

2 TABLE OF CONTENTS 1 Overview of the Central Hazmat Database Background Users Functional uses Data flows and links Access Content Services offered by CHD... 9 Page 2 of 9

3 1 Overview of the Central Hazmat Database 1.1 Background The SSN Group and the High Level Steering Group on SSN have agreed on the development and maintenance of a central database for HAZMAT information that have to be notified and exchanged in accordance with the VTMIS Directive and the RFD. This database is referred to in this document as the Central HAZMAT Database (CHD). The overall objective of the CHD is to: Improve the data quality of HAZMAT notifications to SSN, Minimise the administrative burden for the reporting parties when submitting the HAZMAT information to the NSW, and Support the MS emergency response services by providing specialised information for the response to incidents involving chemical substances. The CHD will be provided as a service of the Central SafeSeaNet system, which may be used by National SSN systems as well as NSW systems. 1.2 Users The CHD should serve the needs of: Industry stakeholders (manufacturers, shippers, freight forwarders, logistics companies) responsible for providing the Material Safety Data Sheets (MSDSs) to the ship reporting parties, Reporting parties (masters, ship agents, and ship operators) responsible for the completeness and accuracy of the HAZMAT information transmitted to the NSW, Relevant MS authorities (SSN NCAs, single window, port, maritime, security and port state control authorities) responsible for receiving, validating and processing HAZMAT information transmitted by the reporting parties, Emergency services of the MS responsible for providing effective response to maritime incidents to minimise loss of life, damage to property and prevention of pollution, and EMSA services responsible for validating the data quality of the information exchanged between MS through SSN. 1.3 Functional uses The objectives of the CHD are achieved if it is used as a and verification tool during the HAZMAT reporting process both at national and central level: a. As a : The users can search for the correct HAZMAT details. This can be done either by using specific identifiers (code or convention textual, UN Number, IMO class), or by inputting the product s textual, how it is carried (bulk or packaged) and, when applicable, type of product (liquid, gas or solid) and browse the structure of the database until the correct identification of the relative code or convention is found, as shown in Figure 1. Page 3 of 9

4 Liquid Oil Chemicals or noxious MARPOL Annex I MARPOL Annex II/IBC Bulk Gas IGC Mode of Carriage Solid IMSBC Packaged IMDG Figure 1 - Retrieving Information from the CHD application The administrative burden of the reporting party can be minimised if the CHD is integrated in the National Single Window (NSW). Once the reporting party inputs an identifier (e.g. textual or the UN number), the NSW would automatically fill in the remaining static data elements. Competent authorities and EMSA services can download from the CHD hazmat, information needed to respond to incidents involving ships carrying HAZMAT cargo. b. For verification: Competent authorities and EMSA services can cross-check and validate the correctness of HAZMAT data notified to SSN by the national SSN and NSW systems. 1.4 Data flows and links The information flow between the users of the CHD is presented in Figure 2 below: Page 4 of 9

5 Industry stakeholders (manufacturers, shippers, freight forwarders, logistics companies) Reporting party (ship agent, operator or master) verification National SSN/ National Single Window verification update Central SSN Central HAZMAT Database (CHRD) Reporting verification OTHER MEBER STATES National SSN/ National Single Window Reporting and Exchange of information Figure 2 - Information flow 1.5 Access The CHD is made available to the users via: EMSA maritime applications portal (MAP), A public site, and System-to-system interface (see section 3 below) 2 Content The CHD will include a comprehensive list of all HAZMAT that have to be notified in accordance with the VTMIS Directive. The content of the CHD is introduced in the table next page. Page 5 of 9

6 No. Data element Type Leng th 1 DG classification 2 Textual 3 Mode of Carriage 4 Type of Product carried in bulk 5 IMO hazard class(*) Mandato ry or Optional Description 1 Attribute contains the information in which IMO Code(s) DG must be declared Text The textual is a mandatory field but its content is derived from the appropriate IMO Code and Conventions 1 Depending on the relevant IMO code or convention. 0-1 Depending on the relevant IMO code or convention. Text In accordance with IMDG, IBC, and IMSBC codes 6 UN number Text UN number of HAZMAT product in accordance with the IMO Codes 7 Packing group(*) 8 Subsidiary risks(*) Enum 1 Values as appropriate and as defined in IMDG Text list 9 Flashpoint Decimal List range or Any risks in addition to the class to which dangerous goods are assigned; and which is determined by a requirement to have a subsidiary risk. A dangerous good may have up to 5subsidiary risks. The temperature in degrees Celsius at which a liquid will give off enough flammable vapour to be ignited. (Note: In the IMDG list this is IMO Codes and Conventions, including possible IMDG IBC IMSBC IGC Marpol Annex 1 IMDG IBC IMSBC IGC MARPO L_ANNE X1 Proper Shipping Name Product name Bulk cargo Shipping Name Produ ct Name Name of Oil Packaged Bulk Bulk Bulk Bulk 1 to 9 and relevant subclasses and divisions (e.g. 1.1F) 4 digits "I", "II", "III", - Y (e.g. See SP204, 6.1/8 etc) Y Liquid - Chemic als or noxious S, P, S/P Solid Gas Liquid - Oil B, A and B Page 6 of 9

7 No. Data element Type Leng th Mandato ry or Optional Description IMO Codes and Conventions, including possible IMDG IBC IMSBC IGC Marpol Annex 1 contained within the Properties and Observations column). 10 Marine Pollutant(*) value The code value defined in MARPOL Annex III and IMDG. (Note: In the IMDG list this is contained within the Subsidiary Risks column). P, - Error! Bookmark not defined. 11 Pollution category(*) The code defined in MARPOL Annex II and IBC. "X", "Y", "Z", "OS" 12 EmS(*) 0-2 list Emergency response procedures for ships carrying dangerous goods. Two are possible: Fire (F) and Spillage (S). F-A to F-J S-A to S-Z 13 Additional Information Text Any additional information regarding dangerous and polluting goods on-board (Properties and Observations in the IMDG list) Y 14 MAR-CIS Access button 0-1 access to MAR-CIS 2 product datasheet Y Y Y 15 MAR-CIS data sheet availability Binary 1 Code: TRUE or FALSE Y Y Y 16 HazmatID 1 Composed as follows: Y Y Y Y Y a. the first part will indicate the relevant IMO Convention or Code of the product by using the abbreviation of the code (IMDG, IMSBC, IBC, etc). b. The following digits will indicate the UN number, if available. If a UN number is unavailable, as in the case of IBC products, 0000 is used. Page 7 of 9

8 No. Data element Type Leng th Mandato ry or Optional Description IMO Codes and Conventions, including possible IMDG IBC IMSBC IGC Marpol Annex 1 c. The last digits will refer to the sequence number of the product. Page 8 of 9

9 3 Services offered by CHD The CHD shall be made available via system-to-system interface to other systems, including National Single Window system (e.g. via SOAP web services). These system-to-system services will include: a) Push automatically updates and changes in the CHD; b) Transmission of a list of HAZMAT products defined in a request, for example the list of UN Numbers and mode of carriage for the IMDG; Page 9 of 9