I'd Rather Lose a Sale Than Sell You the Wrong Allen-Bradley PLC

In my role coordinating emergency automation support for plants across the Midwest, I've handled maybe 300 rush calls in the last nine years. Maybe 280—I'd have to check the CRM. And here's what I believe more strongly every time the phone rings at 2 AM:

I'd rather lose a sale than sell you the wrong Allen-Bradley PLC.

That sounds counterintuitive for someone who gets paid to solve urgent problems. But after enough line-down midnights, you learn that "fast" only counts if the fix stays fixed. The wrong controller isn't just a bad purchase—it's a time bomb at the center of someone's production line.

The Micro820 question: when "downgrading" is the professional move

In March 2024, a maintenance manager called me at 5:17 PM on a Friday from a packaging plant in Ohio. A wrapping line was down. He already had a PO drafted for what another distributor had told him he needed: an Allen-Bradley ControlLogix PLC—the flagship processor. The number on that PO was about $4,200.

I asked him what the machine actually did.

Eleven digital inputs. Seven outputs. One analog sensor. A basic HMI. No motion control. No remote I/O. No plant-wide EtherNet/IP backbone.

So I gave him the answer that sounds like bad sales: you don't need a ControlLogix for this. An Allen-Bradley Micro820 PLC will cover it.

The Micro820 is a fixed-I/O controller in the Micro800 family—kind of a workhorse for small machines and stand-alone equipment. It's a fraction of the cost of the big system, it programs in Connected Components Workbench, and the setup is simple enough that a technician can have it running in a couple of hours.

But the thing that actually convinced him was the timeline. He was down Friday evening and wanted to run Monday morning. A Micro820 could be configured and tested the same night. A ControlLogix meant backplane planning, module selection, and a commissioning schedule that would bleed into the next week.

I don't have hard data on how often people overspec their Allen-Bradley controllers. But based on my experience, my sense is that at least one out of three "urgent ControlLogix" requests I get could be handled by a Micro820 or another mid-range processor.

People think a bigger PLC means a more reliable system. Actually, it's often the opposite. Oversizing multiplies points of failure: more configuration steps, more modules, more addressing possibilities. The right-sized controller is the reliable one. Does that sound like bad advice? It's not. It's the difference between solving a problem and creating a new one.

The other side of the coin: under-spec'ing is worse

Then again, the opposite mistake is even costlier.

Earlier this year, a client came to us after a distributor had saved them $1,800 on paper by spec'ing a Micro800-series controller on a material handling line with twenty-three remote I/O drops, redundant power, and coordinated motion. The distributor made the numbers look great. The client signed because the quote was cheap.

The line was commissioned and immediately became the bottleneck. The controller ran pegged near max scan time. HMI polls lagged. The servo sequence started getting jittery under load. They patched it for two months before calling us. After a week of on-site diagnostics, the verdict was unambiguous: the system needed the Allen-Bradley ControlLogix PLC—the full-scale processor, with the I/O capacity and the scan-time headroom to do the job.

The $1,800 they saved on the front end turned into a $9,200 retrofit, plus about 32 hours of lost production across three shifts. The "budget controller" choice looked smart until the process couldn't run. Net loss, counting labor: roughly $11,400. I don't know what their unplanned downtime cost, but I'm sure they do.

I've never fully understood the logic of spec'ing a tiny controller to save maybe 8% on a job that loses 40% of its value if it's wrong. My best guess is that people anchor to the sticker price and stop thinking about the total cost of ownership.

Where the boundary gets fuzzy: VFD cable, battery chargers, and the line I won't cross

This is where "we-do-everything" suppliers start to smell like trouble.

One of the most common questions I get from newer plant engineers is, honestly, a reasonable one: "What is VFD cable, and does it matter?" Let me give you the short version.

VFD cable—variable frequency drive cable—is a shielded power cable built to handle the high-frequency voltage spikes that VFDs generate. The shielding protects motor bearings and nearby signal wiring from interference. If you're installing a drive on any motor bigger than a few horsepower, yes, it matters. Using standard cable can cause bearing failures and mysterious faults.

Does my company sell VFD cable? No. We can source it, but we're not cable experts. Honestly, I know just enough to be dangerous—and that's exactly why I don't claim to be one. If you need a hundred feet this week, I'll give you two vendors I've tested and one I'd use on a deadline. But pretending I'm a cable specialist is how you end up with a mysterious drive fault at 11 PM on a Saturday.

Then there's the classic: a maintenance lead asked me to spec a 12/24 volt battery charger for a control panel backup system. I paused. I've installed plenty of 24V DC power supplies, but a true 12/24 volt battery charger—with float charging, thermal compensation, the works—that's a specialty product. A wrong pick will quietly cook batteries for months, and you'll find out the moment you actually need them.

I told him I don't do that, then sent him to someone who builds industrial battery systems daily. Did I lose money on that ticket? Maybe a couple hundred dollars of markup. But that client said something later that stuck with me: "The vendor who said, 'this isn't our strength—here's who does it better' earned my trust for everything else."

And yes, I once got a call asking if we carried a 7.3 fuel filter housing rebuild kit. That's a part for a Ford 7.3L Powerstroke diesel. At a PLC company. I laughed for ten seconds, then gave him the name of a diesel specialist. He got his part. I got a story—and a reminder that every company has a lane.

But what about "one-stop shop"? Isn't that easier?

I used to think that. And in 2023, our own leadership tested the idea. We expanded into panel building, wire harnesses, even some on-site mechanical installation. "Be everything to everyone" was the phrase making the rounds. The theory was that clients would love the convenience of one vendor for everything.

It didn't work.

I wish I had tracked the metrics of that experiment more carefully. What I can say anecdotally is that within six months, our core work—PLC programming and emergency support—started degrading. Projects took longer because senior engineers were supervising panel assemblies instead of reviewing programs. Junior staff didn't get mentored because the seniors were stretched thin. One long-term client left during that period and didn't come back.

The assumption is that a one-stop shop saves money on procurement. The reality is that most one-stop shops are mediocre at every stop on their menu. That's when we implemented a policy I'm actually proud of: if a request falls outside our lane, we refer it out—no exceptions.

This approach works precisely because of its boundaries. We do PLCs—Allen-Bradley in particular, plus programming and training around them. That focus makes us faster, safer, and more dependable for the things that matter most.

Bottom line: boundaries are a feature, not a bug

If you've ever been on a plant floor at 3 AM with a dead line and a budget that can't absorb another mistake, you know what I mean. The right controller—an Allen-Bradley Micro820 PLC for a small stand-alone machine, an Allen-Bradley ControlLogix PLC for a large distributed system—isn't a luxury. It's the cheapest insurance you can buy.

And the supplier who tells you "that's outside what we do" isn't failing you. They're protecting you from the vendor who'll fake it until something breaks.

So here's my advice: next time you're getting quotes for an automation project, ask what the supplier won't do. Their answer will tell you more about their integrity than their catalog ever will.