Nav 54-13
Nav 54-13
E
IMO
SUMMARY
Executive summary: This document is the proposed high level strategy for e-Navigation
submitted by the Correspondence Group, and also advises on the
methodology adopted to identify user needs. It also proposes an
implementation strategy for e-Navigation
Strategic Direction: 5.2
High-level Action: 5.2.4
Planned Output: 5.2.4.4
Action to be taken: Paragraph 27
Related documents: MSC/Circ.1091, MSC/Circ.878, MSC/Circ.346; resolution MSC.252(83);
MSC/Circ.982; NAV 53/22, NAV 53/13, NAV 53/13/1; COMSAR 12/11
and NAV 54/INF.3
Introduction
1 NAV 53 agreed that in order to progress the work on the e-Navigation strategy for
NAV 54, the intersessional Correspondence Group should be re-established under the
co-ordination of the United Kingdom. The Group includes representatives from different Flag
States, Maritime Agencies and Non-Governmental Organizations. Flag States who participated
include Australia, the Bahamas, Bolivia, Brazil, Canada, China, Denmark, Finland, Germany,
Japan, the Marshall Islands, the Netherlands, Norway, Panama, Poland, Portugal, the Republic of
Korea, South Africa, Singapore, Spain, Sweden, Turkey, the United Kingdom and the
United States. Other Governmental and Non-Governmental Organizations that participated
include APA, BIMCO, British Chamber of Shipping, CIRM, IALA, ICS, IEC, IFSMA, IHMA,
IHO, IMPA, INTERCARGO, INTERTANKO, MENAS, the Nautical Institute, and OCIMF.
For reasons of economy, this document is printed in a limited number. Delegates are
kindly asked to bring their copies to meetings and not to request additional copies.
I:\NAV\54\13.doc
NAV 54/13 -2-
2 NAV 53 also approved the terms of reference (see annex 1) for this Correspondence
Group. Specifically the Group was asked to:
.3 review the need to consult other maritime agencies and interest groups –
navigational practitioners, support agencies, research organizations, equipment
manufacturers and port managers; and
.3 generic high level user needs for ship and shore based users using the above
methodology;
4 In its work the Correspondence Group took into account relevant documents from
NAV 53, progress made at NAV 53 relating to the development of an e-Navigation strategy, the
guidance in MSC/Circ.1091 on Issues to be considered when introducing new technology on
board ship and MSC/Circ.878-MEPC/Circ.346 on Human Element Analysing Process (HEAP).
The Correspondence Group also acknowledges and is grateful for the work performed by other
stakeholders – in particular, the work done by IALA in identifying users groups and their
respective needs.
Background
Discussion
7 Based on the inputs from the intersessional Correspondence Group, COMSAR 11 and the
Working Group, NAV 53 provisionally finalized the following for e-Navigation:
The concept is based on the harmonization of marine navigation systems and supporting shore
services necessary to meet identified user needs.
8 NAV 53 agreed that the core objectives of the e-Navigation concept using electronic data
capture, communication, processing and presentation should be to:
.5 support the effective operation of contingency response, and search and rescue
services;
.7 integrate and present information onboard and ashore through a human interface
which maximizes navigational safety benefits and minimizes any risks of
confusion or misinterpretation on the part of the user;
.8 integrate and present information onboard and ashore to manage the workload of
the users, while also motivating and engaging the user and supporting
decision-making;
.9 incorporate training and familiarization requirements for the users throughout the
development and implementation process;
.10 facilitate global coverage, consistent standards and arrangements, and mutual
compatibility and interoperability of equipment, systems, symbology and
operational procedures, so as to avoid potential conflicts between users; and
I:\NAV\54\13.doc
NAV 54/13 -4-
9 NAV 53 agreed to the following expectations for the onboard, onshore and
communications elements of e-Navigation:
.1 Onboard:
Navigation systems that benefit from the integration of own ship sensors,
supporting information, a standard user interface, and a comprehensive system for
managing guard zones and alerts. Core elements of such a system will include,
actively engaging the mariner in the process of navigation while preventing
distraction and overburdening,
.2 Ashore:
The management of vessel traffic and related services from ashore enhanced
through better provision, co-ordination, and exchange of comprehensive data in
formats that will be more easily understood and utilized by shore-based operators
in support of vessel safety and efficiency, and
.3 Communications:
An infrastructure providing authorized seamless information transfer onboard
ship, between ships, between ship and shore and between shore authorities and
other parties with many related benefits, including a reduction of single person
error.
These have been used as the starting point for the development of user requirements:
10 There is a clear and compelling need to equip shipboard users and those ashore
responsible for the safety of shipping with modern, proven tools that are optimized for good
decision making in order to make maritime navigation and communications more reliable and
user friendly. The overall goal is to reduce errors. However, if current technological advances
continue without proper co-ordination there is a risk that the future development of marine
navigation systems will be hampered through a lack of standardization onboard and ashore,
incompatibility between vessels and an increased and unnecessary level of complexity.
13 A significant number of potential ship and shore-based users of e-Navigation have been
identified and are summarized in annex 3.
14 The needs of a typical SOLAS ship user and a generic shore authority have been used as
the basis for developing this strategy.
I:\NAV\54\13.doc
-5- NAV 54/13
15 IALA has developed a methodology for capturing evolving user needs (annex 4). It is
based on the elements contained within the accepted definition of e-Navigation and uses
templates to define specific user needs based on the harmonized: collection, integration,
exchange, presentation, analysis and human element aspects for all users. This methodology was
accepted by the Correspondence Group and distributed amongst members of IMO, IALA and
other maritime agencies and interest groups.
16 Following extensive feedback from Member States, other Maritime Organizations, and
interested parties; an analysis was conducted resulting in the identification of high-level generic
user needs for both ship and shore users. Annex 5 contains completed user need methodology
templates for the SOLAS mariner and shore authorities (including VTS, coastal surveillance,
SAR, counter pollution, port authorities, and other maritime services).
17 It is envisioned that more detailed user needs study may need to be performed in order to
identify users with specific needs that were not captured in the initial analysis.
18 The following high-level user needs are distilled from the user need analysis provided in
annex 5:
.7 Analysis:
e-Navigation systems should support good decision making, improve performance
and prevent single person error. To do so, shipboard systems should include
analysis functions that support the user in complying with regulations, identifying
risks, and avoiding collisions and groundings including the calculation of Under
Keel Clearance (UKC) and air draughts. Shore based systems should support
environmental impact analysis, forward planning of vessel movements,
hazard/risk assessment, reporting indicators and incident prevention.
Consideration should also be given to the use of analysis for incident response and
recovery, risk assessment and response planning, incident detection and
prevention, risk mitigation, preparedness, resource (e.g., asset) management and
communication.
1
S-Mode is the proposed functionality for shipborne navigation displays using a standard, default presentation,
menu system and interface.
I:\NAV\54\13.doc
-7- NAV 54/13
.8 Implementation Issues:
Training, good practices and familiarization relating to aspects of e-Navigation for
all users must be effective and established in advance of technical
implementation. The use of simulation to establish training needs and assess its
effectiveness is endorsed. e-Navigation should as far as practical be compatible
forwards and backwards and support integration with equipment and systems
under existing IMO carriage requirements. The highest level of interoperability
between e-Navigation and external systems should be sought where practicable.
19 The development of the e-Navigation strategy has followed a top-down, holistic approach
through the Correspondence Group and in close cooperation with the IALA e-Navigation
Committee (e-NAV). As identified in the report of NAV 53, it is essential that the strategy be
based on a structured methodology and logical phases. The strategy has taken into account the
previous work done by the Correspondence Group, the recommendations of COMSAR 11 and
NAV 53 on the identification of essential functions for shipboard systems under the e-Navigation
strategy (NAV 53/13/1) and work done by IALA in developing a methodology for capturing and
defining user needs.
e-Navigation Strategy
20 In order to implement e-Navigation several steps are required. This includes a strategy
comprising a number of elements (listed below), and additionally a gap analysis, cost benefit
analysis and the creation of a detailed implementation plan. The implementation plan will need
to identify responsible jurisdictions which would in turn be responsible for determining
appropriate methods of delivery. Implementation of the strategy will also need to take into
account public relations and promotion of the e-Navigation concept to key stakeholder and user
groups.
21 In order to capture evolving user needs, it is important that the implementation strategy
elements remain under review. A structured approach will be required to capture evolving user
needs, making use of the existing agreed methodology, to incorporate any ensuing changes into
the strategy and implementation plan.
.1 Architecture:
The overall conceptual, functional and technical architecture will need to be
developed and maintained, particularly in terms of process description, data
structures, information systems, communications technology and regulations.
.2 Human Element:
Training, competency, language skills, workload and motivation are identified as
essential. Alert management, information overload and ergonomics are prominent
concerns. These aspects of e-Navigation will have to be taken into account in
accordance with IMO Human Element work.
I:\NAV\54\13.doc
NAV 54/13 -8-
.4 Position Fixing:
Position fixing systems will need to be provided that meet user needs in terms of
accuracy, integrity, reliability and system redundancy in accordance with the level
of risk and volume of traffic.
.6 ENCs:
At NAV 53 IHO reported, “There would be adequate coverage of consistent
ENCs by the time any further mandatory carriage requirements were likely to be
adopted by IMO”. The Sub-Committee was also of the opinion that the
availability of ENCs worldwide was most important and requested IHO and
Member Governments to continue their efforts in increasing the coverage.
E-Navigation will likely benefit from increased functionality of the future IHO
S-100 standard.
.7 Equipment Standardization:
This part of the work will follow the development of performance standards and
will involve users and manufacturers.
.8 Scalability:
IMO Member States have a responsibility for the safety of all classes of vessels.
This may include the scalability of e-Navigation for all potential users. Extension
of the concept to non-SOLAS vessels should be seen as an important task, to be
addressed, in the first instance through consultation on user requirements.
Strategy Implementation
24 The identification of commonalities across users making best use of existing capabilities
and systems should be considered.
I:\NAV\54\13.doc
-9- NAV 54/13
1. requested to note the high-level user needs and support the proposed e-Navigation
Strategy with its strategic elements; and
2. invited to consider an appropriate course of action for the adoption of the Strategy
at MSC 85.
***
I:\NAV\54\13.doc
NAV 54/13
ANNEX 1
1 NAV 53 agreed to progress the development of an e-Navigation strategy for NAV 54.
The intersessional Correspondence Group was re-established under the coordination of the
United Kingdom.
2 NAV 53 also approved the terms of reference for this Correspondence Group which
should:
.3 review the need to consult other maritime agencies and interest groups –
navigational practitioners, support agencies, research organizations, equipment
manufacturers and port managers; and
***
I:\NAV\54\13.doc
NAV 54/13
ANNEX 2
The original submission to MSC on the development of a work programme for e-Navigation
(MSC 81/23/10) highlights the compelling need to equip the master of a vessel and others
responsible for the safety of shipping with modern (but proven) tools to improve the reliability of
marine navigation and communications thereby reducing the potential for loss of life, injury,
environmental damage (both through normal operations, e.g., emissions, and in accidents, e.g.,
spillages) and unnecessary commercial cost. A recent report by the International Union of
Marine Insurance indicates that raising trends of marine accidents both in terms of numbers and
costs are those associated with collisions and groundings. There are numerous examples of
accidents and incidents, especially collisions and groundings, which subsequent investigation and
analysis suggests they might have been avoided had there been suitable input from the
appropriate technologies in the navigation decision-making process. The following table
summarizes the causes of collisions and groundings during the last ten years. The causal data
and examples cited in the table are derived from Nautical Institute (NI) research into collisions
and groundings2. This research indicates that, of the collisions and grounding investigated,
around 60% are caused by direct human error. Most accidents and incidents occurred outside of
VTS and Pilotage areas “indicating that VTS and Pilotage works effectively considering that
most close quarter situations take place in these areas3”. The Nautical Institute research results
are summarized in the following table:
Collisions Groundings
24% were attributed to insufficient 17% were attributed to poor or no
assessment of the situation passage plan
23% were attributed to poor or no 18% were due to poor bridge
lookout, in addition, in 13% of management
collisions one vessel was completely 12% were due to no lookout/one man
unaware of the other vessel on the bridge
Other causes were: 14% were due to poor navigation
o confusion in VHF 22% were due to fatigue, including
communications (9%) 8% that were due to the OOW falling
o infractions of COLREGs (8%) asleep
o fatigue including officer of the 14% were due to poor
watch (OOW) falling asleep communication with the pilot
(11%) 3% were caused by a lack of
o poor bridge management (4%) procedures
o pilot/master communications
breakdown (1%)
The NI report quoted that “in 43% of all the collision cases involving merchant vessels that were
investigated by the United Kingdom’s Marine Accident Investigation Branch (MAIB) over
a 10-year period, the watchkeeper was either completely unaware of the other vessel until time of
collision or only became aware of the other vessel when it was too late to take effective avoiding
2
The analysis uses data derived from the Nautical Institute and from the UK Marine Accident Investigation
Branch (MAIB), Australian Transport Safety Bureau (ATSB), Swedish Accident Investigation Board, Transport
Accident Investigation Commission (NZ), Transport Safety Board of Canada, ,Marine Accident Inquiry Agency
(Japan), Isle of Man Ship Registry, Irish Marine Casualty Investigation Board (IMCIB), and Accident
Investigation Board of Finland.
3
Seaways, The International Journal of the Nautical Institute, July 2007, pages 4 and 5.
I:\NAV\54\13.doc
NAV 54/13
ANNEX 2
Page 2
action”. This is almost entirely due to very poor watchkeeping, where lookouts are either not
present or ineffective, and the Officer of the Watch (OOW) is asleep, fatigued, absent, distracted
or totally disengaged with the task of keeping a safe navigation watch. Despite advances in
bridge resource management training, it seems that the majority of watchkeeping officers make
critical decisions for navigation and collision avoidance in isolation, due to a general reduction in
manning.
The IMO human element vision principles and goals (Resolution A.947(23)) contains the
principle: ‘In the process of developing regulations, it should be recognized that adequate
safeguards must be in place to ensure that a “single person error” will not cause an accident
through the application of these regulations.’
IMO MSC/Circ.878 states: ‘A single person error must not lead to an accident. The situation
must be such that errors can be corrected or their effect minimized. Corrections can be carried
out by equipment, individuals or others. This involves ensuring that the proposed solution does
not rely solely on the performance of a single individual’. In human reliability analysis terms,
the presence of someone checking the decision-making process improves reliability by a factor
of 10. If e-navigation could assist in improving this aspect, both by well-designed onboard
systems and closer cooperation with vessel traffic management (VTM) systems, risk of collisions
and grounding and their inherent liabilities could be dramatically reduced.
Although e-Navigation would have ameliorated the situations described above, technology alone
would not have provided a complete solution but there is a need to also recognize the role of the
practice of good seamanship, the provision of suitable training and the use of procedures.
***
I:\NAV\54\13.doc
NAV 54/13
ANNEX 3
The tables below provide preliminary lists of e-Navigation users classified into:
shipborne users, and
shore-based users.
Shipborne users
Generic SOLAS vessels
Commercial tourism craft
High speed craft
Mobile VTS assets
Pilot vessels
Coastguard vessels
SAR vessels
Law enforcement vessels (police, customs, border control, immigration, fisheries
inspection)
Nautical assistance vessels (tugs, salvage vessels, tenders, fire fighting, etc.)
Counter pollution vessels
Military vessels
Fishing vessels
Leisure craft
Ferries
Dredgers
AtoN service vessels
Ice patrol/breakers
Offshore energy vessels (rigs, supply vessels, lay barges, survey vessels, construction
vessels, cable layers, guard ships, production storage vessels)
Hydrographic survey vessels
Oceanographic research vessels
Shore-based users
Ship owners & operators, safety managers
VTM organizations
VTS centres
Pilot organizations
Coastguard organizations
Law enforcement organizations
National administrations
Coastal administrations
Port authorities
Security organizations
Port state control authorities
Incident managers
Counter pollution organizations
Military organizations
Fairway maintenance organizations
I:\NAV\54\13.doc
NAV 54/13
ANNEX 3
Page 2
AtoN organizations
Meteorological organizations
Hydrographic Offices/Agencies
Ship owners & operators, logistics managers
News organizations
Coastal management authorities
Marine accident investigators
Health and safety organizations
Insurance and financial organizations
National, regional and local governments and administration
Port authorities (strategic)
Ministries
Marine environment managers
Fisheries management
Tourism agencies (logistics)
Energy providers
Ocean research institutes
Training organizations
Equipment and system manufacturers and maintainers
***
I:\NAV\54\13.doc
NAV 54/13
ANNEX 4
User:
[Define user here i.e. Merchant mariner, Flag administration, VTS operator etc.. ]
Primary need:
[State primary need as a clear mission statement here e.g., “e-Navigation should
support mariners in the maintenance of safe passing, safe clearing distances and
collision avoidance”]
I:\NAV\54\13.doc
NAV 54/13
ANNEX 4
Page 2
I:\NAV\54\13.doc
NAV 54/13
ANNEX 4
Page 3
Analysis “e-Navigation should support the user [Analysis needs may refer
through the appropriate analysis of data to any additional
and information to support the primary functionality for decision
need.” support tools, or the rapid
and systematic processing
of routine tasks..]
Human “e-Navigation should support the user [This section should be
Element through the application of Human used to identify all user
Issues Element principles to support the needs related to the
primary need.” human element on board
and ashore, (such as
effective training,
competencies,
familiarization, human
centred work
environment, distraction
from primary tasks,
human engagement,
workload, fatigue and job
satisfaction).]
Any other Comment:
[This section should be used to identify any restrictions or limitations assumed when
defining the primary need, (for e.g., when defining ‘safe navigation’ you might state
that the task of ‘grounding avoidance’ has been dealt with separately for
simplification. Or to make any other suggested ‘user needs’ that you feel have not been
addressed elsewhere in the exercise.]
***
I:\NAV\54\13.doc
NAV 54/13
ANNEX 5
e-Navigation High Level User Needs for SOLAS Mariners and for Shore Authorities
I:\NAV\54\13.doc
NAV 54/13
ANNEX 5
Page 2
I:\NAV\54\13.doc
NAV 54/13
ANNEX 5
Page 3
I:\NAV\54\13.doc
NAV 54/13
ANNEX 5
Page 4
Primary need: Effective management of the maritime domain, including support for safe
and efficient navigation, security, and the protection of the marine environment.
I:\NAV\54\13.doc
NAV 54/13
ANNEX 5
Page 5
effectively manage the maritime and supporting the decision making process.
domain. Training, certification, good practices, and
familiarization need to be addressed as
appropriate for all functional aspects of e-
Navigation.
Consideration should be given to ergonomics,
ease of use, standardization, and the working
environment to optimize human performance.
Any other Comment:
This template describes the basic user needs for e-Navigation from the perspective of a generic
shore authority user, including VTS, Coastal Surveillance, SAR, Counter Pollution,
Port Authorities, and other maritime services. Further or alternate functional requirements for
shore based users will be contained in other templates.
___________
I:\NAV\54\13.doc