S-100 Phase 1 is live: what survey contractors must change now

What changed

S-100 Phase 1 of the International Hydrographic Organization (IHO) entered into force in January 2026. This is no longer a development programme: the first set of S-100 product specifications is released for operational use, and S-100 ECDIS is legal for use from 1 January 2026.

Phase 1 covers seven product specifications, all of which entered into force in January 2026: S-101 (Electronic Navigational Chart, the successor to S-57), S-102 (Bathymetric Surface), S-104 (Water Level Information), S-111 (Surface Currents), S-124 (Navigational Warnings), S-128 (Catalogue of Nautical Products) and S-129 (Under Keel Clearance Management). S-124 and S-128 are part of that released Phase 1 set.

The release followed pre-operational testing and live trials rather than a single demonstration. One verified example is already in the water: the Australian Hydrographic Office ran the first live shipboard S-100 bridge trial in Sydney Harbour, with Tidetech supplying ocean data and OSI Maritime Systems the ECDIS, aboard two Carnival vessels, carrying S-104 and S-111 layers at 100 m resolution on 20-minute intervals (results due early June 2026); earlier work had been simulator-based. The reported value of S-100 in such exercises is qualitative – better situational awareness from layered, interoperable data – rather than any single audited performance figure, and contractors should treat headline percentage claims with caution.

The substantive point for survey practice is what S-100 is, not the marketing around it. S-100 is the IHO Universal Hydrographic Data Model: a common framework under which multiple product specifications share data structures, feature catalogues and metadata. Compliant systems can ingest near-real-time updates rather than waiting for full chart re-issues, and can combine layers from different specifications – bathymetry, currents, water levels, warnings – on one platform. That is the change that matters for how you acquire, process and deliver data.

Why this matters for survey contractors

S-100 is starting to appear in scopes of work from port authorities, national hydrographic offices and energy developers. Toolchains that have produced S-57 for years do not produce conformant S-100 deliverables without rework.

The modular structure of S-100 changes how data is organised. Instead of a single ENC cell carrying everything, deliverables separate into distinct components: gridded bathymetric surfaces, feature catalogues, metadata and uncertainty information, each with its own validation rules and tooling. Treating S-100 as a relabelled S-57 export produces files that may pass a syntactic check but do not carry the resolution, surface integrity or provenance that the specifications intend.

The reality on deck

Most commercial hydrographic processing environments remain S-57-native. As a matter of current industry practice, mainstream packages from vendors such as QPS and Teledyne CARIS add S-100 output through dedicated modules or conversion tools – for example CARIS HPD and its S-100 modules, or QPS Qimera and Fledermaus for S-102 surface export – rather than reworking the core processing flow, which was built around the legacy chart model. Confirm the specific module and version against each product in scope rather than assuming a package name implies full coverage. The practical consequence is parallel workflows.

Production is no longer purely hypothetical: Brazil’s Centro de Hidrografia da Marinha (CHM) produced its first S-101 ENC, the Port of Suape cell, validated against the S-101 ENC Product Specification Edition 2.0.0 with IHO RENC packages, and plans expansion from 2026. That is the kind of live reference a client may cite back to you when judging contractor capability.

Expect to deliver in both formats for an extended period. The IMO has set a dual-fuel transition – S-57 and S-101 ENCs carried in parallel – running until 1 January 2029, after which new IMO ECDIS Performance Standards apply. Until then, vessels still rely on S-57 ENCs in service, so contractors should plan for dual-format output across the transition window rather than a clean cut-over. That duplication carries real cost in validation, QC and documentation.

Metadata is no longer optional detail. S-100 expects explicit uncertainty information, feature attribution and data provenance: survey instruments, processing methods, uncertainty sources and QC measures, documented to a standard that a thinly documented ENC never had to meet. This underpins the integrated, frequently updated products clients now expect, and it adds processing time per survey. Budget and schedule for that overhead rather than discovering it during delivery.

Where clients and contractors get it wrong

1. Assuming automatic conversion is enough

Running existing S-57 results through a converter can produce files that validate, but they are not fit for purpose. The S-102 Bathymetric Surface specification expects gridded surface data appropriate to the survey’s resolution and purpose. Where an S-57 workflow relied on manual feature selection and selective depth retention, S-102 delivers the gridded bathymetric surface at the specified resolution. That affects acquisition density, storage, processing and archiving, so the change has to be planned upstream of conversion.

2. Ignoring dual-format delivery cost

Pricing an S-100 transition as a like-for-like swap fails. Delivering in two formats means two validation passes, two QC cycles and two documentation sets across the transition window. Contractors who omit that duplication from their bids either erode margin or cut corners on deliverable quality.

3. Underestimating QC time for feature attribution

The S-100 feature catalogues are more detailed than S-57 object classes, with richer attribution for wrecks, obstructions and seabed infrastructure: condition, reliability and provenance. QC has to reconcile that attribution against survey data and external sources, which remains a manual, labour-intensive task. Contractors new to S-100 often hit incomplete provenance only at final QC, and remediation after processing adds days to the schedule. Build provenance capture into the workflow from acquisition onward.

4. Neglecting software capability gaps

S-100 support is uneven across packages. One tool may export S-101 well but handle S-102 surfaces poorly; another may manage S-102 but struggle with S-128 catalogues. Confirm coverage across every product in scope before committing to S-100 output, and budget for additional modules or custom code to close gaps. Clients often assume their contractor is fully equipped; discovering a capability gap after award is an expensive lesson. Verify licences, compute and team training against the actual scope before you bid.

What needs to change in your survey specification

Survey specifications written for S-57 deliverables need revision. State explicitly which S-100 products are in scope – S-101, S-102, or additional specifications such as S-104 or S-111 where the contract requires them – with resolution, coverage and uncertainty thresholds defined per product.

Uncertainty has to be formalised. S-102 bathymetric products carry explicit per-node uncertainty, and survey deliverables must document total propagated uncertainty (TPU) computed to IHO S-44 standards – cite the edition and order structure directly, namely S-44 Edition 6.1.0 and the survey order required for the work, rather than a generic “IHO standards” reference. Where a workflow relies on rough TPU estimates, document the uncertainty sources, the calculation method and the verification procedure. Clients buying S-100 data will not accept loosely quantified uncertainty.

Adjust delivery timelines. Metadata generation, feature-attribution verification and the dual-format QC noted above take time, so allow additional lead time for S-100 deliverables over an equivalent S-57 scope rather than carrying over legacy turnaround commitments. Finally, tie deliverables to named software and versions: S-100 specifications and their validation rules evolve, and recording the toolchain version protects both parties if validation behaviour changes later.

What must change on your survey vessels

The value of S-100 comes from integrated product packages, so sensor capability shapes what you can deliver. Bathymetry alone exploits little of S-104 and S-111; realising those products may require water-level sensors, current profilers or additional positioning capability. Where a client’s scope actually calls for S-104 or S-111, a competitor delivering bathymetry with surface-current and water-level layers leaves a bathymetry-only bid offering a narrower product; where the scope does not require those layers, the gap does not bite. Vessel capability determines the product scope you can credibly tender for.

Calibration and validation records matter more under S-100’s update model, because clients expect more frequent reissue than S-57 allowed. Keep calibration checks, sound-velocity profiles and positioning validations documented so data can be reprocessed quickly when an update is required, rather than relying on summary field notes.

Implementation priorities

Start with a software capability review. Map your current processing chain against each S-100 product specification in scope and close any gaps with new modules or custom tooling before bidding S-100 work; winning a contract and then finding you cannot generate S-102 surfaces is an avoidable failure.

Train the team. Object mapping, metadata generation and validation differ from S-57 practice. Use publicly available S-100 sample datasets to rehearse the workflow and expose bottlenecks before production. Build documentation templates for acquisition, processing methods, uncertainty models and QC – the S-100 metadata requirements are extensive but largely standardised, so templates improve speed and consistency.

Update quoting and pricing models to reflect that S-100 output costs more than S-57: itemise dual-format delivery, metadata overhead and additional QC time so price-driven clients understand what they are buying. Engage national hydrographic offices early; they lead implementation in their areas and often provide validation tools, sample data and technical support.

What this means for contract negotiation

Pin down technical requirements precisely. Clients unfamiliar with S-100 may ask for “full S-100 compliance” without defining the products or thresholds; resolve that at the contract stage. Adding S-111 surface currents, for instance, implies current-profiling capability and the processing to support it, and that should be priced and scoped, not assumed.

Set realistic deadlines. Clients anchored on S-57 turnaround may not account for added S-100 processing; explain the dual-format lead time and negotiate rather than accept a deadline you will miss. Agree validation criteria up front – S-100 validators can return different results, so name the reference validator in the contract clause to avoid disputes when one tool flags what another accepts. Make it concrete: nominate the IHO S-100 test framework, or for ENC content the S-58 validation checks that S-101 inherits, as the criterion of record, rather than leaving “conformant” undefined.

The long view

S-100 is the most significant change to hydrographic data standards in a generation, and the transition is genuinely awkward: software is maturing, clients are still learning the requirements and validation practice is still settling. The dual-fuel window to 1 January 2029 gives the industry time, but, as already covered, it locks contractors into parallel workflows for years rather than a clean cut-over.

The competitive logic is straightforward. Clients increasingly value contractors who deliver genuine S-100 products – high-resolution surfaces, properly attributed features, documented uncertainty and update-ready data – over relabelled S-57. Reworking workflows, software and contract templates now, during the transition, is cheaper than scrambling once S-100 deliverables are routinely specified. The question is not whether to adapt, but how to do it without disrupting live projects: review software capability, train the team, build templates and rehearse on sample data before S-100 becomes the default in your tenders.

---

Based on: New milestone for S-100 ecosystem as Phase 1 enters into force. Additional references: the Australian Hydrographic Office / Tidetech / OSI Maritime Systems live S-100 bridge trial in Sydney Harbour (S-104 and S-111 layers; results due early June 2026); IHO S-44 Edition 6.1.0; and the Centro de Hidrografia da Marinha (CHM) first S-101 ENC for the Port of Suape.