The OIM · Operations Intelligence Model · Decide

You trust the numbers now. This is what you decide from.

The OIM is the operations intelligence layer that sits on top of your ERP and turns the data you already have into a live view of what’s happening on the floor, in the language your team already speaks, on hardware you already own. It’s the last rung of the ladder: the thing you build once the numbers are proven and worth deciding on.

What it is

The OIM takes the raw operational data your ERP already produces and builds it into a real model. A Kimball dimensional model on a medallion architecture, with ISO 22400 / SMRP-aligned metrics: throughput, OEE, downtime, reliability, quality. Not a report someone else built and handed you, but a foundation you own, understand, and can defend.

You own it outright. It runs local-first, on hardware you already have. No cloud dependency, no vendor holding access to your production data, no subscription, no IT team required to stand it up. The infrastructure, the model, the data, all yours. The same intelligence enterprises pay data teams to build, put in the hands of a plant that never had one.

The OIM is where the ladder leads. Verify checked the numbers you suspected, Validate proved the whole move, and Vigil kept the watch. The OIM is what the same people build once that trust is earned: a shared view of the floor, on numbers you’ve already watched hold.

Why it matters

Before any operational insight can matter, someone has to build the model. Take the raw export, define what “downtime” means for this floor, map the reason codes, decide which timestamp to trust. That work is unglamorous and rarely talked about, and without it nothing else works. Most manufacturers never get it, because it was only ever built for companies with a data team.

The payoff is a single shared truth. The same data model speaks to every level. Operators see what they need, plant managers see theirs, executives see theirs, and no reconciliation meeting is needed to argue about whose number is right. That is the difference between a black box you inherited and a system you can reason with.

How it works
  1. Map what your data means. Walk your tables field by field, confirm what each one represents, and flag what diverges from the standard. A one-time setup, after which OIM learns your system so you don’t have to re-explain it.
  2. Schedule it, then leave it. Once mapped, OIM refreshes on a schedule you control. No manual exports, no re-loading files. Your view stays current on its own.
  3. Translate to every level. One data model, rendered for the people who need it: the operator’s view, the plant manager’s, the executive’s. No one reconciles three versions of the same number.
  4. Show the data quality alongside. The OIM scores what’s missing, inconsistent, or needs attention right next to the view, not buried in a footnote. You trust the output because you can see the input.
The thinking behind it
No. 014 INFLUENCES

Goldratt on the Floor.

Operations intelligence is the information that gives you the confidence to choose what’s next. The worldview OIM is built to serve: constraints, throughput, and the one thing actually worth looking at.

Read the Fieldbook →