A camera can find a print defect, but the finished roll is not automatically ready for release. The converter still has to locate the affected section, remove or correct it, make a controlled splice, confirm the count and prove that the repaired area was checked again. A bidirectional inspection rewinder is useful when that return-and-verify sequence is part of the approved job procedure. Start with the release evidence, not the machine description.
Write the defect-handling sequence before selecting the machine
List what happens when the inspection system flags a defect. Identify who accepts the alarm, how the machine returns to the affected repeat, where the operator cuts the web, how many labels are removed and how the splice is made. State whether the corrected area must pass the camera again before it can enter the finished roll.
Separate defects that require removal from warnings that need review. A missing character, unreadable code, colour variation, contamination and splice can have different acceptance rules. The inspection system needs a maintained defect master, but the rewinder workflow also needs a clear disposition for each alarm class.
Record the required proof. This may include an inspection report, removed-label count, splice count, start and end counter readings, back-number sequence and an approved roll label. If production cannot define the evidence, the equipment supplier cannot confirm which inspection and re-inspection functions are necessary.
Use bidirectional travel when the web must return and be verified
A conventional inspection rewinder can stop at a recorded defect position, but the correction method may still depend on manual web handling and a separate verification step. Bidirectional travel becomes relevant when the approved process requires the web to move back to the fault and then pass through inspection again after correction.
PRATI describes SATURN Bidi as a bidirectional inspection rewinder with inspection and re-inspection functions. Its listed operations include print-quality inspection, back numbering with related inspection, counting, slitting and rewinding. Those functions should be matched to the job rather than treated as a standard package for every label roll.
Define the distance and web path involved in returning to a defect. Check whether labels can be damaged, marked or delaminated during repeated travel, especially with booklet constructions, clear-on-clear materials or sensitive surfaces. Trial the actual construction and normal roll diameter, not only a short paper sample.
Separate normal production from secure finishing
Not every roll needs the same level of control. A standard commercial label may require inspection, editing and a final report. A pharmaceutical, security or sequentially numbered job may require all security devices to be enabled, a controlled web path, verified quantity and a documented re-inspection after every intervention.
PRATI states that SATURN Bidi has FAST MODE for standard processing and SAFE MODE for failsafe, certified finishing. It also says SAFE MODE begins processing only when the integrated security systems are enabled. During specification, ask which sensors, counters, inspection functions and interlocks are included in the proposed configuration and how their status appears in the job record.
Do not rely on a mode name as the quality procedure. The converter must define access rights, alarm acknowledgement, reconciliation of removed labels, splice approval, data retention and final release authority. The machine can enforce parts of the sequence, but the plant still owns the acceptance criteria and records.
Reconcile numbering, quantity and splices together
A visually clean roll can still fail if the quantity is wrong or a number is missing, duplicated or out of sequence. Map every point where counts can change: leader removal, defect editing, splice preparation, sample removal, slitting and final roll separation. Decide which counter is the release counter and how it is checked.
For back-numbered work, specify the number format, position, reading direction, acceptable sequence and action for an unreadable or duplicate number. Confirm whether the camera reads the number itself or only verifies print presence. The answer changes the inspection task and the evidence available after rewinding.
Give each splice a reason and traceable position. If labels are removed, record the quantity before the web is joined. A final roll report should reconcile the input quantity, approved removals, samples, waste, splice count and delivered quantity. Test that report during acceptance with planned faults and operator interventions.
Check the web path between jobs
Short remnants from the previous job create a serious control problem when constructions, artwork or sequential data change. Define how the machine is cleared, how the empty path is confirmed and who signs the line-clearance record. The procedure should cover the unwind, inspection area, buffers or loops, slitting section, splice table and rewind shafts.
PRATI says SATURN Bidi uses a purge liner to clean the web path between jobs and links this function to pharmaceutical requirements. Confirm the exact purge procedure, the material required, the areas it covers and the record produced by the proposed machine. Do not assume that one automatic cycle replaces the plant's full line-clearance check.
Run a changeover trial from one distinct job to another. Use clearly different artwork or numbered material, complete the normal cleaning and purge procedure, then inspect the next job and all removed waste. The acceptance test should prove that the previous web cannot remain hidden in the machine or enter the next finished roll.
Test the complete release workflow with production rolls
Prepare a trial plan with known, documented faults. Include a print defect, a counting intervention, a splice and a job change. Confirm that the system detects the intended fault, returns to the correct position, supports the approved correction and re-inspects the repaired section without losing the quantity record.
Use the intended self-adhesive paper, filmic, clear-on-clear or booklet-label construction and the planned slit pattern. Record web tension, roll build, rewind direction, core size and finished-roll diameter. Inspection accuracy alone is not enough if repeated travel damages the construction or the finished rolls cannot be released in the required format.
Royal Coat represents PRATI inspection, slitting and rewinding technology across India, Bangladesh, Sri Lanka, Nigeria and Kenya. For a bidirectional-inspection review, send the Royal Coat team the label construction, web width, roll diameters, defect classes, inspection standard, numbering and count rules, splice procedure, line-clearance requirement, finished-roll format and the records needed for release.
Questions from production and purchasing teams
What to ask about bidirectional label inspection
Does every 100% inspected label job need bidirectional rewinding?
No. It is most relevant when the approved process requires the web to return to a defect and the corrected section to pass through inspection again.
What is the difference between inspection and re-inspection?
Inspection finds and records the original defect. Re-inspection checks the edited or corrected web again before it is accepted into the finished roll.
Should counting be checked separately from print quality?
Yes. A roll can pass visual inspection and still contain the wrong quantity or a missing or duplicate number after labels are removed.
Why is web-path clearance important between jobs?
Material from the previous job can enter the next roll or invalidate quantity and traceability. Define a purge and physical line-clearance check for every relevant area.
What should be included in a bidirectional inspection trial?
Use production material and planned faults to test detection, reverse positioning, correction, re-inspection, counting, splicing, slitting, roll build and the final release report.