Model page description content

[kofi-k]

Provide a short description for model pages
A format like the following is preferred:

Client X had problem Y.
We investiaged A, B, C and D.
We came up with solution Z

Feel free to use a different structure if it better fits how you want to present your model.

Please put all descriptions into a single document and share it with me, @kofi-k on teams.

@AteZenmo

• Hessenpoort
• Kas Als Energiebron
• Dordtse Kil I & II en Amstelwijck West
• Dordtse Kil III & IV
• Gemeente Alblasserdam
• Gemeente Hardinxveld-Giessendam
• Gemeente Sliedrecht
• Dordrecht
• Papendrecht
• Zwijndrecht
• Hendrik-Ido-Ambacht

@naudloomans

• Nijmegen Hengstdal
• Nederland
• Hilversum
• Bunderbuurten Veghel
• Loenen
• Vruchtenbuurt
• Digital twin Drechtsteden
• Over 't Spoor
• Oostdonk
• Kerkbuurt
• Antoniapolder

@PeterHogeveen

• Borchwerf
• Amersfoort
• Veenendaal
• Tuinzigt

@GillisHommen

• Ambachtse Zoom
• Amstelwijck Businesspark
• Bakestein
• De Geer
• De Staart
• Groote Lindt v2
• Leerpark
• Nieuwe Weg
• Papendrecht Oosteind
• Sliedrecht
• Vaanpark

@Luc-Sol

• PreZero

[naudloomans]

@kofi-k @GillisHommen @AteZenmo
I would suggest the same text for all Drechtsteden -> bedrijventerrein models, as they are used for exactly the same purpose in the same project, and details on results we do not obtain ourselves typically

[AteZenmo]

@naudloomans @GillisHommen Yeah I agree on that for the most part, however we could make a different one for municipality models and company terrain models in my opinion, at least for a little bit.
And maybe add a paragraph to the the dortsekill III and IV and antonia polder modlers where we mention something about the specific researches we did there (battery management/sizing and dudok/ehub research + gridoperator topology data)

[GillisHommen]

Proposal text for all the business parks in the Drechtsteden below. This one can be used for all the models under my name, and a number of them listed with Ate and Naud.

"In the Drechtsteden region, companies are joining forces to form energy cooperatives. Helped by our Lux Energy Twin, these cooperatives enable local energy trading, shared energy management systems and group connection contracts, thereby optimising their energy infrastructure, avoiding grid congestion bottlenecks and maximising the use of local sustainable energy production. "

@AteZenmo @naudloomans if you have suggestions for improvements, that's more than welcome!

[GillisHommen]

@naudloomans @GillisHommen Yeah I agree on that for the most part, however we could make a different one for municipality models and company terrain models in my opinion, at least for a little bit. And maybe add a paragraph to the the dortsekill III and IV and antonia polder modlers where we mention something about the specific researches we did there (battery management/sizing and dudok/ehub research + gridoperator topology data)

I would say a separate text should be used for the RES and residential models of the Drechtsteden. The 'special' projects we did for Dortse Kil III/IV and Antoniapolder are worth mentioning, although these models are not on our website I believe.

[naudloomans]

Thanks Gillis, I used your text and added sections in Dutch and English for the different pages.
@kofi-k can you work with this.

Texts Drechtsteden models website.docx

@GillisHommen and @AteZenmo if you want you can give feedback.

[kofi-k]

Thanks Gillis, I used your text and added sections in Dutch and English for the different pages.
@kofi-k can you work with this.

Sure, just as long as we're all in agreement

[naudloomans]

@kofi-k
Here some text and instructions for the other models

In a more general note. I am thinking we could add a data tag (month + year) of when the model was last updated. This to help kind of filter very old models. @peter-hogeveen what do you think?

Tekst website models Naud.docx

[peter-hogeveen]

A date tag is a good idea, I think we should do that! Can we automatically get the input value for that tag from our private cloud? The upload date of the model is shown there, but im not sure you can programatically reach it @Erikvv and @kofi-k.

I think we could show the text: 'Model update date: xx-xx-xxxx' in at the purple line: