05 Features
Scripts and calculations
The efficiency that matters in your plant is almost never one of the packaged formulas. It usually combines readings from different instruments.
Illustrative figures.
How it works
The calculation declares what it needs
Every plant has one number that decides whether the day went well. It is almost never one of the numbers the instrument portal puts on its front page, because that number combines readings from different instruments.
The computation declares what it needs
Inputs, parameters and outputs are declared alongside the code. The system resolves the inputs and hands them over: the computation opens no connection, holds no credential and never reaches the network.
It runs on windows, not on a timer
Work is scheduled against the time windows it has to cover. If data arrives late the window is recomputed, instead of staying wrong forever.
It is tried on history before it goes live
The same formula runs over years already recorded without writing anything, and can run in shadow beside the active version with the differences compared.
The result is a measurement like any other
It is kept beside the raw data, with the version of the computation that produced it. It feeds charts, thresholds and notifications exactly as a field reading does.
What comes out
What comes out
A calculation's result is kept like any other measurement, together with the version of the formula that produced it.
No connection opened by the calculationWhere it is used
In every industry, no exceptions
The protocol changes, the way of working does not. It is why the same measurement layer sits under plants that have nothing in common.
Nearby features
The step before and the step after
Which number
decides your day?
Tell us about the formula that lives in a spreadsheet today: we will say what it takes to run it on the real data.