Merge branch 'system_level_control' of https://github.com/NREL/H2Integrate into system_level_control

Author: johnjasa

docs/_static/class_hierarchy.html

@@ -71,9 +71,14 @@ parts:
   - caption: Control
     chapters:
       - file: control/control_overview
-      - file: control/open-loop_controllers
-      - file: control/pyomo_controllers
-      - file: control/controller_demonstrations
+      - file: control/system_level_control/system_level_control
+        sections:
+          - file: control/system_level_control/control_classifier
+      - file: control/storage_level_control
+        sections:
+          - file: control/open-loop_controllers
+          - file: control/pyomo_controllers
+          - file: control/controller_demonstrations
   - caption: Demand
     chapters:
       - file: demand/demand_components

docs/_toc.yml

@@ -0,0 +1,3 @@
+# Storage-Level Control
+
+ADD

docs/control/storage_level_control.md

@@ -43,8 +43,17 @@ A dispatchable performance model represents anything that can receive a set poin
 ```
 
 ## Storage
-Storage is a unique control classifier because it assumes that within the model that energy isn't created or destroyed (minus some efficiency losses). While it's technically "dispatchable" in that it can receive and change its performance based on a set point it's handling within H2I is unique because it's attached to storage performance models, which is handled differently than converter performance models.
+Storage is a unique control classifier because it assumes that within the model that energy isn't created or destroyed (minus some efficiency losses). While it's technically "dispatchable" in that it can receive and change its performance based on a set point it's handling within H2I is unique because it's attached to storage performance models, which is handled differently than converter performance models. A converter model only has positive (or zero) `{commodity}_out`, whereas a storage model can have positive or negative `{commodity}_out`.
 
-The storage performance models that have the "storage" control classifier additionally require a storage-level controller in addition to the overarching system level controller. See the image below for reference. The storage-level controller takes in the system level-controller set points and outputs charge (negative) and discharge (positive) commands (storage-level set points) to the storage performance model.
+There are two types of cases for the storage control classifier:
+1. **with a storage controller**
+When the storage performance model is controlled with a storage-level controller (open-loop or feedback controlled), the system-level controller outputs combined demand, that is always positive to the storage-level controller. The demand is `{commodity}_in` from the technologies upstream of the storage that output the same commodity to the storage performance model and the `remaining_demand`.
 
-ADD IMAGE - wait until [PR # 731](https://github.com/NatLabRockies/H2Integrate/pull/731) comes in.
+2. **without a storage controller**
+The system-level controller outputs set points to the storage performance model which can be considered charge (negative) and discharge (positive) commands (storage-level set points) to the storage performance model, directly.
+
+
+```{figure} figures/storage.png
+:width: 85%
+:align: center
+```

docs/control/system_level_control/control_classifier.md

@@ -0,0 +1,10 @@
+# System-Level Control
+
+System-level control (SLC) within H2I is meant to operate to control the entire plant with performance and cost feedback driving the operation of the plant or system in a closed-loop. It acts as a supervisory controller, which can work with other technology level controllers.
+
+```{figure} figures/slc_basic.png
+:width: 70%
+:align: center
+```
+
+At a very basic level the SLC receives a demand. Based on that demand