Set up once, use on every machine.

Some calculations look correct but are not — for example when very fast sensor data is fed into a step that expects one value per interval. The result is not an error message but a believable wrong number. Toleron refuses such a setup while it is being built and says what is missing.

Every released calculation step stays fixed. An improvement becomes a new version; what is running keeps working exactly as before.

An evaluation is described once in machine-neutral terms — for example “the spindle load”. For each machine you assign once which of its values that is, with live values shown while you assign.

After that, every dashboard, report and evaluation works for that machine. A new controller brand needs an assignment, not programming.

• Preview runs a new evaluation on your real history while you are still editing it. Gaps in the data stay visible as gaps.
• Recalculating the past can be paused and resumed, and what was already calculated is kept.
• Going live follows fixed steps: a new evaluation first runs in a test phase in the background, without affecting your dashboards, and can only go live after an observation period. Rolling back is always possible.
• Nothing in use disappears by accident: Toleron refuses to delete a value that a running evaluation still produces.

Toleron derives production figures the same way on every machine: machine state (from the controller or from a retrofitted sensor), shift calendars with breaks, night shifts and holidays, part counting with traceable corrections, job detection from program changes, downtime with automatic rules and bulk manual classification, and OEE recalculated every minute.