Troubleshooting unmet hours in OpenStudio

---UPDATE 7/21/2015---

This Measure automates many of the checks listed below and gives you a nice report summarizing the results.

Basic checks:

1. Look at hours unmet per zone table in eplusout.htm file
   • Make sure that the zone with the problem is not a slave zone on a single-zone VAV system.
   • Check your thermostat setpoint schedules for this zone to make sure values are reasonable
2. Check that design days are for the same location as the weather file
   • Open the .osm in a text editor to look at this.
3. Check the tolerance for reporting unmet hours
   • Try 2F and re-run. If tolerance is too tight, you can get false alarms.
4. Check design/sizing temperature for each plant loop.
   • This is found by clicking the dashed line in the center of a plant loop.
5. Check the operational temperature in the plant loop's setpoint manager.
   • It should match up with the design/sizing temperature for that loop.
   • If you size the loop for 180F water but tell it to operate at 150F, the equipment won't be big enough during peak times.
6. Check design/sizing heating and cooling supply air temperatures for air loop.
   • This is found by clicking the dashed line in the center of the air loop.
7. Check the operational temperature in the air loop's setpoint manager.
   • It should match up with the design/sizing temperature for that loop.
   • If you size the loop for 55F supply air but tell it to operate at 60F, the equipment might not be big enough during peak times.
8. Check that sizing design day thermostat is using a constant setpoint schedule with no setback.
   • This is a 90.1 requirement. If your design day has a setback, your system will be oversized in an attempt to be able to go from setback to setup in a single timestep.
   • Equipment that is significantly oversized might not operate properly at low load conditions.

More detailed checks:

Use the BCL Measure "Add Output Variable" to request timeseries data and inspect these data in ResultsViewer to see what's going on.

1. Examine the zone temperatures and their thermostat setpoints
   • See how much the system is missing setpoint by
   • A shoulder time when transitioning between setback and setup is common
   • You might need to schedule your HVAC on a bit earlier to overcome this
2. Examine the unmet hours per zone
   • See what times of day/year the unmet hours occur
3. Check sizing factor (safety factor) in model.
   • This is found on the Simulation Setting tab

Other resources:

• IES VE has a very good guide that conceptually holds true for most simulation engines.
• Trane has a guide for Trace 700.

EnergyPlus has a neat trick of being able to report out a ton of variables which can be viewed in the ESO file viewer. Usually if you are getting unmet load hours there is something wrong with your system as the previous answerers have pointed out. The easiest way to check your systems and what they are doing is to report out your node flow rates and node temperatures. For one hour of the day you can plot the temperatures and flow through your AHU. you can see the temperature and flow return from the zones, the outdoor air temperature and return, then the fan, the coils and finally what is being delivered to each space, it is here you can also see which spaces are reheating and which aren't (assuming you have a reheat system). You can do the same for your plant loops, it is clear when you do this, whether your flow is too high or non existent, whether your coils are working or not, whether they are meeting setpoint etc.., whether your outdoor air is coming in when it should be and stopping when it should be. Whether your fan is running constantly and so on.

By doing it this way you aren't relying on a check list and luck you are analysing what your system is actually doing and whether it is doing it correctly. More importantly you can point out to your clients any potential issues that they might have designed into the system that need to be discussed.

Regarding OpenStudio, I have found that the defaults for the Output Control Reporting Tolerances for heating and cooling are very low, 0.2K if you open an empty OpenStudio model. AHSRAE 90.1-2007 Addendum cr defines the reporting tolerance as half of the throttling range, or the room temperature difference between full heating and no heating or full cooling and no cooling. Of course this doesn't solve any modeling issues that may be causing hours to be unmet but it is important to understand how the unmet hours are determined and that they are being reported correctly.

Fundamentally, unmet hours will be due to issues with either capacity or controls. From this basic understanding we can use various avenues to troubleshoot.

Capacity:

Here are some questions to ask when troubleshooting capacity issues:

• Are the loads in the spaces reasonable and what you expect?
• Are the capacities of the systems serving these spaces reasonable and what they should be?
• If the capacities are incorrect, revisit your assumptions or examine the autosizing to ensure it is working correctly

Controls:

If the capacities are as they should be then move on to controls:

• Are the heating/cooling sources actually operating?
• If not, when and under what circumstances are they off? Every day? Evenings only? Summer only?
• If they are operating, is the energy actually reaching or being removed from the space? (Is the damper open?)
• What devices/sequences/limits/etc could be causing this.
• If the devices are working correctly are the temperatures of the loops/fluids as they should be? What controls these temperatures in your model?

The particular methods used to answer these questions will depend on the software being used and may be a combination of standard or custom reporting.