- Latest available (Revised)
- Point in Time (31/01/2020)
- Original (As adopted by EU)
Commission Regulation (EC) No 414/2007 of 13 March 2007 concerning the technical guidelines for the planning, implementation and operational use of river information services (RIS) 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
When the UK left the EU, legislation.gov.uk published EU legislation that had been published by the EU up to IP completion day (31 December 2020 11.00 p.m.). On legislation.gov.uk, these items of legislation are kept up-to-date with any amendments made by the UK since then.
Legislation.gov.uk publishes the UK version. EUR-Lex publishes the EU version. The EU Exit Web Archive holds a snapshot of EUR-Lex’s version from IP completion day (31 December 2020 11.00 p.m.).
Version Superseded: 31/12/2020
Point in time view as at 31/01/2020.
There are currently no known outstanding effects by UK legislation for Commission Regulation (EC) No 414/2007, ANNEX.
Revised legislation carried on this site may not be fully up to date. At the current time any known changes or effects made by subsequent legislation have been applied to the text of the legislation you are viewing by the editorial team. Please see ‘Frequently Asked Questions’ for details regarding the timescales for which new effects are identified and recorded on this site.
Accord européen relative au transport international des marchandises dangereuses par voie de navigation intérieur du Rhin
Automatic identification system (transponder)
Advanced river navigation
Adviesdienst Verkeer en Vervoer (The Netherlands)
Binnenvaart informatie en communicatie systeem (electronic reporting system)
Calamity abatement support
Central Commission for the Navigation on the Rhine
Closed circuit television
Code européen de voies de la navigation intérieure (European code for inland waterways), edited by UN/ECE
Consortium operational management platform river information services (R&D project of the EU, 2003 — 2005)
Data warehouse for the River Danube
Differential global positioning system
Electronic chart and display information system
Economic Commission for Europe of the United Nations
Electronic data interchange
Electronic data interchange for administration, commerce and transport (UN/ECE Standard)
Electronic navigational chart
Estimated time of arrival
Estimated time of departure
European Telecommunications Standards Institute
Fairway information
Fairway information service
Global orbiting navigation satellite system
Global navigation satellite system
Global system for mobile communication
High frequency
Harmonised commodity description and coding system of WCO
International Organisation of Marine Aids to Navigation and Lighthouse Authorities
International Electrotechnical Commission
International Hydrographic Organisation
International maritime dangerous goods code
International Maritime Organisation
Inland navigation demonstrator of river information services (R&D project of EU, 1998–2000)
International Standardisation Organisation
Information technology
International Telecommunication Union
Local area network
Lock and bridge management
Official ship number
International Navigation Association
Port and terminal management
River information services
Required time of arrival
Search and rescue
Signs and signals on inland waterways, edited by UN/ECE
Short message service
International Convention on Safety of Life at Sea
Self organising time division multiple access AIS
Strategic traffic information (image)
Transmission control protocol/Internet protocol
Traffic information
Tactical traffic information (image)
Universal mobile telecommunication system
Universal time coordinated
VHF data link
Very high frequency
Vessel traffic centre
Vessel traffic management and information services (maritime navigation)
Vessel traffic services
Wireless application protocol
World Customs Organisation
Wireless fidelity
Zentralkommission für die Rheinschifffahrt
Relation between RIS area and VTS area
RIS development and redesign
Arenas roles and management tasks in inland shipping
Elements of an information processing loop
Information processing loop
Derivation of RIS services
River information services
Functional decomposition of river information services
Relation between services and systems
Data set for ship reporting
The planning process for RIS
Possible stepwise development of the different parts of RIS
Guidelines and Criteria for Vessel Traffic Services in Inland Waters (Inland VTS Guidelines), (world-wide), IALA recommendation V-120, June 2001, 2001;
Regional Arrangement Concerning the Radiotelephone Service on Inland Waterways (Basel), 2000;
technical specifications for Inland ECDIS as defined under the RIS Directive(1);
technical specifications for vessel tracking and tracing systems, such as Inland AIS, as defined under the RIS Directive;
technical specifications for electronic ship reporting in inland navigation as defined under the RIS Directive;
technical specifications for notices to skippers in inland navigation as defined under the RIS Directive;
Harmonised Commodity Description and Coding System of the WCO (worldwide);
UN Code for Trade and Transport Locations UN/LOCODE (worldwide);
EDIFACT Standard of the UN (worldwide);
Standardised UN/ECE Vocabulary for Radio Connections in Inland Navigation (Europe), 1997.
Guidelines and recommendations for RIS, 1999 (used as starting point for the RIS Guidelines by PIANC);
Functional definition of the RIS concept, 1998;
Standardisation of data communication (AIS, GNSS, Internet), 1999;
Standards for tactical data exchange, communication and messages (Inland AIS), 1998;
Standardisation of data, 1998:
standards of codes (country, location, terminal, type of vessel, cargo),
RIS scenarios (functions),
data-interchange standards (EDIFACT, S-57 update mechanism);
reporting databases, 1999.
The following terms are used in connection with river information services in these RIS Guidelines (see also some specific definitions in Chapters 4 and 5).
River information services means harmonised information services to support traffic and transport management in inland navigation, including, wherever technically feasible interfaces to other transport modes. RIS aim at contributing to a safe and efficient transport process and at utilising the inland waterways to their fullest extent. RIS are already in operation in manifold ways.
Explanatory notes:
RIS include interfaces with other transport modes, sea, roads and railways.
Rivers in the context of RIS include all inland waterways and ports as defined in Article 2(1) of the RIS Directive.
RIS is also the generic term for all individual information services to support inland navigation in a harmonised way.
RIS collect, process, assess and disseminate fairway, traffic and transport information.
RIS are not dealing with internal commercial activities between one or more of the involved companies, but RIS are open for interfacing with commercial activities.
For the purpose of RIS, modern river information systems consist of one or more harmonised IT systems. An IT system (information technology system) is the totality of human resources, hardware, software, communication means and regulations in order to fulfil the task of processing information.
The RIS area is the formally described area, where RIS are active. A RIS area may comprise the waterways in a geographical river basin, including the territories of one or more countries (e.g. in a situation where a waterway forms the borderline between two countries) (Figure 2.3).
A RIS centre is the place, where the services are managed by operators. A RIS may exist without a RIS centre (e.g. an Internet service, a buoys service). When ship/shore interaction in both ways (e.g. by VHF service) is intended, one or more RIS centres are needed. If a VTS centre or a lock exists in a RIS area, they may also be used as RIS centres. It is recommended to concentrate all services in a RIS area into one single RIS centre.
Inland vessel traffic services are 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 VTS area.
VTS should comprise at least an information service and may include others, such as navigational assistance service, or a traffic organisation service, or both, defined as below:
an information service is a service to ensure that essential information becomes available in time for on-board navigational decision-making,
a navigational assistance service is a service to assist on-board navigational decision-making and to monitor its effects. Navigational assistance is especially of importance in reduced visibility, or difficult meteorological circumstances or in case of defects or deficiencies affecting the radar, steering or propulsion. Navigational assistance is given in due form of position information at the request of the traffic participant or in special circumstances when deemed necessary by the VTS operator, using technologies such as GNSS/Galileo,
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 (Chapters 4.5 and 5.3.1).
Where present, VTS are part of river information services (Figure 2.3). Within RIS, Inland VTS belongs to the group of traffic management services with the emphasis on information service and traffic organisation (Chapter 4.5 and 5.3.1).
A VTS area is the delineated, formally declared service area of a VTS. A VTS area may be subdivided in sub-areas or sectors.
A VTS centre is the centre from where the VTS is operated. Each sub-area of the VTS may have its own sub-centre.
The competent authority as referred to in Article 8 of the RIS Directive is the authority made responsible for safety, in whole or in part, by the government, including environmental friendliness and efficiency of vessel traffic. The competent authority usually has the tasks of planning, arranging funding and of commissioning of RIS.
The RIS authority is the authority with the responsibility for the management, operation and coordination of RIS, the interaction with participating vessels, and safe and effective provision of the service.
The users of the services can be described in a number of different groups: skippers, RIS operators, lock/bridge operators, waterway authorities, terminal operators, operators in calamity centres, fleet managers, cargo shippers, consignors, consignees, freight brokers, and supply forwarders.
River information services work on the basis of different information levels. Fairway information contains the data of the waterway only. Traffic information has the information on vessels in the RIS area. Traffic information can be divided into tactical traffic information and strategic traffic information. Traffic information is provided by traffic images.
There are three levels of information:
Fairway information (FI) contains geographical, hydrological, and administrative information regarding the waterway (fairway) in the RIS area that is required by the RIS users to plan, execute and monitor a voyage. Fairway information is one-way information: shore to ship or shore to office (users’ office).
Tactical traffic information (TTI) is the information affecting the skipper's or the VTS operator's immediate decisions with respect to navigation in the actual traffic situation and the close geographic surroundings. A tactical traffic image contains position information and specific vessel information of all targets detected by a radar and presented on an electronic navigational chart, and — if available — enhanced by external traffic information, such as the information delivered by an Inland AIS. TTI may be provided on board a vessel or on shore, e.g. in a VTS centre.
Strategic traffic information (STI) is the information affecting the medium and long term decisions of RIS users. A strategic traffic image contributes to the planning decision capabilities regarding a safe and efficient voyage. A strategic traffic image is produced in a RIS centre and delivered to the users on demand. A strategic traffic image contains all relevant vessels in the RIS area with their characteristics, cargoes and positions, stored in a database and presented in a table or on an electronic map. Strategic traffic information may be provided by a RIS/VTS centre or by an office.
Vessel tracking means the function of maintaining status information of the vessel, such as the current position and characteristics, and — if needed — combined with information on cargo and consignments.
Vessel tracing means the retrieving of information concerning the whereabouts of the vessel and — if needed — information on cargo, consignments and equipment.
Part of this service can be fulfilled for example by Inland AIS. Other parts can be fulfilled by an electronic ship reporting system.
a radio equipped for the simultaneous reception of inland navigation radio on two VHF channels (ship/ship and ship/shore);
a radar for the presentation of the traffic in the close surroundings of the vessel;
a PC with mobile communication facilities (GSM) for the reception of e-mail and Internet, and for electronic reporting;
an Inland ECDIS device with electronic navigational charts (ENCs);
in information mode,
in navigation mode (with radar overlay);
a vessel tracking and tracing system, such as Inland AIS, with position receiver (GNSS/Galileo) and radio transceiver using Inland ECDIS for visualisation.
The idea of the thematic network WATERMAN (Chapter 1(6)) behind the development of the framework architecture for RIS was to translate policy objectives into specifications for application design. The RIS architecture should be defined in such a way that RIS applications will be produced to be efficient, expandable and able to interact with other RIS applications or applications for other modes of transport. RIS architecture development should lead to an integrated environment of RIS applications in a way that the performance, usefulness and efficiency of the applications will be enhanced.
River information services may be developed and redesigned according to Figure 4.1.
RIS will be realised and kept operational by a set of cooperating stakeholders. The most important of them are:
Policy makers want the RIS to solve (or diminish) traffic and transport problems. One party of policy makers are the authorities responsible for safety on the waterways. Other policy makers, e.g. organisations of ship owners, want to provide transport/logistical information services to cargo shippers and terminal operators. The different groups of policy makers have their own policy objectives, tasks and ideas about the required services to achieve its objectives. Once the services have been selected, the functions and information needs with their restrictions and interactions for providing these services should be determined.
Regional managers control the RIS applications, e.g. waterway managers of the competent authority, traffic control managers, managers of search and rescue services, ship owners, and cargo shippers. They define requirements for applications with more detailed and accurate descriptions of the services and the functions, regarding local aspects or aspects of man/machine interface.
System engineers prepare system specifications and integrate hardware and software components into system components. RIS and VTS suppliers, system integrators, and telecommunication operators will combine the system components into complete systems which enable RIS services.
Service providers make and keep RIS operational and therefore they develop, maintain and operate the RIS applications. They control the autonomous applications and, where necessary, they provide the main input into the applications either by themselves or by RIS users.
RIS users can be described as a number of different groups: skippers, RIS operators, lock/bridge operators, waterway authorities, terminal operators, operators in calamity centres, fleet managers, cargo shippers, consignors, consignees, freight brokers, supply forwarders.
An objective is the description of intention. The objective may also be called the goal or aim. RIS have three main objectives:
transport should be safe:
minimise injuries,
minimise fatalities,
minimise voyage incidents;
transport should be efficient:
maximise throughput or effective capacity of waterways,
maximise the carrying capacity of vessels (length, width, draught and height),
reduce travel time,
reduce workload of RIS users,
reduce transport costs,
reduce fuel consumption,
provide efficient and economical link between transport modes,
provide efficient harbours and terminals;
transport should be environmentally friendly:
reduce environmental hazard,
reduce polluting emissions and spills due to accidents, illegal actions or normal operations.
These objectives should be met under the constraints that all RIS are supplied in a manner that is reliable, cost efficient and legally sound.
River information services support a number of management tasks in inland shipping. These tasks are related to the objectives (Chapter 4.3) and performed in three different ‘arenas’:
transport logistics where parties that cause the transport cooperate with parties that organise the transport (e.g. consignors, consignees, shippers, supply forwarders, freight brokers, fleet owners),
transport where parties that organise the transport cooperate with parties that execute the transport (e.g. fleet owners, terminal operators, customers),
traffic where parties that execute the transport (e. g. ship masters and navigators) cooperate with parties that manage the resulting vessel traffic (e.g. traffic manager, competent authorities).
The tasks are performed by different actors playing their role and being involved in transport objects and transport processes. One actor can be a stakeholder in one or more arenas at the same time. The activities of the actors are combined at transfer points and transfer processes. Figure 4.4.a gives an overview of all the relevant roles (and thus the stakeholders fulfilling these roles) responsible for traffic, transport and transport logistics in inland shipping. The tasks in Figure 4.4.a are also called communal tasks in the sense that individual tasks of the involved roles have to be tuned to each other by mutually informing each other, by negotiation or — in some cases — by passing on directions. This overview is the basis for defining RIS (Source: COMPRIS: RIS architecture, reference model).
The management tasks allow deriving the following RIS in relation to the objectives, where one RIS service can fulfil one or more management tasks (Table 4.4.b):
Derivation of RIS
ITL = Information for transport logistics () = numbering in Table 4.5 | |||
Objectives Chapter 4.3) | Management tasks (Figure 4.4 a) | RIS (Table 4.5) | |
---|---|---|---|
Efficiency | Transport object related | Consignment management | ITL cargo management (5.d) |
Stock management | |||
Transport service management | ITL outside the scope of RIS | ||
Terminal management | ITL terminal management (5.c) | ||
Fleet management | ITL cargo and fleet management (5.d) | ||
Safety, environmental friendliness, efficiency | Infrastructure management | Fairway information service (1) | |
Statistics (7) | |||
Waterway charges and harbour dues (8) | |||
Efficiency | Transport process related | Supply chain management Transport chain management | ITL cargo and fleet management (5.d) |
ITL transport management (5.b) | |||
ITL inter-modal port and terminal management (5.c) | |||
ITL voyage planning (5.a) | |||
Safety, efficiency | Traffic process related | Traffic management | Traffic information (2) |
Traffic management (3) | |||
Safety, environmental friendliness, efficiency | All objects and processes | Incident management and calamity abatement | Calamity abatement support (4) |
Law enforcement | Information for law enforcement (6) |
The tasks in all RIS arenas are performed by the actors in cycles as shown in Figures 4.4.c and d. Moreover, the tasks may take place on an operational, tactical or strategic level (good examples are the tactical and strategic traffic information levels, defined in Chapter 2.11). This concept allows to draw for each individual task an information processing loop including the actions of the different actors. Every step in the information processing loop can be supported by river information services, which help the actor in his observations, evaluations, decisions, and actions. The information processing loop can be used to define the river information services (Chapter 4.5) and RIS functions (Chapter 4.6). An example for an information processing loop is given in Appendix A (COMPRIS: RIS architecture, information architecture).
A service provides and uses information. It supports the user in achieving an improvement in performance. Services are developed by development projects and initiatives (driven by stakeholders or by technology push). Services are the means for the user to achieve the objectives. The execution of a task can be enhanced by using one or more services.
River information services as identified in Chapter 4.4 are rearranged and subdivided according to Table 4.5.
Visual aids to navigation
Radiotelephone service on inland waterways
Internet service
Electronic navigational chart service
Tactical traffic information (TTI)
Strategic traffic information (STI)
Local traffic management (vessel traffic services - VTS
Navigational support (NS)
Lock and bridge management (LBM)
Voyage planning (VP)
Transport management (TPM)
Intermodal port and terminal management (PTM)
Cargo and fleet management (CFM)
Abbreviations in Table 4.5 are used only to provide the connection to Table 4.6.
A RIS function is understood as a contribution to a service. The functional decomposition of river information services allows the allocation of information supply to user demand. Table 4.6 shows the connections between services (Chapter 4.5), functions (Chapter 4.6), users (Chapter 4.2.5) and information levels (Chapter 2.11). It also shows that in many cases the same function serves many participants in the transport process. Table 4.6 gives an example as a guide to anybody else and may remind the reader in making his/her own list.
Functional decomposition of river information services
No | RIS service RIS sub-serviceRIS function | Information level | User | |||||||
---|---|---|---|---|---|---|---|---|---|---|
Ship master | VTS operator | Lock/bridge operator | Waterways authority | Terminal operator | Calamity centre | Fleet manager | Cargo shipper | |||
FIS | Fairway information service | |||||||||
Provision of information on: | ||||||||||
FIS.1 | Geography of the navigation area and their updates | FIS | X | X | X | X | X | X | X | |
FIS.2 | Navigation aids and traffic signs | FIS | X | X | X | X | X | |||
FIS.3 | Water depths contours in the navigation channel | FIS | X | X | X | X | X | X | ||
FIS.4 | Long time obstructions in the fairway | FIS | X | X | X | X | X | X | X | |
FIS.5 | Actual meteorological information | FIS | X | X | X | X | ||||
FIS.6 | Temporary obstructions in the fairway | FIS | X | X | X | X | X | |||
FIS.7 | Present and future water levels at gauges | FIS | X | X | X | X | X | X | ||
FIS.8 | State of the rivers, canals, locks and bridges in the RIS area | FIS | X | X | X | X | X | X | ||
FIS.9 | Restrictions caused by flood and ice | FIS | X | X | X | X | X | X | X | |
FIS.10 | Malfunctions of aids to navigation | FIS | X | X | X | |||||
FIS .11 | Short term changes of lock and bridge operating times | FIS | X | X | X | X | X | |||
FIS .12 | Short term changes of aids to navigation | FIS | X | X | X | |||||
FIS.13 | Regular lock and bridge operating times | FIS | X | X | X | X | X | X | X | |
FIS.14 | Physical limitations on waterways, bridges and locks | FIS | X | X | X | X | X | X | X | |
FIS.15 | Navigational rules and regulations | FIS | X | X | X | X | X | X | ||
FIS.16 | Rates of waterway infrastructure charges | FIS | X | X | X | X | ||||
FIS.17 | Regulations and recommendations for pleasure navigation | FIS | (X) | X | X | |||||
TI | Traffic information | |||||||||
TTI | Tactical traffic information (short term related) | |||||||||
TTI.1 | Presentation of own vessel's position | TTI | X | X | ||||||
TTI.2 | Presentation of other vessels' positions | TTI | X | X | ||||||
STI | Strategic traffic information (medium and long term related) | |||||||||
STI. 1 | Presentation of fairway information (=FIS) | FIS | X | X | X | X | ||||
STI. 2 | Presentation of vessel's positions in large surroundings | STI | X | X | X | X | ||||
STI.3 | Medium and long term assessment of traffic situation | STI | X | X | ||||||
STI.4 | Presentation of vessel's characteristics | STI | X | X | X | X | X | X | ||
STI.5 | Presentation of cargo's characteristics | STI | X | X | X | X | X | X | ||
STI.6 | Presentation of intended destination | STI | X | X | X | X | X | X | X | X |
STI.7 | Presentation of information on incidents/accidents in the coverage area | STI | X | X | X | X | ||||
STI.8 | Organisation and regulation of traffic flow | STI | X | X | X | |||||
TM | Traffic management | |||||||||
VTS | Vessel traffic services (local) | |||||||||
VTS.1 | Presentation of vessel's positions in large scale | TTI | X | |||||||
VTS.2 | Monitoring of passing and manoeuvring arrangements | TTI | X | |||||||
VTS.3 | Short term assessment of traffic situation | TTI | X | |||||||
VTS.4 | Organisation and regulation of traffic flow in RIS coverage area | TTI | X | |||||||
NS | Navigational support | |||||||||
NS.1 | Information to pilots (navigational support) | TTI | X | X | ||||||
NS.2 | Information to tug boats (nautical support) | STI | X | |||||||
NS.3 | Information to bunker boats, waste oil removal boats, vessel equipment firms (vessel support service) | STI | X | X | ||||||
LBM | Lock and bridge management | |||||||||
LBM.1 | Lock/bridge operation | |||||||||
LBM.1.1 | Presentation of actual status of lock/bridge process | TTI | X | X | ||||||
LBM.1.2 | Presentation of short term planning of lock/bridge (ETAs/RTAs of vessels, waiting places, lock/bridge positions) | TTI | X | X | X | |||||
LBM.2 | Lock/bridge planning | |||||||||
LBM.2.1 | Provision of ETAs of approaching vessels | STI | X | |||||||
LBM.2.2 | Provision of information on medium and long term schedule of lock/bridge process | STI | X | X | ||||||
LBM.2.3 | Provision of medium and long term RTAs of vessels | STI | X | X | ||||||
CAS | Calamity abatement support | |||||||||
CAS.1 | Information on incidents focused on traffic situation | TTI | X | X | X | |||||
CAS.2 | Assessment of the traffic situation in the situation of an incident | TTI | X | X | ||||||
CAS.3 | Coordination of the assistance of patrol vessels | TTI | X | X | X | |||||
CAS.4 | Assessment of the possible effects of the accident on environment, people and traffic | TTI | X | X | ||||||
CAS.5 | Presentation of information to patrol vessels, police boats, fire squad boats | TTI | X | X | ||||||
CAS.6 | Initiation and coordination of search and rescue activities | TTI | X | X | X | |||||
CAS.7 | Taking measures on traffic, environmental and people protection | TTI | X | X | ||||||
ITL | Information for transport logistics/management | |||||||||
VP | Voyage planning | |||||||||
VP.1 | Provision of information on port of destination, RTA at final destination, type of cargo | STI | X | X | X | |||||
VP.2 | Provision of information on and presentation of the fairway network at different scales | STI | X | X | X | |||||
VP.3 | Presentation of lock and bridge opening times and general waiting times | STI | X | X | X | |||||
VP.4 | Presentation of long term weather information | STI | X | X | X | |||||
VP.5 | Presentation of mid and long term prediction of water levels | STI | x | X | X | |||||
VP.6 | Presentation of information on route characteristics with RTAs, ETAs, ETDs at waypoints | STI | X | X | X | |||||
VP.7 | Presentation of information affecting travel information | STI | X | |||||||
TPM | Transport management | |||||||||
TPM.1 | Provision and presentation of ETAs of vessels | STI | X | Ship supplier organisation Bunker organisation Repair organisation | X | |||||
TPM.2 | Provision and presentation of voyage plans of vessels | STI | X | X | ||||||
TPM.3 | Provision of information on free loading space | STI | X | X | ||||||
TPM.4 | Monitoring of the performance of contracted transports and terminals | Freight brokers Transport service quality managers | ||||||||
TPM.5 | Monitoring unusual threats (like strikes, fall in water level) for the reliability of transport | |||||||||
TPM.6 | Match the transport and terminal performance with service levels agreed on | |||||||||
TPM.7 | Define adjustments to methods for voyage planning | |||||||||
PTM | Inter-modal port and terminal management | |||||||||
PTM.1 | Presentation of actual terminal or port status | |||||||||
PTM.1.1 | Presentation of vessels waiting, being loaded/unloaded | TTI | X | X | ||||||
PTM.1.2 | Presentation of actual status of terminal process | TTI | X | X | ||||||
PTM.1.3 | RTAs of vessels, waiting places, positions | X | X | X | ||||||
PTM.2 | Port or terminal planning | |||||||||
PTM.2.1 | ETAs of approaching vessels | STI | X | |||||||
PTM.2.2 | Medium and long term schedule terminal process | X | ||||||||
PTM.2.3 | Medium and long terms RTAs of vessels | STI | X | X | ||||||
CFM | Cargo and fleet management | |||||||||
CFM.1 | Information on fleet of vessels and their transport characteristics | STI | X | X | ||||||
CFM.2 | Information on the cargo to be transported | STI | X | X | ||||||
ILE | Information for law enforcement | |||||||||
ILE.1 | Cross-border management (immigration service, customs) | X | ||||||||
ILE.2 | Compliance with requirements for traffic safety | X | ||||||||
ILE.3 | Compliance with environmental requirements | X | ||||||||
ST | Statistics | X | ||||||||
ST.1 | Transit of vessels and cargo at certain points (locks) of the waterway | X | ||||||||
CHD | Waterway charges and harbour dues | X | X | X | X |
RIS applications are regional or dedicated uses of systems under specific requirements: local, functional, process-oriented. RIS application means the provision of river information services through dedicated systems. A single application can use one or more systems to provide a service.
A wide range of technical systems has been developed for RIS, most of them used for more than one service, function or application (Table 4.8):
Relation between services and systems
System | Service | |||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Fairway information | Traffic information | Traffic management | Calamity abatement support | Information for transport logistics | Information for law enforcement | Statistics | Waterway charges and harbour dues | |||||||
Tactical | Strategic | Vessel traffic services | Navigational support | Lock and bridge management | Voyage planning | Transport management | Inter-modal port and terminal management | Fleet and cargo management | ||||||
Visual aids to navigation | x | |||||||||||||
Radar reflecting aids to navigation | x | x | ||||||||||||
Light signals | x | x | x | |||||||||||
Mobile phone (voice and data) | x | x | x | x | x | x | x | x | x | x | ||||
GNSS/Galileo for vessel positioning | x | x | x | x | x | x | ||||||||
VHF radio | x | x | x | x | x | x | x | x | x | x | ||||
Internet | x | x | x | x | x | x | x | x | ||||||
Vessel based radar | x | x | x | |||||||||||
Shore based radar | x | x | x | x | ||||||||||
Shore based CCTV cameras | x | x | x | |||||||||||
Electronic navigational chart | x | x | x | x | x | x | ||||||||
Vessel tracking and tracing system | x | x | x | x | x | x | x | x | x | x | x | |||
Ship reporting system | X | x | x | x | x | x | x | x | x |
Because technology changes fast, the emphasis is laid more on services and less on technology dependent systems in this Chapter.
radiotelephone service on inland waterways;
Internet service;
electronic navigational chart service (e.g. Inland ECDIS with ENC).
These three FIS categories are dealt with in this Chapter. They are mainly based on the current situation, but for example notices to skipper may be supplied also via ENC service in the future.
ship-to-ship;
nautical information;
ship-to-port authorities;
on-board communications;
public correspondence (service on a non-mandatory basis).
Of these five categories, only the first three are important for RIS. The radiotelephone service enables direct and fast communication between skippers, waterway authorities and port authorities. It is best suited for urgently needed information on a real time basis.
Radio Regulations of the International Telecommunication Union ITU (worldwide);
Regional Arrangement Concerning the Radiotelephone Service on Inland Waterways (Basel, 6 April 2000);
Standardised UN/ECE Vocabulary for Radio Connections in Inland Navigation (UN Economic Commission for Europe No 35, 1997);
national inland waterway rules for navigation.
for urgent information needing to be updated frequently and having to be communicated on a real time basis;
for dynamic information having to be communicated on a daily basis.
temporary obstructions in the fairway, malfunctions of aids to navigation;
short-term changes of lock and bridge operation times;
restrictions in navigation caused by flood and ice;
present and future water levels at gauges.
scheduled reports on the state of the waterways incl. water level reports at the gauges at fixed times of the day;
urgent reports at special events (e.g. traffic regulations after accidents).
dynamic nautical information on the state of the waterways that needs to be communicated not faster than on a daily basis;
dynamic hydrographical information, as actual water levels, water level predictions, navigation channel depths (if available), ice and flood predictions and reports;
static information (e.g. physical limitations of the waterway, regular operating times of locks and bridges, navigational rules and regulations).
The abovementioned information shall be provided via notices to skippers or via Inland ECDIS for waterways of class Va and above.
E-mail subscription to computers on board of vessels and in offices;
SMS subscription to mobile phones;
WAP pages to mobile phones.
Information concerning the traffic situation may be provided in two ways (Chapter 2.11):
as tactical traffic information (TTI), using radar and — if available — a vessel tracking and tracing system such as Inland AIS with underlain electronic navigational charts;
as strategic traffic information (STI) using an electronic ship reporting system (e.g. database with ship and cargo data, reports by VHF or other mobile communication facilities — voice and data).
lock and bridge management (calculation of estimated time of arrival — ETA — and required time of arrival — RTA);
voyage planning;
calamity abatement support (vessel and cargo data);
terminal management (calculation of ETA and RTA).
voice reporting via mobile phone;
voice reporting via VHF (Chapter 5.1.2 (6));
electronic reporting via on-board computer (e.g. BICS application) and mobile communication facilities (e.g. mobile phone data) or shore based computers and fixed communication lines for initial reports (vessel identity and cargo);
vessel tracking and tracing (e.g. by Inland AIS) for progress reports (vessel's position and ETA).
Table 5.2.3. | |
Data set for ship reporting (example) | |
Static data of vessels in composition | |
---|---|
Type | MV |
Name | Arcona |
Official vessel No (for sea vessels IMO-No) | 4,620,004 |
Length | 110 m |
Width | 11,4 m |
Variable data | |
Number of crew on board | 3 |
Position (by waterway and km) | Emmerich, km 857,0 |
Sailing direction | upstream bound |
Number of vessels in composition | 2 |
Length of composition | 187 m |
Width of composition | 11,4 |
Draught | 3,2 m |
Next reporting point (lock/bridge, terminal) | Meiderich lock |
ETA at reporting point with accuracy | 17:30 ± 0:30 |
For each partial cargo | |
Category of cargo | Chemical product |
Harmonised system code of cargo | 310 210 |
Loading point (UN location code) | Rotterdam |
Destination point (UN location code) | Dortmund |
Amount of cargo (tons) | 2 800 |
Only if dangerous cargo | |
Name of cargo | Na-Nitrit |
Code of cargo | ADN, ADNR |
Class | 5.1 |
Package code | III |
UN-No (if available) | 1 500 |
Quantity of blue cones/lights | 1 |
narrow fairway and/or shoals,
narrow bends,
narrow and/or many bridges,
fast water currents and/or cross currents,
fairway with traffic regulations, e.g. one-way-traffic,
conjunction of waterways,
high traffic density.
Navigational support is the generic term for some services to assist inland navigation.
In the traffic arena (Chapter 4.4), navigational support is provided by pilots to prevent the development of dangerous vessel traffic situations on board or in special circumstances on shore. Nautical support is provided by tug boats or boatmen to assist in safe navigation and mooring.
In the transport arena, vessel support services are services given to the skipper by e.g., bunker boats, waste oil removal boats, vessel equipment firms, and repair organisations.
support of the lock/bridge master in short-term decisions for planning of the lock and bridge cycle by presentation of an electronic lock diary, by a database, and by registration of waiting times;
support of the lock/bridge master in medium term decisions by data exchange with the neighbouring locks;
support of the skipper by transmission of waiting times;
optimising of lock circles by calculation of ETAs/RTAs for a chain of locks, transmission of RTAs to skippers.
when entering or leaving the area of a RIS centre;
at specified reporting points within the area of the RIS centre;
when the data has been changed during the voyage;
before and after stops of longer than a specific period.
voyage planning;
transport management;
intermodal port and terminal management;
cargo and fleet management.
fairway information service (Chapter 5.1);
strategic traffic information (Chapter 5.2.3);
lock and bridge management (Chapter 5.3.3).
controlling the overall performance of the contracted fleet managers/skippers and terminal operators;
controlling the progress in the contracted transports;
monitoring unexpected threats for the reliability of these transports;
finalising the transport (delivery and invoice).
the exchange of information between users and customers relating to vessels and terminals;
fleet planning support;
ETA/RTA negotiations between vessels and terminals;
vessel tracking and tracing;
electronic market places.
The competent authorities should indicate the data structure in use to application builders.
Law enforcement ensures that people within a given jurisdiction adhere to the laws of that jurisdiction. RIS supports law enforcement in inland navigation in the fields of:
cross-border management (e.g. the movement of people controlled by the immigration service, customs);
compliance with the requirements for traffic safety;
compliance with the environmental requirements.
In accordance with Article 4 of the RIS Directive, Member States shall take the necessary measures to implement RIS on inland waterways falling within the scope of Article 2.1 of that Directive. Member States may apply the Directive also to those inland waterways and ports which are not referred to in Article 2.1.
The concerned competent authority usually should provide the necessary expertise and arrange funding to provide the desired levels of technology and expertise to meet the objectives.
have a legal basis for the actions of the RIS and assure that the RIS are in conformity with national and international laws;
determine the objectives of the RIS;
appoint a RIS authority;
describe the area of coverage of the RIS;
determine the services and functions which will be rendered;
define the requirements for the applications;
provide the equipment necessary to carry out the tasks given to the RIS;
provide and train sufficient and competent personnel;
harmonise the demands of traffic and transport management by cooperation with the organisations of cargo shippers, fleet owners and port owners.
The liability element of compliance with RIS guidance is an important consideration which can only be decided on a case-by-case basis in accordance with national law. Consequently, a RIS authority should take into account the legal implications in the event of a shipping accident, where RIS operators may have failed to carry out their duty competently.
Table 6.4 illustrates the steps to follow when planning for the development and implementation of RIS.
Hydrographical, hydrological and meteorological conditions
Waterway conditions
e.g. dimensions of waterways (locks, bridges, fairways), visibility along fairways, specific constraints (bends, narrows, shoals, narrow and low bridges), navigation patterns, bottlenecks, operating times of locks
Current and future traffic and transport situation
number of passengers, tons of cargo, kind of cargo, composition of fleet
Number, type and impact of accidents including analysis of consequences
Legal situation
authorities, incident/calamity regulations
Regional management and organisational situation
e.g. lock operators, harbour and terminal companies
Existing RIS systems
Other problems in the area,
e.g. delays
short description, representation of performance and cost estimation of the potential IT systems
Design on a functional basis
external and internal functions dependant on the local situation
Translation of the functional design into a technical design (systems)
Definition of equipment needed on vessels and on shore
Risk assessment, e.g. types of risks and weighing of risks by pair wise comparison
Efficiency of transport by cost/benefit analysis
reduction of waiting times for vessels, higher reliability, shorter voyage duration, costs of incidents, accidents and delays
Environment impact study
if appropriate, for urban areas and the river
Liability in the legislation and regional legal basis
Competent authority for planning and construction
RIS authority for operation
authority that is carrying out the task
Personnel facilities
eventually fully automated, training aspects
The successful delivery of RIS depends upon competent and experienced personnel to fulfil the responsibilities of a RIS authority. The recruitment, selection and training of suitable personnel are a pre-requisite to the provision of professionally qualified personnel capable of contributing to safe and efficient vessel operations. Such personnel will help to ensure that full regard is given to the diverse tasks inherent in RIS activities.
Possible stepwise development of the different parts of RIS
(in italics: system tested, but not implemented yet)
Type of service | Step | System configuration | Chapter | |
---|---|---|---|---|
1. Fairway information services | 1.1 Voice communication shore/ship | 1 | Local nautical information by VHF at locks and bridges | 5.1.2 |
2 | Central nautical information by VHF system with RIS centre | 5.1.2 | ||
1.2 Internet | 1 | Internet homepage with notices to skippers and water levels, static pages without content management system | 5.1.3(1) | |
2 | As No 1, but additionally dynamic pages with content management system | 5.1.3(3) | ||
3 | E-mail subscription of notices to skippers and water levels | 5.1.3(4) | ||
4 | On demand, presentation of all fairway information from port of departure to port of destination for route planning on one web page | 5.1.3(5) | ||
1.3 Electronic navigational chart | 1 | Electronic raster chart (scan from paper chart) | ||
2 | Inland ECDIS in information mode | 5.1.4(1) | ||
2. Traffic information | 2.1 Tactical traffic information (TTI) on board by radar, Inland ECDIS, and vessel tracking and tracing | 1 | TTI by radar | 5.2.2(1) |
2 | TTI by radar and Inland ECDIS in navigation mode, only safety relevant objects in the ENC | 5.2.2(2) to (4) 5.1.4(3) | ||
3 | As No 2, all objects in ENC | 5.1.4(4) | ||
4 | Inland ECDIS as No 3, additionally with water depths | 5.1.4(5) | ||
5 | Inland ECDIS as No 1, additionally with vessel tracking and tracing | 5.2.2(5) | ||
2.2 Strategic traffic information by ship reporting system | 1 | Database at RIS centre, reports via voice GSM, input in RIS centre manually | 5.2.3(5a) | |
2 | Database at RIS centre, reports via voice VHF, input in RIS centre manually | 5.2.3(5b) | ||
3 | Database at RIS centre, initial reports via electronic ship reporting (data GSM), input in RIS centre automatically, position reports via voice VHF | 5.2.3(5c) | ||
4 | As No 3, add. reports on positions and ETAs via vessel tracking and tracing systems, input in RIS centre automatically | 5.2.3(5d) | ||
5 | Database at RIS centre, add. electronic data interchange between RIS centres | 5.2.3(9) | ||
3. Traffic management | 3.1 Vessel traffic services (VTS) | 1 | Shore based radar stations, VTS centre, Inland ECDIS with radar overlay | 5.3.1(1) |
2 | As No 1, Inland ECDIS with radar overlay and target tracking | 5.3.1(3) | ||
3 | Inland ECDIS with vessel tracking and tracing information | 5.3.1(3) | ||
3.2 Lock and bridge management | 1 | Database for lock diary, registration of waiting times, local | 5.3.3(1a) | |
2 | As No 1, add. data exchange with other locks | 5.3.3(1b) | ||
3 | As No 2, add. transmission of waiting times to skippers (support of voyage planning) | 5.3.3(1c) | ||
4 | Optimising of lock circles by calculation of ETAs/RTAs for a chain of locks, emission of RTAs to skippers, input of positions of vessels by vessel tracking and tracing system | 5.3.3(1d) | ||
4. Calamity abatement support | 4.1 Ship reporting system for certain types of vessels and compositions | 1 — 5 | System configurations as No 2.2 | 5.4 |
4.2 Ship reporting system for all vessels | 1 — 5 | System configurations as No 2.2 | 5.4 | |
5. Voyage planning | 5.1 Fairway information | 1 | System configurations as Nos 1.1 to 1.3 | 5.5(2) |
5.2 Lock/bridge management, transmission of RTAs and waiting times | 2 | System configurations as No 3.2.4 |
inland navigation does not stop at borders of countries;
new IT developments in other modes of transport should be adopted in inland navigation in order to enable an integration of transport (multimodal transport on road, rail and waterway);
the different RIS systems reach their full benefit only when they are harmonised;
suppliers of equipment will not start producing hardware and software for RIS, if the standards and technical specifications are not drawn up.
these RIS guidelines as a framework;
IALA inland VTS guidelines;
inland ECDIS technical specifications;
Eelectronic ship reporting technical specifications;
notices to skippers technical specifications;
vessel tracking and tracing technical specifications (such as Inland AIS technical specifications);
inland radar requirements (future ETSI standard);
regional arrangement concerning the radio telephone service on inland waterways.
IHO, IEC as regards Inland ECDIS;
IALA as regards Inland VTS;
PIANC as regards river information services;
ITU, ETSI; IEC, IALA as regards Inland AIS;
ITU as regards inland VHF;
UN/ECE as regards special standards to be used in electronic ship reporting (e.g. EDIFACT, UN/LOCODE).
Directive 2005/44/EC of the European Parliament and of the Council of 7 September 2005 on harmonised river information services (RIS) on inland waterway in the Community (OJ L 255, 30.9.2005, p. 152).
Results available on CD from the Transport Research Centre (AVV), Rijkswaterstaat, PO Box 1031, 3000 BA Rotterdam, The Netherlands.
The final report of 15 March 2003 on the ARGO test operation with depths information can be downloaded from the web page www.elwis.de under the rubric ‘RIS-Telematikprojekte (ARGO)’.
Information available from the Transport Research Centre (AVV), Rijkswaterstaat, PO Box 1031, 3000 BA Rotterdam, The Netherlands.
Results available from the Transport Research Centre (AVV), Rijkswaterstaat, PO Box 1031, 3000 BA Rotterdam, The Netherlands and www.euro-compris.org.
Latest Available (revised):The latest available updated version of the legislation incorporating changes made by subsequent legislation and applied by our editorial team. Changes we have not yet applied to the text, can be found in the ‘Changes to Legislation’ area.
Original (As adopted by EU): The original version of the legislation as it stood when it was first adopted in the EU. No changes have been applied to the text.
Point in Time: This becomes available after navigating to view revised legislation as it stood at a certain point in time via Advanced Features > Show Timeline of Changes or via a point in time advanced search.
Geographical Extent: Indicates the geographical area that this provision applies to. For further information see ‘Frequently Asked Questions’.
Show Timeline of Changes: See how this legislation has or could change over time. Turning this feature on will show extra navigation options to go to these specific points in time. Return to the latest available version by using the controls above in the What Version box.
Access essential accompanying documents and information for this legislation item from this tab. Dependent on the legislation item being viewed this may include:
This timeline shows the different versions taken from EUR-Lex before exit day and during the implementation period as well as any subsequent versions created after the implementation period as a result of changes made by UK legislation.
The dates for the EU versions are taken from the document dates on EUR-Lex and may not always coincide with when the changes came into force for the document.
For any versions created after the implementation period as a result of changes made by UK legislation the date will coincide with the earliest date on which the change (e.g an insertion, a repeal or a substitution) that was applied came into force. For further information see our guide to revised legislation on Understanding Legislation.
Use this menu to access essential accompanying documents and information for this legislation item. Dependent on the legislation item being viewed this may include:
Click 'View More' or select 'More Resources' tab for additional information including: