Operations intelligence, floor-level thinking, and the data questions manufacturers are actually asking.
The data exists. The model doesn't. Why I built OIM, and the philosophy that kept it from becoming another brittle framework.
A six-layer architecture that never needs its SQL touched. Here's how config-driven design, dimensional modeling, and a parametric targeting engine converge.
Build for the person doing the work. Everything else follows.
One operator, 35 work orders, and a shift report that still couldn't answer a simple question. The story behind OIM.
Nobody cares how complicated your analysis was. Here's the one thing that actually gets acted on.
How a Data Vault 2.0 fingerprint concept — adapted for 50M rows — became the DQ classification system at the heart of OIM.
Dashboard graveyards exist for one reason: they don't answer the questions that drive action. Here's the test for whether yours will get used.
Standard BI tells you what happened. Operations intelligence tells you what it means, and what to do next.
Why knowing what to work on next is the only metric that actually moves the needle.
Most manufacturers are sitting on years of operational data they never use. Here's what it actually takes to turn that into a clear picture of your floor.
A quick introduction to operations intelligence, and why 345