URS checklist

What should a cap feeder URS include?

A useful cap feeder user requirement specification defines the closure, outlet condition, capper interface, controls, changeover expectation and acceptance evidence before the feeder is ordered.

Request cap feeder advice Call 01494 623015

Build the answer around the real closure and line.

Send representative caps, bottles, photos, available space, capper details and target output so Lancing can test the practical route instead of guessing from a generic feeder description.

Send project details

Direct answer

A cap feeder URS should define the required outcome, not just a machine name.

A user requirement specification for a cap feeder should state what closure is being handled, how it should leave the feeding system, how the downstream capper receives it, how operators refill and recover the route, and how the installation will be accepted. It should avoid assuming that a bowl, sorter or elevator is correct before sample evidence is reviewed.

The strongest URS describes the cap path from bulk loading to capper handover. It should include any known problems such as bridging, nesting, scuffing, dip-tube tangling, cap-low stoppages, rejected caps, poor handover or manual placement errors.

URS contents

Use the URS to remove ambiguity before quotation.

The table is qualitative because the final figures depend on the closure, capping machine and line layout.

URS area	What to define	Why it matters
Closure and bottle	Cap type, material, dimensions, liner, tamper band, decoration, bottle neck finish and production variation.	Feeding behaviour depends on real geometry, finish and balance rather than catalogue diameter alone.
Required presentation	Accepted exit orientation, pick point, chute entry, open or closed side, leading feature and rejection boundary.	The feeder can only be accepted if the required outlet condition is measurable.
Line and capper interface	Existing capper, handover height, chute angle, starwheel, chuck, spindle, placement head or manual assisted point.	The best feeder route can fail if it does not match the way the capper takes the closure.
Controls and stops	Cap-in-chute, cap-low, fault, demand, pause, restart and operator messages.	Controls prevent the feeder from starving, flooding or restarting unpredictably.
Changeover and access	Formats to run, change parts, settings, cleaning needs, reject bins, guards and safe access.	Operators need a route that can be used repeatedly, not only a one-off demonstration.
Acceptance evidence	FAT/SAT checks, sample range, line stop/restart, reject handling and first production verification.	Acceptance criteria make the project testable without inventing unsupported headline performance figures.

Buyer questions

Questions a good URS should answer.

Should the URS name the feeder type?

Only if the feeder type has already been justified by samples or previous production experience. It is usually safer to state the required cap presentation and let the supplier confirm whether a bowl, elevator, sorter, presenter or combined system is the best route.

Should the URS include an output target?

Yes, but the target should be described as the production demand the line must support, not a guaranteed feeder figure. Confirmed output depends on closure behaviour, refill method, buffer, chute design and downstream capper performance.

How should future cap formats be handled?

List any likely future caps separately from the immediate production cap. The useful question is whether the same route can support them with settings or change parts, or whether their geometry creates a different feeding problem.

Why does the responsibility boundary matter?

The URS should state who supplies the feeder, chute, cap release, capper interface, guards, sensors and controls. Clear boundaries reduce commissioning risk and avoid gaps between the feeder supplier and the capper supplier.

Send URS details Open specification guide

Related guidance

Continue from the URS to testable evidence.

Design review checklistCheck layout, access and handover before build.Trial planningPlan samples and evidence before ordering.Controls and I/ODefine the signals between feeder and capper.