The control panel for the whole set: start any solution, connect a Litmus Edge once, and provision or remove each one from its card.
A control panel that runs the industry solutions rather than being one of them. It starts and stops each solution, connects to a Litmus Edge once rather than once per solution, and provisions or removes each one from its own card with a preview before anything is written.
It runs each solution from its published image, so no source checkout is needed. It can also ask the connected Edge to pull and run a solution itself, through the Edge Applications API and the registry credentials the device already holds, which puts the simulator on the Edge own network and removes the reachability question entirely.
It lists the Litmus solutions catalogue joined against the container registries this machine can read, so what is published and what is actually runnable here are one view rather than two.
Serves on port 4009. It needs access to the host Docker socket, because the solutions run as sibling containers so their ports land on the host.
A six-machine bottling line, simulated end to end, that configures Litmus Edge itself and turns filler giveaway, CIP verification and downtime into money.
Five ISA-88 bioreactors where the batch record is the product: every critical process parameter deviation, and whether the batch can be released.
Nine lift stations and a treatment works on DNP3, deliberately split across two Litmus Edges managed from one Litmus Edge Manager.
