WEBVTT 00:00.000 --> 00:14.320 Hello everybody, I'm Thomas from TNOT and I'm here today to talk about the NG system description 00:14.320 --> 00:22.200 language and all the tools that have been built around it. TNOT is similar to Fraunhofer or 00:22.200 --> 00:34.200 Vito or CNRS. It's a bit smaller, not sure if that means that we're much more agile 00:34.200 --> 00:43.560 because we do have 5,000 people working in a national research organization. Doing a lot of 00:43.560 --> 00:49.120 different things, we have about a thousand people in the ICT unit doing a lot of strategy 00:49.120 --> 01:00.920 things, data stuff, AI stuff and the since two years we have a new team, a new proposition 01:00.920 --> 01:07.240 called the digital transition energy systems where we bring systems engineering knowledge that 01:07.240 --> 01:13.080 we bring to the high tech sector in the Netherlands. A lot to ASML and Philips and near 01:13.080 --> 01:19.840 the field, etc. We try to bring that to the energy domain as we see that the complexity 01:19.840 --> 01:29.120 of software is increasing a lot in the energy domain and systems engineering approach can bring 01:29.120 --> 01:38.920 some clarity. What I started in March at this research is to TNOT and I think the research 01:38.960 --> 01:44.640 institutes like TNOT should focus much more on open source development and they should 01:44.640 --> 01:53.080 collaborate on a European wide scale because we develop things for industry to do it again 01:53.080 --> 01:59.800 and then find implementation partners to actually take it over. A research institute like 01:59.800 --> 02:08.800 TNOT is not allowed to develop to start to compete with other organizations. So we actually 02:08.880 --> 02:15.480 have to build building blocks that everybody can use. I think the energy domain, that's why I'm 02:15.480 --> 02:20.680 very excited also to be here and also to see all the other initiatives that are here. I think 02:20.680 --> 02:29.000 it's sort of a uniquely positioned domain to show that open source solutions can be collaboratively 02:29.000 --> 02:39.000 built between governments, between energy companies coming, between IT companies to actually 02:39.000 --> 02:47.320 show other digital public infrastructures how can be done. I think the limit energy foundation 02:47.320 --> 02:54.600 is a great example of that and I hope that together with people in this room and outside 02:54.680 --> 02:59.080 this room and all the open source initiatives in the energy domain actually show that it makes a lot of 02:59.080 --> 03:05.320 sense for sort of a worldwide global collaborative approach towards a big challenge that we all face. 03:07.240 --> 03:17.240 So today I'll speak mostly about a taxonomy called ESDL and why I think that's important 03:18.200 --> 03:25.720 is that we speak the same language and that the energy systems will be military quality so there will be gas, 03:25.720 --> 03:34.760 hydrogen, warmth and electricity all coming together and people need to make decisions on what to do and how to 03:34.760 --> 03:41.640 weigh sort of should I invest in a heat network, a higher than system or shall we wait for the 03:41.720 --> 03:51.320 grid operated to upgrade the grid. Therefore, a common language could help a lot. To know, 03:51.320 --> 04:02.760 developed the language in 2017, this is one of the projects that I'll skip for now, so we developed 04:02.840 --> 04:12.120 the language in 2017 and there is many standards out there. So I'm not here to push this one standard 04:12.840 --> 04:19.880 I'm simply here because I joined TNO and got excited about this sort of open source 04:21.400 --> 04:28.200 endeavor but if there's a better alternative out there, a better taxonomy that we can all embrace 04:28.280 --> 04:36.440 that would help sort of create one single language, let me know. I know that from previous 04:36.440 --> 04:42.280 discussion at the Linux energy foundation that Toby has from the open energy transition made a case for 04:42.280 --> 04:51.400 a taxonomy built in the open street maps case, we'll speak later about it today I hope and also 04:51.400 --> 04:58.440 at the end of the day there is somebody is usually already in the room presenting GEMS. 05:00.120 --> 05:04.200 It's also a taxonomy to describe the energy grid. Is it built in commodity as well? 05:07.800 --> 05:13.720 Mathematical language. Okay, interesting for all the different commodities as well. 05:14.200 --> 05:24.040 Thanks. So there you have it. Please also visit this last presentation and then help in the discussion 05:24.040 --> 05:33.400 of which one to all adopt basically. So the challenges we saw maybe it's a bit self-explanatory 05:33.400 --> 05:38.280 for people here in this room that there was no interoperability between results of different 05:38.280 --> 05:44.600 models. There was actually a big study in the Netherlands and they said, how does the future look 05:44.600 --> 05:52.600 like and then there were three extremely different outcomes and it was basically impossible for a 05:52.600 --> 05:59.560 government to see like okay but what were the assumptions made, what were the how was the system 05:59.560 --> 06:05.240 described that you used for your modeling. So yeah then you have three completely different 06:05.400 --> 06:16.200 visions. So what to act on as a government can hard. And the last part is the aggregate ability. 06:17.560 --> 06:23.160 So you have business parks, you have municipalities, you have provinces and you have nationwide 06:23.160 --> 06:28.600 maybe even European wide challenges of how to integrate renewables and where to do that best. 06:28.600 --> 06:34.440 So how do you aggregate plans on these different scales? It would mean or it would help a lot 06:34.520 --> 06:42.360 if there would be one single language to describe all these systems based on which you can 06:42.360 --> 06:47.880 do simulations based on which you can aggregate the results to have sort of a common plan and come 06:47.880 --> 06:58.280 go. And the is the on that sort of the is the energy system. It's an XML based solution hierarchical 06:58.360 --> 07:06.440 model. Basically it has five different asset types. So the the ones that you can imagine 07:07.080 --> 07:15.400 and you can create any energy system that you you'd like. You can do many different things 07:15.400 --> 07:22.360 with it. You can store your profile information on it. You can include spatial information. 07:22.440 --> 07:29.800 You can include sort of different plans, even different scenarios, different investment plans 07:29.800 --> 07:36.280 for the future. So there's it's quite a rich model where you can do a lot. 07:38.440 --> 07:44.760 So on high level the thing that makes this better than sort of a tabular approach is I think that 07:44.760 --> 07:50.920 you you can you can create your relationships between all the different parts of your energy system. 07:50.920 --> 07:56.680 And then you're sure that they are connected to one another before you actually do your 07:56.680 --> 08:03.080 simulation that they're connected in the right way. So they're connected in sort of a 08:05.240 --> 08:10.600 hierarchical way as I explained. This is how it's built up. I'm not going to explain that you can 08:10.600 --> 08:17.640 definitely read it online because it's documented quite well. You cannot read this but this is what 08:17.800 --> 08:24.600 it looks like. So they first created this and then they thought like yeah but it's super rich and 08:24.600 --> 08:31.240 it's all encompassing. But then they thought why is it not taking off? Well because people 08:33.240 --> 08:38.440 had to use still by then or had to use sort of coding language to actually browse through 08:38.440 --> 08:45.080 this entire system until they made GIS interface, the map editor. And then also internally 08:45.160 --> 08:53.560 within TNO things started to move because on the map editor you can draw your system and you can sort of 08:55.480 --> 09:02.120 view the different profiles that you have attached to a particular asset that you draw 09:02.920 --> 09:12.440 in your on your map. And then once you do that it simply creates an EIS DL file that you can then 09:12.520 --> 09:23.560 use for your simulation. And that's what they did. So they created a lot of simulations since 09:23.560 --> 09:33.240 this map editor was built in 2019. Many different things, many different areas where it sort of 09:34.520 --> 09:39.080 was applied because all of a sudden all these different research groups started to think like hey 09:39.160 --> 09:46.760 but this actually makes sense a lot for our research as well. So the entire North Sea 09:46.760 --> 09:53.160 a wind park plans were mapped using EIS DL many business parks were mapped so there were many 09:53.160 --> 10:05.480 different projects that actually started to create this EIS DL described systems. And then sort of as 10:05.480 --> 10:11.320 a result there were many models created because of sudden a lot of data became available in this 10:11.320 --> 10:23.160 particular format. So I mean not everything is open source by the way. So for example there 10:23.160 --> 10:29.480 are also proprietary stuff like this wind park profile generator that you can draw up the shape 10:29.480 --> 10:35.960 of a wind park and then it it calculates how the profile or how to power drops if one wind 10:35.960 --> 10:41.800 mill is beyond the other. The urban strategy it's a proprietary solution from synxus. 10:43.880 --> 10:55.880 The one that's not on here is RKGIS from EIS. It's not open source. We do work on a QGIS implementation 10:55.880 --> 11:02.280 at the moment but we are actually also quite excited about the SE collaboration that they start to adapt 11:02.280 --> 11:09.320 EIS DL because that means that from as they have 60% of all municipalities in the Netherlands and 11:09.320 --> 11:16.200 all provinces using their product they could from their proprietary GIS interface actually use all 11:16.200 --> 11:24.120 these open source models to run their simulations and they could use their sort of known interface 11:24.200 --> 11:29.720 to actually simply drop and EIS DL and then send it to one of these open source simulations. 11:31.160 --> 11:37.160 So that's what actually I'm super excited about that opportunity. The challenge is however 11:38.280 --> 11:47.880 to make these simulations good and better than what proprietary offerings at the moment 11:48.680 --> 11:58.280 provide. Because I mean TNO still is a research institute so we don't necessarily excel 11:58.280 --> 12:07.880 in designing user interfaces as you can imagine. So there's all these tools that make it easy 12:07.880 --> 12:17.400 make it easier. Descript with EIS DL to use it to visualize results and many of it is 12:18.040 --> 12:26.520 quite well documented. So it started to sort of to flower the all sort of ecosystem of tools 12:26.520 --> 12:31.800 around this this language in this map and one of the products was the energy data repository 12:32.760 --> 12:42.040 where because people that use EIS DL they wanted data and trust worthy data. So we created 12:42.040 --> 12:49.320 this data repository where assets are actually described in EIS DL like manner. So you could 12:49.320 --> 12:59.320 easily include them in your simulation. One of the initiatives is together with a PBL and 12:59.320 --> 13:05.400 other Dutch large governmental institute to look at the industry, look at all the processes that 13:05.400 --> 13:12.360 the industry actually have and then convert these processes into EIS DL assets so that it becomes 13:12.360 --> 13:21.480 really easy for the industry to say like hey I use this particular heater or this particular bio gas 13:23.000 --> 13:31.240 whatever thing and then also you have your EIS DL analogy of that asset available you could actually 13:31.320 --> 13:39.720 start connecting it in within your company but also with other assets in your energy hub and start 13:39.720 --> 13:49.160 to simulate what the best way forward is to build your energy hub for example. So energy hubs is 13:49.160 --> 13:58.040 is one particular domain where tools have been developed and there's commercial energy advisors 13:59.000 --> 14:07.560 actually targeting these particular domains there was a very large company using EIS DL and SM one of 14:07.560 --> 14:13.480 the open source simulation tools build around it. Unfortunately I heard last week that they 14:14.840 --> 14:23.320 chose for a proprietary alternative I think because they didn't understand sort of the richness 14:23.320 --> 14:30.360 of what EIS DL could provide and they definitely didn't understand I think the opportunity that 14:30.360 --> 14:40.200 if you would together as an industry jointly developed open source solutions you have a much bigger 14:40.200 --> 14:49.000 impact. So that was unfortunate but there is still some I recall it iron in the fire so 14:49.960 --> 14:55.800 there's many different projects in companies that use it and that we hope to develop 14:56.680 --> 15:05.880 a community with where we can also draw some maintenance fees from. How many minutes do I still have? 15:05.880 --> 15:15.560 What's the time? As timid as that? Text. So the people group is another 15:15.560 --> 15:22.280 gives user interface that started to specifically for district heating and then SC now starts to 15:22.280 --> 15:30.600 adapt EIS DL and mostly for business parks as a start but as I said as they provide the interface 15:30.600 --> 15:38.840 for many municipalities and provinces it makes a lot of sense that will also be part of our target area. 15:39.240 --> 15:49.080 So the application remains they're very I think I've mentioned that there's also market modeling 15:50.120 --> 15:55.560 I mean there's it's quite vast right so we are 5,000 people and we have I think over 15:56.280 --> 16:01.880 1500 people working in the energy domain so so they do a lot of advice for the government and then 16:02.040 --> 16:07.960 I said I guess sure let's use EIS DL for it. One of the things that has been 16:07.960 --> 16:15.640 developed a bit more recently is the spatial energy explorer where you can sort of drop your EIS DL systems 16:15.640 --> 16:21.960 and you there's a lot of public data and information out there so one of the things that I hope 16:21.960 --> 16:29.480 this year is also that we start to connect more with grid operators to together give a better insight 16:29.560 --> 16:38.840 to all the entrepreneurs and companies that want to expand but don't know what the exact situation 16:38.840 --> 16:44.680 is and to make it actually very easy to see like hey what's the available capacity what happens 16:44.680 --> 16:52.760 if we combine sort of multiple companies in sort of a group transport agreement as it's called 16:52.760 --> 16:58.360 in Netherlands which is happening quite a lot now because there's a lot of congestion and these tools 16:58.920 --> 17:06.440 could could help with easing and facilitating sort of both be offered from grid operator to 17:06.440 --> 17:12.360 a company as from energy hubs to say like hey how how shall we organize how should we share 17:13.640 --> 17:22.920 the limited capacity on the grid yeah I mean I think this is this is quite 17:23.240 --> 17:33.720 make sense so in energy hubs I briefly mentioned it before so typical questions that you can answer 17:33.720 --> 17:42.840 with with this simulation a software is showing up on the right so is it well the mentioned 17:43.720 --> 17:49.320 are the imbalance so what's the energetic balance so you can also see like what's the impact 17:49.960 --> 17:55.960 either you're hiding in your gas your heat in your your electricity flows and you can you can 17:55.960 --> 18:03.160 answer basically the effects of what would happen if I add a communal battery or if I interfere 18:03.160 --> 18:11.160 in any way in my energy hub this is a good diagram which fun tool if you know it is nice you can 18:11.160 --> 18:17.240 just get a repo in it and it shows you sort of the architecture of the particular repo so I did that 18:17.240 --> 18:23.560 for for SM I was one of the developers said it's almost right you didn't say what was not right 18:26.280 --> 18:32.680 you can check though because this is the repo that the left foot through this is the picture that 18:32.680 --> 18:40.120 he made so this is correct and and this is sort of a bit a bit behind the curtains are not going 18:40.280 --> 18:49.000 in detail but what I think is nice to show is that you have your different sort of carriers 18:49.000 --> 18:55.960 your different solvers that you can use per carrier but then you can also use any other 18:55.960 --> 19:02.920 solvers obviously available and also some solvers that's for example alian there is building 19:02.920 --> 19:09.240 and it's built in such a way that you can easily attach your own calculation 19:10.760 --> 19:17.640 sort of engine to it so for example one particular company made this clever way of 19:19.080 --> 19:25.960 estimating what the low profile looked like of a EV park for particular angi hub and that particular 19:26.040 --> 19:35.000 model could easily be integrated into into this simulation and then make a work so the North Sea 19:36.280 --> 19:44.280 great great place and there's a lot of wind mills being built if you don't know the jet 19:46.120 --> 19:54.120 and that has been metin is the oh and also the interconnections with the mainland 19:55.960 --> 20:03.960 were modeled and then sort of a like a particular example of misido which is a simulation engine 20:03.960 --> 20:12.040 that used a lot for for heat but also for gas by the way I was just he is was created 20:12.680 --> 20:18.680 and used to basically show like what would happen with the pressure in the hydrogen tanks 20:18.680 --> 20:25.160 if you would add electrolyzers based next to these wind parks and where you would add the hydrogen 20:25.240 --> 20:34.920 storage it was simulated what was the effect on the pressure in the system that was crit 20:37.240 --> 20:45.480 long story short I guess there's all these different standards ontologies maybe not even 20:45.480 --> 20:54.760 the right word data models maybe mathematical descriptions I wrote it there already so I look forward 20:54.760 --> 21:02.760 to to that perspective and I think I think sort of to to get this picture and make it as 21:02.760 --> 21:11.960 light blue as possible would definitely be my my ambition yeah then this is another tool that was 21:11.960 --> 21:18.760 been built to help sort of orchestrate many different simulations it's also open source but I'm not going 21:19.560 --> 21:32.920 to go too much in detail about it so maybe just as a last announcement we had a project 21:32.920 --> 21:41.400 proposals submitted that basically looked at combining the knowledge on on AI so at you know we 21:41.400 --> 21:51.160 developed our own LLM we didn't steal any data though so we actually we are compliant with 21:51.160 --> 21:59.000 a GDPR and we are now at GPT 3.5 so we're a bit behind but at least we didn't steal a data 21:59.960 --> 22:06.760 and so that took most of the time to actually create all the contracts with all the data providers 22:06.840 --> 22:12.200 and now we're actually figuring out like okay what sort of the strategy of bringing this 22:13.960 --> 22:22.360 ethically trained LLM to the market but while doing that we also generated a lot of knowledge on AI 22:22.360 --> 22:31.000 so now we're training AI on ESDL to make it easier to query energy systems that have been described 22:31.080 --> 22:39.320 in ESDL but also to change them and then to run iteratively different simulations so that's 22:40.360 --> 22:50.440 that's the idea we do together with with the synxes so that synxes developed solutions on GPUs 22:50.440 --> 22:57.400 so then you need to sort of break up your simulation models so that it can in parallel run 22:57.640 --> 23:03.480 and all these different GPUs quite cool but we we're not sure if we can start this 23:03.480 --> 23:09.080 but it helps out and I hope to hear from most of you today. Thanks. 23:19.000 --> 23:20.360 Two minutes? Okay. 23:28.280 --> 23:37.960 I was very clear. Why do you think that the data model started to be popular when there was a user in 23:39.320 --> 23:43.720 why do I think the data model started to become possible when there was user interface popular? 23:45.160 --> 23:50.440 Well because because people that don't understand what the data model is all of a sudden could 23:50.440 --> 23:56.760 simply drop in a user interface that they could select like hey I have a woodmill here and 23:56.760 --> 24:02.920 I could connect it to something else it will pop up and say that connection is not allowed and then 24:02.920 --> 24:07.960 they would start to think like oh okay so and then they would actually start to create sound 24:09.000 --> 24:15.800 energy systems described in ESDL and it was much easier for the data scientist and the software 24:15.880 --> 24:25.400 engineers then to use that input generated by people don't understand data models so there was 24:25.400 --> 24:29.480 much better collaboration actually between the different departments. 24:36.760 --> 24:45.640 There's seconds so just count down together. Okay thank you everybody. Have a nice day. 24:45.800 --> 24:49.800 Thank you all, thank you so much.