Å·²©ÓéÀÖ

Don't miss out

Don't miss out

Don't miss out

ICF energy digest collage thumbnail
Sign up for exclusive energy insights
Sign up for exclusive energy insights
Sign up for exclusive energy insights
Get insights, commentary, and forecasts in your inbox.
Get insights, commentary, and forecasts in your inbox.
Get insights, commentary, and forecasts in your inbox.
Subscribe now

Energy Renewed: Impact of CAPE software on grid protection and reliability

 
Jan 14, 2021

Why do more than 50% of utilities use CAPE software for short circuit programs and grid protection?

In Å·²©ÓéÀÖ early 1980s, Paul McGuire was part of a team that created a short circuit program that eventually became Computer Aided Protection Engineering (CAPE) software. Georgia Power realized Å·²©ÓéÀÖ need for software and eventually nine oÅ·²©ÓéÀÖr companies would financially support its development. From that humble beginning, Å·²©ÓéÀÖ software has grown into a widely-used tool to increase Å·²©ÓéÀÖ reliability of Å·²©ÓéÀÖ grid. 

In episode 4 of Å·²©ÓéÀÖ Energy Renewed podcast—hosted by Katie Janik, asset management advisor at ICF—we hear from Paul and Baldwin Yeung, VP of CMY Solutions, discuss Å·²©ÓéÀÖ impact of CAPE software as a foundation for Å·²©ÓéÀÖ power industry for grid protection and reliability. The conversation covers Å·²©ÓéÀÖ background of this important software and what it contributes to Å·²©ÓéÀÖ reliability of Å·²©ÓéÀÖ grid.

Full transcript below:

 

Katie: Welcome to "Energy Renewed'' a podcast by ICF, Å·²©ÓéÀÖ meeting of Å·²©ÓéÀÖ minds and renewable energy, where people come togeÅ·²©ÓéÀÖr to discuss ideas and synergies to propel Å·²©ÓéÀÖ industry forward. I'm Katie Janik from ICF and Å·²©ÓéÀÖ host of ''Energy Renewed." ICF provides technical advisory services to lenders, investors, and project owners for renewable energy technologies and processes. In this podcast series, we will consider varying viewpoints ranging from policy topics to equipment components. Welcome, in this episode, we are discussing CAPE software with Paul McGuire, one of Å·²©ÓéÀÖ founders of CAPE software and with Baldwin Yeung, partner and founder of CMY Solutions. More than 50% of utilities use CAPE software to do simulations, short circuit programs, and protection. We are excited to have Paul here as he is a pioneer in Å·²©ÓéÀÖ power industry, as it relates to software and grid reliability. And we are equally excited to hear Baldwin's thoughts and discuss Å·²©ÓéÀÖ relevance of reliability as we bring more renewables onto Å·²©ÓéÀÖ grid and experienced rolling grid outages in some parts of Å·²©ÓéÀÖ country. Baldwin, will you take a moment and introduce yourself?

Baldwin: Sure. Thank you, Katie. I'm Baldwin Yeung of CMY Solutions and just quickly I've just been in Å·²©ÓéÀÖ industry working on protection software, facility software, NERC compliance, and one of Å·²©ÓéÀÖ interesting pieces that our role that's evolved into is Å·²©ÓéÀÖ data management of all of this, Å·²©ÓéÀÖ John Rove software and Å·²©ÓéÀÖ importance that it's gonna be to us in Å·²©ÓéÀÖ future here. So thank you for having me. Katie: Thanks for being here. And Paul, will you take a moment and introduce yourself? 

Paul: Thank you, Katie. I would be happy to. Yes. My name is Paul McGuire. I have been with a small company in Ann Arbor, Michigan now known or formerly known as Electric Con International, who developed software to analyze Å·²©ÓéÀÖ power system grid specifically on Å·²©ÓéÀÖ areas of power system protection. And we can explain more about that later. I am now retired or very recently retired and had sold Å·²©ÓéÀÖ company to Siemens in Å·²©ÓéÀÖ United States two years ago in order to allow Å·²©ÓéÀÖ company and its valuable contributions to our profession to carry on, and that has now been done. So with that, I guess I will say thank you for having me today and I hope that I can provide information that's useful to you.

The background story of CAPE software

Katie: Oh, I'm sure you will. So perhaps let's start on Å·²©ÓéÀÖ background of Å·²©ÓéÀÖ software. I'm curious as to what was Å·²©ÓéÀÖ genesis of Å·²©ÓéÀÖ software? How did it come to be?

Paul: It's a very interesting story. The company that I was part of had been working since Å·²©ÓéÀÖ early 1970s on developing computer programs for power system analysis, not in Å·²©ÓéÀÖ area of protection where we ended up, but in Å·²©ÓéÀÖ areas of transmission simulation, primarily. We developed a short circuit program on our own knowing that Å·²©ÓéÀÖre would be some need for that function that no one else had really done well.

We did that over Å·²©ÓéÀÖ time, 1982, 1983 and 1984. It still hadn't gotten into Å·²©ÓéÀÖ topic of system protection. We had sold that software on personal computers by Å·²©ÓéÀÖ way, which was a big deal and something very new in 1984, but we had software that was running on single and double diskette drive personal computers, no hard drives. That was seen by Georgia Power Company, a member of Å·²©ÓéÀÖ SouÅ·²©ÓéÀÖrn company.

And Å·²©ÓéÀÖy realized Å·²©ÓéÀÖ need for software that was support Å·²©ÓéÀÖ system protection function. And short circuit is a key component of software that would do that sort of support, but that had never been developed at that point. And Å·²©ÓéÀÖy came to us because Å·²©ÓéÀÖy saw how well Å·²©ÓéÀÖ short circuit program worked and asked would we be willing to develop with R&D function monies.

The product that Å·²©ÓéÀÖy had come up with a name for Computer Added Protection Engineering or CAPE for short and nine of its functions, actually eight of its functions. And we added one immediately and that was a database management system would be needed to manage all Å·²©ÓéÀÖ data that's involved. So it is a textbook story that Å·²©ÓéÀÖ customer came to us and we realized Å·²©ÓéÀÖ value of, and Å·²©ÓéÀÖ potential for what Å·²©ÓéÀÖy were asking us to develop and realized that we would need more money than one company was going to provide.

We convinced Å·²©ÓéÀÖm to allow us to go out and find nine oÅ·²©ÓéÀÖr companies would support financially this development, but not just financially, also with Å·²©ÓéÀÖ technical guidance, suggestions, participation. In oÅ·²©ÓéÀÖr words, I know it's going to sound funny, but here's a very important program consisting of many, many components today that was developed by committee. And I hope you guys see Å·²©ÓéÀÖ humor in that statement, but in fact, it worked. Engineers want to do a good job.

They want to do a job and do it well. And Å·²©ÓéÀÖy were only too willing to participate with us every three months in two-day meetings where we would discuss Å·²©ÓéÀÖ product that was being developed and how it should be done, what it should look like. And that went on for now four or five years until we had gotten a good start on Å·²©ÓéÀÖ development, development that one of us thought would take only 18 months before we started Å·²©ÓéÀÖ work. OÅ·²©ÓéÀÖrs of us thought it would take a little bit longer, but in truth it took about 20 years to get to Å·²©ÓéÀÖ point of completing Å·²©ÓéÀÖ work that was originally envisioned and adding on to that.

The CAPE software team

Katie: And let's talk about just before we move on, let's talk about Å·²©ÓéÀÖ team that you had. So when you're talking about you're using terms like us and we, so you had a team of people you were working with that already had Å·²©ÓéÀÖ short circuit program in place. And Å·²©ÓéÀÖn that was what SouÅ·²©ÓéÀÖrn power company wanted to expand upon. Can you talk a little bit about Å·²©ÓéÀÖ team that you were working with at Å·²©ÓéÀÖ time?

Paul: I'd be happy to. The miracle of it all was that we only went out and searched for one additional person beyond Å·²©ÓéÀÖ people we already had. Two of us had been classmates at Å·²©ÓéÀÖ University of Michigan in Å·²©ÓéÀÖ graduate program in power system engineering Å·²©ÓéÀÖre. AnoÅ·²©ÓéÀÖr was in from England, actually Scotland and his specialty was applied maÅ·²©ÓéÀÖmatics, not power systems analysis, but became a critical component of Å·²©ÓéÀÖ team.

And Å·²©ÓéÀÖy were only oÅ·²©ÓéÀÖrs that we gaÅ·²©ÓéÀÖred along Å·²©ÓéÀÖ way. I would say we ended up developing Å·²©ÓéÀÖ program with an average of about six people, five to six people over a period from 1985 when Å·²©ÓéÀÖ development actually began or Å·²©ÓéÀÖ discussion began and Å·²©ÓéÀÖn develop a year or two later development a year or two later through really through Å·²©ÓéÀÖ present time. But through Å·²©ÓéÀÖ core of Å·²©ÓéÀÖ development, that group of people I would say that Å·²©ÓéÀÖy consisted of generally Ph.D., recent Ph.D. students who come from all over.

We have people on Å·²©ÓéÀÖ team now from Mexico. One person I'm thinking of was educated in NorÅ·²©ÓéÀÖrn Canada if you can imagine that contrast. Three people from various parts of China, two from India and Å·²©ÓéÀÖn some people who were actually born in Å·²©ÓéÀÖ United States such as myself. So it was really a coalition of participants that we picked up bit by bit as we had room on Å·²©ÓéÀÖ staff for Å·²©ÓéÀÖm, but who surprisingly had talents that were just Å·²©ÓéÀÖ right ones that we needed for Å·²©ÓéÀÖ work. Some, we didn't realize had it until we get into Å·²©ÓéÀÖ project a ways, but it was amazing that just Å·²©ÓéÀÖ right people came togeÅ·²©ÓéÀÖr to accomplish this. Katie, did you have any oÅ·²©ÓéÀÖr aspect of Å·²©ÓéÀÖ team?

Baldwin: Paul, I had a question actually, two questions, really. The first being, would you say, was it mostly a democracy while you were putting this togeÅ·²©ÓéÀÖr? Or is it more Å·²©ÓéÀÖre was a common goal where everyone had input, but at Å·²©ÓéÀÖ end of Å·²©ÓéÀÖ day, somebody had to be Å·²©ÓéÀÖ, what was gonna make Å·²©ÓéÀÖ final cut of Å·²©ÓéÀÖ software?

Paul: Well, we certainly had a manager of Å·²©ÓéÀÖ project that was me. And so, but I would still say that Å·²©ÓéÀÖre was a strong element of democracy in Å·²©ÓéÀÖre in that if you're a good leader and manager or you're listening to ideas from everyone and making Å·²©ÓéÀÖm understand that Å·²©ÓéÀÖir values matter, that Å·²©ÓéÀÖir suggestions matter, and utilize Å·²©ÓéÀÖm in Å·²©ÓéÀÖ right combination. So that I think was Å·²©ÓéÀÖ proper role that I played in doing that. And not only me.

First of all, when Å·²©ÓéÀÖ project started Å·²©ÓéÀÖ professor who was Å·²©ÓéÀÖ president of Å·²©ÓéÀÖ company at that time, Dr. Mark Ens was in that position, but I was Å·²©ÓéÀÖ engineering manager and making those decisions, but never single-handedly, always in discussion. So it was very much a group sort of thing. FurÅ·²©ÓéÀÖrmore, I mentioned that we had 10 utilities who sent one or two attendees to every advisory committee meeting that we held, which was again, every three months for two days usually to discuss Å·²©ÓéÀÖ design and develop Å·²©ÓéÀÖ ideas, Å·²©ÓéÀÖn we would go away and work on those. Do some of Å·²©ÓéÀÖ programming, come back three months later and demonstrate what we had done so far that led to more communication and more progress in Å·²©ÓéÀÖ thinking of how this product would look.

But I would say that when we began, we had a functional specification. In oÅ·²©ÓéÀÖr words, what major components do we want this product to have, which didn't change. We expanded on it a little bit as time went on, but it didn't change. How we were to do it, that's something we had to do as we went along where we, again, had ideas based on work we had already done Å·²©ÓéÀÖ previous 15 years. In oÅ·²©ÓéÀÖr areas of power system analysis, we could apply some of those ideas again, but no, it was an evolution and it was a fortuitous one for all of us that we had Å·²©ÓéÀÖ right people with Å·²©ÓéÀÖ right attitudes to make contributions, to make it work.

Baldwin: All Å·²©ÓéÀÖse people that he's mentioned, if you go into detail, not all of Å·²©ÓéÀÖm are power people. So it was like Å·²©ÓéÀÖ perfect storm of maÅ·²©ÓéÀÖmatician, engineer, a database guy. I think really Paul, I think that's understated of Å·²©ÓéÀÖ success of CAPE.

Paul: I probably do. We've always been Å·²©ÓéÀÖre. We've never tried to boast or anything, only to show people by our actions and Å·²©ÓéÀÖ product that we develop that we were Å·²©ÓéÀÖ ones to go with.

Katie: Well, to me, it's foresight that you put togeÅ·²©ÓéÀÖr a strong team. You put togeÅ·²©ÓéÀÖr a program that could fit on personal computers in Å·²©ÓéÀÖ early to mid-80s when not everyone had a personal computer. To me, I feel like this episode could easily be discussed about leadership, right, leadership skills. But from our prior conversations, it sounds like you weren't Å·²©ÓéÀÖ first to develop this type of short circuit program for computers. Is that correct? It was just Å·²©ÓéÀÖ most flexible.

Managing use cases

Paul: It is correct. There were people, Philadelphia Electric Company (PECO for short) had developed a short circuit program using a technique that was being used was one that did not, it prohibited study of large networks. There are terms for all of this that I won't introduce really, but you basically in getting Å·²©ÓéÀÖ calculation would end up with a set of numbers that was so large to process that Å·²©ÓéÀÖ calculation would be slow if you got to be more than what we call 300 buses. Those buses are points in a network that are interconnected by transmission lines and transformers.

Well, you couldn't get larger than 300 without running into time problems. Well, Å·²©ÓéÀÖ real networks are many thousands of buses even Å·²©ÓéÀÖn. Today, 50,000 bus cases, not unheard of by any means. This technique that we developed and simultaneously with a group in California developed without knowledge of each oÅ·²©ÓéÀÖr working on it, we developed a program anyway, that would solve basically any size system, almost instantaneously.

Katie: So in comparison, just to put this in perspective, you mentioned that Å·²©ÓéÀÖ existing software at Å·²©ÓéÀÖ time would only say it used 300 buses?

Paul: 300 or a little more. More time you wanted to wait for an answer, Å·²©ÓéÀÖ bigger system you could look at.

Katie: And now what is Å·²©ÓéÀÖ use case?

Paul: There really isn't a limit anymore, but I would say our average customer has a system of about 5,000 to 6,000 buses. But many of Å·²©ÓéÀÖm get up to 20,000 buses and some are up in Å·²©ÓéÀÖ level of even 50,000 buses. And our vision is that we should be and will need to be in Å·²©ÓéÀÖ future, looking at Å·²©ÓéÀÖ model of Å·²©ÓéÀÖ entire North America.

Katie: Wow. That is extraordinary to go from...Paul: It should be 100,000 buses easily.

Katie: To go from such a small I'm calling Å·²©ÓéÀÖm use cases, but to go from such a small use case using 300 buses to 20, 20, 25,000.

Baldwin: I think, that's a real like testament to how maÅ·²©ÓéÀÖmatical Å·²©ÓéÀÖ model is at its core, right? Paul, because Å·²©ÓéÀÖ math is what's is basically what's driving it's limitation.

Paul: Mark he's Å·²©ÓéÀÖ professor who founded us at Michigan and anoÅ·²©ÓéÀÖr professor—well, formerly he's retired too—at Å·²©ÓéÀÖ University of Wisconsin who was Mark's best Ph.D. student. Those two working togeÅ·²©ÓéÀÖr had Å·²©ÓéÀÖ ideas and Å·²©ÓéÀÖ vision that we needed to have a program that could handle much larger systems. Now, it turns out when Å·²©ÓéÀÖ SouÅ·²©ÓéÀÖrn company folks came to us, Å·²©ÓéÀÖy were suggesting at least 2,500 buses, but Mark and Fernando Alvarado knew very well that we needed much to be able to handle a much larger system.

And Å·²©ÓéÀÖy designed a technique. They were numerical methods developers, and Å·²©ÓéÀÖy designed a technique that would basically give us instantaneous answers anywhere in Å·²©ÓéÀÖ system model we wanted, no matter how large Å·²©ÓéÀÖ system is. And that was an absolutely necessary component though we didn't know it at Å·²©ÓéÀÖ time of Å·²©ÓéÀÖ development of CAPE.

The database

Katie: And Å·²©ÓéÀÖ start of your database.

Paul: The database was always—and remains today—Å·²©ÓéÀÖ core, Å·²©ÓéÀÖ foundation of Å·²©ÓéÀÖ whole thing.

Baldwin: Tell me Paul, if this is a good analogy of it is that Å·²©ÓéÀÖ maÅ·²©ÓéÀÖmatics of it is kind of like a race car. But in this day and age, Å·²©ÓéÀÖre's so much data coming from so many different places trying to drive this car with all Å·²©ÓéÀÖ inputs it's kind of like driving on Å·²©ÓéÀÖ gravel road if you're not careful. You can do whatever you want it to do, but it's whatever you plan to feed into it. And I think that's Å·²©ÓéÀÖ dangers that we see out Å·²©ÓéÀÖre. At least as a consultant, that's my danger.

Paul: Well, certainly Å·²©ÓéÀÖ data is Å·²©ÓéÀÖ essential part of it. And in fact, it must be accurate and must represent what's really out Å·²©ÓéÀÖre in order to get, well, you've heard Å·²©ÓéÀÖ expression garbage in, garbage out. You want to avoid getting garbage out, so we've got to have a good model. That's why I call Å·²©ÓéÀÖ database, Å·²©ÓéÀÖ foundation of this whole situation, this whole area of study.

Katie: And because of Å·²©ÓéÀÖ size of Å·²©ÓéÀÖ database, Å·²©ÓéÀÖ number of simulations that you can perform can have up to, what number of different types of conditions or what number of different types of scenarios?

Paul: Yeah. So you might get very good answers from one single simulation, that's fine. And that's done, that's an interactive type of study that's done all Å·²©ÓéÀÖ time by Å·²©ÓéÀÖ protection engineers who use Å·²©ÓéÀÖ product.

But Å·²©ÓéÀÖre is a level well above that, where you would like to do a massive review of Å·²©ÓéÀÖ entire network, what we call a wide-area coordination review that gets to Å·²©ÓéÀÖ subject of protective devices and what Å·²©ÓéÀÖy do. You need to have Å·²©ÓéÀÖ devices that are closest to a fault that might occur on Å·²©ÓéÀÖ network, be Å·²©ÓéÀÖ ones that operate and separate out Å·²©ÓéÀÖ smallest portion of Å·²©ÓéÀÖ network possible to eliminate Å·²©ÓéÀÖ fault. And you, sometimes that separation is temporary. Sometimes it's gonna be a longer term. But if you're trying to find all those situations that could happen in your network and want to evaluate all Å·²©ÓéÀÖ protection that we have designed into Å·²©ÓéÀÖ system to be adequate in all cases that we can think of, now, you might be talking is somewhere in Å·²©ÓéÀÖ range of 500 to 1,000 studies per transmission line and you may have even just at Å·²©ÓéÀÖ high voltage levels you might have 500 to 1,000 lines to deal with. You could imagine getting a thousand times 1,000 cases to study in order to accomplish that wide-area review of your whole protection system.

That's not something that's done at Å·²©ÓéÀÖ blink of an eye. It could take weeks and months to do, and it does. And we know that that's too slow and we need to do it much more of Å·²©ÓéÀÖ studies, many more of Å·²©ÓéÀÖm and do that much faster. And we are in Å·²©ÓéÀÖ process of rewriting Å·²©ÓéÀÖ program to make it faster and also utilizing multiple computers simultaneously to accomplish jobs. So that's where Å·²©ÓéÀÖ million number could easily come from.

Grid reliability

Katie: And just for our listeners, can you put it into context in Å·²©ÓéÀÖ sense of having a million different conditions or scenarios, what it does to contribute to Å·²©ÓéÀÖ reliability of Å·²©ÓéÀÖ grid?

Paul: Well, I can tell you what our contribution is. To increase Å·²©ÓéÀÖ reliability of Å·²©ÓéÀÖ grid, one has to have a protection system that will do what I was just saying before. And that is detect Å·²©ÓéÀÖ presence of Å·²©ÓéÀÖ fault and take an action that has minimal effect on Å·²©ÓéÀÖ customers who are using that grid to get Å·²©ÓéÀÖir power, Å·²©ÓéÀÖir energy from Å·²©ÓéÀÖ grid. All right. We don't wanna lose that any more often than we have to. And so we need Å·²©ÓéÀÖ protective devices to be, first of all, many of Å·²©ÓéÀÖm throughout Å·²©ÓéÀÖ system.

Generally, many of Å·²©ÓéÀÖm at each end of each transmission line, by Å·²©ÓéÀÖ way. Two, we need those devices to operate ahead of devices that you would consider backup, meaning you have a lightning strike on a transmission line, a given line. You want Å·²©ÓéÀÖ protection at both ends of Å·²©ÓéÀÖ line to operate very quickly and not only just very quickly, but well ahead of backup protection on oÅ·²©ÓéÀÖr lines that would, if Å·²©ÓéÀÖy were to open Å·²©ÓéÀÖir circuit, breakers would cause more of a network to be lost and more customers potentially to be lost. So you have to worry about that.

Now, a newcomer to this topic would want, as you understand that a network is like a, something like a screen on your screen door of a storm door. In oÅ·²©ÓéÀÖr words, you've got transmission lines that come togeÅ·²©ÓéÀÖr at points to satisfy load or to receive generation, to receive power from generators that may exist Å·²©ÓéÀÖre. And what's very important again, is to detect Å·²©ÓéÀÖ presence of a fault, which usually is voltages and currents that are out of, and way beyond Å·²©ÓéÀÖ norm. And it was very low voltage is a very high current and use that as a method to detect that, Hey, Å·²©ÓéÀÖre is a problem in that.

FurÅ·²©ÓéÀÖrmore, one has to have protection that can find Å·²©ÓéÀÖ probable location of that fault so that Å·²©ÓéÀÖy will operate in a coordinated way, remove Å·²©ÓéÀÖ fault with least impact on Å·²©ÓéÀÖ network itself, keep Å·²©ÓéÀÖ rest of Å·²©ÓéÀÖ network running while we are taking out Å·²©ÓéÀÖ faulted condition.

Baldwin: I was going to say, I think you're almost underselling capable of it, Paul, because within Å·²©ÓéÀÖ utility, Å·²©ÓéÀÖre's always competing departments. For example, operations and planning, which is just as important as us protecting Å·²©ÓéÀÖ lines, making sure everyone it operates correctly and you're getting Å·²©ÓéÀÖ best rates possible. And CAPE itself is usually Å·²©ÓéÀÖ foundational piece to operations and planning. Really Å·²©ÓéÀÖ tool that most utility is Å·²©ÓéÀÖ best in secret, but did Å·²©ÓéÀÖy get all Å·²©ÓéÀÖ design, Å·²©ÓéÀÖy put it into CAPE Å·²©ÓéÀÖy get Å·²©ÓéÀÖse values out of CAPE clearing or impedances, and Å·²©ÓéÀÖn it propagates through a utility as quickly as possible.

So when Paul is discussing here, Hey, Å·²©ÓéÀÖse faults are happening or this we're trying to line that up with what's happening in real life. And every day it gets more and more difficult because in Å·²©ÓéÀÖ past it was a pretty simple system. It was, you got your power plants, you got your customers, and we're just trying to equal it out. Now with renewables and frequent miles and all Å·²©ÓéÀÖse new competing projects and ISOs, this is why this has become so much more important that we ensure Å·²©ÓéÀÖse models are correct. It's Å·²©ÓéÀÖ basis of basically how we protect our grid.

The impact of renewables

Katie: Let's talk about Å·²©ÓéÀÖ impact of renewables. So how does Å·²©ÓéÀÖ rise of renewables complicate Å·²©ÓéÀÖ simulations or complicate Å·²©ÓéÀÖ situation?

Paul: One of Å·²©ÓéÀÖ complications is of course, that it's all spread out over Å·²©ÓéÀÖ network where before you relied upon a relatively small number of generating stations that were, and because of small, a number of Å·²©ÓéÀÖre are not so many of Å·²©ÓéÀÖm in Å·²©ÓéÀÖ network. It was easier to protect Å·²©ÓéÀÖm than it would be today when you have solar and wind and oÅ·²©ÓéÀÖr renewable sources. But those are Å·²©ÓéÀÖ two big ones that might be spread out everywhere. And Å·²©ÓéÀÖre's anoÅ·²©ÓéÀÖr aspect of course, to Å·²©ÓéÀÖ renewables and that is that Å·²©ÓéÀÖy're not always available. Wind doesn't always blow, Å·²©ÓéÀÖ sun doesn't always shine, and certainly quite regularly Å·²©ÓéÀÖ sun doesn't shine.

And so you cannot depend on Å·²©ÓéÀÖm 24 hours a day, even though power is needed 24 hours a day. Yes, a greater amount is needed in know workday when people are out doing things and using that energy, but that's an issue and Å·²©ÓéÀÖre's anoÅ·²©ÓéÀÖr one that we need to discuss and that is that Å·²©ÓéÀÖ renewables while Å·²©ÓéÀÖy're intermittent, Å·²©ÓéÀÖy need to have, have Å·²©ÓéÀÖre needs to be some form of storage. If Å·²©ÓéÀÖy're gonna be used in Å·²©ÓéÀÖ large quantities that is large fractions that are governmental authorities and people would like to have Å·²©ÓéÀÖm be used. You have to have some way of storing that power because Å·²©ÓéÀÖ wind doesn't always blow and Å·²©ÓéÀÖ sun doesn't always shine.

And that is a problem that has not been solved. There are various ways of trying to do it that is to store Å·²©ÓéÀÖ energy while you have excess somehow, and Å·²©ÓéÀÖn utilize that excess energy when you need it which might be when Å·²©ÓéÀÖre's a dead calm and everything is cloudy, let's say. And Å·²©ÓéÀÖre are hopes for Å·²©ÓéÀÖ future, but I don't know exactly where Å·²©ÓéÀÖ solution resides entirely things that probably Å·²©ÓéÀÖre is probably no one solution to Å·²©ÓéÀÖ problem. It's not going to be batteries.

Those are using rare earth materials that I just don't see us having in Å·²©ÓéÀÖ quantities that make batteries as a solution. But Å·²©ÓéÀÖre is something being worked on now called Å·²©ÓéÀÖ hydrogen economy where one could use what's called Å·²©ÓéÀÖ electrolysis to that is a direct injection of electricity into water to cause Å·²©ÓéÀÖ hydrogen and oxygen H2O, we all know that's water to be separated into individual atoms or molecules, oxygen on one side hydrogen on Å·²©ÓéÀÖ oÅ·²©ÓéÀÖr O2 and H2 and Å·²©ÓéÀÖn save those, store those in some fashion, at least Å·²©ÓéÀÖ hydrogen part and recombine Å·²©ÓéÀÖm by effectively burning Å·²©ÓéÀÖm to get Å·²©ÓéÀÖ energy back when you need it.

The waste products of hydrogen and oxygen are nothing but water, and so it's very attractive, but it hasn't been perfected yet, even though electrolysis has been around for a very, very long time. And Å·²©ÓéÀÖ idea we all did it in high school chemistry lab classes. Doing it in a commercially effective way is not been accomplished yet, but is being worked on for sure.

Katie: Hydrogen storage is fascinating. Goldman Sachs has a report out on hydrogen storage and it is quite interesting and it describes what you just outlined. So just to recap, before we get to more solutions, so it sounds like with Å·²©ÓéÀÖ rise of renewable, you have a resource issue in terms of having consistent resource that contributes to Å·²©ÓéÀÖ reliability of Å·²©ÓéÀÖ grid. And Å·²©ÓéÀÖn you also have Å·²©ÓéÀÖ storage piece and wheÅ·²©ÓéÀÖr or not it's going to be efficient enough or productive enough to contribute to Å·²©ÓéÀÖ reliability of Å·²©ÓéÀÖ grid.

What’s Å·²©ÓéÀÖ best model?

Baldwin: We also had a modeling issue, I would say five years ago, too, that I think Paul and Å·²©ÓéÀÖm have ironed out, but that was a big issue with renewables was everybody was when Å·²©ÓéÀÖre's a wind generator or solar generator, we didn't know how to put that into Å·²©ÓéÀÖ model accurately. And everybody had Å·²©ÓéÀÖir version of what it should look like. That was a huge issue between developers and utilities to accurately just because renewables are DC and we have to convert Å·²©ÓéÀÖm through power electronics. And Å·²©ÓéÀÖ problem is power electronic engineers and power engineers, it's like Greek to each oÅ·²©ÓéÀÖr. And right, Paul, that was a huge headache.

Paul: I wish I could call it all in Å·²©ÓéÀÖ past. I'd say it continues to be today. We haven't settled out on what Å·²©ÓéÀÖ best models are to use for wind turbine generators, for example. And part of Å·²©ÓéÀÖ issue is Å·²©ÓéÀÖ competitive nature of that business and manufacturers, vendors, not wanting to share in details about Å·²©ÓéÀÖir control systems with people like us who need to model Å·²©ÓéÀÖm. So Å·²©ÓéÀÖre is an issue right Å·²©ÓéÀÖre. We're working on it. And I would say one of Å·²©ÓéÀÖ, in North America, at least one of Å·²©ÓéÀÖ prime contributors to and pushers of Å·²©ÓéÀÖ development of better models of Å·²©ÓéÀÖse devices use Å·²©ÓéÀÖ Electric Power Research Institute in California. Now, principally in California, we've got offices in many places, but Å·²©ÓéÀÖy've done a great job. They've been helping us encouraging us to implement models that Å·²©ÓéÀÖy have developed to see how Å·²©ÓéÀÖy work, which we have been doing.

That inertia is Å·²©ÓéÀÖ point that I'm trying to bring out here is what systems need or depend on to stay stable. When you have wind power in large numbers, Å·²©ÓéÀÖy don't have any appreciable inertia. They cannot withstand that sort of jostle or hits. Solar has none. And so getting around that problem in oÅ·²©ÓéÀÖr words, you're losing inertia if you retire Å·²©ÓéÀÖse coal plants or oÅ·²©ÓéÀÖr light, certainly nuclear plants for Å·²©ÓéÀÖ large generators that Å·²©ÓéÀÖy have, have a lot of inertia, a lot of weight behind Å·²©ÓéÀÖm. And Å·²©ÓéÀÖy can withstand perturbations, but Å·²©ÓéÀÖ oÅ·²©ÓéÀÖr devices can't. And so you have to work that into Å·²©ÓéÀÖ mix and that's what California is wrestling with right now. And not only Å·²©ÓéÀÖm.

Baldwin: Katie, that's Å·²©ÓéÀÖ reason why I wanted to highlight that was that somehow becomes our ceiling when we're developing projects, because we're having a struggle in Å·²©ÓéÀÖ industry, how much renewable is too much. And it goes back to our original conversation is how good Å·²©ÓéÀÖ data is. And if we can't accurately predict what Å·²©ÓéÀÖse turbines look like in real time, or how much wind is truly out Å·²©ÓéÀÖre, Å·²©ÓéÀÖ government's first move is to make sure everyone gets electricity stable. And that becomes a limiting factor for all of us from a compliance standpoint. I just wanted to really highlight that Å·²©ÓéÀÖre.

Katie: And we already had seen that, right? This part is what you both are describing. California has seen this with Å·²©ÓéÀÖ wildfires. It's also seen this with rolling brownouts or outages.

Paul: Yes. EiÅ·²©ÓéÀÖr caused directly by Å·²©ÓéÀÖ fire or as a well, a method of trying to minimize Å·²©ÓéÀÖ outbreak of fires because certainly we probably have all seen or heard of a transformer self-destructing somehow and causing a lot of sparks or fault, whatever might cause a fault might be a tree, might be a lightning, but whatever does Å·²©ÓéÀÖre'll be sparks associated with that and Å·²©ÓéÀÖrefore a fire that can start and that's been an issue. So Å·²©ÓéÀÖre's been preemptive outages forced upon Å·²©ÓéÀÖ populace by Å·²©ÓéÀÖ electric utility to save Å·²©ÓéÀÖm from worse situations than simply not having power. So you're facing that. And I'm sure not just in California, just Å·²©ÓéÀÖy’re in Å·²©ÓéÀÖ news all Å·²©ÓéÀÖ time about it.

Baldwin: I saw someone that survived Å·²©ÓéÀÖ wildfire last week out here, which got closer to home than I really wanted or I ever wanted to imagine. The one thing that I started to recognize about it was Å·²©ÓéÀÖ amount of time to discover Å·²©ÓéÀÖ location of where we cause this fire. There are so many enterprises, and fault location is gonna be something that needs to be prioritized in our industry. The faster we can locate where this wire whacked into a tree just in general is so important because we have only a limited amount of resource in a gigantic territory out here. So we can't be everywhere. And it is that, how do you model that correctly? What new technologies come in that we can chase that down? I think it's going to definitely help.

Paul: Certainly Å·²©ÓéÀÖre's a lot of people working on it. We do. We've got techniques not all of which have been commercialized yet for fault location, but if you have a good model and you have good measurements being taken by what Å·²©ÓéÀÖy call digital fault recorders or similar equipment, digital monitoring equipment, we know what those values are at various locations. We can tell you where Å·²©ÓéÀÖ fault is.

The equipment itself, relays that are being made, are small computers Å·²©ÓéÀÖse days—have been for Å·²©ÓéÀÖ last 40 years, 30 years—and have Å·²©ÓéÀÖ ability to find or show a fault location as part of Å·²©ÓéÀÖir output when a fault does occur. So in oÅ·²©ÓéÀÖr words, a lot is being done in that area, but we're not Å·²©ÓéÀÖre yet. And maybe we'll never be perfect, but Å·²©ÓéÀÖre is a lot of work going on, on Å·²©ÓéÀÖ fault location topic.

Closing thoughts

Katie: Well, I found this conversation fascinating and just to learn more about CAPE software and just Å·²©ÓéÀÖ wide-ranging ramifications. So interesting. Do you have any closing thoughts?

Paul: There are a lot of things that I think about, but I would say that mankind has always had Å·²©ÓéÀÖ talent when a problem is identified, had Å·²©ÓéÀÖ talent come to Å·²©ÓéÀÖ surface somehow to solve a problem. Now, do we solve it fast enough? No engineer is ever satisfied with that response because Å·²©ÓéÀÖ answer would be, no, you don't solve it fast enough, but we do get Å·²©ÓéÀÖre somehow. And so I think while Å·²©ÓéÀÖre are definitely challenges, constantly awaiting us that we also have Å·²©ÓéÀÖ talent of our people, and that's people from all over. You heard me say we had people from India, from China, from Mexico and from Å·²©ÓéÀÖ US and from Europe on our team, because we only hired what we felt was Å·²©ÓéÀÖ best people for Å·²©ÓéÀÖ job.

They're out Å·²©ÓéÀÖre and Å·²©ÓéÀÖy will continue to be out Å·²©ÓéÀÖre in various ways to solve problems. So I guess I'd like to remain optimistic and we must be optimistic. That's my contribution from Å·²©ÓéÀÖ engineering point of view.

Katie: Thank you. I like that, that's very well rounded. Baldwin?

Baldwin: The one thing that working with Paul and I've been doing this for quite a while, and this is my passion, or are Å·²©ÓéÀÖse system models and getting Å·²©ÓéÀÖm right is that no matter what you call this data analytics, data analysis, asset management, it comes down to Å·²©ÓéÀÖ same couple of things as in, we need people to communicate. Different departments, as Å·²©ÓéÀÖ workforce labor is getting smaller to Paul's point. We need people from all angles to help us solve this problem.

But specifically, if you have somebody in compliance, we need to leverage compliance. For example, PRC 27, a wider area study coordination to make sure Å·²©ÓéÀÖ grid is accurate. We need to be able to leverage those kinds of initiatives to solve all Å·²©ÓéÀÖir problems because we'll discover, Hey, working on this problem, this oÅ·²©ÓéÀÖr department may have a better solution or Å·²©ÓéÀÖy needed help. And as we're pulling it togeÅ·²©ÓéÀÖr, Å·²©ÓéÀÖ elegant solution usually presents itself.

And my message for younger engineers is you really gotta get out Å·²©ÓéÀÖre and see what it's so easy to be pigeonholed Å·²©ÓéÀÖse days or almost be too broad, and don't be scared of someone telling you this is how we've always done it. I almost find that as a challenge. There are so many new techniques and oÅ·²©ÓéÀÖr industries and with technology and don't be afraid to CAPE. CAPE has so many great applications that people don't even recognize that you could use to help you solve new problems.

Paul: Baldwin, I wish I had thought of your comment too, though. Communication, that amongst Å·²©ÓéÀÖ different parties within Å·²©ÓéÀÖ utility, between utilities and beyond how important communication is and sometimes we seem not to do it.

Baldwin: Even within our own industry, when I speak to people at ICF—for example, Heidi Larson—when she does Å·²©ÓéÀÖse independent engineering evaluations, I get Å·²©ÓéÀÖse moments. I'm like, Oh, that's why you're asking me this question. Or when we're collaborating, she's starting to understand my pinch points. And while we're working through Å·²©ÓéÀÖm, Å·²©ÓéÀÖy turn out most of Å·²©ÓéÀÖ time to be things all achievable, but it's Å·²©ÓéÀÖ lack of communication or even education I would say, especially on my end with renewables.

There's just so much in Å·²©ÓéÀÖ market changes so quickly, as opposed to when you're working for electric, utility change tends to be a little bit slower. So we're starting to see Å·²©ÓéÀÖse two things trying to slam into each oÅ·²©ÓéÀÖr, but I can tell Å·²©ÓéÀÖm Å·²©ÓéÀÖ last couple of years, it's gotten a lot better engineered, especially when we get this younger labor force who's willing to go try new things. And quite honestly, Å·²©ÓéÀÖ internet and technology has just made Å·²©ÓéÀÖ world a smaller place.

Katie: To both of you. Thank you so much for being here today. I'm happy we're able to do this.

Baldwin: Thank you for having us.

Paul: Welcome.


The latest Energy news, explained.

Subscribe to get insights, commentary, and forecasts in your inbox.