Yesoem editorial · General procurement and process guidance
A hardware prototype can work while leaving its manufacturing decisions unresolved. A lid fits because somebody adjusts it; a cable clears because it is routed differently; a bracket is modified during assembly. Those interventions are useful learning, but they should not disappear when a team orders its next batch. For a sheet metal product, a valuable step between prototype and repeat production is to decide which interfaces must remain stable and which features may still change.
This is a practical planning approach, not a claim about market growth or a universal rule that every design must be frozen early. The objective is to keep experimentation possible while making its consequences visible.
Treat interfaces as purchasing decisions
An interface is where the fabricated part meets something else: a display, hinge, fastener, cable, seal, neighbouring panel or installation surface. Its definition affects more than the outline in a drawing. It also determines which component must be available for a fit check, who owns the relevant dimensions and what evidence allows an assembly to be accepted.
For each important interface, name the mating component and its revision. State whether the supplier receives a physical sample, a controlled model or a drawing. If the purchased component is still undecided, record that uncertainty instead of allowing a convenient prototype component to become an undocumented production assumption.
Separate stable requirements from open choices
A useful working document has three short lists. The first contains requirements that cannot change without approval, such as mounting locations or an agreed external envelope. The second contains features the supplier may propose changing, such as a noncritical flange arrangement. The third contains unresolved choices that prevent a reliable production decision.
NASA's configuration-management guidance explains the role of identifying an agreed baseline and controlling subsequent changes. A small hardware team need not adopt a space-program workflow to use that principle: an identifiable release and a clear approval record are more useful than several files all named “final.” NASA's guidance provides the underlying systems-engineering context.
Do not put every dimension in the first list merely because it appears in CAD. Ask what function a requirement protects. Where dimensional relationships need formal definition, agree the applicable drawing convention with the responsible engineer. ASME's Y14 standards overview describes standards for engineering drawings and dimensioning; citing it does not establish a supplier's capability or require one convention for every project.
Compare two routes for an uncertain component
Consider a hypothetical enclosure whose display has not yet been selected. One route is to integrate the mounting features directly into the main panel. Another is to use a separate mounting part that can change independently. Neither route is automatically better.
The integrated approach may simplify the parts list, but a display change could require a new panel revision. The separate part may isolate that change, while introducing another component, joint and inspection responsibility. The decision should consider access, stiffness, appearance, assembly time and the likely replacement task. These are questions for the design review, not numerical savings that can be assumed in advance.
Record why the chosen route was accepted. If the component later changes, the team can revisit the actual trade-off rather than treating the earlier prototype as unquestionable evidence.
Use a change-impact checklist
Before releasing an update, ask the following questions together rather than passing a revised drawing between departments without context:
- Which part numbers, drawings and purchased components are affected?
- Does the change alter a mating surface, hole pattern, installation clearance or assembly sequence?
- Is existing material, work in progress, finished stock or tooling affected?
- Which inspection or fit checks must be repeated, and who accepts the results?
- When does the new revision take effect, and how will old and new parts be distinguished?
The answer can be brief. A change affecting only a label location need not receive the same review as a change to a load-bearing interface. What matters is a conscious decision about the impact, including any uncertainty that remains.
Make the next batch a learning step
For a prototype or small batch, state what the order is intended to demonstrate. It might establish assembly access, check an approved appearance sample or test a particular mounting arrangement. Define the evidence required for that decision and separate it from tests that are outside the order.
After receiving the parts, record deviations, assembly interventions and unanswered questions against the released revision. A successful one-off fit does not by itself show that every future batch or component combination will work. Conversely, a useful prototype may reveal a design change before a larger commitment is made.
Yesoem welcomes discussions about prototype and small-batch enquiries. Bring the interface decisions and open questions alongside your drawings when contacting the team. The existing RFQ preparation guide covers the enquiry package; the project contact page provides the confirmed contact channels. Feasibility, responsibilities and timing remain subject to project review.