Measured Acceptance
Acceptance is the evidence-based decision that one named feeder–press–die configuration meets approved job and interface criteria. It is separate from adjustment and commissioning, and it must remain reviewable after the trial team leaves.
- IdentityExact machine, die, material, job and revisions.
- MeasurementTarget, individual results, units and method.
- InterfaceFunction, source, receiver, state and response.
- DispositionPass, deviation, owner, action and approval.
Freeze the accepted configuration
Record the feeder model or project identity, press, die, material, strip layout, feed reference, recipe revision, release method, relevant interface hardware and operating condition. Acceptance evidence from another die, material or recipe does not prove the current job.
| Configuration group | Record | Reason |
|---|---|---|
| Equipment | Feeder, press, die and relevant options by project identity | Prevents evidence from being assigned to the wrong line. |
| Job | Material, width, thickness, pitch, strip layout and part revision | Connects the result to the work being released. |
| Controls | Recipe, I/O list, interface drawing and applicable software or parameter revision | Defines what each observed state means. |
| Authority | Test owner, stop authority, witness and final approver | Makes decisions and open items traceable. |
Approve the measurement plan before collecting results
The released plan must define the target, reference points, instrument, resolution, sample count, operating modes, speed stages, tolerance and rule for handling an outlier or interrupted run. This page does not invent a universal tolerance or sample number.
- Keep individual values: an average alone can hide drift, alternating error or one unstable feed.
- Keep conditions: tie every result to the material, mode, speed, recipe and sequence position.
- Keep the reference: state whether the measurement is strip travel, die progression, pilot-hole location or an approved part characteristic.
- Keep the disposition: pass, repeat, reject or accept by an authorized deviation process.
Evaluate accuracy and repeatability separately
Accuracy asks whether measured feeding is centered on the approved target. Repeatability asks whether consecutive feeds remain sufficiently consistent. A feeder can be repeatable but biased, or average correctly while individual feeds vary too much. Record both instead of applying an unexplained compensation to one sample.
| Review | Evidence | Typical hold question |
|---|---|---|
| Target accuracy | Approved target and each measured result | Was the same reference and method used throughout? |
| Repeatability | Consecutive results and their sequence | Does variation begin after speed, release or material changes? |
| Strip condition | Marks, edge rub, pilot-hole damage and deformation | Is the measurement masking slip or mechanical constraint? |
| Part result | Approved dimensional or visual criteria where applicable | Is the part characteristic actually controlled by feed position? |
Verify feeder–press interface functions
Create a responsibility matrix for every project-defined exchange. Name the function, source, receiver, active and inactive meaning, prerequisites, expected response, safe state, observation method and acceptance record. Terms such as “feed signal” are not enough if the project contains separate permissive, request, ready and complete states.
Validate release and pilot behavior
Where the die uses pilots, the authorized trial must show that the feeder releases the strip during the project-defined correction condition and regains control as required for the next feed. Record the press mode, speed stage, observed machine state, strip behavior and evidence source. A photograph of the feeder does not prove release timing.
- No constraint: the strip is not visibly pulled against the pilot correction defined by the die process.
- No uncontrolled movement: release does not allow unintended strip travel or loss of reference.
- Repeatable handoff: the behavior remains consistent for the required approved sample and speed stages.
Close deviations before production release
A failed or ambiguous check is not erased by rerunning only the best-looking cycle. Create a deviation record with the exact condition, evidence, containment, owner, corrective action and authorized retest. If the configuration changes during correction, identify which earlier results must be repeated.
Retain raw evidence
Keep individual measurements, relevant interface logs or observations, photos tied to the condition, and the approved test sheet.
Release the named state
The approval must identify the machine, job, recipe and operating range actually accepted, plus every remaining restriction.
Keep long-tail acceptance topics separate
These pages answer narrower questions and are intentionally not merged into this checklist:
Encoder and signal synchronizationArchitecture, interruption triage and safe signal checks.
Signal cam setupDedicated installation and project timing context.
Frequently asked questions
Does one accurate feed pass acceptance?
No. Acceptance should include the approved set of consecutive results and conditions needed to evaluate accuracy and repeatability.
Can commissioning results be used for acceptance?
Yes, when the approved acceptance plan defines them, the configuration is unchanged, and the raw results, conditions and authorization are retained.
What if a signal name is unclear?
Stop the interface decision, identify the released drawing or I/O definition and assign the controls owner. Do not infer polarity or purpose from a label alone.
Build a reviewable acceptance package
Provide configuration identity, approved criteria, individual measurements, interface evidence, release observations, deviations and sign-off. HENLI can review whether the package clearly separates facts, assumptions and open work.
