A general distinction is made here between digital tools and digital applications. A digital tool is a piece of software used in conjunction with other tools by developers or engineers, for creating products with specific functionalities. Frameworks, libraries, programming languages and standards are also listed under tools. A digital application, on the other hand, is a standalone piece of software designed for a specific use case. Typically, a digital application consists of a chain of tools with possible direct interaction with the end user. Platforms are also listed under Applications. It is entirely possible to have a tool that can also be classified as an application. In a first step, we collect these digital tools and applications and make them available to you as an overview and inspiration. A detailed compilation of the tools and applications can only be undertaken together with the users, so please feel free to contact us. We look forward to hearing your application examples from your projects.
When putting together the tools, we took the following aspects into account:

• Short description – What is it about?
• Area of application – What do the developers describe as the area of application of their digital tool? Options are administration, research/teaching, industry and services.
• Use type – What purpose is the tool used for? Options include simulation, monitoring, optimization, planning, control, advanced control.
• Life cycle phase – In which phase of the product life cycle is the tool used? The phases of preliminary planning, planning, implementation and operation are taken into account here.
• User interface – How can users operate the digital tool? Does it require an independent installation, is there a web-based interface or, for example, via the command line?
• Target group – Who do you say the digital tool is aimed at? As a rule, digital tools can be used by everyone.
• Last update – When did the last update occur? Particularly in the case of digital tools that are developed as part of research projects, further development or maintenance can be stopped after the project has been completed.
• Accessibility – How accessible is the tool? Is it paid, open-source or freeware?
• License – Under what license was the digital tool published and are there any costs associated with using the digital tool?
• Alternatives – Identification of concrete examples of the use of tools in the construction sector/energy transition construction (e.g., funding indicators).
• Specific use cases – Identification of concrete examples of the use of tools in the construction sector/energy transition (e.g., project number).
• Developers/maintainers – Who is responsible for the development and maintenance of the tool?
• General type of tool – What type is the tool? Is it a digital tool, a framework/library, a programming language, a standard or even an application?
• Published – Is a publication planned? (if not already done)
• Publication planned – If the tool is not yet published, is there plans to release it?
• Year of publication – If the tool is published, in what year was it released?
• Sources of information – Source for further information about the tool, e.g., git repo, project website.
• Level of development – What is the current development status? The following options are possible:
  1. First draft (pre-alpha)
  2. Essential functions (alpha)
  3. Not yet fully tested (beta)
  4. All functions preserved, possibly containing errors (Release Candidate - RC)
  5. Ready for productive use (released)
• Programming language – Which programming language is mainly used to implement the tool?
• Most important framework/libraries – What are the most important frameworks or libraries for implementation?
• Database system – Which database system does the tool use?
• Spatial scale of use cases – On what scale is the tool used? Does the tool find in a component, a system, a building, or in a district/network or a region/country?
• Norms/Standards – Which norms or standards serve as the basis or orientation for the tool?

Additional information:

https://simquality.de/tools
The Simquality compiles information and data on quality assurance and standardization of simulation processes,including independent tests of simulation software. Further information is provided about tools like IDA ICE,EDSL-TAS, NANDRAD, ETU Simulation, THERAKLES, TRNSYS and AixLib can be found on the website mentioned above.

https://github.com/protontypes/open-sustainable-technology
The Open Sustainable Technology project collects open, sustainable and actively maintained projects that aim to enable a sustainable energy transition.It encompasses standards, data, and programs without further classification.

https://www.baulinks.de/architektursoftware/index.php
The baulinks website collects information about software with a focus on architecture and crafts. In addition to CAD tools or digital tools for planning, information on digital timesheets or digital tools for calculating quantities is also collected.

https://openenergy-platform.org
The Openenergy platform aims to make the modeling of energy systems transparent. For this purpose, information and digital tools on the topic of energy are collected.

https://www.energy.gov/eere/buildings/building-energy-modeling
Other sites such as those operated by the Office of Energy Efficiency & Renewable Energy of the United States of America Website collects information about digital tools that are financed and created by them. In addition, clear information is provided through further information such as a blog.

https://www.gebaeudeforum.de/service/toolbox/
The Climate Neutral Building Forum provides an overview of digital tools. These are aimed particularly at people who work in accounting and consulting.