Back in March 2024, I was standing on the plant floor with water pooling around my safety toe and a control panel that had just gone dark. Our old control panel for sprinkler system had been acting up all winter, but this time it wasn't a nuisance. It was a shutdown. The panel was built around relays and a drum timer that nobody had stocked since 2011. My first thought was to find a like-for-like replacement. I couldn't have been more wrong.
The quote that made me question everything
I'm the procurement manager at a 180-person packaging company. I've managed our maintenance budget—roughly $1.4M a year—for the past six years. So when a piece of equipment fails, my first question is always: what's this going to do to the annual cost line?
We called in a local integrator. They quoted $18,500 for a new master control panel, including programming, testing, and installation. That sounded high, but not absurd. Then a second integrator quoted $14,200. "This is more like it," I thought. Then I asked for the complete breakdown.
That's when the red flags appeared. The $14,200 quote didn't include a software license, or the "commissioning" visit, or the overtime for the weekend startup, or the terminal blocks. Wait—terminal blocks? Yes. An itemized list of additional fees started to look like a second invoice. By the time I added everything, the low quote was roughly $17,900. The transparent $18,500 quote from the first integrator was actually the cheaper option.
I've learned to ask 'what's NOT included' before I ask 'what's the price.' That one question is worth more than a spreadsheet of unit prices.
That experience didn't just save me $400. It pushed me to question what we were actually paying for. A big chunk of both quotes was engineering labor. So I asked our senior maintenance tech, Rob, whether the project was something we could build ourselves.
Why we built our own master control panel
Rob didn't hesitate. "We already run Omron PLCs on the wrappers," he said. "We've got Sysmac Studio on the laptop I'm using. I can program ladder logic. We can build this."
I was skeptical. In my experience, "we can build this" has led to a few expensive procurement disasters. But Rob had a good point: the machine that runs our carton wrapper uses an Omron PLC NX (NX102 series, I think it was). We already had the software, the cable, and the local distributor's support number. We weren't starting from zero.
So we made the case to management. Instead of buying a completed control panel for sprinkler system from an outside vendor, we'd build a new master control panel in-house. The plan: one Omron PLC NX as the brain, one digital output module, a power supply, a small HMI, and a handful of contactors. We'd set it up on the bench, test it for a week, and only then install it in the field.
It was a risk. But the numbers looked compelling. Parts were roughly $3,000. Internal labor at burdened rates was maybe another $2,500. Total was a little over $5,500. That was about a third of the outsourced quote, and we'd own the knowledge afterward.
The programming step I was afraid of
The part I dreaded most was the programming. Rob knew relays and standard electrical troubleshooting. He wasn't an expert in Omron's NX series. But we had something even better: a project to learn on.
The basic programming logic of Omron PLC is actually pretty close to old-school relay control. You read the input signals, you do the logic, and you energize the outputs. In ladder logic, it looks almost like a relay schematic—contacts on the left, coils on the right, rungs in between. If you can understand why two contacts in series make an AND, and two contacts in parallel make an OR, you're about halfway there.
The part that took longer was understanding how the NX series handles variables and tags instead of fixed memory addresses. With older PLCs, you might have a physical input at address 0.00. On the NX, you can name that input "pump_flow_switch" and use it in multiple places, then let the software handle the mapping. It's a better way once you stop fighting it. According to Omron's documentation, the NX series supports ladder, structured text, and function blocks. We stuck to ladder because it was the language Rob could review quickly.
We spent about four evenings building the program. The first version had a huge bug: the pump started before the low-level switch opened. We caught it in the bench test, not in the field, which is exactly why you buy a test cable and a spare afternoon.
Testing voltage with a multimeter (the step I almost skipped)
Before we connected the PLC to anything real, Rob and I went through the panel circuit by circuit. This is where I learned how to test voltage with a multimeter—not just to see whether a wire is live, but to verify that the correct voltage is present at the correct terminal. We checked 24 VDC at the power supply terminals, 120 VAC at the pump contactor coils, and continuity across the emergency stop relay. We checked for shorts between terminal rails. We did it twice.
The first time we powered up the Omron PLC NX, I was holding a multimeter like a security blanket. Nothing smoked. The green LED came on. The HMI displayed the first screen. Rob laughed at me. "That's the boring part," he said. He was right, but I didn't care. Boring is good.
That habit has already paid off. In November, we had a false alarm on one of the sprinkler circuits. Instead of guessing, Rob pulled out the multimeter and in ten minutes found a loose terminal. No service call, no downtime.
What the whole project cost
Let me be honest with numbers because I'm a cost controller and that's what I do. Here's the ballpark:
- Omron NX PLC CPU and digital output module: ~$1,850
- Enclosure, contactors, power supply, terminal blocks, wire, labels: ~$780
- Small HMI for manual override and timer adjustments: ~$350
- Miscellaneous (fuses, din rail, cable glands): ~$180
- Internal labor (40 hours at burdened rate): ~$2,400
The total came to about $5,560. Add the week of testing downtime—some of which was planned maintenance downtime, so it wasn't entirely a loss—and we still came in under $8,000. The best outsider quote we received was $18,500. Even with a generous view of our own labor, we saved close to $10,500 on that one project.
I know what you're thinking. "Great, it worked for you, but you had an electrician who already knew PLCs." That's fair. My experience is based on one project at one company. If we didn't already have a Sysmac Studio license and a maintenance team with electrical troubleshooting skills, the calculus might be different. I can only speak to our situation.
What I'd tell another cost controller
Three things, bottom line.
First, transparency in pricing is a competitive advantage. The first integrator didn't win the bid—we took the work in-house—but their detailed quote made it possible for us to see exactly what we could do ourselves. The vendor who hides fees behind a low base number is either hoping you won't ask or assuming you won't calculate. Both are bad signs.
Second, cost per piece is not the same as cost per project. Our master control panel cost more in parts than the estimate for "just a PLC module." But the total cost of ownership was way lower because we now have the program, the drawing, and the knowledge. We don't need to pay someone $160 an hour to change a timer delay.
Third, don't be afraid of the learning curve. The basic programming logic of Omron PLC is something a decent maintenance tech can learn in a month, and the online resources from Omron are honestly pretty good. You don't need a computer science degree to read a timer and a counter.
We've been running that control panel for sprinkler system for 11 months now (as of this writing, February 2025). It's been down once, and we fixed it in an hour. That's the sort of result I like to put on a cost tracking sheet.
