Production Handover and Documentation

A production handover is the point at which a product moves from the people who developed it to the people who will build it every day. The information that changes hands at that moment determines whether the process runs or stalls.

The handover is a document set and a series of conversations, and both are needed. A package without the conversations leaves questions that nobody knows to ask.

What the Build Package Contains

The package includes the assembly drawing, the bill of materials, the work instructions, the process parameters, the tooling list, the test programme and the inspection criteria. Each item should be at the revision that will be built.

A package that is complete but scattered across several systems is not usable at the station. The practical format is a single index with the location of each item.

Process Parameters

The parameters include the printer settings, the profile, the oven atmosphere, the placement programme and the inspection limits. They should be recorded as values rather than as a range, with a note of the conditions they were developed under.

A parameter that was developed on a different line should be re-verified rather than transferred, since the equipment differs. This is described for the profile in zone verification.

Tooling and Its Location

The tooling list should identify every item, its location and its condition, so that the line can find what it needs. A tool that is listed and missing delays the first build.

The register is also what prevents duplicate purchases and lost items, as discussed for tooling investment.

Training and Competence

The handover should identify the skills the product requires and confirm that the operators have been trained for them. A new process introduced without training is built with old habits.

The training records should reference the instruction revision used, as described for workmanship training.

Known Issues and Lessons

The development team knows which steps are difficult and which defects appeared during the pilot. Those should be written down rather than remembered, because the people change.

The list should include the temporary measures taken during the ramp and the criteria for removing them, so that a containment does not become permanent.

Acceptance of the Handover

The receiving team should accept the package by building to it, which is the only test that the documentation is complete. A handover accepted on a document review is accepted on faith.

The acceptance should include a first article verified against the drawing and the process record. This is the same discipline as first article checks.

Support After the Handover

The development team should remain available for a defined period, since questions appear during the first weeks of production. An agreed support window is better than an open ended expectation.

The questions that are asked should be recorded, since they reveal gaps in the package that can be closed for the next product.

Records

The handover should be recorded with the package revision, the date and the people involved, so that the state of the process at the start of production is known.

It belongs with the production documentation described for manufacturing processes.

Process Control and Verification

Where the requirement is not written down, the shop supplies its own default, and the default is chosen for the process rather than for the design. The measurements that matter are the repeatable ones: conductor width and spacing, annular ring, finished hole size, plating thickness and surface finish are all verifiable on a coupon that travels with the panel.

Running a first article through the same checks as the production panel confirms that the two agree, and that comparison is the cheapest form of process control available at prototype stage. Keeping a sample from the panel turns a dispute into a measurement, because the same coupon can be re-examined by both parties without rebuilding the batch.

Reviewing the design before the data is released is cheaper than correcting it after the panel is in the tank, because every step downstream inherits the decision made at the front end. Documenting the assumption is part of the design work, and a short note on the drawing prevents a question that would otherwise arrive a day later and cost a day of schedule.

The process window is set by the narrowest step in the flow, so an improvement anywhere else shows up as margin rather than as yield until that step is addressed.

Checks Before Release

The checks that matter are the ones performed on the product rather than on a sample kept for the purpose, because a coupon that travels with the panel is the only evidence about that panel. Where a requirement can be measured, it should be measured at the point of manufacture and recorded against the board or the lot it applies to.

A parameter that is set once and never re verified drifts, and the drift is usually discovered by a defect rather than by the record. The tooling, the material and the profile form one system, and a change to any of them should be assessed against the other two before it is released.

Where the process window is narrow, the measurement resolution has to be better than the window, or the data cannot distinguish a good part from a marginal one. A record that identifies the operator, the date and the settings is worth more than a record that identifies only the result.

FAQ

When should the handover happen? Before the first production build, with the pilot as the rehearsal.

What is the most common gap? The process parameters, which are often known by one engineer and written nowhere.

How is the handover verified? By building to the package and verifying the first article against the drawing and the process record.

Should the development team remain involved? For a defined window, since the questions that appear in the first weeks are the ones the package does not answer.