ELEXIA Use Cases Definition

by EDP

In the last months of the project, part of the focus has been on advancing the Requirements engineering and use case definitions for the pilot sites - and producing a preliminary version of the deliverable that defines the use cases for each pilot and a KPI methodology.

The first step we have taken to correctly define the Use Cases (UCs) was characterizing the pilot’s energy system. For each site, the initial conditions were identified (e.g., demand/supply data), along with the involved assets, stakeholders, and technologies, as well as the pilot’s goals.

Τhe UCs are defined with the primary purpose of providing a clear and concise understanding of how a system should be managed designed, developed, and tested to meet the needs of its users. The UCs are established so they consider every module inside of each ELEXIA’s tool. These tools can be divided into three large categories: Digital Services Platform, System Planning Toolbox, and Energy Management System (EMS).

Also, they allow the tool developers and stakeholders to acquire a deeper understanding of how the system will be used and help identify potential issues before the system is implemented.

15 Use Cases have been defined and will be demonstrated in ELEXIA’s project. They are divided into three main categories according to the pilot they are associated with: Portuguese pilot – Port of Sines, Norwegian pilot – Dokken area, Danish pilot – Copenhagen area, including Høje-Taastrup municipality. A fourth category was also created to define a Use Case common to all pilots, related with the storage and sharing of data.

To ensure harmonization and replicability of the UCs, these are described according to the IEC 62559-2 standard which follows a specific template structured by the next seven sections:

  1. Description of the Use Case,

  2. Diagrams of Use Case,

  3. Technical Details,

  4. Step by Step Analysis of the Use Case,

  5. Information Exchanged,

  6. Requirements and Common Terms and

  7. Definitions.

The forthcoming iteration of this deliverable will encompass a more extensive elucidation of the UCs, interactions among actors, and the seamless integration of tools, as the project tasks evolve.

Previous
Previous

Our 3rd Consortium Meeting’s Overview

Next
Next

APS’s work on the Stakeholder Community Engagement Strategy and the Integration of the EMS & SPT tools