When I first started reviewing automation project deliverables, I assumed the biggest risk was the programming itself. Wrong code, wrong I/O mapping, wrong safety logic. So I focused on the TIA Portal blocks and the S7-1500 configuration files, and I let the “boring” stuff slide—the manual version, the lifecycle support status, the power supply specifications.
My first wake-up call came during a Q2 2023 audit. A small integrator had shipped a control cabinet with a Siemens PLC that was already two years past its standard support end date. The customer—a small manufacturer running a single packaging line—had bought it on a trade show discount. The integrator’s quote was $200 cheaper than the next competitor. That $200 saved on the hardware cost them $6,800 in downtime when the PLC failed and Siemens wouldn’t issue a replacement without a valid support contract. The manufacturer had to scramble for a gray-market spare, and the line was down for eleven days.
Not ideal. Expensive, actually. That experience shifted my whole approach. Now I review roughly 200 unique automation procurement packages annually, and I’ve rejected about 12% of first deliveries in 2024 alone—mostly because of hidden lifecycle risks that looked like “cost savings” on paper.
The most common complaint I hear from customers—especially small ones—is: “I’ve got a PLC on my bench but I can’t find the latest manual. The link I used last year gives a 404.” That’s the surface symptom. They think the problem is a broken PDF link. The real problem is that they never verified the lifecycle status of the hardware they bought.
It’s tempting to assume that any Siemens PLC you can buy on Mouser or DigiKey is “current.” But the lifecycle of a product like the S7-1200 or S7-1500 follows a defined timeline: Active → Product Transition → Service & Support → Phase-Out → Legacy. Once a product enters the “Product Transition” phase, manufacturing continues but innovation stops. In “Service & Support,” you can still get replacements, but no further software updates. After that, you’re on your own.
Let me give you a specific example. In our Q1 2024 quality audit, we reviewed 47 PLC orders across six integration partners. Three included CPUs that had already entered the “Product Transition” phase—one of them, an S7-1200 1214C, was within six months of its phase-out date. The integrator had quoted it because they had inventory and wanted to clear stock. The customer, a startup with a $15,000 prototype budget, had no idea. They would have designed their entire control software around a platform that would lose TIA Portal updates within a year.
That’s the deep problem: not the missing manual, but the missing lifecycle awareness. The manual search is just the symptom.
A large OEM with a dedicated procurement team can absorb the risk of an obsolete PLC. They have spares on the shelf, support contracts, and enough leverage to get expedited replacements. But a small company—the one buying a single S7-1200 for a custom machine—has no margin for error. When that PLC fails three years later and the “lifetime buy” window has closed, they’re looking at a redesign, not a replacement.
I’ve seen this pattern repeat. The vendor who offers the lowest quote is often the one selling hardware that’s close to phase-out. They’re not malicious; they’re just clearing inventory. But the small customer, who doesn’t know to ask for the lifecycle status, pays the price later. And by then, the vendor has moved on to the next order.
That’s why I advocate for what I call “small-friendly lifecycle transparency.” Every quote, no matter the order size, should include the product’s current lifecycle phase and the estimated support end date. Siemens publishes this data on its Industry Online Support portal—it’s public. The integrator just has to copy it into the quote.
When I implemented this requirement in our procurement specs in 2022, the rejection rate for lifecycle-related issues dropped from 18% to 4%. The cost? Zero. Just a five-line addition to the RFQ template.
Here’s where the seemingly unrelated keywords start to connect. A PLC that’s past its support window is more vulnerable—but even a supported PLC can be killed by power quality issues. I’ve seen a $400 surge destroy an S7-1500 CPU because the cabinet had a cheap power strip without surge protection. The integrator had used a surge protector power strip with USB (intended for a desk, not a factory floor) because it was $12 cheaper than an industrial-grade surge suppressor.
The machine was down for two days while we sourced a replacement CPU. The lost production was worth about $9,000. The installation engineer told me, “I didn’t think power was that critical.” He assumed all surge protectors were the same. Not true—and the electrical socket types matter too: a Type F (Schuko) socket used in Europe vs. a Type B (NEMA 5-15) in the US can have different grounding configurations, affecting how the surge suppressor works.
Then there’s the battery. Siemens PLCs (S7-1200 uses a rechargeable lithium battery, S7-1500 uses a CR2032 coin cell for the real-time clock) need to be checked. I used to think you replace the battery only when the PLC complains. Actually, you should check it periodically with a multimeter. I had a case where a maintenance technician assumed the battery was fine because the PLC was still running. But the backup time had dropped from 20 days to 2 hours. When we had a power outage over a weekend, the program was lost. The how to check a battery with a multimeter skill is something every field engineer should have: measure voltage under no load (should be 3.0V or higher for a CR2032) and under a small load (below 2.7V means replace).
These details—lifecycle status, surge protection, socket type, battery voltage—are the “boring” stuff. But they’re where real costs hide.
Let me put it in concrete numbers. I ran a blind cost comparison last year across three typical small-project scenarios:
Over three years, Scenario B had a 22% probability of a downtime event (based on our field data), with an average cost of $4,300 per event. Expected loss: ~$950. So that $85 “savings” turned into a net loss of $865. Worse, the small customer had no support options because the PLC was phase-out.
The numbers said go with the budget option. My gut said something felt off—the vendor was evasive about lifecycle dates. I went with my gut. Turns out the “slow to reply” was a preview of “slow to support.”
None of this is new, but it’s rarely applied to small orders. Here’s a minimal checklist I now include in every specification, from a $200 S7-1200 kit to a $50,000 automation project:
Three years ago, I would have said “you don’t need all that for a simple PLC order.” I was wrong. My initial approach to vendor selection was completely wrong—I thought lowest quote wins. The total cost of ownership includes downtime, and downtime costs 50x the hardware price.
That’s why I’m a strong believer in serving small customers with the same diligence. When I was starting out, the vendors who treated my $200 orders seriously are the ones I still use for $20,000 orders. Small doesn’t mean unimportant—it means potential.
If you’re buying a Siemens PLC today, take 10 minutes to check the lifecycle status. While you’re at it, check the surge protector rating and the battery voltage. Your future self—and your production line—will thank you.