I recently had the opportunity to join Russell Treat on the Pipeliners Podcast for a conversation about a topic we both feel strongly about: the challenge of responding to pipeline leak alarms.
Russell and I have enjoyed talking about leak detection and pipeline operations in the past, so I appreciated the chance to dig more deeply into the subject with him. Leak detection can sound straightforward from the outside—monitor what goes into a pipeline, compare it to what comes out, and alarm when something doesn’t add up. In practice, it is anything but simple.
In the episode, we discuss why leak alarms are among the most complex alarms a pipeline controller can receive, including the difficult balance between sensitivity and false alarms, the influence of changing pipeline operating conditions and instrumentation, and the importance of giving controllers the information and procedures they need to confidently evaluate an alarm. We also explore one of the areas that deserves particular attention: determining when it is safe to restart a pipeline after a shutdown.
One of the themes that comes through in our conversation is that effective pipeline leak detection is about much more than an algorithm. Technology matters, but so do the pipeline, its instrumentation, its operating practices, and—most importantly—the people who ultimately have to interpret and respond to what the system is telling them.
Russell and I both care deeply about helping operators to be successful in safely running their pipelines, and I enjoyed the opportunity to have a thoughtful conversation about where the industry can continue to improve.
Listen to Episode 455 of the Pipeliners Podcast: “Leak Alarm – The Most Complex Alarm a Controller Can Get.”
