Atlantic Bastion provides a compelling illustration of what the next generation of Defence programmes will demand.
The Strategic Defence Review describes a layered sensor network operating above, on and below the water, bringing together Type 26 frigates, uncrewed surface and underwater vessels, acoustic detection systems and a digital targeting web. The programme brings together the Royal Navy, RAF, Strategic Command, the UK Hydrographic Office, NATO and commercial partners.
This is not simply a new platform programme. It is a multi-domain, system-of-systems challenge in which established assets, new technologies, data, people and suppliers must work together as an operational whole.
That makes Atlantic Bastion an important example of a broader truth: in hybrid defence programmes, innovation is only part of the challenge. The programme must also define what is needed, understand how the elements depend on one another, engage the right organisations and maintain assurance as the capability evolves.
The question is not just whether promising technology exists. It is whether Defence can integrate it at the pace of the threat.
Complexity Accumulates Between the Ambition and the Work Package
Atlantic Bastion encompasses crewed and uncrewed platforms, sensors, communications, digital infrastructure, machine-supported analysis and operational decision-making. These capabilities are at different stages of maturity and will not all follow the same development or commercial path.
Some are established systems. Some involve the adaptation of commercially available technologies. Others are progressing through experimentation, demonstration and spiral development. Each brings its own requirements, dependencies, security considerations, evidence and maturity challenges.
This creates a difficult translation task.
Strategic intent has to become an integrated set of requirements. Those requirements then have to be decomposed to the appropriate level of the engineering lifecycle and translated into work packages: structured definitions of the scope, outputs, interfaces, responsibilities, evidence and acceptance criteria for a particular area of delivery. These work packages must give suppliers sufficient clarity to respond effectively without unnecessarily constraining how they meet the requirement. Interfaces, dependencies, review points and acceptance criteria must remain visible as the programme changes.
In my experience, this is where valuable time is frequently lost. It is not necessarily caused by a lack of expertise. It happens because skilled people spend too much of their time finding information, reconciling documents, rebuilding previous work and working out which version represents the current position.
Every clarification cycle consumes time. Every missing dependency creates the potential for rework. Every requirement that matures after supplier engagement has begun makes planning and comparison more difficult.
On a system-of-systems programme, those effects multiply.
Institutional Knowledge Only Creates an Advantage When It Can Be Mobilised
Large defence primes possess considerable institutional knowledge. They have data from previous programmes, established supplier networks and people with deep knowledge of particular technologies and domains.
That should create a significant advantage. But possessing information is not the same as being able to mobilise the right information for the programme immediately in front of you.
Relevant material may be distributed across previous projects, document repositories, business units and individual professional networks. Supplier information may be extensive but not organised around the exact combination of capability, maturity, security and delivery requirements involved in a new programme.
The Ministry of Defence’s own Data Strategy for Defence recognises the underlying problem across the wider Defence environment: data can become trapped in organisational, technical and contractual silos, creating duplication, multiple versions of the truth and difficulty finding authoritative information.
The practical requirement is therefore not another large repository. It is a controlled way to bring the relevant knowledge, evidence and people together around a specific delivery need.
This is particularly important for programmes such as Atlantic Bastion, where established primes, specialist SMEs and technology businesses may all contribute different parts of the solution. Atlantic Bastion activity reported by the Ministry of Defence has already involved proposals from 26 firms and demonstrations from 20 companies ranging from major primes to technology SMEs.
The programme needs access to the breadth of that ecosystem without losing coherence.
What a More Structured Approach Could Look Like
Consider what the structured definition and development of one capability within a programme like Atlantic Bastion might involve.
The starting point would be the operational context and intended effect: what must the capability enable, under what conditions, and as part of which wider mission thread?
From there, the programme could structure requirements across the relevant levels of the V curve and identify the lifecycle phases, review milestones and evidence needed for progression.
Individual work packages could then define:
- The capability or service required
- Its relationship with other platforms, sensors and networks
- Interfaces and dependencies
- Security and information-assurance considerations
- Required maturity and delivery timescales
- Verification and acceptance criteria
- Skills, effort and governance requirements
Those work packages should not exist as isolated documents. Each should remain connected to its originating requirement and to the evidence, deliverables and decisions that follow.
When a requirement changes – as it inevitably will during experimentation and spiral development – the affected work packages and dependencies should be visible. When suppliers respond, their proposals should be considered against a consistent structure. When a review takes place, decision-makers should be able to see what has been agreed, what remains uncertain and what evidence supports progression.
That is how programmes create pace without replacing scrutiny with haste.
Releasing People to Apply Judgement
This also explains the potential workforce benefit of better requirements and work package tooling. The wrong conclusion is that automation removes the need for experienced engineers, commercial specialists or assurance professionals. Complex programmes require their judgement precisely because the context, risks and trade-offs cannot simply be automated.
The opportunity is to stop using those people as document production machinery.
A platform such as Positiv Cohort’s proprietary delivery tool Mission Assured, can structure source information, reuse relevant material from previous projects, support the development of first drafts and maintain relationships between requirements, deliverables and evidence. Accountable people remain responsible for reviewing, challenging and approving the result.
This can reduce time spent on activities such as:
- Locating and reassembling previous material
- Reformatting similar information across multiple documents
- Checking whether documents remain consistent
- Manually maintaining traceability
- Repeating clarification caused by incomplete work packages
- Preparing information for governance and supplier engagement
The immediate outcome on a typical programme can be in the region of 2 to 4 man weeks of specialist capacity released to work on alternate tasks. The same team can either used the time saved to focus on other programmes or spend more time on engineering judgement, integration, assurance and stakeholder alignment within the defined programme to optimise outcomes.
In some circumstances, that may also reduce the need to expand programme support or document production teams as activity grows. The purpose is not fewer people at any cost. It is ensuring that scarce, experienced people are working where they create the most value.
From Organisational Memory to Programme Advantage
Mission Assured has been developed to support this controlled path from intent to delivery.
It brings together project context, requirements, lifecycle structure, work-package development, document drafting, review and supplier engagement. Machine learning can accelerate repeatable activities, while humans remain in control of context, judgement and approval.
For a programme with the characteristics of Atlantic Bastion, the potential value lies in helping teams:
- Develop more complete requirements before approaching the supplier base
- Create consistent work packages across diverse capability areas
- Identify dependencies between systems and suppliers earlier
- Preserve traceability from requirement to deliverable and acceptance
- Bring relevant knowledge from previous projects into the current programme
- Organise stakeholder and supplier information around the requirement at hand
- Compare responses on a more consistent basis
- Maintain governance while requirements evolve through spiral development
Mission Assured cannot create relationships or institutional knowledge that do not exist. Nor does it replace established programme management, engineering or security systems.
It can, however, make authorised knowledge easier to apply to a defined programme need – turning accumulated data, experience and contacts into structured delivery information sooner.
That distinction matters. The competitive advantage of a prime or wider delivery ecosystem should not depend solely on how much knowledge it possesses. It should depend on how quickly it can bring the right knowledge and expertise to bear on the mission.
Mission Pace Requires Assured Foundations
Atlantic Bastion depends on integration: crewed and uncrewed systems, multiple domains, different suppliers and continually developing technologies must contribute to a shared operational effect.
The programme therefore needs more than rapid innovation. It needs requirements that mature early enough to guide delivery, information that remains traceable as the solution changes, and supplier engagement built around a common understanding of what must be achieved.
That is not administrative overhead. It is part of the operational capability.
If Defence wants to exploit new technology at the pace of relevance, it must also accelerate the work that turns strategic intent into controlled, deliverable and assured activity.
More speed, less haste.
If the challenges explored here reflect those facing your programme, I would be pleased to compare perspectives. Contact me to discuss requirements, integration and supplier engagement in complex Defence programmes, or to arrange a demonstration of Mission Assured.
