1.1 It is advisable that the following considerations
are taken into account when planning testbeds as it will assist in
the harmonized reporting of testbed results.
1.2 When planning testbeds, the e-navigation solutions
selected should ideally be linked to user needs and the objectives
of e-navigation. Where possible, solutions should address gaps identified
in the e-navigation gap analysis.
1.3 It is recommended that testbeds take into
account a structured, transparent, objective and repeatable methodology.
Where the output is in the form of software tools, these should ideally
be open-source, with arrangements in place for collaboration, incorporating
user feedback and identified improvements.
2.1 It is advisable that, without restricting
innovation, testbeds align with the approved overarching e-navigation
architecture and solutions including the technical/operational services
in the Maritime Service Portfolios.
3
User and stakeholder involvement
3.1 Testbeds should ideally involve users and
stakeholders at every stage – from planning to implementation
and assessment of results.
4
Human-centred design and
quality assurance principles
4.1 Human-centred design and quality assurance
principles should be taken into account during the development of
e-navigation solutions.
5.1 The agreed Common Maritime Data Structure
(CMDS) is the IHO S-100 Geospatial Information (GI) Registry. Testbeds
should therefore preferably use the IHO S-100 framework for data modelling
and exchange. Other data model frameworks may be used for testbeds.
However, it is advisable that, for results to be of value to the development
of e-navigation, steps should be taken to incorporate solutions into
the IHO S-100 framework.
6
Reference to the e-navigation
documentation
6.1 It is advisable that testbeds highlight links
to user needs, gap analysis and solutions already identified.
7.1 Information on testbeds should be provided
to the Organization.