The $4,200 Siemens PLC Mistake I Still Think About

I remember the exact Thursday morning in February 2023, mostly because I thought I was going to finish the quote early and grab lunch.

The job wasn't big. A food processing plant about forty minutes from our office wanted to upgrade their ten-year-old S7-300 line. New sensors, new HMI, a program that didn't freeze every Tuesday at noon for no reason. I was handling the technical scope, which meant I was picking the hardware.

I was eight months into my role. I knew just enough to be dangerous. I'd programmed S7-1200s on three previous projects. TIA Portal felt like a second language. So when I spec'd the hardware at $1,850 and the client approved it, I thought I had this one handled.

We commissioned in March. Clean signals, clean HMI, customer signed off. The plant manager shook my hand in the break room.

Everything looked fine.

That was the problem.

Background: What I Thought I Understood About Siemens PLC

In 2023, Siemens held somewhere between 35% and 40% of the global PLC market, depending on which analyst report you read. That meant thousands of engineers were making the same kind of hardware-selection decisions I was making, across the same dizzying product family. I thought reading TIA Portal documentation cover to cover meant I understood the catalog.

It didn't.

Here's the thing about knowing how to program a Siemens PLC: it tells you almost nothing about knowing which Siemens PLC to buy for a given job. I had confused fluency in one with fluency in the other. Those are very different skills.

I'll fast-forward through the part where I found out.

August: The Phone Call

"We're adding a high-speed packaging line," the same plant manager told me. "Servos need to do synchronized motion. Cam synchronization, flying shear. Can your PLC handle that?"

My first thought was: how many amps are we talking about?

My second thought was: let me open the selection matrix.

The S7-1200—even a fully loaded CPU 1214C—doesn't support advanced motion control. It does point-to-point positioning, basic speed control, and some closed-loop work. But cam synchronization and flying shear? That's S7-1500T territory. It says so right in the selection guide. The column I'd never really looked at, because why would I have? I was buying for today, not for whatever the customer might do next year.

The price difference: upgrading from a 1214C to a 1511T-1 PN was about $4,200 in hardware. Actually, $4,350 once we paid expedited shipping on the 1500-series front connector. Plus rewiring, because the terminal blocks are completely different, so every field wire had to be pulled and landed again. Plus three days of downtime the customer hadn't budgeted for.

I had to say that number out loud on a phone call.

Total cost of the mistake: roughly $4,600 by the time I added up urgent hardware, labor, and a partial credit I gave the customer to keep the relationship intact. That doesn't include the three days of lost production on their end.

They didn't yell. That silence was worse than yelling.

The Lesson I Actually Needed

After that, I created a rule for myself. Every selection, I check the customer's 24-month roadmap, not just what they need in the next 12 months. I don't just note it "for later"—I open the selection matrix and verify specifically: if they need X, will this model survive?

But the rule wasn't the real lesson.

A few weeks later, the same customer came back. This time they wanted to talk about a full plant automation project. Every line, one system, one point of contact. They'd talked to two other integrators but felt we were the only ones who'd been straight with them about the PLC problem.

I wanted that contract. My boss wanted that contract.

I could have said yes. It sounded simple: we knew PLC programming, the customer trusted us, the project was just the same thing at a bigger scale.

But here's what we were actually good at: Siemens PLC programming for single-line retrofits. That's it. Full-plant integration—safety systems across a dozen stations, distributed I/O, multi-line coordination—we'd done maybe two in five years, and both had gone sideways in ways I'd rather not go into.

So I called a Siemens system partner we'd worked with before. We put together a joint scope: we'd handle the PLC programming for the two existing lines, they'd handle the new line integration, safety validation, and ongoing support.

The customer signed. Then they said something I still think about: "I appreciate the honesty. I would have been angrier if you'd said you could do everything and then screwed it up."

That's what the $4,200 actually bought.

Where Expertise Ends (And Why That's Fine)

I've seen a lot of vendors—maybe I've been this vendor—treat "this isn't our strength" like a broken sentence. Something that costs you the deal. In practice, it does the opposite. It earns you the right to be believed about everything else. The vendor who says "this isn't our strength, here's who does it better" gets trusted on the parts that are their strength. That sounds like a compromise. It's actually a trust strategy.

Mind you, I'm not saying we can't do anything. I'm saying that some requests shouldn't be PLC projects at all, and customers often can't tell the difference. One client asked us to program a PLC for an RV power surge protector. Fine—it's a control problem in the sense that a fish is a swimming problem. A $40 timer module handles it better. Another engineer insisted we build a PLC-controlled enclosure for a Tesla Model 3 air filter assembly (a concept display, don't ask). We passed on both. Not because we couldn't. Because the tool was wrong.

For people who ask what PLC programming even is—it's structured logic (ladder, function block, or structured text) that tells a machine what to do next. But the "what to do next" needs to be worth industrial-grade hardware. An RV surge protector isn't.

So here's the question I ask now before we take on a project: is this something we actually do well, or just can do?

If the answer is "can," we say so, and we refer the customer to someone who does it well.

That policy has cost us deals. Five years in, I'm comfortable with that. It's made the jobs we do keep worth the money customers pay for them.

A Short Checklist for Your Next Siemens PLC Project

Before we quote any Siemens PLC job now, we run through the same four questions with the customer:

1. What's the 24-month expansion plan for this line? (Not the 12-month plan. The 24-month one.)
2. Did anyone use the words "high-speed," "synchronized," "cam," or "flying shear"?
3. Is this primarily a PLC programming job or a systems integration job?
4. If it's the second one, do we do it well, or just can we do it?

If the answer to question four is "can," we pick up the phone and call the person who does it well.

The $4,200 was the most expensive lesson I've paid for in this industry. It taught me something no Siemens catalog will ever print: sometimes the most useful thing a supplier can say is that you should call someone else.

"The vendor who said 'this isn't our strength—here's who does it better' earned my trust for everything else."