openstudio-standards 0.2.16 → 0.2.17.rc1

data/lib/openstudio-standards/standards/ashrae_90_1_prm/docs/baseline_building_rotation_exception.md

@@ -0,0 +1,44 @@
+Check if the baseline model is exempted from the orientation requirements
+
+# ASHRAE 90.1-2019
+- G3.1 (5) Orientation. The *baseline building performance* shall be generated by simulating the *building* with its actual *orientation* and again after rotating the entire *building* 90, 180, and 270 degrees, then averaging the results. The *building* shall be modeled so that it does not shade itself.
+
+- G3.1 (5) Orientation Exceptions:
+  - If it can be demonstrated to the satisfaction of the *rating authority* that the *building orientation* is dictated by site considerations.
+  - *Buildings* where the *vertical fenestration area* on each *orientation* varies by less than 5%
+
+# Code Requirement Interpretation
+The code requires the baseline building performance to be the average value of the model facing four different orientations (0, 90, 180, 270).
+
+Exception shall be applied when site consideration approved by rating authority or the vertical fenestration area on each orientation varies by less than 5%.
+
+# Implementation Methodology
+At beginning of the baseline generation, a method `run_all_orientations` is called to flag the rotation.
+
+The `run_all_orientations` function implements the logics as followings:
+- Default value from `run_all_orients`.
+- Check fenestration area variances at each orientation - if any of the combination has a variation that is greater than 5%, then set the flag to true
+- Check user data from `userdata_building`. If the `is_rotation_exmpted` data is available, override the previous flag.
+
+## Key Ruby Methods
+`run_all_orientations`
+
+## Test Case Documentation
+
+### Test case 1:
+- Prototype: Small Office
+- User data folder: N/A
+- Summary:
+The case will require rotation on four orientations.
+
+### Test case 2:
+- Prototype: Small Office
+- User data folder: N/A
+- Summary:
+This case have 40% wwr on four orientations, rotation is still required.
+
+### Test case 3:
+- Prototype: Small Office
+- User data folder: *userdata_bro_01*
+- Summary:
+This case have have identical fenestration area for four orientation and user data set to exempt.

data/lib/openstudio-standards/standards/ashrae_90_1_prm/docs/check_pump_power_and_control.md

@@ -0,0 +1,71 @@
+# Pump power and control
+
+## Code requirements
+G3.1.3.5: Hot-water pumps
+The baseline building design hot-water pump power shall be **19 W/gpm**. The pumping
+system shall be modeled as primary-only with continuous variable flow and a minimum
+of 25% of the design flow rate. Hot-water systems serving **120,000 ft2** or more shall be
+modeled with variable-speed drives, and systems serving less than **120,000 ft2** shall be
+modeled as riding the pump curve.
+
+Exception to G3.1.3.5:
+The pump power for systems using purchased heat shall be **14 W/gpm**.
+
+G3.1.3.10 Chilled-Water Pumps (System 7, 8, 11, 12 and 13)
+Chilled-water systems shall be modeled as primary/secondary systems with constant-flow
+primary loop and variable-flow secondary loop. For systems with cooling capacity
+of **300 tons or more**, the secondary pump shall be modeled with variable-speed drives
+and a minimum flow of 25% of the design flow rate. For systems with **less than 300 tons**
+cooling capacity, the secondary pump shall be modeled as riding the pump curve. The baseline building constant-volume primary pump power shall be modeled as **9 W/gpm**,
+and the variable-flow secondary pump power shall be modeled as **13 W/gpm** at design
+conditions. For computer room systems using System 11 with an integrated fluid economizer,
+the baseline building design primary chilled-water pump power shall be increased
+by **3 W/gpm** for flow associated with the fluid economizer.
+
+Exception to G3.1.3.10
+For systems using purchased chilled water, the building distribution pump shall be modeled
+with variable-speed drive, a minimum flow of 25% of the design flow rate, and a pump power
+of **16 W/gpm**.
+
+G3.1.3.11 Heat Rejection (Systems 7, 8, 11, 12 and 13)
+The baseline building design condenser-water pump power shall be **19 W/gpm** and modeled as constant volume.
+For computer room systems using System 11 with an integrated fluid economizer, the baseline building design condenser-water-pump power shall be increased by **3 W/gpm** for flow associated with the fluid economizer.
+Each chiller shall be modeled with separate condenser-water and chilled-water pumps interlocked to operate with the associated chiller.
+
+#### key functions
+ashrae_90_1_prm.PlantLoop.rb: plant_loop_apply_prm_baseline_pump_power
+Standards.PlantLoop.rb: plant_loop_apply_prm_baseline_pumping_type
+    - Sub-function: plant_loop_apply_prm_baseline_hot_water_pumping_type
+    - Sub-function: plant_loop_apply_prm_baseline_chilled_water_pumping_type
+    - Sub-function: plant_loop_apply_prm_baseline_condenser_water_pumping_type
+
+#### Parameters:
+Pump power constants set in PlantLoop class:
+```ruby
+HOT_WATER_PUMP_POWER = 19 # W/gpm
+HOT_WATER_DISTRICT_PUMP_POWER = 14 # W/gpm
+CHILLED_WATER_PRIMARY_PUMP_POWER = 9 # W/gpm
+CHILLED_WATER_SECONDARY_PUMP_POWER = 13 # W/gpm
+CHILLED_WATER_DISTRICT_PUMP_POWER = 16 # W/gpm
+CONDENSER_WATER_PUMP_POWER = 19 # W/gpm
+```
+Pump curve coefficients used to defining the pump type
+```ruby
+when 'Riding Curve'
+  coeff_a = 0.0
+  coeff_b = 3.2485
+  coeff_c = -4.7443
+  coeff_d = 2.5294
+when 'VSD No Reset'
+  coeff_a = 0.0
+  coeff_b = 0.5726
+  coeff_c = -0.301
+  coeff_d = 0.7347
+```
+
+### Limitations
+
+- The code implemented a primary and secondary loop configuration for chilled water loop. The primary loop has chiller at the supply side and a perfect heat exchanger at the demand side. The secondary loop has the heat exchanger at the supply side and coils at the demand side. In this configuration, each chiller will interlock with a pump. However, the pump operation strategy is not implemented yet.
+- The integrated water economizer for system type 11 is not implemented.
+
+### PRM-RM

data/lib/openstudio-standards/standards/ashrae_90_1_prm/docs/dcv.md

@@ -0,0 +1,68 @@
+# DCV for Appendix G baseline generation
+
+Xuechen (Jerry) Lei, PNNL
+Update: 06/29/2022
+
+## Code requirements
+
+### 90.1-2019
+
+#### 6.4.3.8 Ventilation Controls for High-Occupancy Areas
+
+Demand control ventilation (DCV) is required for spaces larger than 500 ft<sup>2</sup> and with a design occupancy for ventilation of >= 25 ppl/kft<sup>2</sup> of floor area and served by systems with one or more of the following:
+
+- a. Air economizer
+- b. Automatic modulating control of outdoor air damper
+- c. **Design outdoor airflow greater than 3000 cfm**
+
+Exceptions to 6.4.3.8
+
+1. Systems with exhaust air energy recovery complying with, and where required by, Section 6.5.6.1.
+2. Multiple-zone systems without DDC of individual zones communicating with a central control panel.
+3. **Systems with a design outdoor airflow less than 750 cfm.**
+4. Spaces where >75% of the space design outdoor airflow is required for makeup air that is exhausted from the space or transfer air that is required for makeup air that is exhausted from other spaces.
+5. Spaces with one of the following occupancy categories as defined in ASHRAE Standard 62.1: correctional cells, daycare sickrooms, science labs, barbers, beauty and nail salons, and bowling alley seating.
+
+**Note that in most cases, such systems will always have economizer. As a result, the deciding conditions for DCV mandate are mostly: 1. > 500 ft<sup>2</sup>; 2. >= 25 ppl/kft<sup>2</sup>; and 3. design outdoor airflow > 750 cfm.**
+
+#### G3.1.2.5 Ventilation
+
+Minimum ventilation system outdoor air intake flow shall be the same for the proposed design and baseline building design.
+
+Exception to G3.1.2.5
+
+1. When modeling demand control ventilation in the proposed design in systems with outdoor air capacity less than or equal to 3000 cfm serving areas with an average design capacity of **100 people per 1000 ft<sup>2</sup> or less.**
+2. ...
+
+**We checked with 90.1 committee that in this exception, the relationship between the two conditions should be "or".**
+
+### PRM-RM
+
+#### 3.5.5.4 Minimum Outdoor Air Ventilation Rate
+
+|               |                                                                                                                                                                   |
+| ------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| Applicability | All HVAC zones                                                                                                                                                    |
+| Definition    | The minimum quantity of outdoor ventilation air that must be provided to the space when it is occupied                                                            |
+| Units         | cfm or cfm/ft²                                                                                                                                                    |
+| Input         | Restrictions As designed                                                                                                                                          |
+| Baseline      | Building Minimum ventilation system outdoor air intake flow shall be the same for the proposed and baseline building designs. Except in the following conditions: |
+
+- Demand control ventilation shall not be modeled in zones served by systems with outdoor air less than 3000 cfm **and** occupant density of 100 people per 1000 ft<sup>2</sup> or less.
+- ...
+
+**According to the clarification in previous section, the 'and' in above exception should also be 'or'.**
+
+## Code requirements interpretation
+
+The high level idea behind Appendix G DCV requirements is: if DCV is not required per 90.1 Section 6.4.3.8, but the proposed model has it, then Appendix G wants to credit the DCV-introduced energy saving by removing DCV in the baseline model.
+
+If the space has conditions such as a high occupancy density (>= 25 ppl/kft<sup>2</sup>) and high design outdoor airflow (>= 3000 cfm), then according to 90.1 6.4.3.8, DCV is mandatory. In this case (i.e. DCV is mandatory according to 90.1 6.4.3.8), Appendix G baseline and proposed model should both have DCV. As a result, energy savings caused by DCV is not credited for Appendix G. One thing to note is, "both having DCV" is based on exception 1, however, the conditions specified for high occupancy density (>= 100 ppl/kft<sup>2</sup>) in this exception is different from 90.1 6.4.3.8 (>= 25 ppl/kft<sup>2</sup>), and other conditions used to unsatisfy this exception (outdoor air less than 3000 cfm or occupant density of 100 people per 1000 ft<sup>2</sup> or less) is different from the conditions to require mandatory DCV in 90.1 6.4.3.8. As a result, there may be a case where DCV is mandatory per 90.1, but Exception 1 of Appendix G 3.1.2.5 is not met. For instance, when design OA flow is 3500 cfm and occupant density is 50 ppl/kft<sup>2</sup>, DCV is mandatory according to 90.1 6.4.3.8, while according to PRM-RM, DCV shall not be modeled.
+
+If the space is not required to have DCV according to 90.1 6.4.3.8, but the proposed model has DCV, then we would like to credit the energy savings of DCV for the proposed model under appendix G. To make this happen, we would delete the DCV in the baseline model. The condition difference in the above bullet also has impact here. For instance, due to satisfying exception of 90.1 6.4.3.8, DCV is not required, and in the meantime, because of a large design OA flow of 4000 cfm, exception 1 of Appendix G 3.1.2.5 is not met, so baseline and proposed model need to have the same ventilation OA flow. In such a case, whether DCV is implemented in the proposed model or not, we will keep baseline the same (do nothing for baseline). If DCV is mandatory but not implemented in the proposed model, an error will be raised.
+
+For the five exceptions of 90.1 6.4.3.8, we will not implement the checking of them under Appendix G. Instead, we will ask the user to provide such information of if the model meets any exception for not having mandatory DCV.
+
+## Implementation design summary diagram
+
+![Appendix G DCV implementation diagram](./dcv_implementation.png)

data/lib/openstudio-standards/standards/ashrae_90_1_prm/docs/elevators.md

@@ -0,0 +1,14 @@
+Elevators
+
+# ASHRAE 90.1-2019
+## Section G3.1.16 Elevators
+Where the proposed design includes elevators, the baseline building design shall be modeled to include the elevator cab motor, ventilation fans, and lighting power. The elevator motor use shall be modeled with the same schedule as the proposed design. When included in the proposed design, the baseline elevator cab ventilation fan shall be 0.33 W/cfm and the lighting power density shall be 3.14 W/ft2; both operate continuously.
+
+# Code Requirement Interpretation
+The code requirement is straightforward, so are the exception.
+
+# Implementation
+The characteristics of the proposed model elevator(s) are provided by the user using the user data CSV file which includes the each elevator car weight, rated load, counter weight of the car, speed of the car, number of stories served by the elevator, the number of similar elevators, the floor area occupied the elevator, and the ventilation flow rate. The BHP and elevator power are calculated according to Section G3.1.16, the baseline elevator power is used in place of the proposed one (which can be through an electric equipment object or an exterior equipment fuel object). Process loads such as ventilation and lighting are modeled separately and as they are supposed to be modeled as operating continuously.
+
+# Key Ruby Methods
+- `model_add_prm_elevators`: Add baseline elevators based on user data

data/lib/openstudio-standards/standards/ashrae_90_1_prm/docs/exhaust_air_energy_recovery.md

@@ -0,0 +1,36 @@
+Exhaust Air Energy Recovery
+
+# ASHRAE 90.1-2019
+## Section G3.1.2.10 Exhaust Air Energy Recovery
+
+Individual fan systems that have both a design supply air capacity of 5000 cfm or greater and have a minimum design outdoor air supply of 70% or greater shall have an energy recovery system with at least 50% enthalpy recovery ratio. Fifty percent enthalpy recovery ratio shall mean a change in the enthalpy of the outdoor air supply equal to 50% of the difference between the outdoor air and return air at design conditions. Provision shall be made to bypass or control the heat recovery system to permit air economizer operation, where applicable.
+
+If any of these exceptions apply, exhaust air energy recovery shall not be included in the baseline
+building design:
+1. Systems serving spaces that are not cooled and that are heated to less than 60°F.
+2. Systems exhausting toxic, flammable, or corrosive fumes or paint or dust. This exception
+shall only be used if exhaust air energy recovery is not used in the proposed design.
+3. Commercial kitchen hoods (grease) classified as Type 1 by NFPA 96. This exception shall
+only be used if exhaust air energy recovery is not used in the proposed design.
+4. Heating systems in Climate Zones 0 through 3.
+5. Cooling systems in Climate Zones 3C, 4C, 5B, 5C, 6B, 7, and 8.
+6. Where the largest exhaust source is less than 75% of the design outdoor airflow. This exception
+shall only be used if exhaust air energy recovery is not used in the proposed design.
+7. Systems requiring dehumidification that employ energy recovery in series with the cooling
+coil. This exception shall only be used if exhaust air energy recovery and series-style
+energy recovery coils are not used in the proposed design.
+
+# Code Requirement Interpretation
+The code requirement is straightforward, so are the exception.
+
+# Implementation
+The requirement poses one main challenge: EnergyPlus/OpenStudio doesn't support enthalpy recovery ratio (ERR) as a modeling input, so the effectiveness associated with a specific enthalpy recovery ratio have to be determined. There is no direct conversion from ERR to effectiveness as the ERR depends on specific design conditions which are not prescribed either by the rating standard or 90.1. PNNL did some preliminary research using data from one manufacturer to derive reasonable effectiveness values from the code required 50% ERR. The findings were implemented in OpenStudio-Standards through this [pull request](https://github.com/NREL/openstudio-standards/pull/1165) when adding 90.1-2019 version of the prototype building models. The same regressions were used to make generated baseline model comply with this requirement.
+
+Exception 1 is automatically handled by checking the thermostats of all zones served by an air loop, if at least one of them is heated to less than 60F, an ERV is not modeled in the baseline model. Exception 2, 3, 6, and 7 are handled through user data inputs. Exception 5 is ignored since all baseline models in Appendix G are modeled as cooled. Exception 4 is automatically handled by code and relates to heating and ventilation only systems in hot climate zones.
+
+# Key Ruby Methods
+- `air_loop_hvac_apply_energy_recovery_ventilator_efficiency`: Set effectiveness value of an ERV's heat exchanger
+- `air_loop_hvac_energy_recovery_ventilator_flow_limit`: Determine the airflow limits that govern whether or not an ERV is required (this is where the exceptions are evaluated, if none apply the limit is set to 5000 cfm)
+- `heat_exchanger_air_to_air_sensible_and_latent_minimum_effectiveness`: Defines the minimum sensible and latent effectiveness of the heat exchanger
+- `heat_exchanger_air_to_air_sensible_and_latent_design_conditions`: Determine the heat exchanger design conditions for a specific climate zones
+- `heat_exchanger_air_to_air_sensible_and_latent_enthalpy_recovery_ratio`: Determine the required enthalpy recovery ratio (currently defaulted to 0.5)

data/lib/openstudio-standards/standards/ashrae_90_1_prm/docs/f_c_factors.md

@@ -0,0 +1,19 @@
+F/C-factors
+
+# ASHRAE 90.1-2019
+See F- and C-factor requirements from Table G3.4-1 through -8.
+
+# Implementation
+
+# Key Ruby Methods
+## Existing
+* `model_add_construction`: this method creates a construction from the openstudio standards dataset, it was modified to create the appropriate F/C factor construction objects instead of regular constructions
+* `model_find_and_add_construction`: this method helps find a particular construction and add it to the model after modifying the insulation value if necessary; it was modified to accept a another argument, `surface` which can be used for surface specific construction such as F/C-factor constructions
+* `model_apply_prm_construction_types` this method goes through the default construction sets and hard-assigned constructions and clone the existing constructions and set their intended surface type and standards construction type per the PRM; The code did not cover all pertinent outside boundary condition which prevented the creation of correct assignment of constructions to surface with specific outside boundary conditions
+* `model_apply_standard_constructions`: this method applies the standard construction to each surface in the model, based on the construction type currently assigned; missing outside boundary condition type related to ground surfaces were added  
+## New
+* `construction_set_surface_slab_f_factor`: set the surface specific F-factor parameters of a construction
+* `construction_set_surface_underground_wall_c_factor`: set the surface specific C-factor parameters of a construction
+* `model_update_ground_temperature_profile`: update ground temperature profile based on the weather file specified in the model
+* `model_add_design_days_and_weather_file`: the content of this method was used in multiple other method, so, in order to avoid code duplicate, it was moved to this method which adds the design days and weather file for the specified climate zone 
+ 

data/lib/openstudio-standards/standards/ashrae_90_1_prm/docs/fan_power_credits.md

@@ -0,0 +1,15 @@
+Fan Power Credits
+
+# ASHRAE 90.1-2019
+Note 1 and 2 under Table G3.1.2.9 indicate that the baseline fan brake horsepower adjustment factor, A, is calculated according to Section 6.5.3.1.1 using the pressure-drop adjustment from the proposed design and the design flow rate of the baseline building system. The pressure-drop adjustment for evaporative coolers or heat recovery devices that are not required in the baseline system by Section G3.1.2.10.
+
+# Code Requirement Interpretation
+Section 6.5.3.1.1 include credits but also deductions. Following an internal discussion we concluded that the intent of Appendix G should be to base the deduction on the baseline building design and not the proposed design.
+
+# Implementation
+Fan power credits are provided by the user via the `userdata_airloop_hvac.csv` and `userdata_zone_hvac.csv` files. The deductions are only applicable to system 6 and 8 and are handled in the code in `air_loop_hvac_fan_power_limitation_pressure_drop_adjustment_brake_horsepower()`. Credits and deduction are stored as an `additionaProperty` at the `ThermalZone` and `AirLoopHVAC` level. The baseline fan power credits/deductions are calculated for each zone as follows: Az = sum(PD_sum * CFM_d_baseline/4131), where CFM_d_baseline is the baseline __zone__ design air flow and PD_sum. The system A is obtained by summing all the zone Az.
+
+# Key Ruby Methods
+* `thermal_zone_get_fan_power_limitations()`: calculate the fan power credits/deductions for a zone
+* `air_loop_hvac_fan_power_limitation_pressure_drop_adjustment_brake_horsepower`: calculate the fan power limitation pressure drop adjustment (expressed in terms of BHP)
+* `handle_zone_hvac_user_input_data`: use the user-defined CSV files to assign fan power credits to each zone

data/lib/openstudio-standards/standards/ashrae_90_1_prm/docs/preheat_coil.md

@@ -0,0 +1,59 @@
+Preheat coil requirements
+
+# ASHRAE 90.1-2019
+
+G3.1.3.7 Preheat Coils (System 5 through 8)
+The baseline system shall be modeled with a preheat coil controlled to a fixed set point of 20F less than the design room heating temperature set point.
+
+# PRM-Reference Manual:
+For baseline system 5 through 8, the baseline will be modeled with preheat coil controlled to a fixed setpoint 20 F less than the design zone heating temperature setpoint. If there are multiple zone heating setpoints, the preheat setpoint will be determined by the zone with the highest heating temperature setpoint.
+
+The preheat coil capacity will be oversized by 25%. Sizing calculation shall be based on the heating design day and cooling design day conditions, as defined in Section 3.1.5 of this document. Oversizing would be carried out at zone level where the sizing parameters would be applied to the zone design's heating coil loads.
+
+The heating source for baseline system 5 and 7 will be hydronic. Buildings with baseline system 6 and 8 will be modeled with electric resistance preheat coils.
+
+The coil efficiency is not applicable to electric coils
+
+# Requirement change:
+## ASHRAE 90.1-2013 Appendix G:
+G3.1.2.4 Preheat Coils: If the HVAC system in the proposed design has a preheat coil and a preheat coil can be modeled in the baseline system, the baseline system shall be modeled with a preheat coil controlled in the same manner as the proposed design.
+
+## ASHRAE 90.1-2016, 2019 Appendix G:
+G3.1.3.19: System 5 through 8, The baseline system shall be modeled with a preheat coil controlled to a fixed setpoint 20F less than the design room heating temperature set point.
+
+# Key Ruby Methods
+
+*Standards.Model.rb*
+```ruby
+# Template method for adding a setpoint manager for a coil control logic to a heating coil.
+# ASHRAE 90.1-2019 Appendix G.
+def model_set_central_preheat_coil_spm(model, thermal_zones, coil)
+	return true
+end
+```
+This implementation is overriden in the subclass *ashrae_90_1_prm.Model.rb*
+
+```ruby
+def model_set_central_preheat_coil_spm(model, thermal_zones, coil)
+	# below is the sudo code
+	coil_name = coil.name.get.to_s
+
+	max_heat_setpoint = 0.0
+	thermalZone.each do |zone|
+		# Get the thermalstat heating setpoint of each zone
+		# Reset the max_heat_setpoint if a zone has a higher heating setpoint value
+	end
+
+	max_heat_setpoint_f = convert(max_heat_setpoint, 'C', 'F')
+	preheat_setpoint_f = max_heat_setpoint_f - 20 # required to be 20F lower than the max heat setpoint
+	preheat_setpoint_c = convert(preheat_setpoint_f, 'F', 'C')
+
+	schedule = add_constant_schedule(preheat_setpoint_c)
+
+	# add a new_setpointManager_scheduled
+	# add the schedule to the new setpoint manager scheduled.
+	# add the new setpoint manager to the coil.
+end
+```
+
+Currently, the method is only being called when executing system type 5, 6, 7, and 8 generation routines.

data/lib/openstudio-standards/standards/ashrae_90_1_prm/docs/pump_power_control.md

@@ -0,0 +1,46 @@
+Pump power and control requirements
+
+# ASHRAE 90.1-2019
+
+## G3.1.3.5 Hot-Water Pumps
+The baseline building design hot-water pump power shall be 19 W/gpm. The pumping system shall be modeled as primary-only with continuous variable flow and a minimum of 25% of the design flow rate. Hot-water systems serving 120,000 ft2or more shall be modeled with variable-speed drives, and systems serving less than 120,000 ft2 shall be modeled as riding the pump curve. 
+
+### Exception to G3.1.3.5
+The pump power for systems using purchased heat shall be 14 W/gpm.
+
+## G3.1.3.10 Chilled-Water Pumps (Systems 7, 8, 11, 12, and 13)
+Chilled-water systems shall be modeled as primary/secondary systems with constantflow primary loop and variable-flow secondary loop. For systems with cooling capacity of 300 tons or more, the secondary pump shall be modeled with variable-speed drives and a minimum flow of 25% of the design flow rate. For systems with less than 300 tons cooling capacity, the secondary pump shall be modeled as riding the pump curve. The baseline building constant-volume primary pump power shall be modeled as 9 W/gpm, and the variable-flow secondary pump power shall be modeled as 13 W/gpm at design conditions. For computer room systems using System 11 with an integrated fluid economizer, the baseline building design primary chilled-water pump power shall be increased by 3 W/gpm for flow associated with the fluid economizer.
+
+### Exception to G3.1.3.10
+For systems using purchased chilled water, the building distribution pump shall be modeled with variable-speed drive, a minimum flow of 25% of the design flow rate, and a pump power of 16 W/gpm.
+
+## G3.1.3.11 Heat Rejection (Systems 7, 8, 11, 12, and 13)
+The baseline building design condenser-water pump power shall be 19W/gpm and modeled as constant volume. For computer room systems using System 11 with an integrated fluid economizer, the baseline building design condenser water-pump power shall be increased by 3W/gpm for flow associated with the fluid economizer.
+Each chiller shall be modeled with separate condenser-water and chilled-water pumps interlocked to operate with the associated chiller.
+
+# Requirement change:
+## ASHRAE 90.1-2013 Appendix G:
+### G3.1.3.5 Hot-Water Pumps:
+The baseline building design hot-water pump power shall be 19 W/gpm. The pumping system shall be modeled as primary-only with continuous variable flow. Hot-water systems serving 120,000 ft2 or more shall be modeled with variable-speed drives, and systems serving less than 120,000 ft2 shall be modeled as riding the pump curve.
+
+Exceptions: The pump power for systems using purchased heat shall be 14 W/gpm.
+
+### G3.1.3.10 Chilled-Water Pumps (System 7, 8 and 11)
+The baseline building design pump power shall be 22 W/gpm. Chilled-water systems with a cooling capacity of 300 tons or more shall be modeled as primary/secondary systems with variable-speed drives on the secondary pumping loop. Chilled-water pumps in systems serving less than 300 tons cooling capacity shall be modeled as a primary/secondary systems with secondary pump riding the pump curve. For computer room systems using System 11 with an integrated water-side economizer, the baseline building design primary chilled-water pump power shall be increased 5 W/gpm for flow associated with the water-side economizer.
+
+Exceptions: The pump power for systems using purchased chilled water shall be 16 W/gpm.
+
+### G3.1.3.11 Heat Reject (System 7, 8, 9, 12, and 13)
+The baseline building design condenser-water pump power shall be 19 W/gpm. For computer room systems using System 11 with an integrated water-side economizer, the baseline building design condenser water-pump power shall be increased 5 W/gpm for flow associated with the water-side economizer. Each chiller shall be modeled with separate condenser water and chilled-water pumps interlocked to operate with the associated chiller.
+
+## ASHRAE 90.1-2016, 2019 Appendix G:
+G3.1.3.19: System 5 through 8, The baseline system shall be modeled with a preheat coil controlled to a fixed setpoint 20F less than the design room heating temperature set point.
+
+# Key Ruby Methods
+
+*Standards.Model.rb*
+```ruby
+plant_loop_apply_prm_baseline_pump_power()
+plant_loop_apply_prm_baseline_pumping_type()
+```
+```

data/lib/openstudio-standards/standards/ashrae_90_1_prm/docs/return_air_type.md

@@ -0,0 +1,31 @@
+Return Air Type
+
+# ASHRAE 90.1-2019 PRM Reference Manual
+For baseline building systems 1 and 2, the return air path shall be direct-to-unit. For baseline building systems 3 through 8 and 11 through 13 and when the proposed design is direct-to-unit, the baseline building shall be ducted return, otherwise the baseline building return air path shall be the same as proposed design.
+
+# Implementation
+For each zone:
+
+* Retrieve the type of return used by the HVAC system serving the zone
+  * If the zone is served by air loops
+    * ignore air loop-based DOAS
+    * if air loop uses a return plenum -> return_plenum
+    * if air loop uses a return path -> ducted_return
+  * If the zone is served by zonal systems
+    * direct-to-unit since zonal systems cannot be connected to return plenum objects
+* Using additional properties, set the type of return as one of the following: return_plenum, ducted_return, direct-to-unit
+* Using additional properties, set the name of the plenum zone used when return_plenum is specified
+
+Once the systems have been created:
+
+* Using the zone design air flow rate and previously added additional properties determine the dominant return air configuration (the most dominant ones being the one with the most air flow)
+* All system are by default assumed to be ducted_return/direct-to-unit (using the zone mixer object) but if return_plenum ends up being the dominant one, pass the appropriate argument to the method creating the systems
+
+To simplify reporting at that point, use `ducted_return_or_direct_to_unit` and `return_plenum` as the additional property field.
+
+# Key Ruby Methods 
+## New
+* `model_determine_baseline_return_air_type`: determine the baseline return air type associated with each zone
+* `model_identify_return_air_type`: identify the return air type associated with each thermal zone
+* `air_loop_hvac_return_air_plenum`: determine if the air loop has a return air plenum 
+ 

data/lib/openstudio-standards/standards/ashrae_90_1_prm/docs/set_baseline_wwr.md

@@ -0,0 +1,191 @@
+Set window to wall ratio in the baseline model
+
+# ASHRAE 90.1-2019
+- G3.1 (5) Baseline c: Vertical Fenestration Areas: For building area types included in the Table G3.1.1-1, vertical fenestration areas for new buildings and additions shall equal that in Table G3.1.1-1 based on the area of gross above-grade walls that separate conditioned spaces and semiheated spaces from the exterior. 
+- G3.1 (5) Baseline c: Where a building has multiple building area types, each type shall use the values in the table. 
+- G3.1 (5) Baseline c: The vertical fenestration shall be distributed on each face of the building in the same proportion as in the proposed design. 
+- G3.1 (5) Baseline c: For building areas not shown in Table G3.1.1-1, vertical fenestration areas for new building and additions shall equal that in the proposed design or 40% of gross above-grade wall area, whichever is smaller, and shall be distributed on each face of the building in the same proportions in the proposed design.
+- G3.1 (5) Baseline c: ([addendum_l](https://www.ashrae.org/file%20library/technical%20resources/standards%20and%20guidelines/standards%20addenda/90_1_2019_l_20201030.pdf)): If this would cause the combined vertical fenestration and opaque door area on a given face to exceed the gross above-grade wall area on that face, then the vertical fenestration area on other faces shall be increased in proportion to the gross above-grade wall area of these faces such that the total baseline building vertical fenestration area is equal to that calculated following Table G3.1.1.-1.
+- G3.1 (5) Baseline c: The fenestration area for an existing building shall equal the existing fenestration area prior to the proposed work and shall be distributed on each face of the building in the same proportions as the existing building.
+
+# Code Requirement Interpretation
+1. Fenestration area shall be calculated based on the area of gross above-grade walls that separate conditioned spaces and semiheated spaces from the exterior
+2. If the window to wall ratio building type (wwr_building_type) can be found in Table G3.1.1-1, then the baseline window to wall ratio shall equal to the values specified in the table by proportionally decrease or increase the fenestration area.
+3. If the wwr_building_type cannot be found in the Table or it is other type, the baseline window to wall ratio shall equal to 40% or proposed window to wall ratio, whichever is smaller.
+4. Multiple wwr_building_types in a building shall use the values in the table correspondingly.
+5. If the fenestration area increase exceeds the host wall surfaces, then the residual shall be distributed to the other wall surfaces proportionally to its wall surface area
+6. Existing building shall remain the fenestration area the same as the existing fenestration area prior to the proposed work
+
+# Implementation Methodology
+- For `space_group` in `wwr_building_type`
+    - calculate total wall area `wall_m2 = calculate_wall_area(space_group)`
+    - calculate total wall area of walls has fenestration subsurfaces `fene_only_wall_m2 = calculate_fene_only_wall_area(space_group)`
+    - calculate total window area `wind_m2 = calculate_total_wind_area(space_group)`
+    - get the window to wall ratio (wwr) limit from Table 3.1.1-1 `wwr_lim = table_3.1.1-1(wwr_building_type)`
+    - calculate multiplier `multiplier = wwr_lim / (wind_m2 / wall_m2)`
+    - For `space` in `space_group`:
+      - For `surface` in `space.surfaces` where `surface_boundary_condition == 'Outdoor' && surfaceType=='Wall'`:
+        - set reduction ratio `reduction_ratio = 1.0` 
+        - calculate the window to wall ratio of the surface `surface_wwr = get_wwr_of_a_surface`
+        - if reduction is requested `multiplier < 1.0`
+          - reduction ratio is set to `1.0 - multiplier`
+          - call function to shrink the fenestration towards centroid `sub_surface_reduce_area_by_percent_by_shrinking_toward_centroid`
+        - elsif `wwr_building_type == 'all others'`
+          - reduction ratio set to `1.0`
+          - do nothing
+        - else
+          - calculate maximum fenestration area that wall surfaces with fenestration can reach `max_wwr = fene_only_wall_m2 * 0.9 / wall_m2` (Note: 90% wwr is the upper limit for each surface in OpenStudio standard)
+          - if the wwr limit is greater than max wwr `max_wwr < wwr_lim`
+            - if the surface has no fenestration `if surface_wwr == 0` (Note: In this case, it is required to add new fenestration to the surface)
+              - Add window to the surface by a calculated ratio `surface.setWindowToWallRatio(1.0 + (wwr_lim*wall_m2 - max_wwr*wall_m2)/(wall_m2-fene_only_wall_m2))`
+            - else: (Note: In this case, it is required to maximize the fenestration area in this surface to 90% wwr)
+              - Set window to wall ratio to 90% `surface.setWindowToWallRatio(0.9)`
+          else
+            - if the surface has no fenestration `if surface_wwr == 0`
+              - Do nothing
+            - else:
+              - Set a new window to wall ratio to the surface `surface.setWindowToWallRatio(surface_wwr * multiplier)`
+
+## Key Ruby Methods
+The function `get_wwr_reduction_ratio` implements the logic for calculating the reduction ratio `reduction_ratio` and `surface_adjust_fenestration_in_a_surface` implements the logics to adjust the window to wall ratio for a surface
+
+The implementation of both functions can be found in the `ashrae_90_1_prm.Model.rb`
+
+## Notes:
+The function works well with cases where WWR reduction is needed. For WWR increase to meet Table G3.1.1-1 values, the function's limitation is listed below:
+1. The function will remove all windows in the surface then add a new window to meet the required WWR.
+2. The function will keep the existing doors but there could be cases the location of door overlaps with the new window.
+
+In addition, when increasing the WWR requires adding windows to surfaces with no windows, the function will not adding any windows to spaces tagged as plenum and/or used as a AirLoopSupplyPlenum or AirLoopReturnPlenum. 
+
+## Test Case Documentation
+
+### Test case 1:
+- Prototype: Small Office
+- User data folder: */userdata_default_test*
+- Summary:
+
+The target WWR is 19% and the test prototype has WWR of 21.20%. 
+
+A regular WWR reduction shall be applied in this case to set the WWR in the baseline model to 19%.
+
+### Test case 2:
+- Prototype: Small Office - WWR adjusted.
+- User data folder: */userdata_default_test*
+- Summary:
+- 
+  Test prototype:
+
+|                       | Total  | North | East  | South | West  |
+|-----------------------|--------|-------|-------|-------|-------|
+| Wall Area (m2)        | 281.51 | 84.45 | 56.30 | 84.45 | 56.30 |
+| Window Area (m2)      | 28.15  | 8.44  | 5.63  | 8.44  | 5.63  |
+| Window-Wall Ratio (%) | 10%    | 10%   | 10%   | 10%   | 10%   |  
+
+The target WWR is 19%. The test prototype has WWR of 10% (10% for every surface).
+
+A regular WWR increase shall be applied in this case to set the WWR in the baseline model to 19% for every surface.
+
+Baseline:
+
+|                       | Total  | North | East  | South | West  |
+|-----------------------|--------|-------|-------|-------|-------|
+| Wall Area (m2)        | 281.51 | 84.45 | 56.30 | 84.45 | 56.30 |
+| Window Area (m2)      | 53.49  | 16.05 | 10.70 | 16.05 | 10.70 |
+| Window-Wall Ratio (%) | 19%    | 19%   | 19%   | 19%   | 19%   |  
+
+### Test case 3:
+- Prototype: Small Office - WWR adjusted.
+- User data folder: */userdata_default_test*
+- Summary:
+
+Test prototype:
+
+|                       | Total  | North | East  | South | West  |
+|-----------------------|--------|-------|-------|-------|-------|
+| Wall Area (m2)        | 281.51 | 84.45 | 56.30 | 84.45 | 56.30 |
+| Window Area (m2)      | 5.63   | 0.0   | 0.0   | 0.0   | 5.63  |
+| Window-Wall Ratio (%) | 2%     | 0%    | 0%    | 0%    | 10%   |  
+
+In this case, the WWR shall be increased to 19% however, the maximum WWR by expanding windows in West facade only is 17.7%, about 1.3% smaller than the required by the code.
+The function shall increase the rest facades proportionally to meet the overall 19% WWR target.
+
+Baseline:
+
+|                       | Total  | North | East  | South | West  |
+|-----------------------|--------|-------|-------|-------|-------|
+| Wall Area (m2)        | 281.51 | 84.45 | 56.30 | 84.45 | 56.30 |
+| Window Area (m2)      | 53.49  | 1.06  | 0.7   | 1.06  | 50.67 |
+| Window-Wall Ratio (%) | 19%    | 1.25% | 1.25% | 1.25% | 90%   |  
+
+### Test Case 4
+- Prototype: Mid Apartment
+- User data folder: */userdata_default_test*
+- Summary:
+
+Test prototype:
+
+|                       | Total   | North  | East   | South  | West   |
+|-----------------------|---------|--------|--------|--------|--------|
+| Wall Area (m2)        | 1542.06 | 564.80 | 206.23 | 564.80 | 206.23 |
+| Window Area (m2)      | 306.92  | 112.97 | 43.82  | 112.97 | 37.16  |
+| Window-Wall Ratio (%) | 19.9%   | 20%    | 21.25% | 20%    | 18.02% |  
+
+The test prototype WWR is 19.9%. Based on code, Mid-apartment shall be `Other` building window to wall ratio type so in the baseline, it should have 40% WWR or its proposed design whichever is smaller.
+
+Baseline:
+
+|                       | Total   | North  | East   | South  | West   |
+|-----------------------|---------|--------|--------|--------|--------|
+| Wall Area (m2)        | 1542.06 | 564.80 | 206.23 | 564.80 | 206.23 |
+| Window Area (m2)      | 308.41  | 112.97 | 44.74  | 113.54 | 37.16  |
+| Window-Wall Ratio (%) | 20%     | 20%    | 21.7%  | 20.1%  | 18.02% |  
+
+In this case, a 0.1% tolerance is applied.
+
+### Test Case 5
+- Prototype: Mid Apartment - WWR adjusted
+- User data folder: */userdata_default_test*
+- Summary:
+
+Test prototype:
+
+|                       | Total   | North  | East   | South  | West   |
+|-----------------------|---------|--------|--------|--------|--------|
+| Wall Area (m2)        | 1542.06 | 564.80 | 206.23 | 564.80 | 206.23 |
+| Window Area (m2)      | 750.59  | 282.40 | 92.90  | 282.40 | 92.90  |
+| Window-Wall Ratio (%) | 50%     | 50%    | 50%    | 50%    | 50%    |  
+
+The test prototype WWR is 50%. Based on code, Mid-apartment shall be `Other` building window to wall ratio type so in the baseline, it should have 40% WWR or its proposed design whichever is smaller.
+
+Baseline:
+
+|                       | Total   | North  | East   | South  | West   |
+|-----------------------|---------|--------|--------|--------|--------|
+| Wall Area (m2)        | 1542.06 | 564.80 | 206.23 | 564.80 | 206.23 |
+| Window Area (m2)      | 616.84  | 225.92 | 87.02  | 229.58 | 74.32  |
+| Window-Wall Ratio (%) | 40%     | 40%    | 42.20% | 40.65% | 36.04% |  
+
+
+### Test Case 6
+- Prototype: Medium Office - WWR adjusted
+- User data folder: */userdata_default_test*
+- Summary:
+
+Test prototype:
+
+|                       | Total   | North  | East   | South  | West   |
+|-----------------------|---------|--------|--------|--------|--------|
+| Wall Area (m2)        | 1977.67 | 593.30 | 395.53 | 593.30 | 395.53 |
+| Window Area (m2)      | 27.38   | 0.0    | 27.38  | 0.0    | 0.0    |
+| Window-Wall Ratio (%) | 1.38%   | 0%     | 6.92%  | 0%     | 0%     |  
+
+The test prototype has WWR of 1.38%. The target WWR is 31%. The building has plenums so this test case shall increase the window to wall ratio to 31% by adding more windows to the rest facades and in the meantime, avoids adding new windows to the plenum surfaces
+
+Baseline:
+
+|                       | Total   | North  | East   | South  | West   |
+|-----------------------|---------|--------|--------|--------|--------|
+| Wall Area (m2)        | 1977.67 | 593.30 | 395.53 | 593.30 | 395.53 |
+| Window Area (m2)      | 613.08  | 137.48 | 246.45 | 137.49 | 91.66  |
+| Window-Wall Ratio (%) | 31%     | 23.17% | 62.31% | 23.17% | 23.17% | 

data/lib/openstudio-standards/standards/ashrae_90_1_prm/docs/set_hw_and_chw_supply_water_temp_reset_control.md

@@ -0,0 +1,24 @@
+Apply water supply temperature reset control to hot water loop and chilled water loop.
+
+# ASHRAE 90.1-2019
+
+G3.1.3.4 Hot-Water Supply Temperature Reset (Sys 1, 5 ,7, 11, and 12)
+
+Hot-water supply temperature shall be reset based on outdoor dry-bulb temperature using the following schedule: 180F at 20F and below, 150F at 50F and above and ramped linearly between 180F and 150F at temperature between 20F and 50F.
+
+Exception G3.1.3.4: Systems served by purchased heat
+
+G3.1.3.8: Chilled-Water Supply Temperature Reset (Sys 7, 8, 11, 12 and 13)
+
+Chilled-water supply temperature shall be reset based on outdoor dry-bulb temperature using the following schedule: 44F at 80F and above, 54F at 60F and below, and ramped linearly between 44F and 54F at temperature between 80F and 60F.
+
+Exception G3.1.3.9:
+If the baseline chilled-water system serves a computer room HVAC system, the supply chilled-water temperature shall be reset higher based on the HVAC system requiring the most cooling; i.e., the chilled-water set point is reset higher until one cooling-coil valve is nearly wide open. The maximum reset chilled-water supply temperature shall be 54F
+Systems served by purchased chilled water.
+
+
+# Key Ruby Methods
+
+## plant_loop_enable_supply_water_temperature_reset(plant_loop)
+Search and identify the hot water loops and chilled water loops (exclude district systems).
+Add SetpointManagerOutdoorAirReset to the loops.