Your Facilities Budget Has a PLC Problem—Even If You Don't Own a Robot
The "That's an Engineer's Problem" Myth Needs to Die
If you're an office administrator who still thinks PLCs are strictly an engineering concern, you're already making bad purchasing decisions—you just don't know it yet.
I manage facilities and service ordering for a 180-person manufacturer across three sites: main office, production floor, and a warehouse annex. That's roughly $85,000 a year spread across eleven vendors, and I report to both our operations director and our CFO. When I took over purchasing in 2021, I had exactly one rule about anything with a circuit board: forward the spec sheet to maintenance and stay out of it.
That rule worked fine until it didn't. In 2023, we replaced two rooftop AC units and a standby generator controller, and I realized halfway through the quote comparison that I had no idea whether the building automation layer in those systems would talk to anything else we owned. The vendor could have sold me a brick with a Siemens logo on it and I wouldn't have known the difference. That was the moment I started reading about Siemens PLCs—not because I wanted to, but because the equipment I was already buying depended on them.
Here's my argument, plainly: the line between "facilities procurement" and "industrial automation" has basically dissolved. The people signing the purchase orders need to understand what they're signing for.
Free Training Is Real—If You Know Where to Look
I hear the objection already: "I'm not learning ladder logic for a purchasing job." Fair. I'm not suggesting you become a programmer. But the search term "siemens plc training online free" exists for a reason, and I've used those resources—here's the honest version of what's available.
Siemens' official SITRAIN courses are paid, and some of them are not cheap. What most admins don't realize is that Siemens publishes an enormous amount of free material through its Industry Online Support portal—manuals, tech data sheets, application examples, and recorded webinars. The company also offers a trial version of TIA Portal, and its official YouTube channel has walkthroughs that are genuinely useful for understanding what the software does, even if you never open the software yourself. What I mean is that you don't need to complete a certification to benefit—you need about four hours of reading to know which questions to ask a vendor, which is a very different skill.
I spent maybe six hours total over two weeks, mostly during lunch. It was enough to understand what a CPU module does versus an I/O module, and why the controller in our new air handler needed to match the protocol of the building management system. That single piece of knowledge saved us from a change order that our mechanical contractor later estimated at $3,800.
Support Duration Is a Budget Line, Not a Spec Sheet Footnote
This is the argument I wish someone had made to me two years ago. When you buy a PLC-based system—whether it's a controller in a generator, an air compressor, or a chiller plant—you are not buying a box. You are buying a support window.
Siemens publishes product lifecycle data on its Industry Online Support portal. As of what I've read there, the S7-300 family moved into phase-out in late 2023, while the S7-1200 and S7-1500 are current-generation and remain active. That distinction matters enormously to a facilities budget, because the moment a controller line stops getting firmware and security updates, every device downstream of it becomes a future capital expense. I've watched this play out with an old access control panel—not a Siemens product, to be clear—where the replacement quote came in at four times what we'd originally paid because the whole system had to be swapped at once instead of phased in.
The long-term support duration of a Siemens PLC isn't just an engineer's concern. It's the difference between replacing a controller on your schedule and replacing it on the manufacturer's schedule. Before I sign anything now, I ask the vendor to show me the lifecycle status in writing. If they can't, that's a data point.
The Boring Stuff Changed Too
Here's the part that surprises people: the most old-school items on my purchasing list are exactly where automation has changed the rules. Air conditioner contactor replacement used to be a straightforward parts swap—match the coil voltage, match the load rating, done. Now the contactor in a modern packaged unit reports its own cycle count to the controller, and the controller tells the building system when to schedule replacement. If I buy a dumb contactor to save $40, I've disconnected a diagnostic the maintenance team was relying on.
Same story with the battery backup generator. The annual service used to be a fixed schedule: oil, filter, belts, done. Now the generator controller logs run hours, load profiles, and fault codes, and a decent service contract reads that data instead of guessing. Which brings me to the question I've actually been asked by a vendor: can you change the oil filter without changing the oil? Technically yes. Practically, on any engine with a manufacturer interval, you're trading a $30 filter for a contaminated oil charge and a warranty argument. The old logic was "save the money, nobody will notice." The new logic is that the controller notices, the log notices, and eventually the service technician notices.
Look, I'm not saying every facilities buyer needs to understand PID loops. I'm saying the equipment got smarter and our purchasing habits didn't keep up. That's an industry evolution problem, not a technical one.
"But I Don't Touch the Control Cabinet"
I get it. You're not on the floor with a multimeter. Neither am I. But here's the thing: the control cabinet's contents show up in the contract you sign, the warranty you negotiate, and the service agreement you renew. When our maintenance lead can't get a firmware update because the controller is past its support window, he doesn't call Siemens—he calls me, because I bought it. The responsibility chain runs through procurement whether or not procurement wants it.
To be fair, there's a version of this where the engineering team owns all of it and the admin just processes paperwork. Some companies run that way, and it works. But in a mid-size operation with a lean maintenance staff, the gap between "what the equipment needs" and "what the budget approved" is exactly where problems hide.
What I Actually Do Now
Three questions before any facilities purchase that involves a controller, and I ask them in writing:
- What is the product lifecycle status of the controller, and where is that documented?
- What diagnostics does this equipment report, and to what system?
- What's the service interval schedule, and does the controller log the data that proves it was followed?
That's it. Three questions, maybe ten extra minutes per quote. It has already changed two vendor conversations and one service contract.
The industry moved. The purchasing process didn't. I'd rather update my process than keep paying for the gap.