How it works

What it simulates

A bioreactor suite: the reactor, its media charge and harvest vessels, the temperature control unit and the cleanroom around them. Five units, 94 tags, over Modbus TCP, running ISA-88 phases from charge to harvest.

Everything is recorded against the batch rather than against the clock, so a deviation belongs to a phase and a parameter, not to a timestamp somebody has to reconcile later.

• ISA-88 phase state, step and elapsed time
• critical process parameters against their recipe bands
• cleanroom differential pressure and particle counts

What it configures on Litmus Edge

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

• 5 DeviceHub devices on the Modbus TCP driver, 94 tags
• 5 Digital Twin models, one instance each
• 5 multi-input Analytics groups: batch execution, CPP deviations, batch release, batch yield, environmental monitoring

Scenarios you can inject

• A pH or dissolved oxygen control fault takes a critical process parameter out of its band for long enough to matter, and the batch becomes one that cannot be released
• A temperature control unit losing cooling drives the reactor above its band during the phase where it counts
• A cleanroom pressure loss raises an environmental deviation against the batch that was running at the time