Deployment evaluation · 17

Mission data quality

Validate coverage, calibration, uncertainty, provenance, custody and fitness for the intended decision.

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

FUURAA thesis

The mission product must meet a declared quality threshold independently of vehicle autonomy.

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

Completeness

Quantify planned, observed, missing, rejected and repeated coverage.

02

Accuracy

Trace calibration, reference, processing and uncertainty to each result.

03

Use

Confirm review, custody, version and the decision threshold the product supports.

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

    What quality specification applies?

  2. 02

    How much data are missing or rejected?

  3. 03

    Which processing step changes interpretation?

  4. 04

    Was usefulness confirmed by the recipient?

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

    Quality specification and acceptance criteria

  2. 02

    Evidence package 2

    Raw-to-product provenance record

  3. 03

    Evidence package 3

    Independent review and acceptance decision

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.