RESOLVE Scenario Tool

The RESOLVE Scenario Tool is a user-centric model interface, designed to link data, inputs, assumptions, and constraints with the RESOLVE code. The primary step in being able to make that linkage is making sure that xlwings is correctly set-up.

Overview of Data Flow to RESOLVE Model

The main data are organized in RESOLVE upstream workbooks, and is recommended to collect and format key input datasets into template tables, most importantly for baseline, load and candidate resource data, for easy data transfer to the RESOLVE model. While these workbooks are available and accessible for review of data inputs, users should not need to edit these files and can instead directly rely on Scenario Tool for reviewing or using the data.

Illustration of data flow from upstream workbooks to RESOLVE Scenario Tool

Structure & Tabs of the Scenario Tool

All CPUC RESOLVE Scenario Tools have the following main worksheets.

Scenario Tool Tab	Short Description
Cover	Takes input for Python & Folder Path as defined by the user
RESOLVE Case Setup	A tab where users can look at existing case designs, make new cases, record them, save data inputs and case settings
Timeseries Clusters	Sample days represented in RESOLVE as well as chronological days representing inter-day sharing are included here
Zonal Topology	Zones, inter-zonal power flow paths, and path expansion options as well as simultaneous flow limits are defined
Load Components	Defines different load components and values for each zone
Passthrough Inputs	Gathers all inputs across multiple tabs that contain useful information to carry to RESOLVE case outputs
Fuels	Includes all defined fuels and their price and GHG and carbon price policy attributes
Carbon Price	Includes carbon price scenarios
Emissions Policy	Includes emissions target scenarios and policy adjustments
Clean Energy Policy	Includes clean energy targets for RPS and SB100 scenarios and policy adjustments at CAISO level
System Reliability	Includes ELCCs, and system reliability target scenarios and adjustments at the CAISO level
Baseline Resources - Default	Includes all existing resources across all zones. Represents their cost and operational inputs as well as their policy attributes and memberships with asset groups. Additional worksheets with “Baseline” in the name include additional scenarios related to all or subset of Baseline resources.
Min Local Capacity Groups	Include min operational capacity that has to be maintained in local areas aggregated at the IOU level
Candidate Resources - Default	Includes all candidate resources across all zones. Represents their cost and operational inputs as well as their policy attributes and memberships with operational group and asset groups. Additional worksheets with “Baseline” in the name include additional scenarios related to all or subset of Candidate resources.
Resource Dispatch Groups	Includes details on operational groups. (A group of one or more resources that are similar operationally, are dispatched with their operational groups)
Min Build Groups	Includes all min build requirement for all or subset of candidate resources
Max Build Groups	Includes all max build requirement for all or subset of candidate resources
Candidate Shed DR	Includes Shed Dr candidate resource options and their attributes
Tx Constraints	Includes CAISO transmission constraints such as existing headrooms for FCDS, SSN and EODS deliverability periods
CAISO Tx Upgrades	Includes candidate upgrades potential and costs to expand CAISO Tx constraints
Tx Membership	Includes CAISO transmission memberships with resources and transmission upgrades with FCDS, SSN and EODS deliverability coefficients
Lists	Includes dropdown options defined in the workbook
Scenarios	Includes all scenarios within all worksheets
xlwings.conf	Includes paths to user’s RESOLVE python link and resolve folder directory

Additional details are also covered in the FAQ section. Comprehensive information on the key inputs and assumptions present in the Scenario Tool can be found in the Inputs & Assumptions document released by the CPUC. For users planning on comprehensively using the Model, a thorough reading of the I&A document is recommended.