Locked
4 carry-forward decisions now define the survey-camera baseline.
Requirements closeout checklist ยท 2026-06-17
Close RFS-011 by answering the remaining fleet decisions.
The mission role, target class, detector branch, package size, and payload budget are now stable enough to carry forward. RFS-011 should stay open until the target area, altitude path, payload branch, airframe class, and stakeholder sign-off are explicit.
Closeout state
Four decisions are locked; five still block requirements closure.
Open
5 stakeholder decisions still control fleet size, altitude, and procurement.
Coverage lever
One payload covers about 182 ha/h at 120 m, or 378 ha/h with the waiver case.
COTS gate
6 modeled paths clear SNR 10; quotes and product data are still missing.
Carry-forward baseline
These decisions are stable enough for the next design pass.
| Decision | Current answer | Evidence | Carry-forward rule |
|---|---|---|---|
| Operating role | Area-survey, find-only camera rather than a cue-following spotter. | Dani reply recorded on 2026-06-14; the mission-decision page treats the camera as the wide-field survey instrument. Evidence page | Carry this as the default unless RFS explicitly reopens the mission role. |
| Design target class | 3 cm smouldering-char patch is the design driver. | The F-number/aperture trade and COTS screen both use the 3 cm, 430 K smouldering-char target as the benchmark gate. Evidence page | Keep 1 cm ember and weak warm-edge cases as stress rows, not the first build driver. |
| Detector branch | 640 x 512 uncooled LWIR radiometric branch, with Boson+ as the custom reference. | The stakeholder reply kept the 640-class branch, and the detector catalogue still uses Boson+ 640 radiometric as the preferred custom-optics core. Evidence page | Do not switch detector pitch, format, or NETD without rerunning the sizing screens. |
| Payload and budget bounds | 150 mm package, sub-2 kg payload boundary, AUD 100k payload budget excluding drones. | The expert update and later coverage artifacts use the same package, mass, and budget assumptions. Evidence page | Treat any larger package, heavier payload, or bigger budget as a formal requirements change. |
Before closing RFS-011
These rows still need stakeholder answers.
| Decision | Current state | Ask before closing | Why it matters |
|---|---|---|---|
| One-hour target area | Not yet specified by RFS. | Choose the operational block size that must be revisited hourly, or provide a range for the first trial. | This is the main remaining fleet-economics input; it decides whether custom payloads can fit the AUD 100k budget. |
| Altitude authorisation | 120 m AGL cap is the conservative reference; waiver path remains unconfirmed. | Confirm whether above-120 m survey operations are realistic for RFS trials. | A waiver can reduce payload count for a 500 ha block, but it cannot fix every budget case. |
| COTS versus custom payload branch | Fast 640-class COTS paths pass first-order physics, but product evidence is missing. | Ask vendors for exact raw-frame, calibration, integration, mass, power, and quote data. | If a COTS path clears product gates, the first build may avoid custom optics; otherwise custom ownership remains justified. |
| Airframe and payload class | 2 kg-capable fixed-wing or VTOL class is assumed, not signed off. | Confirm that RFS accepts the heavier survey-airframe class for the first payload trial. | If not, the project must down-select to a lighter COTS branch or relax capability. |
| Closeout authority | No recorded stakeholder sign-off yet. | Get an explicit stakeholder note accepting the locked decisions and resolving the open rows. | Only then should RFS-011 move to Complete pending commit or Done. |
Coverage consequence
The target area directly sets payload count and unit-cost ceiling.
| Target area | Payloads at 120 m | Max unit cost at 120 m | Fit at 120 m | Payloads with waiver | Max unit cost with waiver | Fit with waiver |
|---|---|---|---|---|---|---|
| 250 ha (2.5 km2) | 2 | USD 33k | Only low-end custom fits | 1 | USD 66k | Custom band fits |
| 500 ha (5.0 km2) | 3 | USD 22k | Needs cheaper payload or more budget | 2 | USD 33k | Only low-end custom fits |
| 1,000 ha (10.0 km2) | 6 | USD 11k | Needs cheaper payload or more budget | 3 | USD 22k | Needs cheaper payload or more budget |
Procurement consequence
COTS can only close the budget gap if product evidence is real.
| Payload path | Status | 1px SNR | Coverage | Procurement action |
|---|---|---|---|---|
| Custom Boson+ survey reference | Custom reference | 45.0 | 179 ha/h | Keep as the controlled custom reference, but do not fabricate before the COTS quote gate. |
| 45 deg 640-class radiometric camera | Physics pass, product gate open | 105.8 | 341 ha/h | Do not buy generically; ask vendors for raw radiometry, calibration hooks, mass, power, and quote. |
| 69 deg 640-class mapping camera | Physics pass, product gate open | 38.4 | 565 ha/h | Quote only as a find-only area-survey branch; reject if raw frames or calibration state are hidden. |
| Lepton 3.1R SWaP floor | Reject primary path | 0.4 | 898 ha/h | Use only as an electronics and pipeline floor; reject as the RFS-011 primary payload. |
Stakeholder reply needed
A short answer set is enough to close the requirements item.
Ask 1
Pick the hourly target area or first-trial range.
Ask 2
Confirm whether above-120 m operations can be used for the survey case.
Ask 3
Choose whether to quote COTS first or keep custom optics as the first build branch.
Ask 4
Confirm the 2 kg-capable fixed-wing or VTOL class is acceptable.
Ask 5
Reply with explicit sign-off so RFS-011 can be closed in TODO bookkeeping.