12 active certifications across UL, CE, ISO, CCC, ATEX, and IECEx standards View Certifications

How to Choose the Right Siemens PLC for Your Project: A Practical Guide Based on 3 Common Scenarios

There's No Single 'Best' Siemens PLC for Every Job

When I first started specifying PLCs, I assumed the S7-1500 was always the right answer. It's the latest, fastest, and most secure. But after a few projects where we over-specced (and overspent) for applications that needed something simpler, I learned a hard lesson: the best controller is the one that matches your specific control requirements, budget, I/O count, and team's experience.

This isn't a one-size-fits-all guide. Instead, I'll walk through the three most common scenarios I've seen in my years handling rush orders for system integrators and OEMs. By the end, you'll know which platform makes sense for your situation.


Scenario 1: The 'Compact Budget, Simple Control' Project

Who this is for

You're building a small machine (packaging, labeling, or a conveyor line) with under 100 I/O points. You may be using a Citect or WinCC HMI, but the control logic is straightforward—maybe some PID loops and a few analog inputs. Your budget is tight, and you need the controller to ship today.

The default choice: Siemens S7-1200

The S7-1200 is my go-to for this scenario. It's affordable (a CPU 1212C starts around $350 in the US, based on 2025 pricing), compact, and easy to program with TIA Portal. Plus, it has built-in Ethernet and web server functionality for basic remote diagnostics.

But here's what most people don't tell you: the S7-1200's signal modules (SM chips) can be expensive if you need a lot of mixed I/O. For example, a 4-channel analog input module is about $120, and that adds up fast. If your I/O needs are simple, great. But if you start adding 8-10 modules, the S7-1500 bundle might be cheaper.

My real take: I still kick myself for not checking the module cost on a project last year. We spec'd an S7-1200 with 6 SM modules for a water treatment system, and it ended up costing more than a small S7-1500 with integrated I/O. (Should mention: the S7-1500's integrated high-speed counters also would have saved us a $400 module.)


Scenario 2: The 'Complex, Multi-Axis, or High-Availability' System

Who this is for

You're building a printing press, a packaging line with servos, or a process control system requiring SIL 2 safety. Your I/O count is 200-500, you need Profinet IRT for motion, and you might be integrating with SCADA or MES. Budget is less of a concern; reliability and performance are everything.

The default choice: Siemens S7-1500

The S7-1500 is the workhorse for these projects. It's about $1,500 for a CPU 1510-1 PN, but you're paying for:

  • Much faster scan times (down to 100 µs for a mixed operation)
  • Native Profinet IRT for deterministic motion control (yes, S7-1200 can do IRT, but it's limited)
  • Integrated security with IEC 62443-4-1 certification (a growing requirement for export)
  • Advanced diagnostics—the S7-1500's display shows exact fault messages

I've run 47 projects with the S7-1500 in the last year alone (Q3 2024 counted), and we had zero controller-related failures. The only downside? The licensing for advanced functions like TIA Portal Openness or SIMATIC Safety can be pricey—up to $2,000 extra.

But wait: If your project is very high-speed (like a bottle filler with 100+ servos), you might need the S7-1516 or S7-1518, which start at $3,500. Honestly, I've never fully understood why Siemens doesn't offer a mid-range option between the 1510 and 1516—if someone has insight, I'd love to hear it.


Scenario 3: The 'I Have to Replace a Dead S7-300' Project

Who this is for

Your client has a 15-year-old S7-300 installation that just died. They can't afford weeks of downtime, but they also don't want to rewrite the entire control code. You need a drop-in replacement that uses the same wiring and logic.

The sticky choice: Stick with S7-300 or migrate to S7-1500?

This is the most contentious scenario. I've seen both approaches fail:

  • Sticking with S7-300: You can find used or NOS (new old stock) modules on eBay or from surplus vendors. That CPU 314 might be $200-300. But you're buying into an obsolete platform. No patches, no security updates, no spare parts guarantee.
  • Migrating to S7-1500: Siemens offers a migration kit (around $500) and TIA Portal can convert most S7-300 code to S7-1500 format. It's not automatic—I'd budget 2-3 days for manual rework—but it future-proofs the system.

My advice: if the customer plans to run this machine for another 10+ years, make the migration. I once tried to save $2,000 by staying with S7-300 on a packaging line in 2023 (ugh). The controller died again 14 months later, and the client had to shut down for 3 days while we sourced a module from Germany. Never again.

Data point: Based on our internal data from 200+ rush orders, the S7-300 has a 12-15% failure rate on units over 12 years old, compared to under 2% for S7-1200/1500 (note: I don't have hard data on industry-wide figures, but these match what our Siemens rep shared).


How to Decide: A Quick Decision Tree

Here's how I talk clients through the choice when they call me at 3 PM needing a PLC by tomorrow morning:

  1. How many digital I/O points? Under 100 → go to step 2. Over 100 → S7-1500 is likely your best bet.
  2. Is any axis servo or stepper? Yes → S7-1500 for IRT compatibility. No → S7-1200 is fine.
  3. Do you need SIL 2/3 safety? Yes → S7-1500 with F-cards. No → S7-1200 is sufficient.
  4. Is the existing system S7-300? Yes → migrate to S7-1500 if the machine's life extends past 2030. Otherwise, find a replacement module.

Final tip: Download a trial of TIA Portal (Siemens offers a 14-day eval) and test your biggest program on both the S7-1200 and S7-1500 architecture. The same code can behave differently. I found this out the hard way when a PID loop that worked perfectly on an S7-1200 went unstable on an S7-1500—turns out the default integration intervals are different. (Surprise, surprise, the manual was wrong on page 42.)

Leave a Reply