IN Brief:
- Saab has introduced a new 9LV naval combat-system architecture covering combat management and Ceros-linked fire control.
- Standardised data handling and zero-trust security are combined with separation between critical combat functions and cloud-native applications.
- The design targets both major combatants and smaller vessels, with future integration of crewed and uncrewed platforms in view.
Saab has introduced a new architecture for its 9LV naval combat system, combining standardised data handling with cyber security controls intended to let warships add software capabilities without disrupting essential combat functions. The 3 November launch covers the wider 9LV combat system, its combat management element, and fire control equipment associated with the Ceros director family.
Saab’s data-centric approach uses a standardised information model to carry information between sensors, weapons, command functions, and connected units. The redesigned architecture also separates mission-critical combat processes from more flexible cloud-native applications. Ship operators could then develop or replace selected software functions while keeping weapon-control processes subject to stricter integration and qualification requirements.
A combat management system receives measurements and reports from radar, electro-optical equipment, sonar, communications links, and other sources. The information must be correlated into tracks before an operator can assess a contact and, where authorised, connect it to an appropriate defensive or offensive system. Differences in data formats, timestamps, and track identities can make that process more difficult, especially when information arrives from multiple platforms.
A common information model is intended to reduce the number of custom data conversions between participating systems. When an additional radar or information-sharing application is introduced, its outputs must still be mapped correctly to existing track identities, timing references, and sensor confidence information. The architecture provides a basis for integration; the resulting tactical picture depends on the quality of the measurements and the way the combat system processes them.
Zero-trust cyber security is another component of the architecture. Under that model, connections and requests between applications and devices are authorised according to their identity and permissions rather than automatically trusted because they originate on a ship network. Access controls, software configuration, and segregation between equipment of differing criticality become part of the system integration work, alongside the testing needed to preserve combat functions when communications are disrupted.
For an in-service warship, the separation between critical and adaptable applications may allow planning, display, and information-sharing functions to change on a different schedule from the core combat system. Updates that influence the tactical picture still require checks for data integrity, operator workload, and compatibility with existing decision processes. Saab’s release describes the approach but does not associate it with a specified ship refit or contracted software deployment.
The launch encompasses 9LV Combat System, its combat management functions, and the 9LV fire control system with Ceros. Saab’s established 9LV fire control range integrates director equipment with shipborne guns or other effectors, while the broader combat system connects those engagement functions to sensors and command decisions. Introducing a new architectural generation across the portfolio does not establish that every vessel fitted with an earlier 9LV configuration has received the redesign.
An engagement-quality track imposes tighter demands than a general surveillance display. Weapon control must receive sufficiently accurate and timely sensor information, account for the ship’s movement, and maintain an assured connection between tracking equipment and the firing solution. Core combat functions are therefore subject to predictable timing, interface, and safety requirements even when other applications can be updated more readily.
Saab also identifies interoperability with allied forces as a design objective. Ships may need to exchange information with aircraft, land command systems, and other vessels while preserving the source and meaning of the data. NATO-aligned information exchange can contribute to a shared operating picture, although integration still depends on the particular datalinks, communications equipment, and security permissions installed by each customer.
The proposed architecture is intended for major multi-mission combatants as well as smaller naval vessels, although their installation constraints differ considerably. Large ships can accommodate several command positions, multiple sensors, and redundant communications paths. A patrol vessel has less electrical capacity, cooling, equipment space, and crew availability, making the selection and integration of functions central to the practical configuration.
Information from uncrewed surface and underwater systems could also enter a vessel’s tactical picture through the standardised model. Such inputs need their source, timing, location, and reliability preserved when they are correlated with observations from the ship’s own sensors. A remote vehicle that drops its connection or sends intermittent observations creates a different track-management problem from a permanently installed, locally connected radar.
The 3 November introduction establishes the architecture and its intended applications, with the first ship installation and customer configuration still to be announced. The level of separation between core functions and cloud-native applications will depend on the equipment specified, its interfaces, and the acceptance regime used by the customer navy.
Naval combat systems routinely outlast individual sensors, displays, and communications standards. Saab is addressing that lifecycle through a common data model and differentiated software functions, while retaining the need to validate the complete installation whenever it is modified. Shipboard integration and qualification will provide the first programme-specific evidence of how the new 9LV architecture performs.
