[ APPLICATIONS ]

Six missions that need more than one machine

Each is set out as a concept of operations — the problem, the sequence, the force mix, and what degrades it. No case studies, because we have not earned any yet.

Every mission below runs on the same five-step spine.
01
Detection
02
Human in the loop
03
Assignment
04
Coordinated action
05
Scale
[ Mission 04 · AIR ]
Terrain the mission is flown over
Block 01 — the problem

An emitter is somewhere in a corridor. One receiver gives you a bearing and a guess. Moving that receiver to get a second bearing takes time the emitter uses to stop transmitting, and the fix you eventually compute describes where it used to be.

↓ Concept of operations
Block 02 — concept of operations

Simultaneous bearings for a fix that holds

AIRBORNE ASSETGROUND NODETARGET / CONTACTTASKINGSENSOR
OUTER LAYERINNER LAYERPROTECTED AREAE-0110 KG EWE-0210 KG EWA-012 KG EO/IRA-02INTERCEPTORCONTACTINBOUNDG-01ROVER 30GROUND STATIONAUTHORISATION010203040506FIX RESOLVED
01DETECTION
Signal intercepted
E-01 · 10 kg EW

A receiver detects an emission of interest and characterises it.

02ASSIGNMENT
Receivers repositioned
E-02, E-03

Two further receivers move to a baseline computed for the bearing, not to a fixed pattern.

03DETECTION
Simultaneous bearings
E-01..03

Three receivers take bearings on a shared timebase, and the fix resolves while the emitter is live.

04HUMAN IN THE LOOP
Operator reviews
GROUND STATION

The fix, its error ellipse and the signal characterisation are presented together.

05COORDINATED ACTION
Effect applied
E-02 · EW module

Where authorised, denial is applied from the asset with the best geometry rather than the nearest one.

06SCALE
Corridor held
ALL

Receivers return to collection while one asset holds the effect, so collection does not stop to deliver it.

Block 03 — why this needs multiple agents
Mission 04

Geolocation by bearing requires two receivers separated in space at the same instant. That is not a capability you add to a platform, it is a property of having more than one. Three receivers on a shared timebase resolve a fix while the emitter is still transmitting.

The rest of this page is the working detail behind that claim — the sequence, the assets, and the conditions under which it fails.↓ Force mix
Block 04 — force mix

5 assets, one operator

Each row opens the configurator preloaded with that configuration. The fleet builder template renders the same objects.
Block 05 — constraints and mitigations

What degrades this, and what the system does about it

Stated plainly because an evaluator will find these anyway. Mitigations are design decisions, not guarantees.

01
Baseline geometry

Receivers too close together produce an error ellipse too large to act on.

The required baseline is computed from the bearing and shown before the assets move. Where geometry cannot be achieved, the fix is reported as a bearing, not a position.

02
Emitter discipline

A disciplined emitter transmits in bursts too short for a three-receiver solution.

Partial solutions accumulate across bursts rather than being discarded, and the confidence is reported honestly as it converges.

03
Timebase under jamming

Simultaneous bearings need a shared clock, which is usually taken from GNSS.

Each receiver holds a local oscillator disciplined before the mission and drifts within a stated bound, so the fix degrades predictably rather than failing.

04
Own-force interference

Applying denial in a corridor affects friendly links in the same band.

Affected friendly links are named before the effect is offered, and the operator authorises with that list in front of them.

Block 06 — next

Take this mix into the fleet builder

Configure this force mix

Bring a mission, not a shortlist

We will walk the concept of operations against your requirement and say plainly where it does not fit.