Welcome to the Pipelineers Podcast, Episode 409, sponsored by Inter-SYS Corporation, providers of POIMS, the Pipeline Operations Excellence Management System, operations and compliance software for the Pipeline Operator to address safety program management, control remandagement, and field operations. Find out more about POIMS at intersyscorp.com. The Pipelineers Podcast, where professionals, public eks, and industry insiders share their knowledge and experience about technology, projects, and pipeline operations. And now your host, Russell Treet.
Thanks for listening to the Pipelineers Podcast. I appreciate you taking the time and to show that appreciation. We give away a customized Yeti Tumblr to one listener every episode. This week, our winner is Jeremiah Todd with Calseca.
To learn how you can win this prize, stick around to the end of the episode. This week, we talk with Jim Curry of Vaps Callons and get an update on PHMSA rule-making and the outlook for the next couple of years. Jim, welcome to the Pipelineers Podcast. Russell, it's good to be with you again.
Thanks for having me back on. I guess I didn't screw up too bad last time. That's about enough to free to keep me off. Well, actually, you know, what I should say is that with your predecessor there at Vaps, moving on to become the Chief Counsel at PHMSA, our buddy, Keith Coyle, you're now the new guy at Vaps.
And I want to just say thank you very much for a great to participate again. And thank you very much to Vaps Callon for being a long-term sponsoring podcast. Hey, we appreciate the opportunity, Russell. I'm happy to kind of continue with the relationship here.
Well, great. Well, let's start here like I like to. If you would, tell us a little bit about your background and your current role at Vaps Callon, kind of how you got there. Sure, absolutely.
So, I'll rewind about 20 years. I can't believe I'm saying that. It's been a long time. So, I started my legal career at PHMSA as an attorney there.
I was there for about five years doing all kinds of things, rulemaking, enforcement, spent a lot of time in Alaska. It was a great place to start a legal career, worked with some really great people, learned a lot, went out into private practice after about five years. And another firm grew up a pipeline safety practice and then started with Vaps Callon almost 10 years ago. Keith Coyle, Brian Kurdock, and I started a small office here in DC for Vaps Callon.
We're up to about 20 people now, which is fantastic growth. But what I do and Brian does and our other team members do is really all pipeline safety. You name it. If it touches pipeline safety, we do it.
And so, a lot of enforcement, a lot of preventative counseling and super busy with rulemaking work over the summer and even before we're in pipeline safety, after authorization season. So, we get involved there as well. So, we really kind of touch all of the aspects of pipeline safety and we love what we do. Yeah, that's one of the things I've learned in my career is like a lot of other things with attorneys, there's lots of specializations.
And the pipeline safety world is a area of specialization, but it's very technical and it's very broad as an attorney. There's a lot of things you're doing in that domain. Yeah, absolutely. I mean, people say, well, that's really narrow and it's like, well, it's actually not.
We're doing legislation, we're doing rulemaking. And I really do love working with our engineering and technical partners and our clients. That's one of the favorite parts of my job. I talk to engineers every day and I translate engineering into layperson.
No, no, you translate engineering into legal person. That's a different thing. Oh, I'm poking fun. I find it interesting that you're saying, I love working with engineers because that makes you a unique kind of attorney.
Not every attorney would say that. I really do that. I mean, they're great partners. I think we can accomplish a lot together and we do.
Yeah, I agree. I agree. Well, look, I brought you on. There's several things I wanted to talk to.
And first, I just want to kind of talk a little bit about what PHMSA is up to. When I talked to Keith a few weeks ago, we talked about, you know, there's a new sheriff in town, a new administration and some of the things that are coming out. But one of the themes seems to be efficient regulations and use of advanced technology. So as somebody who's not with the agency, but works closely with them, and we're closely with the operators, how do you and how do you think the industry is viewing this new set of priorities that we're hearing from PHMSA?
Yeah, I think industry is viewing it very favorably as an opportunity. And I think it is a once in a generation opportunity. Basically, the administration and the agency have come to stakeholders and said, we want to do better. We want to achieve high safety performance, but we want to do it in a way that's sort.
How do we do that? And you hit on the key theme, which is the use of advanced technology. I think another key theme is, you know, is the regulatory framework risk-based? And if it's not, let's make it risk-based.
I think, you know, stakeholders are viewing this as a tremendous opportunity. Well, I think that the whole idea of trying to become more nimble as a rulemaking body is a huge challenge, a huge undertaking for any federal agency and the more technical the agency, I think the bigger the challenge is. But we have significant opportunities to improve safety performance with some of the technologies that are evolving really rapidly, in particular AI. AI is a bit of a buzzword, but, you know, AI is, you can think of that as advanced, very powerful algorithms.
And they have the ability to look at a lot of stuff and draw conclusions, which is one of the things that we have to do with human resources and pipelineing right now. Are you aware of any conversations going on in the rulemaking or regulatory oversight around AI? Yeah, a little bit. I think everybody is kind of in the same boat trying to figure out.
I think everybody recognizes the power and the potential and they're trying to figure out, okay, how can this make our sector better than the things that we do? And you hit on it. I mean, we have, you know, terabytes of data about, you know, even an individual pipeline or even from a single pig run. How do we integrate that data in a way that we can learn more from it than we can now?
And so, you know, I think the agency is very interested in that. I understand that they have used some AI tools themselves, you know, within DOT. I don't, you know, have any details on that, but, you know, I think they're looking at it and certainly on the operator side, their vendors who are starting to look at that and operators themselves are trying to figure out how they can leverage the technology. Yeah, we're doing the same thing.
We have a project ongoing that's a FIMS R&D effort that's using AI to support training and exercise response, that sort of thing. What I'm, what I'm finding about what I'm seeing happen in the market right now, in the pipeline market is AI requirements are starting to pop up in software and service agreements where they're, they're setting some boundaries of what is it, isn't allowable with, you know, my data as an operator, right, which makes a lot of sense, right? Because they don't just any AI to come in and grab their data and feed it out to the internet. Right?
That would not be good. And likewise, we're seeing a lot of people that are, they're all doing kind of exploratory projects, trying to figure out what the real world business cases and value propositions are from the tech. So really, it's going to move really fast. I think just looking at the market, you know, our market and pipeline is going to look radically different because of AI.
Exactly. Yeah. I mean, just, you know, I spent a fair bit of time personally with some of the AI tools and just, you know, thinking about what they did for me six months ago versus what they can do for me now. It's pretty different.
Yeah. Yeah. They're evolving quickly for sure. For sure.
So is there any other kind of advanced technology beyond AI that you think the industry is looking at and could have regulatory or rulemaking implications? Absolutely. I mean, I think one area where we as an industry have made tremendous progress, you know, in the past couple of decades is on, and again, a little bit specific here, but on analytical tools for integrity management, we know so much more than we did than when those rules were first adopted, you know, for liquids in the early 2000s and for gas in the 2000s. You know, and those roles were kind of calibrated to what we knew at the time.
And so they were a lot more conservative. And, you know, right now operators, our clients and operators across the country all the time are going out and digging up anomalies and fixing them that they know full well are not injurious. They're not going to cause harm. How do they know that the AI tools are better?
The analytical methods are better engineering critical analysis tools, you know, algorithms for sizing defects, all of that is just so much better. And then you layer that on top of just, you know, 25 years of experience with integrity management. And, you know, we're just really in a different place. And so there's an opportunity now to kind of right size the ranks and to allow operators to use these tools.
And so, you know, if I'm an operator and I'm forced to spend X to fix something that's not harmful, I'd rather spend that X, you know, over here on something, you know, on AI or on something that I know is harmful and really needs some more resources. So there's certainly been guidance come out of the agency around, you know, risk management approaches and probabilistic risk analysis approaches for determining how to, you know, optimize safety. But the challenge, I think, and I think is what you're pointing out, is some of the old, you know, regulatory requirements actually consume resources that would not otherwise be consumed if you were full on doing a risk analysis approach. Yeah, that's exactly right, Russell.
And, you know, there's certainly a lot of work that's been going on in the last 10 years around, you know, risk models for integrity management. But I think AI is going to, I think it's going to be a ton of topspin on that whole conversation. Because you're going to be able to look at tens of thousands of features that A, 10 years ago, you couldn't find because tools couldn't get them and B, far outstrip our ability from an engineering resources standpoint to do all the analysis in a manual way. So that provides a huge opportunity to potentially find things that might otherwise get missed and to redirect those limited resources where they have the most benefit.
Right. Right. And, you know, I don't think there's a lot of parallels in medicine and biology, you know, it's kind of what we're trying to do here. And I don't think AI is going to replace individuals.
I mean, what you, it's a tool for us, right? And you have a seasoned engineer who knows an asset really well. And this kind of allows them to magnify their efforts. It's not really replacing them.
It's sort of enhancing them. Yeah. And I think that's exactly right. I think it's another tool that goes into the engineers toolkit.
It does not replace engineering judgment. But what it does do is allow a single engineer to do a much, much larger set of analysis, which is required because the tools are generating exponentially more data. I mean, you ran a tool 10 years ago on a piece of pipe. You might find a hundred defects.
You run it today. You might find 10. Well, a hundred features that require investigation and you run that same kind of tool today with its advanced technology, you might find 10,000 features that require investigation. That's a big deal.
So it's like bounded up and all that. So what kind of things? So I know that there's been a call come for FIZZA to industry and other stakeholders saying, what are the things we could adapt, modify and improve, remove from the regulations that would improve? What kind of things are you seeing or do you see that?
Where does the opportunity to remove or revise some of the requirements? Yeah, I think it's a lot. And I think that's the challenges for us in industry. Is we basically what the agency has said through a variety of rulemaking is essentially the following.
We are open to your ideas, whatever they may be, and wherever they may be in the code. And that's a wonderful opportunity, but the challenge associated with doing that is prior to the station, right? Because we live in a world where, you know, in rulemaking, there are the rulemaking laws of physics, right? And they say that it always takes you longer to get these things out and done and do a good job than you think it will.
And so there's real timing constraints. And so I think as an industry, we really need to focus in on what's the most important to improve safety and improve efficiency. And I guess I'll maybe level set a little bit with where we are kind of macro on the rulemaking. I mean, right now we have literally dozens of rulemaking out there that the agency has issued so far this year.
The issued a number of rules kind of early part of the year in May and June. And then in early July, they issued over two dozen pipeline safety related rules. And so they, I mean, to your comment earlier, you know, on the agency's sort of ability to move forward on a lot of fronts that are technical at the same time. I mean, I commend them for their productivity.
I mean, they've gotten things out so fast that would have never come out in a previous administration until maybe a year or two. Right. Because everybody spends the first year figuring out what them to stand for, right? Like this team and the staff, they already know.
They know what the priorities are. And so they were able to hit the ground running an issue, a variety of quality documents in a short period of time. And they kept us busy for sure. I, you know, I think if I, if I, if you ask me what, what should stakeholders focus on?
I think most stakeholders should focus on two rulemaking of the several dozen. And they're all important, but there are two that really kind of have a lot bound up in them. One is repair criteria. And that's all about modernizing repair criteria.
We talked a little bit about that before. And then the second one is a broad regulatory reform rule, which the agency asked kind of across its programs, how can we do better? Um, it's a repair criteria. I industry did a great job kind of coalescing around what was important.
And, and there you've got more on the liquids than the gas side, but there's still some work to be done on the gas side. Uh, you have a set of criteria that really kind of frozen in time, frozen 25 years ago. Um, and this is, you know, long seem well criteria, dense, dense with metal loss, uh, tank requirements that are driving very, very large costs, um, that are really not warranted, right? Um, and that operators would really rather program elsewhere.
Uh, again, and it's all about making, you know, making sure the rags reflect modern technology and that they are risk based and they're not effectively risk based right now that there's work to be done. Now a lot of that stuff is prescriptive and that goes back to where we were when those regulations were originally written. Right. And we have as an industry way, way different capacities and capabilities in that domain that we did, you know, 20, 30 years ago when they're writing these rags.
Exactly. Exactly. And one of the things I think is most exciting in the repair criteria comment or, uh, context is the use of engineering critical assessments. So, you know, a suite of engineering tools where, you know, if I'm a dent with metal loss and it's underneath the river and in HDD and under the current criteria, I have to fix it.
So what does that mean? I'm not going to go take up the HDD. I'm going to redo an HDD, right? Maybe that's, maybe that's $10 million.
Um, or maybe I should run an engineering critical assessment. I have been tooled data. I have other information on materials properties. Let's run that through the assessment and ask, is this something that needs to be repaired?
Is this in jurias? And if it is, we'll do it. If it's not, uh, well, we'll keep it on it. Um, and I think that's, that's just one example of how operators would like to use engineering critical assessment, you know, sort of as a, as a backstop or we have this prescriptive criteria, but let's, let's create some ability to have an alternative.
Well, and the problem with the prescriptive criteria is it doesn't take into account the cost of repair. And, and while I realized that the public would be, well, I don't care what it costs on the pipeline to be safe, right? The pipeline operator is, well, you know, I want to pipeline to be safe as well, but I have to be able to sustain my ability to operate maintain pipeline. Right.
So, you know, something like, uh, doing an ECA on a particular feature and coming up with a strategy to manage that risk that costs a quarter of a million dollars a year versus spending, you know, 20 million to doing a new HDD under a waterway. That means that there's, you know, 19 million, 750 to spend on other stuff. Right. Cause they're going to not have that budget and I'm going to take that budget away.
They're going to apply that budget to other things. And I think what's really important, and I think, you know, we, we, as operator community, I think need to continually educate the public on this. Nobody wants to have a bad day. No, you know, we need to, you know, we have this, this, this set of social circumstances where the public expects us to operate safely 100% of the time.
And that is, you know, that's the objective. And so if something needs to get fixed, it's going to get fixed. And I think the public needs to understand that we sort of share that objective in a really fundamental way. You know, but what, what these alternatives allow us to do is just be, is to be smarter about it.
And I'll give you an example of how industry sort of put its money where its mouth is, you know, in comments on the repair criteria we're making. And industry said, Hey, we'd really like to have the option for ECA. But they also said, Hey, we should actually add some prescriptive repair criteria for things that we know, based on 25 years of experience, you really need to go fix those things. Right.
Now the code, right now the code doesn't require them to be fixed, you know, certain kinds of cracking defects. And so they didn't just come in and say, I want relief. I'm sorry. The operators just didn't come in and say, I won't really, if they said, we'd like some flexibility over here where we've earned it.
And then over here where we've learned about things that are actually harmful that you don't make us fix now, but we know you should. We're willing to have you put those in the code and hold us to it. Yeah. Things like that are really, you know, all that stuff gets lost in translation.
If you're reading something article in the media about pipeline safety, right? Sure. But it's super important because I think it underscores, you know, the commitment of industry to do the right thing. Yeah.
No, I think that's absolutely right. And I think those are really good, good points. Let me shift a little bit. You talked about there are a couple of dozen open rulemaking and that there are more things on the table in a shorter period of time with this administration than we have seen historically.
House FIMS are going to get all that done. Yeah. So I think they've pursued an interesting strategy. I think it's been pretty effective so far.
And so a lot of those rules are actually direct, they're called direct final rules. And so there are certain set of circumstances where federal agency can and just issue something that's final without coming through, you know, notice and comment, and they did that for many of the rules that they issued in July. And so things like clean up things like, Hey, here's how we're going to count time enforcement cases or here's how, you know, here's a standard that is just way overdue. We're just going to bring this standard up to date.
And then here's another one that's overdue and bring this and so on and so forth. And so a lot of those, the agency has just issued with immediate effect. Now in some cases, operators and even the NGOs came in and said, Hey, wait a minute, you know, we need to kind of go through more of a process here. And in those cases, they're going to say, all right, yeah, we'll go through the process.
But basically, they kind of laid out a bunch of cards and there are some that are going to, you know, just kind of go through. Like everybody just agrees that that's the right thing to do a specific example might be that API 1165, which is incorporated by reference was originally written in 2015, which makes that, I think, I'll actually take those back to 2007. And there's a second edition that came out two years ago that is radically different and reflects current technology for HMIs. Makes sense to just say, well, let's just adopt this new standard.
Because fundamentally, it says the same thing, but the examples are more reflective of what current capabilities are. And that should be, that shouldn't be controversial. Right. And I think the agency's done a good job of sort of finding those things that it could move ahead with where there's.
Yeah, I was calling those kind of administrative things because they, to me, most of that is not controversial. Of course, you never know until you put it out there. But a lot of that I think is not controversial. It's more administrative.
So you call that, what'd you call that direct to direct final rule? Direct final rule. Yeah. Is that a new TLA for the agency?
No, I mean, it's, you know, direct final rules have been allowed under federal law for a long time, decades. Okay. They just haven't heard that before. You know, they have done a few in the past, but it hasn't been terribly common.
I think, and again, this goes back to the fact that this leadership team knows the agency really well. And Keith, in particular, give him a lot of kudos. I mean, he knows the administrative procedure act. He knows all the tools available to the agency in a way that, you know, maybe proceeding administration is just where to wear them.
And so he said, all right, you know, how can we, how can we put points on the board? Right. And, you know, frankly, I mean, in those instances where they did a direct final rule and there were comments, then they kind of shift into sort of a more normal making process. They say, all right, okay, we need to kind of hear this one out.
We'll put this on the normal track, but for, for others, they're able to just proceed without doing that. So I think it's been a pretty shrewd and productive. Well, if you put a, you know, just pick a numbers out of the air, but if you put, you know, 30 things on the table that are direct final rules and 20 of them get through the process as direct final rules, well, you, you've just accumulated a lot of wins and improvement without a lot of, you know, unnecessary administrative overhead. Exactly.
Exactly. That's cool. It is. And I, you know, but I think for some of the bigger stuff where discussion needs to be added repair criteria, the regulatory reform rule, those are on a normal rule making track.
And so where we are in those is we, the agency issued advanced notices proposal making. So that's not a proposal. It's a, hey, we're thinking about the following. What do you think?
Um, and then the proposals, the actual proposed rule text will come later. And that's what the agency's working on now. Become it periods for the repair criteria and the regulatory reform rule closed over the summertime. And I know that, um, you know, Paul, we're already the new administrator and, um, I've been catchmenting Keith Coyle and others are working really hard.
So is Paul, has Paul gotten through a sin of confirmation? Is that company? Yeah, I should have should have mentioned that up front. He actually was sworn in on Monday.
So he's in the, uh, in the chair and films. I missed that, but that's awesome. I'm glad to hear that. I knew it was imminent.
I knew it was imminent. Great. We haven't had a proper administrator in a while. That's right.
He's been vacant for a while. That's, that's right. That's right. And the good thing is Mr.
Robert, he was not a stranger to the agency. He was the chief counsel in the last Trump administration. He knows Keith, he knows Ben, um, he knows Emily Wong well. That's the political leadership team.
So I think you already have a well oil team. Right. I agree to Keith and I talked about that. I think again, I think that's kind of awesome.
Actually, you got people actually know the business and know the agency. That's that's great. Can I mention one thing that we haven't touched on? And I get a lot of questions on and yeah, please, we're mentioning it.
You know, I think there's this sort of misconception, particularly in the media that, okay, there's just, you know, new agency, new administration, and they're just going to kind of slash and burn, right? Um, and that's, that's not what they're doing. No, it's not at all. And I would say first and foremost, their priority continues to be safety.
I mean, that's what their leadership has basically been speaking on, you know, out in public forums since the beginning of this administration, they have the secretary of transportation mandate to be a safety agency and to really focus hard. They well, the other thing that's also true kind of to this point, right? I'm just kind of trying to underscore what you're saying, Jim, is all the things that the previous administration was working on that were mandated by Congress are still mandated by Congress. That's correct.
Still have to be done and we'll be talking about when it comes time for reauthorization. So, you know, none of that stuff is, I mean, I may have gotten paused to have another look at it, but it's still got to get completed. That's right. And that's right.
And that's another really important factor that the agency is going to have to grapple with. And this is kind of where the NGOs come into play and the NGOs have already begun to file comments and some of these rulemaking proceedings and say sort of what you just said, hey, there's still these mandates out there. You know, you guys have to do that. And so I think PHMSA is balancing between a set of kind of the risk-based advanced technology, you know, modernize the code, they're balancing that against, all right, we still do have these statutory mandates that we need to deal with.
And you know, that's going to keep their plate full for sure. Yeah, no doubt. No doubt. OK, well, I had a couple of other things I wanted to visit about kind of on the same theme.
So what advice would you give to operators regarding these realities and what they should be focusing on themselves? Yeah, good question. So I think the key thing is not to treat every single one of these rulemakings as the top priority is you can't do that realistic, right? And so evaluating as an operating company where you are spending a bunch of money that you know is not making your assets safer and zero in on that.
I'm trying to get flexibility there so that you can reprogram, you know, that that resource to things where you really can move the needle on safety. And so that's going to be repair criteria. It's going to be modernization of things like the classification rules for the gas transmission operators. It's going to be a broader use of engineering critical assessments, not just for defects, but for other purposes as well for MOP re-reconformation, for example, that's allowed now, but it's a little bit constrained and needs to be unconstrained.
So I think it's just focusing on that sort of simple theme. And then you kind of pick the pieces of the rulemaking that kind of hit on that theme for you. So that's kind of one piece of advice, another piece of advice. And this is really important to me.
What we as an industry need and what firms are need in front of the public needs is rule changes that are durable that will stay on the test and are not likely to be, you know, reversed as political winds change in the future. And so what can we all come out there and really support from a cost and data perspective? And this is going to do a couple of things. And so I think when industry can bring to bear cost data to support what it is asking for and safety performance data to support what it is asking for, then it makes it easier for firms to satisfy pipeline safety, app rulemaking requirements that do a cost benefit analysis and risk analysis.
And remember, I mean, firms is changing rules that were put in place through other rulemaking in the past that had their own cost benefit analysis. And if we can't muster up enough data to show why the world has changed, then litigation risk goes up and there will be litigation. And so, you know, how can you contribute data and learning safety performance data cost data to the agency so that it can make a really strong cost benefit analysis and a really strong rulemaking that, you know, any future administration would look at it and say, yeah, that's actually, it's actually pretty reasonable. Yeah.
Well, I think I think the whole comment about durability is really material. And I think that's one of the things I tend to lose sight of. You know, when you work in technology, everything's quick, everything's transitional. But when you're working in regulatory rulemaking, you really need to focus on durability because these rule makings, they don't come around that often in any particular domain.
So they need to be able to last 10, 20 years. Yeah. And the flip side, the flip side of the durability coin is certainty. You're a big publicly traded company.
You don't want a new set of technical rules every time. No, no, it's just it's not anybody's interest. No. Yeah.
So one last question before we break your, Jimmy, what do you think this means in terms of inspections? You think that the, you know, our inspection is going to accelerate, is the nature of the inspection going to change? But what's your take or is it business as usual for now? Yeah, I think it's, you know, that's a whole interesting area.
I mean, the agency has issued a memo. They did this in July, a little bit already issued a memo that's laying out the inspection priorities. Right. It's really a wonderful thing.
It's like, Hey, we're going to focus on the things that have the biggest impact on one, the causes of accidents and two, the consequences of accidents. Um, I mean, that's great. Right. That's what they should be focused up.
Right. Yeah. Exactly. And so that that's been really helpful.
I think there's still some education to be done. I think that your leadership team's been a great job. Um, I think at the staff level, the field level, um, I think there's, you know, still some learning that needs to be done there in terms of focusing on those priorities. So I think for the short term, that's kind of going to set the tone.
I think longer term, if you do get regulatory modernization, um, you know, at the field level, there's going to be, you know, I think, at the industry level, too, there's going to be some education in terms of, okay, how, how is the world changed? How do we move from a, in a place where the criteria are really prescriptive and it's kind of easy. It's like, yeah, I think, yeah, yeah. Here's my take on that.
I think what we're going to see, and I don't know the timeframe that this is going to occur, but we're going to see a shift from questions like, did you do this? Where's your evidence to questions like, why did you choose to do this? And not this. Yeah.
Right. Right. Because actually the second question is a much better question, but it does require a level of maturity and competency and capability on the operator side that's new and different. Yeah.
And I think, you know, operators and, and from Zen inspection staff, we're going to, you know, they're going to have to learn together on that one. Because you're exactly right. When you move from something that's very prescriptive to something that's more, you know, tell me, show me your work, show me why you did this. There's just, it opens up these opportunities for more dialogue and kind of more back and forth.
Um, frankly, I mean, in an ideal world like better partnerships between, right? And between the regulated community, they have a good conversation about the engineering basis for something. They might not agree, but, you know, they kind of respect each other's positions. Exactly.
Exactly. Well, listen, um, this is awesome. Uh, I appreciate you, you know, taking the time to talk to me. We're kind of at the end of time, but we need to come back and get back together.
Um, I think the next thing we ought to talk about is whatever the next big rulemaking is. I mean, I haven't had one of those conversations in a while. It's about time. Yeah.
You know, and I think it will be, you know, hopefully the next couple of months will actually get one of these proposed rules with some rule text in it. We can sink our teeth into and have an conversation. I'd look forward to that. I wonder if we'll have an LPAC or a GPAC before the end of the year.
Do you think? Yeah, I don't know. I don't know. Yeah.
I think my thinking is probably not, but we might have three next year. I think next year is going to be a busy year. I absolutely agree with you. I think we're going to be hustling.
Buckle up, buckle up. Yeah. That's the takeaway from this podcast. Things are going to change.
Buckle up. That's right. That's a lot of opportunity, though. Thank you, Russell.
I really appreciate the opportunity to join you. It's always a great time. Great. Thanks.
Thanks for your time, Jim. We'll talk again soon. OK. I hope you enjoyed this week's episode of the Pipelineers Podcast and our conversation with a DM.
Just a reminder, you should register to win our customized Pipelineers Podcast Yeti Tumpered. Simply visit pipelinepodcastnetwork.com slash win and enter yourself in the drawing. If you'd like to support the podcast, please leave us a review. And you can do that on Apple Podcast Google Play Spotify or wherever you happen to listen, 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 pipeline podcast network. We'll reach out to me on LinkedIn. Thanks for listening.