WEBVTT 00:00.000 --> 00:12.080 Yeah, hey, good afternoon. I'm Pierre, Pierre Kill, Opremot. I wanted to give 00:12.080 --> 00:16.440 actually a follow-up of the talk which was held by Eric last year here on a pilot 00:16.440 --> 00:20.600 we're doing in the sport work. He's some docklands in Amsterdam about grid congestion 00:20.600 --> 00:26.040 and engaging households. And we think it works, but I'll share about a bit more about 00:26.040 --> 00:31.040 the minute. A bit of background to Opremot, we had an up-cent complete open source 00:31.040 --> 00:36.040 in general IoT platform, basically targeting equipment manufacturers and 00:36.040 --> 00:41.040 system integrators as well as as governments and NGOs. We were using our software. 00:41.040 --> 00:46.040 The picture would almost say for you that's probably obvious. So we have pieces like 00:46.040 --> 00:51.040 OK, the protocols, the integrations, the layers where you can unify your objects and add 00:51.040 --> 00:57.040 all kinds of logic to it. And towards the application side, we have a library of web 00:57.040 --> 01:02.040 components which allows a front end developers to quickly make the spoke apps for 01:02.040 --> 01:08.040 end users or integrators. And as a company, we support it to integrators and 01:08.040 --> 01:15.040 and manufacturers with services. To give you a bit of idea of some of the 01:15.040 --> 01:20.040 custom-zone users of Opremot, just quickly going through the first one is the city of 01:20.040 --> 01:26.040 or actually not an empty city council, which uses our software for optimizing the energy 01:26.040 --> 01:33.040 production and consumption on their sites, including V2G charging, for 01:33.040 --> 01:38.040 co-workers of Dutch entity use open mode for a control of smart lighting in a public 01:38.040 --> 01:45.040 space. K2 systems is a German equipment manufacturer who does mounting materials for 01:45.040 --> 01:52.040 solar panels and in snow-rich areas they add weight sensors to it to measure the snow loads. 01:52.040 --> 01:58.040 And the reason for that is the risk of panel breaking or micro cracks and therefore 01:58.040 --> 02:05.040 the lifetime or the production rates are decreasing. The fourth one is military 02:05.040 --> 02:10.040 police in the Netherlands use it for forecasting and measuring passenger flows on the 02:10.040 --> 02:16.040 airports and the reason of it is to predict queues on the checkpoints so that they can 02:16.040 --> 02:20.040 flexibly move people around to prevent queues basically in the end. 02:20.040 --> 02:27.040 On the other hand, I'm sure you heard the length before. To Dutch dzo, I'm going to 02:27.040 --> 02:32.040 talk about it in a minute. We're using it for congestion management there and 02:32.040 --> 02:37.040 digitize a Finnish company who does power line monitoring in icy regions 02:37.040 --> 02:43.040 Finland and the risk of the power lines breaking so they actively monitoring to prevent 02:43.040 --> 02:50.040 the power lines to be broken. This really is short. We have a booth here so I 02:50.040 --> 02:57.040 really want to go into the topic. You can in the AWS building basically a rough overview 02:57.040 --> 03:01.040 on the left side of the real world. We have all kind of APIs. We have a broker in our 03:02.040 --> 03:08.040 platform so you can connect over MQTT but you can also run open mode on premise. 03:08.040 --> 03:11.040 It's the same code base which you then run on the local instance. 03:11.040 --> 03:16.040 Create your local network and as you can connect these gateways, multiple gateways 03:16.040 --> 03:22.040 to a sent for instance of open modes. In open mode itself, we have already mentioned 03:22.040 --> 03:27.040 that protocol integrations. We run a several kind of rules. 03:27.040 --> 03:34.040 The solution is so groovy scripting when then flow. That's the visual modeling of rules. 03:34.040 --> 03:39.040 And we have some built-in services like a map service, notification service, which 03:39.040 --> 03:43.040 can also easily add your own specific service of course by using the APIs we have. 03:43.040 --> 03:50.040 And towards the front ends, we have a standard manager of what we call manager 03:50.040 --> 03:54.040 you live for the let's say the expert user to configure all of this. 03:54.040 --> 03:58.040 And do you also have a dashboard builder for that let's say professional users to 03:58.040 --> 04:04.040 make dashboards for their users again. Or we have a library of web components which 04:04.040 --> 04:09.040 allow front end developers to build specific apps for their end users. 04:09.040 --> 04:14.040 Now going into the project, we talked about it last year. We started and the project 04:14.040 --> 04:19.040 I think it was a couple of months in running. Now you're running them over a year 04:19.040 --> 04:23.040 and it was about engaging households and to prove that actually you could 04:23.040 --> 04:27.040 incentivize residents and in this case it's a district and I'm still 04:27.040 --> 04:32.040 in with 500 households. And the problem, the typical problem in the Netherlands 04:32.040 --> 04:38.040 is they are the transformers which are getting too low in capacity. 04:38.040 --> 04:42.040 And we want to prove that we can motivate people to change their power 04:42.040 --> 04:46.040 consumption in peak congestion moments. 04:46.040 --> 04:51.040 So basically this is the story the way we explain it to residents in the neighborhood 04:51.040 --> 04:55.040 say hey we want to introduce a solution which first of all helps you 04:55.040 --> 04:59.040 optimizing your individual users to align your own production with your own 04:59.040 --> 05:04.040 consumption that's good for everybody especially for your water in the 05:04.040 --> 05:09.040 ends. So the low is bill and secondly say well if you can't use it yourself 05:09.040 --> 05:14.040 use it with your net or give it to your neighbor that's the basic. 05:14.040 --> 05:18.040 And by doing it the first reason for that would be what we introduced 05:18.040 --> 05:22.040 because you then you would help the grid operate because we limit the 05:22.040 --> 05:25.040 investment in the future capacity. 05:25.040 --> 05:30.040 We introduced an app for that that was the one I'm showed here. 05:30.040 --> 05:35.040 I'm not going to detail or show that in a minute but I wanted to show what 05:35.040 --> 05:39.040 the results are and what we're seeing here is we have 71 active 05:40.040 --> 05:46.040 participants last year in 2024 we had 48 challenges people earned 35 to 146 05:46.040 --> 05:52.040 euro max so not a lot of money but it's a nice financial incentive 05:52.040 --> 05:57.040 and this is a graph showing for a typical day what actually happened because 05:57.040 --> 06:01.040 the big questions of course what did we actually reach and what we did 06:01.040 --> 06:05.040 measure is that with manual interventions people were actually 06:05.040 --> 06:09.040 we were able to see that on average we had an half kilo watt 06:09.040 --> 06:14.040 hour reduction just by these people just by on average 15 people 06:14.040 --> 06:19.040 joining just by manual interventions so only the manual side so 06:19.040 --> 06:24.040 that obviously says well that was quite promising so we said hey the 06:24.040 --> 06:30.040 obvious next step is start adding automation and scalable way so that's 06:30.040 --> 06:33.040 what we're looking at now in the next step but also add things like 06:33.040 --> 06:38.040 dynamic terrors so if you can say hey you make use of my dynamic terrors 06:38.040 --> 06:42.040 then obviously we can enhance the benefit for for users and as of 06:42.040 --> 06:46.040 January 1st energy caring for you to be if you okay I'll leave the 06:46.040 --> 06:53.040 question to the end of that then I'm in that as January the peer 06:53.040 --> 06:58.040 to peer is allowed in announced now we also working in energy provider 06:58.040 --> 07:02.040 to see better we can actually arrange it for people and that would 07:02.040 --> 07:06.040 strengthen and and seeing whether that could could go inside with the 07:06.040 --> 07:11.040 avoiding congestion so the next step two things which we doing first of all 07:11.040 --> 07:17.040 be looking at automation and adding that to to the app we currently have 07:17.040 --> 07:23.040 of course we want to increase the number of participants with more 07:23.040 --> 07:27.040 communication but also to double the incentive people are getting and in 07:27.040 --> 07:31.040 terms of automation you just give you some feeling what we think could be 07:31.040 --> 07:35.040 more realistic it's not just added these numbers that's not what I'm trying to do 07:35.040 --> 07:40.040 here but imagine there are 20 about 20 home if you use in that one 07:40.040 --> 07:46.040 district we are 13 public charges there if you could reduce power with five 07:46.040 --> 07:51.040 kilowatts with five cars charging in in a peak moments and that's 25 07:51.040 --> 07:55.040 kilowatts if you assume that heating there's no heating and heat pumps 07:55.040 --> 07:59.040 here but in other districts we now extend into so we're going to extend to 07:59.040 --> 08:04.040 districts if you switch off the heat pump for an hour heat pump for an hour 08:04.040 --> 08:09.040 people probably will notice we're going to talk about it and it's typically 08:09.040 --> 08:14.040 five kilowatts that's also 25 kilowatts and the last one that's what we want 08:14.040 --> 08:19.040 to experiment because it creates a lot of hassle is that our noise let's 08:19.040 --> 08:23.040 put it that people are buying home batteries and trading and doing all 08:23.040 --> 08:27.040 kind of stuff so from the network operator point of view we want to figure out 08:27.040 --> 08:32.040 how can these batteries be actually beneficial for the day so so the 50 times 08:32.040 --> 08:36.040 five hundred robber delivering back in a moment would also be 25 kilowatts just 08:36.040 --> 08:42.040 give you some idea what we might achieve quickly the app because if you haven't 08:42.040 --> 08:46.040 been in your last view so this is what the app does for users the 1563 is your 08:46.040 --> 08:51.040 own consumption real time in seconds even the green indicates there's nothing 08:51.040 --> 08:55.040 wrong with the neighborhoods if there's something wrong obviously you're not 08:55.040 --> 09:00.040 looking at the app but it will tell you that there's something wrong here but the real 09:00.040 --> 09:04.040 thing is that you will receive a push notification 50 minutes ahead of that 09:04.040 --> 09:09.040 inviting you to join the challenge and if you then press the push notification 09:09.040 --> 09:12.040 you'll end up in this page and you're being asked hey do you want to join the 09:12.040 --> 09:17.040 challenge and they said why not and the challenge means you get a personalized 09:17.040 --> 09:25.040 target so in this case I got a 600 watts target and then you go to this few and 09:25.040 --> 09:31.040 there's a clock taking the green circle is actually going around in every six 09:31.040 --> 09:37.040 minutes and it's green because I'm below the 600 watts and in a period of an hour 09:37.040 --> 09:43.040 you can maximum 10 points so where does the automation so we already had this 09:43.040 --> 09:47.040 automation now comes in is here in the tips and actions or the tips and tricks 09:47.040 --> 09:52.040 so wherever you would call it and in this case as we have connected home battery 09:52.040 --> 09:57.040 as an example actually as people have allowed it and they can put in settings 09:57.040 --> 10:01.040 here I agree that you use my home battery in these cases if I join a challenge 10:01.040 --> 10:06.040 in this case it says hey we actually this charging your battery is 660 watts 10:06.040 --> 10:11.040 and you can say we'll stop this charging I don't want it so you can always 10:11.040 --> 10:17.040 overrule the action and you can imagine that we could do the same with 10:17.040 --> 10:26.040 ev charging or your thermostat for example once completed you get feedback on 10:26.040 --> 10:32.040 how many points you earn and of course there's something like trophies as we call 10:32.040 --> 10:38.040 them so you have an overview of the points you've earned and there's an exchange 10:38.040 --> 10:43.040 rate so you can always see how much money you actually earn and that's being 10:43.040 --> 10:48.040 handed out on a yearly basis which we now did for first time so that's the first 10:48.040 --> 10:53.040 automation and the second part we are looking into now we also going to do that 10:53.040 --> 10:58.040 is the let's say looking at a multiple methods to motivate self-consumption 10:58.040 --> 11:03.040 or energy markets or wherever we call it the first one is obviously the grid 11:03.040 --> 11:09.040 congestion we just explained what we are doing that are other aspects in this which 11:09.040 --> 11:14.040 we gradually want to add and see whether we can they can enhance the solution 11:14.040 --> 11:18.040 or how they potentially could conflict and then try to find solution as well 11:18.040 --> 11:22.040 then the first one after grid congestion or the second one is then the dynamic energy 11:22.040 --> 11:32.040 charge the energy sharing in the district we also going to add it to the solution 11:32.040 --> 11:37.040 and the other one is maximized really self-consumption we were talking about 11:37.040 --> 11:41.040 hands and really the optimization in the house so there we're looking 11:41.040 --> 11:46.040 with open hap and home assistant to see hey maybe you can do something in the house 11:46.040 --> 11:50.040 or connect to existing home information systems and the last one is important 11:50.040 --> 11:54.040 to share we doing this now in multiple districts so we do it in Amsterdam we 11:54.040 --> 11:59.040 going to extend to a second district in R&M we starting with one or two districts 11:59.040 --> 12:04.040 and in the Hague we also doing it with the stadium so we're doing the same 12:04.040 --> 12:09.040 and the last I wanted to add here is that we always talking about 24 hours but we have 12:09.040 --> 12:14.040 a bigger problem or bigger maybe a bigger problem and that's the seasonal aspect 12:14.040 --> 12:18.040 so what we also going to do and that's what we're going to do in R&M in the coming years 12:18.040 --> 12:25.040 so just to manage expectations here is add a high temperature storage solution 12:25.040 --> 12:34.040 and then basically do seasonal storage here and that's my last slide 12:34.040 --> 12:40.040 so I hope it give you a big overview and hopefully I can give you an update next year again 12:40.040 --> 12:51.040 oh there was one question there 12:51.040 --> 12:55.040 and the first question for those when you're still on the slide 12:55.040 --> 13:01.040 you know what can you get a bit of a reference on how much is it's in the 13:02.040 --> 13:09.040 so the capacity of the transformer is a thousand so eight and a half is one percent less 13:09.040 --> 13:16.040 so that doesn't sound much and the way we did it if that's so that's not much 13:16.040 --> 13:21.040 but it's promising if you look at all the things you could potentially add 13:21.040 --> 13:28.040 to all these houses that join the Israel they require a house memory 13:28.040 --> 13:33.040 no no no no so they initial the numbers here without any automation 13:33.040 --> 13:38.040 so just push notification hey please one is and people actually and we were positive 13:38.040 --> 13:44.040 by the actually run to whatever hey what's like this my 2000 what come from turn on the 13:45.040 --> 13:51.040 capital device or whatever and they actually seem to do that already manually so of course 13:51.040 --> 13:57.040 it does last over time it's a bit I mean novelty does well but maybe you'll still have 13:57.040 --> 14:03.040 some people happy to go on doing when they get a surprise like yeah 14:03.040 --> 14:09.040 the back of the previous talk for the automatic control have you assessed as to the 14:09.040 --> 14:15.040 computer and so which one would you like a yes but they're 14 or 15 now so 14:15.040 --> 14:20.040 and the thing we and favor don't get it wrong we want to have a standout 14:20.040 --> 14:25.040 but the problem is that the not the problem are challenges that we need to scale today 14:25.040 --> 14:30.040 and there isn't so we're looking for a way how can we get 150 people on board 14:30.040 --> 14:34.040 so that's why we didn't do automation because then everybody can join 14:34.040 --> 14:39.040 now this next step of the automation we actually we've looked at e-notes to integrate 14:39.040 --> 14:44.040 the e-notes because they offer all the integrations just being pragmatic and we hope that 14:44.040 --> 14:52.040 S2 comes no yeah because the nobody has not nobody is that way and on the other 14:52.040 --> 14:56.040 hands we're looking at the because they're the early adopters the homicist and open 14:56.040 --> 15:00.040 happy users because in our name for example we have already quite a few homicist 15:00.040 --> 15:09.040 users so they can be the the other early adopters to be the promoters in the in 15:09.040 --> 15:13.040 the neighborhood