Last August, my company took on a packaging cell project that stretched us in ways I didn't expect. We're a four-person automation shop — mostly retrofits and small machines. This one? A servo-driven pusher, a five-axis robot arm, an HMI, and a safety circuit. The customer's spec sheet asked for Omron PLCs because their entire plant runs on CP1L and CP1H units. Their maintenance team already knew that ecosystem, so staying in it was the logical move from a lifecycle cost standpoint.
I handle procurement, so my job was simple on paper: source the controls, stay within budget, don't slow down the build. Our controls budget was $18,500. What happened over the next six weeks turned into a cost comparison spreadsheet I still use, and a lesson about hidden line items that I'd rather have learned a cheaper way.
The Quotes Roll In
I sent the I/O list and network drawings to three distributors. The first quote came back at $14,800. The second — from a vendor we'd never used — came in at $12,200, same PLC models, same rough I/O count, plus a free programming cable. Then our usual distributor quoted $15,600, but their package included something the others didn't: a two-hour site visit from their applications engineer.
Here's something vendors won't tell you: the first quote is almost never the final price for an ongoing relationship. There's usually room to negotiate once you've proven you're a reliable customer. But what I didn't catch right away was that the cheapest quote had gaps — not in the line items, but in the assumptions behind them.
"Why is theirs $2,600 less?" I asked my engineer, who was sketching the network topology on a whiteboard that had seen better days.
He shrugged. "Different surge protection spec, maybe. Or they're not quoting the same servo drive."
That "or" bothered me. I started building a comparison spreadsheet.
Surge Arresters vs. Surge Protectors: Not the Same Line Item
Vendor B's quote listed "surge suppression" as a single line item — $180. Our usual distributor itemized it as two components: a surge arrester at $240 and a surge protector at $95 for the control panel feed.
Now, I'm not an electrical engineer, so I can't speak to the code requirements in depth. What I can tell you from a procurement perspective is the difference matters for your budget.
Surge arresters and surge protectors get used interchangeably on job sites all the time. They're not the same. A surge arrester handles larger transient overvoltages — lightning strikes, utility switching — and shunts that energy to ground. A surge protector, or TVSS if you want the acronym, handles smaller, more frequent transients that can slowly degrade a PLC power supply over time. Most industrial panels need both, at different points in the system.
Vendor B wasn't trying to pull a fast one, I think. They just spec'd it the way a lot of shops do — one generic line item. But the customer's approved drawings specified both. We would have bought the missing component anyway. There went $240 of the "savings."
The Pulse Output Maximum Frequency Speed Question
The Omron PLC programming side got more interesting. Our engineer needed pulse output channels for the servo pusher. The customer's spec called for "pulse output maximum frequency: 1 MHz" — the speed at which the PLC sends step and direction pulses to the servo drive. From the datasheet — Omron's published specifications for the CP1H, which I pulled in February 2025 — the pulse output maximum frequency speed is 1 MHz on the high-speed outputs. But the robot control panel — the operator station with the E-stop, mode selector, and the HMI — also needed a dedicated pulse train for the robot's indexing axis. The CP1H has two pulse output channels, so technically it could handle both. But there was zero headroom for the third axis the customer hinted they'd add "someday."
The CP1H would do the job today. But the NX102 — a moderately more expensive option — would give us headroom without a control panel redesign later. Our usual distributor's quote included the NX102. The two cheaper quotes didn't, because I'd written the request around the CP1H. I'd asked for "what meets the spec today," not "what carries us into next year."
That's a mistake I've made before, which is why our procurement policy now requires quotes from three vendors using identical assumptions. At least, that's been my experience over the past six years of ordering controls for this shop.
The Windows Sound Control Panel Moment
I want to say the rest of the project went smoothly. It didn't. The surprise showed up in the configuration screens for the pulse outputs inside the Omron programming software.
Our controls engineer described the setup interface as having "more hidden menus than the Windows sound control panel." If you've ever tried to figure out why your laptop's audio isn't working, you know that's saying something.
What he meant: the datasheet spec for pulse output maximum frequency — 1 MHz on the CP1H — is the ceiling, not the default. Out of the box, the pulse output was configured at 100 kHz. Ten times slower than the machine design required. If we hadn't caught that during commissioning, the servo would have moved at one-tenth the expected speed, and we'd have spent a full day chasing what looked like a motion fault.
To be fair, this isn't an Omron-specific quirk. Every PLC brand ships with conservative defaults. But it's worth knowing before you start writing code, because "maximum frequency supported" and "maximum frequency configured" are two different numbers.
What the Numbers Actually Said
Here's the final TCO comparison from my spreadsheet:
- Vendor B (cheapest): $12,200 base quote + $240 missing surge arrester + $1,900 estimated labor for compatibility work + $350 future hardware upgrade when the third axis materializes = $14,690 effective total.
- Vendor C (our usual distributor): $15,600 all-in, including the site visit, correctly itemized surge protection, and the NX102 with room to grow.
The difference was $910. Not $3,400. And that $910 bought us a machine that could handle the customer's "someday" without a control panel redesign and a second round of Omron PLC programming.
The "buy the cheapest quote and make it work" thinking comes from an era when control panels were simpler — a handful of relays, one PLC, no networking. Today's machines have EtherNet/IP, safety ratings, and firmware versions that can eat your labor budget if you don't look closely. I get why people go with the cheapest option — budgets are real. But this project was our credibility on the line. The customer didn't care what we saved on the PLC. They cared whether the machine ran.
The Small Order Lesson
There's a broader point here, and it's one I care about as someone who buys a lot of stuff for a small shop. Good vendors treat small orders seriously. Vendor C's quote was $15,600 — not huge by industrial standards, but they assigned their applications engineer to our project for two hours, free of charge. He flagged the surge arrester spec before we signed. He pointed out the pulse output configuration issue during the site visit. He didn't have to do any of that.
When I was starting out, the vendors who took my $500 orders seriously are the ones I still call for $50,000 orders. Small doesn't mean unimportant — it means potential. That's not a feel-good line. It's how I've built my vendor list over six years of tracking every order.
What I'd Tell You If You're Pricing a Similar Project
If you're quoting an Omron PLC system for a small build, here's the short version of what I learned:
- Ask what "surge protection" actually includes. A surge arrester and a surge protector are not interchangeable, and you may need both. One generic line item usually means one is missing.
- Check the pulse output maximum frequency in the actual configuration, not just the datasheet. The default is often far below the ceiling.
- Quote the robot control panel as its own line item. That's where integration surprises hide — communication protocols, extra I/O, grounding questions.
- Run the TCO, not just the sticker price. Include the labor hours you could burn compensating for equipment gaps, and the cost of a future upgrade.
The machine shipped two weeks late — partly my fault, because I spent time chasing a cheaper quote that turned out not to be cheaper. If I remember correctly, the final invoice from Vendor C came to $15,620 including a couple of minor connector additions. It ran fine. The customer ordered a second cell in Q1 2025, and we quoted it with the same NX102 and the properly itemized surge protection. This time the quote went out before they asked.
That's the metric I track in the end. Not the invoice total. The reorder rate. That's the number our $15,600 purchase protected.
