BeedyThe plant is running. Every module reads from it.
A generic 300 m³/d membrane bioreactor, simulated on our server-side ASM1 engine and running around the clock. Upsets happen on their own, like they do on a real site. Open a module to see it working on live data.
Meet OTIS, your plant's AI operator
He lives in every module. He reads the same plant you do, tells you what matters on each page, and answers from the plant's real data.
- Watches
- Every signal and every crew note, and shows what moved first when something goes wrong.
- Guides
- What needs a decision, who acts next, and the one click to do it.
- Advises
- He never decides. The PLC keeps its interlocks and a person always clicks.
Modules
Each module is licensed on its own and runs on the same plant model. Plants usually start with operations and add intelligence once the data has earned trust.
A new plant is configuration
Assets are described once against a template library. The modules don't change when the plant does.
Computation stays on the server
Process engine, equipment signals and root-cause analysis run server-side. The browser only displays results.
OTIS is never in the safety loop
The PLC keeps its interlocks. OTIS observes, advises, and only operates through a vetted gateway with a heartbeat.