How it works

What it simulates

A bottling line: filler, capper, labeller, checkweigher, case packer and the CIP skid that cleans them. Six machines, 94 tags, over Modbus TCP.

Every machine reports PackML state, its own counters and its own reason codes, so the line reads the way a real one does: the machine that stopped is rarely the machine that caused it, and the buffers between them are what say which is which.

• machine states, counts and reason codes per station
• fill weights bottle by bottle at the checkweigher
• CIP phases, temperatures and conductivity against the recipe

What it configures on Litmus Edge

On startup, and it removes exactly what it created when you are finished:

• 6 DeviceHub devices on the Modbus TCP driver, 94 tags
• 6 Digital Twin models, one instance each
• 4 multi-input Analytics groups: giveaway, weight check, CIP verification, downtime

Scenarios you can inject

• A filler drifting high sends every bottle out with more product than it was sold with, and the checkweigher sees it long before anyone counts the stock
• A CIP cycle that ran without cleaning finishes normally but misses the recipe's temperature and contact time, which is the difference between a wash and a verified clean
• A capper jam and labeller microstops stop the line at a machine that is not the cause, and the buffer levels name the one that is