Claim OwnershipKenexis - Functional Safety Podcast
Subscribed: 3Played: 230
Subscribe
© Kenexis
Description
Welcome to the Kenexis Functional Safety Podcast! I'm Ed Marszal, President and CEO of Kenexis, a leading technical safety consultancy for the chemical process industry. With decades of experience in safety instrumented systems, I bring a unique perspective to this podcast, having actively contributed to the ISA 84 committee since 1994.
In this inaugural season, we'll delve into the IEC 61511 standard, examining each word's significance. I'll provide detailed insights into the standard's interpretation and application, complemented by personal stories from my career and committee discussions.
In this inaugural season, we'll delve into the IEC 61511 standard, examining each word's significance. I'll provide detailed insights into the standard's interpretation and application, complemented by personal stories from my career and committee discussions.
45 Episodes
Reverse
A device should never remain in bypass indefinitely. Bypassduration must be time-limited, and appropriate compensating measures must be implemented. Listen in for more information and thoughts on this importanttopic.
The design shall allow for testing of the SIS either end to end OR in segments meaning you could test one piece at a time, but when you do that, you have to be very careful…Tune in as this topic is explored in greater detail, covering Sections 11.8.1 to 11.8.3 in this episode.
Many users of generic, off-the-shelf PLC logic solvers for Safety Instrumented Systems are surprised to learn that maintenance and engineering interfaces are not permitted to be connected while the process is in operation.Join us as section 11.7.3 is discussed in more detail.
Bypasses and resets are two standard data elements routinelytransmitted from the BCPS to the SIS, and this communication must be done safely…Listen in for more information on this section.
You can transfer data to and from the Safety Integrated System (SIS), but your design must prevent an outside failure from causing an internal SIS failure.In this episode, we dive into the crucial world of secure data transfer for SIS.
Don't let the certificate distract you. Your role as an instrumentation and control engineer requires continued diligence. The work still needs to be done!
Did you know that you can install Programmable Logic Controllers (PLCs) based on prior use without being certified? Sounds easy, right? Think again!While they are exempt from formal certification, we reveal why achieving full compliance with installation and safety requirements is often an extremely difficult, if not impossible, hurdle for engineers. Tune in to learn why relying on prior use might be a compliance nightmare!
The devices you use in your safety instrumented systems DO NOT have to be certified! We're cutting through the noise to give you the facts on what truly matters for functional safety. In this episode we discuss the actual requirements—the principles, standards, and engineering practices—that dictate a device's suitability.
You achieve a given SIL target by running a calculation that verifies you achieved the proper probability of failure on demand, yet the standards committee doesn’t trust to do that properly….
How should the safety instrumented system respond to adetected failure? Well, it will respond however you want it to respond…
Unscrupulous equipment vendors often bury critical safety information in a product's safety manual to get their products certified. Therefore, it's essential to read the manual thoroughly to uncover any potential hazards.Join us as Ed discusses this topic in more detail.
Energize to trip or de-energize to trip, that is the question… and the answer is… you can do whatever you want…
A device used by the SIS shall not be used by the BPS (unless that’s what you really want to do) ….Join Ed to hear his thoughts, experience and insights as he digs further into Clause 11.2.9 to 11.2.10.
In this week’s podcast Ed discusses clause 11.2.8, which is all about manual shutdowns. The session ranges from the apocryphal or true OG manual shutdown that traces back to the Manhattan project - the SCRAM - to a second hand story of why a toilet malfunction generated the requirement that manual shutdowns be independent of the logic solver.
Once the Safety Instrumented System brings the system to a safe state, it should remain in that state until an operator manually intervenes.This topic is explored in more detail with a discussion of clause 11.2.6 to 11.2.7 of the IEC 61511 standard.
We've finally arrived at clause 11 titled SIS Design and Engineering, which is where the core work happens! This episode, the discussion focuses on sections 11.1 to 11.2.5.
After several weeks of laying the groundwork on SafetyRequirements Specifications (SRS), we're back for a more focused discussion.This episode, we're zeroing in on SRS specifically for application software by discussing clauses 10.3.3 to 10.3.6
Wow! There are a lot of things in the safety requirements specifications clause. It has taken us several episodes, but we finally get to finish up the discussion on this section.
In this episode, we dive deeper into the requirements forstarting up and re-starting Safety Instrumented Systems (SIS). Wasn’t this already covered in bullet point 16? Join us as we revisit Clause 10.3.2 to clarify any confusion and unpack what’s really required when bringing SIS back online.
“Fail safe” is a common term—and it sounds great. Who wouldn’t want things to fail safe? But here’s the thing: can we ever really guarantee that? Join us as we unpack what “fail safe” really means, why it’s not always as foolproof as it sounds, and what that means in the real world.
Comments
Download from Google Play
Download from App Store
United States