Why don't you please make me a picture of the audience.
Come in fast, sophisticated, required.
Press on a talk about IoT net building.
Something.
Yeah, exactly.
Thank you.
Perfect introduction.
I am Pierre, I'm going with open modes.
Last year we explained a bit about engaging residents in a residential area to try to solve congestion problems.
I don't know if you were there.
I'd like to follow up on that and explain what we did last year also linking to a project we're doing in the Hague with the state in which is another network operator.
But first a bit about open modes.
This should work.
I don't think you have to tell us here.
But we, in general, are building fully open source IoT platform.
Which obviously means you need to connect to real systems in the real world.
So I don't want to say all about it.
And as we transfer everything we connect to is still there.
No, the microphone.
Oh, I told you.
Oh, this.
We translated it on convert.
Everything we connect to what we call assets of different asset types.
We have a model and that means you can add some intelligence to it.
And either it can be, or I'll come to that in a second how you do it.
And I'll do that.
For front end users, we very much focus on them to be able to create specific applications.
We spend a lot of effort not just on logic but also on on on the front end apps.
Either for end user or consumers.
We have a.
Yeah, should I say that here we have 100% open source.
But what I mean with it is we don't have different repositories.
We just have one and it's used by anybody.
So there's nothing.
We do also for professional users, which is somewhere hidden in a closed.
And the other thing to say.
If we say that we intuitive, I think you the judge of that.
But it's.
It's we want to be completely transparent about it.
There's a company behind it.
So open mode is also company and that's the benefit that for professional users, which are mostly
manufacturers of system integrators.
We also offer the service to help them build their application on top of open mode.
Yeah, this in just in brief.
So tell a bit about the platform.
I think this is your obvious part.
So obviously to the links to the real world.
We have APIs, but we also have different protocol agents raising from.
We have an empty broker and a client.
But we also can connect with HTTP or recently over lower one through
Chub Stack or things stack.
And within it, we have some ways to automate simple things which are completely.
You why when then of flow rules, which you can also connect your own services nowadays.
And we have published one services, which is a more advanced forecasting services.
And some services are building like a map service and a notification service.
And on the front end, we have a web components and the standard of the shelf.
UIs are manager UIs, basically that's the access to this whole system.
Plus we have a dashboard builder to build applications for mostly professional users.
And for consumers, we have a web components where we build dedicated web apps.
And we have both an iOS and Android console too.
Yeah, do that quickly.
If you're a font and developer, of course.
Well, one more item relevant to say is that you can run open mode on premise locally.
And then we have a tunneling option.
And so that's for typically system integrators.
We say I need remote access to an installation.
And that can turn on to a local installation and get access to local systems.
Recap on the last year or the share the last year.
We call it our grid.
And it's a way to optimize, look at energy optimization.
We extended it just not only from Amsterdam, but also doing it in our name,
which is not a Dutch city together with all the other.
One of the three bigger DSOs in the Netherlands.
And what we're doing is trying to visualize it in this picture.
So this is the app for residents.
And the right screenshot is when there's nothing wrong with the grid.
There's no overcapacity or there's no grid congestion problems.
And users would have a real time inside in a power consumption second inside.
And the fact that the background here is green means there's nothing wrong.
No problems with the grid.
And the same is representate here in this graph.
But you also see some red backgrounds.
And the red backgrounds is actually when we have had or expect congestion problems.
And the way we do it is we forecast as we have a link to all these individual users in a district.
And they have a tunnel in their smart meter.
We can actually aggravate the data and also do forecasting.
So we can forecast together with the network operator, whether there will be grid congestion issues or not.
And if those happen, people get a push notification 50 minutes ahead.
So just a choice to say 50 minutes is still allowed you to act.
And last year we shared that then they get this view on the left this one.
And they requested to join a challenge.
And it's a challenge.
We'll meaning if they join, that's the button here.
They go to the middle screen.
And for an hour they get a power target, personal power target.
And if they meet the target, they can earn 10 points maximum.
And the points have an exchange rate.
So they actually get some payment at the end of the year to give you an indication.
It ranges from 33 cents to 120 euro on a typically.
So what are results part of it we shared last year?
So until now it was or last year we shared purely manual impact of users or manual actions by users.
We now have in two districts.
165 participants about of course, which means active users.
So people who press buttons and act on request.
But we've also and that we did last year is we added automation.
So we took the step to let's automate this because obviously you don't keep on manually pressing buttons.
And the only reason we did it initially is because we want to engage as many people as possible.
There are a lot of people in districts we don't even know how to automate anything.
So we want to include everybody.
And that's how we got to the 165 participants.
And now gradually we're adding automation and we do it in three ways.
Users can link their own home automation system.
So either home assistance or open app.
Or they can connect a vehicle, the charging session.
And they can connect batteries.
And this is the battery.
So this is coming through a subsidy of all the only in this case in these two districts.
They give a subsidies so people can buy this battery.
Plug and play battery at a lower price than normal.
And when there's congestion problem, the battery will start discharging to help out.
This is the integration with home assistance and open app.
The clear difference is here is that you pick up digitally the signal that there is a challenge.
But you decide yourself, of course, how you fulfill the target.
The strategy on what to optimize what to stop or what to start.
That's up to you and to you to program that in either home assistance or in open app.
That's a bit different with when you connect your vehicle, when you connect your vehicle,
when we detect that you're actually charging at that moment to be paused the charging.
So we paused for that period and afterwards we started charging again.
And of course, you can opt out.
So we don't want it in a specific instance.
No, no, no, no, no, no, no. I need a charge.
So we've resolved.
Last year we shared the fact that we got purely on manual interventions.
So people only manually changing things.
We could prove that we were able to reduce the peaks with about eight kilo watt,
which doesn't sound much.
But the fact that it's purely manual and amount of participants was already quite impressive.
So you know, let's continue this because this manually continuously people pressing buttons.
The only thing we we saw here.
But with the automation and it's a bit early to really quantify it now.
We have reached around 30 kilowatt reduction.
But there's something else happening is that we see because we of course been monitoring it.
That people who were charging have shifted their charging sessions structurally outside these speakers.
So they're moving to daytime or at midnight and actually seeing peaks at midnight.
A lot of people are charging at two to midnight, which wasn't the case here we go.
Which brings me to what the title set is to another project which builds on what we've done.
And this is called a smart beach or a slim strum net in Dutch, which is in the Hague and this project was stayed in.
So there are other diesel in the mountains.
And the difference is here is that actually two difference here.
First of all, it's a district with beach civilians.
So we call them houses but actually not.
Beach civilians, the border or the Saudi harbour, police, government building.
But you also have shared assets.
So not these panels because that's not a lot.
But there's a 90 kilowatt peak solar farm in the harbour.
And there is a battery shared battery with the cooperation.
But the corporate cooperation only has also has its own electricity grid.
So they collectively have a contract with the energy provider as well.
So what does it mean?
It's similar as before.
This is really an area where the squid and jussian problems.
So what we've done here is for those who know the gopax is the Dutch congestion market.
So the Hague and the cooperation have signed a contract with stayed in with the dynamic capacity base contract.
And we've connected it over gopax so we can handle capacity request.
And we make the translation sometimes to challenges.
So the average user has no clue what you're talking about.
If you talk about gopax or congestion or dynamic capacity base contracts.
So we make the translation to the similar kind of challenges we showed before.
And on top of it, as there's a collective energy contract.
What we do is, and we do it for again an open source service.
So we added the forecasting service to open mode.
And that forecasting service we can use to also forecast the apex spot prices.
And why do we need it?
Because where that we can also schedule the flexible assets in the district.
And where that we can give the forecast to the energy provider.
And that the consequence of that is that we can all the Hague or the energy cooperative can sign an energy contract without any imbalance costs.
So that's obviously very attractive.
Without any not saying any very limited balance costs.
So how does that look?
If I look at this picture, the blue lines and the top and the bottom are actually the capacity limits.
And on the top side you see that it drops somewhere and the right side, which is between seven and eight you can't see that.
This is an experiment, of course.
It drops it to 10 kilowatts.
But also the feeding was reduced to 10.
And you see that the green line, which is the net power consumption on the Slimstown net.
It's actually staying within this small bandwidth.
What does it do it by controlling the flex to the orange line?
It's the orange line is the flexibility.
The biggest part of that is that battery.
It's not the only part that's also charges.
And the battery starts, of course, discharging to mostly discharging to stay within the blue lines.
And the other thing you see is on the left here, a small period where this charges.
And why is that? Because that moment the prices are high.
And it still has capacity left.
So it still has capacity left for doing this.
And it knows. So we say, oh, I'll charge here a bit because I kind of earn a bit extra here.
So that's a practical case how it works.
And the obvious question is then what's next?
So I don't have to explain this picture. I'm sure you've seen this multiple times today.
Yes? So we always look at this picture.
But we forgot about this picture.
And the only thing would change instead of time.
It's a January and summer and winter.
And there's another problem we have with the energy balance.
So what we're now looking into is look at a longer term storage of electricity.
And then in a smart way integrated as well.
And it's not as easy as just summer winter because also then the evening and day peak.
You have to combine the two.
So that's what we're doing and we're doing it.
We're looking into a heat storage.
So ways to convert electricity into heat.
And basically, let's say, stored in concrete, not concrete.
And then you can have a real long term energy storage.
Probably at a quite cost-effective way.
Though that's in with the 10 minutes lift on 9.
What I wanted to talk about is short.
We had a booth here and the same building.
So if you want to know more, you're welcome anyhow to come and visit us and we can explain more.
But there's some time for questions, I think.
Yes? Any questions?
As an understanding, you're most of the software company.
And in the last slide, you said, like, we're looking into heat storage.
Are you then looking into the setting of the hardware for that?
Or are you just lost about how to predict the management research?
Yeah, yeah.
So your questions are we now also use more software companies?
Yes.
As we're also looking into hardware.
If you talk about an energy management system, first of all, it's both.
Not one or the others.
If you want to solve the whole puzzle, you need both.
But our users are system integrators or manufacturers equipment manufacturers.
So in this case, we're working with a system integrator together with the cooperative.
And they, of course, are analyzing what are the best solutions to use here.
But as from the software side, of course, we need to know,
okay, what's the strategy to optimize that?
So that's where we are involved.
We don't do our work.
Yeah.
So if you look at the repository, we have a forecasting service.
And the forecasting service is a generic forecasting model.
So we started doing just profit, which some of you probably know is a way of forecasting.
It seems to be already quite accurate.
With the big standing that service to also add gradient-based modeling.
For example, but that's a generic service, which you can use for any application and open mode.
And for example, we configure it.
Let's do the apex forecasting.
And just define the regress as we need and see whether it's forecast well.
Which you can also use it to say, well, I want to forecast the package,
and see it's probably related to a amount of rain and temperature.
And day of the week.
Yep.
Yeah. So your question.
So what's the storage you talked about the storage?
What is it about?
We don't do hardware as to your question.
It's the government they tendering now in an off-the-standard to say,
there are solutions in the market to do this with sand or concrete or basalt or sold or.
So it's going to be tendered to come first with an off-the-standard to see what the final solution would be.
But the data feasibility study that they think it's feasible.
So we'll wait and see.
I think there was one more question.
And no, we do it on on two levels if that's the question.
So on the let's say the cooperative level or the residential area,
we look at an optimization because it's the shared conflict,
for example, the energy contract that's a collective one.
But those sort of congestion is a collective under the,
in this case, the low voltage transformer.
But what we do internally is also translate to individual assets or,
or let's call residents.
And they would trigger on the price.
So they would trigger on individual price.
But they get an additional incentive, for example,
if it's beneficial for the whole grid.
And we have a way of translating it.
So let's say we have an EMS on the cooperation level,
but we have an EMS on individual level as well.
Yes. So also your question was,
can an individual households decide where they want to join on us or participate
in the central energy optimization?
Yeah.
So the EMS on the,
can you join on not yet?
Yes. So in the,
the app I showed,
it went too quick.
There's opt in and opt out.
So you can decide,
do I want all the made or not?
How do I want to automate and react?
But also from the incentive model you can choose,
or you should be able to choose,
but I know the grid problem,
but I prefer to optimize on my individual solar.
Yeah, yeah, behind the means of both.
Yes.
It was one first there.
Yeah.
Yep.
Yeah. So your questions,
we say that we,
there was exchange rate with the points,
so people actually get money.
No.
Sorry for that.
Yeah.
So how it's financially done is that,
of course,
according to the law that we don't have dynamic tariffs,
so the grid,
the network operator count,
directly incentivize because we don't have the moles for that,
but the way we do it now,
you have a budget per district,
and the budget is paid by the network operator,
and we basically divided by the number of earned points.
And that's exchange rate,
and times the number of points,
and that's what you get paid out,
and it's paid out by the project.
So there's a project team,
which consists of the government,
the city itself,
and still have more on them,
plus the other partners,
and they pay out to the residents.
Protects.
As a consumer,
you get money,
how does it improve?
Yeah.
Yeah, it's a good question.
So what's the impact on personal income,
or taxing,
or this sounds like poor answer I don't know,
so I guess it's income,
so you would have to register it.
But it are not large amounts,
yeah, a good fair question.
It needs a structural solution,
of course,
this is an experiment to see where it can work on it.
So it's not a complete answer or an question.
You add a question.
Yeah, for the communications,
so between your service sites,
data and the community level data,
and your local assets,
and your service standards,
that you're following on their own.
Yeah,
we remember this last year,
we were behind the talk about S2 standard,
and I forgot a guy's name,
but he's mentioned,
yes,
we introducing the 12 standard,
and we follow a standard if there is one.
We know the finest standard,
beginning involved in asked about,
what would be a good standard,
but we know not the ones to set the standard,
and they're not many,
that's actually a problem,
so there's a lot of initiatives,
of course, to try and standardize this.
Yeah,
and all kinds of reasons,
of course, by companies don't want the standard,
some of them.
Then there was one more, I thought,
thank you.
Yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah
yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah, yeah