Price taker model for DISPATCHES, Rehashed

.github/workflows/typos.toml

@@ -37,6 +37,9 @@ equil = "equil"
 astroid = "astroid"
 # delt == delta
 delt = "delt"
+# FOM for fixed operating and maintenance for DISPATCHES
+FOM = "FOM"
+fom = "fom"
 # Minimal Infeasible System
 mis = "mis"
 MIS = "MIS"

docs/reference_guides/apps/grid_integration/index.rst

@@ -20,6 +20,7 @@ wholesale electricity markets. For more information, please look at the introduc
    Bidder
    Tracker
    Coordinator
+   multiperiod/index
 
 Cite us
 ^^^^^^^

docs/reference_guides/apps/grid_integration/multiperiod/Price_Taker.rst

@@ -0,0 +1,55 @@
+Price Taker
+===========
+
+Price takers are companies or individuals who must accept market prices since they lack the market share
+to directly influence the market price. Likewise, it is assumed that a price taker's resource or energy
+system is small enough such that it does not significantly impact the market. When coupled with multi-period modeling,
+the price-taker model is able to synthesize grid-centric modeling with steady-state process-centric modeling, as
+depicted in figure below.
+
+.. |pricetaker| image:: images/pricetaker.png
+  :width: 1200
+  :alt: Alternative text
+  :align: middle
+
+|pricetaker|
+
+The following equations represent the multi-period price taker model, where :math:`d` are design decisions,
+:math:`u` are operating decisions, :math:`δ` are power decisions, :math:`s` are scenarios (timeseries/representative days),
+:math:`w` is weight/frequency, :math:`R` is revenue, :math:`π` is price data,
+:math:`C` is capital and operating costs, :math:`g` is the process model, and :math:`h` is the temporal constraint.
+
+    .. math::
+
+       max_{d,u, δ} = \sum_{s ∈ S} \sum_{t ∈ T} w_{s}[R(d,u_{s,t},δ_{s,t},π_{s,t}) - C(d,u_{s,t},δ_{s,t})]
+
+    .. math::
+
+       g(d,u_{s,t},δ_{s,t}) = 0; ∀_{s} ∈ S, t ∈ T
+
+    .. math::
+
+       h(d,u_{s,t},δ_{s,t},u_{s,t+1},δ_{s,t+1}) = 0; ∀_{s} ∈ S, t ∈ T
+
+
+The price taker multi-period modeling workflow involves the integration of multiple software platforms into the IDAES optimization model
+and can be broken down into two distinct functions, as shown in the figure below. In part 1, simulated or historical
+ISO (Independent System Operator) data is used to generate locational marginal price (LMP)
+signals, and production cost models (PCMs) are used to compute and optimize the time-varying dispatch schedules for each
+resource based on their respective bid curves. Advanced data analytics (RAVEN) reinterpret the LMP signals and PCM
+as stochastic realizations of the LMPs in the form of representative days (or simply the full-year price signals).
+In part 2, PRESCIENT uses a variety of input parameters (design capacity, minimum power output, ramp rate, minimum up/down time, marginal cost, no load cost, and startup profile)
+to generate data for the market surrogates. Meanwhile, IDAES uses the double loop simulation to integrate detailed
+process models (b, ii) into the daily (a, c) and hourly (i, iii) grid operations workflow.
+
+.. |hybrid_energy_system| image:: images/hybrid_energy_system.png
+  :width: 1200
+  :alt: Alternative text
+  :align: middle
+
+|hybrid_energy_system|
+
+.. module:: idaes.apps.grid_integration.multiperiod.price_taker_model
+
+.. autoclass:: PriceTakerModel
+  :members:

docs/reference_guides/apps/grid_integration/multiperiod/index.rst

@@ -0,0 +1,13 @@
+Multi-Period Modeling
+=====================
+
+Multi-period modeling can be used to simplify dynamic optimization problems
+by linking steady-state models over a time horizon with rate-limiting constraints.
+Therefore, sets of constraints at one temporal index will affect decisions taken
+at a different moment in time. These interactions can be used to model the relationship
+between the energy systems and wholesale electricity markets.
+
+.. toctree::
+    :maxdepth: 2
+
+    Price_Taker

idaes/apps/grid_integration/__init__.py

@@ -15,3 +15,8 @@
 from .coordinator import DoubleLoopCoordinator
 from .forecaster import PlaceHolderForecaster
 from .multiperiod.multiperiod import MultiPeriodModel
+from .multiperiod.price_taker_model import PriceTakerModel
+from .multiperiod.design_and_operation_models import (
+    DesignModel,
+    OperationModel,
+)

idaes/apps/grid_integration/multiperiod/design_and_operation_models.py

@@ -0,0 +1,120 @@
+#################################################################################
+# The Institute for the Design of Advanced Energy Systems Integrated Platform
+# Framework (IDAES IP) was produced under the DOE Institute for the
+# Design of Advanced Energy Systems (IDAES).
+#
+# Copyright (c) 2018-2023 by the software owners: The Regents of the
+# University of California, through Lawrence Berkeley National Laboratory,
+# National Technology & Engineering Solutions of Sandia, LLC, Carnegie Mellon
+# University, West Virginia University Research Corporation, et al.
+# All rights reserved.  Please see the files COPYRIGHT.md and LICENSE.md
+# for full copyright and license information.
+#################################################################################
+from functools import reduce
+from pyomo.environ import (
+    Var,
+    Param,
+    Binary,
+    Expression,
+    NonNegativeReals,
+    Constraint,
+)
+from pyomo.common.config import ConfigValue, In
+from idaes.core.base.process_base import declare_process_block_class
+from idaes.core.base.process_base import ProcessBlockData
+
+
+@declare_process_block_class("DesignModel")
+class DesignModelData(ProcessBlockData):
+    """
+    Class for containing design model ...
+    """
+
+    CONFIG = ProcessBlockData.CONFIG()
+    CONFIG.declare(
+        "model_func",
+        ConfigValue(
+            doc="Function that builds the design model",
+        ),
+    )
+    CONFIG.declare(
+        "model_args",
+        ConfigValue(
+            default={},
+            doc="Dictionary containing arguments needed for model_func",
+        ),
+    )
+
+    def build(self):
+        super().build()
+
+        self.config.model_func(self, **self.config.model_args)
+
+
+@declare_process_block_class("OperationModel")
+class OperationModelData(ProcessBlockData):
+    """
+    Class for containing design model ...
+    """
+
+    CONFIG = ProcessBlockData.CONFIG()
+    CONFIG.declare(
+        "model_func",
+        ConfigValue(
+            doc="Function that builds the design model",
+        ),
+    )
+    CONFIG.declare(
+        "model_args",
+        ConfigValue(
+            default={},
+            doc="Dictionary containing arguments needed for model_func",
+        ),
+    )
+
+    CONFIG.declare(
+        "declare_op_vars",
+        ConfigValue(
+            default=True,
+            domain=In([True, False]),
+            doc="Should op_mode, startup, shutdown vars be defined?",
+        ),
+    )
+    CONFIG.declare(
+        "append_lmp_data",
+        ConfigValue(
+            default=True,
+            domain=In([True, False]),
+            doc="Should LMP data automatically be appended to the model?",
+        ),
+    )
+
+    # noinspection PyAttributeOutsideInit
+    def build(self):
+        super().build()
+
+        # Build the model
+        if self.config.declare_op_vars:
+            self.op_mode = Var(
+                within=Binary,
+                doc="Binary var: 1 if the unit is operating, 0 otherwise",
+            )
+
+            self.startup = Var(
+                within=Binary,
+                doc="Binary var: 1 if the startup is initiated, 0 otherwise",
+            )
+
+            self.shutdown = Var(
+                within=Binary,
+                doc="Binary var: 1 if the shutdown is initiated, 0 otherwise",
+            )
+
+        if self.config.append_lmp_data:
+            self.LMP = Param(
+                initialize=1,
+                mutable=True,
+                doc="Parameter: Will be updated to LMP value at given time",
+            )
+
+        self.config.model_func(self, **self.config.model_args)