«Where does value get lost in the overall operations of the business?» The ERP, the MES and the SCADA each do their job well, but this question falls between their perimeters: it belongs to no one. Addressing that space is a discipline in its own right, and it has a name — Operational Intelligence.
Every manufacturing company already has an operating model. The problem is that it is almost never explicit: it lives in the production manager's head, in the habits of the shift, in the Monday morning Excel spreadsheets.
When that model is not shared and updated in real time, decisions are made on different versions of the same reality. Not through incompetence: because every function legitimately sees only its own portion.
Operational Intelligence is the discipline that makes that model explicit, shared and updated in real time. It presupposes the existence of reliable vertical systems: it does not replace them, it increases their value.
«The MES answers the question how is production going. arteMES answers the question how is your business performing.»
Every category of digital tools was created to answer a question that previous systems could not handle. The ERP addressed administrative fragmentation. The MES addressed production visibility. What remains uncovered today is cross-functional operational fragmentation: the information lost between one domain and another.
We call Operational Intelligence the discipline that addresses that space. Whether it constitutes a category in its own right or an extension of the preceding ones is a discussion that interests us more than it does you: what matters is that that question today has no owner.
An Operational Intelligence Platform operates on three levels that activate in progressive sequence. Each one is useless without the previous.
The PLC knows the machine stopped. The ERP knows the order is delayed. The purchasing office knows the materials arrived late. Rarely does a system know that those three things are connected, that they occurred within two hours of each other and that together they generated a three-day delivery delay.
At 10:47 on Tuesday a press stops due to a hydraulic failure. The MES logs the stoppage, the technician enters the cause code, OEE drops. End of story — from the MES's perspective.
But it is not the end of the story. That press was working on the most urgent order of the week. The delay triggers a priority change that shifts another order and causes a delivery to slip. The downstream machines remain powered on and waiting, consuming energy without producing. The manager spends two hours reorganising the schedule.
When discussing the cost of a stoppage, the conversation almost always stops at the direct cost: lost machine time, unproductive labour, maintenance. Real items, but only the most visible part. The most significant part lies in the downstream chain.
The invisible cost appears in no report because almost no system was designed to see it. This is not a technology gap: it is a design gap.
Objections are not resistance: they are signals that the problem exists and that someone has already tried to address it. Every objection conceals a confirmation of the problem.
«With what you have today, can you know — right now, without manually extracting data — which order is eroding the most margin?»
The most concrete impact is not technical. It is organisational: systems do not change, conversations change.
You do not need to choose software. You need to identify where margin is being lost. That is the starting point: two weeks, one machine, no replacement.