E2District Public Deliverables 

E2District is voluntarily participating in the Horizon 2020 Open Data pilot and is committed to enhancing interrelated research in the EU energy efficiency domain.

The objective of this deliverable is to define high-level functional requirements for E2District platform and methodology, based on the needs expressed by all different stakeholders, for the development of a District Management and Decision Support framework for District Heating and Cooling Networks (DHCN). To do so, a first step has been to identify the stakeholders involved in the design and operation phases of DHCN, and to list what could be their needs, based on the experience and expertise of each project partner. Subsequently, services that could answer those needs have been defined and sorted in three categories: needs, constraints and wishes (needs with low priority levels). Finally, high-level functions, defining how the system could satisfy these services, have been defined. For each function, a list of input data, output data (results) and a description of what should be done by the function is given. This work should serve as a first basis for the specification and development of the different components of the system (models, algorithms and platforms), within the framework of Work Packages 2 to 4. As the various tasks of the project will be progressing, these requirements will be reviewed and updated if necessary based on the experience the consortium gains in the execution.   

In deliverable D1.1 (D1.1: Report on requirements for district heating and cooling, 2016), based on the services needs definition, we introduced the concept of a system that formalize and address the needs of the stakeholders. It is an exhaustive and high level answer, which encompasses all features that are expected. This document now goes down one level, by listing and detailing the use cases for which the platform will be developed and tested, for both demonstrator and virtual sites. A use-case is a fixed evolution of one or several aspects of a DHCN ecosystem compared to the existing situation. These aspects are operating mode, technical configuration and context. The different use cases defined in this deliverable have been built and validated by all partners to either answer to the stakeholder’s requirements or tackle replicability problematic, and will be used directly into the different Work Packages for the development. So after listing all possible evolutions on the three aspects, use cases are defined for each site (Cork and Varna), with a specific formalization. Finally, a replicability section is presented, which purpose is to make sure that the developments are applicable to other contexts than the ones related to the sites studied during the project.

The objective of this deliverable is to define operational and maintenance KPIs (DHN efficiency, carbon footprint, quality of service, ROI etc.) and also to define KPIs for the estimation of energy and CO2 savings regarding the project target (reduce the energy consumption of space and water heating by 30% compared to today’s level). These KPIs will be used to validate and assess the DOS and DSP platforms, and their underlying tools and therefore they must be defined to give reliable information about the performance of the DHC system.

Work Package 2  

D2.1 Detailed Specifications on Interoperability
This report outlines the Detailed Specifications on Interoperability between tools from different partners involved in E2District project. The report, associated to Task 2.1, addresses this harmonisation process for the specific case of the different solicitations that District Simulation Platform (developed within WP2) shall have to support throughout the project. As illustrated on Figure 1 this work has been closely done with WP3 requirements and aims to prepare as best as possible the integration of these simulation features in WP4.

Work Package 4

This deliverable defined the District Operation System for supporting the functional requirements of the functions defined in deliverable D1.1 with regards to the operation of the primary heating and cooling network as well as with regards to the operation of individual groups of buildings. It was shown how the operational scenarios described in D1.1 are translated into a system architecture comprising logical modules and their interactions. It was argued how an event-driven platform architecture would best suit the requirements of the E2District Operation System.The document describes how the overall E2District architecture and its modules can be implemented using an extension of the existing NiCore platform framework. This framework will be used to facilitate a reference implementation of this architecture in a cloud based district operation system platform. Furthermore, the document provides a reference for the various APIs available to module developers, both external as well as internal, and shows how building and district heating and cooling sub-systems are abstracted through the platform to allow a unified access to data and controllable assets.

Work Package 6

D6.1 Dissemination and Communication Plan (DCP)
This report outlines the E2District Dissemination and Communication Plan (DCP). The plan identifies, organises and defines the management and promotion of project objectives and results. The aim of the E2District project is to develop, deploy, validate and demonstrate a novel cloud based District Management and Decision Support framework for next generation DHC systems. Therefore, the dissemination strategy employed builds on the requirements specification conducted in the early stages of the project (D1.1) to ensure a focus on the relevant stakeholders. The idea underpinning the dissemination strategy is to take key external stakeholders through a three stage process of awareness, understanding and action, so that, ultimately, relevant stakeholders are applying the E2District solution for optimised community energy management.

D6.2 Data Management Plan (DMP)

This document establishes the E2District project's approach to data management for the datasets captured or processed inside the project, according to the guidelines published by the EC. The plan identifies how data collected or generated  by the E2District project will be organised, stored and shared and specifies what type of data will be made publicly available by the project (open access) in so far as it is possible to do at this stage of the project. Suitable public repositiories to store the data have also been identified. This DMP is not a fixed document and will, therefore, evolve throughout the E2District project according to the progress of project activities.

D6.3 Implementation of Dissemination/Communication of Results Report I
​This deliverable presents the dissemination and communications activities for the initial15 month period of the E2District project which had the objective of assisting the project in achieving the greatest possible impact among E2District’s stakeholders in Europe. It includes details of dissemination and communication activities from all five partners of the E2District consortium.