Skip to content
Episode 311: Learning Integrity Management with Christopher De Leon and Rhett Dotson episode artwork

Nov 21, 2023 35 min

Episode 311: Learning Integrity Management with Christopher De Leon and Rhett Dotson

from Pipeliners Podcast Hosted by Russel Treat

In this episode of the Pipeliners Podcast, hosts Christopher De Leon and Rhett Dotson join Russel Treat to discuss learning integrity management. The hosts share insights from their experience in the pipeline industry and the creation of their podcast, "Pipeline Things." They highlight the importance of understanding pipeline failures, the role of regulations, and the challenges of pipeline integrity management. The hosts delve into their series called "The Failure Files," where they explore significant pipeline failures, analyze the lessons learned, and emphasize the importance of continuous improvement in integrity management. The conversation touches on topics such as the maturity of pipeline integrity programs, the balance between compliance and safety, and the need for a proactive approach to risk analysis. Visit PipelinePodcastNetwork.com for a full episode transcript, as well as detailed show notes with relevant links and insider term definitions.

Episode details come from the podcast's RSS feed.

Embed this episode

Ready to play

Episode 311: Learning Integrity Management with Christopher De Leon and Rhett Dotson

0:00 35:32
of matches

Transcript Auto-generated, may contain errors

Welcome to the Pipe Liners Podcast, Episode 311, sponsored by Inter-SYS Corporation, Providers of Poems, the Pipeline Operations Excellence Management System, Compliance and Operations Software for the Pipe Liners Control Center to address control remandagement, SCADA, and audit readiness. Find out more about poems at intersyscorp.com. I have the Integrity Management Junior Gurus, Rhett and Chris. Why don't you do this for me for the Pipe Liner Podcast audience?

Would you give us a quick introduction? Yeah sure, so I'll go far. So Rhett Dodson, Chief Engineer at D2 Integrity, been doing consulting for about 19 years, and over the last decade, has been in the Pipeline Sphere, previous guest on the Pipe Liners Podcast, and really excited to be back again. I'd like to say it was the genesis of our podcast and career.

Oh, it for sure was. So I'll jump in Chris for the Director D2 Integrity, been doing Pipeline Integrity for about 15 years now. And in a former life, with a former employer, we got introduced to the Pipe Liners Podcast, which in one way or another, ended up leading to us also having a podcast. So yeah, totally happy being back here.

Well, and you guys are doing some great work in the Integrity Domain. I say all the time, I'm not an Integrity Management guy, but lack yourselves. When you start getting out there and doing podcast, you start learning about all the other aspects of Pipeline that you didn't know about. So I want to talk to you guys a little bit about what you're doing with Pipeline Things, and how that got started, and how far along.

Because you're getting the point you've got quite a few episodes out there now. Yeah, that's a fun one. So I'll give my brief take and can jump in. So occasionally, I have good ideas, and sometimes, far fewer times, I have really bad ideas.

And so Rhett and I were being explorers about a year and a half ago, two years ago. And we decided to go out and see what we could do on our own. And in some of our downtime, I was like, hey, Rhett, what do you think about us doing a podcast? And Rhett being who Rhett is, he's like, let's do it.

You know, he's like, that's correct. I think my first reaction was your idiot. But I like the historical version of this is great. Yeah.

This is why you guys are such a good team. Yeah. And so, but let's be real. How many times have you said that Rhett?

And how do we turn out? Come on, finish your statement. Go ahead. A lot.

My first reaction was this sounds stupid. Like, I don't know that we can do this. I was definitely not super keen on it initially. Once we talked about it, I was like, okay, you know, let's see what goes, how this works.

Like, will anyone listen to us? How many episodes have you guys done now? I feel like I should know that right off hand. And Christopher, I don't think I actually know that.

Is it more than 20? Yeah, it's more than 20. I want to say we're probably around 30 to 40 episodes now. That's exactly what I was supposed to say.

Yeah. We're 30 to 40 episodes. And we've had north of 10 guests now. Yeah.

So, one of the things that in the research I was doing, it's interesting you talk about the conversation you got. I was having both sides of that conversation in my head when I was thinking about starting the Five-Finers podcast. And I'm like, nobody's doing this. Why am I?

Why should I think that if I do it, it worked? Anybody would care, right? I mean, you know, I was having both sides of that conversation in my own head. So, you know, anyway, I will say, Russell, I thought we had something good.

I still have it because I'll keep it forever. We did an episode and we talked about the beauty of the 80s was the second way. And somebody sent us a 1976 Reader's Digest in the mail anonymously after that episode. And I still don't know to this date who or what fan actually sent the 1976 Reader's Digest.

Oh, yeah, you don't know that. So, and then I was like, maybe we have something here. Maybe this is worth doing. Well, it's a very interesting vehicle, particularly when you're getting started because you're putting content out and you don't initially hear anything, right?

It takes a while. And then you go to a trade show and people are like, Oh, yeah, I know you guys, I saw such and such. And I heard this and that was really helpful. And you know, so you guys are, you know, you're you're you're doing a bit more video.

I don't do video. I focus purely on audio at least at this point. But you're actually creating a lot of very interesting content. And you guys, because of your focus on integrity management, you tend to do deep dives with some really technical leadership.

And really, what I asked you guys on to talk about is what you're doing with your series and how you're focusing on education. So maybe you could tell us a little bit about the series you guys are working on that is focused on learning pipeline integrity. Why is that so important? And tell me a little bit about what you're coming from and putting that together.

Yeah, so I'll take this one, Chris, if you don't mind. So when we started, Chris has always kind of been on the theme of we need to do a series around a set, a set arc and we chose arc because that relates to anime, which is also one of our nerdy passions or a lot of times we'll do comic books or, you know, it's like whenever they were doing the Marvel universe, you had, you know, arc two, arc three. And so we, we like art as a good word to convey that. And we usually choose topics around that theme.

And usually they center around what we get asked about the most. So I mean, it started logically with inline inspection, which has always been very close to Christopher and I. And then we did the PPM series publicly, you know, again, that one focused on eye-light technology providers and kind of which ones are making moves and shifts and bringing about new things in the industry. This latest arc, which kind of spawned, you know, where we're at today, that one began with, I used to do in my previous role, we would do once a year a series with or like, let's call it an in-person training with all of the young engineers that covered previous pipeline failures.

Like, how did we get to the regulatory environment that we're in? And I always entitled it, never forget that was the name of the presentation. And it was really amazing to me how that gravitated towards the younger engineers that we would hire because they were often completely unaware of some of them that occurred before they were even born at the rate that we were hiring them. And I'm also amazed even in my own influence within, I mean, I've been doing this now, I mentioned over a decade, there's still failures that happen that, you know, it happens.

Demps are NTSB, right of report. I'm busy. I don't look at the details and the lessons potentially learned from that bill unnoticed in my own career. So I've had this passion to say, look, let's center around some of these incidents that happened.

What the key takeaways were, with really two goals in mind. One is that never forget, like as pipelineers, we should never forget the events that shaped our industry. And then number two is fully appreciating, you know, what shaped us in terms of our regulatory environment. And let's not forget those lessons as we move forward.

Yeah, I think that's a great take, a great take. Go ahead, Chris. Yeah, one of our things is, I remember when I started my first gig working for Jerry Rau as a pipeline integrity engineer, and there's a certain moments that I feel like kind of defying you. And what we tried to do with this most recent arc, like we called it the failure files in this case was exactly that right is it's we have new regulation and pipeline integrity that's kind of it's kind of overarching, right?

It's like this big sweep of how it's influencing how we're approaching pipeline integrity management. And so in that, you know, I'm talking to Rhett and I was like, I think a lot of people will maybe miss the why. Like, why are we doing this? And what's our intent?

And unfortunately, when regulations pass, there's a lot of dynamics that are happening that most people don't either have exposure to or aren't able to decipher all of the information to figure out what are we trying to accomplish. And so instead of, you know, writing papers about it or articles, we figured, Hey, let's leverage our podcast platform that where we can maybe review what happened, and then maybe that can begin to serve a basis for some of the regulation we have. And so what we did is we started, let's go to the big ones and let's not just start at what we call the new gas rule, but let's go back to see how do we even start with integrity management. And that's where we start with things like Bellingham and et cetera.

So and the focus, I mean, our audience is just like you said earlier, right? It is pipeline integrity management. When I started, I was often the youngest guy in the room and integrity management was starting. Now we have great initiatives in the industry like YPP and stuff like that where people are really breeding, beginning a little bit more attracted to pipeline integrity management and kind of what we're trying to do.

And we just want to use our platform a little bit to make some other information available to them because sometimes it's easier to listen to somebody at 1.5 on a podcast for 30 minutes than, you know, pick up a bunch of articles and read. So that's kind of what our what our intent was with this latest arc. Well, I think that's to be commended and I love the idea of starting with the significant failures and the NTSB reports and kind of breaking that all down. I've actually had this conversation with a number of people on various podcasts about the idea of what does it mean to be a professional pipeline or a pipeline professional, right?

I mean, Larry Shelton, who's the guest on the Bellingham episode and he shares his personal interest, he talks about, you know, what it means to be a pipeline or how that is a term of respect, right? It means something. And I really believe that if you're going to be an engineer in a pipeline business, you should have a working knowledge of the key failures. Bellingham, San Bruno, Marshall, there's probably some others, you know, Pecus Texas, some others that you can throw in there and you need to know the entirety of the story that led to the failure.

Because without that, we are as an industry subject to have it happen again. It's really, you know, there's a lot we can do in terms of systems and processes and all that to head these things off. But if we don't have that shared experience, then we are at risk of having things regard. And that's the balance that Rhett and I often try to find in our episodes when we're going through these.

And it's, you know, we find ourselves in the US with regulation that is too often we feel as consultants, what we see is too often leading to compliance activities, right? And we feel often that by reviewing these failures and making a little bit more personable about the consequences, a lot of the people that we are listening to our podcast, we know our decision makers, right? Whether it's what tool do I run, do I dig this anomaly or not? What information do I integrate?

And so we're trying to reach out to those individuals and say, if we can make them aware of what actually happened in the failure, maybe that can help them better. Man is integrity of their line. Yeah, I think it's a great point. When you think about what is the difference between a competent engineer, a good engineer and a great engineer, right?

And what is the difference? A competent engineer knows how to do the job, knows how to run the math, knows how to work the process. A good engineer knows all that and knows where the process comes from. And a great engineer knows everything that can go wrong, right?

And, you know, it's that knowledge of what can go wrong that is really the difference maker, right? And generally that comes from engineers with experience and oftentimes that experiences, you know, all the things that went wrong for you as you worked your career, right? We learn a lot more from the things that didn't go as planned. It's just the nature of human beings and how we learn.

So what are some of the things you're focusing on specifically as you're trying to put together material that has training content, training value for engineers? Yes, I think for Christopher and I, we always try and stay close to usually close to I.L.I. and usually close to integrity. So when we did this series, I'm sure a lot of people could say, Hey, you know, you didn't focus on this or you didn't focus on that.

It's like Bellingham, you know, there were all sorts of things that went into a huge discussion about the valve, for instance, and the set point on the valve. We completely skipped over that altogether because most of when we talk about inline inspection, we don't get into valves and set points and things like that inside of the fences. Although it was very central to a lot of the consequences that happened. We touch a little bit on the control room, but only because the control room I could relate when you talk about bias, system bias.

So when you talk about deferring to one person as an SME who's the loudest voice in the room, those are conversations that I feel happen on the integrity side in an almost identical manner where when you're looking at, Hey, do we want to do we want to tackle this feature, for instance, or do we recommend digging this feature? If you have one person steps up in the room and presents themselves as an expert, a lot of times people will coalesce behind that person and there may not be enough dissenting opinion expressed. I feel like a lot of times where we're faced with just like in say, you know, Marshall, where they were trying to decide is this column separation or is this something else? We're faced with similar information.

We related it to kind of like poker where you only know the cards in front of you and there's unknown cards that are down on the table and you're always trying to figure out what the other person has and what's down on the table and you're dealing with limited information. So we really try and relate it to the integrity engineers, to people who are managing pipeline integrity and closely associated with the highlight. I'd say that's our heartbeat and then everything kind of centers around that heartbeat. It's interesting that you make that point because I agree with you that the team dynamics around these complex engineering decisions, particularly when you have a senior engineer and other more junior engineers, that team dynamic can skew the decision making.

Often times not necessarily in the best way, right? Absolutely. We saw that, you know, like in another failure. I worked offshore in the beginning part of my career and was around when Deepwater Horizon happened and anybody ever reads the reports around that, talked a lot about confirmation bias and how a group of people got together and just kind of groupthink led them to believe that there weren't issues with the casing that ultimately led to the Horizon incident and the deaths that followed there.

It's so important in our industry and when I work with younger engineers, I made it a point to tell them, look, I might not have more experience than you, but it doesn't mean I'm always more right than you. And everybody in this room needs to feel like you have an engineering degree, you have the right to speak up. And if you think something was done wrong or you think something is wrong, you need to speak up. And I think the best integrity programs have got to focus on creating a culture like that, Russell.

Anybody in the room can say, do we sure? Does that make sense? Because I got to be honest, that sounds crazy. Well, it's the subtleties right there to the problem.

It's not the things that are clear cut, it's the subtleties. And the confirmation bias, that was a big thing in Marshall. The operator there had a history of leak alarms that root cause was column separation. And they had that history on that line.

And consequently, they were not able to see past the common occurrence through to the uncommon occurrence. And that's a challenge, man. That's a challenge in our business because these failures are rare. Which makes them hard to identify.

And we often highlight that in the various discussions that we have. Because there's so many elements of the decision-making process, specifically when it relates to pipeline integrity, where you have this bias, right? And we've talked about whether it's personal bias or institutional bias or industry bias. And so, again, we think that fortunately through this platform of podcasts and guests, it's kind of like what we're doing now, by creating just these exposures of lessons learned, we hope that, and I'm going to make a reference here, they kind of serve as AGMs, right?

So we use these above-ground markers to serve as a benchmark for ILI tools to know where they're at, you know, are they drifting, how much is left, how fast is it going, right? So we hope that our podcast and the various topics and the different guests that we bring on kind of serve as personal AGMs, right? To keep us a little bit grounded in saying, hey, you know, we traditionally use this vendor or this process because that's how we've done it. And there is merit in that, right?

When you have a process and system keeping that going. But there's also these elements and integrity management of continuous improvement, right? Data integration. Yeah, this is actually a really important conversation.

I have a premise, okay? And I'd like to hear your thoughts on this. I believe that we're coming out of a long period in the pipeline world where we have been focusing on tools and techniques for evaluating the level and that we have, we've gotten step changes and safety performance improvement because of that. However, I think we're lagging behind because we've not at the same time had management systems applied the same way, and that we need to really begin to focus on the management systems for doing the work.

So there's two parts to that. One is you've got to start looking at the work as a process. And then you've got to understand what are the nodes in the process and how they're going to relate. And then somebody needs to be looking at the process and asking the question, is this process continuing to get us the result we're looking for?

So you actually need people who are standing outside the process looking at it and others who are inside the process working it. Yeah. And that we haven't had in our business, a lot of people standing outside the process evaluate. I would say, Russell, you're touching on a topic that I would maybe relate to program maturity, right?

You're speaking from experience, right? And having seen mature programs and mature systems, what we have found is a lot of times operators are at different stages of maturity in their integrity management plan, right? Or their integrity management program. So you'll have an operator who unfortunately through fire, learning by fire, has had incidents and they've had to grow their teams and through lessons learned, put people who are focusing on the pipeline and then focusing on the program and finding program improvements.

But you have other operators in some cases where they're now only being brought into integrity management because of their asset type and the expansion of regulations. And so those operators unfortunately aren't going to be able to have the resources in place or the institutional knowledge to understand what you just said, right? Is it's, hey, there's the safety performance and then there's a component of what is our management system's performance. And so it's difficult.

It's something that Rhett and I want benefit from, but also as an industry we get hurt from, right? I say benefit from it because we're consultants, right? And I often say your consultants are only as good as their network and their experience. But on the flip side, it's like, you know, often we're solving the same problem over and over and over, right?

Because as an industry, you know, different operators are at different maturity levels in their integrity management programs. Can we look more at them as a system? When you asked that question, Russell, what really resonated with me is before we started the series on the failure files, I've not been a big fan of prescriptive regulations. After going through the failure files, I'm like, oh man, it's hard to argue that we don't need them.

It's very difficult to argue that pipeline integrity would be better without it. I don't even know that I can make that argument. And I've tended to fall more and more in line with, yeah, I believe we need more prescriptive regulatory management. The challenge is you said that you need somebody in the process asking, is that identifying what we want?

When you have a prescriptive regulatory environment, I feel like too often that question becomes, is this meeting regulatory requirements rather than is this identifying what we want? Exactly. And that's the tension I've caught in because I want that prescriptive regulatory because I feel like when you look at these failures, we need it. But then when that becomes the focus, again, it goes to the point that Chris was making, there's a distinction between operator maturity and industry maturity.

You know, there's a lot of conversation going on at PHMSA about moving to predictive risk analysis, the probabilistic risk risk, man, I can't speak today, probabilistic risk analysis, right? And that is kind of moving in that way. And when I talk about this, I'm thinking about dimming and total quality management, six-sigma, and all those kinds of things, where they're constantly looking at the process and is giving us the result we need in the most optimal way, right? And to your point, what tends to happen is we apply those kinds of sciences, but the result we're looking for is are we compliant versus are we as safe as we can be?

And that is a difficult distinction, and it's difficult for any operator to get there because it's a both-and, it's not an either-or, I got to be both compliant and doing what's best for safety. And I'll tell that a little bit, right? So we saw the white paper that was issued a couple of years ago related to different risk models for pipeline integrity management, right? And they had a table in there where it's like, they say probabilistic is best practice.

And it just kind of goes back to institutional, but also in this case, industrial maturity, right? So we appreciate that there was a worker get put in place, but some operators, just there are pipelines and assets where it doesn't make sense to do probabilistic because probabilistic is only as good as the volume and quality of data you have, right? And so if you're having to issue this programmatic approach or system-wide approach, that may not be the best option. It may not be the best allocation of resources, right?

And so part of that as I get to operator maturity is it's in time that's back to this podcast. I think that's why this platform that you offer Russell and what we try to do is it's resurface these with guests. If I'm not mistaken, I think we've had about 14 guests on our podcast. I know you have many, many, many more than that, but I think what we're trying to share is it's, hey guys, as your organization is maturing, reach out to the network, be abreast of what's going on so that you can learn from everybody else.

And you'll learn how to interpret things that either industry or regulation or maybe Congress is trying to push out. And then you can bring that in and turn that into something meaningful for your organization so you can apply your resource where they matter the most, right? Because we don't think it makes sense to put all this money into data gathering and put it into a system if it's not helping you solve the problem, which is reducing leaks and reducing failures. Exactly.

Exactly. I mean, you're exactly right. And the reality is all operators have a limited budget and they have limited resources and they're trying to apply those in the best way they can. And all these things we're talking about are tools for doing that.

I want to kind of shift a little bit. I have an idea that I think you guys could execute in your podcast. And I'm very serious about this. I think we're doing a podcast about ideas for our podcast.

I think Russell, this isn't last of the hostile takeover last time, whenever he just jumped on and grabbed the microphone on PPI. I feel like this is a subtle, subtle takeover. No, it's not a takeover. I'm actually trying to collaborate with you guys and do something via value for the industry.

And for those of you that want to find the hostile takeover attempt, you can search YouTube and there it's available out there. Anyway, here's what I'm driving that guys. I think one of the things you guys would be uniquely qualified to do is to find the actual ILI records related to some of these failures and combine it with ILI records that are normal records for features that are discovered that need to be evaluated, but did not result in a failure and like kind of create a game, do you dig? Right?

Oh, man. You just want like we could do a LinkedIn post once a week with would you dig this feature and then reveal where it is and the hard part of getting that data. The idea is great. Yeah, I know the hard part of the beginning.

Well, if you, if you, yeah, yeah, you, maybe, I mean, you know, depends on if you, when you look at stuff that's old, then maybe it's not as big a deal. I don't know. It's a really interesting question, right? Because I think what you would find is some of the features that resulted in failures people would choose not to dig.

Yeah, I wonder why is making me question why in the NTSB in the FIMSA reports, we don't include images of the ILI signals. I'm trying to think if I have ever seen an NTSB report that included an image of the ILI signal. Yeah, we talk them out a lot, but often often often, often, well, you get photographs of the defect when they dig it up and look at it. But yeah, actually that is, I think you should send a correspondence to the LEAP pipeline investigator and NTSB and ask that question.

That gets really interesting. So I'm trying to gather, I'm trying to calibrate my thoughts there. We're probably making somebody nervous having this conversation. Yeah.

So I maybe I worked at an inspection company for a long time and a lot of things go through your mind, right? And so one of the things I would say is that some different technologies respond differently to material and to feature types. And I think something that we need to be real careful with and this is not a caveat or get out a jail free card for I like technologies, but rather, you know, the pipe and the feature, I.e. the flaw, the imperfection or the defect, may have a different response in each ILI system.

And so if we were to do something like that, I think what would be important is it's sometimes those images wouldn't be as objective or as plain, as straightforward as when you look at like a crater or a leak or a pipe that has. I think the value in doing something like that is you get to kind of look at the you get to look at the salty, so you get to look at the differences and it provides a way for people to develop experience that they wouldn't otherwise develop. I mean, that would be the benefit of doing it, right? And that is true, right?

So I mean, one of the ones that comes to mind is the hard spot failure. We have a podcast on that as well if you guys want to go listen to it. And I mean, that was the case, right? So ILI had been run as a baseline.

They were deemed to be non issue. An incident happens, they go back and look at old data under new experience, new competence, new algorithm, and all of a sudden more features are revealed, right? And that's just something you're always going to be susceptible when it comes to mind. That's a whole that's a whole other conversation because the quality of the tools is improving.

The data quantity they can gather is improving. So what's happening is we're exposing a whole lot more features and it's having a huge impact on workload, right? So there's challenges with all this. But anyways, I would love to see you guys do a weekly link then drop on do you dick?

That would be cool if you could figure out how to pull that off. Might not be doable, but I think it's an iffy idea. We will take it into account. If we do happen to get sued as a result of that idea, do you offer legal service for two?

I can refer you to some good attorneys. It would be the equivalent thing, my domain would be you continued operate. And we run that in some of our training, we run that as an exercise. It was a whole exercise and you build a scenario up and you keep walking through the scenario and you can continue to ask you continue to operate, you continue to operate.

It's really interesting what comes up when you do that. And it's very helpful for training. So anyways, hey guys, look, I'm kind of coming to end of time here. Always a pleasure to have you guys on board.

I will tell the listeners that I am soon going to be a guest on the pipeline things podcast. They're going to quiz me about the control room side of some of the failures they've been talking about. And hopefully I'll be well equipped to answer whatever questions may come out. So be looking for that on the pipeline things podcast.

We'll probably rewrite it here. Audio only. I have been told I have a face for the audio form of podcasting. You know, that brings up a whole question about different generations.

And some people actually really like the YouTube version. It's interesting. I don't know why. Well, I mean, I think when you when you have audio and you have more of a TV experience, you get more of the communication that's going on than just the audio.

The flip side of that is however that if I'm driving, if I'm cooking a meal, if I'm working out, I can't watch a video generally. You know, I can listen to audio. So, you know, I'm actually starting to look at what would it take for us to do some audio stuff. I want to try and do a bit more of it.

I've done a little of that is some trade shows and stuff. Short format, you know, a few minutes, but we're looking at doing doing more of that. So we might go to school on you guys a little bit here when we see what all you're doing. Well, we do appreciate you everything you've done to create an environment where this is attractive and just the following that you have.

We're really impressed and we appreciate every opportunity to work with you Russell. Well, thanks guys. And I really appreciate you acknowledging that. And I think what y'all are doing is great.

And to others that have other ideas about podcasts and our domain, I'd say, come on in the water's fine. Absolutely. Thanks again. We do appreciate it.

Russell. All right. Take care guys. Cheers.

I hope you enjoyed this week's episode of the Pipeliners Podcast and our conversation with Chris and Red. Just a reminder before you go, you should register to win our Customize Pipeliners Podcast Yeti Tumbler. Simply visit pipelinepodcastnetwork.com slash win and yourself in the drawing. If you would like to support this podcast, please leave us a review on Apple Podcasts.

We will play Spotify, wherever you happen to listen. You can find instructions at pipelinepodcastnetwork.com. If you have ideas, questions or topics you'd be interested in hearing about, please let me know either on the contact us at age at pipelinepodcastnetwork.com or reach out to me on LinkedIn. Thanks for listening.

I'll talk to you next week.

Frequently asked questions

How long is this episode of Pipeliners Podcast?

This episode is 35 minutes long.

When was this Pipeliners Podcast episode published?

This episode was published on November 21, 2023.

Is there a transcript available for this episode?

Yes, a full transcript is available for this episode. You can read the complete transcript on the episode page.

Can I download this Pipeliners Podcast episode?

Yes. Use the download control on the episode player to save the publisher-provided media file.