In Schedule mode, the power requested by the controller to the fleet does not directly depend on a previous power flow solution. However, previous power flow solutions may indirectly affect the available energy at the storage, which in turns may impede the fleet to follow the specified schedule, as shown in this example. The storage controller has been specified as follows: 


New StorageController.SC element=Line.ln5815900-1 terminal=1 modedis=schedule

~ tup=3 tflat=4 tdn=2 timeDischargeTrigger=14 modecharge=Time

~ timeChargeTrigger=2 %ratekW=100 %rateCharge=50 %reserve=20 eventlog=yes


Note that even though the controller does not utilize any power/current reference in this mode, it requires an element to be specified.

A graph with numbers and lines??Description automatically generated

Figure 18: Dispatch shape as defined by Tup, Tflat, Tdn and timeDischargeTrigger properties

Figure 19 shows the power measured at the feeder head along with the total power dispatched by the fleet. Note that during discharging, it precisely follows the schedule until 6pm. However, at 7pm some elements of the fleet are fully depleted, as shown in Figure 20. The elements that still have energy stored continue following the schedule, until 9pm, when the entire fleet has reached the specified %reserve.

A graph with red lines and numbers??Description automatically generated

Figure 19: Powers at the monitored element and the total power dispatched by the fleet

A graph of a line graph??Description automatically generated with medium confidence

Figure 20: State of charge of each element of the fleet