
867
integrity monitoring (RAIM) was included for all
GNSS/RNSS receivers, but currently not all
performance standards require that the results of
RAIM should be used for the provision of status and
integrity information contributing to alert
management and an integrity warning of system
malfunction, non-availability or discontinuity, and
they should be provided to users within 10 sec.
Similar concern arises regarding SNR or
augmentation data needed by advanced RAIM
(ARAIM). The EUSPA research shows that maritime
users still have very basic knowledge of RAIM
algorithms in GNSS receivers and their interpretations
[EUSPA, 2021].
The discussion at NCSR finalized with request to
MSC for extension of the completion year to 2024 and
alteration of the scope of this output to develop a
framework document instead of strict performance
standards. Anyway, the MSC during its 107 session
noted that the urgency and possible implications for
existing performance standards of a change of scope
of the output (consolidation of performance
standards) had not been thoroughly considered by the
NCSR, and NCSR had too high current workload to
proceed with this output right away. Doubts if the
intended application of the new resolution would be
both for existing and newly installed receivers were
also expressed. So, the final decision was not to agree
to extend the target completion year of the
GNSS/RNSS performance standards output and to
move the output “Development of generic
performance standards for shipborne satellite
navigation system receiver equipment” to the post-
biennial agenda until a clear indication of the new
scope of the work is conducted and information on
the associated implications are provided by the NCSR.
5 DISCUSSION
Some of the concerns raised by the opposition to the
new generic performance standards for shipborne
satellite navigation system receiver equipment can be
mitigated rationally:
1. Developing a standard to combine all GNSS PS into
a single PS.
As described in the report of the CG, the CG
recognized that there are both common aspects for
all GNSS/RNSS, as well as certain aspects of the
individual PS which only apply to the individual
systems given their different technologies used. As
such the development of a single minimum PS
applicable for all GNSS/RNSS receivers would not
adequately address all system specific
requirements currently described and agreed to by
IMO in the individual PS. To resolve this issue the
CG developed the presented structure of the
Generic PS to contain the minimum PS aspects
applicable to all GNSS in the annex of the draft
MSC Resolution. But to also capture the aspects of
the individual GNSS PS only applicable to an
individual PS, appendices are suggested to contain
specific receiver requirements for any GNSS/RNSS
to be included in the new Generic GNSS/RNSS
receiver PS. This way a single MSC resolution is
suggested to address both generic as well as
individual PS components.
2. The Generic GNSS/RNSS PS should reduce the
administrative burden and avoid the need for type
new approvals for existing systems.
To address this concern the recommended new
MCS Resolution should include a numbering and
versioning schema for both the generic part
(Annex) as well as the individual parts per
GNSS/RNSS (Appendices). The type approval
would be executed with both the generic
specifications (Annex) as well as the applicable
individual parts (Appendix or, for multi receivers
Appendices). If a system is to be certified for BDS
as an example, it would be certified according to
version 1 of annex relevant part as well as version
x of relevant appendix. This way the addition of a
next appendix (for example for Galileo) will have
no affect to any BDS receivers, as well as any
changes to another appendix.
3. The current GNSS/RNSS system administrations
should individually be able to decide of the mi-
gration from the individual PS to the Generic PS.
The shifting of data from current individual
performance standards to the new generic
template is in sole discretion of GNSS/RNSS
system administration – the performance
standards in new format must be input to MSC,
adopted and the previous ones revoked. It is
recommended to perform this migration once an
update of the system PS is necessary, as then new
type approval is necessary anyhow. Member states
or organizatio
ns (like EC) who do not want to
switch to new template will have their standards
written as they are, until the time they decide to
suggest amendments to the PS of the GNSS/RNSS
they are responsible for.
4. The suggested PS doesn’t include an existing
GNSS/RNSS and as such is currently not appli-
cable to any system.
This is a correct statement, and it is intentionally
done this way. During the development of the
framework of this single generic PS all existing
GNSS/RNSS have been included as appendices.
This was done to ensure that all existing GNSS PS
can be merged into the suggested Generic
Standard. But to avoid unnecessary administrative
actions, like re-type approval, only a template has
been developed. The appendix FG-1-1 for QZSS,
FG-1-2 for Galileo and FG-1-3 for BDS have been
added for illustration purposes only. According to
stipulations in the proposed standard the
respective organization could decide when they
want to migrate.
5. The document with United States comments [IMO,
2022b] or other additional requirements.
Additional requirement for GNSS/RNSS
equipment could be added individually to a
system relevant appendix. New functional
requirement would not have to be applicable to
existing individual GNSS/RNSS PS or it can reduce
the administrative burden to the organizations as
by one simple addition to the generic part it
becomes applicable to all included GNSS/RNSS PS.