Welcome to the Pipe Liners Podcast, episode 57. This episode of the Pipe Liners Podcast is sponsored by Inersys Corporation, providers of Poems, the Pipeline Operations Excellent Management System, Industry Leading Software for the Pipe Liners Control Center. To find out more about Inersys Control Room solutions, go to Inersyscorp.com slash podcast. The Pipe Liners Podcast were professionals, bubblegeeks, and industry insiders share their knowledge and experience about technology, projects, and pipeline operations.
And now your host, Russell Treet. Thanks for listening to the Pipe Liners Podcast. We appreciate you taking the time and to show that appreciation, we're giving away a customized Yeti Tumblr to one listener each episode. This week, our winner is John Castile with Northwest Natural.
Congratulations, John. Your Yeti is on its way to learn how you can win this signature prize pack. Stick around to the end of the episode. This week, we have the FAB3.
That's what I'm choosing to call them at this point from Marathon Pipeline, Jason Dalton, Dan Sinssel, and Kyle Miller are returning to talk about managing slack line in the liquid pipeline. Well, Jason, Kyle, Dan, welcome back to the Pipe Liners Podcast. It's good to be here. Pleasure to be back.
We're going to talk about slack line today. And I know there's gas guys that listen to this. I think most people in the liquid world would know what slack line is, but maybe you could give us a definition for those in the business that might not have heard the term slack line. Just tell us what is slack line.
Why is it so important for us to talk about it? Sure. So a slack line is simply a line in which liquid and vapor phases both exist at the same time. That's typically at a local high point.
If it's flowing, we call it two-phase flow or open-channel flow. Of course, it's not technically an open channel because you have vapor, but the vapor space does rob you of capacity. Well, also it also creates other kinds of operating problems, right? Right.
Yeah, we've got a couple, you know, whether it's if it's running, there are some leak detection implications with that. And if it's down, you know, if we shut down and we don't have a tight line, you know, typing the opposite of slack, we've got to leak detection applications there too, so we can get into that. Cool. Maybe we'll just start and you guys can talk a little bit about what are some of the things that could cause a line to go slack.
Sure. So there's a couple of main things that cause a line to go slack while you're running. Before we start, a quick terminology thing, from marathon pipeline, slack line, is pretty much any condition where there's vapor present along, whether the line is flowing or the line is shut down and not moving product. Some operators choose to use the term column separation.
We don't use that term. We just use slack line. When a line's running, the things that typically calls back, calls a slack line is if there's insufficient back pressure. So sometimes like when we're coming down into a river valley, you clip the high point right before you come into a terminal that's going to load barges.
And that kind of case, you need more than just a delivery back pressure to make sure that you're clearing the high points and that your local pressure at the high point is above the vapor pressure. On the flip side, if you're discharging it too low of a pressure and you've got a big hill in the middle of your line, you could also cause the local pressure at that high point to go to vapor. The last one's fluid properties. So we do a batch operation and we'll carry many different kinds of fluids on the pipeline.
So the same line is carrying diesel fuel with a very low vapor pressure and also be carrying propane and pressure controls have to be designed to use both of those fluids with very different vapor pressures. So you know, one day when you're carrying a line full of all diesel fuel, everything's fine the next day you switch over and you've got propane in the line and you're cutting the high point, which means your local pressure at the high point is less than the vapor pressure of the fluid. So it boils off and creates a vapor pocket. Right.
So first definition, high point, that sounds straightforward enough. What's a high point? The high point is there are actually a couple of different ones. There's a local high point.
So if you've got a pump station for you, another pump station, it could be the local high point in that signal line. The other one is the highest point on the line between the initial receipt location and delivery point. Yeah, it's just a hilltop basically. It's a simple term.
Yeah. Right. And then what is vapor pressure? You can think of it as kind of the boiling point of a liquid.
So we want to talk about water at normal atmospheric temperature. Water wants to boil at 212 degrees Fahrenheit, but as you increase that pressure, your boiling point continues to go up and it works in reverse. If your pressure drops below atmospheric pressure, it will start to boil off at lower and lower temperatures and the vapor pressure, we just kind of save vapor pressure in the industry and we don't tie it to a specific temperature on the liquid side. We just got to say all the vapor pressure of propane is typically like 147 PSI and it's actually the vapor pressure at the temperature of the lines flowing at.
So you need to know both things to manage slack lines. If you've got a line that's warming as it goes up through flowing along the terrain, that vapor pressure is changing. The vapor pressure to circle back to the original question is just the pressure at a given temperature at which it flew and will begin to boil or transition from a liquid to a vapor. Right.
And that sounds, I mean, that sounds relatively straightforward, but I know that that operationally in a liquid line, particularly if you're using multiple products in that line, and that's a big deal. And of course, reverse is true if the product gets too cold and congealed, become a solid. Yeah, I think they have a lot of trouble with that in the gas world with the gas hydrates. We don't see a lot of that in the liquids world.
Well, it depends if you're using a bunker fuel or some of the, some of the fuel oils used for power generation, those have to be heated because they solidify at like 90 degrees Fahrenheit, 80 degrees Fahrenheit. Yeah. So there are some exceptions to that. And I think the thing that's interesting in this whole conversation and why this becomes complex is that vapor pressure is dependent on the product that's in the line and on temperature and pressure.
So it's a combination of those three things that determines what your vapor pressure is. Absolutely. And then you also use the term back pressure. So we ought to impact that a little bit.
So what's a back pressure? Back pressure is the pressure that the line delivers at its termination point. So, you know, typically when we're doing a first design, we'll start at a tank. So it's delivering from one atmospheric storage tank.
It goes potentially hundreds of miles to multiple pumps and it ends up delivering to another atmospheric storage tank. And at the delivery end, we'll start with atmospheric pressure and work through the elevation change in the tank. So you add in your static head of whatever that fluid is and the height of the tank. And then you look at the rate the system's flowing and calculate all your friction losses from where the pipeline ties into your delivery facility and add all those together.
So you add in and we got five PSI through a meter run that you're going to lose. You've got a strainer that can potentially lose 10 PSI and then you've got a tank. It's got another 10 PSI. So you stumble those together and you end up with 25 PSI back pressure at the flow rate.
You're running. If you're back pressure at that point and you put a hydraulic gradient in it, which is your friction drop per mile and you look back the line to where the gradient goes over the height point, if the pressure there is lower than vapor pressure, then you have to increase back pressure in your delivery facility, which would you can look at, do I want to do something like decrease the size of my tank farm pipeline? So I've got more back pressure in the facility or the real common thing and the thing we do a lot of is you put a back pressure valve in, which creates variable friction loss so that you can run the line always in its optimal way. I mean, you don't want to always be burning off 100 PSI through your facility.
If sometimes you need 25 and sometimes you 100. We have some lines that give about 40 to 50 pounds of back pressure. We've had lines that keep 400 pounds of back pressure in areas where the elevation profile is treacherous. Right.
You know, this is one of those things that I say this all the time, but everything's easy until you know enough about it. And this is one of those conversations where on the surface of it, it seems pretty easy, but it gets real complex real quick as you start throwing in all the variables. Right. So, you know, a simple, a simple illustration of this for listeners that might not have ever been exposed to this stuff that we're talking about, the typology.
If you think about a straw and I'm trying to move liquid through a straw, if I'm, you know, if I've got a mouthful of water and I'm blowing through a straw, I put my finger over the end of the straw, I can blow real hard and I'm not going to get any fluid to come out. If I just, you know, if I remove it, it's just going to come right out. If I take and I just leave a little bit, I'm going to get a stream of water and that water, if it's, you know, if it's a high enough pressure stream is going to go to vapor pretty quickly or small droplets pretty quickly. So all of this conversation about slackline is managing that reality in hundreds of miles a pipe.
Sounds simple if you, if you say quickly. So, you know, don't slow down. Right. And it's, you know, we'll say that nothing is ever empty.
And we talk about an empty pipe. Well, that pipe may be full of air. You know, we say, you know, one goes slack. Oh, okay.
It's empty at the top really. That's a vapor pocket. All of those things have to be managed. It's, it's never empty and air and vapor have to be managed very differently.
So just makes our job fun. Well, that's right. That's right. Fun.
That's the perfect word. So let's talk a little bit about normal startup and shutdown because those are the three key operating conditions you get concerned about around slackline. So let's give the listeners a definition of normal startup and shutdown and why slackline is a different consideration in those cases. I mean, honestly, it might be easier to start with, start with a shutdown because we don't like to start up a line having been slack, you know, for a very length of time due to a leak detection purposes and we can talk about that in a bit.
So when we shut our lines down, we've actually taken a great efforts to do studies on all of our pipelines to model their particular shutdown characteristics for those, those elevation profiles, the pumps, as Jason mentioned, we have back pressure valves on several lines that we will tune transient models to accurate line conditions. We will develop shutdown procedures to try to trap as much pressure as possible on the line. You don't want to trap so much that you pop a relief valve or you exceed that 110% of MOP, but we also don't want to trap nothing and shut the line down in the slack condition. So on all of our systems, that's a big thing that our group does is we will model those shutdowns.
We work with the operations center on procedures to shut it down and trap as much pressure as possible. And then that way, when we start up, we know that we've had we've had good leak detection the whole time. On the startup of a line that has gone slack, one thing that's that's difficult about that is when you have that vapor cavity collapse at one or several high points along your line, you're going to have a pressure spike there that's not going to be seen the transmitters on either end. And industry literature indicates that that would be typically about half of a typical jukowski spike, which is the instantaneous search bike you get on a valve closure.
So there's a there's a bit of a peril there. We're currently working through the, uh, working through the phases to manage that. Yeah. You know, we probably I'll talk a little bit about jukersky and, you know, what's otherwise called a water hammer and why that's such an important consideration in this, but, um, so let's, if we could, we just maybe would just depart on that a little bit.
So, you know, when you think about normal operation or so, what's sometimes called static operation, right? That's just the line is flowing and it's flowing around its design pressure, around its design parameters. So that would be kind of considered normal operation. Another way to refer to it.
When I'm shutting down, I've got to close valves to hold that pressure and the rate at which I close those valves is material. If I close them too fast, I'm going to get water hammer and I'm going to get that, I'm going to get that, I'm going to get that fresh pressure spike and I'm going to move it up and down the line. And that can be very damaging. So, you know, this is not, it's a non trivial thing, right?
To just shut a line down and hold pressure, but without causing pressure transients. Right. Yeah. So, and that's where we, um, we have all of our lines either have a main line, surge relief valve at the delivery location to manage this, or we'll put a flow control on the line to keep the shutdown at an intrinsically safe pressure.
Right. So if we did have a valve closure, we would be able to withstand that spike and that pressure build without exceeding 110% of our NOP. Right. So do you guys have any situations where you would automatically close a valve on some kind of an emergency or upset or is that all done by when I say automatically, I mean, through the automation versus by a controller operating a valve.
So we don't have that particular piece of equipment. We actually, we're taking the stance that that actually induces more risk on the system than having an operator or a human in the loop. You know, anytime you have something that's automated, it's really hard to model every potential scenario and make the programming applicable across the board. And, you know, there's storage and industry of a lightning strike, the hit of valve actuator and maybe actuator go closed all by itself.
It adds a level of risk that we're really not willing to adopt. So all of our valves are commanded, closed by an operator in our operations center when they feel the need to close that valve, following the normal procedures. Right. Now, that's why I asked the question.
I think it's important for listeners to kind of understand that because that's a that's a question for someone who doesn't understand this issue of managing pressure and pressure transients that they often don't understand is that you got to be very deliberate about how you close these valves. It costs problems and they don't, you know, some of these valves can take, you know, several minutes just in normal actuation to close. And you do that on purpose to not have these water and issues. Anybody that's got, you know, valves at the house and is closed up quick and has heard the, you know, the, the, the lying shake in the old house, that's, you don't want that happening on the pipeline.
No, there's a, there's a significant amount of energy that's in these lines. And the way that they're being managed, they are, they're safe and the energy is handled in an appropriate manner. But every time you start to try to force the systems to make fast actions, you start to erode some of the safety that's built into these systems. Yeah.
Yeah. Very well said. So let's let's kind of circle back and talk a little bit about what can cause a line to go slack during a shutdown. So the most common cause of slack for us is cooling during shutdowns.
Our product, whether it's crude or refined products, is typically at least several degrees warmer coming in than the ground. And it doesn't take much between 50, you know, 50, 100 psi, you know, is not uncommon to lose for just one degree Fahrenheit. So, and especially if you're coming out of a refinery processing unit, maybe it's 100, 100, 510 degrees and the earth is at 60 or 70. It's not going to take you too long to drop 300 or 400 pounds and it goes slack.
And there is an equation in API 521, specifically section four that we use that relates the pipe properties with the fluid properties and then pressure loss for temperature loss. So when we shut down and we know we're going to go slack or we know the line's going to be down for three or four days, our operation center analysts have a tool that we have put together in the knowledge management database. It's called the slack line tool and we've got profiles of lines. We've got screenshots of what the detection system is going to look like.
We've got notes on which segments go slack right away, which once never goes slack to try to give them a point of reference for what's normal and what's abnormal. And with just its only temperature loss and not a leak, there's a nice sort of slow and steady decay that they've been trained to recognize. And if you had a rupture while the line is down and static, it's going to get a little bit steeper. And there's many times that we'll get called in from our group to log into the system, maybe after hours and look at a pressure trend and then look at ground temperature probes near the line and look at ambient weather conditions and try to figure out if it's just due to cooling or if it might be something else going on.
As you're giving that description, I've got pictures going through my mind of what that looks like. And so I was quite there for a second as I was thinking about it, because it's really, you know, that's a huge amount of work to build that up in a way that the operators can use it effectively. And I think that's because these situations are normal, but not usual. Knowing what the line's going to do given various environmental and fluid conditions other than just pump the fluid is not really what you're doing as 80% of your job.
You know, 80% of your job is move the product. Correct. So one of the things that I think the whole industry as a whole was trying to do is to ask the controllers or whoever is sitting in their operations and running the line to think through their head, what do I expect this line to do when I make this change and compare what their thinking should happen with what they're actually seeing. And what Kyle was talking about, one of the things that we've done, and I know there's some other companies are doing the same thing, is to save pressure trends of what a typical slack line event looks like following shutdown and provide historical pressure trends and historical leak detection system output for those events.
They can look back and say, you know, it's, I'm pumping product out of a tank that's at 90 degrees and it's winter. So I'm going to expect the line to lose pressure pretty quick. And then they watch what's happening in the line and lose his pressure a lot faster than they would expect. It goes to lack a lot sooner and they can pull up a historic trend and go through and take a look at what has the line done in the past and compare that with what it's doing right now and give themselves a level of safety that, yes, I've seen it do this before.
This is this is typical for this line or no, this is not typical. This is something that I've never seen before. Right. And that's that's a really important point here is that this is that this kind of work you're talking about in terms of doing the hydraulic analysis and the calculations versus what's actually going on in the control room and the nature of that and the need to collaborate with.
I think you're making some really important points to be thinking about as a liquids operator is what should the controller expect to see? And how do they know? You know, what's where do they go to get something factual to compare to? It's a big deal.
Absolutely. Let's talk about let's shift a little bit. We'll talk a little bit about startup. What would cause us a line to go slack on startup?
But typically if you're getting ready to start up a pipeline, one of the ways that you can end up with a slack event during startup is that you would open the head gate at your delivery location. And that allows the pressure to drain off into that delivery station. And if you don't have sufficient pressure on the line prior to opening that or if there's any type of delay that happens in your starting up the receipt end of the pipe, you can have sections of that pipe go slack during that startup event. And again, that's where we would look for what is a normal trend that we would expect to see in that case.
Right. So we're going to be common, certainly not desirable, but it's fairly common for the kind of reasons we were talking about earlier here. So how do I, what are the kinds of things I'm going to do if I know I have a line that slack and I've got to start it up? What am I going to be looking to do?
Well, I guess at least here, we want to understand kind of how slack is the line. So how much vapor space do we anticipate is in that line so that when we start it up, we have some understanding of how much fluid we're going to be pushing into the line before we expect to see a response at the other end. Because that's an area where you, at least with our detection system, there's a time period where you're putting more fluid into the pipe than you're taking out and that can be a cause for concern if it's more than you anticipated. Yeah, the scariest feeling is when you know you've got a line that slack and it's several hundred miles long and you're going to start to see meter counts on your receipt end and you don't see any corresponding meter counts on your delivery end and just looking at it, you're putting a lot of barrels of hydrocarbon into the line and you're not getting any out.
And if you haven't done the research prior to that to know that you've got a thousand barrel vapor space in the line, that has every signature of a leak event. And being able to tell the controllers that they need to expect that is something that's very important. You just, you don't want to expect them to every time they turn it on, think, I'm going to add two thousand barrels to this before I start to see my pressure drives. That's the easiest way to, and we throw around the term normalization of deviance.
That's one of the ways you cause that is the controllers get used to the fact that they're going to turn a pump on and run the pump for 30 minutes and not see anything. And the next week is they're going to run the pumps for 31 minutes and not see anything. And before it's over with, you've got a pipeline that's pushing hydrocarbon out onto the ground where you don't want it. Right.
So, yeah, so again, and that's kind of what I was kind of driving out in the question is there is a need to understand where I'm starting from. Absolutely. That I have that I have a vapor space and how big is that vapor space and what should I anticipate once I start closing that vapor space? It's interesting and for people that, you know, aren't familiar with liquid operations kind of having a knowledge of, oh, that's why this is hard.
That's why this is complex is important. Even if you're not really working in that domain. Yeah, I know here we, we actually monitor, we track all of our slack lines. If any segment of a system goes slack, we receive an alarm in our OC and we track each of those alarms and we won't restart that pipeline until the trends have been reviewed and that we verified that it was a slack line that followed a normal or anticipated trends and it's been reviewed by someone other than just the console and then we'll approve it for restart of that line.
So, it's something we take very seriously here in our operations. Right. Yeah. I think that that's probably the most risky thing that you do in liquid pipelining is start at the pipeline.
It's where you tend to know the least about what's happening and where you need to know the most comparatively. Right. I agree. Yeah.
So it's, I think that that's, that's really important that you guys are laying kind of out a process of, you know, we've got to have a, we've got to have some seniority, some experience, look at it needs to be more than one set of eyeballs and then we need to have a plan for restart and that's, you know, pretty much every time we start a pipeline, we've got to have a plan for that particular restart. Let's talk a little bit about how slack line impacts leak detection. Sure. Which part of it do you want to talk about?
There's a lot of ways that slack line impacts our leak detection systems. I would say let's just kind of start at a high, just a high level and not because we could probably do, you know, a whole 30 minutes, 45 minutes just on that subject alone. So maybe we'll just kind of address it from a high level in a leak detection system. The meters and the pressure transmitters are eyes on the pipe and pressure transmitters can see as far at least in a liquid line can see as far as there is positive pressure on that pipeline.
So our model can interpret pressure changes as volume changes anywhere along that line as long as there's positive pressure. When you get to a vapor pocket, that vapor pocket, the pressure in that segment of the line doesn't care what elevation changes happen in that pocket. And so we get effectively a blind spot for our pressure transmitter. Now we try to compensate for that by having the model calculating the amount of vapor space, you know, going to heat transfer calculations to determine how much vapor we would anticipate and establish where that vapor liquid barrier would be.
But at that point, we're really calculating a lot more unknowns than we have knowns. So there's a great deal of uncertainty that comes into our leak detection models when we have those vapor pockets in the line. Yeah. That's a hard thing to speak about in simplistic terms, I think, you know, because that the nature of a fluid and how it carries pressure versus the nature of a vapor and how it carries pressure very different.
And that causes confusion, if you will, for the leak detection model. Yep. So it's, yeah, it's very, very problematic. So I know that some operators have, you know, have have policy where they will not run with slackline.
You know, if they get slackline, they shut down and close it up before they run. They just, you know, they won't and some operators do because they have to, because of the nature of the elevation changes in their system, it's just impossible to not have slackline. And they tend to be very on what's going on with slackline and how that's affecting things. So it's a big deal.
So what are the things, what are the key things you need to do to mitigate slackline? Well, some of the methods we talked about earlier are back pressure valves, then detailed shutdown procedures to keep us from going slack. Another thing is if you are going to experience a slackline, is understanding the limitations of your leak detection system and looking for any way that you can to supplement that in the areas where you're concerned about being slack. Right.
And in the, in the running condition, we have station suction set points that'll keep the gradient. There's only one or two places on all of our lines I can think of where we ever go slack and it's extremely, extremely rare because we have a suction set point high enough to keep the gradient tight as Dan was saying, to keep positive pressure at all times while we're running. I guess, you know, I'm sitting there a lot of times I'd like to try and do kind of how do you wrap all this up? You know, what are your three key takeaways?
I think this one is a little bit more challenging maybe than than some of the other conversations we've had on the podcast because there's a, there's really a lot that goes into this. I think I think the first thing is slackline increases operating risk. That's the key takeaway. And it increases that risk for a myriad of reasons.
It, it, it impacts the effectiveness of my leak detection and it creates the opportunity, if not properly managed to, to create pressure spikes that I don't want to have. So I think the first thing is just, you know, it's, it's a risky slackline represents risk. I think the second part of this is, is it from an operational standpoint, second takeaway is from an operational standpoint, you got to have a plan each time you have a slackline and that's got to involve the appropriate people and experience to evaluate it and address it. Um, and then lastly, that when you have slackline, your leak detection is impacted and you may need to think about alternative means of leak detection when you have slackline.
So there's one other thing that I'd like to get your comment on. Um, and that is for periods of time when a pipeline is shut in and you've got cooling operating, do you think it would be appropriate to have a completely different type of computational leak detection for that situation? And what might that look like? I'll answer, I'm not the leak detection expert in the room.
That's Mr. Sensal, but I'll answer from kind of a hydraulics perspective. If you've got a line that's going to be slack for a while, one of the things that I think it's important to look at is what your historical pressures are, because the changes in elevation create static pressures on your pressure transmitters. And if you're looking at a transmitter and it has, for the past five years of his life, it has never dropped below 17 PSI.
And today it's a 10. That's a pretty big smoking gun that something abnormal is going on. And that is controller monitoring is a recognized leak detection method. So that is one, one method I would say would be an alternative way to look at the line.
Dan's got some experience with other systems that might weigh in on. Yeah, I mean, from taking the look at what's historical, you know, you could also apply some type of statistical model to your pressure trends to show that it's within the normal, statistically normal range for what your trends have done during that shut-in procedure or shut-in time period. Some other things we can do is if you know the line is going to be down and slack for some period of time, as Jason was saying, the pressures shouldn't change on that line. So you can tighten up some deviation alarming or some limit alarming on your data system.
So that, you know, instead of a large pressure change signaling an alarm, it might be a couple of PSI, which will give you an alarm. You also can increase aerial patrols or you can increase ground patrol of your line to supplement that leak detection system while you're in that slack condition. Yeah, I think the kind of thing I was driving at in my question is the idea of watching your pressure, because theoretically, if I have a line isolated, I should hold my pressure within within some bounds based on how much cooling you have. Right, exactly, which is a number you can mathematically model.
Right. So, you know, it's interesting. I think as, you know, as I look at leak detection in our industry, you know, a lot of our focus in the last 10, 15 years has been on the ability to find the smaller leaks in normal operating conditions. And I think that focus is beginning to change or at least be extended where we're starting to look now.
How do I find leaks when I'm not doing, you know, during startup or shut down or or shut our shut-in? How do I find leaks in those situations? Because actually that math is a little different. Absolutely.
Well, guys, look, this is great as always. I really appreciate you coming on board. Um, and I'm looking forward to having some more of these conversations. Oh, sir.
Thank you. Russell. Thanks, Russell. I hope you enjoyed this week's episode of the Pipeliners podcast and our conversation with Dan, Kyle and Jason with marathon pipeline.
I certainly did. And I certainly learned some new stuff. Just a reminder before you go, you should register to win our customized Pipeliners podcast, Yeti Tumblr. Simply visit pipelinerspodcast.com slash win to enter yourself in the drawing.
If you would like to support this podcast, please leave a review on Apple Podcast, Google Play or whatever smart device podcast app you use to listen to the Pipeliners podcast. You can find instructions on the website. Finally, if you have ideas, questions or topics you'd be interested in, please let us know on the contact us page at pipelinerspodcast.com or reach out to me on LinkedIn. Thanks for listening.
I'll talk to you next week.