As you can see, this is by far the costliest system. And yet, with foresight, I might have saved a lot in change orders. We incurred two days of design time and three days of wiring time for the first contractor-requested change. The second manufacturer-fault-driven change cost us two days design time and two days of wiring time. The cost of this change time could easily run up to $8,000. If I’d used a safety PLC and safety I/O in the first place, a contractor-requested change might need one day of extra programming -- at about $1,000.
What’s the final score? I spent more than $6,350 in hardware and $8,000 in change time with dedicated, modular safety relays. I could have spent $11,700 for safety PLC and change time. I assume you're thinking that the manufacturer defect could not have been predicted, so the change time should not be counted against the modular relay route. That's a fair assumption, so we’ll price out the modular relay approach at $10,350 versus the $11,700 for the safety PLC.
One more change to the safety design, and the safety PLC looks rather attractive, doesn’t it? I plan to push harder for the safety PLC on the next industrial automation project. I might lose the gamble, because no changes will be necessary, but it is rather nice to be able to make changes in software rather than hardware. This compares quite well with the argument for hand drafting versus computer-aided drafting. The initial drafting work takes about the same amount of time regardless of tool, but as soon as a change is required, software wins every time.
Is the cost of this safety worth it? Tell us what you think in the comments section below.
I love this real-world example of how one simple design decision and component change can have real impact on the cost of the BOM and the ultimate performance of the product. This is a classic example of what happens every day in design iteration. It really shines a spotlight on how a more holistic view and big-picture thinking can really have impact on design results not to mention, costs. Thanks for sharing, TJ.
Beth, I have to write a correction here. I realize I neglected to SUBTRACT the cost of the standard PLC from my safety PLC figure (the safety PLC performs both the safety function and the regular PLC function in one unit and thus replaces the standard PLC).
This would adjust the total safety PLC cost down to around $7000. The safety PLC decision becomes even more attractive for the next system.
Interesting piece, TJ. With safety becoming more an integral part of the integrated architecture/product line-ups for many automation control vendors, it will be interesting to see how the pricing trends play out over the next few years. Would expect that the premium will be heading downward but it's impossible to know how fast.
The purchase price is declining, and safety PLC options are even more attractive at installation because the long cable home runs get decreased. Instead of having all safety device cables return to the central location where the safety relays reside, the devices can land locally at distributed Ethernet IO locations which communicate via regular Ethernet cable. The Ethernet IO cable already must be pulled back to the central PLC; this gives a significant cost savings for cabling and installation time.
The drawback to SafetyPLC option is the complexity for post-acceptance troubleshooting. The skill level required to maintain and troubleshoot such a system is much higher. Trouble-shooting a system using regular safety relays can be much simpler.
Apologies for quoting Yoda, but it does seem like we (engineers) are expected to predict future events, and be right every single time (OR THOUSANDS COULD DIE!!!)
While it was theoretically possible that I could have discovered the manufacturer flaw prior to purchasing the hardware, It would not have been practical. This would mean searching the manufacturer's knowledgebase for every single part used, with multiple searches and good keyword guesses for each part.
I suppose engineers should expect the customer to change their mind several times through the life of a project (we did charge a change fee), planning too much for such events simply drives the cost up unnecessarily.
OK, writing that helped gel the answer to your question. A logic-based (software) solution to problems may cost more up front but is likely to be the lower cost choice over the life of a design. The fact that it is likely the more complex solution as well means the work force needs more education (and should be compensated better for having acquired that education).
TJ, thanks for this post. You've taken the argument to where it really counts--cost. You've also noted that foresight could have saved time and money. Design News will try to come back and take a deeper look at this, along the lines of the article Jon Titus mentions, about analyzing the benefits and tradeoffs of safety in the context of safety-rated PLCs.
A number of factors are affecting the cost of safety including suppliers moving to provide "right-sized" solutions based on the requirements and the complexity of systems. Plus there is the move to networked safety systems, especially on the Industrial Ethernet side, where there has been an increase in the number of devices available and infrastructure which allows large amounts of safety data to be passed over the network in a failsafe way. A second major trend affecting costs is the combination of failsafe operation, machine and motion control in one controller. Many systems in the past had separate controllers for motion and safety. But increasingly all of these functions are available in a single controller on one network.
The dollar amounts are really "price", not "cost". Cost requires a holistic view- what are the consequences of the safety system failing to react? How often will a false alarm occur and what is the cost in downtime and product/ ingredient scrap? Also the price range of the various options is ~$6k. If that's part of a $10M system with a few sales per year, the project delays might far exceed any price savings. Liability cost exposure might need to be considered too.
If you've spent any time looking for the right connector to use in a smartphone or other mobile device, you might believe that all fine-pitch, low-profile connectors are created equal. But they're not.
For industrial control applications, or even a simple assembly line, that machine can go almost 24/7 without a break. But what happens when the task is a little more complex? That’s where the “smart” machine would come in. The smart machine is one that has some simple (or complex in some cases) processing capability to be able to adapt to changing conditions. Such machines are suited for a host of applications, including automotive, aerospace, defense, medical, computers and electronics, telecommunications, consumer goods, and so on. This discussion will examine what’s possible with smart machines, and what tradeoffs need to be made to implement such a solution.