In this episode, host Russel Treat captures conversations with industry experts during the 2024 API Pipeline Conference in Salt Lake City. The topics discussed include insights into pipeline safety, stakeholder engagement, alarm management, and the importance of community and first responder collaboration.

This episode provides a snapshot of current trends and challenges in the pipeline industry featured during the Pipeline and Cybernetics conference.

Conversations from the 2024 API Pipeline Conference Show Notes, Links, Insider Terms, and Full Episode Transcript

• API Pipeline and Cybernetics Conference took place on May6-8th 2024, in Salt Lake City, Utah. It will be held in Austin, Texas April 24-27th, 2025. Visit API.org here for more attending information.
• API RP 1173 established the framework for operators to implement pipeline safety management systems. The PSMS standard includes 10 core elements.
• Pipeline SMS (Pipeline Safety Management Systems) or PSMS is an industry-wide focus to improve pipeline safety, driving toward zero incidents.
  • API RP 1185 aims to use the Pipeline SMS framework to build on stakeholder engagement to support more community involvement and dialogue.
  • API RP 1187, also known  Landslide Integrity Management for Pipeline, is a recommended practice from the American Petroleum Institute that focuses on geohazards and pipeline integrity management.
• 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.
• PHMSA (Pipeline and Hazardous Materials Safety Administration) is responsible for providing pipeline safety oversight through regulatory rulemaking, NTSB recommendations, and other important functions to protect people and the environment through the safe transportation of energy and other hazardous materials.
• Upstream is the operation stage in the oil and gas industry that involves exploration and production. 
• Midstream is the processing, storing, transporting and marketing of oil, natural gas, and natural gas liquids.
• Downstream is the process involved in converting oil and gas into the finished product, including refining crude oil into gasoline, natural gas liquids, diesel, and a variety of other energy sources. The closer an oil and gas company is to the process of providing consumers with petroleum products, the further downstream the company is said to be.
• ILI (In-line Inspection) is a method to assess the integrity and condition of a pipeline by determining the existence of corrosion, cracks, deformations, or other structural issues that could cause a leak.
• 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.
• 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.
• Leak Detection is the process of monitoring, diagnosing, and addressing a leak in a pipeline to mitigate risks.
• Rhett Dotson is a Chief Engineer with D2 Integrity, LLC. Connect with Rhett on LinkedIn.
• Terri Larson, APR is the owner of Larson Communications & Consulting. Connect with Terri on LinkedIn.
• Mallory Gill is a Sr. Regulatory Analyst with EnerSys Corporation. Connect with Mallory on LinkedIn.
• Jack Willingham is the Yazoo County Emergency Management Director at Yazoo County. Connect with Jack on LinkedIn.
• Jerad Stack is the CEO and Co-Founder at Flowstate Solutions. Connect with Jerad on LinkedIn.

Conversations from the 2024 API Pipeline Conference Full Episode Transcript

Russel Treat: Welcome to the “Pipeliners Podcast,” episode 338, 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.

Since its formation as a standards setting organization in 1919, API has developed more than 800 standards to enhance industry operations worldwide. Find out more about API at API.org.

Announcer: The Pipeliners Podcast, where professionals, bubba geeks, and industry insiders share their knowledge and experience about technology, projects, and pipeline operations.

Now your host, Russel Treat.

Russel: Thanks for listening to the Pipeliners Podcast. We appreciate you taking the time. To show the appreciation, we give away a customized YETI tumbler to one listener every episode. This week, our winner is Christina Rodriguez Mendez with Genesis Energy. Congratulations, Christina. Your YETI is on its way. To learn how you can win this signature prize, stick around till the end of the episode.

This week, we’re going to speak to a number of people as we capture conversations from the API Pipeline and Cybernetics Conference in Salt Lake City.

Hey, Rhett. Thanks for coming by. I heard that you were trying to take over my booth while I was away on a call for a second. I’m thinking we should negotiate a truce.

Rhett Dotson: Not trying. It was pretty much successful…

Russel: [laughs]

Rhett: …but my business partner hadn’t shown up with the backdrop that I needed to replace it with. D2 Integrity pipeline.

Russel: I appreciate that.

Rhett: Do we need an armistice?

Russel: We should have a ceasefire or something.

Peace settlement, negotiated settlement. I don’t know. Something like that. Here we are at API Pipeline Conference. What are you learning so far? What are you taking away?

Rhett: I learned that the rains make it really hard to get out of Houston.

I actually got here very late last night. It’s early.

Russel: We had one of our team that couldn’t get out at all. He’s not getting here till midday today.

Rhett: I’m looking forward to joining a couple of presentations. There’s one on cracks and ILI. I’m looking forward to seeing what’s going on there. Then there was another one on hard spots. I always like to keep up with those two emerging threats. What about you?

Russel: We’re giving a couple of papers, one on aligning policy and procedure with the PHMSA requirements and inspection protocols and another on streamlining and facilitating alarm management, which, in the control room area, is a hot topic these days.

Rhett: It might have had a little bit to do with some failures that I remember reading about.

Russel: A lot of people are just reevaluating what they’re doing with their alarm measurement programs. The control room management rule has been around now 12 years. Everybody put something in place. Like with all new regulations, there’s kind of an arc.

We’re running about two years behind because we took a two year pause because of COVID. We’re about 10 years in. It’s time for people to reevaluate, looking for more effective, more efficient ways of managing these kinds of programs.

Rhett: Should people be coming by your booth to shoot the podcast with you at this conference?

Russel: Absolutely. We’re looking for people to come by and talk to us. You know this. When you’re running a podcast, you’re ravenous for content.

Rhett: That’s right.

Russel: All of the thought leaders in pipelining, and particularly around control room and integrity management, are here. We’re going to try and grab as many as we can.

Rhett: If the booth is empty, what should they do? It was empty when I came by, Russel. Greg should be guarding the booth. Greg’s behind the camera. Greg will be guarding the booth.

Rhett: There it is. Come join Russel on the Pipeliners Podcast here at API.

Russel: Nice. Thanks for the plug. That’s awesome.

Russel: Terri, good to see you here at API Pipeline Conference.

Terri Larson: It’s good to be here.

Russel: You’re looking sharp, as always.

Terri: I try.

Russel: See, when I do an audio podcast, people don’t get the benefit when these attractive ladies are on the podcast, but we’re doing this one on video.

Terri: [laughs]

Russel: I’m working on my flattery. How’s it working?

Terri: You’re doing so good, so far. 

Russel: Excellent. What brings you to API this year? Anything in particular that you’re here to see or learn?

Terri: Mostly, it’s to see and hear how people are talking about stakeholder engagement. It’s a critical part of communication. It’s critical to pipeline safety, everything that goes on around pipelines, how we engage with our stakeholders, who go beyond those audiences, for public awareness, and have for years.

We’re finally recognizing that as an industry. That’s really why I’m here, is to see how those conversations are evolving.

Russel: Of course, we have the new API recommended practice, 1185, on stakeholder engagement. There’s a number of sessions on that, a couple of panels on it. Going to be a lot of conversation on that, I expect, over the course of the next couple of days.

Terri: There will and there should be. Was just in a really interesting discussion on environmental justice with the Marathon folks. I’m really looking forward to the 1185 sessions this afternoon. I worked on an 1185 website that we’re just launching for API today, pipelinepublicengagement.org. I think .com will work as well.

Russel: As we’re having this conversation, I’m going to take us down a rabbit hole, if I might.

I am prone to do this.

Terri: Like you don’t…I know. 

Russel: I didn’t warn Terri at all. Last week, I was at AGA Operations Conference in Seattle. Of course, protesting is a cottage industry in Seattle. We had protesters. I so wish I had had something to hand out to them. Like, “Here, just go here. Go to this website.”

Terri: Yes, but go with the conversation, not the thing.

Russel: It was interesting. They were actually pretty much pretty polite. They weren’t rude. They weren’t aggressive. There was a 5K run that the AGA does as part of their Ops conference. The protesters went along with. They were having a hard time keeping up. It was humorous.

Anyways.

Terri: I did hear about this from someone on the plane yesterday.

Russel: Good. I guess the point I’m making is this whole conversation about stakeholder engagement, it’s broader than just the people we historically think of.

Terri: It is, but it’s also being willing to sit down with people who don’t agree with us and a willingness to actually listen to what they have to say and then engage in a conversation built on what they have to say.

Russel: I will leave that to you.

‘m being a little humorous. That is a really challenging thing when some of the people that we would be talking to are so far away from where we are, just in their mindset and belief systems and what they believe to be true about our industry.

Terri: Often though, if you really get into that conversation and you actually listen to what they have to say, you can find common ground. Then you build on that common ground. You may never be friends, but until we actually are willing to listen to what they have to say, as an industry…

Historically, we don’t do that, sometimes for good reason. Until we’re really willing to hear what they’re saying, we’re never going to get past that.

Russel: If you go back to our founders and how they built our system of government and such, it was designed for those kinds of conversations to happen. One of the problems with social media is it causes people to be in their little echo chambers. They’re fed only what they say. Getting across that’s tough.

Anyways, this whole stakeholder engagement conversation is a big one, I guess is what I’m trying to say.

Terri: It is, and it’s evolving. It’s not new. There are other industries who’ve done this really well for a really long time. For us, it’s new, and it’s evolving. We need to allow ourselves to go on that journey.

Russel: I got to say that every time I talk to you about this, I always feel challenged and educated because your expertise and what you do and your experience is so different than mine. I’m always fascinated by your perspective on it.

I’ll be interested to know what you learned over the course of the next couple of days. Maybe we’ll get you back on a podcast, and we’ll do a more detailed debrief.

Terri: Sounds good.

Russel: Good to see.

Terri: You too.

Russel: I am sitting here at the API Pipeline Conference with my junior podcaster Mallory Gill. She has grown from not even wanting to be on the podcast to hosting the podcast. We’re probably going to get her a podcast later. She doesn’t know that yet.

Mallory Gill: We should just start recording our meetings. That’ll be my podcast.

Russel: That’ll be the podcast. You just came from the AGA Operations Conference.

Mallory: I did.

Russel: Now you’re here, a few days later, with the API Pipeline Conference. What have you learned so far? What are you here to learn? What do you want to know before you leave?

Mallory: Oh my. Hard to define just a couple of things. We’re moving into different spaces at EnerSys. There’s a lot of learning to be done in program implementation. We’ve historically been in a very niche part of pipelining for control room management, as you know.

We’re starting to move into more full program implementation. Anything that PHMSA governs or that the state governs, we have solutions for that now. I’m particularly trying to expand my expertise and become more of an asset to our folks in the integrity management space, PSMS, so a lot. There’s a lot.

Russel: What’s so true about what we do is there’s so much to learn. Even if you learn one domain really thoroughly, if you’re not in that domain for two or three years, you’re not current anymore.

It’s just a lot of information. We’re doing a paper on aligning regulatory requirements with company policies and procedures. Why is that important? Why is that a big part of what we do at EnerSys?

Mallory: It’s very important because you want your software to be fully integrated into your systems. Not only because I work in software, but in general, I’m an advocate for, when you implement something, you really need to find a way to commit fully to it to realize the value.

Russel: To get to the value of a new software, there’s always organizational changes and training and other things that have to occur to actually get the value. It’s never just about the tool. It’s always about what is the solution. The solution always requires people. That’s always part of it.

Mallory: It’s about aligning your organization as well, so not just aligning with “We have a new application that we’re using,” but aligning your organization, getting clear about everyone’s rules and responsibilities, making sure that everyone’s on the same page and working towards common goals.

Russel: Sounds easy if you say it fast.

Mallory: I know. I did say it fast.

Russel: My wife Susan always tells me, “Russel, quit saying that on the podcast,” but it’s true.

Mallory: It’s so true. It’s a nice, gentle reminder that we may sound a little preachy at times saying, “Just do this. Do that.” It’s easy to say when you’re not the one doing it. Believe me, we see the pain in some of our operators and our clients. We’re very sympathetic to that.

Russel: I’m reflecting, as we’re sitting here, talking, that I got you on the camera at an AGA conference, which I think was your first conference we ever went to. You’d been working with the company full time for just a few months. What’s it been like, as a young person, learning the pipeline business?

Mallory: Oh my gosh. I have nothing but positive experiences from these conferences. I was so fortunate that you all invited me to be a part of that as soon as I came on board. I was still in college. I was freshly out of a summer internship with EnerSys. You all took a risk. You said, “We want you to come to…”

Russel: We didn’t really take a risk. We saw your potential.

Mallory: Sure. Depending on how you look at it.

Russel: We invested.

Mallory: Yes, absolutely. The best experiences, the best people. I think I said this probably in the first one too. Everyone is so willing to educate. It’s a community.

Russel: That’s the thing that I wish people who don’t know our industry knew about our industry, is how serious we take this, how hard we work on it, and how we’re really interested and eager to find people to train so there’s somebody to carry on to do this after we’re no longer doing it. It’s great.

I’m curious, what do your peers say when you tell them what you’re doing, you’re working in the energy industry? I know you have friends scattered around the country.

Mallory: It’s actually funny. I was just on a bachelorette trip before I came here.

Russel: We won’t talk about that. We’ll talk about that off camera.

Mallory: Very tame.

We were in the car. We were all saying what do we do for a living. My friends have only just now been able to get their elevator pitch down for what I do. They’re like, “She works in control rooms. She does consulting and compliance.” They think it’s awesome. They think it’s really cool. They’re very supportive of all the traveling I get to do. They love seeing me thrive.

Russel: When I go see my family on the West Coast…They’re somewhat conservative, but they’re in a bastion of…People ask me, “What do you do?” I’m like, “I work in pipeline safety.” Versus “I work in pipeline operations.” Just understanding your audience. Right?

Mallory: Right.

Russel: Exactly.

Mallory: I got some friends who are in more of the engineering side of oil and gas as well.

Russel: That’s right. Cool. Thank you for sitting down. She didn’t want to. I had to drag her in, just for the record. As always, she does great.

Thanks. Thank you very much. We’ll look forward to having you host again and ask me questions.

Mallory: I think I like that better.

Russel: Actually, you want to ask me a question or two before we get off the microphone?

Mallory: Sure. What are you hoping that people will take away from your presentations this week?

Russel: Oh man. Couple of things. I’m doing two presentations. One is in the pipeline section– we talked about that–aligning. The other is about streamlining alarm management, facilitating alarm management.

What I want people to understand is that with really good, thoughtful planning and an intentional selection of systems, and intentional organization of the human capital, you can get better, but it takes all three of those elements.

We’re talking, in one domain, about streamlining or doing what we call natural compliance, which is you figure out what you need to do. You implement the systems to do it. Then all of the recordkeeping and all of the demonstration of compliance is embedded in your systems so that you pick up velocity.

Likewise, in alarm management, what we’re doing there is, right now, we’re really focusing not so much on the software but on the program. A lot of pipeline operators are 10, 12 years into doing alarm management. They’re starting to look at what they’ve been doing and ask some questions about “Are we really doing the right thing? Are we really adding the right value?”

We’re at a place where it makes sense to do a program level reset for a lot of operators, just to reconsider. There’s value to get out of alarm management that we’re not getting yet as an industry. Basically, what I hope people take out of it is some ideas about things they can do better around their systems and their human resources around those systems.

Mallory: Very cool.

Russel: Cool. That was a hard question. I’m tired now.

Mallory: I know. I didn’t throw you a softball. Sorry about that.

Russel: Good. Thanks.

Mallory: Thanks, Russel.

Russel: I’m sitting here at API Pipeline Conference with Jack Willingham. Jack, tell us, what is your job? What do you do?

Jack Willingham: I’m the Emergency Management Director in Yazoo County, Mississippi.

Russel: Jack was directly involved with the CO2 incident in Satartia, Mississippi. I hope I said that right. He tried to coach me about three times.

Jack: Satartia is exactly right. You did really well. Most people say, “Satardia.” You did great. Satartia.

Russel: Satartia. Thanks for the coaching. I appreciate that. I think, Jack, that you have a very unique perspective that pipeliners need to hear, about what first responders are walking into, what’s the reality from them when there is a pipeline incident.

I know you’ve been going around. You’ve given some presentations and participated in some things. What is the message you would like for pipeliners to know about that incident in particular?

Jack: Not just that pipeline incident. That incident really brought it to life, but any incident or any involvement. Where pipeliners need to be involved is they need to engage with the first responders. They need to go inside these communities.

They need to visit the departments and find out who’s responding to incidents. They need to visit each individual department, see and meet the personnel, sit down and talk to them, learn their capabilities, and let them figure out the capabilities of the pipeline, to work together to try to close gaps in what they may need.

They need to go into these departments and then find out what equipment that these departments have and see if they have even close to the proper equipment that they need to respond to a specific incident with the product that that particular pipeliner has.

Not only that. They need to make sure that these guys are trained or have access to the training that they need to respond to these incidents. This is crucial. These are volunteers in small communities. We need to make sure that they have what they need to respond to these incidents.

Russel: That’s probably something that a lot of people don’t realize, is that a large portion of the folks that would be first responders on a pipeline incident are probably volunteer fire departments.

Jack: That is correct. As a matter of fact, your very first responders to most of these incidents are probably going to be a local law enforcement agent, like a deputy sheriff or something.

Russel: That’s absolutely right.

Jack: That is who who would get there first. You not only have to engage the fire departments. You’re going to have to go in and engage your law enforcement and get with these guys. These small sheriff’s departments are going to be rural.

I was, at one time, when I worked for the sheriff’s department, one deputy patrolling a 937 square mile county by myself. You’re going to have to make sure that these guys are prepared to do the basics of what they need to do to get people to safety in an incident like this.

Russel: That’s so very important. A lot of pipeliners, particularly the guys in the trucks, the guys that are working on the facilities, working on the assets, they know this. What would you tell pipeliners in terms of what’s the best mechanism to reach out to these guys and get the engagement?

I know that there’s a lot of conversation this year about API 1185, stakeholder engagement, and all that. That’s a big part of this conversation. What would be your recommendation to pipeliners about how to get that engagement?

Jack: Look, these small counties, they’re going to all have an emergency management director. This guy should be the center of all your responders. He’s usually going to wear multiple hats.

In my case, I’m the Emergency Management Director. I’m the Fire Coordinator, over eight departments. I’m actually the 911 Director, where I’m over the dispatchers. I’ve got direct contact with the sheriff’s department.

Your first step would be to go in and find your emergency management director and let him get you pointed in the right direction to meet with these people. Your second step is, once you meet with him, you need to get in with maybe some of your town leaders and your churches, to get involved with not just the responders but the communities that these pipelines run through.

We want to make sure the residents have a basic knowledge of what to do in the rare chance that there was an incident. Do you live near the ocean?

Russel: Fairly close. I’m probably 40 miles.

Jack: How many people in Iowa actually know what to do when there’s a tsunami? Most of them do because we teach them this. Why have we not engaged our communities themselves to teach them what to do? Even though there’s a rare chance of an incident, let’s make sure they’re educated on the basis of what to do when there is one.

Russel: This is an interesting challenge. This is something the pipeline industry’s been struggling with for years, about how to get the right level of engagement.

Just listening to you talk about all the roles you fulfill in your role, that sounds like an awful big job. It sounds like there’s a lot going on there. Getting to the top of that priority queue with those people is sometimes challenging.

Jack: It is. Again, just like with my job, I have a lot of jobs. Again, once you get into these communities, you’re going to be able to branch out. You’re going to be able to find the people that you need to assist you in getting this word out. You’re not going to be able to do it by yourself.

I can’t do all those jobs by myself. I’ve got to develop relationships within my community. I’ve got to trust people and get my word to them. They’re going to pass it and make sure we get it to the right people.

Russel: You just said a mouthful. It is about community. It is about relationships. It’s about building relationships with a community. Right on point.

Jack: It’s networking.

Russel: That’s what we’re doing here at this conference.

Jack: That’s exactly what it is within these communities.

Russel: We actually have a representative from the National Association of State Fire Marshals here, which I think is awesome…

Jack: That is awesome.

Russel: …on Partners Row. There is some outreach going on. We could certainly do more. One of the things that I wonder about, the unique thing about pipelines is what they’re carrying, each thing they’re carrying, has a different set of threats.

Jack: It’s all unique. That’s the whole thing. In the past or in the olden days, in the industry and even as first responders, we were all taught one response, one general pipeline. This is what we’re going to do.

With the emergence of things like CO2 now, the responses are just going to be different. We’ve got to make sure the word not only gets out to your first responders. The incident we had in Satartia, the word needs to get out to your local hospitals and emergency rooms. They simply weren’t prepared for the response from what happened in that particular instance.

Russel: CO2 is an asphyxiant.

Jack: That’s correct.

Russel: It’s not a combustible.

Jack: Everybody goes, “CO2 is not dangerous because it can’t hurt you.” That’s when I preach back, “A pillow’s not dangerous until they put it over your face.”

Russel: My first job out of the military, I worked in CO2. It’s not dangerous in small doses. When it displaces all the oxygen, it’s extremely dangerous.

Jack: Like I say, that pillow’s not dangerous till your wife puts it over your face.

Russel: No doubt. Where are you going? What are you doing beyond just coming to API this week? What are you doing to try and get pipeliners more effectively engaged?

Jack: Again, I’ve spoken numerous times in DC. I’ve spoken in front of PHMSA. I’ve been all over. I’m just trying to pass the word to everyone, not just pipeliners.

I’m not just directing this towards pipeliners. I’m directing it towards first responders that we have a responsibility to engage with the pipeliners also. We’re going to have to meet in the middle. We’re just going to have to make sure that we…

Russel: It’s just not the first responders and the pipeliners. It’s the landholders.

Jack: It’s the community members. It’s the politicians.

Russel: It’s the local communities. All of that.

Jack: Again, it’s the medical community. It’s just everybody. Just make sure we all come together and we’re prepared for any incident. No matter how rare it might be, just make sure we’re prepared for it.

Russel: The challenge is being prepared for that thing that very rarely happens.

Jack: That’s right. That’s correct. If we save just one life by being prepared for it, I think it was worth everything we put into it.

Russel: I know some people that have been involved in some of the major pipeline incidents. I’ve had some of them come on and talk on the podcast. Many of us will work our entire career and never have a direct experience of an incident. That’s a good thing.

Jack: That is.

Russel: The challenge is the few of us that do, we really need for them to share their experiences. What I would say is, when you make an emotional connection to the fiduciary responsibility that we carry as pipeliners and that first responders carry for their communities, that emotional connection matters. It helps us. It helps ground us.

It helps connect us to what we’re doing, why it’s important. It helps us learn things that we need to have available to us even if we’re not using them every day.

Jack: That’s a great statement. I agree. I agree completely. Like I say, again, we just need to make sure that we do our part from the emergency management side and the pipelines do their part. If we can get everybody together, we can have our communities prepared. We can have our responders prepared. We’ll be a lot better off.

Russel: Thanks for taking the time to talk to me. Good luck with the rest of the conference.

Jack: Man, I enjoyed it. Thank you very much.

Russel: Thank you.

Jack: It was great to meet you.

Russel: Bye.

I’m sitting here at the API Pipeline and Cybernetics Conference. I have Jerad Stack with me, of Flowstate. Flowstate is a leak detection company. I understand you guys are doing a paper, right?

Jerad Stack: We are. We have a paper tomorrow morning, which means nothing to your listeners. We have a paper on our technology that we call segment health monitoring.

Beyond just leak detection, one of the things that we’ve noticed our customers getting back to us on are “How do I know my leak detection is working? How do I have assurance that the stuff I built a year ago or six months ago is still catching leaks today?”

We have a bunch of technology to make sure, if your meters have drifted, we can understand how that affects your sensitivity or your accuracy and making sure you’re really making sure your system still works.

Russel: People that understand leak detection know that leak detection is only as good as your instrumentation. One of the things that you guys are going to be talking about in your paper is how do you keep your leak detection good even if you’re having issues with your instrumentation. That’s a huge thing.

These are the reasons you should come to the API Pipeline and Cybernetics Conference, because you get to find out this cool stuff.

Jerad: There’s a ton of stuff that you can learn here. Not just from us, but from all the rest of the presenters. It’s been a really good show.

Russel: Thank you.

Jerad: Thanks.

Russel: I hope you enjoyed this week’s episode of the Pipeliners Podcast and our conversations from the API Pipeline Conference. Just a reminder before you go, you should register to win our customized Pipeliners Podcast YETI tumbler. Just visit PipelinePodcastNetwork.com/Win and enter yourself in the drawing.

Best way to support us is to leave us a review. We would appreciate it if you would. You can do that on Apple Podcast, Google Play, Spotify. You can find instructions at PipelinePodcastNetwork.com.

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.

Transcription by CastingWords