Bottling line

a 500 ml pet bottling line as five machines in sequence filler, capper, labeller, checkweigher and case packer, with the accumulation buffers between them six devices and 94 tags over modbus tcp operator view on 4010 , modbus tcp on 5020 what it demonstrates product giveaway the filler drifts high, every bottle goes out with a little more product than it was sold with, and the checkweigher sees it before anyone counts the stock the cost is continuous rather than an event cip verification a clean in place cycle is judged against the recipe it was supposed to follow, not against whether it finished a wash that ran below temperature is a wash that did not happen downtime root cause when the line stops, the machine that stopped is rarely the machine that caused it the buffers between machines are what tell you which one to fix what it puts on litmus edge six devicehub devices, one per machine plus the cip skid, with 94 tags between them a digital twin model and instance for each machine analytics groups behind the giveaway, cip and downtime figures on the operator view deploy services bottling line image us docker pkg dev/litmus customer facing/litmus solutions/bottling line demo 0 1 0 container name bottling line demo restart unless stopped ports \ target 4010 published 4010 protocol tcp \ target 5020 published 5020 protocol tcp environment \# fill these in edge url "${edge url }" edge api token "${edge api token }" sim host "${sim host auto}" apply on start "${apply on start 1}" edge verify tls "${edge verify tls 0}" http port "4010" modbus port "5020" autostart "1" tick seconds "0 2" seed "7" log level "info" put the three values in a env beside the compose file edge url=https //10 0 0 5 edge api token=your token sim host=10 0 0 9 docker compose up d open http //localhost 4010 the edge is configured within about a minute and the page fills in configuration variable default what it does edge url the docker host litmus edge to configure edge api token unset token for that edge or a username and password, or a client id and secret sim host auto address the edge polls to reach this solution apply on start 1 configure the edge on startup edge verify tls 0 1 checks the edge's certificate autostart 1 start the line running tick seconds 0 2 simulation step seed 7 makes a run repeatable what you see the operator view shows the five machines with their live tags, the bottles moving between them, and the accumulation buffers filling and draining above them are the kpis the analytics groups produce below the line are the faults turn one on and watch it work through the line filler mean drifts high, so giveaway climbs capper jams and holds, cascading back up the line labeller micro stops repeatedly product tank runs low and the filler starves caustic wash runs below temperature the page holds until litmus edge is verified to be carrying the solution's devices, so what you are looking at is always backed by a real edge removing it docker compose down to remove what it created on the edge, use clean up in the solutions provisioner # , or call the solution's own clean endpoint it removes only the six devices, twin models and instances this solution created support support\@litmus io mailto\ support\@litmus io