System anatomy · 07

Command, control and lost link

Treat communications coverage, latency, priority, cybersecurity and loss behaviour as safety-critical system properties.

Evidence statusCross-domain mission framework · vehicle, operation and jurisdiction validation requiredLast reviewed: 15 August 2026
07

FUURAA thesis

A remote or supervised system is only as controllable as its end-to-end command path under degradation.

Engineering map

Turn the title into engineering objects that can be observed, measured and reviewed.

Each layer states the boundary to establish and the evidence needed for the next decision.

01

Path

Map vehicle, relay, network, remote centre, credentials and external providers.

02

Priority

Protect safety commands from payload traffic, congestion and stale instructions.

03

Loss

Define timeouts, autonomous fallback, notification and reconnection authority.

Verification questions

Write the questions first, then decide whether a demo, test, pilot or operating record can answer them.

Each question needs an object, conditions, denominator, threshold and accountable decision owner.

  1. 01

    Which links carry safety-critical commands?

  2. 02

    What is the maximum tolerable latency?

  3. 03

    Can payload traffic starve control?

  4. 04

    What state is entered after link loss?

Evidence to preserve

Enable the next reader to reconstruct conditions, results, failures and the decision.

A conclusion alone loses reviewability; raw records, configuration and exclusions matter too.

  1. 01

    Evidence package 1

    End-to-end communications architecture

  2. 02

    Evidence package 2

    Coverage, latency and congestion test

  3. 03

    Evidence package 3

    Lost-link and reconnection event log

Scope boundary

State what this evidence still cannot be generalised to.

Sources and evidence status

Read standards scope, measurement evidence and application conclusions separately.

Source dates and review status remain visible; external sources open in a new tab.