1. Allocate ownership
For each boundary, identify which machine creates the condition, which receives it, which action follows and which party supplies the hardware, wiring and software.
Automatic bottle-line integration
Bottle capping line controls and interlocks.
Define how the capper, cap feeder, conveyors, inspection and surrounding machines exchange state information and recover from normal production disturbances.
Define the evidenceRecord the conditions, responsibilities and approved result before final machinery configuration.
Use production-intent samplesConfirm suitability with the actual bottle, closure and line context.
Carry results into acceptanceUse the same definitions through quotation, trial, FAT, SAT and handover.
Answer first
A control specification should describe machine states and responsibility at each interface, not only a list of electrical signals.
The purpose is to make the line predictable. When bottles stop arriving, downstream capacity disappears, caps run low or a reject station becomes unavailable, the equipment should move to an agreed state and restart through a known sequence. The exact design depends on the selected machinery and site risk assessment, but the functional questions can be defined before detailed engineering.
| State or event | Questions to agree | Acceptance evidence |
|---|---|---|
| Ready and permissive | Which conditions must be true before the capper may accept a bottle? Which machine owns the line-start command and which devices can withhold permission? | State display and a demonstrated refusal to start when an agreed permissive is absent. |
| Starved | How does the capper respond when upstream bottle supply falls below the required condition? Are bottles already in the machine completed, retained or rejected? | Controlled run-down and restart without an incorrectly spaced or uncapped first bottle. |
| Blocked | Where can finished bottles wait safely? What signal is sent when downstream equipment cannot accept more bottles? | No uncontrolled pressure, instability, scuffing or loss of reject traceability during the agreed block. |
| Cap low, no cap or feeder fault | Is the response a warning, controlled stop, run-down or reject? How are bottles between detection and application handled? | Normal replenishment, low-level operation and recovery without unchecked uncapped bottles. |
| No bottle, mispositioned bottle or incomplete cap placement | Which sensors prevent the closing cycle, which pack is rejected and how is the sequence reset? | Representative conditions are detected and the affected bottle follows the agreed disposition. |
| Inspection or reject unavailable | Can the line continue, does it stop, and who may reset a full reject container or inspection fault? | Alarm, stop and reset permissions demonstrated with the reject boundary visible. |
| Recoverable fault | Which faults may be cleared through normal controls and which require isolation or maintenance intervention? | One or more agreed fault-recovery sequences performed using the documented operator method. |
| Emergency stop and guarding | What is the defined machine boundary, how is stored energy controlled and what conditions are required before reset and restart? | Site-appropriate safety validation and restart behaviour; this must follow the final design and competent risk assessment. |
Build the functional sequence
Write the line story from bottle release to accepted outfeed.
2. Define pack tracking
State how the line knows which bottle may be affected by a missing cap, incomplete cycle, inspection failure or stopped transfer, and where that bottle goes.
3. Define recovery
Describe the operator actions, reset permissions, retained bottles, rejected bottles and first accepted pack after the fault is cleared.
4. Connect to physical flow
Match state signals to the actual accumulation available before and after the capper. A control delay cannot create physical buffer space that the layout does not contain.
FAT and SAT evidence
Test the interface conditions that are available at each stage and record the site-dependent items.
Factory testing may use simulated signals or connected project equipment. The record should identify the source of every simulated state, the response observed, any timing or setting used and the interface still to be proven with the final upstream or downstream machine. Site acceptance should repeat the relevant sequence with the installed conveyors, guards, utilities, product and operators.
| Test record field | Information to capture |
|---|---|
| Initial state | Machine mode, bottles and caps present, buffer level, guards, inspection and reject availability. |
| Event applied | The exact state or fault, where it was introduced and whether the signal was real or simulated. |
| Expected response | Which equipment should stop, continue, complete a cycle, reject a pack, alarm or withhold restart. |
| Observed result | Machine sequence, affected bottles, operator action, alarms, rejects and time or conditions to stable recovery where relevant. |
| Open boundary | Any final-site signal, safety function, network, upstream/downstream behaviour or product condition not available at the factory. |
Use this guide with the buffering and accumulation guide, accepted-output validation and the existing FAT and SAT checklist. Safety-related controls must be designed and validated for the final machine and installation by competent parties; this page is a project-definition aid, not a substitute for that work.