Defense software / Archive
ACT, CMRE and MARCOM have distinct roles in the planned 2027 Arctic demonstration. The Baltic predecessor shows why suppliers also need to follow national adoption decisions.
CAE's 2026 filing reports a reduction in issue intake per project from an AI-assisted engineering workflow. That metric requires careful interpretation.
The 2026 filing provides a deployment count for a visual system using a gaming engine. Qualification scope remains specific to the reported applications.
Patria's June and July disclosures describe software integration and significant licence orders, while leaving individual customers and values undisclosed.
EDA reports €136 million of orders in the first two years of its current satellite-communications framework. Its factsheet identifies Telespazio France as the framework supplier and explains how member requests become service contracts.
The March handover sits inside a programme buying boats, shore systems, training and support. OCCAR’s earlier contracts show why the commercial opportunity extends beyond a single delivery.
The buyer’s award record separates ten-year management charges from vehicle hire and leasing. A later European procurement shows Babcock’s distinct role as purchasing agent for the MOD.
The MQ-20 and Talon IQ flight records show different integration settings. Airbus’s agreement-to-flight chronology adds context for buyers comparing software, tools and partner support.
The €575,000 MTU award combines a cyber-range platform with support for the university’s existing OpenStack environment. Its June2025-to-February2026 procurement history provides a useful comparison for suppliers selling into education and industry training.
DSIT’s signed four-year contract gives NPL a funded measurement programme. Its research remit and published lifecycle work show where evaluation tools can help AI customers make better adoption decisions.
The January 2026 announcement reports a US$64.15 million task order and a smaller initial obligation for enterprise technology support.
The January announcement combines equity financing with industrial cooperation; the funding total is not a customer contract value.
Australia announced fourteen emerging-technology contracts in January. Software suppliers should connect their capability to a measurable decision-support task.
The support extension bridges an existing training system towards a separate Gladiator–SPARTAN service competition. The 2026 notices show how the future scope and contract period developed.
The government's December 2025 announcement identifies CAE Australia and a delivery start planned for 2026, but does not confirm subsequent acceptance.
The Navy’s industrial software investment connects production data across shipbuilders and suppliers. Earlier BlueForge work and GAO’s wider findings explain both the market opportunity and the limits of pilot productivity claims.
The 2025 agreement purchases learning content for the NCDS Academy; an earlier award to the same supplier reveals a longer customer relationship.
The Siemens agreement sits beside Rolls-Royce’s long-term customer contract and other named engineering partnerships. Together, the records show why industrial software entry depends on a precise role within an established delivery organisation.
One PESCO EW project completed its feasibility study, ACCESS coordinates a development concept, and JEEWCI focuses on common training and doctrine. Their different outputs point to different commercial relationships.
The $60 million award identifies discovery software as a distinct buying category; public product and disaster-pilot records explain the role between data holdings and applications.
The companies’ 2025 flight-test announcement provides a public example of software moving onto an established platform, with further evaluation still required.
The Alliance’s data strategy identifies catalogues, originator control and accountable product teams as parts of its 2030 direction. For software suppliers, the opportunity depends on fitting those responsibilities into existing customer systems.
The NCSC’s roadmap now has a consultancy pilot and a July2026 industry workshop report behind it. Together they show a near-term market for discovery and planning, alongside the longer product migration towards2035.
BSI Flex 335 defines an interface, while Dstl supplies development tools with their own version and support limits. For sensor businesses, the commercial question is who owns integration and acceptance.