The RFP That Started It All
It was Q2 of 2023. I had just been handed the budget for our annual control system refresh—roughly $180,000 in cumulative spending to manage across six production lines. It’s the kind of project that looks simple on paper: replace aging programmable logic controllers (PLCs) on three machines, standardize on one platform, and get out before the end-of-year shutdown.
If you’ve ever managed a procurement cycle for industrial automation, you know the drill: send out an RFP, get quotes, compare, and pick the winner. Simple, right?
Not quite. I’d been a procurement manager for eight years, but this was my first deep dive into PLCs. I knew the basics—Omron, Siemens, Allen-Bradley were the big names—but I didn’t know the nuances. And boy, did that come back to bite me.
The ‘Budget-Friendly’ Quote
We sent out our spec sheet. It was fairly generic: 24 inputs, 16 outputs, Ethernet/IP, a couple of analog channels, and programming software. Standard stuff for a packaging line.
One vendor—let’s call them Vendor B—came back with a quote that was 22% lower than everyone else. The line item said: “Equivalent Omron CP1E-NA20DR-A.” I wasn’t an engineer, but I’d done my homework. The CP1E was a solid, entry-level model. The price was tempting.
Honestly, I was ready to sign. The savings were clear. My procurement policy required three quotes, but Vendor B’s price was a no-brainer. I almost pulled the trigger.
The First Red Flag
Then one of our senior maintenance engineers, a guy who’s been with us for 15 years, pulled me aside. “You’re not seriously going with that, are you?” he asked, half-joking.
I showed him the quote. He skimmed it and pointed to one line: “Software license: Not included.”
“Yeah, so?” I said. “We have CX-One already.”
He shook his head. “Look at the model number. CP1E-NA20DR-A. That’s an older version. Does not support the latest version of CX-One. You’d need the legacy CX-Programmer—separate license, $1,200 per seat. Also, you won’t get the new function blocks for safety interlocks.”
I stared at the quote again. I hadn’t even looked at the software compatibility. Let me rephrase that: I had assumed that all CP1E models were the same. I hadn’t verified.
Take it from someone who's been burned: never assume 'same specifications' means identical results across vendors. I learned that lesson the hard way.
The Race to Fix It
This gets into technical territory that isn’t my expertise. I’m not a controls engineer. What I can tell you from a procurement perspective is how much it cost us to correct that oversight.
I went back to the TCO spreadsheet I should have built in the first place. Vendor A (the one I almost dismissed) had quoted a CP1L model—a step up in performance—with a full software suite included, plus two days of on-site training for our techs. Vendor B’s “cheaper” option, after adding the legacy software, a one-day training session (because their model wasn’t compatible with our training materials), and a rush shipping charge for the second batch we had to order, was actually 4% more expensive.
Seriously. The 'cheap' option ended up costing us more. And that’s not including the hidden cost of engineering time spent figuring out the quirks of a model we weren’t familiar with.
I calculated the worst case: complete redo on a line with wrong hardware, costing $3,500 in downtime. The best case was saving $800. The expected value said go for the cheaper option, but the downside felt catastrophic.
The 12-Point Checklist (Born from Disaster)
After that fiasco, I built a procurement checklist for any automation component. It’s saved us an estimated $8,000 in potential rework since 2023. Here’s what it includes:
- Software version compatibility: Is the quoted hardware supported by the latest programming environment? If not, what’s the cost of the legacy version?
- Training and documentation: Does the vendor provide training for this specific model? Are our techs already familiar with it?
- Future-proofing: Will this model be supported for the next 5-7 years? Or is it end-of-life? (Check the Omron product lifecycle page for this.)
- Total peripheral cost: Cables, communication modules, power supplies—what’s the full BOM?
- Warranty and support SLA: What’s the response time for a replacement? Is advanced replacement available?
Skipping the final hardware compatibility review because we were rushing and 'it's basically the same as last time' was a $1,200 mistake. It wasn't the same.
The Outcome: A Better Process
In the end, we went with the CP1L from Vendor A. The total contract, including training and a 3-year warranty, came to $4,200. It cost more upfront, but the peace of mind was worth it. The lines went live without a hitch during the shutdown.
Even after choosing the new vendor, I kept second-guessing. What if Vendor B’s hardware was perfectly fine? The two weeks until delivery were stressful. But when the first line started up without a single error, I knew we made the right call.
Since then, our procurement policy requires quotes from at least three vendors, but with a mandatory TCO comparison spreadsheet. We also require engineering sign-off on the spec sheet before the RFP goes out.
I’ve never fully understood why some vendors quote a bare-bones solution to win the price war. My best guess is they’re betting you’ll pay for the add-ons later. It’s more art than science.
What I Learned (and What You Should Steal)
Five minutes of verification beats five days of correction. That’s the bottom line. The 12-point checklist I created after my third mistake has saved us an estimated $8,000 in potential rework. It’s not the most exciting tool in the world, but it works.
Also: don’t be afraid to admit when you’re out of your depth. I’m not a controls engineer. I don’t pretend to be. But by building relationships with our in-house experts and forcing myself to learn the difference between a CP1E and a CP1L, I became a better buyer.
Most importantly: The lowest priced option is rarely the lowest total cost. Especially for industrial equipment that needs to run 24/7.
Over the past 6 years of tracking every invoice in our system, I’ve found that 70% of our 'budget overruns' came from hidden compatibility issues. We implemented a 'pre-qualify before quoting' policy and cut overruns by 40%.
So, before you sign that purchase order for an Omron PLC, take 20 minutes and run it through a TCO calculator. You might be surprised what you find.
