[ 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 02 · AIR + LAND ]
Terrain the mission is flown over
Block 01 — the problem

An area of interest is larger than one sensor footprint, and what matters is change rather than a single image. Flying a pattern gives you snapshots hours apart, and by the time two frames are compared the moment has passed.

↓ Concept of operations
Block 02 — concept of operations

Distributed coverage with onboard change detection

AIRBORNE ASSETGROUND NODETARGET / CONTACTTASKINGSENSOR
AIR LAYERTARGETGROUNDA-012 KG EO/IRA-022 KG EO/IRA-042 KG EO/IRA-0320 KG RELAYTARGETTARGETT+9 HRGROUND STATIONONE OPERATOR010203040506CHANGE RAISED
01DETECTION
Baseline pass
A-01..03 · 2 kg EO/IR

Three aircraft fly overlapping lanes and build a baseline of the area.

02ASSIGNMENT
Lanes reallocated
SYSTEM

Lane assignment adjusts to wind and remaining endurance rather than holding a fixed pattern.

03DETECTION
Change detected
A-02 · onboard

Onboard comparison flags a change against the baseline and raises it, rather than streaming full video.

04HUMAN IN THE LOOP
Operator adjudicates
GROUND STATION

The operator confirms or dismisses. Confirmed changes become track files.

05COORDINATED ACTION
Ground asset closes
G-01 · Rover 30

Where the change is reachable, a rover takes a closer look without committing an aircraft.

06SCALE
Revisit rate held
ALL

Remaining aircraft close the gap left by the tasked asset, so revisit degrades gracefully instead of collapsing.

Block 03 — why this needs multiple agents
Mission 02

Area coverage scales with the number of sensors, not with the endurance of one. Aircraft flying overlapping lanes hold a revisit rate no single platform reaches, and change detection runs onboard so the operator is told what moved rather than shown everything.

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.
×3
Survey aircraft
2 kg air · multirotor
Tier 2GNSS-denied · EO/IRES-AIR-2K-T2-GD-D2ADConfigure →
×1
Ground node
30 kg ground
Tier 3EO/IR · mesh + LTEES-GND-30K-T3-GDLand configurator in build
×1
Operator station
Ground · rugged
Mesh · LTEES-GCS-01Land configurator in build
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
Cloud and obscuration

Low cloud, dust and smoke break an EO baseline and generate false change detections.

Detections carry an obscuration flag and the baseline is not overwritten while it is set. The operator sees a gap in coverage rather than a confident wrong answer.

02
Revisit rate versus resolution

Flying lower for resolution narrows the footprint and lengthens the revisit interval.

Altitude is a tasked parameter per lane, so an area can be flown wide and fast or narrow and slow, and the resulting revisit rate is shown before the task is committed.

03
Onboard compute limits

Change detection at full frame rate exceeds what the airframe can process at this class.

Detection runs on a reduced cadence sized to the class, and that cadence is published in the configuration rather than assumed.

04
Ground mobility

A rover cannot reach much of the terrain an aircraft can observe.

Reachability is computed from terrain before the rover is offered, so the operator is not handed a task that will fail.

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.