Welcome to the Pike Liners Podcast, episode 199, sponsored by Rosen, the global leader in cutting-edge solutions across all areas of the integrity process change, providing operators the data they need to make the best integrity management decisions. To find out more about Rosen, go to rosen-group.com. Thank you, sir. Well, it's good to have you back.
You were recently on the podcast. We've been back on episode 124 and we talked a lot about API 1176 and crack management and all of that. Maybe a good place to start is just tell us what's been going on since the last time we talked with 1176. Yeah, that's a good place to start.
The API team who put together and spearheaded the creation of 1176 is currently going through a revision. So periodically we open up the recommended practices and standards and make sure that they're relevant and keep them relevant through revisions as they come up periodically throughout the years. So right now, 1176 is currently going through a revision. There's a large API team with a number of operators who are going to take a look at that document and keep it current.
So when do you think the thing will start coming out for ballot review? How far away is that? It probably is six months to a year to be ballad. So it takes some time to go through about 176 pages of a document.
I participate on some of the API committees in other domains and it always takes way longer than what you think it's going to take as part of it. It sure is. So I know that there's been a fair amount of industry collaboration going on around just integrity management in general and with some specific interest around crack and crack tools. So maybe you could tell us a little bit about what you've been participating with and related to operator meetings with the crack tool guys.
Yeah, so a couple of years ago, the API group, it's the R&D work group got together and decided to meet with the ally vendors and ask them how do we help the vendors get in front of the technology and have the operators help the vendors get the technology as best we can. And one of the things we heard loud and clear was we need real world samples and we're there from each one of the I live vendors as it pertains to cracks in particular. So we got back to our offices and we talked it through and we said, okay, let's make a real effort here to get real world crack samples and send them to the PRCITDC so we can set up a test loop. And it took us a little bit, but the operators came through.
We have an 800 foot test loop that is currently at the TDC and it can run in a liquid service, we put water in it, because ultrasonic tools are the best tools to find cracks. And with ultrasonic, you need a liquid coupling. So we built an 800 foot test loop with real world crack samples in particular hook cracks in the seams in order to test ILI tools and help them get better. Well, I've been out for the TDC and I've seen the facilities they've had out there and it's really quite fascinating what they do and how they've got that loop set up and how they know with the pipe, you know, here are the faults we're looking for.
And I've got that data for that pipe from a lot of different tools, including handheld stuff. It's really fascinating what they can do in terms of building a data set for test purposes. Yeah, that's for sure. So we have eight acres out there and a large portion of it set up for pull testing, but another section of it is set up for these test loops.
And the operators donated pipe with cracks in it. And then we scrub those pipes with NDE out in the warehouse, we put them up on pipe stands, and it was a near laboratory setting, where you could spend hours upon hours testing this pipe and making sure we have the best available information from an industry perspective on what's in the pipe. Yeah, so how many vendors have run their tools through this test loop so far? What's been the challenges with getting the vendors to run and look at the vendor data and all that?
Truthfully, the biggest challenge has been COVID. A couple of our vendors are not in Houston, but the PRCI-CDC is here in Houston. So to get the tools and the technicians, like from Canada to Houston, has actually been a bit of a challenge, especially with quarantine rules and things like that. But we have one vendor that's been through the test loop.
And what's real interesting is that test loop is designed to run it several times around the loop, several different speeds, and then we can take it out, turn it around and go the opposite direction. So the vendors can get multiple looks at the cracks in two different directions. Well, that's fascinating. I'm wondering what you find when you do that.
I mean, how different does the crack look when you're running different speed in a different direction? Well, we want to give them as many chances to be successful as they can. And we want to be able to learn as much as we can by these test loops. We have not gotten any results from that first vendor yet.
Our second vendor is set up for September. So we're excited about that. And we have two other vendors behind them already scheduled. So Mike, I'm not an ILI guy by a long stretch.
I can kind of spell out ILI. It's about what I know about ILI. But I do know a fair amount of doing research projects and what's required to get something through its basis and out to market. And I would think as a vendor that I'd want to run, I'd want to grab that data, and then I'd want to do a bunch of back office analysis and evaluation of what I found.
That's probably going to drive me to make some changes in my tool. And then I probably want to run it again. No, you bring up a great point. We've always set this up as a minimum of two phases.
One was to get a baseline. And then hopefully in 2022, they are ready to make those adjustments to either their tool or their processes, programs or algorithms, and then come back out in 2022 and rerun it again. No, you bring up a great point. Yeah, well, I mean, that's the nature of how you get something really tuned up and ready to go at value in the marketplace.
You've got this iterative process of, okay, I know what I'm looking for. I'm sure they saw the cracks, but like really seeing exactly what they need to see and knowing what they're seeing, that's the tricky bit. No, you're exactly right. It's not just detection.
It's identification and characterization. So we have to be able to see the crack. We have to be able to identify it as a crack. We have to be able to identify it as a hook crack and not a lack of fusion.
We have to be able to size it, length, depth and width. So it's multiple faceted. So I'm hoping they got plenty of looks at these cracks and they can tell us what the optimum speeds they need to run at and directions they need to run at. And hopefully it'll get a lot of really good information.
We have a gold mine of samples. When we were testing the samples out at the TDC with the third party NDE, non-destructive testing, the technicians giggled when they went past some of the defects because there are plenty of defects. And I asked them, why are you giggling? He said, this is a treasure trove of defects.
You guys have found the best samples that we've ever seen. Well, yeah, it's, you know, I'm not a night like I, but I am that kind of geek. I would be the same way. They're like, look at all the things we can see because you never, you know, I think one of the things that you guys have done with this collaborative effort here is you've got, you've created a situation where both the operators and the tool vendors can look at a very wide variety of defects in very short order.
And you just don't get that opportunity in the field. No, and I don't think this has ever really existed in this manner with the operators and the vendors working together. They asked us for samples, real world crack samples, and the operators came through. Yeah, well, that's, that's awesome.
That's awesome. And I, you know, that's, that is, it's interesting too, because one of the things we're really challenging with in the, in the business in our industry is how do we do a better job of sharing information? And there's a lot of concern when you start sharing information that might be, you know, punitive or litigious or something like that might have a risk with it. But what you guys have done you're pulling samples out of pipe that you found in your programs that you decided to pull and then saying, okay, let's put this in a run and let people look at it.
I think it's awesome. It's awesome. Yeah, it has been a really good project so far. And I'm really glad to be part of it.
Yeah, I bet it's a lot of fun. So talking about sharing, what is the industry doing to get better about sharing beyond just, you know, getting some segments of pipe? Are there other things that are going on from an industry collaboration standpoint that people ought to know about or might want to participate in? Yeah, I think as a whole, we've all looked at the elephant in the room on data.
And we've, we all have a ton of data. And what the struggle is, is how do we share my data with you and your data with me being such a huge data set? So I've worked on this problem a little bit with PRCI. And I think if you eat the elephant all at once, it's very daunting.
So how do we break up the data in different segments? Give an example. I was looking at our river crossing risk data and looking at it from a stance, well, if I was to share this information, what would it look like and what could I share? And what I found was there's data within our data that is incredibly shareable, like the characteristics of the river.
That's not anything that I couldn't share or shouldn't be able to share. There's also in some ways that's public domain, right? It is, but we each one of us do our own data evaluation boots on the ground at the river. So there's four variables that we look at.
We look at the ability for the river to change, of course, right? Because we know it's going to change. It is slow change in most cases. But we know that the channel, the river channel with different flood events can get deeper.
So that's one variable. How deep can a river get under certain flood events? Then we also know that the banks can change the sides of the rivers. So how, what is the potential for the bank to erode under flood events?
What's the potential for the bank to fail on flood events? And then the last one is how much migration you're going to get from the river? How much is the river going to change directions? And you got to remember we built these pipelines, 50, 60 years ago, in some cases, when the river may have been smaller or shallower.
Or in a completely different place. Exactly. So we have to do is monitor the characteristics and the river's behavior. So we've all put together risk metrics, similar to what I've spelled out.
And there's four variables that I think we could share as an industry. And I think we could all learn from it. And it's independent of my pipeline. I didn't tell you how deep my pipeline is.
I didn't tell you where my pipeline was. All we've done is talk about rivers. So why wouldn't we be able to share that? So we currently have a pilot program within PRCI.
We've been working with a river expert. His name is Dr. Jeff Berry. He's with Geomorphic Solutions.
And he basically is kind of the leading industry expert on river risk characteristics. Interesting. So this might be a little bit out from the weeds. But recently I was, as I do sometimes in the evening at the end of the day, I get on YouTube and I just look for videos I find interesting.
And I saw a video that was a hydrology lab at a university. And they were running experiments about how a river shape changes by varying the speed of the current and the direction of the river and what you put in the river and how that changes the banks and all that kind of stuff. I'm wondering if you've ever looked at capstone projects around this kind of stuff. Are you familiar with capstone projects?
A little bit. We do some of those here at Phillips as well. But I don't think we've looked at it from that standpoint. I think that's a great idea.
I know that Dr. Jeff Berry has actually done some testing at a university as well, where he was using acoustics to hear the movement of the rivers, which was kind of interesting. Oh, wow. Which are right.
The differences between sedimentary deposition and the characteristics of it moving is exactly what we're looking for. So yeah, I think working with universities or other experts like that is a really good idea. I'm sure there's some PhD engineer in the civil engineering department at A&M that would love the opportunity to do that kind of project. And I'm sure there's some engineers that need capstone projects to get their diploma stamped and get out and make the living.
Right? So yeah, this would be a good one. The interesting look at that. Definitely.
Okay. So let's I want to segue a little bit, talk a little bit about in the ditch in the E. So it seems to me that there's a lot of opportunity for improvement in that domain. And that's a little different than running the I.L.I.
tools. I mean, you've got technicians that are actually in the ditch with tools, collecting data and all of that. And again, it's not something I don't know a lot about. But what is the industry doing in that domain from a collaboration standpoint?
No, that's another good question. I think the last time we talked, we were talking about inline inspection and cracks. And we mentioned NDE in the last episode. We basically took it as an industry in two phases.
One, improve I.L.I. but two, improve NDE. And as we have dove into the NDE process and industry, we've learned quite a few things. Again, the key is samples.
We need good real world samples from a midstream perspective in order for NDE technicians to test and qualify. The NDE companies themselves typically deal with thick, flat plates. Well, on the pipeline side, we deal with thin, curved pipe. So it's typically not as thick as the plates.
It's a lot thinner. And ultrasonic, the ultrasonic technique reacts differently to different defects in that curved thin setting. When you have a thick plate, it can be easy to find a defect when you have curved pipe. It's actually somewhat challenging.
So what we decided to do was put together a qualification validation, use an API. They currently have a program for the refining industry. So what we did was create one for the midstream industry. And we got samples to test NDE companies to have them come out here and validate their qualification on midstream pipe.
The first thing we did was test wall thickness. So we've got that out there. And then the second one was long-seam defects. It's still pretty new.
But what we need is we need more samples as an industry and we need to be putting more technicians through this NDE qualification process. Again, back to the samples. It really takes samples to get that done. And it takes us operators.
The operators have to get those samples. Yeah, that's right. Because they're the ones that have them. One of the things that comes up for me is I think about what you're talking about.
NDE is typically done in a ditch. I do a dig, I expose a joint pipe, and then I get to set the technicians' loops and they go about gathering their data on the pipe. I would think that you'd almost need to, if you know, once you get the samples kind of like with the test loop, how valuable is it to have those samples in a ditch and see how you get the data in the ditch versus having it sitting in a rack and see how you get the data? How big a deal is that really?
That might be a challenge. But I like the way you think, you know, we need to be in the mud laying down ants falling on you. I don't know if you need to have drop ants on people. But I mean, there is an aspect of doing this in a confined space and doing it looking up, you know, on the bottom of a pipe versus, you know, doing it looking down on a flat plate.
No, you're exactly right. And so what we're trying to do is we're trying to get those samples, get them, get them, get their training up to speed from their company's perspective and then have something available to them so they can actually validate that qualification. You're 100% right. The human factors piece of this is huge.
I think we're taking in phases. I like your suggestion, but I think what we're going to do is try to create the samples first, get them tested on it, see how many we can get validated, and then maybe utilize that TDC to create maybe a bellhole or to and see if they can't crawl down in it. Yeah, I like to think, you know, I think there'd be some real value to that. Now you could do it in a way that was more laboratory than pure field, right?
Yeah. So that, you know, to keep it out of the weather and that kind of stuff. But even so, just, you know, being in a confined space and having to get around a 360 degree pipe, that's different than that piece of pipe sitting on a rack and I'm, you know, walking beside the pipe, it just is. Oh, it's totally is it.
The human factors piece is going to be a challenge from a testing perspective. The other thing that we did that was interesting too is, you know, typically operators only deal with the middleman from the MD perspective. And let me give you an example. So if I have a pipe and a dig and I need it to be tested, I call the service provider that has the equipment and the technicians to give me the information.
What we decided to do is go to the manufacturers. So we recently met with the manufacturers of the equipment that our third party and the company's use. And we've actually learned a lot from that as well. The equipment that is available, the techniques that are available, the programs that are available.
And the other thing we learned is the manufacturers want samples too. So two weeks ago, we invited Olympus out to the TDC to test their equipment on some of the pipe as well. And they spent the entire day out there. We scanned the seams both directions using multiple techniques.
One side of the equipment was using a flat wedge. The other side was using a curved wedge. So we could see if the wedges make a difference in picking up the seam cracks. They recently a week ago went back out there on Thursday and spent the entire day out there again.
And what we're trying to do is try to figure out with the equipment we have what are the best techniques and what techniques don't work. And that way we can get smarter as an industry. And then we can be sharing that with our third party service providers in order to get the best data we can from the ditch. Yeah, that actually that's a great segue because it brings up the next question that's in my mind is, what degree are their good standardized industry practice for doing this kind of work versus it's up to the service provider to have their practice?
I think there's lots of standards out there. Again, the ASNT, TC1A process is sound. But I think the if you get into the minutiae, it's all around what are you testing? It gets back to the midstream component.
I think we just have to expand on the midstream component of indie testing and qualification. Again, it's curved samples and thinner samples. And we need to be getting the indie providers training and certification up and running around that. Well, that makes sense.
And then the follow up question is, do they need to select their technique and equipment based on the threat they're looking for? Right point. Yes, indeed. If they're looking for a crack in the pipe body, it's different techniques and different equipment than you would if you're looking for cracks in the seam.
So good question. So again, we need samples. Yeah. And so that just opens up a whole Pandora's box for me.
And I need to build this a little bit so you kind of understand where I'm coming from. Again, I'm kind of an novice in this domain, but I do kind of understand some of the larger operators and what their dig practice is. And I know that it's somewhat common that if I'm going to do a dig to investigate a specific threat, that generally what I'll do is I'll open a ditch up and I'll get probably that segment and the girth whales on either end of that segment. And then when I go and I do the indie gathering, I'll gather in the on the entirety of that segment.
And then that goes into my database to help with other analysis and assessment. So that's kind of the T up the question would be, well, if I've got to use different kinds of equipment and different kinds of techniques to look for different kinds of threats, when I have an open ditch, how much gathering's enough? Yeah, that's a great point. Typically, though, we know where the targeted defects are going to be based on the inline inspection.
So you may evaluate the entire joint visually, but then use your techniques on the targeted defects. And hopefully you know what those targeted defects are based on the eye line results. Yeah, that makes perfect sense. That makes perfect sense, Michael.
But the flip side of that is I'm an engineer and we never get enough data, right? So I want every technique and every machine you don't want to run at all. You know, it's I know that's not realistic, but there is a little bit of that in this conversation, right? Because there is the cost is in opening up the ditch.
The cost is not in gathering the data once I have the ditch open. Really? Yep, good point. So anyway, since that's the whole how much data is enough question and that question is unanswerable.
It is and we get that question a lot in the integrity field. Oh, it's not just integrity. But yes, I'm with you. I think the way to kind of wrap this up, and this is, you know, I know there's a lot of people that listen to this podcast and they'll listen to something that's kind of very specific and technical like what we're talking about here.
And this isn't really the domain they operate in, but they want to know about it. What would you have to say around coding age of pipe as it relates to just the industry and how we're collaborating around that? Yeah, that's a good question. It's yum.
I've been in the industry a while and the more I look at some of the older coatings, the more I wish we had those older coatings back, hand applied coal tar. That's probably, that's probably like a really controversial opinion, right? I don't know enough about this face to know what I'm going to make that as a guess. Yeah, you're probably right.
But some of that old hand applied coal tar is still intact. It's still perfect. Even if it was built in the 50s. So it's really not about the age of the pipe or the coating itself.
It's about the environment around it and the changes that have happened around it that are affecting the coatings. But some of the older coatings are fabulous. They put it on thick, it structurally sound, and it's still intact with the pipe. It makes you wonder why we don't still do that.
I've wondered that myself. But the decades we've gotten different coatings and different ways to apply it. And all that's done is change the way we have to look for the changes in the coating and the change in the environment and how it affects those different coatings. But you gotta remember, coating is the number one tool to stop corrosion.
If you don't have the environment touching your pipe, you're probably not going to have corrosion. Right. That's right. That's right.
So keep it going on that. You can stay it fast. That's right. But there's so many changes around the pipe that happen that you have to monitor.
Right. Yeah. And you know what it's interesting too, you know, it's sometimes, I think one of the challenges in our business is that we have so many of these really vertical technical domains that we have to have a lot of competency and capability. Then when we start talking about cross-technical domains like cathodic protection versus coating versus ILI versus pressure cycling.
And you those conversations I think get really interesting sometimes because what helps me in one area hurts me any other often. Right. Yeah. Yep.
You're right. So listen, this has been great. You got anything you want to kind of talk about that we haven't already covered? Well, I guess I feel like I didn't finish much on the data sharing.
We do currently have a project with several operators working to share river crossing characteristics. We are working with PRCI. We're working with GM Morphic Solutions to try to come up with a way to put together a data set that is shareable. We've got several operators agreeing to pilot a project right now.
And we're kind of in the middle of that project as we speak. But hopefully what will happen is we'll be able to share a map or a database with those four different characteristics of rivers. And that way operators can take a look at their pipeline and their assets and see if their assets are going to be affected by the different characteristics. The other thing that and really how it came up was if I'm evaluating boots on the ground, information and measuring river characteristics on my pipeline right away, but then right next to me is another operator, we ought to be sharing that information.
So the other piece of that share is should we be sharing our schedules? So should I talk to operator B and let them know that I'm going to be out on a river evaluating river, I have an expert on that river with side zone, our capabilities and vegetation density, measurement techniques right next to their pipeline and would they want to be a part of that? So how do we share the schedules? How do we share the expertise?
And then how do we share the data further? So we're right in the middle of that. But again, it's breaking up the data, not not sharing everything all at once because it seems pretty daunting. But how can we share bits and pieces of it?
And I think we can do that by breaking these different data sets up. Let's take a look at not the data, but the learnings from the data. And that's the river. The information, the process data.
And there's a lot, I think there's a lot of value and a lot of opportunity. And water crossing information is certainly one area. But I think there's others as well. When you start looking at things like potential landslides or other kinds of things where multiple operators would all benefit from the same data.
No, you're exactly right. And where we can get better data for everybody if we collaborate about how we get that data. Yeah, and I'm hoping this project is just the stepping stone for the others. Right.
And again, I think we've been looking at it wrong. We've been saying it's data, but it's really not. It's what you've learned from your data is so much more valuable. Me staring at your data may not come to the same conclusion.
But if you share the information that you obtained from your data, I think that's valuable. Well, I absolutely agree with that. And I can't tell you how many conversations I've been in where we all agree on some general assessment of the raw data. And the real value is in the conversation about the details that we disagree on.
Because we all end up learning something in the midst of that disagreement. Right. Point. Yeah.
And actually, I think that's one of the things our industry does really well. We can get to agreement at one level and discussion at another and have that actually improve the overall understanding and outcome. Yes, sir, definitely. Well, listen, it's so grateful if you're coming back on the podcast, always good to have you.
I always feel like I'm on a very steep learning curve when I've got you here talking. I appreciate it so much. Thank you. I hope you enjoyed this week's episode of the Pipe Liners Podcast, our conversation with Stack.
Just a reminder, before you go, you should register to win our customized Pipe Liners Podcast Yeti Tumblr. Simply visit pipeminerspodcast.com slash win and enter yourself in the drawing. If you would like to support the podcast, please leave us a review on Apple Podcast, Google Play, or whatever smart device you happen to use to listen. You can find instructions at pipelinerspodcast.com.
If you have ideas, questions, or topics you'd be interested in, please let me know either by filling out the contact us page at pipelinerspodcast.com or reach out to me on LinkedIn. Thanks for listening. I'll talk to you next week.