WEBVTT 00:00.000 --> 00:12.000 Okay, let's get started, my name is Chris Sheer, I'm the resource head of 00:12.000 --> 00:17.400 resource strategy at the future way, and I'm also the chair for the 00:17.400 --> 00:23.400 Auras working group at the Lenders Foundation Energy. 00:23.400 --> 00:29.000 Today, my topic on my talk is exploring the Auras Open Renewable Energy 00:29.000 --> 00:34.600 Systems. Last year, I was here to present it, and this year, just to present 00:34.600 --> 00:42.000 some latest updates for the Auras Working Group. 00:42.000 --> 00:49.000 I live in Static Valley, which is the San Francisco Bay Area in California. 00:49.000 --> 00:54.000 There is a place called Masel Landing in Montgomery, California, which is about 00:54.000 --> 01:04.000 1.5 hours drive south of my home. Just a couple of weeks ago, there was a big fire, 01:04.000 --> 01:11.000 and that first was a battery energy storage facility. 01:11.000 --> 01:19.000 And that facility was used by PGIE Pacific Gas Electric, which is our home's 01:19.000 --> 01:27.000 power utility service company. This company was famous because a few years ago, 01:27.000 --> 01:32.000 California, not in California, there were fires. 01:32.000 --> 01:40.000 A number of huge fires from the forest. And in the forest, a week ago, there are 01:40.000 --> 01:49.000 like a heavy metal ingredients, stuff that is around the residential area, because of this 01:49.000 --> 01:56.000 fire. And that fire is a particular from the battery facility, with a long, long batteries. 01:56.000 --> 02:05.000 So we see there is a centralized challenge, a power supply, basically with the power 02:05.000 --> 02:15.000 systems. And these systems are, what happened if we do this in the decentralized 02:15.000 --> 02:21.000 situation, the decentralized entity, right? And PGIE realized there is a challenge there. 02:21.000 --> 02:26.000 So they have started to implement some of the solutions, like the distributed solutions 02:26.000 --> 02:32.000 that they are working with, Tesla Powerwall. So several of my colleagues have installed 02:32.000 --> 02:38.000 Tesla Powerwall in their homes, and they participate in the PGIE program. 02:38.000 --> 02:45.000 It's more like a virtual program where I was told that before there is a weather event 02:45.000 --> 02:50.000 or there is huge demand, the PGIE will fill out their home batteries for them. 02:50.000 --> 02:55.000 And the next day, if there is event, then they will just drain out the battery, so that they 02:55.000 --> 03:01.000 can supply the local communities. So people who can, you know, use all the 03:01.000 --> 03:08.000 Tesla Powerwall, but that's a proper solution. It's very hard. And if you want to 03:08.000 --> 03:12.000 expand the batteries, it's going to be very costly. And you cannot think of it, you cannot 03:12.000 --> 03:17.000 change it. You have to hire contractors, go your home, that's very expensive, too 03:17.000 --> 03:23.000 expanded, or too anything else with it. So there is alternative, this is the open solutions, 03:23.000 --> 03:30.000 and that's what OS comes into play. So what is OS? So the OS is short for open, you 03:30.000 --> 03:35.000 knowable energy systems. It is not a product, it's not a software, it's not a hard work, 03:35.000 --> 03:43.000 but it is a specification. It is a framework that allows people, vendors to develop their 03:43.000 --> 03:51.000 own open, disaggregated energy solutions. So the key value position is that, as I said, 03:51.000 --> 03:55.000 you know, this is an open source solution. It's the open solution. It's a different from 03:56.000 --> 04:03.000 black box, it's open. And our aim is to make it a simple installation and integration. 04:03.000 --> 04:10.000 And it's a modular design and then linearly scalable. This is the overall architecture 04:10.000 --> 04:17.000 of the OS system. Now we have power productions from like a smart solar panels and wind turbines, 04:18.000 --> 04:26.000 and there are smart batteries. And we have all the, this process, we have added a module 04:26.000 --> 04:34.000 called a Wi-Fi sensor switch, where the home house load. For example, you're 04:34.000 --> 04:41.000 macrower oven, your coffee maker, you can just plug it into this Wi-Fi switch sensor, 04:41.000 --> 04:48.000 and then you will inform the controller. If there's a load, you will give the signal to the controller 04:48.000 --> 04:54.000 and the controller can inform the batteries to release to your local home grid instead of getting 04:54.000 --> 05:02.000 power from the public grid. So, so this, I mentioned, this is a standardization effort, 05:02.000 --> 05:08.000 it's our standardization. So the purpose of this standardization is to allow standardized 05:08.000 --> 05:14.000 uniform architecture. Allow, so we have borrowed this concept from the data center in 05:14.000 --> 05:21.000 the cloud data center, where you have all the cabinets. And you can have standard specifications. 05:21.000 --> 05:30.000 You can plug in the servers, you can plug in the storage devices. So, so that you can, 05:30.000 --> 05:35.000 you can, you can standardize on this one factor so that you can enable 05:36.000 --> 05:42.000 manufacturer to, to build a standard equipment. And easier for the, either for the producers 05:42.000 --> 05:48.000 or for the managers and it also easier for the consumers, so you play the deploy and, and, 05:48.000 --> 05:53.000 and a job and deploy, plug and play solution. So, that's where we borrowed that. 05:53.000 --> 05:59.000 So, that's what we're planning to do in the next year. And hopefully, if you are, people are interested, 05:59.000 --> 06:07.080 you can join us. We connect to my LinkedIn and also the 06:07.080 --> 06:12.360 Auras GitHub so that you can help contribute. And since we have a 10 minutes talk 06:12.360 --> 06:17.800 is pretty short as the last minute. And so that is all for my presentation. 06:17.800 --> 06:25.240 Yes, sure, go ahead. Anybody have any questions about the yes, go ahead. 06:25.480 --> 06:33.240 So I was wondering, so it's an organization, the framework, which is 06:33.240 --> 06:38.120 you said something about physical dimensions, but I guess also about communication. 06:38.840 --> 06:44.280 Yes, yes, they gave to the internet. So you want to have this open and then 06:45.000 --> 06:50.680 the different companies would implement it then by themselves. So you 06:51.320 --> 06:55.800 use this framework and then all the whatever inverted companies and 06:55.800 --> 07:00.760 concrete companies, which integrated or how do you plan to 07:00.760 --> 07:03.640 to spread this and how it should be used with this. 07:03.640 --> 07:05.960 Yes, a great question. The question is, how would you 07:09.640 --> 07:13.320 develop the standard so companies can adopt? And this is where 07:14.200 --> 07:20.440 following the very playbook from the OCP, the open compute platform. 07:21.000 --> 07:27.880 Or open 19, there's another standard for data center equipment. 07:28.680 --> 07:34.280 There's a hardware equipment specification. That's like a Facebook and a Google 07:34.280 --> 07:39.880 Microsoft. They're all kind of adopting that. So we're trying to borrow that concept into 07:39.880 --> 07:45.480 this renewable energy system. So it makes it easier for manufacturers. For 07:45.480 --> 07:49.320 you know, the big cloud service providers, they use this because they have massive 07:50.200 --> 07:54.040 departments. And if we have the same nature of the massive department in our 07:54.040 --> 07:57.720 communities, we need that kind of a concept as well to help 07:58.600 --> 08:00.760 lower the cost and ease it with deploy. 08:06.760 --> 08:08.760 One more. Yes. 08:09.000 --> 08:20.600 Now, a cabinet was more like a photo. It's an outdoor. So it needs to be like a weatherproof, 08:21.320 --> 08:28.040 fireproof, you know, windproof, all the kind of thing. Yes. Because you put it 08:28.040 --> 08:32.680 outside. So it needs to be able to do it.