5 things to consider when selecting a safety system

Performance requirements now drive the selection process

10/29/2013


Hazard management in places like offshore drilling is critical to the safety of people and property, and is one of five considerations when choosing a safety system. Courtesy: ABBSafety is among the top priorities in any manufacturing facility, and given the changes in the industry, technology and even standard, there are a lot of concerns starting with the selection of a safety system.

The performance based safety standards (IEC61508 and IEC61511/ISA84) have changed the way safety system selection should happen. Gone are the days of simply choosing a certified product, or selecting a preferred architecture; today’s system selection is driven by performance requirements. 

1: Hazard understanding

Correct, this has nothing to do with the safety system hardware. It is critical in the process to understand the scope of the process hazards and to determine the necessary risk reduction required. This should be done to create the Safety Requirements Specification (SRS) necessary to start a system selection. Even when replacing an existing system, this is critical as the risk profile of the plant may have changed since installation. 

2: The more diverse the better

Technology diversity: There has been a long standing requirement that a safety system must be different (or diverse) technology from its process automation counterpart to avoid common cause failures. But most safety systems rely on component redundancy (hardware fault tolerance, or HFT) to meet reliability and availability requirements, introducing a degree of common cause failure directly into the safety system.

Rather than redundancy, leading systems now provide diversity of technologies designed into logic solvers and I/O modules, along with a high degree of diagnostics, to allow a simplex hardware configuration to meet SIL3 requirements.

Product implementation diversity: The standards are imposing diversity on the way manufacturers deliver the product you buy. Even though most safety systems are manufactured by process automation vendors, organizational diversity between the two product teams is only the first level of separation.

Within the safety product team, leading suppliers will also be separating the design group from product development group and then again from product testing group. Ask your potential suppliers how diverse they really are? 

3: Systematic safeguards

This addresses how much protection against mistakes is built into the safety system. You should be asking for:

  • certified software libraries that offer functions according to the SIL requirements of the application,
  • compiler restrictions to enforce implementations according to the SIL requirements,
  • user security management to separate approved from non-approved users for overrides, bypass and other key functions,
  • and, audit trail capability to record and document changes to aid in compliance with functional safety standards 

4: Availability

As mentioned above, previous generations of safety systems met reliability requirements through HFT. This feature helped to provide availability and kept plants running in the event of a component failure with the safety system. Whether you needed it or not, you paid for it. Understand if you need high availability or not as some processes can easily tolerate shutdowns from spurious trips when using simplex configurations that still deliver appropriate SIL coverage.

If you know you need availability, look for a system supporting firmware update or upgrade and maintenance without disrupting the process. 

5: Separate, interfaced, or integrated?

Using the SRS and your business requirements, make a clear determination of one of these three requirements. Integrated offers many key benefits, drawing on common capabilities of the process automation system not related to the safety functions directly. But only being interfaced or even kept completely separate are options, and need to be thoroughly considered.

However, achieving the desired risk reduction involves more than just choosing a system. On our next posting we’ll cover implementation, security, operation, and maintenance of a safety system. 

Luis Duran is Product Marketing Manager at ABB for the Safety Automation System business.



Abdelsalam , Non-US/Not Applicable, Egypt, 11/04/13 01:22 PM:

Hi,
I have technical question if possible.
If we have to connect Pushbutton to Safety system to cause shutdown how much is the accepted distance from the PB to the system?
Taking into consideration that the ESD pushbutton shall be connected to analog input channel in order to be monitored using serial and parallel resistances, too much length (7 Km as my application ) could affect not only on the size of the cable to eliminate the voltage droop but also it may have transmission line concerns like capacitance , reflections and ringing effect.
Now the question is it applicable to connect the Pushbutton conventionally and can eliminate these effects or by other way? How we install it? Or it is not applicable at all and we have to think again about it?
BN , , 11/19/13 09:47 PM:

My point of view is ,its not worth to monitor the analog status rather we can install teh PB with diagnostics features and increase the testing frequency .More important is to perform FMEA & nullify the failure modes thru best design practices.
Anonymous , 12/05/13 12:46 PM:

If critical - use single mode fiberoptic cable and converters as your primary communication to transmit your shutdown signal to your safety PLC. Back this up with phone line communication to your shutdown system.
Or
Use phone line as your primary and satellite communication as your backup.
The Engineers' Choice Awards highlight some of the best new control, instrumentation and automation products as chosen by...
Each year, a panel of Control Engineering editors and industry expert judges select the System Integrator of the Year Award winners.
Control Engineering Leaders Under 40 identifies and gives recognition to young engineers who...
Learn more about methods used to ensure that the integration between the safety system and the process control...
Adding industrial toughness and reliability to Ethernet eGuide
Technological advances like multiple-in-multiple-out (MIMO) transmitting and receiving
Virtualization advice: 4 ways splitting servers can help manufacturing; Efficient motion controls; Fill the brain drain; Learn from the HART Plant of the Year
Two sides to process safety: Combining human and technical factors in your program; Preparing HMI graphics for migrations; Mechatronics and safety; Engineers' Choice Awards
Detecting security breaches: Forensic invenstigations depend on knowing your networks inside and out; Wireless workers; Opening robotic control; Product exclusive: Robust encoders
The Ask Control Engineering blog covers all aspects of automation, including motors, drives, sensors, motion control, machine control, and embedded systems.
Join this ongoing discussion of machine guarding topics, including solutions assessments, regulatory compliance, gap analysis...
News and comments from Control Engineering process industries editor, Peter Welander.
IMS Research, recently acquired by IHS Inc., is a leading independent supplier of market research and consultancy to the global electronics industry.
This is a blog from the trenches – written by engineers who are implementing and upgrading control systems every day across every industry.
Anthony Baker is a fictitious aggregation of experts from Callisto Integration, providing manufacturing consulting and systems integration.
Integrator Guide

Integrator Guide

Search the online Automation Integrator Guide
 

Create New Listing

Visit the System Integrators page to view past winners of Control Engineering's System Integrator of the Year Award and learn how to enter the competition. You will also find more information on system integrators and Control System Integrators Association.

Case Study Database

Case Study Database

Get more exposure for your case study by uploading it to the Control Engineering case study database, where end-users can identify relevant solutions and explore what the experts are doing to effectively implement a variety of technology and productivity related projects.

These case studies provide examples of how knowledgeable solution providers have used technology, processes and people to create effective and successful implementations in real-world situations. Case studies can be completed by filling out a simple online form where you can outline the project title, abstract, and full story in 1500 words or less; upload photos, videos and a logo.

Click here to visit the Case Study Database and upload your case study.