Moving from a laboratory motion prototype to an OEM requirements package

A laboratory prototype shows that a concept may be worth developing. An OEM requirements package explains what must be supplied, how it will connect and what evidence will establish acceptance. Moving between those stages requires more than replacing a bench drawing with a production part number.

This article proposes a documentation process. It does not claim that any catalogue stage is qualified for semiconductor throughput, medical use, cleanrooms, vacuum service or another specialized production environment.

Separate observations from requirements

Start with a record of what the prototype actually did. Include configuration, payload, mounting orientation, measurement method and relevant conditions. Preserve unsuccessful trials and workarounds as well as useful results.

Then write the requirement the product genuinely needs. An observed result may suggest that a target is feasible, but it does not automatically define the correct contractual limit. Conversely, a laboratory result obtained under favorable conditions does not establish behavior across all intended operating conditions.

Newport’s motion terminology reference distinguishes motion specifications. Use clear terms in the package: commanded increments, repeatability and positioning accuracy should not be substituted for one another.

Freeze interfaces at useful boundaries

Create controlled drawings for the mounting surface, moving payload, adapter and service connections. Identify dimensions that matter to the functional point, not just the outer envelope. Include the required space for installation and replacement.

Record controller, cable and software interface assumptions. Distinguish documented functions from prototype scripts or manual actions that someone performed during testing. A production requirement must state whether those actions will remain manual, be automated or be removed through a design change.

Capture configuration identifiers and revisions. If the proposed unit differs from the tested prototype, show the differences explicitly so that the review can decide which evidence remains applicable.

Replace vague duty claims with an operating profile

Describe the intended sequence of moves, holds, loading events and idle periods. State the relevant payload and orientation for each part of the sequence. The supplier needs more than a requested maximum speed to evaluate the application.

Identify environmental and service requirements separately. If vacuum, cleanliness or another special condition matters, request explicit configuration-specific evidence. Do not infer compatibility from material names, surface treatment or a successful ambient bench trial.

Zaber’s rotary selection guidance illustrates that load geometry and motion requirements belong in selection. Its product capabilities do not establish duty or life ratings for the mechanisms in this catalogue.

Practical OEM handoff checklist

• Archive the tested prototype configuration and measurement records.
• Separate observations, design targets and contractual acceptance limits.
• Freeze mounting, payload, cable and controller interface revisions.
• Describe the representative operating sequence and duty assumptions.
• List environmental qualifications that still need explicit evidence.
• Define acceptance tests, instruments, conditions and required records.
• Assign owners and closure criteria to unresolved requirements.

Keep a change-impact record. A replacement motor, revised holder or different cable route can affect the relevance of earlier evidence even when the product’s outward appearance is unchanged.

Hypothetical example: the bench needed an operator

Suppose a prototype completes a positioning task successfully, but an engineer manually checks the part reference after each loading operation. The proposed OEM system is expected to run without that intervention. Copying the prototype’s move sequence would omit an important function.

The requirements package records the manual check, identifies its purpose and asks the team to define an acceptable production method. It may lead to improved tooling, an added measurement or a different workflow, but the example does not presume which solution will work. No production rate or reliability result is claimed.

Make acceptance reproduce the requirement

For each important requirement, state the evidence that will demonstrate it under the intended conditions. Separate supplier component tests from tests of the integrated machine. Identify which must occur before shipment and which need the final installation.

Use the specification basis guide when interpreting catalogue fields, and attach the completed package to a quotation request. The objective is a reviewable agreement about configuration and evidence, not an unsupported promotion of a laboratory success into a production qualification.

Include an explicit disposition for failed acceptance tests, identifying who reviews the evidence and which changes require renewed verification before delivery.