From Prototype to Production: What Changes When an Unmanned Vehicle Must Be Built Repeatedly

A prototype answers one question: can this vehicle exist and perform? Production answers a harder one: can it exist again—next month, in quantity, built by people who did not design it, from parts bought rather than hand-made, to a specification that inspection can verify? Teams that treat production as “building more prototypes” discover the difference the expensive way. The difference is not effort; it is a change in what the engineering is about.

What actually changes

• The design must become explicit. A prototype tolerates knowledge living in the builder’s head. Production requires drawings, models, tolerances, torque values, adhesives, cure times, and acceptance criteria written down precisely enough that a stranger can build the vehicle—and an inspector can reject a bad one.
• Configuration control becomes law. When every vehicle must match a defined configuration, changes stop being tweaks and become controlled events with review, effectivity, and records. Without this, a fleet becomes a collection of similar-looking one-offs that no maintenance program can serve.
• Parts stop being heroic. The hand-finished bracket and the one component a friendly supplier expedited must give way to sourced parts with lead times, alternates, and incoming inspection. Make/buy decisions, supplier assessment, and material flow become engineering topics, not purchasing chores.
• Quality becomes a system, not a person. Prototype quality is the lead engineer looking hard at everything. Production quality is planned inspection points, traceability from raw material to serial number, and records that survive an audit—and staff turnover.
• The workforce becomes part of the design. Assembly sequences, work instructions, fixtures, and training determine whether the drawing package produces good vehicles or scrap. Design-for-assembly stops being a slogan and starts driving change requests.
• Test changes character. Development test asks whether the design works. Production test asks whether this unit was built correctly—a shorter, cheaper, repeatable check that must be designed like any other part of the product.

Common mistakes

• Quoting production prices from prototype costs, then discovering that documentation, quality, and supplier development were never in the number.
• Freezing the design too late—or never—so the line builds a moving target.
• Scaling rate before first-pass yield is understood, which multiplies rework instead of output.
• Leaving supportability out of the production baseline, so the fielded fleet cannot be maintained economically.
• Assuming the prototype team can simply become the production team without new skills, roles, and tooling.

A readiness checklist

• Is there a released, change-controlled design baseline that a third party could build from?
• Does every part have a source, a lead time, and an acceptance method?
• Are assembly steps documented with work instructions and the fixtures they assume?
• Are inspection points, acceptance tests, and traceability defined per unit?
• Has a low-rate build been used to measure yield, hours, and cost before committing to rate?
• Is the support system—spares, manuals, repair levels—part of the same baseline?

Crossing this gap is a project in its own right, with its own requirements, reviews, and evidence. Plan it that way, and production becomes a designed outcome instead of a hopeful extrapolation.