Question-and-Answer Resource for the Building Energy Modeling Community
Get started with the Help page
Ask Your Question

Revision history [back]

There are a group of Availability Manager objects that turn loops off according to min or max temperature bounds. One example is the AvailabilityManager:HighTemperatureTurnOff, which you can apply to the boiler loop to turn off whenever the outdoor air temperature is above 67F. Likewise, you can also apply the AvailabilityManager:LowTemperatureTurnOff object to the chiller loop to turn off whenever the outdoor air temperature is below 67F.

Controlling the AHU's is tricky. Ideally, you would want the AHU supply fan to operate when the space temperature and outdoor air temperature both align i.e. (space temperature requires heating and outdoor air temperature is below 67F) or (space temperature requires cooling and outdoor air temperature is above 67F). Otherwise, the AHU supply fan may operate while the boiler or chiller loop is shutoff, so energy is wasted from supplying unconditioned air. To properly apply this control strategy for the AHU supply fan to operate according to both space temperature and outdoor air temperature, you will need to use EMS objects because there isn't a great Availability Manager that will work (AvailabilityManager:DifferentialThermostat comes close, but it will be difficult to control correctly).

If you are working in OpenStudio, you cannot define Availability Managers or EMS objects within the application. However, there are OpenStudio SDK objects that allow you to write an OpenStudio measure to add Availability Managers and EMS objects to the OSM.