Accepted output
Packs that pass the agreed finished-pack checks within the defined run period. Exclude setup, rejected, held or uninspected packs.
Production evidence
What should a trigger capping production run log record?
Link bottle and closure lots, machine settings, line states, interventions, rejects and finished-pack checks so trigger capping performance can be repeated and investigated.
Answer first
A useful run log records conditions, events and accepted finished packs
A trigger capping production run log should identify the format and component lots, approved settings revision, operator role, start and finish times, line states, replenishment, adjustments, faults, rejects, inspections and recovery actions. It should distinguish accepted output from machine cycles and make the affected-pack window traceable after any intervention.
The record may combine automatic control data with manual entries. Sensors and PLC events can show machine states, but they cannot know whether a closure lot changed, why an operator adjusted a guide or which retained sample passed quality inspection. Use consistent names across production, quality, maintenance and technical support.
- Record the observed result before assigning a cause.
- Separate normal running, starved, blocked, planned-stop and fault time.
- Link changes and interventions with first-off approval.
- Identify component lots and the time they entered the process.
- Retain enough context to reconstruct the affected-pack window.
Core fields
Record the pack, machine state and quality result together
| Record group | Fields to define | Why it is needed |
|---|---|---|
| Run identity | Date/time, order or batch reference, line/machine identity, shift and responsible role. | Creates a traceable production boundary. |
| Format and components | Bottle, neck finish, trigger closure, dip tube, supplier/revision and lot identities. | Links performance with the physical pack and component changes. |
| Settings and tooling | Approved recipe/settings revision, change parts, guide/head positions and authorised adjustments. | Shows which controlled configuration produced the result. |
| Line states | Running, starved, blocked, planned stop, fault, recovery, changeover and inspection time. | Separates capper performance from external line conditions. |
| Counts | Accepted packs, rejected packs by observed category, held packs and setup samples. | Prevents mechanical cycles or discharged bottles being reported as accepted output. |
| Quality checks | Tube entry, thread, cap height, approved torque/functional result, appearance and orientation. | Connects production quantity with the finished-pack decision. |
| Events and interventions | Replenishment, jam, fault, cleaning, adjustment, maintenance, reset and first-off release. | Defines what changed and which packs may require containment. |
| Close-out | Retained samples, unresolved actions, material disposition and handover to next shift or function. | Prevents open risks being lost when the run ends. |
State and count definitions
Agree what each number means before using it
Mechanical cycles
Machine actions or indexing events. These may be useful for diagnosis but do not prove that a conforming pack was produced.
Starved time
The capper cannot run because bottles, closures or another required input are unavailable at the defined point.
Blocked time
The capper cannot discharge because downstream equipment or accumulation is unable to accept more packs.
Fault and recovery time
Time from a defined fault state through safe clearance, inspection, reset and first approved pack after restart.
Planned stop time
Agreed non-fault activity such as changeover, scheduled inspection, cleaning or normal replenishment where classified separately.
Affected packs
Use time, position and inspection to define the hold window
After a jam, setting change or component issue, identify the last accepted check, first known defect, packs in the machine and conveyors, downstream buffer and first approved pack after recovery. The site’s quality system should define hold, recheck and disposition; the run log should provide the evidence needed to apply it.
Record the event time and line state
Capture automatic fault information where available and the operator’s observed sequence.
Identify material in process
Include bottles and closures in feeders, transfer paths, capper stations, conveyors and downstream accumulation.
Contain and inspect
Use the agreed defect and finished-pack checks. Retain representative accepted and affected samples.
Approve the restart
Record the action, settings revision and first-off result before normal acceptance resumes.
Close the event
Document disposition, unresolved actions and any extra monitoring for the next production period.
Buyer questions
Questions about trigger capping run records
Why record the trigger closure lot in the run log?
Closure-lot identity helps show whether a change in feeding, tube behaviour, thread engagement or appearance followed a component change. It also supports a narrower affected-pack review and a more useful discussion with the component supplier.
Should every short stop be logged?
Define a practical rule based on the line’s control and quality needs. Automatic state data may capture frequent short stops, while manual entries should focus on events requiring intervention, adjustment, containment or first-off approval. The categories must be consistent enough to explain lost output and risk.
What is accepted trigger capping output?
Accepted output is the number of packs that pass the agreed checks during the defined production period. It is not the machine’s theoretical cycle rate and should exclude rejected, held, setup or uninspected packs. Record starved, blocked and fault time separately.
How should trigger capper settings be recorded?
Use an approved recipe or settings revision where possible, supported by the tooling and format identity. Record authorised changes with time, reason, person or role and first-off result. Avoid relying only on photographs of unlabelled screens or handwritten numbers without context.
What should be recorded after a trigger capper jam?
Record the fault sequence, component and pack position, suspected obstruction, safe clearance, parts removed, transfer-path inspection, settings changed, affected-pack decision and first approved pack after restart. Keep the observed result separate from the final diagnosed cause.
Who should review a trigger capping run log?
The site should assign roles appropriate to its operation. Operators may complete routine entries, quality staff review pack results and disposition, maintenance reviews equipment events, and production or engineering reviews trends. The machine supplier can use the same evidence when technical support is needed.
Use this with the controls and sensors guide, quality inspection plan and incoming component checks.
Define the evidence your trigger capping line should retain
Share the required formats, quality checks, line states, controls and reporting needs when discussing the machinery scope.
Performance analysis
Turn run records into explainable OEE evidence
Retain the raw planned time, stop duration, cycle/pack counts, accepted packs, rework and rejects. The OEE result should be traceable back to these records and the agreed cell boundary.
| Run-log field | Why it matters |
|---|---|
| Planned production time | Defines the denominator and separates planned cleaning, changeover, breaks or maintenance. |
| Stop start/end and reason | Supports availability and loss analysis by feeder, capper, inspection or connected line stage. |
| Supported ideal rate | Provides the performance reference for the actual format and accepted-quality condition. |
| Accepted, held, reworked and rejected packs | Prevents quality loss being hidden inside total cycle count. |
| Component lots and format | Allows performance shifts to be compared with bottle, trigger and dip-tube changes. |
Use the trigger capper OEE and downtime guide for definitions and loss categories.