DEV Community: Ahana Basu

Stop Comparing CMMS Tools, Start Comparing Outcomes

Ahana Basu — Mon, 29 Jun 2026 12:25:28 +0000

A buddy of mine runs maintenance for a midsized operator out of Oklahoma. He sent me a spreadsheet last month. 14 columns. 9 CMMS vendors. Color-coded. Checkboxes for things like "mobile work orders" and "offline mode" and "custom dashboards."

I asked him one question. "If you pick the one with the most green checkmarks, what actually changes on Monday morning?"

He stared at me for about ten seconds.

That's the problem with how this industry buys software.

The Checklist Trap

Procurement loves a feature matrix. Vendors love a feature matrix even more, because they can engineer their product to win the matrix.

Everyone ends up comparing tools that look identical on paper. Mobile app, check. Asset hierarchy, check. PM scheduling, check. Reporting suite, check.

Six months later the team is still drowning in reactive work, the work orders still take 4 days to close, and the dashboards nobody asked for are getting beautifully updated every hour.

The features were never the question. The outcomes were.

What You're Actually Buying?

Strip away the marketing and a maintenance system is doing four things for you:

Getting the right job to the right tech faster
Keeping assets running longer between failures
Making sure parts and people show up at the same time
Giving leadership a real picture of what's happening across sites

That's it. Everything else is packaging.

If a tool wins the checklist but doesn't move those four needles, you bought a very expensive logbook.

The Question Nobody Asks in the Demo

Vendors love to walk you through the UI. The slick mobile screen. The drag-and-drop scheduler. The Gantt view that took their design team three sprints to build.

Here's the question that actually matters, and almost nobody asks it.

"Show me a customer who reduced mean time to repair by 30% using your platform, and walk me through exactly how the workflow changed."

Watch what happens. About half the vendors will pivot to a generic case study. A quarter will show you a logo wall. The ones who can actually answer it tend to be the ones worth shortlisting.

The difference between cmms vs fsm software matters less than whether the tool you pick actually changes how work flows from anomaly to closeout. Categories are useful for analysts. They don't fix downtime.

Outcomes Worth Buying For

If I had to rank what actually matters when you're picking a maintenance platform, it'd look something like this.

Time from issue detected to work order closed. This single metric tells you more than any dashboard ever will
Reactive vs planned work ratio. If you're still 70% reactive a year in, the tool isn't working
Technician wrench time. How much of an 8 hour shift is actually spent fixing things versus hunting for info
First-time fix rate. Did the tech show up with the right part, the right info, and the right access
Audit and compliance turnaround. Can you pull a clean report in 20 minutes when a regulator asks

Notice none of these are features. They're business results.

Why Most Teams Get Stuck?

The honest answer is that comparing outcomes is harder than comparing features.

Features fit on a spreadsheet. Outcomes require you to map your own workflow, identify where the friction actually lives, and then figure out whether a given tool removes that friction or just decorates around it.

Most buying committees don't have the time or the political room for that, so they default to the checklist. The vendor with the longest list wins. The team that has to use the thing every day loses.

That's why so many CMMS rollouts end up shelfware. Procurement picked the most feature-rich option. The maintenance team needed the one that fit their actual workflow.

What Outcome-Driven Looks Like in Practice?

A platform built around outcomes does a few unsexy things really well.

A work order generated from an alert reaches the right tech's phone within minutes, with the asset history pre-attached
Inventory checks happen automatically when a job is created, not after a tech drives to the warehouse and finds an empty shelf
Field updates sync back without somebody having to retype them in the office at the end of the day
The supervisor sees the same picture the operator sees, not a sanitized version filtered through two reports and a Monday morning meeting

This is roughly what Equipt.ai was designed around. Not a CMMS competing on module count, but a connected workflow where maintenance, assets, inventory, and field execution actually share the same brain. The win isn't a prettier dashboard. The win is that an asset that used to take 11 days from issue to closeout now takes 3, and your reactive ratio quietly drops from 70% to 40% without anyone running a special initiative.

If you want a deeper read on where the category is heading, the broader cmms software trends point in the same direction. Less monolith, more execution. Less reporting, more doing.

A Better Way to Run an Evaluation

If I were buying a maintenance platform tomorrow, here's how I'd run the process.

First, write down 3 to 5 outcomes you actually want to change. Not features. Outcomes. Lower MTTR. Higher first-time fix rate. Fewer emergency callouts. Whatever your operation actually needs.

Second, build a one-page workflow of how those outcomes are blocked today. Where does work actually get stuck. Who's waiting on what.

Third, hand that page to every vendor and ask them to walk you through how their platform changes that specific workflow. Not a generic demo. Yours.

Fourth, talk to two of their customers who started where you are. Not their flagship customers. Real ones who've been on the platform 18 months and have honest scars to show you.

You'll learn more in those four steps than in 40 hours of feature comparison spreadsheets.

Where Field Service Fits?

One more thing worth flagging. A lot of operations teams are realizing that maintenance and field service are blurring together. The tech walking the pad isn't doing a different job than the tech responding to a service ticket. Same person, same hands, same assets.

Buying a separate CMMS and a separate field service management software stack creates the exact disconnect you were trying to fix in the first place. Two systems, two logins, two data models, two sources of truth that always disagree. The teams getting ahead are running one connected system, not two parallel ones.

What Procurement Doesn't Want to Hear?

A lot of buying committees get rewarded for negotiating on price. Nobody gets rewarded for negotiating on outcomes.

That's backwards.

A 15% discount on a platform that doesn't move your MTTR is a worse deal than full price on one that does. Run the math. The cost of an extra week of downtime on a single critical asset usually dwarfs the entire annual software bill. We optimize the wrong column on the invoice.

The Bottom Line

Stop scoring vendors. Start scoring your operation.

Pick the metrics you'd be embarrassed to show your CEO right now, and choose the platform that moves those numbers. Everything else is theater.

The best maintenance software isn't the one with the longest feature list. It's the one your team actually uses on a Tuesday at 4pm when a compressor trips and the deadline for the audit is Friday.

What I Learned Implementing AI-Powered Spare Parts Management in an Oilfield Yard

Ahana Basu — Mon, 22 Jun 2026 11:16:45 +0000

The first time I walked into our parts yard at 5 a.m. and watched a senior tech dig through three shelves for a single stuffing box packing set, I knew the spreadsheet wasn't cutting it. He found it. Forty minutes later. The pumper on location had already called twice.

That morning is basically why we ended up rebuilding the whole thing around AI. Not because somebody read a Gartner report. Because a guy named Travis was tired.

Here's what actually happened when we switched, what worked, what didn't, and a few things I'd tell anyone in oil and gas before they start.

The Yard Was a Mess and Nobody Wanted to Say It

We had a CMMS. We had bin locations. We had a parts clerk who knew where everything was if you asked nicely.

The problem was none of that survived a busy week.

Here's what was actually going on:

Two of the same VFD sitting in a back row because nobody knew we had one
Beam pump bearings stocked for a well type we retired in 2022
Glycol pump seals out of stock for six weeks while three units waited
Inventory counts that matched the system on January 1 and nothing after
Techs pulling parts and writing it down "later"

Later never came. Later is a myth in field operations.

A real parts yard before any structured tracking. Closer to the norm than anyone wants to admit.

What AI Actually Does Here (It's Not Magic)

When our ops manager said "AI for parts," half the yard rolled their eyes. Fair. There's a lot of noise around this.

What it really does is boring in the best way. It looks at your work order history, equipment runtime, failure patterns, and consumption rates, then hands back a forecast that isn't based on a gut feeling from 2019.

A few things it started catching for us almost immediately:

Seasonal demand on heater treater elements we always under-ordered in November
A specific brand of pump packing that failed 40% faster on one pad
Reorder points that were set once and never touched since the yard opened

The shift from "we usually order this much" to "based on the last 14 months and current runtime, you'll need 6 in the next 21 days" is the whole game.

If you want a deeper walkthrough of how that demand modeling actually works under the hood, Equipt put together a solid breakdown on how to digitize spare part management that I sent to our purchasing lead before we kicked off.

Connecting Parts to the Equipment They Actually Live On

This is the part I underestimated.

A bearing isn't just a bearing. It's a bearing on Unit 14, which is a Lufkin 320, which had a gearbox rebuild in March, and has been running hotter than its peers since May.

When parts records sit in one system and equipment history sits in another, you lose all of that. The tech sees a part number. He doesn't see that the last three times this bin was pulled, the unit was back down within 90 days.

Once we tied parts usage to asset history, two things happened:

We stopped replacing symptoms. The bearing wasn't the problem. The alignment was.
We started seeing which suppliers' parts actually lasted on our equipment, not in a catalog.

That's where a connected oil and gas asset management setup earns its keep. One asset, one history, one parts trail. No more cross-referencing three tabs to figure out why a pump keeps eating seals.

The Overstocking Problem Nobody Talks About

Everyone worries about stockouts. Nobody talks about the $180,000 in slow-moving inventory aging on the back rack.

We had:

Specialty valves for a workover rig we sold in 2023
An entire shelf of fittings for a metric-spec pump line we phased out
Filters in three sizes when techs only ever pulled one

AI sorted this in about a week of usage analysis. It flagged anything that hadn't moved in 18 months and cross-checked it against current active equipment. The list was uncomfortable. We moved or wrote off about a third of it.

The cash that freed up went into actually stocking the fast-movers properly.

Same yard, four months in. The shelves aren't fancier. They just match what the field actually pulls.

Where Maintenance Strategy Fits In

You can't talk about parts without talking about how you do maintenance. If you're still running pure reactive, AI forecasting won't save you, because your demand signal is chaos.

We had to clean up our maintenance approach first. If you haven't sat down and worked out where you actually fall on the preventive vs predictive vs proactive maintenance spectrum, the parts side will keep fighting itself.

Quick version of what we learned:

Preventive gives the forecast something stable to chase
Predictive tells you the part is about to be needed before the failure happens
Proactive changes which parts you stock in the first place

The yard inventory shifted as our maintenance posture shifted. That's normal. That's the point.

What Surprised Me Most

A few things I didn't expect going in:

Techs adopted the mobile scanning faster than the office staff adopted the dashboards
The biggest savings weren't on big-ticket parts, they were on the small consumables nobody tracked
Suppliers negotiated better terms once we could show them clean usage data
Our parts clerk became more valuable, not less, because she was finally working on planning instead of hunting

The fear that "AI will replace the parts guy" was the opposite of what happened. The parts guy got promoted.

A Few Things I'd Do Differently

If I were starting again tomorrow:

Spend two full weeks cleaning master data before turning anything on. Bad data in, bad forecasts out.
Get the field techs in the room for the bin layout, not just the warehouse lead.
Don't pick a tool that only talks to itself. The whole point is connection.

That last one is why we ended up settling on a single platform instead of bolting three tools together. When parts, work orders, asset history, and maintenance plans live in the same place, the AI has something real to work with. Equipt.ai was where we landed because their oil and gas software treats the yard as part of operations, not as a separate inventory problem to solve later.

Final Thought

The first morning after we went live, Travis walked in, scanned a bin, grabbed the right packing set in under a minute, and left without saying anything.

That's the whole win. Nobody talked about AI. Nobody talked about dashboards. A guy got a part and went back to work.

If you're in an oilfield yard right now wondering whether this is worth the lift, that's the bar. Not the demo. Not the slide deck. Whether Travis gets out the door faster on a Tuesday morning.

Why 90% of Oilfield Maintenance Programs Still Fail in 2026 (And the AI Fix That Works)

Ahana Basu — Tue, 16 Jun 2026 09:07:59 +0000

Last week, I was on a call with a maintenance supervisor from a midstream operator in West Texas. He had a spreadsheet open. Color-coded, actually pretty. Then a compressor tripped offline mid-conversation, and he just laughed. "That one wasn't even on the list."

That story is basically the oilfield in 2026.

Operators have spent fortunes on CMMS rollouts, sensor upgrades, and dashboards nobody opens after the first month. The maintenance programs look great on paper. Audits pass, KPIs get reported, and then a pump dies on a Saturday, and the whole quarter's plan goes sideways.

So why does this keep happening? And what's actually changed now that AI is in the mix?

I've been digging into this for a while, talking to ops people, vendors, and a few skeptical reliability engineers.

Here's the honest version.

The Real Reason Most Programs Fail (Hint: It Isn't the Tech)

People love blaming software. The CMMS is clunky, the sensors aren't talking to each other, and the dashboard is ugly.

Sure, all of that is true sometimes.

But the deeper issue?

Most oilfield maintenance programs are stuck in a calendar mindset. You service the pump every 90 days because the manual says so. The pump may be fine. The pump may have been screaming for help on day 47. Doesn't matter. The calendar wins.

A few patterns I see again and again:

Work orders are generated by tradition, not by condition
Sensor data collected but never used for actual decisions
Technicians are fixing the same failure modes every six months without anyone stopping to ask why
"Predictive" tools that flag everything as urgent, so nothing feels urgent

That last one is the killer. Alert fatigue is real. When your screen lights up 40 times a shift, you start ignoring it, and the expensive software becomes wallpaper.

Preventive, Predictive, Proactive: They're Not the Same Thing

A lot of teams mix these up, and it costs them. There's a useful breakdown of preventive vs proactive maintenance worth reading before you commit a budget anywhere.

Quick version, though:

Preventive is calendar-based. Time triggers the work.
Predictive is data-based. Sensor patterns trigger the work.
Proactive is root-cause based. You fix the reason failures keep happening in the first place.

Most "AI maintenance" pitches are really just dressed-up predictive. Which is fine, but it's only half the story. If your bearings keep failing because the alignment was off from day one, no amount of vibration analysis will save you.

You'll just predict the same failure faster, more accurately, every single time.

What 2026 Actually Looks Like in the Field

Talked to a reliability engineer in the Permian last month. Her team runs about 1,200 assets across three pads. Two years ago, they were drowning in tickets and chasing ghosts.

Now?

Four people manage the same footprint that used to take twelve, and unplanned downtime is down somewhere around 60%.

What changed wasn't a single tool. It was the layering:

Sensors got cheaper, so coverage went up across the board
Edge devices started doing real analysis on-site instead of pinging the cloud for every reading
AI models finally got decent at separating noise from actual anomalies
Field techs got mobile interfaces that actually work with gloves on in cold weather (huge, honestly)

The combo matters. Any one of those alone is a science project that quietly dies in a procurement folder somewhere.

Her favorite story: an AI flag on a glycol pump that nobody on the team would have caught manually. Bearing temp drift, tiny but consistent, over about ten days. They swapped it during a scheduled visit instead of a 2 am emergency.

Total cost difference, roughly $40k on one asset.

Where AI Actually Earns Its Keep

Look, I'm not going to pretend AI is magic. It isn't. But there are specific spots where it genuinely moves the needle for oilfield ops.

Failure pattern recognition across fleets is the big one. Humans are great at watching one pump. They're terrible at noticing that 47 pumps across four counties are all showing the same micro-trend three weeks before catastrophic failure. AI eats that for breakfast.

Smart prioritization is the other. Instead of 40 alerts, you get the three that matter today, ranked by downtime risk and revenue impact.

Auto-generated work orders with parts pre-staged sound small. It saves hours per ticket and stops the parts-runner shuffle that nobody budgets for.

This is where an intuitive oil and gas software stops being a cost center and starts paying for itself. The ROI math gets pretty hard to ignore once you see a real before-and-after from a working pilot.

The Stuff Nobody Talks About

Implementation kills more good intentions than bad technology does. A few honest things I've seen go wrong:

Companies buy the platform, then assign zero internal owner. It dies in six months.
Field teams get told "the AI says to do X" with no context, so they ignore the AI on principle.
Data quality is awful for the first 90 days, and leadership panics instead of letting the models calibrate.
The vendor disappears after go-live, and nobody on the customer side knows how to retrain a model.

Teams that win treat the rollout like a relationship, not a project. They pilot small. They listen to techs in the field. They tune as they go, and they don't expect miracles in week two.

One supervisor told me his rule: "If the system can't explain why it's flagging something in one sentence, we don't use that feature yet." Pretty good rule, honestly.

What to Look For When You're Evaluating Tools

If you're shopping right now, here's what I'd actually care about:

Does it integrate with the SCADA and historian you already have, or does it want to rip and replace?
Can a tech use it on a phone, in the field, with a bad signal?
Are the AI recommendations explainable, or is it a black box you have to trust?
Does the vendor understand oilfield assets specifically, or are they retrofitting something generic?

That last one is bigger than people realize. A platform built for hospital HVAC is not going to understand a beam pump correctly. Domain matters a lot. It's one reason purpose-built oil and gas asset management software tends to outperform generic enterprise tools, even when the generic ones cost more upfront.

So, Is It Actually Different This Time?

Honest answer: yes, but only if you change how your team works alongside the tools.

The 90% failure rate isn't really about AI being too immature. It's about programs being designed around compliance and tradition instead of conditions and outcomes.

The AI piece is a multiplier, not a savior. Pair it with a team that's allowed to act on what it sees, give them a couple of quarters to settle in, and the numbers shift fast.

I'd love to hear from people running this in production right now. What's working on your end this year?

What's still broken?

Drop a comment below, I actually read every single one of them.