I've said this to every engineer I've worked with, and it still gets me weird looks: I buy PLCs for a living, but I don't know enough to specify one. I'm not a controls engineer. I'm not a safety engineer. I'm a procurement manager who has spent six years and about $1.8 million on automation components, and the biggest lesson I've learned is that the most expensive thing in a project is the confidence that you know what you're doing when you don't.
That may sound like a weird thing to say in an article about Omron PLC. But it's the whole point. I've bought Omron NX, NJ, CJ, CP1L, and CP1H units. I've worked with clients who needed a scissor lift control panel that talks to a PLC, and clients who needed a safety-rated controller because the old one was past its 'use by' date. I can manage the purchase. I cannot walk into a control panel and wire it. Once I accepted that, my procurement decisions got a lot better.
Lesson one: the PLC is the beginning, not the box
In March 2023, I made a mistake that I still think about. We had an order for twenty PLCs for a packaging line. The engineer specified a certain CJ series model. I found a slightly different model that looked compatible. Same family. Same I/O count. Lower price by about $48 per unit. I did the math and felt like a hero.
Turns out, the I/O count wasn't the whole story. The communication protocol was different. We spent an extra 40 hours on adapters and programming to make the alternate unit connect to the existing network. Total extra cost: $1,150 in parts and about 40 hours of labor. Actually, when we counted the downtime on the packaging line, it was closer to $4,200. I don't have hard data on how many companies make this same mistake, but I know I'm not the only one who's done it.
Now I don't pretend to know every detail about the Omron PLC communication protocol. EtherNet/IP, EtherCAT, Modbus—I can say the words, but I can't tell you how the stack works. What I've learned is that 'we'll make it work' is not a technical spec. When you're buying automation parts, the protocol matters as much as the processor speed. Actually, it matters more, because a mismatch will eat your labor budget before you even open the manual.
Omron safety PLC: not a place to cut corners
This is where I really hit my boundary. I know enough about functional safety to know that I don't know enough. The datasheets for Omron safety PLC units list SIL and PL ratings, which I've learned to check before comparing prices. I don't know every detail of the certification standards from memory. What I know is that a safety-rated controller is designed to fail in a predictable way, not just to process logic faster.
One vendor once offered me a non-safety PLC for a job where a safety-rated one was specified. The quote was about 15% lower. I didn't reject it because I'm a standards expert. I rejected it because I know what I don't know. If someone gets hurt because I saved a few hundred dollars? That isn't a procurement decision. It's a responsibility I have no business taking.
I've also asked Omron's application support a few questions that were probably very basic to them. They didn't make me feel stupid. They said, 'Talk to one of our engineers.' That's the right answer. A supplier that knows its own boundaries is a supplier worth paying.
When the part is simple, the decision still isn't
The same mindset applies to things that look simpler than a PLC. A few months ago, a maintenance supervisor asked me to source a scissor lift control panel. My first instinct was to search for the term and buy the first one that would ship quickly. But I stopped. I asked him to spec it. He asked about platform height, limit switches, and whether the panel needed to connect to the machine's existing safety circuit. I hadn't thought of any of those questions. Not even one.
That's exactly the point. If I had bought the panel on price alone, we probably would have spent the savings on return shipping and downtime. Not a good trade.
The same thing happened when I searched for the types of multimeter. I want to say there are three main types: digital, analog, and clamp. Don't quote me on that. I gave up and asked the electrician. He didn't need a 'types of multimeter' article. He needed a specific model with the right current rating and safety category. The listicle I almost bought from was exactly the sort of simplification that costs money.
And then there's the question I keep seeing in forums: can you plug a surge protector into a surge protector? I am not an electrician, so I'm not going to answer that. But as a buyer, I know that when an electrical question starts with 'can you,' the right move is to ask someone who actually knows—not to order something off an online forum's recommendation. Power surges are exactly how you end up needing a new PLC.
Look, I have mixed feelings about sourcing from any single brand. There have been times when an Omron quote was not the lowest, and I had to explain to my boss why. But I've learned that the total cost of ownership includes the cost of being wrong. If the part is specified correctly and the support is there, the 'cheapest option' is a distraction. I'm not saying Omron is flawless. I'm saying I've stopped pretending that price per unit is the only number in my spreadsheet.
'So you're telling me to over-spec everything?' No.
Here's the objection I get when I explain this: 'You're the cost controller. Aren't you supposed to find savings? If we never take a risk, we'll never cut costs.'
I hear that. But I'm not saying avoid risk. I'm saying avoid guessing. A cost controller's job is to compare apples to apples, not to eat the apple without checking if it's real.
The vendor who says 'this isn't our strength—here's who does it better' earns my trust for everything else. I've had that happen twice. Once when a representative told me I didn't need the premium cable, and once when an engineer said 'you should use a different safety relay for that application.' Both of those conversations saved money. The vendors who say 'yes, absolutely, we can do that' for everything? Those are the ones I double-check.
Bottom line
I still buy Omron PLCs. I still compare prices, question specifications, and push back on lead times. But I've stopped pretending that my title gives me the authority to make engineering decisions I'm not qualified to make.
The most professional thing I can say is: 'I don't know this part. Help me understand what I'm buying.' That's not weakness. That's the whole job.
If you're sourcing automation parts, you don't have to be an engineer. You have to be curious enough to ask, humble enough to listen, and brave enough to walk away from a deal that's too cheap to be safe. That's the lesson a scissor lift control panel, a multimeter question, and a surge-protector debate all taught me.
The smartest money I've ever spent wasn't on a better PLC. It was on the words 'I don't know.'
