Lockheed baseline shifts Navy software cadence

Lockheed Martin has delivered the first Integrated Combat System-enabled baseline to the US Navy, advancing a shift towards common combat-system infrastructure, containerised software, and a predictable upgrade rhythm across the surface fleet.

The delivery centres on the Aegis BL9.C3.0 package. It is the first baseline compiled from Lockheed Martin’s Forge development environment and introduces a re-architected display component, Tactical Platform as a Service, and a suite of new operational capabilities. Tactical PaaS establishes the foundation for containerised software, with follow-on deliveries planned to integrate additional capabilities, sensors, effectors, and software.

A six-month operating cadence for updates and certifications is now being introduced for fleet fielding. Naval combat systems have historically been powerful but complex, with major upgrades often tied to long shipyard periods, bespoke integration cycles, and platform-specific configurations. A common baseline is intended to reduce that friction by allowing capability to be developed once and deployed more predictably.

The US Navy’s surface fleet faces a threat environment moving faster than traditional upgrade cycles. Anti-ship missiles, hypersonic glide vehicles, ballistic missiles, cruise missiles, drones, electronic warfare, cyber threats, and contested sensors all place pressure on ship combat systems. A destroyer or cruiser may remain in service for decades, while its software and sensor-effector integration need to evolve far more quickly.

The Integrated Combat System concept treats combat architecture as a scalable, netted system rather than a series of isolated shipboard configurations. In practical terms, that means common software, common compute infrastructure, reusable applications, and a clearer route to deploy updates across multiple ships. The goal is fleetwide commonality, not better performance on one vessel alone.

Manufacturing and integration work will reach far beyond code. Naval combat systems touch displays, processors, racks, networks, cybersecurity, radar interfaces, missile interfaces, fire-control loops, command software, operator consoles, power, cooling, ship installation, test equipment, and training. Containerised software does not remove the need for rugged hardware or careful certification. It changes how new functions are packaged, tested, accredited, and rolled out.

Tactical PaaS carries particular weight for naval systems integrators. Containerisation is routine in commercial software environments, but shipboard combat systems demand mission assurance, deterministic performance, cybersecurity, redundancy, latency control, and integration with safety-critical functions. Bringing containerised approaches into naval combat systems requires a disciplined bridge between modern software practice and military-grade assurance.

Forge also highlights the value of a controlled development environment. Defence software cannot be treated as a loose set of patches produced by disconnected teams. A common environment supports traceability, automated test, configuration control, and repeatability. Those features become essential when the Navy wants a six-month update rhythm rather than occasional major capability insertions.

The effector side adds urgency. The US Navy is expanding Aegis-linked capability, including work around additional air and missile defence options. New missiles, sensors, electronic systems, and applications all need combat-system pathways. A common ICS-enabled baseline can shorten the route from development to fleet deployment, provided certification and integration capacity keeps pace.

The UK’s BOREALIS space-domain awareness programme reflects a similar movement in another domain, where secure software, data fusion, user interfaces, and updateable architectures are becoming central to military capability. Naval combat systems are travelling the same route, although with the added challenge of shipboard safety, weapons control, and fleet sustainment.

For shipbuilders and naval systems suppliers, the balance of work is changing. Traditional shipbuilding remains capital-intensive and slow-cycle, but combat-system competitiveness now depends heavily on software pipelines, integration labs, digital twins, cybersecurity accreditation, and rapid test environments. A yard can deliver the hull; the combat system has to keep adapting after the ship enters service.

Fleetwide commonality also has sustainment value. Different baselines across different ships create training burdens, spare parts differences, documentation issues, and uneven capability. Common infrastructure allows operators, maintainers, and developers to work from a more consistent foundation. That can reduce cost, improve update speed, and support allied interoperability where Aegis or related systems are used by partner navies.

Rapid software delivery still needs discipline. Six-month updates require controlled requirements, strong cyber assurance, crew training alignment, and enough test capacity to avoid pushing immature capability to the fleet. Combat-system software cannot behave like a consumer application. Every update touches operational confidence, tactical doctrine, safety, and weapons employment.

Lockheed Martin’s first ICS-enabled baseline therefore marks a production shift as well as a technical milestone. Naval combat capability is increasingly being manufactured through software factories, validated in integration environments, and deployed through common architectures. The ships remain steel, sensors, launchers, power systems, and people. Their combat edge increasingly depends on whether the software layer can move at the speed of the threat.