
This tab displays a list of all entities of the system (conventional thermal and hydro generating units, RES portfolios, DR portfolios, etc.). The user can create a new entity by pressing the “+” button at the upper-left side of the window. Then, a pop-up window opens, where the user can choose the type of the entity and specify if it is with or without virtual units.

When creating a Thermal Entity with virtual units the user should provide a name of the entity and its commissioning date. Also, the user can add the Entity’s Features such as:
Decommissioning Date
Entity Code
After filling the virtual entities section below, user should select a specific configuration that will be used for DAM.

Entity Features: User should press the circled "+" icon to add new entity features.

User provides a "Valid from" date for the data that we are going to be inserted, choose the producer, an exit point, a parent station, fuel, zone and if it is dispatchable or not. The options are in a list and user should select the appropriate value. We click "Accept" to save the selections. When something changes we can click the "+" button again and insert the new details with the new validity date. In this way, a detail history is stored in the system by selecting the validity date at "Valid From" field in entity features box. Lastly, there is an option to edit the current data with "pencil" icon.

Same logic applies in "Cost Data" section. User should click "+" button and fill in the relevant fields as shown in the image below. Take into account the units of measurement when data are filled.

In next section “Virtual Entities” user can add a new Virtual Entity and define the new entity’s basic features, such as:
Entity Features
Cost Data
Entity Data
Thermal Soak Steps
Maximums Offer Steps
Minimum Offer Steps
Auxiliary Load
After filling all the relevant field user should press accept on bottom of box.

Last configuration is about "Virtual Entity Transitions". Here user configures the transition between the different configurations of virtual units. By pressing "+" a new window opens where we define the transition by filling the initial configuration ("Entity From") and the final configuration ("Entity To"), the validity date that this transition is true and the the respective duration (hours or half-hours, based on the ISP time-step) of each transition depending on the thermal state of the unit. After, configuring all the data we press "Save" on the bottom.

When creating a Thermal Entity without virtual units the user should name the Entity and complete its commissioning date. Optionally, decommissioning date and entity code may be filled. Also, the user can add the Entity’s features, such as:
Valid From (the set of entries is valid from this date and on, until a new entry with a more recent date is imported to the system by the user)
Producer
Parent Station
Zone (i.e. bidding zone)
Exit Point
Fuel
Dispatchable (true of false)

In the section “Cost Data”, the user can define the entity’s costs for startup (in qmu per startup type), shutdown (in €/shutdown), extra fuel additional variable cost (in €/MWh), maintenance additional variable cost (in €/MWh), human resources (in €/MWh), fuel improvement (in €/MWh), emissions additional variable cost (in €/MWh), and no-load cost (in €/hour).

In the section “Entity Data” the user can define the new entity’s:
Generic Data
Heat Rate Data
Operating Timings Data
Ramping and Reserve Capacity Data
Reconciliation Data
The user can also complete the Thermal Soak Steps (in MW), as shown in Figure 2-27, per thermal state (hot, warm, cold). Each set of entries has a valid from / valid to time-range. The user can also complete the maximum and minimum offer steps (for Reserve Offers and Balancing Energy Offers). These offer steps relate to the offers’ identification process in the Balancing Market simulation module, in case the anonymized offers are publicly available by the TSO and the technical characteristics of the units are also available in the system. In case the Balancing Market simulation module is not available in the system, then the user can ignore these entries (or leave them to the default values). Finally, there are fields for auxiliary load data that optionally can be filled.

Relevant is the procedure to create a other type of entities like hydro, RES, demand entity etc.
Important: These is no option to delete an entity, but user can terminate an entity's validity by inserting a past date at the decommission date field.