sdom 0.0.1

A Python package for NREL open-source SDOM (Storage Deployment Optimization Model)

Storage Deployment Optimization Model (SDOM)

SDOM (Storage Deployment Optimization Model) is an open-source, high-resolution grid capacity-expansion framework developed by NREL. It’s purpose-built to optimize the deployment and operation of energy storage technologies, leveraging hourly temporal resolution and granular spatial representation of Variable Renewable Energy (VRE) sources such as solar and wind.

SDOM is particularly well-suited for figure out the required capacity to meet a carbon-free generation mix target by:

• 📆 Evaluating long-duration and seasonal storage technologies
• 🌦 Analyzing complementarity and synergies among diverse VRE resources
• 📉 Assessing curtailment and operational strategies under various grid scenarios

Table of contents

• HOW SDOM WORKS?
• KEY FEATURES
  • OPTIMIZATION SCOPE
  • NOTES ON MODEL EXPANSION
• PUBLICATIONS AND USE CASES OF SDOM
• SDOM EXAMPLE (Demonstration script)
• CONTRIBUTING GUIDELINES

How SDOM Works?

🔍 At its core, SDOM models the gap between electricity demand and fixed generation:

Inputs include time series data for:

• Load profiles
• Fixed generation (e.g., large hydropower, nuclear, and other must-run renewables)

Outputs include:

• The optimal technology portfolio capacity (PV solar, wind, storage types, thermal capacity) to reliably meet demand.
• Dispatch profiles for each technology, highlighting how resources are operated hour-by-hour
• Insights on operational metrics like VRE curtailment, storage cycling, and thermal usage

An illustrative figure below shows the flow from inputs to optimization results, enabling exploration of storage needs under varying renewable integration levels.

Key Features

⚙️

• Accurate Representation of Storage Technologies Diversity: SDOM is strongly focused in providing a framework able to represent different storage technologies by:

  • Representation of short, long an seassonal storage technologies,
  • Including charging/discharging capacity decoupling,
  • Optimization of both energy and power capacity,
  • Full temporal cronology.

• Temporal Resolution: Hourly simulations over a full year enable precise modeling of storage dynamics and renewable generation variability.

• Spatial Resolution: Fine-grained representation of VRE sources (e.g., solar, wind) captures geographic diversity and enhances system fidelity.

• Copper Plate Modeling: SDOM Model neglects transmission constraints to keep the model tractable from the computational standpoint. Future SDOM releases should include inter-regional transmission constraints.

• Fixed Generation Profiles: Nuclear, hydropower, and other non-variable renewables (e.g., biomass, geothermal) are treated as fixed inputs using year-long time series data.

  • Currently its beeing developed a modeling approach to include a Hydro modeling considering Monthly energy budgets in order to be able to represent the hydro flexibility.

• System Optimization Objective: Minimizes total system cost—including capital, fixed/variable O&M, and fuel costs—while satisfying user-defined carbon-free or renewable energy targets.

• Modeling approach: Formulated as a Mixed-Integer Linear Programming (MILP) model to allow rigorous optimization of investment and capacity decisions.

• Platforms:

  • SDOM was originally developed in GAMS (https://github.com/NREL/SDOM).

  • In order offer a full open-source solution also was developed this python package. This version requires python 3.10+.

• Solver Compatibility: Currently the SDOM python version is only compatible with open-source CBC solver. In this repo the windows executable for cbc is provided. You will need to provide the path of cbc solver to run SDOM as illustrated in our script demonstration

Optimization Scope

📉 SDOM performs cost minimization across a 1-year operation window using a copper plate assumption—i.e., no internal transmission constraints—making it computationally efficient while capturing major cost drivers. Conventional generators are used as balancing resources, and storage technologies serve to meet carbon or renewable penetration goals.

Notes on Model Expansion

While SDOM currently supports a 1-year horizon, multiyear analyses could provide deeper insights into how interannual variability affects storage needs. Chronological, simulation-based approaches are better suited for this but present significant computational challenges—especially at hourly resolution. Extending SDOM to support multiyear optimization is left as future work.

PUBLICATIONS AND USE CASES OF SDOM

📄

• Original SDOM paper:

  • Guerra, O. J., Eichman, J., & Denholm, P. (2021). Optimal energy storage portfolio for high and ultrahigh carbon-free and renewable power systems. Energy Environ. Sci., 14(10), 5132-5146. https://doi.org/10.1039/D1EE01835C.
  • NREL media relations (2021). Energy Storage Ecosystem Offers Lowest-Cost Path to 100% Renewable Power.

• SDOM GAMS version software registration

• Uses cases in the "Renewables in Latin America and the Caribbean" or RELAC initiative (Uruguay, Peru, El Salvador):

  • Guerra, O. J., et al. (2023). Accelerated Energy Storage Deployment in RELAC Countries. National Renewable Energy Laboratory (NREL).

• Webinar video:

  • Guerra, O. J., et al. (2022). Optimizing Energy Storage for Ultra High Renewable Electricity Systems. Conference for Colorado Renewable Energy society.

SDOM EXAMPLE (Demonstration script)

Please see an SDOM demo script on this github repo.

CONTRIBUTING GUIDELINES

💻

General Guidelines

• Follow PEP 8 for code style and formatting.
• Write clear, concise, and well-documented code.
• Add docstrings to all public classes, methods, and functions.
• Include unit tests for new features and bug fixes.
• Use descriptive commit messages.
• Open issues or discussions for significant changes before submitting a pull request.
• Ensure all tests pass before submitting code.
• Keep dependencies minimal and document any new requirements.
• Review and update documentation as needed.
• Be respectful and collaborative in all communications.

Please see a complete developers guide here: Developers Guide