The following list showcases new features and enhancements in the latest version of AURORA.
The new charting component available with v13.1 offers some exciting new features for advanced user customization. The initial layout for setting up charts is now more intuitive and advanced features are just a click away.
The new Chart Setup window includes many features found in prior versions of Aurora, but now also includes some formatting features right up front.
Long-Term Capacity Expansion Enhancements
This release includes a number of new options for controlling the constraints on new build decisions during long-term studies. Various global or resource specific options dial in exactly what the analyst needs for their simulations.
Linking Battery & Renewables
For MIP LT solutions, the New Resources table contains a new, optional column called Limiting New Resource ID which is used to link resources together so that a new resource option is limited by the build selections of another new resource option.
Two new Constraint Types have been added to the Constraint table:
- LT Reserve Margin - Aurora will accept additional reserve margin target constraints, including at a monthly level. This constraint can only be referenced by zones directly in the Constraint ID column of the Zone Definition table and Aurora will use the set of all zones referencing the constraint as the region over which the reserve margin target must be met. See the Help for more details on setting up this option.
- LT Capacity Min - This option is similar to the LT Capacity Max except it seeks to constrain the build decisions such that the total average nameplate capacity from the resources in the constraint which are online is greater than or equal to the input target.
The Decommissioning Cost column in the Resources table represents the total cost in base year currency/MW to retire a unit and is used in long-term studies as part of the retirement decision analysis. It represents a disincentive to retire, and the higher the value the less likely a unit will be to retire.
This column offers the convenience of not having to worry about capacity that changes over time especially when trying to match up the peak credit with capacity to get the desired peak capacity counted towards the reserve margin.
Scarcity Pricing Function
The new optional Scarcity Pricing Function column provides the option for resources to get paid a scarcity premium based on the zonal reserve margin (in percentage terms) in each year, similar to the application for Capacity_Revenue payments. The column should be populated with a reference to a vector in the Time Series Weekly table that defines a piecewise linear function where the domain is the annual peak reserve margin (from 1 to 168) and the output of the function is the real currency/kW-yr scarcity revenue value to be used.
Capacity Payment Calculation Options
This version includes a new option for determining the load payment that each zone or portfolio will be required to make to pay for capacity.
Version 13.1 brings some significant speed improvements when using Commitment Optimization. In the default cases delivered by Energy Exemplar, typically simulations of two summer months with sampled hours, improvements of 24-47% were experienced. On the much more intensive 8760 runs, the default projects showed improvements of 17-40%, shaving minutes and hours off the typical run times.
In v13.0 Aurora offered the ability to allow multiple island in the network, but any contingency causing an island in the network was ignored. With v13.1, solving islanded systems is extended to deal with node islanding as a result of contingencies. By using the new Allow Contingency Islanding switch on the Nodal form of Simulations Options, Aurora approximates the re-dispatch within the largest island caused by an islanding contingency. Furthermore, flow constraints are added to ensure that re-dispatch does not cause flow limit violations for branches and corridors in the largest island. Be sure to check out the Help for complete details on the simulation logic for this feature.
LMP Contribution by Hub and LF Area
Version 13.1 extends LMP Contribution reporting to hubs and loadflow areas by using the Report LMP Contributions column, in the Hub Definitions or LF Area Map tables, to specify the number of top branch and corridor contributions to report for the specified hub/LF area in the NodalLMPContributions output table.
Assign Non-Flow Constraints to MCE
This new switch determines how the LMP components are computed for a bus. When the switch is selected, the impact of any binding, non-flow constraints (such as wheeling, reserve margin, emission and others) are captured in the Marginal_Cost_Energy (MCE), and the Marginal_Cost_Congestion (MCC) calculation is based solely on binding flow constraints. When the switch is unchecked, the impacts of binding, non-flow constraints are captured in the MCC component for the bus.
A new way to specify how non-conforming load is treated has been added via the NonConforming Load Net of Zonal Load column in the Supplemental Bus table. When NonConforming Load Net of Zonal Load is True, the non-conforming bus load is subtracted from the zonal demand before assigning load to the remaining buses in the aggregate area. So, if load from the zonal data passed through to an aggregate area is 10,000 MW and the netted non-conforming load for all buses in the aggregate area is 80 MW, the total load for all buses in the aggregate area will still equal 10,000 MW, but the remaining 9,920MW will be distributed among the remaining buses.
Version 13.1 now offers the ability to specify multi-section lines as contingent elements using “&1” in the Circuit ID column.