<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <journal-title-group>
        <journal-title>D. Hick);</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>Low-code to fight climate change: the Climaborough project</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Aaron Conrardy</string-name>
          <email>aaron.conrardy@list.lu</email>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Armen Sulejmani</string-name>
          <email>armen.sulejmani@list.lu</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Cindy Guerlain</string-name>
          <email>cindy.guerlain@list.lu</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Daniele Pagani</string-name>
          <email>daniele.pagani@list.lu</email>
          <xref ref-type="aff" rid="aff2">2</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>David Hick</string-name>
          <email>david.hick@dksr.city</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Matteo Satta</string-name>
          <email>m.satta@matteosatta.com</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Jordi Cabot</string-name>
          <email>jordi.cabot@uni.lu</email>
          <xref ref-type="aff" rid="aff2">2</xref>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>ANCI Toscana</institution>
          ,
          <addr-line>Florence</addr-line>
          ,
          <country country="IT">Italy</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Daten-Kompetenzzentrum für Städte und Regionen (DKSR) GmbH</institution>
          ,
          <addr-line>Berlin</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Luxembourg Institute of Science and Technology</institution>
          ,
          <addr-line>Belval</addr-line>
          ,
          <country country="LU">Luxembourg</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>University of Luxembourg</institution>
          ,
          <addr-line>Belval</addr-line>
          ,
          <country country="LU">Luxembourg</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2025</year>
      </pub-date>
      <volume>000</volume>
      <fpage>0</fpage>
      <lpage>0003</lpage>
      <abstract>
        <p>The EU-funded Climaborough project supports European cities to achieve carbon neutrality by 2030. Eleven cities in nine countries will deploy in real conditions products and services fostering climate transition in their local environment. The Climaborough City Platform is being developed to monitor the cities' overall progress towards their climate goals by aggregating historic and real-time data and displaying the results in user-friendly dashboards that will be used by non-technical experts to evaluate the effectiveness of local experimental initiatives, identify those that yield significant impact, and assess the potential consequences of scaling them up to a broader level. In this paper, we explain how we have put in place a low-code/no-code strategy in Climaborough in response to the project's aim to quickly deploy climate dashboards. A low-code strategy is used to accelerate the development of the dashboards. The dashboards embed a no-code philosophy that enables all types of citizen profilesto configureand adapt the dashboard to their specificneeds.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Climaborough</kwd>
        <kwd>Climate</kwd>
        <kwd>BESSER</kwd>
        <kwd>Dashboard</kwd>
        <kwd>Low-code</kwd>
        <kwd>No-code</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>Climaborough12 is a research project, co-funded by the European Union and CINEA, aimed at
bridging the gap between the design and implementation of urban innovations, tackling
climate change and its consequential need for rapid adaptation and mitigation. Specifically, it
aims to overcome the bottlenecks when transitioning from prototyping to testing and to market
deployment of innovation. It is a four-year project started on January 1, 2023 and coordinated by
ANCI Toscana3 with the participation of 27 additional partners, of which 14 European cities
engaged in their ecological and digital transition. Seven work packages (WP) were defined to
tackle different tasks: (WP1) Urban Planning and Climate Neutrality Evaluation, (WP2)
Climaborough City Platform, (WP3) CLIMHUBS Setup, Co-Creation and Collaboration, (WP4)
Innovative Procurement, (WP5) Climate Sandbox Demonstration in Real Environments, (WP6)
Dissemination, Communication and Exploitation and (WP7) Management.</p>
      <p>The primary outcome of the project will be the development of a structured process
incorporating a set of tactical tools designed in collaboration with domain experts, including
an innovative procurement process aimed at accelerating cities’ capacity to implement climate
transition strategies within urban planning. More specifically, as part of the process, cities are
engaged in defining their specific needs, which are addressed through an innovative
procurement process managed by ANCI Toscana. This process enables cities to identify and
adopt disruptive solutions across various sectors, including energy, mobility, waste management,
and circular economy. These solutions are subsequently implemented and tested using a
sandbox methodology, and the resulting data is integrated into the platform. The impact of
these initiatives is then assessed through a Climate Neutrality Framework4, which facilitates the
estimation of their broader scalability and effectiveness and helps cities in their decision to adopt
them or not at scale.</p>
      <p>To evaluate the progress and effectiveness of the solutions, and the project in general, it is
critical to put in place an infrastructure to make sure the generated data (at the specific solution level,
at the city level, at the project level...) will be monitored and evaluated. This includes
defining(1) KPIs related to the solution specificgoals, (2) Metrics to estimate the solution’s
contribution to overarching climate KPIs, and (3) KPIs describing the overall cities’ progress
towards climate related goals (such as reaching zero carbon emission) using aggregated data
from solutions and beyond.</p>
      <p>To help cities assess the effectiveness of implemented solutions and better understand their
potential impact on achieving climate neutrality on a larger scale, the Climaborough City
Platform will be developed by WP2, led by the Daten-Kompetenzzentrum für Städte und
Regionen5 (DKSR) in collaboration with the Luxembourg Institute of Science and Technology6
(LIST) and the Institut Mines-Télécom7 (IMT), and will incorporate a data ingestion pipeline,
dashboards for visualizing results and a digital twin component.</p>
      <p>The creation of the dashboards is especially important and challenging, as it needs to cater to
a variety of users and enable the adaptation of the core dashboard to the specific data and
solutions under evaluation in a given city. To make things worse, this adaptation sometimes
needs to be done by non-technical people in the public administration, as they rely on the
visualization to support their decision-making.</p>
      <p>
        In this sense, this paper focuses on describing how the project has followed a low-code and
3https://ancitoscana.it/
4https://ec.europa.eu/research/participants/documents/downloadPublicdocumentIds=080166e517cb7a44&amp;appId=PPGMS
5https://www.dksr.city
6https://www.list.lu/
7https://www.imt.fr/
no-code strategy [
        <xref ref-type="bibr" rid="ref1 ref2">1, 2</xref>
        ] to create these flexible dashboards in an optimal way, highlighting the
benefits of this type of technologies in complex data manipulation and visualization scenarios
such as that of this project. In short, the low-code part is used to speed up the development
of the core dashboard components while a no-code mechanism, embedded in the generated
dashboards, allows users to add, remove and configure the dashboard widgets. This strategy is
implemented on top of the low-code platform BESSER8 [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. Therefore, we typically refer to
these dashboards as BESSER-dashboards.
      </p>
      <p>Next sections are structured as follows. Section 2 describes the Climaborough City Platform and
its application in Climaborough. Then, Section 3 provides more details on the low-code
respectively no-code contribution. Afterwards, Section 4 presents the current state of the
platform and discusses some of the choices we made based on encountered challenges. Finally,
Section 5 concludes this paper and presents the next steps.</p>
    </sec>
    <sec id="sec-2">
      <title>2. The Climaborough City Platform</title>
      <p>The BESSER-dashboards are part of the Climaborough City Platform. This platform is a
datadriven system for monitoring and evaluating the effectiveness of urban climate solutions, while
tracking progress toward the cities’ climate transition goals. It serves as a centralized data
aggregator, integrating streams from heterogeneous sources. By consolidating these diverse
inputs, the platform provides a comprehensive view of key performance indicators through its
dashboards.</p>
      <p>Platform requirements were defined through co-creation workshops and interviews with
cities and experts, in which predefined features were ranked based on their priority by the
participants to ensure the functional and non-functional needs were met.</p>
      <p>In the following, we will outline the architecture of the Climaborough City Platform, as
illustrated in Figure 1.</p>
      <p>The Data Ingestion Segment is responsible for gathering and managing data from diverse
sources. It integrates historical records, real-time data provided by solution providers, and
additional datasets from external climate initiatives such as Copernicus9. This layer relies on
traditional data collection and processing techniques, ensuring robustness and reliability.</p>
      <p>Once data is ingested, it is processed in the Analytics Segment, where it is aggregated and
analyzed based on Key Performance Indicators (KPIs). These KPIs, developed in collaboration with
cities and domain experts, allow stakeholders to measure the effectiveness of their climate strategies.</p>
      <p>Additionally, this segment integrates a Digital Twin (DT), proposed by the IMT, which enables
predictive modeling and scenario analysis. The DT leverages real-time and historical data to
simulate the potential impacts of various climate strategies, helping cities anticipate challenges
and optimize their policies accordingly.</p>
      <p>The final layer translates the processed data into actionable insights through visualizations on a
dashboard that follows a no-code approach. Its primary goal is to allow cities to interactively
explore and visualize climate-related data and KPIs without requiring technical expertise. The
8https://github.com/BESSER-PEARL/BESSER
9https://www.copernicus.eu/en
no-code interface enables users to create and modify dashboards with a simple drag-and-drop
mechanism, significantly lowering the barrier to data-driven decision-making.</p>
      <p>This part is where the platform’s low-code and no-code innovations take effect. In the
following sections, we will explore how this approach enables rapid dashboard deployment,
enhances usability and adoption, and empowers cities in their climate transition efforts.</p>
    </sec>
    <sec id="sec-3">
      <title>3. BESSER-dashboards: Low-code approach to configure no</title>
      <p>code dashboards
Our main objective with the BESSER-dashboards is to speed up the development of dashboards and
their integration in data-driven projects while guaranteeing that the resulting dashboards can be
created and adapted by non-technical stakeholders. As illustrated in Figure 2, our approach
is built around BESSER, a robust low-code platform that guides developers through two
primary stages: modeling and code generation.</p>
      <p>The creation of a final dashboard involves then two stages. In the first one, technical people
select the data and the core features of the dashboard. In a second stage, non-technical people
adapt the dashboard to their specific needs. Let us see both phases in more detail.</p>
      <p>During the modeling stage, designers and developers definea data model that forms the
foundation of their application. While data modeling still needs to be led by technical people, the
abstract nature (thanks to the use of graphical modeling languages) still allows for collaboration with
non-technical stakeholders, allowing for their involvement at an early stage. This model is then fed
directly into our automated code generators, which produce a complete backend and frontend
environment for a web application consisting of the no-code dashboards and additional data
management features. This process eliminates repetitive manual coding and ensures that the
generated code is consistent, scalable, and tightly aligned with the specified data structure. In
situations where a project already has an existing backend, BESSER can generate only the
necessary additional components, ensuring seamless integration without requiring a complete
system overhaul. This web application comes with a dashboard front-end preconfigured, via
the use of low-code techniques, to be aware of the data model and include all the necessary
connections to read the data from the backend.</p>
      <p>After this initial configuration, non-technical users are now allowed to modify all dashboard
widgets. BESSER-dashboards embed a no-code philosophy, enabling diverse users such as
city planners or sustainability officers to drag-and-drop widgets for tailored views. Users can
select a datasource from a list and associate it with a visualization through simple drag-and-drop
actions, eliminating the need for manual coding or technical expertise. The visualization is
automatically configured based on the datasource schema for optimal clarity. Additionally, a
conversational agent further simplifies interactions, allowing users of all technical backgroundto
adjust their dashboard or query data using natural language.</p>
      <p>In addition to the basic dashboard interaction, an AI-powered multilingual conversational
agent is also available on the dashboard. This agent plays two different roles:
1. Help in the no-code strategy by offering a conversational (textual and audio) dashboard
interaction to let users create, modify and read dashboard content by directly chatting
with the agent.
2. Answer data questions. Complementing the visualizations, cities can also ask the agent
questions. Thanks to its curated internal knowledge and the use of Retrieval-Augmented
Generation (RAG), which integrates Large Language Models (LLMs), the agent is able to
provide useful answers. The knowledge body is being created in collaboration with
domain experts from other work packages, while also including research and results
from other climate initiatives such as NetZeroCities10, and Climaborough project
deliverables and data. This facilitates both the knowledge transfer from experts and
replication of implemented solutions, given that many of the challenges cities face are not
unique. This process is depicted in Figure 3.</p>
    </sec>
    <sec id="sec-4">
      <title>4. Current state of the Climaborough City Platform</title>
      <p>An early version of a data processing module is under development, exploring different
technologies to streamline data ingestion and transformation. This module is currently
tested with various approaches, including direct integration from source like Google Drive to
API Endpoints. To improve data accessibility and organization, the development of a data catalog is
being considered.</p>
      <p>At the same time, the BESSER-dashboards leverage a structured backend and an interactive
frontend that streamline the dashboard creation. The backend leverages a model-driven
approach, enabling the automatic generation of a REST API and a database schema directly
from the defined metamodel, ensuring consistency between data structures and API endpoints.
On the frontend, the no-code interface provides already significant flexibility and
customization possibilities, as users can drag and drop visual components, position and resize
them dynamically and adapt the design and descriptions of the visualizations (e.g., changing
the color of a visualization or the title). The low-code process is already in place, and in
collaboration with the cities, we have started modeling the data models corresponding to their
needs. Figure 4 contains a screenshot of the dashboard creator, where one can see the possible
visualizations that the dashboard supports.</p>
      <p>The conversational agent-based dashboard creation feature further streamlines the process by
allowing users to generate and modify dashboards through natural language commands.
Currently in an advanced prototyping phase, efforts are focused on enhancing contextual
understanding and enabling more complex customization options. Additionally, the RAG
features are in place, which provide structured climate-related insights. Ongoing improvements aim to
refine response accuracy and expand document coverage with expert contributions.</p>
      <sec id="sec-4-1">
        <title>4.1. Discussion</title>
        <p>In this section, we cover some reflections from the use of information system techniques and in
particular low-code / no-code techniques in the context of the project.</p>
      </sec>
      <sec id="sec-4-2">
        <title>Flexibility of model-based and low-code approaches One of the initial choices we</title>
        <p>considered was using an existing dashboard tool for the Climaborough City Platform (e.g.
Grafana). However, after careful evaluation, we decided to develop our own solution to maintain full
control over its features, customization, and adaptability. Moreover, thanks to following a
model-based approach, we could easily change the tech stack targeted by the code generators in
case cities had some preferences / restrictions in the type of infrastructure they wanted to use.
Given the evolving requirements of a research project involving so many partners, this was a
critical concern that low-code helps us to address.</p>
        <p>Balancing low-code and no-code approaches Another crucial consideration was whether to
implement a fully low-code or no-code solution instead of a mixed one as we have done in the
project. A fully no-code approach would have introduced many limitations as users would have
been restricted to a predefined number of templates to build the complete dashboard. A fully
low-code one would have offer full flexibility but required technical expertise during the
customization phase. Our mixed approach aims to combine both worlds.</p>
        <p>
          Need for AI-enhanced components While our dashboard is built on core information
systems and model-based techniques, it was inevitable to add also AI techniques in the mix.
Users expect them (e.g. in the form of a conversational agent). Therefore, it is clear that, more
and more, we need to combine classical engineering techniques with AI ones to build smart
software systems [
          <xref ref-type="bibr" rid="ref4">4</xref>
          ]. Fortunately, BESSER is already created with this goal in mind, and it was
therefore easy to integrate conversational agent development in our low-code process.
Early validation Preliminary testing by our project partners has demonstrated significant
interest in the dashboard’s core features. Cities have responded positively to the intuitive nature of
the no-code interface, highlighting its ease of use and accessibility. The positive feedback from
partner cities highlights how blending low-code for setup with no-code for user interaction makes
climate data visualization more accessible and engaging. Cities have embraced the ability to
effortlessly shape their own dashboards, giving them direct control over their data without
needing technical expertise. This hands-on approach fosters greater involvement and ownership in
their climate monitoring efforts.
        </p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Conclusion and future work</title>
      <p>In an effort to support the performance tracking of the pilots deployed in the Climaborough
project, we presented the concept of the Climaborough City Platform. Specifically, given the
project’s goal of fast implementation of climate solutions, we focused on the low-code approach to
quickly configure the backend and frontend environment of a no-code dashboard creator for
nontechnical users, enhanced by advanced interaction methods.</p>
      <p>Based on the feedback provided by cities, we will improve both aspects. We also plan to study in
what other parts of the project architecture (potentially involving other WPs), a low-code
strategy could also make sense. For instance, in the creation and execution of climate simulation
scenarios.</p>
      <p>Finally, we plan to connect the Climaborough City Platform to other climate initiatives
such as the NetZeroCities platform11 or the Climaborough twin project UP203012. This could
include pushing or pulling data from the NetZeroCities knowledge repository or including
NetZeroCities benchmarks.</p>
    </sec>
    <sec id="sec-6">
      <title>Acknowledgments</title>
      <p>This project is supported by the Luxembourg National Research Fund (FNR) PEARL programme under
the grant agreement 16544475 and the Climaborough project, co-funded by the European Union under
the grant agreement 101096464.</p>
    </sec>
    <sec id="sec-7">
      <title>Declaration on Generative AI</title>
      <p>During the preparation of this work, the authors used GPT-4 in order to: Grammar and spelling check.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>D.</given-names>
            <surname>Di Ruscio</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Kolovos</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Lara</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Pierantonio</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Tisi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Wimmer</surname>
          </string-name>
          ,
          <article-title>Low-code development and model-driven engineering: Two sides of the same coin?</article-title>
          ,
          <source>Software and Systems Modeling</source>
          <volume>21</volume>
          (
          <year>2022</year>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>J.</given-names>
            <surname>Cabot</surname>
          </string-name>
          ,
          <article-title>The low-code handbook: Learn how to unlock faster and better software development with low-code solutions</article-title>
          ,
          <source>Jordi Cabot</source>
          ,
          <year>2024</year>
          . URL: https://lowcode-book.com/.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>I.</given-names>
            <surname>Alfonso</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Conrardy</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Sulejmani</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Nirumand</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Ul Haq</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Gomez-Vazquez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.-S.</given-names>
            <surname>Sottet</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Cabot</surname>
          </string-name>
          ,
          <article-title>Building besser: an open-source low-code platform</article-title>
          ,
          <source>in: International Conference on Business Process Modeling, Development and Support</source>
          , Springer,
          <year>2024</year>
          , pp.
          <fpage>203</fpage>
          -
          <lpage>212</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>J.</given-names>
            <surname>Cabot</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Clarisó</surname>
          </string-name>
          ,
          <article-title>Low code for smart software development</article-title>
          ,
          <source>IEEE Softw</source>
          .
          <volume>40</volume>
          (
          <year>2023</year>
          )
          <fpage>89</fpage>
          -
          <lpage>93</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>