Brian Crusoe is a manufacturing operations and analytics specialist with 8+ years inside food and CPG plants. He has worked inside MES environments, led production teams, built plant-floor analytics tools, and delivered $1.7M+ in documented savings across six facilities.

The difference is practical: he knows what MES data looks like after a bad shift, how reason codes get abused, why supervisors distrust dashboards, and how CI projects fail when no one proves the fix held.

I didn’t start in software. I started as a lean lead technician running candy lines at Ferrara. Worked my way through production supervision and management at Aspire Bakeries, Hearthside, HelloFresh, Real Good Foods, Glanbia, and Del Monte. Chicken processing lines with 170 people. Powder blending operations. Bakery production. Meal kit assembly. Confectionery.

Along the way, I kept hitting the same problem: MES systems collected everything, teams exported it to Excel, supervisors built charts for the morning meeting — and then nothing changed. The data was never missing. What was missing was a structured process for turning data into action.

So I built my own tools. An OEE analytics platform. Short-stop pattern detection. SMED analysis pipelines. Production intelligence dashboards. They work — but the tools were never the point. The point was the process around them: how does a finding become a fix, who owns the fix, does it hold, and what happens when it doesn’t?

That’s what Crusoe Advisory does. And TRI is the framework that makes it systematic.