Sustained accepted rate
State parts per minute at the agreed hand-off, test duration, allowed interventions and representative reject conditions.
USER REQUIREMENT GUIDE
Specify the production result—not just the feeder.
Use this checklist to define the component, accepted output, hand-off, integration and proof needed from a complete automated parts feeding project.
Prepared by the Sortation Solutions project team · Updated 1 September 2026 · Approx. 8 minute read
DIRECT ANSWER
What belongs in a parts feeding system specification?
A useful specification describes the complete production outcome and the evidence that will prove it.
Record every part variant, real sample condition, sustained accepted output, final presentation, permissible contact and damage, buffer behaviour, inspection, changeover, controls, safety, access, factory testing, installation and handover. Then state who owns each interface and how acceptance will be measured.
Avoid copying a theoretical feeder speed into the requirement. Define accepted components at the receiving-machine hand-off over a representative test period.
CHECKLIST 01
Component and sample definition.
The supplied sample population must represent the parts the system will meet in production.
| Record | Questions to answer | Evidence to provide |
|---|---|---|
| Full component family | Which variants run now, and which future formats require provision? | Named part list, drawings, CAD and revision status |
| Incoming condition | Are parts oily, dusty, warm, static-prone, tangled, nested or cosmetically sensitive? | Uncleaned production samples and packaging method |
| Natural variation | What dimensional, moulding, stamping, finish or supplier variation is acceptable? | Samples from different batches, cavities and suppliers |
| Difficult population | Which acceptable parts have historically caused misfeeds or damage? | Known difficult but conforming parts, clearly labelled |
| Part contact rules | What surfaces may touch, accumulate or recirculate? | Cosmetic zones, damage limits and cleanliness requirement |
| Trial quantity | Can the required test duration run without excessive reuse? | A representative bulk quantity agreed before the trial |
CHECKLIST 02
Output, orientation and hand-off.
Describe what the next process needs at the exact point where responsibility transfers.
Orientation and datum
Define every axis, face, feature, pitch, height, location tolerance and stability condition required downstream.
Demand profile
Include machine cycle, bursts, micro-stops, planned pauses, recipe changes and restart behaviour.
Buffer requirement
Define useful accumulation time, first-in/first-out needs, allowable queue pressure and empty/full responses.
Quality checks
List features that must be present or correct, reject destinations, confirmation and any production data required.
Receiving interface
Record physical envelope, datum, ownership, existing drawings, available access and permitted machine modifications.
CHECKLIST 03
Integration, operation and lifecycle.
These requirements turn separate equipment into a usable production system.
Bulk loading
State container size, batch weight, loading frequency, operator reach, lift assistance and low-level warning needs.
Controls boundary
Define PLC and HMI standards, I/O or network handshakes, recipe ownership, alarms, data and remote support policy.
Safety and guarding
Record required standards, risk-assessment responsibilities, stops, interlocks, reset zones and safe recovery access.
Changeover
Set the expected frequency, target method, tooling storage, recipe control, verification and acceptable duration.
Maintenance access
Protect cleaning, inspection, adjustment, jam clearance, tooling replacement and planned maintenance routes.
Documentation and support
List manuals, drawings, software backups, spares, training, warranty, response and final record requirements.
ACCEPTANCE PLAN
Make proof measurable before an order is placed.
A signed test route prevents “works” from meaning different things to different parties.
| Stage | Define in advance | Example evidence |
|---|---|---|
| Feasibility or development trial | Sample mix, duration, orientation, rate and visible failure modes | Trial record, observations, concept recommendation and open risks |
| Factory acceptance test | Complete scope present, test population, operating states, output, quality and intervention limits | Timed results, reject checks, alarm/recovery demonstration and action list |
| Installation readiness | Utilities, foundations, access, lifting, networks, isolations and receiving-machine status | Signed readiness checklist and interface drawings |
| Site acceptance | Integrated production period, product mix, output, quality, changeover and training | Agreed results, documented exceptions and handover record |
Acceptance values must be tailored to the actual project; the examples above are planning prompts, not contractual criteria.
COMMON QUESTIONS
Specification checklist answers.
A requirement can remain technology-neutral while still being technically precise.
What should a parts feeding system specification include?+
It should define the complete component family, sample condition, sustained accepted output, exact hand-off, allowable damage, inspection, buffering, controls, guarding, operator access, changeovers, FAT, documentation, installation and site acceptance responsibilities.
How many component samples are needed for feeder trials?+
The quantity depends on the feed rate, test duration, recirculation limits and natural variation. Samples should represent normal production and difficult but acceptable parts, not only ideal examples.
Should a specification state feeder technology?+
Usually it is better to state the required result, constraints and acceptance evidence unless a technology is mandated for a documented reason. This leaves room to select the most suitable complete architecture.
What is the correct feeder rate to specify?+
Specify sustained accepted components at the agreed hand-off under representative operating conditions, including normal rejects, replenishment and recovery, rather than a short peak inside the feeder.
REQUIREMENT REVIEW
Turn your checklist into a testable complete-system scope.
Send drawings, representative components, output, hand-off and existing-line information for an initial engineering conversation.