S101 User Requirements Workshop

1
S-101 User Requirements Workshop

• Breakout Group B
• Day 1

2
How should overlapping and data of different
scales be managed / organized by S-101 for ECDIS ?

• Scale management
• compilation scale optimum display scale
• list of allowed scales
• no overlap in a single scale, but another scale
  can have any overlap
• Reduction of overlapping data
• publish aids to navigation as separate layer
• publish other objects as before
• Product catalogs
• should be based on real coverage, not boxes

3
Should the concept of Navigation Purpose Code be
carried forward to S-101 ? Should it be modified
or replaced by other arrangements ? If so, what
and how ? What are impacts ?

• Navigation Purpose is only useful for Chart
  Catalog purposes
• Use of Navigation Purpose for chart drawing
  selections should be discontinued

4
What improvements can be made to the current
arrangements for loading and managing permits ?

• Permits are distribution issue
• End users want to pay for a certificate which
  proves that the vessel has a contract for up to
  date charts. This certificate should have an
  appendix which specify charts covered by the
  contract
• End users want to see all charts as managed
  database instead of individual cells. Especially
  they need a date up to which his database is
  updated.
• Management of individual expiry dates is
  difficult. Easy permit is based on single expiry
  date

5
What improvements can be made to avoid low-level
data warning messages appearing on loading ENCs?

• Limit warning to severe only
• update synchronization, missing files, CRC etc.
• Revise IEC Test Data Set
• current test data set include examples and
  instructions for illegal object, illegal
  attribute and invalid value of attribute gt
  detection of them is checked in type approval
• one purpose is to check correct presentation of
  question mark. This should remain but
  instructions should clearly limit use of test to
  displayed chart
• continue in next page

6
What improvements can be made to avoid low-level
data warning messages appearing on loading ENCs?

• How to inform manufacturer, data provider and
  data producers
• For remaining warnings ECDIS should make a single
  log-file, which can be given for data producer
• How user could now if the viewed chart is ok
• ECDIS should have a mechanism to indicate if a
  cell has problem with up to date state
• How manufacturers and type approval bodies know
  what to do
• somewhere there should be clear written
  instructions

7
How should overlapping and data of different
scales be managed / organized by S-101 for ECDIS ?

• Scale management
• compilation scale optimum display scale
• list of allowed scales
• Reduction of overlapping data
• publish aids to navigation as separate layer
• publish other objects as before
• Product catalogs
• should be based on real coverage, not boxes

8
S-101 User Requirements Workshop

• Breakout Group B
• Day 2

9
What technical options are available for plug
and play-type upgrading in the ECDIS equipment
of things like feature catalogues, symbol
libraries, et cetera ?

• Feature catalogue
• easy case, everybody agrees machine readability
  and publishing by publisher of Product
  specification (e.g. S-101 by IHO, AML by NATO
  etc.)
• format of machine readable catalogue should be
  defined in S-100. (most suitable format e.g. ISO
  8211 or XML or ? must be agreed)
• version of feature catalogue should be linked to
  publishing of new version of Product
  specification. Consider minor and major version
  numbering.

10
What technical options are available for plug
and play-type upgrading in the ECDIS equipment
of things like feature catalogues, symbol
libraries, et cetera ?

• Portrayal library
• open standard to do everything by machine
  readable files is technically possible, but
  difficult to create and result is not optimal for
  performance of drawing
• OEMs see different presentation as a possibility
  to differentiate in competition
• plug and play should be done by individual OEMs
  and this process should be type approved by each
  OEM
• version of portrayal library should be linked to
  publishing of new version of Product
  specification (S-101, AML etc.). Consider minor
  and major version numbering.

11
What technical options are available for plug
and play-type upgrading in the ECDIS equipment
of things like feature catalogues, symbol
libraries, et cetera ?

• Portrayal library (continued)
• machine readable register of symbols to be
  discussed in plenary
• simple or complex format ?
• who maintains ?
• who pays ?
• who needs it ?
• etc.

12
What technical options are available for plug
and play-type upgrading in the ECDIS equipment
of things like feature catalogues, symbol
libraries, et cetera ?

• Portrayal library (continued)
• machine readable lookup tables to be discussed in
  plenary
• viewing groups
• chart alarms groups ?
• be part of feature catalogue ?
• simple or complex format ?
• who maintains ?
• who pays ?
• who needs it ?
• etc.

13
How might this affect type approval of ECDIS ?

• Type approval should be more flexible
• can this be achieved ? IMO and IEC normally do
  these things not IHO
• Proposed method for plug and play includes both
  machine readable files and software upgrade by
  individual OEM
• result is that software changes, which
  traditionally implies new type approval
• IHO needs to provide documentation of delta for
  version changes as well as dataset for testing