Official Journal of the European Union

COMMISSION REGULATION (EC) No 416/2007

of 22 March 2007

concerning the technical specifications for Notices to Skippers as 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 COMMISSION OF THE EUROPEAN COMMUNITIES,

Having regard to the Treaty establishing the European Community,

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 thereof,

Whereas:

In accordance with Article 1 of Directive 2005/44/EC, River Information Services (RIS) shall be developed and implemented in a harmonised, interoperable and open way.

In accordance with Article 5 of Directive 2005/44/EC, technical specifications for Notices to Skippers shall be defined.

The technical specifications for Notices to Skippers shall be based on the technical principles set out in Annex II to the Directive.

In accordance with Article 1(2) of Directive 2005/44/EC, the technical specifications shall take due account of the work carried out by relevant international organisations.

They shall also take due account of the work carried out by the expert group on Notices to Skippers which is composed of representatives of the competent authorities for the implementation of Notices to Skippers and official members from other governmental bodies as well as observers from the industry.

The technical specifications, which are the subject of this Regulation, correspond to the current technical 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 in accordance with Article 5(2) of Directive 2005/44/EC. Amendments to the technical specifications shall take due account of the work carried out by the expert group on Notices to Skippers.

The draft technical specifications have been examined by the Committee referred to in Article 11 of Directive 2005/44/EC.

The measures provided for in this Regulation are in accordance with the opinion of the Committee referred to in Article 11 of Directive 2005/44/EC.

HAS ADOPTED THIS REGULATION:

Article 1

This Regulation defines the technical specifications for Notices to Skippers. The technical specifications are set out in the Annex to this Regulation.

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.

(1) OJ L 255, 30.9.2005, p. 152.

ANNEX

Notices to Skippers

TABLE OF CONTENTS

1. Introduction

2. Data standard

3. Water level information

4. Way of distribution

5. Procedure for changes in the reference tables and the XML scheme of Notices to Skippers

6. Structure of the messages and coding in XML-format

6.1. Structure of the Notices to Skippers

6.1.1. General

6.1.2. XML definition overview

6.1.3. Explanation of tags

6.1.4. Explanation of codes

6.1.4.1. Subject codes assigned to the Notices to Skippers

6.1.4.2. Explanation of ice codes

6.1.4.3. Encoding of limitation periods

Appendix: Specifications of examples for the implementation of the Notices to Skippers

Reference tables

XML scheme (XML_V2_7.XSL)

ABBREVIATIONS

ENC Electronic Navigational Chart FIS Fairway Information System Inland ECDIS Inland Electronic Chart Display and Information System GlW Gleichwertiger Wasserstand RNW Regulierungs-Niederwasser WGS 84 Wold Geodetic System 1984 XML Extended Markup Language

1. INTRODUCTION

In the following, the primary functions and performance requirements are described.

Fairway Information Services (FIS) contain geographical, hydrological and administrative data that are used by skippers and fleet managers to plan, execute and monitor a trip. FIS provide dynamic information (e.g. water levels, water level predictions etc.) as well as static information (e.g. regular operating times of locks and bridges) regarding the use and status of the inland waterway infrastructure, and thereby support tactical and strategic navigation decisions.

Traditional means to supply FIS are e.g. visual aids to navigation, notices to skippers on paper, broadcast and fixed telephone on locks. The mobile phone using GSM has added new possibilities of voice and data communication, but GSM is not available in all places and at all times. Tailor-made FIS for the waterways can be supplied by radiotelephone service on inland waterways, Internet service or electronic navigational chart service (e.g. Inland ECDIS with ENC).

The following technical specifications for Notices to Skippers provide rules for the data transmission of fairway information via Internet service.

The standardisation of Notices to Skippers will:

— provide automatic translation of the most important content of notices in all the languages of the participating countries,

— provide a standardised structure of data-sets in all the participating countries to facilitate the integration of notices in voyage-planning systems,

— provide a standard for water level information,

— be compatible with the data-structure of Inland ECDIS to facilitate integration of Notices to Skippers into Inland ECDIS,

— facilitate data-exchange between different countries,

— use standard vocabulary in combination with code lists.

It will not be possible to standardise all the information, which is contained in Notices to Skippers. Part of the information will be provided as ‘free text’ without automatic translation. The standardised part should cover all the information which is:

— important for the safety of Inland Navigation (for example: sunken small craft on the right side of the fairway at the Danube, river-km 2 010),

— needed for voyage planning (for example: closure of locks, reduction of vertical clearance, ...).

Additional information (for example: cause of the closure of a lock) can be given as free text.

2. DATA STANDARD

Notices to Skippers shall be provided according to Chapter 6, XML message definition.

In order to enable a broad applicability, the XML message definition contains a wide range of elements. The message is structured into entities (tags), such as sections, groups, subgroups and data elements. The use of free text in the data elements should be restricted to a minimum. Wherever it is possible, data elements are encoded (standardised). The XML message definition defines the structure of the XML message and the codes. The standardised code values, their explanation and translation into 23 languages are provided in reference tables.

A XML-template, the XML-scheme, for Notices to Skippers which is based on the XML definition and the standardised code values contains a complete definition for all the XML elements including possible formats and code values.

In order to obtain a machine-readable XML message one has to fill out the empty fields in the XML-scheme (free text) and to select the code values from the value lists provided in the XML-scheme.

The reference tables and the XML scheme of Notices to Skippers are published by the European Commission at http://ec.europa.eu/transport/iw/index_en.htm

3. WATER LEVEL INFORMATION

Water level information is very important for voyage planning as well as safety. At the moment there is no common standard of referencing water level information (Germany for example is using the GlW, gleichwertiger Wasserstand, the Danube Commission is recommending the RNW, Regulierungs Niederwasser, which is defined slightly different. The vertical clearance is mostly referred to a high water level, but sometimes to low water level. The values of gauges are referring to different sea-levels or to special reference points). Therefore it is not possible to integrate water level information in systems for automatic calculation of clearances.

The reference tables for Notices to Skippers are containing a list of gauges relevant for inland navigation with their reference values. The water level information in the message can be referred to the zero point of a gauge, as it has been done in the past, and the on-board software can calculate the absolute height by use of the reference data of the technical specifications.

4. WAY OF DISTRIBUTION

Member States shall ensure that Notices to Skippers are provided according to these technical specifications in XML-format downloadable in the Internet. In order to enable a specific download, Internet services should provide a possibility to select:

— a specific waterway section (fairway section number of the ID according to Table 1), or

— a specific part of a waterway, defined by the river-km (fairway hectometre of the ID according to Table 1) of the starting and the end point,

— a time of validity (starting date and end date according to Table 1),

— and a date of publication of the notice (date of publication according to Table 1).

Notices according to this standard can additionally be provided for example by:

— WAP (Wireless Application Protocol) services,

— E-mail services.

Data exchange between the authorities is recommended. All the authorities using this standard can integrate Notices to Skippers of other authorities and countries in their own services. The participating parties (authorities) can agree the procedure of transmitting the XML messages by push or pull services directly.

5. PROCEDURE FOR CHANGES IN THE REFERENCE TABLES AND THE XML SCHEME OF NOTICES TO SKIPPERS

Proposals for amendments to the reference tables or the XML scheme have to be sent together with an explanation, why the amendment is needed to the chairperson of the Notices to Skippers 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 amendment procedure as defined in the Terms of Reference for the Notices to Skippers expert group shall apply.

The European Commission will proceed with the amendment in accordance with the procedures established in the RIS Directive. In this context, one shall take due account of the work of the expert group.

If a proposal for amendment is adopted, the updated reference tables and XML scheme are published by the European Commission at http://ec.europa.eu/transport/iw/index_en.htm

6. STRUCTURE OF THE MESSAGES AND CODING IN XML-FORMAT

This chapter describes the structure and formatting of standardised electronic Notice to Skippers messages.

6.1. Structure of the Notices to Skippers

6.1.1. General

Notice to Skippers' messages have the following information sections:

— identification of the message,

— fairway and traffic related message, water level related messages as: — water level messages, — least sounded depth — messages, — vertical clearance — messages, — barrage status — messages, — discharge messages, — regime messages, — predicted water level — messages, — least sounded predicted depth — messages, — predicted discharge — messages.

— ice messages.

Figure 1

Notice to Skippers message structure

A standardised message in XML-format contains therefore four different sections:

(1) Message identification

(2) Fairway and traffic related messages

(3) Water level related messages

(4) Ice messages

Normally in one message only two sections will be filled: The identification section and at least one of the sections: fairway and traffic related messages, water level related or ice message (mix of sections, different type of message information is not allowed).

The fairway and traffic related section contains limitations for a fairway (link) or an object. Notice to Skippers relate to a fairway or a geographical object (point). If the message is about an Object the fairway section shall be filled with the related fairway information without the limitation section.

If a notice contains different limitations for different target groups or different communication information for different limitations, several fairway and traffic related sections with the same number can be used.

The Water level related message section contains measurements for an Object usually a tide gauge.

The Ice message section contains information about the ice conditions and for a fairway (link).

6.1.2. XML definition overview

This section gives an overview of the definition of the message coded in XML. A XML-scheme for Notices to Skippers containing a complete definition for all the XML elements including the possible formats is published at http://ec.europa.eu/transport/iw/index_en.htm

Table 1

XML message specification

No Tag (Group headers and closers are boldly printed) Description Mandatory Conditional Rule applicable <?xml version=«1.0’ encoding=«iso-8859-1’?> <RIS_Message> Notice to Skippers 1s <identification> Identification section M 1 1.1 <from>String</from> Sender of the message M 1.2 <originator>Riza</originator> Originator (initiator) of the information in this message M 1.3 <country_code>CH</country_code> Country where message is valid M 1.4 <language_code>HU</language_code> Original language used in the textual info. (contents) M 1.5 <district>WaddenZee</district> District/Region within the specified country, where the message is applicable C 1.6 <date_issue> 20011231<date_issue> Date of editing C 1.7 <time_issue> 1145<time_issue> Time of editing C 1e </identification> 2s <ftm> Fairway and traffic related section C 1 2.1 <year> 2001</year> Year of first issuing of the notice M 2.2 <number> 9999</number> Number of the notice (per year) M 2.3 <serial_number> 99</serial_number> Serial no of notice (replacements and withdrawals) original notice: 00 M 2.4s <target_group> Target group information C 2.4.1 <target_group_code>ALL</target_group_code> Target group (vessel type) for this message M Default: all 2.4.2 <direction_code>ALL</direction_code> Upstream or downstream traffic, or both M Default:all 2.4e </target_group> 2.5 <subject_code>OBSTRU</subject_code> Subject code M 2.6s <validity_period> Overall period of validity M 2.6.1 <date_start> 20011231</date_start> Start date of validity period M 2.6.2 <date_end> 99999999</date_end> End date of validity period (indefinite: 99999999) M 2.6e </validity_period> 2.7 <contents>String</contents> Contents/notice text in original language C 2.8 <source>String</source> Notice source (authority) C 2.9 <reason_code>REPAIR</reason_code> Reason/justification of notice C 2.10s <communication> Communication channel information C 2.10.1 <reporting_code>INF</reporting_code> Reporting regime (information or duty to report) M 5 2.10.2 <communication_code>TEL</communication_code> Communication code (telephone, VHF etc.) M 5 2.10.3 <number>String</number> Telephone, VHF number, e-mail: address, URL or teletext C 5 2.10e </communication> 2.11s <fairway_section> Fairway section, also available for objects (no. 2.12) M 2 2.11.1s <geo_object> Geo information of fairway M 2.11.1.1 <id>String</id> Unique id of the fairway section (1x or 2x) M 2.11.1.2 <name> String </name> (Local) Name of the fairway section (f.e.: Rhine between bridge A and bridge B) M 2.11.1.3 <type_code>FWY</type_code> Type of geographical object M Default: FWY 2.11.1.4s <coordinate> Fairway section begin and end coordinates (2x) C 2.11.1.4.1 <lat> 42 34.1234 N</lat> M 5 2.11.1.4.2 <long> 123 45.1234 E</long> M 5 2.11.1.4e </coordinate> 2.11.1e </geo_object> 2.11.2s <limitation> Fairway section limitations C 2.11.2.1s <limitation_period> Limitation periods/intervals C 2.11.2.1.1 <date_start> 20011231</date_start> Start date of limitation period (overall) M 5 2.11.2.1.2 <date_end> 20011231</date_end> End date of limitation period C 2.11.2.1.3 <time_start> 1420</time_start> Start time of limitation period C 2.11.2.1.4 <time_end> 0500</time_end> End time of limitation period C 2.11.2.1.5 <interval_code>SAT</interval_code> Interval for limitation if applicable C 2.11.2.1.e </limitation_period> 2.11.2.2 <limitation_code>OBSTRU</limitation_code> Kind of limitation M 5 2.11.2.3 <position_code>AL</position_code> Position, which side M 5, default: all 2.11.2.4 <value> 3.14159</value> Value of limitation (i.e. max draught) C 2.11.2.5 <reference_code>NAP</reference_code> Value reference C 2.11.2.6 <indication_code>MAX</indication_code> C 2.11.2e </limitation> 2.11.e </fairway_section> 2.12s <object> Object section () C 3 2.12.1s <geo_object> Geo Information of object M 5 2.12.1.1. <id>String</id> Unique id of the geographical object M 5 2.12.1.2 <name>String</name> (Local) Name of the geographical object M 5 2.12.1.3 <type_code>FWY</type_code> Type of geographical object M 5 2.12.1.4s <coordinate> Object coordinates (1x) C 2.12.1.4.1 <lat> 42 34.1234 N</lat> M 5 2.12.1.4.2 <long> 123 45.1234 E</long> M 5 2.12.1.4e </coordinate> 2.12.1e 2</geo_object> 2.12.2s <limitation> Object limitation section C 2.12.2.1s <limitation_period> Limitation periods/intervals C 2.12.2.1.1 <date_start> 20011231</date_start> (see <fairway section>) M 5 2.12.2.1.2 <date_end> 20011231</date_end> C 2.12.2.1.3 <time_start> 1420</time_start> C 2.12.2.1.4 <time_end> 0500</time_end> C 2.12.2.1.5 <interval_code>SAT</interval_code> C 2.12.2.1e </limitation_period> 2.12.2.2 <limitation_code>OBSTRU</limitation_code> M 5 2.12.2.3 <position_code>AL</position_code> M 5, default: all 2.12.2.4 <value> 3.14159</value> C 2.12.2.5 <reference_code>NAP</reference_code> C 2.12.2.6 <indication_code>MAX</indication_code> C 2.12.2e </limitation> 2.12e </object> 2e </ftm> 3s <wrm> Water level related section C 1 3.1s <validity_period> Overall period of validity of water level message C 3.1.1 <date_start> 20011231</date_start> Start date of validity period M 5 3.1.2 <date_end> 20011231</date_end> End date of validity period M 5 3.1e </validity_period> 3.2s <geo_object> Geo Information of measurement location, tide gauge M 5 3.2.1 <id>String</id> (Waterway section) Unique id of the geographical object M 5 3.2.2 <name>String</name> (Pegelname) (Local) Name of the geographical object M 5 3.2.3 <type_code>FWY</type_code> Type of geographical object M 5, default: FWY 3.2.4s <coordinate> Object coordinates (1x or 2x) C 3.2.4.1 <lat> 42 34.1234 N</lat> M 5 3.2.4.2 <long> 123 45.1234 E</long> M 5 3.2.4e </coordinate> 3.2.e </geo_object> 3.3 <reference_code>NAP</reference_code> Value reference (measurement reference) C 6 3.4s <measure> Measurements (normal or predicted values) M 5 3.4.1 <predicted> 1</predicted> Predicted measurement (1) or real measurement (0) M 5 3.4.2 <measure_code>DIS</measure_code> Kind of water level related information M 5 3.4.3 <value> 314159</value> Value C 6 3.4.4 <difference> 314159</difference> Difference with previous measurement C 3.4.5 <barrage_code>OPD</barrage_code> Barrage status C 3.4.6 <regime_code>HIG</regime_code> Regime applicable C 3.4.7 <measuredate> 20011231</measuredate> Date of measurement M 5 3.4.8 <measuretime> 1420</measuretime> Time of measurement M 5 3.4e </measure> 3e </wrm> 4s <icem> Ice related section C 1 4.1s <validity_period> Overall period of validity of ice information C 4.1.1 <date_start> 20011231</date_start> Start of validity period M 5 4.1.2 <date_end> 20011231</date_end> End of validity period M 5 4.1e </validity_period> 4.2s <fairway_section> Fairway M 5 4.2.1 <geo_object> Geo Information of fairway location M 5 4.2.1.1 <id>String</id> Unique id of the fairway section (1x or 2x) M 5 4.2.1.2 <name>String</name> (Local) Name of the fairway section M 5 4.2.1.3 <type_code>FWY</type_code> Type of geographical object M 5, default: FWY 4.2.1.4 <coordinate> Fairway section begin and end coordinates (2x) C 4.2.1.4.1 <lat> 42 34.1234 N</lat> M 5 4.2.1.4.2 <long> 123 45.1234 E</long> M 5 4.2.1.4e </coordinate> 4.2.1e </geo_object> 4.2.2s <limitation> Fairway section limitations not applicable 4.2.2e </limitation> Fairway section limitations not applicable 4.2e </fairway_section> 4.3s <ice_condition> Ice conditions M 5 4.3.1 <measuredate> 20011231</measuredate> Date of measurement M 5 4.3.2 <measuretime> 1420</measuretime> Time of measurement M 5 4.3.3 <ice_condition_code>A</ice_condition_code> Condition code C 4 4.3.4 <ice_accessibility_code>A</ice_accessibility_code> Accessibility code C 4 4.3.5 <ice_classification_code>A</ice_classification_code> Classification code C 4 4.3.6 <ice_situation_code>A</ice_situation_code> Situation code C 4 4.3e </ice_condition> 4 e </icem> </RIS_Message> Rules applicable to table 1: 1. In one message at least two sections have to be filled in: — the identification section (1), — one of the sections: — fairway and traffic related messages (2), — water level related message (3), — ice message (4). 2. Group 2.11 (fairway section) is also available for object related messages (No 2.12). 3. Group 2.12 (objects) is not available for fairway related messages (No 2.11). 4. In group 4.3, at least one of the conditional elements 4.3.3 to 4.3.6 have to be filled in. 5. If a conditional group contains mandatory subgroups or elements these are only mandatory if the group on the higher level is applied. 6. Only mandatory for water levels and vertical clearance.

6.1.3. Explanation of tags

The meaning of the different tags used in the XML definition is described on the page ‘Tags’ of the reference tables for Notices to Skippers at http://ec.europa.eu/transport/iw/index_en.htm

6.1.4. Explanation of codes

The meaning of the different codes used in the XML definition is described in the reference tables for Notices to Skippers at http://ec.europa.eu/transport/iw/index_en.htm The formats and possible values of all XML elements are described in the XML Scheme for Notices to Skippers at http://ec.europa.eu/transport/iw/index_en.htm

— Notices to Skippers can be divided into two categories, namely URGENT and NOT URGENT. Urgent notices always contain a limitation for shipping traffic. There must therefore be one or more records in the limitations section. If there is no limitation section the message is not urgent.

— Latitude and longitude coordinates are referred to WGS 84 and presented in degrees and minutes with at least three, but preferable four decimals (dd mm.mmmm N, ddd mm.mmmm E)

— Decimals in numeric fields are indicated with a. (period). No thousand separators are used.

— Only cm, m3/s, h, km/h and kW are allowed to be used as units.

— For waterways there is no objects section. For objects (bridges etc.) the waterway section shall be included.

— The location code according to the technical specification for electronic ship reporting has to be used as unique ID.

6.1.4.1. Subject codes assigned to the Notices to Skippers

In the following, the meaning of and situations defined by the different subject codes are explained.

Blockage

In case, no form of navigation is possible:

— through all the lock chambers of a lock,

— through all the passages of a bridge,

— passing a specified point on the fairway,

— on a specified section of the fairway.

Partial obstruction

In case, limited navigation is possible:

— through one or more lock chambers of a lock, leaving at least one open,

— through one or more passages of a bridge, leaving at least one open,

— passing a specified point on the fairway, leaving a part of the fairway open.

Delay

In case, an obstruction occurs, limited in time, at a bridge, lock or on a section, between a specified start and end date.

For example: Delay of at most two hours on November 13 between 08:00 and 17:00.

Encoded:

date_start: 20021113 date_end: 20021113 time_start: 0800 time_end: 1700 limitation_code: Delay position_code: All value: 2

No service

In case a movable bridge is not operated during a specified period. This period should lie within the normal operating hours.

No service of a lock is an ‘Obstruction’ or ‘Delay’.

No service of a movable bridge means that passing under the bridge still is possible. Otherwise it is an ‘Obstruction’.

Change Service

In case a modification in the normal operating hours occurs at a lock or bridge.

Normally this means a limitation of the operating hours, due to work, rather than an increase.

A limitation in the operating hours of a lock usually implies an obstruction.

For example if a lock normally is operated between 06:00 and 20:00, and the operating hours are now limited to between 10:00 and 14:00, then this will result in an obstruction between 06:00 and 10:00 and another obstruction between 14:00 and 20:00.

A limitation in the operating hours of a bridge usually implies ‘No Service’.

Vessel length

In case somewhere a smaller maximum length for passing vessels is allowed/possible.

Usually this occurs at a lock (half lock chamber).

Clearance width

In case somewhere a smaller maximum width for passing vessels is available.

This occurs during work on a lock/bridge.

This subject is also used if the available width of the fairway is less, even if this has no influence on the maximum available width of the waterway.

Vessel air draught

In case somewhere a smaller maximum height for passing vessels is allowed.

Clearance height

This occurs also if the vertical clearance is locally decreased by for example painting equipment.

Vessel draught

In case somewhere a smaller maximum draught for passing vessels is allowed.

Available depth

In case the least sounded depth is modified. This has no impact on the maximum draught.

No mooring

In case somewhere on the fairway mooring is not allowed.

Change of marks

In case a change occurs in the fairway marks used for navigational purposes, such as buoys, beacons, sector lights, notice marks, etc.

Work

Other activities on or near the fairway which do not fall within the mentioned subjects.

Dredging

Dredging activities for which none of the other mentioned subjects are valid.

Exercises

Exercises for which none of the other mentioned subjects are valid.

Event

Events (rowing competitions, fireworks etc.) where none of the other mentioned subjects are valid.

Announcement

All other notices where none of the other (structured) subjects are valid.

Notice withdrawn

The message has to be published as a serial number of the original message.

If for one single message more subjects are possible, then the limitation with the greatest impact on shipping traffic is selected.

6.1.4.2. Explanation of ice codes

The meaning of the ice codes used in the XML definition is described in the reference tables of Notices to Skippers at http://ec.europa.eu/transport/iw/index_en.htm

The thickness indicated in column 2 of the ice_condition_code gives information on average thickness only. The description has to be used to select the code for a specific situation.

6.1.4.3. Encoding of limitation periods

The limitation period has to be encoded by:

— date_start,

— date_end,

— time_start,

— time_end,

— interval_code.

As the limitation period is very important for voyage planning, limitation periods have to be encoded in accordance with the following examples:

Limitation period date_start date_end time_start time_end Interval_code 2005-01-01, 07:00 to 2005-01-31, 20:00 20050101 20050131 0700 2000 Continuous (C) 2005-01-01 to 2005-01-31, each day from 07:00 to 20:00 20050101 20050131 0700 2000 Daily (M) 2005-01-01 to 2005-01-31, every working day (Monday to Friday) from 07:00 to 20:00 20050101 20050131 0700 2000 Monday to Friday (M) 2005-01-01 to 2005-01-21, each week from Monday 07:00 to Friday 20:00 20050103 20050107 0700 2000 Continuous (C) 20050110 20050114 0700 2000 Continuous (C) 20050117 20050121 0700 2000 Continuous (C) 2005-01-01 to 2005-01-31, each day from 07:00 to 20:00 with the exception of 2005-01-06 20050101 20050131 0700 2000 Daily (M) 20050106 20050106 With the exception of (M)