Blog
Field notes from the platform
Engineering notes on equipment models, simulation, operator screens and advisory AI. Read the decisions and workshop findings behind the platform.
QME 2026, wrapped: real water, local inference, three days of hard questions
Our QME stand combined a water filtration rig, simulation and advisory inference on local hardware. What we demonstrated, what visitors asked and where the work goes next.
Consystence is in public beta
The July 2026 public-beta launch: individual sandboxes, team access and the QME demonstration. A record of what was available at launch, with links to current access options.
Where the standard library goes next: water, gas, and data centres
The standard library covers 29 device types across four families. Water utilities, gas and data-centre libraries are planned next, shaped by the equipment beta users need.
Bad data must never look live
Old and faulty readings need different treatment. How quality states affect operator screens, historian storage and command preconditions, and why quality is separate from data provenance.
Dead chain, idle plant, or frozen PLC? Teaching the platform to tell
A quiet process, a lost link and a stopped controller can look alike. How controller heartbeats help the platform distinguish them and give operators useful evidence.
C#, not Structured Text: retargeting the PLCnext generator
Why the PLCnext generator moved from Structured Text to the C# runtime used by the simulator, and what the change meant for shared control behavior across targets.
Sign in when the internet will not: identity that survives the link dropping
Site operators need to sign in when the cloud link drops. How local operator identity, cloud sign-in and machine credentials keep their responsibilities separate.
Generated, not written: deterministic PLC code from the device model
How deterministic code generation connects equipment definitions to controller programs, screens and history, with shared conformance tests to keep target behavior aligned. Includes dated implementation updates.
One device model, many PLC vendors
How a shared equipment model connects to different controller brands through drivers. The integration boundaries, workshop evidence and remaining field-validation work behind that approach.
Edge-first: why a site keeps running when the link to the cloud drops
How site-local screens, operator identity and buffered data support operation through cloud outages. The architecture, its storage limits and the distinction between workshop evidence and field experience.
One semantic UI tree, many renderers
How the browser and CLI render a shared description of the operator interface, and how that architecture developed. Includes dated updates on the browser migration.
Advisory by design: why our AI explains the plant but never controls it
Why Consystence AI can explain plant state and recommend actions but cannot command equipment. The architectural boundary between advisory reasoning, operator decisions and deterministic controller logic.