Case study 02 · Equipment / Quality
Production Equipment Run-Off & Acceptance
Project record
Professional- Project type
- Professional project
- Domain
- Capital equipment acceptance
- Role
- Manufacturing / Industrial Engineering Manager
- Methods
- Specification review · Acceptance criteria definition · Vendor run-off · Capability study · Punch-list disposition
- Date
- 2024–2026
- Data
- Run-off and capability data generated during acceptance; not reproduced here
- Confidentiality
- Method abstracted. No vendor identity, equipment specification, drawings, cycle times or capability records are disclosed.
Context
New automated production equipment was being introduced into a high-volume manufacturing area. The equipment had been specified and purchased; my involvement began at the point where it had to be proven before it could be accepted and released to production.
The reason this matters more than it sounds: equipment acceptance is the last point at which a supplier still has both the obligation and the leverage to fix something. After buy-off, every remaining defect becomes the plant’s problem, paid for in downtime, scrap and engineering time for the life of the asset. The acceptance decision is cheap. Everything after it is not.
Problem
The specification described what the equipment was supposed to be. It did not, in a usable form, describe what would constitute proof — which is the more common failure in capital projects. “Capable of producing the part to drawing” and “target cycle time” are procurement language, not acceptance criteria. They cannot be passed or failed by two people looking at the same data.
So the first deliverable was not a test. It was a translation: every requirement restated as a characteristic, a method, a sample size and a pass condition, agreed with the vendor before anyone stood in front of the machine.
Constraints
- The installation date was committed and there was production demand waiting behind it — schedule pressure ran against the acceptance decision the entire time.
- Some characteristics could only be verified at volume, which meant part of acceptance necessarily happened after installation and had to be structured as a staged buy-off rather than a single event.
- Acceptance criteria had to be negotiated with a vendor who had a commercial interest in a broader definition of “acceptable.”
- Repeatability had to be demonstrated across operators and shifts, not by the vendor’s best technician.
My role
I defined the acceptance criteria, led the run-off, owned the punch list and its disposition, and made the buy-off recommendation. I also owned the PFMEA, control plan, work instructions and inspection criteria the equipment would run under once accepted — which is the reason acceptance and production readiness were treated as one decision rather than two.
Approach
| Area | Characteristic | Verification method | Pass condition |
|---|---|---|---|
| Build conformity | As-built configuration vs specification and drawings | Physical and documentation review against the purchase specification | No deviation from specified configuration without an approved, documented deviation |
| Safety | Guarding, interlocks, emergency stop function | Functional test of each safety device and interlock path | Every device functions as designed; no bypass required to run the process |
| Cycle time | Sustained cycle time at production configuration | Timed run over a defined production quantity, not a demonstration cycle | Sustained rate meets the specified rate with the specified operator content |
| Repeatability | Output consistency across operators and shifts | Repeat runs with different operators under standard work | No operator-dependent difference in output characteristics beyond the agreed band |
| Process capability | Key product characteristics produced by the equipment | Capability study over a defined sample from stable production | Capability index meets the agreed minimum on each key characteristic |
| Controls | Alarms, fault recovery, data output, parameter security | Functional test including induced faults and recovery | Faults annunciate correctly, recover to a safe known state, and parameters cannot be changed without authorization |
| Documentation | Manuals, spare parts list, maintenance plan, parameter records | Turnover package review against the documentation index | Complete package received and reviewed; maintenance plan loaded before release |
Scroll table horizontally →
Acceptance workflow
- Specification review
Establish what was actually bought, including every referenced standard and drawing revision.
- Acceptance criteria defined and agreed
Characteristic, method, sample and pass condition — signed by the plant and the vendor before run-off.
- Vendor run-off
Executed against the criteria table, with results recorded as evidence rather than as observations.
- Punch list
Every finding logged with a severity, an owner and a required closure evidence type.
- Corrective action
Vendor closes findings; plant verifies rather than accepts a status report.
- Re-test
Re-run only the affected criteria, plus anything the correction could plausibly have disturbed.
- Buy-offStaged
Released for production use with the capability criterion carried as an open item until volume data existed.
- Production releaseReleased
Full release after capability was demonstrated at volume and the punch list was closed.
Analysis
Run-off produced the usual distribution of findings: a small number of genuine non-conformances, a larger number of workmanship and documentation items, and a handful of items that were really specification ambiguities rather than defects — places where the plant and the vendor had read the same sentence differently.
The decisive finding was not a broken part. It was that the equipment met cycle time in a demonstration run and did not sustain it over a production-length run, because a recovery step that was trivial at low volume accumulated. That distinction only appears if the acceptance criterion specifies a sustained rate over a defined quantity rather than a cycle time. It was the clearest argument I have encountered for writing the sample size into the criterion.
Capability was the other open question. At run-off there was not enough stable production to compute a meaningful capability index, and computing one anyway would have produced a number with no statistical standing. Rather than accept a weak study or delay the installation, capability was carried as an explicit open acceptance item with a defined closure requirement.
Engineering judgment
- What decision had to be made?
Can this machine be accepted? And more precisely: can it be released to production while one acceptance criterion — process capability — cannot yet be evaluated on statistically meaningful data?
- What evidence mattered?
Safety and build conformity were closed outright; those are not candidates for staging. Sustained cycle time was re-tested and met after the vendor’s correction. The remaining gap was capability, where the honest position was that the evidence did not exist yet rather than that it was unfavourable. That made a staged buy-off legitimate: production release with the criterion open, a defined sample and closure date, and containment in the form of tightened in-process inspection until the study closed.
- What would cause me to change the decision?
Two things would have changed it. If any safety or build-conformity item had been open, buy-off would have been withheld entirely — there is no version of staging those. And if the early capability data had trended unfavourably rather than merely being insufficient, the correct move is to withhold release, because accepting equipment and then discovering it cannot hold the characteristic converts a supplier obligation into a plant problem. Schedule pressure is a reason to work faster, not a reason to lower the evidence standard.
Engineering Decision
Equipment acceptance
STAGED BUY-OFF — released for production with one open acceptance item
Basis
Safety, build conformity, controls, repeatability and sustained cycle time were verified and closed. Process capability could not be evaluated on a statistically meaningful sample at run-off, so it was carried as an open acceptance item under containment rather than signed off on weak data.
Criteria to close full acceptance
- Capability study completed on the defined sample from stable production, meeting the agreed minimum on every key characteristic
- All punch-list items closed with the evidence type defined at logging — not with a status report
- Tightened in-process inspection maintained until the capability study closes
- Control plan, work instructions and maintenance plan updated to the as-accepted configuration
- Any specification ambiguity resolved by written agreement, so the next identical machine is bought against a clearer specification
Disposition recommended by manufacturing engineering · full release granted after capability closure
Evidence accepted at full release
- Capability study on each key characteristic, from stable production at volume
- Sustained-rate run record over the defined production quantity
- Safety device and interlock functional test records
- Punch-list closure evidence, item by item
- As-accepted configuration and parameter record
- Turnover documentation package reviewed against the documentation index
Result
The equipment was released to production on the committed schedule, with the capability criterion closed on real volume data shortly afterward and the punch list closed against defined evidence. Nothing was accepted on the strength of a verbal assurance.
The durable output was the criteria structure itself. Writing characteristic, method, sample and pass condition for every requirement meant later equipment could be specified and accepted against something that could actually be failed — and it made the ambiguities visible during negotiation rather than during run-off.
What I learned
A requirement without a sample size is not an acceptance criterion. The sustained-rate finding existed only because the criterion specified a quantity. A cycle-time number on its own would have passed.
Negotiate the criteria, not the findings. Every hour spent agreeing pass conditions before run-off saves several during it. Arguments about whether something is a defect are almost always arguments about a criterion nobody wrote down.
“Pass with an open item” is a real disposition, and it needs rules. It is legitimate when the missing evidence is missing rather than unfavourable, when containment covers the interval, and when closure has a defined sample and date. Without those three, it is just a failure with better manners.
Acceptance and production readiness are one decision. Accepting equipment without the control plan, work instructions and maintenance plan in place moves the risk rather than closing it.
Tools & methods
- Specification review
- Acceptance criteria definition
- Vendor run-off
- Punch-list disposition
- Functional testing
- Capability study
- PFMEA
- Control plan
- Standard work
- Turnover documentation
Why this project is on the site
Production-equipment run-off is not the same thing as a mission-critical factory acceptance test. The equipment class, the failure consequences and the standards regime all differ. The underlying quality discipline is the same: requirements must be translated into measurable acceptance criteria, evidence must be objective, and unresolved defects must be dispositioned before release.
The liquid cooling skid study applies that discipline to cooling equipment, and the 8D investigation shows what happens when a performance criterion is not met at FAT.