The Navy is now pushing over-the-air software updates to some of its most important and complex systems aboard ships. What a phone does overnight next to your bed, a warship can increasingly do while underway at sea.
It was only a few years ago that we started adding this capability for business systems afloat —the backbone of email, collaboration, and other network utilities aboard Navy ships. Now, it’s being applied to combat systems, like radar, sonar, and weapons. This signals a sea change in speed of delivery. An update that once waited for a maintenance availability, a formal test event, and a calendar measured in years can reach the Fleet far faster. The ship may set sail with one software baseline and fight with a better one.
That is not simply an information technology improvement. It changes how naval power is generated. It is a force designed to absorb new capabilities, reconfigure mission threads, and adapt faster than threats change in front of them.
The Chief of Naval Operations’ Fighting Instructions describe our Hedge Strategy, built to increase the Navy’s impact, adapt to dynamic adversaries, field asymmetric capabilities, and empower a distributed force. In service to this strategy, rapid software updates can strengthen the main battle force with tailored offsets against specific threats, without waiting for every platform to be redesigned, replaced, or overhauled in home port.
Recent combat from Ukraine to the Red Sea shows why this matters. Sensors are detected and countered. Communications pathways are jammed. Algorithms and tactics are revised. An advantage can disappear in weeks, days or hours. Hardware still matters, but software compresses the time between observation, adaptation, and renewed effectiveness. The United States does not need to match every adversary platform one for one. It needs to make its force harder to predict, easier to reconfigure, and faster to improve. Rate of change can become an asymmetric hedge.
That requires an adaptive mission architecture. The Navy’s approach, the Adaptable Mission Architecture or AMA, is both a technical design philosophy and an operational mindset. It builds systems, teams, and decision processes that can evolve continuously as missions, threats, and technology change. Its standard is not whether a system meets today’s threshold requirement, but whether the force can continue to learn, integrate, and improve after fielding.
AMA connects four areas that are too often treated as separate initiatives: a common modular open systems approach to computing; common cloud and transport architecture, right down to enterprise services; a software-defined naval force; and the human talent required to integrate them. Published interfaces, automated testing, secure delivery pathways, and constant Fleet feedback make components replaceable without rebuilding the entire mission thread. Every component is a tenant not a permanent owner.
While AMA describes how mission systems should fit and evolve, Modern Service Delivery (MSD) describes how new capabilities can move through the institution in a streamlined and repeatable process, rather than laboriously reinventing the wheel for each innovation. MSD applies systems engineering to the delivery system itself and scales what’s already been working. Reusable services, secure defaults, automated evidence, and clear paths for exceptions reduce repeated debates over first principles. This has allowed for starting on second base, with fewer conversations about basics and more conversations about the specific mission. To jumpstart those in-depth conversations, Navy leaders have conducted Demand Signal Forums with industry partners around the nation. .
Clearer technical guidance, the AMA and MSD processes, and better communications with industry are means, however, not ends. . The outcome is capability that reaches the Fleet safely and repeatedly before the problem changes.
Execution must match the architecture. Under Secretary Hegseth’s new Warfighting Acquisition System, the Department of the Navy established a Portfolio Acquisition Executive for Mission Systems to serve as a central integrator. The shift moves the Navy beyond stovepiped program execution toward integrated mission capability delivered at operational speed. Legacy acquisition divided accountability by component: Each individual program could succeed while the end-to-end mission thread still failed at the seams. Portfolio accountability, by contrast, makes the seams someone’s job. It connects resources, integration, testing, and fielding to an operational effect, rather than a collection of programs. The Portfolio Acquisition Executive for Mission Systems and Department of Navy Chief Information Office accept this charge.
The Fighting Instructions also combine hedge investment with a Fleet adoption plan, because the Navy gains no advantage when technology is merely invented, contracted, or demonstrated. Advantage appears when Sailors and Marines can employ it reliably under operational conditions. Adoption has become a primary measure of innovation. The question is no longer only, “What did we build?” It is, “How quickly did it become a trusted part of the fight?” First movers get the credit. Fast adopters get the outcomes.
This only works when our organizations can adapt as quickly as the technology they are fielding. The hardest part of modernization is rarely the engineering alone. It is changing how decisions are made, how teams work together, and how quickly the institution learns. These are human factors, not technological ones, and they require Battle Ready Sailors as much as better software. The Navy increasingly needs, has, and recruits operators who can explain the mission problem, technologists who understand the operational environment, and acquisition professionals who can translate both into fielded capability. Software fluency is now being treated as warfighting proficiency, not as a contractor service that can be outsourced or delegated.
The speed of adaptation is now a defining measure of readiness. Programs are reporting how long it takes to deliver and certify an update, how quickly a component can be replaced, and how often Fleet feedback changes the product. What we increasingly need are modular Lego blocks of capability and partners who help us phase out stovepiped systems and integration hogs — what the Navy calls Operation Cattle Drive.
Industry and allies are our acceleration partners in this era of faster execution. For industry, the request is simple: stop pitching monoliths. A brilliant but closed system is still a stovepipe, doomed to become a legacy system with a long integration tail. Bring us severable divestments and modular improvements. Publish the interfaces. Price for portability. That is how the Navy creates additional room to maneuver. Friction in integration and interoperability are disqualifiers. The future force must be built from Lego blocks, not stovepipes.
Seapower has always depended on range, payload, endurance, logistics, and skilled Sailors. It now also depends on update speed and adaptation speed. Technology compresses timelines if you can adopt it well. Smart architecture accelerates integration. Culture determines whether either delivers lasting operational advantage. The ship can sail with one software baseline and fight with a better one. That is more than a software update. It is a new way to generate combat power.
James Day is the Department of the Navy’s Portfolio Acquisition Executive for Mission Systems and has served the Navy as both a uniformed officer and a civilian leader. Justin Fanelli is the Chief Technology Officer of the Department of the Navy and teaches software-defined warfare at Georgetown University.
