Data & Security
Where Your Data Lives
There is no agent on your control network, no OPC connection, and no requirement to move your historian into a vendor-operated service. A diagnosis is produced without a single outbound call.
The engine reads a history file. Starting a pilot needs no firewall change, no OPC server and no read access to the control network — which is usually the difference between a project that starts this quarter and one that starts next year.
The reference model, the 54 indicators, the fault signatures and the consequence costing all run in one process against local files. No plant data leaves the deployment for a diagnosis to be produced.
qemIntel calls a language model. It sends the retrieved knowledge cards and the values on your current screen — roughly two thousand tokens — never the history file. The provider is an environment setting rather than code, so it can be swapped, or pointed at a model you host.
The calibration, the fault library and the causal map describe your unit. There is no per-tag licence and no lock-in that makes leaving expensive.
What we do not claim
More on how it works
The platform runs on a real amine train with thirteen days of one-minute history behind it. Open a diagnosis and read the evidence for yourself.
Open the platform