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 producer

05:42.000 --> 05:47.000
for the monitors and also easier for the consumers. So you place it, deploy and, and,

05:47.000 --> 05:53.000
drop and deploy, plug and place solution. So that's, we borrowed that. So that's,

05:53.000 --> 05:58.000
what we're planning to do, what's the next year. And hopefully, if people are interested,

05:58.000 --> 06:07.120
people are interested, you can join us, we connect to my LinkedIn and also the

06:07.120 --> 06:12.080
Auras GitHub so that you can help contribute and since we have a 10 minutes

06:12.080 --> 06:17.160
talk it's pretty short at the last minute and so that is all for my

06:17.160 --> 06:25.040
presentation yes sure go ahead anybody have any question about the yes go

06:25.040 --> 06:33.760
ahead so I was wondering so it's anization framework which is you

06:33.760 --> 06:38.120
said something about physical dimensions but I guess also about communication

06:38.120 --> 06:44.320
yes you see a gear to be implemented so you want to have this open and then

06:44.320 --> 06:51.880
the different companies would implement it then by themselves so you if this

06:51.880 --> 06:57.400
framework and then all the whatever inverted companies and concrete companies

06:57.400 --> 07:02.120
which integrated or how you plan to to spread this and how it should

07:02.120 --> 07:10.160
be used if it's a good question the question is how would you develop the

07:10.160 --> 07:16.720
standard so companies can adopt and this is where following the very playbook

07:16.720 --> 07:26.000
from the OCP the open compute platform or open 19 there's another standard for

07:26.000 --> 07:32.520
data center equipment the hardware equipment specification that's like a

07:32.520 --> 07:38.400
Facebook and Google Microsoft they're all kind of adopting that so we're trying

07:38.400 --> 07:43.960
to borrow that concept into this renewable energy system so it makes it easier for

07:44.120 --> 07:48.840
manufacturers for you know the big cloud service providers they use this because

07:48.840 --> 07:53.040
they have massive departments and if we have the same nature of the massive

07:53.040 --> 07:57.680
department in our communities we need that kind of a concept as well to help

07:58.440 --> 08:00.440
lower the cost and easy to deploy

08:14.840 --> 08:21.600
that cabinet was more like for the outdoor so it used to be like weather proof fire

08:21.600 --> 08:28.800
proof you know the proof of the kind of thing yes because you put it outside so

08:28.800 --> 08:32.840
you need to be able