A metric from anything. Back over every past month.
Whatever made it into the shift log, a meter reading or an imported data set can become a metric — and the module calculates it for every past period from the day you switch it on.
Performance dialogue (the roof of the OE house)
Pick a metric — one click
Electricity ÷ Output produced100 × (Output produced − Output produced (previous)) ÷ Output produced (previous)1000 × Open work orders ÷ Operating hoursOutput produced ÷ Average headcount
—
The other modules collect data. This one consumes it.
Everything else follows from that single difference: no new process, no training, and no waiting for data to accumulate.
They introduce a new process. Training, resistance, and weeks before enough data exists to show anything.
Zero new process. On the day you switch it on it calculates over all your existing data — because the formula runs at display time, not from pre-stored numbers.
Four sources, one namespace
The module does not care where a number came from. Once something is a data point, it can go into a formula.
Whatever the log elements record: quantity, temperature, operating mode, attendance — every field of the log-element builder.
Increasing counters (energy, steam, water). The module derives the difference, and if the chain breaks it says so — it does not write a zero.
Anything that did not originate in OPEREX: lab results, external measurements, an old spreadsheet. Once imported, it is just another data point.
Work orders, incidents, permits. As modules go live your metric options grow by themselves — your formulas do not need rewriting.
Any collected data point becomes a metric
Click a data point and it drops into the formula. The metric calculates immediately — and retroactively: the inputs are already in the system, so there is nothing to upload and nothing to wait for.
Start from a worked example
The formula
—
Try it: type a data point that does not exist, or divide by something that is zero. The card will not print a zero — it tells you what is missing. In this module “no data” and “zero” are two different sentences.
Every BI element you know — with your own metrics
Key figures, trends, rankings, metric matrices, coverage, timelines: everything a management report needs is here. The difference is that you are not handed pre-built reports — every tile carries your own metric, under your own label.
- Key figureOne number against its target
- TrendMovement over time
- RankingWhat contributes most
- Metric matrixSeveral metrics, several scopes
- CoverageHow much is recorded
- TimelineRaw intervals
Views can be narrowed to a site, a plant or any dimension-and-value pair, and the picture downloads as a PDF.
Whoever decides should not have to go looking
Choose how often and to whom. The document goes out as a PDF, and it is archived.
How often
Recipients
This is what goes out
Switch it on whenever you want
separately priced monthly module- You switch it onNo rollout project, no data migration, no training. The shift log carries on unchanged.
- On day one you see the pastIt does not start collecting from now — it calculates back over your existing data. That follows from the module consuming data rather than collecting it.
- You switch it off if you do not need itThe data stays where it is — it belongs to the log, not to the module. Switching off closes the views, not the facts.
A number is only worth something if you know how far to trust it
These are not marketing promises but built-in rules of the module — the same ones that run in the code.
- Missing data is not zeroIf a period has no measurement, the metric does not print 0 — it says there is no data. Conflating the two produces a quietly dishonest trend.
- Every number carries its coverageA 100% computed from data that is 40% filled in still reads as “100%”. That is why coverage is its own figure, not a footnote.
- Unclassified time is not zero-impactWe do not claim that what we did not classify does not matter. The module states the uncertainty as a lower bound.
- A ratio is not the average of ratiosThe monthly average of daily ratios is not the monthly ratio. The module recomputes from its own inputs at every resolution.
Who it is for
Four roles, four different questions — from the same data.
One screen in the morning: where we drifted from target, and what happened overnight.
Specific figures and trends — what we changed, and whether it shows.
Incidents, open items, coverage — in an auditable, retrievable form.
A weekly report in the inbox. No logging in, no searching.
Frequently asked questions
Does it require new data entry?
No. The module interprets data you already have — shift-log elements, meter readings and imported data sets. If you want a metric from something nobody records today, you will of course need to add a log element for it; but you do that on the shift-log side, not here.
Does it really calculate retroactively?
Yes, and it is not a trick: the formula is evaluated at display time rather than read from a pre-computed number. That is why every past period can be calculated immediately from data that is already stored. Where there is no input, the module does not guess — it says there is no data.
Who can see the analytics?
A separate permission controls it, and it is off for everyone by default except the administrator. Site access filters exactly as it does elsewhere: data from a site you cannot see does not appear in your metrics either.
What happens if we switch the module off?
The data stays where it is, because it belongs to the log rather than to the module. Switching off closes the analytics views and the scheduled reports. If you switch it back on, it calculates back over your history just as it did the first time.
Can we send reports to someone outside the company?
Yes, a scheduled report can go to a plain e-mail address. The interface marks such recipients separately, because for them the system's permissions do not filter what they see — that decision should be a conscious one. The document that goes out is archived.
What does it cost?
Operations Analytics is a separately priced monthly module that you can switch on and off at any time. The rates are on the pricing page; if pricing is not public yet, get in touch and we will talk it through.
Step by step, in the Help
The HOW of the product: numbered steps with screenshots — not theory.
A taste of one article: “Log an event in the diary”
Once the module is on, the Analytics page appears in the menu. You grant access per role — by default nobody sees it except the administrator.
Pick data points and write the formula. Give it a name and a unit — that is what appears on tiles and in reports, never the technical key.
Choose the view, the frequency and the recipients. The report goes out as a PDF, and the sent document is archived.
Related reading from the knowledge base
Go deeper into the methodology behind this module.
- The maintenance role in asset teams
- Operations' role in the asset team
- Support functions in the asset team
- Technology's role in the asset team
Part of the OPEREX system
One module among several — all built around operational excellence, sharing data with each other.
Let's start a pilot
We'll show you OPEREX on your own operational processes — no strings attached.
Request a demo