In this episode of the Pipeliners Podcast, recent guest Mallory Gill steps in as the host, interviewing Russell about alarm management.
Russell shares his background in SCADA projects for pipeline operators and how he became involved in alarm management, highlighting the various aspects and complexities of the field.
They discuss the evolution of alarm management within the pipeline industry since the introduction of the control room management rule in 2010, emphasizing the need for continuous improvement and the challenges faced by operators in achieving best practices.
Russell also provides insights into the implementation of alarm management plans and the importance of a holistic approach to optimizing alarm systems for both safety and operational performance.
Listen to the episode now to learn more about strategies for effective alarm rationalization, the distinction between configuration and enunciation of alarms, and the role of risk-based approaches in improving safety outcomes.
Alarm Management, What’s Next? Show Notes, Links, and Insider Terms:
- Mallory Gill is a Sr. Regulatory Analyst with EnerSys Corporation. Connect with Mallory on LinkedIn.
- EnerSys Corporation is a frequent sponsor of the Pipeliners Podcast. Find out more about how EnerSys supports the pipeline control room through compliance, audit readiness, and control room management through the POEMS Control Room Management (CRM Suite) software suite.
- Russel Treat is the CEO of EnerACT Energy Services, as well as the host of the Pipeliners Podcast and the founder of the Pipeline Podcast Network. Connect with Russel on LinkedIn.
- EnerACT Energy Services is a holding company of oil and gas technology and service companies. EnerSys Corporation is a frequent sponsor of the Pipeliners Podcast. Find out more about how EnerSys supports the pipeline control room through compliance, audit readiness, and control room management through the POEMS Control Room Management (CRM Suite) software suite.
- Control Room Management is regulated by PHMSA under 49 CFR Parts 192 and 195 for the transport of gas and hazardous liquid pipelines, respectively. PHMSA’s pipeline safety regulations prescribe safety requirements for controllers, control rooms, and SCADA systems used to remotely monitor and control pipeline operations.
- Pipeline SMS (Pipeline Safety Management Systems) or PSMS is an industry-wide focus to improve pipeline safety, driving toward zero incidents.
- Alarm management is the process of managing the alarming system in a pipeline operation by documenting the alarm rationalization process, assisting controller alarm response, and generating alarm reports that comply with the CRM Rule for control room management.
- Alarm rationalization is a component of the Alarm Management process of analyzing configured alarms to determine causes and consequences so that alarm priorities can be determined to adhere to API 1167. Additionally, this information is documented and made available to the controller to improve responses to uncommon alarm conditions.
- API 1167 provides operators with recommended industry practices in the development, implementation, and maintenance of an Alarm Management program. The implementation of API 1167 is required by reference in the CRM Rule.
- Alarm rationalization is a component of the Alarm Management process of analyzing configured alarms to determine causes and consequences so that alarm priorities can be determined to adhere to API 1167. Additionally, this information is documented and made available to the controller to improve responses to uncommon alarm conditions.
- Valve and Rupture Rule is a newly updated PHMSA regulation. This rule establishes requirements for rupture-mitigation valves, such as spacing, maintenance and inspection, and risk analysis. The final rule also requires operators of gas and hazardous liquid pipelines to contact 9-1-1 emergency call centers immediately upon notification of a potential rupture and conduct post-rupture investigations and reviews.
- Process Safety Management (PSM) refers to a set of interrelated approaches to managing hazards associated with the process industries and is intended to reduce the frequency and severity of incidents resulting from releases of chemicals and other energy sources.
- AOC (Abnormal Operating Condition) is defined by the 49 CFR Subpart 195.503 and 192.803 as a condition identified by a pipeline operator that may indicate a malfunction of a component or deviation from normal operations that may indicate a condition exceeding design limits or result in a hazard(s) to persons, property, or the environment.
- SCADA (Supervisory Control and Data Acquisition) is a system of software and technology that allows pipeliners to control processes locally or at remote location. SCADA breaks down into two key functions: supervisory control and data acquisition. Included is managing the field, communication, and control room technology components that send and receive valuable data, allowing users to respond to the data.
- HMI (Human Machine Interface) is the user interface that connects an operator to the controller in pipeline operations. High-performance HMI is the next level of taking available data and presenting it as information that is helpful to the controller in understanding the present and future activity in the pipeline.
- Plan Do Check Act (Deming Method) is a continuous quality improvement model consisting of a logical sequence of four repetitive steps for continuous improvement and learning: Plan, Do, Check (Study), and Act.
- MOC (Management Of Change) focuses on planning the processes in a system, the type and quality of changes required, the risks associated with the plan for change, and the people that will be impacted by the change so that it is clearly communicated to stakeholders.
- Gap Analysis is the means by which a company can recognize its current state—by measuring time, money, and labor—and compare it to its target state. By defining and analyzing these gaps, the management team can create an action plan to move the organization forward and fill in the performance gaps.
- O&M (Operation & Maintenance) is a comprehensive approach to performing pipeline tasks related to the operation and maintenance of gas and liquid pipeline systems. A robust O&M program provides personnel with the knowledge and understanding of each situation to enable them to correctly assess the situation and take corrective action.
- CRMP (Control Room Management Plan) captures the policies and procedures that are to be followed in the control room to ensure the safe operations of pipeline assets. Operators that are subject to the PHMSA CRM Rule are required to have a CRMP.
- KPI (key performance indicator) is a measurable value that is intended to show how well a business is adhering to its business model and strategies.
- PLCs (Programmable Logic Controllers) are programmable devices placed in the field that take action when certain conditions are met in a pipeline program.
- ISA-18.2 defines an alarm as “an audible and/or visible means of indicating to the operator an equipment malfunction, process deviation, or abnormal condition requiring a response.
- Other Pipeliners Podcast episodes about Alarm Management
- Episode 51 featuring Jerry Coleman discusses the challenges of Alarm Management.
- Episode 165 and Episode 166 with Doug Rothenberg goes over what alarm management is and its history.
- Episode 186 with Ross Adams talks over alarm management from a compliance standpoint, and Episode 163 discusses overcoming challenges in alarm management.
- Episode 96 with Stephen Swanson talks about process safety management and combines that with alarm management.
- Episode 28 featuring Giancarlo Milano discusses leak alarm response.
Alarm Management, What’s Next? Full Episode Transcript
Russel Treat: Welcome to the “Pipeliners Podcast,” episode 332, sponsored by the American Petroleum Institute, driving safety, environmental protection, and sustainability across the natural gas and oil industry through world-class standards and safety programs.
Be sure and register for the API 2024 Pipeline Conference and Expo for Pipeline, Control Room, and Cybernetics, May 6th through 8th at the Hyatt Regency in Salt Lake City.
This is a valuable opportunity to expand your knowledge, collaborate, and network with more than 700 industry professionals, who are all working to continue their mission to sustain, transform, and secure the needs across the globe. Find out more at api.org.
[background music]
Announcer: The Pipeliners Podcast, where professionals, Bubba geeks, and industry insiders share their knowledge and experience about technology projects and pipeline operations. And now, your host, Russell Treat.
Russel: Thanks for listening to the Pipeliners Podcast. I appreciate you taking the time. To show that appreciation, we give away a customized Yeti tumbler to one listener every episode. This week, our winner is Chris Kuhn with Genesis Energy. Congratulations, Chris. Your Yeti is on his way. To learn how you can win this signature prize, stick around to the end of the episode.
This week, we bring Mallory Gill back as the interviewer to talk to me about alarm management.
Mallory Gill: Russell, welcome back to the Pipeliners Podcast. Thanks for joining me.
Russel: [laughs] It’s good to be here, Mallory, and thank you for offering to be the host for a day.
Mallory: Yeah, this is exciting. It’s better, I think, than being the one who’s being interviewed.
Russel: We’ll get your opinion on that when we’re done. How’s that?
Mallory: Yeah, we’ll come back to that. Today we are discussing alarm management. Russell, why don’t you tell us a little bit about your background? How you came to learn about alarm management, and why you think you’re a subject matter expert.
Russel: I’ll start with the easy question first. In 2007, we were doing a lot of SCADA projects for pipeline operators. One in particular where we were modernizing some older gas storage fields. They were building some new gas storage fields and we were putting automation into those fields, and they had pipeline systems to go along with all that.
At that same time, we started hearing about the control room management rule coming in to PHMSA. I immediately started like, “What’s this whole control room management thing?” and started reading about it.
Basically, I would say the control room management has different aspects to it. One big aspect is everything around adequate information. Then it has to do with shift handover, and it has to do with high-performance HMI. Another big aspect is all the training, and organizational requirements, and so forth.
Then another big aspect is alarm management. I at that time, in 2007, had never heard about alarm management. I knew what alarming was because we’ve been putting in SCADA systems, been doing for a long time, but I hadn’t heard about high-performance HMI, and I hadn’t heard about alarm management, so I went school.
Through working the phones and talking to people who know, I got introduced to a gentleman by the name of Doug Rothenberg, who literally wrote the process alarm management.
Because of that, I’ve read his book, which is about 500 pages written by an engineer. It’s really good, but it’s not the easiest thing to read. We formed a relationship with Doug, he came alongside us on some projects we were working on, I went to a bunch of his trainings for alarm, writing alarm philosophy documents.
Over the course of that, probably 2007 to 2012, ’13, did a lot of projects and alarm management, probably a dozen-plus during that period of time. Fairly significant projects. That’s how I learned about it.
What qualifies me to be a subject matter expert? Boy, probably that seven years of grinding it out with Doug and working very closely with him, and asking him hundreds of stupid questions.
Mallory: I’ll say, we work together now, Russell, and certainly, in addition to all of that foundation building that you did with Doug Rothenberg, is name?
Russel: Right.
Mallory: All of that foundation building. In addition to that, you’re staying very current on where the industry is headed, you’re involved in alarm management projects with our CRM facilitator and support clients.
In your opinion, and based on what you’ve seen, does the subject tend to change? Is there a lot of new information coming in about alarm management on a pretty consistent basis, or is it a static set of static framework?
Russel: Yeah, great question. It’s both, and. When the rule when the control room management rule was published in 2010, and everybody had to have something in place by 2012, everybody did something.
That’s now 10-plus years ago, and people are beginning to look at their programs, and they’re asking, “Are we doing the right thing? Are we doing the best thing for us? Are we getting value out of this activity?”
When we first started with control room management, nobody understood what control room management was. They didn’t understand what high-performance HMI was. They didn’t understand what situational awareness was. They didn’t understand what alarm management was.
As an industry, we acknowledge now what it is, we have a pretty good understanding of, at least conceptually what it is, and everybody has something in place. But as an industry, many operators are looking at what they’re doing and starting to ask the question, is there a better way to do this?
Mallory: My own experience with alarm management, and this is an interesting conversation because I only think about it in the here and now. Not so much in the evolution of a CRM program.
It is interesting to think about such a robust program like alarm management, and how many operators probably around 2010 to 12, we’re just trying to get something implemented, like you said, versus now we’ve got over 10 years under our belt.
With the CRM regulations being published and having some opportunity to improve our program, how much further do you think we need to go before, as an industry, we’re achieving best practice with alarm management? What are some themes that you’re seeing?
Russel: That’s a great question as well. I think we have a long way to go. I think a couple of things are important to understand as well. Whenever a new regulatory requirement comes out, there’s a timeline that’s a natural timeline that we go through where that rule matures with the operators and with the regulators.
The first round of inspections under CRM were, do you have something in place? Does your program say the right things? Second round was more about, “Do you have procedures, and do those procedures reflect what you say in your policy statements?
Then third round was more about records, and we’re starting to get into the fourth round, or longer for a lot of operators, and these inspections are beginning to become, particularly with the larger operators, or the operators that PHMSA would say have more operating risk…
Depending on where you are and what you’re carrying as product and your size, and those sort of things, PHMSA is looking at that, and now they’re starting to say, are we getting the safety impact we’re looking for? I think that’s just the natural maturity of any regulatory requirement. That’s one thing that’s changed.
The other thing that’s changed is people, when they were first being required to do alarm management, where they went out to the alarm management vendors that were available at the time, most of whom had backgrounds in doing alarm management in the process industries, refining, petrochemical, nuclear power, that sort of thing…
There’s some fairly significant differences between what’s required in those industries and what we need in pipelining. I think we have a very different level…I think everybody understands what alarm management is, and everybody’s doing something, and everybody’s wondering about a better way to do it.
The other thing I would say is that API 1167, which is pipeline alarm management, wasn’t published until about 18 months after the rule went into effect.
Mallory: That is interesting.
Russel: Right, and it’s not currently incorporated by reference into the CRM rule.
Mallory: What did operators who were around at the time the CRM rule was published, what framework do those operators have for implementing an alarm management program?
Russel: For most of them, what they did is they went to industry consultants, people like Doug Rothenberg, brought them in to help them write philosophies and programs, and then went about implementing those programs the best they could.
Mallory: The industry experts at that time — still talking about the period of time where the CRM rule comes out, operators are trying to implement — you’ve established that before the 2007 to 2012 timeline, there wasn’t this level of, maybe detail isn’t the right word, but this robust program for alarm management.
There were probably very few resources available at that time to even help you progress.
Russel: Yes, the people who knew alarm management didn’t have a lot of experience with pipelining, and the people who had a lot of experience with pipelining and pipeline automation and all that didn’t have much experience with alarm management.
Fairly big skills and knowledge gap at that time. You asked me earlier, why do I hold myself out as an SMA? I would not say that I’m an alarm management SMA. I would say I’m a pipeline alarm management SMA. I would not feel comfortable trying to do alarm management in a petrochemical facility, for example.
The other thing that qualifies myself and others that are out there is I have a great deal of operating experience across a lot of operators in my 30-plus years of doing automation, and projects, and working around control rooms. I have a lot of understanding of how they actually operate and the risks that are presented based on those operations.
Mallory: That’s a good segue into, let’s talk about, as an industry, looking at the PHMSA-regulated operators. Where do you think we currently stand? If you could give us a letter grade from what you’ve seen so far about how we’re generally doing with alarm management?
Russel: I’m not going to give us a letter grade. I’m going to go more to the PSMS maturity model.
Mallory: [laughs] Fair enough.
Russel: Because I don’t want to be called out for giving the industry a bad letter grade, to be [inaudible 13:34] frank. What I would say is, in the maturity model in the PHMSA program, or the PSMS program, it’s a one through five, with a one being the lowest level of maturity and a five being the highest. I think that as an industry, we’re largely between a two and a three.
Mallory: Can you remind us what the two and three are? I believe it’s developing, written plan, and implementing it…
[crosstalk]
Russel: One is you’re developing, two is you have a plan, three is you have the plan implemented and you’re beginning to improve it. Four or five, or more, you have meaningful KPIs and you’re actively working those KPIs and fully into the plan-do-check-act cycle.
Mallory: As we’re talking about the connection between alarm management for CRM and then PSMS as a program, it’s bringing something together for me, which is that, of the tenets of CRM, alarm management is one of the few that requires operators to document deficiency resolution.
Which I think is almost like a precursor to the concept of PSMS, where we’re very actively checking our program and being very diligent about identifying deficiencies and integrating this proactive approach to managing a program.
Anyway, I’ve never made that connection before. As you said that it’s a little bit more of maybe a safety management-centric program, that connection became a little clearer.
Russel: We’ve done a number of white papers and presentations over the year about PSMS, and used alarm management as an illustration of how to do it effectively, and how that relates.
In fact, we’re doing one of those at API this year as well. I think you’re absolutely right, it is an area in the CRM role where the full implementation of PSMS is much more in line of sight than it is in other places.
Because ideally what you’re doing is you’re doing a monthly review of how your system is performing, you’re looking for corrective actions to improve it, and then you’re also doing an annual review of the overall program and its effectiveness.
The interesting thing about alarm management as a process is I control how I configure my alarms, but the process controls how those alarms enunciate. It’s not a direct connection. There’s this constant trying to understand, “What is the connection between the alarms and how I have them configured?” and how they’re actually being enunciated in the system.
Mallory: Can you elaborate a little further on the distinction between those two things? Because I am slightly less of a expert than you are.
Russel: See, that’s why you make a good interview. You have curiosity. You’re seeking to understand. That’s good.
Mallory: [laughs] I’m more for the people.
Russel: [laughs] What I mean by configuration is I’m determining what points to have throw alarms. This particular pressure, I’m going to have it throw alarms. I’m determining at what pressure values or alarm activation set points those alarms are going to be thrown.
I’m trying to do that in a way that I minimize the total number of activations. When I’m working with people around the rationalization and configuration, what I say is the aspirational goal for alarm management is there’d be one and only one alarm for every abnormal operating condition.
Nobody’s there, and very few people are anywhere close. That’s the aspirational goal. That’s what you’re trying to get to over time. You’re not alarming on high pressure. Rather, you’re alarming on a pipeline obstruction. High pressure would be how I indicate I have the abnormal operating condition of a pipeline obstruction.
Mallory: What you’re speaking to sounds very much like why PHMSA wants us to identify sequential, N sequence AOCs. Is that accurate?
Russel: Yes. There’s certainly a connection there. If you look at incident investigations, and particularly if you look at Bellingham, there is a correlation between effective incident management and effective alarm management.
Mallory: Interesting.
Russel: When you’re in an incident, in the ideal world, you’d get one alarm and it would say, “Hey, this is what just happened.” Rather than you get a hundred alarms and you got to figure it out. That’s what I mean by we control configuration. We don’t control activation.
Activation is when the pressure actually passes that set point. When the pressure passes the set point, I get an alarm and then I got to figure out what’s the root cause. Is it a pipeline obstruction? Do I have a pump or a flow control set point adjusted incorrectly? Did somebody, who’s taking on a gas system, did somebody who’s taking a lot of gas quit taking gas?
I’m looking for the root cause behind the pressure surge, right?
Mallory: Do you think that many operators who have a CRM program implemented, do you think there’s a level of understanding about the difference between that configuration and enunciation, the level of analysis that has to then occur after we just do our engineering defined set points and activations? Is that kind of next step do you think clear to many operators?
Russel: I think that part is clear to many operators, yes. I think what’s less clear to many operators is what is the process for really improving performance. Improving performance in an alarm management case is, making all of the alarms more meaningful, making all of the alarms better documented, and providing tools for the controller to quickly run through their rubric to determine root cause and corrective action.
I think people have a good understanding of the difference between the configuration and the activations. I don’t think they have a good understanding of the things they can do to optimize and improve the system by making adjustments in the way they configure alarms. A lot of times it’s things like put dead bands on the alarms, right?
Sometimes it could be every time this particular operating condition occurs, I get these three alarms. Let’s take those three alarms and create some code in the automation so that it looks for all three of them and gives us another alarm that tells us what the real problem is. That level of really improving systems, I don’t think we’re there yet.
Mallory: If I’m paraphrasing what you were to say there, your general recommendation for how an operator can be continuously improving their alarm program is by implementing some very proactive effectiveness reviews of their AOCs, of their alarms, doing that analysis, and then reflecting any changes to practice in our policy and procedure?
Russel: Not just policy procedure, but also in our system. That would be in our management tools, in our automation, and in our SCADA. It’s both of those. It could be policy and procedure, or documentation, but it could also be modifications to the automation system itself.
It could be adding instruments, in order to be able to see something you couldn’t previously see. It could be putting logic around the alarm annunciations to look for sympathetic alarms, or redundant alarms, and things like that. It’s that level of sophistication that’s where we’re not really doing what’s possible yet.
I think we’re going to start moving in that direction. I think you’re going to see the vendors start offering tools that facilitate some of that stuff as well.
Mallory: Yeah, I want to jump to a different subject. Everything that we’re talking about as far as best practice goes, and we’ve laid out some what I think are pretty helpful, both tangible and intangibles there. How do you take all of that and then apply it to, you have obviously a suite of software tools, CRM suite, how much of that methodology did you take and apply then to alarm manager?
Russel: To give a little bit background. Alarm manager is our product. It’s EnerSys tool set as part of CRM suite that we use for doing alarm management. What we found when we first started doing alarm management with customers, we were using a third party tool that had been in the market for some time.
It’s a tool that a lot of pipeline operators picked up. We found that tool to be problematic for a couple of reasons. One, there’s a whole bunch of rather specific analytical reports that you need to see in alarm management — fleeting alarm analysis, chattering alarm analysis, alarm flood analysis — things like that, looking for bad actors and things that need to be corrected.
We found the reporting difficult to work with. The other thing that we saw was the need for the ability to copy paste.
Mallory: Can you clarify what you mean by copy paste?
Russel: Yeah, so one of the things that’s unique about pipelining versus other kinds of processes is that there’s a lot of duplication of equipment. There’s a lot of mainline valve sites on a pipeline. Those mainline valve sites, like on a liquid line, you’ll typically have a pressure on either side of the valve.
You’ll have maybe a temperature, and then you’ll have all the IO or the instrumentation around commanding the valve to move and monitoring the valve movement, right? If I have 300 valves in a pipeline system, then every time I rationalize another mainline valve that’s set up the same way, with the same instrumentation, on the same product, operating at the same pressure, I ought to be able to copy paste from the last one I did.
Because it’s alarm management, I need to have a mechanism, not just copy paste and forget. I need to copy paste, review, and accept. When we built alarm manager, one of the key reasons we built it is to add that feature. That has literally saved us hundreds, if not thousands of hours at this point doing alarm rationalization.
Mallory: When you say review and accept, my mind automatically goes to management of change. Am I on the right track there?
Russel: Yeah, I think so. You have to realize that when you’re doing alarm rationalization, you’re not actually working in the live automation system. You’re working in a system that’s documenting what the rationalization should be, right? It’s more like I’m working in an engineering system.
I don’t generally use copy paste other than when I’m doing my original rationalization, or I’m doing some kind of major rationalization reset.
Mallory: You’re saying, this original rationalization is very labor intensive, right? You want the ability to, I’m not going to say automate, but reduce some of that time where possible through…?
[crosstalk]
Russel: …working around similar, if not identical sites. The copy paste functionality copies from one mainline valve to another, and it has intelligence in it to know these things match. This didn’t exist in the copy from. This existed in the copy from, but didn’t exist in the paste.
It has enough knowledge to look for those differences and flag all that. That all radically accelerates my ability to do the rationalization.
Mallory: I maybe jumped ahead a little bit here to implementation, but I want to go backwards to the planning portion of alarm management. What kinds of documents, policies, and procedures should an operator have in place if they are going to have an alarm management plan?
Russel: Yeah, great question. We, in the last two years, have made a fairly substantial shift in our approach. When we started with just an alarm philosophy. What we’ve shifted to is now we have an alarm philosophy, which is a generic, “This is our approach to alarm management.”
It follows very closely what’s in API 1167. We did a big project where we aligned our documentation with 1167. Then we have an alarm management plan. The alarm management plan specifies how I use my alarm management tools, how I implement alarm management in SCADA, and the process and procedures I use to do rationalization, documentation, and review.
What our recommendation would be primarily what you need is a philosophy and alarm management plan. Philosophy being generic and the management plan being specific to the SCADA system and operation.
It would be rare. I would think you’d need more than one alarm philosophy, even a large operator with many different kinds of operations, but you might very well need multiple alarm management plan.
Mallory: Interesting. For those listening who don’t know, I work with some CRM clients, helping them maintain compliance with the regulations. A lot of the questions that I’m asking are coming directly out of some of either meetings or questions that I’ve had in meetings and when advising clients. I’m just now having an opportunity and they’re all coming up.
How often do you recommend or invest practice? How often should operators be revising or making changes to either their alarm philosophy, or their alarm management plans?
Russel: Ideally, not often, right? That’s the kind of thing that ought to be looked at in a 5- to 10-year cycle. Now, I want to talk to that a little bit because I actually think one of the things that’s going on in the industry right now is that many people are at that 10-year point, and they’re starting to look at what they’re doing, how they’re doing it, and ask questions about, is there a better way?
In particular, one of the things that I have seen is the approaches to rationalization have been overly simplistic. For example, I rationalize every high-high on every tank across my system the same way. I would argue that that’s invalid.
A high-high on a 50,000-barrel crude oil tank is not the same thing as a high-high on a standard API field tank. Is not the same thing as a high on a butane tank, right? One of the things that we’re finding is that…I’ll frame this way.
When we originally started doing our approach, it followed ISA 18.2. Which was an available standard, a mature standard, a well understood standard in the process industries. It takes a risk based approach to determining alarm severity, so whether something’s critical, high, medium, low.
The reason for severity and alarm management is I want the most high consequence alarm indication to go to the top of the controllers list. That’s what that’s all about so that it doesn’t get buried or overlooked.
One of the things that we did initially is we took and we aligned our risk matrix with the typical kind of safety matrix. For example, if you had a health and safety matrix, you probably have a hierarchy between no consequence, reportable injury, lost time, on that hierarchy of severity.
When you start doing alarm management, a lot of times that way of thinking about severity it’s problematic. What we’re finding is, and actually one of the things I’m working on right now, is a discussion document for some of our customers around rethinking the risk matrix they use.
Maybe the risk matrix should be one factor in the matrix is the operating pressure. If you think about a gas distribution company, they probably have systems at 600 PSI, systems at 350 PSI, systems at 150 PSI, and systems at 75 PSI and lower. Those things have different risks associated with them, right?
Likewise, if a location is in an HCA, high consequence area, versus it’s in a rural area, versus it’s in an urban area, but not an HCA, those things have different risks. Those kinds of risks are generally better understood in a pipeline operator and easier to identify. We’re working on coming up with simpler to understand risk matrices.
Mallory: I don’t even know where to begin with that.
Russel: That’s fine. When the roles are reversed, I often find myself talking to somebody and I just tell them, “That’s spun my head. All that’s causing the wheels to turn, but I have no follow up question available.”
Mallory: I wonder if that’s a daunting prospect or maybe surprising to some operators that maybe even the factors that we’re looking at in our risk approach are shifting. It sounds like maybe what you’re suggesting is a little bit more intuitive. While it may be a shift from what we’re used to, ultimately it gets us closer to operating safer and rationalizing more appropriately.
Russel: Yes. That’s exactly right. Ultimately that’s what the regulators are looking for. They want people to have programs that are improving their safety performance. What a lot of operators did, and they did it out of necessity when they first put their programs in, particularly guys with large, complex systems, is they made simplifying assumptions.
It’s now we’re entering a new season and it’s a good time to be rethinking about, “What are we going to do in the next 10 years in this discipline? We need to move to risk based rationalization. That will help us improve our safety performance. That’s my final thoughts about where we’re headed.
Mallory: I guess my last question would be, do you have any advice for operators who are maybe finding that alarm management is their primary area of concern in their program? Just a general, “Hey, maybe start here.” Anything of reassurance for those folks?
Russel: Oh, it’s such a good question. I got to think about how to frame this answer a little bit. I want to be careful about how I say this. For a lot of operators, they’re probably at a point where it makes sense to do a fundamental rethink of their whole approach to alarm management.
If an operator’s at that place, certainly, I’m always available to take a phone call and have a skull session. I love having those kind of conversations. I would also say that if you’re at that place, one of the beautiful things about having a rethink about your approach is you don’t have to do a whole lot of work yet.
Looking at, “Well, what could we do with our alarm management?” would not only assist us with our safety performance but would also help us with our operating and commercial performance. PHMS’s primary focus is safety-related alarms.
When we do alarm rationalization, we tend to look at it comprehensively. There’s plenty of things in a pipeline system that need to be alarmed and brought to the controller’s attention and worked but are not safety-related, but they can have significant commercial consequences. When we’re going to do alarm management, my recommendation is think about doing a reset.
When you do the reset, think about it holistically in terms of “What operating value can I get, not just safety value, out of doing a better job with alarming?”
Mallory: Awesome. Well, I hope that this was educational and maybe inspired some operators who are struggling with their alarm programs to just do a high-level reset. There are solutions out there. [laughs]
Russel: I want to say thank you for being the host. It’s nice to be a guest. Did a great job of asking questions.
Mallory: Thank you.
Russel: Maybe there’s a podcast in your future. Who knows?
Mallory: I feel like I always have a million questions for you. Maybe just in our next face-to-face we…
Russel: Just start recording?
Mallory: …more audio.
Russel: [laughs]
Mallory: We can just start splicing together some different conversations into a great big podcast.
Russel: What an awesome idea. I like that.
Mallory: [laughs]
Russel: All right. Great. Thank you, Mallory.
Mallory: Thanks, Russel.
Russel: I hope you enjoyed this week’s episode of the Pipeliners Podcast, and our conversation with Mallory and myself. Just a reminder before you go, you should register to win our customized Pipeliners Podcast YETI tumbler. Simply visit pipelinepodcastnetwork.com/win and enter yourself in the drawing.
If you’d like to support us, please leave us a review. You can do that on Apple Podcasts, Google Play, wherever you happen to listen.
[background music]
Russel: If you have ideas, questions, or topics you’d be interested in, please let me know either on the Contact Us page at pipelinepodcastnetwork.com or reach out to me on LinkedIn. Thanks for listening. I’ll talk to you next week.



