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 RAF’s £16.9 million Gladiator support extension is now part of a longer procurement story. Announced in December 2025, it sustains the existing synthetic training environment while additional systems are integrated. During 2026, the Ministry of Defence also progressed a separate competition combining future Gladiator services with the Royal Navy’s SPARTAN requirements.
For training software and integration businesses, the important development is the connection between those two purchases. The extension keeps an established capability supported. The later competition defines a customer-facing service for the next period. They have different values, schedules and commercial implications.
The RAF’s 19 December 2025 announcement names Boeing Defence UK as the supplier. It describes continued support until 2028, alongside integration work involving air command and control, combat air and joint fires.
The core system is MOD-owned. Military personnel, civil servants and industry work together at RAF Waddington’s Air Battlespace Training Centre to operate, maintain and incrementally develop it. That ownership structure is important: the government is sustaining a capability it owns, with industry carrying defined responsibilities around it.
The January 2026 edition of Desider specifies a support period of two years and three months, with a further three-month option. It also identifies the DE&S Synthetic Environments and Training team as the contracting organisation. The published option is a potential continuation, not evidence of an exercised extension.
For a supplier, continuity and improvement are connected obligations. The customer needs the training environment to remain usable while its supported systems evolve. A proposed change therefore has to account for the service already being delivered.
An April 2025 procurement notice described Boeing as the system designer and explained the buyer’s reliance on its knowledge of the software, interfaces and relationships with subcontractors and equipment manufacturers. The buyer linked the extension to maintaining the capability while preparing for a future competition.
That notice used an estimated £25 million value and a six-month option. The later RAF and DE&S announcements report £16.9 million and a shorter option. These are different dated descriptions in the procurement history; the public records cited here do not explain a complete reconciliation between them.
The practical lesson is that incumbent advantage can reside in accumulated integration knowledge. A new entrant may understand a technology category without yet understanding the customer’s supported configuration and delivery responsibilities. Competing for a continuing service requires a credible plan to acquire and retain that knowledge.
A specialist supplier can also use that insight when considering a partner role. It should identify a contribution that the prime can integrate and support, with clear responsibility for changes. A product demonstration alone does not establish that the wider service can depend on it.
The 5 March 2026 preliminary market engagement notice introduced the combined Gladiator and SPARTAN requirement. It covered support and enhancement, platform integration, interoperability and the Royal Navy’s needs.
At that stage, the buyer estimated £50 million excluding VAT and a contract running from April 2028 to March 2032, with a possible extension to 2034. An industry day was scheduled for 30 March. These were planning terms for a future purchase, separate from the existing Boeing extension.
SPARTAN’s inclusion is commercially significant because it brings another service organisation into the requirement. Suppliers need to understand which capabilities can be shared and which need to reflect different user workflows. Reuse may reduce duplicated development, but it does not eliminate the work of adapting and supporting the service for another customer group.
For an integration business, the opportunity is consequently broader than connecting one simulator. The customer wants a managed environment whose participating systems and content can change over time.
The later MOD tender, reproduced on Sell2Wales in July 2026, moves beyond consultation. Although its title retains “PPN”, its notice type is UK4 and its text describes a competitive flexible procurement for an expected fully managed service.
The estimated value remains £50 million excluding VAT. The initial period is now five years, from April 2028 to March 2033, with possible extensions totalling two years. The notice also allows for additional services. Its detailed expression-of-interest deadline was 4 August 2026, which has passed as of this article’s September review.
Those developments should not be collapsed into the earlier planning record. The longer initial period changes the service horizon. The move to a tender changes what suppliers are being asked to do. Neither establishes that a winner has been selected.
The notice’s service structure also directs attention towards the organisation that can sustain the whole requirement. A company supplying one tool may be better positioned through a delivery team than as the prime responsible for every element.
The future buyer is asking for continuity, integration and enhancement within one service. That combination makes staff knowledge, supported versions and change control part of the commercial proposition.
Consider a hypothetical company specialising in simulation data preparation. Its contribution could be valuable if it reduces a recurring burden for the service provider and fits the customer’s accepted workflow. To make that case, it would need to explain how outputs are reviewed, how updates are supported and where responsibility passes to the rest of the team.
A company pursuing the full service would need a broader proposition. It would have to demonstrate how it can maintain the existing environment, introduce approved changes and keep the customer informed when dependencies shift. These are organisational capabilities, not simply features on a software roadmap.
The notice itself recognises that changes in standards and in the wider environment may require the service to adapt. This makes a long contract period a delivery commitment as well as a revenue horizon. A price based only on maintaining today’s configuration would be difficult to compare with the intended evolving service.
There is a further distinction between supplying content and accepting responsibility for the environment in which it is used. A library of digital assets may be updated frequently, while the service provider still has to maintain a consistent training experience. The commercial arrangement needs to make that relationship workable. For a specialist content or software company, a strong reference would show how its updates were introduced without disrupting the supported service. For the prime, the same reference would help demonstrate that partner contributions can be managed over the contract period.
Gladiator’s public record contains support, future integration ambitions, market engagement and a tender. Each stage answers a different question. The next material developments will include the selected delivery arrangement and evidence of work accepted by the customer.
The MTU cyber-range award offers a smaller civilian comparison in which software and infrastructure support are bought together. CWIX 2026 shows why a supplier’s integration reference needs a defined scope and configuration.
For defense software businesses, the combined Gladiator–SPARTAN procurement makes the commercial category clear. Governments buy the continuing ability to run and develop a shared training environment. The strongest supplier proposition explains how that service remains useful as its participants and requirements change, and who takes responsibility for making that happen.
Primary material read on 6 September 2026. Government programme statements and attributed supplier disclosures are kept separate from future milestones and undisclosed contractual terms.
Suggest a correction