Oil and Gas
From the Wild West to End-to-End
How SEQTEK rebuilt Taurex's repair process, and gave the business data it could finally forecast on.
The problem
A drill bit's life is a loop. It gets built, it runs, it comes back, it's repaired, and it runs again, sometimes for years. Tracking that loop is the heart of Taurex's business, and by the time a bit reached repair, the tracking fell apart.
Before SEQTEK, the hand-off into repair was, in Taurex's own words, the Wild West. There was a transfer system almost nobody used correctly. Chad, their IT manager, spent part of every day fixing 10 to 15 broken transfers by hand. Once a bit finally landed in repair, a person had to reconstruct its story from scratch: was it dull and in need of repair, sharp and just needing a repaint, damaged beyond saving? Then they typed in a new assembly number by hand. Multiply that by every bit and every technician, and the naming drifted, the same situation handled two different ways on two different days. When the identity of the thing can't be trusted, nothing built on top of it can be either.
That was the real problem underneath. Taurex's larger goal was good data: normalized, comprehensible records they could actually analyze and feed into a data warehouse. One of the key stakeholders was a data engineer who simply needed the data in better shape before any of the modeling they wanted could happen. Fixing repair was how you got there.
The solution
The scale of the mess wasn't obvious until it was drawn. To design the fix, Andrew mapped the entire process into one enormous flowchart, every path a bit could take on its way through repair, so the team could finally see how many actually existed. Only then could they build a system to handle them all.
What they built tracks the full lifecycle end to end, picking up exactly where the field ticket leaves off. A bit is checked into repair with a few structured questions, answered again when it's received, and those answers tell the system which path it's on. The bit runs its course and the system assigns the new assembly number itself, by rule. Same inputs, same output, every time. The naming stopped drifting because a person stopped doing it, and old workarounds could finally be retired. The system used to need a fake storage location just to remember whether a bit had cutters in it. Now it simply knows.
The impact
With a trustworthy, end-to-end backbone in place, the work compounded. The comprehensible process created room for things Taurex had always wanted but could never cleanly support: engineers can now prescribe which cutters belong in a given bit, and engineering inspections are captured as part of the flow. Downstream, the clean data made cutter forecasting and better revenue forecasting possible, along with performance analysis across a bit's whole life. And all of it shipped alongside the everyday features and fixes that made the shop's daily work easier, not harder.
None of that was a numbering project. It was the Localshoring® process at work: manufacturing alignment among a lot of people with a lot of different ideas about how repair should run, and turning the least consistent corner of Taurex's operation into one of its most dependable.