By Paul R Salmon FCILT, FSCM
Introduction: A Concept Everyone Agrees With
“Orchestration” has rapidly become one of the most used—and least challenged—terms in modern supply chain thinking.
It is presented as the evolution of the profession:
- moving beyond efficiency
- moving beyond visibility
- moving towards real-time, end-to-end decision-making
In theory, orchestration represents the pinnacle of supply chain maturity:
a fully integrated system where data, decisions, and actions are aligned across the entire network—delivering operational advantage at pace.
In commercial environments, this shift is already underway.
In UK Defence, however, the reality is more complex.
The uncomfortable truth is this:
Orchestration is not failing because the idea is wrong.
It will struggle because the system it depends on is not yet ready.
What Do We Mean by Orchestration?
Before challenging the concept, it is important to define it clearly.
Supply chain orchestration is not simply coordination.
It is not a dashboard.
It is not a control tower.
It is the ability to:
- sense demand and disruption in near real-time
- understand the impact across the end-to-end system
- make decisions across multiple functions simultaneously
- execute those decisions rapidly and coherently
It requires:
- integrated data
- aligned decision rights
- system-level visibility
- and, critically, authority to act
This last point is often overlooked.
Because orchestration is not just about seeing the system.
It is about controlling it.
The Structural Reality of UK Defence
The UK Defence supply chain is not a single system.
It is a system of systems, comprising:
- Front Line Commands (Army, Navy, RAF)
- Defence Equipment & Support (DE&S)
- Strategic Command
- enabling organisations
- industry partners across multiple tiers
Each of these has:
- different objectives
- different funding lines
- different governance structures
- different levels of authority
No single organisation owns the supply chain end-to-end.
And this is where the first major challenge emerges.
1. You Cannot Orchestrate What You Do Not Control
In commercial organisations, orchestration works because control is clearer.
Even in complex global businesses:
- supply chain authority is typically centralised
- decision rights are defined
- trade-offs (cost vs service vs risk) can be made within one structure
In Defence:
- demand is generated by Front Line Commands
- supply is managed by DE&S
- delivery is often executed by industry
- strategic direction sits elsewhere
This creates a fundamental disconnect.
Decisions that should be made at system level are instead:
- fragmented
- negotiated
- or delayed
The result is not orchestration.
It is coordination through compromise.
And coordination is not enough in a high-tempo, contested environment.
2. Orchestration Is a Data Problem Before It Is an Operating Model
At its core, orchestration relies on one thing above all else:
trusted, consistent, accessible data.
Without it:
- signals are unclear
- decisions are delayed
- actions are misaligned
In UK Defence, data challenges are well understood:
- multiple systems across platforms and domains
- inconsistent definitions of key metrics
- fragmented ownership of data
- variable data quality
Even fundamental concepts such as:
- lead time
- availability
- demand
can have different meanings depending on where you sit in the system.
This is not a minor issue.
It means that when Defence attempts orchestration, it is often:
- aligning spreadsheets
- reconciling reports
- debating definitions
Rather than making decisions.
The risk is clear:
👉 Orchestration becomes data reconciliation at scale.
3. Governance Slows What Orchestration Depends On
Orchestration assumes speed.
It assumes that once insight is generated:
- decisions can be made quickly
- actions can be taken immediately
But Defence operates within a governance framework designed for:
- assurance
- accountability
- control of public funds
This results in:
- layered approvals
- complex commercial considerations
- risk-averse decision-making
These are not flaws—they are necessary.
But they are not aligned to the pace required for orchestration.
Even when:
- the data is available
- the analysis is complete
- the recommendation is clear
the ability to act can be constrained.
The result is a critical gap:
👉 Insight exists, but execution lags.
And orchestration without execution is simply analysis.
4. Commercial Boundaries Limit True Integration
A fully orchestrated supply chain requires visibility and influence across:
- Tier 1 suppliers
- Tier 2 and Tier 3 networks
- logistics providers
- maintenance and support functions
In Defence:
- much of this sits with industry
- data is often commercially sensitive
- contracts are not always designed for transparency
This creates structural blind spots.
Defence may understand its immediate suppliers, but beyond that:
- visibility reduces
- influence weakens
- risk increases
Without access to:
- upstream constraints
- supplier dependencies
- capacity limitations
true orchestration becomes impossible.
Because orchestration is not just about internal alignment.
It is about network-level control.
5. Culture: The Hidden Barrier
Perhaps the most significant challenge is not structural or technical.
It is cultural.
Orchestration requires:
- trust in data
- trust in models
- trust in automated decision-making
Yet across Defence, there remains:
- a preference for manual intervention
- limited adoption of forecasting tools
- a tendency to override system outputs
This is not irrational.
It reflects:
- the complexity of Defence environments
- the consequences of failure
- the experience of practitioners
But it creates a paradox.
Defence invests in:
- modelling
- analytics
- decision-support tools
Yet often stops short of:
- fully implementing their outputs
The result is:
👉 Systems that inform decisions, rather than make them.
And orchestration cannot exist in a system where:
- every decision is manually validated
- every output is questioned
- every action is delayed
6. The Absence of a Mandated Operating Model
In leading organisations, orchestration is not optional.
It is:
- defined
- mandated
- embedded
Control towers have:
- authority
- accountability
- decision rights
In Defence:
- multiple approaches coexist
- modelling is often advisory
- forecasting is not universally adopted
There is no single, enforced way of working.
This leads to:
- inconsistency
- duplication
- inefficiency
And most importantly:
👉 a lack of system coherence.
Without a mandated operating model, orchestration becomes:
- an aspiration
- a pilot
- a concept
But not a reality.
7. System Integration Is Still Evolving
Orchestration depends on integration:
- of systems
- of data
- of processes
- of decision-making
UK Defence is actively progressing System Integration (SI):
- aligning structures
- defining roles
- integrating capabilities
But this journey is ongoing.
Key questions remain:
- who owns integration across portfolios?
- who assures system-level decisions?
- how are cross-cutting risks managed?
Until these are resolved, the system remains:
- partially connected
- partially aligned
- partially integrated
And orchestration requires completeness.
Not partial alignment.
The Risk: Orchestration Theatre
If Defence adopts the language of orchestration without addressing the fundamentals, a new risk emerges:
Orchestration theatre.
This is where:
- dashboards are implemented
- control towers are established
- data platforms are built
But:
- decisions are not accelerated
- outcomes do not improve
- the system does not change
It looks like progress.
But it is not transformation.
Examples include:
- control towers without authority
- dashboards without action
- models without implementation
- data lakes without trust
This is not failure.
It is misalignment between ambition and reality.
What Must Change First
If orchestration is to succeed in UK Defence, the focus must shift.
Not on the concept—but on the enablers.
1. Define End-to-End Ownership
Someone must own:
- supply chain performance
- trade-offs across cost, service, and risk
- system-level outcomes
Without ownership, there is no orchestration.
2. Standardise Data at Source
Through Critical Data Elements (CDEs):
- one definition of demand
- one definition of availability
- one definition of lead time
Data must be:
- consistent
- governed
- trusted
Without this, orchestration will always fail.
3. Move from Advisory to Authority
Modelling and forecasting must:
- inform decisions
- and be empowered to drive them
This requires:
- mandate
- trust
- accountability
4. Redesign Commercial Models
Contracts must enable:
- data sharing
- transparency across tiers
- integration of systems
Without industry alignment, orchestration stops at Tier 1.
5. Build a Culture of Trust in Data
This is the hardest shift.
It requires:
- confidence in models
- reduced manual intervention
- acceptance of automated decision-making
Not blind trust.
But informed trust.
6. Stabilise System Integration
Before orchestrating, Defence must:
- complete integration
- define roles
- align responsibilities
Only then can orchestration operate effectively.
Conclusion: Fix the System, Then Orchestrate It
Orchestration is not a flawed concept.
It represents exactly what modern supply chains need:
- speed
- alignment
- adaptability
But it is not a starting point.
It is an outcome.
In UK Defence, the foundations are still being built:
- data
- governance
- integration
- ownership
Until these are in place, orchestration will struggle.
Not because it is wrong.
But because it is ahead of the system it depends on.
The priority, therefore, is clear:
Do not chase orchestration.
Build the conditions that make it possible.
Only then will it move from:
- buzzword
to - operational capability
And ultimately:
👉 from concept to operational advantage.
Leave a Reply