Map every test stage
Incoming, subassembly, firmware, calibration, functional, system, environmental, flight, data review, final acceptance, and customer-specific evidence.
CONSTRAINT GUIDE / TEST CAPACITY
When test controls drone production.
Model equipment, fixtures, software, calibration, setup, failure analysis, retest, data review, staffing, and acceptance as one test production system.
How can test capacity control the entire drone factory?
Accepted output cannot exceed the complete test system's sustainable throughput. Equipment cycle, setup, calibration, software, fixtures, failure analysis, retest, data review, staffing, environmental limits, and release authority all consume test capacity.
PLANNING RELATIONSHIP / NOT A FORECAST
Accepted test output depends on more than nominal cycle time.
Staffed usable test time÷Effective test cycle plus queues×First-pass acceptance=Planning output signal
The relationship is intentionally simplified. Real planning must account for product mix, setup, calibration, maintenance, shared assets, environmental restrictions, retest, review, and release rules.
Measure effective cycle
Include setup, changeover, queue, loading, automation, technician touch time, data transfer, review, failure analysis, retest, and release.
Separate failure demand
Track false failures, product defects, fixture issues, software issues, calibration escapes, retest loops, and investigation load.
Define acceptance authority
Clarify what record establishes pass, who reviews it, what blocks release, and how exceptions are controlled.
TEST CAPACITY CHECK
Questions to answer before adding assembly upstream
| Question | Evidence | Why it matters |
|---|---|---|
| Which test step limits accepted output? | Queue, utilization, effective cycle, and release data by step | The most visible equipment may not be the system constraint |
| What drives retest? | Failure modes, false-failure rate, repair loop, and re-entry point | Retest can consume more capacity than initial test |
| What is shared? | Fixture, chamber, range, software, technician, reviewer, and calibration calendars | Shared resources create hidden coupling across products |
| Can the test basis replicate? | Released procedure, configuration, fixtures, software, data, training, and authority | A second station without control may not produce equivalent evidence |
NEXT COMPONENT / DECISION
Treat test as a production system, not an end-of-line box.
A high-level review can separate nominal equipment capacity from the complete path to accepted output.
Request a production scale review