See a mission unfold.

Inspect infrastructure

Create a documented visual and thermal assessment of a defined, authorised building envelope.

Required capabilities

• Flight planning · Platform
• Optical imaging · Observe
• Thermal imaging · Inspect
• Georeferencing · Analyse
• Anomaly detection · Analyse
• Human review · Report
• Inspection report · Report

Candidate resources — and why each was chosen or not

• Licensed drone operator · dual sensor · Human + platform — Eligible · SelectedCovers Optical imaging + Thermal imaging — One flight answers both imaging requirements from the same viewpoints, so optical and thermal frames align without a second acquisition.
• Fixed thermal camera network · Fixed installation — Unavailable · Not selectedCovers Thermal imaging — Answers the same requirement at no acquisition cost, but the installed cameras face the yard — they cover none of the elevations in scope.
• Photogrammetry analysis API · Software service — Eligible · SelectedCovers Georeferencing + Anomaly detection — Returns per-finding confidence and a coordinate for every anomaly, which is what makes the report reviewable rather than just illustrated.
• Restricted airspace corridor · Policy context — Approval required · PreconditionPerforms no work: it is the authorisation the flight depends on, and the plan cannot leave the checkpoint until it is granted.

Constraints evaluated

• Authorised area only Decided the selectionBounds the flight plan itself — step 01 plans no path outside the authorised zone.
• Operator licence verified HoldsChecked against the register before the operator became eligible at all.
• Daylight window HoldsThe proposed flight sits inside it.
• Cost ceiling HoldsThe selected set fits under it.
• Weather: wind < 20 km/h Checked at executionChecked on the day, not now — a gust past the limit aborts the flight, and the mission re-flies inside the window.

Proposed plan

1. 01 Plan flight path over authorised zone
2. 02 Capture optical + thermal passes
3. 03 Georeference and align imagery
4. 04 Detect thermal anomalies
5. 05 Route findings to human reviewer

Human checkpoint — approval required before execution

Evidence captured

Auditable inspection report with imagery, anomaly candidates, provenance, and reviewer sign-off.

Diagnose an industrial anomaly

Determine why a production stage is operating outside its normal range and recommend safe checks.

Required capabilities

• Telemetry access · Retrieve
• Asset context · Retrieve
• Anomaly detection · Analyse
• Maintenance knowledge · Retrieve
• Workflow orchestration · Platform
• Human approval · Platform
• Report generation · Report

Candidate resources — and why each was chosen or not

• Plant telemetry historian · Data service — Eligible · SelectedCovers Telemetry access — Holds the affected stage at the sample rate the deviation shows up in, and is read-only by construction — no path to the control network.
• Legacy PLC interface · no verified adapter · Control system — Unavailable · Not selectedCovers Telemetry access — Would answer the same requirement at the controller itself, including signals the historian was never configured to poll — but no adapter has been verified for this controller family, so nothing may read from it.
• Asset & maintenance knowledge base · Software service — Eligible · SelectedCovers Asset context + Maintenance knowledge — Carries the asset hierarchy and the repair history together, so ranked causes can cite what has already failed on this stage.
• Anomaly-detection model · Software service — Eligible · SelectedCovers Anomaly detection — Fitted to this line’s own operating envelope; a generic detector would flag every shift change and every product changeover.
• On-site maintenance engineer · Human operator — Approval required · SelectedThe fallback for everything the blocked controller path would have answered — a person who may open the panel under the plant’s own permit rules, on the plant’s approval rather than this system’s.

Constraints evaluated

• Read-only telemetry access Decided the selectionWhy the historian was selected — read-only by construction — and half of what keeps the controller path closed.
• Production safety envelope Decided the selectionLimits the proposed checks to ones that keep the stage inside it.
• No direct control commands HoldsNothing in the plan issues one; the engineer acts under the plant’s own permit.
• Escalation policy defined HoldsThe route past the human checkpoint is named before the mission starts.
• Next maintenance window Checked at executionAny physical check waits for it — a scheduling fact, not a property of the plan.

Proposed plan

1. 01 Pull telemetry for the affected stage
2. 02 Correlate with asset context and maintenance history
3. 03 Detect deviations from the normal operating envelope
4. 04 Rank probable causes with confidence
5. 05 No verified adapter for the legacy PLC — route the controller-side reading to the on-site engineer instead of the control network
6. 06 Propose safe checks for engineer approval

Human checkpoint — approval required before execution

Evidence captured

Diagnostic report with ranked causes, confidence, and recommended safe checks — released only after human approval.

Assess an environmental area

Assess whether vegetation stress has increased in a defined area over the past season.

Required capabilities

• Historic imagery access · Retrieve
• New aerial or satellite imagery · Observe
• Weather context · Retrieve
• Geospatial alignment · Analyse
• Change detection · Analyse
• Report generation · Report

Candidate resources — and why each was chosen or not

• Satellite imagery archive · Dataset — Eligible · SelectedCovers Historic imagery access — Already holds last season’s scenes for this area, so the baseline is a retrieval rather than an acquisition.
• Multispectral drone survey · Platform + operator — Approval required · SelectedCovers New aerial or satellite imagery — Costs an approval and a flight, but resolves vegetation stress below the archive’s pixel size and can fly inside the season boundary the comparison depends on.
• Satellite tasking order · Commercial service — Eligible · Not selectedCovers New aerial or satellite imagery — Answers the same requirement with no flight approval at all — and is still not chosen: the earliest pass falls after the season boundary, which would make the two scenes incomparable.
• Regional weather archive · Data service — Eligible · SelectedCovers Weather context — Station records for both seasons, which is what separates genuine stress from an ordinary dry spell.
• Change-detection model · Software service — Eligible · SelectedCovers Geospatial alignment + Change detection — Aligns the scenes and computes the vegetation index in one pass, so the comparison is reproducible from a single pipeline.

Constraints evaluated

• Season-over-season comparability Decided the selectionRejected the satellite tasking order — its earliest pass falls after the season boundary.
• Resolution threshold Decided the selectionPut the fresh scene on the drone: the archive’s pixel size cannot resolve stress at plant scale.
• Defined area of interest HoldsScopes the retrieval and the flight alike.
• Budget limit HoldsThe selected set fits under it — the tasking order was not rejected on price.

Proposed plan

1. 01 Pull historic imagery for the area
2. 02 Fly fresh multispectral imagery inside the season window
3. 03 Align scenes geospatially
4. 04 Run vegetation-index change detection
5. 05 Contextualise with weather data

Human checkpoint — approval required before execution

Evidence captured

Change-detection report with confidence bands, weather context, and full data provenance.