-
There's no single right Siemens PLC — it depends on where you sit
- Scenario A: You're keeping an S7-300 line alive
- Scenario B: You're building a new line with moderate complexity
- Scenario C: You're building a line that needs OT/IT integration or long-term cyber compliance
-
How to figure out which scenario you're actually in
There's no single right Siemens PLC — it depends on where you sit
Last year I helped audit a mid-size packaging plant's procurement history. Somewhere in that $180,000 of cumulative PLC-related spending across six years, I counted four "new" controller purchases that could have been avoided if the team had just agreed earlier on what their actual upgrade window looked like. Two of those ended up as S7-300 spare parts anyway. One was a premature S7-1500 upgrade on a line that only runs 8 digital I/O cards. The fourth was an S7-1200 retrofit that everybody — including me — thought would be cheaper than it was.
That's not an argument for or against any one Siemens model. It's an argument for separating your decision into scenarios before you start comparing quotes. Because the honest answer to "which Siemens PLC should we buy in 2025" is: it depends — and here's how to figure out which situation you're actually in.
I'm going to give you three scenarios. Each has a different cost logic, different hidden traps, and — in at least one case — a recommendation that goes against what most vendors will tell you.
Scenario A: You're keeping an S7-300 line alive
A quick S7-300 overview (for context)
Siemens launched the S7-300 family back in 1994. It's been the workhorse of mid-range European automation ever since — tens of thousands of installations in food processing, packaging, water treatment, material handling. If you've worked in a plant built between roughly 1998 and 2015, you've probably touched an S7-300.
As of early 2024, Siemens has issued phase-out notices for most S7-300 components. That doesn't mean the controllers stop working tomorrow — installed bases keep running for another decade or more — but it does mean official spares availability is shrinking, and the pricing curve on new-old-stock modules is heading in a direction you want to catch early.
The cheapest thing is not always the "cheap" thing
Here's a surface illusion I see constantly in legacy-line procurement: From the outside, refurbished S7-300 modules look like a 40-60% discount on the official list price. The reality is that around a third of the refurbs we've tested fail within the first year — and the testing burden falls on you.
I'm not saying never buy refurbished. I'm saying the TCO math on a refurb S7-300 module is different from the TCO on a new one. You need to budget for: incoming test/bench time (typically 2-4 hours per module), a degraded warranty (3-6 months vs. 12-24 for new-old-stock), and a higher probability of a second swap inside 24 months.
"We didn't have a formal incoming-inspection process for refurbished S7-300 parts. Cost us when a batch of three CPU 315 units arrived with inconsistent firmware. Two of the three were unusable on our specific line until we reflashed them — which took another two days."
That story is me. It's why our procurement policy now requires bench-verification on every refurbished S7-300 module before it goes into a critical cabinet, and why we hold a small three-month buffer stock of the modules we most commonly lose.
The counterintuitive call on S7-300
If your S7-300 line is going to run for another 3-5 years and you have maybe 10-15 controllers across your plant, my honest opinion is that you should not rush the upgrade. Buy new-old-stock modules for the critical paths, build a spares kit, and revisit annually. The math on a premature upgrade — meaning one you could postpone — rarely works in your favor once you factor in re-engineering time, panel rewiring, and TIA Portal migration labor.
That said, if a specific controller has failed twice in 12 months, that's a different conversation. Fail-frequency changes the math.
Scenario B: You're building a new line with moderate complexity
Why the S7-1200 usually wins here
For a new line with, say, 30-80 I/O points, a handful of analog inputs, and moderate motion or HMIs — the S7-1200 is the model I'd start with. It's been in continuous production since 2009, gets software updates regularly, and integrates with TIA Portal without the license overhead you get on the higher tiers.
The catch — and this is where I have a strong opinion — is that the S7-1200 is often the wrong answer at the moment of purchase and the right answer at the moment of commissioning. People forget to include the training time, the portal license tier (Basic vs. Comfort), and the re-integration work when they compare it against a cheap third-party controller.
Where the hidden costs actually live
- TIA Portal licensing. The Basic license covers the S7-1200 but you'll want Comfort the moment you do any significant HMI work. That's a real line item — budget for it before you decide the S7-1200 is "cheaper."
- Firmware compatibility. A new S7-1200 CPU shipped in 2025 may not talk to firmware on an older TIA Portal install on your engineering workstation. Plan for a software version sync.
- Physical infrastructure. The same circuit breaker box, surge protection, and cabinet wiring you'd spec for any PLC still needs to be spec'd. The controller is maybe 15-20% of the cabinet cost — don't confuse the two.
I said something along the lines of "standard spec" to a supplier on one of these builds a couple of years back. They heard "whatever fits." Result: the S7-1200 arrived with a different digital-input voltage configuration than our existing panels, and we ended up re-specifying half the sensor wiring. Two-week delay, plus a partial re-order. The lesson wasn't about Siemens — it was that "standard" is not a spec.
Scenario C: You're building a line that needs OT/IT integration or long-term cyber compliance
When the S7-1500 premium actually pays off
If your new line needs to talk to an MES, an ERP, or a cloud data pipeline — or if it's going into a facility that's subject to IEC 62443 cybersecurity requirements — the S7-1500 is where I'd point you. Not because it's "better." Because the integrated diagnostics, the native OPC UA support, and the cybersecurity capabilities are already inside the controller and don't require a separate gateway.
The S7-1500 doesn't make sense for a 40-I/O point standalone machine with a single HMI. It becomes very hard to beat the moment you start pricing the alternative: an S7-1200 plus an OPC UA gateway plus a separate firewall plus the integration labor for all three.
The regional market share consideration (why it matters to a buyer)
Here's something most procurement-oriented content skips: Siemens PLC market share varies significantly by region, and that variance affects your parts strategy. According to 2024 market analyses from firms like Omdia and Interact Analysis, Siemens holds roughly 30-35% of the global PLC market by revenue, but the regional numbers are more uneven. In Western and Central Europe the share is commonly quoted around 40% (higher in some Eastern European markets), while in North America it's closer to 20-25% because of Allen-Bradley's dominant position.
Verify current figures before you use them in a business case — market studies update quarterly. But the practical implication is real: your spares availability, lead times, and secondary-market pricing for any given S7 model depend on where you are. S7-300 modules are far easier to source in Germany than in, say, a Southeast Asian market where the installed base skewed toward Mitsubishi or local brands. If you're running a multi-region operation, you cannot assume your European spares strategy ports cleanly to your Asian sites.
How to figure out which scenario you're actually in
Three questions. Be honest on each — the wrong answer here costs a lot more than the wrong controller.
- What's your existing installed base? If you already have S7-300 controllers running, and the code is stable, Scenario A is probably you — even if some vendor is telling you otherwise. Migrating an existing S7-300 line is almost never the cheapest path in the first 36 months.
- What's your growth and integration horizon over the next 3 years? If you expect to add at least one new line with significant OT/IT integration requirements in that window, don't buy the middle option — buy the S7-1500 now and pocket the integration savings on the second line. If you don't, the S7-1200 is the right middle.
- What's your "fail twice, replace" threshold? Every plant I've worked with eventually has one: the point at which a legacy component has failed often enough that the repair math bends the curve. Set it explicitly (for us it's two failures of the same module in 12 months) so the decision doesn't get made emotionally at 2 AM during a production stoppage.
The right answer isn't the one that shows up first in a product catalog. It's the one that matches the situation you're actually in, priced on total cost including verification, training, and downtime — not on the sticker on the module. Five minutes of scenario-matching beats five weeks of a procurement you didn't need to run.
