The purpose of deliverable D4.234 is to define the technical design of the Integrated Decision Support Systems (IDSS) based on the decision process defined in D4.1. It reports the results of the three sub-tasks: a) inclusion of Key Performance Indicators (KPIs) in decision process b) functional design of the Graphical User Interface (GUI), c) Technical Design of both the Dashboard and The Framework that integrates the Dashboard with the databases and Modules used in the decision process.

For KPI inclusion, we described the process of the decision makers in using KPIs based on the Phases defined in D4.1 (see Figure 1). This inclusion resulted in both expected actions and the support from the Dashboard.  The IDSS support is identified in Phase A with 13 and in Phase B with 8 actions that vary from administrative to calculation functions. The color-coded diagram in Figure 1 distinguishes the degree of automation of the IDSS. Green boxes refer to semi-automatic/semi-manual actions conducted by the end-user, whereas the blue ones specify full-automated actions handled by the IDSS components itself.

ecodistrict_Integrated Decision Support Systems

Figure 1 – The IDSS in Phases A and B

KPI inclusion prepared a basis for the functional design of the GUI and technical design of the Dashboard and the Framework of the IDSS.

For the GUI, we presented a Mock-Up, which functionally simulates the screens in correlation with the KPI inclusion in the decision process. The examples of GUI screens are provided in Figure 2 and Figure 3.

Ecodsitrict Graphical User Interface

 Figure 2 – Administrative functions in GUI Mock-up

Ecodistrict Graphical User Interface

 Figure 3 – Calculation functions in GUI Mock-up

For the Dashboard, we presented the system architecture, which dealt with server environment (communicating the Framework with the Database) and client applications (connecting end-user applications to the server)(see Figure 4).

Ecodistrict Dashboard

 Figure 4 – Dashboard system architecture

The Dashboard became a common interface for the end-users to follow the decision making process and to control of the connected Modules. And the Framework needs to be designed in a way to connect end-user applications with the Dashboard.

For the Framework, we reported the connection (a message service) between the Dashboard and the Modules via TNO’s IMB (Inter-Model Broker) Hub. It also presented the architecture of the IDSS framework (see Figure 5).

Ecodistrict framework architecture

Figure 5 – Architecture overview of the IDSS Framework

Through these functional and technical designs of the IDSS components, there were main technical choices made in D4.234. These choices will be the basis for the upcoming activities in ECODISTR-ICT. As developing the IDSS and its components will be an iterative process, the feedback from the consortium partners and the external stakeholders in the use cases will be incorporated in the next development steps.

Share on Google+Share on FacebookTweet about this on TwitterShare on LinkedIn