Selection evidence, not a model shortcut
A defensible feeder decision starts with the released job requirement, continues through documentary capability evidence, and ends with a measured acceptance record.
This framework is for a named part, die, strip layout, press condition and feeder project. It does not explain the feed-pitch concept, publish generic machine limits, recommend a feeder type, or provide adjustment, calibration, setup or troubleshooting instructions.
Record what the released job package requires, including its source, revision, units, references and applicable conditions.
Retain the named configuration and the controlled document that states its capability for the submitted requirement.
Keep the approved method, measurement context, result, disposition and sign-off as a separate acceptance record.
Freeze the job, drawing, die, strip layout and feed reference
Begin with identity, not an assumed number. The selection record should name the part or job, the approved drawing revision, the die and strip-layout revision, the press or line identity, the feed reference used by the released package, and the people authorized to resolve missing or conflicting data. If two documents carry different revisions or references, that is a data hold rather than permission to choose the more convenient entry.
The record also needs the material and production context that qualifies the requirement: material grade and condition, thickness, width, surface restrictions, strip orientation, relevant die progression, the approved press operating window, and any project-defined pilot, release or interface condition. These are inputs for the named project. They are not universal selection rules, and this article does not infer their effect on a feeder.
| Record field | Named source | Release question | Hold condition |
|---|---|---|---|
| Part, job and drawing | Approved job package and drawing revision | Is the identity current and unambiguous? | Missing revision, superseded issue or conflicting identity |
| Die and strip layout | Released die and progression records | Are the governing layout and reference points named? | Draft layout, unclear reference or unapproved change |
| Press and interface context | Project interface and operating documents | Are the applicable conditions and authority identified? | Unknown line identity, condition or responsibility |
A useful freeze sheet is reviewable by engineering, procurement, tooling, production and the supplier without relying on memory. Each field should show who supplied it, when it was released, which revision applies and who owns clarification. That discipline prevents an RFQ from silently mixing a new drawing with an old layout or treating an early quotation assumption as final job data.
Record the required pitch, range or sequence from the released source
Once the governing records are identified, transcribe the actual job requirement exactly as those records state it. The controlled entry may include a single required value, a released range, or an approved sequence. Preserve its units, direction, reference points and applicable tolerance only when the named source supplies them. Do not fill an empty field from a brochure, a prior project, a website table or an operator’s recollection.
Context belongs beside the entry. Note the job and revision, material condition, strip and die reference, expected production condition, and any released qualifier that changes when the requirement applies. A bare value detached from these conditions is not a complete procurement input. If the project package does not state a required range, sequence, direction, reference or criterion, label the omission as an RFQ hold and assign the authority responsible for resolving it.
Copy only from the named released record. Retain document number, revision, page or field reference, units and approval status.
Mark missing or conflicting data visibly. An unresolved blank is a decision gate, not an invitation to invent a limit.
Attach the material, die, strip, press and project conditions under which the requirement was released.
Reopen the requirement when its governing drawing, die, strip layout, material or operating condition changes.
Separate required, supplier-declared and measured acceptance data
Keep the three evidence classes in different columns or records. The required entry comes from the released job package. Supplier-declared data comes from the named feeder configuration and its controlled capability documentation. Measured and accepted data comes from the authorized acceptance activity. The three may be compared, but they are not interchangeable.
| Evidence class | What the record identifies | Minimum traceability | What it does not prove |
|---|---|---|---|
| Required job data | The released value, range or sequence for the named job | Job, drawing/layout revision, source, units, references and conditions | That any proposed feeder can meet it |
| Supplier-declared capability | The stated capability of the named configuration | Model/configuration, option state, controlled document and applicable conditions | That the submitted job has passed acceptance |
| Measured and accepted result | The observed result under the approved acceptance plan | Method, instrument/calibration record, sample, criterion, result, disposition and sign-off | Capability outside the tested and approved scope |
This separation makes an RFQ auditable. It shows whether procurement has a complete requirement, whether a supplier declaration addresses the same conditions, and whether acceptance has been completed or remains open. It also prevents marketing language, a screen value or a quotation line from being presented as measured production evidence.
Request capability evidence and complete RFQ inputs without guessing
An evidence-ready RFQ gives the supplier the frozen job package and asks for a response tied to the named proposed configuration. The response should identify the feeder, relevant options and revision-controlled capability evidence that covers the submitted requirement and its applicable conditions. Unknowns stay visible. A quotation that omits the governing range, sequence, material condition or interface qualifier should return for clarification rather than being upgraded into an assumption.
- Attach controlled job inputs. Include the released drawing and strip-layout references, required entry, material context, press condition, relevant interface inputs and acceptance authority.
- Request a named response. Require the exact proposed configuration, documentary capability reference, applicable conditions, exclusions and unresolved dependencies.
- Compare like with like. Confirm that units, references, direction, job conditions and revisions align before treating the declaration as responsive.
- Keep holds open. Assign missing data, exceptions and conflicts to a responsible owner with a due date and disposition path.
Roller-specific commercial discovery and data collection belongs in the roller feeder RFQ checklist. Product questions belong to the existing NC servo feeder models and high-speed roller feeder models pages. Those routes are owner boundaries, not recommendations, capability proof or permission to choose a model from width and pitch alone.
Freeze the authorized acceptance plan and evidence record
Acceptance should be planned before the result is needed. The released plan identifies the authorized setup, representative material and job, measurement reference, approved method, instrument and calibration record, sampling plan, criterion, observers, stop conditions, disposition authority and required sign-off. This article does not supply those values or the measurement procedure; it defines the fields that make the resulting record traceable.
Detailed method ownership stays separate. Use the existing feeder pitch measurement and calibration page for that specialist topic, while the named project procedure remains the controlling authority. Installation and setup responsibilities likewise remain with NC servo feeder installation and acceptance planning. Neither linked page substitutes for the current job’s released documents.
Record the job, material, die, press, feeder configuration, document revisions and actual test conditions.
Cite the approved method, measurement reference, instrument identity and applicable calibration record.
Retain each observed result with its source-bound criterion, sample context and reviewer.
Record accept, hold, rework or other authorized disposition, plus retest and final sign-off when required.
A photograph may document context, but it cannot replace the controlled result. The final package should allow a reviewer to reconstruct which requirement was checked, under which authorized conditions, by which method, with which instrument record, against which criterion, and how any exception was resolved.
Route unknowns, deviations and the controlled handoff
Not every comparison closes on the first review. Missing source data, an incomplete supplier declaration, a measurement outside the released criterion, a changed job condition or an unexplained observation should remain visible until an authorized owner dispositions it. Do not convert the exception into a generic diagnosis or make an undocumented adjustment to force closure.
Return missing or conflicting job inputs to the drawing, tooling or process authority named by the project.
Ask the supplier to clarify the named configuration, document, conditions, exclusion or dependency in writing.
Preserve the result, contain the affected scope, obtain disposition, and record any approved retest and closure.
Symptom-led investigation belongs with NC servo feeder feed-error diagnosis; this page does not assign a cause or corrective setting. The handoff here consists of the frozen requirement, supplier response, acceptance record, unresolved items, dispositions, approvals and change-control triggers. If the drawing, strip layout, material, die, press condition or feeder configuration changes, reopen the affected evidence rather than carrying the old acceptance forward automatically.
Frequently asked questions
Which records should establish the actual job requirement?
Use the named released job package, drawing, die and strip-layout records that the project authority identifies as controlling. Retain their revisions, units, references, applicable conditions and approval status. Missing or conflicting data should remain an assigned RFQ hold.
How should supplier-declared capability be handled?
Keep it as a separate evidence class tied to the exact proposed feeder configuration, controlled capability document and applicable conditions. Compare it with the released requirement, but do not present the declaration as a measured or accepted result.
Does this framework provide an adjustment or calibration method?
No. Adjustment, calibration, setup and troubleshooting remain with their dedicated owners and the named machine or project procedure. This framework records the approved method reference, instrument and calibration record, result, criterion, disposition and sign-off.
What belongs in the acceptance evidence package?
Include the job and configuration identity, governing document revisions, actual conditions, authorized method, measurement reference, instrument and calibration record, sampling, criterion, result, deviations, disposition, retest when required and final approval.
What happens when required data is missing or a result is outside criteria?
Place the affected decision on hold, preserve the observation and context, assign the named technical or commercial owner, obtain an authorized disposition, and record any approved retest and closure. Do not guess a value, cause, model or corrective setting.
Build an evidence-ready feeder RFQ
Bring the released job, drawing and strip-layout references; actual required data; material and press context; open questions; requested capability documents; and the acceptance-plan owner. A complete handoff keeps requirements, declarations and accepted results distinct.
