Step 2: Create a Scenario and Run a DCUCOPF Optimization
Now that all pieces of the structure and topology of your model are in place, it is time to develop the scenarios and carry out the optimization. The tutorial objective is to assess the impact of the look ahead on the storage operation of the power system. In addition, you will analyze how the storage operation reduces the renewable curtailment.
Now, you will create a scenario to model a time window of a week (7 consecutive daily optimizations) with an hourly timestep resolution. In addition, you will learn how to retrieve solar and wind weather resource data from external data providers and import and include profiles. Two scenarios will be created: one with a look ahead and one without a look ahead.
1. Scenario 1 without a look ahead
You can now develop the business-as-usual DCUCOPF scenario that you will use for understanding the storage operation without any forecast information on the following day.
Thus, in this case, no look ahead is implemented.
From the Scenario tab select StartTime
) at 01/01/2023 00:00 (i.e., 00:00 a.m.
on the first of January 2023).
Set the scenario end time (EndTime
) to 08/01/2023 00:00.
The TimeHorizon
is 1440 minutes, and the time step (TimeStep
) is 3600 seconds, as shown in Figure 1.
After filling in all the fields, click on Ok to save and create the scenario.
Once the scenario is created, you need to define the profiles your external will follow during the optimization.
Use deterministic profile for each external.
Some profile covers one day with a hourly time step (i.e., a total of 24 steps like demand D1) while others cover seven days with an hourly time step (i.e., 168 steps like PRF_SOLAR retrieved from the data provider).
The profile modeling the demand has a peak at 17:00 each day.
Import the profiles using .\Energy Markets\Tutorial 3
of the folder Tutorials
in the directory (C:\Users\...\Documents\encoord\SAInt-v3\Projects
) Figure 2 shows an example of the profiles after the import.
Distribution
and Deviation
are irrelevant for deterministic profiles.With the following guidance, make sure to collect and generate the solar profile for the PV object. Use the how-to connect weather data, collect solar data and generate solar profile.
Finally, include the wind profile using .\Energy Markets\Tutorial 3
of the folder Tutorials
in the directory (C:\Users\...\Documents\encoord\SAInt-v3\Projects
).
Once the profiles are loaded, open the scenario event table and add the events presented in Table 1 using either the map view or the model explorer.
Start Time | Object Name | Parameter | Profile | Value | Unit of Measure |
---|---|---|---|---|---|
01/01/2023 01:00 |
EDEM.D1 |
|
D1 |
1 |
MW |
01/01/2023 01:00 |
PV.PV |
|
PRF_PV |
1 |
MW |
01/01/2023 01:00 |
XGEN.SOLAR |
|
SOLAR |
1.05 |
MW |
01/01/2023 01:00 |
XGEN.WIND |
|
WIND |
1 |
MW |
01/01/2023 01:00 |
WIND.WINDFARM |
|
PRF_WIND |
1 |
MW |
Finally, you can run the scenario and check the simulation log for possible problems. If everything goes as expected, there will be no error or warning. Congratulations! Please, remember to save the project.
Run the new scenario and check out the demand not served and the contribution from coal and gas generators. Use the following plot command in the command window to generate Figure 3.
nplot('EDEM.D1.PNS;legend=Demand not served;blue;dash;5','FGEN.G1.P;legend=Coal generator;black','FGEN.G2.P;legend=Gas generator;gray')
1.1. A new policy is in act
Assume that the TSO operating the network is affected by a new policy limiting the total generation of fuel generators (sum of Coal and Gas) to a maximum hourly operation of 325 MW.
Before analyzing the impact of the new policy, check out how much the maximum generation from fuel generators in the previous scenario. Groups are helpful for this! |
Select Constraints
, then menu: [Add New Constraints].
In the property editor, name the constraint "FOSSIL_FUELS_POLICY." Assign the variable P
of both FGEN, right click on G1 in the model explorer and select .
Repeat the process for G2 to add a P
variable to the newly created constraint.
Rename the EVAR respectively G1 and G2.
Finally, select the constraint object and set the UpBoundDef
property to 325.
Now you are ready to go and see the new policy’s impact on the system.
Execute the scenario and repeat the same plot as before, as shown in Figure 4.
You can observe a higher demand not served in the network. Evaluate if the look ahead can have an impact on the system operation.
2. Scenario 2 with look ahead
Assume the storage operator (of both X1 and X2) has invested to improve its forecasting capability. The new team now has a clearer picture of the expected demand, and the expected solar and wind generation for the following three days. This improvement will help them plan and operate the storage more efficiently.
Select InService
(in this case, you will keep it).
To add the look ahead, open the scenario editor |
Execute the scenario and repeat the same plot as before.
The demand not served is lower on the fourth day of the simulation, as shown in Figure 5.