There's No "Best" PLC — Here's How to Find Yours
I've spent the last eight years coordinating emergency automation support. In that time, I've handled more than 200 rush jobs — including 14 same-day turnarounds where a production line was completely dead and the clock was bleeding money. If there's one thing I've learned, it's this: the "best" PLC doesn't exist. What exists is the right PLC for your specific scenario.
And in 2025, that scenario matters more than ever. Siemens has the S7-1200 G2 making real waves in compact automation. Beckhoff keeps pushing PC-based control into territory that traditional PLCs used to own. And thousands of legacy S7-300/400 systems are hitting end-of-support this year, forcing migration decisions on engineers who'd rather not touch a working system.
So instead of giving you a single recommendation (which would be lazy and probably wrong for your situation), here's how I break it down. Three scenarios. Three different answers. And a clear way to figure out which one you're in.
Scenario A: You Need It Running by Monday
This is my world. A machine goes down on Friday afternoon. The OEM can't get a replacement for six weeks. Production is losing $12,000 an hour. You need a PLC that's on the shelf, documented to death, and supported by an ecosystem that doesn't require a PhD to navigate at 2 AM.
For this scenario, the Siemens S7-1200 G2 is hard to beat. Not because it's the most powerful controller on the market — it isn't. But because when you're in triage mode, you're not optimizing for performance. You're optimizing for time-to-running.
Here's what I mean in practice. In March 2024, a packaging client called at 6 PM on a Thursday. Their S7-1200 (first-gen) had fried a communication module during a power surge. They had a product launch the following Tuesday. Normal lead time on the replacement module from the distributor: 10 days. We found a used module from a local integrator, but the firmware was mismatched.
The fix? We flashed the firmware using TIA Portal V18, restored the project from a backup the client didn't know they had (long story), and had them running by 2 PM Friday. Total downtime: under 24 hours. That's not because the S7-1200 G2 is magical. It's because Siemens has enough market penetration that you can find parts, documentation, and experienced help almost anywhere.
Before you even swap hardware, though, you're probably testing wiring. If you're staring at a multimeter wondering what the symbol for continuity is, it's the little sound-wave icon (or the one that looks like a diode with sound waves coming off it). Touch your probes together — if it beeps, you've got continuity. That's your first check before you start blaming the PLC.
And keep your field kit stocked. Mine has spare fuses, a good multimeter, and a 12V gel battery charger for testing backup power circuits. I also keep a cigarette lighter battery charger in the truck — not glamorous, but when your laptop dies on a remote site with no outlet, you'll thank yourself. (Note to self: buy a second one, the last one walked off.)
Where this scenario breaks down: if "running by Monday" means "custom motion profile with sub-millisecond cycle times," the S7-1200 G2 will frustrate you. That's not what it's built for.
Scenario B: Throughput Demands High-Speed Motion Control
Here's where I'll be honest: this is not Siemens' strongest territory. If your application is high-speed packaging, CNC-style interpolation, or anything where cycle times are measured in microseconds and your motion axes need to stay perfectly synchronized, Beckhoff's TwinCAT ecosystem is genuinely compelling.
I went back and forth on this for two weeks in 2023. We had a client building a high-speed pick-and-place system. The spec called for 8 axes of synchronized servo control at 0.5 ms cycle times. On paper, an S7-1500 with technology objects could handle it. But my gut said Beckhoff. The client wanted Siemens because their maintenance team already knew TIA Portal.
We went with Siemens. It worked — but we spent three extra weeks in commissioning dialing in the motion performance. A Beckhoff-based system would have been faster to commission for that specific application. The client's team could maintain the Siemens system more easily, which was worth something. But if that project had been on a tighter timeline, I would have pushed harder for Beckhoff.
So if you're squarely in Scenario B — high-axis-count, high-speed motion, PC-based control architecture — Beckhoff deserves a serious look. This isn't a knock on Siemens. It's just acknowledging that different tools are optimized for different jobs. (And if you're doing standard discrete automation with a few axes, the S7-1500 is perfectly capable.)
Scenario C: You're Migrating from S7-300/400 and Nobody's Happy About It
The most frustrating part of PLC migration: the existing system works fine. You'd think "if it ain't broke, don't fix it" would apply. But then Siemens announces end-of-support, and suddenly you're planning a migration you didn't ask for.
After the third S7-300 migration I coordinated in 2024, I was ready to write a book about it. What finally helped was building a repeatable process.
For this scenario, the S7-1500 is the natural target. TIA Portal handles the migration tools reasonably well, the programming model is familiar to anyone who's touched Step 7, and the ecosystem support is there. But — and this is important — don't let anyone tell you it's a simple lift-and-shift. It isn't.
The I/O wiring is different. The communication protocols have changed. And if your original S7-300 program was written by someone who retired in 2015 and never documented anything, you're in for a treat. (Surprise, surprise.)
My recommendation for Scenario C: budget 30-40% more migration time than your integrator quotes. Not because they're wrong, but because nobody can see the landmines until they start digging. We lost a $48,000 contract in 2023 because we bid an S7-300 to S7-1500 migration at what seemed like a reasonable 6 weeks. It took 11. The client was understanding, but we ate the overage. That's when we implemented our "no fixed-bid migrations without a site audit" policy.
How to Figure Out Which Scenario You're In
Here's the part where I'm supposed to give you a clean checklist. Instead, I'll give you the three questions I actually ask:
- What's the cost of downtime per hour? If it's over $5,000, Scenario A rules everything. You optimize for availability and support ecosystem, not specs.
- Are you pushing motion performance boundaries? If your cycle times are under 1 ms or you have more than 6 synchronized axes, look hard at Scenario B. Be honest with yourself.
- Is this a forced migration or a new design? Forced migrations default to Scenario C. New designs can be A or B depending on the performance requirements.
If you're still unsure, consider this: the S7-1200 G2 works for about 80% of standard discrete automation applications. It's the safe default when you don't have extreme requirements. If you're in the other 20% — either extreme motion performance or large-scale migration — that's when the decision gets interesting.
"I've tested six different PLC selection frameworks over the years. The one that actually works is: figure out what you can't afford to lose, then pick the platform that protects that."
The Honest Limitations
I recommend Siemens PLCs — specifically the S7-1200 G2 for compact applications and the S7-1500 for larger systems — for most of the scenarios I see. But here's where I'd tell you to look elsewhere:
- You need sub-millisecond deterministic motion at scale. Beckhoff's PC-based architecture has real advantages here. This isn't a sales pitch against Siemens; it's just physics and architecture.
- Your budget is under $800 for a complete controller setup. The S7-1200 G2 isn't the cheapest option on the market. If cost is the dominant constraint, there are alternatives that work fine for simple applications.
- You're fully standardized on another ecosystem and it's working. Switching costs are real. If your team knows Rockwell or Mitsubishi and your systems are running well, don't switch just because Siemens has market share.
The difference between a good outcome and a frustrating one usually isn't the PLC brand. It's whether you picked the right scenario before you picked the hardware. Get that part right, and most of the platform debates become much less important.
Pricing and availability data referenced from distributor quotes (Q1 2025); verify current lead times with your local supplier. Product specifications are based on published Siemens and Beckhoff documentation as of January 2025.