An inspection rewinder can reach its set speed and still hold up the finishing department. The missing production is often outside the steady run: the job waits for a defect map, knives are positioned again, a splice takes too long, finished rolls are removed slowly or the operator cannot release the roll without another check. Before comparing a faster machine, divide the lost time into named steps. The largest loss may have little to do with maximum web speed.
Start with one shift of event times, not one average speed
Record the planned start, material arrival, first web movement, first accepted roll and final accepted roll for every job on one inspection slitter rewinder. Between those points, mark setup, web threading, knife positioning, camera setup, defect repair, roll change, sample approval, cleaning, maintenance and waiting. Use a simple reason code and let the operator add a short note when the code does not explain the stop.
Keep run speed and productive time separate. A machine may run at the expected speed for twenty minutes and then wait fifteen minutes for a new core, a missing inspection file or a decision on whether a marked defect is acceptable. The shift average will look poor, but increasing the set speed will not remove that wait. It may instead produce finished rolls faster than they can be checked, removed and labelled.
NIST describes overall equipment effectiveness as availability multiplied by performance and quality. That distinction is useful here even if the plant does not calculate a formal OEE figure. Availability asks whether the rewinder was ready to run, performance asks how it ran during operating time, and quality asks how much output passed the defined requirement. Keep those questions separate so that one number does not hide three different problems.
Split changeover at the first accepted finished roll
Measure changeover from the last accepted roll of the previous job to the first accepted roll of the next job. Then divide it into tasks: removing finished rolls, clearing cores and trim, loading the parent roll, threading, entering the job, setting guides, positioning knives, loading the defect file, setting the counter and approving the first roll. This shows whether the delay comes from the machine, the work instruction, material staging or the release procedure.
Do not count the first moving web as the end of setup. If the operator still needs to correct slit width, tension, count or camera settings, the job is not yet producing saleable rolls. Record the material consumed before acceptance as setup waste. A faster acceleration or automatic knife positioner has value only when the surrounding steps are ready to use it.
PRATI describes current SATURN configurations with inspection, slitting and rewinding functions, while SATURN Next adds automatic setup, defect positioning, cutting, waste editing and splicing in its advanced configuration. These functions address particular tasks. The plant still needs its own time study to decide which task is limiting output and which level of automation is justified for the actual job mix.
Treat defect repair as a production route of its own
A roll with no marked defect follows a different route from a roll that must stop, reverse, locate the fault, remove material, splice and return to running direction. Record the number of defect interventions, the time per intervention and the metres removed. Also record false alarms and defects that cannot be located at the expected position. That evidence separates inspection-system performance from the mechanics of cutting and splicing.
If the camera creates a defect map on the press or inspection system, check how the rewinder receives and interprets that data. A file that is late, named incorrectly or tied to the wrong roll creates a waiting loss before the first splice. A position that drifts during the roll creates repeated searching. Verify roll identity, reference position, web direction and the operator's release rule before blaming the rewinder.
Where defect rejection and splicing are automated, define the acceptance rule before enabling the sequence. Some marks require removal, some require review and some are process artefacts that should not stop the job. Automation can reduce manual intervention, but it cannot correct an unclear defect standard. Keep an accepted and failed sample with the job so that the decision is consistent across operators and shifts.
Specify the improvement from the loss register
After several comparable jobs, rank the losses by minutes and frequency. If knife setup dominates, investigate repeatable slit plans, verified knife references and automatic positioning. If defect repair dominates, examine defect-map accuracy, web reversal, splice method and automated waste editing. If roll handling dominates, review shaft, core, roll-removal and labelling arrangements. If waiting dominates, correct material staging and job data before changing machinery.
Compare alternatives using the same job family: substrate and liner, parent-roll width and diameter, number of lanes, finished-roll diameter, run length, normal defect count, splice rule, inspection requirement and release evidence. A pharmaceutical label, a clear-on-clear cosmetic label and a plain logistics label may use the same rewinder but impose very different checks and intervention times. One headline speed cannot describe all three.
Run a controlled trial and compare first accepted roll time, productive running time, intervention time, setup waste, accepted output and operator actions. ISO 22400 provides an industry-neutral framework for defining and using manufacturing KPIs; the practical point is to define each measure before comparing results. For a Royal Coat review, send the job mix, web and roll dimensions, slit plan, defect workflow, current time study and the output required per shift.
Questions from production and purchasing teams
What to ask about inspection rewinder productivity diagnosis
Why is the inspection rewinder slow when its running speed is correct?
The loss may sit in setup, waiting, defect repair, splicing, roll removal, labelling or release rather than steady running speed. Time those steps separately.
When should changeover time end?
End it at the first accepted finished roll, not when the web first moves. Corrections and waste before acceptance still belong to changeover.
What should be recorded for each defect intervention?
Record the defect type, position accuracy, search time, material removed, splice time, false alarms and whether the repaired roll passed release.
Will a higher maximum speed fix a finishing bottleneck?
Only when productive running speed is the main loss. It will not correct missing job data, long setup, repeated defect searches or slow roll handling.
What information is needed to specify inspection-rewinder automation?
Provide substrate and liner, web width, slit plan, roll dimensions, job lengths, defect frequency, inspection standard, splice rule, current time study and required shift output.