What Are Override Commands?
Override commands are commands that are manually sent to an Acumen EMS via Monitor that tell the energy storage system on site how to dispatch. These commands override the default operating strategy at the site. For example, if a site's default operating strategy is Demand Charge Management, and a user issues an override command for the ESS to Discharge at 100kW, the site will begin discharging at 100kW regardless of the effect on the site’s demand charge management performance.
What Are Override Commands Used For?
Override commands are a powerful feature and can be used for a variety of use cases.
One use case is demand response program participation. For example, when a demand response event is called, a user can utilize the override command feature to program the ESS to dispatch at full power for the duration of the event, generating maximum revenue. This is especially powerful when coupled with the Acumen Virtual Powerplant Controller.
A second use case is to adjust the ESS operation to better handle site events that will alter the site's load profile. For example, if your site's load profile typically does not have significant demand at night, but you are planning on hosting an outdoor event with industrial lighting, you can schedule your energy storage system to dispatch at full power to coincide with when you are planning on turning on the industrial lighting to offset the increased demand spike.
A third use case is planning for inclement weather or other conditions that may cause grid instability. For example, if there is an outage predicted, a user can send an override command to the ESS to charge to 100% SOC and maintain that SOC for the next 48 hours or until told differently.
There are many other use cases for override events. If you have questions about your specific use case, please contact your Energy Toolbase account manager or your company administrator.
Override Command Conflict Resolution
Conflicting commands are commands that have any amount of overlapping time. Conflicting commands result in Acumen implementing one command and ignoring any conflicting commands. In the case of conflicting commands, the most recently sent command will take precedence. This conflict resolution logic is the same whether the commands are sent from the Manual Override User Interface or the Acumen Virtual Powerplant Controller.
Conflict Resolution Example:
- On January 2nd at 9:00AM, a user creates Override Command 1 via the Manual Override User Interface telling the ESS to Discharge at 100kW from January 2nd at 5:00PM until January 2nd at 9:00PM.
- On January 2nd at 9:01AM user sends Override Command 2 via the Manual Override User Interface at the site page telling the system to Charge at 100kW from January 2nd at 8:30PM until January 2nd at 10:00PM.
- Since there is a 30-minute overlap, these override commands are considered conflicting. Override Command 2 will take precedence because it was the latest override command sent to Acumen.
- Override Command 2 will occur as scheduled, and Override Command 1 will be cancelled and removed from the site calendar.
Frequently Asked Questions About Override Commands
1. What operating modes can I use in override commands?
Please see the help center article detailing each available operating mode. Note that not all override commands are available for every system. Override functionality is dependent on the specifications of the system.
2. Can override commands be edited?
No. Override commands can only be created and cancelled.
3. Can any user create override commands?
No. There are both read and write permissions for overrides. Users with the read-only permissions can only view override data. Users with the proper override write permissions can create or cancel overrides.
4. How do I get the proper permissions to create overrides?
Contact your Energy Toolbase account manager or your company administrator.
5. Are systems that have override command functionality Rule 21 / 2030.5 compliant?