EmberScope

RFS-011 answer pack - 2026-06-18

Record the stakeholder answers needed to close the requirements.

The closeout checklist names the open decisions. This page turns them into answer rows for target area, altitude, payload branch, airframe class, and sign-off authority.

Fill answer record Requirements closeout Coverage sizing grid COTS payload screen

Closeout state

5 answers remain before RFS-011 can close.

The locked baseline has 4 decisions. The open side has 5 decisions, now mapped to recordable answer fields.

Use this page for the meeting

Choose one option or write a bounded replacement for each question, then record the accepting stakeholder.

Keep RFS-011 open until signed

Do not mark RFS-011 complete until the selected answers and the accepting stakeholder are recorded in project notes.

Answer record

Fill these fields from the stakeholder reply.

Field Recorded value
Answered by
Answer date
Hourly target area
Altitude basis
Payload branch
Airframe class
Sign-off authority
Evidence source

Stakeholder questions

Each answer changes the next optics or procurement move.

Question

Hourly target area

What land block must one fleet revisit every hour in the first trial?

This is the missing input that turns per-drone coverage into fleet count and maximum affordable payload cost.

Option Answer to record Evidence Design consequence Follow-up
250 ha first trial
Evidence page		Hourly revisit target = 250 ha.2 payloads at 120 m with a USD 33k unit-cost ceiling, or 1 payload with a waiver and a USD 66k ceiling.This is the least costly meaningful trial block and can fit one waiver-enabled custom payload or two cheaper 120 m payloads.Use this if RFS wants a focused proof flight before scaling.
500 ha planning case
Evidence page		Hourly revisit target = 500 ha.3 payloads at 120 m with a USD 22k unit-cost ceiling, or 2 payloads with a waiver and a USD 33k ceiling.This is the current central planning case; it makes altitude authorisation and unit-cost control decisive.Use this if RFS wants a few-square-kilometre operational block.
1000 ha stretch case
Evidence page		Hourly revisit target = 1000 ha.6 payloads at 120 m with a USD 11k unit-cost ceiling, or 3 payloads with a waiver and a USD 22k ceiling.This exceeds the current custom-payload budget envelope unless the payload becomes cheaper or the fleet budget changes.Use this only if RFS accepts a budget or architecture change.

Closeout test: Record one target area or a bounded first-trial range in hectares.

Question

Altitude path

Can the first survey case assume above-120 m operations?

The waiver case roughly doubles per-drone coverage and can remove one payload from the 500 ha planning case.

Option Answer to record Evidence Design consequence Follow-up
Stay at 120 m
Evidence page		Altitude basis = 120 m AGL cap.The conservative model covers about 182 ha/h per payload.Fleet count rises; the optics and payload branch must work within the most conservative operating envelope.Keep procurement and optics gates tied to the 120 m rows.
Waiver path is realistic
Evidence page		Altitude basis = above-120 m waiver case may be used.The waiver model covers about 378 ha/h per payload.Fewer payloads may cover the same block, but the optical design must still hold the 3 cm target gate at the higher altitude.Ask RFS to name the trial altitude and authorisation path.

Closeout test: Record whether the 120 m cap is binding or the waiver case is in scope.

Question

Payload branch

Should AAO quote COTS first, custom optics first, or both in parallel?

Fast 640-class COTS cameras now pass first-order physics, but only exact product data can prove raw radiometry, calibration access, mass, power, and cost.

Option Answer to record Evidence Design consequence Follow-up
Quote COTS first
Evidence page		Procurement branch = COTS quote gate before custom fabrication.45 deg 640-class radiometric camera reaches SNR 105.8; 69 deg 640-class mapping camera reaches SNR 38.4.This can protect the AUD 100k fleet budget, but only if raw/pre-AGC frames and calibration state are accessible.Request vendor evidence and quotes before ordering hardware.
Run COTS and custom in parallel
Evidence page		Procurement branch = parallel COTS quote gate and custom optics maturation.The custom reference reaches SNR 45.0, while fast 640-class COTS paths also clear the benchmark.This preserves schedule optionality but spends effort on two paths until quotes and interface evidence arrive.Use the same raw-data and calibration checklist for both paths.
Custom first
Evidence page		Procurement branch = custom optics first.The custom reference is the controlled design path; Lepton 3.1R SWaP floor is rejected at SNR 0.4, so not every cheap COTS path is viable.This keeps optical ownership but probably limits the AUD 100k fleet to one or two payloads unless cost is reduced.Restart prescription work only after EFL/FOV and F-number targets are fixed.

Closeout test: Record one procurement branch and the product evidence required before spending.

Question

Airframe class

Is a 2 kg-capable fixed-wing or VTOL survey aircraft acceptable for the first payload?

The current payload boundary points to heavier survey aircraft; a smaller airframe would reopen payload mass, optics, and coverage assumptions.

Option Answer to record Evidence Design consequence Follow-up
2 kg class accepted
Evidence page		Airframe basis = 2 kg-capable fixed-wing or VTOL class is acceptable.The fleet coverage model uses fixed-wing survey platforms and flags 2 kg payload support as a gating assumption.The 150 mm / sub-2 kg custom path can remain in the design space.Carry the current payload envelope into vendor and airframe conversations.
Must be lighter
Evidence page		Airframe basis = first payload must fit a lighter drone class.The COTS screen shows Lepton-class SWaP paths are too weak for the 3 cm target, so smaller is not automatically mission-capable.The project must relax target, coverage, altitude, or payload ownership before the optics work can proceed honestly.Define the actual mass, power, and volume ceiling before more prescription work.

Closeout test: Record the accepted aircraft class or the replacement mass and power envelope.

Question

Requirements sign-off

Who can accept the locked baseline and close RFS-011?

The site now has enough decision artifacts to close the interview, but the TODO must stay open until a stakeholder explicitly accepts the answers.

Option Answer to record Evidence Design consequence Follow-up
Accept locked baseline
Evidence page		Stakeholder accepts area-survey role, 3 cm char target, 640-class LWIR branch, 150 mm package, sub-2 kg payload, and AUD 100k payload budget.These are the locked rows on the closeout checklist.RFS-019 can restart toward a survey prescription instead of revisiting mission role and target class.Record the name, date, and source note before marking RFS-011 complete.
Reopen one baseline item
Evidence page		Stakeholder reopens one or more locked baseline decisions.Any change to role, target class, detector branch, payload envelope, or budget changes the downstream optical target.RFS-011 stays open and the derived coverage, COTS, and prescription pages must be rerun before prototype work.Name the changed decision and rerun the affected decision artifacts.

Closeout test: Record the accepting stakeholder, accepted baseline, and answer source.

Evidence links

Source artifacts behind the answer rows.