How the S-100 framework can enable true autonomy for USVs

The maritime sector is entering what is often called the S-100 era. Much of the discussion so far has focused on compliance timelines and new product specifications. However, the deeper importance of S-100 lies in how hydrographic and maritime data can be structured and integrated for use by a wide range of software systems, supporting both human-facing applications and machine-driven decision processes. So what benefits does this bring in practice? As an example, rather than introducing fundamentally new navigational semantics compared to S-57, the significance of the new chart product specification S-101 lies in how chart data can be consistently integrated with other maritime datasets within a common framework. This shift is especially important for the development of autonomous and semi-autonomous maritime systems. 

Today’s uncrewed surface vehicles (USVs) are equipped with many sensors. They use GNSS, INS, radar, Lidar, cameras and onboard data processing to observe their surroundings. Despite these capabilities, most maritime autonomous systems still depend on human supervision, predefined routes or very cautious operating limits. One major reason is not the lack of data, but the difficulty of turning maritime information into structured inputs that can be used directly by navigation and mission software.

Why autonomy struggles with chart-based information 

Human navigators combine many sources of information when making decisions. They use charts, tides, currents, traffic rules and local knowledge together. Traditional Electronic Navigational Charts (ENCs) based on S-57 contain structured digital features and attributes, and they are accurate and reliable. However, in operational practice they have been primarily deployed through ECDIS implementations that emphasize standardized portrayal and human interpretation, rather than broader machine-to-machine integration across multiple data domains. 

For autonomous systems, using chart information outside this display-focused environment is not simple. While a USV can identify features such as traffic separation schemes or restricted areas in S-57 data, the way this data is commonly implemented and accessed does not always provide standardized, machine-ready relationships or explicit links to other maritime information sources. This makes it harder to combine chart data with dynamic environmental data and operational rules inside a single decision process. 

S-100 does not change the basic meaning of most chart features, but it does change how different types of maritime data can be modelled, related and delivered together. It provides a common framework that enables clearer relationships between objects, improved handling of temporal aspects, and consistent data structures across multiple product specifications. This makes it easier to use maritime data as direct input to navigation and mission software, rather than only as background information for display. 

S-101 as part of a navigation knowledge system 

S-101 is the new chart product specification within the S-100 framework. The features and attributes in S-101 are largely similar to those in S-57, but they are now part of a broader data environment that is designed to work with other S-100 products in a consistent way.

A USV using S-101 data can identify hazards, traffic lanes, restricted areas and depth limits, just as with S-57. The key difference is that S-101 is designed to operate within a multi-product S-100 ecosystem, allowing chart information to be linked more systematically with other standardized maritime datasets and processed together within different types of software systems, including – but not limited to – ECDIS. When combined with onboard decision-making and rule-based systems, S-101 can contribute to a broader navigation knowledge representation rather than acting solely as a display-oriented chart product. 

For example, a traffic separation scheme can be treated not only as a chart feature, but also as part of a set of navigation constraints that influence route selection and vessel behaviour. Depth areas can be evaluated together with vehicle draft, expected squat and predicted water levels. This supports navigation that is based on operational limits and safety rules rather than fixed waypoints alone. This approach allows navigation to move towards constraint-based planning, where USVs can evaluate and adjust routes continuously using standardized and interoperable data inputs, instead of being followed rigidly once they are set. 

Integrating S-100 layers for better decisions 

The real strength of S-100 becomes clear when chart data is combined with other S-100-based products. Safe navigation depends not only on where hazards are located, but also on how conditions change over time. S-104 water level information allows clearance to be evaluated using actual or predicted tides. S-111 surface current data supports planning that considers drift and energy use. High-resolution bathymetry from S-102 supports under-keel clearance management more precisely, which is important for larger or heavily loaded USVs. 

When these layers are used together, route planning becomes time dependent. In operational or pilot deployments where such data is available, a system can evaluate not only whether a route is safe, but also when it is safe and what operational cost it may involve. For offshore missions such as survey support, environmental monitoring or offshore wind operations, this can improve safety and efficiency and reduce the need for human intervention. Instead of cancelling or delaying a mission when conditions are poor, an autonomous system could adjust timing, route or operating speed to remain within safe limits while still meeting mission goals. 

From navigation to mission-level reasoning 

As S-100 data becomes part of onboard autonomy systems, charts and environmental data can support more than basic navigation. Autonomous systems can compare multiple route options while considering safety, legal restrictions, energy use and mission needs such as data quality or station-keeping accuracy. This is especially useful in busy or changing environments like ports, offshore construction sites and coastal waters.

A USV can respond to changing conditions while staying within defined operational boundaries. Human operators still play an important role. They define mission goals, safety limits and acceptable risks. The autonomous system handles detailed execution within those limits.  

Implications for hydrographic offices and data producers 

As more systems rely on machine processing of maritime data, the role of hydrographic offices and data producers continues to change. In the past, success was measured mainly by how clearly information could be displayed to human users. Today, data must also be consistent, well-structured and suitable for automated use. 

Small differences in how features are encoded or updated can have larger effects on autonomous systems than on human users. Clear definitions, reliable update cycles and good handling of uncertainty become even more important. Dynamic products also raise questions about how often data should be refreshed and how users can trust short-term predictions. 

Nowadays, hydrographic offices are not only chart producers, but also providers of operational data used directly in navigation systems. This increases the need for consistent implementation of standards and close cooperation with system developers and regulators. 

Challenges and realities of S-100 adoption 

Although the S-100 has been available for some time, real-world adoption has been slow. One reason is that global coverage of S-101 is still incomplete, and many regions continue to rely on S-57 data. This makes it difficult for system developers to depend fully on S-100 products in operational systems. Another challenge is the cost and complexity of updating production and validation systems. Hydrographic offices need new tools, new workflows and new training to support S-100 products. This transition takes time and funding, making it especially difficult for organizations with limited resources. 

Certification and legal responsibility are also important concerns. When autonomous systems use dynamic data such as water levels and currents, it is not always clear how this information can be certified for safety-critical use, or who is responsible if decisions based on predicted data lead to incidents. Regulators are still developing rules for maritime autonomous surface ships, and these rules are not yet fully aligned with technical data standards. 

Onboard integration presents further difficulties. Offshore communication bandwidth, while improving with solutions such as satellite broadband, still needs to be managed carefully and can affect how frequently large data volumes are updated or transferred. Processing multiple data layers in real time also requires reliable computing systems and strong data quality checks to avoid using outdated or inconsistent information. These issues do not mean that S-100 is unsuitable for autonomy, but they show that the main barriers are not only technical standards. They also include infrastructure, regulation, trust and long-term investment. 

Conclusion 

Sensors allow autonomous maritime systems to observe their surroundings, and software allows them to react to what they see. The full benefits of S-100 for autonomy will not appear overnight. They depend on data coverage, production systems, certification processes and regulatory acceptance. However, as these parts of the ecosystem mature, S-100 is likely to play a key role in moving maritime autonomy from controlled trials towards wider and more reliable operational use.