In Put Out Put Reference
In Put Out Put Reference
In Put Out Put Reference
0 Documentation
Build: f420c06a69
COPYRIGHT (c) 1996-2021 THE BOARD OF TRUSTEES OF THE UNIVERSITY OF ILLINOIS,
THE REGENTS OF THE UNIVERSITY OF CALIFORNIA THROUGH THE ERNEST ORLANDO
LAWRENCE BERKELEY NATIONAL LABORATORY, OAK RIDGE NATIONAL LABORATORY,
MANAGED BY UT-BATTELLE, ALLIANCE FOR SUSTAINABLE ENERGY, LLC, AND OTHER
CONTRIBUTORS. ALL RIGHTS RESERVED. NO PART OF THIS MATERIAL MAY BE REPRO-
DUCED OR TRANSMITTED IN ANY FORM OR BY ANY MEANS WITHOUT THE PRIOR WRIT-
TEN PERMISSION OF THE UNIVERSITY OF ILLINOIS OR THE ERNEST ORLANDO LAWRENCE
BERKELEY NATIONAL LABORATORY. ENERGYPLUS IS A TRADEMARK OF THE US DEPART-
MENT OF ENERGY.
Contents
1 Input-Output Reference 25
1.1 What’s different about EnergyPlus Input and Output? . . . . . . . . . . . . . . . . 25
1.1.1 EnergyPlus Input Processing . . . . . . . . . . . . . . . . . . . . . . . . . . 25
1.1.2 General Input Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
1.1.3 EnergyPlus Output Processing . . . . . . . . . . . . . . . . . . . . . . . . . 27
1.2 IDD Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
1.2.1 IDD – IP Units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
1.3 Input – Output Descriptions (Document) . . . . . . . . . . . . . . . . . . . . . . . . 33
1.3.1 Input Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
1.3.2 Output Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
1.4 Using EnergyPlus as a Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
1.4.1 State API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
1.4.2 Functional API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
1.4.3 Runtime API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
1.4.4 Data Exchange API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
1.4.5 Full Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
1.4.6 Building and Linking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
1.5 Group – Simulation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
1.5.1 Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
1.5.2 Timestep . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
1.5.3 ConvergenceLimits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
1.5.4 Building . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
1.5.5 SurfaceConvectionAlgorithm:Inside . . . . . . . . . . . . . . . . . . . . . . . 54
1.5.6 SurfaceConvectionAlgorithm:Outside . . . . . . . . . . . . . . . . . . . . . . 55
1.5.7 HeatBalanceAlgorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
1.5.8 HeatBalanceSettings:ConductionFiniteDifference . . . . . . . . . . . . . . . 57
1.5.9 ZoneAirHeatBalanceAlgorithm . . . . . . . . . . . . . . . . . . . . . . . . . 58
1.5.10 ZoneAirContaminantBalance . . . . . . . . . . . . . . . . . . . . . . . . . . 59
1.5.11 ShadowCalculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
1.5.12 Output:Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
1.5.13 Output:DebuggingData . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
1.5.14 Output:PreprocessorMessage . . . . . . . . . . . . . . . . . . . . . . . . . . 66
1.5.15 ZoneCapacitanceMultiplier:ResearchSpecial . . . . . . . . . . . . . . . . . . 66
1.5.16 SimulationControl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
1.5.17 PerformancePrecisionTradeoffs . . . . . . . . . . . . . . . . . . . . . . . . . 69
1.5.18 HVACSystemRootFindingAlgorithm . . . . . . . . . . . . . . . . . . . . . . 77
2
CONTENTS 3
1.5.19 Meter:Custom . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
1.5.20 Meter:CustomDecrement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
1.5.21 Custom Meter Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
1.5.22 Simulation Parameter Outputs . . . . . . . . . . . . . . . . . . . . . . . . . 82
1.6 Group – Compliance Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
1.6.1 Compliance:Building . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
1.7 Group – Location – Climate – Weather File Access . . . . . . . . . . . . . . . . . . 82
1.7.1 Site:Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
1.7.2 Site:VariableLocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
1.7.3 SizingPeriod:DesignDay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
1.7.4 Longer Design Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
1.7.5 SizingPeriod:WeatherFileDays . . . . . . . . . . . . . . . . . . . . . . . . . . 93
1.7.6 SizingPeriod:WeatherFileConditionType . . . . . . . . . . . . . . . . . . . . 95
1.7.7 RunPeriod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
1.7.8 RunPeriodControl:SpecialDays . . . . . . . . . . . . . . . . . . . . . . . . . 100
1.7.9 RunPeriodControl:DaylightSavingTime . . . . . . . . . . . . . . . . . . . . . 101
1.7.10 WeatherProperty:SkyTemperature . . . . . . . . . . . . . . . . . . . . . . . 102
1.7.11 Site:WeatherStation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
1.7.12 Site:HeightVariation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
1.7.13 Site:GroundTemperature:BuildingSurface . . . . . . . . . . . . . . . . . . . . 107
1.7.14 Site:GroundTemperature:Shallow . . . . . . . . . . . . . . . . . . . . . . . . 107
1.7.15 Site:GroundTemperature:Deep . . . . . . . . . . . . . . . . . . . . . . . . . 108
1.7.16 Site:GroundTemperature:Undisturbed:FiniteDifference . . . . . . . . . . . . 108
1.7.17 Site:GroundTemperature:Undisturbed:KusudaAchenbach . . . . . . . . . . . 109
1.7.18 Site:GroundTemperature:Undisturbed:Xing . . . . . . . . . . . . . . . . . . 110
1.7.19 Site:GroundDomain:Slab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
1.7.20 Site:GroundDomain:Basement . . . . . . . . . . . . . . . . . . . . . . . . . . 117
1.7.21 Site:GroundTemperature:FCfactorMethod . . . . . . . . . . . . . . . . . . . 122
1.7.22 Site:GroundReflectance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
1.7.23 Site:GroundReflectance:SnowModifier . . . . . . . . . . . . . . . . . . . . . . 123
1.7.24 Site:WaterMainsTemperature . . . . . . . . . . . . . . . . . . . . . . . . . . 123
1.7.25 Site:Precipitation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
1.7.26 RoofIrrigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
1.7.27 Solar and Visible Spectrum Objects . . . . . . . . . . . . . . . . . . . . . . . 126
1.7.28 Site:SolarAndVisibleSpectrum . . . . . . . . . . . . . . . . . . . . . . . . . . 127
1.7.29 Site:SpectrumData . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
1.7.30 Climate Group Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
1.7.31 Weather Data Related Outputs . . . . . . . . . . . . . . . . . . . . . . . . . 128
1.7.32 Outputs for local temperature/wind speed calculations . . . . . . . . . . . . 135
1.8 Group – Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
1.8.1 Day Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
1.8.2 ScheduleTypeLimits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
1.8.3 Day Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
1.8.4 Schedule:Day:Hourly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
1.8.5 Schedule:Day:Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
1.8.6 Schedule:Day:List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
4 CONTENTS
6 Output 2994
6.1 Using ReadVarsESO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2995
6.1.1 Creating Charts and Spreadsheet files from Output Variables . . . . . . . . 2995
Input-Output Reference
This document is intended to be an encyclopedic reference for the EnergyPlus Input Data Dictionary
(IDD), Input Data File (IDF) and potential resultant outputs (various output files).
The following descriptions are “grouped” by the elements in the IDD (ref: Getting Started
Document and the IDD Conventions). In some cases, the descriptions of reporting will be done for
an object (e.g., Lighting electrical consumption or thermal comfort value for a group of people) and
in some cases for the entire group (e.g., ambient condition reports).
25
26 CHAPTER 1. INPUT-OUTPUT REFERENCE
all its input the first time it is called. The implication for the user is that error messages may show
up in somewhat peculiar places. A further implication is that no order is needed in the input data
file! Data that is not needed by a particular simulation is not processed.
3) The data dictionary provides the capability to do “automatic” range checking on numeric
fields as well as fill in numeric defaults. Both filling in defaults and “automatic” range checking are
done when the data is read. Other checks may need a combination of fields and won’t be done until
the data is “processed” (after the simulation starts).
4) A couple of other differences that might not be true in other programs: Blanks are
significant in alpha fields SO DesignDay is not the same as Design Day (1 space between Design
and Day) nor Design Day (2 spaces between Design and Day). Alpha objects, however, are case
insensitive SO DesignDay is the same as ‘designday’ or ‘SizingPeriod:DesignDay’.
• Fields do not extend over line boundaries. Usually, if a comma or (as appropriate) semi-colon
is not the last field value on a line, one will be inserted. Of course, several fields may appear
on a single line as long as they are comma separated. (And the last could be followed by a
semi-colon).
• Commas delimit fields – therefore, no fields can have embedded commas. No error will
occur but you won’t get what you want. You cannot surround a field with “ to accommodate
commas in the fields.
• The comment character is a exclamation “!”. Anything on a line after the exclamation is
ignored.
• Input records (aka input line length) can be up to 500 characters in length. If you go over
that, no error will occur but you won’t get what you want.
• Each Alpha string in the input data file (aka alpha field length) can be up to 100 characters
in length. Anything beyond that is truncated. This would apply to all names (such as zone
name, node name, schedule name) in fields.
• Each Alpha string (including Section and Class/Object keywords) is mapped to UPPER case
during processing, unless the “retaincase” flag marks the field in the IDD. Get routines from
1.2. IDD CONVENTIONS 27
the EnergyPlus code that use the Section and Object keywords automatically map to UPPER
case for finding the item. The primary drawback with this is that error messages coming out
of the input processor will be in UPPER case and may not appear exactly as input.
• Special characters, such as tabs, should NOT be included in the file. However, tabs can be
accommodated and are turned into spaces.
• All numbers can be flexibly input and are processed into single precision variables (i.e. 1.0,
1.000, 1, .1E+1 are all processed equally).
!
! 1. If a particular comment is not applicable (such as units , or default)
! then simply omit the comment rather than indicating N/A.
!
! 2. Memos and notes should be brief (recommend 5 lines or less per block).
! More extensive explanations are expected to be in the user documentation
! cycles/hr
! days
! deg
! dimensionless
! eV
! hr
! J/J
! kg/kg
! kg -H2O/kg -air
! kmol
! kmol/s
! m3/m3
! minutes
! Mode
! ms
! ohms
! percent
! ppm
! rev/min
! s
! V
! VA
! W/m2 or deg C
! W/m2 , W or deg C
! W/s
! W/W
! years
! **************************************************************************
The IDD excerpt above is the complete definition as seen in the IDD file.
First, the object name is given. (Site:Location) This is followed by a comma in both the
definition (IDD) and in an input file (IDF). In fact, all fields except the terminating field of an IDD
class object and IDF object are followed by commas. The final field in an IDD class object or in an
IDF object is terminated by a semi-colon.
Next is an alpha field, the location name. As noted above, for input, spaces are significant in
this field. The main inputs for Site:Location are numeric fields. These are numbered (as is the
alpha field) for convenience. The \ designations will show various information about the objects as
described above in the IDD conventions discussion. Of importance for reading this document are
the units and possible minimum and maximum values for a field.
There is automatic processing of the \minimum, \maximum and \default data for numeric fields.
Any infractions of the \minimum, \maximum fields are automatically detected and messages will
appear in the standard error file. After all the input is checked, infractions will cause program
termination (before the bulk of the simulation is completed). Defaults are also enforced if you leave
the numeric field blank.
Some objects need all the parameters listed by the definition; some do not. In the descriptions
that follow, we will try to indicate which parts are optional. Usually, these will be the last fields in
the object input or definition. Even if items are not used for a particular object (e.g. Multiplier in
the FenestrationSurface:Detailed and type = Door), the field must be included unless it is the last
field in the object. So, for this instance, one must include a multiplier field (must be numeric and
would need to obey any \minimum, \maximum rules) for doors.
Two spreadsheet files are included with the installation:
• ExampleFiles.xls – shows many details about the included example files including highlights
of features.
• ExampleFiles-ObjectsLink.xls – shows, for each object, the first three occurrences of that
object in an example file.
The Simple (or regular) display looks like the following figure and is interpreted:
Zone/HVAC – when the output is produced at the “Zone” timestep (ref: number of timesteps
in each hour) or at the “HVAC” aka System timestep (which can vary for each hour).
Average/Sum – whether this is a averaged value over the reporting period (such as a temper-
ature or rate) or whether this is a summed value over the reporting period. Reporting periods are
specified in the Output:Variable or Output:Meter objects.
<Variable Name> – The variable name one uses for reporting is displayed (e.g., Site Outdoor
Drybulb Temperature) along with the units (e.g., [C]).
Example from the eplusout.rdd file:
Note that the eplusout.mdd file is similar, but meters are only available at the Zone timestep.
• Zone,Meter,Electricity:Facility [J]
• Zone,Meter,ExteriorLights:Electricity [J]
• Zone,Meter,EnergyTransfer:Facility [J]
• Zone,Meter,EnergyTransfer:Building [J]
The IDF display has all the same information in an IDF-ready form (i.e., you could copy and
paste it into your input file using a text editor).
Example from the eplusout.rdd file:
All of the same information appears in a slightly different form and defaults to “hourly” reporting
frequency (which, of course, can be changed when you put it into your input file). The “*” is
preselected so that you would be reporting for all those items.
• The Energy Management System, which was the first method to allow reading and writ-
ing simulation data while a simulation was running, and allowing user-defined scripts to be
executed to alter simulation data.
• The EnergyPlus unit test structure, which has, as a side-effect, enabled the ability to “reset”
the state of a simulation, and re-run another, in the same memory space.
1.4. USING ENERGYPLUS AS A LIBRARY 37
• Version 9.3 included the first version of the modern API in EnergyPlus.
• As of version 9.4, the API was improved with the ability to more reliably “reset” the simulation
state. This caused some breaking changes in the API, which are expected to be very rare
moving forward.
• Then as of version 9.5, EnergyPlus became thread-safe. By refactoring 17,000 global and
static variables in the program, the state object now holds the entire state of the program,
and threads will not cross-talk.
• With the release of EnergyPlus 9.6, another major enhancement was made that allowed API
clients to execute input files that included Python Plugins. The original implementation had
a limitation that kept the two from working together, but this was remedied so that interfaces
that call the API can simultaneously execute files with Python Plugins.
Interface developers that have been building on top of EnergyPlus have primarily interacted with
the simulation in the traditional manner. The interface would create an input file in a directory, copy
in weather data and any other supporting data, and then kick off a simulation in that directory.
The interface could grab output messages from the simulation, but that was essentially it. The
interface just had to wait until EnergyPlus completed, check data in the output files, and decide
what to do next. Grabbing any sort of data from the simulation during a run, even just progress,
was highly difficult.
The EnergyPlus API has been created to change that situation and open new doors into the
simulation program and the opportunity to embed EnergyPlus into vastly more workflows and
applications. A new formal EnergyPlus API is implemented that allows interacting with different
“categories” of the simulation. Technically speaking, the categories are not different, as they operate
using the same API mechanics. The categorization is purely organizational. In the following
subsections, the API is laid out with examples in both C and Python. Full API documentation will
be provided separate from this document. Check the release notes for your specific release for more
information.
Prior to calling into most of the API functions, the API client must create a new state instance.
This state instance is not to be directly accessed by the client, but instead the client must simply
be a courier of this state instance and pass it in and out of the API calls. Whenever the client is
done with that instance, the instance can be reset to be prepped for another run of EnergyPlus, or
destroyed if the client is done with it.
An example of this in C is listed here:
#include <EnergyPlus/api/state.h>
That does not do much. But moving through the rest of the API functions, it will become clear
that this is at the core of an EnergyPlus API workflow.
In Python, that same example is similar:
from pyenergyplus.api import EnergyPlusAPI
api = EnergyPlusAPI ()
state = api.state_manager.new_state ()
api.state_manager.reset_state(state)
api.state_manager.delete_state(state)
print ("Wow even boring in Python !?")
It is quite minimal, objects are constructed, methods are called, and objects are destructed.
Note that the initializeFunctionalAPI function must be called once to setup the program. Note
that the constructor function arguments are case-insensitive. Also note that no simulation has been
executed here, this is purely calling into the library to evaluate functions.
The same operations, but in Python are listed here:
from pyenergyplus.api import EnergyPlusAPI
api = EnergyPlusAPI ()
state = api.state_manager.new_state ()
psychrometrics = api.functional.psychrometrics(state , )
rh = psychrometrics.relative_humidity_b (state , 24, 0.009 , 101325)
Some subtle differences are present. In Python, the client creates an instance of an Ener-
gyPlusAPI class to access all methods. Functional category API methods are accessed via the
EnergyPlusAPI.functional variable. Note that in Python, in contrast to C, the psychrometric
functions also live on a class that must be constructed.
The code is straightforward, though excessively minimal. A minimal function is created, which
accepts one argument - a state object, and does nothing. This function is then passed to a callback
registration function via the runtime API. EnergyPlus is executed, passing along any command line
arguments that are received by the test program. This is a convenience because the energyplus
function expects arguments just like the EnergyPlus(.exe) program, so the test script would have
the same command line capabilities as EnergyPlus itself. For this code, it could be executed with
something like: program.exe -D /path/to/input.idf. Once EnergyPlus is complete, the state
object is reset, the callback is re-registered, and EnergyPlus is run again. Since the test script is
complete at this point, there is no need to reset the state again.
The code is strikingly similar in Python:
import sys
from pyenergyplus.api import EnergyPlusAPI
api = EnergyPlusAPI ()
state = api.state_manager.new_state ()
api.runtime. callback_begin_new_environment (state , dummy_callback_function )
api.runtime.run_energyplus(state , sys.argv [1:])
api.state_manager.reset_state(state)
api.runtime. callback_begin_new_environment (state , dummy_callback_function )
api.runtime.run_energyplus(state , sys.argv [1:])
Once again, a dummy function is created, then registered, followed by a call to run EnergyPlus
(passing along the relevant command line arguments), the state is cleared, then the function is
registered again and EnergyPlus is run a second time. Note that when calling EnergyPlus as a
library, you should just pass the arguments, not the filename itself. In Python, the argv variable
will have the filename as the first item in the list, so this example trims that off.
In an API workflow, the client would interact with variables in three steps. First the user
will either specify the output as requested in the input file provided, or call a variable request
function to mark the variable as requested. Second the user will call to lookup a variable
ID/handle, passing in the variable type name and key. Third the variable value can be looked
up while a simulation is running by calling a get-value function on the API.
Meters Meters represent groups of variables which are collected together, much like a meter on
a building which represents multiple energy sources. Meters are handled the same way as
variables, except that meters do not need to be requested prior running a simulation. From
an API standpoint, a client must simply get a handle to a meter by name, and then access
the meter value by using a get-value function on the API.
Internal Variables The name “internal variable” is used here as it is what these variables were
called in the original EMS implementation. Another name for these variables could be “static”
variables. Basically, these variables represent data that does not change throughout a simula-
tion period. Examples include calculated zone volume or autosized equipment values. These
values are treated just like meters, you use one function to access a handle ID, and then use
this handle to lookup the value.
Simulation Parameters A number of parameters are made available as they vary through the
simulation, including the current simulation day of week, day of year, hour, and many other
things. These do not require a handle, but are available through direct function calls.
With these read-only data exchange items available, there are already a number of new pos-
sibilities. As an example, an EnergyPlus interface developer could very easily change from just
executing the EnergyPlus program, to calling EnergyPlus as a library function. This would unlock
the potential to not only get better progress status updates, but the interface could also request
and lookup values of some energy meters or other output variables, and present this to the user
graphically while the simulation is running. However, much more power comes with the addition
of actuators, described next.
Actuators Actuators are the way that users modify the program at runtime using custom logic
and calculations. Not every variable inside EnergyPlus can be actuated. This is intentional,
because opening that door could allow the program to run at unrealistic conditions, with flow
imbalances or energy imbalances, and many other possible problems. Instead, a specific set of
items are available to actuate, primarily control functions, flow requests, and environmental
boundary conditions. These actuators, when used in conjunction with the runtime API and
data exchange variables, allow a user to read data, make decisions and perform calculations,
then actuate control strategies for subsequent time steps.
Actuator functions are similar, but not exactly the same, as for variables. An actuator
handle/ID is still looked up, but it takes the actuator type, component name, and control
type, since components may have more than one control type available for actuation. The
actuator can then be “actuated” by calling a set-value function, which overrides an internal
value, and informs EnergyPlus that this value is currently being externally controlled. To
allow EnergyPlus to resume controlling that value, there is an actuator reset function as well.
A special note about data exchange. Variables, meters, and actuators are not immediately avail-
able as soon as the program starts. The memory associated with these along with the bookkeeping,
42 CHAPTER 1. INPUT-OUTPUT REFERENCE
must be set up during program initialization. There is a risk that the variables requested are not
set up by the first API callback point. This is intentional because some API callbacks may want to
be called this early. To avoid problems, a function is available on this API that will allow a client
to check if the API data is “fully ready”. For almost all applications, if this is not ready, the client
should just return from the callback and let EnergyPlus continue, and wait until it is ready before
doing any manipulation.
It is difficult (impossible?) to exercise the data exchange API without at least also demonstrating
the runtime API. In order to exchange data with the simulation, you must first create a runtime
callback function and register that, then execute EnergyPlus, and finally wait until EnergyPlus calls
your callback function. At this point, you can then perform data exchange. Minimal examples that
tie the runtime and data exchange APIs together are shown here, first in C:
#include <EnergyPlus/api/datatransfer.h>
#include <EnergyPlus/api/runtime.h>
#include <EnergyPlus/api/state.h>
The actual operations happening in this example are completely fictional, but nevertheless
demonstrate a possible minimal case. Note that the variable to be used is requested, and if the api
data is not fully ready in the callback, it simply returns and waits.
And now in Python:
from pyenergyplus.api import EnergyPlusAPI
one_time = True
outdoor_temp_sensor = 0
outdoor_dew_point_actuator = 0
def time_step_handler(state):
global one_time , outdoor_temp_sensor , outdoor_dew_point_sensor , outdoor_dew_point_actuator
if one_time:
if not api.exchange. api_data_fully_ready (state):
return
outdoor_temp_sensor = api.exchange. get_variable_handle (
state , u"SITE OUTDOOR AIR DRYBULB TEMPERATURE", u"ENVIRONMENT"
)
outdoor_dew_point_actuator = api.exchange.get_actuator_handle (
state , "Weather Data", "Outdoor Dew Point", "Environment"
)
one_time = False
oa_temp = api.exchange. get_variable_value (state , outdoor_temp_sensor )
1.5. GROUP – SIMULATION PARAMETERS 43
api = EnergyPlusAPI ()
state = api.state_manager.new_state ()
api.runtime. callback_end_zone_timestep_after_zone_reporting (state , time_step_handler )
api.exchange. request_variable(state , "SITE OUTDOOR AIR DRYBULB TEMPERATURE", "ENVIRONMENT ")
api.runtime.run_energyplus(state , sys.argv [1:])
Note that when strings are passed through the Python API, they are both case-insensitive, and
type-insensitive. By type-insensitive, this means they can be either Python strings, or Python bytes
objects. In this example, both are used, as well as mixed-casing, to demonstrate the flexibility.
When building C applications, the build should include the EnergyPlusInstallRoot path in your
include path, so that when the client has an #include<EnergyPlus/api/func.h>, it will be able to
find it relative to the EnergyPlus install root path. Once the code is compiled, it should be linked
to the EnergyPlus shared library, which also lives in the root of the EnergyPlus install. The actual
command will be different based on your system and compiler, but using gcc on Linux, for example,
the command passed to the linker would be -l/path/to/libenergyplusapi.so.
When building Python applications, the EnergyPlusInstallRoot should be added to the search
path prior to trying to import anything else. This can be accomplished through the use of environ-
ment variables, but it is also easy to do at the beginning of scripts, for example:
import sys
sys.path.insert(0, '/path/to/EnergyPlusInstallRoot')
from pyenergyplus import api
1.5.1 Version
1.5.1.1 Inputs
1.5.1.1.1 Field: Version Identifier
The Version object allows you to enter the proper version that your IDF was created for. This
is checked against the current version of EnergyPlus and a Severe error issued (non-terminating)
if it does not match the current version string. Note that versions are often significant and there
is no guarantee that the older file will run in the newer versions of the program. See IDF Version
Updater (Auxiliary Programs Document) for methods of changing the older files to newer versions.
1.5.2 Timestep
1.5.2.1 Inputs
1.5.2.1.1 Field: Number of Timesteps per Hour
The Timestep object specifies the “basic” timestep for the simulation. The value entered here is
usually known as the Zone Timestep. This is used in the Zone Heat Balance Model calculation as
the driving timestep for heat transfer and load calculations. The value entered here is the number of
timesteps to use within an hour. Longer length timesteps have lower values for Number of Timesteps
per Hour. For example a value of 6 entered here directs the program to use a zone timestep of 10
minutes and a value of 60 means a 1 minute timestep. The user’s choice for Number of Timesteps
per Hour must be evenly divisible into 60; the allowable choices are 1, 2, 3, 4, 5, 6, 10, 12, 15, 20,
30, and 60.
The choice made for this field has important implications for modeling accuracy and the overall
time it takes to run a simulation. Here are some considerations when choosing a value:
• The solution technique used in EnergyPlus has been designed to be stable with zone timesteps
of up to sixty minutes (Number Timesteps in Hour = 1). However, 60 minutes is considered a
“long” timestep and it should only be used in rare occasions where there is no HVAC system,
accuracy is not a concern, and short run times are critical. Such long timesteps are not recom-
mended to use because simulation results are more accurate for shorter timesteps, of say 10
minutes or less (Number of Timesteps per Hour of 6 or more). Shorter zone timesteps improve
the numerical solution of the Zone Heat Balance Model because they improve how models
for surface temperature and zone air temperature are coupled together. Longer timesteps
introduce more lag and lead to more a dampened dynamic response.
• Simulation run time increases with shorter timesteps or larger values for Number of Timesteps
per Hour. The effect varies with the nature of the model. The user can test out different
values on their particular model to understand the implications for his or her particular case.
Sometimes large models with multizone HVAC and Plant systems execute nearly as fast with
15 minute timesteps as with 60 minute timesteps because fewer iterations are required in
the system modeling since the prior timestep’s results are close to the final outcome of next
timestep.
• The weather data files usually have 60-minute (or hourly) data. However, it does not follow
that this should be used as the basis for choosing the zone timestep because:
1.5. GROUP – SIMULATION PARAMETERS 45
• EnergyPlus carefully interpolates the weather data between data points for use at shorter
timesteps. This is discussed in a later section: Weather Data Hourly Interpolation
• Many aspects of a model have time scales that differ from the that of the weather data. A
goal of the modeling is to predict how the building will respond to the weather. However,
the building’s response is not governed by the time scale that the weather data are available
at, but rather the time scales of the dynamic performance of the thermal envelope as well as
things like schedules for internal gains, thermostats, and equipment availability.
• If the model will include calculating the cost of electricity, then the user should be aware that
many electric utility tariffs base charges on demand windows of a specified length of time.
If the choice of Number of Timesteps per Hour is not consistent with the demand window,
then unexpected results may be obtained. For reasonable prediction of the maximum rates
for electricity use for in calculating demand charges, the length of the zone timestep needs
to be consistent with the tariff’s demand window. The following table lists what values are
consistent with various demand windows.
There is also second type of timestep inside EnergyPlus that is known as the System Timestep.
This is a variable-length timestep that governs the driving timestep for HVAC and Plant system
modeling. The user cannot directly control the system timestep (except by use of the Conver-
genceLimits object). When the HVAC portion of the simulation begins its solution for the current
zone timestep, it uses the zone timestep as its maximum length but then can reduce the timestep,
as necessary, to improve the solution. The technical details of the approach are explained in the
Engineering Documentation under “Integrated Solution Manager”.
Users can see the system timestep used if they select the “detailed” frequency option on an
HVAC output variable (e.g. Zone Air Temperature). To contrast, the “Zone” variables will only be
reported on the zone timestep (e.g. Zone Mean Air Temperature).
And, the IDF example:
Suggested defaults are 4 for non-HVAC simulations, 6 for simulations with HVAC, 20 is the
minimum for ConductionFiniteDifference and HeatAndMoistureFiniteElement simulations. Green
roof (ref: Material:RoofVegetation) also may require more timesteps.
Note that hourly data (such as outdoor conditions expressed by Design Days or Weather data)
are interpolated to the Zone Timestep. This is discussed in a later section: Weather Data Hourly
Interpolation
46 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.5.3 ConvergenceLimits
This item is an “advanced” feature that should be used only with caution. It is specifically included
to assist some users “speed up” calculations while not overly compromising accuracy. The user
must judge for him/herself whether the reduced run time is useful.
1.5.3.1 Inputs
1.5.3.1.1 Field: Minimum System Timestep
Usually the minimum system timestep is allowed to vary from the zone timestep (as maximum)
to a minimum timestep of 1 minute during certain system calculations. This might be when the
system turns on or off, for example. Entering 0 in this field sets the minimum system timestep to
be the same as the zone timestep. Otherwise the units of the field are minutes. It’s probably a
good idea to have any minimum entered be a divisor of the zone timestep.
In order to reduce time used in simulating your building, you may choose to enter a lesser
number than the default of 20 for the maximum number of iterations to be used. Or, you may
wish to enter a bigger number for certain buildings. To get more information printed with a “max
iteration” message, you need to enter a “Output:Diagnostics, DisplayExtraWarnings;” command
(which may also generate other warnings than just this one).
for understanding how many plant solver iterations are actually being used during a particular
simulation. The lower limit of the value for this field is “2.”
Use in an IDF:
ConvergenceLimits ,
0, !- Minimum System Timestep (0 = same as zone timestep)
25, !- Maximum HVAC Iterations
3, !- Minimum Plant Iterations
9; !- Maximum Plant Iterations
1.5.4 Building
The Building object describes parameters that are used during the simulation of the building.
There are necessary correlations between the entries for this object and some entries in the
Site:WeatherStation and Site:HeightVariation objects, specifically the Terrain field.
1.5.4.1 Inputs
1.5.4.1.1 Field: Building Name
Building name is specified for output convenience.
It does a similar comparison with lowest temperatures experience within all the zones. If the
current simulation day and the previous day values are within the tolerance, then it has passed the
second warm-up check. Similar things are done with the loads tolerance and the maximum heating
and cooling loads that are experienced within the spaces. Those are compared individually to the
values for the previous day. If they are both in tolerance, then the simulation has passed the third
and fourth warm-up check. The simulation stays in the warm-up period until ALL FOUR checks
have been passed. See Engineering Reference and Output Details document for further explanation
and outputs.
Please note–other “convergence tolerance” inputs are required for certain HVAC equipment (unit
ventilator, unit heater, window AC, etc.). The purpose and units of these parameters are different
from “load convergence tolerance” and “temperature convergence tolerance” in the BUILDING
object.
two surfaces.) If the zone’s surfaces do not enclose a space or if the zone is not convex you should
use Solar Distribution = FullExterior instead of FullInteriorAndExterior.
If you use FullInteriorAndExterior the program will also calculate how much beam radiation
falling on the inside of an exterior window (from other windows in the zone) is absorbed by the
window, how much is reflected back into the zone, and how much is transmitted to the outside. In
this calculation the effect of a shading device, if present, is accounted for.
Diffuse Radiation
Diffuse solar transmitted through exterior and interior windows is distributed according to the
approximate view factors between the transmitting window and all other heat transfer surfaces in
the zone. The portion of this diffuse solar that is reflected by all surfaces in the zone is subsequently
redistributed uniformly (based on area and solar absorptance) to all heat transfer surfaces in the
zone, along with interior reflected beam solar and shortwave radiation from lights. Refer to the
section “Solar Distribution” in the Engineering Reference Guide for more information including
equations.
Reflection calculations
Note: Using the reflection calculations can be very time-consuming. Even error-prone. As a
possible alleviation, you can use the Output:Diagnostics “DoNotMirrorDetachedShading” in many
cases to get past a fatal error.
If using reflections, the program calculates beam and sky solar radiation that is reflected from
exterior surfaces and then strikes the building. These reflecting surfaces fall into three categories:
1) Shadowing surfaces. These are surfaces like overhangs or neighboring buildings entered
with Shading:Site, Shading:Building, Shading:Site:Detailed, Shading:Building:Detailed, Shading:-
Overhang, Shading:Overhang:Projection, Shading:Fin, Shading:Fin:Projection or Shading:Zone:-
Detailed objects. See Figure 1.3.
1.5. GROUP – SIMULATION PARAMETERS 51
These surfaces can have diffuse and/or specular (beam-to-beam) reflectance values that are
specified with the ShadingProperty:Reflectance object which specifies those parameters. They have
a default value of .2 for both visible and diffuse reflection.
2) Exterior building surfaces. In this case one section of the building reflects solar radiation
onto another section (and vice-versa). See Figure 1.4.
The building surfaces are assumed to be diffusely reflecting if they are opaque (walls, for exam-
ple) and specularly reflecting if they are windows or glass doors. The reflectance values for opaque
surfaces are calculated by the program from the Solar Absorptance and Visible Absorptance val-
ues of the outer material layer of the surface’s construction (ref: Material object properties). The
reflectance values for windows and glass doors are calculated by the program from the reflectance
properties of the individual glass layers that make up surface’s construction assuming no shading
device is present and taking into account inter-reflections among the layers (ref: Window Proper-
ties).
3) The ground surface. Reflection from the ground is calculated even if reflections option is
not used;l but then the ground plane is considered unobstructed, i.e., the shadowing of the ground
by the building itself or by obstructions such as neighboring buildings is ignored. Shadowing by the
building itself or neighboring buildings is taken into account when the “with reflections” option is
used but then the “view factor to ground” is NOT used. This is shown in Figure 1.5.
Figure 1.3: Solar reflection from shadowing surfaces. Solid arrows are beam solar radiation; dashed
arrows are diffuse solar radiation. (a) Diffuse reflection of beam solar radiation from the top of an
overhang. (b) Diffuse reflection of sky solar radiation from the top of an overhang. (c) Beam-to-
beam (specular) reflection from the façade of an adjacent highly-glazed building represented by a
vertical shadowing surface.
Figure 1.4: Solar reflection from building surfaces onto other building surfaces. In this example
beam solar reflects from a vertical section of the building onto a roof section. The reflection from
the window is specular. The reflection from the wall is diffuse.
1.5. GROUP – SIMULATION PARAMETERS 53
Figure 1.5: Shadowing from building affects beam solar reflection from the ground. Beam-to-diffuse
reflection from the ground onto the building occurs only for sunlit areas, A and C, not from shaded
area, B.
..Max Temp Comparison = 2.06E -002 vs Temperature Convergence Tolerance = 0.50 – Pass Convergence
..Min Temp Comparison = 5.95E -003 vs Temperature Convergence Tolerance = 0.50 – Pass Convergence
..Max Cool Load Comparison = 9.5082E -002 vs Loads Convergence Tolerance = 5.00E -002 – Fail Convergence
As noted in the message, there will be more information in the .eio file. (Refer to Output Details
document as well for examples.)
You may be able to increase the Maximum Number of Warmup Days and get convergence, but
some anomalous buildings may still not converge. Simulation proceeds for x warmup days until
“convergence” is reached (see the discussion under the Temperature Convergence Tolerance Value
field in this object, just above).
The value in this field is an overall parameter for all types of environments in the simulation.
The maximum nmber of warmup days can also be controlled separately for individual designgdays
using the input field Maximum Number Warmup Days in the SizingPerod:DesignDay object.
wish to increase warmup days more than the previous field. In this particular case, the previous
field will be automatically reset to the value entered in this field and EnergyPlus will run exactly
the number of warmup days specified in this field.
An example from an IDF:
Building ,
PSI HOUSE DORM AND OFFICES , !- Name
36.87000 , !- North Axis {deg}
Suburbs , !- Terrain
0.04, !- Loads Convergence Tolerance Value
0.4000000 , !- Temperature Convergence Tolerance Value {deltaC}
FullInteriorAndExterior , !- Solar Distribution
40, !- Maximum Number of Warmup Days
6; !- Minimum Number of Warmup Days
1.5.5 SurfaceConvectionAlgorithm:Inside
This input object is used control the choice of models used for surface convection at the inside face of
all the heat transfer surfaces in the model. This object sets the selection for convection correlations
in a global way. The Zone Inside Convection Algorithm input field in the Zone object may be used
to selectively override this value on a zone-by-zone basis. Further, individual surfaces can refine
the choice by each surface or surface lists – see object SurfaceProperty:ConvectionCoefficients and
object SurfaceProperty:ConvectionCoefficients:MultipleSurface.
1.5.5.1 Inputs
1.5.5.1.1 Field: Algorithm
The model specified in this field is the default algorithm for the inside face all the surfaces..
The key choices are Simple, TARP, CeilingDiffuser, AdaptiveConvectionAlgorithm, and
ASTMC1340.
The Simple model applies constant heat transfer coefficients depending on the surface orienta-
tion.
The TARP model correlates the heat transfer coefficient to the temperature difference for
various orientations. This model is based on flat plate experiments.
The CeilingDiffuser model is a mixed and forced convection model for ceiling diffuser config-
urations. The model correlates the heat transfer coefficient to the air change rate for ceilings, walls
and floors. These correlations are based on experiments performed in an isothermal room with a
cold ceiling jet. To avoid discontinuities in surface heat transfer rate calculations, all of correlations
have been extrapolated beyond the lower limit of the data set (3 ACH) to a natural convection
limit that is applied during the hours when the system is off.
The AdaptiveConvectionAlgorithm model is an dynamic algorithm that organizes a
large number of different convection models and automatically selects the one that best applies.
The adaptive convection algorithm can also be customized using the SurfaceConvectionAlgo-
rithm:Inside:AdaptiveModelSelections input object. These models are explained in detail in the
EnergyPlus Engineering Reference Document.
The ASTMC1340 model correlates mixed convection coefficients to the surface-to-air temper-
ature difference, heat flow direction, surface tilt angle, surface characteristic length, and air speed
past the surface. These correlations are based on ASTM C1340 standard.
The default is TARP.
1.5. GROUP – SIMULATION PARAMETERS 55
IDF Example:
1.5.6 SurfaceConvectionAlgorithm:Outside
Various exterior convection models may be selected for global use. The optional Zone Outside
Convection Algorithm input field in the Zone object may be used to selectively override this
value on a zone-by-zone basis. Further, individual surfaces can refine the choice by each sur-
face or surface lists – see object SurfaceProperty:ConvectionCoefficients and object SurfaceProp-
erty:ConvectionCoefficients:MultipleSurface.
1.5.6.1 Inputs
1.5.6.1.1 Field: Algorithm
The available key choices are SimpleCombined, TARP, MoWiTT, DOE-2, and Adap-
tiveConvectionAlgorithm.
The Simple convection model applies heat transfer coefficients depending on the roughness and
windspeed. This is a combined heat transfer coefficient that includes radiation to sky, ground, and
air. The correlation is based on Figure 1.142, Page 25.1 (Thermal and Water Vapor Transmission
Data), 2001 ASHRAE Handbook of Fundamentals. Note that if Simple is chosen here or in the
Zone field and a SurfaceProperty:ConvectionCoefficients object attempts to override the calculation
with a different choice, the action will still be one of combined calculation. To change this, you
must select one of the other methods for the global default.
All other convection models apply heat transfer coefficients depending on the roughness, wind-
speed, and terrain of the building’s location. These are convection only heat transfer coefficients;
radiation heat transfer coefficients are calculated automatically by the program.
The TARP algorithm was developed for the TARP software and combines natural and wind-
driven convection correlations from laboratory measurements on flat plates.
The DOE-2 and MoWiTT were derived from field measurements. DOE-2 uses a correlation
from measurements by Klems and Yazdanian for rough surfaces. MoWitt uses a correlation from
measurements by Klems and Yazdanian for smooth surfaces and, therefore, is most appropriate
for windows (see SurfaceProperty:ConvectionCoefficients:MultipleSurface for how to apply to only
windows).
The AdaptiveConvectionAlgorithm model is an dynamic algorithm that organizes a
large number of different convection models and automatically selects the one that best applies.
The adaptive convection algorithm can also be customized using the SurfaceConvectionAlgo-
rithm:Outside:AdaptiveModelSelections input object. All algorithms are described more fully in
the Engineering Reference.
The default is DOE-2.
Note that when the surface is wet (i.e. it is raining and the surface is exposed to wind) then
the convection coefficient appears as a very large number (1000) and the surface is exposed to the
Outdoor Wet-bulb Temperature rather than the Outdoor Dry-bulb Temperature.
IDF Example:
1.5.7 HeatBalanceAlgorithm
The HeatBalanceAlgorithm object provides a way to select what type of heat and moisture transfer
algorithm will be used for calculating the performance of the building’s surface assemblies. This
input controls the overall algorithm used for all the surfaces unless one or more of the SurfaceProp-
erty:HeatTransferAlgorithm:* objects are used to alter the selection for particular surfaces.
1.5.7.1 Inputs
1.5.7.1.1 Field: Algorithm
Four values are allowed to select which solution will be used.
• The ConductionTransferFunction selection is a sensible heat only solution and does not
take into account moisture storage or diffusion in the construction elements.
– MaterialProperty:MoisturePenetrationDepth:Settings
– MaterialProperty:PhaseChange
– MaterialProperty:VariableThermalConductivity
– MaterialProperty:PhaseChangeHysteresis
– MaterialProperty:HeatAndMoistureTransfer:Settings
– MaterialProperty:HeatAndMoistureTransfer:SorptionIsotherm
– MaterialProperty:HeatAndMoistureTransfer:Suction
– MaterialProperty:HeatAndMoistureTransfer:Redistribution
– MaterialProperty:HeatAndMoistureTransfer:Diffusion
– MaterialProperty:HeatAndMoistureTransfer:ThermalConductivity
1.5. GROUP – SIMULATION PARAMETERS 57
And, after careful perusal, you cannot find a solution as suggested in the error description. You
may then want to enter a higher number than the default for this field.
1.5.8 HeatBalanceSettings:ConductionFiniteDifference
This object is used to control the behavior of the Conduction Finite Difference algorithm for surface
heat transfer. The settings are global and affect how the model behaves for all the surfaces.
1.5.8.1 Inputs
1.5.9 ZoneAirHeatBalanceAlgorithm
The ZoneAirHeatBalanceAlgorithm object provides a way to select what type of solution algorithm
will be used to calculate zone air temperatures and humidity ratios. This object is an optional
object. If the default algorithm is used, this object is not required in an input file.
1.5.9.1 Inputs
1.5.9.1.1 Field: Algorithm
Three choices are allowed to select which solution algorithm will be used. The ThirdOrder-
BackwardDifference selection is the default selection and uses the third order finite difference
approximation to solve the zone air energy and moisture balance equations. The AnalyticalSo-
lution selection uses the integration approach to solve the zone air energy and moisture balance
1.5. GROUP – SIMULATION PARAMETERS 59
equations. The EulerMethod selection uses the first order finite backward difference approxima-
tion to solve the zone air energy and moisture balance equations.
And, a default IDF example is shown below:
ZoneAirHeatBalanceAlgorithm , ThirdOrderBackwardDifference ; !- Algorithm
1.5.10 ZoneAirContaminantBalance
The ZoneAirContaminantBalance object provides a way to select which contaminant type will be
simulated. Although carbon dioxide is not considered as an indoor contaminant but it is used as an
indicator of indoor air quality in buildings. From modeling point of view EnergyPlus treats carbon
dioxide as a type of contaminant. In addition to carbon dioxide, a generic contaminant type model
was also added. This object is optional, only required in the input data file if the user wishes to
model contaminant concentration levels as part of their simulation.
1.5.10.1 Inputs
1.5.10.1.1 Field: Carbon Dioxide Concentration
Input is Yes or No. The default is No. If Yes, simulation of carbon dioxide concentration levels
will be performed. If No, simulation of carbon dioxide concentration levels will not be performed.
1.5.10.2 Outputs
The following output variables are available when Carbon Dioxide Concentration = Yes.
HVAC ,Average ,Zone Air CO2 Internal Gain Volume Flow Rate [m3/s]
HVAC ,Average ,Zone Air CO2 Concentration [ppm]
60 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.5.10.2.2 Zone Air CO2 Internal Gain Volume Flow Rate [m3/s]
This is the total (net) rate of carbon dioxide internal gains/losses for a zone in m3 /s from
all types of sources or sinks. It includes impacts from three objects: ZoneContaminantSource-
AndSink:CarbonDioxide, People, and GasEquipment. Positive values denote carbon dioxide gener-
ation (gain or source), while negative values denote carbon dioxide removal (loss or sink).
1.5.10.3 Outputs
The following output variable is available when Generic Contaminant Concentration = Yes.
HVAC,Average,Zone Generic Air Contaminant Generation Volume Flow Rate [m3/s]
HVAC,Average,Zone Air Generic Air Contaminant Concentration [ppm]
1.5.10.3.2 Zone Generic Air Contaminant Generation Volume Flow Rate [m3/s]
This is the rate of generic air contaminant added (or subtracted) to a zone from all types of
sources or sinks.
1.5.11 ShadowCalculation
This object is used to control some details of EnergyPlus’s solar, shadowing and daylighting models.
There are two basic methods available for the calculations. In order to speed up the calculations,
shadowing calculations (sun position, etc.) for the default method are performed over a period of
days. Note that this value may be very important for determining the amount of sun entering your
building and by inference the amount of cooling or heating load needed for maintaining the building.
Though termed “shadowing” calculations, it in affect determines the sun position for a particular
day in a weather file period simulation. (Each design day will use the date of the design day object).
Even though weather file data contains the amount of solar radiation, the internal calculation of
sun position will govern how that affects various parts of the building. By default, the calculations
are done for every 20 days throughout a weather run period; an average solar position is chosen
and the solar factors (such as sunlit areas of surfaces) remain the same for that number of days.
When more integrated calculations are needed for controlling dynamic windows or shades, a second
method is available where solar calculations are performed at each zone timestep.
This object also allows setting up global flags to import and export exterior shading calculations
results. This enables importing pre-calculated results of the shading fractions for each exterior
building surface from external simulation tools. This also enables reusing the shading results for
parametric runs which usually do not change external shading.
1.5. GROUP – SIMULATION PARAMETERS 61
The object also allows input to disable self-shading effect from exterior surfaces from all zones,
or from a subset of zones. Two flags are defined to enable the maximal flexibility of various inter-
pretation of self-shading: one to disable shading between zones of a same zone group, the other to
disable shading between different zone groups. The shading by exterior surfaces of the specified
zones groups will be bypassed.
1.5.11.1 Inputs
1. PolygonClipping
2. PixelCounting
3. Scheduled
4. Imported
Default: PolygonClipping
If PixelCounting is selected and GPU hardware (or GPU emulation) is not available, a warn-
ing will be displayed and EnergyPlus will revert to PolygonClipping. Unlike PolygonClipping,
PixelCounting has no limitations related to zone concavity when used with any “FullInterior” solar
distribution options (i.e., it can accommodate both concave and convex zones equally).
Use of the PixelCounting method requires some overhead in passing instructions between the
CPU and the GPU. For low numbers of shading surfaces (less than about 200 for most hardware),
PolygonClipping requires less runtime than PixelCounting. However, PixelCounting runtime scales
significantly better at higher numbers of shading surfaces.
Some computers have multiple GPUs. In this case, the highest performance GPU is not always
used by default. You may want to select which GPU is used when running EnergyPlus by setting
the graphics performance preferences on your computer.
If Scheduled is chosen, the External Shading Fraction Schedule Name is required in Sur-
faceProperty:LocalEnvironment. If some exterior surfaces do not have their SurfaceProp-
erty:LocalEnvironment objects, no shading is assigned on those exterior surfaces.
If Imported is chosen, the Schedule:File:Shading object is required to define the external
file that stores all shading calculation results. The results are imported altogether by reading the
Schedule:File:Shading object during initialization. The file explicitly defines the mappings to
the surfaces. If the data for a surface is not listed in the file, no shading is assigned on this surface.
The sunlit fraction to overwrite accounts for the shading of both direct and sky diffuse solar
radiation caused by all exterior shadowing surfaces. In this case, shadow patterns on exterior
surfaces caused by detached shading, side-fins, overhangs, and exterior surfaces of all zones are
overwritten. The interior shading devices, such as window shades and blinds, should be further
calculated and applied after the importing.
62 CHAPTER 1. INPUT-OUTPUT REFERENCE
SutherlandHodgman A simpler algorithm but it works well in cases where receiving surfaces (of
shadows) are non-convex.
ConvexWeilerAtherton Only accurate where both casting and receiving surfaces are convex.
Warnings/severe errors are displayed when necessary.
Default is SutherlandHodgman. More details on polygon clipping are contained in the Engi-
neering Reference.
1.5.11.1.8 Field: Output External Shading Calculation Results This fields indicates
whether or not (Yes or No)to save internal shading calculation results to an external file, which
can be imported back as needed. This file saves external sunlit fractions for all surfaces. If Yes is
chosen, hourly shading fraction of all surfaces will be exported as a CSV file, naming as ”output
file prefix + shading” (the default name is ”eplusshading.csv” if no output file prefix is defined).
Each column of the CSV file lists the annually calculated shading fraction of each surface with
time-step interval. It only writes data for each simulation day that shadows are calculated, e.g.
once every 20 days by default. If the results are intended to be reused to be imported back
using ImportedShading in Field: External Shading Calculation Method, the Calculation
Frequency should be set as one to write year-round hourly results. Design days are not included.
The default choice is No.
1.5.11.1.9 Field: Disable Self-Shading Within Shading Zone Groups This fields spec-
ifies during shading calculation, for all surfaces in a targeted Zone Group, whether or not (Yes or
No ) the self-shading effect by exterior surfaces of all zones within the target Zone Group is dis-
abled. If Yes, self-shading will be disabled from all exterior surfaces in a given Shading Zone Group
to surfaces within the same Shading Zone Group. If both Disable Self-Shading Within Shading
Zone Groups and Disable Self-Shading From Shading Zone Groups to Other Zones = Yes, then all
self-shading from exterior surfaces will be disabled.If only one of these fields = Yes, then at least
one Shading Zone Group must be specified, or this field will be ignored. Shading from Shading:*
surfaces, overhangs, fins, and reveals will not be disabled.
1.5.11.1.10 Field: Disable Self-Shading From Shading Zone Groups to Other Zones
This fields specifies during shading calculation, for all surfaces in a targeted Zone Group, whether
or not (Yes or No ) the self-shading effect from all exterior surfaces in the target Zone Group to
other zones is disabled. If Yes, self-shading will be disabled from all exterior surfaces in a given
Shading Zone Group to all other zones in the model. If both Disable Self-Shading Within Shading
64 CHAPTER 1. INPUT-OUTPUT REFERENCE
Zone Groups and Disable Self-Shading From Shading Zone Groups to Other Zones = Yes, then all
self-shading from exterior surfaces will be disabled. If only one of these fields = Yes, then at least
one Shading Zone Group must be specified, or this field will be ignored. Shading from Shading:*
surfaces, overhangs, fins, and reveals will not be disabled.
1.5.11.1.11 Field: Shading Zone Group ZoneList Name The shading zones group speci-
fies group of zones which are controlled by the Disable Self-Shading fields. This object is extensible,
so additional fields of this type can be added to the end of this object.
Examples of this object in IDF: (note this object must be unique in an IDF)
ShadowCalculation , PixelCounting , Periodic , 1;
Note that the use of “1” in the examples is NOT the same as using Timestep calculation
frequency – “1” causes daily calculation of the sun position variables but does not change the
shadowing calculations more frequently than daily.
1.5.12 Output:Diagnostics
Sometimes, messages only confuse users – especially new users. Likewise, sometimes certain output
variables exist for only a certain condition but some take them at face value/name. Some features
may be very important but under certain instances cause problems. Thus, we have added the
diagnostic output object to be able to turn on or off certain messages, variables, and features
depending on conditions.
Both fields of the Output:Diagnostics command can accept all the applicable keys. More than
one object may be entered.
1.5.12.1 Inputs
1.5.12.1.1 Field: key1, key2
Allowable choices are:
DisplayAllWarnings – use this to get all warnings (except the developer warnings “Display-
ZoneAirHeatBalanceOffBalance”). This key sets all other display warning values to on.
DisplayExtraWarnings – use this to get all extra warnings. An example of an extra warning
is when a user enters a ceiling height or volume with the Zone object and EnergyPlus calculates
something significantly different based on the entered zone geometry.
DisplayUnusedSchedules – use this to have the unused schedules (by name) listed at the end
of the simulation.
DisplayUnusedObjects – use this to have unused (orphan) objects (by name) listed at the
end of the simulation.
DisplayAdvancedReportVariables – use this to be able to use certain advanced output
variables where the name may be misleading and you need to understand the concepts or reasons
for use. If you put in this field, then you will be able to report on these features. They are noted
in the descriptions of objects or output variables.
1.5. GROUP – SIMULATION PARAMETERS 65
1.5.13 Output:DebuggingData
There may be times when a particular input file requires additional debugging. The Out-
put:DebuggingData object may be used to report all available node data (e.g., temperature, mass
flow rate, set point, pressure, etc.). The debug data is reported to the DBG text file. The debug
file first reports the node number and name, and then all available node information for each zone
time step (Ref. Timestep).
The 2 fields of the Output:DebuggingData object can accept either a 1 (turn on) or any other
value (turn off). Only one object may be entered.
1.5.13.1 Inputs
1.5.13.1.1 Field: Report Debugging Data
This field turns on debug reporting when a value of 1 is entered. Any other value (usually 0)
disables debug reporting.
disables “reporting at all time” and debug data is only reported for each environment (RunPeriod
or SizingPeriod:DesignDay).
In IDF use:
Output:DebuggingData ,
1,1;
1.5.14 Output:PreprocessorMessage
The Output:PreprocessorMessage object can be used by preprocessor programs to EnergyPlus for
passing certain conditions/errors that might not be detected by scripts executing the EnergyPlus
system of programs. This allows EnergyPlus to intercept problems and terminate gracefully rather
than the user having to track down the exact conditions.
There is no reason for a user to enter an Output:PreprocessorMessage object but you should
encourage interface developers to use this feature. More than one Output:PreprocessorMessage
objects may be entered. Of course, no preprocessor message objects are necessary if there is no
error information to be passed.
1.5.14.1 Inputs
1.5.14.1.1 Field: Preprocessor Name
The preprocessor name (e.g. EPMacro, ExpandObjects) is entered here. Case is retained so
that messages from EnergyPlus look very similar to what a preprocessor would produce.
Output:PreprocessorMessage ,
No Preprocessor Used , !- preprocessor name
Information , !- error severity
Illustrative Message , !- message line 1
No problems for processing; !- message line 2
1.5.15 ZoneCapacitanceMultiplier:ResearchSpecial
This object is an advanced feature that can be used to control the effective storage capacity of
the zone. Capacitance multipliers of 1.0 indicate the capacitance is that of the (moist) air in the
volume of the specified zone. This multiplier can be increased if the zone air capacitance needs to
be increased for stability of the simulation or to allow modeling higher or lower levels of damping
1.5. GROUP – SIMULATION PARAMETERS 67
of behavior over time. The multipliers are applied to the base value corresponding to the total
capacitance for the zone’s volume of air at current zone (moist) conditions.
1.5.15.1 Inputs
1.5.15.1.1 Field: Name
The name of the ZoneCapacitanceMultiplier:ResearchSpecial object.
1.5.16 SimulationControl
The input for SimulationControl allows the user to specify what kind of calculations a given Ener-
gyPlus simulation will perform. For instance the user may want to perform one or more of the sizing
calculations but not proceed to an annual weather file simulation. Or the user might have all flow
rates and equipment sizes already specified and desire an annual weather without any preceding
sizing calculations. Sizing runs, even for large projects, are quickly run – they do not add much to
the overall simulation time. The SimulationControl input allows all permutations of run selection
by means of 5 yes/no inputs.
68 CHAPTER 1. INPUT-OUTPUT REFERENCE
Only one SimulationControl object is permitted for each EnergyPlus input file. While a Simu-
lationControl is needed to trigger sizing calculations, it is optional for other runs (design days, run
periods). The actions will still be shown in the eplusout.eio file (see Output Details and Examples
Document).
1.5.16.1 Inputs
1.5.16.1.1 Field: Do Zone Sizing Calculation
Input is Yes or No. The default is No. Zone Sizing (see Sizing:Zone object) performs a special
calculation, using a theoretical ideal zonal system, and determines the zone design heating and
cooling flow rates and loads, saving the results in the zone sizing arrays.
1.5.17 PerformancePrecisionTradeoffs
The PerformancePrecisionTradeoffs object can be used to control tradeoffs between performance
(speed) and precision for certain EnergyPlus features. This object enables users to choose to use
selected options that are intended to shorten the time needed for the computer to run EnergyPlus
simulations, but may tend to decrease the accuracy of results compared to methods that require
longer computing time. The field by field explanation of the object follows the next section, which
describes the procedure by an example of how to use the _perflog.csv file in conjunction with the
options available in the PerformancePrecisionTradeoffs object.
Run Direct Radiant Override Num of Min Suppress System PsyTsatFnPb MaxZone MaxAllowed Runtime
Coil Algorithm Mode Timesteps Warmup Resets Timestep TempDiff DelTemp [second]
[#/hour] [minute]
This example uses 19 different simulations to arrive at the recommended values for the Perfor-
mancePrecisionTradeoffs object, but fewer trials could have been made to reach a similar conclusion.
The first run (Run 1, Normal mode) shows the results of no performance precision tradeoffs being
applied and is the same as not having the PerformancePrecisionTradeoffs object present. It is a
good idea to use this as a first step so that a baseline of the time, errors, and oscillations are
available for reference. Runs 2 through 9 are just stepping through the Override Modes (Mode01
to Mode08). Run 10 employs the “Use Coil Direct Solution” option, but the time gain for the
simulation is not so significant. Therefore it is not used anymore in later runs. Runs 11 through 19
repeat the various override modes, but this time with the CarrollMRT radiant exchange algorithm.
The biggest savings of the computation time are from Mode01 (Run 2) application. Compared to
the Normal mode (Run 1) baseline, applying Mode01 (Run 2) immediately reduces the simulation
time by 62%, to about only 37.9% of that for the Normal baseline. Then again, by applying Mode02
(Run 3), the simulation time is reduced by 5.3% compared to Mode02 (Run 1); Mode03 (Run 4)
saves about 0.2% compared to Mode02 (Run 3); and Mode04 (Run 5) saves about 0.7% on top of
Mode03 (Run 4). Compared to the normal baseline (Run 1), Mode04 (Run 5) only consumes about
one third (35.5%) of the computation time of Run 1 Normal baseline.
Next, when Mode05 (Run 6) is applied, the simulation time is significantly reduced again—
Mode05 reduces the simulation time by nearly a half compared to Mode04 (Run 5). The run
time for Mode05 (Run 6) is only 51.8% of that for Mode04 (Run 5); and it is only 17.0% of the
Normal baseline (Run 1). The run time for Mode06 (Run 7)was reduced by 3.7% in comparison
with Mode05 (Run6).Mode07 (Run 8) cuts the simulation time by about 0.7% compared to Mode
06 (Run 7); the overall simulation time of Mode07 (Run 8) is about 16.4% of the Normal baseline.
The final Mode08 (Run 9) cuts the simulation time by another 2.1% compared to Mode07 (Run
8); and the overall run time for Mode08 is only 16.0% (or about one-seventh) of that for the Run
1 Normal baseline.
In general, the higher models—Mode05 to Mode08—significantly save the simulation time with
1.5. GROUP – SIMULATION PARAMETERS 71
both ScriptF and CarrollMRT, taking about one-fifth to one-seventh of the original Normal simu-
lation time. These modes seem to be good choices for faster simulations. However, we still need to
look at other results in the _perflog.csv file first before coming to that conclusion.
These example simulations each takes about three minutes or less to try. If your building takes
much longer than a few minutes, you might want to temporarily change the run period to just
a month or even a week to tune the PerformancePrecisionTradeoffs object inputs. If temporarily
shortening the run period is necessary, it is best to pick a month or week that has some cooling
and some heating. Just remember to set your run period back to a full year before coming to any
conclusions about the building or energy efficiency options being considered for the building.
Table 1.4: PerfLog Energy Columns
The CarrollMRT options seem to have a much more significant impact on the natural gas usage;
and the total water and the times are similar to the runtimes using ScriptF. So for this example,
CarrollMRT does not seem to be a right choice. In these cases, the computation times are not very
different from the ScriptF instances; however, the energy usage is further away from the Normal
baseline. The electricity usage differences for Runs 2 through 8 are small compared to Run 1
(the Normal baseline case), and are less than 0.34% different. The natural gas usage has more
significant differences of 0.5% to 1.1%, and the water usage differs from 0.4% to 1.1%. From an
energy perspective, these impacts for the ScriptF Runs 2 through 8 are probably tolerable.
Table 1.5: PerfLog Oscillation Columns
The number of hours any zone is oscillating for Run 1 (the Normal baseline case) using Script F
is only 2.6 hours, with almost none of the hours in the dead band and nearly all during occupancy.
This changes when considering the other ScriptF cases using Mode01 to Mode08 (Run 2 to Run
9). For Mode01 (Run 2), the oscillating hours increase but are still less than 8 hours per year.
While more than doubling, it is still considered a small change on an absolute basis. The change
is even more minor when considering the oscillating hours during occupancy. The oscillation hours
in the dead band for Mode01 (Run 2) increase about 6 hours. For Mode02 to Mode04, there is an
increase of about 1 hours for each oscillating hour categories (the total, the occupancy, and the dead
band ones), though they are considered to be a relatively minor change from the Normal baselines
especially when comparing further with those for the succeeding Mode05 and Mode08. For Mode05
to Mode08 (Runs 6 to 9), the oscillating hours increase significantly, by more than one order of
magnitude to about 161–169 hours per year. The numbers are also reflected in similar fashions for
the the oscillating hours during occupancy and for the oscillating hours during dead band. For the
CarrollMRT cases, similar trends can be observed when applying Mode01 to Mode08. The most
significant change starts from Mode05, which for both ScriptF and CarrollMRT raise the oscillating
hours to about 173–177. This is a substantial change that does indicate a significant shift in the
way the simulation program is behaving. On the other hand, the number of warnings for all the 19
cases are not too much different from each other ranging from 64 to 73, except for Run 9 which has
2,379 warnings. No severe errors are reported for any of these simulations, so no column is shown
for them.
The decision on which mode to use is up to the individual modelers. These simulations runs
can be clearly classified into three tiers based on the simulation speed (computation time) and
the numerical stability (oscillation hours): the first tier is the normal run, which incurs the least
oscillations (the best), but also takes the longest computation time; the second tier includes Mode02
to Mode04, where the simulation time can be cut to roughly one-third of that for the Normal
baseline, but with a minor penalty for increased oscillation hours; and the third tier includes Mode05
to Mode08, which can achieve an superior simulation time advantage, reaching around one-fifth to
one-seventh of that for the Normal baseline, but also with significant oscillation hours penalties
of about one order of magnitude higher. For simulations conducted in these test modes, Runs 5
(Mode04) is recommended as a balanced option for speed and numerical stability (oscillations).
It does not use direct coil solution, uses ScriptF, and Mode04. This simulation time also shows
an advantages over the other lower modes cases–it saves time compared to Mode01–Mode03—
and still has tamed the oscillating hours. Further, it does not add too much additional overrides
compared to the higher modes (Mode05–Mode08), which should be avoided if not adding value. For
1.5. GROUP – SIMULATION PARAMETERS 73
extreme speed benefit, higher modes such as Mode05 to Mode08 definitely show an advantage in
the computation time, as they cost only about only one-seventh to one-fifth of the normal base, and
only about half of those for the lower modes (such as Mode02–Mode04). However, substantially
higher oscillating hours will be incurred as a downside with these higher modes.
Additional guidance on how to make EnergyPlus faster appears in the “Tips And Tricks for Using
EnergyPlus” document that is distributed with EnergyPlus within the section titled “Platforms and
Run-Time.”
The Part Load Ratio (PLR) for a single speed coil or a multiple speed coil at speed 1 is calculated
using the equation below:
DesOutTemp − InletTemp
PLR = (1.4)
OutTempFull − InletTemp
where
PLR = Part load ratio for a single speed coil or for a multiple speed coil at speed 1;
DesOutTemp = Desired outlet temperature to meet setpoint;
InletTemp = Inlet temperature;
OutTemptFull = Outlet temperature at PLR = 1 as full output.
The Speed Ratio for a multiple speed coil at speed > 1 is calculated using the equation below:
DesOutTemp − OutTempFulli−1
SpeedRatio = (1.5)
OutTempFulli − OutTempFulli−1
where
SpeedRatio = Ratio to represent how long the higher speed runs as a fraction of the system
timestep, and the lower speed runs in the rest of the system timestep;
DesOutTemp = Desired outlet temperature to meet setpoint;
OutTempFulli = Outlet temperature of full output at the higher speed;
OutTempFulli−1 = Outlet temperature of full output at the lower speed.
Note: The choice of Load in the Control Type of the AirLoopHVAC:UnitarySystem object is
required for all coils listed in the above table. In addition, when Coil:Cooling:DX is specified under
AirLoopHVAC:UnitarySystem, the following coil configurations are supported for Direct Solution:
Single speed mode at Nominal Speed Number = 1 in the Coil:Cooling:DX:CurveFit:OperatingMode
1.5. GROUP – SIMULATION PARAMETERS 75
Mode Description
Normal No overrides
Mode01 Zone time step (TimeStep object) will be set to one timestep per hour
Mode02 Mode01 plus ZoneAirHeatBalanceAlgorithm will be set to Euler
Mode03 Mode02 plus Minimum Number of Warmup Days will be set to 1
Mode04 Mode03 plus Begin Environment Reset Mode will be set to Suppres-
sAllBeginEnvironmentResets
Mode05 Mode04 plus minimum system timestep length will be 1 hour
Mode06 Mode05 plus use cubic spline interpolations in replacement of the psy-
chrometric function PsyTsatFnPb
Mode07 Mode06 plus MaxZoneTempDiff will be set to 1.00
Mode08 Mode07 plus MaxAllowedDelTemp will be set to 0.1
Advanced Allow direct input of convergence field values
The increasing mode number roughly corresponds with increased speed. Mode01 to Mode05 are
overriding inputs in other parts of the IDF/epJSON file and is equivalent to changing those input
76 CHAPTER 1. INPUT-OUTPUT REFERENCE
directly. Mode06 offers an alternative method to calculate saturated temperature given pressure
in replacement of the psychrometric function PsyTsatFnPb. Mode07 and Mode08 are changing
convergence parameters previously not available to be modified by the user.
• construction
• orientation
• surface height
• zone
• enclosure
• solar/wind exposure
• movable insulation
Surfaces with the following objects defined are currently never grouped because there is a high
likelihood that they will experience dissimilar conditions throughout a simulation:
• ConstructionProperty:InternalHeatSource
• ZoneProperty:UserViewFactors:BySurfaceName
• WindowShadingControl
• WindowProperty:AirflowControl
• WindowMaterial:GlazingGroup:Thermochromic
• DaylightingDevice:Tubular
• WindowsCalculationEngine
• SurfaceProperty:SolarIncidentInside
Surface heat balance and interior radiation exchange calculations are performed across all sur-
faces within a group. Surface heat balance calculations are skipped for all but one surface within
a group, and subsequently updated using the results from the representative surface. For interior
radiation exchange, surfaces within a group are collected into a single area for participating in inte-
rior longwave radiation exchange. This will reduce the scale and complexity of the algorithm with
minimal impact on accuracy. Solar shading and interior solar distribution are still calculated for
each individual surface. The absorbed solar radiation used for the surface heat balance equations
within a group is the area weighted average of all surfaces within the group.
An IDF example:
PerformancePrecisionTradeoffs ,
Yes , !- Use Coil Direct Solutions
CarrollMRT; !- Zone Radiant Exchange Algorithm
Mode06 , !- Override Mode
0.3, !- MaxZoneTempDiff
0.002 , !- MaxAllowedDelTemp
Yes; !- Use Representative Surfaces for Calculations
1.5.18 HVACSystemRootFindingAlgorithm
The HVACSystemRootFindingAlgorithm object provides a way to select what type of solution
algorithm will be used to find a part load ratio or mass flow rate at given equipment/system load
in HVAC system simulations. This object is an optional object. If the default algorithm is used,
this object is not required in an input file.
78 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.5.18.1 Inputs
1.5.18.1.1 Field: Algorithm
Five choices are allowed to select which solution algorithm will be used: RegulaFalsi, Bisection,
BisectionThenRegulaFalsi, RegulaFalsiThenBisection, and Alternation. The RegulaFalsi selection
is the default selection. Bisection selection will allow the program to use the bisection method to
get a solution. The BisectionThenRegulaFalsi selection requires the program to apply the bisection
method first. After the number of iteration is above the value defined in the next field, the Regu-
laFalsi algorithm will be applied. The RegulaFalsiThenBisection selection requires the program to
apply the RegulaFalsi method first. After the number of iteration is above the value defined in the
next field, the bisection algorithm will be applied. The Alternation selection forces number of iter-
ation (defined in the next field) using RegulaFalsi first. Then Bisection and RegulaFalsi algorithm
will be alternated after the number of iteration is above the value defined in the next field.
1.5.19 Meter:Custom
A custom meter allows the user to group variables or meters onto a virtual meter that can be used
just like a normal meter created by EnergyPlus. For consistency, the items being grouped must all
be similar. A Meter:Custom cannot reference another Meter:Custom.
1.5.19.1 Inputs
1.5.19.1.1 Field: Name
This is a user defined name for the custom meter. Names for custom meters cannot duplicate
internal meter names.
• Electricity
• NaturalGas
• Propane
• FuelOilNo1
1.5. GROUP – SIMULATION PARAMETERS 79
• FuelOilNo2
• Diesel
• Gasoline
• Coal
• OtherFuel1
• OtherFuel2
• Steam
• DistrictHeating
• DistrictCooling
• Water
• Generic
Resource types are generally self-explanatory. Generic is included for convenience when a custom
meter is defined that doesn’t quite fit the “resource” categories. See the examples below.
1.5.20 Meter:CustomDecrement
The decrement custom meter is very similar to the custom meter specification but additionally
allows a predefined meter to be used as the “source” meter and the remaining items subtract from
that predefined meter.
80 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.5.20.1 Inputs
1.5.20.1.1 Field: Name
This is a user defined name for the custom meter. Names for custom meters cannot duplicate
internal meter names.
• Electricity
• NaturalGas
• Propane
• FuelOilNo1
• FuelOilNo2
• Diesel
• Gasoline
• Coal
• OtherFuel1
• OtherFuel2
• Steam
• DistrictHeating
• DistrictCooling
• Water
• Generic
Meter:Custom ,
MyBuildingElectric , !- Name
Electricity , !- Resource Type
, !- Key Name #1
Electricity:Building; !- Output Variable or Meter Name #1
Meter:CustomDecrement ,
MyBuildingOther , !- Name
Electricity , !- Resource Type
Electricity:Building , !- Source Meter Name
, !- Key Name #1
MyGeneralLights; !- Output Variable or Meter Name #1
For an example of “generic” Resource type, one might put the Building Infiltration Heat Loss
& Heat Gain on a set of custom meters:
Meter:Custom ,
Building Infiltration Heat Loss , !- Name
Generic , !- Resource Type
*, !- Key Name 1
Zone Infiltration Total Heat Loss Energy; !- Output Variable Name 1
82 CHAPTER 1. INPUT-OUTPUT REFERENCE
Meter:Custom ,
Building Infiltration Heat Gain , !- Name
Generic , !- Resource Type
*, !- Key Name 1
Zone Infiltration Total Heat Gain Energy; !- Output Variable Name 1
One can then report these values the same way one reports other standard meters.
1.6.1 Compliance:Building
The Compliance:Building object describes parameters related to compliance to building standards,
building codes, and beyond energy code programs.
1.6.1.1 Inputs
1.6.1.1.1 Field: Building Rotation for Appendix G
Building Rotation for Appendix G allows for the building model to be rotated for use with
compliance such as ASHRAE 90.1 Appendix G. Appendix G requires the building to be rotated 0,
90, 180 and 270 degrees and the values averaged to establish baseline energy use. This input works
with relative or world coordinate systems.
An example from an IDF:
Compliance:Building ,
90; !- Building Rotation for Appendix G
1.7.1 Site:Location
The location class describes the parameters for the building’s location. Only one location is allowed.
Weather data file location, if it exists, will override any location data in the IDF. Thus, for an annual
simulation, a Location does not need to be entered.
1.7. GROUP – LOCATION – CLIMATE – WEATHER FILE ACCESS 83
1.7.1.1 Inputs
1.7.1.1.1 Field: Name
This alpha field is used as an identifying field in output reports.
Most examples in this document include the comment lines that illustrate each data field’s value.
However, this is not necessary (though it makes the IDF more readable). The previous example
could also be:
Site:Location , DENVER COLORADO ,39.75 , -104.87 , -7 ,1610.26;
1.7.2 Site:VariableLocation
This variable location class describes the parameters for a moving and/or rotating building’s loca-
tion. The applications for this include:
The latitude, longitude, and orientation are all defined according to the same conventions as in
the regular “Site:Location” object.
84 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.7.2.1 Inputs
1.7.2.1.1 Field: Name
This alpha field is used as an identifying field in output reports.
Schedule:File ,
LatitudeSchedule , !- Name
, !- Schedule Type Limits Name
TripLog.csv , !- File Name
2, !- Column Number
1; !- Rows to Skip at Top
Schedule:File ,
LongitudeSchedule , !- Name
, !- Schedule Type Limits Name
TripLog.csv , !- File Name
3, !- Column Number
1; !- Rows to Skip at Top
Schedule:File ,
OrientationSchedule , !- Name
, !- Schedule Type Limits Name
TripLog.csv , !- File Name
4, !- Column Number
1; !- Rows to Skip at Top
1.7.3 SizingPeriod:DesignDay
The design day input describes the parameters to effect a “design day” simulation, often used for
load calculations or sizing equipment. Using the values in these fields, EnergyPlus “creates” a
complete days’ worth of weather data (air temperatures, solar radiation, etc.) Normal operation
uses the default range multipliers as shown in Figure 1.6 though users may choose to input their
own multiplier schedule. Likewise, normal operation specifies one “humidity indicating condition”
1.7. GROUP – LOCATION – CLIMATE – WEATHER FILE ACCESS 85
which is used to calculate the humidity ratio at maximum temperature – this is used as the constant
humidity ratio for the entire day. Again, this can be overridden by specifying a relative humidity
schedule or requesting generation of an hourly wet-bulb temperature profile. Multiple design days
may be specified.
We refer you to the ASHRAE Handbook of Fundamentals for philosophy of what parameters
are important for use as “design conditions” in sizing equipment.
In the install, the “design day files” are included for the weather file locations that are included
(weatherdata folder). All the design day definitions from the ASHRAE design conditions (latest pub-
lication date) are included, grouped by WMO region, on the main web site with the weather data.
https://www.energyplus.net/weather These files are in “macro” form but it is easy to cut and paste
the appropriate definition segments. These files include the location information as well as some loca-
tions have RunPeriodControl:DaylightSavingTime objects.
1.7.3.1 Inputs
1.7.3.1.1 Field: Name
This field, like the location name, is used simply for reporting and identification. This name
must be unique among the SizingPeriod names entered.
The multipliers are taken from the ASHRAE 2009 HOF. More explicitly, EnergyPlus creates
an air temperature for each timestep by using the entered maximum dry-bulb temperature in
conjunction with the entered daily range and the above multiplier values. The actual equation used
is shown below:
where
Tcurrent = Air temperature of current Hour of Day
TM ax = User supplied Max Dry-bulb Temperature
Trange = User supplied Daily Temperature Range
TM ultiplier = Range multiplier as shown on the above graph
The range multiplier values represent typical conditions of diurnal temperatures (i.e. the low
temperature for the day occurring about 5:00 AM and the maximum temperature for the day
occurring about 3:00 PM. Note that EnergyPlus does not shift the profile based on the time of solar
noon as is optionally allowed in ASHRAE procedures.
ASHRAE research indicates that dry-bulb and wet-bulb temperatures typically follow the same
profile, so EnergyPlus can use the default profile to generate humidity conditions (see Humidity
Indicating Type = WetBulbProfileDefaultMultipliers below).
If you specify MultiplierSchedule in this field, then you need to create a day schedule that
specifies a multiplier applied to the temperature range field (above) to create the proper dry-bulb
temperature range profile for your design day.
If you specify DifferenceSchedule in this field, then you need to create a day schedule that
specifies a number to be subtracted from dry-bulb maximum temperature for each timestep in the
day. Note that numbers in the delta schedules cannot be negative as that would result in a higher
maximum than the maximum previously specified.
If you specify TemperatureProfileSchedule in this field, then you need to create a day
schedule that specifies the actual dry-bulb temperatures throughout the day. You will not need to
include a Maximum Dry-Bulb Temperature in that field.
If you leave this field blank or enter DefaultMultipliers, then the default multipliers will be
used as shown in the “temperature range” field above.
1.7.3.1.24 Field: ASHRAE Clear Sky Optical Depth for Beam Irradiance (taub)
Optical depth for beam radiation, used only when Solar Model Indicator is ASHRAETau or
ASHRAETau2017. See next field.
1.7.3.1.25 Field: ASHRAE Clear Sky Optical Depth for Diffuse Irradiance (taud)
Optical depth for diffuse radiation, used only when Solar Model Indicator is ASHRAETau or
ASHRAETau2017. Taub and Taud values are tabulated by month for 5564 locations worldwide on
the CD that accompanies the ASHRAE HOF. ASHRAETau model Taub and Taud values are used
from the 2009 ASHRAE HOF and ASHRAETau2017 model Taub and Taud values are used from
either 2013 or 2017 ASHRAE HOF as needed.
SizingPeriod:DesignDay ,
Denver Centennial Golden Ann Htg 99% Condns DB - sched solar , !- Name
1, !- Month
13, !- Day of Month
WinterDesignDay , !- Day Type
-16, !- Maximum Dry -Bulb Temperature {C}
0.0, !- Daily Dry -Bulb Temperature Range {deltaC}
, !- Dry -Bulb Temperature Range Modifier Type
, !- Dry -Bulb Temperature Range Modifier Schedule Name
Wetbulb , !- Humidity Condition Type
-16, !- Wetbulb or DewPoint at Maximum Dry -Bulb {C}
, !- Humidity Indicating Day Schedule Name
, !- Humidity Ratio at Maximum Dry -Bulb {kgWater/kgDryAir}
, !- Enthalpy at Maximum Dry -Bulb {J/kg}
, !- Daily Wet -Bulb Temperature Range {deltaC}
83411. , !- Barometric Pressure {Pa}
2.3, !- Wind Speed {m/s}
180, !- Wind Direction {deg}
No , !- Rain Indicator
No , !- Snow Indicator
No , !- Daylight Saving Time Indicator
92 CHAPTER 1. INPUT-OUTPUT REFERENCE
Schedule:Day:Hourly ,
Winter (1/13) Beam Solar ,
Any Number ,
0 ,0 ,0 ,0 ,0 ,0 ,0 ,190 ,698 ,852 ,892 ,919 ,957 ,953 ,856 ,700 ,213 ,0 ,0 ,0 ,0 ,0 ,0 ,0;
Schedule:Day:Hourly ,
Winter (1/13) Diffuse Solar ,
Any Number ,
0,0,0,0,0,0,0,35,118,116,92,65,40,14,0,0,5,0,0,0,0,0,0,0;
1.7.3.2 Outputs
For the schedule fields in the object, several output variables can be used:
• Zone,Average,Sizing Period Site Drybulb Temperature Range Modifier Schedule Value [C]
1.7.3.2.5 Sizing Period Site Drybulb Temperature Range Modifier Schedule Value []
1.7.3.2.6 Sizing Period Site Drybulb Temperature Range Modifier Schedule Value
[deltaC]
1.7.3.2.7 Sizing Period Site Drybulb Temperature Range Modifier Schedule Value [C]
This schedule value is active when any Design Day objects have / use the drybulb temperature
range modifier schedule option. For those objects that don’t have this option, the value will be
displayed as -999.
1.7.5 SizingPeriod:WeatherFileDays
The SizingPeriod:WeatherFileDays object describes using a selected period from the “attached”
weather file to be used in load calculations or sizing equipment. The period selected can be as small
as a single day or larger. Multiple periods may be input. While this object may be used for sizing
calculations, you should also consider using design days that represent more long term extremes or
conditions.
1.7.5.1 Inputs
1.7.5.1.1 Field: Name
This field allows for an assigned name for this run period so it can be tracked easily in sizing
and other outputs.
SizingPeriod:WeatherFileDays ,
Winter including Extreme Winter days , !- Name
1,25,2,1, !- Begin/end Day/Month
1.7. GROUP – LOCATION – CLIMATE – WEATHER FILE ACCESS 95
1.7.6 SizingPeriod:WeatherFileConditionType
When the EPW files are created, a heuristic procedure identifies extreme and typical periods in
the actual weather file. This object will allow one of those periods to be selected for sizing or load
calculations (typically). Multiple objects may be input. While this object may be used for sizing
calculations, you should also consider using design days that represent more long term extremes or
conditions.
1.7.6.1 Inputs
1.7.6.1.1 Field: Name
This field allows for an assigned name for this run period so it can be tracked easily in sizing
and other outputs.
• SummerExtreme
• SummerTypical
• WinterExtreme
• WinterTypical
• AutumnTypical
• SpringTypical
• WetSeason
• DrySeason
• NoDrySeason
• NoWetSeason
• TropicalHot
• TropicalCold
96 CHAPTER 1. INPUT-OUTPUT REFERENCE
SizingPeriod:WeatherFileConditionType ,
Extreme Winter Weather Period for Design , !- Name
WinterExtreme , !- Period Selection
WinterDesignDay , !- Day Type
No , !- Use Weather File Daylight Saving Period
No; !- Use Weather File Rain and Snow Indicators
1.7.7 RunPeriod
The RunPeriod object describes the elements necessary to create a weather file simulation. Multi-
ple run periods may be input. EnergyPlus accepts weather files in the special EnergyPlus weather
format (described briefly below this document and in more detail in the Auxiliary Programs doc-
ument). These files can describe Daylight Saving Time periods as well as holidays within their
definitions. Note that the weather file also may contain design condition information, typical and
extreme period information, ground temperatures based on air temperature calculations. The Run-
Period object allows the user to override the use of both the Daylight Saving Period (i.e. use or
1.7. GROUP – LOCATION – CLIMATE – WEATHER FILE ACCESS 97
ignore) and holidays that are embedded within the weather file. The object also describes the ele-
ments necessary to use a specially crafted (likely multiple year) weather file in a simulation. These
kinds of weather files and simulations might be useful for matching utility periods or simulating
several years of differing weather data. Leap days are required when using actual weather (see
“Treat as Actual Weather” below), but will be processed and used during leap years when the days
are present in the weather file and enabled in the weather file header. Note that when the weather
is treated as non-actual, the leap day will be skipped if it is not present, resulting in incorrect day
types for the remainder of the year. Further, the weather data interpolation for the first hour can
also be specified to use Hour1 (natural) or Hour24 (considering warning up).
1.7.7.1 Inputs
1.7.7.1.1 Field: Name
This optional field allows the RunPeriod to be named for output reporting. When left blank,
the weather file location name is used. Note that the weather file location name will be appended
to this name in tabular/summary reports.
Note: EnergyPlus processed weather files available on the EnergyPlus web site: https://www.
energyplus.net/weather have neither special days specified nor daylight saving period. However, DDY
(Design Day) files produced from the ASHRAE Design Conditions that accompany the EPW files may
include a DaylightSavingPeriod object for certain locations.
in the field “turns off” the rain indicator for this period. You might use this to be able to compare
two “same location” weather files of different years, origins, etc.
1.7.8 RunPeriodControl:SpecialDays
For weather file run periods, special day run periods can be described. These will always be in
effect for the selected days in the run period. Depending on the Use Special Days value in the
RunPeriod:* object(s), these can augment any special days included on the weather file.
Note: EnergyPlus processed weather files available on the EnergyPlus web site: https://www.
energyplus.net/weather have neither special days specified nor daylight saving period. However, DDY
(Design Day) files produced from the ASHRAE Design Conditions that accompany the EPW files may
include a DaylightSavingPeriod object for certain locations.
1.7.8.1 Inputs
1.7.8.1.1 Field: Name
This alpha field is the title for the special day period. It must be unique among all the special
day period objects entered.
In the table, Month can be one of (January, February, March, April, May, June, July, August,
September, October, November, December). Abbreviations of the first three characters are also
valid.
In the table, Weekday can be one of (Sunday, Monday, Tuesday, Wednesday, Thursday, Friday,
Saturday). Abbreviations of the first three characters are also valid.
1.7.9 RunPeriodControl:DaylightSavingTime
Similar to a special day period, a daylight saving period may be entered to be applied to weather
file run periods. These will always be in effect, regardless of the value entered on the RunPeriod
object. Note that this period will always override any daylight saving period specified in a weather
file.
Note: EnergyPlus processed weather files available on the EnergyPlus web site: https://www.
energyplus.net/weather have neither special days specified nor daylight saving period.
Note: For EnergyPlus Output:Variable and Output:Meter reporting, the time stamps
are always in standard time. When daylight saving time is active, scheduled loads and
controls will shift one hour relative to standard time.
1.7.9.1 Inputs
1.7.9.1.1 Field: Start Date
This is the starting date of the daylight saving period. Note that it can be entered in several
formats as shown in Table 1.9. Date Field Interpretation.
! Syria Standard
RunPeriodControl:DaylightSavingTime , 4/1, 10/1;
Of course, these could not all appear in the same IDF as only one DaylightSavingPeriod ob-
ject per input file is allowed. More information on Daylight Saving Periods can be seen on the
web at: http://www.webexhibits.org/daylightsaving/. The ASHRAE Handbook of Fundamentals
[ASHRAE 2005] also contains information about daylight saving periods and their climatic infor-
mation now includes start and end dates for many locations.
1.7.10 WeatherProperty:SkyTemperature
Sky Temperature, or radiative sky temperature, is internally calculated by EnergyPlus with an
empirical model using sky cloudiness factors and current clear sky emissivity. For flexibility, the
following object can be entered to override the entire internal sky temperature calculation from
schedule import.
In particular, during Weather File Run Periods, the sky temperature is derived by the horizontal
infrared radiation if presented in the weather file input by default. For flexibility, the field Use
Weather File Horizontal IR can be set to “No” to ignore horizontal IR values from the weather
file and always use the specified sky model for horizontal infrared radiation and sky temperature
calculations.
By default, EnergyPlus calculates clear sky emissivity using Clark-Allen model. The following
object can also be entered to adopt alternative sky emissivity calculation methods. Alternative
methods of sky emissivity calculation include the calibrated forms of Berdahl & Martin, Brunt, and
Idso model. Their algorithms are all described in the Engineering Reference document. Much of the
literature describes the sky temperature as relative to water vapor pressure, drybulb or dewpoint
temperature.
1.7.10.1 Inputs
DifferenceScheduleDryBulbValue – the values in the schedule are subtracted from the dry-
bulb temperature value (+values would then be less than the drybulb temperature, -values would
then be greater than the drybulb temperature) for the resulting sky temperature value.
DifferenceScheduleDewPointValue – the values in the schedule are subtracted from the
dewpoint temperature value (+values would then be less than the dewpoint temperature, -values
would then be greater than the dewpoint temperature) for the resulting sky temperature value.
WeatherProperty:SkyTemperature ,
DENVER_STAPLETON Ann Clg 1% Sky Temperature modifier , !- Name
ScheduleValue , !- Calculation Type
DaySchedule5; !- Schedule Name
Schedule:Day:Interval ,
DaySchedule5 , !- Name
Temperature , !- Schedule Type Limits Name
Yes , !- Interpolate to Timestep
until: 24:00 , !- Time 1
5; !- Value Until Time 1
104 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.7.11 Site:WeatherStation
The Site:WeatherStation object is used to specify the measurement conditions for the climatic data
listed in the weather file. These conditions indicate the height above ground of the air temperature
sensor, the height above ground of the wind speed sensor, as well as coefficients that describe
the wind speed profile due to the terrain surrounding the weather station. There are necessary
correlations between the entries for this object and some entries in the Building object, specifically
the Terrain field.
Weather stations throughout the world (ref: WMO – World Meteorological Organization) take
their measurements at standard conditions:
• Weather station is in a flat, open field with little protection from the wind.
When using weather data from standard sources (e.g., TMY2, IWEC, TMY, or ASHRAE design
day data), it is not necessary to use the Site:WeatherStation object. However, if you are using
custom weather data or real-time weather data, you may need to read and understand the concepts
in the Site:WeatherStation object.
The measurement conditions at the weather station (i.e., the weather file) are used by En-
ergyPlus in conjunction with the Terrain field of the Building object, or optionally with the
Site:HeightVariation object (see below), to calculate the local variation in atmospheric proper-
ties as a function of height above ground. Outdoor air temperature decreases with height, while wind
speed increases with height. The algorithms for this calculation are in the Engineering Reference.
The Site:WeatherStation object is useful when working with a custom weather file that
includes data that were not measured at the WMO standard conditions. For example, the weather
data could be measured on site, or on the roof top of a nearby building. The wind speed profile
coefficients can be estimated from the table below or calculated beforehand using more sophisticated
techniques such as CFD modeling of the weather station terrain.
If the Site:WeatherStation object is omitted from the input file, the WMO standard mea-
surement conditions are assumed.
1.7.11.1 Inputs
1.7.11.1.1 Field: Wind Sensor Height Above Ground
The height [m] above ground for the wind speed sensor.
This would change if you had a different wind speed profile exponent or wind speed profile
boundary layer thickness at your site.
1.7.12 Site:HeightVariation
The Site:HeightVariation object is used to specify the local variation in atmospheric properties at the
site and should be used only if you require advanced control over the height-dependent variations
106 CHAPTER 1. INPUT-OUTPUT REFERENCE
for wind speed and temperature. The coefficients set by this object are used by EnergyPlus, in
conjunction with the Site:WeatherStation object (see above), to calculate the local variation in
atmospheric properties as a function of height above ground. Outdoor air temperature decreases
with height, while wind speed increases with height. The local outdoor air temperature and wind
speed are calculated separately for all zones and surfaces, and optionally for outdoor air nodes
for which a height has been specified (see OutdoorAir:Node object). With the default inputs,
wind speed falls significantly at heights lower than the weather station measurement height, and
temperature increases slightly. The algorithms for this calculation are in the Engineering Reference.
There are necessary correlations between the entries for this object and some entries in the Building
object, specifically the Terrain field.
Note that using this object overrides the wind speed profile coefficients implied by the Terrain
field of the Building object even if the wind speed profile fields are left blank. The wind speed
profile coefficients can be estimated from the table above (see Site:WeatherStation) or calculated
beforehand using more sophisticated techniques such as CFD modeling of the site terrain.
1.7.12.1 Inputs
1.7.12.1.1 Field: Wind Speed Profile Exponent
The wind speed profile exponent for the terrain surrounding the site. The exponent can be
estimated from the table above (see Site:WeatherStation) or calculated beforehand using more
sophisticated techniques, such as CFD modeling of the site terrain. Note that using this object
overrides the wind speed profile coefficients implied by the Terrain field of the Building object
even if this field is left blank. This field can be set to zero to turn off all wind dependence on height.
Note that the Air Temperature Sensor Height in the Site:WeatherStation object should also be
set to zero in order to force the local outdoor air temperatures to match the weather file outdoor
air temperature. This change is required because the Site:WeatherStation object assumes an
air temperature gradient of 0.0065 K/m. This field can be set to zero to turn off all temperature
dependence on height.
Site:HeightVariation ,
0.22, !- Wind Speed Profile Exponent
370, !- Wind Speed Profile Boundary Layer Thickness {m}
0.0065; !- Air Temperature Gradient Coefficient {deltaC/m}
1.7.13 Site:GroundTemperature:BuildingSurface
Ground temperatures are used for the ground heat transfer model. There can be only one ground
temperature object included, and it is used as the outside surface temperature for all surfaces
with Outside Boundary Condition = Ground. The object is options if you have no surfaces with
ground contact. The outside surface temperature for individual surfaces can be specified using the
OtherSideCoefficients (ref: SurfaceProperty:OtherSideCoefficients) object that allows Toutside to
be set with a schedule. This permits using any number of different outside face temperatures in
addition to the ground temperature.
Caution: The “undisturbed” ground temperatures calculated by the weather converter should not
be used in building losses but are appropriate to be used in the Site:GroundTemperature:Shallow and
Site:GroundTemperature:Deep objects. The reasoning (for building losses) is that these values are
too extreme for the soil under a conditioned building. For best results, use the Slab or Basement
program described in this document to calculate custom monthly average ground temperatures (see
the Ground Heat Transfer section). This is especially important for residential applications and very
small buildings. If one of these ground temperature preprocessors is not used, for typical commercial
buildings in the USA, a reasonable default value is 2 ◦C less than the average indoor space temperature.
More information about determining appropriate ground temperatures is given in the Auxiliary
Programs document.
1.7.13.1 Inputs
1.7.13.1.1 Field: Month Temperature(s) – 12 fields in all
Each numeric field is the monthly ground temperature (degrees Celsius) used for the indicated
month (January = 1st field, February = 2nd field, etc.)
An IDF example:
Site: GroundTemperature:BuildingSurface ,19 ,20 ,20 ,20 ,20 ,20 ,20 ,20 ,20 ,20 ,20 ,20;
1.7.14 Site:GroundTemperature:Shallow
Site:GroundTemperature:Shallow are used by the Surface Ground Heat Exchanger (i.e. object:
GroundHeatExchanger:Surface). Only one shallow ground temperature object can be included.
108 CHAPTER 1. INPUT-OUTPUT REFERENCE
Note that the ground temperatures included in full year weather files may be suitable of being used
for the values in these fields – namely, the .5 m depth temperatures that are calculated for “undisturbed”
soil of “typical” conditions. However, you may wish to use some other change effect – based on the
weather conditions of the building location.
This object may be used for objects requiring “undisturbed” ground temperatures. In these
instances, the “name” input field is not required.
1.7.14.1 Inputs
1.7.14.1.1 Field: Month Temperature(s) – 12 fields in all
Each numeric field is the monthly surface ground temperature (degrees Celsius) used for the
indicated month (January = 1st field, February = 2nd field, etc.)
An IDF example:
Site: GroundTemperature:Shallow ,4 ,4 ,6,6,10,10,15,15,14,14,8 ,8;
1.7.15 Site:GroundTemperature:Deep
Site:GroundTemperature:Deep are used by the Pond Ground Heat Exchanger object (i.e. object:
GroundHeatExchanger:Pond). Only one deep ground temperature object can be included.
Note that the ground temperatures included in full year weather files may be suitable of being used
for the values in these fields – namely, the 4 m depth temperatures that are calculated for “undisturbed”
soil of “typical” conditions. However, you may wish to use some other change effect – based on the
weather conditions or special knowledge of the building location.
This object may be used for objects requiring “undisturbed” ground temperatures. In these
instances, the “name” input field is not required.
1.7.15.1 Inputs
1.7.15.1.1 Field: Month Temperature(s) – 12 fields in all
Each numeric field is the monthly deep ground temperature (degrees Celsius) used for the
indicated month (January = 1st field, February = 2nd field, etc.)
An IDF example:
Site: GroundTemperature:Deep , 16 ,16 ,16 ,16 ,16 ,16 ,16 ,16 ,16 ,16 ,16 ,16;
1.7.16 Site:GroundTemperature:Undisturbed:FiniteDifference
Site:GroundTemperature:Undisturbed:FiniteDifference may be used by all objects requiring “undis-
turbed” ground temperatures. The object uses a 1D finite difference heat transfer model which uses
the weather file to obtain surface boundary conditions. An annual simulation is run on the model
during it’s initialization until the annual ground temperature profile has reached steady periodic be-
havior. Once steady periodic behavior is reached, the ground temperatures are cached for retrieval
during the rest of the simulation.
1.7. GROUP – LOCATION – CLIMATE – WEATHER FILE ACCESS 109
1.7.16.1 Inputs
1.7.16.1.1 Field: Soil Thermal Conductivity
The thermal conductivity of the soil, in W/m-K.
1.7.17 Site:GroundTemperature:Undisturbed:KusudaAchenbach
Site:GroundTemperature:Undisturbed:KusudaAchenbach may be used by all objects requiring
“undisturbed” ground temperatures. It provides an undisturbed ground temperature based on
the correlation developed by Kusuda T. and P. Achenbach. 1965. The correlation uses three
parameters for ground temperature at the surface to define a correlation for undisturbed ground
temperatures as a function of depth and time. If one thinks of the ground temperature for a
given depth as a sinusoid, the average ground temperature, amplitude (average difference between
maximum ground temperature and minimum ground temperature), and the phase shift (day of
minimum surface temperature) are all required to define the correlation.
If the parameters are left blank they can be autocalculated by including soil surface temperatures
in the input using the Site:GroundTemperature:Shallow object. They can also be calculated by using
the CalcSoilSurfTemp preprocessor.
Kusuda, T. and P.R. Achenbach. 1965. ‘Earth Temperatures and Thermal Diffusivity at Se-
lected Stations in the United States.’ ASHRAE Transactions. 71(1): 61-74.
110 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.7.18 Site:GroundTemperature:Undisturbed:Xing
Site:GroundTemperature:Undisturbed:Xing may be used by all objects requiring “undisturbed”
ground temperatures. It provides an undisturbed ground temperature based on the correlation
developed by Xing, 2014. The correlation is a 5 parameter, 2 harmonic model based on the work
of Lord Kelvin (Thomson, 1862). The average soil surface temperature and two sets of surface
temperature amplitude and phase shift must be provided. Parameters for 4000+ international
locations can be found in Xing, 2014.
Thomson, W. 1862. ‘On the Reduction of Observations of Underground Temperature, with
applications to Professor Forbes’ Edinburgh Observations and the continued Calton Hill Series.’
Proceedings of the Royal Society of Edinburgh. IV: 342-346.
Xing, L. 2014. Estimations of Undisturbed Ground Temperatures using Numerical and Analyt-
ical Modeling. Ph.D. Diss. Oklahoma State University, Stillwater, OK.
1.7.18.1 Inputs
1.7.18.1.1 Field: Soil Thermal Conductivity
The thermal conductivity of the soil, in W/m-K.
1.7. GROUP – LOCATION – CLIMATE – WEATHER FILE ACCESS 111
1.7.19 Site:GroundDomain:Slab
This section documents the input object used to simulate ground coupled heat transfer with horizon-
tal building surfaces within EnergyPlus. Horizontal ground surfaces within EnergyPlus interact with
the Site:GroundDomain object by utilizing the SurfaceProperty:OtherSideConditionsModel object.
By utilizing this object, multiple horizontal surfaces can be coupled to the same Site:GroundDomain
object. Each horizontal surface may also have its unique ground domain, however, runtime will be
adversely affected.
Generally, there are two scenarios which Site:GroundDomain is equipped to model: in-grade
slabs and on-grade slabs.
The in-grade slab option can be used to simulate situations when the upper slab surface is near
the ground surface level. For this situation, slab’s upper surface must interact with the zone via
an OSCM boundary. Due to this, the FloorConstruction object for the zone floor must include
a thin layer of the upper floor material. Horizontal and vertical insulation are modeled by the
GroundDomain in this scenario. Horizontal insulation can be modeled as covering the full horizontal
112 CHAPTER 1. INPUT-OUTPUT REFERENCE
surface, or it can be limited to the perimeter regions only. In the latter case, the perimeter insulation
width must be specified.
The on-grade slab option can be used to simulate situations when the lower slab surface is
near the ground surface level. In this situation, the entire floor must be included within the
floor construction object. Vertical insulation is modeled by the GroundDomain in this scenario.
Horizontal insulation can only be modeled as covering the full horizontal surface.
1.7.19.1 Inputs
1.7.19.1.1 Field: Name
Alpha field used as a unique identifier for each ground domain.
1.7.19.2 Outputs
The following output variables are available.
• Zone, Average, Zone Coupled Surface Heat Flux [W/m2]
• Zone, Average, Zone Coupled Surface Temperature [C]
1.7. GROUP – LOCATION – CLIMATE – WEATHER FILE ACCESS 117
1.7.20 Site:GroundDomain:Basement
This section documents the input object used to simulate ground coupled heat transfer with
underground zones within EnergyPlus. Zone surfaces within EnergyPlus interact with the
Site:GroundDomain:Basement object by utilizing the SurfaceProperty:OtherSideConditionsModel
object. Two separate OSCM are required for the basement vertical and horizontal surfaces.
Vertical wall surfaces will interact with the first OSCM while the horizontal floor surface will
interact with the second OSCM. Basement floor and wall surfaces are constructed normally
by using the BuildingSurface:Detailed object, with the outside boundary condition being the
OtherSideConditionsModel for the basement floor or wall. The outside surface of the wall being
the interface between the ground domain and the EnergyPlus zone. Horizontal and vertical ground
insulation are simulated by the ground domain, and therefore should not be included in the wall
and floor construction objects.
Site:GroundDomain:Basement ,
CoupledBasement , !- Name
10, !- Ground Domain Depth {m}
1, !- Aspect ratio
5, !- Perimeter offset {m}
1.8, !- Soil Thermal Conductivity {W/m-K}
3200, !- Soil Density {kg/m3}
836, !- Soil Specific Heat {J/kg -K}
30, !- Soil Moisture Content Volume Fraction {percent}
50, !- Soil Moisture Content Volume Fraction at Saturation {percent}
Site: GroundTemperature :Undisturbed:KusudaAchenbach , !- Type of Undisturbed Ground Temperature Object
KATemps , !- Name of Undisturbed Ground Temperature Object
1, !- Evapotranspiration Ground Cover Parameter
BasementFloorOSCM , !- Name of Basement Floor Boundary Condition Model
Yes , !- Basement Horizontal Underfloor Insulation Present (Yes/No)
Basement Insulation , !- Basement Horizontal Insulation Underfloor Material Name
Full , !- Full Horizontal or Perimeter Only (Full/Perimeter)
, !- Perimeter width (m)
2.5, !- Depth of Basement Wall In Ground Domain {m}
BasementWallOSCM , !- Name of Basement Wall Boundary Condition Model
Yes , !- Basement Wall Vertical Insulation Present(Yes/No)
Basement Insulation , !- Basement Wall Vertical Insulation Material Name
2.5, !- Vertical insulation depth from surface (m)
Hourly; !- Domain Update interval. (Timestep , Hourly)
4; ! Mesh Density Parameter
1.7.20.1 Inputs
1.7.20.1.1 Field: Name
Alpha field used as a unique identifier for each basement domain. Multiple basements domains
can be simulated simultaneously, however, each domain must have a unique name. Additionally,
despite the ability to simulate multiple domains simultaneously, these domains do not interact with
118 CHAPTER 1. INPUT-OUTPUT REFERENCE
each other and are treated as independent domains with boundary conditions given by the model
parameters below.
1.7.20.2 Outputs
1.7.21 Site:GroundTemperature:FCfactorMethod
Site:GroundTemperature:FCfactorMethod is used only by the underground walls or slabs-on-grade
or underground floors defined with C-factor (Construction:CfactorUndergroundWall) and F-factor
(Construction:FfactorGroundFloor) method for code compliance calculations where detailed con-
struction layers are unknown. Only one such ground temperature object can be included. The
monthly ground temperatures for this object are close to the monthly outside air temperatures
delayed by three months. If user does not input this object in the IDF file, it will be defaulted to
the 0.5m set of monthly ground temperatures from the weather file if they are available. Entering
these will also overwrite any ground temperatures from the weather file in the F and C factor usage.
If neither is available, an error will result.
1.7.21.1 Inputs
1.7.21.1.1 Field: Month Temperature(s) – 12 fields in all
Each numeric field is the monthly ground temperature (degrees Celsius) used for the indicated
month (January = 1st field, February = 2nd field, etc.)
And, the IDF example:
Site: GroundTemperature:FCfactorMethod , 9.5, 3.5, -0.7, -1.7, -0.6, 3.6, 9.3, 14, 18.2, 22.7, 21.2, 16.8;
1.7.22 Site:GroundReflectance
Ground reflectance values are used to calculate the ground reflected solar amount. This fractional
amount (entered monthly) is used in this equation:
1.7.22.1 Inputs
1.7.22.1.1 Field: Month Average Ground Reflectance(s) – 12 fields in all
Each numeric field is the monthly average reflectivity of the ground used for the indicated month
(January = 1st field, February = 2nd field, etc.)
And use in an IDF:
Site:GroundReflectance ,
0.600 , !January Ground Reflectance
0.600 , !February Ground Reflectance
0.400 , !March Ground Reflectance
0.300 , !April Ground Reflectance
0.200 , !May Ground Reflectance
0.200 , !June Ground Reflectance
0.200 , !July Ground Reflectance
0.200 , !August Ground Reflectance
0.200 , !September Ground Reflectance
0.200 , !October Ground Reflectance
0.300 , !November Ground Reflectance
0.400; !December Ground Reflectance
1.7. GROUP – LOCATION – CLIMATE – WEATHER FILE ACCESS 123
1.7.23 Site:GroundReflectance:SnowModifier
It is generally accepted that snow resident on the ground increases the basic ground reflectance.
EnergyPlus allows the user control over the snow ground reflectance for both “normal ground
reflected solar” calculations (see above) and snow ground reflected solar modified for daylighting.
These are entered under this object and both default to 1 (same as normal ground reflectance – no
special case for snow which is a conservative approach).
1.7.23.1 Inputs
1.7.23.1.1 Field: Ground Reflected Solar Modifier
This field is a decimal number which is used to modified the basic monthly ground reflectance
when snow is on the ground (from design day input or weather data values).
Outputs will show both the inputs from the above object as well as monthly values for both
Snow Ground Reflectance and Snow Ground Reflectance for Daylighting.
1.7.24 Site:WaterMainsTemperature
The Site:WaterMainsTemperature object is used to calculate water temperatures delivered by under-
ground water main pipes. The mains temperatures are used as default, make-up water temperature
inputs for several plant objects, including: WaterUse:Equipment, WaterUse:Connections,
WaterHeater:Mixed and WaterHeater:Stratified. The mains temperatures are also used in
the water systems objects to model the temperature of cold water supplies.
Water mains temperatures are a function of outdoor climate conditions and vary with time of
year. A correlation has been formulated to predict water mains temperatures based on two weather
inputs:
These values can be calculated from annual weather data using the auxillary program CalcSoil-
SurfTemp preprocessor. For more information on the water mains temperatures correlation, see the
EnergyPlus Engineering Document.
Alternatively, the Site:WaterMainsTemperature object can read values from a schedule. This is
useful for measured data or when water comes from a source other than buried pipes, e.g., a river
or lake.
If there is no Site:WaterMainsTemperature object in the input file, a default constant value of
◦
10 C is assumed.
1.7.24.1 Inputs
1.7.24.1.1 Field: Calculation Method
This field selects the calculation method and must have the keyword Schedule, Correlation
or CorrelationFromWeatherFile. If calculation method is CorrelationFromWeatherFile, the two
numeric input fields below are ignored. Instead, EnergyPlus calculates them from weather file.
1.7.25 Site:Precipitation
The Site:Precipitation object is used to describe the amount of water precipitation at the building
site over the course of the simulation run period. Precipitation includes both rain and the equivalent
water content of snow. Precipitation is not yet described well enough in the many building weather
data files. So this object can be used to provide the data using Schedule objects that define rates
of precipitation in meters per hour.
A set of schedules for site precipitation have been developed for USA weather locations and
are provided with EnergyPlus in the data set called PrecipitationSchedulesUSA.idf. The user can
1.7. GROUP – LOCATION – CLIMATE – WEATHER FILE ACCESS 125
develop schedules however they want. The schedules in the data set were developed using En-
ergyPlus’ weather file (EPW) observations and the average monthly precipitation for the closest
weather site provided by NOAA. EPW files for the USA that were based on TMY or TMY2 include
weather observations for Light/Moderate/Heavy rainfall, however most international locations do
not include these observations. The values were modeled by taking the middle of the ranges quoted
in the EPW data dictionary. The assumed piecewise function is shown below.
Light = 0.0125
Amount (m/hour) = Moderate = 0.052 (1.10)
Heavy = 0.1
The values were inserted on hour by hour basis for the month based on the observations. Then
each month was rescaled to meet the average precipitation for the month based on the 30-year
average (1971-2000) provided by the NOAA/NCDC. Therefore, the flags in the EPW file match the
precipitation schedules for the USA. Note that summing the average monthly precipitation values
will not give you the average yearly precipitation. The resulting value may be lower or higher than
the average yearly value.
Once the typical rainfall pattern and rates are scheduled, the Site:Precipitation object provides
a method of shifting the total rainfall up or down for design purposes. Wetter or drier conditions
can be modeled by changing the Design Annual Precipitation although the timing of precipitation
throughout the year will not be changed.
1.7.25.1 Inputs
1.7.25.1.1 Field: Precipitation Model Type
Choose rainfall modeling options. Only available option is ScheduleAndDesignLevel.
Site:Precipitation ,
ScheduledAndDesignLevel , !- Precipitation Model Type
0.75, !- Design Level Total Annual Precipitation {m/yr}
PrecipitationSchd , !- Schedule Name for Precipitation Rates
0.80771; !- Average Total Annual Precipitation {m/yr}
1.7.26 RoofIrrigation
The RoofIrrigation object is used to describe the amount of irrigation on the ecoroof surface over
the course of the simulation runperiod. This object is used to provide irrigation data using Schedule
objects that define rates of irrigation in meters per hour. These schedules can be one of two types:
Schedule, or SmartSchedule.
1.7.26.1 Inputs
1.7.28 Site:SolarAndVisibleSpectrum
The SolarAndVisibleSpectrum object is used to specify the solar and visible spectrum data which
is used as spectral weighting function to calculate the window performance (transmittance and
absorptance) in EnergyPlus. This is a unique object, if it is missing from an IDF file, the default
(same as EnergyPlus version 8.0) solar and visible spectrum data will be used.
1.7.28.1 Inputs
1.7.28.1.1 Field: Name
This field specifies the name of the SolarAndVisibleSpectrum object.
1.7.29 Site:SpectrumData
The Site:SpectrumData object holds the user defined solar or visible spectrum data. For solar
spectrum, up to 107 pairs of (wavelength, spectrum) can be entered. For visible spectrum, up to
81 pairs can be entered.
1.7.29.1 Inputs
1.7.29.1.1 Field: Name
This field specifies the name of the SpectrumData object. The name must be unique across all
SpectrumData objects.
Note that these data values may be interpolated from “hour” points (ref: Weather Data Hourly
Interpolation). Most of the data values represent the “average” over the reporting resolution period.
The outdoor wet-bulb temperature is derived (at the timestep) from the values for dry-bulb tem-
perature, humidity ratio and barometric pressure.
The outdoor humidity ratio is derived (at the timestep) from the dry-bulb temperature, relative
humidity and barometric pressure.
14
Horizontal IR
Sky T emperature = − 273.15Conversion f rom Kelvin to Centigrade (1.11)
Sigma
1.7.31.16 Site Ground Reflected Solar Radiation Rate per Area [W/m2]
The ground reflected solar amount (W/m2 ) is derived from the Beam Solar, Diffuse Solar, User
specified Ground Reflectance (for month) and Solar Altitude Angle:
Groundreflectedsolar
= (Beamsolar · cos (SolarAltitudeAngle) + Diffusesolar) · Groundreflectancemonth (1.12)
where if the calculation returns a value < 0.0, then 0.0 will be reported.
For example, a normal office building may have normal “occupancy” rules during the weekdays
but significantly different use on weekend. For this, you would set up rules/schedules based on
the weekdays (Monday through Friday, in the US) and different rules/schedules for the weekend
(Saturday and Sunday, in the US). However, you could also specially designate SummerDesignDay
and WinterDesignDay schedules for sizing calculations. These schedules can be activated by setting
the Day Type field in the Design Day object to the appropriate season (SummerDesignDay for
cooling design calculations; WinterDesignDay for heating design calculations).
In a different building, such as a theater/playhouse, the building may only have occupancy
during certain weeks of the year and/or certain hours of certain days. If it was every week, you
could designate the appropriate values during the “regular” days (Sunday through Saturday). But
this would also be an ideal application for the “CustomDay1” and/or “CustomDay2”. Here you
would set the significant occupancy, lighting, and other schedules for the custom days and use
unoccupied values for the normal weekdays. Then, using a weather file and setting special day
periods as appropriate, you will get the “picture” of the building usage during the appropriate
periods.
1.8.2 ScheduleTypeLimits
Schedule types can be used to validate portions of the other schedules. Hourly day schedules,
for example, are validated by range – minimum/maximum (if entered) – as well as numeric type
(continuous or discrete). Annual schedules, on the other hand, are only validated for range – as the
numeric type validation has already been done.
1.8.2.1 Inputs
1.8.2.1.1 Field: Name
This alpha field should contain a unique (within the schedule types) designator. It is referenced
wherever Schedule Type Limits Names can be referenced.
and IP units. This field is not used by EnergyPlus. The available options are shown below. If none
of these options are appropriate, select Dimensionless.
• Dimensionless
• Temperature
• DeltaTemperature
• PrecipitationRate
• Angle
• Convection Coefficient
• Activity Level
• Velocity
• Capacity
• Power
• Availability
• Percent
• Control
• Mode
1.8.4 Schedule:Day:Hourly
The Schedule:Day:Hourly contains an hour-by-hour profile for a single simulation day.
1.8.4.1 Inputs
1.8.4.1.1 Field: Name
This field should contain a unique (within all DaySchedules) designation for this schedule. It is
referenced by WeekSchedules to define the appropriate schedule values.
1.8. GROUP – SCHEDULES 139
1.8.5 Schedule:Day:Interval
The Schedule:Day:Interval introduces a slightly different way of entering the schedule values for a
day. Using the intervals, you can shorten the “hourly” input of the “Schedule:Day:Hourly” object to
2 fields. And, more importantly, you can enter an interval that represents only a portion of an hour.
Schedule values are “given” to the simulation at the zone timestep, so there is also a possibility of
“interpolation” from the entries used in this object to the value used in the simulation.
1.8.5.1 Inputs
1.8.5.1.1 Field: Name
This field should contain a unique (within all DaySchedules) designation for this schedule. It is
referenced by WeekSchedules to define the appropriate schedule values.
If “Linear” is entered, then the value that is used is based on the linear interpolation between
successive values. With linear, if the value at 1:00 is 0.0 and the value at 2:00 is 10.0, with fifteen
minute timesteps, the value at 1:15 would be 2.5, the value at 1:30 would be 5.0 and the value at
1:45 would be 7.5.
1.8.6 Schedule:Day:List
To facilitate possible matches to externally generated data intervals, this object has been included.
In similar fashion to the Schedule:Day:Interval object, this object can also include “sub-hourly”
values but must represent a complete day in its list of values.
1.8.6.1 Inputs
1.8.6.1.5 Field Value 1 (same definition for each value – up to 1440 (24*60) allowed)
1.8.8 Schedule:Week:Daily
1.8.8.1 Inputs
1.8.8.1.1 Field: Name
This field should contain a unique (within all WeekSchedules) designation for this schedule. It
is referenced by Schedules to define the appropriate schedule values.
142 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.8.8.1.2 Field: Schedule Day Name Fields (12 day types – Sunday, Monday, … )
These fields contain day schedule names for the appropriate day types. Days of the week (or
special days as described earlier) will then use the indicated hourly profile as the actual schedule
value.
An IDF example:
Schedule:Week:Daily , Week on Peak ,
Day On Peak ,Day On Peak ,Day On Peak ,
Day On Peak ,Day On Peak ,Day On Peak ,
Day On Peak ,Day On Peak ,Day On Peak ,
Day On Peak ,Day On Peak ,Day On Peak;
1.8.9 Schedule:Week:Compact
Further flexibility can be realized by using the Schedule:Week:Compact object. In this the fields,
after the name is given, a “for” field is given for the days to be assigned and then a dayschedule
name is used.
1.8.9.1 Inputs
1.8.9.1.1 Field:Name
This field should contain a unique (within all WeekSchedules) designation for this schedule. It
is referenced by Schedules to define the appropriate schedule values.
1.8.10 Schedule:Year
The yearly schedule is used to cover the entire year using references to week schedules (which in
turn reference day schedules). If the entered schedule does not cover the entire year, a fatal error
will result.
1.8.10.1 Inputs
1.8.10.1.1 Field: Name
This field should contain a unique (between Schedule:Year, Schedule:Compact, and Sched-
ule:File) designation for the schedule. It is referenced by various “scheduled” items (e.g. Lights,
People, Infiltration) to define the appropriate schedule values.
1.8.10.1.3 Field Set (WeekSchedule, Start Month and Day, End Month and Day)
Each of the designated fields is used to fully define the schedule values for the indicated time
period). Up to 53 sets can be used. An error will be noted and EnergyPlus will be terminated if an
incomplete set is entered. Missing time periods will also be noted as warning errors; for these time
periods a zero (0.0) value will be returned when a schedule value is requested. Each of the sets has
the following 5 fields:
The following definition will generate an error (if any scheduled items are used in the simulation):
Schedule:Year ,MySchedule ,Fraction ,4,1,9,30;
1.8.11 Schedule:Compact
For flexibility, a schedule can be entered in “one fell swoop”. Using the Schedule:Compact object,
all the features of the schedule components are accessed in a single command. Like the “regular”
schedule object, each schedule:compact entry must cover all the days for a year. Additionally, the
validations for DaySchedule (i.e. must have values for all 24 hours) and WeekSchedule (i.e. must
have values for all day types) will apply. Schedule values are “given” to the simulation at the zone
timestep, so there is also a possibility of “interpolation” from the entries used in this object to the
value used in the simulation.
This object is an unusual object for description. For the data the number of fields and position
are not set, they cannot really be described in the usual Field # manner. Thus, the following
description will list the fields and order in which they must be used in the object. The name and
schedule type are the exceptions:
1.8.11.1 Inputs
1.8.11.1.1 Field: Name
This field should contain a unique (between Schedule:Year, Schedule:Compact, and Sched-
ule:File) designation for the schedule. It is referenced by various “scheduled” items (e.g. Lights,
People, Infiltration) to define the appropriate schedule values.
! Schedule Continuous
Schedule:Compact ,
Continuous ,
on/off ,
146 CHAPTER 1. INPUT-OUTPUT REFERENCE
Through: 12/31 ,
For: AllDays ,
Until: 24:00 , 1.0;
1.8.12 Schedule:Constant
The constant schedule is used to assign a constant hourly value. This schedule is created when a
fixed hourly value is desired to represent a period of interest (e.g., always on operation mode for
supply air fan).
1.8.12.1 Inputs
ScheduleTypeLimits ,
On/Off , !- Name
0, !- Lower Limit Value
1, !- Upper Limit Value
DISCRETE , !- Numeric Type
Availability; !- Unit Type
1.8. GROUP – SCHEDULES 147
1.8.13 Schedule:File
At times, data is available from a building being monitored or for factors that change throughout
the year. The Schedule:File object allows this type of data to be used in EnergyPlus as a schedule.
Schedule:File can also be used to read in hourly or sub-hourly schedules computed by other software
or developed in a spreadsheet or other utility.
The format for the data file referenced is a text file with values separated by commas (or other
optional delimiters) with one line per hour. The file may contain header lines that are skipped. The
file should contain values for an entire year (8760 or 8784 hours of data) or a warning message will
be issued. Multiple schedules may be created using a single external data file or multiple external
data files may be used. The first row of data must be for January 1, hour 1 (or timestep 1 for
subhourly files).
Schedule:File may be used along with the FuelFactors object and TDV files in the DataSets
directory to compute Time Dependent Valuation based source energy as used by the California
Energy Commission’s Title 24 Energy Code. See Fuel Factor for more discussion on Time Dependent
Valuation.
Two optional fields: Interpolate to Timestep and Minutes per Item allow for the input of
sub-hourly schedules (similar to the Schedule:Day:List object).
1.8.13.1 Inputs
A sub-hourly indication. Note that this is identical to an hourly file because there are 60 minutes
per item – the number of hours defaults to 8760 and the column separator defaults to a comma. If
the number of minutes per item had been, say, 15, then the file would need to contain 8760*4 or
35,040 rows for this item.
Schedule:File ,
elecTDVfromCZ06com , !- Name
Any Number , !- Schedule Type Limits Name
DataSets\TDV\ TDV_2008_kBtu_CTZ06 .csv , !- File Name
1, !- Column Number
4, !- Rows to Skip at Top
, !- Number of Hours of Data
, !- Column Separator
, !- Interpolate to Timestep
60; !- Minutes per Item
1.8.13.2 Outputs
An optional report can be used to gain the values described in the previous Schedule objects. This
is a condensed reporting that illustrates the full range of schedule values – in the style of input:
DaySchedule, WeekSchedule, Annual Schedule.
! will give them on hourly increments (day schedule resolution)
Output:Schedules , Hourly;
! will give them at the timestep of the simulation
Output:Schedules , Timestep;
This report is placed on the eplusout.eio file. Details of this reporting are shown in the Output
Details and Examples document.
1.8.14 Schedule:File:Shading
The Schedule:File:Shading object allows shading schedules to be imported altogether from a file
exported using ShadowCalculation Output External Shading Calculation Results. The object can
also be used to read in hourly or sub-hourly schedules of the sunlit fraction of all exterior surfaces
computed by other software or developed in a spreadsheet or other utility.
The format for the data file is Comma-separated values (CSV). The CSV file referenced is a
text file with values separated by commas (or other optional delimiters) with one line per timestep.
Each column stores the annual shading sunlit fraction schedule data of an exterior surface. The
150 CHAPTER 1. INPUT-OUTPUT REFERENCE
sunlit fraction is only overwritten and used when the sun is above horizon at a certain time step. To
map to the surface, each column should name its column header exactly the same with the surface
name defined in the Surface:Detailed object. If any surface name is missing, the sunlit fraction
of this surface will be set to 1.0 during the run period, which means no shading will be assigned
for this surface, and a warning message will be issued. The file should contain values for an entire
year with the exact same number of rows as the total number of time steps in a year (number of
days in a year * number of hours per day * number of time steps per hour). Time step should be
consistent with the setting in the Timestep object. Otherwise, an error will be issued.
The first row of the CSV file should be the header, and the first column of the CSV file should
be the timestamp and is not imported.
With a Schedule:File:Shading object defined, the shading schedules for all exterior surfaces
(if defined) can be imported altogether without repeatedly defining Schedule:File objects.
1.8.14.1 Inputs
1.8.14.1.1 Field: File Name
This field contains the name of the file that contains the data for the shading schedules. The
field should include a full path with file name, for best results. The field must be ≤ 100 characters.
The file name must not include commas or an exclamation point. A relative path or a simple
file name should work with version 7.0 or later when using EP-Launch even though EP-Launch
uses temporary directories as part of the execution of EnergyPlus. If using RunEPlus.bat to run
EnergyPlus from the command line, a relative path or a simple file name may work if RunEPlus.bat
is run from the folder that contains EnergyPlus.exe.
Here is an IDF example:
Schedule:File ,
eplusshading.csv; !- Name of File
• Material
• Material:NoMass
• Material:AirGap
• Material:RoofVegetation
• Material:InfraredTransparent
Material is the “preferred” type of material. This requires knowledge of many of the thermal
properties of the material, but it allows EnergyPlus to take into account the thermal mass of
the material and thus allows the evaluation of transient conduction effects. Material:NoMass is
similar in nature but only requires the thermal resistance (R-value) rather than the thickness,
thermal conductivity, density, and specific heat. Note that using a simple R-value only material
forces EnergyPlus to assume steady state heat conduction through this material layer. Finally,
Material:AirGap should only be used for an air gap between other layers in a construction. This
type assumes that air is sufficiently lightweight to require only an R-value. In addition, since it is
not exposed to any external environment, surface properties such as absorptance are not necessary.
Material:RoofVegetation is used to help model “green roofs”. Material:InfraredTransparent is used
similarly to the NoMass materials. Each of these materials is described in more detail below.
There are several material additions that can be made to the basic material properties. These
additional material types are:
• MaterialProperty:MoisturePenetrationDepth:Settings
• MaterialProperty:HeatAndMoistureTransfer:SorptionIsotherm
• MaterialProperty:HeatAndMoistureTransfer:Diffusion
• MaterialProperty:HeatAndMoistureTransfer:Settings
• MaterialProperty:HeatAndMoistureTransfer:Redistribution
• MaterialProperty:HeatAndMoistureTransfer:Suction
• MaterialProperty:HeatAndMoistureTransfer:ThermalConductivity
• MaterialProperty:PhaseChange
• MaterialProperty:PhaseChangeHysteresis
These material property objects are used in conjunction with the basic material specification and
reference back to the name of the basic material type. Without the basic material type specified the
program, will give a severe error and terminate. For example, specifying the moisture materials and
changing the HeatBalanceAlgorithm to a moisture simulation will allow the moisture simulation to
take place.
152 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.9.3 Material
This definition should be used when the four main thermal properties (thickness, conductivity,
density, and specific heat) of the material are known. This syntax is used to describe opaque
construction elements only.
When a Material is used for the Construction of a building surface, care should be taken to
not attempt to model assemblies that were not included in the intended scope of applicability for
the underlying heat transfer models. The building surface models are for normal applications
to building energy efficiency where the main focus is on assemblies with some thermal resistance.
Extremely thin and/or highly conductive material layers should be neglected from the Construction
rather than included because they will not contribute to the assembly’s overall thermal resistance
or heat capacity. For some cases, thin and/or highly conductive materials are a serious problem
for the heat transfer modeling and the values for thickness, conductivity, density and specific heat
are checked for appropriateness. This check calculates the Material’s thermal diffusivity from the
inputs for conductivity, density, and specific heat and compares it to a maximum threshold of 1.E-5
(m2 /s). If the diffusivity is above this threshold, then the program checks if the layer is sufficiently
thick and may issue a warning if it is too thin and highly conductive.
The absorptance values in this object impart surface properties to the construction and should
be applied to the thermally significant inner and outer layers in the overall assembly. Attempting
to trick the program by modeling thin “paint” layers to apply surface properties is not a good idea;
the models were not intended to support such strategies.
1.9.3.1 Inputs
1.9.3.1.1 Field: Name
This field is a unique reference name that the user assigns to a particular material. This name
can then be referred to by other input data (ref: Construction object).
1.9.4 Material:NoMass
Use this definition when only the thermal resistance (R value) of the material is known. This object
is used to describe opaque construction elements.
1.9.4.1 Inputs
1.9.4.1.1 Field: Name
This field is a unique reference name that the user assigns to a particular material. This name
can then be referred to by other input data (ref: Construction object).
1.9.5 Material:InfraredTransparent
A Infrared Transparent surface is similar to a resistance-only surface. The surface will actually
participate in the transfer of visible and solar radiation by doing a wavelength transformation and
making all short wave length radiation that is incident on the surface into long wave length radiation
and having it participate in the long wavelength radiant exchange. Note the ConvectionCoef-
ficient instructions that follow the Infrared Transparent construction object below.
1.9.5.1 Inputs
1.9.5.1.1 Field: Name
This field contains the unique name (across all Material objects) for the Infrared Transparent
material.
A Infrared Transparent surface should not participate in a convective/conductive exchange be-
tween the zones it separates. In order to minimize this effect, the ConvectionCoefficients object
must be used for the surfaces referencing the Infrared Transparent (IRT) construction.
An example idf object specification for use with the IRT surface is shown below. Note that
surfaces are not described in this example
Material:InfraredTransparent ,
IRTMaterial1; !- Name
Construction ,
IRTSurface , !- Name
IRTMaterial1; !- Outside Layer
SurfaceProperty:ConvectionCoefficients ,
Bottom:Top , !- SurfaceName
Outside , !- Convection Type 1
value , !- Convection Value Type 1
156 CHAPTER 1. INPUT-OUTPUT REFERENCE
SurfaceProperty:ConvectionCoefficients ,
SecondLevel:Bottom , !- SurfaceName
Outside , !- Convection Type 1
value , !- Convection Value Type 1
0.1, !- Convection value 1 {W/m2 -K}
, !- Convection Schedule 1
Inside , !- Convection Type 2
value , !- Convection Value Type 2
0.1; !- Convection value 2 {W/m2 -K}
SurfaceProperty:ConvectionCoefficients ,
SecondLevel:Top , !- SurfaceName
Outside , !- Convection Type 1
value , !- Convection Value Type 1
0.1, !- Convection value 1 {W/m2 -K}
, !- Convection Schedule 1
Inside , !- Convection Type 2
value , !- Convection Value Type 2
0.1; !- Convection value 2 {W/m2 -K}
SurfaceProperty:ConvectionCoefficients ,
ThirdLevel:Bottom , !- SurfaceName
Outside , !- Convection Type 1
value , !- Convection Value Type 1
0.1, !- Convection value 1 {W/m2 -K}
, !- Convection Schedule 1
Inside , !- Convection Type 2
value , !- Convection Value Type 2
0.1; !- Convection value 2 {W/m2 -K}
1.9.6 Material:AirGap
This material is used to describe the air gap in an opaque construction element. Glass elements use
a different property (WindowGas) to describe the air between two glass layers.
1.9.6.1 Inputs
1.9.6.1.1 Field: Name
This field is a unique reference name that the user assigns to a particular material. This name
can then be referred to by other input data (ref: Construction object).
1.9.7 MaterialProperty:MoisturePenetrationDepth:Settings
This material is used to describe the nine moisture material properties that are used in the EMPD
(Effective Moisture Penetration Depth) heat balance solution algorithm. The EMPD algorithm
is a simplified, lumped moisture model that simulates moisture storage and release from interior
surfaces. The model uses convective mass transfer coefficients that are determined by existing heat
and mass transfer relationships, e.g. the Lewis relation. The EMPD model includes two fictitious
layers of material with uniform moisture content: a surface layer, which accounts for short-term
moisture buffering, and a deep layer, which accounts for more slowly responding moisture buffering.
The model calculates the moisture transfer between the air and the surface layer and between the
surface layer and the deep layer. This moisture transfer impacts the zone humidity, and also impacts
the zone temperature through latent-to-sensible conversion from the heat of adsorption.
This moisture model is used when the appropriate EMPD moisture materials are specified and
the Solution Algorithm parameter is set to MoisturePenetrationDepthConductionTransferFunction.
1.9.7.1 Inputs
1.9.7.1.1 Field: Name
This field is a unique reference name that the user assigns to a particular material. This name
can then be referred to by other input data (ref: Construction object).
2 × 10−7 · T 0.81
δperm,air =
Pambient
where T is the temperature [C] and Pambient the ambient atmospheric pressure [Pa].
u = a · ϕb + c · ϕd
where
a, b, c, d = Coefficients to define the relationship between the material’s moisture content and
the surface air relative humidity
158 CHAPTER 1. INPUT-OUTPUT REFERENCE
u = Moisture content defined as the mass fraction of water contained in a material, per mass of
dry material [kg/kg]
ϕ = Surface air relative humidity [0 to 1],
where
δperm = water vapor permeability in the material, kg/m-s-Pa (see Vapor diffusion resistance
factor above)
Psat = saturated vapor pressure at some nominal temperature, Pa
τsurf = cycle period of typical RH variations, s. 24 hours (87600 s) is often used.
ρmaterial = dry density of material, kg/m^3
du
dϕ
= slope of moisture soprtion curve, abϕb−1 + cdϕd−1
If this field is left blank or set to autocalculate, the above equation will be used to calculate
the surface layer penetration depth assuming a τsurf of 24 hours. To use a period different than
24 hours, the equation above can be used to calculate the penetration depth based on a different
value of τsurf . The penetration depth can also be entered as an empirical value, as in Woods and
Winkler, 2016. If calculating dEM P D,surf , the assumed value of τsurf should not be less than 4x the
simulation timestep to ensure an accurate and stable solution.
where each term is the same as the surface layer, except that the cycle period is different. This
is usually on the order of weeks for the deep layer.
1.9. GROUP – SURFACE CONSTRUCTION ELEMENTS 159
If this field is left blank or set to autocalculate, the above equation will be used to calculate
the deep layer penetration depth assuming a τdeep of three weeks. To use a period different than
3 weeks, the equation above can be used to calculate the penetration depth based on a different
value of τdeep . The penetration depth can also be entered as an empirical value, as in Woods and
Winkler, 2016.
This set of inputs is for gypsum board with density 750 kg/m^3. This also assumes 2 coats of
latex paint:
MaterialProperty: MoisturePenetrationDepth :Settings ,
Concrete , !- Name
6.0, !- Water Vapor Diffusion Resistance Factor {dimensionless}
0.0065 , !- Moisture Equation Coefficient a {dimensionless}
0.65, !- Moisture Equation Coefficient b {dimensionless}
0.022 , !- Moisture Equation Coefficient c {dimensionless}
10, !- Moisture Equation Coefficient d {dimensionless}
0.021 , !- Surface Layer Penetration Depth {m}
0.08, !- Deep Layer Penetration Depth {m}
0.0003 , !- Coating Layer Thickness {m}
6000; !- Coating Layer Water Vapor Diffusion Resistance Factor {dimensionless}
Finally, here are values representing the empirical whole-house inputs from Woods et al., 2014
(see Engineering Reference). Density is 800 kg/m^3:
MaterialProperty: MoisturePenetrationDepth :Settings ,
Concrete , !- Name
8.0, !- Water Vapor Diffusion Resistance Factor {dimensionless}
0.012 , !- Moisture Equation Coefficient a {dimensionless}
1, !- Moisture Equation Coefficient b {dimensionless}
0, !- Moisture Equation Coefficient c {dimensionless}
1, !- Moisture Equation Coefficient d {dimensionless}
0.019 , !- Surface Layer Penetration Depth {m}
0.113 , !- Deep Layer Penetration Depth {m}
160 CHAPTER 1. INPUT-OUTPUT REFERENCE
Other materials inputs can be estimated using the equations above and material properties
from a variety of sources, such as Kumaran, 1996, the WUFI simulation software, or the ASHRAE
1018-RP report.
1.9.7.2 Outputs
1.9.7.2.1 EMPD Surface Inside Face Water Vapor Density [kg/m3]
The vapor density at the inside face of the surface, where the EMPD moisture balance solution
algorithm is applied. This is the actual surface, separated from the zone air only by the convective
mass transfer coefficient.
Units are kg of water per cubic meter of air.
1.9.8 MaterialProperty:PhaseChange
Advanced/Research Usage: This material is used to describe the temperature dependent mate-
rial properties that are used in the Conduction Finite Difference solution algorithm. This conduction
model is done when the appropriate materials are specified and the Solution Algorithm parame-
ter is set toConductionFiniteDifference. This permits simulating temperature dependent thermal
conductivity and phase change materials (PCM) in EnergyPlus.
1.9.8.1 Inputs
1.9.8.1.1 Field: Name
This field is a regular material name specifying the material with which this additional temper-
ature dependent property information will be associated.
where:
ko is the 20C value of thermal conductivity(normal idf input)
k1 is the change in conductivity per degree temperature difference from 20C
HeatBalanceAlgorithm ,
ConductionFiniteDifference ;
Timestep ,
12;
Material ,
E1 - 3 / 4 IN PLASTER OR GYP BOARD , !- Name
Smooth , !- Roughness
1.9050000E-02, !- Thickness {m}
0.7264224 , !- Conductivity {W/m-K}
1601.846 , !- Density {kg/m3}
836.8000 , !- Specific Heat {J/kg -K}
0.9000000 , !- Thermal Absorptance
0.9200000 , !- Solar Absorptance
0.9200000; !- Visible Absorptance
MaterialProperty:PhaseChange ,
E1 - 3 / 4 IN PLASTER OR GYP BOARD , !- Name
0.0, !- Temperature coefficient ,thermal conductivity(W/m K2)
-20., !- Temperature 1, C
0.01, !- Enthalpy 1 at –20C, (J/kg)
20., !- Temperature 2, C
33400 , !- Enthalpy 2, (J/kg)
20.5, !- temperature 3, C
70000 , !- Enthalpy 3, (J/kg)
100., !- Temperature 4, C
137000; !- Enthalpy 4, (J/kg)
1.9.9 MaterialProperty:PhaseChangeHysteresis
This object is used to describe an advanced level of physics belonging to phase change materials
used in building envelopes. The base phase change input object describes a single process curve
whereby a material moves from a crystallized to liquid state and back. This input object adds a
hysteresis effect, allowing the melting/freezing process to follow different curves, representing an
effect that is commonly seen in actual building envelope phase change material applications. This
object also allows users to enter characteristic properties of the processes instead of a detailed
temperature/enthalpy curve, making it more amenable for studies in which the user does not have
the detailed test data required to generate the temperature/enthalpy curve. For more information
on the use of phase change materials (PCM) with hysteresis, see the Conduction Finite Difference
Solution Algorithm section of the EnergyPlus Engineering Reference document.
164 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.9.9.1 Inputs
The MaterialProperty:PhaseChangeHysteresis object includes the following inputs. For the charac-
teristic curve properties, see the engineering reference.
1.9.9.1.2 Field: Latent Heat during the Entire Phase Change Process
This is the total amount of latent heat absorbed or discharged during the transition from solid
to liquid or back, in Joules. The shapes of the enthalpy curves differ based on direction, but the
total amount of energy from one state to the other does not.
HeatBalanceAlgorithm , ConductionFiniteDifference ;
Timestep , 12;
Material ,
E1 - 3 / 4 IN PLASTER OR GYP BOARD , !- Name
Smooth , !- Roughness
1.9050000E-02, !- Thickness {m}
0.7264224 , !- Conductivity {W/m-K}
1601.846 , !- Density {kg/m3}
836.8000 , !- Specific Heat {J/kg -K}
0.9000000 , !- Thermal Absorptance
0.9200000 , !- Solar Absorptance
0.9200000; !- Visible Absorptance
MaterialProperty:PhaseChangeHysteresis ,
E1 - 3 / 4 IN PLASTER OR GYP BOARD , !- Name
10000 , !- Latent Heat of Fusion {J/kg}
0.5, !- Liquid State Thermal Conductivity {W/m-K}
1500, !- Liquid State Density {kg/m3}
2000, !- Liquid State Specific Heat {J/kg -K}
1, !- High Temperature Difference of Melting Curve {deltaC}
23, !- Peak Melting Temperature {C}
1, !- Low Temperature Difference of Melting Curve {deltaC}
0.5, !- Solid State Thermal Conductivity {W/m-K}
1600, !- Solid State Density {kg/m3}
2000, !- Solid State Specific Heat {J/kg -K}
1, !- High Temperature Difference of Freezing Curve {deltaC}
20, !- Peak Freezing Temperature {C}
1; !- Low Temperature Difference of Freezing Curve {deltaC}
1.9.9.2 Outputs
The MaterialProperty:PhaseChangeHysteresis object also includes the following outputs. The Con-
duction Finite Difference solution algorithm uses a finite difference solution technique where the
166 CHAPTER 1. INPUT-OUTPUT REFERENCE
surfaces are divided into a nodal arrangement. These outputs are specific to Conduction Finite
Difference solution.
The following output variables are applicable to all opaque heat transfer surfaces when using
Solution Algorithms ConductionFiniteDifference. Note that the “X” in the list and descriptions
below must be replaced by a number that indicates the node at which the variables are being
reported. So, for example, to report the surface temperature for node 7, one would use “CondFD
Surface Temperature Node 7”.
• -2 = liquid
• -1 = melting
• 0 = transition
• 1 = freezing
• 2 = crystallized
1.9.10 MaterialProperty:VariableThermalConductivity
This object is used to describe the temperature dependent material properties that are used in the
CondFD (Conduction Finite Difference) solution algorithm. This conduction model is used when
the appropriate CondFD materials are specified and the Solution Algorithm parameter is set to
condFD.
1.9.10.1 Inputs
1.9.10.1.1 Field: Name
This field is a regular material name specifying the material with which this additional temper-
ature dependent property information will be associated.
HeatBalanceAlgorithm ,
ConductionFiniteDifference ;
Timestep ,
12;
Material ,
PCMPlasterBoard , !- Name
Smooth , !- Roughness
1.9050000E-02, !- Thickness {m}
168 CHAPTER 1. INPUT-OUTPUT REFERENCE
MaterialProperty:VariableThermalConductivity ,
PCMPlasterBoard , !- Name
0, !- Temperature 1 {C}
4.2, !- Thermal Conductivity 1 {W/m-K}
22, !- Temperature 2 {C}
4.2, !- Thermal Conductivity 2 {W/m-K}
22.1, !- Temperature 3 {C}
2.5, !- Thermal Conductivity 3 {W/m-K}
100, !- Temperature 4 {C}
2.5; !- Thermal Conductivity 4 {W/m-K}
1.9.10.2 Outputs
The Conduction Finite Difference solution algorithm uses a finite difference solution technique where
the surfaces are divided into a nodal arrangement. These outputs are specific to Conduction Finite
Difference solution.
The following output variables are applicable to all opaque heat transfer surfaces when using
Solution Algorithms ConductionFiniteDifference. Note that the “X” in the list and descriptions
below must be replaced by a number that indicates the Node at which the variables are being
reported. So, for example, to report the surface temperature for node 7, one would use “CondFD
Surface Temperature Node 7”.
indicates heat flowing towards the inside face of the surface. Note that this matches the sign con-
vention for Surface Inside Face Conduction Heat Transfer Rate per Area and is opposite the sign
of Surface Outside Face Conduction Heat Transfer Rate per Area.
1.9.10.2.4 CondFD Surface Heat Capacitance Outer Half Node <X> [W/m2-K]
1.9.10.2.5 CondFD Surface Heat Capacitance Inner Half Node <X> [W/m2-K]
These will output the half-node heat capacitance in surfaces being simulated with Conduc-
tionFiniteDifference. The key values for this output variable are the surface name. The nodes are
numbered from outside to inside of the surface. The full listing will appear in the RDD file. For this
output, the heat capacitance is defined as the product of specific heat, density, and node thickness.
Zero is reported for R-layer half-nodes and for undefined half-nodes. There is no outer half-node for
Node 1 which is the outside face of the surface, and there is no inner half-node for Node N which
is the inside face of the surface. CondFD Surface Heat Capacitance is only available when the user
includes a Output:Diagnostics, DisplayAdvancedReportVariables designation in the input file.
1.9.11 MaterialProperty:HeatAndMoistureTransfer:Settings
Advanced/Research Usage: This object is used to describe two of the seven additional ma-
terial properties needed for the CombinedHeatAndMoistureFiniteElement heat balance solution
algorithm. The settings object is used when the solutions algorithm is set to CombinedHeatAnd-
MoistureFiniteElement and the appropriate material properties are assigned to each material. This
permits the simulation of the moisture dependent thermal properties of the material as well as the
transfer of moisture through, into and out of the material into the zone or exterior.
In addition to the Porosity and Initial Water content properties described here, five additional
properties, described by tabulated relationships between variables, are required. These properties
are;
• MaterialProperty:HeatAndMoistureTransfer:SorptionIsotherm
• MaterialProperty:HeatAndMoistureTransfer:Suction
• MaterialProperty:HeatAndMoistureTransfer:Redistribution
• MaterialProperty:HeatAndMoistureTransfer:Diffusion
• MaterialProperty:HeatAndMoistureTransfer:ThermalConductivity
All materials in a construction are required to have all material properties defined for HAMT
to work.
Within the MaterialProperty:HeatAndMoistureTransfer:Settings object the following fields are
defined.
1.9.11.1 Inputs
1.9.11.1.1 Field: Material Name
This field is a unique reference name that the user assigns to a particular material. This name
can then be referred to by other input data.
170 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.9.12 MaterialProperty:HeatAndMoistureTransfer:SorptionIsotherm
Advanced/Research Usage: This material property is used in conjunction with the Combined-
HeatAndMoistureFiniteElement heat balance solution algorithm.
The Isotherm data relates the moisture, or water content [kg/m3] of a material with the relative
humidity (RH). The water content is expected to increase as relative humidity increases, starting
at zero content at 0.0relative humidity fraction and reaching a maximum, defined by the porosity,
at 1.0 relative humidity fraction, which corresponds to 100% relative humidity. Relative humidities
are entered as fraction for this object ranging from 0.0 to 1.0. These two extremes (0.0 and 1.0) are
automatically set by the HAMT solution. However, if they are entered they will be used as extra
data points. Data should be provided with increasing RH and moisture content up to as high an
RH as possible to provide a stable solution. One possible reason for the following error message
may be that a material has a very rapid increase in water content for a small change in RH, which
can happen if the last entered water content point is at a low RH and the material has a very high
porosity.
** Warning ** HeatAndMoistureTransfer : Large Latent Heat for Surface ROOF
Another potential reason for this error being generated is the use of inappropriate values for
Vapor Transfer Coefficients. See the SurfaceProperties:VaporCoefficients object in the Advanced
Surface Concepts group.
1.9.12.1 Inputs
1.9.12.1.1 Field: Material Name
This field is a unique reference name that the user assigns to a particular material. This name
can then be referred to by other input data.
1.9.13 MaterialProperty:HeatAndMoistureTransfer:Suction
Advanced/Research Usage:This material property is used in conjunction with the Combined-
HeatAndMoistureFiniteElement heat balance solution algorithm.
The suction data relates the liquid transport coefficient, under suction, to the water content
of a material. A data point at zero water content is required. The liquid transport coefficient at
the highest entered water content value is used for all liquid transport coefficient values above this
water content. These coefficients are used by HAMT when the rain flag is set in the weather file.
1.9.13.1 Inputs
1.9.13.1.1 Field: Material Name
This field is a unique reference name that the user assigns to a particular material. This name
can then be referred to by other input data.
1.9.14 MaterialProperty:HeatAndMoistureTransfer:Redistribution
Advanced/Research Usage:This material property is used in conjunction with the Combined-
HeatAndMoistureFiniteElement heat balance solution algorithm.
The redistribution data relates the liquid transport coefficient to the water content of a material
under normal conditions. A data point at zero water content is required. The liquid transport
coefficient at the highest entered water content value is used for all liquid transport coefficient
values above this water content. These coefficients are used by the Heat and Moisture Transfer
algorithm when the rain flag is NOT set in the weather file.
1.9.14.1 Inputs
1.9.14.1.1 Field: Material Name
This field is a unique reference name that the user assigns to a particular material. This name
can then be referred to by other input data.
1.9.15 MaterialProperty:HeatAndMoistureTransfer:Diffusion
Advanced/Research Usage:This material property is used in conjunction with the Combined-
HeatAndMoistureFiniteElement heat balance solution algorithm.
The MU data relates the vapor diffusion resistance factor (dimensionless) to the relative humidity
as fraction(RH). A data point at zero RH is required. The vapor diffusion resistance factor at the
highest entered relative humidity (RH) value is used for all vapor diffusion resistance factor values
above this RH. The relative humidity maximum value in fraction is 1.0.
1.9.15.1 Inputs
1.9.15.1.1 Field: Material Name
This field is a unique reference name that the user assigns to a particular material. This name
can then be referred to by other input data.
1, !- Number of Mu Points
0, !- Relative Humidity Fraction 1
180; !- Water Vapor Diffusion Resistance Factor 1
1.9.16 MaterialProperty:HeatAndMoistureTransfer:ThermalConductivity
Advanced/Research Usage:This material property is used in conjunction with the Combined-
HeatAndMoistureFiniteElement heat balance solution algorithm.
The thermal data relates the thermal conductivity [W/m-K] of a material to the moisture or
water content [kg/m3]. A data point at zero water content is required. The thermal conductivity
at the highest entered water content value is used for all thermal conductivity values above this
water content. If this object is not defined for a material then the algorithm will use a constant
value entered in the Material object for all water contents.
1.9.16.1 Inputs
1.9.16.1.1 Field: Material Name
This field is a unique reference name that the user assigns to a particular material. This name
can then be referred to by other input data.
Users can select any one of the Temperature, Relative Humidity or Water Content variables for
any cell to be reported, using the following naming scheme for the output variable.
176 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.9.18 WindowMaterial:Glazing
In the following, for exterior windows, “front side” is the side of the glass closest to the outside air
and “back side” is the side closest to the zone the window is defined in. For interzone windows,
“front side” is the side closest to the zone adjacent to the zone the window is defined in and “back
side” is the side closest to the zone the window is defined in.
1.9.18.1 Inputs
For uncoated glass, when alternative optical properties are available—such as thickness, visible
index of refraction, and visible extinction coefficient—they can be converted to equivalent visible
transmittance and reflectance values using the equations given in “Glass Optical Properties
Conversion.”
1.9.18.1.15 Field: Dirt Correction Factor for Solar and Visible Transmittance
This is a factor that corrects for the presence of dirt on the glass. The program multiplies the
fields “Solar Transmittance at Normal Incidence” and “Visible Transmittance at Normal Incidence”
by this factor if the material is used as the outer glass layer of an exterior window or glass door.1
If the material is used as an inner glass layer (in double glazing, for example), the dirt correction
factor is not applied because inner glass layers are assumed to be clean. Using a material with dirt
correction factor < 1.0 in the construction for an interior window will result in an error message.
Representative values of the dirt correction factor are shown in Table 1.13.
1
If Optical Data Type = Spectral, the program multiplies the solar and visible transmittance at each wavelength
by the dirt correction factor.
1.9. GROUP – SURFACE CONSTRUCTION ELEMENTS 179
The default value of the dirt correction factor is 1.0, which means the glass is clean.
It is assumed that dirt, if present, has no effect on the IR properties of the glass.
Figure 1.12: Comparison between transmittance properties of transparent glass (Solar Diffusing =
No) and translucent glass (Solar Diffusing = Yes).
1.9.18.1.19 Field: Window Glass Spectral and Incident Angle Transmittance Data
Set Table Name
If Optical Data Type = SpectralAndAngle, this is the name of a spectral and angle data set of
transmittance defined with a curve or table object with two independent variables. The first and
second independent variables must be Angle, and Wavelength, respectively. The restriction is based
on internal dataset use. Each dataset is divided into subsets for each incident angle internally.
1.9.18.1.20 Field: Window Glass Spectral and Incident Angle Front Reflectance Data
Set Table Name
If Optical Data Type = SpectralAndAngle, this is the name of a spectral and angle data set of
front reflectance defined with a curve or table object with two independent variables. The first and
second independent variables must be Angle, and Wavelength, respectively. The restriction is based
on internal dataset use. Each dataset is divided into subsets for each incident angle internally.
1.9.18.1.21 Field: Window Glass Spectral and Incident Angle Back Reflectance Data
Set Table Name
If Optical Data Type = SpectralAndAngle, this is the name of a spectral and angle data set of
back reflectance defined with a curve or table object with two independent variables. The first and
second independent variables must be Angle, and Wavelength, respectively. The restriction is based
on internal dataset use. Each dataset is divided into subsets for each incident angle internally.
It should be pointed out that when Optical Data Type = SpectralAndAngle for a glass layer
in a construction, the table input data are converted into polynomial curve fits with 6 coefficients,
so that all outputs of optical properties for the same construction will be curve values for a given
incident angle. Therefore, the values may be slightly different from input values.
IDF examples of Spectral average and using a Spectral data set:
WindowMaterial:Glazing ,
CLEAR 3MM , !- Name
SpectralAverage , !- Optical Data Type
, !- Window Glass Spectral Data Set Name
0.003 , !- Thickness {m}
0.837 , !- Solar Transmittance at Normal Incidence
1.9. GROUP – SURFACE CONSTRUCTION ELEMENTS 181
WindowMaterial:Glazing ,
SPECTRAL GLASS INNER PANE , ! Material name
Spectral , ! Optical data type {SpectralAverage or Spectral}
TestSpectralDataSet , ! Name of spectral data set
0.0099 , ! Thickness {m}
, ! Solar transmittance at normal incidence
, ! Solar reflectance at normal incidence: front side
, ! Solar reflectance at normal incidence: back side
, ! Visible transmittance at normal incidence
, ! Visible reflectance at normal incidence: front side
, ! Visible reflectance at normal incidence: back side
0.0, ! IR transmittance at normal incidence
0.84, ! IR emissivity: front side
0.84, ! IR emissivity: back side
0.798; ! Conductivity {W/m-K}
WindowMaterial:Glazing ,
SPECTRAL AND ANGLE GLASS INNER PANE , ! Material name
SpectralAndAngle , ! Optical data type {SpectralAverage or Spectral}
, !- Name of spectral data set
0.0099 , ! Thickness {m}
, !- Solar transmittance at normal incidence
, !- Solar reflectance at normal incidence: front side
, !- Solar reflectance at normal incidence: back side
, !- Visible transmittance at normal incidence
, !- Visible reflectance at normal incidence: front side
, !- Visible reflectance at normal incidence: back side
0.0, !- IR transmittance at normal incidence
0.84, !- IR emissivity: front side
0.84, !- IR emissivity: back side
0.798 , !- Conductivity {W/m-K}
, !- Dirt Correction Factor for Solar and Visible Transmittance
, !- Solar Diffusing
, !- Young 's modulus
, !- Poisson 's ratio
TranmittanceDataSet , !- Window Glass Spectral+Incident Angle Transmittance Data Set Table Name
FrontReflectanceDataSet , !- Window Glass Spectral+Incident Angle Front Reflectance Data Set Table
Name
BackReflectanceDataSet ; !- Window Glass Spectral+Incident Angle Back Reflectance Data Set Table Name
WindowMaterial:Glazing ,
Glass_5012_Layer , !- Layer name : CLEAR_6.PPG
BSDF , !- Optical Data Type
, !- Spectral Data name
0.005664 , !- Thickness
, !- Solar Transmittance
, !- Solar Front Reflectance
, !- Solar Back Reflectance
, !- Visible Transmittance
, !- Visible Front Reflectance
, !- Visible Back reflectance
0.000000 , !- IR Transmittance
182 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.9.19 WindowMaterial:Glazing:RefractionExtinctionMethod
This is an alternative way of specifying glass properties. Index of refraction and extinction coeffi-
cient are given instead of the transmittance and reflectance values used in WindowMaterial:Glazing.
However, unlike WindowMaterial:Glazing, WindowMaterial:Glazing:RefractionExtinctionMethod
is restricted to cases where the front and back optical properties of the glass are the same.
This means it cannot be used for glass with a coating on one side. In that case Win-
dowMaterial:Glazing should be used. Also, unlike WindowMaterial:Glazing, WindowMate-
rial:Glazing:RefractionExtinctionMethod does not allow input of glass wavelength-by-wavelength
(spectral) properties.
1.9.19.1 Inputs
1.9.19.1.1 Field: Name
The name of the glass layer. It corresponds to a layer in a window construction.
1.9.19.1.10 Field: Dirt Correction Factor for Solar and Visible Transmittance
This is a factor that corrects for the presence of dirt on the glass. It multiplies the solar and
visible transmittance at normal Incidence (which the program calculates from the input values of
thickness, solar index of refraction, solar extinction coefficient, etc.) if the material is used as the
outer glass layer of an exterior window or glass door. If the material is used as an inner glass layer
(in double glazing, for example), the dirt correction factor is not applied because inner glass layers
are assumed to be clean. Using a material with dirt correction factor < 1.0 in the construction for
an interior window will result in an error message.
Representative values of the direct correction factor are shown in Table 1.13.
The default value of the dirt correction factor is 1.0, which means the glass is clean. It is assumed
that dirt, if present, has no effect on the IR properties of the glass.
T = 0.86156
n = 1.526
2
1.526 − 1
r=
1.526 + 1
τ = 0.93974
R = 0.07846
1.9.21 WindowMaterial:GlazingGroup:Thermochromic
Thermochromic (TC) materials have active, reversible optical properties that vary with temper-
ature. Thermochromic windows are adaptive window systems for incorporation into building en-
velopes. Thermochromic windows respond by absorbing sunlight and turning the sunlight energy
into heat. As the thermochromic film warms it changes its light transmission level from less ab-
sorbing to more absorbing. The more sunlight it absorbs the lower the light level going through
it. By using the suns own energy the window adapts based solely on the directness and amount of
sunlight. Thermochromic materials will normally reduce optical transparency by absorption and/or
reflection, and are specular (maintaining vision).
1.9. GROUP – SURFACE CONSTRUCTION ELEMENTS 185
1.9.21.1 Inputs
1.9.21.1.1 Field: Name
A unique user assigned name for a particular thermochromic glass material.
1.9.21.1.2 Field Set (Optical Data Temperature, Window Material Glazing Name)
This object is extensible, so additional sets of the next two fields can be added to the end of
this object.
WindowMaterial:Gas ,
AIR 6MM , !- Name
Air , !- Gas Type
0.0063; !- Thickness {m}
WindowMaterial:Glazing ,
TCGlazing0 , !- Name
SpectralAverage , !- Optical Data Type
186 CHAPTER 1. INPUT-OUTPUT REFERENCE
WindowMaterial:Glazing ,
TCGlazing20 , !- Name
SpectralAverage , !- Optical Data Type
, !- Window Glass Spectral Data Set Name
0.0030 , !- Thickness
0.2442 , !- Solar Transmittance at Normal Incidence
0.7058 , !- Front Side Solar Reflectance at Normal Incidence
0.7058 , !- Back Side Solar Reflectance at Normal Incidence
0.3192 , !- Visible Transmittance at Normal Incidence
0.6308 , !- Front Side Visible Reflectance at Normal Incidence
0.6308 , !- Back Side Visible Reflectance at Normal Incidence
0.0000 , !- Infrared Transmittance at Normal Incidence
0.9000 , !- Front Side Infrared Hemispherical Emissivity
0.9000 , !- Back Side Infrared Hemispherical Emissivity
0.0199 , !- Conductivity
1.0000 , !- Dirt Correction Factor for Solar and Visible Transmittance
No; !- Solar Diffusing
WindowMaterial:Glazing ,
TCGlazing25 , !- Name
SpectralAverage , !- Optical Data Type
, !- Window Glass Spectral Data Set Name
0.0030 , !- Thickness
0.2442 , !- Solar Transmittance at Normal Incidence
0.7058 , !- Front Side Solar Reflectance at Normal Incidence
0.7058 , !- Back Side Solar Reflectance at Normal Incidence
0.3192 , !- Visible Transmittance at Normal Incidence
0.6308 , !- Front Side Visible Reflectance at Normal Incidence
0.6308 , !- Back Side Visible Reflectance at Normal Incidence
0.0000 , !- Infrared Transmittance at Normal Incidence
0.9000 , !- Front Side Infrared Hemispherical Emissivity
0.9000 , !- Back Side Infrared Hemispherical Emissivity
0.0199 , !- Conductivity
1.0000 , !- Dirt Correction Factor for Solar and Visible Transmittance
No; !- Solar Diffusing
WindowMaterial:Glazing ,
TCGlazing30 , !- Name
SpectralAverage , !- Optical Data Type
, !- Window Glass Spectral Data Set Name
0.0030 , !- Thickness
0.2442 , !- Solar Transmittance at Normal Incidence
0.7058 , !- Front Side Solar Reflectance at Normal Incidence
0.7058 , !- Back Side Solar Reflectance at Normal Incidence
0.3192 , !- Visible Transmittance at Normal Incidence
0.6308 , !- Front Side Visible Reflectance at Normal Incidence
0.6308 , !- Back Side Visible Reflectance at Normal Incidence
0.0000 , !- Infrared Transmittance at Normal Incidence
0.9000 , !- Front Side Infrared Hemispherical Emissivity
0.9000 , !- Back Side Infrared Hemispherical Emissivity
0.0199 , !- Conductivity
1.0000 , !- Dirt Correction Factor for Solar and Visible Transmittance
No; !- Solar Diffusing
WindowMaterial:Glazing ,
1.9. GROUP – SURFACE CONSTRUCTION ELEMENTS 187
TCGlazing35 , !- Name
SpectralAverage , !- Optical Data Type
, !- Window Glass Spectral Data Set Name
0.0030 , !- Thickness
0.2442 , !- Solar Transmittance at Normal Incidence
0.7058 , !- Front Side Solar Reflectance at Normal Incidence
0.7058 , !- Back Side Solar Reflectance at Normal Incidence
0.3192 , !- Visible Transmittance at Normal Incidence
0.6308 , !- Front Side Visible Reflectance at Normal Incidence
0.6308 , !- Back Side Visible Reflectance at Normal Incidence
0.0000 , !- Infrared Transmittance at Normal Incidence
0.9000 , !- Front Side Infrared Hemispherical Emissivity
0.9000 , !- Back Side Infrared Hemispherical Emissivity
0.0199 , !- Conductivity
1.0000 , !- Dirt Correction Factor for Solar and Visible Transmittance
No; !- Solar Diffusing
WindowMaterial:Glazing ,
TCGlazing40 , !- Name
SpectralAverage , !- Optical Data Type
, !- Window Glass Spectral Data Set Name
0.0030 , !- Thickness
0.2442 , !- Solar Transmittance at Normal Incidence
0.7058 , !- Front Side Solar Reflectance at Normal Incidence
0.7058 , !- Back Side Solar Reflectance at Normal Incidence
0.3192 , !- Visible Transmittance at Normal Incidence
0.6308 , !- Front Side Visible Reflectance at Normal Incidence
0.6308 , !- Back Side Visible Reflectance at Normal Incidence
0.0000 , !- Infrared Transmittance at Normal Incidence
0.9000 , !- Front Side Infrared Hemispherical Emissivity
0.9000 , !- Back Side Infrared Hemispherical Emissivity
0.0199 , !- Conductivity
1.0000 , !- Dirt Correction Factor for Solar and Visible Transmittance
No; !- Solar Diffusing
WindowMaterial:Glazing ,
TCGlazing45 , !- Name
SpectralAverage , !- Optical Data Type
, !- Window Glass Spectral Data Set Name
0.0030 , !- Thickness
0.2442 , !- Solar Transmittance at Normal Incidence
0.7058 , !- Front Side Solar Reflectance at Normal Incidence
0.7058 , !- Back Side Solar Reflectance at Normal Incidence
0.3192 , !- Visible Transmittance at Normal Incidence
0.6308 , !- Front Side Visible Reflectance at Normal Incidence
0.6308 , !- Back Side Visible Reflectance at Normal Incidence
0.0000 , !- Infrared Transmittance at Normal Incidence
0.9000 , !- Front Side Infrared Hemispherical Emissivity
0.9000 , !- Back Side Infrared Hemispherical Emissivity
0.0199 , !- Conductivity
1.0000 , !- Dirt Correction Factor for Solar and Visible Transmittance
No; !- Solar Diffusing
WindowMaterial:Glazing ,
TCGlazing50 , !- Name
SpectralAverage , !- Optical Data Type
, !- Window Glass Spectral Data Set Name
0.0030 , !- Thickness
0.2442 , !- Solar Transmittance at Normal Incidence
0.7058 , !- Front Side Solar Reflectance at Normal Incidence
0.7058 , !- Back Side Solar Reflectance at Normal Incidence
0.3192 , !- Visible Transmittance at Normal Incidence
0.6308 , !- Front Side Visible Reflectance at Normal Incidence
0.6308 , !- Back Side Visible Reflectance at Normal Incidence
0.0000 , !- Infrared Transmittance at Normal Incidence
0.9000 , !- Front Side Infrared Hemispherical Emissivity
0.9000 , !- Back Side Infrared Hemispherical Emissivity
0.0199 , !- Conductivity
1.0000 , !- Dirt Correction Factor for Solar and Visible Transmittance
No; !- Solar Diffusing
188 CHAPTER 1. INPUT-OUTPUT REFERENCE
WindowMaterial:Glazing ,
TCGlazing55 , !- Name
SpectralAverage , !- Optical Data Type
, !- Window Glass Spectral Data Set Name
0.0030 , !- Thickness
0.2442 , !- Solar Transmittance at Normal Incidence
0.7058 , !- Front Side Solar Reflectance at Normal Incidence
0.7058 , !- Back Side Solar Reflectance at Normal Incidence
0.3192 , !- Visible Transmittance at Normal Incidence
0.6308 , !- Front Side Visible Reflectance at Normal Incidence
0.6308 , !- Back Side Visible Reflectance at Normal Incidence
0.0000 , !- Infrared Transmittance at Normal Incidence
0.9000 , !- Front Side Infrared Hemispherical Emissivity
0.9000 , !- Back Side Infrared Hemispherical Emissivity
0.0199 , !- Conductivity
1.0000 , !- Dirt Correction Factor for Solar and Visible Transmittance
No; !- Solar Diffusing
WindowMaterial:Glazing ,
TCGlazing60 , !- Name
SpectralAverage , !- Optical Data Type
, !- Window Glass Spectral Data Set Name
0.0030 , !- Thickness
0.2442 , !- Solar Transmittance at Normal Incidence
0.7058 , !- Front Side Solar Reflectance at Normal Incidence
0.7058 , !- Back Side Solar Reflectance at Normal Incidence
0.3192 , !- Visible Transmittance at Normal Incidence
0.6308 , !- Front Side Visible Reflectance at Normal Incidence
0.6308 , !- Back Side Visible Reflectance at Normal Incidence
0.0000 , !- Infrared Transmittance at Normal Incidence
0.9000 , !- Front Side Infrared Hemispherical Emissivity
0.9000 , !- Back Side Infrared Hemispherical Emissivity
0.0199 , !- Conductivity
1.0000 , !- Dirt Correction Factor for Solar and Visible Transmittance
No; !- Solar Diffusing
WindowMaterial:Glazing ,
TCGlazing65 , !- Name
SpectralAverage , !- Optical Data Type
, !- Window Glass Spectral Data Set Name
0.0030 , !- Thickness
0.2442 , !- Solar Transmittance at Normal Incidence
0.7058 , !- Front Side Solar Reflectance at Normal Incidence
0.7058 , !- Back Side Solar Reflectance at Normal Incidence
0.3192 , !- Visible Transmittance at Normal Incidence
0.6308 , !- Front Side Visible Reflectance at Normal Incidence
0.6308 , !- Back Side Visible Reflectance at Normal Incidence
0.0000 , !- Infrared Transmittance at Normal Incidence
0.9000 , !- Front Side Infrared Hemispherical Emissivity
0.9000 , !- Back Side Infrared Hemispherical Emissivity
0.0199 , !- Conductivity
1.0000 , !- Dirt Correction Factor for Solar and Visible Transmittance
No; !- Solar Diffusing
WindowMaterial:Glazing ,
TCGlazing75 , !- Name
SpectralAverage , !- Optical Data Type
, !- Window Glass Spectral Data Set Name
0.0030 , !- Thickness
0.2442 , !- Solar Transmittance at Normal Incidence
0.7058 , !- Front Side Solar Reflectance at Normal Incidence
0.7058 , !- Back Side Solar Reflectance at Normal Incidence
0.3192 , !- Visible Transmittance at Normal Incidence
0.6308 , !- Front Side Visible Reflectance at Normal Incidence
0.6308 , !- Back Side Visible Reflectance at Normal Incidence
0.0000 , !- Infrared Transmittance at Normal Incidence
0.9000 , !- Front Side Infrared Hemispherical Emissivity
0.9000 , !- Back Side Infrared Hemispherical Emissivity
0.0199 , !- Conductivity
1.9. GROUP – SURFACE CONSTRUCTION ELEMENTS 189
WindowMaterial:Glazing ,
TCGlazing85 , !- Name
SpectralAverage , !- Optical Data Type
, !- Window Glass Spectral Data Set Name
0.0030 , !- Thickness
0.2442 , !- Solar Transmittance at Normal Incidence
0.7058 , !- Front Side Solar Reflectance at Normal Incidence
0.7058 , !- Back Side Solar Reflectance at Normal Incidence
0.3192 , !- Visible Transmittance at Normal Incidence
0.6308 , !- Front Side Visible Reflectance at Normal Incidence
0.6308 , !- Back Side Visible Reflectance at Normal Incidence
0.0000 , !- Infrared Transmittance at Normal Incidence
0.9000 , !- Front Side Infrared Hemispherical Emissivity
0.9000 , !- Back Side Infrared Hemispherical Emissivity
0.0199 , !- Conductivity
1.0000 , !- Dirt Correction Factor for Solar and Visible Transmittance
No; !- Solar Diffusing
1.9.21.2 Outputs
1.9.21.2.1 Surface Window Thermochromic Layer Temperature [C]
The temperature of the TC glass layer of a TC window at each time step.
1.9.22 WindowMaterial:Gas
This object specifies the properties of the gas between the panes of a multi-pane window. Gas Type
= Custom allows you to specify the properties of gases other than air, Argon, Krypton or Xenon.
There is an EnergyPlus Reference Data Set for Material:WindowGas that contains several types
of gas of different thicknesses. See Material:WindowGasMixture for the case that the gas fill is a
mixture of different gases.
1.9.22.1 Inputs
1.9.22.1.1 Field: Name
The name of the gas fill. It refers to a layer in a window construction.
P roperty = Coef f icientA +Coef f icientB ∗T emperatureK +Coef f icientC ∗T emperature2K (1.14)
WindowMaterial:Gas ,AIRGAP ,
AIR , ! Gas type (Air - Argon - Krypton - Xenon - Custom)]
0.0125; ! Thickness {m} 1/2 inch
WindowMaterial:Gas ,
Gas_1_W_0_0100 , !- gap name - Air
Air , !- type
0.0100; !- thickness
WindowMaterial:Gas ,
Gas_16_W_0_0003 , !- gap name
Custom , !- type
0.0003 , !- thickness
2.873000e-003, !- Conductivity Coefficient A
7.760000e-005, !- Conductivity Coefficient B
0.000000e+000, !- Conductivity Coefficient C
3.723000e-006, !- Conductivity Viscosity A
4.940000e-008, !- Conductivity Viscosity B
0.000000e+000, !- Conductivity Viscosity C
1002.737000 , !- Specific Heat Coefficient A
0.012324 , !- Specific Heat Coefficient B
0.000000 , !- Specific Heat Coefficient C
28.969999 , !- Molecular Weight
1.400000; !- Specific Heat Ratio
1.9.23 WindowMaterial:GasMixture
This object allows you to specify the fill between the panes of a multi-pane window to be a mixture
of two, three or four different gases chosen from air, argon, krypton and xenon. It can also be used
if only one type of gas in the fill. In this case you can also use WindowMaterial:Gas. Note that the
fractions of gas types in the mixture should add up to 1.0.
1.9.23.1 Inputs
1.9.23.1.1 Field: Name
The name of the gas mixture. It refers to a layer in a window construction.
WindowMaterial:GasMixture ,ArgonKryptonMix ,
0.0125 , ! Thickness {m} 1/2 inch
2, ! Number of Gases in Mixture
Argon , ! Gas 1 Type
0.6, ! Gas 1 Fraction
Krypton , ! Gas 2 Type
0.4; ! Gas 2 Fraction
1.9.24 WindowMaterial:Gap
This input object is used to define the gap between two layers in a complex fenestration system,
where the Construction:ComplexFenestrationState object is used. It references the gas or gas mix-
tures defined in the WindowMaterial:Gas and WindowMaterial:GasMixture objects. It is referenced
as a layer in the Construction:ComplexFenestrationState object ;it cannot be referenced as a layer
from the Construction object.
1.9.24.1 Inputs
1.9.24.1.1 Field: Name
Unique name of the gap.
WindowMaterial:Gas ,
Gas_1_W_0_0120 , !- gap name - Air
Air , !- type
0.0120; !- thickness
WindowMaterial:Gap ,
Gap_1_Layer , !- gap name: Air
0.0120 , !- thickness
Gas_1_W_0_0120 , !- Gas (or Gas Mixture) name
101325.0000; !- pressure
WindowMaterial:Gap ,
Gap_16_Layer , !- gap name: Vacuum_0 .001_pr -0.5_ps -50.8
0.0003 , !- thicknessGas_16_W_0_0003 ,
!- Gas (or Gas Mixture) name
0.1333 , !- pressure
, !- deflection state
SupportPillar_16_Gap_1 ; !- SupportPillar
WindowGap:SupportPillar ,
SupportPillar_16_Gap_1 , !- Name
0.0508 , !- spacing
0.0005; !- radius
1.9.25 WindowGap:DeflectionState
This input object is used to enter data describing deflection state of the gap. It is referenced from
WindowMaterial:Gap object only and it is used only when deflection model is set to MeasuredDe-
flection (see WindowThermalModel:Params), otherwise it is ignored.
1.9.25.1 Inputs
1.9.25.1.1 Field: Name
Unique name of the deflection state.
WindowMaterial:Gap ,
Gap_1_Layer , !- gap name: Air
0.0120 , !- thickness
Gas_1_W_0_0120 , !- Gas (or Gas Mixture) name
101325.0000 , !- pressure
194 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.9.26 WindowGap:SupportPillar
This input object is used to enter data describing support pillar of the gap. Support pillars are
used in vacuum glazing in order to prevent deflection of glass layers.
1.9.26.1 Inputs
1.9.26.1.1 Field: Name
Unique name of the support pillar.
1.9.27 WindowMaterial:SimpleGlazingSystem
This model should be used with caution. There may be significant differences in performance
between the simple window system and the usual more detailed model.
This input object differs from the other WindowMaterial objects in that it describes an entire glazing
system rather than individual layers. This object is used when only very limited information is available
on the glazing layers or when specific performance levels are being targeted. The layer by layer description
offers superior method of modeling windows that should be used instead of this object when sufficient data
are available. This object accesses a model that turns simple performance indices into a fuller model of
the glazing system.
The performance indices are U-factor and Solar Heat Gain Coefficient, and optionally Visible Transmit-
tance. The values for these performance indices can be selected by the user to represent either glazing-only
windows (with no frame) or an average window performance that includes the frame. Inside the program
the model produces an equivalent window glazing layer with no frame. The properties of the modeled glaz-
ing layer are reported to the EIO file using the IDF input object syntax for the WindowMaterial:Glazing
input object. This equivalent layer could be reused in subsequent models if desired, however there will
be important differences in the modeled window performance because the simple glazing system model
includes its own special model for angular dependence when incident beam solar is not normal to the plane
of the window.
When this object is referenced in a Construction object, it cannot be used with other glazing or gas
material layers. Shades or blinds cannot be located between the glass, but these can be used on the inside
or the outside of the glazing system. If the glazing system does have between-the-glass shades or blinds,
then the U and SHGC values entered in this object should include the impacts of those layers. Adding
window treatment layers such as shades or screens will alter the overall performance to be different than
the performance levels prescribed in this object.
1.9.27.1 Inputs
1.9.27.1.1 Field: Name
The name of the glazing system. This value is unique across all constructions.
196 CHAPTER 1. INPUT-OUTPUT REFERENCE
WindowMaterial:SimpleGlazingSystem ,
SimpleWindow:DOUBLE PANE WINDOW , !- Name
2.716 , !- U-Factor
0.763 , !- Solar Heat Gain Coefficient
0.812 ; !- Visible Transmittance
1.9.28 WindowMaterial:Shade
This object specifies the properties of window shade materials. Reflectance and emissivity properties are
assumed to be the same on both sides of the shade. Shades are considered to be perfect diffusers (all trans-
mitted and reflected radiation is hemispherically-diffuse) with transmittance and reflectance independent
of angle of incidence. There is an EnergyPlus Reference Data Set for WindowMaterial:Shade that contains
properties of generic window shades.
Window shades can be on the inside of the window (“interior shades”), on the outside of the window
(“exterior shades”), or between glass layers (“between-glass shades”). When in place, the shade is assumed
to cover all of the glazed part of the window, including dividers; it does not cover any of the window frame,
if present. The plane of the shade is assumed to be parallel to the glazing.
WindowMaterial:Shade can be used for diffusing materials such as drapery and translucent roller
shades. For slat-type shading devices, like Venetian blinds, that have a strong angular dependence of
transmission, absorption and reflection, it is better to use WindowMaterial:Blind. WindowMaterial:Screen
should be used to model wire mesh insect screens where the solar and visible transmission and reflection
properties vary with the angle of incidence of solar radiation.
Transmittance and reflectance values for drapery material with different color and openness of weave
can be obtained from manufacturers or determined from 2001 ASHRAE Fundamentals, Chapter 30, Fig.
31.
There are two methods of assigning a shade to a window:
1.9.28.1 Inputs
1.9.28.1.1 Method 1:
1) Define the construction of the window without the shade, the so-called “bare” construction.
1.9. GROUP – SURFACE CONSTRUCTION ELEMENTS 197
1.9.28.1.2 Method 2:
1) Define the Construction of the window without the shade, the so-called “bare” construction.
2) Reference the bare construction in the FenestrationSurface:Detailed for the window.
3) Define the WindowMaterial:Shade.
4) Define another Construction, called the “shaded construction,” that includes the WindowMate-
rial:Shade.
5) Define a WindowShadingControl for the window in which you (a) reference the shaded construction
and (b) specify how the shade is controlled.
Note that WindowShadingControl has to be used with either method, even if the shade is in place
at all times. You will get an error message if you try to reference a shaded construction directly from
FenestrationSurface:Detailed.
εeff ≈ ε (1 − η) (1.15)
Teff ≈ η + T (1 − η) (1.16)
For most materials T is very close to zero, which gives
Teff ≈ η (1.17)
Figure 1.14: Vertical section (a) and perspective view (b) of glass and interior shade layers showing
variables used in the gap air flow analysis. In (b), the air-flow opening areas Abot , Atop , Al , Ar and
Ah are shown schematically. See Engineering Manual for definition of thermal variables.
200 CHAPTER 1. INPUT-OUTPUT REFERENCE
Figure 1.15: Examples of air-flow openings for an interior shade covering glass of height H and width
W . Not to scale. (a) Horizontal section through shade with openings on the left and right sides
(top view). (b) Vertical section through shade with openings at the top and bottom (side view).
In (a) Left-Side Opening Multiplier = Al /sH = min(l/s, 1) and Right-Side Opening Multiplier =
Ar /sH = min(r/s, 1). In (b) Top Opening Multiplier = Atop /sW = t/s and Bottom Opening
Multiplier = Abot /sW = b/s.
1.9. GROUP – SURFACE CONSTRUCTION ELEMENTS 201
WindowMaterial:Shade ,
DRAPES - CLOSE WEAVE MEDIUM , !- Name
0.05, !- Solar transmittance
0.3000000 , !- Solar Reflectance
.05, !- Visible transmittance
0.3000000 , !- Visible reflectance
0.9000000 , !- Infrared Hemispherical Emissivity
0.0, !- Infrared Transmittance
0.003 , !- Thickness {m}
0.1, !- Conductivity {W/m-K}
0.050 , !- Shade to glass distance {m}
1.0, !- Top opening multiplier
1.0, !- Bottom opening multiplier
0.0, !- Left -side opening multiplier
0.0, !- Right -side opening multiplier
0.0; !- Air flow permeability
1.9.29 WindowMaterial:Blind
This object specifies the properties of a window blind consisting of flat, equally-spaced slats. Unlike
window shades, which are modeled as perfect diffusers, window blinds have solar and visible transmission
and reflection properties that strongly depend on slat angle and angle of incidence of solar radiation. There
is an EnergyPlus Reference Data Set for WindowMaterial:Blind that contains properties of generic window
blinds.
Blinds can be located on the inside of the window (“interior blinds”), on the outside of the window
(“exterior blinds”), or between two layers of glass (“between-glass blinds”). When in place, the blind is
assumed to cover all of the glazed part of the window, including dividers; it does not cover any of the
window frame, if present. The plane of the blind is assumed to be parallel to the glazing. When the blind
is retracted it is assumed to cover none of the window. The solar and thermal effects of the blind’s support
strings, tapes or rods are ignored. Slat curvature, if present, is ignored.
There are two methods of assigning a blind to a window:
1.9.29.1 Inputs
1.9.29.1.1 Method 1:
1) Define the construction of the window without the blind, the so-called “bare” construction.
2) Reference the bare construction in the FenestrationSurface:Detailed for the window.
3) Define the WindowMaterial:Blind.
4) Define a WindowShadingControl for the window in which you (a) specify that this WindowMate-
rial:Blind is the window’s shading device and (b) specify how the blind is controlled.
1.9.29.1.2 Method 2:
1) Define the Construction of the window without the blind, the so-called “bare” construction.
2) Reference the bare construction in the FenestrationSurface:Detailed for the window.
3) Define the WindowMaterial:Blind.
4) Define another Construction, called the “shaded construction,” that includes the WindowMate-
rial:Blind.
5) Define a WindowShadingControl for the window in which you (a) reference the shaded construction
and (b) specify how the blind is controlled.
Note that WindowShadingControl has to be used with either method, even if the blind is in place at
all times. You will get an error message if you try to reference a construction with a blind directly from
Window objects (FenestrationSurface:Detailed or Window).
202 CHAPTER 1. INPUT-OUTPUT REFERENCE
Note also that WindowShadingControl is used to determine not only when the blind is in place, but
how its slat angle is controlled.
WindowMaterial:Blind ,
White Painted Metal Blind , !- Name
HORIZONTAL , !- Slat orientation
0.025 , !- Slat width (m)
0.01875 , !- Slat separation (m)
0.001 , !- Slat thickness (m)
45.0 , !- Slat angle (deg)
44.9 , !- Slat conductivity (W/m-K)
0.0 , !- Slat beam solar transmittance
0.8 , !- Front Side Slat beam solar reflectance
0.8 , !- Back Side Slat beam solar reflectance
0.0 , !- Slat diffuse solar transmittance
0.8 , !- Front Side Slat diffuse solar reflectance
0.8 , !- Back Side Slat diffuse solar reflectance
0.0 , !- Slat beam visible transmittance
0.7 , !- Front Side Slat beam visible reflectance
0.7 , !- Back Side Slat beam visible reflectance
0.0 , !- Slat diffuse visible transmittance
0.7 , !- Front Side Slat diffuse visible reflectance
0.7 , !- Back Side Slat diffuse visible reflectance
0.0 , !- Slat Infrared hemispherical transmittance
0.9 , !- Front Side Slat Infrared hemispherical emissivity
0.9 , !- Back Side Slat Infrared hemispherical emissivity
0.050 , !- Blind -to -glass distance
0.0 , !- Blind top opening multiplier
0.0 , !- Blind bottom opening multiplier
0.5 , !- Blind left -side opening multiplier
0.5 , !- Blind right -side opening multiplier
, !- Minimum slat angle (deg)
; !- Maximum slat angle (deg)
1.9.30 WindowMaterial:ComplexShade
This input object is used to define shade layers used in the Construction:ComplexFenestrationState object.
1.9.30.1 Inputs
1.9.30.1.1 Field: Name
Unique name of the shading layer.
Figure 1.16: (a) Side view of a window blind with horizontal slats (or top view of blind with vertical
slats) showing slat geometry. The front face of a slat is shown by a heavy line. The slat angle is
defined as the angle between the glazing outward normal and the slat outward normal, where the
outward normal points away from the front face of the slat. (b) Slat orientations for representative
slat angles. The slat angle varies from 0o , when the front of the slat is parallel to the glazing and
faces toward the outdoors, to 90o , when the slat is perpendicular to the glazing, to 180o , when the
front of the slat is parallel to the glazing and faces toward the indoors. The minimum and maximum
slat angles are determined by the slat thickness, width and separation.
1.9. GROUP – SURFACE CONSTRUCTION ELEMENTS 207
• Woven – the conductivity of the woven shade material (such as the thread for a fabric shade)
• BSDF – for modeling shades whose properties are represented by a BSDF file
• OtherShadingType – for modeling shading systems which do not belong to the any of the previous
group
Smin = min(S1 , S2 )
Figure 1.17: Three cases for the Dtop calculation for an indoor/outdoor shade: Case a) A shading
device between the frame; Case b) A shading device outside the frame, covering the frame; Case c)
a shading device outside the frame, not covering the frame.
1.9. GROUP – SURFACE CONSTRUCTION ELEMENTS 209
Figure 1.18: Calculation of Dtop for a shading device between glass layers
210 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.9.31 WindowMaterial:Screen
This object specifies the properties of exterior window screen materials. The window screen model assumes
the screen is made up of intersecting orthogonally-crossed cylinders. The surface of the cylinders is assumed
212 CHAPTER 1. INPUT-OUTPUT REFERENCE
Figure 1.20: Side view of horizontal venetian blind slats or top view of blinds with vertical slats.
Front face of slats is marked with red line.
1.9. GROUP – SURFACE CONSTRUCTION ELEMENTS 213
The window screen “assembly” properties of overall beam solar reflectance and absorptance (including
the screen material ‘cylinders’ and open area) also change with sun angle and are calculated based on the
values of the beam solar transmittance components (direct and reflected components described above) and
the physical properties of the screen material (i.e., screen material diameter, spacing, and reflectance).
Transmittance, reflectance, and absorptance of diffuse solar radiation are considered constant values
and apply to both the front and back surfaces of the screen. These properties are calculated by the model
as an average value by integrating the screen’s beam solar properties over a quarter hemisphere of incident
radiation. Long-wave emissivity is also assumed to be the same for both sides of the screen.
There is an EnergyPlus Reference Data Set for WindowMaterial:Screen that contains properties for
generic window screens. Window screens of this type can only be used on the outside surface of the window
(“exterior screens”). When in place, the screen is assumed to cover all of the glazed part of the window,
214 CHAPTER 1. INPUT-OUTPUT REFERENCE
including dividers; it does not cover any of the window frame, if present. The plane of the screen is assumed
to be parallel to the glazing.
WindowMaterial:Screen can be used to model wire mesh insect screens where the solar and visible
transmission and reflection properties vary with the angle of incidence of solar radiation. For diffusing
materials such as drapery and translucent roller shades it is better to use the WindowMaterial:Shade
object. For slat-type shading devices like Venetian blinds, which have solar and visible transmission and
reflection properties that strongly depend on slat angle and angle of incidence of solar radiation, it is better
to use WindowMaterial:Blind.
There are two methods of assigning a screen to a window:
1.9.31.1 Inputs
1.9.31.1.1 Method 1:
1) Define the construction of the window without the screen, the so-called “bare” construction.
2) Reference the bare construction in the FenestrationSurface:Detailed for the window.
3) Define the WindowMaterial:Screen object.
4) Define a WindowShadingControl for the window in which you (a) specify that this Mate-
rial:WindowScreen is the window’s shading device, and (b) specify how the screen is controlled.
1.9.31.1.2 Method 2:
1) Define the Construction of the window without the screen, the so-called “bare” construction.
2) Reference the bare construction in the FenestrationSurface:Detailed for the window.
3) Define the WindowMaterial:Screen object.
4) Define another Construction, called the “shaded construction,” that includes the WindowMate-
rial:Screen.
5) Define a WindowShadingControl for the window in which you (a) reference the shaded construction,
and (b) specify how the screen is controlled.
Note that WindowShadingControl has to be used with either method, even if the screen is in place
at all times. You will get an error message if you try to reference a shaded construction directly from a
FenestrationSurface:Detailed object.
to less than 1.0. In the absence of better information, the input value for diffuse solar reflectance should
match the input value for diffuse visible reflectance.
Commercially-available gray scale or grayscale reflecting chart references can be purchased for improved
accuracy in estimating visible reflectance (by visual comparison of screen reflected brightness with that of
various known-reflectance portions of the grayscale).
WindowMaterial:Screen ,
EXTERIOR SCREEN , !- Name
ModelAsDiffuse , !- Reflected Beam Transmittance Accounting Method
0.6, !- Diffuse Solar Reflectance
0.6, !- Diffuse Visible Reflectance
0.9, !- Thermal Hemispherical Emissivity
221.0 , !- Conductivity {W/m-K}
0.00154 , !- Screen Material Spacing (m)
0.000254 , !- Screen Material Diameter (m)
0.025 , !- Screen -to -Glass Distance {m}
0.0, !- Top Opening Multiplier
0.0, !- Bottom Opening Multiplier
0.0, !- Left -Side Opening Multiplier
0.0, !- Right -Side Opening Multiplier
0; !- Angle of Resolution for Output Map {deg}
Construction ,
DOUBLE PANE WITHOUT SCREEN , !- Name
GLASS - CLEAR SHEET 1 / 8 IN , !- Outside Layer
WinAirB1 - AIRSPACE RESISTANCE , !- Layer \#2
GLASS - CLEAR SHEET 1 / 8 IN; !- Layer \#3
WindowShadingControl ,
DOUBLE PANE WITH SCREEN , !- Name
West Zone , !- Zone Name
1, !- Shading Control Sequence Number
ExteriorScreen , !- Shading Type
, !- Name of construction with shading
AlwaysOn , !- Shading Control Type
ScreenSchedule , !- Schedule Name
20.0, !- SetPoint {W/m2 , W or deg C}
YES , !- Shading Control Is Scheduled
NO , !- Glare Control Is Active
EXTERIOR SCREEN , !- Material Name of Shading Device
, !- Type of Slat Angle Control for Blinds
, !- Slat Angle Schedule Name
, !- Setpoint 2 {W/m2 or deg C}
, !- Daylighting Control Object Name
Sequential , !- Multiple Surface Control Type
Zn001:Wall001:Win001; !- Fenestration Surface 1 Name
218 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.9.32 WindowMaterial:Shade:EquivalentLayer
This object specifies the properties of Equivalent Layer window shade (roller blind) materials. Shades are
considered to be thin, flat and perfect diffusers (all transmitted and reflected radiation is hemispherically-
diffuse). However, shades can have beam-beam transmittance by virtue of their material openness. The
beam-beam transmittence is assumed to be the same for both sides of the shade and is the same as
the openness area fraction. Beam-diffuse transmittance and reflectance, and emissivity properties can be
different for front and back side of the shade.Window shades can be placed on the inside of the window,
on the outside of the window, or between glass layers. WindowMaterial:Shade:EquivalentLayer is used
for roller blinds. The off-normal solar property calculation of shades (roller blind) is based on a set of
correlations developed from measurement of samples of commercially produced roller blind material with
openness fraction less than 0.14. The model is not intended for materials with unusually high values
of openness and should be limited to a maximum openness fraction of 0.20. The visible spectrum solar
properties input fields are not used currently hence can be left blank. The equivalent layer window shade
model does not support WindowShadingControl.
1.9.32.1 Inputs
1.9.32.1.1 Field: Name
Name of the shade. It is referenced as an inside, inbetween or outside layer in an equivalent layer win-
dow construction.
WindowMaterial:Shade:EquivalentLayer ,
Shade1 , !- Name
0.190 , !- Shade Beam -Beam Solar Transmittance
0.206 , !- Front Side Shade Beam -Diffuse Solar Transmittance
0.206 , !- Back Side Shade Beam -Diffuse Solar Transmittance
0.499 , !- Front Side Shade Beam -Diffuse Solar Reflectance
0.499 , !- Back Side Shade Beam -Diffuse Solar Reflectance
0.0, !- Shade Beam -Beam Visible Transmittance
0.0, !- Shade Beam -Diffuse Visible Transmittance
0.0, !- Shade Visible Reflectance
0.0, !- Shade Material Infrared Transmittance
0.84, !- Front Side Shade Material Infrared Emissivity
0.84; !- Back Side Shade Material Infrared Emissivity
1.9.33 WindowMaterial:Drape:EquivalentLayer
Specifies the optical and thermal properties of equivalent layer window drape fabric materials.
Drapery fabric shades are commonly placed on the the inside of the window. The long-wave (Thermal)
properties for commonly used drapery fabrics are assumed to be the same on both sides but different values
can be specified when required. Drape fabric shade layers are considered to be perfect diffusers (reflected
220 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.9.33.1 Inputs
1.9.33.1.1 Field: Name
Name of the drape fabric shade layer. It is referenced as an inside, in between or outside layer in an
equivalent layer window construction.
1.9.34 WindowMaterial:Blind:EquivalentLayer
This object specifies the properties of an Equivalent Layer window blind consisting of thin and equally-
spaced slats. The model assumes that slats are flat and thin, and applies correction for the slat curvature
effect based on the user specified slat crown. Slats are assumed to transmit and reflect diffusely. The
effective shortwave optical and longwave optical properties of venetian blind layer is estimated analytically.
The Equivalent Layer blind model requires optical properties and geometry of the slats shown in Figure 1.24.
Likewise, effective longwave properties are obtained for the layer knowing longwave properties of the slats.
The input data required to characterize a venetian blind are: front and back side reflectance and
transmittance of the slat, geometry (Slat width, w, slat spacing, s, slat crown, c, and slat angle, ϕ, and
long wave emittance and transmittance of the slat. Blinds can be located on the inside of the window, on
the outside of the window, or between two layers of glass. The blind is assumed to cover all of the glazed
part of the window. The equivalent layer window blind model allows three slat angle control types (see
Slat Angle Control input field) but does not support WindowShadingControl.
1.9.34.1 Inputs
1.9.34.1.1 Field: Name
Name of the venetian blind. It is referenced as an inside, outside or in between layers in an equivalent
layer window construction.
Figure 1.24: Geometry and Properties used for venetian blind analysis
1.9. GROUP – SURFACE CONSTRUCTION ELEMENTS 225
WindowMaterial:Blind:EquivalentLayer ,
VBU8D6 +45SW1 , ! - Name
Horizontal , ! - Slat Orientation
0.025 , ! - Slat Width
1.9. GROUP – SURFACE CONSTRUCTION ELEMENTS 227
1.9.35 WindowMaterial:Screen:EquivalentLayer
This object specifies the optical and thermal properties of exterior screen materials for Equivalent Layer
Window. Can only be placed on the exterior side of window construction. The window screen model
assumes the screen is made up of intersecting orthogonally-crossed cylinders. The surface of the cylinders
is assumed to be diffusely reflecting. The beam solar radiation transmitted through an equivalent Layer
window screen varies with sun angle and is made up of two distinct elements: a beam-beam component
and a beam-diffuse component. The beam-beam transmittance component is calculated using screen
openness area fraction determined from the geometry of the screen and the incident angle of the sun.
Empirical correlations are used to obtain the effective off-normal solar and longwave properties of insect
screens. Insect screen geometry is shown in Figure 1.25. The calculation of effective solar properties
requires a set of properties measured at normal incidence. The equivalent layer window screen shade
model does not support WindowShadingControl.
The formulation of the model, assumption and correlations used to calculate effective solar and longwave
properties of insect screens are described in the Engineering Reference.
1.9.35.1 Inputs
1.9.35.1.1 Field: Name
Name of the insect screen. It is referenced as an outside layer in an equivalent layer window construction.
WindowMaterial:Screen:EquivalentLayer ,
INSCRN , !- Name
0.763 , !- Screen Beam -Beam Solar Transmittance
0.052 , !- Screen Beam -Diffuse Solar Transmittance
230 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.9.36 WindowMaterial:Glazing:EquivalentLayer
Glass material properties for equivalent layer window model. Uses transmittance/reflectance input
method. For exterior windows, “front side” is the side of the glass closest to the outside air and “back
side” is the side closest to the zone the window is defined in. For interzone windows, “front side” is the
side closest to the zone adjacent to the zone the window is defined in and “back side” is the side clos-
est to the zone the window is defined in. The equivalent layer window glazing model does not support
WindowShadingControl.
1.9.36.1 Inputs
1.9.36.1.1 Field: Name
The name of the glass layer. It corresponds to a layer in an equivalent layer window construction.
visible transmittance is assumed to be the same for both sides of the glazing. If this input field is specified
as “Autocalculate”, then the calculated transmittance will be used. The minimum value is 0.0, and the
maximum value is less than 1.0. This input field is not used currently.
WindowMaterial:Glazing:EquivalentLayer ,
GLZCLR , !- Name
SpectralAverage , !- Optical Data Type
, !- Window Glass Spectral Data Set Name
0.83, !- Front Side Beam -Beam Solar Transmittance
0.83, !- Back Side Beam -Beam Solar Transmittance
0.08, !- Front Side Beam -Beam Solar Reflectance
0.08, !- Back Side Beam -Beam Solar Reflectance
0.0, !- Front Side Beam -Beam Visible Transmittance
0.0, !- Back Side Beam -Beam Visible Transmittance
0.0, !- Front Side Beam -Beam Visible Reflectance
0.0, !- Back Side Beam -Beam Visible Reflectance
234 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.9.37 WindowMaterial:Gap:EquivalentLayer
This object is used in windows equivalent layer construction object and specifies the properties of the
gap between the layers in multi-layer equivalent layer window object. There is an EnergyPlus Reference
Data Set for Material:WindowGas that contains several types of gas. This object uses the gas types:
Air, Argon, Xenon, Crypton, and Custom. For Custom gas type users are required to entering the
thermophicial properties.
1.9.37.1 Inputs
1.9.37.1.1 Field: Name
The name of the gap. It refers to a layer in a window construction equivalent layer.
WindowMaterial:Gap:EquivalentLayer ,
Custom CO2 Sealed 12mm , !- Name
CUSTOM , !- Gas Type
0.0120 , !- Thickness {m}
Sealed , !- Gap Vent Type
-5.8181E-3, !- Conductivity Coefficient A {W/m-K}
7.4714E-5, !- Conductivity Coefficient B {W/m-K2}
0.0, !- Conductivity Coefficient C {W/m-K3}
8.5571E-7, !- Viscosity Coefficient A {kg/m-s}
4.7143E-8, !- Viscosity Coefficient B {kg/m-s-K}
0.0, !- Viscosity Coefficient C {kg/m-s-K2}
5.76903E2 , !- Specific Heat Coefficient A {J/kg -K}
9.18088E-2, !- Specific Heat Coefficient B {J/kg -K2}
0.0, !- Specific Heat Coefficient C {J/kg -K3}
44.01; !- Molecular Weight {g/mol}
236 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.9.38 Material:RoofVegetation
This definition must be used in order to simulate the green roof (ecoroof) model. The material becomes
the outside layer in a green roof construction (see example below). In the initial release of the green roof
model, only one material may be used as a green roof layer though, of course, several constructions using
that material may be used. In addition, the model works only with the ConductionTransferFunction heat
balance solution algorithm. This model was developed for low-sloped exterior surfaces (roofs). It is not
recommended for high-sloped exterior surfaces (e.g., walls).
1.9.38.1 Inputs
1.9.38.1.1 Field: Name
This field is a unique reference name that the user assigns to a particular ecoroof material. This name
can then be referred to by other input data.
Material:RoofVegetation ,
BaseEco , !- Name
0.5, !- Height of Plants {m}
5, !- Leaf Area Index {dimensionless}
0.2, !- Leaf Reflectivity {dimensionless}
0.95, !- Leaf Emissivity
180, !- Minimum Stomatal Resistance {s/m}
EcoRoofSoil , !- Soil Layer Name
MediumSmooth , !- Roughness
0.18, !- Thickness {m}
0.4, !- Conductivity of Dry Soil {W/m-K}
641, !- Density of Dry Soil {kg/m3}
1.9. GROUP – SURFACE CONSTRUCTION ELEMENTS 239
Material:RoofVegetation ,
LowLAI , !- Name
0.5, !- Height of Plants {m}
0.5, !- Leaf Area Index {dimensionless}
0.2, !- Leaf Reflectivity {dimensionless}
0.95, !- Leaf Emissivity
180, !- Minimum Stomatal Resistance {s/m}
EcoRoofSoil , !- Soil Layer Name
MediumSmooth , !- Roughness
0.18, !- Thickness {m}
0.4, !- Conductivity of Dry Soil {W/m-K}
641, !- Density of Dry Soil {kg/m3}
1100, !- Specific Heat of Dry Soil {J/kg -K}
0.95, !- Thermal Absorptance
0.8, !- Solar Absorptance
0.7, !- Visible Absorptance
0.4, !- Saturation Volumetric Moisture Content of the Soil Layer
0.01, !- Residual Volumetric Moisture Content of the Soil Layer
0.2, !- Initial Volumetric Moisture Content of the Soil Layer
Simple; !- Moisture Diffusion Calculation Method
Construction ,
ASHRAE 90.1 -2004 _Sec 5.5-2_Roof , !- Name
BaseEco , !- Outside Layer
ASHRAE 90.1 -2004 _Sec 5.5-2 _Roof Insulation_1 , !- Layer \#2
ASHRAE 90.1 -2004 _Sec 5.5-2_MAT -METAL; !- Layer \#3
• Zone,Average,Green Roof Soil Sensible Heat Transfer Rate per Area [W/m2]
• Zone,Average,Green Roof Vegetation Sensible Heat Transfer Rate per Area [W/m2]
• Zone,Average,Green Roof Vegetation Latent Heat Transfer Rate per Area [W/m2]
• Zone,Average,Green Roof Soil Latent Heat Transfer Rate per Area [W/m2]
240 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.9.39.5 Green Roof Soil Sensible Heat Transfer Rate per Area [W/m2]
Sensible heat flux to ground (W/m2 )
1.9.39.6 Green Roof Vegetation Sensible Heat Transfer Rate per Area [W/m2]
Sensible heat transfer to foliage (W/m2 )
1.9.39.9 Green Roof Vegetation Latent Heat Transfer Rate per Area [W/m2]
Latent heat flux from vegetation (W/m2 )
1.9. GROUP – SURFACE CONSTRUCTION ELEMENTS 241
1.9.39.10 Green Roof Soil Latent Heat Transfer Rate per Area [W/m2]
Latent heat flux from ground surface (W/m2 )
1.9.40 MaterialProperty:GlazingSpectralData
With the MaterialProperty:GlazingSpectralData object, you can specify the wavelength-by-wavelength
transmittance and reflectance properties of a glass material. To determine the overall optical properties of
a glazing system (solar and visible transmittance and solar absorptance vs. angle of incidence) EnergyPlus
first calculates transmittance and absorptance vs. angle of incidence for each wavelength. This is then
weighted by a standard solar spectrum to get the solar transmittance and absorptance vs. angle of incidence
(for use in the solar heat gain calculations), and further weighted by the response of the human eye to get
the visible transmittance vs. angle of incidence (for use in the daylighting calculation).
MaterialProperty:GlazingSpectralData should be used for multi-pane windows when one or more of
the glass layers is spectrally selective, i.e., the transmittance depends strongly on wavelength. An example
is glass with a coating that gives high transmittance in the daylight part of the solar spectrum (roughly 0.4
to 0.7 microns) and low transmittance at longer wavelengths, thus providing better solar heat gain control
than uncoated glass. If spectral data is not used in case, the overall optical properties of the glazing system
that EnergyPlus calculates will not be correct.
You can input up to 450 sets of values for wavelengths covering the solar spectrum. Each set consists
of {wavelength (microns), transmittance, front reflectance, back reflectance}
Spectral data of this kind are routinely measured by glass manufacturers. Data sets for over 800
commercially available products are contained in an Optical Data Library maintained by the Windows
Group at Lawrence Berkeley National Laboratory. This library can be downloaded from http://windows.
lbl.gov/. You will have to edit entries from this library to put them in the format required by the EnergyPlus
WindowGlassSpectralData object.
An alternative to using the MaterialProperty:GlazingSpectralData object is to run the WINDOW
window analysis program. This program has built-in access to the Optical Data Library and let’s you
242 CHAPTER 1. INPUT-OUTPUT REFERENCE
easily create customized, multi-layer glazing systems that can be exported for use in EnergyPlus. For more
details, see “StormWindow”.
1.9.40.1 Inputs
1.9.40.1.1 Field: Name
The name of the spectral data set. It is referenced by WindowMaterial:Glazing when Optical Data
Type = Spectral.
MaterialProperty:GlazingSpectralData ,
TestSpectralDataSet ,
! { from WINDOW 4 library }
! { actual 9.91 mm clear laminate: 15 _mil PVB , ID :37966/50032 -39 -9 } 10.38
! { conductivity PVB adjusted , W/M/K } 0.798
! { thermal IR transmittance , assumed } tir = 0.00
! { thermal IR hemispherical emittance , assumed } emis = 0.84 0.84
! WL T Rfront Rback
.300, 0.000 , 0.045 , 0.045 ,
.310, 0.000 , 0.044 , 0.044 ,
.320, 0.000 , 0.044 , 0.044 ,
.330, 0.000 , 0.042 , 0.042 ,
.340, 0.000 , 0.041 , 0.041 ,
.350, 0.000 , 0.040 , 0.040 ,
<snip >
2.450 , 0.200 , 0.040 , 0.040 ,
2.500 , 0.214 , 0.039 , 0.039;
1.9.41 Construction
For walls, roofs, floors, windows, and doors, constructions are “built” from the included materials. Each
layer of the construction is a material name listed in order from “outside” to “inside”. Up to ten layers
(eight for windows) may be specified (one of the few limitations in EnergyPlus!). “Outside” is the layer
furthest away from the Zone air (not necessarily the outside environment). “Inside” is the layer next to
the Zone air. In the example floor below, for example, the outside layer is the acoustic tile below the floor,
the next layer is the air space above the tile, and the inside layer is the concrete floor deck.
Window constructions are similarly built up from items in the Window Materials set using similar
layers.. See Figure 1.27. Illustration for material ordering in windows, which shows the case where an
interior shading layer such as a blind is present. The gap between the inside glass layer (layer #3) and the
1.9. GROUP – SURFACE CONSTRUCTION ELEMENTS 243
interior shading layer is not entered. Similarly, for an exterior shading layer, the gap between the outside
glass layer and the shading layer is not entered.
However, for a between-glass shading device the gaps on either side of the shading layer must be entered
and they must have the same gas type. In addition, the gap widths with and without the between-glass
shading layer must be consistent (see Figure 1.28).
A maximum of four glass layers and one shading layer is allowed. A gas layer must always separate
adjacent glass layers in a multi-pane glazing without a between-glass shading layer.
Outside and inside air film resistances are never given as part of a construction definitions since they
are calculated during the EnergyPlus simulation. Note also that constructions are assumed to be one-
dimensional in a direction perpendicular to the surface.
1.9.41.1 Inputs
1.9.41.1.1 Field: Name
This field is a user specified name that will be used as a reference by other input syntax. For example,
a heat transfer surface (ref: Building Surfaces) requires a construction name to define what the make-up
of the wall is. This name must be identical to one of the Construction definitions in the input data file.
Figure 1.28: Window construction with and without a between-glass shading layer. Shown are gap
widths g, g1 and g2 , and shading layer width, w. An error will result if g1 + g2 + w is not equal to
g, where w is zero for a blind and greater than zero for a shade.
246 CHAPTER 1. INPUT-OUTPUT REFERENCE
be a film coefficient since EnergyPlus will calculate outside convection and radiation heat transfer more
precisely.
Construction , DOUBLE PANE WITH ROLL SHADE , !- Material layer names follow:
GLASS - CLEAR SHEET 1 / 8 IN ,
WinAirB1 - AIRSPACE RESISTANCE ,
GLASS - CLEAR SHEET 1 / 8 IN ,
ROLL SHADE - LIGHT
1.9.43 Construction:CfactorUndergroundWall
This input object differs from the usual wall construction object in that it describes an entire construction
rather than individual layers. This object is used when only the wall height (depth to the ground) and the
C-factor are available. This object accesses a model that creates an equivalent layer-by-layer construction
for the underground wall to approximate the heat transfer through the wall considering the thermal mass
of the earth soil.
This object is referenced by underground wall surfaces with their fields ‘Outside Boundary Condition’
set to GroundFCfactorMethod.
1.9.43.1 Inputs
1.9.43.1.1 Field: Name
The name of the underground wall construction.
Construction:CfactorUndergroundWall ,
CfactorUGWall ,
0.436 , ! C-factor (W/m2K), does not include soil or air films
4.57; ! Height (m)
BuildingSurface:Detailed ,
Zn001:Wall001 , !- Name
Wall , !- Surface Type
CfactorUGWall , !- Construction Name
ZONE ONE , !- Zone Name
GroundFCfactorMethod , !- Outside Boundary Condition
, !- Outside Boundary Condition Object
NoSun , !- Sun Exposure
NoWind , !- Wind Exposure
0.0, !- View Factor to Ground
4, !- Number of Vertices
0.0 ,0.0 ,4.572 , !- X,Y,Z = = > Vertex 1
0.0 ,0.0 ,0.0 , !- X,Y,Z = = > Vertex 2
15.24 ,0.0 ,0.0 , !- X,Y,Z = = > Vertex 3
15.24 ,0.0 ,4.572; !- X,Y,Z = = > Vertex 4
1.9.44 Construction:FfactorGroundFloor
This input object differs from the usual ground floor construction object in that it describes an entire
construction rather than individual layers. This object is used when only the floor area, exposed perimeter,
248 CHAPTER 1. INPUT-OUTPUT REFERENCE
and the F-factor are available. This object accesses a model that creates an equivalent layer-by-layer
construction for the slab-on-grade or underground floor to approximate the heat transfer through the floor
considering the thermal mass of the earth soil.
This object is referenced by slab-on-grade or underground floor surfaces with their fields ‘Outside
Boundary Condition’ set to GroundFCfactorMethod.
1.9.44.1 Inputs
1.9.44.1.1 Field: Name
The name of the ground floor construction.
Construction:FfactorGroundFloor ,
slabconst ,
0.12, !F-factor in W/m-K
232.26 , !Area in m2
61.0; !Exposed perimeter in m
BuildingSurface:Detailed ,
Zn001:Flr001 , !- Name
Floor , !- Surface Type
slabconst , !- Construction Name , FLOOR
ZONE ONE , !- Zone Name
GroundFCfactorMethod , !- Outside Boundary Condition , Surface
, !- Outside Boundary Condition Object , Zn001:Flr001
NoSun , !- Sun Exposure
NoWind , !- Wind Exposure
0, !- View Factor to Ground
4, !- Number of Vertices
15.24 ,0.0 ,0.0 , !- X,Y,Z = = > Vertex 1
0.0 ,0.0 ,0.0 , !- X,Y,Z = = > Vertex 2
0.0 ,15.240 ,0.0 , !- X,Y,Z = = > Vertex 3
15.24 ,15.24 ,0.0; !- X,Y,Z = = > Vertex 4
1.9.45 ConstructionProperty:InternalHeatSource
In some cases, such as radiant systems, a construction will actually have resistance wires or hydronic tubing
embedded within the construction. Heat is then either added or removed from this building element to
provide heating or cooling to the zone in question. In the case of building-integrated photovoltaics, the
energy removed in the form of electricity will form a sink. It is possible to enter such constructions
into EnergyPlus with the syntax described below. The internal source capability is available with both
1.9. GROUP – SURFACE CONSTRUCTION ELEMENTS 249
1.9.45.1 Inputs
1.9.45.1.1 Field: Name
This field is a user specified name that will be used as a reference by other input syntax. For example,
a heat transfer surface (ref: Building Surfaces) requires a construction name to define what the make-up
of the wall is.
condition imposed at the inside and outside surface (i.e., surface temperatures are still isothermal as if the
surface was one-dimensional).
1.9.45.2 Outputs
• Zone,Average,Surface Internal Source Location Temperature [C]
1.9.46 Construction:AirBoundary
Construction:AirBoundary indicates an open boundary between two zones. It may be used for base surfaces
and fenestration surfaces. When this construction type is used, the Outside Boundary Condition of the
surface (or the base surface of a fenestration surface) must be either Surface or Zone. A base surface with
Construction:AirBoundary cannot hold any fenestration surfaces.
The two zones separated by this air boundary will be grouped together into a combined enclosure
for solar distribution, daylighting, and radiant exchange (including distribution of radiant internal gains).
If a given zone has an air boundary with more than one zone, then all of the connected zones will be
grouped together. For example, if there is an air boundary between zones A and B, and another air
boundary between zones B and C, all three zones (A, B, and C) will be grouped into a single enclo-
sure. Normal default simplified view factors will apply unless detailed view factors are specified using
ZoneProperty:UserViewFactors:BySurfaceName.
1.9.46.1 Inputs
1.9.46.1.1 Field: Name
The name of the construction.
None There will be no air exchange modeled across this surface. Other objects, such as ZoneMixing and
ZoneCrossMixing or AirflowNetwork openings may be specified if desired.
walls. These are walls—such as stud walls—that have complicated heat-flow paths so that the conduction
is two- or three-dimensional. Thermal bridges are one of the common terms for these complicated heat-flow
paths; this dataset will help you represent these in EnergyPlus.
The materials here are not real materials but are “equivalent” materials obtained from finite-difference
modeling. (The thickness, conductivity, density and specific heat values of the material layers for the
different constructions have been taken from the ASHRAE report “Modeling Two- and Three-Dimensional
Heat Transfer through Composite Wall and Roof Assemblies in Hourly Energy Simulation Programs (1145-
TRP),” by Enermodal Engineering Limited, Oak Ridge National Laboratory, and the Polish Academy of
Sciences, January 2001.). EnergyPlus will calculate conduction transfer functions using these materials.
The heat transfer based on these conduction transfer functions will then be very close to what would be
calculated with a two- or three-dimensional heat transfer calculation.
For stud walls, using these composite constructions will give more accurate heat flow than you would
get by manually dividing the wall into a stud section and a non-stud section.
If your wall’s exterior or interior roughness or thermal, solar or visible absorptances are different from
those in the data set, you can make the appropriate changes to the first material (the outside layer) or the
third material (the inside layer). None of the other values should be changed.
Complete description of the CompositeWallConstructions data set are found in the OutputDetail-
sAndExamples document.
1.9.48 Construction:ComplexFenestrationState
This input object is used to describe the properties of a single state for complex fenestration. There are
two parts to the input, 1) layer-by-layer physical description of fenestration system and 2) a set of matrices
that describe overall system optical performance. Each layer also has associated with it two matrices that
give the layer absorptance (for front and back incidence on the system.
The optical properties are given as a two-dimensional matrix describing the basis and four two-
dimensional matrices of system bidirectional optical properties.
These input objects will generally be exported directly from the WINDOW program and it is expected
that users usually will not develop the input themselves. However, this is an option for users who prefer
to use a different method (e.g., Monte-Carlo ray-trace or measurement) of determining optical properties.
Multiple instances of this object are used to define the separate operating states of complex fenestra-
tion. For example, blinds could be deployed or redirected to create a new state, or electrochromic glazings
could change transmittance. Each separate state defines the materials present and the overall optical
performance. If the glazing system has only one state, then only one of these objects is needed.
If there is more than one complex fenestration state, it will be controlled using the EMS actuator called
“Surface” with the control type “Construction State” and the EMS input object called EnergyManage-
mentSystem:ConstructionIndexVariable.
1.9.48.1 Inputs
1.9.48.1.1 Field: Name
Unique name of this construction. Used to identify type of window in surface objects.
An complex fenestration IDF example with double layer (first layer is shading device):
1.9.49 WindowThermalModel:Params
This input object is used with the Construction:ComplexFenestrationState
1.9.49.1 Inputs
1.9.49.1.1 Field: Name
Unique name of the window thermal model parameters.
• ISO15099
• EN673Declared
• EN673Design
• ISO15099
• ScaledCavityWidth
• ConvectiveScalarModel_NoSDThickness
• ConvectiveScalarModel_withSDThickness
• NoDeflection
• TemperatureAndPressureInput
• MeasuredDeflection
WindowThermalModel:Params ,
ThermParam_59 , !- name
ISO15099 , !- standard
ISO15099 , !- thermal model standard
1.00, !- SD scalar
NoDeflection; !- deflection model
WindowThermalModel:Params ,
ThermParam_59 , !- name
ISO15099 , !- standard
ISO15099 , !- thermal model standard
1.00, !- SD scalar
TemperatureAndPressureInput , !- deflection model
, !- vacuum pressure limit
21.00 , !- temperature at time of fabrication
10000.00; !- pressure at time of fabrication
WindowThermalModel:Params ,
ThermParam_1006 , !- name
ISO15099 , !- standard
ISO15099 , !- thermal model
1.0000 , !- SDScalar
NoDeflection , !- deflection model
13.238; !- vacuum pressure limit
1.9.50 Matrix:TwoDimension
This is input object is only used with Construction:ComplexFenestrationState object to enter a two-
dimensional matrix of values.
It is used to define the Basis Matrix for BSDF input data, and is also used to define the actual BSDF
matrices data for the complete fenestration definition as well as the individual layers of the system.
The data are entered in row-major order: all the elements of row 1, followed by all the elements of
row 2, etc. The number of values to be entered depends on the number of rows and the number of
columns. Blank fields are treated as having been set to zero.
See example IDF file “SmOff_ CmplxGlz_IntExtShading.idf” for the definition of two complex shading
layers with matrix data defined.
1.9.51 Construction:WindowEquivalentLayer
This object defines the construction for equivalent layer window (ASHWAT) model. This window can
model various mix of glazing and shading layers combination. Shadings are defined as an integral part of
the construction. The construction is defined by listing the layers name starting with outside layer and
work your way to the inside Layer. Up to six solid layers (glazing and shade) and up to five gaps, i.e.,
a total of up to 11 layers maximum are allowed in equivalent layer window object. The solid layer types
allowed are: Glazing, Insect Screen, Roller Blinds, Venetian Blind, and Drape Fabrics. This window model
requires optical data of the individual glazing and shading layers to calculate the effective optical properties
of the composite fenestration construction. Venetian blinds in equivalent layer window model can be in
a fixed slat angle or has the option to control the slat angle in order to maximize visibility, or maximize
solar gains. An equivalent-layer concept can simulate wide range of multiple glazing and shading layers
combination and provides unlimited flexibility to combine different types of shading layers in a fenestration.
The equivalent-layer window model does not support daylighting control. For the gap layer object any
one of the five different Gas types can be specified: AIR, ARGON, XENON, KRYPTON, or CUSTOM.
This window object is referenced by fenestration surfaces. For details of the model description refer to
Equivalent Layer Fenestration Model section in Engineering Reference. The various layer objects that can
be referenced in Equivalent Layer window model are:
WindowMaterial:Glass:EquivalentLayer
WindowMaterial:Shade:EquivalentLayer
WindowMaterial:Drape:EquivalentLayer
WindowMaterial:Blind:EquivalentLayer
WindowMaterial:Screen:EquivalentLayer
WindowMaterial:Gap:EquivalentLayer
1.9.51.1 Inputs
1.9.51.1.1 Field: Name
This field is a user specified name that will be used as a reference by other input syntax. For example,
a heat transfer surface (ref: Fenestration) requires a construction name to define what the make-up of
the fenestration is. This name must be identical to one of the Window Construction Equivalent Layer
definitions in the input data file.
Each equivalent layer window construction must have at least one layer. This field defines the material
name associated with the layer on the outside of the construction—outside referring to the side that is
exposed to the outdoor environment or another zone. Material layers for equivalent layer window model
are defined based on their thermal properties elsewhere in the input file (ref: WindowEquivalentLayerMa-
terialNames)
Construction:WindowEquivalentLayer ,
Six Solid Layers Window , !- Name
INSCRN , !- Outside Layer
Air GAP Outdoor 12.7mm , !- Layer 2
GLZGRY , !- Layer 3
Argon GAP Sealed 12.7mm , !- Layer 4
FEP , !- Layer 5
Xenon GAP Sealed 12.7mm , !- Layer 6
LOF1436 , !- Layer 7
Krypton GAP Sealed 12.7mm , !- Layer 8
GLZCLR , !- Layer 9
Air GAP Indoor 12.7mm , !- Layer 10
ShadeTrns; !- Layer 11
1.9.52 Construction:WindowDataFile
The WINDOW program, which does a thermal and optical analysis of a window under different design
conditions, writes a data file (“Window data file”) containing a description of the window that was analyzed.
The Construction:WindowDataFile object allows a window to be read in from the WINDOW data file—
see “Importing Windows from WINDOW.” For information on adding a shading device to the window see
“WindowShadingControl.”
1.9.52.1 Inputs
1.9.52.1.1 Field: Name
This is the name of a window on the Window data file. An error will result if EnergyPlus cannot find
a window of this name on the file, or if the file, shown in the next field, is not present. The location of the
data file should be specified in the File Name field. For details on what is done with the data if a matching
window is found on the file see “Importing Windows from WINDOW.”
command line, a relative path or a simple file name may work if RunEPlus.bat is run from the folder that
contains EnergyPlus.exe.
If this field is left blank, the file name is defaulted to Window5DataFile.dat.
Input Example
Construction:WindowDataFile ,
DoubleClear; !- Name of a Window on the Window Data File
! Note -- Window5DataFile.dat is presumed to be in the "run" folder where EnergyPlus.exe is
FenestrationSurface :Detailed ,
Zn001:Wall001:Win001 , !- Name
Window , !- Class
DoubleClear , !- Construction Name
Zn001:Wall001 , !- Base Surface Name , and Target (if applicable)
0.5, !- View Factor to Ground
, !- Frame/Divider name
1.0, !- Multiplier
4, !- Number of vertices
0.548 , 0.0, 2.5000 , !- X,Y,Z of Vertices
0.548 , 0.0, 0.5000 ,
5.548 , 0.0, 0.5000 ,
5.548 , 0.0, 2.5000;
An example showing use of specific data file name and complete path location follows:
Construction:WindowDataFile ,
DoubleClear , !- Name of a Window on the Window Data File
C:\ EnergyPlusData\DataSets\MyWindow.dat;
1.9.52.2 Outputs
An optional report (contained in eplusout.eio) gives calculational elements for the materials and construc-
tions used in the input. These reports are explained fully in the Output Details and Examples document.
1.10.1 Space
This object defines a space (or room) in the building. All Spaces are part of a Zone. Every Zone contains
one or more spaces.
Space is an optional input. If a Zone has no Space(s) specified in the input then a default Space named
<Zone Name> will be created. If some surfaces in a Zone are assigned to a Space and some are not,
then a default Space named <Zone Name>-Remainder will be created. Input references to Space Names
must have a matching Space object. Default space names may not be referenced in the input except for
Output:Variable keys).
Space geometry is specified by attaching surfaces to a space using the “Space Name” field. If a Space
has only floor surface(s) assigned to it, the Space is assumed to share the same enclosure with other such
Spaces in the same Zone (and with any surfaces that are not explicitly assinged to a space). If a Space
also has other types of surfaces (non-floor) then the Space forms its own enclosure unless it is connected
to other spaces with air boundaries (see Construction:AirBoundary).
260 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.10.1.1 Inputs
1.10.1.1.1 Field: Name
The name of the Space object. Must be unique across Zone and Space names.
1.10.2 SpaceList
The SpaceList object defines a list of Space objects. It is primarily used with Internal Gains objects
(People, Lights, etc.) to apply the same gain across a group of Spaces.
Space lists are not exclusive. A Space can be referenced by more than one SpaceList object.
1.10.2.1 Inputs
1.10.2.1.1 Field: Space List Name
The name of the SpaceList object. Must be unique across SpaceLists and Spaces.
SpaceList ,
Mid Floor List , !- Name
Mid West Space , !- Space 1 Name
Mid Center Space , !- Space 2 Name
Mid East Space; !- Space 3 Name
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 261
1.10.3 Zone
This element sets up the parameters to simulate each thermal zone of the building. This object defines a
thermal zone of the building. Every Zone contains one or more Spaces.
Space is an optional input. If a Zone has no Space(s) specified in the input then a default Space named
<Zone Name> will be created. If some surfaces in a Zone are assigned to a Space and some are not,
then a default Space named <Zone Name>-Remainder will be created. Input references to Space Names
must have a matching Space object. Default space names may not be referenced in the input except for
Output:Variable keys).
1.10.3.1 Inputs
1.10.3.1.1 Field: Name
The name of the Zone object. Must be unique across Zone and Space names.
Note that the Zone Ceiling Height is the distance from the Floor to the Ceiling in the Zone, not an
absolute height from the ground.
measurements on flat plates. The DOE-2 and MoWiTT were derived from field measurements. The
AdaptiveConvectionAlgorithm model is an dynamic algorithm that organizes a large number of different
convection models and automatically selects the one that best applies. The adaptive convection algorithm
can also be customized using the SurfaceConvectionAlgorithm:Outside:AdaptiveModelSelections input ob-
ject. All algorithms are described more fully in the Engineering Reference.
If omitted or blank, the algorithm specified in the SurfaceConvectionAlgorithm:Outside object is the
default.
Zone ,
DORM ROOMS AND COMMON AREAS , !- Name
0.0000000E+00, !- Direction of Relative North {deg}
0.0000000E+00, !- X Origin {m}
6.096000 , !- Y Origin {m}
0.0000000E+00, !- Z Origin {m}
1, !- Type
1, !- Multiplier
autocalculate , !-Ceiling Height {m}
autocalculate; !- Volume {m3}
– HVAC,Average,Zone Air Heat Balance System Convective Heat Gain Rate [W]
– HVAC,Average,Zone Air Heat Balance Air Energy Storage Rate [W]
– HVAC,Average,Zone Air Heat Balance Deviation Rate [W]
– HVAC,Sum,Zone Air System Sensible Heating Energy [J]
– HVAC,Sum,Zone Air System Sensible Cooling Energy [J]
– HVAC,Average,Zone Air System Sensible Heating Rate [W]
– HVAC,Average,Zone Air System Sensible Cooling Rate [W]
– HVAC,Average,Zone Air Humidity Ratio[kgWater/kgDryAir]
– HVAC,Average,Zone Air Relative Humidity[%]
These two variable outputs are/should be identical. However, note that they can be reported at
different time intervals. “Zone Mean Air Temperature” is only available on the Zone/HB timestep
(Number of Timesteps per Hour) whereas “Zone Air Temperature” can be reported at the HVAC
timestep (which can vary).
From the code definition, the zone mean air temperature is the average temperature of the air
temperatures at the system timestep. Remember that the zone heat balance represents a “well
stirred” model for a zone, therefore there is only one mean air temperature to represent the air
temperature for the zone.
This is very similar to the mean air temperature in the last field. The “well stirred” model for the
zone is the basis, but this temperature is also available at the “detailed” system timestep.
This is the dewpoint temperature of the zone calculated from the Zone Mean Air Temperature
(above), the Zone Air Humidity Ratio (below) and the outdoor barometric pressure.
This is the zone air node temperature for the well-mixed room air model, which is the default
room air model type (RoomAirModelType = Mixing). But for other types of Room Air Model (the
RoomAir:TemperaturePattern:* and RoomAirSettings:* objects) the zone thermostat air tempera-
ture may depend on the Thermostat Height and Thermostat Offset.
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 267
The Mean Radiant Temperature (MRT) in degrees Celsius of a space is a measure of the combined
effects of temperatures of surfaces within that space. Specifically it is the surface area × emissivity
weighted average of the zone inside surface temperatures (ref. Surface Inside Temperature), where
emissivity is the Thermal Absorptance of the inside material layer of each surface.
Zone Operative Temperature (OT) is the average of the Zone Mean Air Temperature (MAT) and
Zone Mean Radiant Temperature (MRT), OT = 0.5*MAT + 0.5*MRT. This output variable is not
affected by the type of thermostat controls in the zone, and does not include the direct effect of high
temperature radiant systems. See also Zone Thermostat Operative Temperature.
1.10.5.7 Zone Air Heat Balance Internal Convective Heat Gain Rate [W]
The Zone Air Heat Balance Internal Convective Heat Gain Rate is the sum, in watts, of heat
transferred to the zone air from all types of internal gains, including people, lights, equipment etc.
This and the following provide results on the load components of the zone air heat balance. This
field is not multiplied by zone or group multipliers.
The Zone Air Heat Balance Surface Convection Rate is the sum, in watts, of heat transferred to the
zone air from all the surfaces. This field is not multiplied by zone or group multipliers.
1.10.5.9 Zone Air Heat Balance Interzone Air Transfer Rate [W]
The Zone Air Heat Balance Interzone Air Transfer Rate is the sum, in watts, of heat transferred to
the zone air from all the transfers of air from other thermal zones. This field is not multiplied by
zone or group multipliers.
1.10.5.10 Zone Air Heat Balance Outdoor Air Transfer Rate [W]
The Zone Air Heat Balance Outdoor Air Transfer Rate is the sum, in watts, of heat transferred to
the zone air from all the transfers of air from the out side, such as infiltration. This field is not
multiplied by zone or group multipliers.
1.10.5.11 Zone Air Heat Balance System Air Transfer Rate [W]
The Zone Air Heat Balance System Air Transfer Rate is the sum, in watts, of heat transferred to the
zone air by HVAC forced-air systems and air terminal units. Such HVAC systems are connected to
the zone by an inlet node (see ZoneHVAC:EquipmentConnections input field called Zone Air Inlet
Node or Node List Name) This field is not multiplied by zone or group multipliers. The Zone Air
Heat Balance System Air Transfer Rate may not agree exactly with the equipment-level delivered
energy transfer rate when the zone temperature is changing significantly over a timestep (e.g. during
thermostat setback and setup), but the energy will balance out over time.
268 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.10.5.12 Zone Air Heat Balance System Convective Heat Gain Rate [W]
The Zone Air Heat Balance System Convective Heat Gain Rate is the sum, in watts, of heat trans-
ferred directly to the zone air by “non-air” HVAC systems. Such HVAC systems are not connected
to the zone by an inlet node but rather add or subtract heat directly to the zone air in a manner
similar to internal gains. These include the convective fraction of zone HVAC baseboards and high
temperature radiant systems, zone HVAC refrigeration chiller set, and the extra convective cool-
ing provided by the cooled beam air terminal unit. This field is not multiplied by zone or group
multipliers.
1.10.5.13 Zone Air Heat Balance Air Energy Storage Rate [W]
The Zone Air Heat Balance Air Energy Storage Rate is the heat stored, in watts, in the zone air as
result of zone air temperature changing from one timestep to the next. This field is not multiplied
by zone or group multipliers.
The Zone Air Heat Balance Deviation Rate is the imbalance, in watts, in the energy balance for zone
air. The value should be near zero but will become non-zero if zone conditions are changing rapidly
or erratically. This field is not multiplied by zone or group multipliers. (This output variable is only
generated if the user has set a computer system environment variable DisplayAdvancedReportVari-
ables equal to “yes”.)
This output variable represents the sensible heating energy in Joules that is actually supplied by
the system to that zone for the timestep reported. This is the sensible heating rate multiplied
by the simulation timestep. This is calculated and reported from the Correct step in the Zone
Predictor-Corrector module. This field is not multiplied by zone or group multipliers.
Zone Air System Sensible Heating (and Cooling) Energy (and Rate) all report the heating or
cooling delivered by the HVAC system to a zone. These values are calculated by multiplying
the supply air mass flow rate by the difference between the supply air temperature and the zone
air temperature. This does not always indicate the operation of heating or cooling coils. For
example, cooling will be reported if the supply air is cooled due to the introduction of outside
air, even if all coils are off.
In addition, certain ”non-air” zone-based systems will also add their heating or cooling contri-
bution to this output variable. For example, the following zone equipment will also add their
output to the appropriate heating or cooling energy/rate output variable:
– ZoneHVAC:Baseboard:RadiantConvective:Water
– ZoneHVAC:Baseboard:RadiantConvective:Steam
– ZoneHVAC:Baseboard:RadiantConvective:Electric
– ZoneHVAC:Baseboard:Convective:Water
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 269
– ZoneHVAC:Baseboard:Convective:Electric
– ZoneHVAC:CoolingPanel:RadiantConvective:Water
– ZoneHVAC:RefrigerationChillerSet
This means that system output from equipment such as high and low temperature radiant systems
are NOT included in this output variable as the control of these radiant systems are handled
separately with their own unique controls.
Finally, note that these variables are calculated at the system timestep. When reported at the
“detailed” reporting frequency, these variables will never show heating and cooling both in the
same system timestep. If reported at a frequency less than “Detailed” (for example, Hourly)
values may appear in both the heating and cooling variable for the same hour if the system
cooled the zone for part of the reporting period and heated the zone for another part of the
reporting period.
This output variable represents the sensible cooling energy in Joules that is actually supplied by
the system to that zone for the timestep reported. This is the sensible cooling rate multiplied
by the simulation timestep. This is calculated and reported from the Correct step in the Zone
Predictor-Corrector module. This field is not multiplied by zone or group multipliers. For additional
information on this output variable, see the note that accompanies the Zone Air System Sensible
Heating Energy output variable above.
This output variable represents the sensible heating rate in Watts that is actually supplied by the
system to that zone for the timestep reported. This is calculated and reported from the Correct step
in the Zone Predictor-Corrector module. This field is not multiplied by zone or group multipliers.
For additional information on this output variable, see the note that accompanies the Zone Air
System Sensible Heating Energy output variable above.
This output variable represents the sensible cooling rate in Watts that is actually supplied by the
system to that zone for the timestep reported. This is calculated and reported from the Correct step
in the Zone Predictor-Corrector module. This field is not multiplied by zone or group multipliers.
For additional information on this output variable, see the note that accompanies the Zone Air
System Sensible Heating Energy output variable above.
This output variable represents the air humidity ratio after the correct step for each zone. The
humidity ratio is the mass of water vapor to the mass of dry air contained in the zone in (kg
water/kg air) and is unitless.
270 CHAPTER 1. INPUT-OUTPUT REFERENCE
This output variable represents the air relative humidity after the correct step for each zone. The
relative humidity is in percent and uses the Zone Air Temperature, the Zone Air Humidity Ratio
and the Outside Barometric Pressure for calculation.
These output variables represent the sum of radiant gains from specific internal sources (e.g. equip-
ment) throughout the space or zone in Watts (for rate) or joules. This includes radiant gain from
People, Lights, Electric Equipment, Gas Equipment, Other Equipment, Hot Water Equipment, and
Steam Equipment.
1.10.5.23 Space or Zone Total Internal Visible Radiation Heating Rate [W]
1.10.5.24 Space or Zone Total Internal Visible Radiation Heating Energy [J]
These output variables expresse the sum of heat gain in Watts (for rate) or joules that is the
calculated short wavelength radiation gain from lights in the space or zones. This calculation uses
the total energy from lights and the fraction visible to realize this value, summed over the space or
zones in the simulation.
These output variables represent the sum of convective gains from specific sources (e.g. equipment)
throughout the space or zone in Watts (for rate) or joules. This includes convective gain from People,
Lights, Electric Equipment, Gas Equipment, Other Equipment, Hot Water Equipment, and Steam
Equipment.
These output variables represent the sum of latent gains from specific internal sources (e.g. equip-
ment) throughout the space or zone in Watts (for rate) or joules. This includes latent gain from
People, Electric Equipment, Gas Equipment, Other Equipment, Hot Water Equipment, and Steam
Equipment.
These output variables represent the sum of all heat gains throughout the space or zone in Watts (for
rate) or joules. This includes all heat gains from People, Lights, Electric Equipment, Gas Equipment,
Other Equipment, Hot Water Equipment, and Steam Equipment.
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 271
These output variables represent the heat emitted to ambient from exfiltration in Watts. The
exfiltration rate is calculated by solving a mass flow balance on the zone including infiltration,
ventilation, outdoor air mixing, zone-to-zone mixing, and all of the zone inlet, exhaust, and return
nodes. The latent parts are determined by taking the difference between the total and the sensible
rate. Positive values indicate the zone injects heat to the environment, while negative values indicate
the building extracts heat from the environment.
These output variables represent the heat emitted to ambient from exhaust air in Watts. The zone
exhaust air flow rate is aggregated from the zone exhaust nodes. Positive values indicate the building
injects heat to the environment, while negative values indicate the building extracts heat from the
environment.
These output variables represent the total amount of heat emitted to ambient from all zones by
exfiltration in Watts. Positive values indicate the building injects heat to the environment, while
negative values indicate the building extracts heat from the environment. This includes both sensible
and latent heat loss from zone exfiltration.
These output variables represent the total amount of heat emitted to ambient from all zones by
exhaust air in Watts. Positive values indicate the building injects heat to the environment, while
negative values indicate the building extracts heat from the environment. This includes both sensible
and latent heat loss from zone exhaust air.
1.10.6 ZoneList
The ZoneList object defines a list of Zone objects. It is primarily used with the ZoneGroup object
to provide a generalized way for doing “Floor Multipliers”. (See the ZoneGroup description below.)
The associated ZoneList output variables also provide a way to aggregate and organize zone loads.
Zone lists are not exclusive. A zone can be referenced be more than one ZoneList object.
272 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.10.6.1 Inputs
ZoneList ,
Mid Floor List , !- Name
Mid West Zone , !- Zone 1 Name
Mid Center Zone , !- Zone 2 Name
Mid East Zone; !- Zone 3 Name
1.10.6.2 Outputs
All ZoneList variables are the sum of the corresponding Zone variables. Zone Multiplier fields in the
Zone objects are also taken into account.
1.10.7 ZoneGroup
The ZoneGroup object adds a multiplier to a ZoneList. This can be used to reduce the amount
of input necessary for simulating repetitive structures, such as the identical floors of a multi-story
building. To create a “Floor Multiplier”, use the ZoneList object to organize several zones into a
typical floor. Then use the Zone List Multiplier field in the ZoneGroup object to multiply the system
load for the zones in the list will also be multiplied. Zones with a Multiplier field greater than one
in the Zone object are effectively double-multiplied.
NOTE: Although ZoneLists are not exclusive by themselves, ZoneLists used to form a ZoneGroup
are exclusive; the ZoneLists used with a ZoneGroup must not have any zones in common.
1.10.7.1 Inputs
– For floors that are multiplied, connect exterior boundary conditions of the floor to the ceiling
and vice versa.
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 273
– Since exterior convection coefficients vary with elevation, locate the typical middle floor zones
mid-height between the lowest and highest middle floors to be modeled.
– Shading must be identical for all multiplied floors or less accurate results may be obtained by
using the zone list multiplier.
ZoneGroup and ZoneList can also be used to simulate other repetitive cases, such as clusters of zones
on the ground.
ZONE GROUP ,
Mid Floor , !- Zone Group Name
Mid Floor List , !- Zone List Name
8; !- Zone List Multiplier
1.10.7.2 Outputs
All ZoneGroup variables report the associated ZoneList value multiplied by the Zone List Multiplier.
1.10.8 Surface(s)
What’s a building without surfaces?
EnergyPlus allows for several surface types:
– BuildingSurface:Detailed
274 CHAPTER 1. INPUT-OUTPUT REFERENCE
– FenestrationSurface:Detailed
– Shading:Site:Detailed
– Shading:Building:Detailed
– Shading:Zone:Detailed
Each of the preceding surfaces has “correct” geometry specifications. BuildingSurface and Fenes-
tration surfaces (heat transfer surfaces) are used to describe the important elements of the building
(walls, roofs, floors, windows, doors) that will determine the interactions of the building surfaces
with the outside environment parameters and the internal space requirements. These surfaces are
also used to represent “interzone” heat transfer. All surfaces are modeled as a thin plane (with no
thickness) except that material thicknesses are taken into account for heat transfer calculations.
During specification of surfaces, several “outside” environments may be chosen:
– Ground – when the surface is in touch with the ground (e.g. slab floors)
– Outdoors – when the surface is an external surface (e.g. walls, roofs, windows directly exposed
to the outdoor conditions)
– Surface – when the surface is
∗ An adiabatic internal zone surface
∗ A interzone surface
– Zone – when the surface is
∗ A interzone surface in which the other surface is not put in the input file.
– OtherSideCoefficients – when using a custom profile to describe the external conditions of
the surface (advanced concept – covered in subject: SurfaceProperty:OtherSideCoefficients)
– OtherSideConditionsModel – when using specially modeled components, such as active
solar systems, that cover the outside surface and modify the conditions it experiences.
– The zone that contains the other surface that is adjacent to this surface but is not entered in
input.
Note that heat transfer surfaces are fully represented with each description. As stated earlier in
the Construction description, materials in the construction (outside to inside) are included but
film coefficients neither inside nor outside are used in the description – these are automatically
calculated during the EnergyPlus run. Interzone surfaces which do not have a symmetrical
construction (such as a ceiling/floor) require two Construction objects with the layers in reverse
order. For example, CEILING with carpet, concrete, ceiling tile and FLOOR with ceiling tile,
concrete, carpet. If interzone surfaces have a symmetrical construction, the specification for the
two surfaces can reference the same Construction. When a surface is connected as the outside
boundary condition for another surface, the two surfaces may be in the same plane, or they may
be separated to imply thickness.
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 275
Shading surfaces are used to describe aspects of the site which do not directly impact the physical
interactions of the environmental parameters but may significantly shade the building during specific
hours of the day or time so the year (e.g. trees, bushes, mountains, nearby buildings which aren’t
being simulated as part of this facility, etc.)
Note that surfaces which are part of the simulated building automatically shade other parts of
the building as geometry and time of day dictate – there is no need on the user’s part to include
surfaces that might be in other zones for shading.
– InternalMass
is used to specify the construction/material parameters and area of items within the space that are
important to heat transfer calculations but not necessarily important geometrically. (For example,
furniture within the space – particularly for large spaces). Internal mass can also be used for
internal walls that are not needed (when FullInteriorAndExterior Solar Distribution is in effect) for
solar distribution or to represent many, if not all, interior walls when solar is distributed to the floors
only.
– Adiabatic Surfaces – These surfaces would be represented as common surfaces (between two
zones) where both zones are typically the same temperature. Thus, no transfer is expected
in the surface from one zone to the next. These surfaces should be described as simply in-
ternal surfaces for the zone referencing as their Outside Boundary Condition Object (see later
description in individual surface objects) their own surface names.
– Surfaces in Middle Zones – Middle zones in a building can be simulated using a judicious use of
surfaces and zone multipliers to effect the correct “loads” for the building. Thus, middle zone
behavior can be simulated without modeling the adjacent zones. This is done by specifying a
surface within the zone. For example, a middle floor zone can be modeled by making the floor
the Outside Boundary Condition Object for the ceiling, and the ceiling the Outside Boundary
Condition Object for the floor.
– Surfaces between Zones with differing temperatures – These zones represent the true use of
interzone surfaces. In a residence that has an attached garage, the garage may be unheat-
ed/uncooled or at least not conditioned to the same degree as the residence interior. In this
case, EnergyPlus can be used to accurately calculate the effects of the differently conditioned
space to the other spaces.
If geometry is correct, conditions 1, 3, and 7 should take care of all surfaces, but the other conditions
supply common sense when the geometry is incorrect. More information about the EnergyPlus view
factor calculation is contained in the Engineering Reference document.
1.10.11 GlobalGeometryRules
Before the surface objects are explained in detail, a description of geometric parameters used in
EnergyPlus will be given. Since the input of surface vertices is common to most of the surface types,
it will also be given a separate discussion.
Some flexibility is allowed in specifying surface vertices. This flexibility is embodied in the Global-
GeometryRules class/object in the input file. Note that the parameters specified in this statement
are used for all surface vertice inputs – there is no further “flexibility” allowed.
In order to perform shadowing calculations, the building surfaces must be specified. EnergyPlus uses
a three dimensional (3D) Cartesian coordinate system for surface vertex specification. This Right
Hand coordinate system has the X-axis pointing east, the Y-axis pointing north, and the Z-axis
pointing up. See figure below.
1.10.11.1 Inputs
surface were 4 sided. Extrapolate 3 sided figures to this convention. For 5 and more sided figures,
again, try to extrapolate the best “corner” starting position.
1.10.12 Surfaces
Surfaces make up the buildings and the elements that shade buildings. There are several methods
to inputting surfaces, ranging from simple rectangular surfaces to detailed descriptions that describe
each vertex in the order specified in the GlobalGeometryRules object. The simple, rectangular
surface objects are described first with the more detailed descriptions following.
1.10.13 Walls
Walls are usually vertical (tilt = 90 degrees). These objects are used to describe exterior walls,
interior walls (adiabatic), underground walls, and walls adjacent to other zones.
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 279
1.10.14 Wall:Exterior
The Wall:Exterior object is used to describe walls that are exposed to the external environment.
They receive sun, wind – all the characteristics of the external world.
1.10.14.1 Inputs
1.10.15 Wall:Adiabatic
The Wall:Adiabatic object is used to describe interior walls and partitions. Adiabatic walls are used
to describe walls next to zones that have the same thermal conditions (thus, no heat transfer).
1.10.15.1 Inputs
1.10.16 Wall:Underground
The Wall:Underground object is used to describe walls with ground contact. The temperature at
the outside of the wall is the temperature in the GroundTemperature:BuildingSurface object.
1.10.16.1 Inputs
1.10.17 Wall:Interzone
The Wall:Interzone object is used to describe walls adjacent to zones that are significantly different
conditions than the zone with this wall.
1.10.17.1 Inputs
1.10.18 Roofs/Ceilings
Roofs and ceilings are, by default, flat (tilt = 0 degrees). These objects are used to describe roofs,
interior ceilings (adiabatic) and ceilings adjacent to other zones.
1.10.19 Roof
The Roof object is used to describe roofs that are exposed to the external environment.
284 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.10.19.1 Inputs
1.10.20 Ceiling:Adiabatic
The Ceiling:Adiabatic object is used to describe interior ceilings that separate zones of like conditions.
1.10.20.1 Inputs
1.10.21 Ceiling:Interzone
The Ceiling:Interzone object is used to describe interior ceilings that separate zones of differing
conditions (and expect heat transfer through the ceiling from the adjacent zone).
1.10.21.1 Inputs
1.10.22 Floors
Floors are, by default, flat (tilt = 180 degrees). These objects are used to describe floors on the
ground, interior floors (adiabatic) and floors adjacent to other zones.
1.10.23 Floor:GroundContact
The Floor:GroundContact object is used to describe floors that have ground contact (usually called
slabs). The temperature at the outside of the floor is the temperature in the GroundTempera-
ture:BuildingSurface object.
1.10.23.1 Inputs
1.10.24 Floor:Adiabatic
The Floor:Adiabatic object is used to describe interior floors or floors that you wish to model with
no heat transfer from the exterior to the floor.
1.10.24.1 Inputs
1.10.25 Floor:Interzone
The Floor:Interzone object is used to describe floors that are adjacent to other zones that have
differing conditions and you wish to model the heat transfer through the floor.
290 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.10.25.1 Inputs
1.10.26 Windows/Doors
The following window and door objects can be used to specify simple, rectangular doors and windows.
In each case, the lower left corner (locator coordinate) of the window or door is specified relative to
the surface it is on. Viewing the base surface as a planar surface, base the relative location from the
lower left corner of the base surface. Vertex entry description as well as provisions for a few other
surface types can be entered with the FenestrationSurface:Detailed object.
1.10.27 Window
The Window object is used to place windows on surfaces that can have windows, including exterior
walls, interior walls, interzone walls, roofs, floors that are exposed to outdoor conditions, interzone
ceiling/floors. These, of course, can be entered using the simple rectangular objects or the more
detailed vertex entry objects. Shades and screens may be applied by referencing this subsurface in
a window shading control (ref: WindowShadingControl object). To assign a shade to a window or
glass door, see WindowMaterial: Shade. To assign a screen, see WindowMaterial:Screen. To assign
a blind, see WindowMaterial:Blind. To assign switchable glazing, such as electrochromic glazing,
see WindowShadingControl.
1.10.27.1 Inputs
1.10.28 Door
The Door object is used to place opaque doors on surfaces that can have doors, including exterior
walls, interior walls, interzone walls, roofs, floors that are exposed to outdoor conditions, interzone
ceiling/floors. These, of course, can be entered using the simple rectangular objects or the more
detailed vertex entry objects.
1.10.28.1 Inputs
1.10.29 GlazedDoor
The GlazedDoor object is used to place doors on surfaces that can have doors, including exterior
walls, interior walls, interzone walls, roofs, floors that are exposed to outdoor conditions, interzone
ceiling/floors. These, of course, can be entered using the simple rectangular objects or the more
detailed vertex entry objects. Shades and screens may be applied by referencing this subsurface in
a window shading control (ref: WindowShadingControl object). To assign a shade to a window or
glass door, see WindowMaterial: Shade. To assign a screen, see WindowMaterial:Screen. To assign
a blind, see WindowMaterial:Blind. To assign switchable glazing, such as electrochromic glazing,
see WindowShadingControl.
1.10.29.1 Inputs
1.10.30 Window:Interzone
The Window:Interzone object is used to place windows on surfaces that can have windows, including
interzone walls, interzone ceiling/floors. These, of course, can be entered using the simple rectangular
objects or the more detailed vertex entry objects.
1.10.30.1 Inputs
subsurfaces (and the calculation of the interior distribution of beam solar radiation transmitted by
windows and glass doors) are done for the specified subsurface position and dimensions.
Multiplier should be used with caution. Multiplier > 1 can give inaccurate or nonsensical results in
situations where the results are sensitive to window or glass door position. This includes shadowing
on the window/glass door, daylighting from the window/glass door, and interior distribution of solar
radiation from the window/glass door. In these cases, the results for the single input window/glass
door, after multiplication, may not be representative of the results you would get if you entered each
of the multiple subsurfaces separately.
If Multiplier > 1, you will get
–a warning if Solar Distribution = FullExterior or FullInteriorAndExterior (ref: Building - Field:
Solar Distribution), indicating that the shadowing on the input window or the interior solar radiation
distribution from the input window may not be representative of the actual group of windows. No
warning is issued if Solar Distribution = MinimalShadowing.
–an error if the window is an exterior window/glass door in a zone that has a detailed daylighting
calculation (Daylighting:Detailed specified for the zone). Since a single window with a multiplier
can never give the same daylight illuminance as the actual set of windows, you are not allowed to
use Multiplier in this situation.
1.10.31 Door:Interzone
The Door:Interzone object is used to place opaque doors on surfaces that can have doors, including
interzone walls, interzone ceiling/floors. These, of course, can be entered using the simple rectangular
objects or the more detailed vertex entry objects.
298 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.10.31.1 Inputs
1.10.32 GlazedDoor:Interzone
The GlazedDoor:Interzone object is used to place doors on surfaces that can have doors, including
interzone walls, interzone ceiling/floors. These, of course, can be entered using the simple rectangular
objects or the more detailed vertex entry objects.
1.10.32.1 Inputs
Wall:Exterior ,
Zn001:Wall001 , !- Name
EXTERIOR , !- Construction Name
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 301
Window ,
Zn001:Wall001:Win001 , !- Name
SINGLE PANE HW WINDOW , !- Construction Name
Zn001:Wall001 , !- Building Surface Name
, !- Frame and Divider Name
1, !- Multiplier
4, !- Starting X Coordinate {m}
3, !- Starting Z Coordinate {m}
3, !- Length {m}
5; !- Height {m}
Door ,
Zn001:Wall001:Door001 , !- Name
HOLLOW WOOD DOOR , !- Construction Name
Zn001:Wall001 , !- Building Surface Name
1, !- Multiplier
14, !- Starting X Coordinate {m}
0, !- Starting Z Coordinate {m}
3, !- Length {m}
5; !- Height {m}
Wall:Adiabatic ,
Zn001:Wall004 , !- Name
INTERIOR , !- Construction Name
ZONE 1, !- Zone Name
90, !- Azimuth Angle {deg}
90, !- Tilt Angle {deg}
20, !- Starting X Coordinate {m}
0, !- Starting Y Coordinate {m}
0, !- Starting Z Coordinate {m}
20, !- Length {m}
10; !- Height {m}
Floor:Adiabatic ,
Zn001:Flr001 , !- Name
FLOOR , !- Construction Name
ZONE 1, !- Zone Name
90, !- Azimuth Angle {deg}
180, !- Tilt Angle {deg}
0, !- Starting X Coordinate {m}
0, !- Starting Y Coordinate {m}
0, !- Starting Z Coordinate {m}
20, !- Length {m}
20; !- Width {m}
Ceiling:Interzone ,
Zn001:Roof001 , !- Name
CEILING34 , !- Construction Name
ZONE 1, !- Zone Name
Zn003:Flr001 , !- Outside Boundary Condition Object
180, !- Azimuth Angle {deg}
0, !- Tilt Angle {deg}
0, !- Starting X Coordinate {m}
0, !- Starting Y Coordinate {m}
10, !- Starting Z Coordinate {m}
20, !- Length {m}
20; !- Width {m}
Window ,
Zn002:Wall001:Win001 , !- Name
SINGLE PANE HW WINDOW , !- Construction Name
302 CHAPTER 1. INPUT-OUTPUT REFERENCE
– BuildingSurface:Detailed
– Wall:Detailed
– RoofCeiling:Detailed
– Floor:Detailed
– FenestrationSurface:Detailed
– Shading:Site:Detailed
– Shading:Building:Detailed
– Shading:Zone:Detailed
use the same vertex input. The numeric parameters indicated below are taken from the BuildingSur-
face:Detailed definition; the others may not be exactly the same but are identical in configuration.
They are also “extensible” – so, to define more vertices for these surfaces, simply add the required
number of vertices (X, Y, and Z coordinates for each vertex) to the input file. Note that Fenestra-
tionSurface:Detailed is not extensible and is limited to 4 (max) vertices. If the Number of Surface
Vertex groups is left blank or entered as autocalculate, EnergyPlus looks at the number of groups
entered and figures out how many coordinate groups are entered.
Note that the resolution on the surface vertex input is 1 millimeter (.001 meter).
Therefore, using vertices that are very close together (< 1 mm) may result in invalid
dot product and fatal errors during shading calculations.
The figure above will help illustrate Surface Vertex entry. The convention used in “GlobalGeom-
etryRules” dictates the order of the vertices (ref: GlobalGeometryRules). In this example, the
conventions used are Starting Vertex Position = UpperLeftCorner and Vertex Entry Direction =
CounterClockwise. The surfaces for this single zone are:
4,0,0,H, 0,0,0, A,0,0, A,0,H; ! (4 vertices , South Wall)
4,A,0,H,A,0,0,A,B,0,A,B,H; ! (4 vertices , East Wall)
ignore other walls that are not shown in this figure
4,C,0,J,A,0,H,A,B,H,C,B,J; ! (4 vertices , roof)
3,C,0,J,0,0,H,A,0,H; ! (3 vertices , gable end)
4,0,0,H, 0,0,0, A,0,0, A,0,H; ! (4 vertices , South Wall)
Note that in this example, point 1 of the entry is the Upper Left Corner of the rectangular surfaces
and the point of the triangle for the 3 sided surface. The east wall shows the order of vertex
entry. For horizontal surfaces, any vertex may be chosen as the starting position, but the Vertex
Entry Direction convention must be followed. The surface details report (Output: Surfaces:List,
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 303
Details;) is very useful for reviewing the accuracy of surface geometry inputs (ref: Surface Output
Variables/Reports and Variable Dictionary Reports).
From the detailed vertices, EnergyPlus tries to determine the “height” and “width” of the surface.
Obviously, this doesn’t work well for >4 sided surfaces; for these, if the calculated height and width
are not close to the gross area for the surface, the height and width shown will be the square root of
the area (and thus a square).
1.10.35 Wall:Detailed
The Wall:Detailed object is used to describe walls.
1.10.35.1 Inputs
1. Surface – if this surface is an internal surface, then this is the choice. The value will either be a
surface in the base zone or a surface in another zone. The heat balance between two zones can
be accurately simulated by specifying a surface in an adjacent zone. EnergyPlus will simulate
a group of zones simultaneously and will include the heat transfer between zones. However, as
this increases the complexity of the calculations, it is not necessary to specify the other zone
unless the two zones will have a significant temperature difference. If the two zones will not be
very different (temperature wise), then the surface should use itself as the outside environment
or specify this field as Adiabatic. The surface name on the “outside” of this surface (adjacent
to) is placed in the next field.
2. Adiabatic – an internal surface in the same Zone. This surface will not transfer heat out of the
zone, but will still store heat in thermal mass. Only the inside face of the surface will exchange
heat with the zone (i.e. two adiabatic surfaces are required to model internal partitions where
both sides of the surface are exchanging heat with the zone). The Outside Boundary Condition
Object can be left blank.
3. Zone – this is similar to Surface but EnergyPlus will automatically create the required surface
in the adjacent zone when this is entered for the surface. If there are windows or doors on the
surface, EnergyPlus automatically creates appropriate sub-surfaces as well.
4. Outdoors – if this surface is exposed to outside temperature conditions, then this is the choice.
See Sun Exposure and Wind Exposure below for further specifications on this kind of surface.
5. Foundation - uses an alternative model (currently only the KivaTM model) to account for
the multi-dimensional heat transfer of foundation surfaces. The Outside Boundary Condition
Object will refer to the name of a Foundation:Kiva object (or be left blank to use the default
foundation without extra insulation).
6. Ground - The temperature on the outside of this surface will be the Site:GroundTemperature:Surface
value for the month.
7. GroundFCfactorMethod – if this surface is exposed to the ground and using the Construc-
tion:CfactorUndergroundWall, then this is the choice. The temperature on the outside of
this surface will be the Site:GroundTemperature:FcfactorMethod value for the month.
8. OtherSideCoefficients – if this surface has a custom, user specified temperature or other
parameters (See SurfaceProperty:OtherSideCoefficients specification), then this is the choice.
The outside boundary condition will be the name of the SurfaceProperty:OtherSideCoefficients
specification.
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 305
Note: Zones with interzone heat transfer are not adiabatic and the internal surfaces contribute
to gains or losses. Adiabatic surfaces are modeled by specifying the base surface itself in this
field. Also, for interzone heat transfer, both surfaces must be represented – for example, if you
want interzone heat transfer to an attic space, the ceiling in the lower zone must have a surface
object with the outside face environment as the floor in the attic and, likewise, there must be a
floor surface object in the attic that references the ceiling surface name in the lower zone.
Equally, if the Outside Boundary Condition is “OtherSideCoefficients”, then this field’s value
must be the SurfaceProperty:OtherSideCoefficients name. Or if the Outside Boundary
Condition is “OtherSideConditionsModel” then this field’s value must be the SurfaceProp-
erty:OtherSideConditionsModel name.
306 CHAPTER 1. INPUT-OUTPUT REFERENCE
Note: When a surface is specified with “NoWind”, this has several implications. Within the heat
balance code, this surface will default to using the simple ASHRAE exterior convection coefficient
correlation with a zero wind speed. In addition, since the ASHRAE simple method does not
have a separate value for equivalent long wavelength radiation to the sky and ground, using
“NoWind” also eliminates long wavelength radiant exchange from the exterior of the surface to
both the sky and the ground. Thus, only simple convection takes place at the exterior face of a
surface specified with “NoWind”.
the shelf. And for DaylightingDevice:Tubular you need to enter the View Factor to Ground for the
FenestrationSurface:Detailed corresponding to the dome of the tubular device.
Note 1: The corresponding view factor to the sky for diffuse solar radiation is not a user input; it
is calculated within EnergyPlus based on surface orientation, sky solar radiance distribution, and
shadowing surfaces.
Note 2: The view factors to the sky and ground for thermal infrared (long-wave) radiation are not
user inputs; they are calculated within EnergyPlus based on surface tilt and shadowing surfaces.
Shadowing surfaces are considered to have the same emissivity and temperature as the ground, so
they are lumped together with the ground in calculating the ground IR view factor.
1.10.36 RoofCeiling:Detailed
The RoofCeiling:Detailed object is used to describe a roof or ceiling.
1.10.36.1 Inputs
1. Surface – if this surface is an internal surface, then this is the choice. The value will either be a
surface in the base zone or a surface in another zone. The heat balance between two zones can
be accurately simulated by specifying a surface in an adjacent zone. EnergyPlus will simulate
a group of zones simultaneously and will include the heat transfer between zones. However, as
this increases the complexity of the calculations, it is not necessary to specify the other zone
unless the two zones will have a significant temperature difference. If the two zones will not be
very different (temperature wise), then the surface should use itself as the outside environment
308 CHAPTER 1. INPUT-OUTPUT REFERENCE
or specify this field as Adiabatic. The surface name on the “outside” of this surface (adjacent
to) is placed in the next field.
2. Adiabatic – an internal surface in the same Zone. This surface will not transfer heat out of the
zone, but will still store heat in thermal mass. Only the inside face of the surface will exchange
heat with the zone (i.e. two adiabatic surfaces are required to model internal partitions where
both sides of the surface are exchanging heat with the zone). The Outside Boundary Condition
Object can be left blank.
3. Zone – this is similar to Surface but EnergyPlus will automatically create the required surface
in the adjacent zone when this is entered for the surface. If there are windows or doors on the
surface, EnergyPlus automatically creates appropriate sub-surfaces as well.
4. Outdoors – if this surface is exposed to outside temperature conditions, then this is the choice.
See Sun Exposure and Wind Exposure below for further specifications on this kind of surface.
5. Ground – The temperature on the outside of this surface will be the Ground Temperature.
6. OtherSideCoefficients – if this surface has a custom, user specified temperature or other
parameters (See SurfaceProperty:OtherSideCoefficients specification), then this is the choice.
The outside boundary condition will be the name of the SurfaceProperty:OtherSideCoefficients
specification.
7. OtherSideConditionsModel – if this surface has a specially-modeled multi-skin component,
such as a transpired collector or vented photovoltaic panel, attached to the outside (See Sur-
faceProperty:OtherSideConditionsModel specification), then this the choice. The outside face
environment will be the name of the SurfaceProperty:OtherSideConditionsModel specification.
8. GroundSlabPreprocessorAverage – uses the average results from the Slab preprocessor
calculations.
9. GroundSlabPreprocessorCore – uses the core results from the Slab preprocessor calcula-
tions.
10. GroundSlabPreprocessorPerimeter – uses the perimeter results from the Slab preprocessor
calculations.
11. GroundBasementPreprocessorAverageWall – uses the average wall results from the Base-
ment preprocessor calculations.
12. GroundBasementPreprocessorAverageFloor – uses the average floor results from the
Basement preprocessor calculations.
13. GroundBasementPreprocessorUpperWall – uses the upper wall results from the Base-
ment preprocessor calculations.
14. GroundBasementPreprocessorLowerWall – uses the lower wall results from the Basement
preprocessor calculations.
zones. This is done by specifying a surface within the zone. For example, a middle floor zone can be
modeled by making the floor the Outside Boundary Condition Object for the ceiling, and the ceiling
the Outside Boundary Condition Object for the floor.
If the Outside Boundary Condition is Zone, then this field should contain the zone name of the
adjacent zone for the surface.
Note: Zones with interzone heat transfer are not adiabatic and the internal surfaces contribute
to gains or losses. Adiabatic surfaces are modeled by specifying the base surface itself in this
field. Also, for interzone heat transfer, both surfaces must be represented – for example, if you
want interzone heat transfer to an attic space, the ceiling in the lower zone must have a surface
object with the outside face environment as the floor in the attic and, likewise, there must be a
floor surface object in the attic that references the ceiling surface name in the lower zone.
Equally, if the Outside Boundary Condition is “OtherSideCoefficients”, then this field’s value
must be the SurfaceProperty:OtherSideCoefficients name. Or if the Outside Boundary
Condition is “OtherSideConditionsModel” then this field’s value must be the SurfaceProp-
erty:OtherSideConditionsModel name.
Note: When a surface is specified with “NoWind”, this has several implications. Within the heat
balance code, this surface will default to using the simple ASHRAE exterior convection coefficient
correlation with a zero wind speed. In addition, since the ASHRAE simple method does not
have a separate value for equivalent long wavelength radiation to the sky and ground, using
“NoWind” also eliminates long wavelength radiant exchange from the exterior of the surface to
both the sky and the ground. Thus, only simple convection takes place at the exterior face of a
surface specified with “NoWind”.
Unused if reflections option in Solar Distribution field in Building object input unless a Daylight-
ingDevice:Shelf or DaylightingDevice:Tubular has been specified.
If you do not use the reflections option in the Solar Distribution field in your Building object input,
you are responsible for entering the View Factor to Ground for each heat-transfer surface. Typical
values for a surface that is not shadowed are obtained by the simple equation:
View Factor to Ground = (1-cos(SurfTilt))/2
For example, this gives 0.5 for a wall of tilt 90°. If the tilt of the wall changes, then the View Factor
to Ground must also change.
If you enter autocalculate in this field, EnergyPlus will automatically calculate the view factor to
ground based on the tilt of the surface.
If you do use the reflections option in the Solar Distribution field in your Building object
input, you do not have to enter View Factor to Ground values. In this case the program will
automatically calculate the value to use for each exterior surface taking into account solar shadowing
(including shadowing of the ground by the building) and reflections from obstructions (ref: Building,
Field: Solar Distribution).
However, if you do use the reflections option AND you are modeling a DaylightingDevice:Shelf or
DaylightingDevice:Tubular, then you still need to enter some values of View Factor to Ground. For
DaylightingDevice:Shelf you need to enter View Factor to Ground for the window associated with
the shelf. And for DaylightingDevice:Tubular you need to enter the View Factor to Ground for the
FenestrationSurface:Detailed corresponding to the dome of the tubular device.
Note 1: The corresponding view factor to the sky for diffuse solar radiation is not a user input; it
is calculated within EnergyPlus based on surface orientation, sky solar radiance distribution, and
shadowing surfaces.
Note 2: The view factors to the sky and ground for thermal infrared (long-wave) radiation are not
user inputs; they are calculated within EnergyPlus based on surface tilt and shadowing surfaces.
Shadowing surfaces are considered to have the same emissivity and temperature as the ground, so
they are lumped together with the ground in calculating the ground IR view factor.
1.10.37 Floor:Detailed
The Floor:Detailed object is used to describe floors.
1.10.37.1 Inputs
1. Surface – if this surface is an internal surface, then this is the choice. The value will either be a
surface in the base zone or a surface in another zone. The heat balance between two zones can
be accurately simulated by specifying a surface in an adjacent zone. EnergyPlus will simulate
a group of zones simultaneously and will include the heat transfer between zones. However, as
this increases the complexity of the calculations, it is not necessary to specify the other zone
unless the two zones will have a significant temperature difference. If the two zones will not be
very different (temperature wise), then the surface should use itself as the outside environment
or specify this field as Adiabatic. The surface name on the “outside” of this surface (adjacent
to) is placed in the next field.
2. Adiabatic – an internal surface in the same Zone. This surface will not transfer heat out of the
zone, but will still store heat in thermal mass. Only the inside face of the surface will exchange
heat with the zone (i.e. two adiabatic surfaces are required to model internal partitions where
both sides of the surface are exchanging heat with the zone). The Outside Boundary Condition
Object can be left blank.
3. Zone – this is similar to Surface but EnergyPlus will automatically create the required surface
in the adjacent zone when this is entered for the surface. If there are windows or doors on the
surface, EnergyPlus automatically creates appropriate sub-surfaces as well.
4. Outdoors – if this surface is exposed to outside temperature conditions, then this is the choice.
See Sun Exposure and Wind Exposure below for further specifications on this kind of surface.
5. Foundation - uses an alternative model (currently only the KivaTM model) to account for
the multi-dimensional heat transfer of foundation surfaces. The Outside Boundary Condition
Object will refer to the name of a Foundation:Kiva object (or be left blank to use the default
foundation without extra insulation).
6. Ground - The temperature on the outside of this surface will be the Site:GroundTemperature:Surface
value for the month..
7. GroundFCfactorMethod – if this surface is exposed to the ground and using the Construc-
tion:CfactorUndergroundWall, then this is the choice. The temperature on the outside of
this surface will be the Site:GroundTemperature:FcfactorMethod value for the month.
8. OtherSideCoefficients – if this surface has a custom, user specified temperature or other
parameters (See SurfaceProperty:OtherSideCoefficients specification), then this is the choice.
The outside boundary condition will be the name of the SurfaceProperty:OtherSideCoefficients
specification.
312 CHAPTER 1. INPUT-OUTPUT REFERENCE
Note: Zones with interzone heat transfer are not adiabatic and the internal surfaces contribute
to gains or losses. Adiabatic surfaces are modeled by specifying the base surface itself in this
field. Also, for interzone heat transfer, both surfaces must be represented – for example, if you
want interzone heat transfer to an attic space, the ceiling in the lower zone must have a surface
object with the outside face environment as the floor in the attic and, likewise, there must be a
floor surface object in the attic that references the ceiling surface name in the lower zone.
Equally, if the Outside Boundary Condition is “OtherSideCoefficients”, then this field’s value
must be the SurfaceProperty:OtherSideCoefficients name. Or if the Outside Boundary
Condition is “OtherSideConditionsModel” then this field’s value must be the SurfaceProp-
erty:OtherSideConditionsModel name.
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 313
Note: When a surface is specified with “NoWind”, this has several implications. Within the heat
balance code, this surface will default to using the simple ASHRAE exterior convection coefficient
correlation with a zero wind speed. In addition, since the ASHRAE simple method does not
have a separate value for equivalent long wavelength radiation to the sky and ground, using
“NoWind” also eliminates long wavelength radiant exchange from the exterior of the surface to
both the sky and the ground. Thus, only simple convection takes place at the exterior face of a
surface specified with “NoWind”.
the shelf. And for DaylightingDevice:Tubular you need to enter the View Factor to Ground for the
FenestrationSurface:Detailed corresponding to the dome of the tubular device.
Note 1: The corresponding view factor to the sky for diffuse solar radiation is not a user input; it
is calculated within EnergyPlus based on surface orientation, sky solar radiance distribution, and
shadowing surfaces.
Note 2: The view factors to the sky and ground for thermal infrared (long-wave) radiation are not
user inputs; they are calculated within EnergyPlus based on surface tilt and shadowing surfaces.
Shadowing surfaces are considered to have the same emissivity and temperature as the ground, so
they are lumped together with the ground in calculating the ground IR view factor.
Floor:Detailed ,
Floor_NorthZone_1stFloor ,!- Name
FLOOR -SLAB -ASSEMBLY , !- Construction Name
NorthZone_1stFloor , !- Zone Name
Ground , !- Outside Boundary Condition
, !- Outside Boundary Condition Object
NoSun , !- Sun Exposure
NoWind , !- Wind Exposure
0.0, !- View Factor to Ground
4, !- Number of Vertices
0, 11, 0, !- X,Y,Z 1 {m}
25, 11, 0, !- X,Y,Z 2 {m}
25, 5.5, 0, !- X,Y,Z 3 {m}
0, 5.5, 0; !- X,Y,Z 4 {m}
RoofCeiling:Detailed ,
Ceiling_SouthZone_1stFloor , !- Name
CEILING -FLOOR -ASSEMBLY , !- Construction Name
SouthZone_1stFloor , !- Zone Name
Surface , !- Outside Boundary Condition
Floor_SouthZone_2ndFloor ,!- Outside Boundary Condition Object
NoSun , !- Sun Exposure
NoWind , !- Wind Exposure
0.0, !- View Factor to Ground
4, !- Number of Vertices
0, 0, 3.4, !- X,Y,Z 1 {m}
25, 0, 3.4, !- X,Y,Z 2 {m}
25, 5.5, 3.4, !- X,Y,Z 3 {m}
0, 5.5, 3.4; !- X,Y,Z 4 {m}
Wall:Detailed ,
InteriorWall_SouthZone_1stFloor , !- Name
INTERIOR -WALL -ASSEMBLY , !- Construction Name
SouthZone_1stFloor , !- Zone Name
Surface , !- Outside Boundary Condition
InteriorWall_NorthZone_1stFloor , !- Outside Boundary Condition Object
NoSun , !- Sun Exposure
NoWind , !- Wind Exposure
0, !- View Factor to Ground
4, !- Number of Vertices
25, 5.5, 3.7, !- X,Y,Z 1 {m}
25, 5.5, 0, !- X,Y,Z 2 {m}
0, 5.5, 0, !- X,Y,Z 3 {m}
0, 5.5, 3.7; !- X,Y,Z 4 {m}
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 315
1.10.38 BuildingSurface:Detailed
The BuildingSurface:Detailed object can more generally describe each of the surfaces.
1.10.38.1 Inputs
1. Surface – if this surface is an internal surface, then this is the choice. The value will either be a
surface in the base zone or a surface in another zone. The heat balance between two zones can
be accurately simulated by specifying a surface in an adjacent zone. EnergyPlus will simulate
a group of zones simultaneously and will include the heat transfer between zones. However, as
this increases the complexity of the calculations, it is not necessary to specify the other zone
unless the two zones will have a significant temperature difference. If the two zones will not be
very different (temperature wise), then the surface should use itself as the outside environment
or specify this field as Adiabatic. The surface name on the “outside” of this surface (adjacent
to) is placed in the next field.
316 CHAPTER 1. INPUT-OUTPUT REFERENCE
2. Adiabatic – an internal surface in the same Zone. This surface will not transfer heat out of the
zone, but will still store heat in thermal mass. Only the inside face of the surface will exchange
heat with the zone (i.e. two adiabatic surfaces are required to model internal partitions where
both sides of the surface are exchanging heat with the zone). The Outside Boundary Condition
Object can be left blank.
3. Zone – this is similar to Surface but EnergyPlus will automatically create the required surface
in the adjacent zone when this is entered for the surface. If there are windows or doors on the
surface, EnergyPlus automatically creates appropriate sub-surfaces as well.
4. Outdoors – if this surface is exposed to outside temperature conditions, then this is the choice.
See Sun Exposure and Wind Exposure below for further specifications on this kind of surface.
5. Foundation - uses an alternative model (currently only the KivaTM model) to account for
the multi-dimensional heat transfer of foundation surfaces. The Outside Boundary Condition
Object will refer to the name of a Foundation:Kiva object (or be left blank to use the default
foundation without extra insulation).
6. Ground - The temperature on the outside of this surface will be the Site:GroundTemperature:Surface
value for the month.
7. GroundFCfactorMethod – if this surface is exposed to the ground and using the Construc-
tion:CfactorUndergroundWall, then this is the choice. The temperature on the outside of
this surface will be the Site:GroundTemperature:FcfactorMethod value for the month.
8. OtherSideCoefficients – if this surface has a custom, user specified temperature or other
parameters (See SurfaceProperty:OtherSideCoefficients specification), then this is the choice.
The outside boundary condition will be the name of the SurfaceProperty:OtherSideCoefficients
specification.
9. OtherSideConditionsModel – if this surface has a specially-modeled multi-skin component,
such as a transpired collector or vented photovoltaic panel, attached to the outside (See Sur-
faceProperty:OtherSideConditionsModel specification), then this the choice. The outside face
environment will be the name of the SurfaceProperty:OtherSideConditionsModel specification.
10. GroundSlabPreprocessorAverage – uses the average results from the Slab preprocessor
calculations.
11. GroundSlabPreprocessorCore – uses the core results from the Slab preprocessor calcula-
tions.
12. GroundSlabPreprocessorPerimeter – uses the perimeter results from the Slab preprocessor
calculations.
13. GroundBasementPreprocessorAverageWall – uses the average wall results from the Base-
ment preprocessor calculations.
14. GroundBasementPreprocessorAverageFloor – uses the average floor results from the
Basement preprocessor calculations.
15. GroundBasementPreprocessorUpperWall – uses the upper wall results from the Base-
ment preprocessor calculations.
16. GroundBasementPreprocessorLowerWall – uses the lower wall results from the Basement
preprocessor calculations.
Note: Zones with interzone heat transfer are not adiabatic and the internal surfaces contribute
to gains or losses. Adiabatic surfaces are modeled by specifying the base surface itself in this
field. Also, for interzone heat transfer, both surfaces must be represented – for example, if you
want interzone heat transfer to an attic space, the ceiling in the lower zone must have a surface
object with the outside face environment as the floor in the attic and, likewise, there must be a
floor surface object in the attic that references the ceiling surface name in the lower zone.
Equally, if the Outside Boundary Condition is “OtherSideCoefficients”, then this field’s value
must be the SurfaceProperty:OtherSideCoefficients name. Or if the Outside Boundary
Condition is “OtherSideConditionsModel” then this field’s value must be the SurfaceProp-
erty:OtherSideConditionsModel name.
Note: When a surface is specified with “NoWind”, this has several implications. Within the heat
balance code, this surface will default to using the simple ASHRAE exterior convection coefficient
correlation with a zero wind speed. In addition, since the ASHRAE simple method does not
have a separate value for equivalent long wavelength radiation to the sky and ground, using
“NoWind” also eliminates long wavelength radiant exchange from the exterior of the surface to
both the sky and the ground. Thus, only simple convection takes place at the exterior face of a
surface specified with “NoWind”.
For example, if there are no obstructions, a vertical surface sees half of the ground plane and so
View Factor to Ground = 0.5. A horizontal downward-facing surface sees the entire ground plane,
so View Factor to Ground = 1.0. A horizontal upward-facing surface (horizontal roof) does not see
the ground at all, so View Factor to Ground = 0.0.
Unused if reflections option in Solar Distribution field in Building object input unless a Daylight-
ingDevice:Shelf or DaylightingDevice:Tubular has been specified.
If you do not use the reflections option in the Solar Distribution field in your Building object input,
you are responsible for entering the View Factor to Ground for each heat-transfer surface. Typical
values for a surface that is not shadowed are obtained by the simple equation:
View Factor to Ground = (1-cos(SurfTilt))/2
For example, this gives 0.5 for a wall of tilt 90°. If the tilt of the wall changes, then the View Factor
to Ground must also change.
If you enter autocalculate in this field, EnergyPlus will automatically calculate the view factor to
ground based on the tilt of the surface.
If you do use the reflections option in the Solar Distribution field in your Building object
input, you do not have to enter View Factor to Ground values. In this case the program will
automatically calculate the value to use for each exterior surface taking into account solar shadowing
(including shadowing of the ground by the building) and reflections from obstructions (ref: Building,
Field: Solar Distribution).
However, if you do use the reflections option AND you are modeling a DaylightingDevice:Shelf or
DaylightingDevice:Tubular, then you still need to enter some values of View Factor to Ground. For
DaylightingDevice:Shelf you need to enter View Factor to Ground for the window associated with
the shelf. And for DaylightingDevice:Tubular you need to enter the View Factor to Ground for the
FenestrationSurface:Detailed corresponding to the dome of the tubular device.
Note 1: The corresponding view factor to the sky for diffuse solar radiation is not a user input; it
is calculated within EnergyPlus based on surface orientation, sky solar radiance distribution, and
shadowing surfaces.
Note 2: The view factors to the sky and ground for thermal infrared (long-wave) radiation are not
user inputs; they are calculated within EnergyPlus based on surface tilt and shadowing surfaces.
Shadowing surfaces are considered to have the same emissivity and temperature as the ground, so
they are lumped together with the ground in calculating the ground IR view factor.
1.10.39 FenestrationSurface:Detailed
This surface class is used for subsurfaces, which can be of five different types: Windows, Doors,
GlassDoors, TubularDaylightDomes, and TubularDaylightDiffusers. A subsurface (such as a win-
dow) of a base surface (such as a wall) inherits several of the properties (such as Outside Boundary
Condition, Sun Exposure, etc.) of the base surface. Windows, GlassDoors, TubularDaylightDomes,
and TubularDaylightDiffusers are considered to have one or more glass layers and so transmit solar
radiation. Doors are considered to be opaque. For Surface Type = Window and GlassDoor, shades
and screens may be applied by referencing this subsurface in a window shading control (ref: Window-
ShadingControl object). To assign a shade to a window or glass door, see WindowMaterial: Shade.
To assign a screen, see WindowMaterial:Screen. To assign a blind, see WindowMaterial:Blind. To
assign switchable glazing, such as electrochromic glazing, see WindowShadingControl.
The surface can be of 3 sides or 4 sides. A 4-sided but non-rectangular fenestration surface is allowed
and will be transferred to an equivalent rectangular surface with the same area and aspect ratio for
the convection calculations at window air gaps.
1.10.39.1 Inputs
in the calculation of conduction heat transfer, solar gain, daylighting, etc. A Window or GlassDoor,
but not a Door, can have a movable interior, exterior or between-glass shading device, such as blinds
(ref: WindowMaterial:Blind object), and can have a frame and/or a divider (ref: WindowProp-
erty:FrameAndDivider object). TubularDaylightDomes and TubularDaylightDomes are specialized
subsurfaces for use with the DaylightingDevice:Tubular object to simulate Tubular Daylighting De-
vices (TDDs). TubularDaylightDomes and TubularDaylightDomes cannot have shades, screens or
blinds. In the following, the term “window” applies to Window, GlassDoor, TubularDaylightDome,
and TubularDaylightDome, if not otherwise explicitly mentioned.
As noted in the description of the BuildingSurface:Detailed, Azimuth (facing angle) and Tilt are
calculated from the entered vertices. Tilts of subsurfaces will normally be the same as their base
surface. If these are significantly beyond the “normals” for the base surface, warning messages may
be issued. If the facing angles are not correct, you may have a window pointing “into” the zone
rather than out of it – this would cause problems in the calculations. Note, too, that a “reveal”
(inset or outset) may occur if the plane of the subsurface is not coincident with the base surface; the
reveal has an effect on shading of the subsurface.
FenestrationSurface :Detailed ,
Zn001:Wall001:Win001 , !- SubSurface Name
Window ,SINGLE PANE HW WINDOW , !- Class and Construction Name
Zn001:Wall001 ,, !- Base Surface Name and Target (if applicable)
0.5000000 , !- VF to Ground
WINDOW -CONTROL -DRAPES , !- Window Shading Control
TestFrameAndDivider , !- Frame/Divider name
5, !- Multiplier
4, !- Rectangle (number of sides)
1.524000 , 0.1520000 , 2.743000 ,
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 323
1.10.41 InternalMass
Any surface that would logically be described as an interior wall, floor or ceiling can just as easily be
described as Internal Mass. Internal Mass surface types only exchange energy with the zone in which
they are described; they do not see any other zones. There are two approaches to using internal
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 325
mass. The first approach is to have several pieces of internal mass with each piece having a different
construction type. The other approach is to choose an average construction type and combine all of
the interior surfaces into a single internal mass. Similar to internal surfaces with an adiabatic bound-
ary condition, the zone will only exchange energy with the inside of the Internal Mass construction.
If both sides of the surface exchange energy with the zone then the user should input twice the area
when defining the Internal Mass object. Note that furniture and other large objects within a zone
can be described using internal mass. However, simplifying calculations using internal mass must be
used with caution when the “FullInteriorAndExterior” or “FullInteriorAndExteriorWithReflections”
Solar Distribution model (see Building parameters) is chosen. A single Internal Mass object can be
applied to a set of zones. This requires specifying a zone list name instead of a zone name in the
input field Zone or ZoneList Name.
1.10.41.1 Inputs
Example
When zoning an office building, five west-facing offices have been combined into one zone. All of the
offices have interior walls made of the same materials. As shown in the figure below, this zone may
be described with 5 exterior walls and 11 internal walls or 1 exterior wall and 1 internal mass. Note
that fewer surfaces will speed up the EnergyPlus calculations.
Example
A five-story building has the same ceiling/floor construction separating each of the levels. Zones that
are on floors 2 through 4 may be described using a single piece of internal mass to represent both
326 CHAPTER 1. INPUT-OUTPUT REFERENCE
the floor and ceiling. The construction for this internal mass would be identical to the ceiling/floor
construction that would be used to describe separate surfaces and the area of the internal mass
surface would be the total surface area of the combined ceilings/floors (i.e. twice the total floor
area).
InternalMass ,
Zn002:IntM002 , !- Surface Name
PARTITION02 , !- Construction Name
DORM ROOMS AND COMMON AREAS , !- Zone or ZoneList Name
371.6122; !- Total area exposed to Zone {m2}
Zone ,Average ,Surface Outside Face Incident Sky Diffuse Surface Reflected Solar Radiation Rate per
Area[W/m2]
Zone ,Average ,Surface Outside Face Incident Beam To Beam Surface Reflected Solar Radiation Rate per
Area[W/m2]
Zone ,Average ,Surface Outside Face Incident Beam To Diffuse Surface Reflected Solar Radiation Rate
per Area[W/m2]
Zone ,Average ,Surface Outside Face Beam Solar Incident Angle Cosine Value []
Zone ,Average ,Surface Anisotropic Sky Multiplier []
Zone ,Average ,Surface Window BSDF Beam Direction Number []
Zone ,Average ,Surface Window BSDF Beam Theta Angle [rad]
Zone ,Average ,Surface Window BSDF Beam Phi Angle [rad]
Zone ,Average ,Surface Outside Face Thermal Radiation to Air Heat Transfer Rate [W]
Zone ,Average ,Surface Outside Face Heat Emission to Air Rate [W]
Output variables applicable to opaque heat transfer surfaces (FLOOR, WALL, ROOF, DOOR).
Note – these are advanced variables – you must read the descriptions and understand
before use – then you must use the Diagnostics object to allow reporting.
Zone ,Average ,Surface Inside Face Solar Radiation Heat Gain Rate [W]
Zone ,Average ,Surface Inside Face Solar Radiation Heat Gain Rate per Area [W/m2]
Zone ,Sum ,Surface Inside Face Solar Radiation Heat Gain Energy [J]
Zone ,Average ,Surface Inside Face Lights Radiation Heat Gain Rate [W]
Zone ,Average ,Surface Inside Face Lights Radiation Heat Gain Rate per Area [W/m2]
Zone ,Sum ,Surface Inside Face Lights Radiation Heat Gain Energy [J]
Zone ,Average ,Surface Inside Face Conduction Heat Transfer Rate [W]
Zone ,Average ,Surface Inside Face Conduction Heat Gain Rate [W]
Zone ,Average ,Surface Inside Face Conduction Heat Loss Rate [W]
Zone ,Average ,Surface Inside Face Conduction Heat Transfer Rate per Area [W/m2]
Zone ,Sum ,Surface Inside Face Conduction Heat Transfer Energy [J]
Zone ,Average ,Surface Outside Face Conduction Heat Transfer Rate [W]
Zone ,Average ,Surface Outside Face Conduction Heat Gain Rate [W]
Zone ,Average ,Surface Outside Face Conduction Heat Loss Rate [W]
Zone ,Average ,Surface Outside Face Conduction Heat Transfer Rate per Area [W/m2]
Zone ,Sum ,Surface Outside Face Conduction Heat Transfer Energy [J]
Zone ,Average ,Surface Average Face Conduction Heat Transfer Rate [W]
Zone ,Average ,Surface Average Face Conduction Heat Gain Rate [W]
Zone ,Average ,Surface Average Face Conduction Heat Loss Rate [W]
Zone ,Average ,Surface Average Face Conduction Heat Transfer Rate per Area [W/m2]
Zone ,Sum ,Surface Average Face Conduction Heat Transfer Energy [J]
Zone ,Average ,Surface Heat Storage Rate [W]
Zone ,Average ,Surface Heat Storage Gain Rate [W]
Zone ,Average ,Surface Heat Storage Loss Rate [W]
Zone ,Average ,Surface Heat Storage Rate per Area [W/m2]
Zone ,Sum ,Surface Heat Storage Energy [J]
Zone ,Average ,Zone Opaque Surface Inside Face Conduction [W]
Zone ,Average ,Zone Opaque Surface Inside Faces Total Conduction Heat Gain Rate [W]
Zone ,Average ,Zone Opaque Surface Inside Faces Total Conduction Heat Loss Rate [W]
Zone ,Sum ,Zone Opaque Surface Inside Faces Total Conduction Heat Gain Energy [J]
Zone ,Sum ,Zone Opaque Surface Inside Faces Total Conduction Heat Loss Energy [J]
Zone ,Average ,Zone Opaque Surface Outside Face Conduction [W]
Zone ,Average ,Zone Opaque Surface Outside Face Conduction Gain[W]
Zone ,Average ,Zone Opaque Surface Outside Face Conduction Loss[W]
Zone ,Average , Surface Inside Face Beam Solar Radiation Heat Gain Rate [W]
Zone ,Sum ,Zone Exterior Windows Total Transmitted Beam Solar Radiation Energy [J]
Zone ,Average ,Zone Interior Windows Total Transmitted Beam Solar Radiation Rate [W]
Zone ,Sum ,Zone Interior Windows Total Transmitted Beam Solar Radiation Energy [J]
Zone ,Average ,Zone Exterior Windows Total Transmitted Diffuse Solar Radiation Rate [W]
Zone ,Sum ,Zone Exterior Windows Total Transmitted Diffuse Solar Radiation Energy [J]
Zone ,Average ,Zone Interior Windows Total Transmitted Diffuse Solar Radiation Rate [W]
Zone ,Average ,Surface Window Total Glazing Layers Absorbed Solar Radiation Rate [W]
Zone ,Average ,Surface Window Total Glazing Layers Absorbed Shortwave Radiation Rate [W]
Zone ,Sum ,Surface Window Total Glazing Layers Absorbed Solar Radiation Energy [J]
Zone ,Average ,Surface Window Shading Device Absorbed Solar Radiation Rate [W]
Zone ,Sum ,Surface Window Shading Device Absorbed Solar Radiation Energy [J]
Zone ,Average , Surface Window Transmitted Solar Radiation Rate [W]
Zone ,Sum ,Surface Window Transmitted Solar Radiation Energy [J]
Zone ,Average ,Surface Window Transmitted Beam Solar Radiation Rate [W]
Zone ,Average ,Surface Window Transmitted Beam To Beam Solar Radiation Rate [W]
Zone ,Average ,Surface Window Transmitted Beam To Diffuse Solar Radiation Rate [W]
Zone ,Sum ,Surface Window Transmitted Beam Solar Radiation Energy [J]
Zone ,Sum ,Surface Window Transmitted Beam To Beam Solar Radiation Energy [J]
Zone ,Sum ,Surface Window Transmitted Beam To Diffuse Solar Radiation Energy [J]
Zone ,Average ,Surface Window Transmitted Diffuse Solar Radiation Rate [W]
Zone ,Sum ,Surface Window Transmitted Diffuse Solar Radiation Energy [J]
Zone ,Average ,Surface Window System Solar Transmittance []
Zone ,Average ,Surface Window System Solar Absorptance []
Zone ,Average ,Surface Window System Solar Reflectance []
Zone ,Average ,Surface Window Gap Convective Heat Transfer Rate [W]
Zone ,Sum ,Surface Window Gap Convective Heat Transfer Energy [J]
Zone ,Average ,Surface Window Heat Gain Rate [W]
Zone ,Sum ,Surface Window Heat Gain Energy [J]
Zone ,Average ,Surface Window Heat Loss Rate [W]
Zone ,Sum ,Surface Window Heat Loss Energy [J]
Zone ,Average ,Surface Window Net Heat Transfer Rate [W]
Zone ,Sum ,Surface Window Net Heat Transfer Energy [J]
Zone ,Average ,Surface Window Glazing Beam to Beam Solar Transmittance []
Zone ,Average ,Surface Window Glazing Beam to Diffuse Solar Transmittance []
Zone ,Average ,Surface Window Glazing Diffuse to Diffuse Solar Transmittance []
Zone ,Average ,Surface Window Model Solver Iteration Count []
Zone ,Average ,Surface Window Solar Horizontal Profile Angle[deg]
Zone ,Average ,Surface Window Solar Vertical Profile Angle[deg]
Zone ,Average ,Surface Window Outside Reveal Reflected Beam Solar Radiation Rate [W]
Zone ,Sum ,Surface Window Outside Reveal Reflected Beam Solar Radiation Energy
Zone ,Average ,Surface Window Inside Reveal Reflected Beam Solar Radiation Rate [W]
Zone ,Sum ,Surface Window Inside Reveal Reflected Beam Solar Radiation Energy [J]
Zone ,Average ,Surface Window Inside Reveal Absorbed Beam Solar Radiation Rate [W]
Zone ,Average ,Surface Window Inside Face Glazing Condensation Status []
Zone ,Average ,Surface Window Inside Face Frame Condensation Status []
Zone ,Average ,Surface Window Inside Face Divider Condensation Status []
Zone ,Average ,Surface Shading Device Is On Time Fraction []
Zone ,Average ,Surface Window Blind Slat Angle [deg]
Zone ,Average ,Surface Window Blind Beam to Beam Solar Transmittance []
Zone ,Average ,Surface Window Blind Beam to Diffuse Solar Transmittance []
Zone ,Average ,Surface Window Blind Diffuse to Diffuse Solar Transmittance []
Zone ,Average ,Surface Window Blind and Glazing System Beam Solar Transmittance []
Zone ,Average ,Surface Window Blind and Glazing System Diffuse Solar Transmittance []
Zone ,Average ,Surface Window Screen Beam to Beam Solar Transmittance []
Zone ,Average ,Surface Window Screen Beam to Diffuse Solar Transmittance []
Zone ,Average ,Surface Window Screen Diffuse to Diffuse Solar Transmittance []
Zone ,Average ,Surface Window Screen and Glazing System Beam Solar Transmittance []
Zone ,Average ,Surface Window Screen and Glazing System Diffuse Solar Transmittance []
Zone ,State ,Surface Storm Window On Off Status []
Zone ,Average ,Surface Window Inside Face Frame and Divider Zone Heat Gain Rate [W]
Zone ,Average ,Surface Window Frame Heat Gain Rate [W]
Zone ,Average ,Surface Window Frame Heat Loss Rate [W]
Zone ,Average ,Surface Window Divider Heat Gain Rate [W]
Zone ,Average ,Surface Window Divider Heat Loss Rate [W]
Zone ,Average ,Surface Window Frame Inside Temperature [C]
Zone ,Average ,Surface Window Frame Outside Temperature [C]
Zone ,Average ,Surface Window Divider Inside Temperature [C]
Zone ,Average ,Surface Window Divider Outside Temperature [C]
330 CHAPTER 1. INPUT-OUTPUT REFERENCE
If the user requests to display advanced report/output variables (e.g. see Output:Diagnostics keyword
DisplayAdvancedReportVariables) the the following additional output variables are available for
exterior windows and glass doors
Zone ,Average ,Surface Window Inside Face Glazing Zone Convection Heat Gain Rate [W]
Zone ,Average ,Surface Window Inside Face Glazing Net Infrared Heat Transfer Rate [W]
Zone ,Average ,Surface Window Shortwave from Zone Back Out Window Heat Transfer Rate [W]
Zone ,Average ,Surface Window Inside Face Frame and Divider Zone Heat Gain Rate [W]
Zone ,Average ,Surface Window Inside Face Gap between Shade and Glazing Zone Convection Heat Gain
Rate [W]
Zone ,Average ,Surface Window Inside Face Shade Zone Convection Heat Gain Rate [W]
Zone ,Average ,Surface Window Inside Face Shade Net Infrared Heat Transfer Rate [W]
If the user requests to display advanced report/output variables (e.g. see Output:Diagnostics key-
word DisplayAdvancedReportVariables) the the following additional output variable is available for
Equivalent Layer Window;
Zone ,Average , Surface Window Inside Face Other Convection Heat Gain Rate [W]
Output variables applicable to interior and exterior windows and doors under certain conditions (see
next three subsections for more information) are:
Zone ,Average ,Surface Window Total Absorbed Shortwave Radiation Rate Layer <x> [W]
Zone ,Average ,Surface Window Front Face Temperature Layer <x> [C]
Zone ,Average ,Surface Window Back Face Temperature Layer <x> [C]
1.10.43.1 Surface Window Total Absorbed Shortwave Radiation Rate Layer <x>
[W]
This will output shortwave radiation absorbed in a window layer. The key values for this output
variable are the surface name. Layers are numbered from the outside to the inside of the surface.
The full listing will appear in the RDD file. Note that this variable is only defined for constructions
defined by a Construction:ComplexFenestrationState.
This will output a temperature for the front face of the layer. The layer front face is considered to be
the face closest to the outside environment. The full listing will appear in the RDD file. Note that
this variable is only defined for constructions defined by a Construction:ComplexFenestrationState.
For other window constructions, this variable is also defined for the outer layer (Layer 1) only. The
value will be identical to the Surface Outside Face Temperature.
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 331
This will output a temperature for the back face of the layer. The layer back face is considered to
be the face closest to the inside environment. The full listing will appear in the RDD file. Note that
this variable is only defined for constructions defined by a Construction:ComplexFenestrationState.
For other window constructions, this variable is also defined for the inner layer only. The value will
be identical to the Surface Inside Face Temperature.
This output is the number of iterations used in a part of the solution for surface heat transfer that
accounts for thermal radiation heat transfer between zone surfaces. This is simply a counter on the
iteration loop for inside face surface modeling. There is only one instance of this output in a given
run and the Key Value is “Simulation.”
This is the temperature of the surface’s inside face, in degrees Celsius. Former Name: Prior to
version 7.1 this output was called Surface Inside Temperature.
This is the temperature of movable insulation installed on the inside of the construction at the
movable insulation’s inside face (the one facing the zone), in degrees Celsius. This variable is only
valid when the surface has movable insulation and the movable insulation is actually scheduled to
be present. For surfaces that have no movable insulation or the movable insulation is not scheduled
to be present, the value of this variable is set to the Surface Inside Face Temperature. It should be
noted that users can limit how often this output variable is generating by using a schedule to control
when this output is produced. For example, this user could add the following syntax to an input file
that includes movable insulation:
Output:Variable ,Zone1:WestWall ,Surface Inside Face Interior Movable Insulation Temperature ,
timestep , MovableInsulationSchedule ;
In this example, interior movable insulation is used on the west wall of zone 1 and is only present
when the schedule (MovableInsulationSchedule) is greater than zero. Adding this output variable
syntax to the input file reports the temperature at the inside face of the interior movable insulation
only when the movable insulation is present. The use of the movable insulation schedule in the
output variable designation limits when this value shows up in the EnergyPlus output file to when
it is actually scheduled to be present. At other times, no value will be reported. The limiting of
332 CHAPTER 1. INPUT-OUTPUT REFERENCE
when the output is generated allows the user to generate useful statistics instead of having those
statistics influenced by values for when the movable insulation is not present. If the user does not
use the output variable schedule feature, the output for this variable will equal the surface inside
face temperature when the movable insulation is not present.
This is the temperature of the surface’s outside face, in degrees Celsius. Former Name: Prior to
version 7.1, this output was called Surface Outside Temperature.
This is the effective bulk air temperature used for modeling the inside surface convection heat
transfer. This is the same as the zone mean air temperature when using the mixing model for
roomair. However, if more advanced roomair models are used, this variable will report the air
temperature predicted by the roomair model as it was used in the surface heat balance model
calculations. Former Name: Prior to version 7.1, this output was called Surface Int Adjacent Air
Temperature.
1.10.44.7 Surface Inside Face Convection Heat Gain Rate per Area [W/m2]
These “inside face convection heat gain” output variables describe the heat transferred by convection
between the inside face and the zone air. The values can be positive or negative with positive
indicating heat is being added to the surface’s face by convection. Different versions of the report
are available including the basic heat gain rate (W), and a per unit area flux (W/m2), and an energy
version (J).
Former Name: Prior to version 7.1, these outputs were called “Surface Int Convection Heat *” and
had used the opposite sign convention.
This is the coefficient that describes the convection heat transfer. It is the value of “Hc” in the
classic convection model Q = Hc* A* (T – T). This is the result of the surface convection algorithm
used for the inside face. Former Name: Prior to version 7.1, this output was called “Surface Int
Convection Coeff.”
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 333
1.10.44.10 Surface Inside Face Net Surface Thermal Radiation Heat Gain Rate
[W]
1.10.44.11 Surface Inside Face Net Surface Thermal Radiation Heat Gain Rate
per Area [W/m2]
1.10.44.12 Surface Inside Face Net Surface Thermal Radiation Heat Gain Energy
[J]
These “inside face net surface thermal radiation heat gain” output variables describe the heat trans-
ferred by longwave infrared thermal radiation exchanges between the inside faces of other surfaces
in the zone. The values can be positive or negative with positive indicating heat is being added to
the surface’s face by thermal radiation. Different versions of the report are available including the
basic heat gain rate (W), and a per unit area flux (W/m2), and an energy version (J).
1.10.44.13 Surface Inside Face Solar Radiation Heat Gain Rate [W]
1.10.44.14 Surface Inside Face Solar Radiation Heat Gain Rate per Area [W/m2]
1.10.44.15 Surface Inside Face Solar Radiation Heat Gain Energy [J]
These “inside face solar radiation heat gain” output variables describe the heat transferred by solar
radiation onto the inside face. The values are always positive and indicate heat is being added to
the surface’s face by solar radiation. This is sunlight that has entered the zone through a window
and been absorbed on the inside face of the surface. Different versions of the report are available
including the basic heat gain rate (W), and a per unit area flux (W/m2), and an energy version (J).
1.10.44.16 Surface Inside Face Lights Radiation Heat Gain Rate [W]
1.10.44.17 Surface Inside Face Lights Radiation Heat Gain Rate per Area
[W/m2]
1.10.44.18 Surface Inside Face Lights Radiation Heat Gain Energy [J]
These “inside face lights radiation heat gain” output variables describe the heat transferred by
shortwave radiation onto the inside face. The values are always positive and indicate heat is being
added to the surface’s face by shortwave radiation that emanated from electric lighting equipment
and was absorbed by the surface. Different versions of the report are available including the basic
heat gain rate (W), and a per unit area flux (W/m2), and an energy version (J).
1.10.44.19 Surface Inside Face Internal Gains Radiation Heat Gain Rate [W]
1.10.44.20 Surface Inside Face Internal Gains Radiation Heat Gain Rate per
Area [W/m2]
1.10.44.21 Surface Inside Face Internal Gains Radiation Heat Gain Energy [J]
These “inside face internal gains radiation heat gain” output variables describe the heat transferred
by longwave infrared thermal radiation onto the inside face that emanated from internal gains such
334 CHAPTER 1. INPUT-OUTPUT REFERENCE
as lights, electric equipment, and people. The values are always positive and indicate heat is being
added to the surface’s face by the absorption of longwave thermal radiation. Different versions of
the report are available including the basic heat gain rate (W), and a per unit area flux (W/m2),
and an energy version (J).
1.10.44.22 Surface Inside Face System Radiation Heat Gain Rate [W]
1.10.44.23 Surface Inside Face System Radiation Heat Gain Rate per Area
[W/m2]
1.10.44.24 Surface Inside Face System Radiation Heat Gain Energy [J]
These “inside face system radiation heat gain” output variables describe the heat transferred by in-
frared thermal radiation onto the inside face that emanated from HVAC equipment such as baseboard
heaters or high-temperature radiant heating panels. The values are always positive and indicate heat
is being added to the surface’s face by the absorption of thermal radiation. Different versions of the
report are available including the basic heat gain rate (W), and a per unit area flux (W/m2), and
an energy version (J).
1.10.44.26 Surface Outside Face Convection Heat Gain Rate per Area [W/m2]
These “outside face convection” output variables describe heat transferred by convection between
the outside face and the surrounding air. The values can be positive or negative with positive values
indicating heat is added to the surface face by convection heat transfer. Different versions of the
report are available including the basic heat gain rate (W), and a per unit area flux (W/m2 ), and
an energy version (J).
Former Name: Prior to version 7.1, these outputs were called “Surface Ext Convection Heat *” and
used the opposite sign convention.
This is the coefficient that describes the convection heat transfer. It is the value of “Hc” in the
classic convection model Q = Hc* A* (T – T). This is the result of the surface convection algorithm
used for the outside face. Former Name: Prior to Version 7.1, this output was called “Surface Ext
Convection Coeff.”
1.10.44.29 Surface Outside Face Net Thermal Radiation Heat Gain Rate [W]
1.10.44.30 Surface Outside Face Net Thermal Radiation Heat Gain Rate per
Area [W/m2]
1.10.44.31 Surface Outside Face Net Thermal Radiation Heat Gain Energy [J]
These “outside face net thermal radiation” output variables describe the heat transferred by longwave
infrared thermal radiation exchanges between the surface and the surroundings of the outside face.
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 335
This is the net of all forms of longwave thermal infrared radiation heat transfer. The values can be
positive or negative with positive indicating the net addition of heat to the outside face. Different
versions of the report are available including the basic heat gain rate (W), and a per unit area flux
(W/m2), and an energy version (J).
Former Name: Prior to version 7.1, these outputs were called “Surface Ext Thermal Radiation Heat
*” and used the opposite sign convention.
1.10.44.32 Surface Inside Face Exterior Windows Incident Beam Solar Radiation
Rate [W]
1.10.44.33 Surface Inside Face Exterior Windows Incident Beam Solar Radiation
Rate per Area [W/m2]
1.10.44.34 Surface Inside Face Exterior Windows Incident Beam Solar Radiation
Energy [J]
Beam solar radiation from the exterior windows in a zone incident on the inside face of a surface in the
zone. If Solar Distribution in the BUILDING object is equal to MinimalShadowing or FullExterior,
it is assumed that all beam solar from exterior windows falls on the floor. In this case the value
of this output variable can be greater than zero only for floor surfaces. If Solar Distribution equals
FullInteriorExterior the program tracks where beam solar from exterior windows falls inside the zone,
in which case the value of this variable can be greater than zero for floor as well as wall surfaces.
Different versions of the report are available including the basic incident rate (W), a per unit area
flux (W/m2), and an energy version (J).
1.10.44.35 Surface Inside Face Interior Windows Incident Beam Solar Radiation
Rate [W]
1.10.44.36 Surface Inside Face Interior Windows Incident Beam Solar Radiation
Rate per Area [W/m2]
1.10.44.37 Surface Inside Face Interior Windows Incident Beam Solar Radiation
Energy [J]
Beam solar radiation from the interior (i.e., interzone) windows in a zone incident on the inside face
of a surface in the zone. This value is calculated only if Solar Distribution in the BUILDING object
is equal to FullInteriorExterior. However, the program does not track where this radiation falls.
Instead, it is treated by the program as though it were diffuse radiation uniformly distributed over
all of the zone surfaces. See Figure 1.33. Different versions of the report are available including
the basic incident rate (W), a per unit area flux (W/m2), and an energy version (J).
1.10.44.38 Surface Inside Face Initial Transmitted Diffuse Absorbed Solar Radi-
ation Rate [W]
As of Version 2.1, diffuse solar transmitted through exterior and interior windows is no longer
uniformly distributed. Instead, it is distributed according to the approximate view factors between
the transmitting window and all other heat transfer surfaces in the zone. This variable is the
336 CHAPTER 1. INPUT-OUTPUT REFERENCE
Figure 1.33: Beam solar radiation entering a zone through an interior window is distributed inside
the zone as though it were diffuse radiation.
amount of transmitted diffuse solar that is initially absorbed on the inside of each heat transfer
surface. The portion of this diffuse solar that is reflected by all surfaces in the zone is subsequently
redistributed uniformly to all heat transfer surfaces in the zone, along with interior reflected beam
solar and shortwave radiation from lights. The total absorbed shortwave radiation is given by the
next variable.
As of Version 2.1, the previous variable plus absorbed shortwave radiation from uniformly distributed
initially-reflected diffuse solar, reflected beam solar, and shortwave radiation from lights. This sum
is the power of all sources of solar and visible radiation absorbed by the surface at the inside face.
The variable reports an index that points to specific Construction. The variable is an additional
output variable when Output:Diagnostics, DisplayAdvancedReportVariables; is given in an input
file.
In order to find a corresponding construction using the index, following steps are suggested:
1. Find a surface name from Surface Construction Index in the .csv file
2. Search the surface name in lines starting with HeatTransfer Surface in the .eio file
3. The seventh item is the construction name with matched surface name.
The outdoor air dry-bulb temperature calculated at the height above ground of the surface centroid.
Former Name: Prior to version 7.1, this output was called “Surface Ext Outdoor Dry Bulb.”
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 337
The outdoor air wet-bulb temperature calculated at the height above ground of the surface centroid.
Former Name: Prior to version 7.1, this output was called “Surface Ext Outdoor Wet Bulb.”
The outdoor wind speed calculated at the height above ground of the surface centroid. This value
may differ from site wind speed depending on the height of the surface (ref. Site:HeightVariation).
In addition, the value may be different from the site wind speed when using OutdoorAir:Node with
SurfaceProperty:LocalEnvironment or ZoneProperty:LocalEnvironment. It can also be modified
using EMS. Former Name: Prior to version 7.1, this output was called “Surface Ext Wind Speed.”
This output reports the actual wind direction at the outside face of a surface. As with the wind
speed variable above, this value may be different from the site wind direction when using Out-
doorAir:Node with SurfaceProperty:LocalEnvironment or ZoneProperty:LocalEnvironment. It can
also be modified using EMS.
The outside area of an exterior surface that is illuminated by (unreflected) beam solar radiation.
The fraction of the outside area of an exterior surface that is illuminated by (unreflected) beam solar
radiation. Equals Surface Outside Face Sunlit Area divided by total surface area.
1.10.45.7 Surface Outside Face Thermal Radiation to Air Heat Transfer Coeffi-
cient [W/m2-K]
This is the coefficient that describes thermal radiation heat transfer between the outside face and the
air mass surrounding the surface. It is the value of “Hr” in the classic linearized model for thermal
radiation Q = Hr * A * (T_surf – T_surfodb) when applied to the ambient air. Where T_surf =
Surface Outside Face Temperature, and T_surfodb = Surface Outside Face Outdoor Air Drybulb
Temperature. Former Name: Prior to version 7.1, this output was called “Surface Ext Rad to Air
Coeff.”
1.10.45.8 Surface Outside Face Thermal Radiation to Sky Heat Transfer Coeffi-
cient [W/m2-K]
This is the coefficient that describes thermal radiation heat transfer between the outside face and
the sky surrounding the surface. It is the value of “Hr” in the classic linearized model for thermal
radiation Q = Hr * A * (T_surf – T_sky) when applied to the sky. Where T_surf = Surface Outside
Face Temperature, and T_sky = Site Sky Temperature. Former Name: Prior to version 7.1, this
output was called “Surface Ext Rad to Sky Coeff.”
338 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.10.45.9 Surface Outside Face Thermal Radiation to Ground Heat Transfer Co-
efficient [W/m2-K]
This is the coefficient that describes thermal radiation heat transfer between the outside face and
the ground surrounding the surface. It is the value of “Hr” in the classic linearized model for
thermal radiation Q = Hr * A * (T_surf – T_odb) when applied to the ground. Where T_surf
= Surface Outside Face Temperature, and T_odb = Site Outdoor Air Drybulb Temperature (used
as an approximation for the ground surface temperature). Former Name: Prior to version 7.1, this
output was called “Surface Ext Rad to Ground Coeff.”
1.10.45.10 Surface Outside Face Thermal Radiation to Air Heat Transfer Rate
[W]
This is thermal radiation heat transfer rate between the outside face and the air mass surrounding
the surface.
This is total heat transfer rate between the outside face and the air mass surrounding the surface by
convection and thermal radiation.
1.10.45.12 Surface Outside Face Solar Radiation Heat Gain Rate [W]
1.10.45.13 Surface Outside Face Solar Radiation Heat Gain Rate per Area
[W/m2]
1.10.45.14 Surface Outside Face Solar Radiation Heat Gain Energy [J]
These “outside face solar radiation” output variables describe the heat transferred by the absorption
of solar radiation at the outside face. This is the result of incident solar radiation being absorbed at
the surface face. The values are always positive.
1.10.45.15 Surface Outside Face Incident Solar Radiation Rate per Area [W/m2]
The total solar radiation incident on the outside of an exterior surface. It is the sum of:
– Surface Outside Face Incident Beam Solar Radiation Rate per Area
– Surface Outside Face Incident Sky Diffuse Solar Radiation Rate per Area
– Surface Outside Face Incident Ground Diffuse Solar Radiation Rate per Area
– Surface Outside Face Incident Sky Diffuse Surface Reflected Solar Radiation Rate per Area
– Surface Outside Face Incident Beam To Beam Surface Reflected Solar Radiation Rate per Area
– Surface Outside Face Incident Sky Diffuse Surface Reflected Solar Radiation Rate per Area
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 339
1.10.45.16 Surface Outside Face Incident Beam Solar Radiation Rate per Area
[W/m2]
The solar beam radiation incident on the outside of an exterior surface, including the effects of
shadowing, if present. The beam here is that directly from the sun; it excludes beam specularly
reflected from obstructions.
1.10.45.17 Surface Outside Face Incident Sky Diffuse Solar Radiation Rate per
Area [W/m2]
The solar diffuse radiation from the sky incident on the outside of an exterior surface, including the
effects of shadowing, if present.
1.10.45.18 Surface Outside Face Incident Ground Diffuse Solar Radiation Rate
per Area [W/m2]
The solar diffuse radiation incident on the outside of an exterior surface that arises from reflection of
beam solar and sky diffuse solar from the ground. This is the sum of the next two output variables,
“Surface Outside Face Incident Beam To Diffuse Ground Reflected Solar Radiation Rate per Area”
and “Surface Outside Face Incident Sky Diffuse Ground Reflected Solar Radiation Rate per Area.”
The reflected solar radiation from the ground is assumed to be diffuse and isotropic (there is no
specular component).
If “Reflections” option is not chosen in the Solar Distribution Field in the BUILDING object, the
effects of shadowing are accounted for by the user-specified value of View Factor to Ground for the
surface. If “Reflections” option is chosen, the program determines the effects of shadowing, including
time-varying shadowing of the ground plane by the building itself.
The solar diffuse radiation incident on the outside of an exterior surface that arises from beam-to-
diffuse reflection from the ground. It is assumed that there is no beam-to-beam (specular) component.
The beam here is that directly from the sun; it excludes beam specularly reflected from obstructions.
1.10.45.20 Surface Outside Face Incident Sky Diffuse Ground Reflected Solar
Radiation Rate per Area [W/m2]
The solar diffuse radiation incident on the outside of an exterior surface that arises from sky diffuse
solar reflection from the ground. The sky diffuse here is that directly from the sky; it excludes
reflection of sky diffuse from obstructions.
1.10.45.21 Surface Outside Face Incident Sky Diffuse Surface Reflected Solar
Radiation Rate per Area [W/m2]
The solar diffuse radiation incident on the outside of an exterior surface that arises from sky diffuse
reflection from one or more obstructions. This value will be non-zero only if “Reflections” option is
chosen in the BUILDING object.
340 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.10.45.22 Surface Outside Face Incident Beam To Beam Surface Reflected Solar
Radiation Rate per Area [W/m2]
The solar beam radiation incident on the outside of an exterior surface that arises from beam-to-beam
(specular) reflection from one or more obstructions. This value will be non-zero only if “Reflections”
option is chosen in the BUILDING object. For windows, the program treats this beam radiation as
diffuse radiation in calculating its transmission and absorption.
1.10.45.23 Surface Outside Face Incident Beam To Diffuse Surface Reflected So-
lar Radiation Rate per Area [W/m2]
The solar diffuse radiation incident on the outside of an exterior surface that arises from beam-
to-diffuse reflection from building shades or building surfaces. This value will be non-zero only if
“Reflections” option is chosen in the BUILDING object.
1.10.45.24 Surface Outside Face Beam Solar Incident Angle Cosine Value []
The cosine of the angle of incidence of (unreflected) beam solar radiation on the outside of an exterior
surface. The value varies from 0.0 for beam parallel to the surface (incidence angle = 90O ) to 1.0
for beam perpendicular to the surface (incidence angle = 0O ). Negative values indicate the sun is
behind the surface, i.e the surface does not see the sun.
This is the view factor multiplier for diffuse sky irradiance on exterior surfaces taking into account
the anisotropic radiance of the sky. The diffuse sky irradiance on a surface is given by Anisotropic
Sky Multiplier * Diffuse Solar Irradiance.
The following variables apply only to opaque surfaces, where an opaque surface is considered here to
be an exterior or interzone heat transfer surface of class FLOOR, WALL, ROOF or DOOR. Note
– these are advanced variables – you must read the descriptions and understand before
use – then you must use the Output:Diagnostics object to allow reporting.
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 341
1.10.46.2 Surface Inside Face Conduction Heat Transfer Rate per Area [W/m2]
These “inside face conduction” output variables describe heat flow by conduction right at the inside
face of an opaque heat transfer surface. A positive value means that the conduction is from just
inside the inside face toward the inside face. A negative value means that the conduction is from
the inside face into the core of the heat transfer surface.
Note that Inside Face Conduction, when positive, does not indicate the heat flow from the surface
to the zone air, which is governed by the inside face convection coefficient and the difference in
temperature between the inside face and the zone air.
Different versions of the reports are available. The basic heat gain rate (W) and a per unit area
flux (W/m2 ) can have positive or negative values with the sign convention that positive indicates
heat flowing toward the face itself. There are also directed “gain” and “loss” versions that have only
positive values or zero when the heat flow direction opposes.
Former Name: Prior to version 7.1, these outputs were called “Opaque Surface Inside Face Conduc-
tion *.”
Former Name: For Conduction Finite Difference simulations (CondFD), CondFD Inside Surface
Heat Flux is replaced with Surface Inside Face Conduction Heat Transfer Rate Per Area. Likewise
for CondFD Inside Heat Flux to Surface.
1.10.46.6 Surface Outside Face Conduction Heat Transfer Rate per Area [W/m2]
These “outside face conduction” output variables describe heat flow by conduction right at the
outside face of an opaque heat transfer surface. A positive value means that the conduction is from
just inside the outside face toward the outside face. A negative value means that the conduction is
from the outside face into the core of the heat transfer surface.
Note that outside face conduction, when positive, does not indicate the heat flow from the surface
to the surrounding air, which is governed by the outside face convection coefficient and the difference
in temperature between the inside face and the surrounding air.
Different versions of the reports are available. The basic heat transfer rate (W) and a per unit area
flux (W/m2 ) can have positive or negative values with the sign convention that positive indicates
heat flowing toward the face itself. There are also directed “gain” and “loss” versions that have only
positive values or zero when the heat flow direction opposes.
Former Name: For Conduction Finite Difference simulations (CondFD), CondFD Outside Surface
Heat Flux is replaced with Surface Outside Face Conduction Heat Transfer Rate Per Area. Likewise
for CondFD Outside Heat Flux to Surface.
342 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.10.46.10 Surface Average Face Conduction Heat Transfer Rate per Area
[W/m2]
These “average face conduction” output variables combine the inside face conduction and outside
face conduction reports together to describe the conduction situation in a heat transfer surface in a
nominal way. This is simply the average of the inside and outside face conduction rates, but with
the sign convention for the outside face switched to match the inside face so that positive values here
indicate heat flowing into the thermal zone.
Different versions of the reports are available. The basic heat conduction rate (W) and a per unit
area flux (W/m2 ) can have positive or negative values with the sign convention that positive indicates
heat flowing toward the thermal zone. There are also directed “gain” and “loss” versions that have
only positive values or zero when the heat flow direction opposes (W). Finally there is a version for
total energy transfer (J).
These “heat storage” output variables combine the inside face conduction and outside face conduction
reports together to describe the thermal storage situation in a heat transfer surface in a nominal
way. This is simply the difference between the inside and outside face conduction, but with the sign
convention arranged so that positive values indicate heat being added to the core of the surface.
Different versions of the reports are available. The basic heat storage rate (W) and a per unit area
flux (W/m2 ) can have positive or negative values with the sign convention that positive indicates
heat being added to the surface’s mass. There are also directed “gain” and “loss” versions that have
only positive values or zero when the heat storage direction opposes (W). Finally there is a version
for total energy stored (J).
The sum of the Opaque Surface Inside Face Conduction values for all opaque surfaces in a zone for
both positive and negative sums. For example, assume a zone has six opaque surfaces with Opaque
Surface Inside Face Conduction values of 100, -200, 400, 50, 150 and –300 W. Then Zone Opaque
Surface Inside Face Conduction = 700 - 500 = 200 W. Or if a zone has six opaque surfaces with
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 343
Opaque Surface Inside Face Conduction values of -100, -200, 400, -50, 150 and –300W. Then Zone
Opaque Surface Inside Face Conduction = 550 – 650 = -100 W.
1.10.46.20 Zone Opaque Surface Inside Faces Total Conduction Heat Gain Rate
[W]
1.10.46.21 Zone Opaque Surface Inside Faces Total Conduction Heat Gain En-
ergy [J]
These are the power and energy sums for the Opaque Surface Inside Face Conduction values for all
opaque surfaces in a zone when that sum is positive. For example, assume a zone has six opaque
surfaces with Opaque Surface Inside Face Conduction values of 100, -200, 400, 50, 150 and –300 W.
Then Zone Opaque Surface Inside Faces Total Conduction Heat Gain Rate = 700 - 500 = 200 W.
1.10.46.22 Zone Opaque Surface Inside Faces Total Conduction Heat Loss Rate
[W]
1.10.46.23 Zone Opaque Surface Inside Faces Total Conduction Heat Loss En-
ergy [J]
These are the power and energy absolute value for the sums of the Opaque Surface Inside Face
Conduction values for all opaque surfaces in a zone when that sum is negative. For example, assume
a zone has six opaque surfaces with Opaque Surface Inside Face Conduction values of -100, -200,
400, -50, 150 and –300W. Then Zone Opaque Surface Inside Faces Total Conduction Heat Loss Rate
= |550 – 650| = |-100| = 100 W.
The sum of the Opaque Surface Outside Face Conduction values for all opaque surfaces in a zone for
both positive and negative sums. For example, assume a zone has six opaque surfaces with Opaque
Surface Outside Face Conduction values of 100, -200, 400, 50, 150 and –300 W. Then Zone Opaque
Surface Outside Face Conduction = 700 - 500 = 200 W. Or if a zone has six opaque surfaces with
Opaque Surface Outside Face Conduction values of -100, -200, 400, -50, 150 and –300W. Then Zone
Opaque Surface Outside Face Conduction = 550 – 650 = -100 W.
1.10.46.26 Zone Opaque Surface Outside Face Conduction Gain Energy [J]
These are the power and energy sums for the Opaque Surface Outside Face Conduction values for
all opaque surfaces in a zone when that sum is positive. For example, assume a zone has six opaque
surfaces with Opaque Surface Outside Face Conduction values of 100, -200, 400, 50, 150 and –300
W. Then Zone Opaque Surface Outside Face Conduction Gain = 700 - 500 = 200 W.
344 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.10.46.28 Zone Opaque Surface Outside Face Conduction Loss Energy [J]
These are the power and energy absolute value for the sums of the Opaque Surface Outside Face
Conduction values for all opaque surfaces in a zone when that sum is negative. For example, assume
a zone has six opaque surfaces with Opaque Surface Outside Face Conduction values of -100, -200,
400, -50, 150 and -300W. Then Zone Opaque Surface Outside Face Conduction Loss = |550 – 650|
= |-100| = 100 W.
1.10.46.29 Surface Inside Face Beam Solar Radiation Heat Gain Rate [W]
Beam solar radiation from exterior windows absorbed on the inside face of an opaque heat transfer
surface. For Solar Distribution = FullInteriorAndExterior, this quantity can be non-zero for both
floor and wall surfaces. Otherwise, for Solar Distribution = FullExterior or MinimalShadowing, it
can be non-zero only for floor surfaces since in this case all entering beam solar is assumed to fall on
the floor. Note that this variable will not be operational (have a real value) unless there are exterior
windows in the zone.
The total Surface Window Transmitted Solar Radiation Rate of all the exterior windows in a zone.
The sum of the heat flow from all of the exterior windows in a zone when that sum is positive. (See
definition of “heat flow” under “Window Heat Gain,” below.)
The absolute value of the sum of the heat flow from all of the exterior windows in a zone when that
sum is negative.
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 345
1.10.47.8 Surface Window Total Glazing Layers Absorbed Solar Radiation Rate
[W]
1.10.47.9 Surface Window Total Glazing Layers Absorbed Solar Radiation En-
ergy [J]
The total exterior beam and diffuse solar radiation absorbed in all of the glass layers of an exterior
window.
1.10.47.10 Surface Window Shading Device Absorbed Solar Radiation Rate [W]
The amount of beam and diffuse solar radiation entering a zone through an exterior window. It is
the sum of the following two variables, “Surface Window Transmitted Beam Solar Radiation Rate”
and “Surface Window Transmitted Diffuse Solar Radiation Rate.”
The solar radiation transmitted by an exterior window whose source is beam solar incident on the
outside of the window. For a bare window, this transmitted radiation consists of beam radiation
passing through the glass (assumed transparent) and diffuse radiation from beam reflected from the
outside window reveal, if present. For a window with a shade, this transmitted radiation is totally
diffuse (shades are assumed to be perfect diffusers). For a window with a blind, this transmitted
radiation consists of beam radiation that passes between the slats and diffuse radiation from beam-
to-diffuse reflection from the slats. For a window with a screen, this value consists of direct beam
radiation that is transmitted through the screen (gaps between the screen material) and diffuse
radiation from beam-to-diffuse reflection from the screen material.
For each zone time step,
Surface Window Transmitted Beam Solar Radiation Rate = Surface Window Transmitted Beam To
Beam Solar Radiation Rate + Surface Window Transmitted Beam To Diffuse Solar Radiation Rate
Surface Window Transmitted Beam Solar Radiation Energy = Surface Window Transmitted Beam
To Beam Solar Radiation Energy + Surface Window Transmitted Beam To Diffuse Solar Radiation
Energy
346 CHAPTER 1. INPUT-OUTPUT REFERENCE
For a window with a blind, this transmitted radiation consists of beam radiation that passes between
the slats. For a window with a screen, this value consists of direct beam radiation that is transmitted
through the screen (gaps between the screen material).
For a window with a blind, this transmitted radiation consists of diffuse radiation reflected from
beam by the slats. For a window with a screen, this value consists of diffuse radiation reflected by
the screen material.
1.10.47.20 Zone Exterior Windows Total Transmitted Beam Solar Radiation En-
ergy [J]
The sum of the Surface Window Transmitted Beam Solar Radiation Rate (see definition above) from
all exterior windows in a zone.
1.10.47.21 Zone Interior Windows Total Transmitted Beam Solar Radiation Rate
[W]
1.10.47.22 Zone Interior Windows Total Transmitted Beam Solar Radiation En-
ergy [J]
The sum of the Surface Window Transmitted Beam Solar Radiation Rate (see definition above) from
all interior windows in a zone.
The solar radiation transmitted by an exterior window whose source is diffuse solar incident on the
outside of the window. For a bare window, this transmitted radiation consists of diffuse radiation
passing through the glass. For a window with a shade, this transmitted radiation is totally diffuse
(shades are assumed to be perfect diffusers). For a window with a blind, this transmitted radiation
consists of diffuse radiation that passes between the slats and diffuse radiation from diffuse-to-
diffuse reflection from the slats. For a window with a screen, this value consists of diffuse radiation
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 347
transmitted through the screen (gaps between the screen material) and diffuse radiation from diffuse-
to-diffuse reflection from the screen material.
The combined beam and diffuse solar that first entered adjacent zones through exterior windows in
the adjacent zones, was subsequently reflected from interior surfaces in those zones (becoming diffuse
through that reflection), and was then transmitted through interior windows into the current zone.
The sum of the Surface Window Transmitted Diffuse Solar Radiation Rate (see definition above)
from all interior windows in a zone.
Effective solar transmittance of an exterior window, including effect of shading device, if present.
Equal to “Surface Window Transmitted Solar Radiation Rate” divided by total exterior beam plus
diffuse solar radiation incident on the window (excluding frame, if present).
Effective solar absorptance of an exterior window, including effect of shading device, if present.
Equal to “Window Solar Absorbed: All Glass Layers” plus “Window Solar Absorbed: Shading
Device” divided by total exterior beam plus diffuse solar radiation incident on window (excluding
frame, if present)
Effective solar reflectance of an exterior window, including effect of shading device, if present. Equal
to: [1.0 – “Surface Window System Solar Transmittance” – “Surface Window System Solar Absorp-
tance”].
For an airflow window, the forced convective heat flow from the gap through which airflow occurs.
This is the heat gained (or lost) by the air from the glass surfaces (and between-glass shading device
348 CHAPTER 1. INPUT-OUTPUT REFERENCE
surfaces, if present) that the air comes in contact with as it flows through the gap. If the gap airflow
goes to the zone indoor air, the gap convective heat flow is added to the zone load. Applicable to
exterior windows only.
The total heat flow to the zone from the glazing, frame and divider of an exterior window when the
total heat flow is positive.
For a window without an interior shading device, this heat flow is equal to:
Here, short-wave radiation is that from lights and diffuse interior solar radiation.
For a window with an interior shading device, this heat flow is equal to:
The total window heat flow can also be thought of as the sum of the solar and conductive gain to
the zone from the window.
The absolute value of the total heat flow through an exterior window when the total heat flow is
negative. (See definition of “total heat flow” under “Surface Window Heat Gain Rate,” above.)
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 349
The total heat flow through the glazing, frame and divider of an exterior window. Negative values
imply heat flow to the exterior.
The important distinction between this output variable and those for “Surface Window Heat
Gain/Loss” is that this represents the net heat flow through the window and not the heat flow to
the zone. The only difference is the heat flow to the zone does not account for radiation from the
opaque frame and divider components. This is because these components, as a simplification, do
not participate in the overall radiative exchange with other surfaces in the zone.
For a window without an interior shading device, this heat flow is equal to:
Here, short-wave radiation is that from lights and diffuse interior solar radiation.
For a window with an interior shading device, this heat flow is equal to:
The fraction of exterior beam solar radiation incident on the glass of an exterior window that is
transmitted through the glazing as beam radiation. This is for the base window without shading.
Takes into account the angle of incidence of beam solar radiation on the glass.
The fraction of exterior beam solar radiation incident on the glazing of an exterior window that is
transmitted through the glazing as diffuse radiation.
The fraction of exterior diffuse solar radiation incident on the glass of an exterior window that is
transmitted through the glass assuming that the window has no shading device. It is assumed that
incident diffuse solar is transmitted only as diffuse with no beam component.
350 CHAPTER 1. INPUT-OUTPUT REFERENCE
The number of iterations needed by the window-layer heat balance solution to converge.
For a vertical exterior window, this is an angle appropriate for calculating beam solar quantities
appropriate to horizontal window elements such as horizontal reveal surfaces, horizontal frame and
divider elements and horizontal slats of window blinds. It is defined as the angle between the window
outward normal and the projection of the sun’s ray on the vertical plane containing the outward
normal. See Figure 1.34.
For an exterior window of arbitrary tilt, it is defined as the angle between the window outward normal
the projection of the sun’s ray on the plane that contains the outward normal and is perpendicular
to the ground.
If the sun is behind the window, the horizontal profile angle is not defined and is reported as 0.0.
Note that in most texts and in window equivalent layer model what we call “horizontal profile angle”
is called “vertical profile angle.”
For a vertical exterior window, this is an angle appropriate for calculating beam solar quantities
appropriate to vertical window elements such as vertical reveal surfaces, vertical frame and divider
elements and vertical slats of window blinds. It is defined as the angle between the window outward
normal and the projection of the sun’s ray on the horizontal plane containing the outward normal.
See Figure 1.34.
For an exterior window of arbitrary tilt, it is defined as the angle between the window outward normal
the projection of the sun’s ray on the plane that contains the outward normal and is perpendicular to
the plane defined above for Surface Window Solar Horizontal Profile Angle for a window of arbitrary
tilt.
If the sun is behind the window, the vertical profile angle is not defined and is reported as 0.0.
Note that in most texts and in window equivalent layer model what we call “vertical profile angle”
is called “horizontal profile angle.”
1.10.47.47 Surface Window Outside Reveal Reflected Beam Solar Radiation En-
ergy [J]
Beam solar radiation reflected from the outside reveal surfaces of a window (ref: Reveal Surfaces
under WindowProperty:FrameAndDivider object). There are both rate and energy versions.
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 351
Figure 1.34: Vertical exterior window showing solar horizontal profile angle, solar vertical profile
angle and solar incidence angle.
352 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.10.47.48 Surface Window Inside Reveal Reflected Beam Solar Radiation Rate
[W]
1.10.47.49 Surface Window Inside Reveal Reflected Beam Solar Radiation En-
ergy [J]
Beam solar radiation reflected from the inside reveal surfaces of a window (ref: Reveal Surfaces
under WindowProperty:FrameAndDivider object). There are both rate and energy versions.
1.10.47.50 Surface Window Inside Reveal Absorbed Beam Solar Radiation Rate
[W]
Beam solar radiation absorbed at the inside reveal surfaces of a window, in Watts.
1.10.47.51 Surface Window Inside Reveal Reflected Diffuse Zone Solar Radiation
Rate [W]
Diffuse solar radiation reflected from inside reveal surfaces of a window into the zone, in Watts.
1.10.47.52 Surface Window Inside Reveal Reflected Diffuse Frame Solar Radia-
tion Rate [W]
Diffuse solar radiation reflected from inside reveal surfaces onto the frame surfaces of a window, in
Watts.
1.10.47.53 Surface Window Inside Reveal Reflected Diffuse Glazing Solar Radi-
ation Rate [W]
Diffuse solar radiation reflected from inside reveal surfaces onto the glazing surfaces of a window, in
Watts.
A value of 1 means that moisture condensation will occur on the innermost glass face of an exterior
window (i.e., on the glass face in contact with the zone air). Otherwise the value is 0. The condition
for condensation is glass inside face temperature < zone air dewpoint temperature.
For airflow exterior windows, in which forced air passes between adjacent glass faces in double- and
triple-pane windows, a value of 1 means that condensation will occur on one or both of the glass
faces in contact with the airflow. In this case the condition for condensation is:
– For airflow source = indoorair, temperature of either face in contact with airflow < zone air
dewpoint temperature.
– For airflow source = outdoorair, temperature of either face in contact with airflow < outside
air dewpoint temperature.
As for regular windows, the value will also be 1 if condensation occurs on the innermost glass face.
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 353
If an exterior window has a frame and the value of this flag is 1, condensation will occur on the
inside surface of the frame. The condition for condensation is frame inside surface temperature <
zone air dewpoint temperature.
If an exterior window has a divider and the value of this flag is 1, condensation will occur on the
inside surface of the divider. The condition for condensation is divider inside surface temperature <
zone air dewpoint temperature.
The fraction of time that a shading device is on an exterior window. For a particular simulation
timestep, the value is 0.0 if the shading device is off (or there is no shading device) and the value is
1.0 if the shading device is on. (It is assumed that the shading device, if present, is either on or off
for the entire timestep.) If the shading device is switchable glazing, a value of 0.0 means that the
glazing is in the unswitched (light colored) state, and a value of 1.0 means that the glazing is in the
switched (dark colored) state.
For a time interval longer a timestep, this is the fraction of the time interval that the shading device
is on. For example, take the case where the time interval is one hour and the timestep is 10 minutes.
Then if the shading device is on for two timesteps in the hour and off for the other four timesteps,
then the fraction of time that the shading device is on = 2/6 = 0.3333.
For an exterior window with a blind, this is the angle in degrees between the glazing outward normal
and the blind slat angle outward normal, where the outward normal points away from the front face
of the slat. The slat angle varies from 0 to 180 deg. If the slat angle is 0 deg or 180 deg, the slats
are parallel to the glazing and the slats are said to be “closed”. If the slat angle is 90 deg, the slats
are perpendicular to the glazing and the slats are said to be “fully open”. See illustrations under
WindowMaterial:Blind. For blinds with a fixed slat angle, the value reported here will be constant.
For WindowMaterial:Blind:EquivalentLayer blinds the slat angle varies from -90 to 90 deg. If the
slat angle is -90 deg or 90 deg, the slats are parallel to the glazing and the slats are said to be
“closed”. If the slat angle is 0 deg, the slats are perpendicular to the glazing and the slats are said
to be “fully open”. For blinds with a fixed slat angle, the value reported here will be constant.
For an exterior window with a blind, this is the fraction of exterior beam solar radiation incident on
the blind that is transmitted through the blind as beam solar radiation when the blind is isolated
(i.e., as though the window glass were not present). Depends on various factors, including slat angle,
width, separation, and thickness, and horizontal solar profile angle (for blinds with horizontal slats)
or vertical solar profile angle (for blinds with vertical slats). The transmittance value reported here
will be non-zero only when some beam solar can pass through the blind without hitting the slats.
354 CHAPTER 1. INPUT-OUTPUT REFERENCE
For an exterior window with a blind, the fraction of exterior beam solar radiation incident on the
blind that is transmitted through the blind as diffuse solar radiation when the blind is isolated (i.e., as
though the window glass were not present). Depends on various factors, including slat angle, width,
separation, thickness and reflectance, and horizontal solar profile angle (for blinds with horizontal
slats) or vertical solar profile angle (for blinds with vertical slats).
For an exterior window with a blind, the fraction of exterior diffuse solar radiation incident on the
blind that is transmitted through the blind as diffuse solar radiation when the blind is isolated (i.e.,
as though the window glass were not present). Depends on various factors, including slat angle,
width, separation, thickness and reflectance. For blinds with a fixed slat angle the transmittance
value reported here will be constant.
1.10.47.62 Surface Window Blind and Glazing System Beam Solar Transmit-
tance []
The fraction of exterior beam solar radiation incident on an exterior window with a blind (excluding
window frame, if present) that is transmitted through the blind/glass system as beam solar radia-
tion. Depends on various factors, including type of glass; solar incidence angle; slat angle, width,
separation, and thickness; and horizontal solar profile angle (for blinds with horizontal slats) or
vertical solar profile angle (for blinds with vertical slats).
1.10.47.63 Surface Window Blind and Glazing System Diffuse Solar Transmit-
tance []
The fraction of exterior diffuse solar radiation incident on an exterior window with a blind (exclud-
ing window frame, if present) that is transmitted through the blind/glass system as diffuse solar
radiation. Depends on various factors, including type of glass and slat angle, width, separation,
thickness and reflectance. For blinds with a fixed slat angle the transmittance value reported here
will be constant.
For an exterior window with a screen, this is the fraction of exterior beam solar radiation incident on
the screen that is transmitted through the screen as beam solar radiation when the screen is isolated
(i.e., as though the window glass were not present). Depends on various factors, including the screen
reflectance and the relative angle of the incident beam with respect to the screen. This value will
include the amount of inward reflection of solar beam off the screen material surface if the user
specifies this modeling option (i.e., Material: WindowScreen, field Reflected Beam Transmittance
Accounting Method = Model as Direct Beam).
For an exterior window with a screen, the fraction of exterior beam solar radiation incident on the
screen that is transmitted through the screen as diffuse solar radiation when the screen is isolated
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 355
(i.e., as though the window glass were not present). Depends on various factors, including the screen
reflectance and the relative angle of the incident beam with respect to the screen. This value is the
amount of inward reflection of solar beam off the screen material surface if the user specifies this
modeling option (i.e., Material: WindowScreen, field Reflected Beam Transmittance Accounting
Method = Model as Diffuse); otherwise, this value will be zero.
For an exterior window with a screen, the fraction of exterior diffuse solar radiation incident on the
screen that is transmitted through the screen as diffuse solar radiation when the screen is isolated
(i.e., as though the window glass were not present). Depends on various factors including screen
material geometry and reflectance. This value is calculated as an average, constant For a window
with a screen, this value consists of diffuse radiation transmitted through the screen (gaps between
the screen material) and diffuse radiation from diffuse-to-diffuse reflection from the screen material.
For a window with a screen, this value consists of diffuse radiation transmitted through the screen
(gaps between the screen material) and diffuse radiation from diffuse-to-diffuse reflection from the
screen material.
1.10.47.67 Surface Window Screen and Glazing System Beam Solar Transmit-
tance[]
The fraction of exterior beam solar radiation incident on an exterior window with a screen (exclud-
ing window frame, if present) that is transmitted through the screen/glass system as beam solar
radiation. Depends on various factors, including the screen reflectance and the relative angle of the
incident beam with respect to the screen. This value will include the amount of inward reflection of
solar beam off the screen material surface if the user specifies this modeling option (i.e., Material:
WindowScreen, field Reflected Beam Transmittance Accounting Method = Model as Direct Beam).
1.10.47.68 Surface Window Screen and Glazing System Diffuse Solar Transmit-
tance []
The fraction of exterior diffuse solar radiation incident on an exterior window with a screen (exclud-
ing window frame, if present) that is transmitted through the screen/glass system as diffuse solar
radiation. Depends on various factors including screen material geometry and reflectance.
The beam solar radiation transmitted through an interior window. Calculated only if Solar Distri-
bution = FullInteriorAndExterior in your Building input. The origin of this radiation is beam solar
that enters through an exterior window in a zone and then passes through an interior window into
the adjacent zone. The amount of this radiation depends on several factors, including sun position,
intensity of beam solar incident on the exterior window (including effects of shadowing, if present),
relative position of the exterior and interior window, and the size and transmittance of the windows.
Note that if there are two or more exterior windows in a zone, then beam solar from one or more
of them may pass through the same interior window. Likewise, if there are more than two or more
356 CHAPTER 1. INPUT-OUTPUT REFERENCE
interior windows in a zone then beam solar from a single exterior window may pass through one or
more of the interior windows. There are both rate and energy versions of the output.
Indicates whether a storm window glass layer is present (ref: StormWindow object). The value is 0
if the storm window glass layer is off, 1 if it is on, and –1 if the window does not have an associated
storm window. Applicable only to exterior windows and glass doors.
1.10.47.72 Surface Inside Face Initial Transmitted Diffuse Transmitted Out Win-
dow Solar Radiation Rate [W]
As of Version 2.1, the diffuse solar transmitted through exterior windows that is initially distributed
to another window in the zone and transmitted out of the zone through that window. For exterior
windows, this transmitted diffuse solar is “lost” to the exterior environment For interior windows,
this transmitted diffuse solar is distributed to heat transfer surfaces in the adjacent zone, and is
part of the Surface Inside Face Initial Transmitted Diffuse Absorbed Solar Radiation Rate for these
adjacent zone surfaces.
The following output variables for windows or glass doors are available when the user requests to
display advanced output variables. These seven reports show the individual components that are
combined to determine overall Surface Window Heat Gain Rate and/or Surface Window Heat Loss
Rate (described above).
1.10.47.74 Surface Window Inside Face Glazing Zone Convection Heat Gain Rate
[W]
The surface convection heat transfer from the glazing to the zone in watts. This output variable
is the term called “[Convective heat flow to the zone from the zone side of the glazing]” under the
description above for Surface Window Heat Gain Rate output variable. If the window has an interior
shade or blind, then this is zero and the glazing’s convection is included in the report called “Surface
Window Inside Face Gap between Shade and Glazing Zone Convection Heat Gain Rate”.
1.10.47.75 Surface Window Inside Face Glazing Net Infrared Heat Transfer Rate
[W]
The net exchange of infrared radiation heat transfer from the glazing to the zone in watts. This
output variable is the term called “[Net IR heat flow to the zone from zone side of the glazing]”
under the description above for Surface Window Heat Gain Rate output variable.
1.10.47.76 Surface Window Shortwave from Zone Back Out Window Heat Trans-
fer Rate [W]
This is the short-wave radiation heat transfer from the zone back out the window in watts. This is
a measure of the diffuse short-wave light (from reflected solar and electric lighting) that leave the
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 357
zone through the window. This output variable is the term called “[Short-wave radiation from zone
transmitted back out the window]” under the description above for Surface Window Heat Gain Rate
output variable.
1.10.47.77 Surface Window Inside Face Frame and Divider Zone Heat Gain Rate
[W]
This is the heat transfer from any frames and/or dividers to the zone in watts. This output variable
is the term called “[Conduction to zone from window frame and divider, if present]” under the
description above for Surface Window Heat Gain Rate output variable. (The word “conduction”
here is used because the models is simplified compared to the complexities of surface convection and
radiation.)
This is the positive heat flow from window frames to the zone in watts. This is part of the Surface
Window Inside Face Frame and Divider Zone Heat Gain Rate.
This is the negative heat flow from window frames to the zone in watts. This is part of the Surface
Window Inside Face Frame and Divider Zone Heat Gain Rate.
This is the positive heat flow from window dividers to the zone in watts. This is part of the Surface
Window Inside Face Frame and Divider Zone Heat Gain Rate.
This is the negative heat flow from window dividers to the zone in watts. This is part of the Surface
Window Inside Face Frame and Divider Zone Heat Gain Rate.
1.10.47.86 Surface Window Inside Face Gap between Shade and Glazing Zone
Convection Heat Gain Rate [W]
This is the convection surface heat transfer from the both the glazing and the shade’s back face to
the zone in Watts. This output variable is the term called “[Convective heat flow to the zone from
the air flowing through the gap between glazing and shading device]” under the description above for
Surface Window Heat Gain Rate output variable. For Equivalent Layer window this output variable
is the convection heat gain from vented interior air gap to the zone in Watts.
1.10.47.87 Surface Window Inside Face Shade Zone Convection Heat Gain Rate
[W]
This is the convection surface heat transfer from the front side of any interior shade or blind to the
zone in Watts. This output variable is the term called “[Convective heat flow to the zone from the
zone side of the shading device]” under the description above for Surface Window Heat Gain Rate
output variable. For equivalent Layer window this output variable is the convection heat gain rate
from the inside face of a glazing or a shade to the zone in Watts.
1.10.47.88 Surface Window Inside Face Shade Net Infrared Heat Transfer Rate
[W]
The net exchange of infrared radiation heat transfer from the shade or blind to the zone in watts.
This output variable is the term called “[Net IR heat flow to the zone from the zone side of the
shading device]” under the description above for Surface Window Heat Gain Rate output variable.
1.10.47.89 Surface Window Inside Face Other Convection Heat Gain Rate [W]
The other (extra) convection heat transfer rate from the inside face of a an equivalent layer window.
This output is computed from the difference in convection flux when using equivalent inside surface
temperature of a window instead of the inside surface temperature from the standard surface heat
balance calculation.
The temperature under which the optical data of the TC glass layer are specified.
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 359
The switching factor (tint level) of the switchable window: 0 means no switching – clear state; 1
means fully switched – dark state.
1.10.49.1 DXF
This report produces a special file (eplusout.dxf) in the industry standard DXF (Drawing Inter-
change Format) for drawings. It is produced and accepted by many popular, commercial CAD
programs. Detailed reference can be found on the AutoCADTM website at: http://www.autodesk.
com/techpubs/autocad/acadr14/dxf/index.htm.
EnergyPlus produces this file from the Report command:
This version of the report creates lines in the eplusout.eio file for each surface (except internal mass
surfaces). Details of this reporting is shown in the Output Details and Examples document.
There are two kinds of shading surfaces in EnergyPlus: detached and attached. A detached
shading surface, such as a tree or neighboring building, is not connected to the building. An attached
shading surface is typically an overhang or fin that is attached to a particular base surface of the
building, usually a wall; attached shading surfaces are usually designed to shade specific windows.
Objects for detached shading surfaces:
– Shading:Site
– Shading:Building
– Shading:Site:Detailed
– Shading:Building:Detailed
Similarly to the surfaces, the detailed objects use vertex entry whereas the other objects are limited
to rectangular representation.
Objects for attached shading surfaces:
– Shading:Overhang
– Shading:Overhang:Projection
– Shading:Fin
– Shading:Fin:Projection
– Shading:Zone:Detailed
EnergyPlus creates “bi-directional” shades from each shading surface entered. This means that the
shade you input will cast a shadow no matter which side of the shade the sun is on. For example,
a vertical fin will cast a shadow whether the sun is on the left side or right side of the fin. Prior to
V1.0.2, a shading surface cast a shadow only in the hemisphere toward which the surface faced. This
hemisphere is the one pointed to by the shading surface’s outward normal vector, which is the cross
product V23 x V21, where V23 is the vector from vertex 2 to vertex 3 of the shading surface and
V21 is the vector from vertex 2 to vertex 1. Beginning with V1.0.2, the shades in EnergyPlus are
“bi-directional” so that they can cast shadows in both hemispheres depending on the time-varying
position of the sun relative to the shading surface.
It is important to note that EnergyPlus will automatically account for “self-shading” effects—such
as in L-shaped buildings—in which some of the building’s wall and roof surfaces shade other parts
of the building, especially windows. This means that you only need to describe shading elements
that aren’t building heat-transfer surfaces.
Shading surfaces can also reflect solar radiation onto the building. This feature is simulated if
you choose FullExteriorWithReflections or FullInteriorAndExteriorWithReflections in the Building
object (ref: Building - Field: Solar Distribution). In this case, you may specify the reflectance
properties of a shading surface with the ShadingProperty:Reflectance object. Note: If no Shading-
Property:Reflectance object is defined, then the shading surface reflectance values are assumed to be
0.2 and the fraction of shading surface that is glazed is assumed to be 0.0.
Shading surfaces also automatically shade diffuse solar radiation (and long-wave radiation) from the
sky. And they will automatically shade diffuse solar radiation from the ground if Solar Distribution
Field = FullExteriorWithReflections or FullInteriorAndExteriorWithReflections in the Building ob-
ject. (If the reflections option for Solar Distribution is used, the program also takes into account
the reduction of solar radiation reflected from the ground due to shading of the ground by shading
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 361
surfaces and by the building itself.) Otherwise, shading surfaces will not shade diffuse radiation from
the ground unless you enter a reduced value for View Factor to Ground for those building surfaces
that are shaded (ref: BuildingSurface:Detailed - Field: View Factor to Ground and FenestrationSur-
face:Detailed - Field: View Factor to Ground).
This is a unique character string associated with the detached shading surface. Though it must be
unique from other surface names, it is used primarily for convenience with detached shading surfaces.
Theoretically, this should face to the surface it is shading (i.e. if a south wall, this should be a north
facing shade) but since EnergyPlus automatically generates the mirror image, the facing angle per
se’ is not so important.
The tilt angle is the angle (in degrees) that the shade is tilted from horizontal (or the ground).
Default for this field is 90 degrees.
The rectangular surfaces specify the lower left corner of the surface for their starting coordinate. See
the introductory paragraph for rules on this entry.
Shading:Building ,
Bushes -East , !- Name
90, !- Azimuth Angle {deg}
90, !- Tilt Angle {deg}
45, !- Starting X Coordinate {m}
0, !- Starting Y Coordinate {m}
0, !- Starting Z Coordinate {m}
50, !- Length {m}
1; !- Height {m}
Shading:Site ,
Bushes -North , !- Name
0, !- Azimuth Angle {deg}
90, !- Tilt Angle {deg}
45, !- Starting X Coordinate {m}
50, !- Starting Y Coordinate {m}
0, !- Starting Z Coordinate {m}
50, !- Length {m}
1; !- Height {m}
This is a unique character string associated with the detached shading surface. Though it must be
unique from other surface names, it is used primarily for convenience with detached shading surfaces.
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 363
The name of a schedule of solar transmittance values from 0.0 to 1.0 for the shading surface. If
a blank is entered in this field, the transmittance value defaults to 0.0, i.e., the shading surface is
opaque at all times. This scheduling can be used to allow for seasonal transmittance change, such
as for deciduous trees that have a higher transmittance in winter than in summer. Transmittance
based on time of day can also be used—a movable awning, for example, where the transmittance is
some value less than 1.0 when the awning is in place and is 1.0 when the awning is retracted.
The following assumptions are made in the shading surface transmittance calculation:
– Both sides of the shading surface have the same transmittance properties.
– The transmittance is the same for both beam and diffuse solar radiation.
– Beam solar transmittance is independent of angle of incidence on the shading surface.
– Beam radiation incident on a shading surface is transmitted as beam radiation with no change
in direction, i.e., there is no beam-to-diffuse component.
– If two shading surfaces with non-zero transmittance overlap, the net transmittance is the
product of the individual transmittances. Inter-reflection between the shading surfaces (and
between the shading surfaces and the building) is ignored.
– For the daylighting calculation (ref: Group – Daylighting) the shading surface’s visible trans-
mittance is assumed to be the same as its solar transmittance.
– Shading devices are assumed to be opaque to long-wave radiation no matter what the solar
transmittance value is.
Note that shading devices only shade solar radiation when the sun is up, which is automatically
determined by EnergyPlus from latitude, time of year, etc. The user need only account for the
time-varying transmittance of the shading device in the transmittance schedule, not whether the
sun is up or not.
The number of sides in the surface (number of X,Y,Z vertex groups). For further information, see
the discussion on “Surface Vertices” above.
IDF example of Detached Shading Surfaces:
Shading:Building:Detailed ,
EAST SIDE TREE , !- Detached Shading
ShadingTransmittance :0002 , !- Shadowing Transmittance & Schedule
3, !-Triangle
33.52800 , 10.66800 , 10.05800 ,
33.52800 , 13.71600 , 0.9140000 ,
33.52800 , 4.572000 , 0.9140000 ;
Shading:Building:Detailed ,
WEST SIDE TREE , !- Detached Shading
ShadingTransmittance :0002 , !- Shadowing Transmittance & Schedule
3, !-Triangle
-3.048000 , 7.620000 , 10.05800 ,
-3.048000 , 4.572000 , 0.9140000 ,
-3.048000 , 13.71600 , 0.9140000 ;
364 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.10.55 Shading:Overhang
An overhang typically is used to shade a window in a building.
1.10.55.1 Inputs
1.10.56 Shading:Overhang:Projection
An overhang typically is used to shade a window in a building. This object allows for specifying the
depth of the overhang as a fraction of the window or door’s height.
1.10.56.1 Inputs
1.10.57 Shading:Fin
Fins shade either side of windows/doors in a building. This object allows for specification of both
fins for the window. Fin placement is relative to the edge of the glass and user must include the
frame width when a frame is present.
1.10.57.1 Inputs
1.10.58 Shading:Fin:Projection
Fins shade either side of windows/doors in a building. This object allows for specification of both
fins for the window. This object allows for specifying the depth of the fin as a fraction of the window
or door’s width. Fin placement is relative to the edge of the glass and user must include the frame
width when a frame is present.
1.10.58.1 Inputs
Shading:Overhang:Projection ,
Zn001:Wall001:Win001:Shade001 , !- Name
Zn001:Wall001:Win001 , !- Window or Door Name
.7, !- Height above Window or Door {m}
90, !- Tilt Angle from Window/Door {deg}
.2, !- Left extension from Window/Door Width {m}
.2, !- Right extension from Window/Door Width {m}
.6; !- Depth as Fraction of Window/Door Height {m}
Shading:Overhang ,
Zn001:Wall001:Door001:Shade001 , !- Name
Zn001:Wall001:Door001 , !- Window or Door Name
.6, !- Height above Window or Door {m}
90, !- Tilt Angle from Window/Door {deg}
0, !- Left extension from Window/Door Width {m}
0, !- Right extension from Window/Door Width {m}
3; !- Depth {m}
Shading:Fin:Projection ,
Zn001:Wall001:Shade003 , !- Name
Zn001:Wall001:Win001 , !- Window or Door Name
.1, !- Left Extension from Window/Door {m}
.1, !- Left Distance Above Top of Window {m}
.1, !- Left Distance Below Bottom of Window {m}
90, !- Left Tilt Angle from Window/Door {deg}
.6, !- Left Depth as Fraction of Window/Door Width {m}
.1, !- Right Extension from Window/Door {m}
.1, !- Right Distance Above Top of Window {m}
.1, !- Right Distance Below Bottom of Window {m}
90, !- Right Tilt Angle from Window/Door {deg}
.6; !- Right Depth as Fraction of Window/Door Width {m}
1.10.59 Shading:Zone:Detailed
This object is used to describe attached “subsurfaces” such as overhangs, wings or fins that project
outward from a base surface. This classification is used for convenience; actually, a device of this
type can cast shadows on the surface to which it is attached as well as on adjacent surfaces. For
example, a fin may shade its parent wall as well as adjacent walls.
Note that a zone surface can cast shadows on other zone surfaces. However, you don’t have to
worry about such effects—for example, one wall of an L-shaped building shading another wall–
because EnergyPlus will automatically check for this kind of “self shadowing” and do the proper
calculations.
Unlike attached (or detached) shading surfaces, building surfaces can only cast shadows in the
hemisphere towards which they face. This means, for example, that a roof that faces upward will
not cast a shadow downward. (Thus, specifying an oversized roof in an attempt to account for the
shading effects of overhangs will not work). Interior surfaces do not cast shadows of any kind.
1.10.59.1 Inputs
This is the name of the attached shading surface. It must be different from other surface names.
– Both sides of the shading surface have the same transmittance properties.
– The transmittance is the same for both beam and diffuse solar radiation.
– Beam solar transmittance is independent of angle of incidence on the shading surface.
– Beam radiation incident on a shading surface is transmitted as beam radiation with no change
in direction, i.e., there is no beam-to-diffuse component.
– If two shading surfaces with non-zero transmittance overlap, the net transmittance is the
product of the individual transmittances. Inter-reflection between the shading surfaces (and
between the shading surfaces and the building) is ignored.
– For the daylighting calculation (ref: Group – Daylighting) the shading surface’s visible trans-
mittance is assumed to be the same as its solar transmittance.
– Shading devices are assumed to be opaque to long-wave radiation no matter what the solar
transmittance value is.
Note that shading devices only shade solar radiation when the sun is up, which is automatically
determined by EnergyPlus from latitude, time of year, etc. The user need only account for the
time-varying transmittance of the shading device in the transmittance schedule, not whether the
sun is up or not.
Note that for horizontal surfaces, any corner may be chosen as the starting corner. The order
of vertices determines whether the surface is facing up or down. Shading surfaces are mirrored
automatically unless the user specifies “DoNotMirrorDetachedShading”, so each shading surface
need only be described once.
370 CHAPTER 1. INPUT-OUTPUT REFERENCE
Shading:Zone:Detailed ,
Zn003:Wall001:Shade001 , !- Surface Name
Zn003:Wall001 , !- Base Surface Name
ShadingTransmittance :0001 , !- Shadowing Transmittance Schedule
4, !- RectangularLeftFin
57.97000 , 8.450000 ,10.00000 ,
57.97000 , 8.450000 , 0.0000000E+00,
57.97000 , 6.450000 , 0.0000000E+00,
57.97000 , 6.450000 ,10.00000 ;
Shading:Zone:Detailed ,
Zn003:Wall001:Shade002 , !- Surface Name
Zn003:Wall001 , !- Base Surface Name
ShadingTransmittance :0003 , !- Shadowing Transmittance Schedule
4, !- RectangularRightFin
77.97000 , 6.450000 ,10.00000 ,
77.97000 , 6.450000 , 0.0000000E+00,
77.97000 , 8.450000 , 0.0000000E+00,
77.97000 , 8.450000 ,10.00000 ;
1.10.60 ShadingProperty:Reflectance
Specifies the reflectance properties of a shading surface when the solar reflection calculation has
requested, i.e., when if “WithReflections” option is chosen in the Building object (ref: Building
- Field: Solar Distribution). It is assumed that shading surfaces are divided into an unglazed,
diffusely reflecting portion and a glazed, specularly-reflecting portion, either of which may be zero.
The reflectance properties are assumed to be the same on both sides of the shading surface.
Note that a shadowing transmittance schedule (ref: Shading Surfaces, Field: Transmittance Sched-
ule Name) can be used with a reflective shading surface. However, EnergyPlus assumes that the
reflectance properties of the shading surface are constant even if the transmittance varies.
If no ShadingProperty:Reflectance objects are entered, the default values shown here will be used
for shading surfaces. Other surfaces have their reflectance properties defined by the materials in the
outer layers of the constructions.
1.10.60.1 Inputs
The diffuse solar reflectance of the unglazed part of the shading surface (default = 0.2). This
reflectance is assumed to be the same for beam-to-diffuse and diffuse-to-diffuse reflection. Beam-
to-diffuse reflection is assumed to be independent of angle of incidence of beam radiation. Diffuse-
to-diffuse reflection is assumed to be independent of angular distribution of the incident of diffuse
radiation. The outgoing diffuse radiation is assumed to be isotropic (hemispherically uniform).
The sum of this reflectance and the shading surface transmittance should be less than or equal to
1.0.
Shading:Site:Detailed ,
Adjacent Glazed Facade , !- User Supplied Surface Name
, !- Shadowing Transmittance Schedule
4, !- Number of Surface Vertex Groups -- Number of (X,Y,Z) groups
0,-24,30, !- Vertex 1 X,Y,Z coordinates
0,-24,0, !- Vertex 2 X,Y,Z coordinates
0,0,0, !- Vertex 3 X,Y,Z coordinates
0,0,30; !-Vertex 3 X,Y,Z coordinates
ShadingProperty:Reflectance ,
Adjacent Glazed Facade , !- Name of Surface:Shading Object
0.3, !- Diffuse Solar Reflectance of Unglazed Part of Shading Surface
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 373
IDF example of Shading Surface Reflectance for shading surface without specular reflection
Shading:Site:Detailed ,
Adjacent Blank Facade , !- User Supplied Surface Name
, !- Shadowing Transmittance Schedule
4, !- Number of Surface Vertex Groups -- Number of (X,Y,Z) groups
0,-24,30,
0,-24,0,
0,0,0,
0,0,30;
ShadingProperty:Reflectance ,
Adjacent Blank Facade , !- Name of Surface:Shading Object
0.4, !- Diffuse Solar Reflectance of Unglazed Part of Shading Surface
0.4, !- Diffuse Visible Reflectance of Unglazed Part of Shading Surface
0.0, !- Fraction of Shading Surface That Is Glazed
; !- Name of glazing construction
1.10.61 WindowShadingControl
Window shading with coverings like drapes, blinds, screens or pull-down shades can be used to reduce
the amount of solar radiation entering the window or reduce daylighting glare. It can also be used
to reduce heat loss through the window (movable insulation). Leaving the window covering open in
the winter can maximize solar heat gain and thereby reduce heating loads.
With WindowShadingControl you specify the type, location, and timing of the shading device, what
variable or combination of variables controls deployment of the shading device, and what the control
setpoint is. If the shading device is a blind, you also specify how the slat angle is controlled. Each
WindowShadingControl object is associated with a zone and has a list of one or more windows and
glass doors to which the shading control is applied (ref: FenestrationSurface:Detailed with Type =
Window or GlassDoor, Window, and GlazedDoor).
NOTE: WindowShadingControl does not work with complex fenestration systems. Controlled com-
plex fenestration systems can be made only with Energy Management Systems objects. Refrencing a
FenestrationSurface:Detailed in a WindowShadingControl while using complex fenestration systems
will be ignored by program.
As shown in Figure 1.36, a shading device can be inside the window (Shading Type = Interior-
Shade or InteriorBlind), outside the window (Shading Type = ExteriorShade or ExteriorBlind), or
between panes of glass (Shading Type = BetweenGlassShade or BetweenGlassBlind). The exception
is window screens which can only be outside the window (Shading Type = ExteriorScreen).
When a shading device is present it is either retracted or activated. When it is retracted it covers
none of the window. When it is activated it covers the entire glazed part of the window (but not the
frame). Whether the shading device is retracted or activated in a particular timestep depends on
the control mechanism: see “Shading Control Type,” below. To model a case in which the shading
device, when activated, covers only part of the window you will have to divide the window into two
separate windows, one with the shading device and one without the shading device.
A shading device can also be of a kind in which the optical properties of the glazing switch from
one set of values to another in order to increase or decrease solar or visible transmittance (Shading
Type = SwitchableGlazing).
374 CHAPTER 1. INPUT-OUTPUT REFERENCE
this shaded construction is composed as follows: if the name of the window construction is
CCC and the material name of the shading device is DDD, then the shaded construction name
is CCC:DDD:INT for an interior shading device and CCC:DDD:EXT for an exterior shading
device.
This method is the required if you want to add a shading device to a construction brought in
from a WINDOW Data File (ref:Construction:WindowDataFile).
Note that if both “Name of Construction with Shading” and “Material Name of Shading Device”
are specified, the former takes precedence.
Most Shading Control Types allow you to specify a schedule that determines when the control is
active. One example is a control that is active seasonally. For example, to deploy shading only in
the summer when the incident solar is high enough, use Shading Control Type = OnIfHighSolarOn-
Window with a schedule that is 1 during the summer months and 0 otherwise and specify Shading
Control Is Scheduled = YES.
To deploy one shading device during one time period and another during another time period for
the same window, specify two different WindowShadingControl objects that both reference the same
fenestration. Each of the WindowShadingControl input objects would include the same window on
their lists of fenestration objects, but would reference different schedule input objects. The referenced
schedule input objects should have non-zero values specified at different times for each WindowShad-
ingControl. This approach can be used to add shading that is different for different seasons. When
more than one WindowShadingControl is used for the same window based on schedule, the type
of shading, control type, setpoints, and several other parameters must be the same in the different
WindowShadingControl objects, but the shading device and construction can be different.
In addition, most Shading Control Types also allow you to specify that glare control is active in
addition to the specified Control Type. For example, you might want to deploy shading when
the solar incident on a window is too high OR the glare from the window is too high. This type
of joint control requires that the window be in a daylit zone, that the maximum allowed glare
be specified in the Daylighting object for the zone, and that Glare Control Is Active = YES in
WindowShadingControl.
If Shading Type = InteriorBlind, ExteriorBlind or BetweenGlassBlind you can use WindowShading-
Control to specify how the slat angle of the blind is controlled when the blind is in place.
A special type of WindowShadingControl is SwitchableGlazing. An example is electrochromic glaz-
ing in which the transmittance and reflectance of the glass is controlled electronically. For example,
you could have electrochromic glazing switch from clear (high transmittance) to dark (low trans-
mittance) to control solar gain. If you choose the Shading Type = SwitchableGlazing option for
WindowShadingControl, the unswitched (clear) state is specified by the Construction referenced by
the window and the switched (dark) state is specified by the Construction referenced by Window-
ShadingControl for that window. For example, if you specify Shading Type = SwitchableGlazing
and Shading Control Type = OnIfHighSolarOnWindow, then the glazing will switch to the dark
state whenever the solar radiation striking the window exceeds the Setpoint value.
For Shading Type = SwitchableGlazing the state of the window is either clear (unswitched) or dark
(fully switched) for all Shading Control Types except MeetDaylightIlluminanceSetpoint. In this
case, the transmittance of the glazing is adjusted to just meet the daylight illuminance set point at
the first daylighting reference point (see Daylighting). This type of control assures that there is just
enough solar gain to meet the daylighting requirements in a zone, and no more, thus reducing the
cooling load.
To specify the order of when shades are deployed, the two different approaches can be used:
376 CHAPTER 1. INPUT-OUTPUT REFERENCE
- If shades for each window are independently controlled, than a single WindowShadingControl
object should be used and the Multiple Surface Control Type field should be set to Sequential. The
windows should be specified in the Fenestration Surface N Name fields in the order that they should
be deployed. The Shading Control Sequence Number field is not used being used since only one
WindowShadingControl is used so it can be set to any value or left blank.
- If shades for a group of windows are deployed together and shades for another group of windows
are deployed after that, than multiple WindowShadingControl objects should be used. Each Win-
dowShadingControl should have Multiple Surface Control Type field should be set to Group and the
names of each window in the group should be specified in the Fenestration Surface N Name fields.
The Shading Control Sequence Number in the WindowShadingControl object that controls the first
group of shades should be set to 1. The Shading Control Sequence Number in the WindowShading-
Control object that controls the second group of shades should be set to 2. Any number of additional
groups of shades can be added and Shading Control Sequence Number can be incremented by one
for each group.
It is possible to mix these two approaches. For example, if first a group of shades is controlled together
followed by a sequence of individual windows than these approaches can be combined with the
Multiple Surface Control Type field should be set to Sequential in the second WindowShadingControl
object.
1.10.61.1 Inputs
InteriorBlind: A slat-type shading device, such as a Venetian blind, is on the inside of the window.
(In the shaded Construction the shading layer must be a WindowMaterial:Blind.)
ExteriorBlind: A slat-type shading device is on the outside of the window. (In the shaded Construc-
tion the shading layer must be a WindowMaterial:Blind.)
BetweenGlassBlind: A slat-type shading device is between two glass layers. (In the shaded Con-
struction the shading layer must be a WindowMaterial:Blind.) This shading type is allowed only for
double- and triple-glazing. For triple-glazing the blind must be between the two inner glass layers.
SwitchableGlazing: Shading is achieved by changing the characteristics of the window glass, such as
by darkening it.
SetPoint is unused for Shading Control Type = OnIfScheduleAllows, OnIfHighGlare and Daylight-
Illuminance.
Construction , SINGLE PANE WITH INT SHADE , ! Name of construction with shade
GLASS - CLEAR SHEET 1 / 8 IN , !- First material layer
ROLL SHADE ; !- Second material layer
WindowShadingControl ,
CONTROL ON INCIDENT SOLAR , !- Name
West Zone , !- Zone Name
1, !- Shading Control Sequence Number
InteriorShade , !- Shading Type
SINGLE PANE WITH INT SHADE , !- Name of construction with shading device
OnIfHighSolarOnWindow , !- Shading Control Type
, !- Schedule name
50.0, !- Setpoint {W/m2}
NO , !- Shading Control Is Scheduled
NO , !- Glare Control Is Active
, !- Material Name of Shading Device
, !- Type of Slat Angle Control for Blinds
, !- Slat Angle Schedule Name
, !- Setpoint 2 {W/m2 or deg C}
West Zone_DaylCtrl , !- Daylighting Control Object Name
Sequential , !- Multiple Surface Control Type
Zn001:Wall001:Win001; !- Fenestration Surface 1 Name
FenestrationSurface :Detailed ,
Zn001:Wall001:Win001 , !- SubSurface Name
Window , !- Class
SINGLE PANE WITH NO SHADE , !- Name of construction without shading device
Zn001:Wall001 , !- Base Surface Name
, !- Target
0.5000000 , !- VF to Ground
, !- Frame/Divider name
1.0 , !- Multiplier
4 , !- Number of vertices (assumed rectangular)
0.548 , 0.0 , 2.5 , !- x,y,z of vertices {m}
0.548 , 0.0 , 0.5 ,
5.548 , 0.0 , 0.5 ,
5.548 , 0.0 , 2.5 ;
WindowShadingControl ,
CONTROL ON INCIDENT SOLAR , !- Name
West Zone , !- Zone Name
1, !- Shading Control Sequence Number
InteriorShade , !- Shading Type
, !- Name of shaded construction
OnIfHighSolarOnWindow , !- Shading Control Type
, !- Schedule name
50.0, !- Setpoint {W/m2}
NO , !- Shading Control Is Scheduled
NO , !- Glare Control Is Active
ROLL SHADE , !- Material Name of Shading Device
, !- Type of Slat Angle Control for Blinds
, !- Slat Angle Schedule Name
, !- Setpoint 2 {W/m2 or deg C}
West Zone_DaylCtrl , !- Daylighting Control Object Name
Sequential , !- Multiple Surface Control Type
Zn001:Wall001:Win001; !- Fenestration Surface 1 Name
FenestrationSurface :Detailed ,
Zn001:Wall001:Win001 , !- SubSurface Name
Window , !- Class
SINGLE PANE WITH NO SHADE , !- Name of construction without shade
Zn001:Wall001 , !- Base Surface Name
, !- Target
0.5000000 , !- VF to Ground
, !- Frame/Divider name
1.0 , !- Multiplier
4 , !- Number of vertices (assumed rectangular)
0.548 , 0.0 , 2.5 , !- x,y,z of vertices {m}
0.548 , 0.0 , 0.5 ,
5.548 , 0.0 , 0.5 ,
5.548 , 0.0 , 2.5 ;
1.10.62 WindowProperty:FrameAndDivider
The WindowProperty:FrameAndDivider object is referenced by exterior windows that have
– a frame, and/or
– a divider, and/or
– reveal surfaces that reflect beam solar radiation.
A frame surrounds the glazing in a window (see Figure 1.37 and Figure 1.38). It is assumed that
all frame characteristics—such as width, conductance and solar absorptance—are the same for the
top, bottom and side elements of the frame. If the frame elements are not the same then you should
enter area-weighted average values for the frame characteristics.
The window vertices that you specify in the FenestrationSurface:Detailed object are those of the
glazed part of the window, not the frame. EnergyPlus automatically subtracts the area of the
frame—determined from the glazing dimensions and the frame width—from the area of the wall
containing the window.
384 CHAPTER 1. INPUT-OUTPUT REFERENCE
A divider, as shown in Figure 1.37, Figure 1.38 and Figure 1.39, divides the glazing up into separate
lites. It is assumed that all divider elements have the same characteristics. If not, area-weighted
average values should be used. EnergyPlus automatically subtracts the divider area from the glazed
area of the window.
Reveal surfaces, as shown in Figure 1.40, are associated with the setback of the glazing from the
outside and/or inside surface of the parent wall. If the depth and solar absorptance of these surfaces
are specified, the program will calculate the reflection of beam solar radiation from these surfaces.
The program also calculates the shadowing (onto the window) of beam and diffuse solar radiation
by outside reveal surfaces.
In EnergyPlus, a window can have any combination of frame, divider and reveal surfaces, or none
of these.
The best source of frame and divider characteristics is the WINDOW program, which will calcu-
late the values required by EnergyPlus for different frame and divider types. In particular, the
THERM program within the WINDOW program will calculate the effective conductance of frames
and dividers; this is the conductance taking 2-D heat transfer effects into account.
Note that a window’s frame and divider characteristics, along with other window information, can
be read in from the Window Data File (see “Importing Windows from the WINDOW program”
and “Construction:WindowDataFile object”). In this case the WindowProperty:FrameAndDivider
referenced by the window is not applicable and should be blank unless you want to specify reveal
surfaces for beam solar reflection.
In the illustration above, the divider has two horizontal elements and one vertical element.
1.10.62.1 Inputs
The net effect of beam solar reflected from outside reveal surfaces is to increase the heat gain to the
zone, whereas the effect of beam solar reflected from inside reveal surfaces is to decrease the heat
gain to the zone since part of this reflected solar is transmitted back out the window.
If the window has a frame, the absorption of reflected beam solar by the inside and outside surfaces
of the frame is considered. The shadowing of the frame onto interior reveal surfaces is also considered.
WindowProperty:FrameAndDivider ,
TestFrameAndDivider , ! Frame/Divider Name
0.05, ! Frame Width
0.04, ! Frame Outside Projection
0.03, ! Frame Inside Projection
5.0, ! Frame Conductance
1.3, ! Ratio of Frame -Edge Glass Conductance to Center -Of -Glass Conductance
0.8, ! Frame Solar Absorptance
0.8, ! Frame Visible Absorptance
0.9, ! Frame Thermal Emissivity
DividedLite , ! Divider Type
0.03, ! Divider Width
2, ! Number of Horizontal Dividers
2, ! Number of Vertical Dividers
0.03, ! Divider Outside Projection
0.03, ! Divider Inside Projection
5.0, ! Divider Conductance
1.3, ! Ratio of Divider -Edge Glass Conductance to Center -Of -Glass Conductance
0.8, ! Divider Solar Absorptance
0.8, ! Divider Visible Absorptance
0.9, ! Divider Thermal Emissivity
0.7, ! Outside Reveal Solar Absorptance
0.25, ! Inside Sill Depth (m)
0.6, ! Inside Sill Solar Absorptance
0.2, ! Inside Reveal Depth (m)
0.5; ! Inside Reveal Solar Absorptance
392 CHAPTER 1. INPUT-OUTPUT REFERENCE
Figure 1.40: (a) Vertical section through a window (with frame) showing outside and inside reveal
surfaces and inside sill. (b) Perspective view looking from the outside of a window (without frame)
showing reveal surfaces. Note that “Outside Reveal Depth” is not a user input; it is calculated by
the program from the window and wall vertices.
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 393
1.10.63 WindowProperty:AirflowControl
This object is used to specify the control mechanism for windows in which forced air flows in the gap
between adjacent layers of glass. Such windows are called “airflow windows.” They are also known
as “heat-extract windows” or “climate windows.”
A common application is to reduce the zone load by exhausting indoor air through the window. In
the cooling season this picks up and expels some of the solar heat absorbed by the window glass
(and by the between-glass shade or blind, if present). In the heating season this warms the window,
reducing the heat loss from the window. A side benefit is increased thermal comfort. This is because
the inside surface of the window will generally be cooler in summer and warmer in winter.
The surface output variable “Surface Window Gap Convective Heat Transfer Rate” gives the heat
picked up (or lost) by the gap airflow.
1.10.63.1 Inputs
Figure 1.41: Gap airflow configurations for airflow windows. (a) Air exhaust window: Airflow
Source = InsideAir, Airflow Destination = OutsideAir; (b) Indoor air curtain window: Airflow
Source = InsideAir, Airflow Destination = InsideAir; (c) Air supply window: Airflow Source =
OutsideAir, Airflow Destination = InsideAir; (d) Outdoor air curtain window: Airflow Source
= OutsideAir, Airflow Destination = OutsideAir; (e) Airflow to Return Air: Airflow Source =
InsideAir, Airflow Destination = ReturnAir. Based on “Active facades,” Version no. 1, Belgian
Building Research Institute, June 2002.
396 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.10.64 WindowProperty:StormWindow
This object allows you to assign a movable exterior glass layer (“storm window” or “storm glass”)
that is usually applied to a window in the winter to reduce heat loss and removed in the summer.
A WindowProperty:StormWindow object is required for each window that has an associated storm
window. It is assumed that:
– When the storm glass is in place it is the outermost layer of the window, it covers only the
glazed part of the window and not the frame, and it forms a tight seal. See Figure 1.42.
– When the storm glass is not in place it is completely removed and has no effect on window
heat transfer.
– The gap between the storm glass and rest of the glazing is filled with air.
Figure 1.42: Section through a single-glazed window without (left) and with (right) a storm glass
layer. Not to scale.
With the addition of a storm window, single glazing effectively becomes double glazing, double
glazing becomes triple glazing, etc.
The presence of a storm window is indicated by the output variable “Surface Storm Window On Off
Status” (see “Window Output Variables”). This flag is 0 if the storm window is off, 1 if it is on, and
–1 if the window does not have an associated storm window.
The program automatically creates a window construction (ref: Construction) that consists of the
storm window glass layer and its adjacent air layer added to the original (unshaded, or “bare”)
window construction. In the eplusout.eio file this construction is called BARECONSTRUCTION-
WITHSTORMWIN:n, where n is the number of the associated StormWin object. If the window
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 397
1.10.64.1 Inputs
1.10.64.1.3 Field: Distance Between Storm Glass Layer and Adjacent Glass
The separation between the storm glass and the rest of the window (Figure 1.42). It is measured
from the inside of the storm glass layer to the outside of the adjacent glass layer.
1.10.64.1.7 Field: Day of Month that Storm Glass Layer Is Taken Off
The day of the month that the storm window is removed. It is assumed that the storm window is
removed at the beginning of this day, i.e., during the first simulation timestep of the day, and stays
off until the month and day given by Month that Storm Glass Layer Is Put On, Day of Month that
Storm Glass Layer Is Put On.
In the northern hemisphere, the month the storm window is put on is generally greater than the
month it is taken off (for example put on in month 10, when it starts to get cold, and taken off in
month 5, when it starts to warm up). In the southern hemisphere this is reversed: month on is less
than month off.
An IDF example of WindowProperty:StormWindow. The storm window is put in place on October
15 and removed on May 1.
WindowProperty:StormWindow ,
Window1 , !- Name of Window to Which Storm Window Glass Layer is Applied
GlassA , !- Name of Material:WindowGlass or MATERIAL:WindowGlass:AltInput that is the storm
window layer
0.060 , !- Distance from storm window to adjacent glass (m)
10, !- Month that Storm Window Is Put On
15, !- Day of Month that Storm Window Is Put On
5, !- Month that Storm Window Is Taken Off
1; !- Day of Month that Storm Window Is Taken Off
WINDOW v6.3 and later is capable of writing IDF excerpts for Window data. This is the
preferred method as no external file is necessary. See the Tips document for details on obtaining
the IDF excerpt.
The WINDOW program calculates the U-value, Solar Heat Gain Coefficient, solar transmission/ab-
sorption characteristics, visible transmission characteristics and other properties of a window under
standard indoor and outdoor conditions. WINDOW treats the whole window system—glazing,
frame and divider. A sub-program of WINDOW called THERM uses a 2-D finite element calcula-
tion to determine the effective conductance of frame, divider and edge-of-glass elements. Another
sub-program, OPTICS, determines the solar-optical properties of glazing, including laminates and
coated glass.
WINDOW can write a data file containing a description of the window that was analyzed. An
example of this file (which is no longer the preferred method) is shown in the Tips document under
WINDOW generated files. is shown below. This file, which can be named by the user, can be
read by EnergyPlus. For more complete description and examples, see the object description –
Construction:WindowDataFile.
In this way, the same window that was created in WINDOW can be imported into EnergyPlus for
annual energy analysis without having to re-input the window data. To obtain WINDOW, THERM,
or OPTICS go to http://windows.lbl.gov and choose the software link. A major advantage of using
WINDOW to create window input for EnergyPlus is that you will have direct access to WINDOW’s
expanding database of over 1000 different glass types; and you will be able to browse through this
database according to different criteria (color, transmittance, solar heat gain coefficient, etc.) to
help you select the best glass type for your application.
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 399
Although WINDOW writes only one window entry on the WINDOW data file, EnergyPlus users
can combine two or more of these files to end up with a single data file with multiple window entries
of different types. In this way a library of windows from WINDOW can be built up if so desired.
If you combine files like this you should be sure not to leave out or change any of lines from the
original files.
There are four methods for inputting window constructions in EnergyPlus:
Note: When using method 4, the overall glazing system angular dependent prop-
erties, including Tsol, Abs, Rfsol, Rbsol, Tvis, Rfvis, and Rbvis, are not used by
EnergyPlus. Therefore, methods 1 and 2 and preferably 3 are recommended.
– The SHGC calculations in EnergyPlus for window layers input using full spectral data use
a spectral weighting data set (derived from Optics5 data file ISO-9845GlobalNorm.std) that
is different from the WINDOW default spectral weighting data set (W5_NFRC_2003.std).
This difference accounts for most of the variation in SHGC values reported by EnergyPlus and
WINDOW for full spectral data window layer input. This variation is more pronounced for
window constructions of three glass layers or more.
– Users intending to select a window construction based on SHGC value for energy code compli-
ance should base their selection on the value reported by WINDOW since this is the officially
recognized value.
In EnergyPlus, the Window data file is searched for each “Construction:WindowDataFile” object in
the EnergyPlus input. This object has a very simple form:
Construction:WindowDataFile ,
ConstructionName ,
FileName; ! Default is Window5DataFile.dat in the "run" folder.
If there is a window called ConstructionName on the Window data file, the data for that window
is read from the file and the following EnergyPlus objects and their names are created. The “W5”
prefixed to these names indicates that the object originated in the Window data file.
In addition to the canned Surface reports (view the Reports section later in this document) and
surface variables (above), the following variables are available for all zones:
Zone ,Sum ,Zone Total Internal Radiant Heating Energy [J]
Zone ,Sum ,Zone Total Internal Visible Radiation Heating Energy [J]
Zone ,Sum ,Zone Total Internal Convective Heating Energy [J]
Zone ,Sum ,Zone Total Internal Latent Gain Energy [J]
Zone ,Sum ,Zone Total Internal Total Heating Energy [J]
Zone ,Average ,Zone Mean Air Temperature [C]
HVAC ,Average ,Zone Air Temperature [C]
Zone ,Average ,Zone Mean Radiant Temperature [C]
Zone ,Average ,Zone Operative Temperature [C]
Zone ,Average ,Zone Heat Index [C]
Zone ,Average ,Zone Humidity Index [C]
HVAC ,Sum ,Zone Air System Sensible Heating Energy [J]
HVAC ,Sum ,Zone Air System Sensible Cooling Energy [J]
HVAC ,Average ,Zone Air System Sensible Heating Rate [W]
HVAC ,Average ,Zone Air System Sensible Cooling Rate [W]
HVAC ,Average ,Zone Air Humidity Ratio[kgWater/kgDryAir]
HVAC ,Average ,Zone Air Relative Humidity [%]
These two variable outputs are/should be identical. However, note that they can be reported at
different time intervals. “Zone Mean Air Temperature” is only available on the Zone/HB timestep
(Number of Timesteps per Hour) whereas “Zone Air Temperature” can be reported at the HVAC
timestep (which can vary).
From the code definition, the zone mean air temperature is the average temperature of the air
temperatures at the system timestep. Remember that the zone heat balance represents a “well
stirred” model for a zone, therefore there is only one mean air temperature to represent the air
temperature for the zone.
This is very similar to the mean air temperature in the last field. The “well stirred” model for the
zone is the basis, but this temperature is also available at the “detailed” system timestep.
The Mean Radiant Temperature (MRT) in degrees Celsius of a space is really the measure of the
combined effects of temperatures of surfaces within that space. The larger the surface area and the
closer one is to it, the more effect the surface temperature of that surface has on each other. The
MRT is the measure of all these surface areas and temperatures.
1.10. GROUP – THERMAL ZONE DESCRIPTION/GEOMETRY 401
Zone Operative Temperature (OT) is the average of the Zone Mean Air Temperature (MAT) and
Zone Mean Radiant Temperature (MRT), OT = 0.5*MAT + 0.5*MRT. This output variable is not
affected by the type of thermostat controls in the zone, and does not include the direct effect of high
temperature radiant systems. See also Zone Thermostat Operative Temperature.
Zone heat index (HI) is an index that combines air temperature and relative humidity in shaded
areas, to posit a human-perceived equivalent temperature, as how hot it would feel if the humidity
were some other value in the shade. The HI measures the temperature feels like to the human body
when relative humidity is combined with the air temperature. Zone Heat Index is only reported
when ThermalResilienceSummary is declared in Output:Table:SummaryReports.
The Humdity Index (humidex) is an index number used by Canadian meteorologists to describe
how hot the weather feels to the average person, by combining the effect of heat and humidity.
The humidex is a nominally dimensionless quantity (though generally recognized by the public as
equivalent to the degree Celsius) based on the dew-point temperature. Zone Humdity Index is only
reported when ThermalResilienceSummary is declared in Output:Table:SummaryReports.
This field represents the sensible heating energy in Joules that is actually supplied by the system to
that zone for the timestep reported. This is the sensible heating rate multiplied by the simulation
timestep. This is calculated and reported from the Correct step in the Zone Predictor-Corrector
module. This field is not multiplied by zone or group multipliers.
Zone Air System Sensible Heating (and Cooling) Energy (and Rate) all report the heating or
cooling delivered by the HVAC system to a zone. These values are calculated by multiplying
the supply air mass flow rate by the difference between the supply air temperature and the zone
air temperature. This does not always indicate the operation of heating or cooling coils. For
example, cooling will be reported if the supply air is cooled due to the introduction of outside
air, even if all coils are off.
Note that these variables are calculated at the system timestep. When reported at the “detailed”
reporting frequency, these variable will never show heating and cooling both in the same system
timestep. If reported at a frequency less than “Detailed” (for example, Hourly) values may
appear in both the heating and cooling variable for the same hour if the system cooled the zone
for part of the reporting period and heated the zone for another part of the reporting period.
This field represents the sensible cooling energy in Joules that is actually supplied by the system to
that zone for the timestep reported. This is the sensible cooling rate multiplied by the simulation
402 CHAPTER 1. INPUT-OUTPUT REFERENCE
timestep. This is calculated and reported from the Correct step in the Zone Predictor-Corrector
module. This field is not multiplied by zone or group multipliers.
This field represents the sensible heating rate in Watts that is actually supplied by the system to
that zone for the timestep reported. This is calculated and reported from the Correct step in the
Zone Predictor-Corrector module. This field is not multiplied by zone or group multipliers. The
Zone Air System Sensible Heating Rate may not agree exactly with the equipment-level delivered
energy transfer rate when the zone temperature is changing significantly over a timestep (e.g. during
thermostat setback and setup), but the energy will balance out over time.
This field represents the sensible cooling rate in Watts that is actually supplied by the system to
that zone for the timestep reported. This is calculated and reported from the Correct step in the
Zone Predictor-Corrector module. This field is not multiplied by zone or group multipliers. The
Zone Air System Sensible Cooling Rate may not agree exactly with the equipment-level delivered
energy transfer rate when the zone temperature is changing significantly over a timestep (e.g. during
thermostat setback and setup), but the energy will balance out over time.
This field represents the air humidity ratio after the correct step for each zone. The humidity ratio
is the mass of water vapor to the mass of dry air contained in the zone in (kg water/kg air) and is
unitless.
This field represents the air relative humidity ratio after the correct step for each zone. The relative
humidity is in percent and uses the Zone Air Temperature, the Zone Air Humidity Ratio and the
Outside Barometric Pressure for calculation.
This field represents the sum of radiant gains from specific internal sources (e.g. equipment) through-
out the zone in joules. This includes radiant gain from People, Lights, Electric Equipment, Gas
Equipment, Other Equipment, Hot Water Equipment, and Steam Equipment.
This field expresses the sum of heat gain in joules that is the calculated short wavelength radiation
gain from lights in the zones. This calculation uses the total energy from lights and the fraction
visible to realize this value, summed over the zones in the simulation.
1.11. GROUP – ADVANCED SURFACE CONCEPTS 403
This field represents the sum of convective gains from specific sources (e.g. equipment) throughout
the zone in joules. This includes convective gain from People, Lights, Electric Equipment, Gas
Equipment, Other Equipment, Hot Water Equipment, and Steam Equipment.
This field represents the sum of latent gains from specific internal sources (e.g. equipment) throughout
the zone in joules. This includes latent gain from People, Electric Equipment, Gas Equipment, Other
Equipment, Hot Water Equipment, and Steam Equipment.
This field represents the sum of all heat gains throughout the zone in joules. This includes all
heat gains from People, Lights, Electric Equipment, Gas Equipment, Other Equipment, Hot Water
Equipment, and Steam Equipment.
1.11.1 SurfaceProperty:HeatTransferAlgorithm
This object, and three other related objects, can be used to control which surface heat transfer
model is used on specific surfaces. The separate object called HeatBalanceAlgorithm is used to
control the heat transfer model in an overall way while this object can be used to revise the algo-
rithm selections for specific surfaces. This object allows selectively overriding the global setting in
HeatBalanceAlgorithm to choose one of the following models for a particular surface:
1.11.1.1 Inputs
– ConductionTransferFunction
– MoisturePenetrationDepthConductionTransferFunction
– ConductionFiniteDifference
– CombinedHeatAndMoistureFiniteElement
1.11.2 SurfaceProperty:HeatTransferAlgorithm:MultipleSurface
This object can be used to control the surface heat transfer model used for specific types of surfaces.
The separate object called HeatBalanceAlgorithm is used to control the heat transfer model in an
overall way while this object can be used to revise the algorithm selections for specific types of
surfaces. This object allows selectively overriding the global setting in HeatBalanceAlgorithm to
choose one of the following models for all surfaces of a particular type:
1.11.2.1 Inputs
– ConductionTransferFunction
– MoisturePenetrationDepthConductionTransferFunction
– ConductionFiniteDifference
– CombinedHeatAndMoistureFiniteElement
1.11.3 SurfaceProperty:HeatTransferAlgorithm:SurfaceList
This object can be used to control the surface heat transfer model used for a list of surfaces. The
separate object called HeatBalanceAlgorithm is used to control the heat transfer model in an overall
way while this object can be used to revise the algorithm selections for a list of specific surfaces.
This object allows selectively overriding the global setting in HeatBalanceAlgorithm to choose one
of the following models for listed:
1.11.3.1 Inputs
– ConductionTransferFunction
– MoisturePenetrationDepthConductionTransferFunction
– ConductionFiniteDifference
– CombinedHeatAndMoistureFiniteElement
406 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.11.4 SurfaceProperty:HeatTransferAlgorithm:Construction
This object can be used to control the surface heat transfer model used for surfaces that have a
specific type of construction. The separate object called HeatBalanceAlgorithm is used to control
the heat transfer model in an overall way while this object can be used to revise the algorithm
selections for specific constructions. This object allows selectively overriding the global setting in
HeatBalanceAlgorithm to choose one of the following models for all surfaces with particular type of
construction:
1.11.4.1 Inputs
– ConductionTransferFunction
– MoisturePenetrationDepthConductionTransferFunction
– ConductionFiniteDifference
– CombinedHeatAndMoistureFiniteElement
1.11. GROUP – ADVANCED SURFACE CONCEPTS 407
1.11.5 SurfaceControl:MovableInsulation
Movable insulation can be used/scheduled on any surface regular surface (such as a wall, floor,
roof, etc.) but not on a subsurface (such as a window, use WindowShadingControl instead). With
movable insulation, no reference is made in the surface that is using the insulation – rather the
movable insulation statement references the surface to which it is applied.
Exterior and interior movable insulation have undergone some testing and appears to producing
expected results. The underlying principle has been implemented in EnergyPlus for both interior
and exterior movable insulation with the possibility for exterior movable insulation to be transparent
(transparent insulation material or TIM).
TIM exterior layers can be used with the ConductionFiniteDifference (CondFD) solution algorithm.
With this addition, TIM layers can be used in conjunction with wall layers that have phase change
materials (PCM) included, or any other advanced capability of the CondFD algorithm such as
variable conductivity. The input requirements are exactly the same as when used with the CTF
algorithm. The Solution Algorithm needs to be changed to CondFD, and as with CTF, the “Sur-
faceControl:MovableInsulation” object must be completed to specify the insulated surface and the
“WindowMaterial:Glazing” or “WindowMaterial:Glazing:EquivalentLayer” object is needed to pro-
vide the TIM layer properties.
Basically, the addition of movable insulation allows the user to schedule an extra amount of insu-
lation on either the inside or outside surface of a wall (or both). The insulation must be a simple,
homogenous material layer (linked to a material definition within the input data file). Note that En-
ergyPlus allows the exterior movable insulation layer to be transparent to short wavelength radiation
(solar). In this case, incident solar is split between the plane between the movable insulation and
the surface and the plane between the movable insulation and the surrounding air. This calculation
is fairly basic and based on the solar transmittance of the insulation layer (material properties).
Using transparent layers for exterior movable insulation allows solar energy to penetrate deeper into
a construction where it can be stored for later use in the building (similar in concept to a Trombe
Wall).
This field determines whether the movable insulation is applied to the inside or the outside of the
surface by entering either “Inside” or “Outside”, respectively.
408 CHAPTER 1. INPUT-OUTPUT REFERENCE
This field refers the movable insulation back to a particular surface (ref: Building Surfaces) via its
user assigned name so that EnergyPlus knows where to apply this extra layer of insulation. This
will affect either the inside or outside surface heat balance of this surface depending on the value in
the insulation type field (see previous field).
This field is a schedule that theoretically can be any positive real number but was originally intended
to be a parameter between 0.0 and 1.0. Its purpose is to act as a fractional modifier on the resistance
of the material layer. The actual thermal resistance of the movable insulation is equal to the resistance
of the material layer times the current value in the movable insulation schedule. A value of 0.0 simply
means that the movable insulation is not present.
An example of this syntax implemented in an input file is:
SurfaceControl:MoveableInsulation ,
Exterior , ! Insulation Type
Zone001:Wall001 , ! Surface Name
TransparentInsulationMaterial , ! Material Name
PresentInWinterSchedule ; ! Schedule Name
1.11.6 SurfaceProperty:OtherSideCoefficients
By referencing the Other Side Coefficients statement in the surface statements (i.e. Outside Bound-
ary Condition), the temperature of the outer plane of a surface (see Figure 1.43) can be directly
controlled. Other side coefficients can also be used to control the exterior convective heat transfer
coefficient of a surface and the corresponding exterior air temperature. It should be noted that solar
effects are not accounted for when other side coefficients are used. In addition, if other side coeffi-
cients are specified for a surface, they also hold for subsurfaces of that surface (though subsurfaces
can have their own coefficient set).
other side coefficients have the same effect on all types of heat transfer surfaces. In other words,
an interior surface with other side coefficients specified and an exterior wall with identical other
side coefficients specified are simulated exactly the same. A surface that uses other side coefficients
should be thought of as a new or separate type of surface. All heat transfer surfaces are simulated
in the same manner through conduction transfer functions. The only difference between the various
types of heat transfer surfaces is the environment on the other side of the surface. For example, the
1.11. GROUP – ADVANCED SURFACE CONCEPTS 409
other side environment of an exterior surface is the outdoor environment. For an interior surface,
the temperature of the outer plane of the surface is set equal to the temperature of the inner plane
of the surface. Similarly, a surface with other side coefficients specified will allow the user to control
the other side environment.
Heat transfer through a surface is an extremely important component in the calculation of zone
loads. The information to calculate this heat transfer is readily available if the surface is exposed
to the outdoor environment or to another zone that is being simulated. Occasionally, a user will
want to model the heat transfer through a surface that is adjacent to an area that is not included
in the EnergyPlus model. For example, an office area is attached to a warehouse and the user is
only interested in simulating the office area. An interior surface with other side coefficients specified
could be used to control the environment on the other side of the surface, thereby accounting for
the heat transfer through the adjoining surface.
Other Side Coefficients affects the “other side” of a surface as described below. Each coefficient
has a special meaning. You may enter a 0 or blank if you are not using a particular coefficient.
Note that there are two potential ways to use other side coefficients. Either they are used to set
the temperature of the exterior side surface directly (if the combined convective/radiative coefficient
below is less than or equal to zero) or to set both the film coefficient (positive value for the combined
convective/radiative coefficient below) and the outside air temperature.
1.11.6.1 Inputs
(time of day)
C2 = Sin 2π (1.19)
(period)
The value for “period” is controlled in the following field. The value for “time of day” is based on
the zone timestep and is in units of hours. The sine function here uses input as radians. When using
this option, the value for C2 will vary between -1.0 and 1.0 and the value put in the field Constant
Temperature Coefficient is not used. This option cannot be used at the same time as scheduling a
constant temperature with the previous field.
1.11. GROUP – ADVANCED SURFACE CONCEPTS 411
where:
T = Outside Air Temperature when C1 (Combined convective/radiative film Coeff) > 0
T = Exterior Surface Temperature when C1 (Combined convective/radiative film Coeff) < = 0
Tzone = Temperature of the zone being simulated (°C)
Toadb = Dry-bulb temperature of the outdoor air (°C)
Tgrnd = Temperature of the ground (°C) from Site:GroundTemperature:BuildingSurface
Wspd = Outdoor wind speed (m/sec)
Tpast = Other side temperature from previous zone timestep (°C)
! Example input using temperature schedule
SurfaceProperty:OtherSideCoefficients ,
OSCCoef:Zn005:Wall003 , !- Name
0, !- Combined Convective/Radiative Film Coefficient {W/m2 -K}
0.000000 , !- Constant Temperature {C}
1.000000 , !- Constant Temperature Coefficient
0.000000 , !- External Dry -Bulb Temperature Coefficient
0.000000 , !- Ground Temperature Coefficient
0.000000 , !- Wind Speed Coefficient
0.000000 , !- Zone Air Temperature Coefficient
Zn005Wall003OtherSideTempSched ; !- Constant Temperature Schedule Name
! Example input for outside heat transfer coefficient of 1.23, using Toadb
SurfaceProperty:OtherSideCoefficients ,
OSCCoef:Zn005:Wall004 , !- Name
1.230000 , !- Combined Convective/Radiative Film Coefficient {W/m2 -K}
0.000000 , !- Constant Temperature {C}
412 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.11.6.2 Outputs
Zone ,Average ,Surface Other Side Coefficients Exterior Air Drybulb Temperature
1.11.7 SurfaceProperty:OtherSideConditionsModel
By referencing the Other Side Conditions Model statement in the surface statements (i.e. Outside
Boundary Condition), the boundary conditions for the outer plane of the mass wall can be connected
to the appropriate model for various multi-skin components. The types of multi-skin components
that use this object include systems that are mounted to the outside surface using standoffs that
create a small air gap – see Figure 1.44. This type of modeling allows using the usual heat transfer
calculations for the underlying surface with other types of multi-skin component models that are
available including: unglazed transpired solar collectors, ventilated photovoltaic panels, and naturally
ventilated facades.
1.11. GROUP – ADVANCED SURFACE CONCEPTS 413
The boundary condition values are determined dynamically by the program using internal component
models. If you want to define other side surface temperatures or convection conditions, then use
SurfaceProperty:OtherSideCoefficients instead of this object.
It should be noted that when other side conditions models are used, solar effects are removed from
the surface’s outside face heat balance but are used in modeling the component adjacent to that
surface.
The other side conditions model also includes underground piping system interaction. The Pip-
ingSystem:Underground:Domain object represents a mass of ground which may include interaction
with, for example, basement surfaces. In this case, the ground model will internally use the other
side condition model hook to update boundary conditions for those surfaces which use that other
side condition model name reference.
The other side conditions model also includes an underwater boundary condition connection. By
specifying “ConvectiveUnderwater” as the boundary type, and including any number of “Surface-
Property:Underwater” objects in the input, the user can connect surfaces to water such as for a
moving vessel.
1.11.7.1 Inputs
SurfaceProperty:OtherSideConditionsModel ,
UTSC OSCM ZN11 , ! OtherSideConditionsModel Name
GapConvectionRadiation ; ! Type of Modeling used to determine Boundary Conditions
1.11.7.2 Outputs
1.11.7.2.4 Surface Other Side Conditions Modeled Radiation Heat Transfer Co-
efficient [W/m2-K]
This is the effective (Linearized) radiation heat transfer coefficient applied to the other side of the
surface by the model.
1.11.8 SurfaceProperty:Underwater
This object captures the inputs required to model a water-connected boundary condition for a
surface. This model is useful for either statically positioned buildings with natural convection to the
water boundary condition, or a moving building (vessel).
1.11.8.1 Inputs
SurfaceProperty:Underwater ,
Underwater , !- Name
140, !- Distance from Surface Centroid to Leading Edge of Boundary Layer
WaterTempSchedule , !- Free Stream Water Temperature Schedule
VelocitySchedule; !- Free Stream Water Velocity Schedule
Schedule:Constant ,
WaterTempSchedule ,
Any Number ,
23;
Schedule:Constant ,
VelocitySchedule ,
Any Number ,
10.2;
1.11.9 Foundation:Kiva
Foundation:Kiva objects describe boundary conditions for ground-coupled foundation surfaces. Sur-
faces with the “Outside Boundary Condition” defined as “Foundation”, may also refer to a Founda-
tion:Kiva object in the “Outside Boundary Condition Object” field (if unspecified, a default Foun-
dation:Kiva object will be created and applied).
Limitations when using Foundation:Kiva objects include:
– Only floors and walls may use Foundation:Kiva objects as Outside Boundary Conditions.
– For a given zone, each floor surface must reference a different Foundation:Kiva object. In
other words, multiple foundation floor surfaces may exist in the same thermal zone so long as
they reference separate Foundation:Kiva objects. The same Foundation:Kiva object may be
referenced by multiple floors so long as they are in different zones.
– Any number of wall surfaces may reference a single Foundation:Kiva object so long as that
object is referenced by exactly one floor surface in the same thermal zone.
– Foundation wall surfaces that are not triangular or quadrilateral may not translate well into
the two-dimensional finite difference context.
For each floor surface with “Foundation” set as the “Outside Boundary Condition” there must also
be a corresponding “SurfaceProperty:ExposedFoundationPerimeter” object to define how much of
the floor perimeter is below exterior walls.
The inputs from Foundation:Kiva objects are translated into Kiva’s foundation heat transfer model.
KivaTM generates a two-dimensional heat transfer calculation to represent heat flow between a zone
and the adjacent ground. Foundation:Kiva surfaces do not use the same HeatBalanceAlgorithm
(e.g., Conduction Transfer Functions) as the rest of the model.
Foundation:Kiva objects are used to describe the two-dimensional features that cannot be captured
by the typical one-dimensional constructions used in EnergyPlus. Figure 1.45 illustrates Kiva’s two-
dimensional context for a basement where the basement slab and wall both refer to “Foundation”
as the Outside Boundary Condition, the ceiling of the basement and the exterior wall of the zone
above the basement refer to “Surface” (or “Zone”) and “Outdoors”, respectively. Note: Not all of
the foundation wall surface needs to be below grade (see the “Wall Height Above Grade” field for
this object). Any part of the foundation wall above grade is modeled in Kiva’s two-dimensional heat
transfer calculations. The non-foundation surfaces are shown in Figure 1.45 for context, but are not
part of the Kiva model.
1.11. GROUP – ADVANCED SURFACE CONCEPTS 417
Figure 1.45: Outside Boundary Conditions for surfaces within Kiva’s Two-dimensional context.
Only surfaces referencing “Foundation” are simulated in Kiva
This context allows for a finer description of the structural and insulation components of a foundation
that impact heat transfer (Figure 1.46).
Foundation:Kiva objects define only the aspects of the foundation that are not already defined by
the one-dimensional constructions of the respective surfaces. That is, the footing wall and slab
constructions and their relative dimensions are inferred from the respective Surface objects (see
Figure 1.47).
The depth of the foundation is defined by the height of the wall surfaces that reference the Founda-
tion:Kiva boundary condition object. For slab-on-grade foundations, a depth of zero is implied by
having no associated wall surfaces. Figure 1.48 shows a slab-on-grade foundation with whole slab
insulation. Notice there are no walls referencing the “Foundation” Outside Boundary Condition. In
this case, the under-slab insulation is modeled as part of the slab construction, while the edge/gap
insulation is modeled using the interior vertical insulation fields of a Foundation:Kiva object. Note:
Since there are no wall surfaces for slab foundations, the footing wall construction is defined within
the Foundation:Kiva object (or defaulted to a 0.3m wide cast concrete wall).
A walkout basement (with a variable grade along the sides; see Figure 1.49) is best modeled using
discrete quadrilateral surfaces of stepped height for the walls as shown in Figure 1.50.
The width of the floor surface in the two-dimensional context is defined by the area and the exposed
perimeter (see SurfaceProperty:ExposedFoundationPerimeter) of the floor surface object. Details on
this calculation can be found in the Engineering Reference document.
Other components of the two-dimensional context are defined by the Foundation:Kiva:Settings object
and applied uniformly for all instances of Foundation:Kiva objects. These components include:
– Far-Field width
– Deep Ground depth (and boundary type)
– Soil and ground surface thermal properties
BuildingSurface:Detailed ,
Slab Floor , !- Name
Floor , !- Surface Type
Slab Construction , !- Construction Name
Living Room , !- Zone Name
Foundation , !- Outside Boundary Condition
Slab Details , !- Outside Boundary Condition Object
No , !- Sun Exposure
No , !- Wind Exposure
0.0, !- View Factor to Ground
4, !- Number of Vertices
0.0, 0.0, 0.0, !- Vertex 1
0.0, 20.0, 0.0, !- Vertex 2
20.0, 20.0, 0.0, !- Vertex 3
20.0, 0.0, 0.0; !- Vertex 4
Foundation:Kiva ,
Slab Details , !- Name
, !- Initial Indoor Air Temperature
XPS , !- Interior Horizontal Insulation Material Name
0.2, !- Interior Horizontal Insulation Depth
0.6, !- Interior Horizontal Insulation Width
XPS , !- Interior Vertical Insulation Material Name
0.2, !- Interior Vertical Insulation Depth
, !- Exterior Horizontal Insulation Material Name
, !- Exterior Horizontal Insulation Depth
, !- Exterior Horizontal Insulation Width
, !- Exterior Vertical Insulation Material Name
, !- Exterior Vertical Insulation Depth
0.2, !- Wall Height Above Grade
0.3, !- Wall Depth Below Slab
Slab Footing Construction; !- Footing Wall Construction Name
Material ,
XPS , !- Name
Rough , !- Roughness
0.05, !- Thickness
0.029 , !- Conductivity
28, !- Density
1450, !- Specific Heat
0.9, !- Thermal Absorptance
0.7, !- Solar Absorptance
0.7; !- Visible Absorptance
420 CHAPTER 1. INPUT-OUTPUT REFERENCE
Figure 1.50: Walkout basement wall and floor surfaces (in gray) all reference the same Founda-
tion:Kiva object
422 CHAPTER 1. INPUT-OUTPUT REFERENCE
Material ,
Concrete , !- Name
Rough , !- Roughness
0.3, !- Thickness
1.95, !- Conductivity
2400, !- Density
900, !- Specific Heat
0.9, !- Thermal Absorptance
0.7, !- Solar Absorptance
0.7; !- Visible Absorptance
Construction ,
Slab Footing Construction , !- Name
Concrete; !- Outside Layer Name
1.11.9.2 Inputs
Figure 1.55: Definition of exterior grade and footing wall depth relative to the wall surface (for a
basement foundation context)
426 CHAPTER 1. INPUT-OUTPUT REFERENCE
Figure 1.56: Definition of exterior grade and footing wall depth relative to the wall surface (for a
slab foundation context)
1.11.9.3 Outputs
Output for surfaces with a Foundation boundary condition type will include all opaque surface
output variables except:
428 CHAPTER 1. INPUT-OUTPUT REFERENCE
Figure 1.58: Custom blocks representing interior batt insulation and dry wall
1.11.10 Foundation:Kiva:Settings
This object defines settings applied across all Kiva foundation calculations. This object is not
required. If it is not defined, all defaults will be applied.
1.11.10.1 Inputs
Concrete 0.002
Brick 0.003
Soil 0.005
Gravel 0.012
Grass 0.030
– ZeroFlux
– GroundWater
– Autoselect
ZeroFlux applies a zero vertical heat flux (i.e. adiabatic) boundary condition. GroundWater applies a
constant temperature boundary condition, with a temperature equal to the average outdoor air dry-
bulb temperature from the environment(s). Autoselect applies either boundary condition depending
on the elevation of the building site (Williams and Williamson, 1989):
If dwt ≤ 40 m., the GroundWater boundary is applied, otherwise a ZeroFlux boundary is applied
at 40 m. If the calculated ground water depth is shallower than any element of the foundation
construction, then the GroundWater is applied at 1 m below the lowest element.
Default: Autoselect.
1.11.11 SurfaceProperty:ExposedFoundationPerimeter
This object (currently only used in conjunction with Foundation:Kiva boundary conditions) defines
the perimeter of a foundation floor that is exposed to the exterior environment through the floor.
The user may either define the total exposed perimeter, the fraction of the total perimeter that
is exposed, or individually define which segments of the floor surface perimeter are exposed. This
object is required for any floor surface with a Foundation:Kiva boundary condition.
Figure 1.61 illustrates how the exposed perimeter is determined from a floor plan of the foundation
level.
Some buildings may have neighboring zones with different foundation types. For example, a
crawlspace next to a garage with a slab (Figure 1.62). The foundation wall in this case is NOT
considered part of either floor’s exposed perimeter, and should not reference a Foundation boundary
condition. Kiva does not calculate heat flow between two zones through ground. In this case, it is
best to approximate interior foundation wall using an Adiabatic Outside Boundary Condition.
1.11.11.1 Inputs
– BySegment: Each segment of the floor polygon (corresponding to distance between each set of
vertices) is defined as exposed (“Yes”) or not exposed (“No”) in an extensible list corresponding
to the number of vertices in the floor polygon. Exposed perimeter is defined as the sum of all
exposed segment lengths. (The Surface Segment <x> Exposed fields should be filled.) Note:
The number of segments identified in this object must match the number of vertices in the
corresponding surface object.
1.11.12 SurfaceConvectionAlgorithm:Inside:AdaptiveModelSelections
This object provides options to change the individual convection model equations for dynamic selec-
tion when using AdaptiveConvectionAlgorithm. This object is only needed to make changes to the
default model selections for any or all of the surface categories. This object is for the inside face, the
side of the surface facing a thermal zone.
1.11.12.1 Inputs
1.11.12.1.9 Field: Simple Buoyancy Stable Tilted Equation User Curve Name
The SurfaceConvectionAlgorithm:UserCurve named in this field is used when the previous field is
set to UserCurve.
1.11.12.1.14 Field: Floor Heat Ceiling Cool Vertical Wall Equation Source
Applies to zone with in-floor heating and/or in-ceiling cooling. This is for vertical walls. The
key choice options include: ASHRAEVerticalWall, AlamdariHammondVerticalWall, Khali-
faEq3WallAwayFromHeat, FohannoPolidoriVerticalWall, ISO15099Windows, or UserCurve.
1.11.12.1.15 Field: Floor Heat Ceiling Cool Vertical Wall Equation User Curve
Name
The SurfaceConvectionAlgorithm:UserCurve named in this field is used when the previous field is
set to UserCurve.
1.11.12.1.16 Field: Floor Heat Ceiling Cool Stable Horizontal Equation Source
Applies to zone with in-floor heating and/or in-ceiling cooling. This is for passive horizontal surfaces
with heat flow for stable thermal stratification. The key choice options include: WaltonStableHori-
zontalOrTilt, AlamdariHammondStableHorizontal, or UserCurve.
1.11.12.1.17 Field: Floor Heat Ceiling Cool Stable Horizontal Equation User
Curve Name
The SurfaceConvectionAlgorithm:UserCurve named in this field is used when the previous field is
set to UserCurve.
1.11.12.1.19 Field: Floor Heat Ceiling Cool Unstable Horizontal Equation User
Curve Name
The SurfaceConvectionAlgorithm:UserCurve named in this field is used when the previous field is
set to UserCurve.
1.11.12.1.20 Field: Floor Heat Ceiling Cool Heated Floor Equation Source
Applies to zone with in-floor heating and/or in-ceiling cooling. This is for a floor with active heating
elements. The key choice options include: WaltonUnstableHorizontalOrTilt, AlamdariHammon-
dUnstableHorizontal, AwbiHattonHeatedFloor, or UserCurve
1.11.12.1.21 Field: Floor Heat Ceiling Cool Heated Floor Equation User Curve
Name
The SurfaceConvectionAlgorithm:UserCurve named in this field is used when the previous field is
set to UserCurve.
436 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.11.12.1.22 Field: Floor Heat Ceiling Cool Chilled Ceiling Equation Source
Applies to zone with in-floor heating and/or in-ceiling cooling. This is for a ceiling with active
cooling elements. The key choice options include: WaltonUnstableHorizontalOrTilt, AlamdariHam-
mondUnstableHorizontal, KaradagChilledCeiling, or UserCurve.
1.11.12.1.23 Field: Floor Heat Ceiling Cool Chilled Ceiling Equation User Curve
Name
The SurfaceConvectionAlgorithm:UserCurve named in this field is used when the previous field is
set to UserCurve
1.11.12.1.24 Field: Floor Heat Ceiling Cool Stable Tilted Equation Source
Applies to zone with in-floor heating and/or in-ceiling cooling. This is for tilted surfaces with heat
flow for stable thermal stratification. The key choice options include: WaltonStableHorizontalOrTilt,
AlamdariHammondStableHorizontal, ISO15099Windows, or UserCurve.
1.11.12.1.25 Field: Floor Heat Ceiling Cool Stable Tilted Equation User Curve
Name
The SurfaceConvectionAlgorithm:UserCurve named in this field is used when the previous field is
set to UserCurve.
1.11.12.1.26 Field: Floor Heat Ceiling Cool Unstable Tilted Equation Source
Applies to zone with in-floor heating and/or in-ceiling cooling. This is for tilted surfaces with heat
flow for unstable thermal stratification. The key choice options include: WaltonUnstableHorizon-
talOrTilt, AlamdariHammondUnstableHorizontal, ISO15099Windows, or UserCurve.
1.11.12.1.27 Field: Floor Heat Ceiling Cool Unstable Tilted Equation User
Curve Name
The SurfaceConvectionAlgorithm:UserCurve named in this field is used when the previous field is
set to UserCurve.
1.11.12.1.29 Field: Floor Heat Ceiling Cool Window Equation User Curve Name
The SurfaceConvectionAlgorithm:UserCurve named in this field is used when the previous field is
set to UserCurve.
1.11. GROUP – ADVANCED SURFACE CONCEPTS 437
1.11.12.1.31 Field: Wall Panel Heating Vertical Wall Equation User Curve Name
The SurfaceConvectionAlgorithm:UserCurve named in this field is used when the previous field is
set to UserCurve.
1.11.12.1.33 Field: Wall Panel Heating Heated Wall Equation User Curve Name
The SurfaceConvectionAlgorithm:UserCurve named in this field is used when the previous field is
set to UserCurve.
1.11.12.1.35 Field: Wall Panel Heating Stable Horizontal Equation User Curve
Name
The SurfaceConvectionAlgorithm:UserCurve named in this field is used when the previous field is
set to UserCurve.
1.11.12.1.39 Field: Wall Panel Heating Stable Tilted Equation User Curve Name
The SurfaceConvectionAlgorithm:UserCurve named in this field is used when the previous field is
set to UserCurve
1.11.12.1.41 Field: Wall Panel Heating Unstable Tilted Equation User Curve
Name
The SurfaceConvectionAlgorithm:UserCurve named in this field is used when the previous field is
set to UserCurve.
1.11.12.1.43 Field: Wall Panel Heating Window Equation User Curve Name
The SurfaceConvectionAlgorithm:UserCurve named in this field is used when the previous field is
set to UserCurve.
1.11.12.1.45 Field: Convective Zone Heater Vertical Wall Equation User Curve
Name
The SurfaceConvectionAlgorithm:UserCurve named in this field is used when the previous field is
set to UserCurve.
1.11. GROUP – ADVANCED SURFACE CONCEPTS 439
1.11.12.1.46 Field: Convective Zone Heater Vertical Walls Near Heater Equation
Source
Applies to zone with convective heater. This is for vertical walls that are directly affected by
heater. Walls are considered “near” when listed in field set for Fraction of Radiant Energy to Sur-
face. The key choice options include: ASHRAEVerticalWall, AlamdariHammondVerticalWall, Khal-
ifaEq5WallNearHeat, AwbiHattonHeatedWall, FohannoPolidoriVerticalWall, ISO15099Windows, or
UserCurve.
1.11.12.1.47 Field: Convective Zone Heater Vertical Walls Near Heater Equation
User Curve Name
The SurfaceConvectionAlgorithm:UserCurve named in this field is used when the previous field is
set to UserCurve.
Applies to zone with convective heater. This is for horizontal surfaces with heat flow directed
for stable thermal stratification. The key choice options include: WaltonStableHorizontalOrTilt,
AlamdariHammondStableHorizontal, or UserCurve.
1.11.12.1.53 Field: Convective Zone Heater Stable Tilted Equation User Curve
Name
The SurfaceConvectionAlgorithm:UserCurve named in this field is used when the previous field is
set to UserCurve.
440 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.11.12.1.59 Field: Central Air Diffuser Wall Equation User Curve Name
The SurfaceConvectionAlgorithm:UserCurve named in this field is used when the previous field is
set to UserCurve.
1.11.12.1.61 Field: Central Air Diffuser Ceiling Equation User Curve Name
The SurfaceConvectionAlgorithm:UserCurve named in this field is used when the previous field is
set to UserCurve.
1.11.12.1.63 Field: Central Air Diffuser Floor Equation User Curve Name
The SurfaceConvectionAlgorithm:UserCurve named in this field is used when the previous field is
set to UserCurve.
1.11.12.1.65 Field: Central Air Diffuser Window Equation User Curve Name
The SurfaceConvectionAlgorithm:UserCurve named in this field is used when the previous field is
set to UserCurve
1.11.12.1.73 Field Mechanical Zone Fan Circulation Stable Tilted Equation User
Curve Name
The SurfaceConvectionAlgorithm:UserCurve named in this field is used when the previous field is
set to UserCurve.
1.11.12.1.83 Field: Mixed Regime Stable Floor Equation User Curve Name
The SurfaceConvectionAlgorithm:UserCurve named in this field is used when the previous field is
set to UserCurve.
1.11.12.1.85 Field: Mixed Regime Unstable Floor Equation User Curve Name
The SurfaceConvectionAlgorithm:UserCurve named in this field is used when the previous field is
set to UserCurve.
1.11.12.1.87 Field: Mixed Regime Stable Ceiling Equation User Curve Name
The SurfaceConvectionAlgorithm:UserCurve named in this field is used when the previous field is
set to UserCurve.
1.11.12.1.89 Field: Mixed Regime Unstable Ceiling Equation User Curve Name
The SurfaceConvectionAlgorithm:UserCurve named in this field is used when the previous field is
set to UserCurve.
444 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.11.13 SurfaceConvectionAlgorithm:Outside:AdaptiveModelSelections
Options to change the individual convection model equations for dynamic selection when using
AdaptiveConvectionAlgorithm. This object is only needed to make changes to the default model
selections for any or all of the surface categories. This object is for the outside face, the side of the
surface facing away from the thermal zone.
1.11.13.1 Inputs
1.11.13.1.5 Field: Wind Convection Leeward Vertical Wall Equation User Curve
Name
The SurfaceConvectionAlgorithm:UserCurve named in this field is used when the previous field is
set to UserCurve.
1.11.13.1.9 Field: Natural Convection Vertical Wall Equation User Curve Name
The SurfaceConvectionAlgorithm:UserCurve named in this field is used when the previous field is
set to UserCurve.
1.11.14 SurfaceConvectionAlgorithm:Inside:UserCurve
This object is used to describe a custom model equation for surface convection heat transfer coeffi-
cients. If more than one curve is referenced, or non-blank, then they are all used, and the result is
the simple addition of all the curve results.
1.11.14.1 Inputs
1.11.15 SurfaceConvectionAlgorithm:Outside:UserCurve
This object is used to describe a custom model equation for surface convection heat transfer coeffi-
cients. If more than one curve is referenced, or non-blank, then they are all used and the result is
the simple addition of all the curve results.
1.11.15.1 Inputs
1.11.16 SurfaceProperty:ConvectionCoefficients
The convection coefficients of each surface, both exterior and interior, are automatically calculated
during EnergyPlus execution. These calculations are “governed” by other objects such as the Sur-
faceConvectionAlgorithm:Inside (overall default), the Zone object’s field called Zone Inside Convec-
tion Algorithm (Zone Default), the and the SurfaceConvectionAlgorithm:Outside (overall default),
and/or the Zone object’s field called Zone Outside Convection Algorithm (Zone Default). Usually,
that will be enough flexibility for most users. However, if you need to match pre-existing convection
coefficients (from another program) or are trying to match a test suite of results, you may wish
to use the “override” convection coefficients in the following object. This object allows for a single
surface to be given specific convection coefficients.
Note that using these in conjunction, in particular, the “Simple” option on either the Outside
Convection Algorithm or the Zone Outside Convection Algorithm field will result in a combined
coefficient regardless of choice chosen here.
Note that surfaces with “SurfaceProperty:OtherSideCoefficients” cannot use this object with
the “outside” coefficient – attempting to do so will cause a severe error; SurfaceProp-
erty:OtherSideCoefficients surfaces can apply an “inside” coefficient. And, surfaces with
448 CHAPTER 1. INPUT-OUTPUT REFERENCE
“Ground” exposure do not use the “outside” coefficient that might be supplied here. Note,
too, that some lower boundaries are used regardless by certain surface types (i.e. Window) or
certain algorithm types.
1.11.16.1 Inputs
Value Both
Schedule Both
Simple Inside
SimpleCombined Outside
TARP Both
DOE-2 Outside
MoWitt Outside
AdaptiveConvectionAlgorithm Both
ASHRAEVerticalWall Both
ASTMC1340 Inside
1.11. GROUP – ADVANCED SURFACE CONCEPTS 449
WaltonUnstableHorizontalOrTilt Both
WaltonStableHorizontalOrTilt Both
FisherPedersenCeilingDiffuserWalls Inside
FisherPedersenCeilingDiffuserCeiling Inside
FisherPedersenCeilingDiffuserFloor Inside
AlamdariHammondStableHorizontal Both
AlamdariHammondUnstableHorizontal Both
AlamdariHammondVerticalWall Both
KhalifaEq3WallAwayFromHeat Inside
KhalifaEq4CeilingAwayFromHeat Inside
KhalifaEq5WallNearHeat Inside
KhalifaEq6NonHeatedWalls Inside
KhalifaEq7Ceiling Inside
AwbiHattonHeatedFloor Inside
AwbiHattonHeatedWall Inside
BeausoleilMorrisonMixedAssistedWall Inside
BeausoleilMorrisonMixedOpposingWall Inside
BeausoleilMorrisonMixedStableFloor Inside
BeausoleilMorrisonMixedUnstableFloor Inside
BeausoleilMorrisonMixedStableCeiling Inside
BeausoleilMorrisonMixedUnstableCeiling Inside
FohannoPolidoriVerticalWall Both
KaradagChilledCeiling Inside
ISO15099Windows Inside
GoldsteinNovoselacCeilingDiffuserWindow Inside
GoldsteinNovoselacCeilingDiffuserWalls Inside
GoldsteinNovoselacCeilingDiffuserFloor Inside
SimpleCombined Outside
NusseltJurges Outside
McAdams Outside
Mitchell Outside
BlockenWindard Outside
Emmel Outside
ClearRoof Outside
UserCurve Both
If the Convection type was “Value”, then this field is filled and contains the simple value to be used.
Otherwise, this can be blank.
SurfaceProperty:ConvectionCoefficients ,
Zn001:Wall001 , ! Surface Name
Outside , ! Convection Coefficient 1 Location
Value , ! Convection Coefficient 1 Type
9.8, ! Convection Coefficient 1
, ! Convection Coefficient 1 Schedule Name
, ! Convection Coefficient 1 User Curve Name
Inside , ! Convection Coefficient 2 Location
Schedule , ! Convection Coefficient 2 Type
, ! Convection Coefficient 2 {blank because using schedule}
MyInteriorCC , ! Convection Coefficient 2 Schedule Name
; ! Convection Coefficient 2 User Curve Name
SurfaceProperty:ConvectionCoefficients ,
Zn001:Wall002 , ! Surface Name
Inside , ! Convection Coefficient 1 Location
Value , ! Convection Coefficient 1 Type
.8, ! Convection Coefficient 1
, ! Convection Coefficient 1 Schedule Name
, ! Convection Coefficient 1 User Curve Name
Outside , ! Convection Coefficient 2 Location
Value , ! Convection Coefficient 2 Type
5.5, ! Convection Coefficient 2
; ! Convection Coefficient 2 User Curve Name
SurfaceProperty:ConvectionCoefficients ,
Zn001:Wall003 , ! Surface Name
Outside , ! Convection Coefficient 1 Location
Value , ! Convection Coefficient 1 Type
9.8; ! Convection Coefficient 1
1.11.17 SurfaceProperty:ConvectionCoefficients:MultipleSurface
The convection coefficients of each surface, both outside and inside, are automatically calculated
during EnergyPlus execution. These calculations are “governed” by other objects such as the Inside
Convection Algorithm (overall default) and the Zone Inside Convection Algorithm (Zone Default) and
the Outside Convection Algorithm (overall default) and/or the Zone Outside Convection Algorithm
1.11. GROUP – ADVANCED SURFACE CONCEPTS 451
(Zone Default). Usually, that will be enough flexibility for most users. However, if you need to
match pre-existing convection coefficients (from another program) or are trying to match a test suite
of results, you may wish to use the “override” convection coefficients in the following object. This
object is similar to the preceding “ConvectionCoefficients” object but allows multiple surfaces to be
assigned a type with one object entry.
Note that using these in conjunction, in particular, the “Simple” option on either the Outside
Convection Algorithm or the Zone Outside Convection Algorithm field will result in a combined
coefficient regardless of choice chosen here.
Note that surfaces with “SurfaceProperty:OtherSideCoefficients” cannot use this object with the
“outside” coefficient – attempting to do so will ignore OSC surfaces during a multiple surface “apply”;
SurfaceProperty:OtherSideCoefficients surfaces can apply an “inside” coefficient. And, surfaces with
“Ground” exposure do not use the “outside” coefficient that might be supplied here. Note, too,
that some lower boundaries are used regardless by certain surface types (i.e. Window) or certain
algorithm types.
1.11.17.1 Inputs
Value Both
Schedule Both
Simple Inside
SimpleCombined Outside
TARP Both
DOE-2 Outside
MoWitt Outside
AdaptiveConvectionAlgorithm Both
ASHRAEVerticalWall Both
ASTMC1340 Inside
WaltonUnstableHorizontalOrTilt Both
WaltonStableHorizontalOrTilt Both
FisherPedersenCeilingDiffuserWalls Inside
FisherPedersenCeilingDiffuserCeiling Inside
FisherPedersenCeilingDiffuserFloor Inside
AlamdariHammondStableHorizontal Both
AlamdariHammondUnstableHorizontal Both
AlamdariHammondVerticalWall Both
KhalifaEq3WallAwayFromHeat Inside
KhalifaEq4CeilingAwayFromHeat Inside
KhalifaEq5WallNearHeat Inside
KhalifaEq6NonHeatedWalls Inside
KhalifaEq7Ceiling Inside
AwbiHattonHeatedFloor Inside
AwbiHattonHeatedWall Inside
BeausoleilMorrisonMixedAssistedWall Inside
BeausoleilMorrisonMixedOpposingWall Inside
BeausoleilMorrisonMixedStableFloor Inside
BeausoleilMorrisonMixedUnstableFloor Inside
BeausoleilMorrisonMixedStableCeiling Inside
BeausoleilMorrisonMixedUnstableCeiling Inside
1.11. GROUP – ADVANCED SURFACE CONCEPTS 453
FohannoPolidoriVerticalWall Both
KaradagChilledCeiling Inside
ISO15099Windows Inside
GoldsteinNovoselacCeilingDiffuserWindow Inside
GoldsteinNovoselacCeilingDiffuserWalls Inside
GoldsteinNovoselacCeilingDiffuserFloor Inside
SimpleCombined Outside
NusseltJurges Outside
McAdams Outside
Mitchell Outside
BlockenWindard Outside
Emmel Outside
ClearRoof Outside
UserCurve Both
– SurfaceConvectionAlgorithm:Inside
– SurfaceConvectionAlgorithm:Outside
– Zone, Field: Zone Inside Convection Algorithm
– Zone, Field: Zone Outside Convection Algorithm
– SurfaceProperty:ConvectionCoefficients
– SurfaceProperty:ConvectionCoefficients:MultipleSurface
Objects/Description Action
There are additional objects that provide fine control over the models that get assigned.
– SurfaceConvectionAlgorithm:Inside:AdaptiveModelSelections
– SurfaceConvectionAlgorithm:Outside:AdaptiveModelSelections
– SurfaceConvectionAlgorithm:Inside:UserCurve
– SurfaceConvectionAlgorithm:Outside:UserCurve
by identifying which models are in effect at a given time. The adaptive convection algorithms may
switch between models over time and the following output variables provide a way to monitor this
behavior. These outputs are integer codes and the integer values are explained in tables.
This variable reports how the surface was classified as part of the adaptive convection algorithm for
the inside face. The algorithm examines probable flow regimes, heat flow directions, orientations,
HVAC equipment connections, and current operating status to assign each surface a category. The
numbers in this report are integer codes that correspond to surface categories as described in the
following table.
This variable reports the specific model equation used to calculate the inside face convection co-
efficient. This can vary when using the adaptive convection algorithm and so the result of that
selection algorithm is reported here. The following table lists the models associated with specific
interger codes reported here. The models correspond to key words used in input objects.
200 UserValue
201 UserSchedule
202 UserCurve
203 ASHRAEVerticalWall
204 WaltonUnstableHorizontalOrTilt
205 WaltonStableHorizontalOrTilt
206 FisherPedersenCeilDiffuserFloor
207 FisherPedersenCeilDiffuserCeiling
208 FisherPedersenCeilDiffuserWalls
209 AlamdariHammondStableHorizontal
210 AlamdariHammondVerticalWall
211 AlamdariHammondUnstableHorizontal
212 KhalifaEq3WallAwayFromHeat
213 KhalifaEq4CeilingAwayFromHeat
214 KhalifaEq5WallNearHeat
215 KhalifaEq6NonHeatedWalls
216 KhalifaEq7Ceiling
217 AwbiHattonHeatedFloor
218 AwbiHattonHeatedWall
219 BeausoleilMorrisonMixedAssistingWall
220 BeausoleilMorrisonMixedOppossingWall
221 BeausoleilMorrisonMixedStableCeiling
222 BeausoleilMorrisonMixedUnstableCeiling
223 BeausoleilMorrisonMixedStableFloor
224 BeausoleilMorrisonMixedUnstableFloor
225 FohannoPolidoriVerticalWall
226 KaradagChilledCeiling
458 CHAPTER 1. INPUT-OUTPUT REFERENCE
227 ISO15099Windows
228 GoldsteinNovoselacCeilingDiffuserWindow
229 GoldsteinNovoselacCeilingDiffuserWalls
230 GoldsteinNovoselacCeilingDiffuserFloor
The inside face convection heat transfer calculations can be based on different reference air temper-
atures. This reference air temperature can vary during the simulation when the adaptive algorithm
selects models that use different references. The following table lists the meaning of the integer
codes.
This variable reports how the surface was classified as part of the adaptive convection algorithm for
the outside face. The algorithm examines the wind direction, heat flow directions and orientations
to assign each surface a category. The numbers in this report are integer codes that correspond to
surface categories as described in the following table.
-1 Invalid
101 Vertical Wall, Windward
102 Vertical Wall, Leeward
103 Roof, stable heat flow direction
104 Roof, unstable heat flow direction
These variables report the specific model equation used to calculate the outside face’s convection
coefficient. They can vary when using the adaptive convection algorithm and so the results of that
selection algorithm are reported in these variables. The following table lists the models associated
with specific integer codes that might be reported here. The models correspond to key words used
in input objects.
1.11. GROUP – ADVANCED SURFACE CONCEPTS 459
300 None
301 UserValue
302 UserSchedule
303 UserCurve
304 ASHRAESimpleCombined
305 NaturalASHRAEVerticalWall
306 NaturalWaltonUnstableHorizontalOrTilt
307 NaturalWaltonStableHorizontalOrTilt
308 SparrowWindward
309 SparrowLeeward
310 MoWiTTWindward
311 MoWiTTLeeward
312 DOE2Windward
313 DOE2Leeward
314 NusseltJurges
315 McAdams
316 Mitchell
317 ClearRoof
318 BlockenWindward
319 EmmelVertical
320 EmmelRoof
321 AlamdariHammondVerticalWall
322 FohannoPolidoriVerticalWall
323 ISO15099Windows
324 AlamdariHammondStableHorizontal
325 AlamdariHammondUnstableHorizontal
1.11.20 SurfaceProperties:VaporCoefficients
Advanced/Research Usage: The internal and external vapor transfer coefficients that are used by the
CombinedHeatAndMoistureFiniteElement model are automatically calculated during EnergyPlus
execution using information on the convection coefficients. However it is sometimes useful to be able
to “override” the calculation and set fixed values of vapor transfer coefficient for a single surface.
These coefficients are only used by the CombinedHeatAndMoistureFiniteElement model and will be
ignored by other solution algorithms.
1.11.20.1 Inputs
SurfaceProperties:VaporCoefficients ,
South wall , !- Surface Name
Yes , !- Constant External Vapor Transfer Coefficient
0.0000000625 , !- External Vapor Coefficient Value
Yes , !- Constant Internal vapor Transfer Coefficient
0.00000002; !- Internal Vapor Coefficient Value
1.11.21 SurfaceProperty:ExteriorNaturalVentedCavity
This object is used to model a multi-skin exterior heat transfer surface. This is a special case where
the outside face is a slightly detached layer forming a naturally ventilated cavity. The actual outer
surface is referred to as the baffle. The modeling here assumes that the heat capacity in the outer baf-
fle can be neglected since it is much lower than the underlying mass surface. This object is used with
the BuildingSurface:Detailed object where the Heat Transfer surfaces are referred to as the underly-
ing surfaces. The constructions and materials for the BuildingSurface:Detailed object should reflect
the construction of just the underlying surface. The SurfaceProperty:ExteriorNaturalVentedCavity
object is used to describe the decoupled layer, or baffle, and the characteristics of the cavity and
openings for natural ventilation. This object is also used in conjunction with the OtherSideCondi-
tionsModel.
The area and orientation are obtained from BuildingSurface:Detailed objects, which are refer-
enced by name. This object can be used to model certain types of photovoltaic mounting configu-
rations such as interlocking roof pavers. If the baffle covers only part of a surface, then that surface
should be split into separate BuildingSurface:Detailed objects where one matches the size of
the baffle. A single baffle can be associated with as many BuildingSurface:Detailed objects as
desired. The base heat transfer surfaces need not be contiguous nor have the same orientation, but
the program will issue warnings if surfaces have widely ranging tilts and azimuths.
Note that the model involves predicting the rates that ambient air moves in and out of the cavity.
Accurate modeling of these air flows would be extremely challenging and so the models provided
through this object are simplistic engineering models based on discharge coefficients that are sensitive
to wind and buoyancy effects. The accuracy depends on the values for, and applicability of, the
discharge coefficients and unfortunately little research is available to help characterize these. The
1.11. GROUP – ADVANCED SURFACE CONCEPTS 461
models should be considered rudimentary and the user is encouraged to explore different values for
the coefficients in attempts to bound the importance of natural ventilation for the cavities. See the
Engineering Reference for more details.
1.11.21.1 Inputs
SurfaceProperty:ExteriorNaturalVentedCavity ,
PVRoofPaverExtVentCav1 , ! Name
PVRoofPaverSystem1 , ! OtherSideConditionsModel Object Name
0.02, ! Area Fraction of Openings
0.9, ! Thermal Emissivity of Exterior Baffle Material
0.92, ! Solar Absorbtivity of Exterior Baffle
0.05, ! Height scale for buoyancy -driven ventilation
0.05, ! Effective Thickness of Cavity Behind Exterior Baffle
0.97, ! Ratio of Actual surface area to projected surface area
Smooth , ! Roughness of collector
0.1 , ! Cv , Effectiveness for perforations with respect to Wind
0.5 , ! Cd , Discharge Coefficient for Openings with respect to buoyancy -driven flow
Zn001:Roof001 ; ! Surface Name
1.11.21.2 Outputs
In addition to related output that can be obtained for all surfaces, these outputs are available for
exterior naturally vented cavity configurations:
1.11.21.2.3 Surface Exterior Cavity Total Natural Ventilation Air Change Rate
[ACH]
The rate of natural ventilation air exchange between the plenum and ambient when the collector is
inactive in Air Changes per Hour.
1.11.21.2.4 Surface Exterior Cavity Total Natural Ventilation Mass Flow Rate
[kg/s]
The mass flow rate of natural ventilation air exchange between the plenum and ambient when the
collector is inactive.
1.11.21.2.5 Surface Exterior Cavity Natural Ventilation from Wind Mass Flow
Rate [kg/s]
The part of mass flow rate of natural ventilation air exchange between the plenum and ambient when
the collector is inactive due to wind-driven forces.
464 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.11.22 SurfaceProperty:SolarIncidentInside
This object can be used as an alternative to the standard (automatic) EnergyPlus calculation of
the solar radiation incident on interior surfaces of the building. Using this method, the normal
EnergyPlus calculation is replaced with a schedule of solar incidence values that are calculated
outside the program.
1.11.22.1 Inputs
1.11.22.1.4 Field: Inside Surface Incident Sun Solar Radiation Schedule Name
This field specifies the name of a schedule that contains the values for incident solar radiation. Values
from the schedule data will be used to replace the absorbed solar radiation that would normally be
calculated by EnergyPlus. Units in the external schedule file must be W/m2 .
Example for SurfaceProperty:SolarIncidentInside using a compact schedule:
Schedule:Compact ,
North Wall SSG , !- Name
Positive Number , !- Schedule Type Limits Name
Through: 12/31 , !- Field 1
For: AllDays , !- Field 2
Until: 07:00 ,10 , !- Field 3
Until: 17:00 ,20 , !- Field 5
Until: 24:00 ,15; !- Field 7
SurfaceProperty:SolarIncidentInside ,
North Wall Solar Incident , !- Name
Room102 North Wall , !- Surface Name
Room Wall - North , !- Construction Name
North Wall SSG; !- Schedule Name
1.11. GROUP – ADVANCED SURFACE CONCEPTS 465
1.11.23 ComplexFenestrationProperty:SolarAbsorbedLayers
This object can be used as an alternative to the standard (automatic) EnergyPlus calculation of the
solar radiation absorbed by fenestration systems in the building. Using this method, the normal
EnergyPlus calculation is replaced with a schedule of solar absorptance values that are calculated
outside the program.
1.11.23.1 Inputs
Schedule:Compact ,
Layer 1, !- Name
Positive Number , !- Schedule Type Limits Name
Through: 12/31 , !- Field 1
For: AllDays , !- Field 2
Until: 07:00 ,1 , !- Field 3
Until: 17:00 ,2 , !- Field 5
Until: 24:00 ,1.5; !- Field 7
Schedule:Compact ,
Layer 2, !- Name
Positive Number , !- Schedule Type Limits Name
Through: 12/31 , !- Field 1
For: AllDays , !- Field 2
Until: 07:00 ,0.8 , !- Field 3
Until: 17:00 ,1.2 , !- Field 5
Until: 24:00 ,1.0; !- Field 7
Schedule:Compact ,
Layer 3, !- Name
Positive Number , !- Schedule Type Limits Name
Through: 12/31 , !- Field 1
For: AllDays , !- Field 2
Until: 07:00 ,1 , !- Field 3
Until: 17:00 ,2.1 , !- Field 5
Until: 24:00 ,1.7; !- Field 7
ComplexFenestrationProperty :SolarAbsorbedLayers ,
South Window Solar Absorbed Layers , !- Name
Room 102 South Window , !- Fenestration surface name
CFS_Glz_2 , !- Construction Surface name
Layer 1, !- Absorbed solar energy in layer 1
Layer 2, !- Absorbed solar energy in layer 2
Layer 3; !- Absorbed solar energy in layer 3
1.11.24 GeometryTransform
This object provides a simple method of altering the footprint geometry of a model. The intent is to
provide a single parameter that can be used to reshape the building description contained in the rest
of the input file. This object was implemented for use in parametric massing studies and with the
optimization program GenOpt. Although building footprint is often constrained in practice, analysts
may find this object useful for investigating how building form impacts daylighting and solar gains
on the east and west facades without having to change all of the surface geometry input.
Aspect Ratio is defined as the overall length in the East-West direction divided by the overall length
in the North-South direction.
This object should be used with considerable care since it will completely alter the geometry modeled
by EnergyPlus and may have unintended side effects. The surface areas of all horizontal surfaces may
change radically with corresponding changes in Zone floor areas. The total floor area will not change
but individual horizontal surfaces will gain and loose area. Vertical surfaces will have the same
1.11. GROUP – ADVANCED SURFACE CONCEPTS 467
height but will gain and lose length. Lighting and electrical equipment design levels for individual
zones will likely have a different energy per unit area in the transformed geometry.
The surface geometry must be set to Relative, see GlobalGeometryRules. Of course, the coor-
dinates must be entered in relative coordinates as well.
Since windows in EnergyPlus need to be rectangular, it is possible to define a horizontal window
(skylight) that once transformed is no longer rectangular and will cause EnergyPlus to halt. To
avoid this problem, horizontal windows should be defined orthogonal to the Cardinal directions and
building rotation (see Building) used to orient the final form with respect to North.
The object doesn’t create any specific output, but the results of using it can be understood by
viewing DXF output files. Figure 1.63 shows an example of a building that has been morphed using
the Aspect Ratio Transform object. Using this object allowed the same geometry input to generate
both of the models represented in by their DXF output files.
1.11.24.1 Inputs
1.11.25 SurfaceProperty:SurroundingSurfaces
The object is used to calculate long wave radiation to an external surface from its surrounding
surfaces, defining the properties of the surrounding surfaces. The property object declares a list of
single surrounding surfaces which has a name, a field of view factor, and another field Temperature
Schedule Name referencing a schedule containing the temperature of the surrounding surface, which
can be overwritten at each time step in EnergyPlus run time through co-simulation. View factors
are assumed to be constant values. At least one surrounding surface should be defined in this object.
The object also defines the sky and ground temperature and view factors to the external surface.
The sum of all defined view factors should not exceed 1.0. If only sky view is defined in this object,
the ground view factor to this surface will be 1.0 subtracted with the ground view factor and all
other defined surface view factors. If only ground view is defined in this object, the sky view factor
to this surface will be 1.0 subtracted with the sky view factor and all other defined surface view
factors. If neither of the sky and ground view factors are explicitly declared here, the sum of the sky
and ground view factor would be 1.0 subtracted with all other defined surface view factors and the
proportion will be set as the same with the global setting.
468 CHAPTER 1. INPUT-OUTPUT REFERENCE
This field defines the constant sky view factor to an external surface. The sky view factor used
in solar radiation calculation of the surface would be overwritten with the value of the fraction if
defined here. If the field is left blank, the sky view factor of this surface will be calculated with the
rules demonstrated above.
This field is used to supply a schedule name of the sky temperature. The sky temperature used
in solar radiation calculation of the surface would be overwritten with the value of the scheduled
temperature if defined here. If the field is left blank, the global sky temperature would be used.
This field defines the constant ground view factor to an external surface. The ground view factor
used in solar radiation calculation of the surface would be overwritten with the value of the fraction
if defined here. If the field is left blank, the ground view factor of this surface will be calculated with
the rules demonstrated above.
This field is used to supply a schedule name of the ground temperature. The ground temperature
used in solar radiation calculation of the surface would be overwritten with the value of the scheduled
temperature if defined here. If the field is left blank, the global ground temperature would be used.
This field defines the name of a surrounding surface to the external surface.
This field defines the constant view factor of a surrounding surface to an external surface.
This field is used to supply a schedule name of the of a surrounding surface temperature.
The object is extensible so the last three fields can be repeated to define multiple surrounding surface
name, temperature and view factor sets.
An example IDF object follows.
470 CHAPTER 1. INPUT-OUTPUT REFERENCE
SurfaceProperty:SurroundingSurfaces ,
SrdSurfs:Window , !- Name
0.3, !- Sky View Factor
, !- Sky Temperature Schedule Name
0.1, !- Ground View Factor
, !- Ground Temperature Schedule Name
SurroundingSurface1 , !- Surrounding Surface 1 Name
0.6, !- Surrounding Surface 1 View Factor
Surrounding Temp Sch 1; !- Surrounding Surface 1 Temperature Schedule Name
Schedule:Compact ,
Surrounding Temp Sch 1, !- Name
Any Number , !- Schedule Type Limits Name
Through: 12/31 , !- Field 1
For: AllDays , !- Field 2
Until: 24:00 , 15.0; !- Field 3
1.11.26 SurfaceProperty:LocalEnvironment
The object links to a surface object Surface:Detailed and is used when there is a need to calculate
surface level environmental data externally and import them into the simulation to override existing
environmental data, including external solar shading fractions, local air velocity, temperature and
humidity, and surrounding surface temperatures and view factors. The object links to three op-
tional objects including a schedule object declared by Field: External Shading Fraction Sched-
ule Name, a SurfaceProperty:SurroundingSurfaces object declared by Field: Surrounding
Surfaces Object Name, and an OutdoorAir:Node object declared by Field: Outdoor Air
Node Name. The object provides inputs to calculate shading, solar radiation, zone air balance and
surface exterior heat balance.
This is the name of the surface that will be assigned to use the local environmental data defined in
the next three fields. This should be a name of a surface defined elsewhere.
This field is used to import external shading fraction data from external calculation. This should be
a name of a schedule object with fraction input.
This field is used to import surrounding surfaces properties (temperature and view factors to
the external surface) from external calculation. This should be a name of a SurfaceProp-
erty:SurroundingSurfaces object.
1.11. GROUP – ADVANCED SURFACE CONCEPTS 471
This field is used to import local environmental data from local outdoor air nodes, including dry
and wet bulb temperature, wind speed and wind direction. This should be a name of a Out-
doorAir:Node object.
An example IDF object follows.
SurfaceProperty:LocalEnvironment ,
LocEnv:Zn001:Wall001 , !- Name
Zn001:Wall001 , !- Exterior Surface Name
ExtShadingSch:Zn001:Wall001 , !- External Shading Fraction Schedule Name
SrdSurf:Zn001:Wall001 , !- Surrounding Surfaces Object Name
OutdoorAirNode :0001; !- Outdoor Air Node Name
1.11.27 ZoneProperty:LocalEnvironment
The object links to a Zone object and is used when there is a need to calculate zone level envi-
ronmental data externally and import them into the simulation to override existing environmental
data, including local air temperature and humidity, wind velocity and direction. links to an Out-
doorAir:Node object declared by Field: Outdoor Air Node Name. The reference local outdoor
air node provides ambient conditions for the calculation of infiltration and ventilation at the zone
level.
This is the name of the zone that will be assigned to use the local environmental data defined in the
next field. This should be a name of a surface defined elsewhere.
This field is used to import local environmental data from local outdoor air nodes, including dry
and wet bulb temperature, wind speed and wind direction. This should be a name of a Out-
doorAir:Node object.
An example IDF object follows.
ZoneProperty:LocalEnvironment ,
LocEnv:Zn001 , !- Name
Zn001 , !- Exterior Surface Name
OutdoorAirNode :0001; !- Outdoor Air Node Name
1.11.28 SurfaceProperty:HeatBalanceSourceTerm
The object allows additional heat source term of the surface boundary condition in the surface heat
balance calculation. The object specifies a surface with the additional heat source term described by
a schedule of heat rates (can be positive or negative values) in W/m2 . A heat source can be added to
either or both the inside and outside of the same surface. The heat rates are pre-calculated outside
EnergyPlus.
472 CHAPTER 1. INPUT-OUTPUT REFERENCE
This is the name of the surface that will be assigned to use the additional heat source term in heat
balance calculation
The value of this schedule is the source term value for the inside face of this surface. If this field
is left blank, no inside surface source term will be applied. The schedule values are heat rate per
surface area (W/m2), when positive schedule values indicate heat gain and negative values indicates
loss.
The value of this schedule is the source term value for the outside face of this surface. If this field
is left blank, no outside surface source term will be applied. The schedule values are heat rate per
surface area (W/m2), when positive schedule values indicate heat gain and negative values indicates
loss.
SurfaceProperty:HeatBalanceSourceTerm ,
Zn001:Wall001 , !- Surface Name
, !- Inside Face Heat Source Term Schedule Name
HeatSourceSch :001; !- Outside Face Heat Source Term Schedule Name
The first option produces approximate results and uses an area weighted scheme to calculate “view
factors” between surfaces within a thermal zone. Each surface uses the total area that it can “see”
among the other surfaces. The approximate view factor from this surface to each other surface is
then the area of the receiving surface over the sum of areas that are visible to the sending surface.
In order to account in some limited way for the fact that certain surfaces will not see each other,
several assumptions have been built into this view factor approximation. First, a surface cannot
see itself. Second, surfaces with approximately the same azimuth (facing direction) and tilt (“same”
being within a built in limit) will not see each other. This means that a window will not see the wall
that it is placed on, for example. Third, floors cannot see each other. Fourth, if the surface is a floor,
ceiling, roof, or internal mass, the rule for the same azimuth and tilt eliminating radiant exchange
between surfaces is waived when the receiving surface is floor, roof, ceiling, or internal mass as long
as both surfaces are not floors.
1.11. GROUP – ADVANCED SURFACE CONCEPTS 473
Note that this does not take into account that surfaces may be “around the corner” from each other
and in reality not see each other at all. Rooms are assumed to be convex rather than concave in this
method.
To summarize, using the Surface “Class”, the approximate view factors have:
If geometry is correct, conditions 1, 3, and 7 should take care of all surfaces, but the other conditions
supply common sense when the geometry is incorrect. More information about the EnergyPlus view
factor calculation is contained in the Engineering Reference document.
The second option for specifying view factors requires user input values. These should be
used with care in research or special situations. The object available for this is ZoneProp-
erty:UserViewFactors:BySurfaceName.
1.11.30 ZoneProperty:UserViewFactors:BySurfaceName
The method of entering user view factors is to enter each surface name and its view factor value to
other surfaces in a radiant/solar enclosure which may consist of one space, one zone or a group of
spaces or zones.
1.11.30.1 Inputs
– GroundHeatTransfer:Slab:Materials
– GroundHeatTransfer:Slab:MatlProps
– GroundHeatTransfer:Slab:BoundConds
– GroundHeatTransfer:Slab:BldgProps
– GroundHeatTransfer:Slab:Insulation
– GroundHeatTransfer:Slab:EquivalentSlab
– GroundHeatTransfer:Slab:AutoGrid
– GroundHeatTransfer:Slab:ManualGrid
– GroundHeatTransfer:Slab:XFACE
– GroundHeatTransfer:Slab:YFACE
– GroundHeatTransfer:Slab:ZFACE
The following objects may be included in an EnergyPlus input IDF file but are handled by the
Basement preprocessor:
– GroundHeatTransfer:Basement:SimParameters
– GroundHeatTransfer:Basement:MatlProps
– GroundHeatTransfer:Basement:Insulation
– GroundHeatTransfer:Basement:SurfaceProps
– GroundHeatTransfer:Basement:BldgData
– GroundHeatTransfer:Basement:Interior
– GroundHeatTransfer:Basement:ComBldg
– GroundHeatTransfer:Basement:EquivSlab
– GroundHeatTransfer:Basement:EquivAutoGrid
– GroundHeatTransfer:Basement:AutoGrid
– GroundHeatTransfer:Basement:ManualGrid
– GroundHeatTransfer:Basement:XFACE
– GroundHeatTransfer:Basement:YFACE
– GroundHeatTransfer:Basement:ZFACE
1.13. GROUP – ROOM AIR MODELS 475
The documentation both the Slab and Basement objects appear in the AuxiliaryPrograms document
under the “Ground Heat Transfer in EnergyPlus” heading.
The only object described in this section is the control object which activates the use of the prepro-
cessor.
1.12.2 GroundHeatTransfer:Control
The GroundHeatTransfer:Control object determines if the Slab and Basement preprocessors are
going to be executed. When a Slab or Basement run is performed the results are saved in files with
extensions .SLAB or .BSMT so that they do not need to be rerun if no input changes are made to
the GroundHeatTransfer:Slab or GroundHeatTransfer:Basement objects.
1.12.2.1 Inputs
select room airflow configurations. Also note that because the complete mixing model for room air
has long been the standard in building energy simulation, there is not currently a consensus on how
to best model non-uniform air temperatures in buildings. Therefore, it is up to the user to have a
good understanding of when, where, and how to apply the room air models available in EnergyPlus.
The rest of this section provides some guidance in the way of examples and further discussion of the
models available in EnergyPlus.
EnergyPlus offers the different types of air models listed in the table below along with the input
objects associated with the use of that model.
Air Model Key Air model Algorithm Applicability Input Objects Required
1.13.2 RoomAirModelType
EnergyPlus uses the RoomAirModelType object to determine which air model is available for use in
a given zone during the simulation. If no RoomAirModelType object is specified (for each zone or the
whole building), then EnergyPlus will run with the conventional, completely mixing air model (for
each zone or the whole building). Include a RoomAirModelType for each zone that the user wants
modeled using a more detailed method. Currently only a single RoomAirModelType object can be
specified for each zone; you cannot switch between models during a simulation. However, the UCSD
Displacement, Cross Ventilation and UFAD models switch from displacement to mixing ventilation
when the operating conditions do not give rise to unmixed flow. The following parameters are fields
required by the RoomAirModelType object.
1.13.2.1 Inputs
1.13.3 RoomAir:TemperaturePattern:UserDefined
This object is used to explicitly define temperature patterns that are to be applied to the mean air
temperature within a thermal zone. This Room Air modeling option is made available for a number
of reasons. It allows modeling the consequences of air temperature variations during the design phase
when little information is available about the specifics of the air distribution system or positioning
of various loads. This option can be used to evaluate the energy implications of different design
targets for the temperature patterns. It also provides a method of modeling the annual energy use
implications for air temperature distributions determined using separate analyses or measurements.
478 CHAPTER 1. INPUT-OUTPUT REFERENCE
For example, this option could be used to understand the annual energy implications of an air
distribution system that has been previously analyzed using Computational Fluid Dynamics.
This approach differs from the other Room Air modeling in that the static temperature pattern is
not really modeled so that it will respond to conditions that develop during the simulation. More
sophisticated dynamic Room Air models will adjust the temperature pattern based on various factors,
such as air system flow rate, floor temperature, or rates of internal heat gains. The user-defined
temperature distribution patterns are fixed at the beginning and EnergyPlus simply provides results
that include the implications of those patterns. This user-defined distribution option may also be
useful for checking dynamic Room Air models by using “bounding” analysis.
Note that using this object carries a certain degree of responsibility. It would be very easy to define
a pattern that is non-physical and will lead to erroneous results. The user-defined temperature
distributions should (probably) be balanced about the mean so that basic conservation of energy
laws are not violated.
1.13.3.1 Inputs
1.13.4 RoomAir:TemperaturePattern:ConstantGradient
This object is used to model room air with a fixed temperature gradient in the vertical direction.
This fixed-slope method is about the simplest distribution pattern.
In addition to the vertical temperature gradient, there are three other parameters included in the
pattern that are important. The first two might affect how the air system conditioning the room is
operated. The first describes the temperature difference between the mean air temperature and the
point where the sensor of a drybulb thermostat is situated. The second describes the temperature
difference between the mean and the point where system air is being extracted from the zone. This
is considered important because the changes in temperature difference between supply and return
can affect how an air system is controlled to meet the loads. The third parameter can affect the zone
air heat balance by altering the temperature of the air leaving the zone through exhaust fans.
One example of a source of input data for the vertical temperature gradient is ANSI/ASHRAE
Standard 55-2004 Thermal Environmental Conditions for Human Occupancy. Table 5.2.4.3 in this
Standard specifies an allowable vertical temperature difference between head level and ankle level
of 3ºC (5ºF). If we assume a head to ankle length scale of 1.5 m (5 ft), this leads to a temperature
gradient of 3ºC/1.5m, or 2.0 ºC/m.
1.13.4.1 Inputs
1.13.5 RoomAir:TemperaturePattern:TwoGradient
This object provides various controls over the value of the gradient used for determining the pattern of
room air temperatures. It is similar to previous object RoomAir:TemperaturePattern:ConstantGradient
object but simplifies the potentially arduous task of preparing and scheduling a large number
of those objects. With this object, two different gradients are entered and user is given several
options for controlling how the program will interpolate between the two bounds. The user inputs
the height of the location of thermostat, return air, and exhaust air in meters rather than the
temperature offset.
1.13.5.1 Inputs
limit set in the next field, then the gradient entered in the ‘Temperature Gradient Upper Bound’
field is used. Similarly if the heating load is below the value set in the ‘Lower Temperature’ field,
then the gradient entered in the ‘Temperature Gradient Lower Bound’ is used. For heating loads
that lie between the upper and lower bounds, the gradient is determined by linear interpolation
between the two.
1.13.5.2 Outputs
The user-defined air temperature pattern that interpolates between two gradients produces the
following output variable.
HVAC ,Average ,Room Air Zone Vertical Temperature Gradient [K/m]
1.13. GROUP – ROOM AIR MODELS 483
1.13.6 RoomAir:TemperaturePattern:NondimensionalHeight
This object defines a distribution pattern for air temperatures relative to the current mean air
temperature as a function of height. The height, referred to as Zeta, is non-dimensional by normal-
izing with the zone ceiling height. (The actual zone ceiling height can be explicitly entered in the
‘Zone’ object but if not it is calculated by EnergyPlus from the surfaces attached to the zone.) The
temperature differences are not non-dimensional and remain in units of degrees Celsius.
An example of a vertical temperature pattern is shown in the figure below. The pattern itself is
treated as a piecewise, linear model of air temperature as a function of height. This Zeta-DeltaTai
curve, or lookup table, is then mapped to surfaces defined elsewhere in the file. The centroid of each
surface and zone ceiling height are used to automatically assign Zeta values within the program. The
zone named in the referencing RoomAir:TemperaturePattern:UserDefined object is used to determine
which surfaces will be associated with the pattern when it is applied. A single pattern object can be
reused for multiple zones and times.
In addition to the vertical temperature pattern there are three other parameters included in the
pattern that are important. The first two might affect how the air system conditioning the room is
operated. The first describes the temperature difference between the mean air temperature and the
point where the sensor of a drybulb thermostat is situated. The second describes the temperature
difference between the mean and the point where system air is being extracted from the zone. This
is considered important because the changes in temperature difference between supply and return
can affect how an air system is controlled to meet the loads. The third parameter can affect the zone
air heat balance by altering the temperature of the air leaving the zone through exhaust fans.
1.13.6.1 Inputs
1.13.7 RoomAir:TemperaturePattern:SurfaceMapping
This object defines a distribution pattern for the air temperatures adjacent to individual surfaces.
This object uses the specific names of individual surfaces defined elsewhere in the model. This
pattern allows controlling the adjacent air temperature on a surface-by-surface basis rather than by
height. This allows modeling different adjacent air temperatures on the opposite sides of the zone.
In addition to the surface mappings there are three other parameters included in the pattern that
are important. The first two might affect how the air system conditioning the room is operated. The
first describes the temperature difference between the mean air temperature and the point where the
sensor of a drybulb thermostat is situated. The second describes the temperature difference between
the mean and the point where system air is being extracted from the zone. This is considered
important because the changes in temperature difference between supply and return can affect how
486 CHAPTER 1. INPUT-OUTPUT REFERENCE
an air system is controlled to meet the loads. The third parameter can affect the zone air heat
balance by altering the temperature of the air leaving the zone through exhaust fans.
1.13.7.1 Inputs
1.13.7.1.7 Fields (6 and on): Pairs of Surface Names and Temperature Differ-
ences
The remaining fields contain pairs that define a lookup table for the temperature pattern on a
surface-by-surface basis.
1.13.8 RoomAir:Node
The RoomAir:Node object is used to define air nodes for a nodal air model. The number of air node
objects that need to be specified depends on the nodal air model selected. (However, currently only
the Mundt model uses this object). In order to use the Mundt model, the user must specify six or
more RoomAir:Node objects of different types for each zone. The exact number of RoomAir:Node
in the model will vary based on the resolution of walls. If walls (heat transfer surfaces) are split
into separate segments in the vertical direction, then more air nodes of type ‘MundtRoom’ will be
useful. At a minimum, for the Mundt model RoomAir Nodes of the following type are required:
‘Inlet, ‘Floor, ‘Control, ‘Ceiling, ‘MundtRoom, and ‘Return.’
1.13.8.1 Inputs
RoomAir:Node ,
WESTZN:FLOORAIR , !- Node Name
Floor , !- Node Type
WEST ZONE , !- Name of Zone to Which the Air Node Belongs
0.1, !- Height of Nodal Control Volume Center {m}
WESTZN:FLOOR:LEFF , !- surface name
WESTZN:FLOOR:RIGHT; !- surface name
1.13.9 RoomAirSettings:OneNodeDisplacementVentilation
The RoomAirSettings:OneNodeDisplacementVentilation object is used to specify additional input
parameters required by the Mundt model that are not available in other input objects in EnergyPlus.
A single object will be used for the zone.
1.13.9.1 Inputs
1.13.9.2 Outputs
1.13.10 RoomAirSettings:ThreeNodeDisplacementVentilation
This model is applicable to spaces that are served by a low velocity floor-level displacement ventilation
air distribution system. Furthermore, the dominant sources of heat gain should be from people and
other localized sources located in the occupied part of the room. The model should be used with
caution in zones which have large heat gains or losses through exterior walls or windows or which
have considerable direct solar gain. The model predicts three temperatures in the room:
– A foot level temperature (TFLOOR ). The floor region is 0.2 meters deep and TFLOOR represents
the temperature at the mid-point of the region.
– An occupied subzone temperature (TOC ), representing the temperature in the region between
the floor layer and the upper, mixed layer.
– An upper node representing the mixed-layer/outflow temperature (TMX ) essential for overall
energy budget calculations and for modeling comfort effects of the upper layer temperature.
The following fields are used to define an instance of the ‘UCSD Displacement Ventilation Model
Controls’ object.
1.13.10.1 Inputs
– people
– task lights
– electric equipment
490 CHAPTER 1. INPUT-OUTPUT REFERENCE
Figure 1.65: Schematic representation of the three temperature points and temperature gradients
1.13. GROUP – ROOM AIR MODELS 491
– gas equipment
– hot water equipment
– steam equipment
– other equipment
– baseboard heat
Types of internal gains that are assumed to be in the upper subzone are:
– general lights
– tubular daylighting devices
– high temperature radiant heaters
The schedule values should be between 0 and 1. A value of 1 means that all the convection gains
from equipment, task lights and people are dispersed in the lower occupied subzone. Conversely a
value of 0 puts all the lower subzone convective gains into the plumes rising into the upper well-mixed
subzone.
RoomAirSettings: ThreeNodeDisplacementVentilation ,
ZONE ONE , !- Zone Name
Constant - .2, !- Gain Distribution Schedule Name
1, !- Number of Plumes per Occupant
, !- Thermostat Height
, !- Comfort Height
.3; !- Temp. Difference Threshold for Displacement Ventilation
1.13.10.2 Outputs
1.13.10.2.9 Room Air Zone Thermal Comfort Effective Air Temperature [C]
The temperature at the user specified comfort height in degrees C.
1.13.11 RoomAirSettings:CrossVentilation
The UCSD Cross Ventilation Room Air Model provides a simple model for heat transfer and tem-
perature prediction in cross ventilated rooms. Cross Ventilation (CV) is common in many naturally
ventilated buildings, with air flowing through windows, open doorways and large internal apertures
across rooms and corridors in the building.
The CV model is used in EnergyPlus in the context of natural ventilation simulations using the
AirflowNetwork airflow prediction model. Typical CV room flows are characterized by two clearly
distinguishable flow regions that have different airflow velocities and temperature:
Each inflow aperture has one jet region while the recirculation regions are treated as a whole, with
a single temperature and characteristic velocity. The default EnergyPlus perfectly mixed single
temperature node room air approach is not suitable for these partially mixed flows. The proposed
CV model uses multiple nodes with distinct air temperature and airflow velocity (one node for the
recirculations plus one additional node for each inflow aperture).
The following fields are used to define an instance of the ‘UCSD Cross Ventilation Model Controls’
object.
1.13.11.1 Inputs
Figure 1.66: Schematic representation of room air geometry a) schematic representation of a room
geometry that generates cross ventilation airflow. b) the proposed model distinguishes two regions
in the flow: jet and recirculation (shown here in a CFD simulation of one half of a symmetrical
room).
1.13. GROUP – ROOM AIR MODELS 495
1.13.11.2 Outputs
– Zone,Average,Room Air Zone Jet Region Temperature [C]
– Zone,Average,Room Air Zone Recirculation Region Temperature [C]
– Zone,Average,Room Air Zone Jet Region Average Air Velocity [m/s]
– Zone,Average,Room Air Zone Recirculation Region Average Air Velocity [m/s]
– Zone,Average,Room Air Window Jet Region Average Air Velocity [m/s]
– Zone,Average,Room Air Zone Recirculation and Inflow Rate Ratio
– Zone,Average,Room Air Zone Inflow Opening Area [m2]
– Zone,Average,Room Air Zone Room Length [m]
– Zone,Average,Room Air Zone Is Mixing Status
– Zone,Average,Room Air Zone Is Recirculating Status
1.13.11.2.3 Room Air Zone Jet Region Average Air Velocity [m/s]
Average airflow velocity in the jet region of the flow in meters per second. If there is more than one
inflow window this output will be the inflow area weighted area of the jet inflow velocities.
1.13.11.2.4 Room Air Window Jet Region Average Air Velocity [m/s]
Average airflow velocity in the jet region in front of the window, in meters per second.
1.13. GROUP – ROOM AIR MODELS 497
1.13.11.2.5 Room Air Zone Recirculation Region Average Air Velocity [m/s]
Average airflow velocity in the recirculation region of the flow in meters per second.
1.13.12 RoomAirSettings:UnderFloorAirDistributionInterior
This model is applicable to interior spaces that are served by an underfloor air distribution system.
The dominant sources of heat gain should be from people, equipment, and other localized sources
located in the occupied part of the room. The model should be used with caution in zones which
have large heat gains or losses through exterior walls or windows or which have considerable direct
solar gain. The model predicts two temperatures in the room:
– An occupied subzone temperature (TOC ), representing the temperature in the region between
the floor and the boundary of the upper subzone.
– An upper subzone temperature (TMX ) essential for overall energy budget calculations and for
modeling comfort effects of the upper layer temperature.
The following fields are used to define an instance of the ‘UCSD UFAD Interior Model Controls’
object.
498 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.13.12.1 Inputs
RoomAirModelType ,
SPACE5 -1 RoomAir Model , !- Name
SPACE5 -1, !- Zone Name
UnderFloorAirDistributionInterior , !- Room -Air Modeling Type
DIRECT; !- Air Temperature Coupling Strategy
RoomAirSettings:UnderFloorAirDistributionInterior ,
SPACE5 -1, !- Zone Name
Autocalculate , !- Number of Diffusers
Autocalculate , !- Power per Plume
Autocalculate , !- Design Effective Area of Diffuser {m2}
Autocalculate , !- Diffuser Slot Angle from Vertical {deg}
, !- Thermostat Height {m}
, !- Comfort Height {m}
0.001 , !- Temperature Difference Threshold for Reporting {deltaC}
Swirl , !- Diffuser Type
1.7, !- Transition Height {m}
Autocalculate , !- Coefficient A
Autocalculate , !- Coefficient B
Autocalculate , !- Coefficient C
Autocalculate , !- Coefficient D
Autocalculate; !- Coefficient E
1.13.12.2 Outputs
Tocc − Tsup
(1.22)
Tret − Tsup
502 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.13.13 RoomAirSettings:UnderFloorAirDistributionExterior
This model is applicable to exterior spaces that are served by an underfloor air distribution system.
The dominant sources of heat gain should be from people, equipment, and other localized sources
located in the occupied part of the room, as well as convective gain coming from a warm window.
The model predicts two temperatures in the room:
– An occupied subzone temperature (TOC ), representing the temperature in the region between
the floor and the boundary of the upper subzone..
– An upper subzone temperature (TMX ) essential for overall energy budget calculations and for
modeling comfort effects of the upper layer temperature.
The following fields are used to define an instance of the ‘UCSD UFAD Exterior Model Controls’
object.
1.13.13.1 Inputs
1.13.13.2 Outputs
1.13.13.2.10 Room Air Zone Window Plume Heat Transfer Rate [W]
The convective heat gain from windows in an UnderFloorAirDistributionExterior zone.
Tocc − Tsup
(1.23)
Tret − Tsup
– RoomAirSettings:AirflowNetwork
– RoomAir:Node:AirflowNetwork
– RoomAir:Node:AirflowNetwork:AdjacentSurfaceList
– RoomAir:Node:AirflowNetwork:InternalGains
– RoomAir:Node:AirflowNetwork:HVACEquipment
– AirflowNetwork:Intrazone:Node
– AirflowNetwork:Intrazone:Linkage
The first five objects are described below. The last two objects are described in the Airflow Network
Model section. This model also requires additional AirflowNetwork:* objects to form a complete
network.
1.13.15 RoomAirSettings:AirflowNetwork
This object provides inputs in a thermal zone needed for the RoomAirflowNetwork model. The
inputs specify a thermal zone and a list of RoomAir nodes. The object gives a summary of the
model configuration in a zone.
1.13. GROUP – ROOM AIR MODELS 507
1.13.15.1 Inputs
RoomAirSettings:AirflowNetwork ,
NORTH_ZONE , !- Name
NORTH_ZONE , !- Zone Name
RoomAir Schedule , !- Availability Schedule Name
NORTH_ZONE , !- Control Point RoomAir:Node Name
LeftUpper , !- RoomAir:Node:AirflowNetwork 1 Name
CentralUpper , !- RoomAir:Node:AirflowNetwork 2 Name
NORTH_ZONE , !- RoomAir:Node:AirflowNetwork 3 Name
LeftMiddle , !- RoomAir:Node:AirflowNetwork 4 Name
LeftLower , !- RoomAir:Node:AirflowNetwork 5 Name
CentralLower; !- RoomAir:Node:AirflowNetwork 6 Name
1.13.16 RoomAir:Node:AirflowNetwork
This object is used to define a node in a thermal zone. The input specifies the fraction of zone
volume and provides a list of names to define fraction of internal gains, surface connection and
HVAC equipment.
1.13.16.1 Inputs
1.13.17 RoomAir:Node:AirflowNetwork:AdjacentSurfaceList
This object is used to provide a list of connected adjacent surfaces with convective heat transfer
between surfaces and this particular node. When a moisture mode is assigned to surfaces, convective
moisture transfer will be calculated. It should be pointed out that a fraction of a surface exposed to
this particular node is not allowed.
RoomAir:Node:AirflowNetwork:AdjacentSurfaceList ,
Surface_18_T_List , !- Name
Surface_18_T; !- Surface 1 Name
1.13. GROUP – ROOM AIR MODELS 509
1.13.18 RoomAir:Node:AirflowNetwork:InternalGains
This object is used to define a list of internal gains in the same zone and associated fraction assigned
to this particular node.
1.13.18.1 Inputs
1.13.19 RoomAir:Node:AirflowNetwork:HVACEquipment
This object is used to define a list of HVAC equipment objects in the same zone and associated
fractions assigned to this particular node.
1.13.19.1 Inputs
1.13.19.1.5 Field: Fraction of Input or Return Air from HVAC Equipment <#>
The field specifies a fraction of return air from the particular equipment to this node.
This object is extensible, so additional groups fields of these last four fields can be added to the end
of this object.
RoomAir:Node:AirflowNetwork:HVACEquipment ,
CentralUpper_HVAC , !- Name
ZoneHVAC:PackagedTerminalAirConditioner , !- ZoneHVAC or Air Terminal Equipment Object Type 1
NORTH_ZONE PTAC , !- ZoneHVAC or Air Terminal Equipment Object Name 1
0.14, !- Fraction of Output or Supply Air from HVAC Equipment 1
0.14; !- Fraction of Input or Return Air to HVAC Equipment 1
1.13.19.2 Outputs
Each room air model sets up outputs specific to that model. The effect of room air modeling is
usually to adjust the adjacent air temperature along the inside surface of heat transfer surfaces. The
output report “Surface Int Adjacent Air Temperature [C]” is provided for this and described under
Surface Outputs.
1.13.19.3 Outputs
greater than 100 characters a warning will be shown and it will be truncated. If the resulting name
duplicates another such concatenated name, there will be a severe error and terminate the run. The
concatenated name is used when referring to specific instances of internal gains for Output:Variables,
Energy Management System (EMS) controls, and Demand Limiting Controls.
Space Name will result in one instance of the internal gain, named <Object Name>. The full
magnitude of the gain will be applied to the Space using the design level, space floor area, or
space occupancy as appropriate.
SpaceList Name will result in one instance of the internal gain for each Space in the SpaceList,
named <Space Name> <Object Name>. The full magnitude of the gain will be applied to
each Space in the SpaceList using the design level, space floor area, or space occupancy as
appropriate.
Zone Name will result in one instance of the internal gain for each Space in the Zone. If there
is only one Space in the Zone, then the single instance will be named <Object Name>. If
there is more than one Space in the Zone, then each instance will be named <Space Name>
<Object Name>. The full magnitude of the gain will be split between the Spaces in the Zone
apportioned by the Space floor area or occupancy depending on the input method.
ZoneList Name will result in one instance of the internal gain for each Space in each Zone in the
ZoneList. Each instance will be named <Space Name> <Object Name>. The full magnitude
of the gain will be applied to each Zone in the ZoneList then split between the Spaces in each
Zone apportioned by the Space floor area or occupancy depending on the input method.
One exception to this is ElectricEquipment:ITE:AirCooled which only allows Zone or Space Name.
If a Zone Name is specified which contains more than one Space, the same rules apply.
As an example, assume that Zone 1 contains Space 1A and Space 1B, and Zone 2 contains only
Space 2 (objects are abbreviated for clarity):
Space ,
Space 1A, !- Name
Zone 1, !- Zone Name
75.0, !- Floor Area
Space ,
Space 1B, !- Name
Zone 1; !- Zone Name
25.0, !- Floor Area
Space ,
Space 2, !- Name
Zone 2, !- Zone Name
SpaceList ,
All Spaces , !- Name
Space 1A, !- Space 1 Name
Space 1B, !- Space 2 Name
Space 2, !- Space 3 Name
People ,
Office People , !- Name
Zone 1, !- Zone or ZoneList or Space or SpaceList Name
100.0 , !- Number of People
People ,
Lunchroom People , !- Name
Zone 2, !- Zone or ZoneList or Space or SpaceList Name
50.0, !- Number of People
People ,
1.14. GROUP – INTERNAL GAINS 513
Space 1A Office People , 75 people. (concatenated name , apportioned by space floor area)
Space 1B Office People , 25 people. (concatenated name , apportioned by space floor area)
Lunchroom People , 50 people. (simple object name for a single space)
Space 1A Cleaning Crew , 2 people. (full load applied to each space in SpaceList)
Space 1B Cleaning Crew , 2 people.
Space 2 Cleaning Crew , 2 people.
1.14.2 People
The people statement is used to model the occupant’s effect on the space conditions. The following
definition addresses the basic affects as well as providing information that can be used to report the
thermal comfort of a group of occupants. The Fanger, Pierce Two-Node, Kansas State University
Two-Node, ASHRAE Standard 55 Elevated Air Cooling Effect model, and ASHRAE Standard 55
Ankle Draft Risk thermal comfort models are available in EnergyPlus. A user may select any of
these models for each People statement by simply adding the appropriate choice keyword after the
air velocity schedule name. Thermal comfort calculations will only be made for people statements
that include specific requests for these thermal comfort models. This object also requires input of
carbon dioxide generation rate based on people activity level for zone carbon dioxide simulations.
1.14.2.1 Inputs
– People
With this choice, the method used will be a straight insertion of the number of occupants (peo-
ple). (The Number of People field should be filled.)
– People/Area
With this choice, the method used will be a factor per floor area of the zone. (The People per Zone
Floor Area field should be filled).
– Area/Person
With this choice, the method used will be a factor of floor area per person. (The Zone Floor Area
per Person field should be filled).
Resting
Sleeping 72 40 0.7
Reclining 81 45 0.8
Seated, quiet 108 60 1
Standing, relaxed 126 70 1.2
Walking (on level surface)
516 CHAPTER 1. INPUT-OUTPUT REFERENCE
Reading, seated 99 55 1
Writing 108 60 1
Typing 117 65 1.1
Filing, seated 126 70 1.2
Filing, standing 144 80 1.4
Walking about 180 100 1.7
Lifting/packing 216 120 2.1
Miscellaneous Occupational
Activities
area-emissivity weighted average of all of the surfaces in the zone. In cases where the emissivity
of all of the surfaces are sufficiently small (near zero), the mean radiant temperature will be set to
the mean air temperature of the space to avoid divide by zero errors. The other MRT calculation
type is “SurfaceWeighted”. The goal of this calculation type is to estimate a person in the space
close to a particular surface without having to define exact view factors for all of the surfaces and
the location of the person in the space. The MRT used in the thermal comfort calculations when
the “surface weighted” calculation type is selected is actually the average of the temperature of
the surface to which the person is closest (defined by the next field “Surface Name”) and the zone
averaged MRT (defined above). The surface temperature alone is not used because in theory the
maximum view factor from a person to any flat surface is roughly 0.5. In the “surfaceweighted”
calculation, the surface in question actually gets slightly more weighting than 50% since the surface
selected is still a part of the zone average MRT calculation. Again, this simplification was made to
avoid the specification of view factors and the exact location of the person.
A third option is to use “AngleFactor”. This option allows for more explicit positioning of the person
within the space by defining the angle factors from the person to the various surfaces in the zone.
This option requires the user to list the surfaces that the person can see from a radiation standpoint
and also define the angle (or view) factor for each surface. The ComfortViewFactorAngles object
(see next object description) is intended to give the user this opportunity.
– ClothingInsulationSchedule
With this choice, the method used will be a straight insertion of the scheduled clothing insulation
values of occupants (people). (The Clothing Insulation Schedule Name field should be filled.)
– DynamicClothingModelASHRAE55
With this choice, the method used will be the dynamic predictive clothing insulation model developed
by Schiavon and Lee (2013) based on 6,333 selected observations taken from ASHRAE RP-884 and
RP-921 databases. It varies the clothing insulation as a function of outdoor air temperature measured
at 6am as illustrated below.
– CalculationMethodSchedule
With this choice, the method used can be either the ClothingInsulationSchedule or the Dynamic-
ClothingModelASHRAE55, depending on a schedule (to be entered as the next field) that determines
which method to use in different time of a day. When this option is chosen, the next field “Clothing
Insulation Calculation Method Schedule Name” is a required input.
Figure 1.68: Graphical representation fo the dynamic predictive clothing insulation model
520 CHAPTER 1. INPUT-OUTPUT REFERENCE
Fanger Fanger’s Comfort model is applied to calculate related thermal comfort metrics. Fanger
Model PMV, PPD, and Clothing Surface Temperature are calculated and reported as each time
step. Apart from existing required fields in People object, extra fields required for this model
include Surface Name/Angle Factor List Name, Work Efficiency Schedule Name, Clothing
Insulation Schedule Name, and Air Velocity Schedule Name.
Pierce The Pierce Two-Node model is applied to calculate related thermal comfort metrics. Pierce
Model Effective Temperature PMV, Standard Effective Temperature PMV, Discomfort Index,
Thermal Sensation Index, and Standard Effective Temperature are calculated and reported as
each time step.Apart from existing required fields in People object, extra fields required for
this model include Surface Name/Angle Factor List Name, Work Efficiency Schedule Name,
Clothing Insulation Schedule Name, and Air Velocity Schedule Name.
KSU The KSU Two-Node Model is applied to calculate related thermal comfort metrics. KSU
Model Thermal Sensation Vote is calculated and reported as each time step. Note that the
KSU model is computationally intensive and may noticeably increase the execution time of
the simulation. Apart from existing required fields in People object, extra fields required for
this model include Surface Name/Angle Factor List Name, Work Efficiency Schedule Name,
Clothing Insulation Schedule Name, and Air Velocity Schedule Name.
AdaptiveASH55 Adaptive Comfort Model Based on ASHRAE Standard 55-2010 is applied to
calculate related thermal comfort metrics. ASHRAE 55 Adaptive Model 90% Acceptability
Status, 80% Acceptability Status, Running Average Outdoor Air Temperature, and the Adap-
tive Model Temperature are calculated and reported as each time step. AdaptiveASH55 is only
applicable when the running average outdoor air temperature for the past 7 days is between
10.0 and 33.5C.
AdaptiveCEN15251 Adaptive Comfort Model Based on European Standard EN15251-2007 is
applied to calculate related thermal comfort metrics. CEN 15251 Adaptive Model Category
I/II/II Status, Running Average Outdoor Air Temperature, and the Adaptive Model Temper-
ature are calculated and reported as each time step. AdaptiveCEN15251 is only applicable
when the running average outdoor air temperature for the past 30 days is between 10.0 and
30.0C.
1.14. GROUP – INTERNAL GAINS 521
CoolingEffectASH55 ASHRAE 55-2017 Elevated Air Speed Cooling Effect Model is applied to
calculate related thermal comfort metrics. Elevated Air Speed Cooling Effect, Cooling Effect
Adjusted PMV, and Cooling Effect Adjusted PPD are calculated and reported as each time
step. Apart from existing required fields in People object, extra fields required for this model
include Surface Name/Angle Factor List Name, Work Efficiency Schedule Name, Clothing
Insulation Schedule Name, and Air Velocity Schedule Name.
AnkleDraftASH55 ASHRAE 55-2017 Ankle Draft Risk Model is applied to calculate related
thermal comfort metrics. Zone Thermal Comfort ASHRAE 55 Ankle Draft PPD is calculated
and reported as each time step. Apart from existing required fields in People object, extra
fields required for this model include Surface Name/Angle Factor List Name, Work Efficiency
Schedule Name, Clothing Insulation Schedule Name, Air Velocity Schedule Name, and Ankle
Level Air Velocity Schedule Name. Ankle draft PPD calculations are only applicable for relative
air velocity is below 0.2 m/s, and the subject’s metabolic rate and clothing level should be kept
below 1.3 met and 0.7 clo. PPD at ankle draft will be set to -1.0 if if these conditions are not
met.
For descriptions of the thermal comfort calculations, see the Engineering Reference document.
Note that since up to seven models may be specified, the user may opt to have EnergyPlus calculate
the thermal comfort for people identified with this people statement using all seven models if desired.
People ,
Kitchen_ZN_1_FLR_1 , !- Name
Kitchen_ZN_1_FLR_1 , !- Zone or ZoneList or Space or SpaceList Name
BLDG_OCC_SCH , !- Number of People Schedule Name
People , !- Number of People Calculation Method
25.2000,,, !- Number of People , People per Zone Floor Area , Zone Floor Area per Person
0.3000 , !- Fraction Radiant
AUTOCALCULATE , !- Sensible Heat Fraction
ACTIVITY_SCH , !- Activity Level Schedule Name
3.82E-8, !- Carbon Dioxide Generation Rate {m3/s-W}
No , !- Enable ASHRAE 55 Comfort Warnings
ZoneAveraged , !- Mean Radiant Temperature Calculation Type
, !- Surface Name/Angle Factor List Name
WORK_EFF_SCH , !- Work Efficiency Schedule Name
ClothingInsulationSchedule , !- Clothing Insulation Calculation Method
, !- Clothing Insulation Calculation Method Schedule Name
CLOTHING_SCH , !- Clothing Insulation Schedule Name
AIR_VELO_SCH , !- Air Velocity Schedule Name
Fanger; !- Thermal Comfort Model 1 Type
People ,
RIGHT FORK , !- Name
RIGHT FORK , !- Zone or ZoneListName
Dorm Occupancy , !- Number of People Schedule Name
people , !- Number of People Calculation Method
8.00000 , !- Number of People ,
, !- People per Zone Floor Area
, !- Zone Floor Area per Person
0.6000000 , !- Fraction Radiant
Autocalculate , !- Sensible Heat Fraction
Activity Sch , !- Activity level Schedule Name
People ,
AllZones with People , !- Name
AllOccupiedZones , !- Zone or ZoneList or Space or SpaceList Name
OCCUPY -1, !- Number of People Schedule Name
People/Area , !- Number of People Calculation Method
, !- Number of People
.11, !- People per Zone Floor Area {person/m2}
, !- Zone Floor Area per Person {m2/person}
0.3, !- Fraction Radiant
, !- Sensible Heat Fraction
ActSchd , !- Activity Level Schedule Name
3.82E-8, !- Carbon Dioxide Generation Rate {m3/s-W}
No , !- Enable ASHRAE 55 Comfort Warnings
surfaceweighted , !- Mean Radiant Temperature Calculation Type
Zn001:Wall001 , !- Surface Name/Angle Factor List Name
Work Eff Sch , !- Work Efficiency Schedule Name
ClothingInsulationSchedule , !- Clothing Insulation Calculation Method
, !- Clothing Insulation Calculation Method Schedule Name
Clothing Sch , !- Clothing Insulation Schedule Name
Air Velo Sch , !- Air Velocity Schedule Name
FANGER , !- Thermal Comfort Model 1 Type
PIERCE , !- Thermal Comfort Model 2 Type
KSU; !- Thermal Comfort Model 3 Type
1.14.2.2 Outputs
People objects have output variables for individual objects and for space and zone totals.
People specific outputs include:
It should be noted that if a user is trying to output the Standard Effective Temperature (SET) that
the Pierce two-node model must be selected. This variable is calculated as part of the Pierce model
and can be seen in the output by requesting Zone Thermal Comfort Pierce Model Standard Effective
Temperature.
object, then the value of the PPD is determined by using the air temperature and humidity that is
calculated at the system time step; otherwise, if the zone is uncontrolled, the PPD is determined
using the zone air temperature and humidity that is averaged over the zone time step.
This field is the “predicted mean vote” (PMV) calculated using the effective temperature and the
Pierce two-node thermal comfort model.
1.14.2.2.40 Zone Thermal Comfort CEN 15251 Adaptive Model Category I Sta-
tus
This field is to report whether the operative temperature falls into the Category I (90% acceptability)
limits of the adaptive comfort in the European Standard EN15251-2007. A value of 1 means within
(inclusive) the limits, a value of 0 means outside the limits, and a value of -1 means not applicable
(when unoccupied or running average outdoor temp is outside the range of 10.0 to 30.0C).
1.14.2.2.41 Zone Thermal Comfort CEN 15251 Adaptive Model Category II Sta-
tus
This field is to report whether the operative temperature falls into the Category II (80% acceptability)
limits of the adaptive comfort in the European Standard EN15251-2007. A value of 1 means within
(inclusive) the limits, a value of 0 means outside the limits, and a value of -1 means not applicable
(when unoccupied or running average outdoor temp is outside the range of 10.0 to 30.0C).
1.14.2.2.42 Zone Thermal Comfort CEN 15251 Adaptive Model Category III
Status
This field is to report whether the operative temperature falls into the Category III (65% accept-
ability) limits of the adaptive comfort in the European Standard EN15251-2007. A value of 1 means
within (inclusive) the limits, a value of 0 means outside the limits, and a value of -1 means not ap-
plicable (when unoccupied or running average outdoor temp is outside the range of 10.0 to 30.0C).
530 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.14.2.2.43 Zone Thermal Comfort CEN 15251 Adaptive Model Running Aver-
age Outdoor Air Temperature
This field reports the weighted average of the outdoor air temperature of the previous seven days,
an input parameter for the CEN-15251 adaptive comfort model.
1.14.2.3 Outputs
The following output variables are all based on whether the humidity ratio and the operative tem-
perature is within the region shown in ASHRAE Standard 55-2004 in Figure 5.2.1.1. For these
outputs the operative temperature is simplified to be the average of the air temperature and the
mean radiant temperature. For summer, the 0.5 Clo level is used and, for winter, the 1.0 Clo level
is used. The graphs below are based on the following tables which extend the ASHRAE values to
zero humidity ratio.
1.14. GROUP – INTERNAL GAINS 531
19.6 0.012
23.9 0.012
26.3 0.000
21.7 0.000
23.6 0.012
26.8 0.012
28.3 0.000
25.1 0.000
532 CHAPTER 1. INPUT-OUTPUT REFERENCE
You may decide if you need to change parameters to reduce these “uncomfortable” hours. The
individual output variables shown previously may help you get more details on when these are
occurring.
Following are some suggestions that might be applicable:
1.14.4 ComfortViewFactorAngles
When requesting EnergyPlus to do a thermal comfort calculation, the program user has three options
for defining how the mean radiant temperature will be calculated. The user may select “zoneaver-
aged” which results in a mean radiant temperature that is characteristic of an “average” location
near the center of the zone. The user may also elect to place the person near a particular surface
by selecting “surfaceweighted” in the People statement. This takes the average of the zone mean
radiant temperature and the temperature of the surface that the person is near and uses this value
as the mean radiant temperature when calculating thermal comfort.
The third option is for the user to more explicitly position the person within the space by defining
the angle factors from the person to the various surfaces in the zone. This option requires the user
to list the surfaces that the person can see from a radiation standpoint and also define the angle
(or view) factor for each surface. The AngleFactorList input line is intended to give the user this
opportunity.
1.14.4.1 Inputs
1.14.5 Lights
The Lights statement allows you to specify information about a zone’s electric lighting system,
including design power level and operation schedule, and how the heat from lights is distributed
thermally.
A zone may have multiple Lights statements. For example, one statement may describe the general
lighting in the zone and another the task lighting. Or you can use multiple Lights statements for a
zone that has two or more general lighting systems that differ in design level, schedule, etc.
1.14.5.1 Inputs
– LightingLevel
With this choice, the method used will be a straight insertion of the lighting level (Watts) for the
Zone. (The Lighting Level field should be filled.)
– Watts/Area
With this choice, the method used will be a factor per floor area of the zone. (The Watts per Zone
Floor Area field should be filled).
– Watts/Person
With this choice, the method used will be a factor of lighting level (watts) per person. (The Watts
per person field should be filled).
536 CHAPTER 1. INPUT-OUTPUT REFERENCE
the lights are allowed to be dimmed by the applicable daylighting control. If daylighting controls
are operating in the space or zone, all of the applicable Lights objects with a Fraction Replaceable
greater than zero will be reduced by a multiplicative factor that accounts for how much the electric
lighting is lowered due to daylighting (ref. Daylighting Lighting Power Multiplier).
where Tplenum is the previous-time-step value of the return plenum air temperature (C),
and C1 and C2 are the values of the coefficients entered in the next two fields.
To compensate for the change in the return air fraction relative to its input value, the program
modifies Fraction Radiant and fconvected by a scale factor such that
Figure 1.71: Vertical section through a zone and its return air plenum showing recessed lighting (not
to scale). The heat from lights is divided into four fractions, three of which — ReturnAirFraction,
FractionRadiant and FractionConvected — depend on plenum air temperature.
An IDF example:
Lights ,
RIGHT FORK Lights 1, !- Name
RIGHT FORK , !- Zone Name
Office Lighting , !- SCHEDULE Name
LightingLevel , !- Design Level calculation method
1.14. GROUP – INTERNAL GAINS 541
Lights ,
AllZones with Lights , !- Name
AllOccupiedZones , !- Zone or ZoneList or Space or SpaceList Name
LIGHTS -1, !- Schedule Name
Watts/Area , !- Design Level Calculation Method
, !- Lighting Level {W}
16, !- Watts per Zone Floor Area {W/m2}
, !- Watts per Person {W/person}
0.2, !- Return Air Fraction
0.59, !- Fraction Radiant
0.2, !- Fraction Visible
0, !- Fraction Replaceable
GeneralLights; !- End -Use Subcategory
1.14.5.2 Outputs
Lights objects have output variables for individual objects and for space and zone totals.
A related output is Daylighting Lighting Power Multiplier.
1.14.6 ElectricEquipment
The object models equipment in the zone which consumes electricity, such as computers, televisions,
and cooking equipment, also known as “plug loads.” All of the energy consumed by the equipment
becomes a heat gain in the zone or is lost (exhausted) as specified below.
1.14.6.1 Inputs
– EquipmentLevel
With this choice, the method used will be a straight insertion of the electric equipment level (Watts)
for the Zone. (The Design Level field should be filled.)
– Watts/Area
With this choice, the method used will be a factor per floor area of the zone. (The Watts per Zone
Floor Area field should be filled).
– Watts/Person
With this choice, the method used will be a factor of equipment level (watts) per person. (The
Watts per Person field should be filled).
You will get an error message if Fraction Latent + Fraction Radiant + Fraction Lost exceeds 1.0.
ElectricEquipment ,
DORM ROOMS AND COMMON AREAS ElecEq 1, !- Name
DORM ROOMS AND COMMON AREAS , !- Zone Name
Residence Equipment , !- SCHEDULE Name
EquipmentLevel , !- Design Level calculation method
9210.921 , !- Design Level {W}
, !- Watts per Zone Floor Area {watts/m2}
, !- Watts per Person {watts/person}
0.0000000E+00, !- Fraction Latent
0.3000000 , !- Fraction Radiant
0.0000000E+00, !- Fraction Lost
Computers; !- End -use Subcategory
ElectricEquipment ,
AllZones with Electric Equipment , !- Name
AllOccupiedZones , !- Zone or ZoneList or Space or SpaceList Name
EQUIP -1, !- Schedule Name
Watts/Person , !- Design Level Calculation Method
, !- Design Level {W}
, !- Watts per Zone Floor Area {W/m2}
96, !- Watts per Person {W/person}
0, !- Fraction Latent
0.3, !- Fraction Radiant
0; !- Fraction Lost
1.14.7 GasEquipment
The object models equipment in the zone which consumes natural gas, such as cooking equipment
or a gas fireplace. All of the energy consumed by the equipment becomes a heat gain in the zone or
is lost (exhausted) as specified below.
1.14.7.1 Inputs
– EquipmentLevel
With this choice, the method used will be a straight insertion of the gas equipment level (Watts) for
the Zone. (The Design Level field should be filled.)
– Watts/Area or Power/Area
With this choice, the method used will be a factor per floor area of the zone. (The Power per Zone
Floor Area field should be filled).
– Watts/Person or Power/Person
With this choice, the method used will be a factor of equipment level (watts) per person. (The
Power per Person field should be filled).
You will get an error message if Fraction Latent + Fraction Radiant + Fraction Lost exceeds 1.0.
1.14. GROUP – INTERNAL GAINS 549
GasEquipment ,
Office Zones with Gas , !- Name
OfficeZones , !- Zone or ZoneList or Space or SpaceList Name
Gas Eq Sch , !- Schedule Name
Watts/Area , !- Design Level Calculation Method
, !- Design Level {W}
197, !- Power per Zone Floor Area {W/m2}
, !- Power per Person {W/Person}
0.0000000E+00, !- Fraction Latent
0.3000000 , !- Fraction Radiant
0.0000000E+00; !- Fraction Lost
1.14.8 HotWaterEquipment
The object models hot water equipment in the zone which consumes district heating, such as cooking
equipment or process loads. All of the energy consumed by the equipment becomes a heat gain in the
zone or is lost (exhausted) as specified below. This object consumes district heating energy directly
and does not cause a load on a hot water plant loop or water heater. For domestic hot water uses,
such as sinks and showers, see WaterUse:Equipment.
1.14.8.1 Inputs
– EquipmentLevel
With this choice, the method used will be a straight insertion of the hot water equipment level
(Watts) for the Zone. (The Design Level field should be filled.)
– Watts/Area or Power/Area
With this choice, the method used will be a factor per floor area of the zone. (The Power per Zone
Floor Area field should be filled).
– Watts/Person or Power/Person
With this choice, the method used will be a factor of equipment level (watts) per person. (The
Power per Person field should be filled).
You will get an error message if Fraction Latent + Fraction Radiant + Fraction Lost exceeds 1.0.
552 CHAPTER 1. INPUT-OUTPUT REFERENCE
HotWaterEquipment ,
Office Zones with HoWater Equipment ,!- Name
OfficeZones , !- Zone or ZoneList or Space or SpaceList Name
HotWater Eq Sch , !- Schedule Name
Watts/Area , !- Design Level Calculation Method
, !- Design Level {W}
50, !- Power per Zone Floor Area {W/m2}
, !- Power per Person {W/Person}
0.0000000E+00, !- Fraction Latent
1.14. GROUP – INTERNAL GAINS 553
1.14.9 SteamEquipment
The object models steam equipment in the zone which consumes district heating, such as cooking
equipment or process loads. All of the energy consumed by the equipment becomes a heat gain
in the zone or is lost (exhausted) as specified below. This object consumes district heating energy
directly and does not cause a load on a steam plant loop.
1.14.9.1 Inputs
– EquipmentLevel
With this choice, the method used will be a straight insertion of the steam equipment level (Watts)
for the Zone. (The Design Level field should be filled.)
– Watts/Area or Power/Area
With this choice, the method used will be a factor per floor area of the zone. (The Power per Zone
Floor Area field should be filled).
– Watts/Person or Power/Person
With this choice, the method used will be a factor of equipment level (watts) per person. (The
Power per Person field should be filled).
554 CHAPTER 1. INPUT-OUTPUT REFERENCE
You will get an error message if Fraction Latent + Fraction Radiant + Fraction Lost exceeds 1.0.
SteamEquipment ,
SPACE4 -1 ElecEq 1, !- Name
SPACE4 -1, !- Zone or ZoneList or Space or SpaceList Name
EQUIP -1, !- SCHEDULE Name
EquipmentLevel , !- Design Level calculation method
1050, !- Design Level {W}
, !- Power per Zone Floor Area {watts/m2}
, !- Power per Person {watts/person}
0.5, !- Fraction Latent
0.3, !- Fraction Radiant
0, !- Fraction Lost
Laundry; !- End -Use Subcategory
1.14.10 OtherEquipment
Other Equipment object is provided as an additional source for heat gains or losses directly to the
zone with a fuel type that is configurable. If a fuel type is specified, the energy is attributed to the
appropriate end use. Otherwise, a loss can be entered by putting a negative value into the Design
Level field and this object will not have an end-use component – gains or losses do not show up in
the bottom energy lines (except as influencing overall zone gains or losses).
1.14.10.1 Inputs
– EquipmentLevel
With this choice, the method used will be a straight insertion of the other equipment level (Watts)
for the Zone. (The Design Level field should be filled.)
– Watts/Area or Power/Area
With this choice, the method used will be a factor per floor area of the zone. (The Power per Zone
Floor Area field should be filled).
– Watts/Person or Power/Person
With this choice, the method used will be a factor of equipment level (watts) per person. (The
Power per Person field should be filled).
You will get an error message if FractionLatent + FractionRadiant + FractionLost exceeds 1.0.
OtherEquipment ,
BASE -1 OthEq 1, !- Name
Propane , !- Fuel Use Type
BASE -1, !- Zone or ZoneList or Space or SpaceList Name
ALWAYSON , !- SCHEDULE Name
EquipmentLevel , !- Design Level calculation method
6766. , !- Design Level {W}
, !- Power per Zone Floor Area {watts/m2}
, !- Power per Person {watts/person}
0, !- Fraction Latent
0.3, !- Fraction Radiant
0, !- Fraction Lost
1.2E-7, !- Carbon Dioxide Generation Rate
SubCategory1; !- End -Use Subcategory
Gas Equipment
HotWater Equipment
Steam Equipment
Other Equipment
1.14.11.0.11 Space or Zone Hot Water Equipment District Heating Rate [W]
1.14.11.0.12 Space or Zone Hot Water Equipment District Heating Energy [J]
The hot water equipment district heating consumption in Watts (for power) or Joules (for energy).
It is the sum of the radiant, convective, latent and lost components. Hot Water Equipment District
Heating Energy is added to the following district heating meters:.
DistrictHeating:Facility
DistrictHeating:Building
DistrictHeating:Zone:<Zone Name >
DistrictHeating:SpaceType:<Space Type Name >
InteriorEquipment:DistrictHeating
InteriorEquipment:DistrictHeating:Zone:<Zone Name >
InteriorEquipment:DistrictHeating:SpaceType:<Space Type Name >
<End -Use Subcategory >: InteriorEquipment:DistrictHeating
<End -Use Subcategory >: InteriorEquipment:DistrictHeating:Zone:<Zone Name >
<End -Use Subcategory >: InteriorEquipment:DistrictHeating:SpaceType:<Space Type Name >
DistrictHeating:Facility
DistrictHeating:Building
DistrictHeating:Zone:<Zone Name >
DistrictHeating:SpaceType:<Space Type Name >
InteriorEquipment:DistrictHeating
InteriorEquipment:DistrictHeating:Zone:<Zone Name >
InteriorEquipment:DistrictHeating:SpaceType:<Space Type Name >
<End -Use Subcategory >: InteriorEquipment:DistrictHeating
<End -Use Subcategory >: InteriorEquipment:DistrictHeating:Zone:<Zone Name >
<End -Use Subcategory >: InteriorEquipment:DistrictHeating:SpaceType:<Space Type Name >
The amount of heat gain from equipment that is convected to the space or zone air.
1.14.12 ElectricEquipment:ITE:AirCooled
This object describes air-cooled electric information technology equipment (ITE) which has variable
power consumption as a function of loading and temperature.
1.14. GROUP – INTERNAL GAINS 567
1.14.12.1 Inputs
1.14.12.1.10 Field: CPU Power Input Function of Loading and Air Temperature
Curve Name
The name of a two-variable curve or table lookup object which modifies the CPU power input as a
function of CPU loading (x) and air inlet node temperature (y). This curve (table) should equal 1.0
at design conditions (CPU loading = 1.0 and Design Entering Air Temperature).
1.14.12.1.12 Field: Design Fan Air Flow Rate per Power Input
Specifies the cooling fan air flow rate in m3/s per Watt of total electric power input at design
conditions (CPU loading = 1.0 and Design Entering Air Temperature).
This is normalized by power input to allow the design power input to be changed without needing
to change this value.
1.14.12.1.13 Field: Air Flow Function of Loading and Air Temperature Curve
Name
The name of a two-variable curve or table lookup object which modifies the cooling air flow rate as
a function of CPU loading (x) and air inlet node temperature (y). This curve (table) should equal
1.0 at design conditions (CPU loading = 1.0 and Design Entering Air Temperature).
1.14.12.1.24 Field: Electric Power Supply Efficiency Function of Part Load Ratio
Curve Name
The name of a single-variable curve or table lookup object which modifies the electric power supply
efficiency as a function of part load ratio (x). This curve (table) should equal 1.0 at the design power
consumption (part load ratio = 1.0). If this curve is left blank, then the curve is assumed to always
equal 1.0.
object). Any text may be used here to categorize the end-uses in the ABUPS End Uses by Subcat-
egory table and in the LEED Summary table EAp2-4/5 Performance Rating Method Compliance.
The default is ITE-UPS
ElectricEquipment:ITE:AirCooled ,
Data Center Servers , !- Name
Main Zone , !- Zone or Space Name
FlowFromSystem , !- Air Flow Calculation Method
Watts/Unit , !- Design Power Input Calculation Method
500, !- Watts per Unit {W}
200, !- Number of Units
, !- Watts per Zone Floor Area {W/m2}
Data Center Operation Schedule , !- Design Power Input Schedule Name
Data Center CPU Loading Schedule , !- CPU Loading Schedule Name
Model 5250 Power fLoadTemp , !- CPU Power Input Function of Loading and Air Temperature Curve
Name
0.4, !- Design Fan Power Input Fraction
0.0001 , !- Design Fan Air Flow Rate per Power Input {m3/s-W}
Model 5250 AifFlow fLoadTemp , !- Air Flow Function of Loading and Air Temperature Curve Name
ECM FanPower fFlow , !- Fan Power Input Function of Flow Curve Name
15, !- Design Entering Air Temperature {C}
A3 , !- Environmental Class
AdjustedSupply , !- Air Inlet Connection Type
, !- Air Inlet Room Air Model Node Name
, !- Air Outlet Room Air Model Node Name
Main Zone Inlet Node , !- Supply Air Node Name
572 CHAPTER 1. INPUT-OUTPUT REFERENCE
ElectricEquipment:ITE:AirCooled Outputs
1.14.12.1.37 Space or Zone ITE CPU Electricity Rate at Design Inlet Conditions
[W]
1.14.12.1.39 Space or Zone ITE CPU Electricity Energy at Design Inlet Condi-
tions [J]
1.14. GROUP – INTERNAL GAINS 575
1.14.12.1.45 Space or Zone ITE Fan Electricity Rate at Design Inlet Conditions
[W]
1.14.12.1.47 Space or Zone ITE Fan Electricity Energy at Design Inlet Condi-
tions [J]
1.14.12.1.54 Space or Zone ITE UPS Heat Gain to Zone Rate [W]
1.14.12.1.56 Space or Zone ITE UPS Heat Gain to Zone Energy [J]
1.14.12.1.58 Space or Zone ITE Total Heat Gain to Zone Rate [W]
1.14.12.1.60 Space or Zone ITE Total Heat Gain to Zone Energy [J]
1.14.12.1.62 Space or Zone ITE Standard Density Air Volume Flow Rate [m3/s]
1.14.12.1.64 Space or Zone ITE Current Density Air Volume Flow Rate [m3/s]
1.14. GROUP – INTERNAL GAINS 577
1.14.12.1.74 Space or Zone ITE Any Air Inlet Operating Range Exceeded Time
[hr]
1.14.12.1.76 Space or Zone ITE Any Air Inlet Dry-Bulb Temperature Above
Operating Range Time [hr]
578 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.14.12.1.77 ITE Air Inlet Dry-Bulb Temperature Above Operating Range Time
[hr]
Hours when the dry-bulb temperature of the air entering the ITE is above the range specified by
the ITE Environmental Class.
1.14.12.1.79 Space or Zone ITE Any Air Inlet Dry-Bulb Temperature Below
Operating Range Time [hr]
1.14.12.1.80 ITE Air Inlet Dry-Bulb Temperature Below Operating Range Time
[hr]
Hours when the dry-bulb temperature of the air entering the ITE is above the range specified by
the ITE Environmental Class.
1.14.12.1.82 Space or Zone ITE Any Air Inlet Dewpoint Temperature Above
Operating Range Time [hr]
1.14.12.1.83 ITE Air Inlet Dewpoint Temperature Above Operating Range Time
[hr]
Hours when the dewpoint temperature of the air entering the ITE is above the range specified by
the ITE Environmental Class.
1.14.12.1.85 Space or Zone ITE Any Air Inlet Dewpoint Temperature Below
Operating Range Time [hr]
1.14. GROUP – INTERNAL GAINS 579
1.14.12.1.86 ITE Air Inlet Dewpoint Temperature Below Operating Range Time
[hr]
Hours when the dewpoint temperature of the air entering the ITE is above the range specified by
the ITE Environmental Class.
1.14.12.1.88 Space or Zone ITE Any Air Inlet Relative Humidity Above Oper-
ating Range Time [hr]
1.14.12.1.89 ITE Air Inlet Relative Humidity Above Operating Range Time [hr]
Hours when the relative humidity of the air entering the ITE is above the range specified by the ITE
Environmental Class.
1.14.12.1.90 ITE Air Inlet Relative Humidity Difference Above Operating Range
[%]
The temperature difference (in degrees DeltaC) between the air inlet relative humidity and the
maximum allowable relative humidity specified by the ITE Environmental Class. Only positive
values are reported. When the relative humidity of the air entering the ITE is below the maximum
specified by the ITE Environmental Class, this output will be zero.
1.14.12.1.91 Space or Zone ITE Any Air Inlet Relative Humidity Below Oper-
ating Range Time [hr]
1.14.12.1.92 ITE Air Inlet Relative Humidity Below Operating Range Time [hr]
Hours when the relative humidity of the air entering the ITE is above the range specified by the ITE
Environmental Class.
1.14.12.1.93 ITE Air Inlet Relative Humidity Difference Below Operating Range
[%]
The temperature difference (in degrees DeltaC) between the air inlet relative humidity and the
minimum allowable relative humidity specified by the ITE Environmental Class. Only negative
values are reported. When the relative humidity of the air entering the ITE is above the minimum
specified by the ITE Environmental Class, this output will be zero.
1.14.13 ZoneBaseboard:OutdoorTemperatureControlled
This object specifies outside temperature-controlled (OTC) baseboard heating. The capacities (high
and low) are specified in W at the temperatures specified. The schedule allows both capacities to
change hourly on a proportional basis. This baseboard heater does not operate if the outdoor dry-
bulb is above the high temperature limit. Between the high temperature and the low temperature,
the capacity is interpolated (linear) between the high and the low capacity values. Below the low
temperature, the capacity is set at the low capacity value. This allows the user to add baseboard
heat to a perimeter zone starting at a prescribed temperature and then slowly increases this capacity
to a max value.
Example:
> 10 0
10 100,000
8 180,000
6 260,000
4 340,000
2 420,000
0 500,000
<0 500,000
1.14.13.1 Inputs
energy input for the baseboard equipment in a zone as defined by this statement depends on the
actual outdoor temperature and where that temperature is in the range of Low Temperature to High
Temperature..
ZoneBaseboard:OutdoorTemperatureControlled ,
SPACE4 -1 BBHeat 1, !- Name
SPACE4 -1, !- Zone Name
EQUIP -1, !- SCHEDULE Name
1500, !- Capacity at low temperature {W}
0, !- Low Temperature {C}
500, !- Capacity at high temperature {W}
10, !- High Temperature {C}
0.5, !- Fraction Radiant
Baseboard Heat , !- End -Use Subcategory
20; !- Design Zone Heating Setpoint {C}
1.14.13.2 Outputs
Electricity:Facility
Electricity:Building
Electricity:Zone:<Zone Name >
Electricity:SpaceType:<Space Type Name >
InteriorEquipment:Electricity
InteriorEquipment:Electricity:Zone:<Zone Name >
InteriorEquipment:Electricity:SpaceType:<Space Type Name >
<End -Use Subcategory >: InteriorEquipment:Electricity
<End -Use Subcategory >: InteriorEquipment:Electricity:Zone:<Zone Name >
<End -Use Subcategory >: InteriorEquipment:Electricity:SpaceType:<Space Type Name >
1.14.14 SwimmingPool:Indoor
The Indoor Swimming Pool object is used to describe the indoor swimming pools that are exposed
to the internal environment. There are several rules that should be noted regarding the specification
of an indoor pool in EnergyPlus. First, the pool is linked to a surface that must be a floor. The pool
is assumed to cover the entire floor to which it is linked. If the pool only covers part of the floor in
the actual building, then the user must break the floor up into multiple sections.
As pools attempt to achieve a particular water temperature and have a variety of heat losses, heating
equipment is necessary to maintain the proper setpoint temperature. In EnergyPlus, the pool itself
becomes part of the demand side of a plant loop with heating equipment on the supply side providing
whatever heating is needed to maintain the desired temperature. This heating equipment as well
as the loop connections must be entered separately and the input shown in this section only details
what is needed to specify the pool itself.
There are a variety of rules that limit the application of indoor swimming pools in EnergyPlus. The
following are a list of these rules:
– The pool must reference a valid surface in the input file. This surface must be a floor and
cannot be other surface types like ceilings, walls, windows, etc.
– The pool cannot refer to a surface that is also a radiant system, ventilated slab, or another
pool.
– The surface that the pool references must be modeled using conduction transfer functions
(CTF).
1.14. GROUP – INTERNAL GAINS 585
– The pool cannot utilize movable insulation or have a heat source or sink associated with it
(something used to model low temperature radiant systems).
The following information is useful for defining and modeling an indoor pool in EnergyPlus. For
more information on the algorithm used for this model or details on some of the input parameters,
please reference the indoor pool section of the EnergyPlus Engineering Reference document.
1.14.14.1 Inputs
SwimmingPool:Indoor ,
Test Pool , !- Name
F1 -1, !- Surface Name
1.5, !- Average Depth {m}
PoolActivitySched , !- Pool Activity Schedule
MakeUpWaterSched , !- MakeUp Water Temperature Schedule
PoolCoverSched , !- Pool Cover Schedule
0.0, !- Cover Evaporation Factor
0.2, !- Cover Convection Factor
0.9, !- Cover Short -Wavelength Radiation Factor
0.5, !- Cover Long -Wavelength Radiation Factor
Pool Water Inlet Node , !- Water Inlet Node (Plant/Heater)
Pool Water Outlet Node , !- Water Outlet Node (Plant/Heater)
0.1, !- Maximum flow rate from water heating system {m3/s}
0.6, !- Miscellaneous Equipment Power Factor {W/(m3/s)}
PoolSetpointTempSched , !- Pool Water Setpoint Temperature Schedule
15, !- Maximum Number of People in Pool
PoolOccupancySched , !- Pool People Schedule
PoolOccHeatGainSched; !- Pool People Heat Gain Schedule
1.14.14.2 Outputs
1.14.15 ZoneContaminantSourceAndSink:CarbonDioxide
The ZoneContaminantSourceAndSink:CarbonDioxide object allows users to input carbon diox-
ide sources or sinks in a zone. Note that carbon dioxide generation within a zone can also
be specified using People and GasEquipment objects. Multiple ZoneContaminantSource-
AndSink:CarbonDioxide objects can be specified for the same zone.
1.14.15.1 Inputs
ZoneContaminantSourceAndSink :CarbonDioxide ,
NORTH_ZONE CO2 , !- Name
NORTH_ZONE , !- Zone Name
1.e-6, !- Design Generation Rate {m3/s}
CO2 Source Schedule; !- Schedule Name
1.14.15.2 Outputs
HVAC ,Average , Contaminant Source or Sink CO2 Gain Volume Flow Rate [m3/s]
HVAC ,Average , Zone Contaminant Source or Sink CO2 Gain Volume Flow Rate [m3/s]
1.14.15.2.1 Contaminant Source or Sink CO2 Gain Volume Flow Rate [m3/s]
This output is the net carbon dioxide internal gain/loss in m3 /s for an individual ZoneContami-
nantSourceAndSink:CarbonDioxide object.
592 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.14.15.2.2 Zone Contaminant Source or Sink CO2 Gain Volume Flow Rate
[m3/s]
This output is the net carbon dioxide internal gain/loss in m3 /s for all ZoneContaminantSource-
AndSink:CarbonDioxide objects in a zone.
1.14.16 ZoneContaminantSourceAndSink:Generic:Constant
The ZoneContaminantSourceAndSink:Generic:Constant object specifies the generic contaminant
generation rate and removal rate coefficient in a zone. The associated fraction schedules are re-
quired for allowing users to change the magnitude of sources and sinks. The object is equivalent to
the combination of the constant coefficient model and the burst source model defined in the sources
and sinks element types of CONTAM 3.0. The basic equation used to calculate generic contaminant
source and sink for the constant model is given below:
where
Sf = Contaminant generic contaminant source strength [m3 /s]
Gf = Generic contaminant generation rate [m3 /s]
FG = Fraction value from the source fraction schedule at a given time [dimensionless]
Rf = Generic contaminant effective removal rate [m3 /s]
FR = Fraction value from the sink fraction schedule at a given time [dimensionless]
Cf = Generic contaminant concentration value at a given previous time step [ppm]
1.14.16.1 Inputs
1.14.16.2 Outputs
1.14.17 SurfaceContaminantSourceAndSink:Generic:Pressure-
Driven
The SurfaceContaminantSourceAndSink:Generic:PressureDriven object specifies the generic contam-
inant generation rate coefficient, which is used to calculate the generation rate due to the pressure
difference across the surface. The object is equivalent to the pressure driven model defined in the
sources and sinks element types of CONTAM 3.0. This object assumes to work with the AirflowNet-
work model. The surface has to be defined in the AirflowNetwork:Multizone:Surface. Although the
model is designed to be applied to radon and soil gas entry, it is expanded to be applied to all
contaminant transport, including generic contaminant. However, it should be used in caution. The
basic equation used to calculate generic contaminant source for the pressure driven constant model
is provided below:
where
Sf = Generic contaminant source strength [m3 /s]
Hf = Generic contaminant generation rate coefficient [m3 /s]
FG = Fraction value from the source fraction schedule at a given time [dimensionless]
n = Flow power exponent
Pi = Zone pressure [Pa]
Pj = Pressure in an adjacent zone for a interior surface or outdoor for an exterior surface [Pa]
1.14.17.1 Inputs
1.14.17.2 Outputs
– ZONE,Average,Generic Air Contaminant Pressure Driven Generation Volume Flow Rate [m3/s]
1.14.18 ZoneContaminantSourceAndSink:Generic:CutoffModel
The ZoneContaminantSourceAndSink:Generic contaminant:CutoffModel object specifies the generic
contaminant generation rate based on the cutoff concentration model. The basic equation used to
calculate generic contaminant source for the pressure driven constant model is given below:
( )
Cf (t)
Gf (t) ∗ FG ∗ 1 − Ccutof f Cf < Ccutof f
Sf (t) = (1.33)
0 Cf ≥ Ccutof f
where
Sf = Generic contaminant source strength [m3 /s]
Gf = Generic contaminant generation rate [m3 /s]
FG = Fraction value from the source fraction schedule at a given time [dimensionless]
Ccutoff = Cutoff concentration at which emission ceases [ppm]
Cf = Generic contaminant concentration value at a given previous time step [ppm]
1.14.18.1 Inputs
ZoneContaminantSourceAndSink :Generic:CutoffModel ,
NORTH ZONE GC CutoffModel , !- Name
NORTH ZONE , !- Zone Name
1.0E-5, !- Design Generation Rate Coefficient {m3/s}
GC Source Schedule , !- Schedule Name
100000; !- Cutoff Generic Contaminant at which Emission Ceases {ppm
}
1.14.18.2 Outputs
1.14.19 ZoneContaminantSourceAndSink:Generic:DecaySource
The ZoneContaminantSourceAndSink:Generic:DecaySource object specifies the generic contaminant
generation rate based on the decay source model. The basic equation used to calculate generic
contaminant source for the decay source model is given below:
where
Sf = Generic contaminant source strength [m3 /s]
Gf = Initial generic contaminant generation rate [m3 /s]
FG = Fraction value from the source fraction schedule at a given time [dimensionless]
t = Time since the start of emission [second]
tc = Decay time constant [second]
1.14.19.1 Inputs
Note: The variable t, time since the start of emission, will be reset to zero, when a new run
period starts, or the generation schedule value is equal to zero.
1.14.19.2 Outputs
– Zone,Average,Generic Air Contaminant Decay Model Generation Volume Flow Rate [m3/s]
– Zone,Average,Generic Air Contaminant Decay Model Generation Emission Start Elapsed Time
[s]
1.14.20 SurfaceContaminantSourceAndSink:Generic:Boundary-
LayerDiffusion
The SurfaceContaminantSourceAndSink:Generic:BoundaryLayerDiffusion object specifies the
generic contaminant generation rate from surface diffusion. The object is equivalent to the
boundary layer diffusion model driven model defined in the sources and sinks element types of
CONTAM 3.0.
The boundary layer diffusion controlled reversible sink/source model with a linear sorption isotherm
follows the descriptions presented in [Axley 1991]. The boundary layer refers to the region above
the surface of a material through which a concentration gradient exists between the near-surface
concentration and the air-phase concentration. The rate at which a contaminant is transferred onto
a surface (sink) is defined as:
Cs
Sf = h ∗ ρ ∗ A Cf − ∗ 1.0E − 6 (1.35)
k
where
h = Average film mass transfer coefficient over the sink [m/s]
ρ = Film density of air [kg/m3 ]
A = Surface area of the adsorbent [m2 ]
Cf = Concentration in the air at the previous time step [ppm]
Cs = Concentration in the adsorbent [ppm]
k = Henry adsorption constant or partition coefficient [dimensionless]
1.14.20.1 Inputs
1.14.20.2 Outputs
– ZONE,Average, Generic Air Contaminant Boundary Layer Diffusion Generation Volume Flow
Rate [m3/s]
– ZONE,Average, Generic Air Contaminant Boundary Layer Diffusion Inside Face Concentration
[ppm]
1.14.20.2.2 Generic Air Contaminant Boundary Layer Diffusion Inside Face Con-
centration [ppm]
This output is the average generic contaminant level at the interior surface.
1.14.21 SurfaceContaminantSourceAndSink:Generic:Deposition-
VelocitySink
The SurfaceContaminantSourceAndSink:Generic:DepositionVelocitySink object specifies the generic
contaminant removal rate from a surface. The object is equivalent to the deposition velocity sink
model defined in CONTAM 3.0 sources and sinks element types.
The deposition velocity model provides for the input of a sink’s characteristic in the familiar term
of deposition velocity. The removal stops when the sink concentration level is higher than the zone
air concentration level. The deposition velocity model equation is:
where
Sf (t) = Removal rate at time t [m3 /s]
600 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.14.21.1 Inputs
1.14.21.2 Outputs
– ZONE,Average, Generic Air Contaminant Deposition Velocity Removal Volume Flow Rate
[m3/s]
1.14.22 ZoneContaminantSourceAndSink:Generic:Deposition-
RateSink
The ZoneContaminantSourceAndSink:Generic:DepositionRateSink object specifies the generic con-
taminant removal rate from a zone. The object is equivalent to the deposition rate sink model
defined in CONTAM 3.0 sources and sinks element types.
The deposition rate model provides for the input of a sink’s characteristic in the familiar term of
deposition rate in a zone. The removal stops when the sink concentration level is higher than the
zone air concentration level. The deposition rate model equation is:
Where
Sf (t) = Removal rate at time t [m3 /s]
kd = Deposition rate [1/T]
Vz = Zone volume [m3 ]
m = Element multiplier [dimensionless]
C f (t) = Concentration of generic contaminant at the previous time step [ppm]
FR = Schedule or control signal value at time t [dimensionless]
1.14.22.1 Inputs
1.14.22.2 Outputs
– ZONE,Average, Generic Air Contaminant Deposition Rate Removal Volume Flow Rate [m3/s]
Note that two different methodologies are used in the Daylighting:Controls object (SplitFlux and
DElight) and may be intermixed in a single IDF but may not be used in the same zone.
1.15.1 Daylighting:Controls
When this object is used, daylighting illuminance levels are calculated and then used to determine
how much the electric lighting can be reduced. The daylight illuminance level in a zone depends
on many factors, including sky condition; sun position; calculation point; location, size, and glass
transmittance of windows; window shading devices; and reflectance of interior surfaces. Reduction
of electric lighting depends on daylight illuminance level, illuminance set point, fraction of zone con-
trolled and type of lighting control. Two different methods of computing the daylighitng illuminance
and subsequent lighting reduction called SplitFlux and DElight. After the object description below
is are sections that describe the two methodologies in more detail.
1.15.1.1 Inputs
0-200 1.0
200-400 2/3
400-600 1/3
600 and above 0.0
Lighting Control Type set to ContinuousOff is the same similar to Lighting Control Type set to
Continuous except that the lights switch off completely when the minimum dimming point is reached.
1.15.1.1.6 Field: Minimum Input Power Fraction for Continuous Dimming Con-
trol
For Lighting Control Type set to Continuous, the lowest power the lighting system can dim down
to, expressed as a fraction of maximum input power (see figure, below). For Lighting Control Type
set to ContinuousOff, this is the power fraction reached just before the lights switch off completely.
604 CHAPTER 1. INPUT-OUTPUT REFERENCE
The figure shows the relationship between electric light output and electrical input.
1.15.1.1.7 Field: Minimum Light Output Fraction for Continuous Dimming Con-
trol
For Lighting Control Type set to Continuous, the lowest lighting output the lighting system can
dim down to, expressed as a fraction of maximum light output (see figure). This is the fractional
light output that the system produces at minimum input power. For Lighting Control Type set to
ContinuousOff, this is the light output fraction reached just before the lights switch off completely.
Art Galleries 16
Factories: Rough work 28
Factories: Engine assembly 26
Factories: Fine assembly 24
Factories: Instrument assembly 22
Hospital wards 18
Laboratories 22
Museums 20
Offices 22
School classrooms 20
The maximum surface area for nodes in gridding (subdividing) all surfaces in the zone when Day-
lighting Method is set to DElight. All reflective and transmitting surfaces will be subdivided into
approximately square nodes that do not exceed this maximum. Higher resolution subdivisions re-
quire greater calculation times, but generally produce more accurate results. This same gridding
resolution is also used to subdivide any Complex Fenestration System surfaces. It is advisable to
perform at least one simulation of new input using a small gridding resolution such as 0.1m2 to
compare these results against simulation runs at lower resolution (i.e., higher maximum area nodal
grids) to get a sense of possible levels of error. This input is only used in when the Daylighting
Method is set to DElight. This input is ignored when Daylighting Method is set to SplitFlux.
1.15.1.1.14 Field Set (reference point name, fraction controlled, illuminance set-
point)
This set of fields is used together and can be repeated an unlimited number of times to specify some
of the name of the reference point, the fraction of the zone lighting controlled by that reference point
and the illuminance setpoint that should be applied for daylighting control at that reference point.
1.15.2 Daylighting:ReferencePoint
This object is referenced by Daylighting:Controls to identify the reference point coordinates for
each sensor. The reference points in the zone are where horizontal daylighting illuminance will be
calculated. It is assumed that the photocells that control the overhead electric lighting respond to
the light levels at the specified coordinates. Reference points are given in coordinates specified in
the GlobalGeometryRules object Daylighting Reference Point CoordinateSystem field.
When the DElight Daylighting Method is used, there may be up to a maximum of 100 reference
points for each zone. Each Reference Point that is input does NOT need to be included in the
control of the electric lighting system within the zone. This is determined by the fraction of the zone
controlled by each Reference Point, which can be input as 0. Note when the DElight Daylighting
Method is used, that the sum of all Reference Point control fractions must equal 1 to obtain correct
overall results.
608 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.15.2.1 Inputs
Daylighting:Controls ,
West Zone_DaylCtrl , !- Name
West Zone , !- Zone or Space Name
SplitFlux , !- Daylighting Method
, !- Availability Schedule Name
Continuous , !- Lighting Control Type
0.3, !- Minimum Input Power Fraction for Continuous or ContinuousOff
Dimming Control
0.2, !- Minimum Light Output Fraction for Continuous or ContinuousOff
Dimming Control
, !- Number of Stepped Control Steps
1.0, !- Probability Lighting will be Reset When Needed in Manual Stepped
Control
West Zone_DaylRefPt1 , !- Glare Calculation Daylighting Reference Point Name
180.0 , !- Glare Calculation Azimuth Angle of View Direction Clockwise from
Zone y-Axis {deg}
20.0, !- Maximum Allowable Discomfort Glare Index
, !- DElight Gridding Resolution {m2}
West Zone_DaylRefPt1 , !- Daylighting Reference Point 1 Name
1.0, !- Fraction of Lights Controlled by Reference Point 1
500.; !- Illuminance Setpoint at Reference Point 1 {lux}
Daylighting:ReferencePoint ,
West Zone_DaylRefPt1 , !- Name
West Zone , !- Zone or Space Name
3.048 , !- X-Coordinate of Reference Point {m}
3.048 , !- Y-Coordinate of Reference Point {m}
0.9; !- Z-Coordinate of Reference Point {m}
Following are some guidelines for preparing EnergyPlus input to model the effects of daylighting
when using the SplitFlux method. Before studying these guidelines, however, you should read the
description of each input field under Daylighting:Controls, Daylighting:ReferencePoint, and review
the IDF example, above, and the sample daylighting input, PurchAirWithDaylighting.idf.
1.15. GROUP – DAYLIGHTING 609
Figure 1.74: Example showing location of daylighting reference points in the zone coordinate system
(relative) of a rectangular zone with three windows. (a) Perspective view, (b) plan view, (c) elevation
view. All dimensions are in meters.
610 CHAPTER 1. INPUT-OUTPUT REFERENCE
If an exterior wall in a daylit enclosure has a number of identical windows, the windows should be
entered separately rather than using a window multiplier (ref: FenestrationSurface:Detailed). Using
a multiplier would give an incorrect illuminance calculation since individual windows would not be
positioned correctly on the wall.
A zone multiplier should not be used on a daylit zone if the windows in the zone are shadowed by
exterior obstructions like trees or neighboring buildings, or by obstructions caused by other parts
of building. The reason for this is that the shadowing on the windows of the multiplied zone may
be different from zone to zone depending on exactly how the shadows fall on the zones. However, a
zone multiplier may be used on a daylit zone if the shadowing is by overhangs, fins and/or window
setback.
To correctly calculate both direct and inter-reflected daylight illuminance you should try to model
a thermal zone consisting of several similar rooms separated by interior walls as a representative
room with a zone multiplier (ref: Zone). An example of this is shown in Figure 1.75. Room-1 is the
representative room, with a zone multiplier = 4.
Interior walls IW-1, IW-2 and IW-3 should be treated as adiabatic, i.e., they should have Outside
Boundary Condition = Surface and Outside Boundary Condition Object = IW-1, IW-2, or IW-3,
respectively (ref: BuildingSurface:Detailed). Similarly, if the ceiling and floor of Room-1 are interior
surfaces, they should be treated as adiabatic.
Figure 1.75: For daylighting purposes the thermal zone enclosed by the dashed boundary line should
be modeled as a typical zone (Room-1) with a zone multiplier of 4.
Sometimes a representative room cannot be found. Figure 1.76 shows a section of a building with
four rooms having different daylighting characteristics because of different floor area, orientation
and/or window size. In this case lumping the rooms into a single thermal zone would give nonsen-
sical daylighting illuminance values because of the presence of the interior walls, which EnergyPlus
1.15. GROUP – DAYLIGHTING 611
ignores when calculating illuminance reaching a reference point directly from a window (i.e., without
reflection). The solution in this case is to describe each room as a separate thermal zone with its
own daylighting reference points, and input the interior walls because these will participate in the
calculation of inter-reflected illuminance.
Figure 1.76: Rooms A, B, C and D have different daylighting characteristics. If lumped into a
single thermal zone the daylighting calculation will be less accurate because the blockage of direct
light by the interior walls between these rooms is modeled with some simplifications (see Interior
Obstructions below). To get a good daylighting calculation each room should be input as a separate
thermal zone.
The daylighting control calculation allows a thermal zone or space to be divided into multiple
independently-controlled lighting zones. (See the fields: Daylighting Reference Point Name, Frac-
tion of Lights Controlled by Reference Point, and Illuminance Setpoint at Reference Point.) An
example is shown in Figure 1.77, where a relatively deep thermal zone has two lighting zones of
equal area.
The daylighting calculation accounts for the presence of exterior obstructions in determining the
amount of light that strikes the windows. For daylighting purposes exterior obstructions fall into
three categories:
– Fins, overhangs, trees, neighboring buildings, etc., entered with the objects Shad-
ing:Zone:Detailed, Shading:Site:Detailed, or Shading:Building:Detailed.
– Building surfaces like walls and roofs (in an L-shaped building, for example).
– Surfaces associated with window setback.
612 CHAPTER 1. INPUT-OUTPUT REFERENCE
Figure 1.77: Two independently-controlled lighting zones, each with 50% of the area of the thermal
zone.
Category (1) obstructions can have an associated solar transmittance schedule (see description of
the field Transmittance Schedule Name for these shading surfaces). If this schedule is not specified,
the surface is opaque (has zero transmittance).
The daylighting calculation takes the transmittance into account in determining, for example, how
much light enters a window through a translucent awning. It is assumed that the solar and visible
transmittance is the same and that the surfaces are non-diffusing, i.e., they do not change the
direction of transmitted light. Ref:Daylighting:Controls.
Category (2) and (3) surfaces are assumed to be opaque.
Surfaces in all three categories are assumed to be black, i.e., they do not reflect light, unless you
set if “Reflections” option is chosen in the Building object. Then obstructions can reflect light,
such as the top of an overhang reflecting light onto the window above. Ref: Building, Field: Solar
Distribution (with reflections options).
The daylighting calculation accounts for the presence of interior obstructions that lie between a
window and a reference point. Unlike exterior obstructions, which can be light transmitting, interior
obstructions are assumed to be opaque. Interior obstructions can reduce or eliminate the light
directly reaching the reference point through a window.
However, interior obstructions that are walls, ceilings or floors are reflecting so they contribute to
the inter-reflected component of daylight illuminance as do the non-obstructing zone surfaces.
Interior obstructions can belong to the Shading object series. This type of obstruction is assumed
to be non-reflecting so does not contribute to the inter-reflected component of daylight illuminance.
An example of an interior obstruction that is a wall in an L-shaped room is shown in Figure 1.78.
Here, wall A (or, equivalently, Wall B) prevents light from directly getting to the Reference Point
from the window.
1.15. GROUP – DAYLIGHTING 613
Figure 1.78: Wall A (or Wall B) is an interior obstruction that prevents light from directly reaching
the daylighting reference point from the window.
The Daylighting:Controls method, with no additional user input, calculates the contribution of
daylight that passes into a target zone through interior windows.[1] The origin of this daylight is
exterior windows in adjacent zones that share interior windows with the target zone. This capability
is aimed at daylighting through a double façade (also called “double envelope” or “double skin.”)
This is illustrated in Figure 1.79, which shows a double-façade buffer zone, Z0, with exterior windows
EW1 and EW2. Z0 shares interior windows IW1, IW2 and IW3 with daylit occupied zones ZD1,
ZD2 and ZD3, respectively (“daylit” here means the zone has an associated Daylighting:Controls
object). The daylight illuminance at reference points RP1, RP2 and RP3 comes from the interior
windows and has two main sources:
– Daylight that passes through both an exterior window and an interior window in Z0 and reaches
a reference point without reflection. This is called “direct illuminance.”
– Daylight from Z0 that passes through an interior window and reaches a reference point by inter-
reflection in the daylit zone. Because the program calculates this source from the interior solar
distribution in Z0 it is recommended that the most accurate calculation of this distribution be
made, which occurs if Solar Distribution = FullInteriorAndExterior in the Building object.
A third possible source is neglected because it is generally small in double-façade cases. This is
daylight that is reflected from the surfaces of Z0, passes through an interior window and then
reaches a reference point without inter-reflection in the daylit zone.
PurchAirWithDoubleFacadeDaylighting.idf is an input example of daylighting through an interior
window.
614 CHAPTER 1. INPUT-OUTPUT REFERENCE
Figure 1.79: Vertical section through a double-façade building showing daylighting through interior
windows. The dashed lines show that (1) reference point RP1 receives direct light from exterior
window EW1 via interior window IW1; (2) RP2 receives direct light from EW1 and EW2 via IW2;
and (3) RP3 receives direct light from EW2 via IW3.
Figure 1.80 shows schematically the general configuration of daylighting through interior windows
that can be calculated with EnergyPlus. Here, daylit zone ZD has one or more interior windows
that are adjacent to other zones, each of which has one or more exterior windows. ZD itself may
or may not have exterior windows. If it does, than the daylight illuminance from its exterior and
interior windows will be additive. The zones adjacent to ZD may or may not be daylit and may or
may not have other interior windows that are not adjacent to ZD. (The program does not consider
the illuminance in ZD from electric lighting in adjacent zones.)
Figure 1.81 shows schematically a configuration of daylighting through interior windows that cannot
be calculated with EnergyPlus. Here, zone Z has an interior window that is adjacent to zone Z1
which in turn has an interior window adjacent to zone Z2. However, the daylight from the exterior
window in Z2 that enters Z after passing through Z1 is not calculated because Z2 is not adjacent to
Z.
There are two restrictions on the use of exterior-window shading devices when a daylit zone has
interior windows:
1.15. GROUP – DAYLIGHTING 615
Figure 1.80: General configuration of daylighting through interior windows that can be calculated
with EnergyPlus. IW = interior window, EW = exterior window.
Figure 1.81: Configuration in which daylighting of zone Z through its interior window cannot be
calculated with EnergyPlus. IW = interior window, EW = exterior window.
616 CHAPTER 1. INPUT-OUTPUT REFERENCE
1) If two daylit zones share an interior window, neither zone can have an exterior window whose
shading device does glare control (i.e., the WindowShadingControl for the exterior window has Glare
Control Is Active = Yes).
2) If two daylit zones share an interior window, neither zone can have an exterior window with a
WindowShadingControl that has Shading Control Type = MeetDaylightIlluminanceSetpoint.
1.15.5 Daylighting:DELight:ComplexFenestration
Another input object that can only be used when the DElight Daylighting Method is used is
the Daylighting:DElight:ComplexFenestration object. The DElight daylighting analysis method
can be applied to daylighting zones that contain only simple fenestration systems such as win-
dows and skylights that are standard EnergyPlus sub-surfaces. In this situation, no Daylight-
ing:DElight:ComplexFenestration object would be input.
In addition to analyzing simple fenestration systems, DElight includes the capability of analyzing
complex fenestration systems such as geometrically complicated static shading systems (e.g., roof
1.15. GROUP – DAYLIGHTING 617
monitors) and/or optically complicated glazings (e.g., prismatic or holographic glass). This ca-
pability is based on characterizing these complex fenestration systems (CFS) using bi-directional
transmittance distribution functions (BTDF). In general, BTDF data for a specific CFS must be ei-
ther measured or simulated (e.g., using ray-tracing techniques) prior to employing DElight to analyze
it within EnergyPlus. The current implementation of DElight CFS calculations within EnergyPlus
supports two approaches to the input of BTDF, an analytical approach and a file-based approach.
The details of inputting these two approaches are described below under the User Complex Fenes-
tration Type field.
Two analytical CFS BTDF types are currently supported, window and light shelf. The file-based
approach requires that a user has access to a data file containing raw BTDF data that DElight reads
as additional input during its analysis calculations. BTDF data files are described separately since
it is anticipated that individual EnergyPlus users will not create these data files themselves.
The methods related to characterizing and analyzing CFS using BTDF are still evolving. DElight
is an early implementation of CFS analysis methods. These methods, and the input associated with
them here, will likely change in the future.
1.15.5.1 Inputs
BTDF^FILE^Filename
The first form above is for supported analytical CFS types which currently include WINDOW
and LIGHTSHELF. While these analytical types are relatively simple, they represent flexible ways
to explore diffusing CFS systems and the impact of light shelves in redirecting light through an
aperture. Each of these types also requires the visible transmittance of the CFS at normal incidence
angle, and a dispersion angle (in degrees) that represents the “spread” of transmitted light. A small
dispersion angle of 10 corresponds to clear glazing while a large angle of 90 corresponds to perfectly
diffusing glazing. The “^” symbol must be used as a delimiter between sub-fields within this Complex
Fenestration type name string as shown in the IDF example for WINDOW below, and in the DElight
sample input data files.
The second form above is for CFS types for which there is pre-measured or pre-simulated BTDF
data. In this case the Filename sub-field must be a valid data file name that is associated with an
existing BTDF dataset that DElight can use in its calculations.
Daylighting:DELight:ComplexFenestration ,
Window CFS , !- DElight Complex Fenestration User Name
BTDF^GEN^WINDOW ^1.0^20.0 , !- Complex Fenestration Type
ZN003:WALL001 , !- Complex Fenestration Host Surface
Zn003:Wall001:Doppel001 , !- Doppelganger Surface Name
0.0; !- Fenestration Rotation {deg}
1.15.5.2 Outputs
The area-averaged luminance of an exterior window as viewed from the first reference point in the
daylit zone containing the window. In general, higher window luminance values are associated with
higher daylight glare values. (Printed only for exterior windows in daylit zones without interior
windows.)
1.15.6 Output:IlluminanceMap
The Output:IlluminanceMap object expands on the reporting capabilities of the daylighting simu-
lation. For any zone simulated with Daylighting:Controls, the illuminance map can generate up to
2,500 points of additional daylighting illuminance values. The resulting map is output as a comma
delimited text file that can be imported into a spreadsheet program for rapid visualization of the
daylighting illuminance patterns in a zone. The values are produced on an hourly basis. The Z height
of the map is constant (parallel to a flat floor). More than one illuminance map can be created for
a zone. IlluminanceMap output is available only when SplitFlux daylighting method is selected in
Daylighting:Controls object.
1.15.6.1 Inputs
Output:IlluminanceMap ,
Daylit Map , ! Map Name
Daylit Zone , ! Zone Name
0, ! Z Height [m]
0.1, ! X Minimum Coordinate [m]
4.9, ! X Maximum Coordinate [m]
10, ! Number of X Grid Points
0.1, ! Y Minimum Coordinate [m]
9.9, ! Y Maximum Coordinate [m]
10; ! Number of Y grid Points
Since not all zones are rectangular, it is possible to have map points that are outside the zone. Any
illuminance registered at these points is inaccurate and, additionally, a “*” marks these values for
easy observance.
1.15.7 OutputControl:IlluminanceMap:Style
This object specifies the “style” for the illuminance map output (described in the Output Details and
Examples document). As described early in the document (see: EnergyPlus Output Processing),
the user may select the “style” for the daylighting illuminance map output file (eplusmap.<ext>).
622 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.15.7.1 Inputs
1.15.9 DaylightingDevice:Tubular
Tubular daylighting devices (TDDs), also known as tubular skylights or light pipes, are used to bring
natural exterior daylight into the hard-to-reach, interior spaces of a building.
TDDs consist of three components: a dome, a pipe, and a diffuser.
In EnergyPlus each of these components corresponds to an object in the input file.
The dome and diffuser are defined in the same way as windows using the FenestrationSurface:Detailed
object. The Surface Type field must be specified as TubularDaylightDome or TubularDaylightDiffuser
accordingly.
The location and orientation of the dome surface affect the total amount of daylight collected.
The Base Surface of the diffuser object determines to which zone the daylighting is delivered. The
location and orientation of the diffuser surface affect the amount of daylight received at the Day-
lighting:Controls reference points.
Although the object definition is the same as for a window, there are several restrictions on Tubu-
larDaylightDome and TubularDaylightDiffuser objects:
Since commercial TDDs are assumed to be cylindrical in shape, it is recommended that the circular
areas of the actual dome and diffuser be approximated with a square of equivalent area for the Tubu-
larDaylightDome and TubularDaylightDiffuser objects. Although it is possible to use a triangular
surface instead, a square is a much better geometric approximation of a circle.
Note that the TubularDaylightDome surface is allowed to have a different position and tilt from the
roof base surface. If the actual TDD projects some height above the roof surface, the TubularDay-
lightDome coordinates should be located accordingly.
The TubularDaylightDome surface automatically casts a shadow on the roof base surface. However,
since the pipe is not represented by a surface, it will not cast a shadow. If this effect must be
simulated, one or more SURFACE:SHADING objects can be used.
The dome and diffuser objects are connected by the DAYLIGHTING DEVICE:TUBULAR object:
1.15.9.1 Inputs
FenestrationSurface :Detailed ,
Dome1 , !- Subsurface Name
TubularDaylightDome , !- Surface Type
Clear Acrylic Dome , !- Construction Name (only 1 layer allowed in construction)
Attic Roof , !- Base Surface Name
, !- Outside Face Environment (not allowed for TubularDaylightDome )
0.0, !- VF to Ground
, !- Window Shading Control (not allowed for TubularDaylightDome )
, !- Frame/Divider Name (not allowed for TubularDaylightDome )
1.0, !- Multiplier (must be 1.0 for TubularDaylightDome )
4, !- Number of Vertices
2.3425 , 3.1575 , 3.9,
2.3425 , 2.8425 , 3.9,
2.6575 , 2.8425 , 3.9,
2.6575 , 3.1575 , 3.9;
FenestrationSurface :Detailed ,
Diffuser1 , !- Subsurface Name
TubularDaylightDiffuser , !- Surface Type
Frosted Acrylic Diffuser , !- Construction Name (only 1 layer allowed in construction)
Daylit Zone Ceiling , !- Base Surface Name
, !- Outside Face Environment (not allowed for TubularDaylightDiffuser )
0.0, !- VF to Ground
, !- Window Shading Control (not allowed for TubularDaylightDiffuser )
, !- Frame/Divider Name (not allowed for TubularDaylightDiffuser )
1.0, !- Multiplier (must be 1.0 for TubularDaylightDiffuser )
4, !- Number of Vertices
2.3425 , 3.1575 , 2.5,
2.3425 , 2.8425 , 2.5,
2.6575 , 2.8425 , 2.5,
2.6575 , 3.1575 , 2.5;
1.15.9.2 Outputs
1.15.9.2.7 Tubular Daylighting Device Pipe Absorbed Solar Radiation Rate [W]
This is the rate at which solar radiation is absorbed by the pipe in the TDD, in Watts.
– Zone,Average,Surface Outside Face Incident Solar Radiation Rate per Area[W/m2] (incident
inside of pipe)
– Zone,Average,Surface Window Transmitted Solar Radiation Rate [W] (same as Tubular Day-
lighting Device Transmitted Solar Radiation Rate)
– Zone,Average,Surface Window Total Glazing Layers Absorbed Solar Radiation Rate [W]
1.15.10 DaylightingDevice:Shelf
Daylighting shelves, or simply light shelves, are another device for bringing more daylight into a
building. Installed as an accessory to a window, daylighting shelves work by reflecting exterior light
onto the ceiling of a room. Daylighting shelves can have an inside shelf, an outside shelf, or both.
The inside shelf redistributes light that would have entered the zone anyway. Instead of entering as
a beam, all light is reflected onto the zone ceiling and is converted to diffuse shortwave radiation.
The outside shelf changes the amount of light entering the zone. If the shelf surface is more reflective
than the ground, it can increase the amount of light incident on the upper part of the window.
However, the shading effect of the outside shelf on the lower part of the window must also be
considered as it can easily negate any gain achieved in the upper part of the window. All light
reflected from the outside shelf that enters the upper window is assumed to strike the ceiling.
628 CHAPTER 1. INPUT-OUTPUT REFERENCE
NOTE: Unlike a regular Shading:Zone:Detailed object, the vertices of the outside shelf surface
must be ordered so that the outward normal vector points upward, i.e. toward the upper window.
This is necessary in order for the outside shelf to properly receive sunlight and shading from other
surfaces. A mirror shading surface with the outward normal vector pointing in the opposite
direction is automatically created by the program to shade the lower window.
The inside shelf and outside shelf are both optional. However, if neither shelf is specified, the
daylighting shelf object has no effect on the simulation.
1.15. GROUP – DAYLIGHTING 629
1.15.10.1 Inputs
NOTE: It is up to the user to adjust the view factor to ground of the upper window to account
for the part of the view blocked by the outside shelf. The calculated View Factor To Outside
Shelf is reported in the eio file for this purpose. For the typical case where the shelf is parallel
to the ground and the upper window is perpendicular to the ground, the view factor to ground
is simply: 0.5 – View Factor To Outside Shelf.
DaylightingDevice:Shelf ,
Shelf , !- Name
Daylit Upper Window , !- Window Name
Inside Shelf , !- Inside Shelf Name
Outside Shelf , !- Outside Shelf Name
Shelf Construction; !- Outside Shelf Construction Name (required if outside shelf specified)
! 0.29; !- View Factor To Outside Shelf (optional)
FenestrationSurface :Detailed ,
Daylit Upper Window , !- Subsurface Name
Window , !- Surface Type
Standard Window , !- Construction Name
Daylit South Wall , !- Base Surface Name
, !- Outside Face Environment
0.211 , !- VF to Ground (user must adjust to account for view factor to outside shelf)
630 CHAPTER 1. INPUT-OUTPUT REFERENCE
BuildingSurface:Detailed ,
Inside Shelf , !- Surface Name
Wall , !- Surface Type
Shelf Construction , !- Construction Name
Daylit Zone , !- Zone Name
OtherZoneSurface , !- Exterior Conditions (must be OtherZoneSurface)
Inside Shelf , !- Target (must be itself)
NoSun , !- Solar Exposure
NoWind , !- Wind Exposure
0.0, !- VF to Ground
4, !- Number of Vertices
1.0, 0.0, 2.0,
4.0, 0.0, 2.0,
4.0, 1.0, 2.0,
1.0, 1.0, 2.0;
Shading:Zone:Detailed ,
Outside Shelf , !- Surface Name
Daylit South Wall , !- Base Surface Name
, !- Shading Transmittance Schedule (default is always opaque)
4, !- Number of Vertices
1.0, 0.0, 2.0, !- Outward normal vector must point up toward the upper window
1.0, -1.0, 2.0,
4.0, -1.0, 2.0,
4.0, 0.0, 2.0;
1.15.10.2 Outputs
The view factor to outside shelf calculation shows up in the .eio file along with the associated window
and window view factors to sky and ground:
! <Shelf Details>,Name,View Factor to Outside Shelf,Window Name,Window View Factor to
Sky,Window View Factor to Ground
SHELF,0.29,DAYLIT UPPER WINDOW,0.50,0.21
This variable reports the calculated View Factor To Outside Shelf so that the user can correctly
adjust the view factor to ground of the upper window.
The usual window and surface variables are relevant for the upper window:
The following surface variables are reported for the outside shelf surface, if specified:
1.15.11 DaylightingDevice:LightWell
This object is used to model the impacts on daylighting of a “light well” that might be associated
with exterior windows such as skylights. The light well model attenuates the light transmitted
by the skylight. The attenuation is characterized by the well efficiency, which is the ratio of the
amount of light leaving the well to the amount of light entering the well. The well efficiency varies
from close to 1.0 to close to zero if there is high attenuation. The well efficiency is used only
in the EnergyPlus detailed daylighting calculation, where it multiplies the beam and diffuse light
transmitted by the skylight. (The well efficiency is not used in calculating the solar gain through
the skylight.)
The input object describes the light well using basic characteristics of the geometry along with
the visible reflectance of the well’s side walls. The following figure diagrams how the geometry is
characterized.
1.15.11.1 Inputs
Figure 1.86: Skylight with light well: (a) perspective view, (b) vertical section. If the bottom of the
light well is a rectangle of side lengths c and d, as shown in (a), then the perimeter of the bottom
of the well = 2(c+d) and the area = cd (see description of field names for the Light Well object).
[1] Formerly, only the exterior windows in a zone could provide daylight to that zone.
1.16.1 Exterior:Lights
1.16.1.1 Inputs
Exterior:Lights ,
OutsideLights , !- Name
ON , !- SCHEDULE Name
1000, !- Design Level
AstronomicalClock , !- Control Option
Grounds Lights; !- End -Use Subcategory
1.16. GROUP – EXTERIOR ENERGY USE EQUIPMENT 635
1.16.1.2 Outputs
Output for exterior lights appears in three possible places. It will appear on two meters (Electric-
ity:Facility and ExteriorLights:Electricity) as well as in its own designated value in the standard
output file.
1.16.2 Exterior:FuelEquipment
1.16.2.1 Inputs
1.16.3 Exterior:WaterEquipment
1.16.3.1 Inputs
ABUPS End Uses by Subcategory table and in the LEED Summary EAp2-4/5 Performance Rating
Method Compliance table.
IDF Example:
Exterior:WaterEquipment ,
OutsideWaterEq , !- Name
Water , !- Fuel Use Type
ON , !- Schedule Name
1000.0 , !- Design Level
General; !- End -Use Subcategory
1.16.3.2 Outputs
Output for exterior equipment consumption appears in three possible places. It will appear on two
meters (Fuel Type:Facility and ExteriorEquipment:Fuel Type) as well as in its own designated value
in the standard output file, Exterior Equipment Fuel Type Energy. Consumption also appears on any
user-defined end-use subcategory meters, i.e., End-Use Subcategory:ExteriorEquipment:Fuel Type.
All outputs are in [J] except water consumption which is in [m3]. There are also rate versions
1.17.1 ZoneInfiltration:DesignFlowRate
Infiltration is the unintended flow of air from the outdoor environment directly into a thermal zone.
Infiltration is generally caused by the opening and closing of exterior doors, cracks around windows,
and even in very small amounts through building elements. The basic equation used to calculate
infiltration with this object is:
Infiltration = Idesign (Fschedule ) A + B |(Tzone − Todb )| + C (WindSpeed) + D Windspeed2
(1.38)
More advanced infiltration calculations are possible using the EnergyPlus AirflowNetwork model for
natural infiltration driven by wind and/or by forced air. Infiltration described by the equation shown
above is entered into EnergyPlus using the following syntax. Exfiltration (the leakage of zone air to
the outside) is generally handled better as zone exhaust air in the zone equipment description. The
equation must always yield a non-negative results; negative values are set to 0.0.
The question of typical values for these coefficients is subject to debate. Ideally, one should do a
detailed analysis of the infiltration situation and then determine a custom set of coefficients using
methods such as those laid out in Chapter 26 of the ASHRAE Handbook of Fundamentals. The
EnergyPlus defaults are 1,0,0,0 which give a constant volume flow of infiltration under all conditions.
BLAST (one of the EnergyPlus predecessors) used the following values as defaults: 0.606, 0.03636,
0.1177, 0. These coefficients produce a value of 1.0 at 0C deltaT and 3.35 m/s (7.5 mph) windspeed,
which corresponds to a typical summer condition. At a winter condition of 40C deltaT and 6 m/s
(13.4 mph) windspeed, these coefficients would increase the infiltration rate by a factor of 2.75.
In DOE-2 (the other EnergyPlus predecessor), the air change method defaults are (adjusted to SI
units) 0, 0, 0.224 (windspeed), 0. With these coefficients, the summer conditions above would give
a factor of 0.75, and the winter conditions would give 1.34. A windspeed of 4.47 m/s (10 mph) gives
a factor of 1.0.
The source of the BLAST defaults is noted in the BLAST documentation as:
“Empirical equation and the coefficient default were determined from ASHRAE journal articles and
other data on the effects of outdoor weather conditions.”
1.17. GROUP – AIRFLOW 639
The source of the DOE-2 defaults is based on examining the infiltration relationships described in
the ASHRAE Handbook of Fundamentals.
The EnergyPlus example files use all of the above, the BLAST defaults in some (e.g., GeometryTest),
the DOE-2 defaults in some (e.g., 5ZoneAirCooled), and the EnergyPlus defaults in some (e.g.,
LgOffVAVDetCoil).
The local outdoor dry-bulb temperature used in the above basic equation (Todb ) is typically a function
of the height of the zone centroid above ground. The corresponding zone name is given in the second
field. The local outdoor dry-bulb temperature calculation procedure is given in the section of “Local
Outdoor Air Temperature Calculation” in the Engineering Reference.
The local outdoor wind speed used in the above basic equation (WindSpeed) is also a function of
the height of the zone centroid above ground. The corresponding zone name is given in the second
filed. The local outdoor wind speed calculation procedure is given in the section of “Local Wind
Speed Calculation” in the Engineering Reference.
Note: When the value of the Wind Speed Profile Exponent field in the Site:HeightVariation is
equal to 0.0. The local wind speed is always equal to the wind speed given in the weather data
and will not be dependent on zone centroid height. Similarly, if the value of the Air Temperature
Gradient Coefficient is set equal to 0 the local air dry-bulb temperature is also always equal
to the air dry-bulb temperature given in the weather data and will not be dependent on zone
centroid height.
One or more infiltration objects can be defined for each zone, and the resulting infiltration rate for
the zone will simply be the summation of the flow rates specified by the infiltration objects.
1.17.1.1 Inputs
– Flow/Zone
With this choice, the method used will be a straight insertion of the design volume flow rate. (The
Design Flow Rate field should be filled.)
– Flow/Area
With this choice, the method used will be a factor per floor area of the zone. (The flow per Zone
Area field should be filled).
– Flow/ExteriorArea
With this choice, the method used will be a factor per exterior surface area of the zone. (The flow
per Exterior Surface Area field should be filled).
– Flow/ExteriorWallArea
With this choice, the method used will be a factor per exterior wall surface area of the zone. (The
flow per Exterior Surface Area field should be filled).
– AirChanges/Hour
With this choice, the method used will be the number of air changes per hour for the infiltration
amount. This factor, along with the Zone Volume, will be used to determine the Design Flow Rate.
(The Air Changes per Hour field should be filled).
ZoneInfiltration:DesignFlowRate ,
Infiltration 1, !- Name
DORM ROOMS AND COMMON AREAS , !- Zone Name
Infiltration Sch , !- Schedule Name
Flow/Zone , !- Design Flow Rate Calculation Method
2.831685 , !- Design Flow Rate {m3/s}
, !- Flow per Zone Floor Area {m3/s/m2}
, !- Flow per Exterior Surface Area {m3/s/m2}
, !- Air Changes per Hour
0.6060000 , !- Constant Term Coefficient
3.6359996E-02, !- Temperature Term Coefficient
0.1177165 , !- Velocity Term Coefficient
0.0000000E+00; !- Velocity Squared Term Coefficient
ZoneInfiltration:DesignFlowRate ,
OfficeZones Infiltration , !- Name
OfficeZones , !- Zone or ZoneList Name
Infiltration Sch , !- Schedule Name
AirChanges/Hour , !- Design Flow Rate Calculation Method
, !- Design Flow Rate {m3/s}
, !- Flow per Zone Floor Area {m3/s-m2}
, !- Flow per Exterior Surface Area {m3/s-m2}
4.7, !- Air Changes per Hour
0.6060000 , !- Constant Term Coefficient
3.6359996E-02, !- Temperature Term Coefficient
0.1177165 , !- Velocity Term Coefficient
0.0000000E+00; !- Velocity Squared Term Coefficient
1.17.2 ZoneInfiltration:EffectiveLeakageArea
ZoneInfiltration:EffectiveLeakageArea model is similar to the other infiltration objects but uses a
different equation to model the unintended flow of air from the outdoor environment directly into
a thermal zone. Infiltration is generally caused by the opening and closing of exterior doors,
cracks around windows, and even in very small amounts through building elements. This model
is based on work by Sherman and Grimsrud (1980) and is appropriate for smaller, residential-type
buildings. The equation used to calculate infiltration in the effective leakage area model is:
q
AL
Inf iltration = (FSchedule ) Cs ∆T + Cw (W indSpeed)2 (1.39)
1000
where ∆T is the average difference between zone air temperature and the outdoor air temperature
and the other coefficients are described below.
Note that the coefficients for the “EffectiveLeakageArea” model are not interchangeable with the
similarly named coefficients in the “FlowCoefficient” model (see ZoneInfiltration:FlowCoefficient
object).
One or more infiltration objects of different types can be defined for each zone, and the resulting
infiltration rate for the zone will simply be the summation of the flow rates specified by the infiltration
objects.
1.17.2.1 Inputs
Shelter class One story house Two story house Three story house
ZoneInfiltration:EffectiveLeakageArea ,
LIVING ZONE Infil 1, !- Name
LIVING ZONE , !- Zone Name
INF -SCHED , !- Schedule Name
500.0 , !- Effective Air Leakage Area
0.000145 , !- Stack Coefficient
0.000174 ; !- Wind Coefficient
1.17.3 ZoneInfiltration:FlowCoefficient
ZoneInfiltration:FlowCoefficient model is similar to the other infiltration objects but uses a different
equation to model the unintended flow of air from the outdoor environment directly into a thermal
zone. Infiltration is generally caused by the opening and closing of exterior doors, cracks around
windows, and even in very small amounts through building elements. This reformulated model is
based on the AIM-2 model by Walker and Wilson (1998) and is appropriate for smaller, residential-
type buildings. The equation used to calculate infiltration in the flow coefficient model is:
r 2
Inf iltration = (FSchedule ) (c Cs ∆T n )2 + c Cw (s ∗ W indSpeed)2n (1.40)
Where ∆T is the average difference between zone air temperature and the outdoor air temperature
and the other coefficients are described below.
Note that the coefficients for the “Flow Coefficient” model are not interchangeable with the similarly
named coefficients in the “Effective Leakage Area” model (see ZoneInfiltration:EffectiveLeakageArea
object).
One or more infiltration objects of different types can be defined for each zone, and the resulting
infiltration rate for the zone will simply be the summation of the flow rates specified by the infiltration
objects.
1.17.3.1 Inputs
Shelter class No Flue One story house with flue Two story house with flue Three story house with flue
1.17.3.2 Outputs
Zone Infiltration objects have output variables for individual objects and for zone totals.
Object level outputs include:
1.17.4 ZoneVentilation:DesignFlowRate
Ventilation is the purposeful flow of air from the outdoor environment directly into a thermal zone in
order to provide some amount of non-mechanical cooling. Ventilation, as specified by the input syntax
for the ZoneVentilation:DesignFlowRate object, is intended to model “simple” ventilation as opposed
to the more detailed ventilation investigations that can be performed with the AirflowNetwork model
or with air systems that have outdoor air mixers. Zone ventilation, as specified via this input object,
can be controlled by a schedule and through the specification of minimum, maximum and delta
temperatures as described below. The temperatures can be either single constant values for the
entire simulation or schedules which can vary over time. As with infiltration, the actual flow rate
of ventilation air can be modified by the temperature difference between the inside and outside
environment and the wind speed. The basic equation used to calculate ventilation with this model
is:
V entilation = (Vdesign ) (Fschedule ) A + B |Tzone − Todb | + C (W indSpeed) + D W indSpeed2
(1.41)
Similar to infiltration, the question of typical values for these coefficients is subject to debate. Ideally,
one should do a detailed analysis of the ventilation situation and then determine a custom set of
coefficients using methods such as those laid out in Chapter 26 of the ASHRAE Handbook of
Fundamentals. The EnergyPlus defaults are 1,0,0,0 which give a constant volume flow of ventilation
under all conditions. The following discussion is duplicated from the infiltration design flow rate
object. The equation must always yield a non-negative results; negative values are set to 0.0.
1.17. GROUP – AIRFLOW 649
BLAST (one of the EnergyPlus predecessors) used the following values as defaults: 0.606, 0.03636,
0.1177, 0. These coefficients produce a value of 1.0 at 0C deltaT and 3.35 m/s (7.5 mph) windspeed,
which corresponds to a typical summer condition. At a winter condition of 40C deltaT and 6 m/s
(13.4 mph) windspeed, these coefficients would increase the infiltration rate by a factor of 2.75.
In DOE-2 (the other EnergyPlus predecessor), the air change method defaults are (adjusted to SI
units) 0, 0, 0.224 (windspeed), 0. With these coefficients, the summer conditions above would give
a factor of 0.75, and the winter conditions would give 1.34. A windspeed of 4.47 m/s (10 mph) gives
a factor of 1.0.
The source of the BLAST defaults is noted in the BLAST documentation as:
“Empirical equation and the coefficient default were determined from ASHRAE journal articles and
other data on the effects of outdoor weather conditions.”
The source of the DOE-2 defaults is based on examining the infiltration relationships described in
the ASHRAE Handbook of Fundamentals.
The local outdoor dry-bulb temperature used in the above basic equation (Todb ) is typically a function
of the height of the zone centroid above ground. The corresponding zone name is given in the second
field. The local outdoor dry-bulb temperature calculation procedure is described in the “Local
Outdoor Air Temperature Calculation” section of the Engineering Reference.
The local outdoor wind speed used in the above basic equation (WindSpeed) is also a function of
the height of the zone centroid above ground. The corresponding zone name is given in the second
field. The local outdoor wind speed calculation procedure is described in the “Local Wind Speed
Calculation” section of the Engineering Reference.
Note: When the value of the Wind Speed Profile Exponent field in the Site:HeightVariation object
is equal to 0.0, the local wind speed is always equal to the wind speed given in the weather data
and will not be dependent on zone centroid height. Similarly, if the value of the Air Temperature
Gradient Coefficient is set equal to 0, the local air dry-bulb temperature is also always equal to
the air dry-bulb temperature given in the weather data and will not be dependent on zone centroid
height.
One or more ventilation objects (i.e., ZoneVentilation:DesignFlowRate and/or ZoneVentila-
tion:WindandStackOpenArea) can be defined for each zone, and the resulting ventilation rate for
the zone will simply be the summation of the flow rates specified by the ventilation objects.
More advanced ventilation calculations are possible using the EnergyPlus AirflowNetwork model.
1.17.4.1 Inputs
The name of the actual ventilation object becomes <Zone Name> <ZoneVentilation:DesignFlowRate
Object Name> and should be less than the standard length (100 characters) for a name field. If
it is greater than this standard length, it may be difficult to specify in output reporting as it will
be truncated. A warning will be shown if the generated name is greater than 100 characters. If it
duplicates another such concatenated name, there will be a severe error and terminate the run.
– Flow/Zone
With this choice, the method used will be a straight insertion of the design volume flow rate. (The
Design Flow Rate field should be filled.)
– Flow/Area
With this choice, the method used will be a factor per floor area of the zone. (The Flow per Zone
Floor Area field should be filled).
– Flow/Person
With this choice, the method used will be a factor per nominal number of people in the zone. (The
Flow per Person field should be filled).
– AirChanges/Hour
With this choice, the method used will be the number of air changes per hour for the infiltration
amount. This factor, along with the Zone Volume, will be used to determine the Design Flow Rate.
(The Air Changes per Hour field should be filled).
the temperature difference between the outdoor and indoor air dry-bulb temperatures. The units
for this parameter are inverse Celsius.
ZoneVentilation:DesignFlowRate ,
Ventilation 1, !- Name
ZONE 2, !- Zone Name
Simple Vent , !- Schedule Name
Flow/Zone , !- Design Volume Flow Rate calculation method
6.131944 , !- Design Volume Flow Rate {m3/s}
, !- Volume Flow Rate per area {m3/s/m2}
, !- Volume Flow Rate per person {m3/s/person}
, !- Air Changes Per Hour
INTAKE , !- Ventilation Type
400.0 , !- Fan Pressure Rise{Pa}
0.9, !- Fan Total Efficiency
0.6060000 , !- Constant Term Coefficient
2.0199999E-02, !- Temperature Term Coefficient
5.9800001E-04, !- Velocity Term Coefficient
0.0000000E+00!- Velocity Squared Term Coefficient
18.0, !- Minimum Indoor Temperature {C}
, !- Minimum Indoor Temperature Schedule Name
, !- Maximum Indoor Temperature {C}
, !- Maximum Indoor Temperature Schedule Name
1.0; !- Delta temperature {C}
ZoneVentilation:DesignFlowRate ,
SPACE1 -1 Ventl 1, !-Name
SPACE1 -1, !- Zone Name
NightVentSched , !- SCHEDULE Name
Flow/Zone , !- Design Volume Flow Rate calculation method
.05295 , !- Design Volume Flow Rate {m3/s}
, !- Volume Flow Rate per area {m3/s/m2}
, !- Volume Flow Rate per person {m3/s/person}
, !- Air Changes Per Hour
Intake , !- Ventilation Type
67., !- Fan Pressure Rise
.7, !- Fan Total Efficiency
1, !- Constant Term Coefficient
0, !- Temperature Term Coefficient
0, !- Velocity Term Coefficient
0, !- Velocity Squared Term Coefficient
, !- Minimum Indoor Temperature {C}
MinIndoorTemp , !- Minimum Indoor Temperature Schedule Name
, !- Maximum Indoor Temperature {C}
MaxIndoorTemp , !- Maximum Indoor Temperature Schedule Name
, !- Delta Temperature {deltaC}
DeltaTemp , !- Delta Temperature Schedule Name
, !- Minimum Outdoor Temperature {C}
MinOutdoorTemp , !- Minimum Outdoor Temperature Schedule Name
, !- Maximum Outdoor Temperature {C}
MaxOutdoorTemp , !- Maximum Outdoor Temperature Schedule Name
40; !- Maximum WindSpeed {m/s}
1.17. GROUP – AIRFLOW 655
ZoneVentilation:DesignFlowRate ,
West -East Zones Ventilation , !- Name
West -East Zones , !- Zone or ZoneList Name
VentSched , !- Schedule Name
AirChanges/Hour , !- Design Flow Rate Calculation Method
, !- Design Flow Rate {m3/s}
, !- Flow Rate per Zone Floor Area {m3/s-m2}
, !- Flow Rate per Person {m3/s-person}
1.7, !- Air Changes per Hour
Intake , !- Ventilation Type
67., !- Fan Pressure Rise {Pa}
0.7, !- Fan Total Efficiency
1, !- Constant Term Coefficient
0, !- Temperature Term Coefficient
0, !- Velocity Term Coefficient
0, !- Velocity Squared Term Coefficient
, !- Minimum Indoor Temperature {C}
MinIndoorTemp , !- Minimum Indoor Temperature Schedule Name
, !- Maximum Indoor Temperature {C}
MaxIndoorTemp , !- Maximum Indoor Temperature Schedule Name
, !- Delta Temperature {deltaC}
DeltaTemp , !- Delta Temperature Schedule Name
, !- Minimum Outdoor Temperature {C}
MinOutdoorTemp , !- Minimum Outdoor Temperature Schedule Name
, !- Maximum Outdoor Temperature {C}
MaxOutdoorTemp , !- Maximum Outdoor Temperature Schedule Name
40; !- Maximum Wind Speed {m/s}
1.17.5 ZoneVentilation:WindandStackOpenArea
For this model, the ventilation air flow rate is a function of wind speed and thermal stack effect,
along with the area of the opening being modeled. This object can be used alone or in combination
with ZoneVentilation:DesignFlowRate objects. This model is intended for simplified ventilation
calculations as opposed to the more detailed ventilation investigations that can be performed with the
AirflowNetwork model. Using the “Wind and Stack with Open Area” model, the natural ventilation
flow rate can be controlled by a multiplier fraction schedule applied to the user-defined opening area
and through the specification of minimum, maximum and delta temperatures. The temperatures
can be either single constant values for the entire simulation or schedules which can vary over time.
The equation used to calculate the ventilation rate driven by wind is:
where,
Qw = Volumetric air flow rate driven by wind [m3 /s]
Cw = Opening effectiveness [dimensionless]
Aopening = Opening area [m2 ]
Fschedule = Open area fraction [user-defined schedule value, dimensionless]
V = Local wind speed [m/s]
The equation used to calculate the ventilation rate due to stack effect is:
656 CHAPTER 1. INPUT-OUTPUT REFERENCE
p
Qs = CD Aopening Fschedule 2g∆HN P L (|Tzone − Todb |/Tzone ) (1.43)
where,
Qs = Volumetric air flow rate due to stack effect [m3 /s]
CD = Discharge coefficient for opening [dimensionless]
Aopening = Opening area [m2 ]
Fschedule = Open area fraction [user-defined schedule value, dimensionless]
ΔHN P L = Height from midpoint of lower opening to the neutral pressure level [m].
Estimation of this value is difficult; refer to Chapter 16 of the 2009 ASHRAE Handbook of Funda-
mentals for guidance.
Tzone = Zone air dry-bulb temperature [K]
Todb = Local outdoor air dry-bulb temperature [K]
The total ventilation rate calculated by this model is the quadrature sum of the wind and stack air
flow components:
q
V entilationW indAndStack = Qs 2 + Qw 2 (1.44)
The local outdoor air dry-bulb temperature used in the stack effect equation (Todb ) is typically a
function of the height of the zone centroid above ground. The corresponding zone name is given in
the second field. The local outdoor air dry-bulb temperature calculation procedure is described in
the “Local Outdoor Air Temperature Calculation” section of the Engineering Reference.
The local outdoor wind speed used in the above wind-driven equation (V) is also a function of the
height of the zone centroid above ground. The corresponding zone name is given in the second
field. The local outdoor wind speed calculation procedure is described in the “Local Wind Speed
Calculation” section of the Engineering Reference.
Note: When the value of the Wind Speed Profile Exponent field in the Site:HeightVariation object
is equal to 0.0, the local wind speed is always equal to the wind speed given in the weather data
and will not be dependent on zone centroid height. Similarly, if the value of the Air Temperature
Gradient Coefficient is set equal to 0, the local air dry-bulb temperature is also always equal to
the air dry-bulb temperature given in the weather data and will not be dependent on zone centroid
height.
One or more ventilation objects (i.e., ZoneVentilation:DesignFlowRate and/or ZoneVentila-
tion:WindandStackOpenArea) can be defined for each zone, and the resulting ventilation rate for
the zone will simply be the summation of the flow rates specified by the ventilation objects.
More advanced ventilation calculations are possible using the EnergyPlus AirflowNetwork model.
1.17.5.1 Inputs
The values for this field can include negative numbers. This allows ventilation to occur even if the
outdoor temperature is above the indoor temperature. The Delta Temperature is used in the code
in the following way:
IF ((IndoorTemp - OutdoorTemp) < DeltaTemperature) Then ventilation is not allowed.
Thus, if a large negative number is input for DeltaTemperature, the ventilation can be kept on even
if the outdoor temperature is greater than the indoor temperature. This is useful for uncontrolled
natural ventilation (open windows) or as a way to estimate the effect of required ventilation air for
load calculations.
ZoneVentilation:WindandStackOpenArea ,
ZONE 3 Ventl 1, !- Name
ZONE 3, !- Zone Name
0.5, !- Opening Area {m2}
Constant , !- Opening Area Fraction Schedule Name
AutoCalculate , !- Opening Effectiveness
0.0, !- Effective Angle {deg}
1.0, !- Height Difference {m}
AutoCalculate , !- Discharge Coefficient for Opening
18.0, !- Minimum Indoor Temperature {C}
, !- Minimum Indoor Temperature Schedule Name
, !- Maximum Indoor Temperature {C}
, !- Maximum Indoor Temperature Schedule Name
1.0; !- Delta Temperature {deltaC}
1.17.5.2 Outputs
1.17.6 ZoneAirBalance:OutdoorAir
This model calculates a combined zone outdoor airflow by including interactions between mechan-
ical ventilation, infiltration and duct leakage. It is mainly applied to a single zone (e.g., residen-
tial) building. The model combines all outdoor airflows from ZoneInfiltration and ZoneVentilation
objects in the same zone. This object also includes the induced outdoor airflows due to unbal-
anced duct leakage, and unbalanced outdoor airflows introduced by unbalanced airflows from Zone-
HVAC:EnergyRecoveryVentilator objects when the exhaust airflow is greater than the supply outdoor
airflow. This model is intended for simplified outdoor airflow calculations as opposed to the more
detailed outdoor airflow investigations that can be performed with the AirflowNetwork model. The
equation used to calculate the combined zone outdoor airflow is:
q
Q= Qn 2 + Qu,v 2 + Qu,l 2 + Qb,v (1.46)
where,
Q = Combined outdoor airflow with infiltration, balanced and unbalanced outdoor air flows, and
unbalanced duct leakage [m3 /s]
Qn = Natural infiltration airflow from ZoneInfiltration:* objects [m3 /s]
Qb,v = Balanced ventilation airflow, excluding infiltration [m3 /s]
Qu,v = Unbalanced ventilation airflow, excluding infiltration [m3 /s]
Qu,l = Unbalanced duct leakage: the difference between supply and return leaks [m3 /s]
This object cannot be used simultaneously with the EnergyPlus AirflowNetwork model. If the
AirflowNetwork model is active for a simulation time step, the Air Balance Method is reset to “None”
1.17. GROUP – AIRFLOW 663
for that time step. More advanced outdoor airflow calculations are possible using the EnergyPlus
AirflowNetwork model.
This object does not combine any airflows from Fan:ZoneExhaust objects and is independent of
HVAC equipment operation.
This object will not work with the AvailabilityManager:HybridVentilation object in the same zone,
when the Simple Airflow Control Type Schedule Name is provided in the HybridVentilation object.
For this case, the Air Balance Method is reset to “None”.
1.17.6.1 Inputs
ZoneAirBalance:OutdoorAir ,
ZONE 2 Balance 1, !- Name
ZONE 2, !- Zone Name
Quadrature , !- Air Balance Method
0.00, !- Induced Outdoor Air Due to Unbalanced Duct Leakage {m3/s}
Constant; !- Induced Outdoor Air Schedule Name
664 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.17.6.2 Outputs
ZoneAirBalance:OutdoorAir output variables will be provided when the Air Balance Method is
Quadrature. Output variables from the associated ZoneVentilation:* and ZoneInfiltration:* objects
for the same zone will not be produced when ZoneAirBalance:OutdoorAir output variables are
available. If the Air Balance Method = None, then no ZoneAirBalance:OutputAir outputs will
be produced and the associated ZoneVentilation:* and ZoneInfiltration:* objects will specify their
output variables for the zone.
1.17.6.2.1 Zone Combined Outdoor Air Sensible Heat Loss Energy [J]
The sensible (temperature) heat loss that occurs when the outdoor air temperature < zone air
temperature.
1.17.6.2.2 Zone Combined Outdoor Air Sensible Heat Gain Energy [J]
The sensible (temperature) heat gain that occurs when the outdoor air temperature > = zone air
temperature.
1.17.6.2.3 Zone Combined Outdoor Air Latent Heat Loss Energy [J]
The latent heat loss that occurs when the outdoor air humidity ratio < zone air humidity ratio.
1.17.6.2.4 Zone Combined Outdoor Air Latent Heat Gain Energy [J]
The latent heat gain that occurs when the outdoor air humidity ratio > = zone air humidity ratio.
1.17.6.2.5 Zone Combined Outdoor Air Total Heat Loss Energy [J]
The total heat loss that occurs when the sum of Zone Combined Outdoor Air Sensible Heat Gain
Energy and Zone Combined Outdoor Air Latent Heat Gain Energy < the sum of Zone Combined
Outdoor Air Sensible Heat Loss Energy and Zone Combined Outdoor Air Latent Heat Loss Energy.
1.17. GROUP – AIRFLOW 665
1.17.6.2.6 Zone Combined Outdoor Air Total Heat Gain Energy [J]
The total heat gain that occurs when the sum of Zone Combined Outdoor Air Sensible Heat Gain
Energy and Zone Combined Outdoor Air Latent Heat Gain Energy > = the sum of Zone Combined
Outdoor Air Sensible Heat Loss Energy and Zone Combined Outdoor Air Latent Heat Loss Energy.
1.17.6.2.8 Zone Combined Outdoor Air Current Density Volume Flow Rate
[m3/s]
These outputs are the total volume and volume flow rate of outdoor air based on the current density
of zone air.
1.17.6.2.10 Zone Combined Outdoor Air Standard Density Volume Flow Rate
[m3/s]
These outputs are the total volume and volume flow rate of outdoor air based on the standard
density of air. Standard density in EnergyPlus corresponds to 20ºC drybulb, dry air, and nominally
adjusted for elevation.
1.17.7 ZoneMixing
ZoneMixing is intended to allow simplified treatment of air exchange between zones. Note that
this statement only affects the energy balance of the “receiving” zone and that this statement will
not produce any effect on the “source” zone. ZoneMixing statements can be complementary and
include multiple zones, but the balancing of flows between zones is left to the user’s discretion. Also
see ZoneCrossMixing and ZoneRefrigerationDoorMixing. More advanced mixing calculations are
possible using the EnergyPlus AirflowNetwork model for multi-zone airflow with or without HVAC
system operation.
666 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.17.7.1 Inputs
– Flow/Zone
With this choice, the method used will be a straight insertion of the design volume flow rate. (The
Design Flow Rate field should be filled.)
– Flow/Area
With this choice, the method used will be a factor per floor area of the zone. (The Flow per Zone
Floor Area field should be filled).
– Flow/Person
With this choice, the method used will be a factor per nominal number of people in the zone. (The
Flow per Person field should be filled).
– AirChanges/Hour
With this choice, the method used will be the number of air changes per hour for the infiltration
amount. This factor, along with the Zone Volume, will be used to determine the Design Flow Rate.
(The Air Changes per Hour field should be filled).
will be issued and the maximum outdoor shutoff temperature will be set to the minimum outdoor
shutoff temperature.
An IDF Example:
ZoneMixing ,
Kitchen_ZN_1_FLR_1 Exhaust Fanmixing_0 , !- Name
Kitchen_ZN_1_FLR_1 , !- Zone Name
Hours_of_operation , !- Schedule Name
Flow/Zone , !- Design Flow Rate Calculation Method
1.4540 , !- Design Level
, !- Volume Flow Rate per Area {m3/s/m2}
, !- Volume Flow Rate Per Person {m3/s/person}
, !- Air Changes per Hour {ACH}
CAFETERIA_ZN_1_FLR_1 , !- Source Zone Name
0.0; !- Delta Temperature
1.17.7.2 Outputs
1.17.8 ZoneCrossMixing
ZoneCrossMixing is ideally suited for two zones that exchange an equal amount of air between
each other. As with ZoneMixing, this is a simplified interzone airflow in EnergyPlus. The main
difference between ZoneMixing and ZoneCrossMixing is that cross mixing has an energy effect on
both the source and the receiving zone, thus maintaining both the air mass and energy balances
in the two zones. For refrigerated zones, see ZoneRefrigerationDoorMixing. More advanced mixing
calculations are possible using the EnergyPlus AirflowNetwork model for multi-zone airflow with or
without HVAC system operation.
ZoneCrossMixing can be entered once (in one of the mixing zones), twice (once for each zone), or
multiple times (exchanging with more than one zone). Each object will be modeled with its own
control conditions. The object may be entered once if Delta Temperature > 0.0 and it is desirable
to have mixing only when the source zone is warmer than the receiving zone. This might be the
case when the warmer zone is below the colder zone and the mixing is buoyancy driven. If the zones
are next to each other, separated by an open doorway, it would be more suitable to input a cross
mixing object for each zone. Then mixing would occur if the zone temperatures differed by Delta
Temperature or greater regardless of which is the warmer zone.
1.17.8.1 Inputs
– Flow/Zone
With this choice, the method used will be a straight insertion of the design volume flow rate. (The
Design Flow Rate field should be filled.)
– Flow/Area
With this choice, the method used will be a factor per floor area of the zone. (The Flow per Zone
Floor Area field should be filled).
– Flow/Person
672 CHAPTER 1. INPUT-OUTPUT REFERENCE
With this choice, the method used will be a factor per nominal number of people in the zone. (The
flow per person field should be filled).
– AirChanges/Hour
With this choice, the method used will be the number of air changes per hour for the infiltration
amount. This factor, along with the Zone Volume, will be used to determine the Design Flow Rate.
(The Air Changes per Hour field should be filled).
ZoneCrossMixing ,
1stFloor -Garage , !- Name
GARAGE , !- Zone Name
Always On , !- SCHEDULE Name
Flow/Zone , !- Design Flow Rate calculation method
0.1, !- Design Flow Rate {m3/s}
, !- Flow Rate per Area {m3/s/m2}
, !- Flow Rate per Person {m3/s/person}
, !- Air Changes Per Hour
1ST -FLOOR , !- Source Zone Name
1.0; !- Delta temp
ZoneCrossMixing ,
Garage -1stFloor , !- Name
1ST -FLOOR , ! Zone Name
Always On , !- SCHEDULE Name
flow/zone , !- Design Flow Rate calculation method
0.1, !- Design Flow Rate {m3/s}
, !- Flow Rate per area {m3/s/m2}
, !- Flow Rate per person {m3/s/person}
, !- Air Changes Per Hour
GARAGE , ! Source Zone Name
1.0; ! Delta temp
1.17.8.2 Outputs
1.17.9 ZoneRefrigerationDoorMixing
ZoneRefrigerationDoorMixing is ideally suited for two zones, at least one of which is refrigerated, that
exchange an equal amount of dry air. As with ZoneMixing, this is a simplified interzone airflow in
EnergyPlus. The ZoneRefrigerationDoorMixing approach shares some features of both ZoneMixing
and ZoneCrossMixing. Like ZoneCrossMixing, ZoneRefrigerationDoorMixing has an energy effect on
both the source and the receiving zone, thus maintaining both the air mass and energy balances in
the two zones. Unlike the other two mixing objects, ZoneRefrigerationDoorMixing always calculates
the air exchange rate based on the zone temperature and relative humidity. That is, the user does
not specify the air flow rate. The user can moderate the flow through a door-opening schedule.
ZoneRefrigerationDoorMixing can only be entered once for any unique pair of zones. It doesn’t
matter which zone is listed first and the zones will automatically switch back and forth between
source and receiving zones depending upon which zone is colder.
1.17.9.1 Inputs
– None
– AirCurtain
– StripCurtain
An IDF Example:
ZoneRefrigerationDoorMixing ,
Freezer1_Cooler1 , !- Name
Freezer1 , !- Zone 1 Name
Cooler1 , !- Zone 2 Name
Freezer1DoorSched , !- Schedule Name
1.8, !- Door height {m}
2.3, !- Door area {m2}
StripCurtain; !- Door protection type
1.17.9.2 Outputs
1.17.10 ZoneEarthtube
An earth tube is a long, underground metal or plastic pipe through which air is drawn. During
cooling season, as air travels through the pipe, it gives up some of its heat to the surrounding soil
and enters the room as cooler air. Similarly, during heating season, as air travels through the pipe,
it receives some of its heat from the soil and enters the room as warmer air. Simple earth tubes in
EnergyPlus can be controlled by a schedule and through the specification of minimum, maximum,
and delta temperatures as described below. As with infiltration and ventilation, the actual flow rate
of air through the earth tube can be modified by the temperature difference between the inside and
outside environment and the wind speed. The basic equation used to calculate air flow rate of earth
tube in EnergyPlus is:
EarthT ubeF lowRate = (Edesign ) (Fschedule ) A + B |Tzone − Todb | + C (W indSpeed) + D W indSpeed2
(1.47)
For the simulation of the earth tube, a weather data file is required and, therefore, the earth tube
cannot run without weather data file. The required input fields to simulate the earth tube include the
average soil surface temperature, the amplitude of soil surface temperature, and the phase constant
of soil surface temperature. These fields should be calculated in advance by using a separate stand-
alone program (CalcSoilSurfTemp) and should be input into earth tube.
The CalcSoilSurfTemp program is simple and requires only two input fields : soil condition and soil
surface condition in addition to a valid weather file. For soil condition, the user should select the
number corresponding to the actual condition of the soil surrounding the earth tube from the four
680 CHAPTER 1. INPUT-OUTPUT REFERENCE
following options: 1. HEAVY AND SATURATED, 2. HEAVY AND DAMP, 3. HEAVY AND DRY
and 4. LIGHT AND DRY. This determines the thermal diffusivity and thermal conductivity of the
surrounding soil. For soil surface conditions, the user should select the number corresponding to
the actual condition of the ground surface above the earth tube from the eight following options:
1. BARE AND WET, 2. BARE AND MOIST, 3. BARE AND ARID, 4. BARE AND DRY, 5.
COVERED AND WET, 6. COVERED AND MOIST, 7. COVERED AND ARID and 8. COVERED
AND DRY. This determines the absorption coefficient and the fraction of evaporation rate of the
ground surface.
From this information and an analysis of the weather for the location selected, the CalcSoilSurfTemp
program (ref. Auxiliary Programs document) calculates the three parameters listed above. The user
must then add these parameters as input into EnergyPlus. The full input description of an earth
tube in EnergyPlus is given below.
This field is the name of the zone (ref: Zone) and attaches a particular earth tube statement to a
thermal zone in the building.
This field is the name of the schedule (ref: Schedule) that modifies the maximum design volume flow
rate parameter (see next field). This fraction between 0.0 and 1.0 is noted as Fschedule in the above
equation.
This number (noted as Edesign in the above equation) is the maximum amount of air mass flow rate
of the earth tube expected at design conditions. The flow rate is expressed in units of m3 /s. The
design value is modified by the schedule fraction (see previous field) and user specified coefficients
(see last four fields).
This is the indoor temperature (in Celsius) below which the earth tube is shut off. This lower
temperature limit is intended to avoid overcooling a space and thus result in a heating load. For
example, if the user specifies a minimum temperature of 20°C, earth tube is assumed to be available
if the zone air temperature is above 20°C. If the zone air temperature drops below 20°C, then earth
tube is automatically turned off.
This is the indoor temperature (in Celsius) above which the earth tube is shut off. This higher
temperature limit is intended to avoid overheating a space and thus result in a cooling load. For
example, if the user specifies a maximum temperature of 20°C, earth tube is assumed to be available
if the zone air temperature is below 20°C. If the zone air temperature rises above 20°C, then earth
tube is automatically turned off.
1.17. GROUP – AIRFLOW 681
This is the temperature difference (in Celsius) between the indoor and outdoor air dry-bulb temper-
atures below which the earth tube is shut off. This is to allow the earth tube to be stopped either
if the temperature outside is too warm and could potentially heat the space or if the temperature
outside is too cold and could potentially cool the space. For example, if the user specifies a delta
temperature of 2°C, earth tube is assumed to be available if the temperature difference between
indoor and outdoor temperature is at least 2°C. If the outside air dry-bulb temperature is less than
2°C cooler or warmer than the indoor dry-bulb temperature, then the earth tube is automatically
turned off.
This alpha character string defines the type of earth tube as one of the following options: Natural,
Exhaust, or Intake. A natural earth tube is assumed to be air movement/exchange that will not
consume any fan energy or is the result of natural air flow through the tube and into the building.
Values for fan pressure and efficiency for a natural flow earth tube are ignored. For either EXHAUST
or Intake, values for fan pressure and efficiency define the fan electric consumption. For Natural and
Exhaustearth tubes, the conditions of the air entering the space are assumed to be equivalent to
the air which is cooled or heated by passing along the pipe. For Intake earth tubes, an appropriate
amount of fan heat is added to the air stream.
This is the pressure rise experienced across the fan in Pascals (N/m2 ). This is a function of the fan
and plays a role in determining the amount of energy consumed by the fan.
This is the total fan efficiency (a decimal number between 0.0 and 1.0). This is a function of the fan
and plays a role in determining the amount of energy consumed by the fan.
This is the radius of the earth tube/pipe (in meters). This plays a role in determining the amount
of heat transferred from the surrounding soil to the air passing along the pipe. If the pipe has
non-circular cross section, user can use the concept of hydraulic diameter as follows.
However, since this field requires the pipe radius, hydraulic diameter should be divided by two.
This is the thickness of the pipe wall (in meters). This plays a role in determining the amount of
heat transferred from the surrounding soil to the air passing along the pipe.
682 CHAPTER 1. INPUT-OUTPUT REFERENCE
This is the total length of the pipe (in meters). This plays a role in determining the amount of heat
transferred from the surrounding soil to the air passing along the pipe. As the length of the pipe
becomes longer, the amount of the heat transfer becomes larger.
This is the thermal conductivity of the pipe (in W/m°C). This plays a role in determining the amount
of heat transferred from the surrounding soil to the air passing along the pipe.
This is the depth of the pipe under the ground surface (in meters). This plays a role in determining
the temperature of the soil surrounding the pipe.
This alpha character string defines the actual condition of the soil surrounding the earth tube and
can be one of any of the following options: HeavyAndSaturated, HeavyAndDamp, HeavyAndDry or
LightAndDry. This determines the thermal diffusivity and thermal conductivity of the surrounding
soil, which play a role in determining the amount of heat transferred from the surrounding soil to
the air passing along the pipe.
This is the annual average soil surface temperature straight above the earth tube, which plays a role
in determining the temperature of the soil surrounding the pipe. This field should be calculated in
advance using the separate CalcSoilSurfTemp program.
This is the amplitude of soil surface temperature above the earth tube, which plays a role in de-
termining the temperature of the soil surrounding the pipe. This is the difference between the
maximum and minimum soil surface temperature for the whole year divided by two. This field
should be calculated in advance using the separate CalcSoilSurfTemp program.
This is the phase constant of the soil surface temperature straight above the earth tube, which play
a role in determining the temperature of the soil surrounding the pipe at particular time. This is the
time elapsed from the beginning of the year until the soil surface temperature reaches the minimum
value of the year. This field should be calculated in advance using the separate CalcSoilSurfTemp
program.
1.17. GROUP – AIRFLOW 683
This number is the “A” parameter in the above earth tube equation. It is part of the user specified
modifying parameters that are a function of environmental factors. This parameter, however, is a
constant under all conditions and is not modified by any environmental effect. As a result, it is
dimensionless.
This number is the “B” parameter in the above earth tube equation. It is part of the user specified
modifying parameters that are a function of environmental factors. This parameter is modified by
the temperature difference between the outdoor and indoor air dry-bulb temperatures. The units
for this parameter are inverse Celsius.
This number is the “C” parameter in the above earth tube equation. It is part of the user specified
modifying parameters that are a function of environmental factors. This parameter is modified by
the speed of wind being experienced outside the building. The units for this parameter are s/m.
This number is the “D” parameter in the above earth tube equation. It is part of the user specified
modifying parameters that are a function of environmental factors. This parameter is modified by
square of the speed of wind being experienced outside the building. The units for this parameter are
s2 /m2 .
An IDF example:
EARTHTUBE ,
Zone 2, !- Zone Name
Simple EarthTube , !- Schedule Name
3.425198 , !- Design Volume Flow Rate
10.0, !- Minimum Zone Temperature when Cooling
30.0, !- Maximum Zone Temperature when Heating
1.0, !- Delta Temperature
NATURAL , !- EarthTube Type
350.0 , !- Fan Pressure Rise
0.9, !- Fan Total Efficiency
0.25, !- Pipe Radius
0.2, !- Pipe Thickness
15.0, !- Pipe Length
200.0 , !- Pipe Thermal Conductivity
3.5, !- Pipe Depth Under Ground Surface
HeavyAndDamp , !- Soil Condition
15.0, !- Average Soil Surface Temperature
5.6, !- Amplitude of Soil Surface Temperature
0.0, !- Phase Constant of Soil Surface Temperature
0.6060000 , !- Constant Term Flow Coef
2.0199999E-02, !- Temp Term Flow Coef
5.9800001E-04, !- Velocity Term Flow Coef
0.0000000E+00; !- Velocity **2 Term Flow Coef
684 CHAPTER 1. INPUT-OUTPUT REFERENCE
These are the energy and rate associated with the zone cooling provided by the air from the earth
tube. This occurs when the earth tube outlet air temperature is less than zone air temperature.
These are the energy and rate associated with the zone heating provided by the air from the earth
tube. This occurs when the earth tube outlet air temperature is greater than the zone air temper-
ature.
The volume flow rate of air through the earth tube evaluating density at current zone conditions.
1.17. GROUP – AIRFLOW 685
The volume flow rate of air through the earth tube evaluating density at standard conditions.
The mass flow rate of water vapor at the exit of the earth tube.
These are the fan electricity consumption and power for intake or exhaust earth tube types.
This is the temperature of the air entering the zone after passing through the earth tube [C]. This
temperature includes the cooling or heating of outdoor air as it passes along the pipe. When intake
fan assist is used, then the additional heat due to the fan is included in the inlet air temperature.
This is the average temperature of the ground along the outer surface of the earth tube [C].
This is the rate of heat transfer from the earth tube to the outdoor air [W]. Positive values indicate
the rate at which outdoor air is preheated; negative values indicate the rate of precooling.
This is the wet bulb temperature of the air entering the zone after passing through the earth tube
[C].
This is the humidity ratio of the air entering the zone after passing through the earth tube [kgWa-
ter/kgDryAir].
686 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.17.12 ZoneCoolTower:Shower
A cooltower (which is sometimes referred to as a wind tower or a shower cooling tower) is a component
that is intended to model a passive downdraught evaporative cooling (PDEC) that is designed to
capture the wind at the top of a tower and cool the outside air using water evaporation before
delivering it to a space. The air flow in these systems is natural as the evaporation process increases
the density of the air causing it to fall through the tower and into the space without the aid of a
fan. A cooltower typically consists of a water spray or an evaporative pad, a shaft, and a water tank
or reservoir. Wind catchers to improve the wind-driven performance at the top of the tower are
optional. Water is pumped over an evaporative device by water pump which is the only component
consumed power for this system. This water cools and humidifies incoming air and then the cool,
dense air naturally falls down through shaft and leaves through large openings at the bottom of
cooltowers.
The shower cooling tower can be controlled by a schedule and the specification of maximum water
flow rate and volume flow rate as well as minimum indoor temperature. The actual flow rate of
water and air can be controlled as users specify the fractions of water loss and flow schedule. The
required input fields include effective tower height and exit area to obtain the temperature and flow
rate of the air exiting the tower. A schedule and rated power for the water pump are also required
to determine the power consumed. The component typically has a stand alone water system that is
not added to the water consumption from mains. However, users are required to specify the water
source through an optional field, the name of water supply storage tank, in case any water comes
from a water main. The model is described more fully in the Engineering Reference document.
This model requires weather information obtained from either design day or weather file specifica-
tions. The control is accomplished by either specifying the water flow rate or obtaining the velocity
at the outlet with inputs and weather conditions when the water flow rate is unknown. As with
infiltration, ventilation, and earth tubes, the component is treated in a similar fashion to “natural
ventilation” in EnergyPlus.
1.17.12.1 Inputs
ZoneCoolTower:Shower
Cool Tower 1, !- Name of cooltowers
Zone 1, !- Zone name
Simple Vent , !- Schedule
, !- Name of water supply storage tanks
WindDrivenFlow , !- Flow control type
0.0005 , !- Water flow rate from the spray in m3/s
, !- schedule for flow rate (optional , non -existent means constant)
5.0, !- Effective tower height in m
1.0, !- Exit area in m2
10.0, !- Maximum supply air volume flow rate in m3/s
18.0, !- Minimum indoor temperature to prevent overcooling in C
0.05, !- Fraction of Water loss
0.05, !- Fraction of flow that goes to outside
250.0; !- Rated power consumption in W
1.17.12.2 Outputs
1.17.12.2.5 Zone Cooltower Current Density Air Volume Flow Rate [m3/s]
The volumetric flow rate of the air leaving the cooltower evaluating density at current zone conditions.
1.17.12.2.6 Zone Cooltower Standard Density Air Volume Flow Rate [m3/s]
The volumetric flow rate of the air leaving the cooltower evaluating density at standard conditions.
1.17.13 ZoneThermalChimney
A thermal chimney is a vertical shaft utilizing solar radiation to enhance the natural ventilation in
buildings. It consists of a absorber wall, air gap and glass cover with high solar transmissivity. For
the high solar absorption, it is usually south facing.
The key output parameter in the thermal chimney model is the enhanced amount of natural ven-
tilation rate caused by the presence of a thermal chimney. In order to determine the enhanced
ventilation, the discharge air temperature from a thermal chimney should be calculated, which, in
turn, should be computed based on the information on the absorber wall temperature, glass cover
temperature and the vertical air temperature distribution within the thermal chimney. Among them,
energy balances for the absorber wall and the glass cover are carried out using the existing algorithm
currently available in EnergyPlus, which has the similar approach to the Trombe wall. As stated in
the Trombe wall object as well, this approach allows the flexibility for users to specify the various
wall parameters and to explore unusual configurations. On the other hand, the vertical air tempera-
ture distribution and the resultant discharge air temperature of the thermal chimney are computed
using the separate thermal chimney algorithm described in the Engineering Reference document.
Similar to the Trombe wall model, a zone is coupled to the desired surface via an interzone partition.
To simulate the thermal chimney, the Solar Distribution field in the Building object should be set
to FullInteriorAndExterior so that the majority of the solar flux is directed on the absorber wall.
For a normal sized thermal chimney zone, the user can set the Zone Inside Convection Algorithm to
“Detailed”, which takes into account natural convection effects intended for a normal zone. For a
narrow cavity zone having high aspect ratios, there is no built-in algorithm for calculating the correct
convection coefficients on the inside of thermal chimney zone walls. One option is to use the “De-
tailed” convection algorithm similar to the Trombe wall model. However, some error may be incurred
when used with a narrow zone. Another option is to use the SurfaceProperty:ConvectionCoefficients
object to schedule coefficients that have been determined beforehand by the user. In addition, the
wall construction of the adjoining zone must be the mirror image of the wall construction in the
thermal chimney zone.
The full input description of a thermal chimney in EnergyPlus is given below.
This field is a unique user assigned name for an instance of the thermal chimney system.
This field is the name of the thermal chimney zone (ref: Zone). Since the thermal chimney is not
only a system component but also a zone itself, this field is also necessary. It should be differentiated
from the Zone name field described later.
This field is the name of the schedule (ref: Schedule) that denotes whether the thermal chimney can
operate during a given time period. A schedule value greater than 0 (usually 1 is used) indicates
that the system is available and can be on during the time period. A value less than or equal to 0
(usually 0 is used) denotes that the system is not available and must be off for the time period. If
this field is blank, the schedule has values of 1 for all time periods.
692 CHAPTER 1. INPUT-OUTPUT REFERENCE
This number is the width of the absorber wall in the thermal chimney. The width is expressed
in units of m. Even though this value is specified in Surface objects as well, this value is used to
compute the discharge air temperature and the enhanced ventilation rate caused by the thermal
chimney.
This number is the cross sectional area of air channel outlet. The area is expressed in units of
m2 . The enhanced air flow rate by the thermal chimney is dependent on cross sectional areas of
air channel inlet and outlet. Cross sectional areas of air channel inlet will be described later in
conjunction with the distance from the top of thermal chimney to each inlet and relative ratios of
air flow rates passing through each inlet.
This dimensionless number is the discharge coefficient of the thermal chimney. The ventilation rate
enhanced by the thermal chimney is also dependent on the discharge coefficient.
This field is the name of the zone (ref: Zone) to which the thermal chimney is attached. It is used
in conjunction with the next three fields. Note that up to 20 sets of zone name, distance from the
top of the thermal chimney to each inlet, relative ratios of air flow rates passing through each zone
and cross sectional areas of each air channel inlet may be entered for a single thermal chimney if
multiple zones share the common thermal chimney.
This field is the distance from the top of the thermal chimney to each inlet corresponding to each
zone. It is used in conjunction with the zone name, relative ratios of air flow rates passing through
each zone and cross sectional areas of each air channel inlet. The distance is expressed in units of
m. The air flow rate enhanced by the thermal chimney is dependent on the distance between the
thermal chimney outlet and inlet.
1.17.13.9 Field: Relative Ratios of Air Flow Rates Passing through Zone <#>
This dimensionless number is the relative ratio of air flow rates enhanced by the thermal chimney
passing through each zone. The total air flow rate enhanced by the thermal chimney is distributed
to each zone based on this number if multiple zones share the common thermal chimney. It is used
in conjunction with the zone name, the distance from the top of the thermal chimney to each inlet
and cross sectional areas of each air channel inlet. Note that the sum of all ratios must be equal to
1.0.
1.17. GROUP – AIRFLOW 693
This field is the cross sectional areas of each air channel inlet corresponding to each zone. It is used
in conjunction with the zone name, the distance from the top of the thermal chimney to each inlet
and relative ratios of air flow rates passing through each zone. The area is expressed in units of
m2 . The air flow rate enhanced by the thermal chimney is dependent on cross sectional areas of air
channel inlet and outlet.
An IDF example:
ZoneThermalChimney ,
ThermalChimney1 , !- Name of Thermal Chimney System
ThermalChimneyZone , !- Name of Thermal Chimney Zone
ThermalChimneyAvail , !- Availability Schedule Name
3.5, !- Width of the Absorber Wall
0.04, !- Cross Sectional Area of Air Channel Outlet
0.8, !- Discharge Coefficient
Zone1 , !- Zone Name 1
8.0, !- Distance from the Top of the Thermal Chimney to Inlet 1
0.8, !- Relative Ratios of Air Flow Rates Passing through Zone 1
0.02, !- Cross Sectional Areas of Air Channel Inlet 1
Zone2 , !- Zone Name 2
5.0, !- Distance from the Top of the Thermal Chimney to Inlet 2
0.2, !- Relative Ratios of Air Flow Rates Passing through Zone 2
0.02; !- Cross Sectional Areas of Air Channel Inlet 2
– HVAC,Average,Zone Thermal Chimney Current Density Air Volume Flow Rate [m3/s]
– HVAC,Average,Zone Thermal Chimney Standard Density Air Volume Flow Rate [m3/s]
– HVAC,Average,Zone Thermal Chimney Mass Flow Rate [kg/s]
– HVAC,Average,Zone Thermal Chimney Outlet Temperature [C]
– HVAC,Sum,Zone Thermal Chimney Heat Loss Energy [J]
– HVAC,Sum,Zone Thermal Chimney Heat Gain Energy [J]
– HVAC,Sum,Zone Thermal Chimney Volume [m3]
– HVAC,Sum,Zone Thermal Chimney Mass [kg]
The sensible (temperature) heat loss of each zone that occurs when the thermal chimney cools the
zone air.
The sensible (temperature) heat gain of each zone that occurs when the thermal chimney heats the
zone air.
694 CHAPTER 1. INPUT-OUTPUT REFERENCE
The air volumetric flow of each zone enhanced by the thermal chimney.
The air mass flow of each zone enhanced by the thermal chimney.
1.17.14.5 Zone Thermal Chimney Current Density Air Volume Flow Rate [m3/s]
The total air volumetric flow rate caused by the thermal chimney evaluating density at the current
zone conditions.
1.17.14.6 Zone Thermal Chimney Standard Density Air Volume Flow Rate
[m3/s]
The total air volumetric flow rate caused by the thermal chimney evaluating density at standard
conditions.
The total air mass flow rate caused by the thermal chimney.
The temperature of the air which is discharged from the thermal chimney through the outlet.
In addition, the mass flow rate and associated sensible and latent loads are included in Zone Infiltra-
tion * output variables. In other words, the output variables of Zone Infiltration * include impact
of ZoneThermalChimney.
1.17.15 ZoneAirMassFlowConservation
This global object allows users to trigger the zone air mass flow conservation calculation when de-
sired. This object has three input fields; the first choice input field allows the user whether to adjust
mixing flows, the return air flow, or a combination of mixing and return air flows to enforce the
zone air mass flow conservation; and the other fields allows the user to specify how infiltration object
mass flow rate is calculated for zone air mass flow balance calculation. Currently supported options
are: AdjustMixingOnly, AdjustReturnOnly, AdjustMixingThenReturn, AdjustReturn-
ThenMixing, or None. If adjustments for either of mixing, return, or a combination of mixing and
return or infiltration is specified then the zone air mass balance attempts to enforce conservation. If
adjutement choice is None and infiltration adjustments are off, then the zone air mass flow calcula-
tion uses the default method which does not include zone mixing objects and assumes self-balanced
simple infiltration. The default method may not necessarily enforce zone air mass flow conservation
unless the user has specified a balanced flow to begin with. The zone air mass flow conservation
primarily accounts for the zonemixing objects and return air flows in the zone air flow mass balance
calculation. In addition to the zonemixing object and zone return air flows, the procedure accounts
1.17. GROUP – AIRFLOW 695
for zone supply, exhaust, and adjusts infiltration air flows (up or down) when required in order to
balance the zone air mass flow. Mixing and infiltration adjustments will only be made in zones
which have zonemixing or infiltration objects defined in the input. For example, if a zone does not
have any infiltration objects, then no infiltration adjustment will be made for that zone.
The zone mixing object and return flows adjusting options to enforce zone air mass flow conseravtion
are defined as follows. AdjustMixingOnly adjusts the zone mixing object flow only to enforce
zone air mass flow balance. AdjustReturnOnly adjusts the zone return air flow only to enforce
zone air mass flow balance while the zone mixing object flow are kept at user specified values.
AdjustMixingThenReturn adjusts the zone mixing object flow first, and followed with adjusting
the return air flows to enforce zone air mass flow balance. AdjustReturnThenMixing adjusts the
zone return air flow first, and followed with adjusting the zone mixing object flow to enforce zone
air mass flow balance. None does not adjust either the zone mixing or the zone return air flow, and
the zone air mass flow balance uses the default method.
First, depending user choice either the ZoneMixing object mass flow rate, the zone total return air
flow rate, or a combination zone mixing and zone total return flow rates are adjusted or modified in
order to balance zone air mass flow while assuming any zone infiltration objects are self-balanced.
This step will always results in balanced zone air mass for receiving zones of ZoneMixing object but
it may not necessarily result in a balanced air mass flow for source zones.
Second, infiltration flow rates are adjusted according to the options set. Infiltration flow will be
increased or decreased to balance the net flow from supply, exhaust, mixing, and return air flows. If
a negative infiltration rate (exfiltration) is required to balance a zone’s airflow, then the infiltration
rate will be set to zero. This can happen, for example, if the total supply flow exceeds the total
exahust plus return flow.
This object is optional. If it is not present in the input file, the default zone air mass flow calculastion
are used which do not account for zonemixing and infiltration flows.
1.17.15.1 Inputs
1.17.15.1.1 Field: Adjust Zone Mixing and Return For Air Mass Flow Balance
ZoneAirMassFlowConservation ,
Yes , !- Adjust Zone Mixing For Zone Air Mass Flow Balance
AdjustInfiltrationFlow ; !- Infiltration Balancing Method
AllZones; !- Infiltration Balancing Zones
1.17.15.2 Outputs
– HVAC, Average, Zone Air Mass Balance Supply Mass Flow Rate [kg/s]
– HVAC, Average, Zone Air Mass Balance Exhaust Mass Flow Rate [kg/s]
– HVAC, Average, Zone Air Mass Balance Return Mass Flow Rate [kg/s]
– HVAC, Average, Zone Air Mass Balance Mixing Receiving Mass Flow Rate [kg/s]
– HVAC, Average, Zone Air Mass Balance Mixing Source Mass Flow Rate [kg/s]
– HVAC, Average, Zone Infiltration Air Mass Flow Balance Status, []
– HVAC, Average, Zone Mass Balance Infiltration Air Mass Flow Rate, [kg/s]
1.17. GROUP – AIRFLOW 697
1.17.15.2.1 Zone Air Mass Balance Supply Mass Flow Rate [kg/s]
This output variable represents the total supply air mass flow rate of a zone. The value is determined
by summing the supply air mass flow rates contributions from all supply air inlet nodes of a zone.
1.17.15.2.2 Zone Air Mass Balance Exhaust Mass Flow Rate [kg/s]
This output variable represents the total exhaust air mass flow rate of a zone. The value is determined
by summing the exhaust air mass flow rates contributions from all exhaust air nodes of a zone.
1.17.15.2.3 Zone Air Mass Balance Return Mass Flow Rate [kg/s]
This output variable represents the total return air mass flow rate of a zone. The value is determined
by summing the return air mass flow rates contributions from return air nodes of a zone.
1.17.15.2.4 Zone Air Mass Balance Mixing Receiving Mass Flow Rate [kg/s]
This output variable represents the total zone mixing air mass flow rate of a receiving zone from one
or more mixing objects. The value is determined by summing the air mass flow contributions from
all zone mixing objects connected to a single receiving zone.
1.17.15.2.5 Zone Air Mass Balance Mixing Source Mass Flow Rate [kg/s]
This output variable represents the total zone mixing source air mass flow rate of a source zone feeding
one or more mixing objects. The value is determined by summing the air mass flow contributions
from all zone mixing objects connected to a single source zone.
1.17.15.2.7 Zone Air Mass Balance Infiltration Mass Flow Rate [kg/s]
This output variable represents the zone infiltration air mass flow rate in kg/s. This output variable is
reported only for source zones and when the zone air mass flow balance is active. Its value depends on
the Infiltration Balancing Method specified. When the infiltration method is AddInfiltrationFlow this
output represents the additional infiltration air mass flow rate added on top of the base infiltration
air flow in order to balance the zone air mass flow. In this case, the base infiltration air mass flow
calculated using the user specified input is assumed self-balanced. When the infiltration method is
AdjustInfiltrationFlow and the value of “Zone Air Mass Balance Infiltration Status” is 1, this output
represents the infiltration air mass flow rate required to balance the zone air mass flow. This value
could be negative if the zone supply exceeds all other outflows. If the value of “Zone Air Mass
Balance Infiltration Status” is 0, then this output is the self-balanced base infiltration flow rate for
current timestep.
698 CHAPTER 1. INPUT-OUTPUT REFERENCE
In order for EnergyPlus to successfully calculate zone design heating and cooling loads and air flow
rates and for the program to use these results to automatically size the HVAC components a number
of input objects must be present and certain object input fields must be entered.
– The input file should contain a SimulationControl object. The 1st field Do Zone Sizing Calcu-
lation should be entered as Yes. This will cause a zone sizing simulation to be done using all
the sizing periods in the input file as weather. If there are no air or water loops in the HVAC
input fields 2 and 3 can be set to No. If there are one or more air loops (i.e., there is at least one
AirLoopHVAC object in the input file) then the 2nd field Do System Sizing Calculation should
be entered as Yes. If there are one or more water loops (Plant Loop objects) then the 3rd field
Do Plant Sizing Calculation should be set to Yes. Finally either the 4th field (Run Simulation
for Sizing Periods) or the 5th field (Run Simulation for Weather File Run Periods) should be
set to Yes in order to autosize the components and do a real simulation using the autosized
components. The component autosizing calculations are done on the first pass through the
HVAC system in the real simulation.
– There must be at least 2 (up to any number) SizingPeriod objects present. Normally one will
be for summer conditions and one for winter. The summer day should normally have the field
Day Type set to SummerDesignDay. The winter design day should normally have Day Type
set to WinterDesignDay.
– To apply a global sizing factor include the Sizing:Parameters object.
– For each controlled zone in the input file there should be a corresponding Sizing:Zone object.
Similarly for each AirLoopHVAC there should be a Sizing:System object. And for each Plant
or Condenser Loop there should be a Sizing:Plant object. Note however that if a controlled
zone has no corresponding Zone Sizing object the data from the first Zone Sizing object will
be used. Thus if all the zone sizing information is the same only one Zone Sizing object need
be entered.
– Only controlled zones are included in the zone and system sizing calculations. Thus for a design
air flow rate to be calculated for a zone, it must contain a thermostat even though it might not
need or have a thermostat in the full simulation. An illustration would be a three zone building
with a packaged single zone system and a thermostat in one of the zones. In order for the two
slave zones to be included in the design air flow calculations they must be treated as if they
have a thermostat: there must be a ZoneControl:Thermostat for each of the slave zones.
– Some attention should be paid to schedules. In a weekly schedule object the 9th and 10th day
schedules are for summer and winter design days respectively. This means that if a SizingPeriod
object has field Day Type set to SummerDesignDay the day schedule for summer sizing periods
will be in effect. Similarly if a SizingPeriod object has field Day Type set to WinterDesignDay
the day schedule for winter sizing periods will be in effect. Some possible applications of this
capability are:
1) setting internal loads (lights, equipment, occupancy) to maximum all day for cooling and to zero
all day for heating;
1.18. GROUP – DESIGN OBJECTS 699
2) setting heating and cooling thermostat set points to constant values (no set up or set back);
3) setting heating and cooling equipment to be always on.
None of these applications are necessarily recommended but these and other uses of the special
summer/winter design day schedules may prove useful for specific situations.
– Other than zone thermostat setpoints, the sizing calculations generally know nothing about the
system control inputs such as setpoints and availability schedules. The user must coordinate
sizing inputs with the actual simulation control inputs.
– The sizing calculations only recognize the presence of central heating and cooling coils, preheat
and precool coils and reheat coils. These are assumed to deliver the various supply temperatures
specified in the Sizing:System and Sizing:Zone objects. The impact of other components such
as heat recovery, dehumidifiers, and pumps are not accounted for in the sizing calculations.
Central supply and return fan temperature rise is taken into account in sizing the central
cooling coils.
For autosizing to occur at the component level the user must enter the special value autosize in
the numeric fields for which autosizing is available. Those fields can be found by looking at the
Energy+.idd data dictionary file or under individual object details in this document. Fields that
can be autosized are denoted with the comment \autosizable. The components and fields that are
autosizable are listed in the following table. Note that spaces may be inserted in object names to
facilitate readability.
AirConditioner:VariableRefrigerantFlow
Gross Rated Total Cooling Capacity
Gross Rated Heating Capacity
Resistive Defrost Heater Capacity
Water Condenser Volume Flow Rate
Evaporative Condenser Air Flow Rate
Evaporative Condenser Pump Rated Power Con-
sumption
AirLoopHVAC
Design Supply Air Flow Rate
AirLoopHVAC:Unitary:Furnace:HeatCool
Maximum Supply Air Temperature
Cooling Supply Air Flow Rate
Heating Supply Air Flow Rate
No Load Supply Air Flow Rate
AirLoopHVAC:Unitary:Furnace:HeatOnly
Maximum Supply Air Temperature
700 CHAPTER 1. INPUT-OUTPUT REFERENCE
AirLoopHVAC:UnitarySystem
Cooling Supply Air Flow Rate
Heating Supply Air Flow Rate
No Load Supply Air Flow Rate
Maximum Supply Air Temperature
AirTerminal:DualDuct:ConstantVolume
Maximum Air Flow Rate
AirTerminal:DualDuct:VAV
Maximum Damper Air Flow Rate
AirTerminal:DualDuct:VAV:OutdoorAir
Maximum Terminal Air Flow Rate
AirTerminal:SingleDuct:ConstantVolume:CooledBeam
Supply Air Volumetric Flow Rate
Maximum Total Chilled Water Volumetric Flow
Rate
Number of Beams
Beam Length
AirTerminal:SingleDuct:ConstantVolume:FourPipeInduction
Maximum Total Air Flow Rate
Maximum Hot Water Flow Rate
Maximum Cold Water Flow Rate
AirTerminal:SingleDuct:ConstantVolume:Reheat
Maximum Air Flow Rate
Maximum Hot Water or Steam Flow Rate
AirTerminal:SingleDuct:ParallelPIU:Reheat
Maximum Primary Air Flow Rate
Maximum Secondary Air Flow Rate
Minimum Primary Air Flow Fraction
Fan On Flow Fraction
Maximum Hot Water or Steam Flow Rate
AirTerminal:SingleDuct:SeriesPIU:Reheat
Maximum Air Flow Rate
Maximum Primary Air Flow Rate
Minimum Primary Air Flow Fraction
Maximum Hot Water or Steam Flow Rate
AirTerminal:SingleDuct:VAV:HeatAndCool:NoReheat
Maximum Air Flow Rate
AirTerminal:SingleDuct:VAV:HeatAndCool:Reheat
702 CHAPTER 1. INPUT-OUTPUT REFERENCE
Nominal Capacity
Design Chilled Water Flow Rate
Design Condenser Water Flow Rate
Gas Turbine Engine Capacity
Chiller:ConstantCOP
Nominal Capacity
Design Chilled Water Flow Rate
Design Condenser Water Flow Rate
Chiller:Electric
Nominal Capacity
Design Chilled Water Flow Rate
Design Condenser Fluid Flow Rate
Design Heat Recovery Water Flow Rate
Chiller:Electric:EIR
Reference Capacity
Reference Chilled Water Flow Rate
Reference Condenser Fluid Flow Rate
Design Heat Recovery Water Flow Rate
Chiller:Electric:ReformulatedEIR
Reference Capacity
Reference Chilled Water Flow Rate
Reference Condenser Water Flow Rate
Design Heat Recovery Water Flow Rate
Chiller:EngineDriven
Nominal Capacity
Design Chilled Water Flow Rate
Design Condenser Water Flow Rate
ChillerHeater:Absorption:DirectFired
Nominal Cooling Capacity
Design Chilled Water Flow Rate
Design Condenser Water Flow Rate
Design Hot Water Flow Rate
ChillerHeater:Absorption:DoubleEffect
Nominal Cooling Capacity
Design Chilled Water Flow Rate
Design Condenser Water Flow Rate
Design Hot Water Flow Rate
704 CHAPTER 1. INPUT-OUTPUT REFERENCE
ChillerHeaterPerformance:Electric:EIR
Reference Cooling Mode Evaporator Capacity
Design Chilled Water Flow Rate
Design Condenser Water Flow Rate
Coil:Cooling:DX:MultiSpeed
Speed 1 Gross Rated Total Cooling Capacity
Speed 1 Gross Rated Sensible Heat Ratio
Speed 1 Rated Air Flow Rate
Speed 1 Evaporative Condenser Air Flow Rate
Speed 1 Rated Evaporative Condenser Pump
Power Consumption
Speed 2 Gross Rated Total Cooling Capacity
Speed 2 Gross Rated Sensible Heat Ratio
Speed 2 Rated Air Flow Rate
Speed 2 Evaporative Condenser Air Flow Rate
Speed 2 Rated Evaporative Condenser Pump
Power Consumption
Speed 3 Gross Rated Total Cooling Capacity
Speed 3 Gross Rated Sensible Heat Ratio
Speed 3 Rated Air Flow Rate
Speed 3 Evaporative Condenser Air Flow Rate
Speed 3 Rated Evaporative Condenser Pump
Power Consumption
Speed 4 Gross Rated Total Cooling Capacity
Speed 4 Gross Rated Sensible Heat Ratio
Speed 4 Rated Air Flow Rate
Speed 4 Evaporative Condenser Air Flow Rate
Speed 4 Rated Evaporative Condenser Pump
Power Consumption
Coil:Cooling:DX:SingleSpeed
Gross Rated Total Cooling Capacity
Gross Rated Sensible Heat Ratio
Rated Air Flow Rate
Evaporative Condenser Air Flow Rate
Evaporative Condenser Pump Rated Power Con-
sumption
Coil:Cooling:DX:SingleSpeed:ThermalStorage
Rated Evaporator Air Flow Rate
1.18. GROUP – DESIGN OBJECTS 705
EvaporativeFluidCooler:TwoSpeed
High Fan Speed Air Flow Rate
High Fan Speed Fan Power
High Fan Speed U-factor Times Area Value
Design Water Flow Rate
Fan:ComponentModel
Maximum Flow Rate
Minimum Flow Rate
Motor Fan Pulley Ratio
Belt Maximum Torque
Maximum Motor Output Power
Maximum VFD Output Power
Fan:ConstantVolume
Maximum Flow Rate
Fan:OnOff
Maximum Flow Rate
FanPerformance:NightVentilation
Maximum Flow Rate
Fan:VariableVolume
Maximum Flow Rate
FluidCooler:SingleSpeed
Design Air Flow Rate U-factor Times Area Value
Design Water Flow Rate
Design Air Flow Rate
Design Air Flow Rate Fan Power
FluidCooler:TwoSpeed
High Fan Speed U-factor Times Area Value
Design Water Flow Rate
High Fan Speed Air Flow Rate
High Fan Speed Fan Power
HeaderedPumps:ConstantSpeed
Total Rated Flow Rate
Rated Power Consumption
HeaderedPumps:VariableSpeed
Total Rated Flow Rate
Rated Power Consumption
HeatExchanger:AirToAir:SensibleAndLatent
710 CHAPTER 1. INPUT-OUTPUT REFERENCE
HVACTemplate:Zone:WaterToAirHeatPump
Cooling Supply Air Flow Rate
Heating Supply Air Flow Rate
No Load Supply Air Flow Rate
Cooling Coil Gross Rated Total Capacity
Cooling Coil Gross Rated Sensible Heat Ratio
Heat Pump Heating Coil Gross Rated Capacity
Supplemental Heating Coil Capacity
Baseboard Heating Capacity
PlantComponent:TemperatureSource
Design Volume Flow Rate
PlantEquipmentOperation:ComponentSetpoint
Component 1 Flow Rate
Component 2 Flow Rate
Component 3 Flow Rate
Component 4 Flow Rate
Component 5 Flow Rate
Component 6 Flow Rate
Component 7 Flow Rate
Component 8 Flow Rate
Component 9 Flow Rate
Component 10 Flow Rate
PlantLoop
Maximum Loop Flow Rate
Pump:ConstantSpeed
Rated Flow Rate
Rated Power Consumption
Pump:VariableSpeed
Rated Flow Rate
Rated Power Consumption
Pump:VariableSpeed:Condensate
Rated Flow Rate
Rated Power Consumption
Sizing:System
Design Outdoor Air Flow Rate
SolarCollector:FlatPlate:PhotovoltaicThermal
Design Flow Rate
1.18. GROUP – DESIGN OBJECTS 715
ThermalStorage:ChilledWater:Mixed
Use Side Design Flow Rate
Source Side Design Flow Rate
ThermalStorage:ChilledWater:Stratified
Use Side Design Flow Rate
Source Side Design Flow Rate
UnitarySystemPerformance:HeatPump:Multispeed
Heating Speed 1 Supply Air Flow Ratio
Cooling Speed 1 Supply Air Flow Ratio
Heating Speed 2 Supply Air Flow Ratio
Cooling Speed 2 Supply Air Flow Ratio
Heating Speed 3 Supply Air Flow Ratio
Cooling Speed 3 Supply Air Flow Ratio
Heating Speed 4 Supply Air Flow Ratio
Cooling Speed 4 Supply Air Flow Ratio
WaterHeater:Mixed
Tank Volume
Heater Maximum Capacity
Use Side Design Flow Rate
Source Side Design Flow Rate
WaterHeater:Stratified
Tank Volume
Tank Height
Heater 1 Capacity
Use Side Design Flow Rate
Source Side Design Flow Rate
ZoneHVAC:Baseboard:Convective:Electric
Nominal Capacity
ZoneHVAC:Baseboard:Convective:Water
U-Factor Times Area Value
Maximum Water Flow Rate
ZoneHVAC:Baseboard:RadiantConvective:Electric
Nominal Capacity
ZoneHVAC:Baseboard:RadiantConvective:Steam
Maximum Steam Flow Rate
ZoneHVAC:Baseboard:RadiantConvective:Water
Rated Capacity
716 CHAPTER 1. INPUT-OUTPUT REFERENCE
There are 3 places in the input where the user can impose sizing factors.
1. In Sizing Parameters (object: Sizing:Parameters), the user can specify an over-all sizing factor.
This factor is applied to all the zone design loads and air flow rates resulting from the zone sizing
calculations.
2. In Zone Sizing (object: Sizing:Zone), the user can specify a sizing factor for a specific zone.
The factor is applied to the calculated zone design loads and air flow rates for the zone named in
the Sizing:Zone object. This sizing factor overrides the global sizing factor. That is, a zone sizing
factor, if specified, replaces the global sizing factor for the named zone.
3. For some plant components (basically all central chillers, boilers and cooling towers) the user
can specify a sizing factor that modifies the autosized component capacity and flow rates. These
factors are applied after the application of global or zone sizing factors. They are primarily used to
split the design load between multiple components. These sizing factors can change the autosizing
of the associated loops and pumps. The following rules are followed the effect of plant component
sizing factors on loops and pumps.
a. For supply side branches, the sizing factors of all components in series on the branch are summed
and the result becomes the branch sizing factor. If there is a branch pump its autosized design flow
rate is multiplied by the branch sizing factor.
b. For each loop, if the average of the branch sizing factors is less than 1, the loop sizing factor is
set equal to the sum of the branch sizing factors. If the average is greater than 1, the loop sizing
factor is set equal to the maximum of the branch sizing factors. The loop sizing factor is applied to
the loop design flow rate (if autosized) and to the loop pump flow rate (if autosized).
Mixed user-specified and autosized inputs can be successfully used if the following points and sug-
gestions are followed.
1. Each component is autosized independently. Thus user input for a flow rate in one component will
have no effect on other components’ autosized flow rates. For instance, specifying the chilled water
loop pump’s rated flow rate will have no effect on the autosizing of the chiller’s design evaporator
flow rate or on the plant loop’s autosized maximum loop flow rate.
2. Within a component it is best to autosize all inputs and enter specified values for all inputs.
For example, in a chiller, if only the nominal capacity is user-specified, the autosized chilled water
flow rate may not be consistent with the specified capacity.
3. Sizing information flows only from the sizing objects to the components. The sizing calculations
have no knowledge of user-specified values in a component. The only exception to this rule is that
plant loop sizing will collect all component design water flow rates whether autosized or user-specified.
4. If the user wants to specify a zone or system air flow rate it should be done using the Sizing:Zone
and Sizing:System objects rather than done in the individual components.
5. The plant loop flow rates are sized from the total design demand of the components connected
to each loop. The components demanding water need not be autosized for the plant loop autosizing
to work successfully. So the user could specify all the air side components and autosize all the plant
loops and plant components. Or specify the chilled water loop flow rate, chilled water pump inputs
and chiller inputs and let the condenser loop and tower autosize.
1.18. GROUP – DESIGN OBJECTS 719
The results of the component autosizing calculations are reported on the eplusout.eio file. For each
component field that has been autosized the object type, object name, field description with unit,
and value are printed out as comma separated data on a line beginning with Component Sizing.
Examples of this are shown in the Output Details and Examples document.
The complete list of objects that have autosized fields is shown in the following table. Note that
spaces may be inserted in object names to facilitate readability.
AirConditioner:VariableRefrigerantFlow AirLoopHVAC
AirLoopHVAC:Unitary:Furnace:HeatCool AirLoopHVAC:Unitary:Furnace:HeatOnly
AirLoopHVAC:UnitaryHeatCool AirLoopHVAC:UnitaryHeatCool:VAVChangeoverBypass
AirLoopHVAC:UnitaryHeatOnly AirLoopHVAC:UnitaryHeatPump:AirToAir
AirLoopHVAC:UnitaryHeatPump:AirToAir:MultiSpeed
AirLoopHVAC:UnitaryHeatPump:WaterToAir
AirLoopHVAC:UnitarySystem AirTerminal:DualDuct:ConstantVolume
AirTerminal:DualDuct:VAV AirTerminal:DualDuct:VAV:OutdoorAir
AirTerminal:SingleDuct:ConstantVolume:CooledBeam
AirTerminal:SingleDuct:ConstantVolume:FourPipeInduction
AirTerminal:SingleDuct:ConstantVolume:ReheatAirTerminal:SingleDuct:ParallelPIU:Reheat
AirTerminal:SingleDuct:SeriesPIU:Reheat AirTerminal:SingleDuct:ConstantVolume:NoReheat
AirTerminal:SingleDuct:VAV:HeatAndCool:NoReheat
AirTerminal:SingleDuct:VAV:HeatAndCool:Reheat
AirTerminal:SingleDuct:VAV:NoReheat AirTerminal:SingleDuct:VAV:Reheat
AirTerminal:SingleDuct:VAV:Reheat:VariableSpeedFan
Boiler:HotWater
Boiler:Steam Branch
Chiller:Absorption Chiller:Absorption:Indirect
Chiller:CombustionTurbine Chiller:ConstantCOP
Chiller:Electric Chiller:Electric:EIR
Chiller:Electric:ReformulatedEIR Chiller:EngineDriven
ChillerHeater:Absorption:DirectFired ChillerHeater:Absorption:DoubleEffect
ChillerHeaterPerformance:Electric:EIR Coil:Cooling:DX:MultiSpeed
Coil:Cooling:DX:SingleSpeed Coil:Cooling:DX:SingleSpeed:ThermalStorage
Coil:Cooling:DX:TwoSpeed Coil:Cooling:DX:VariableRefrigerantFlow
Coil:Cooling:DX:VariableSpeed Coil:Cooling:Water
Coil:Cooling:Water:DetailedGeometry Coil:Cooling:WaterToAirHeatPump:EquationFit
Coil:Cooling:WaterToAirHeatPump:VariableSpeedEquationFit
Coil:Heating:DX:MultiSpeed
Coil:Heating:DX:SingleSpeed Coil:Heating:DX:VariableRefrigerantFlow
Coil:Heating:DX:VariableSpeed Coil:Heating:Electric
Coil:Heating:Electric:MultiStage Coil:Heating:Fuel
Coil:Heating:Gas:MultiStage Coil:Heating:Steam
Coil:Heating:Water Coil:Heating:WaterToAirHeatPump:EquationFit
720 CHAPTER 1. INPUT-OUTPUT REFERENCE
Coil:Heating:WaterToAirHeatPump:VariableSpeedEquationFit
CoilPerformance:DX:Cooling
CondenserLoop Controller:OutdoorAir
Controller:WaterCoil CoolingTower:SingleSpeed
CoolingTower:TwoSpeed CoolingTower:VariableSpeed
CoolingTower:VariableSpeed:Merkel EvaporativeCooler:Indirect:ResearchSpecial
EvaporativeFluidCooler:SingleSpeed EvaporativeFluidCooler:TwoSpeed
Fan:ComponentModel Fan:ConstantVolume
Fan:OnOff FanPerformance:NightVentilation
Fan:VariableVolume FluidCooler:SingleSpeed
FluidCooler:TwoSpeed HeaderedPumps:ConstantSpeed
HeaderedPumps:VariableSpeed HeatExchanger:AirToAir:SensibleAndLatent
HeatExchanger:FluidToFluid Humidifier:Steam:Electric
HVACTemplate:Plant:Boiler HVACTemplate:Plant:Chiller
HVACTemplate:Plant:Tower HVACTemplate:System:ConstantVolume
HVACTemplate:System:DedicatedOutdoorAir HVACTemplate:System:DualDuct
HVACTemplate:System:PackagedVAV HVACTemplate:System:Unitary
HVACTemplate:System:UnitaryHeatPump:AirToAir HVACTemplate:System:UnitarySystem
HVACTemplate:System:VAV HVACTemplate:System:VRF
HVACTemplate:Zone:BaseboardHeat HVACTemplate:Zone:ConstantVolume
HVACTemplate:Zone:DualDuct HVACTemplate:Zone:FanCoil
HVACTemplate:Zone:IdealLoadsAirSystem HVACTemplate:Zone:PTAC
HVACTemplate:Zone:PTHP HVACTemplate:Zone:Unitary
HVACTemplate:Zone:VAV HVACTemplate:Zone:VAV:FanPowered
HVACTemplate:Zone:VAV:HeatAndCool HVACTemplate:Zone:VRF
HVACTemplate:Zone:WaterToAirHeatPump PlantComponent:TemperatureSource
PlantEquipmentOperation:ComponentSetpoint PlantLoop
Pump:ConstantSpeed Pump:VariableSpeed
Pump:VariableSpeed:Condensate Sizing:System
SolarCollector:FlatPlate:PhotovoltaicThermal ThermalStorage:ChilledWater:Mixed
ThermalStorage:ChilledWater:Stratified UnitarySystemPerformance:HeatPump:Multispeed
WaterHeater:Mixed WaterHeater:Stratified
ZoneHVAC:Baseboard:Convective:Electric ZoneHVAC:Baseboard:Convective:Water
ZoneHVAC:Baseboard:RadiantConvective:ElectricZoneHVAC:Baseboard:RadiantConvective:Steam
ZoneHVAC:Baseboard:RadiantConvective:WaterZoneHVAC:EnergyRecoveryVentilator
ZoneHVAC:EvaporativeCoolerUnit ZoneHVAC:FourPipeFanCoil
ZoneHVAC:HighTemperatureRadiant ZoneHVAC:IdealLoadsAirSystem
ZoneHVAC:LowTemperatureRadiant:Electric ZoneHVAC:LowTemperatureRadiant:VariableFlow
1.18. GROUP – DESIGN OBJECTS 721
ZoneHVAC:OutdoorAirUnit ZoneHVAC:PackagedTerminalAirConditioner
ZoneHVAC:PackagedTerminalHeatPump ZoneHVAC:TerminalUnit:VariableRefrigerantFlow
ZoneHVAC:UnitHeater ZoneHVAC:UnitVentilator
ZoneHVAC:VentilatedSlab ZoneHVAC:WaterToAirHeatPump
ZoneHVAC:WindowAirConditioner
In EnergyPlus the autosizing calculations start with a calculation of the zone design air flow rates
using zone by zone design day simulations. The resulting zone design air flow rates and daily air flow
sequences are used in the subsequent HVAC and central plant air and fluid flow design calculations
and in the component autosizing calculations. The user can override or change the calculated zone
design air flow rates in several ways.
1) The user can enter a value for Sizing Factor in the Sizing:Parameters object (see description
below).
2) The user can specify a zone level Zone Sizing Factor in each Sizing:Zone object.
3) For each zone the user can input a Cooling Design Air Flow Rate and/or a Heating Design
Air Flow Rate (and specify Cooling Design Air Flow Method = Flow/Zone and Heating Design Air
Flow Method = Flow/Zone). These user inputs override the calculated values. The program divides
the user input cooling or heating design air flow rate by the calculated values and uses the result as
a zone sizing factor to multiply all the elements in the design heating and cooling air flow and load
sequences. From this point the design calculations proceed as usual.
Using the results of the zone design air flow rate calculation (including any user input or altered flow
rates) EnergyPlus proceeds to calculate central air system flow rates and cooling and heating loads.
The results of this calculation can be overridden in the following way.
For each system (AirLoopHVAC), in the corresponding Sizing:System object, specify Cooling Design
Air Flow Method to be Flow/System and input a value for Cooling Design Air Flow Rate. Similarly
for heating specify Heating Design Air Flow Method to be Flow/System and input a value for Heating
Design Air Flow Rate.
1.18.2 DesignSpecification:OutdoorAir
This object allows for the outdoor air requirements to be defined in a common location for use by
other objects. This object may be referenced by name from other objects (e.g., VAV terminal units,
AirTerminal:SingleDuct:ConstantVolume:NoReheat, and AirTerminal:SingleDuct:Mixer) as required
to identify an outdoor air quantity for use by that object. Note that a zone name Is not included
as an input to this zone outdoor air definition and the number of people in a zone, zone floor area,
and zone volume can only be determined after this object has been referenced by another. A single
722 CHAPTER 1. INPUT-OUTPUT REFERENCE
zone outdoor air definition may be referenced by multiple objects to specify that the same outdoor
air requirements are used by those objects or multiple zone outdoor air objects may be defined and
referenced by other objects as needed. If multiple zone outdoor air definitions are used, each outdoor
air definition must have a unique name.
1.18.2.1 Inputs
– Flow/Person means the program will use the input from the field Outdoor Air Flow per Person
and the actual zone occupancy to calculate a zone outdoor air flow rate. The density of air is
measured at IUPAC standard temperature and pressure.
– Flow/Area means that the program will use the input from the field Outdoor Air Flow per
Zone Floor Area and the actual zone floor area as the zone outdoor air flow rate. The density
of air is measured at IUPAC standard temperature and pressure.
– Flow/Zone means that the program will use the input of the field Outdoor Air Flow per Zone as
the zone outdoor air flow rate. The density of air is measured at IUPAC standard temperature
and pressure.
– AirChanges/Hour means that the program will use the input from the field Air Changes per
Hour and the actual zone volume (divided by 3600 seconds per hour) as the zone outdoor air
flow rate.
– Sum means that the flows calculated from the fields Outdoor Air Flow per Person, Outdoor Air
Flow per Area, Outdoor Air Flow per Zone, and Air Changes per Hour (using the associated
conversions to m3 /s for each field) will be added to obtain the zone outdoor air flow rate.
– Maximum means that the maximum flow derived from Outdoor Air Flow per Person, Outdoor
Air Flow per Area, Outdoor Air Flow per Zone, and Air Changes per Hour (using the associated
conversions to m3 /s for each field) will be used as the zone outdoor air flow rate.
– IndoorAirQualityProcedure means that the program will use the other procedure defined in
ASHRAE Standard 62.1-2007 to calculate the amount of outdoor air necessary in order to
maintain the levels of indoor air carbon dioxide at or below the setpoint defined in the ZoneCon-
trol:ContaminantController object. Appendix A of the ASHRAE 62.1-2010 user′ s manual dis-
cusses another method for implementing CO2-based DCV in a single zone system. The last
two methods of Proportional Control calculate the required outdoor air flow rate which varies
in proportion to the percentage of the CO2 signal range and has two choices to calculate
occupancy-based outdoor air rate.
– ProportionalControlBasedOnOccupancySchedule uses the real occupancy at the current time
step to calculate outdoor air rate.
– ProportionalControlBasedOnDesignOccupancy uses the design occupancy level to calculate out-
door air rate. The former choice is a good approach to estimate outdoor air rate. However,
for practical applications, the zone controller usually does not have the real time occupancy
1.18. GROUP – DESIGN OBJECTS 723
information, and the design occupancy level is assumed. The latter choice is used in the design
stage.
1.18.2.1.8 Field: Proportional Control Minimum Outdoor Air Flow Rate Sched-
ule Name
This field is the name of schedule that defines how minimum outdoor air requirements change
over time. The field is optional. If left blank, the schedule defaults to 1.0. If used when
724 CHAPTER 1. INPUT-OUTPUT REFERENCE
DesignSpecification :OutdoorAir
ZoneOAData , !- Name
Sum , !- Outdoor Air Method
0.00944 , !- Outdoor Air Flow per Person {m3/s}
0.00305 , !- Outdoor Air Flow per Zone Floor Area {m3/s-m2}
, !- Outdoor Air Flow per Zone {m3/s}
, !- Outdoor Air Flow Air Changes per Hour
OARequirements Sched; !- Outdoor Air Schedule Name
Schedule:Compact ,
OARequirements Sched , !- Name
Any Number , !- Schedule Type Limits Name
Through: 12/31 , !- Field 1
For: Weekdays SummerDesignDay WinterDesignDay , !- Field 2
Until: 24:00 , 1.0, !- Field 4
For: AllOtherDays , !- Field 5
Until: 24:00 , 0.5; !- Field 7
1.18.3 DesignSpecification:OutdoorAir:SpaceList
This object creates a composite outdoor air specification for a list of Spaces (ref Space). The indi-
vidual DesignSpecification:OutdoorAir objects in the list are evaluated during sizing and operation
at the respective Space floor area, volume, and/or occupancy and summed for a total outdoor air
requirement.
1.18.3.1 Inputs
1.18.3.1.3 Field: Space <#> Design Specification Outdoor Air Object Name
Reference to a DesignSpecification:OutdoorAir object.
An IDF example:
DesignSpecification :OutdoorAir:SpaceList ,
SZ DSOA Zone 5 List , !- Name
Space 5 Office , !- Space 1 Name
SZ DSOA Zone 5 Office , !- Space 1 Design Specification Outdoor Air Object Name
Space 5 Conference , !- Space 2 Name
SZ DSOA Zone 5 Conference; !- Space 2 Design Specification Outdoor Air Object Name
1.18. GROUP – DESIGN OBJECTS 725
1.18.4 DesignSpecification:ZoneAirDistribution
This object is used to describe the air distribution effectiveness and fraction of secondary recirculation
air (return air not directly mixed with outdoor air) of a zone. It is referenced by the Sizing:Zone
and Controller:MechanicalVentilation objects.
1.18.4.1 Inputs
Figure 1.87: Zone Air Distribution Effectiveness (Source: ASHRAE Standard 62.1-2010)
1.18. GROUP – DESIGN OBJECTS 727
DesignSpecification :ZoneAirDistribution ,
CM DSZAD ZN_1_FLR_1_SEC_1 , !- Name
1, !- Zone Air Distribution Effectiveness in Cooling Mode {
dimensionless}
1, !- Zone Air Distribution Effectiveness in Heating Mode {
dimensionless}
; !- Zone Air Distribution Effectiveness Schedule Name
1.18.5 Sizing:Parameters
This object allows the user to specify global heating and cooling sizing ratios. These ratios will be
applied at the zone level to all of the zone heating and cooling loads and air flow rates. These new
loads and air flow rates are then used to calculate the system level flow rates and capacities and are
used in all component sizing calculations.
The user can also specify the width (in load timesteps) of a moving average window which can be
used to smooth the calculated zone design flow sequences. The use of this parameter is described
below.
1.18.5.1 Inputs
the effect of thermostat setup and setback and prevent the warm up or cool down flow rates from
dominating the design flow rate calculation. Specifying the width of the averaging window allows
the user to do this.
For example, if the load calculation timestep is 15 minutes and the user specifies the Timesteps in
Averaging Window to be 4, the zone design air flows will be averaged over a time period of 1 hour.
Specifying 8 would result in averaging over a 2 hour period.
1.18.5.2 Outputs
The sizing factors and the averaging window size are reported out on the eplusout.eio file. An
example is:
! <Load Timesteps in Zone Design Calculation Averaging Window >, Value
Timesteps in Averaging Window , 1
! <Heating Sizing Factor Information >, Sizing Factor ID , Value
Heating Sizing Factor , Global , 1.3000
Heating Sizing Factor , Zone SPACE1 -1, 1.3000
Heating Sizing Factor , Zone SPACE2 -1, 1.3000
Heating Sizing Factor , Zone SPACE3 -1, 1.3000
Heating Sizing Factor , Zone SPACE4 -1, 1.3000
Heating Sizing Factor , Zone SPACE5 -1, 1.3000
! <Cooling Sizing Factor Information >, Sizing Factor ID , Value
Cooling Sizing Factor , Global , 1.3000
Cooling Sizing Factor , Zone SPACE1 -1, 1.3000
Cooling Sizing Factor , Zone SPACE2 -1, 1.3000
Cooling Sizing Factor , Zone SPACE3 -1, 1.3000
Cooling Sizing Factor , Zone SPACE4 -1, 1.3000
Cooling Sizing Factor , Zone SPACE5 -1, 1.3000
1.18.6 OutputControl:Sizing:Style
As described early in the document (see: EnergyPlus Output Processing), the user may select the
“style” for the sizing result files (epluszsz.<ext>, eplusssz.<ext>). This object applies to all sizing
output files.
OutputControl:Sizing:Style ,
\memo default style for the Sizing output files is comma -- this works well for
\memo importing into spreadsheet programs such as Excel(tm) but not so well for word
\memo processing progams -- there tab may be a better choice. fixed puts spaces between
\memo the "columns"
\unique -object
A1; \field Column Separator
\required -field
\type choice
\key Comma
\key Tab
\key Fixed
1.18.6.1 Inputs
Note that both tab and comma separated files easily import into ExcelTM or other spreadsheet
programs. The tab delimited files can also be viewed by text editors, word processing programs and
easily converted to “tables” within those programs.
1.18.7 Sizing:Zone
The Sizing:Zone object provides the data needed to perform a zone design air flow calculation for
a single zone. This calculation assumes a variable amount of supply air at a fixed temperature and
humidity. The information needed consists of the zone inlet supply air conditions: temperature and
humidity ratio for heating and cooling. The calculation is done for every design day included in the
input. The maximum cooling load and air flow and the maximum heating load and air flow are then
saved for the system level design calculations and for the component automatic sizing calculations.
The Sizing:Zone object is also the place where the user can specify the design outdoor air flow
rate by referencing the name of a design specification outdoor air object. This can be specified in
a number of ways (ref. DesignSpecification:OutdoorAir).This data is saved for use in the system
sizing calculation or for sizing zone components that use outdoor air.
The user can also place limits on the heating and design cooling air flow rates. See Heating Design
Air Flow Method and Cooling Design Air Flow Method below and the explanations of the various
heating and cooling flow input fields.
The user can ask the zone design calculation to take into account the effect of a Dedicated Outdoor
Air System on the zone design loads and airflow rates. The design calculation will calculate the heat
addition rate to the zone of an idealized SOA system and add or subtract the result from the total
zone loads and flow rates.
1.18.7.1 Inputs
1.18.7.1.2 Field: Zone Cooling Design Supply Air Temperature Input Method
The input must be either SupplyAirTemperature or TemperatureDifference. SupplyAirTemperature
means that the user inputs from the fields of Zone Cooling Design Supply Air Temperature will be
used to determine the zone cooling design air flow rates. TemperatureDifference means that the user
inputs from the fields of Zone Cooling Design Supply Air Temperature Difference will be used to
determine the zone cooling design air flow rates.
1.18.7.1.5 Field: Zone Heating Design Supply Air Temperature Input Method
The input must be either SupplyAirTemperature or TemperatureDifference. SupplyAirTemperature
means that the user inputs from the fields of Zone Heating Design Supply Air Temperature will be
used to determine the zone heating design air flow rates. TemperatureDifference means that the user
inputs from the fields of Zone Heating Design Supply Air Temperature Difference will be used to
determine the zone heating design air flow rates.
1.18.7.1.15 Field: Cooling Minimum Air Flow per Zone Floor Area
The minimum zone cooling volumetric flow rate per square meter (units are m3 /s-m2 ). This field is
used when Cooling Design Air Flow Method is specified as DesignDayWithLimit. In this case it sets
a lower bound on the zone design cooling air flow rate. In all cases the maximum flow derived from
Cooling Minimum Air Flow per Zone Floor Area, Cooling Minimum Air Flow, Cooling Minimum
Air Flow Fraction and the design outdoor air flow rate (including VRP adjustments) is used to set a
minimum supply air flow rate for the zone for VAV systems. The default is 0.000762, corresponding
to 0.15 cfm/ft2 . The applicable sizing factor is not applied to this value.
732 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.18.7.1.20 Field: Heating Maximum Air Flow per Zone Floor Area
The maximum zone heating volumetric flow rate per square meter (units are m3 /s-m2 ). This field is
used when Heating Design Air Flow Method is specified as DesignDayWithLimit. In this case it sets
an upper bound on the zone design heating air flow rate. For this and the next two input fields, the
maximum flow derived from Heating Maximum Air Flow per Zone Floor Area, Heating Maximum
Air Flow, and Heating Maximum Air Flow Fraction is used to set a maximum heating supply air
flow rate for the zone for VAV systems. The default is 0.002032, corresponding to 0.40 cfm/ft2 . If
the maximum heating design flow rate calculated using these input fields is greater than the design
heating flow rate calculated during sizing, these input fields have no impact on sizing. It may be
more appropriate to select only one of these three fields to calculate the maximum heating design
flow rate (i.e., if one or more of these three fields is 0, it will not be used in calculating the maximum
heating design flow rate).
1.18. GROUP – DESIGN OBJECTS 733
NeutralDehumidifiedSupplyAir means that the ventilation air will be cooled and dehumidified and
then reheated to a neutral temperature. The ventilation air is cooled to the lower setpoint tempera-
ture (if necessary) and reheated to the upper setpoint temperature. A good choice for the setpoints
would be 14.4 and 22.2 degrees C.
ColdSupplyAir means that the ventilation air will be used to supply cooling to the zone. Cold outside
air is heated to the upper setpoint; warm outside air is cooled to the lower setpoint. A good choice
for the setpoints would be 12.2 and 14.4 degrees C.
1.18.7.1.26 Field: Dedicated Outdoor Air Low Temperature Setpoint for Design
The lower setpoint temperature to be used with the DOAS design control strategy. The units are
degrees C. The default is autosized to the values given above for the three design control strategies.
1.18.7.1.27 Field: Dedicated Outdoor Air High Temperature Setpoint for Design
The higher setpoint temperature to be used with the DOAS design control strategy. The units are
degrees C. The default is autosized to the values given above for the three design control strategies.
An IDF example:
Sizing:Zone ,
SPACE5 -1, !- Name of a zone
14., !- Zone cooling design supply air temperature {C}
50., !- Zone heating design supply air temperature {C}
0.009 , !- Zone cooling design supply air humidity ratio {kg -H2O/kg -air}
0.004 , !- Zone heating design supply air humidity ratio {kg -H2O/kg -air}
DSOA1 , !- Design Specification Outdoor Air Object Name
0.0, !- zone heating sizing factor
0.0, !- zone cooling sizing factor
designdaywithlimit , !- Cooling Design Air Flow Method
, !- cooling design air flow rate {m3/s}
, !- Cooling Minimum Air Flow per zone area {m3/s-m2}
, !- Cooling Minimum Air Flow {m3/s}
, !- fraction of the cooling design air flow rate
designday , !- Heating Design Air Flow Method
, !- heating design air flow rate {m3/s}
, !- heating max air flow per zone area {m3/s-m2}
, !- heating max air flow {m3/s}
, !- fraction of the cooling design air flow rate
DSZADO1 , !- Design Specification Zone Air Distribution Object Name
Yes , !- Account for Dedicated Outside Air System
ColdSupplyAir , !- Dedicated Outside Air System Control Strategy
12.2, !- Dedicated Outside Air Low Setpoint for Design
14.4; !- Dedicated Outside Air High Setpoint for Design
DesignSpecification :OutdoorAir ,
DSOA1 , !- Name
SUM , !- Outdoor Air Method
0.00236 , !- Outdoor Air Flow per Person
0.000305 , !- Outdoor Air Flow per Zone Floor Area
0.0, !- Outdoor Air Flow per Zone
0.0, !- Outdoor Air Flow Air Changes per Hour
; !- Outdoor Air Flow Rate Fraction Schedule Name
DesignSpecification :ZoneAirDistribution ,
DSZADO1 , !- Name
1.0, !- Zone Air Distribution Effectiveness in Cooling Mode
1.0, !- Zone Air Distribution Effectiveness in Heating Mode
, !- Zone Air Distribution Effectiveness Schedule Name
0.3; !- Zone Secondary Recirculation Fraction
1.18. GROUP – DESIGN OBJECTS 735
1.18.7.2 Outputs
The zone design air flow rates and loads are output onto the local file “epluszsz.<ext>” where <ext>
is the extension from the sizing style object (default is csv – a comma separated file epluszsz.csv).
The columns are clearly labeled. It will easily import into Excel or other spreadsheet program that
accepts delimited files. All of these values are design air flow rates and loads calculated by the
program. No sizing factors have been applied.
The calculated zone design air flow rates and the user input or altered zone design air flow rates are
also reported on the eplusout.eio file. The values are printed out for each zone as comma separated
records beginning with Zone Sizing. Items output on the eio file are: zone name, load type (heating
or cooling), design load, calculated design air flow rate, user design air flow rate, design day name,
time of peak, outside temperature at peak, outside humidity ratio at peak.
1.18.8 DesignSpecification:ZoneHVAC:Sizing
This object is used to describe general sizing and scalable sizing methods which are referenced by
zone HVAC equipment objects. It is optional input field in zone HVAC objects. If a name of this
optional input is not specified or is blank then the sizing method or input specified in the parent
object is used. If the name of this object is entered, then the values or method specified overrides
the sizing method in the parent zone HVAC objects. This object is meant to provide scalable sizing
method to users. The name of this object is an optional input field in the zoneHVAC objects. When
this name in not specified in the zone HVAC object the sizing method or the value specified in the
zone HVAC object will be used.
List of zoneHVAC objects than can reference this object include:
– ZoneHVAC:TerminalUnit:VariableRefrigerantFlow
– ZoneHVAC:PackagedTerminalAirConditioner
– ZoneHVAC:PackagedTerminalHeatPump
– ZoneHVAC:WaterToAirHeatPump
– ZoneHVAC:WindowAirConditioner
– ZoneHVAC:UnitHeater
– ZoneHVAC:UnitVentilator
– ZoneHVAC:FourPipeFanCoil
– ZoneHVAC:VentilatedSlab
– ZoneHVAC:EvaporativeCoolerUnit
– ZoneHVAC:IdealLoadsAirSystem
The sizing methods input fields available in this objects are for supply air flow and capacity for
heating and cooling operating modes. Some zone HVAC equipment has single supply air flow rate
input field that serves both cooling and heating operating modes. So entering either of the cool-
ing or heating scalable sizing input field is sufficient. When there are separate input fields for
cooling, heating, no-cooling, and no-heating operating modes, the corresponding input fields are
specified. The child components supply air flow rate are also sized using scalable sizing methods
specified in the parent objects. The methods allow users to enter a fixed or hard sized values,
autosizable, or scalable sizing methods. Methods allowed for sizing supply air flow rates include:
736 CHAPTER 1. INPUT-OUTPUT REFERENCE
– SupplyAirFlowRate: entered when it is intended that the user specified either hard value
or the simulation engine autosize the supply air flow rates for cooling, heating, and no-cooling
or no-heating operating modes.
– FlowPerFloorArea: entered when it is intended that the simulation engine determine the
supply air flow rates from the user specified supply air flow rates per unit floor area and the
zone floor area of the zone served by the zone HVAC equipment.
– FractionOfAutosizedCoolingAirflow: entered when it is intended that the simulation en-
gine determines the supply air flow rates from the user specified flow fraction and autosized
cooling design supply air flow rate.
– FractionOfAutosizedHeatingAirflow: entered when it is intended that the simulation en-
gine determines the supply air flow rates from the user specified flow fraction and autosized
heating design supply air flow rate.
– FlowPerCoolingCapacity: entered when it is intended t that he simulation engine deter-
mines the supply air flow rates from the user specified supply air flow per cooling capacity value
and autosized cooling design capacity.
– FlowPerHeatingCapacity: entered when it is intended that the simulation engine deter-
mines the supply air flow rates from the user specified supply air flow per heating capacity
value and autosized heating design capacity.
The Design Specification ZoneHVAC Sizing object also has input fields for sizing or scalable siz-
ing of cooling and heating capacity. However, most of the parent zone HVAC objects do not have
input fields for sizing capacities. So, the capacity scalable sizing fields in the parent objects are
used for sizing child components capacity sizings. The scalable capacity sizing may be indirectly
impacted by the scalable supply air flow rates sizing values. Moreover, the autosized cold water,
hot water and steam flow rates in the parent zone HVAC objects (e.g. FanCoils, UnitHeaters,
UnitVentilators, and VentilatedSlabs) and capacity in child components are determined using the
scalable sizing methods. Sizing methods allowed for cooling and heating capacity include: CoolingDe-
signCapacity, HeatingDesignCapacity, CapacityPerFloorArea, FractionOfAutosizedCoolingCapacity,
FractionOfAutosizedHeatingCapacity.
– CoolingDesignCapacity: entered when it is intended that user specifies either a hard sized
cooling capacity value or the simulation engine autosizes cooling capacity value for the cooling
design capacity.
– HeatingDesignCapacity: entered when it is intended that user specifies either a hard sized
heating capacity value or the simulation engine autosized heating capacity value for the heating
design capacity.
– CapacityPerFloorArea: is entered when it is intended that the simulation engine determines
the cooling or heating capacity from user specified capacity per floor area value and the floor
area of the zone served by the zone HVAC equipment.
– FractionOfAutosizedCoolingCapacity: entered when it is intended that the simulation
engine sizes the cooling capacity from the user specified capacity fraction and autosized cooling
design capacity value.
1.18. GROUP – DESIGN OBJECTS 737
Description of the input fields of the design specification zone HVAC sizing object “DesignSpecifica-
tion:ZoneHVAC:Sizing”:
1.18.8.1 Inputs
1.18.8.1.4 Field: Cooling Design Supply Air Flow Rate Per Floor Area {m3/s-
m2}
Enter the cooling supply air volume flow rate per zone conditioned floor area in m3/s-m2. This field
is required field when the Cooling Design air Flow Method is FlowPerFloorArea. This field may be
left blank if a cooling coil is not included in the zone HVAC equipment or the Cooling Design Air
Flow Method is not FlowPerFloorArea. The program calculates the cooling supply air volume flow
rate from the zone conditioned floor area served by the zone HVAC equipment and the flow per unit
area value specified by the user. Zone sizing object (Sizing:Zone) is not required.
738 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.18.8.1.5 Field: Fraction of Autosized Cooling Design Supply Air Flow Rate
Enter the cooling supply air volume flow rate as a fraction of the autosized cooling supply air flow
rate. This input field is required when the Cooling Design air Flow Method is FractionOfAutosized-
CoolingAirflow. This input field may be left blank if a cooling coil is not included in the zone HVAC
equipment or the Cooling Design air Flow Method is not FractionOfAutosizedCoolingAirflow. The
program calculates the cooling supply air volume flow rate from the design autosized cooling supply
air flow rate and user specified fraction. Zone sizing object (Sizing:Zone) is required.
1.18.8.1.6 Field: Cooling Design Supply Air Flow Rate Per Unit Cooling Capac-
ity {m3/s-W}
Enter the cooling supply air volume flow rate per unit cooling capacity in m3/s-W. This input field
is required when the Cooling Design air Flow Method is FlowPerCoolingCapacity. This field may
be left blank if a cooling coil is not included in the zone HVAC equipment or the Cooling Design air
Flow Method is not FlowPerCoolingCapacity. The program calculates the cooling supply air volume
flow rate from the design autosized cooling capacity and user specified flow per cooling capacity
value. Zone sizing object (Sizing:Zone) is required.
1.18.8.1.7 Field: Supply Air Flow Rate Method When No Cooling or Heating is
Required
Enter the method used to determine the supply air volume flow rate when No Cooling or Heating
is required. Inputs allowed are None, SupplyAirFlowRate, FlowPerFloorArea, FractionOfAutosized-
CoolingAirflow, and FractionOfAutosizedHeatingAirflow. None is used when a cooling or heating
coil is not included in the zone HVAC equipment or this field may be left blank. SupplyAirFlowRate
means user specifies the magnitude of supply air flow rate or the program calculates the design
supply air volume flow rate if autosize is specified. FlowPerFloorArea means the program calculates
the supply air volume flow rate from the zone floor area served by the zone HVAC unit and Flow Per
Floor Area value specified by user. FractionOfAutosizedCoolingAirflow means the program calculates
the supply air volume flow rate from user specified fraction and autosized design cooling supply air
volume flow rate value determined by the program. FractionOfAutosizedHeatingAirflow means the
program calculates the supply air volume flow rate from user specified fraction and autosized heating
supply air flow rate value determined by the program. The default method is SupplyAirFlowRate.
1.18.8.1.8 Field: Supply Air Flow Rate When No Cooling or Heating is Required
{m3/s}
Enter the magnitude of the supply air volume flow rate when no cooling or heating is required in
m3/s. This input is an alternative to using the program auto-calculated value. This input is a
required field when the Supply Air Flow Rate Method When No Cooling or Heating is Required is
SupplyAirFlowRate. This field may be left blank if a cooling coil is not included in the zone HVAC
equipment. This input field is also autosizable.
1.18.8.1.9 Field: Supply Air Flow Rate Per Floor Area When No Clg or Htg is
Required {m3/s-m2}
Enter the magnitude of supply air volume flow rate per zone floor area in m3/s-m2. This input
is a required field when Supply Air Flow Rate Method When No Cooling or Heating is Required
is FlowPerFloorArea. The program calculates the supply air flow rate when no cooling or heating
1.18. GROUP – DESIGN OBJECTS 739
is required from user specified flow per floor area and the zone area served by current zoneHVAC
equipment.
1.18.8.1.10 Field: Fraction of Design Cooling Supply Air Flow Rate When No
Clg or Htg Required
Enter the fraction of supply air volume flow rate as a fraction of the autosized cooling supply air
flow rate. This input field is required field when Supply Air Flow Rate Method When No Cooling or
Heating is Required is FractionOfAutosizedCoolingAirflow. The program calculates the supply air
flow rate when no cooling or heating is required from user specified fraction and the design cooling
autosized supply air flow rate.
1.18.8.1.11 Field: Fraction of Design Heating Supply Air Flow Rate When No
Clg or Htg Required
Enter the fraction of supply air volume flow rate as a fraction of the autosized cooling supply air
flow rate. This input field is required field when Supply Air Flow Rate Method When No Cooling or
Heating is Required is FractionOfAutosizedHeatingAirflow. The program calculates the supply air
flow rate when no cooling or heating is required from user specified fraction and the design heating
autosized supply air flow rate.
1.18.8.1.14 Field: Heating Design Supply Air Flow Rate Per Floor Area {m3/s-
m2}
Enter the heating supply air volume flow rate per zone conditioned floor area in m3/s-m2. This field
is required field when the Heating Design air Flow Method is FlowPerFloorArea. This field may be
left blank if a heating coil is not included in the zone HVAC equipment or the Heating Design Air
Flow Method is not FlowPerFloorArea. The program calculates the heating supply air volume flow
740 CHAPTER 1. INPUT-OUTPUT REFERENCE
rate from the zone conditioned floor area served by the zone HVAC equipment and the flow per unit
area value specified by the user.
1.18.8.1.15 Field: Fraction of Autosized Heating Design Supply Air Flow Rate
Enter the heating supply air volume flow rate as a fraction of the autosized heating supply air flow
rate. This input field is required when the Heating Design air Flow Method is FractionOfAutosized-
HeatingAirflow. This input field may be left blank if a heating coil is not included in the zone HVAC
equipment or the Heating Design air Flow Method is not FractionOfAutosizedHeatingAirflow. The
program calculates the heating supply air volume flow rate from the design autosized heating supply
air flow rate and user specified fraction.
1.18.8.1.16 Field: Heating Design Supply Air Flow Rate Per Unit Heating Ca-
pacity {m3/s-W}
Enter the heating supply air volume flow rate per unit heating capacity in m3/s-W. This input field
is required when the Heating Design air Flow Method is FlowPerHeatingCapacity. This field may
be left blank if a cooling coil is not included in the zone HVAC equipment or the Heating Design
air Flow Method is not FlowPerHeatingCapacity. The program calculates the heating supply air
volume flow rate from the design autosized heating capacity and user specified flow per unit heating
capacity value.
served by the zone HVAC equipment and the cooling capacity per unit floor area value specified by
the user.
DesignSpecification :ZoneHVAC:Sizing ,
VRFDesignSpec1 , !- Name
SupplyAirFlowRate , !- Cooling Design Air Flow Method
autosize , !- Cooling Design Supply Air Flow Rate
, !- Cooling Design Supply Air Flow Rate Per Floor Area
, !- Fraction of Autosized Cooling Design Supply Air Flow Rate
, !- Cooling Design Supply Air Flow Rate Per Unit of Capacity {m3/s-W}
SupplyAirFlowRate , !- Supply Air Flow Rate Method When No Cooling or Heating is
Required
autosize , !- Supply Air Flow Rate When No Cooling or Heating is Required
, !- Supply Air Flow Rate Per Floor Area When No Clg or Htg is
Required
, !- Fraction of Autosized Design Cooling Supply Air Flow Rate When No
Clg or Htg
, !- Fraction of Autosized Design Heating Supply Air Flow Rate When No
Clg or Htg
SupplyAirFlowRate , !- Heating Design Air Flow Method
autosize , !- Heating Design Supply Air Flow Rate
, !- Heating Design Supply Air Flow Rate Per Floor Area
, !- Fraction of Autosized Heating Design Supply Air Flow Rate
, !- Heating Design Supply Air Flow Rate Per Unit of Heating Capacity
CoolingDesignCapacity , !- Cooling Design Capacity Method
autosize , !- Cooling Design Capacity {W}
, !- Cooling Design Capacity Per Floor Area {W/m2}
, !- Fraction of Autosized Cooling Design Capacity {-}
HeatingDesignCapacity , !- Heating Design Capacity Method
autosize , !- Heating Design Capacity {W}
, !- Heating Design Capacity Per Floor Area {W/m2}
; !- Fraction of Autosized Cooling Design Capacity {-}
DesignSpecification :ZoneHVAC:Sizing ,
VRFDesignSpec2 , !- Name
FlowPerFloorArea , !- Cooling Design Air Flow Method
, !- Cooling Design Supply Air Flow Rate
3.6311418E-03, !- Cooling Design Supply Air Flow Rate Per Floor Area
, !- Fraction of Autosized Cooling Design Supply Air Flow Rate
, !- Cooling Design Supply Air Flow Rate Per Unit of Capacity {m3/s-W}
FlowPerFloorArea , !- Supply Air Flow Rate Method When No Cooling or Heating is
Required
, !- Supply Air Flow Rate When No Cooling or Heating is Required
3.6311418E-03, !- Supply Air Flow Rate Per Floor Area When No Clg or Htg is
Required
, !- Fraction of Autosized Design Cooling Supply Air Flow Rate When No
Clg or Htg
, !- Fraction of Autosized Design Heating Supply Air Flow Rate When No
Clg or Htg
FlowPerFloorArea , !- Heating Design Air Flow Method
, !- Heating Design Supply Air Flow Rate
3.6311418E-03, !- Heating Design Supply Air Flow Rate Per Floor Area
, !- Fraction of Autosized Heating Design Supply Air Flow Rate
, !- Heating Design Supply Air Flow Rate Per Unit of Heating Capacity
CoolingDesignCapacity , !- Cooling Design Capacity Method
autosize , !- Cooling Design Capacity {W}
, !- Cooling Design Capacity Per Floor Area {W/m2}
, !- Fraction of Autosized Cooling Design Capacity {-}
HeatingDesignCapacity , !- Heating Design Capacity Method
autosize , !- Heating Design Capacity {W}
, !- Heating Design Capacity Per Floor Area {W/m2}
; !- Fraction of Autosized Cooling Design Capacity {-}
DesignSpecification :ZoneHVAC:Sizing ,
VRFDesignSpec3 , !- Name
FractionOfAutosizedCoolingAirflow , !- Cooling Design Air Flow Method
, !- Cooling Design Supply Air Flow Rate
, !- Cooling Design Supply Air Flow Rate Per Floor Area
0.5, !- Fraction of Autosized Cooling Design Supply Air Flow Rate
, !- Cooling Design Supply Air Flow Rate Per Unit of Capacity {m3/s-W}
FractionOfAutosizedCoolingAirflow , !- Supply Air Flow Rate Method When No Cooling or Heating is
Required
1.18. GROUP – DESIGN OBJECTS 743
DesignSpecification :ZoneHVAC:Sizing ,
VRFDesignSpec4 , !- Name
FlowPerCoolingCapacity , !- Cooling Design Air Flow Method
, !- Cooling Design Supply Air Flow Rate
, !- Cooling Design Supply Air Flow Rate Per Floor Area
, !- Fraction of Autosized Cooling Design Supply Air Flow Rate
2.9541628E-05, !- Cooling Design Supply Air Flow Rate Per Unit of Capacity {m3/s-W}
FractionOfAutosizedHeatingAirflow , !- Supply Air Flow Rate Method When No Cooling or Heating is
Required
, !- Supply Air Flow Rate When No Cooling or Heating is Required
, !- Supply Air Flow Rate Per Floor Area When No Clg or Htg is
Required
, !- Fraction of Autosized Design Cooling Supply Air Flow Rate When No Clg
or Htg
0.413231177 , !- Fraction of Autosized Design Heating Supply Air Flow Rate When No Clg
or Htg
FlowPerHeatingCapacity , !- Heating Design Air Flow Method
, !- Heating Design Supply Air Flow Rate
, !- Heating Design Supply Air Flow Rate Per Floor Area
, !- Fraction of Autosized Heating Design Supply Air Flow Rate
2.9541628E-05, !- Heating Design Supply Air Flow Rate Per Unit of Heating Capacity
CoolingDesignCapacity , !- Cooling Design Capacity Method
autosize , !- Cooling Design Capacity {W}
, !- Cooling Design Capacity Per Floor Area {W/m2}
, !- Fraction of Autosized Cooling Design Capacity {-}
HeatingDesignCapacity , !- Heating Design Capacity Method
autosize , !- Heating Design Capacity {W}
, !- Heating Design Capacity Per Floor Area {W/m2}
; !- Fraction of Autosized Cooling Design Capacity {-}
1.18.9 DesignSpecification:AirTerminal:Sizing
This object modifies the sizing of an air loop terminal unit. It may be referenced by a Zone-
HVAC:AirDistributionUnit object. The values specified here are applied to the base sizing results
from the corresponding Sizing:Zone inputs. Any given DesignSpecification:AirTerminal:Sizing object
may be used by multiple terminal units with similar characteristics.
1.18.9.1 Inputs
Name of the design specification air terminal sizing object. This name may be referenced by a
ZoneHVAC:AirDistributionUnit object.
DesignSpecification :AirTerminal:Sizing ,
Recirculation System A Terminal Sizing , !- Name
0.6, !- Fraction of Design Cooling Load
0.8, !- Cooling Design Supply Air Temperature Difference Ratio
1.0, !- Fraction of Design Heating Load
1.0, !- Heating Design Supply Air Temperature Difference Ratio
0.0; !- Fraction of Minimum Outdoor Air Flow
1.18.10 Sizing:System
The Sizing:System object contains the input needed to perform a central forced air system design
air flow, heating capacity, and cooling capacity calculation for a system serving one or more zones.
The information needed consists of the outside environmental conditions and the design supply air
temperatures, outdoor air flow rate, and minimum system air flow ratio.
The outside conditions come from the design days in the input. A system sizing calculation is
performed for every design day in the input file and the resulting maximum heating and cooling air
flow rates and capacities are saved for use in the component sizing calculations.
Supply air conditions are specified by inputting a supply air temperature for cooling, a supply air
temperature for heating, and a preheat temperature.
The system sizing calculation sums the zone design air flow rates to obtain a system supply air flow
rate. The design conditions and the outdoor air flow rate are used to calculate a design mixed air
temperature. The temperature plus the design supply air temperatures allows the calculation of
system design heating and cooling capacities.
1.18. GROUP – DESIGN OBJECTS 745
1.18.10.1 Inputs
1.18.10.1.18 Field: Cooling Supply Air Flow Rate Per Floor Area {m3/s-m2}
Enter the cooling supply air volume flow rate per zone conditioned floor area in m3/s-m2. This field
is required field when the Cooling Supply Air Flow Rate Method is FlowPerFloorArea. This field
may be left blank if a cooling coil is not included in the airloop or the Cooling Supply Air Flow Rate
Method is not FlowPerFloorArea. The program calculates the cooling supply air volume flow rate
from the cooled floor area served by the air loop and the Flow Per Unit Area value specified by the
user.
1.18.10.1.20 Field: Cooling Supply Air Flow Rate Per Unit Cooling Capacity
{m3/s-W}
Enter the cooling supply air volume flow rate per unit cooling capacity in m3/s-W. This input field
is required when the Cooling Supply Air Flow Rate Method is FlowPerCoolingCapacity. This field
may be left blank if a cooling coil is not included in the airloop or the Cooling Supply Air Flow
Rate Method is not FlowPerCoolingCapacity. The program calculates the airloop cooling supply
air volume flow rate from the design autosized cooling capacity and user specified Flow Per Cooling
Capacity value.
748 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.18.10.1.23 Field: Heating Supply Air Flow Rate Per Floor Area {m3/s-m2}
Enter the heating supply air volume flow rate per zone conditioned floor area in m3/s-m2. This field
is required field when the Heating Supply Air Flow Rate Method is FlowPerFloorArea. This field
may be left blank if a heating coil is not included in the airloop or the Heating Supply Air Flow
Rate Method is not FlowPerFloorArea. The program calculates the heating supply air volume flow
rate from the heated or cooled floor area served by the air loop and the Flow Per Unit Area value
specified by the user.
1.18.10.1.24 Field: Heating Fraction of Autosized Heating Supply Air Flow Rate
Enter the heating supply air volume flow rate as a fraction of the airloop autosized heating supply
air flow rate. This input field is required when the Heating Supply Air Flow Rate Method is Frac-
tionOfAutosizedHeatingAirflow. This input field may be left blank if heating coil is not included in
the airloop or the Heating Supply Air Flow Rate Method is not FractionOfAutosizedHeatingAirflow.
The program calculates the heating supply air volume flow rate from the design autosized heating
supply air flow rate and user specified fraction.
1.18.10.1.25 Field: Heating Fraction of Autosized Cooling Supply Air Flow Rate
Enter the heating supply air volume flow rate as a fraction of the airloop autosized cooling supply
air flow rate. This input field is required when the Heating Supply Air Flow Rate Method is Frac-
tionOfAutosizedCoolingAirflow. This input field may be left blank if heating coil is not included in
1.18. GROUP – DESIGN OBJECTS 749
the airloop or the Heating Supply Air Flow Rate Method is not FractionOfAutosizedCoolingAirflow.
The program calculates the heating supply air volume flow rate from the design autosized cooling
supply air flow rate and user specified fraction.
1.18.10.1.26 Field: Heating Design Supply Air Flow Rate Per Unit Heating
Capacity {m3/s-W}
Enter the heating supply air volume flow rate per unit heating capacity in m3/s-W. This input field
is required when the Heating Design air Flow Method is FlowPerCoolingCapacity. This field may
be left blank if a heating coil is not included in the airloop or the Heating Design air Flow Method
is not FlowPerHeatingCapacity. The program calculates the airloop heating supply air volume flow
rate from the design autosized heating capacity and user specified Flow Per Heating Capacity value.
area of the zones served by the airloop. FractionOfAutosizedCoolingCapacity means the program
calculates the design cooling capacity from user specified fraction and the auto-sized design cooling
capacity. If the value this input field is blank or specified as None, then the next three input fields
are not required. The default method is CoolingDesignCapacity.
Sizing:System ,
VAV Sys 1, !- AirLoop Name
sensible , !- Type of Load to Size On
autosize , !- Design Outdoor Air Flow Rate {m3/s}
0.3, !- Minimum System Air Flow Ratio
4.5, !- Preheat Design Temperature {C}
.008, !- Preheat Design Humidity Ratio {kgWater/kgDryAir}
11.0, !- Precool Design Temperature {C}
.008, !- Precool Design Humidity Ratio {kgWater/kgDryAir}
12.8, !- Central Cooling Design Supply Air Temperature {C}
16.7, !- Central Heating Design Supply Air Temperature {C}
noncoincident , !- Sizing Option
no , !- 100% Outdoor Air in Cooling
no , !- 100% Outdoor Air in Heating
0.008 , !- Central Cooling Design Supply Air Humidity Ratio {kgWater/kgDryAir}
0.008 , !- Central Heating Design Supply Air Humidity Ratio {kgWater/kgDryAir}
designday , !- Cooling Supply Air Flow Rate Method
0, !- Cooling Supply Air Flow Rate {m3/s}
, !- Cooling Supply Air Flow Rate Per Floor Area {m3/s-m2}
, !- Cooling Fraction of Autosized Cooling Supply Air Flow Rate {-}
, !- Cooling Supply Air Flow Rate Per Unit Cooling Capacity {m3/s-W}
designday , !- Heating Supply Air Flow Rate Method
0, !- Heating Supply Air Flow Rate {m3/s}
, !- Heating Supply Air Flow Rate Per Floor Area {m3/s-m2}
752 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.18.10.2 Outputs
The system design air flow rates and heating and cooling capacities are output onto the local file
“eplusssz.<ext>” where <ext> is the extension from the sizing style object (default is csv – a comma
separated file eplusssz.csv). The columns are clearly labeled. It will easily import into Excel or other
spreadsheet program that accepts delimited files. The results are calculated values and do not include
any user input system flow rates.
The calculated system design air flow rates and the user input system design air flow rates are also
reported on the eplusout.eio file. The values are printed out for each system as comma separated
records beginning with System Sizing. An example is:
! <System Sizing Information >c++, System Name , Field Description , Value
System Sizing , VAV SYS 1, Calculated Cooling Design Air Flow Rate [m3/s], 1.3194
System Sizing , VAV SYS 1, User Cooling Design Air Flow Rate [m3/s], 1.5000
System Sizing , VAV SYS 1, Calculated Heating Design Air Flow Rate [m3/s], 0.90363
System Sizing , VAV SYS 1, User Heating Design Air Flow Rate [m3/s], 1.0000
1.18.11 Sizing:Plant
The Sizing:Plant object contains the input needed for the program to calculate plant loop flow rates
and equipment capacities when autosizing. This information is initially used by components that
use water for heating or cooling such as hot or chilled water coils to calculate their maximum water
flow rates. These flow rates are then summed for use in calculating the Plant Loop flow rates.
The program will size any number of chilled water, hot water, condenser water and other plant loops.
There should be one Sizing:Plant object for each plant loop that is to be autosized.
1.18.11.1 Inputs
Sizing:Plant ,
Chilled Water Loop , ! name of loop
Cooling , ! type of loop
7.22, ! chilled water supply temperature
6.67, ! chilled water delta T
NonCoincident , !- Sizing Option
1, !- Zone Timesteps in Averaging Window
GlobalCoolingSizingFactor ; !- Coincident Sizing Factor Mode
754 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.18.11.2 Outputs
The loop flow rates are reported on the eplusout.eio file along with the component sizing results.
When coincident plant sizing method is used, the eio file contains special summary report with
various details and interim values from the calculations, under the following record header: ! ,
Plant Loop Name, Sizing Pass {#}, Measured Mass Flow{kg/s}, Measured Demand {W}, Demand
Calculated Mass Flow{kg/s}, Sizes Changed {Yes/No}, Previous Volume Flow Rate {m3/s}, New
Volume Flow Rate {m3/s}, Demand Check Applied {Yes/No}, Sizing Factor {}, Normalized Change
{}, Specific Heat{}.
Air Loop Zone Equipment: The zone equipment section of the input file is defined as more or
less the rest of the zone/air loop (outside air is handled separately as a subset of the air loop). This
includes everything from where the ducts are split to serve various zones up through where the return
ducts from various zones are mixed into a single return duct. Zone equipment can include dampers
and reheat coils as well as zone specific conditioning systems such as thermostatic baseboard or a
window air conditioner. Most control issues are typically dealt with in the zone equipment section
of the simulation.
Plant Loop Demand Side: One side of the plant is where energy is “demanded” by various
components that make up the air loop or zone equipment. Typically, this is the water side of
equipment such as coils, baseboard, radiant heating and cooling, etc. In the case of a condenser
loop, energy is typically “demanded” by a chiller condenser or other water source heat pump. The
demand side of this loop can also include mixers, flow splitters, and a bypass.
Plant Loop Supply Side: The other side of the plant loop is where energy is “supplied” by
various components. The components typically found on the supply side include pumps, boilers,
chillers, purchased heating and cooling, ice storage, etc. In the case of a condenser, the components
would be cooling tower, fluid cooler, or ground source heat exchanger, etc. As with the demand
side, this loop can also include mixers, flow splitters, and a bypass.
The section of the input file for describing the HVAC system tends to follow this structure presented
above. Both plant and condenser loops are defined with a master description and then branch off
into supply and demand side details. Linkage between the two sides is done using node names in the
master statement. The air loop and zone equipment descriptions are slightly more complex due to
the wide range of potential systems that are anticipated. Note that in every section controls become
a key element and must be addressed. Each of the following sections details either a loop, a portion
of a loop, or controls.
1.20.1 NodeList
For convenience, the NodeList object can be used to identify all the nodes for a particular use. A
node list is not always required. The advantage of listing all the nodes in this manner is that input
fields in other objects that ask for a node name can refer to either a single node or a list of nodes
using this object.
There are other lines of input syntax that require the use of a NodeList as part of the input. These
syntax items include: OutdoorAir:NodeList and the SetpointManager objects. In these two cases,
the use of a NodeList statement is mandatory if there is more than one node in this particular “list”.
For example, if the outside air only has a single inlet node, then the name of that node can replace
the node list name in the input syntax. As a result of this mandatory specification of node lists for
certain types of input, nodes can, obviously, and may be members of more than one list.
1.20.1.1 Inputs
This alpha designation must be unique among all the Node List Names. It is used as reference in
various objects (e.g. OutdoorAir:NodeList).
1.20.1.2 Outputs
A simple detail of Nodes and numbers assigned appears in the eplusout.bnd file:
! <Node >,<NodeNumber >,<Node Name >,<Node Fluid Type >,<\# Times Node Referenced After Definition >
Node ,1, OUTSIDE AIR INLET NODE 1,Air ,2
Node ,2,VAV SYS 1 INLET NODE ,Air ,3
Node ,3,MIXED AIR NODE 1,Air ,5
Node ,4,MAIN COOLING COIL 1 OUTLET NODE ,Air ,3
Node ,5,MAIN HEATING COIL 1 OUTLET NODE ,Air ,4
Node ,6,VAV SYS 1 OUTLET NODE ,Air ,7
The following node variable is also available for system nodes that are for “air”:
– HVAC, Average, System Node Current Density Volume Flow Rate [m3/s]
– HVAC, Average, System Node Current Density [kg/m3]
The following node variables are “advanced” and normally used for debugging unusual
cases:
The following node variable reports node carbon dioxide concentration when carbon
dioxide is simulated (ref. ZoneAirContaminantBalance):
The following node variable reports node generic contaminant concentration when
generic contaminant is simulated (ref. ZoneAirContaminantBalance):
The current minimum desired humidity ratio at a system node in kg-water/kg-dry-air. Some con-
trollers and equipment types use the min/max values as dual setpoints at a single node. Not
applicable for liquid nodes.
1.20.1.2.13 System Node Standard Density Volume Flow Rate [m3 /s]
The current volume flow rate at a system node in m3 /s. This is report is calculated from the mass
flow using standardized values for density that do not vary over time (except for steam which varies
with quality). For water nodes this density is determined at a temperature of 5.05ºC. For air
nodes this density is determined for dry air at the standard barometric pressure for the location’s
elevation, and a temperature of 20.0ºC. For air nodes, also see the report “System Node Current
Density Volume Flow Rate.”
1.20.1.2.21 System Node Current Density Volume Flow Rate [m3 /s]
The current volume flow rate at a system node in m3 /s based on the current density. This report
differs from the one called “System Node Standard Density Volume Flow Rate” in that it uses an
air density calculated for the current moist air conditions rather than a standard density.
1.20. GROUP – NODE-BRANCH MANAGEMENT 761
1.20.2 BranchList
A branch list is intended to define the branches or portions of a particular loop that are present on
an individual plant or condenser loop. Thus, the BranchList syntax simply provides a list of branch
names (see Branch syntax) that then refer to more detailed syntax in another part of the input file.
The syntax for describing a list of branches is given below.
Branches in BranchList objects should be listed in flow order: inlet branch, then parallel branches,
then outlet branch. Branches (within a splitter/mixer) are simulated in the order listed.
1.20.2.1 Inputs
1.20.2.2 Outputs
1.20.3 Branch
Branches can be considered the mid-level grouping of items in the EnergyPlus HVAC loop scheme.
Components are the lowest level of information. A collection of components in series forms a branch.
Every branch must have at least one component, but it may have several components in series. The
1.20. GROUP – NODE-BRANCH MANAGEMENT 763
air loop also has “unitary” objects that are compound objects that wrap components and when they
are used it is the unitary objects that appear on the Branch and not the child components. The
Branch defines the order that components appear on the branch. Moreover, a collection of branches
and their connecting information form a loop. Therefore, a branch is a collection of components
while a loop is a collection of branches. Thus, components are specified for particular HVAC loops
by assigning them to branches and then connecting those branches together to form a loop.
For hydronic plant systems, the Branch object is used on both the demand side and the supply side of
the plant loop. For HVAC air systems, the Branch object is only used to describe the components on
the supply side of an air loop. The demand side of the air loop does not use the Branch object. The
outside air system appears on a Branch object but it does not use a Branch object itself to describe
the components that included in the outside air system. So-called “ZoneHVAC:*” equipment, HVAC
equipment directly associated with a zone, do not use the Branch object.
It should be noted that each component also has at least two nodes associated with it—an inlet node
and an outlet node. These nodes, by default, are also part of the branch to which their components
are assigned. Although it may appear redundant to list the node names in both the Branch and
in the component object being referenced, this is needed because many components are connected
to more than one loop at a time and the node names are needed here to distinguish which portion
of the component is being attached to this particular branch and its loop. It should be noted that
each branch must have at least one component on it. A “null” branch such as one where the first
component on the loop is in reality a splitter or mixer should be defined as a single Pipe component
for plant, or a single Duct component for air systems.
1.20.3.1 Inputs
Branch ,
Air Loop Main Branch , !- Branch Name
, !- Pressure Drop Curve Name
AirLoopHVAC:UnitaryHeatCool:VAVChangeoverBypass , !- Comp1 Type
GasHeat CBVAV System , !- Comp1 Name
Air Loop Inlet Node , !- Comp1 Inlet Node Name
Air Loop Outlet Node; !- Comp1 Outlet Node Name
BRANCH ,
Air Loop Main Branch , !- Branch Name
, !- Pressure Drop Curve Name
FAN:ConstantVolume , !- Comp1 Type
Supply Fan 1, !- Comp1 Name
Air Loop Inlet Node , !- Comp1 Inlet Node Name
Cooling Coil Air Inlet Node , !- Comp1 Outlet Node Name
COIL:Water:DetailedFlatCooling , !- Comp2 Type
Detailed Cooling Coil , !- Comp2 Name
Cooling Coil Air Inlet Node , !- Comp2 Inlet Node Name
Air Loop Outlet Node; !- Comp2 Outlet Node Name
1.20.3.2 Outputs
The components on a branch are in series and that list is in simulation and connection order. Each
branch must obey the rules: the outlet for component 1 has to have the same node name as the inlet
for component 2, and so forth.
Eplusout.err contains the test for “individual branch integrity”:
1.20. GROUP – NODE-BRANCH MANAGEMENT 765
The addition of pressure simulation for branches in fluid loops brings a new output at the branch
level:
1.20.4 ConnectorList
A connector list is a collection of either one or two connection devices (Connector:Mixer or Con-
nector:Splitter). Due to the definition of a loop in EnergyPlus, there is a maximum of one mixer
and one splitter allowed for each loop segment. This limitation still allows a tremendous amount of
flexibility to the user and can also still be solved within a reasonable amount of time and without a
complex solver routine. The connection list simply allows the specification of the types and names
of these devices. This allows the main loop statements to have the flexibility to have multiple lists
that can have one or more item.
1.20.4.1 Inputs
1.20.4.2 Outputs
1.20.6 Connector:Splitter
A Connector:Splitter is used to take a single fluid stream or branch and split it into more than one
outlet branches. This input object is used purely to connect the inlet and outlet branches.
1.20. GROUP – NODE-BRANCH MANAGEMENT 767
1.20.6.1 Inputs
1.20.7 Connector:Mixer
A Connector:Mixer is used to combine or mix several inlet branches into a single outlet branch. This
input object is used purely to connect the inlet branches with the outlet branch.
1.20.7.1 Inputs
Connector:Splitter ,
CW Loop Splitter ,
CW Pump Branch ,
Little Chiller Branch ,
Big Chiller Branch ,
Purchased Cooling Branch ,
Supply Bypass Branch;
Connector:Mixer ,
CW Loop Mixer ,
Cooling Supply Outlet ,
Little Chiller Branch ,
Big Chiller Branch ,
Purchased Cooling Branch ,
Supply Bypass Branch;
768 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.20.8 Pipe:Adiabatic
In reality, every component is connected to its closest neighbors via a pipe or a duct. At the current
time, such detail is not needed in EnergyPlus. Thus, the Pipe:Adiabatic component is currently
used more as a connection device (for branches that really do not have any components associated
with them) or as a bypass than anything else. As such, its input is very simple and its algorithm is
equally simple. The current algorithm for a pipe is simply to pass the inlet conditions to the outlet
of the pipe component.
1.20.8.1 Inputs
Pipe:Adiabatic ,
Demand Side Inlet Pipe ,
CW Demand Inlet Node ,
CW Demand Entrance Pipe Outlet Node;
1.20.8.2 Outputs
1.20.9 Pipe:Adiabatic:Steam
To connect the various components in a steam system regardless of it being the condensate or
the steam side of the loop steam pipe needs to be used. In reality, every component is connected
to its closest neighbors via a pipe or a duct. At the current time, such detail is not needed in
EnergyPlus. Thus, the Pipe:Adiabatic:Steam component is currently used more as a connection
device (for branches that really do not have any components associated with them). As such, its
input is very simple and its algorithm is equally simple. The current algorithm for a pipe is simply
to pass the inlet conditions to the outlet of the pipe component.
1.20.9.1 Inputs
Pipe:Adiabatic:Steam ,
Steam Demand 1 Steam Inlet Pipe , !- PipeName
Steam Demand 1 Steam Demand Inlet Node , !- Inlet Node Name
Steam Demand 1 Steam Demand Entrance Pipe Outlet Node; !- Outlet Node Name
1.20.9.2 Outputs
1.20.10 Pipe:Indoor
This object specifies inputs which are used to simulate the heat transfer from a plant loop pipe
placed in a zone or when a user schedule is used to specify an environment.
The data definition for object is shown below.
1.20.10.1 Inputs
Pipe:Indoor ,
Pipe Heat Transfer Towers , !- name of outside panel heat exchanger
Insulated Pipe , !- Construction name
Condenser Tower Outlet Node , !- Comp1 Inlet Node Name
HTPipe Outlet Node , !- Comp1 Outlet Node Name
Water , !- Fluid name
Zone , !- field Ambient Temperature Outside Air Node name
0.05, !- Pipe Inside Diameter (thickness in construction data)
100.0; !- pipe length
1.20.10.2 Outputs
1.20.11 Pipe:Outdoor
This object specifies inputs which are used to simulate the heat transfer from a plant loop pipe
placed in an outdoor environment.
1.20.11.1 Inputs
Pipe:Outdoor ,
Pipe Heat Transfer Towers , !- name of outside panel heat exchanger
Insulated Pipe , !- Construction name
Condenser Tower Outlet Node , !- Comp1 Inlet Node Name
HTPipe Outlet Node , !- Comp1 Outlet Node Name
Water , !- Fluid name
PipeHeatTransfer Inlet Node , !- field Ambient Temperature Outside Air Node name
0.05, !- Pipe Inside Diameter (thickness given in construction data)
100.0; !- pipe length
1.20.11.2 Outputs
1.20.12 Pipe:Underground
This object specifies inputs which are used to simulate the heat transfer from a plant loop pipe
placed underground.
1.20.12.1 Inputs
Pipe:Underground ,
Pipe Heat Transfer Towers , !- Name of Pipe
Insulated Buried Pipe , !- Construction Name
Condenser Tower Outlet Node , !- Inlet Node Name
HTPipe Outlet Node , !- Outlet Node Name
Water , !- Fluid Name
SunExposed , !- Sun Exposure
0.05, !- Pipe Inside Diameter
20.0, !- Pipe Length
Buried Pipe Soil , !- Soil Material
Site:GroundTemperature :Undisturbed:KusudaAchenbach , !- Type of Undisturbed Ground Temperature
Object
KATemps; !- Name of Undisturbed Ground Temperature Object
Construction ,
Insulated Buried Pipe , !- Name
Buried Pipe Insulation , !- Layer #1
Buried Pipe Steel; !- Layer #2
Material ,
Buried Pipe Soil , !- Name
Smooth , !- Roughness
1.5, !- Thickness {m}
0.36, !- Conductivity {W/m-K}
2000.0 , !- Density {kg/m3}
1200.0 , !- Specific Heat {J/kg -K}
0.9, !- Thermal Absorptance
0.5, !- Solar Absorptance
0.5; !- Visible Absorptance
1.20.12.2 Outputs
– PipingSystem:Underground:Domain
– PipingSystem:Underground:PipeCircuit
– PipingSystem:Underground:PipeSegment
1.20.14 PipingSystem:Underground:Domain
This section documents the domain object, which is used to specify information for the overall ground
domain, including thermal properties, mesh parameters, and surface interaction.
1.20.14.1 Inputs
1.20.14.1.25 Field: Convergence Criterion for the Outer Cartesian Domain Iter-
ation Loop
The maximum temperature deviation within any cell between one iteration and another to decide
that the Cartesian domain has converged to within tolerance. A smaller value will improve accuracy
and computation time. A smaller value should be accompanied by a higher number of iterations if
maximum accuracy is desired.
1.20.15 PipingSystem:Underground:PipeCircuit
This section documents the pipe circuit object, which is used to specify information for the plant
loop topology, such as inlet and outlet connections. This object also groups together pipe segments
to define flow paths within a given pipe circuit.
1.20.15.1 Inputs
1.20.15.1.10 Field: Convergence Criterion for the Inner Radial Iteration Loop
The maximum temperature deviation within any cell between one iteration and another to decide
that the radial domain has converged to within tolerance. A smaller value will improve accuracy
and computation time. A smaller value should be accompanied by a higher number of iterations if
maximum accuracy is desired.
1.20.15.1.12 Field: Number of Soil Nodes in the Inner Radial Near Pipe Mesh
Region
The number of soil nodes to discretize pipe cells. More information on mesh development is
provided in the engineering reference manual.
1.20.15.1.13 Field: Radial Thickness of Inner Radial Near Pipe Mesh Region
The radial distance used to discretize pipe cells. More information on mesh development is provided
in the engineering reference manual.
1.20.15.1.14 Field: Number of Pipe Segments Entered for this Pipe Circuit
The number of pipe segment objects which will be defined in the following fields.
1.20.16 PipingSystem:Underground:PipeSegment
This section documents the pipe segment object, which is used to specify information for a single
pipe segment placed at some x, y coordinate in the ground. The flow direction is also defined in
this object to allow for careful description of varying flow paths. This can be useful for accounting
for short circuiting effects if two pipes are placed in counterflow vs. parallel flow.
1.20.16.1 Inputs
PipingSystem:Underground:Domain ,
My Piping System , !- Name
12, !- Xmax
4.5, !- Ymax
36.84 , !- Zmax
2, !- XMeshCount
Uniform , !- XMeshType
, !- XGeometricCoeff
2, !- YMeshCount
Uniform , !- YMeshType
, !- YGeometricCoeff
6, !- ZMeshCount
Uniform , !- ZMeshType
, !- ZGeometricCoeff
1.08, !- GroundThermalConductivity
962, !- GroundDensity
2576, !- GroundSpecificHeat
30, !- MoistureContent
50, !- MoistureContentAtSaturation
Site:GroundTemperature :Undisturbed:KusudaAchenbach , !- Type of Undisturbed Ground Temperature
Object
KATemps , !- Name of Undisturbed Ground Temperature Object
Yes , !- DomainHasBasement
6, !- BasementWidthInDomain
2.5, !- BasementDepthInDomain
Yes , !- ShiftPipeXValuesByBasementWidth
BasementWallOSCM , !- BasementWallBoundaryConditionModel
BasementFloorOSCM , !- BasementFloorBoundaryConditionModel
0.005 , !- CartesianIterationConvergenceCriterion
100, !- CartesianMaxIterations
0.408 , !- EvapotranspirationGroundCoverParameter
1, !- NumPipeCircuits
My Pipe Circuit; !- PipeCircuit
PipingSystem:Underground:PipeCircuit ,
My Pipe Circuit , !- Name
0.3895 , !- PipeThermalConductivity
641, !- PipeDensity
2405, !- PipeSpecificHeat
0.016 , !- PipeInnerDiameter
0.02667 , !- PipeOuterDiameter
0.004 , !- DesignFlowRate
Piping System Inlet Node , !- InletNode
Piping System Outlet Node , !- OutletNode
0.001 , !- RadialIterationConvergenceCriterion
782 CHAPTER 1. INPUT-OUTPUT REFERENCE
100, !- RadialMaxIterations
2, !- RadialMeshCount
0.03, !- RadialMeshThickness
6, !- NumSegments
Segment 1, !- Segment1
Segment 2, !- Segment2
Segment 3, !- Segment3
Segment 4, !- Segment4
Segment 5, !- Segment5
Segment 6; !- Segment6
PipingSystem:Underground:PipeSegment ,
Segment 1, !- Name
0.67, !- X
2.20, !- Burial Depth
IncreasingZ; !- Flow Direction
PipingSystem:Underground:PipeSegment ,
Segment 2, !- Name
0.95, !- X
2.20, !- Burial Depth
IncreasingZ; !- Flow Direction
PipingSystem:Underground:PipeSegment ,
Segment 3, !- Name
1.23, !- X
2.20, !- Burial Depth
IncreasingZ; !- Flow Direction
PipingSystem:Underground:PipeSegment ,
Segment 4, !- Name
1.40, !- X
1.94, !- Burial Depth
DecreasingZ; !- Flow Direction
PipingSystem:Underground:PipeSegment ,
Segment 5, !- Name
1.40, !- X
1.66, !- Burial Depth
DecreasingZ; !- Flow Direction
PipingSystem:Underground:PipeSegment ,
Segment 6, !- Name
1.40, !- X
1.39, !- Burial Depth
DecreasingZ; !- Flow Direction
1.20.16.2 Outputs
1.20.17 Duct
The Duct object is a component for air systems that is a direct analogue for Pipe:Adiabatic in the
fluid loops. It is used when it is necessary (due to the HVAC system configuration) to have a branch
that has no functional components. This case most often arises for a bypass branch. Since every
branch must have at least one component, the Duct component is used for this situation. The duct
is an adiabatic, pass-through component; all of its inlet conditions are passed through unchanged to
its outlet.
1.20.17.1 Inputs
DUCT ,
VAV Sys 1 Bypass Duct , !- Name
VAV Sys 1 Bypass Duct Inlet Node , !- Inlet Node Name
VAV Sys 1 Bypass Duct Outlet Node;!- Outlet Node Name
784 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.20.17.2 Outputs
1.21.1.1 Inputs
– Optimal operates each piece of equipment at its optimal part load ratio. Any remaining loop
demand is distributed evenly to all of the components.
– SequentialLoad loads each piece of equipment sequentially in the order specified in the
PlantEquipmentList to its maximum part load ratio and will operate the last required piece
of equipment between its minimum and maximum part load ratio in order to meet the loop
demand.
1.21. GROUP – PLANT-CONDENSER LOOPS 787
– UniformLoad evenly distributes the loop demand among all available components on the
equipment list for a given load range. If some components do not have the capacity to meet
the uniformly distributed load, the remaining load is distributed sequentially to the other
available components.
– SequentialUniformPLR loads all equipment on the PlantEquipmentList to a uniform part
load ratio (PLR). Components are loaded sequentially based on the order specified in the
PlantEquipmentList until each component is fully loaded, at which point the next subsequent
component is added and the load is distributed uniformly based on PLR between the compo-
nents.
– UniformPLR will load all equipment on the PlantEquipmentList to a uniform part load ratio
(PLR). No equipment will be loaded below its minimum PLR. If the total load is less than
the sum of all equipment on the PlantEquipmentList operating at their respective minimum
PLRs, then the last item in the equipment list is dropped and the load is distributed based on
a uniform PLR for the remaining plant equipment.
Note: For all schemes, if the load for any individual component is less than the component load
at the minimum PLR, the individual component model will false load or reduce duty cycle while
operating at the minimum part load ratio until the load is met.
1.21.1.1.21 Field: Plant Loop Demand Calculation Scheme There are two choices
for plant loop demand calculations schemes in EnergyPlus: SingleSetpoint and DualSetpointDead-
band.
SingleSetpoint - For the SingleSetpoint scheme, the plant loop is controlled to a single temperature
setpoint. This requires a setpoint manager with Control Variable = Temperature to place a setpoint
on the Loop Temperature Setpoint Node. The setpoint will be stored in the Node%TempSetpoint
variable which may be reported using Output:Variable ”System Node Setpoint Temperature.”
Examples of applicable setpoint managers include: SetpointManager:Scheduled, SetpointMan-
ager:OutdoorAirReset, SetpointManager:FollowOutdoorAirTemperature, etc. SingleSetpoint is the
default.
DualSetpoint - For the DualSetpoint scheme, the plant loop is controlled to stay between a
pair of high and low temperature setpoints. This requires one or two setpoint managers to
place two setpoints on the Loop Temperature Setpoint Node. The setpoints will be stored in
the Node%TempSetPointHi and Node%TempSetPointLo variables which may be reported using
Output:Variable ”System Node Setpoint High Temperature” and ”System Node Setpoint Low
Temperature.” There is special setpoint manager, SetpointManager:Scheduled:DualSetpoint, which
will place both the high and low setpoints with Control Variable = Temperature. Otherwise, two set-
point managers are required, one with Control Variable = MaximumTemperature and another with
Control Variable = MinimumTemperature. The two setpoint managers may be the same kind or
different, but care should be taken so that the MinimumTemperature is not set higher than the Max-
imumTemperature. Examples of applicable setpoint managers include: SetpointManager:Scheduled,
SetpointManager:OutdoorAirReset, SetpointManager:FollowOutdoorAirTemperature, etc. Note
that DualSetpoint is used only for plant loops with both heating and cooling supply equipment,
such as a water loop heat pump system. When the loop temperature rises above the MaximumTem-
perature setpoint, then the loop will request cooling, and when the loop temperature is below the
788 CHAPTER 1. INPUT-OUTPUT REFERENCE
PlantLoop ,
Hot Water Loop , !- Plant Loop Name
Water , !- Fluid Type
, !- User Defined Fluid Type
Hot Loop Operation , !- Plant Operation Scheme List Name
HW Loop Outlet Node , !- Loop Temperature Setpoint Schedule Name
100, !- Maximum Loop Temperature {C}
10, !- Minimum Loop Temperature {C}
autosize , !- Maximum Loop Volumetric Flow Rate {m3/s}
0.0, !- Minimum Loop Volumetric Flow Rate {m3/s}
autosize , !- volume of the plant loop {m3}
HW Supply Inlet Node , !- Plant Side Inlet Node Name
HW Supply Outlet Node , !- Plant Side Outlet Node Name
Heating Supply Side Branches , !- Plant Side Branch List Name
Heating Supply Side Connectors , !- Plant Side Connector List Name
HW Demand Inlet Node , !- Demand Side Inlet Node Name
HW Demand Outlet Node , !- Demand Side Outlet Nodes Name
Heating Demand Side Branches , !- Demand Side Branch List Name
Heating Demand Side Connectors , !- Demand Side Connector List Name
Optimal; !- Load Distribution Scheme
In the above example input there is no system availability manager specified and the Demand
Calculation Scheme will default to SingleSetpoint using a single setpoint manager. Common pipe
simulation field in the above example will default to “NONE” since it is not specified.
1.21.1.2 Outputs
In the following output variables, “Debug” denotes variables that are used primarily by the developers
and whose names and application may be cryptic to users. .
1.21.1.2.17 Plant Common Pipe Primary to Secondary Mass Flow Rate [Kg/s]
This output variable gives the mass flow from primary to secondary side in a Two-Way common
pipe simulation. Value is averaged over the reporting interval.
1.21.1.2.18 Plant Common Pipe Secondary to Primary Mass Flow Rate [Kg/s]
This output variable gives the mass flow from secondary to primary side in a Two-Way common
pipe simulation. Value is averaged over the reporting interval.
1.21. GROUP – PLANT-CONDENSER LOOPS 793
1.21.1.2.25 Plant Demand Side Lumped Capacitance Heat Transport Rate [C]
1.21.1.2.26 Plant Supply Side Lumped Capacitance Heat Transport Rate [C]
These two outputs are the heat transfer rate to the the plant (or condenser) loop’s working fluid in
the two half-loops. The program models heat capacitance in the volume of fluid inside the plant
loop itself using two simple models for well-stirred tanks located at each of the half-loop inlet and
outlet pairs. These tank models also receive the heat transferred to the fluid by the work done
by pumping and resulting friction heating. One output is for the point where the fluid leaves the
supply side and enters the demand side. The other output is for the point where the fluid leaves
the demand side and enters the supply side.
1.21.1.2.27 Plant Demand Side Lumped Capacitance Heat Storage Rate [C]
1.21.1.2.28 Plant Supply Side Lumped Capacitance Heat Storage Rate [C]
These two outputs are the heat storage rate of the plant (or condenser) loop’s working fluid in the
two half-loops. The program models heat capacitance in the volume of fluid inside the plant loop
itself using two simple models for well-stirred tanks located at each of the half-loop inlet and outlet
pairs. These tank models also receive the heat transferred to the fluid by the work done by pumping
and resulting friction heating. One output is for the point where the fluid leaves the supply side
and enters the demand side. The other output is for the point where the fluid leaves the demand
side and enters the supply side.
1.21.1.2.29 Plant Demand Side Lumped Capacitance Excessive Storage Time [C]
1.21.1.2.30 Plant Supply Side Lumped Capacitance Excessive Storage Time [C]
These two outputs are the excess storage time of the plant (or condenser) loop’s working fluid in the
two half-loops. The excess storage time is determined by adding the time when the heat storage rate
exceeds the heat transfer rate into the two half-loops at each time step. The program models heat
1.21. GROUP – PLANT-CONDENSER LOOPS 795
capacitance in the volume of fluid inside the plant loop itself using two simple models for well-stirred
tanks located at each of the half-loop inlet and outlet pairs. These tank models also receive the heat
transferred to the fluid by the work done by pumping and resulting friction heating. One output is
for the point where the fluid leaves the supply side and enters the demand side. The other output
is for the point where the fluid leaves the demand side and enters the supply side.
1.21.2 CondenserLoop
The condenser loop input is very similar to that for the plant loop. As of version 7, the two loops are
modeled the same way and inside the program all condenser loops are just plant loops. (In future
versions of the program, this CondenserLoop object might be deprecated and these loops will be
described using the PlantLoop object.) The main differences are the applicable components and
operation schemes. This is depicted in the following diagram.
1.21.2.1 Inputs
This field specifies the time it takes the fluid to circulate through the entire loop. It is only used
when Condenser Loop Volume is set to autocalculate. The default is 2 minutes.
An example of this statement used in an IDF is:
CondenserLoop ,
Condenser Water Loop , !- Name
Water , !- Fluid Type
, !- User Defined Fluid Type
Tower Loop Operation , !- Condenser Equipment Operation Scheme Name
Condenser Supply Outlet Node , !- Condenser Loop Temperature Setpoint Node Name
80, !- Maximum Loop Temperature {C}
10, !- Minimum Loop Temperature {C}
autosize , !- Maximum Loop Flow Rate {m3/s}
0.0, !- Minimum Loop Flow Rate {m3/s}
autocalculate , !- Condenser Loop Volume {m3}
Condenser Supply Inlet Node , !- Condenser Side Inlet Node Name
Condenser Supply Outlet Node , !- Condenser Side Outlet Node Name
Condenser Supply Side Branches , !- Condenser Side Branch List Name
Condenser Supply Side Connectors , !- Condenser Side Connector List Name
Condenser Demand Inlet Node , !- Demand Side Inlet Node Name
Condenser Demand Outlet Node , !- Demand Side Outlet Node Name
Condenser Demand Side Branches , !- Condenser Demand Side Branch List Name
Condenser Demand Side Connectors , !- Condenser Demand Side Connector List Name
SequentialLoad; !- Load Distribution Scheme
SetpointManager:FollowOutdoorAirTemperature ,
MyCondenserControl , !- Name
Temperature , !- Control Variable
OutdoorAirWetBulb , !- Reference Temperature Type
0, !- Offset Temperature Difference {deltaC}
80, !- Maximum Setpoint Temperature {C}
10, !- Minimum Setpoint Temperature {C}
Condenser Supply Outlet Node; !- Setpoint Node or NodeList Name
CondenserLoop ,
Chilled Water Condenser Loop , !- Name
UserDefinedFluidType , !- Fluid Type
PropyleneGlycol15Percent ,!- User Defined Fluid Type
Tower Loop Operation , !- Condenser Equipment Operation Scheme Name
Condenser Supply Outlet Node , !- Condenser Loop Temperature Setpoint Node Name
80, !- Maximum Loop Temperature {C}
10, !- Minimum Loop Temperature {C}
0.00330000 , !- Maximum Loop Flow Rate {m3/s}
0, !- Minimum Loop Flow Rate {m3/s}
autocalculate , !- Condenser Loop Volume {m3}
Condenser Supply Inlet Node , !- Condenser Side Inlet Node Name
Condenser Supply Outlet Node , !- Condenser Side Outlet Node Name
Condenser Supply Side Branches , !- Condenser Side Branch List Name
Condenser Supply Side Connectors , !- Condenser Side Connector List Name
Condenser Demand Inlet Node , !- Demand Side Inlet Node Name
Condenser Demand Outlet Node , !- Demand Side Outlet Node Name
Condenser Demand Side Branches , !- Condenser Demand Side Branch List Name
Condenser Demand Side Connectors , !- Condenser Demand Side Connector List Name
SequentialLoad; !- Load Distribution Scheme
1.21.2.2 Outputs
1.22.2 PlantEquipmentOperationSchemes
1.22.2.1 Inputs
– PlantEquipmentOperation:Uncontrolled
– PlantEquipmentOperation:CoolingLoad
– PlantEquipmentOperation:HeatingLoad
– PlantEquipmentOperation:ComponentSetpoint
1.22. GROUP – PLANT-CONDENSER CONTROL 803
– PlantEquipmentOperation:ThermalEnergyStorage
– PlantEquipmentOperation:UserDefined
PlantEquipmentOperationSchemes ,
CW Loop Operation , !- Name
PlantEquipmentOperation :CoolingLoad , ! Control Scheme 1 Object Type
Peak Operation , !- Control Scheme 1 Name
On Peak , !- Control Scheme 1 Schedule
PlantEquipmentOperation :CoolingLoad , ! Control Scheme 2 Object Type
Off Peak Operation , !- Control Scheme 2 Name
Off Peak; !- Control Scheme 2 Schedule
PlantEquipmentOperationSchemes ,
CW Loop Operation , !- Name
PlantEquipmentOperation :CoolingLoad , ! Control Scheme 1 Object Type
Central Chiller Only , !- Control Scheme 1 Name
PlantOnSched; !- Control Scheme 1 Schedule
1.22.3 CondenserEquipmentOperationSchemes
1.22.3.1 Inputs
– PlantEquipmentOperation:Uncontrolled
– PlantEquipmentOperation:CoolingLoad
– PlantEquipmentOperation:HeatingLoad
– PlantEquipmentOperation:OutdoorDryBulb
– PlantEquipmentOperation:OutdoorWetBulb
– PlantEquipmentOperation:OutdoorDewpoint
– PlantEquipmentOperation:OutdoorRelativeHumidity
– PlantEquipmentOperation:OutdoorDryBulbDifference
– PlantEquipmentOperation:OutdoorWetBulbDifference
– PlantEquipmentOperation:OutdoorDewpointDifference
– PlantEquipmentOperation:UserDefined
The condenser operation schemes apply to the equipment on the ‘supply side’ of the condenser loop—
pumps, cooling towers, ground coupled heat exchangers, etc. The keywords select the algorithm
that will be used to determine which equipment is available for each timestep. The Load Schemes
schemes select a user specified set of equipment for each user specified range of a particular simulation
variable. Load schemes compare the demand on the condenser supply side with specified load ranges
and associated equipment lists. Outdoor schemes compare the current value of an environmental
parameter with user specified ranges of that parameter.
CondenserEquipmentOperationSchemes ,
Tower Loop Operation , !- CondenserOperationSchemeName
PlantEquipmentOperation :CoolingLoad , Control Scheme 1 Object Type
Year Round Tower Operation , !- Control Scheme 1 Name
PlantOnSched; !- Control Scheme 1 Schedule
1.22. GROUP – PLANT-CONDENSER CONTROL 805
1.22.4 PlantEquipmentOperation:Uncontrolled
Uncontrolled loop operation simply specifies a group of equipment that runs ‘uncontrolled’. If the
loop runs, this equipment will run also, unless turned off by the loop flow resolver to maintain
continuity in the fluid loop.
1.22.4.1 Inputs
1.22.5 PlantEquipmentOperation:CoolingLoad
1.22.5.1 Inputs
1.22.6 PlantEquipmentOperation:HeatingLoad
The PlantEquipmentOperation:CoolingLoad and PlantEquipmentOperation:HeatingLoad objects
define the different ranges and which equipment list is valid for each range. After the keyword and
the identifying name, a series of data trios is expected. In each trio, there is a lower limit for the
load range, an upper limit for the load range, and a name that links to an equipment availability
list (the PlantEquipmentList or CondenserEquipmentList objects).
1.22.6.1 Inputs
1.22.6.1.2 Field Set: (Lower limit, Upper Limit, Equip List name) up to 10
This particular load based operation scheme (above) has three different ranges. “Chiller Plant”,
“Chiller Plant and Purchased”, and “Purchased Only” are names which link to various PlantEquip-
mentList or CondenserEquipmentList objects as described below. Gaps may be left in the load
ranges specified, but to operate equipment over the entire range the upper limit of a given range
must equal the lower limit of the next range as shown in the example. If gaps are left in the load
ranges specified, a warning message will be issued when the load to be met falls within a load range
“gap”. If the user wishes to leave a load range “gap” for a specific reason (no equipment to operate
on this plant [or condenser] loop within this load range) and does not want the warning messages
to be generated, then specify a lower limit, upper limit and equipment list name for the gap and do
not specify any equipment in the associated equipment list, as shown below.
PlantEquipmentList ,
Chiller Plant , !- Name
Chiller:Electric , !- Equipment 1 Object Type
Big Chiller; !- Equipment 1 Name
PlantEquipmentList ,
NoEquipmentOperationOnThisPlantLoop ; !- Name
PlantEquipmentList ,
Chiller Plant and Purchased , !- Name
Chiller:Electric , !- Equipment 1 Object Type
Big Chiller , !- Equipment 1 Name
DistrictCooling , !- Equipment 2 Object Type
Purchased Cooling; !- Equipment 2 Name
PlantEquipmentList ,
Purchased Only , !- Name
1.22. GROUP – PLANT-CONDENSER CONTROL 807
1.22.7 PlantEquipmentOperation:OutdoorDryBulb
1.22.8 PlantEquipmentOperation:OutdoorWetBulb
1.22.9 PlantEquipmentOperation:OutdoorRelativeHumidity
1.22.10 PlantEquipmentOperation:OutdoorDewpoint
The outdoor operation objects define the different ranges of the various environmental parameters
and which equipment list is valid for each range. After the keyword and the identifying name, a series
of data trios is expected. In each trio, there is a lower limit for the load range, an upper limit for the
load range, and a name that links to an equipment availability list (the CondenserEquipmentList).
The fields for each of these are:
1.22.10.1 Inputs
1.22.10.1.2 Field Set: (Lower limit, Upper Limit, Equip List name) up to 10
1.22.11 PlantEquipmentOperation:OutdoorDryBulbDifference
1.22.11.1 Inputs
1.22.12 PlantEquipmentOperation:OutdoorWetBulbDifference
1.22.12.1 Inputs
1.22.13 PlantEquipmentOperation:OutdoorDewpointDifference
The Delta Temperature based control strategies help to control any condenser equipment based
on the difference between a reference node temperature and any environmental temperature. For
example a cooling tower can be controlled by a strategy, which looks at the difference between the
tower inlet temperature and wet-bulb temperature. A difference range is specified for each equipment
list.
1.22.13.1 Inputs
1.22.14 PlantEquipmentOperation:ComponentSetpoint
In addition to load range based control on the plant loop, sequencing the plant components based
on the outlet temperature of individual equipment is allowed. This scheme is common to many
present-day Energy Management Systems sequencing. In this scheme, the sequencing is done based
on the order specified in the control object described below.
However, when sequencing a boiler and a cooling tower to control the heating and cooling set point
temperatures of a condenser loop, it is recommended that the boiler and the cooling tower be placed
in a parallel configuration. The series configuration of these two equipment, though possible to
model them, may result in simultaneous heating and cooling operation when the boiler is ON and
the cooling tower operates in free cooling mode, i.e., the cooling tower may provide free cooling that
could over cool the water below the boiler heating setpoint temperature.
1.22.14.1 Inputs
PlantEquipmentOperationSchemes ,
CW Loop Operation , !- PlantOperationSchemeName
PlantEquipmentOperation :ComponentSetpoint , ! Control Scheme 1 Object Type
Test Scheme , !- Control Scheme 1 Name
On; !- Control Scheme 1 Schedule
PlantEquipmentOperation :ComponentSetpoint ,
Test Scheme ,
CHILLER:ELECTRIC , !- Equipment 1 Object Type
Little Chiller , !- Equipment 1 Name
Little Chiller Inlet Node , !- Demand Calculation 1 Node Name
Little Chiller Outlet Node , !- Setpoint 1 Node Name
0.0011 , !- Component 1 Flow Rate
COOLING , !- Operation 1 Type
CHILLER:ELECTRIC , !- Equipment 2 Object Type
Big Chiller , !- Equipment 2 Name
Big Chiller Inlet Node , !- Demand Calculation 2 Node Name
Big Chiller Outlet Node , !- Setpoint 2 Node Name
0.0011 , !- Component 2 Flow Rate
COOLING; !- Operation 2 Type
1.22.15 PlantEquipmentOperation:ThermalEnergyStorage
Users of thermal energy storage, particularly ice storage systems, are often faced with a challenge
of specifying input for these systems. Essentially, they have to define various setpoint managers,
temperature schedules, etc. in order to make the system functional. This plant/condenser control
type simplifies the input somewhat by eliminating both a setpoint manager and a schedule for each
piece of equipment that makes up the ice storage system. In fact, this operation scheme internally
creates the setpoint managers required by the equipment listed as operated by the scheme defined by
this syntax. While the more complex definition is possible and provides more flexibility like hourly
variation of setpoint temperatures at the outlet of each piece of equipment, this input provides the
most convenient method for making the system to work and assumes a single charging setpoint
temperature and a single discharging setpoint temperature. For most systems, this is all that is
needed.
1.22.15.1 Inputs
PlantEquipmentOperationSchemes ,
CW Loop Operation , !- Name
PlantEquipmentOperation :ThermalEnergyStorage , !- Control Scheme 1 Object Type
Chiller and Partial Ice Storage , !- Control Scheme 1 Name
PlantOnSched; !- Control Scheme 1 Schedule Name
PlantEquipmentOperation :ThermalEnergyStorage ,
Chiller and Partial Ice Storage , !- Name
OnPeakEnergy , !- On -Peak Schedule Name
ChargingAvail , !- Charging Availability Schedule Name
7.22, !- Non -charging Chilled Water Temperature
-5.0, !- Charging Chilled Water Temperature
Chiller:Electric , !- Component 1 Object Type
Central Chiller , !- Component 1 Name
Central Chiller Inlet Node , !- Component 1 Demand Calculation Node Name
Central Chiller Outlet Node , !- Component 1 Setpoint Node Name
autosize , !- Component 1 Flow Rate {m3/s}
COOLING , !- Component 1 Operation Type
ThermalStorage:Ice:Detailed , !- Component 2 Object Type
Ice Tank , !- Component 2 Name
Ice Tank Inlet Node , !- Component 2 Demand Calculation Node Name
Ice Tank Outlet Node , !- Component 2 Setpoint Node Name
0.13506E-02, !- Component 2 Flow Rate {m3/s}
DUAL; !- Component 2 Operation Type
1.22.16 PlantEquipmentList
1.22.16.1 Inputs
1.22.17 CondenserEquipmentList
The PlantEquipmentList and CondenserEquipmentList specify available plant and condenser loop
equipment respectively for any loop operation scheme. Each statement contains the object name,
an identifying name (which links the definition back to one of the operation scheme statements)
and a variable length of data pairs. These pairs refer to a plant equipment type and an identifying
name. The type in this list of pairs must correspond to a valid plant object as described in the next
subsection.
Note: If a PlantEquipmentList or CondenserEquipmentList object is specified with no equipment
object types or equipment names, then the corresponding PlantEquipmentOperation:* object will
1.23. GROUP – PLANT EQUIPMENT 813
assume all available equipment on this plant (or condenser) loop should be OFF (not operate) within
the specified lower/upper limit.
1.22.17.1 Inputs
Note that this list is the middle range defined in the PlantEquipmentOperation:CoolingLoad state-
ment named “Peak Operation” above. This defines the equipment available when the load encoun-
tered by the plant (chiller water demand, for example) is between 7000 W and 24500 W. EnergyPlus
will run the “Big Chiller” first up to its capacity and then attempt to meet the remaining load (while
in that range) with the next piece of equipment (in this case, “Purchased:Cooling”) in the list.
The following three outputs are only available for water-cooled chillers
The following blocks of outputs are for steam and fuel-driven chillers
The following output is applicable only for indirect absorption chillersHVAC,Average,Chiller Part
Load Ratio
These outputs are the electric power input to the chiller. In the case of steam or fuel-powered chillers,
this repesents the internal chiller pumps and other electric power consumption. Consumption is
metered on Cooling:Electricity, Electricity:Plant, and Electricity:Facility.
These outputs are the evaporator heat transfer which is the cooling delivered by the chiller. Chiller
Evaporator Cooling Energy is metered on Chillers:EnergyTransfer, EnergyTransfer:Plant, and En-
ergyTransfer:Facility.
These outputs are the evaporator (chilled water) inlet and outlet temperatures and flow rate.
1.23. GROUP – PLANT EQUIPMENT 817
This output is the coefficient of performance for the chiller during cooling operation. It is calcu-
lated as the evaporator heat transfer rate (Chiller Evaporator Cooling Rate) divided by the “fuel”
consumption rate by the chiller. For the constant COP and electric chillers, the “fuel” is electricity
so the divisor is Chiller Electricity Rate [W]. For the absorption chiller, the “fuel” is steam so the
divisor is Steam Consumption Rate [W].
Note that this variable is reported as zero when the chiller is not operating. When reported for
frequencies longer than “detailed” (such as timestep, hourly, daily, monthly or environment), this
output will only be meaningful when the chiller is operating for the entire reporting period. To
determine an average COP for a longer time period, compute the COP based on total evaporator
heat transfer divided by total electric or fuel input over the desired period.
This output is the operating part-load ratio of the indirect absorption chiller. This output may fall
below the minimum part-load ratio specified in the input. For this case, the Chiller Cycling Ratio
is used to further define the performance of the indirect absorption chiller.
This output is the fraction of the timestep the indirect absorption chiller operates. When the chiller
operates above the minimum part-load ratio, a Chiller Cycling Ratio of 1 is reported. When the
chiller operates below the minimum part-load ratio, the Chiller Cycling Ratio reports the fraction
of the timestep the indirect absorption chiller operates.
These outputs are the condenser heat transfer which is the heat rejected from the chiller to either a
condenser water loop or through an air-cooled condenser. Chiller Condenser Heat Transfer Energy
is metered on HeatRejection:EnergyTransfer, EnergyTransfer:Plant, and EnergyTransfer:Facility.
This output is the condenser (heat rejection) inlet temperature for air-cooled or evap-cooled chillers.
For an air-cooled chiller, this output would be the dry-bulb temperature of the air entering the
condenser coil. For an evap-cooled chiller, this output would be the wet-bulb temperature of the air
entering the evaporatively-cooled condenser coil.
These outputs are the electric power input to the chiller’s basin heater (for evaporatively-cooled
condenser type). Consumption is metered on Chillers:Electricity, Electricity:Plant, and Electric-
ity:Facility
818 CHAPTER 1. INPUT-OUTPUT REFERENCE
These outputs are the condenser (heat rejection) inlet and outlet temperatures and flow rate for
water-cooled chillers.
For engine-driven and turbine-driven chillers, these outputs are the shaft power produced by the
prime mover and transferred to the chiller compressor.
For chillers with heat recovery, such as engine-driven chillers, these outputs are the components of
recoverable energy available. For a given chiller type, one or more of the following components may be
applicable: Lube (engine lubricant), Jacket (engine coolant), Exhaust (engine exhaust), and Total.
Chiller Lube Recovered Heat Energy, Chiller Jacket Recovered Heat Energy, and Chiller Exhaust
Heat Recovery Energy are metered on HeatRecovery:EnergyTransfer, EnergyTransfer:Plant, and
EnergyTransfer:Facility.
These outputs are the heat recovery inlet and outlet temperatures and flow rate for chillers with
heat recovery such as engine-driven and gas turbine chillers.
This output variable is available for heat recovery chillers that model split bundle condenser. The
condenser fluid temperatures used to characterize chiller performance are modified to account for
the temperature of the heat recovery fluid. This output is the resulting temperature used for
characterizing chiller performance and is a blend of the temperatures in the condenser and heat
recovery fluid streams. For the Chiller:Electric and Chiller:Electric:EIR models, this is an effective
inlet temperature while for the Chiller:Electric:ReformulatedEIR model, this is an effective outlet
temperature.
These outputs are the steam or fuel input for steam or fuel-fired chillers. Valid fuel types depend on
the type of chiller. <Fuel Type> may be one of: Gas (natural gas), Steam, Propane, Diesel, Gasoline,
FuelOilNo1, FuelOilNo2, OtherFuel1 and OtherFuel2. Consumption is metered on Cooling:<Fuel
Type>, <Fuel Type>:Plant, and <Fuel Type>:Facility.
1.23.3 Chiller:Absorption
1.23.3.1 Inputs
C1
SteamInputRatio = + C2 + C3 ∗ P LR (1.49)
P LR
The following three fields contain the coefficients for the equation.
1.23.3.1.15 Field: Coefficient 1 of the Steam Use Part Load Ratio Curve
C1 in the Generator Heat Input Part Load Ratio Curve. This value is obtained by fitting manufac-
turers’ performance data to the curve.
1.23.3.1.16 Field: Coefficient 2 of the Steam Use Part Load Ratio Curve
C2 in the Generator Heat Input Part Load Ratio Curve. This value is obtained by fitting manufac-
turers’ performance data to the curve.
1.23.3.1.17 Field: Coefficient 3 of the Steam Use Part Load Ratio Curve
C3 in the Generator Heat Input Part Load Ratio Curve. This value is obtained by fitting manufac-
turers’ performance data to the curve.
The following three fields contain the coefficients for the equation.
1.23.3.1.19 Field: Coefficient 1 of the Pump Electric Use Part Load Ratio Curve
C1 in the Pump Electric Use Part Load Ratio Curve. This value is obtained by fitting manufacturers’
performance data to the curve.
1.23.3.1.20 Field: Coefficient 2 of the Pump Electric Use Part Load Ratio Curve
C2 in the Pump Electric Use Part Load Ratio Curve. This value is obtained by fitting manufacturers’
performance data to the curve.
1.23.3.1.21 Field: Coefficient 3 of the Pump Electric Use Part Load Ratio Curve
C3 in the Pump Electric Use Part Load Ratio Curve. This value is obtained by fitting manufacturers’
performance data to the curve.
822 CHAPTER 1. INPUT-OUTPUT REFERENCE
Chiller:Absorption ,
Big Chiller , !- Chiller Name
50000 , !- Nominal Capacity {W}
250, !- Nominal Pumping Power {W}
Big Chiller Inlet Node , !- Plant_Side_Inlet_Node
Big Chiller Outlet Node , !- Plant_Side_Outlet_Node
Big Chiller Condenser Inlet Node , !- Condenser_Side_Inlet_Node
Big Chiller Condenser Outlet Node , !- Condenser_Side_Outlet_Node
0.15, !- Minimum Part Load Ratio
1.0, !- Maximum Part Load Ratio
0.65, !- Opt Part Load Ratio
35.0, !- Temp Design Condenser Inlet {C}
0.0011 , !- Design Chilled Water Flow Rate {m3/s}
0.0011 , !- Design Condenser Water Flow Rate {m3/s}
0.03303 , !- Coefficient1 of the steam use part load ratio curve
0.6852 , !- Coefficient2 of the steam use part load ratio curve
0.2818 , !- Coefficient3 of the steam use part load ratio curve
1.0, !- Coefficient1 of the pump electric use part load ratio curve
0, !- Coefficient2 of the pump electric part load ratio curve
0, !- Coefficient3 of the pump electric use part load ratio curve
5, !- Chilled Water Outlet Temperature Lower Limit {C}
AbsorberSteamInletNode , !- Generator Inlet Node Name
AbsorberSteamOutletNode , !- Generator Outlet Node Name
VariableFlow , !- Chiller Flow Mode
Steam , !- Generator Fluid Type
autosize , !- Design Generator Volumetric Fluid Flow Rate {m3/s}
2.0; !- Degree of Subcooling in Steam Generator {C}
1.23.3.2 Outputs
These chiller output variables are defined above under “Generic Chiller Outputs.”
1.23.4 Chiller:Absorption:Indirect
The Chiller:Absorption:Indirect object is an enhanced version of the absorption chiller model found
in the Building Loads and System Thermodynamics (BLAST) program. This enhanced model is
nearly identical to the existing absorption chiller model (Ref. Chiller:Absorption) with the exceptions
that: 1) the enhanced indirect absorption chiller model provides more flexible performance curves
and 2) chiller performance now includes the impact of varying evaporator, condenser, and generator
temperatures. Since these absorption chiller models are nearly identical (i.e., the performance curves
of the enhanced model can be manipulated to produce similar results to the previous model), it is
quite probable that the Chiller:Absorption model will be deprecated in a future release of EnergyPlus.
1.23.4.1 Inputs
1.23.4.1.17 Field: Generator Heat Input Function of Part Load Ratio Curve
Name
This required alpha field specifies the name of the curve used to determine the heat input to the
chiller. The curve is a quadratic or cubic curve which characterizes the heat input as a function of
chiller part-load ratio. The curve output is multiplied by the chiller’s nominal capacity and operating
part-load ratio or minimum part-load ratio, whichever is greater, to determine the amount of heat
input required for the given operating conditons.
1.23.4.1.18 Field: Pump Electric Input Function of Part Load Ratio Curve Name
This alpha field specifies the name of the curve used to determine the pump electrical input to the
chiller. The curve is a quadratic or cubic curve which characterizes the pump electrical power as a
function of chiller part-load ratio. The curve output is multiplied by the chiller’s nominal pumping
power and operating part-load ratio or minimum part-load ratio, whichever is greater, to determine
the amount of pumping power required for the given operating conditons.
Chiller:Absorption:Indirect ,
Big Chiller , !- Chiller Name
100000 , !- Nominal Capacity {W}
250, !- Nominal Pumping Power {W}
Big Chiller Inlet Node , !- Evaporator Inlet Node Name
Big Chiller Outlet Node , !- Evaporator Outlet Node Name
Big Chiller Condenser Inlet Node , !- Condenser Inlet Node Name
Big Chiller Condenser Outlet Node , !- Condenser Outlet Node Name
0.15, !- Minimum Part Load Ratio
1.0, !- Maximum Part Load Ratio
0.65, !- Opt Part Load Ratio
35.0, !- Temp Design Condenser Inlet {C}
10.0, !- Temp Lower Limit Condenser Inlet {C}
5.0, !- Chilled Water Outlet Temperature Lower Limit {C}
0.0011 , !- Design Chilled Water Flow Rate {m3/s}
0.0011 , !- Design Condenser Water Flow Rate {m3/s}
VariableFlow , !- Chiller Flow Mode
SteamUseFPLR , !- Generator Heat Input function of part -load ratio curve name
PumpUseFPLR , !- Pump Electric Input function of part -load ratio curve name
1.23. GROUP – PLANT EQUIPMENT 829
1.23.4.2 Outputs
These chiller output variables are defined above under “Generic Chiller Outputs.”
1.23.5 Chiller:ConstantCOP
This chiller model is based on a simple, constant COP simulation of the chiller. In this case,
performance does not vary with chilled water temperature or condenser conditions.
Such a model is useful when the user does not have access to detailed performance data.
1.23.5.1 Inputs
performed as usual and the results are multiplied by the sizing factor. For this component the
inputs that would be altered by the sizing factor are: Nominal Capacity, Design Chilled Water Flow
Rate and Design Condenser Water Flow Rate. Sizing Factor allows the user to size a component to
meet part of the design load while continuing to use the autosizing feature.
Chiller:ConstantCOP ,
Little Chiller , !- Name
25000 , !- Nominal Capacity {W}
2.5, !- Nominal COP {W/W}
0.0011 , !- Design Chilled Water Flow Rate {m3/s}
0.0011 , !- Design Condenser Water Flow Rate {m3/s}
Little Chiller Inlet Node , !- Chilled Water Inlet Node Name
Little Chiller Outlet Node , !- Chilled Water Outlet Node Name
Little Chiller Condenser Inlet Node , !- Condenser Inlet Node Name
Little Chiller Condenser Outlet Node , !- Condenser Outlet Node Name
EvaporativelyCooled , !- Condenser Type
1.23. GROUP – PLANT EQUIPMENT 833
1.23.5.2 Outputs
Air-cooled or Evap-cooled:
Evap-cooled:
Water-cooled:
These chiller output variables are defined above under “Generic Chiller Outputs.”
834 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.23.6 Chiller:Electric
This chiller model is the empirical model from the Building Loads and System Thermodynamics
(BLAST) program. Capacity, power, and full load are each defined by a set of performance curves
(quadratics). Chiller performance curves are generated by fitting catalog data to third order polyno-
mial equations. The nominal inputs and curves described below are combined as follows to calculate
the chiller power:
NominalCapacity
Power = FracFullLoadPower·FullLoadPowerRat·AvailToNominalCapacityRatio·
COP
(1.51)
where:
NominalCapacity = Nominal Capacity field
COP = COP field
AvailToNominalCapacityRatio = the result of the Capacity Ratio Curve
FullLoadPowerRat = the result of the Power Ratio Curve
FracFullLoadPower = the result of the Full Load Ratio Curve
1.23.6.1 Inputs
T CEntrequired − T CEntrated
(1.52)
T ELvrequired − T ELvrated
where:
836 CHAPTER 1. INPUT-OUTPUT REFERENCE
TCEntrequired = Required entering condenser air or water temperature to maintain rated capacity.
TCEntrated = Rated entering condenser air or water temperature at rated capacity.
TELvrequired = Required leaving evaporator water outlet temperature to maintain rated capacity.
TELvrated = Rated leaving evaporator water outlet temperature at rated capacity.
TempCondIn − TempCondInDesign
∆Temp = − (TempEvapOut − TempEvapOutDesign) (1.54)
TempRiseCoefficient
TempCondIn = Temperature entering the condenser (water or air temperature depending on con-
denser type).
TempCondInDesign = Design Condenser Inlet Temperature from User input above.
TempEvapOut = Temperature leaving the evaporator.
TempEvapOutDesign = Design Chilled Water Outlet Temperature from User input above.
TempRiseCoefficient = User Input from above.
The following three fields contain the coefficients for the quadratic equation.
The following three fields contain the coefficients for the quadratic equation.
1.23.6.1.39 Field: Heat Recovery Inlet High Temperature Limit Schedule Name
This field is optional. It can be used to control heat recovery operation of the chiller. The schedule
named here should contain temperature values, in C, that describe an upper limit for the return fluid
temperatures entering the chiller at the heat recovery inlet node. If the fluid temperature is too
high, then the heat recovery will not operate. This is useful to restrict the chiller lift from becoming
too high and to avoid overheating the hot water loop. This limit can be used with or without the
alternate control using leaving setpoint that is set in the next field.
Chiller:Electric ,
Big Chiller , !- Chiller Name
WaterCooled , !- Condenser Type
100000 , !- Nominal Capacity {W}
2.75, !- COP
Big Chiller Inlet Node , !- Chilled Water Inlet Node Name
Big Chiller Outlet Node , !- Chilled Water Outlet Node Name
Big Chiller Condenser Inlet Node , !- Condenser Inlet Node Name
Big Chiller Condenser Outlet Node , !- Condenser Outlet Node Name
.15, !- Minimum Part Load Ratio
1.0, !- Maximum Part Load Ratio
.65, !- Optimum Part Load Ratio
29.44 , !- Design Condenser Inlet Temperature {C}
2.682759 , !- Temperature Rise Coefficient
6.667 , !- Design Chilled Water Outlet Temperature {C}
0.0011 , !- Design Chilled Water Flow Rate {m3/s}
0.0005 , !- Design Condenser Water Flow Rate {m3/s}
0.94483600 , !- Coefficient 1 of Capacity Ratio Curve
-.05700880 , !- Coefficient 2 of Capacity Ratio Curve
-.00185486 , !- Coefficient 3 of Capacity Ratio Curve
1.907846 , !- Coefficient 1 of Power Ratio Curve
-1.20498700 , !- Coefficient 2 of Power Ratio Curve
0.26346230 , !- Coefficient 3 of Power Ratio Curve
0.03303 , !- Coefficient 1 of Full Load Ratio Curve
0.6852 , !- Coefficient 2 of Full Load Ratio Curve
0.2818 , !- Coefficient 3 of Full Load Ratio Curve
5, !- Chilled Water Outlet Temperature Lower Limit {C}
VariableFlow; !- Chiller Flow Mode
Chiller:Electric ,
Big Chiller , !- Chiller Name
AirCooled , !- Condenser Type
100000 , !- Nominal Capacity {W}
2.58, !- COP
Big Chiller Inlet Node , !- Chilled Water Inlet Node Name
Big Chiller Outlet Node , !- Chilled Water Outlet Node Name
Big Chiller Condenser Inlet Node , !- Condenser Inlet Node Name
Big Chiller Condenser Outlet Node , !- Condenser Outlet Node Name
.05, !- Minimum Part Load Ratio
1.0, !- Maximum Part Load Ratio
.65, !- Optimum Part Load Ratio
35.0, !- Design Condenser Inlet Temperature {C}
2.778 , !- Temperature Rise Coefficient
6.67, !- Design Chilled Water Outlet Temperature {C}
0.0011 , !- Design Chilled Water Flow Rate {m3/s}
0.002 , !- Design Condenser Water Flow Rate {m3/s}
0.9949 , !- Coefficient 1 of Capacity Ratio Curve
-0.045954 , !- Coefficient 2 of Capacity Ratio Curve
-0.0013543 , !- Coefficient 3 of Capacity Ratio Curve
2.333 , !- Coefficient 1 of Power Ratio Curve
-1.975, !- Coefficient 2 of Power Ratio Curve
0.6121 , !- Coefficient 3 of Power Ratio Curve
0.03303 , !- Coefficient 1 of Full Load Ratio Curve
0.6852 , !- Coefficient 2 of Full Load Ratio Curve
1.23. GROUP – PLANT EQUIPMENT 841
OutdoorAir:Node ,
Big Chiller Condenser Inlet Node , !- Node Name
-1.0; !- Height Above Ground {m}
Chiller:Electric ,
Big Chiller , !- Name
EvaporativelyCooled , !- Condenser Type
100000 , !- Nominal Capacity {W}
2.58, !- Nominal COP
Big Chiller Inlet Node , !- Chilled Water Inlet Node Name
Big Chiller Outlet Node , !- Chilled Water Outlet Node Name
Big Chiller Condenser Inlet Node , !- Condenser Inlet Node Name
Big Chiller Condenser Outlet Node , !- Condenser Outlet Node Name
0.05, !- Minimum Part Load Ratio
1.0, !- Maximum Part Load Ratio
0.65, !- Optimum Part Load Ratio
35.0, !- Design Condenser Inlet Temperature {C}
2.778 , !- Temperature Rise Coefficient
6.67, !- Design Chilled Water Outlet Temperature {C}
0.0011 , !- Design Chilled Water Flow Rate {m3/s}
0.002 , !- Design Condenser Water Flow Rate {m3/s}
0.9949 , !- Coefficient 1 of Capacity Ratio Curve
-0.045954 , !- Coefficient 2 of Capacity Ratio Curve
-0.0013543 , !- Coefficient 3 of Capacity Ratio Curve
2.333 , !- Coefficient 1 of Power Ratio Curve
-1.975, !- Coefficient 2 of Power Ratio Curve
0.6121 , !- Coefficient 3 of Power Ratio Curve
0.03303 , !- Coefficient 1 of Full Load Ratio Curve
0.6852 , !- Coefficient 2 of Full Load Ratio Curve
0.2818 , !- Coefficient 3 of Full Load Ratio Curve
5, !- Chilled Water Outlet Temperature Lower Limit {C}
VariableFlow , !- Chiller Flow Mode
, !- Design Heat Recovery Water Flow Rate {m3/s}
, !- Heat Recovery Inlet Node Name
, !- Heat Recovery Outlet Node Name
, !- Sizing Factor
450, !- Basin Heater Capacity {W/K}
3, !- Basin Heater Setpoint Temperature {C}
Basin heater sch; !- Basin Heater Operating Schedule Name
OutdoorAir:Node ,
Big Chiller Condenser Inlet Node , !- Name
-1.0; !- Height Above Ground {m}
Chiller:Electric ,
Big Chiller , !- Chiller Name
WaterCooled , !- Condenser Type
25000 , !- Nominal Capacity {W}
2.75, !- COP
Big Chiller Inlet Node , !- Chilled Water Inlet Node Name
Big Chiller Outlet Node , !- Chilled Water Outlet Node Name
Big Chiller Condenser Inlet Node , !- Condenser Inlet Node Name
Big Chiller Condenser Outlet Node , !- Condenser Outlet Node Name
.15, !- Minimum Part Load Ratio
1.0, !- Maximum Part Load Ratio
.65, !- Optimum Part Load Ratio
29.44 , !- Design Condenser Inlet Temperature {C}
2.682759 , !- Temperature Rise Coefficient
6.667 , !- Design Chilled Water Outlet Temperature {C}
842 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.23.6.2 Outputs
Air-cooled or Evap-cooled:
Evap-cooled:
Water-cooled:
HeatRecovery:
These chiller output variables are defined above under “Generic Chiller Outputs.”
1.23.7 Chiller:Electric:EIR
This chiller model is the empirical model used in the DOE-2.1 building energy simulation program.
The model uses performance information at reference conditions along with three curve fits for cooling
capacity and efficiency to determine chiller operation at off-reference conditions. Chiller performance
curves can be generated by fitting manufacturer’s catalog data or measured data. Performance curves
for more than 160 chillers, including the default DOE-2.1E reciprocating and centrifugal chillers, are
provided in the EnergyPlus Reference DataSets (Chillers.idf and AllDataSets.idf).
Note: Chiller:Electric:EIR objects and their associated performance curve objects are developed
using performance information for a specific chiller and should normally be used together for an
EnergyPlus simulation. Changing the object input values, or swapping performance curves between
chillers, should be done with caution.
1.23.7.1 Inputs
rates specified above. The biquadratic curve should be valid for the range of water temperatures
anticipated for the simulation.
1.23.7.1.10 Field: Electric Input to Cooling Output Ratio Function of Part Load
Ratio Curve Name
The name of a quadratic performance curve (ref: Performance Curves) that parameterizes the vari-
ation of the energy input ratio (EIR) as a function of the part-load ratio (EIRfTPLR). The EIR is
the inverse of the COP, and the part-load ratio is the actual cooling load divided by the chiller’s
available cooling capacity. This curve is generated by dividing the operating electric input power by
the available full-load capacity (do not divide by load) at the specific operating temperatures. The
curve output should decrease from 1 towards 0 as part-load ratio decreases from 1 to 0. The output
of this curve is multiplied by the reference full-load EIR (inverse of the reference COP) and the En-
ergy Input to Cooling Output Ratio Function of Temperature Curve to give the EIR at the specific
temperatures and part-load ratio at which the chiller is operating. This curve should have a value
of 1.0 when the part-load ratio equals 1.0. An ideal chiller with the same efficiency at all part-load
ratio’s would use a performance curve that has a value of 0 when the part-load ratio equals 0 (i.;e.,
a line connecting 0,0 and 1,1 when plotted as EIRfTPLR versus PLR), however, actual systems can
have part-load EIR’s slightly above or below this line (i.e., part-load efficiency often differs from
rated efficiency). The quadratic curve should be valid for the range of part-load ratios anticipated
for the simulation.
This numeric input represents the fraction of compressor electrical energy consumption that must be
rejected by the condenser. Enter a value of 1.0 when modeling hermetic chillers. For open chillers,
enter the compressor motor efficiency. This value must be greater than 0.0 and less than or equal to
1.0, with a default value of 1.0.
Rate and Reference Condenser Water Flow Rate. Sizing Factor allows the user to size a component
to meet part of the design load while continuing to use the autosizing feature.
1.23.7.1.32 Field: Heat Recovery Inlet High Temperature Limit Schedule Name
This field is optional. It can be used to control heat recovery operation of the chiller. The schedule
named here should contain temperature values, in C, that describe an upper limit for the return fluid
temperatures entering the chiller at the heat recovery inlet node. If the fluid temperature is too
high, then the heat recovery will not operate. This is useful to restrict the chiller lift from becoming
too high and to avoid overheating the hot water loop. This limit can be used with or without the
alternate control using leaving setpoint that is set in the next field.
1.23. GROUP – PLANT EQUIPMENT 849
!
! Curve set (3 Curves):
!
! Cooling Capacity Function of Temperature Curve for open or hermetic water -cooled centrifugal
chillers
! x = Leaving Chilled Water Temperature and y = Entering Condenser Water Temperature
! Same as DOE -2.1E HERM -CENT -CAP -FT (CCAPT3) and OPEN -CENT -CAP -FT (CCAPT1)
Curve:Biquadratic ,
DOE -2 Centrifugal /5.50 COP CAPFT , !- Name
0.257896E+00, !- Coefficient1 Constant
850 CHAPTER 1. INPUT-OUTPUT REFERENCE
0.389016E-01, !- Coefficient2 x
-0.217080E-03, !- Coefficient3 x**2
0.468684E-01, !- Coefficient4 y
-0.942840E-03, !- Coefficient5 y**2
-0.343440E-03, !- Coefficient6 x*y
5.0, !- Minimum Value of x
10.0, !- Maximum Value of x
24.0, !- Minimum Value of y
35.0; !- Maximum Value of y
!
! Energy Input to Cooling Output Ratio Function of Temperature Curve for open or hermetic water -
cooled centrifugal chillers
! x = Leaving Chilled Water Temperature and y = Entering Condenser Water Temperature
! Same as DOE -2.1E HERM -CENT -EIR -FT (EIRT3) and OPEN -CENT -EIR -FT (EIRT1)
Curve:Biquadratic ,
DOE -2 Centrifugal /5.50 COP EIRFT , !- Name
0.933884E+00, !- Coefficient1 Constant
-0.582120E-01, !- Coefficient2 x
0.450036E-02, !- Coefficient3 x**2
0.243000E-02, !- Coefficient4 y
0.486000E-03, !- Coefficient5 y**2
-0.121500E-02, !- Coefficient6x*y
5.0, !- Minimum Value of x
10.0, !- Maximum Value of x
24.0, !- Minimum Value of y
35.0; !- Maximum Value of y
!
! Energy Input to Cooling Output Ratio Function of Part Load Ratio Curve for open or hermetic
water -cooled centrifugal chillers
! x = Part Load Ratio (load/capacity)
! Same as DOE -2.1E HERM -CENT -EIR -FPLR (EIRPLR3) and OPEN -CENT -EIR -FPLR (EIRPLR1)
Curve:Quadratic ,
DOE -2 Centrifugal /5.50 COP EIRFPLR , !- Name
0.222903 , !- Coefficient1 Constant
0.313387 , !- Coefficient2 x
0.463710 , !- Coefficient3 x**2
0.0, !- Minimum Value of x
1.0; !- Maximum Value of x
1.23.7.2 Outputs
– Zone,Meter,HeatRejection:EnergyTransfer [J]
– HVAC,Average,Chiller Part Load Ratio []
– HVAC,Average,Chiller Cycling Ratio []
– HVAC,Average,Chiller False Load Heat Transfer Rate [W]
– HVAC,Sum,Chiller False Load Heat Transfer Energy [J]
Air-cooled or Evap-cooled:
Air-cooled or Evap-cooled reported only when the condenser fan power ratio input field is greater
than 0:
Evap-cooled:
Water-cooled:
HeatRecovery:
Most of these chiller output variables are defined above under “Generic Chiller Outputs.” Output
variables not described above are discussed here.
852 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.23.8 Chiller:Electric:ReformulatedEIR
This chiller model, developed through the CoolToolsTM project sponsored by Pacific Gas and Electric
Company (PG&E), is an empirical model similar to EnergyPlus’ Chiller:Electric:EIR model. The
model uses performance information at reference conditions along with three curve fits for cooling
capacity and efficiency to determine chiller operation at off-reference conditions. The model has the
same capabilities as the Chiller:Electric:EIR model, but can potentially provide significant accuracy
improvement over the Chiller:Electric:EIR model for variable-speed compressor drive and variable
condenser water flow applications. Chiller performance curves can be generated by fitting manufac-
turer’s catalog data or measured data. Performance curves developed from manufacturer’s perfor-
mance data are provided in the EnergyPlus Reference DataSets (Chillers.idf and AllDataSets.idf).
This chiller model can be used to predict the performance of various chiller types (e.g., reciprocating,
screw, scroll, and centrifugal) with water-cooled condensers.
The main difference between this model and the Chiller:Electric:EIR model is the condenser fluid
temperature used in the associated performance curves: the Chiller:Electric:ReformulatedEIR model
uses the LEAVING condenser water temperature while the Chiller:Electric:EIR model uses the EN-
TERING condenser water temperature.
Note: Chiller:Electric:Reformulated EIR objects and their associated performance curve objects are
developed using performance information for a specific chiller and should almost always be used
together for an EnergyPlus simulation. Changing the object input values, or swapping performance
curves between chillers, should be done with extreme caution. For example, if the user wishes to
model a chiller size that is different from the reference capacity, it is highly recommended that the
reference flow rates be scaled proportionately to the change in reference capacity. Although this
model can provide more accurate prediction than the Chiller:Electric:EIR model, it requires more
performance data to develop the associated performance curves (at least 12 points from full-load
performance and 7 points from part-load performance).
1.23.8.1 Inputs
This numeric field contains the chiller’s coefficient of performance. This value should not include
energy use due to pumps or cooling tower fans. This COP should be at the reference temperatures
and water flow rates defined below.
1.23.8.1.10 Field: Electric Input to Cooling Output Ratio Function of Part Load
Ratio Curve Type
This choice field determines which type of the Electric Input to Cooling Output Ratio Function
of Part Load Ratio Curve is used in the chiller modeling. Two curve types are available: (1) Type
LeavingCondenserWaterTemperature is based on the leaving condenser water temperature. (2) Type
Lift is based on the normalized lift, which is the temperature difference between the leaving condenser
water temperature and the leaving evaporator water temperature.
1.23.8.1.11 Field: Electric Input to Cooling Output Ratio Function of Part Load
Ratio Curve Name
The name of performance curve (ref: Performance Curves) that parameterizes the variation of the
energy input ratio (EIR) as a function of the leaving condenser water temperature and the part-load
ratio (EIRfTPLR). The form of this curve is based on the input for Electric Input to Cooling Output
Ratio Function of Part Load Ratio Curve Type.
For the type of LeavingCondenserWaterTemperature, the curve object type should be Curve:Bicubic
or Table:Lookup that parameterizes the variation of the energy input to cooling output ratio (EIR)
as a function of the leaving chilled water temperature and the leaving condenser water temperature.
For the type of Lift, the curve object type should be Curve:ChillerPartLoadWithLift or Table:Lookup
that parameterizes the variation of EIR as a function of the normalized fractional Lift, normalized
Tdev and the PLR. Tdev is the difference between Leaving Chilled Water Temperature and Ref-
erence Chilled Water Temperature. Lift is the difference between the Leaving Condenser Water
Temperature and Leaving Chilled Water Temperature. The EIR is the inverse of the COP, and the
part-load ratio is the actual cooling load divided by the chiller’s available cooling capacity. This
curve is generated by dividing the operating electric input power by the available full-load capacity
(do not divide by load) at the specific operating temperatures. The curve output should decrease
from 1 towards 0 as part-load ratio decreases from 1 to 0. The output of this curve is multiplied by
the reference full-load EIR (inverse of the reference COP) and the Energy Input to Cooling Output
Ratio Function of Temperature Curve to give the EIR at the specific temperatures and part-load
ratio at which the chiller is operating. This curve should have a value of 1.0 at the reference leaving
condenser water temperature with the part-load ratio equal to 1.0. An ideal chiller with the same
efficiency at all part-load ratio’s would use a performance curve that has a value of 0 when the
part-load ratio equals 0 (i.;e., a line connecting 0,0 and 1,1 when plotted as EIRfTPLR versus PLR),
however, actual systems can have part-load EIR’s slightly above or below this line (i.e., part-load
efficiency often differs from rated efficiency). The bicubic curve should be valid for the range of
condenser water temperatures and part-load ratios anticipated for the simulation (otherwise the
program issues warning messages).
Note: Although a bicubic curve requires 10 coefficients (ref. Curve:Bicubic), coefficients 7, 9 and 10
are typically not used in the performance curve described here and should be entered as 0 unless
sufficient performance data and regression accuracy exist to justify the use of these coefficients.
Additionally, coefficients 2, 3, and 6 should not be used unless sufficient temperature data is available
to accurately define the performance curve (i.e., negative values may result from insufficient data).
This numeric input represents the fraction of compressor electrical energy consumption that must be
rejected by the condenser. Enter a value of 1.0 when modeling hermetic chillers. For open chillers,
enter the compressor motor efficiency. This value must be greater than 0.0 and less than or equal to
1.0, with a default value of 1.0.
1.23.8.1.28 Field: Heat Recovery Inlet High Temperature Limit Schedule Name
This field is optional. It can be used to control heat recovery operation of the chiller. The schedule
named here should contain temperature values, in C, that describe an upper limit for the return fluid
temperatures entering the chiller at the heat recovery inlet node. If the fluid temperature is too
high, then the heat recovery will not operate. This is useful to restrict the chiller lift from becoming
too high and to avoid overheating the hot water loop. This limit can be used with or without the
alternate control using leaving setpoint that is set in the next field.
Chiller:Electric:ReformulatedEIR ,
Main Chiller , !- Chiller Name
50000 , !- Reference Capacity {W}
3.99, !- Reference COP
6.67, !- Reference Leaving Chilled Water Temperature {C}
35.0, !- Reference Leaving Condenser Water Temperature {C}
0.00898 , !- Reference Chilled Water Flow Rate {m3/s}
0.01122 , !- Reference Condenser Water Flow Rate {m3/s}
Main Chiller RecipCapFT , !- Cooling Capacity Function of Temperature Curve
Main Chiller RecipEIRFT , !- Electric Input to Cooling Output Ratio Function of
Temperature Curve
LeavingCondenserWaterTemperature !- Electric Input to Cooling Output Ratio Function of Part
Load Ratio Curve Type
Main Chiller RecipEIRFPLR , !- Electric Input to Cooling Output Ratio Function of Part
Load Ratio Curve Name
0.01, !- Minimum Part Load Ratio
1, !- Maximum Part Load Ratio
1, !- Optimum Part Load Ratio
0.07, !- Minimum Unloading Ratio
Main Chiller ChW Inlet , !- Chilled Water Side Inlet Node
Main Chiller ChW Outlet , !- Chilled Water Side Outlet Node
Main Chiller Cnd Inlet , !- Condenser Side Inlet Node
Main Chiller Cnd Outlet , !- Condenser Side Outlet Node
1, !- Fraction of Compressor Electric Power Rejected by
Condenser
2, !- Leaving Chilled Water Lower Temperature Limit {C}
ConstantFlow; !- Chiller Flow Mode
1.23. GROUP – PLANT EQUIPMENT 859
Curve:Biquadratic ,
Main Chiller RecipCapFT , !- Name
0.958546443 , !- Coefficient1 Constant
0.035168695 , !- Coefficient2 x
0.000124662 , !- Coefficient3 x\*\*2
-0.00274551 , !-Coefficient4y
-0.00005000 , !-Coefficient5y \*\*2
-0.00017234 , !-Coefficient6x \*y
5.00, !- Minimum Value of x
10.0, !- Maximum Value of x
20.00 , !- Minimum Value of y
40.94; !- Maximum Value of y
Curve:Biquadratic ,
Main Chiller RecipEIRFT , !- Name
0.732700123 , !- Coefficient1 Constant
-0.00834360 , !- Coefficient2 x
0.000638530 , !- Coefficient3 x\*\*2
-0.00303753 , !-Coefficient4y
0.000484952 , !-Coefficient5y \*\*2
-0.00083584 , !-Coefficient6x \*y
5.00, !- Minimum Value of x
10.0, !- Maximum Value of x
20.00 , !- Minimum Value of y
40.94; !- Maximum Value of y
! Energy Input to Cooling Output Ratio Function of Part Load Ratio Curve
! x = Leaving Condenser water Temperature and y = Part Load Ratio
Curve:Bicubic ,
Main Chiller RecipEIRFPLR , !- Name
0.070862846 , !- Coefficient1 Constant
0.002787560 , !- Coefficient2 x
-0.00000891 , !- Coefficient3 x\*\*2
0.230973399 , !-Coefficient4y
1.250442176 , !-Coefficient5y \*\*2
-0.00216102 , !-Coefficient6x \*y
0.000000 , !-Coefficient7x \*\*3
-0.56300936 , !-Coefficient8y \*\*3
0.000000 , !-Coefficient9x \*\*2\*y
0.000000 , !-Coefficient10x \*y\*\*2
20.00 , !- Minimum Value of x
40.94 , !- Maximum Value of x
0.01, !- Minimum Value of y
1.0; !- Maximum Value of y
1.23.8.2 Outputs
The output variables for Chiller:Electric:ReformulatedEIR are the same as the output variables for
Chiller:Electric:EIR (ref. Electric EIR Chiller Outputs). except for the Chiller Condenser Fan
Electricity Rate and Energy reports
1.23.9 Chiller:EngineDriven
1.23.9.1 Inputs
This alpha field contains the identifying name for the engine driven chiller.
T CEntrequired − T CEntrated
(1.56)
T ELvrequired − T ELvrated
where:
TCEntrequired = Required entering condenser air or water temperature to maintain rated capacity.
TCEntrated = Rated entering condenser air or water temperature at rated capacity.
TELvrequired = Required leaving evaporator water outlet temperature to maintain rated capacity.
TELvrated = Rated leaving evaporator water outlet temperature at rated capacity.
The following three fields contain the coefficients for the quadratic equation.
where PLR is the Part Load Ratio from the Chiller. The Part Load Based Fuel Input Curve
determines the ratio of fuel energy per unit time (J/s) / cooling load (W). This is illustrated by the
logic block in the Engine Driven Chiller algorithm.
IF (PartLoadRat = = 0) THEN
EngineDrivenFuelEnergy = 0
ELSE
ClngLoadFuelRat = CurveValue( EngineDrivenChiller(ChillerNum)%ClngLoadtoFuelCurve , PartLoadRat )
EngineDrivenFuelEnergy = QEvaporator / ClngLoadFuelRat
END IF
T CEntrequired − T CEntrated
(1.65)
T ELvrequired − T ELvrated
The following two fields contain the coefficients for the equation.
0. The basin heater operates when scheduled on and the outdoor air dry-bulb temperature is below
the set point temperature described in the previous field. If this field is left blank, the basin heater
is available to operate throughout the simulation. Regardless of this schedule, the basin heater may
only operate when the chiller is off.
Chiller:EngineDriven ,
Central Chiller , !- Chiller Name
WaterCooled , !- Condenser Type
autosize , !- Nominal Capacity {W}
2.75, !- COP
Central Chiller Inlet Node , !- Chilled Water Inlet Node Name
Central Chiller Outlet Node , !- Chilled Water Outlet Node Name
Central Chiller Condenser Inlet Node , !- Condenser Inlet Node Name
Central Chiller Condenser Outlet Node , !- Condenser Outlet Node Name
0.0, !- Minimum Part Load Ratio
1.0, !- Maximum Part Load Ratio
.65, !- Optimum Part Load Ratio
35.0, !- Design Condenser Inlet Temperature {C}
2.778 , !- Temperature Rise Coefficient
6.67, !- Design Chilled Water Outlet Temperature {C}
autosize , !- Design Chilled Water Flow Rate {m3/s}
autosize , !- Design Condenser Water Flow Rate {m3/s}
0.9949 , !- Coefficient 1 of Capacity Ratio Curve
-0.045954 , !- Coefficient 2 of Capacity Ratio Curve
-0.0013543 , !- Coefficient 3 of Capacity Ratio Curve
2.333 , !- Coefficient 1 of Power Ratio Curve
-1.975, !- Coefficient 2 of Power Ratio Curve
0.6121 , !- Coefficient 3 of Power Ratio Curve
0.03303 , !- Coefficient 1 of Full Load Ratio Curve
0.6852 , !- Coefficient 2 of Full Load Ratio Curve
0.2818 , !- Coefficient 3 of Full Load Ratio Curve
5, !- Chilled Water Outlet Temperature Lower Limit {C}
Fuel Use Curve , !- the Fuel Use Curve
Jacket Heat Recovery Curve , !- the Recovery Jacket Heat curve
Lube Heat Recovery Curve ,!- the Recovery Lube Heat curve
Total Exhaust Energy Curve , !- the Total Exhaust Energy curve
Exhaust Temperature Curve , !- the Exhaust Temperature curve
0.01516 , !- Coefficient1 of UA curve
0.9, !- Coefficient2 of UA curve
0.00063 , !- Maximum Exhaust Flow per W of Power Output {(kg/s)/W}
150, !- Design Minimum Exhaust temp. (Steam Saturation Temperature) {C}
DIESEL , !- Fuel Type
45500 , !- Fuel Heating Value {kJ/kg}
0.0, !- Design heat recovery water flow rate {m3/s}
, !- Heat Recovery Inlet Node Name
, !- Heat Recovery Outlet Node Name
VariableFlow , !- Chiller Flow Mode
60.0; !- Maximum Temp for Heat Recovery. This sets max availability {C}
1.23.9.2 Outputs
868 CHAPTER 1. INPUT-OUTPUT REFERENCE
Air-cooled or Evap-cooled:
– HVAC,Average,Chiller Condenser Inlet Temperature [C]
Evap-cooled:
Water-cooled:
These chiller output variables are defined above under “Generic Chiller Outputs.”
1.23.10 Chiller:CombustionTurbine
This chiller model is the empirical model from the Building Loads and System Thermodynamics
(BLAST) program. Chiller performance curves are generated by fitting catalog data to third order
polynomial equations. Three sets of coefficients are required.
1.23.10.1 Inputs
T CEntrequired − T CEntrated
(1.66)
T ELvrequired − T ELvrated
where:
TCEntrequired = Required entering condenser air or water temperature to maintain rated capacity.
TCEntrated = Rated entering condenser air or water temperature at rated capacity.
TELvrequired = Required leaving evaporator water outlet temperature to maintain rated capacity.
TELvrated = Rated leaving evaporator water outlet temperature at rated capacity.
F uelEnergyInput = P Load∗(F IC1 +F IC2 RLoad+F IC3 RLoad2 )∗(T BF IC1 +T BF IC2 ATair +T BF IC3 ATair
2
)
(1.69)
The following three fields contain the coefficients for the quadratic equation.
where FIC represents the Fuel Input Curve Coefficients, TBFIC represents the Temperature Based
Fuel Input Curve Coefficients, Rload is the Ratio of Load to Combustion Turbine Engine Capacity,
and ATair is the difference between the current ambient and design ambient temperatures.
The following three fields contain the coefficients for the fuel input curve.
where GTCapacity is the Combustion Turbine Engine Capacity, and ATair is the difference between
the current ambient and design ambient temperatures.
conjunction with the Basin Heater Setpoint Temperature described in the following field. The basin
heater electric power is equal to this field multiplied by the difference between the basin heater set
point temperature and the outdoor dry-bulb temperature. The basin heater only operates when the
chiller is off, regardless of the basin heater schedule described below. The basin heater capacity must
be greater than or equal to zero, with a default value of zero if this field is left blank.
Chiller:CombustionTurbine ,
Big Chiller , !- Chiller Name
WaterCooled , !- Condenser Type
30000 , !- Nominal Capacity {W}
2.75, !- COP
Big Chiller Inlet Node , !- Chilled Water Inlet Node Name
Big Chiller Outlet Node , !- Chilled Water Outlet Node Name
Big Chiller Condenser Inlet Node , !- Condenser Inlet Node Name
Big Chiller Condenser Outlet Node , !- Condenser Outlet Node Name
.15, !- Minimum Part Load Ratio
1.0, !- Maximum Part Load Ratio
.65, !- Optimum Part Load Ratio
35.0, !- Design Condenser Inlet Temperature {C}
2.778 , !- Temperature Rise Coefficient
6.67, !- Design Chilled Water Outlet Temperature {C}
1.23. GROUP – PLANT EQUIPMENT 879
1.23.10.2 Outputs
Air-cooled or Evap-cooled:
Evap-cooled:
Water-cooled:
These chiller output variables are defined above under “Generic Chiller Outputs.” The Fuel Type
input will determine which fuel type is displayed in the output. In this example with the user choice
of NaturalGas, you will have Gas Consumption.
1.23.11 ChillerHeater:Absorption:DirectFired
This chiller is a direct fired absorption chiller-heater which is modeled using performance curves
similar to the equivalent chiller in DOE-2.1E. This type of chiller is unusual for EnergyPlus, because
it may be used in the same plant on both a chilled water supply branch and a hot water supply
branch. The chiller has six node connections for chilled water, condenser water, and hot water, and
can provide simultaneous heating and cooling. During simultaneous operation, the heating capacity
is reduced as the cooling load increases (for more details see below). Some equations are provided
below to help explain the function of the various performance curves. For a detailed description of
the algorithm and how the curves are used in the calculations, please see the Engineering Reference.
1.23. GROUP – PLANT EQUIPMENT 881
1.23.11.1 Inputs
CoolFuelInput =
(1.73)
AvailCoolCap · RunFrac · CFIR · CFIRfT(Tcw,l , Tcond ) · CFIRfPLR(CPLR)
1.23.11.1.24 Field: Fuel Input to Cooling Output Ratio Function of Part Load
Ratio Curve Name
The CFIRfPLR curve represents the fraction of the fuel input to the chiller as the load the chiller
varies but the operating temperatures remain at the design values. The curve is normalized so that
at full load the value of the curve should be 1.0. The curve is usually linear or quadratic. The
cooling fuel input to the chiller is computed as follows:
884 CHAPTER 1. INPUT-OUTPUT REFERENCE
CoolElectricPower =
(1.74)
NomCoolCap · RunFrac · CEIR · CEIRfT(Tcw,l , Tcond ) · CEIRfPLR(CPLR)
The HeatCapFCool curve represents how the heating capacity of the chiller varies with cooling
capacity when the chiller is simultaeous heating and cooling. The curve is normalized so an input of
1.0 represents the nominal cooling capacity and an output of 1.0 represents the full heating capacity
(see the Heating to Cooling Capacity Ratio input) The curve is usually linear or quadratic. The
available heating capacity is computed as follows:
1.23.11.1.28 Field: Fuel Input to Heat Output Ratio During Heating Only Op-
eration Curve Name
When the chiller is operating as only a heater, the curve is used to represent the fraction of fuel
used as the heating load varies. It is normalized so that a value of 1.0 is the full available heating
capacity. The curve is usually linear or quadratic and will probably be similar to a boiler curve for
most chillers.
ChillerHeater:Absorption:DirectFired ,
Big Chiller , !- Chiller Name
100000 , !- Nominal Cooling Capacity {W}
0.8, !- Heating to Cooling capacity ratio
0.97, !- Fuel Input to Cooling Output Ratio
1.25, !- Fuel Input to Heating Output Ratio
0.01, !- Electric Input to Cooling Output Ratio
0.005 , !- Electric Input to Heating Output Ratio
Big Chiller Inlet Node , !- Chilled Water Side Inlet Node Name
Big Chiller Outlet Node , !- Chilled Water Side Outlet Node Name
Big Chiller Condenser Inlet Node , !- Condenser Side Inlet Node Name
Big Chiller Condenser Outlet Node , !- Condenser Side Outlet Node Name
Purchased Heat Inlet Node , !- Hot Water Side Inlet Node Name
Purchased Heat Outlet Node , !- Hot Water Side Outlet Node Name
0.000001 , !- Minimum Part Load Ratio
886 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.23.11.2 Outputs
The following three outputs are only available for water-cooled chillers
The “Chiller” output variables are defined above under “Generic Chiller Outputs.” The specific
“Direct Fired Absorption Chiller” output variables and exceptions to the generic outputs are defined
below.
1.23.12 ChillerHeater:Absorption:DoubleEffect
This chiller is an exhaust fired absorption chiller-heater which is modeled using performance curves
similar to the direct fired absorption chiller in DOE-2.1E. The model uses the exhaust gas output
from MicroTurbine. This type of chiller is unusual for EnergyPlus, because it may be used in the
same plant on both a chilled water supply branch and a hot water supply branch. The chiller has six
node connections for chilled water, condenser water, and hot water, and can provide simultaneous
heating and cooling. During simultaneous operation, the heating capacity is reduced as the cooling
load increases (for more details see below). Some equations are provided below to help explain the
function of the various performance curves. For a detailed description of the algorithm and how the
curves are used in the calculations, please see the Engineering Reference.
1.23.12.1 Inputs
The HeatCapFCPLR curve represents how the heating capacity of the chiller varies with cooling
capacity when the chiller is simultaneously heating and cooling. The curve is normalized so an
input of 1.0 represents the nominal cooling capacity and an output of 1.0 represents the full heating
capacity (see the Heating to Cooling Capacity Ratio input) The curve is usually linear or quadratic.
The available heating capacity is computed as follows:
1.23.12.1.28 Field: Thermal Energy Input to Heat Output Ratio During Heating
Only Operation Curve Name
When the chiller is operating as only a heater, the curve is used to represent the fraction of Thermal
Energy used as the heating load varies. It is normalized so that a value of 1.0 is the full available
heating capacity. The curve is usually linear or quadratic and will probably be similar to a boiler
curve for most chillers.
The heating Thermal Energy Input to the chiller is computed as follows:
BoilerLoad
T heoreticalF uelU se = (1.82)
N ominalT hermalEf f iciency
alpha field contains the keyword for the type of temperature input variable, , either Entering-
CondenserTemperature, or LeavingCondenserTemperature. The default is EnteringCon-
denserTemperature.
ChillerHeater:Absorption:DoubleEffect ,
Exh Chiller , !- Chiller Name
100000 , !- Nominal Cooling Capacity {W}
0.8, !- Heating to Cooling capacity ratio
0.97, !- Thermal Energy Input to Cooling Output Ratio
1.25, !- Thermal Energy Input to Heating Output Ratio
0.01, !- Electric Input to Cooling Output Ratio
0.005 , !- Electric Input to Heating Output Ratio
Exh Chiller Inlet Node , !- Chilled Water Side Inlet Node Name
Exh Chiller Outlet Node , !- Chilled Water Side Outlet Node Name
Exh Chiller Condenser Inlet Node , !- Condenser Side Inlet Node Name
Exh Chiller Condenser Outlet Node , !- Condenser Side Outlet Node Name
Exh Chiller Heating Inlet Node , !- Hot Water Side Inlet Node Name
Exh Chiller Heating Outlet Node , !- Hot Water Side Outlet Node Name
0.000001 , !- Minimum Part Load Ratio
1.0, !- Maximum Part Load Ratio
0.6, !- Optimum Part Load Ratio
29, !- Design Entering Condenser Water Temperature {C}
7, !- Design Leaving Chilled Water Temperature {C}
0.0011 , !- Design Chilled Water Flow Rate {m3/s}
1.23. GROUP – PLANT EQUIPMENT 895
1.23.12.2 Outputs
The following three outputs are only available for water-cooled chillers
The “Chiller” output variables are defined above under “Generic Chiller Outputs.” The specific
“Exhaust Fired Absorption Chiller” output variables and exceptions to the generic outputs are
defined below.
1.23.12.2.32 Chiller Heater Source Exhaust Inlet Mass Flow Rate [kg/s]
The exhaust flow rate from the Micro Turbine
1.23.13 Boiler:HotWater
The boiler model calculates the performance of fuel oil, gas and electric boilers. Boiler performance
is based on nominal thermal efficiency. A normailized efficiency performance curve may be used to
more accurately represent the performance of non-electric boilers but is not considered a required
input. When using the normalized efficiency performance curve, if all coefficients are not required
simply set the unused coefficients to 0. For example, an electric boiler could be modeled by setting
the nominal thermal efficiency to a value in the range of 0.96 to 1.0. Coefficient A0 in the normalized
efficiency performance curve would equal 1 and all other coefficients would be set to 0. Coefficients
for other types of non-electric boilers would set a combination of the available coefficents to non-zero
values.
1.23.13.1 Inputs
T heoreticalF uelU se
F uelU sed = (1.83)
N ormalizedBoilerEf f iciencyCurveOutput
Linear → Ef f = A0 + A1 · P LR (1.84)
ratio (PLR). When this type of curve is used, the boiler should operate at (or very near) the design
boiler water outlet temperature. Other curve types may be used when the boiler efficiency is a
function of both PLR and boiler water temperature. Examples of valid single and dual independent
variable equations are shown below. For all curve types PLR is always the x independent variable.
When using 2 independent variables, the boiler outlet water temperature (Toutlet) is always the y
independent variable.
QuadraticLinear → Ef f = A0 +A1 ·P LR+A2 ·P LR2 +A3 ·Tw +A4 ·P LR·Tw +A5 ·P LR2 ·Tw (1.89)
where
Eff = normalized boiler efficiency
PLR = boiler part-load ratio
Tw = boiler water temperature [ºC] ], this can be either entering or leaving temperature depending
on the setting in the previous field
Boiler:HotWater ,
Condensing Boiler , !- Boiler Name
NaturalGas , !- Fuel Type
25000 , !- Nominal Capacity {W}
EnteringBoiler !- Efficiency Curve Temperature Evaluation Variable
0.89, !- Nominal Thermal Efficiency
CondensingBoilerEff , !- Boiler Efficiency Curve Name
0.0021 , !- Max Design Boiler Water Flow Rate {m3/s}
0.10, !- Minimum Part Load Ratio
1.00, !- Maximum Part Load Ratio
1.00, !- Optimum Part Load Ratio
Boiler Inlet Node , !- Boiler Water Inlet Node
Boiler Outlet Node , !- Boiler Water Outlet Node
80, !- Temp Upper Limit Water Outlet {C}
ConstantFlow , !- Boiler Flow Mode
25.0; !- Parasitic Electric Load {W}
Curve:Biquadratic ,
CondensingBoilerEff , !- Name
1.124970374 , !- Coefficient1 Constant
0.014963852 , !- Coefficient2 x
-0.02599835 , !- Coefficient3 x**2
0.0, !-Coefficient4y
-1.40464E-6, !-Coefficient5y **2
-0.00153624 , !- Coefficient6x*y
0.1, !- Minimum Value of x
1.0, !- Maximum Value of x
30.0, !- Minimum Value of y
85.0; !- Maximum Value of y
1.23.13.2 Outputs
Gas:
Propane:
FuelOilNo1:
FuelOilNo2:
Coal:
Diesel:
Gasoline:
OtherFuel1:
OtherFuel2:
1.23.14 Boiler:Steam
The steam boiler model provides a first order approximation of performance for fuel oil, gas and
electric boilers. Boiler performance is based on a “theoretical” boiler efficiency (overall efficiency at
design operating conditions) and a single quadratic fuel use/ part load ratio curve. This single curve
accounts for all combustion inefficiencies and stack losses.
1.23.14.1 Inputs
1.23.14.1.10 Field: Coefficient 1 of Fuel Use Function of Part Load Ratio Curve
1.23.14.1.11 Field: Coefficient 2 of Fuel Use Function of Part Load Ratio Curve
1.23.14.1.12 Field: Coefficient 3 of Fuel Use Function of Part Load Ratio Curve
Boiler:Steam ,
Steam Boiler Plant Boiler , !- Boiler Name
NaturalGas , !- Fuel Type
160000 , !-Maximum Boiler Pressure Pascal
0.8, !- Theoretical Boiler Efficiency
115, !- Max Design Outlet Steam Temp
300000 , !- Nominal Capacity W
0.00001 , !- Minimum Part Load Ratio
1.0, !- Maximum Part Load Ratio
0.2, !- Optimum Part Load Ratio
0.8,!- Coefficient 1 of the fuel use/part load ratio curve
0.1,!- Coefficient 2 of the fuel use/part load ratio curve
0.1,!- Coefficient 3 of the fuel use/part load ratio curve
Steam Boiler Plant Boiler Inlet Node , !- Boiler Steam Inlet Node
Steam Boiler Plant Boiler Outlet Node; !- Plant Loop Outlet Node
Boiler:Steam ,
Steam Boiler Plant Boiler , !- Boiler Name
NaturalGas , !- Fuel Type
160000 , !-Maximum Boiler Pressure Pascal
0.8, !- Theoretical Boiler Efficiency
115, !- Max Design Outlet Steam Temp
autosize , !- Nominal Capacity W
0.00001 , !- Minimum Part Load Ratio
1.0, !- Maximum Part Load Ratio
0.2, !- Optimum Part Load Ratio
0.8,!- Coefficient 1 of the fuel use/part load ratio curve
0.1,!- Coefficient 2 of the fuel use/part load ratio curve
0.1,!- Coefficient 3 of the fuel use/part load ratio curve
Steam Boiler Plant Boiler Inlet Node , !- Boiler Steam Inlet Node
Steam Boiler Plant Boiler Outlet Node; !- Plant Loop Outlet Node
1.23.14.2 Outputs
Gas:
Propane:
FuelOilNo1:
FuelOilNo2:
Coal:
Diesel:
Gasoline:
OtherFuel1:
OtherFuel2:
currently “hardwired” to fluid property R22. FluidProperties:* objects for R-22 must be included
in the idf file. These may be copied from DataSets
FluidPropertiesRefData.idf.
Descriptions and strengths of these two models are available in the following references:
Jin, Hui. 2002. Parameter Estimation Based Models of Water Source Heat Pumps. Phd. Thesis,
Department of Mechanical and Aerospace Engineering, Oklahoma State University. (downloadable
from http://www.hvac.okstate.edu/)
Tang,C. C. 2005. Modeling Packaged Heat Pumps in Quasi-Steady State Energy Simulation Pro-
gram. M.S. Thesis. Department of Mechanical and Aerospace Engineering, Oklahoma State Uni-
versity. (downloadable from http://www.hvac.okstate.edu/)
HeatPump:PlantLoop:EIR:Cooling
HeatPump:PlantLoop:EIR:Heating
Beginning with version 9.1, an EIR-formulated heat pump model was added. This heat pump can
be operated as a water-source object with the source-side connected to another plant loop, or as an
air-source object with the source-side interacting with the outdoor air. This formulation allows the
user to enter curves for specifying the capacity and energy usage in a more generic way, allowing the
curves to be applicable to a wide variety of components. With the original equation fit model, the
curve form was locked in to a specific set of linear coefficients. With the new form, the curve can be
a quadratic function of temperatures, or an even more generic lookup table.
Configuration
The Supply side of the heat pump is usually connected to a Ground Heat Exchanger for a water-
source object. The figure below shows the layout and piping diagram of the water-to-water heat
pump.
First, the equation fit model objects are described. This model has two sets of coefficients, one for
the heating mode and other for the cooling mode.
912 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.23.16 HeatPump:WaterToWater:EquationFit:Cooling
1.23.16.1 Inputs
HeatPump:WaterToWater:EquationFit:Cooling ,
GshpCLG , !- Name
GshpCLG SourceSide Inlet Node , !- Source Side Inlet Node Name
GshpCLG SourceSide Outlet Node , !- Source Side Outlet Node Name
GshpCLG LoadSide Inlet Node , !- Load Side Inlet Node Name
GshpCLG LoadSide Outlet Node , !- Load Side Outlet Node Name
1.89E-03, !- Reference Load Side Flow Rate {m3/s}
1.89E-03, !- Reference Source Side Flow Rate {m3/s}
39890.91 , !- Reference Cooling Capacity {W}
4790.00 , !- Reference Cooling Power Consumption {W}
CoolCapCurve , !- Cooling Capacity Curve Name
CoolPowCurve , !- Cooling Compressor Power Curve Name
8.32, !- Reference Coefficient of Performance
1.0, !- Sizing Factor
GshpHeating; !- Companion Heating Heat Pump Name
Curve:QuadLinear ,
914 CHAPTER 1. INPUT-OUTPUT REFERENCE
Curve:QuadLinear ,
CoolPowCurve , !- Curve Name
-8.59564386 , !- CoefficientC1
0.96265085 , !- CoefficientC2
8.69489229 , !- CoefficientC3
0.02501669 , !- CoefficientC4
-0.20132665 , !- CoefficientC5
-100, !- Minimum Value of w
100, !- Maximum Value of w
-100, !- Minimum Value of x
100, !- Maximum Value of x
0, !- Minimum Value of y
100, !- Maximum Value of y
0, !- Minimum Value of z
100, !- Maximum Value of z
0, !- Minimum Curve Output
38; !- Maximum Curve Output
1.23.16.2 Outputs
This section describes the outputs available for the water to water heat pump, equation fit model;
both cooling and heating.
1.23.17 HeatPump:WaterToWater:EquationFit:Heating
1.23.17.1 Inputs
that the sizing calculations can be coordinated so that the two companion heat pumps get the same
design reference flow rates.
An idf example:
HeatPump:WaterToWater:EquationFit:Heating ,
GshpHeating , !- Name
GshpHeating SourceSide Inlet Node , !- Source Side Inlet Node Name
GshpHeating SourceSide Outlet Node , !- Source Side Outlet Node Name
GshpHeating LoadSide Inlet Node , !- Load Side Inlet Node Name
GshpHeating LoadSide Outlet Node , !- Load Side Outlet Node Name
1.89E-03, !- Reference Load Side Flow Rate {m3/s}
1.89E-03, !- Reference Source Side Flow Rate {m3/s}
39040.92 , !- Reference Heating Capacity {W}
5130.00 , !- Reference Heating Power Consumption {W}
HeatCapCurve , !- Heating Capacity Curve Name
HeatPowCurve , !- Heating Compressor Power Curve Name
7.61, !- Reference Coefficient of Performance
1.0, !- Sizing Factor
GshpCLG; !- Companion Cooling Heat Pump Name
Curve:QuadLinear ,
HeatCapCurve , !- Curve Name
-3.33491153 , !- CoefficientC1
-0.51451946 , !- CoefficientC2
4.51592706 , !- CoefficientC3
0.01797107 , !- CoefficientC4
0.155797661 , !- CoefficientC5
-100, !- Minimum Value of w
100, !- Maximum Value of w
-100, !- Minimum Value of x
100, !- Maximum Value of x
0, !- Minimum Value of y
100, !- Maximum Value of y
0, !- Minimum Value of z
100, !- Maximum Value of z
0, !- Minimum Curve Output
38; !- Maximum Curve Output
Curve:QuadLinear ,
HeatPowCurve , !- Curve Name
-8.93121751 , !- CoefficientC1
8.57035762 , !- CoefficientC2
1.29660976 , !- CoefficientC3
-0.21629222 , !- CoefficientC4
0.033862378 , !- CoefficientC5
-100, !- Minimum Value of w
100, !- Maximum Value of w
-100, !- Minimum Value of x
100, !- Maximum Value of x
0, !- Minimum Value of y
100, !- Maximum Value of y
0, !- Minimum Value of z
100, !- Maximum Value of z
0, !- Minimum Curve Output
38; !- Maximum Curve Output
Next, the parameter estimation model objects are described. This model has two sets of parameters,
one for the heating mode and other for the cooling mode.
1.23.18 HeatPump:WaterToWater:ParameterEstimation:Cooling
1.23.18.1 Inputs
This alpha field contains the identifying name for the ground source heat pump.
1.23.19 HeatPump:WaterToWater:ParameterEstimation:Heating
1.23.19.1 Inputs
1.23.19.2 Outputs
This section describes the outputs available for the water to water heat pump, parameter estimation
model; both cooling and heating.
1.23.20.1 Inputs
HeatPump:PlantLoop:EIR:Heating ,
Heating Coil , !- Name
Heating Coil Load Loop Intermediate Node , !- Load Side Inlet Node Name
Heating Coil Load Loop Supply Outlet Node , !- Load Side Outlet Node Name
WaterSource , ! Condenser Type
Condenser Loop Demand Inlet Node , !- Source Side Inlet Node Name
Condenser Loop Demand Intermediate Node , !- Source Side Outlet Node Name
Cooling Coil , !- Companion Heat Pump Name
0.005 , !- Load Side Design Volume Flow Rate {m3/s}
0.002 , !- Source Side Design Volume Flow Rate {m3/s}
80000 , !- Reference Capacity
3.5, !- Reference COP
, !- Sizing Factor
CapCurveFuncTemp , !- Heating Capacity Modifier Function of Temperature Curve Name
EIRCurveFuncTemp , !- Electric Input to Heating Output Ratio Modifier Function of
Temperature Curve Name
EIRCurveFuncPLR; !- Electric Input to Heating Output Ratio Modifier Function of Part
Load Ratio Curve Name
HeatPump:WaterToWater:EIR:Cooling ,
Cooling Coil , !- Name
Cooling Coil Load Loop Intermediate Node , !- Load Side Inlet Node Name
Cooling Coil Load Loop Supply Outlet Node , !- Load Side Outlet Node Name
WaterSource , !- Condenser Type
Condenser Loop Demand Intermediate Node , !- Source Side Inlet Node Name
Condenser Loop Demand Outlet Node , !- Source Side Outlet Node Name
Heating Coil , !- Companion Heat Pump Name
0.005 , !- Load Side Design Volume Flow Rate {m3/s}
0.003 , !- Source Side Design Volume Flow Rate {m3/s}
75000 , !- Reference Capacity
4.0, !- Reference COP
, !- Sizing Factor
CapCurveFuncTemp2 , !- Heating Capacity Modifier Function of Temperature Curve Name
EIRCurveFuncTemp2 , !- Electric Input to Heating Output Ratio Modifier Function of
Temperature Curve Name
EIRCurveFuncPLR2; !- Electric Input to Heating Output Ratio Modifier Function of Part
Load Ratio Curve Name
1.23.20.2 Outputs
This section describes the outputs available for the water to water heat pump, equation fit model;
both cooling and heating.
BRANCH ,
Heating GshpHeating Branch ,
,
HeatPump:WatertoWater: ParameterEstimatinon:Heating ,
GshpHeating ,
GshpHeating LoadSide Inlet Node ,
GshpHeating LoadSide Outlet Node;
930 CHAPTER 1. INPUT-OUTPUT REFERENCE
BRANCH ,
GshpHeating SourceSide Branch ,
,
HeatPump:WatertoWater: ParameterEstimatinon:Heating ,
GshpHeating ,
GshpHeating SourceSide Inlet Node ,
GshpHeating SourceSide Outlet Node;
3. Add a branch in condenser loop and include its name in the respective splitter and mixer.
! in chilled water loop
1.23.22 DistrictCooling
When the user is not interested in a plant simulation or there is some centralized source of chilled
water, the following object can be used in the input.
1.23.22.1 Inputs
1.23.22.2 Outputs
1.23.23 DistrictHeating
When the user is not interested in a plant simulation or there is some centralized source of hot water
(district heating), the following object can be used in the input.
1.23.23.1 Inputs
1.23.23.2 Outputs
1.23.24 PlantComponent:TemperatureSource
This object allows the simulation of a water (or other fluid) source at a user-specified tempera-
ture. This could include a river, well, or seawater source, or any other configuration where the fluid
temperature being supplied by the component to the plant is known. The temperature may be a
constant or scheduled. Of course, the scheduled value may also be overwritten via EMS in cases
where the specified temperature should be calculated at run-time.
1.23.24.1 Inputs
PlantComponent:TemperatureSource ,
FluidSource , !- Name
FluidSource Inlet Node , !- Inlet Node
FluidSource Outlet Node , !- Outlet Node
Autosize , !- Design Volume Flow Rate {m3/s}
Constant , !- Temperature Specification Type
62, !- Source Temperature {C}
; !- Source Temperature Schedule Name
1.23.24.2 Outputs
The following output variables are available for the temperature source plant components:
1.23.25 CentralHeatPumpSystem
This is a central geothermal application that contains one or more chiller-heaters centrally located
in the building; the available chilled and/or hot water is then piped to the individual zones. Chiller-
heaters used for this particular system can be of two types: 1) standard vapor-compression, non-
reversible cycle chillers designed for heat recovery or 2) reversible-cycle, water-to-water heat pump
chillers. Unlike a distributed ground source heat pump configuration where individual heat pumps
are located in each zone, a centralized geothermal configuration has one or more chiller-heaters.
Its function is to encapsulate the extra controls needed to turn individual chiller-heater modules
on/off and whether they are to operate in cooling-only, heating-only or simultaneous cooling-heating
mode and whether to connect the source water to the evaporator or condenser side. A variety of
control schemes can be designed by setting schedules for both zone control types and individual
chiller-heaters schedules.
The fluid used in this central system is usually water, and there is no sharing of condenser or
evaporator water between multiple machines. However, the control logic is such that the source
water can be delivered to individual chiller-heaters depending on their operating mode, e.g., modules
in simultaneous cooling-heating mode receive no source water, modules in heating-only mode can
have source water directed to their evaporator, or modules in cooling-only mode can have source
water directed to their condenser; the decision on which module(s) receives the source water dictated
by the ‘smart’ controls. The following figures illustrate node interconnections between this central
geothermal application and plant and condenser loops in various situations.
The order of the multiple chiller-heaters’ operation is assumed to be sequential. In other words, the
very first chiller-heater will be called at first to see if it meets all loads that the central heat pump
system should meet. If the chiller-heater meets all loads, the rest chiller-heaters are assumed to be
turned off. If not, the following chiller-heater will be called to meet the remaining loads until all
loads are met in the order as defined in the set of individual chiller-heater objects below. The order
of individual chiller-heater modules needs to be carefully arranged in case users are intended to see
the performance of various combinations of different sizes of chiller-heaters in a central heat pump
system.
936 CHAPTER 1. INPUT-OUTPUT REFERENCE
Figure 1.92: Diagram of a central heat pump system with three chiller-heaters in cooling-only mode
(Condensers reject heat to the ground source loop)
Figure 1.93: Diagram of a central heat pump system with three chiller-heaters in heat recovery
mode (No heat is exchanged with the ground source loop)
1.23. GROUP – PLANT EQUIPMENT 937
Figure 1.94: Diagram of a central heat pump system with one chiller-heater in heat recovery mode
and two chiller-heaters in cooling-only mode
In the above example, the cooling load needs 3 chiller-heaters and the heating load needs 1 chiller
heater. Chiller 1 is in heat recovery mode and isolated from the ground source loop while chillers 2
and 3 are in cooling-only mode, their condensers rejecting heat to the ground source loop.
In the above example, the heating load needs 3 chiller-heaters and the cooling load needs two chiller-
heaters. Chillers 1 and 2 are in heat recovery mode and isolated from the ground source loop while
chiller 3 is in heating-only mode, its evaporator extracting heat from the ground source loop.
Users are required to define three different nodes such as chilled water, hot water, and source water
nodes. Only this central heat pump system will be metered, and individual chiller-heaters’ energy
will be available for reporting only, but not metered.
1.23.25.1 Inputs
Figure 1.95: Diagram of a central heat pump system with two chiller-heaters in heat recovery mode
and one chiller-heater in heating-only mode
This alpha field is paired with the preceding chiller-heater module type to define the name of the
module.
CentralHeatPumpSystem ,
ChillerBank , !- Name
SmartMixing , !- Control Method
Chiller Inlet Node , !- Cooling Loop Inlet Node Name
Chiller Outlet Node , !- Cooling Loop Outlet Node Name
Condenser Inlet Node , !- Source Loop Inlet Node Name
Condenser Outlet Node , !- Source Loop Outlet Node Name
HWInlet , !- Heating Loop Inlet Node Name
HWOutlet , !- Heating Loop Outlet Node Name
460, !- Ancillary Power {W}
, !- Ancillary Operation Schedule Name
ChillerHeaterPerformance :Electric:EIR , !- Chiller Heater Modules Object Type 1
ChillerHeaterModule 1, !- Chiller Heater Modules Performance Component Name 1
ON , !- Chiller Heater Modules Control Schedule Name 1
2, !- Number of Chiller Heater Modules 1
ChillerHeaterPerformance :Electric:EIR , !- Chiller Heater Modules Object Type 2
ChillerHeaterModule 2, !- Chiller Heater Modules Performance Component Name 2
ON , !- Chiller Heater Modules Control Schedule Name 2
2; !- Number of Chiller Heater Modules 2
940 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.23.25.2 Outputs
1.23.26 ChillerHeaterPerformance:Electric:EIR
The performance of the chiller-heater will be defined by two sets of curves meant to describe un-
loading for: 1) cooling-only mode, and 2) heating-only mode or simultaneous cooling-heating mode.
Reference conditions must be defined for both because each has its own set of three unloading
curves based on their associated reference conditions. The cooling-mode curves are typically (but
not always) based on condenser entering water temperature while the heating-only mode curves are
typically based on condenser leaving water temperature. This chiller-heater object allows the user
to specify whether to use condenser leaving or condenser entering as a dependent variable to differ-
entiate, if necessary, the condenser temperature basis used to generate the cooling- and heating-only
mode curves.
This alpha field contains the identifying name of the chiller-heater to be included in a central heat
pump system.
This numeric field contains the reference cooling capacity of the evaporator in cooling mode in Watts.
This value should be based on the reference temperatures and design water flow rates defined below.
This field can be autosized.
This numeric field contains the reference coefficient of performance of the evaporator for cooling. It
must be based on the values of Reference Cooling Mode Leaving Chilled Water Temperature and
Reference Cooling Mode Entering Condenser Water Temperature defined in the next two fields.
This numeric field contains the reference leaving chilled water temperature of the evaporator for
cooling in Celsius. The default value is 6.67°C.
This numeric field contains the reference entering condenser water temperature of the condenser in
the cooling mode in Celsius. The default value is 29.4°C.
1.23. GROUP – PLANT EQUIPMENT 943
This numeric field contains the reference leaving condenser water temperature of the condenser in
the cooling mode in Celsius. The default value is 35.0°C.
This numeric field contains the evaporator’s capacity during the reference heating-only or simulta-
neous cooling-heating mode as a ratio of reference cooling capacity. For example, the ratio may be
expressed as follows:
where Tchw,l is the leaving chilled water temperature and Tcond,l is the leaving condenser water tem-
perature representing the heating-mode and cooling-mode reference temperatures defined elsewhere
in this object.
The default is 0.75. This field is used to determine evaporator capacity in heating-only mode or
simultaneous cooling-heating mode, multiplying it by the value entered in the field of the Reference
Cooling Mode Evaporator Capacity. Note that even when there is no cooling load, i.e., the machine
is in heating-only mode, the evaporator must still run and extract heat from the source water. In
heating-only mode, the leaving chilled water temperature (Tchw,l) may float depending on the
evaporator water flow rate and the source water temperature. In simultaneous cooling and heating
mode, the leaving chilled water temperature (Tchw,l) does not float but is determined by the chilled
water setpoint controls. For both heating-only and simultaneous cooling and heating mode, the
leaving condenser temperature (Tcond,l) is determined by the hot water supply setpoint controls.
This value of Tchw,l, combined with Tcond,l is plugged into the CAPFT and EIRFT curves to
determine the off-rated heating-mode evaporator capacity and associated compressor power.
This numeric field contains the compressor power during simultaneous cooling-heating mode as a
ratio of reference cooling compressor power. For example, the ratio may be expressed as follows:
The default value is 1.5. This field is used to determine full load compressor power at the simultaneous
cooling-heating mode’s reference chilled water leaving and condenser water leaving temperatures.
Note: In heating-only mode, the chilled water leaving temperature floats so the EIRFT curve is used
to modify the simultaneouos cooling-heating full load compressor power value.
This numeric field contains the reference leaving chilled water temperature of the evaporator in
simultaneous cooling-heating mode in Celsius. This is typically the same as the reference cooling
mode value and is used to create the heating-only mode and simultaneous cooling-heating mode
944 CHAPTER 1. INPUT-OUTPUT REFERENCE
unloading curves. The leaving chilled water temperature for the chiller-heater is not allowed to fall
below this value during the heating-only mode and simultaneous cooling-heating mode. The default
value is 6.67°C.
This numeric field contains the reference leaving condenser water temperature of the condenser in
heating mode in Celsius. This field is typically controlled to the design hot water supply temperature,
and used to create the heating-only mode and simultaneous cooling-heating mode unloading curves.
The default value is 60.0°C.
This numeric field contains the reference entering condenser water temperature of the condenser
in heating mode in Celsius. This field typically represents the upper limit of the source water
temperature. The default value is 29.44°C.
1.23.26.12 Field: Heating Mode Entering Chilled Water Temperature Low Limit
This numeric field contains the low limit of the entering chilled water temperature in heating-only
mode or simultaneous cooling-heating mode in Celsius. This field typically represents the lower limit
of the source water temperature. If necessary, auxiliary heat will be activated to prevent source water
temperature falling below the chilled water entering minimum. The default value is 12.2°C.
This alpha field contains the chilled water flow control mode. Valid water flow mode includes constant
flow and variable flow, and the default water flow mode is constant flow.
This numeric field contains the design chilled water flow rate in m3 /s. The minimum value for this
field must be greater than zero, and this field is autosizable.
This numeric field contains the design condenser water flow rate in m3 /s. The minimum value for
this field must be greater than zero, and this field is autosizable.
This numeric field contains the design hot water flow rate in m3 /s. The minimum value and default
value for this field are zero, and this field is autosizable.
1.23. GROUP – PLANT EQUIPMENT 945
This numeric field contains the fraction of efficiency of the compressor electrical energy consumption
that must be rejected by the condenser. This value must be between 0.0 and 1.0, and the default
value is 1.0.
This alpha field contains the type of condenser. WaterCooled is the only valid type, and it requires
the full specification of the condenser loop and its associated equipment.
This alpha field determines whether the entering or leaving condenser water temperature is used
in the cooling mode unloading performance curves that follow. Valid variables include Entering-
Condenser and LeavingCondenser, and the default variable is EnteringCondenser. The condenser
temperature used for the cooling mode unloading performance curves will be dependent on this field
input. For example, leaving condenser water temperature will be used when the LeavingCondenser
is chosen, otherwise entering condenser water temperature.
This alpha field contains the name of a biquadratic performance curve (ref: Performance Curves)
that parameterizes the variation of the evaporator capacity as a function of the leaving chilled water
temperature and either the entering condenser water temperature or the leaving condenser water
temperature as defined in the previous field. It is then multiplied by the reference evaporator capac-
ity to give the cooling capacity at specific temperature operating conditions (i.e., at temperatures
different from the reference temperatures). The curve should have a value of 1.0 at the reference
temperatures and flow rates specified above. The biquadratic curve should be valid for the range of
water temperatures anticipated for the simulation.
1.23.26.21 Field: Cooling Mode Electric Input to Cooling Output Ratio Function
of Temperature Curve Name
This alpha field contains the name of a biquadratic performance curve (ref: Performance Curves)
that parameterizes the variation of the energy input to cooling output ratio (EIR) as a function of
the leaving chilled water temperature and either the entering condenser water temperature or the
leaving condenser water temperature as defined by the user. The EIR is the inverse of the COP. It
is then multiplied by the reference EIR (inverse of the reference COP) to give the EIR at specific
temperature operating conditions (i.e., at temperatures different from the reference temperatures).
The curve should have a value of 1.0 at the reference temperatures and flow rates specified above. The
biquadratic curve should be valid for the range of water temperatures anticipated for the simulation.
946 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.23.26.22 Field: Cooling Mode Electric Input to Cooling Output Ratio Function
of Part Load Ratio Curve Name
This alpha field contains the name of a performance curve (ref: Performance Curves) that parame-
terizes the variation of the energy input to cooling output ratio (EIR) as a function of the part-load
ratio (EIRFPLR). The EIR is the inverse of the COP, and the part-load ratio is the actual cooling
load divided by the available cooling capacity of the chiller-heater. This curve is generated by di-
viding the operating electric input power by the available full-load capacity at the specific operating
temperatures. The curve output should decrease from 1 towards 0 as part-load ratio decreases from
1 to 0. Note that the bi-cubic formulation is generally only valid when LeavingCondenser variable is
chosen for the field of Cooling Mode Condenser Water Temperature Curve Input Variable whereas
the quadratic curve can be used both choices, i.e., LeavingCondenser and EnteringCondenser. The
output of this curve is then multiplied by the reference full-load EIR and the EIRFT to give the
EIR at the specific temperatures and part-load ratio at which the chiller-heater is operating. This
curve should have a value of 1.0 when the part-load ratio equals 1.0. The curve should be valid for
the range of part-load ratios anticipated for the simulation.
1.23.26.23 Field: Cooling Mode Cooling Capacity Optimum Part Load Ratio
This numeric field contains the chiller-heater’s optimum part-load ratio. This is the part-load ratio
at which the chiller-heater performs at its maximum COP. The optimum part-load ratio must be
greater than or equal to the minimum part-load ratio, and less than or equal to the maximum part-
load ratio. (Note: Both the minimum part-load ratio and maximum part-load ratio are taken from
the Cooling Mode EIRFPLR curve definition.) The default value is 1.0.
This alpha field determines whether the entering or leaving condenser water temperature is used
in the heating mode unloading performance curves that follow. Valid variables include Entering-
Condenser and LeavingCondenser, and the default variable is EnteringCondenser. The condenser
temperature used for the cooling mode unloading performance curves will be dependent on this field
input. For example, leaving condenser water temperature will be used when the LeavingCondenser
is chosen, otherwise entering condenser water temperature.
This alpha field contains the name of a biquadratic performance curve (ref: Performance Curves)
that parameterizes the variation of the evaporator capacity in heating mode as a function of the
leaving chilled water temperature and either the entering condenser water temperature or the leav-
ing condenser water temperature as defined in the previous field. This curve is used to evaluate the
adjusted evaporator capacity during heating-only mode or simultaneous cooling-heating mode. This
adjusted capacity is used as part of the cooling part-load calculation for the EIRFPLR curve. It
is then multiplied by the reference evaporator capacity to give the cooling capacity at specific tem-
perature operating conditions (i.e., at temperatures different from the reference temperatures). The
curve should have a value of 1.0 at the reference temperatures and flow rates specified above. The
biquadratic curve should be valid for the range of water temperatures anticipated for the simulation.
1.23. GROUP – PLANT EQUIPMENT 947
1.23.26.26 Field: Heating Mode Electric Input to Cooling Output Ratio Func-
tion of Temperature Curve Name
This alpha field contains the name of a biquadratic performance curve (ref: Performance Curves)
that parameterizes the variation of the energy input to cooling output ratio (EIR) as a function of
the leaving chilled water temperature and either the entering condenser water temperature or the
leaving condenser water temperature as defined by the user. The EIR is the inverse of the COP. It
is then multiplied by the reference EIR (inverse of the reference COP) to give the EIR at specific
temperature operating conditions (i.e., at temperatures different from the reference temperatures).
The curve should have a value of 1.0 at the reference temperatures and flow rates specified above. The
biquadratic curve should be valid for the range of water temperatures anticipated for the simulation.
1.23.26.27 Field: Heating Mode Electric Input to Cooling Output Ratio Func-
tion of Part Load Ratio Curve Name
This alpha field contains the name of a performance curve (ref: Performance Curves) that parame-
terizes the variation of the energy input to cooling output ratio (EIR) as a function of the part-load
ratio (EIRFPLR). The EIR is the inverse of the COP, and the part-load ratio is the actual evaporator
load divided by the available evaporator capacity of the chiller-heater at the reference heating and
simultaneous cooling-heating mode temperatures. This curve is generated by dividing the operating
electric input power by the available full-load capacity (do not divide by load) at the specific oper-
ating temperatures. The curve output should decrease from 1 towards 0 as part-load ratio decreases
from 1 to 0. Note that the bicubic formulation below can only be used when the chiller-heater uses
a variable speed compressor motor drive. It is also generally valid only when LeavingCondenser
variable is chosen for the field of Cooling Mode Condenser Water Temperature Curve Input Variable
whereas the quadratic curve can be used both choices, i.e., LeavingCondenser and EnteringCon-
denser. The output of this curve is then multiplied by the reference full-load EIR (inverse of the
reference COP) and the EIRFT to give the EIR at the specific temperatures and part-load ratio at
which the chiller-heater is operating. This curve should have a value of 1.0 when the part-load ratio
equals 1.0. The curve should be valid for the range of part-load ratios anticipated for the simulation.
1.23.26.28 Field: Heating Mode Cooling Capacity Optimum Part Load Ratio
This numeric field contains the chiller-heater’s optimum part-load ratio during heating-only mode or
simultaneous cooling-heating mode. This is the part-load ratio at which the chiller-heater performs
at its maximum COP. The optimum part-load ratio must be greater than or equal to the minimum
part-load ratio, and less than or equal to the maximum part-load ratio. (Note: Both the minimum
part-load ratio and maximum part-load ratio are taken from the Heating Mode EIRFPLR curve
definition.) The default value is 1.0.
This optional numeric field allows the user to specify a sizing factor for this component. The Sizing
Factor is a multiplier on the design plant chilled water loop flow rate associated with the chiller-
heaters parent CentralHeatPumpSystem object. The chiller-heater’s modified chilled water flow can
then be used to autocalculate the Design Condenser Water Flow Rate and Reference Cooling Mode
Evaporator Capacity values. In general, it is best to autosize all three fields or set fixed values for
all three fields.
948 CHAPTER 1. INPUT-OUTPUT REFERENCE
ChillerHeaterPerformance :Electric:EIR ,
ChillerHeaterModule 1, !- Name
12500 , !- Reference Cooling Mode Evaporator Capacity {W}
1.5, !- Reference Cooling Mode COP {W/W}
6.67, !- Reference Cooling Mode Leaving Chilled Water Temperature {C}
29.4, !- Reference Cooling Mode Entering Condenser Fluid Temperature {C}
35.0, !- Reference Cooling Mode Leaving Condenser Water Temperature {C}
0.74, !- Reference Heating Mode Cooling Capacity Ratio
1.38, !- Reference Heating Mode Cooling Power Input Ratio
6.67, !- Reference Heating Mode Leaving Chilled Water Temperature {C}
60, !- Reference Heating Mode Leaving Condenser Water Temperature {C}
29.44 , !- Reference Heating Mode Entering Condenser Fluid Temperature {C}
5, !- Heating Mode Entering Chilled Water Temperature Low Limit {C}
VariableFlow , !- Chilled Water Flow Mode Type
0.0003525 , !- Design Chilled Water Flow Rate {m$ ^{3}$/s}
0.0005525 , !- Design Condenser Water Flow Rate {m$ ^{3}$/s}
0.0003525 , !- Design Hot Water Flow Rate {m$ ^{3}$/s}
1, !- Compressor Motor Efficiency
WaterCooled , !- Condenser Type
EnteringCondenser , !- Cooling Mode Temperature Curve Condenser Water Independent Variable
ChillerHeaterClgCapFT , !- Cooling Mode Cooling Capacity Function of Temperature Curve Name
ChillerHeaterClgEIRFT , !- Cooling Mode Electric Input to Cooling Output Ratio Function of
!- Temperature Curve Name
ChillerHeaterClgEIRFPLR , !- Cooling Mode Electric Input to Cooling Output Ratio Function of
Part Load
!- Ratio Curve Name
1, !- Cooling Mode Cooling Capacity Optimum Part Load Ratio
LeavingCondenser , !- Heating Mode Temperature Curve Condenser Water Independent Variable
ChillerHeaterHtgCapFT , !- Heating Mode Cooling Capacity Function of Temperature Curve Name
ChillerHeaterHtgEIRFT , !- Heating Mode Electric Input to Cooling Output Ratio Function of
!- Temperature Curve Name
ChillerHeaterHtgEIRFPLR , !- Heating Mode Electric Input to Cooling Output Ratio Function of
Part Load
!- Ratio Curve Name
1, !- Heating Mode Cooling Capacity Optimum Part Load Ratio
1; !- Sizing Factor
Note that much of these output variables are adapted from the definitions above under “Generic
Chiller Outputs” and “Electric EIR Chiller Outputs.” The following outputs are repeated up to the
maximum of individual chiller-heater module objects. The maximum number may be different from
the number of object defined in this object when users define two or more identical chiller-heater
modules for a single chiller heater object in the central heat pump system.
This output represents the operating mode of the chiller-heater module. Two single mode outputs
and three simultaneous cooling-heating mode outputs are possible:
0. off
1. cooling-only mode
2. heating-only mode
3. heat recovery mode
4. cooling dominant simultaneous cooling-heating mode
5. heating dominant simultaneous cooling-heating mode.
The first mode 0 is reported when the chiller-heater is turned off. The next two modes 2 and 3 are
reported when the chiller-heater provides only either cooling or heating, respectively. The last three
modes 3 to 5 indicate when the chiller-heater is in a simultaneous cooling-heating mode. Mode 3
indicates the chiller-heaters provides simultaneous cooling and heating without heat exchange with
the ground source. Mode 4 denotes that at least one of the chiller-heater modules in the central
heat pump system provides both cooling and heating, and the chiller-heater is meeting remaining
cooling demand (see Figure 1.94. Diagram of a central heat pump system with one chiller-heater in
heat recovery mode and two chiller-heaters in cooling-only mode) Similarly, mode 5 indicates that
at least one of the chiller-heater modules in the central heat pump system is in the heat recovery
mode, and the chiller-heater is meeting remaining heating demand (see Figure 1.95).
Note that the decision to operate individual chiller-heater modules is solely dependent on the chiller-
heater schedule and loads. A fraction may appear in case the chiller-heater mode varies within a zone
time step. In this particular case, users may define a detailed reporting frequency for this output
variable.
950 CHAPTER 1. INPUT-OUTPUT REFERENCE
This output is the ratio of the evaporator heat transfer rate plus the false load heat transfer rate (if
applicable) to the available chiller-heater capacity. This value is used to determine ChillerEIRFPLR.
The cycling ratio is the amount of time the chiller-heater operates during each simulation time step.
If the chiller-heater part-load ratio falls below the minimum part-load ratio, the chiller-heater cycles
on and off to meet the loads.
These outputs are the cooling electric power consumption of the chiller-heater.
These outputs are the heating electric power consumption of the chiller-heater.
These outputs are the evaporator heat transfer which is the cooling delivered by the chiller-heater
module.
1.23.27.10 Chiller Heater False Load Heat Transfer Rate Unit <x> [W]
1.23.27.11 Chiller Heater False Load Heat Transfer Energy Unit <x> [J]
These outputs are the heat transfer rate and total heat transfer due to false loading of the chiller-
heater. When the chiller-heater part-load ratio is below the minimum unloading ratio, the chiller-
heater false loads (e.g. hot-gas bypass) to further reduce capacity.
1.23.27.12 Chiller Heater Condenser Heat Transfer Rate Unit <x> [C]
1.23.27.13 Chiller Heater Condenser Heat Transfer Energy Unit <x> [C]
These outputs are the heat transfer which is the heating delivered by the chiller-heater module in
heating mode.
1.24. GROUP – WATER HEATERS AND THERMAL STORAGE 951
1.23.27.16 Chiller Heater Evaporator Mass Flow Rate Unit <x> [C]
These outputs are the evaporator water inlet and outlet temperatures and flow rate. Note that
these represent the chilled water temperatures and flow rate in cooling mode or the source water
temperature and flow rate in heating mode.
1.23.27.19 Chiller Heater Condenser Mass Flow Rate Unit <x> [C]
These outputs are the condenser water inlet and outlet temperatures and flow rate. Note that these
represent the hot water temperatures and flow rate in heating mode or the source water temperature
and flow rate in cooling mode.
This output is the coefficient of performance for the chiller-heater. It is calculated as the evaporator
heat transfer rate divided by the chiller-heater electric power.
This is the output of the curve object Cooling Capacity Function of Temperature Curve.
1.23.27.22 Chiller Heater EIR Temperature Modifier Multiplier Unit <x> [C]
This is the output of the curve object Electric Input to Cooling Output Ratio Function of Temper-
ature Curve.
1.23.27.23 Chiller Heater EIR Part Load Modifier Multiplier Unit <x> [C]
This is the output of the curve object Electric Input to Cooling Output Ratio Function of Part Load
Ratio Curve.
When coupled to the plant loop, the water heater has an inlet node and outlet node on the “source
side” and an inlet node and outlet node on the “use side”. The source side typically draws cold water
from the tank and returns warmer water, for instance, from solar hot water systems or waste heat
recovery systems. The use side typically draws hot water from the tank and returns cooler water from
the cold water supply mains or from the outlet of a heating system. The distinction between source
and use sides is merely a convenience for reporting. They can actually be used interchangeably. If so
desired, either source side or use side can be used by itself, without the other side being connected
to the plant loop.
However, for a water heater that is indirectly heated (e.g. with a separate boiler), the source side
can be used to provide remotely heated water to the tank. The source side is configured to operate
as a component on the demand side of a plant loop. The design flow rate through the source side
can be set by the user or autosized. If autosized, then a Plant Sizing object is needed elsewhere
in the input file for the Plant Loop serving the source side. The water heater input includes an
additional design parameter that describes how rapidly the tank can recover.
If the use side only consists of domestic hot water usage, a simple scheduled use flow rate can be spec-
ified in lieu of the full plant loop connections. The scheduled use flow rate can be used simultaneously
with source side plant connections, but cannot be used with use side plant connections.
For stand-alone operation, there are no node connections to the plant loop on either source or use
sides. The scheduled use flow rate determines all fluid exchange with the water tank.
1.24. GROUP – WATER HEATERS AND THERMAL STORAGE 953
– WaterHeater:Mixed
– WaterHeater:Stratified
There are also compound objects that uses the WaterHeater:Mixed and/or WaterHeater:Stratified
as part of their strategy:
The WaterHeater:Mixed object simulates a well-mixed, single-node water tank. The Water-
Heater:Stratified object simulates a stratified, multi-node water tank. Both water heater objects
can be appropriate for simulating many types of water heaters and storage tanks, including gas and
electric residential water heaters, and a variety of large commercial water heaters. Both objects
share similar features, such as stand-alone operation, on- and off-cycle parasitic loads, and thermal
losses to the zone. However, each object has its advantages which may make one water heater
object more appropriate than the other depending on the application.
Advantages of WaterHeater:Mixed:
Advantages of WaterHeater:Stratified:
1.24.2 WaterHeater:Mixed
The WaterHeater:Mixed object analytically solves the differential equation governing the energy
balance of the water tank. Within a timestep, conditions are solved separately for when the heater
element or burner is “on” (on-cycle) and when it is “off” (off-cycle). This approach allows ambient
losses and parasitic loads to be divided into on-cycle and off-cycle effects and accounted for in detail.
For losses to the ambient environment, the ambient air temperature can be taken from a schedule, a
zone, or the exterior. When used with a zone, a fraction of the skin losses can be added to the zone
heat balance as internal heat gains.
Control options allow the heater to cycle or modulate to meet the load. When cycling, the heater
element or burner is either on or off. The heater remains fully on while heating the tank up to
the setpoint temperature. When the setpoint is reached, the heater turns off. The heater remains
off until the tank temperature falls below the “cut-in” temperature, i.e., the setpoint temperature
minus the deadband temperature difference. The heater continuously cycles on and off to maintain
the tank temperature within the deadband. Most storage-tank water heaters cycle.
When modulating, the heater power varies between the maximum and minimum heater capacities.
The heater stays on as long as the required total demand is above the minimum capacity. Below
the minimum capacity, the heater will begin to cycle on and off based on the deadband temperature
difference. Equipment is usually designed and rated to avoid this condition. Most tankless/instan-
taneous water heaters modulate.
1.24.2.1 Inputs
WaterHeater:Mixed ,
Indirect Water Heater , !- Name
1.00, !- Tank Volume {m3}
Hot Water Setpoint Temperature Schedule , !- Setpoint Temperature Schedule
5.0, !- Deadband Temperature Difference {deltaC}
82.2222 , !- Maximum Temperature Limit {C}
Cycle , !- Heater Control Type
0.0, !- Heater Maximum Capacity {W}
, !- Heater Minimum Capacity {W}
, !- Heater Ignition Minimum Flow Rate {m3/s}
, !- Heater Ignition Delay {s}
ELECTRICITY , !- Heater Fuel Type
0.8, !- Heater Thermal Efficiency
, !- Part Load Factor Curve
, !- Off -Cycle Parasitic Fuel Consumption Rate {W}
, !- Off -Cycle Parasitic Fuel Type
, !- Off -Cycle Parasitic Heat Fraction To Tank
, !- On -Cycle Parasitic Fuel Consumption Rate {W}
, !- On -Cycle Parasitic Fuel Type
, !- On -Cycle Parasitic Heat Fraction To Tank
Zone , !- Ambient Temperature Indicator
, !- Ambient Temperature Schedule
SPACE5 -1, !- Ambient Temperature Zone
, !- Ambient Temperature Outside Air Node
5.0, !- Off -Cycle Loss Coefficient To Ambient Temperature {W/K}
, !- Off -Cycle Loss Fraction To Zone
5.0, !- On -Cycle Loss Coefficient To Ambient Temperature {W/K}
, !- On -Cycle Loss Fraction To Zone
, !- Peak Volumetric Use Flow Rate {m3/s}
, !- Use Flow Rate Fraction Schedule
, !- Cold Water Supply Temperature Schedule
SHWSys1 Pump -SHWSys1 Water HeaterNode , !- Use Side Inlet Node
SHWSys1 Supply Equipment Outlet Node , !- Use Side Outlet Node
1.0, !- Use Side Effectiveness
Indirect Water Heater SrcSideInletNode , !- Source Side Inlet Node
Indirect Water Heater SrcSideOutletNode , !- Source Side Outlet Node
0.9, !- Source Side Effectiveness
autosize , !- Use Side Design Flow Rate
autosize , !- Source Side Design Flow Rate
1.0; !- Indirect Water Heating Recovery Time
1.24.2.2 Outputs
The following output variables are reported for the WaterHeater:Mixed object:
1.24.2.2.15 Water Heater Off Cycle Parasitic Tank Heat Transfer Rate [W]
The average heat gain rate to the tank water due to off-cycle parasitics.
1.24.2.2.16 Water Heater Off Cycle Parasitic Tank Heat Transfer Energy [J]
The heat gain energy to the tank water due to off-cycle parasitics.
1.24.2.2.17 Water Heater On Cycle Parasitic Tank Heat Transfer Rate [W]
The average heat gain rate to the tank water due to on-cycle parasitics.
1.24.2.2.18 Water Heater On Cycle Parasitic Tank Heat Transfer Energy [J]
The heat gain energy to the tank water due to on-cycle parasitics.
1.24.2.2.35 Water Heater Off Cycle Parasitic <Fuel Type> Rate [W]
1.24.2.2.37 Water Heater Off Cycle Parasitic <Fuel Type> Energy [J]
The fuel consumption energy for the off-cycle parasitics.
1.24.3 WaterHeater:Stratified
The WaterHeater:Stratified object divides the water tank into multiple nodes of equal volume. The
nodes are coupled by vertical conduction effects, internode fluid flow, and temperature inversion
mixing. The object simultaneously solves the differential equations governing the energy balances on
the nodes using a numerical method. The system timestep is divided into many small substeps that
allow the simulation to capture events that occur on a very short time scale. This approach allows
ambient losses and parasitic loads to be divided into on-cycle and off-cycle effects and accounted for
in detail.
For losses to the ambient environment, the ambient air temperature can be taken from a schedule, a
zone, or the exterior. When used with a zone, a fraction of the skin losses can be added to the zone
heat balance as internal heat gains.
The WaterHeater:Stratified object allows two heating elements to be simulated. The two elements
can cycle on and off to maintain the node temperature within the deadband. The Heater Priority
Control field determines how the heaters work together. There are two options: MasterSlave or
Simultaneous. In the MasterSlave option, Heater 1 is the master and Heater 2 is the slave. That is,
both heaters are not allowed to turn on at the same time. If the thermostats ask for heat at both
Heater 1 and 2, only Heater 1 will turn on. Once Heater 1 has met the set point, it turns off and
Heater 2 can turn on, if necessary. In the Simultaneousoption, Heater 1 and Heater 2 can turn on
and off independently. Autosizing is available for only Heater 1.
1.24.3.1 Inputs
point, it turns off and Heater 2 can turn on, if necessary. In other words, only one heater can be on
at any time, and Heater 1 is always has priority over Heater 2.
In the Simultaneous option, Heater 1 and Heater 2 can turn on and off independently.
If blank, the default is MasterSlave.
1.24.3.1.31 Field: Uniform Skin Loss Coefficient Per Unit Area to Ambient Tem-
perature
The uniform skin loss coefficient [W/m2-K] or U-Value of the tank to the ambient air temperature.
The uniform skin loss accounts for the tank insulation and applies during both off- and on-cycle
operation. The overall losses at any particular node can be further modified using the Additional
Loss Coefficient fields to account for thermal shorting due to pipe penetrations, water heater feet,
and any other loss effects.
WaterHeater:Stratified ,
Electric Water Heater , !- Name
Water Heater , !- End -Use Subcategory
0.1893 , !- Tank Volume {m3}
1.4, !- Tank Height {m}
VerticalCylinder , !- Tank Shape
, !- Tank Perimeter {m}
82.2222 , !- Maximum Temperature Limit {C}
MasterSlave , !- Heater Priority
Hot Water Set Point Temp Schedule , !- Heater 1 Set Point Temperature Schedule
2.0, !- Heater 1 Deadband Temperature Difference {deltaC}
4500, !- Heater 1 Capacity {W} (Master)
1.0, !- Heater 1 Height {m}
Hot Water Set Point Temp Schedule , !- Heater 2 Set Point Temperature Schedule
5.0, !- Heater 2 Deadband Temperature Difference {deltaC}
4500, !- Heater 2 Capacity {W} (Slave)
0.0, !- Heater 2 Height {m}
ELECTRICITY , !- Heater Fuel Type
0.98, !- Heater Thermal Efficiency
974 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.24.3.2 Outputs
All of the output variables reported for the WaterHeater:Mixed object also apply to the Water-
Heater:Stratified object, with several qualifications noted below:
1.24.4 WaterHeater:Sizing
The WaterHeater:Sizing object is used to provide additional input data needed for designing tank
volume and/or heater capacity for either the Mixed or Stratified water heaters. This object is only
needed if volume or capacity is being automatically sized. There are no output variable associated
with this object – sizing results are reported to the EIO output file and some predefined summary
reports.
A source of design input data for use with this object can be found in the current ASHRAE Handbook
HVAC Applications chapter on Service Water Heating.
1.24.4.1 Inputs
– PeakDraw. This design method uses the design flow rates of all the different demands placed
on the water heater. The tank size is based on how long it can meet the demand and how
quickly it can recover. The user enters the time in hours that the water heater can meet the
demands. Only the hot water uses connected to an individual water heater, or scheduled in
the water heater object for stand-alone units, are included in that water heater’s peak draw.
– ResidentialHUD-FHAMinimum This design method is based on minimum permissible
water heater sizes (established by HUD-FHA in its Minimum Property Standards for One- and
Two-Family Living Units, No. 4900.1-1982). The user enters the number of bathrooms and
bedrooms in this input object. The smallest allowable water heater sizes are used.
– PerPerson This design method scales sizes based on the total number of people in all zones
in the building. Each water heater in the model will be sized using the total (peak, design)
number of people for the entire model. The number of people is determined from People
objects defined elsewhere in the input file
1.24. GROUP – WATER HEATERS AND THERMAL STORAGE 977
– PerFloorArea This design method scales sizes based on the total floor area in all the zones
in the building. Each water heater in the model will be sized using all the floor area in the
model. The floor areas are determined from the geometry input elsewhere in the input file.
– PerUnit This design method scales sizes based on an arbitrary number of units. This can
be used, for example, to size based on the number of rooms in a lodging building. The user
provides the number of units in an input field in this object.
– PerSolarCollectorArea This design method scales tank volume based on the collector area
for a solar hot water collector. The collector area is summed for all the collectors in the model
and each tank is sized for the total. The collector area is determined from input for Solar
Collectors defined elsewhere in the input file.
1.24.5 WaterHeater:HeatPump:PumpedCondenser
The heat pump water heater with pumped condenser (HPWH) is a compound object consisting of a
water heater tank (e.g., WaterHeater:Mixed or WaterHeater:Stratified), a direct expansion (DX) “coil” (i.e.,
an air-to-water DX compression system which includes a water heating coil, air coil, compressor, and
water pump), and a fan to provide air flow across the air coil associated with the DX compression
system. These objects work together to model a system which heats water using zone air, outdoor
air, or a combination of zone and outdoor air as the primary heat source. Numerous configurations
of tank location, inlet air source, and DX coil compressor location can be modeled, with one common
configuration shown below.
Figure 1.97: Schematic diagram for a heat pump water heater located in a zone
In this model, the heat pump water heater’s DX coil is considered the primary heat source and the
water tank’s heater (element or burner) provides supplemental heat as necessary. The model also
assumes that the heat pump’s fan and water pump cycle on and off with the compressor.
To model a heat pump water heater, the input data file must include some combination of the
following objects depending on the configuration to be modeled:
– WaterHeater:HeatPump:PumpedCondenser (required)
– WaterHeater:Mixed or WaterHeater:Stratified (required)
– Coil:WaterHeating:AirToWaterHeatPump:Pumped or Coil:WaterHeating:AirToWaterHeatPump:VariableSpeed (re-
quired)
– Fan:SystemModel or Fan:OnOff (required)
– ZoneHVAC:EquipmentList (when the HPWH draws some or all of its air from the zone, the heat
pump water heater type and name must be in this list)
980 CHAPTER 1. INPUT-OUTPUT REFERENCE
– (when the HPWH draws some or all of its air from the zone, the
ZoneHVAC:EquipmentConnections
HPWH air inlet and outlet node names must be provided in this object)
– (for HPWHs that use outdoor air as all or part of the heat source, the HPWH
OutdoorAir:NodeList
outdoor air node name must be provided in this list)
The input fields for the compound object are described in detail below:
1.24.5.1 Inputs
compressor is not operating, and the model assumes that this parasitic power does not contribute
to heating the water. This parasitic load does, however, affect the zone air heat balance when the
heat pump water heater sends some or all of its outlet air to a zone (i.e., Inlet Air Configuration
field specified as ‘ZoneAirOnly’ or ‘ZoneAndOutdoorAir’) and the Parasitic Heat Rejection Location
field is specified as ‘Zone’. The minimum value for this field is 0.0, and the default value is also 0.0
if this field is left blank.
name must be provided if the Inlet Air Configuration field is specified as ‘Zone and Outdoor Air’,
otherwise this field should be left blank.
– MutuallyExclusive means that once the tank heating element(s) are active, the heat pump
is shut down until the heating element setpoint is reached.
– Simultaneous (default) means that both the tank heating element and heat pump are used
at the same time to recover the tank temperature.
WaterHeater:HeatPump:PumpedCondenser ,
PlantHeatPumpWaterHeater ,!- Name
PlantHPWHSch , !- Availability Schedule Name
PlantHPWHTempSch , !- Compressor Setpoint Temperature Schedule Name
2.0, !- Dead Band Temperature Difference {deltaC}
HPPlantWaterInletNode , !- Condenser Water Inlet Node Name
HPPlantWaterOutletNode , !- Condenser Water Outlet Node Name
0.00115525 , !- Condenser Water Flow Rate {m3/s}
1.00695 , !- Evaporator Air Flow Rate {m3/s}
OutdoorAirOnly , !- Inlet Air Configuration
, !- Air Inlet Node Name
, !- Air Outlet Node Name
HPPlantAirInletNode , !- Outdoor Air Node Name
HPPlantAirOutletNode , !- Exhaust Air Node Name
, !- Inlet Air Temperature Schedule Name
, !- Inlet Air Humidity Schedule Name
, !- Inlet Air Zone Name
1.24. GROUP – WATER HEATERS AND THERMAL STORAGE 987
NOTE: branch object required only when tank use inlet nodes are used.
Branch ,
Central HPWH Branch , !- Name
, !- Pressure Drop Curve Name
WaterHeater:HeatPump:PumpedCondenser , !- Component 1 Object Type
PlantHeatPumpWaterHeater ,!- Component 1 Name
HPWH Use Inlet Node , !- Component 1 Inlet Node Name
HPWH Use Outlet Node; !- Component 1 Outlet Node Name
WaterHeater:Mixed ,
HPWHPlantTank , !- Name
0.757 , !- Tank Volume {m3}
Plant Hot Water Setpoint Temp Schedule , !- Setpoint Temperature Schedule Name
2.0, !- Deadband Temperature Difference {deltaC}
82.2222 , !- Maximum Temperature Limit {C}
CYCLE , !- Heater Control Type
25000 , !- Heater Maximum Capacity {W}
0, !- Heater Minimum Capacity {W}
, !- Heater Ignition Minimum Flow Rate {m3/s}
, !- Heater Ignition Delay {s}
ELECTRICITY , !- Heater Fuel Type
0.98, !- Heater Thermal Efficiency
, !- Part Load Factor Curve Name
10, !- Off Cycle Parasitic Fuel Consumption Rate {W}
ELECTRICITY , !- Off Cycle Parasitic Fuel Type
0, !- Off Cycle Parasitic Heat Fraction to Tank
30, !- On Cycle Parasitic Fuel Consumption Rate {W}
ELECTRICITY , !- On Cycle Parasitic Fuel Type
0, !- On Cycle Parasitic Heat Fraction to Tank
Outdoors , !- Ambient Temperature Indicator
, !- Ambient Temperature Schedule Name
, !- Ambient Temperature Zone Name
HPWHPlantTank OA Node , !- Ambient Temperature Outdoor Air Node Name
0.0, !- Off Cycle Loss Coefficient to Ambient Temperature {W/K}
0.0, !- Off Cycle Loss Fraction to Zone
0.0, !- On Cycle Loss Coefficient to Ambient Temperature {W/K}
0.0, !- On Cycle Loss Fraction to Zone
, !- Peak Use Flow Rate {m3/s}
, !- Use Flow Rate Fraction Schedule Name
, !- Cold Water Supply Temperature Schedule Name
HPWH Use Inlet Node , !- Use Side Inlet Node Name
HPWH Use Outlet Node , !- Use Side Outlet Node Name
0.98, !- Use Side Effectiveness
HPPlantWaterOutletNode , !- Source Side Inlet Node Name
HPPlantWaterInletNode , !- Source Side Outlet Node Name
0.98, !- Source Side Effectiveness
autosize; !- Use Side Design Flow Rate {m3/s}
OutdoorAir:Node ,
HPWHPlantTank OA Node; !- Name
Coil:WaterHeating: AirToWaterHeatPump:Pumped ,
988 CHAPTER 1. INPUT-OUTPUT REFERENCE
HPWHPlantDXCoil , !- Name
25000.0 , !- Rated Heating Capacity {W}
3.2, !- Rated COP {W/W}
0.736 , !- Rated Sensible Heat Ratio
29.44 , !- Rated Evaporator Inlet Air Dry -Bulb Temperature {C}
22.22 , !- Rated Evaporator Inlet Air Wet -Bulb Temperature {C}
55.72 , !- Rated Condenser Inlet Water Temperature {C}
1.00695 , !- Rated Evaporator Air Flow Rate {m3/s}
0.00115525 , !- Rated Condenser Water Flow Rate {m3/s}
No , !- Evaporator Fan Power Included in Rated COP
No , !- Condenser Pump Power Included in Rated COP
No , !- Condenser Pump Heat Included in Rated Heating Capacity and Rated
COP
150.0 , !- Condenser Water Pump Power {W}
0.1, !- Fraction of Condenser Pump Heat to Water
HPPlantFanAirOutletNode , !- Evaporator Air Inlet Node Name
HPPlantAirOutletNode , !- Evaporator Air Outlet Node Name
HPPlantWaterInletNode , !- Condenser Water Inlet Node Name
HPPlantWaterOutletNode , !- Condenser Water Outlet Node Name
100.0 , !- Crankcase Heater Capacity {W}
5.0, !- Maximum Ambient Temperature for Crankcase Heater Operation {C}
WetBulbTemperature , !- Evaporator Air Temperature Type for Curve Objects
HPWHHeatingCapFTemp , !- Heating Capacity Function of Temperature Curve Name
, !- Heating Capacity Function of Air Flow Fraction Curve Name
, !- Heating Capacity Function of Water Flow Fraction Curve Name
HPWHHeatingCOPFTemp , !- Heating COP Function of Temperature Curve Name
, !- Heating COP Function of Air Flow Fraction Curve Name
, !- Heating COP Function of Water Flow Fraction Curve Name
HPWHPLFFPLR; !- Part Load Fraction Correlation Curve Name
Fan:SystemModel ,
HPWHPlantFan , !- Name
PlantHPWHSch , !- Availability Schedule Name
HPPlantAirInletNode , !- Air Inlet Node Name
HPPlantFanAirOutletNode , !- Air Outlet Node Name
2.2685 , !- Design Maximum Air Flow Rate
Discrete , !- Speed Control Method
0.0, !- Electric Power Minimum Flow Rate Fraction
100.0 , !- Design Pressure Rise
0.9 , !- Motor Efficiency
1.0 , !- Motor In Air Stream Fraction
AUTOSIZE , !- Design Electric Power Consumption
TotalEfficiencyAndPressure , !- Design Power Sizing Method
, !- Electric Power Per Unit Flow Rate
, !- Electric Power Per Unit Flow Rate Per Unit Pressure
0.70; !- Fan Total Efficiency
1.24.5.2 Outputs
supplemental heater (element or burner) in the water tank. When the water tank’s (supplemental)
heater set point temperature is higher than the cut-in temperature of the heat pump water heater’s
compressor, the heat pump compressor is disabled and the water tank’s heater (element or burner)
is used to heat the water. During these times the Water Heater Compressor Part Load Ratio is
equal to 0.
1.24.6 WaterHeater:HeatPump:WrappedCondenser
The heat pump water heater with wrapped condenser is a compound object very similar to the
WaterHeater:HeatPump:PumpedCondenser object. It likewise combines a water heater tank, a direct expansion
(DX) “coil”, and a fan to provide air flow across the air coil associated with the DX compression
system. The primary difference is that instead of pumping water through an external condenser, the
heating coils are wrapped around or submerged in the tank. This type of HPWH is most common
in packaged units meant for residential applications.
To model a wrapped condenser heat pump water, the input data file must include some combination
of the following objects depending on the configuration to be modeled:
– WaterHeater:HeatPump:WrappedCondenser (required)
– WaterHeater:Stratified (required)
– Coil:WaterHeating:AirToWaterHeatPump:Wrapped (required)
– Fan:SystemModel! or Fan:OnOff (required)
– ZoneHVAC:EquipmentList (when the HPWH draws some or all of its air from the zone, the heat
pump water heater type and name must be in this list)
– ZoneHVAC:EquipmentConnections (when the HPWH draws some or all of its air from the zone, the
HPWH air inlet and outlet node names must be provided in this object)
– (for HPWHs that use outdoor air as all or part of the heat source, the HPWH
OutdoorAir:NodeList
outdoor air node name must be provided in this list)
The input fields for the compound object are described in detail below:
990 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.24.6.1 Inputs
are connected to a plant loop, otherwise leave this field blank. When used, the branch object should
reflect that this node is part of a WaterHeater:HeatPump:WrappedCondenser object (see branch object example
below).
if the Inlet Air Configuration field above is specified as ‘ZoneAndOutdoor Air’, otherwise this field
should be left blank.
– MutuallyExclusive means that once the tank heating element(s) are active, the heat pump
is shut down until the heating element setpoint is reached.
– Simultaneous (default) means that both the tank heating element and heat pump are used
at the same time to recover the tank temperature.
WaterHeater:HeatPump:WrappedCondenser ,
PlantHeatPumpWaterHeater ,!- Name
PlantHPWHSch , !- Availability Schedule Name
PlantHPWHTempSch , !- Compressor Setpoint Temperature Schedule Name
3.89, !- Dead Band Temperature Difference {deltaC}
0.0664166667 , !- Condenser Bottom Location
0.8634166667 , !- Condenser Top Location
0.2279 , !- Evaporator Air Flow Rate {m3/s}
OutdoorAirOnly , !- Inlet Air Configuration
, !- Air Inlet Node Name
, !- Air Outlet Node Name
HPPlantAirInletNode , !- Outdoor Air Node Name
HPPlantAirOutletNode , !- Exhaust Air Node Name
, !- Inlet Air Temperature Schedule Name
, !- Inlet Air Humidity Schedule Name
, !- Inlet Air Zone Name
WaterHeater:Stratified , !- Tank Object Type
HPWHPlantTank , !- Tank Name
HPWH Use Inlet Node , !- Tank Use Side Inlet Node Name
HPWH Use Outlet Node , !- Tank Use Side Outlet Node Name
Coil:WaterHeating: AirToWaterHeatPump :Wrapped , !- DX Coil Object Type
HPWHPlantDXCoil , !- DX Coil Name
7.2, !- Minimum Inlet Air Temperature for Compressor Operation {C}
Outdoors , !- Compressor Location
, !- Compressor Ambient Temperature Schedule Name
Fan:SystemModel , !- Fan Object Type
HPWHPlantFan , !- Fan Name
DrawThrough , !- Fan Placement
0, !- On Cycle Parasitic Electric Load {W}
0, !- Off Cycle Parasitic Electric Load {W}
, !- Parasitic Heat Rejection Location
, !- Inlet Air Mixer Node Name
, !- Outlet Air Splitter Node Name
, !- Inlet Air Mixer Schedule Name
MutuallyExclusive , !- Tank Element Control Logic
1.262 , !- Control Sensor 1 Height In Stratified Tank
0.75, !- Control Sensor 1 Weight
0.464; !- Control Sensor 2 Height In Stratified Tank
NOTE: branch object required only when tank use inlet nodes are used.
Branch ,
Central HPWH Branch , !- Name
, !- Pressure Drop Curve Name
WaterHeater:HeatPump:WrappedCondenser , !- Component 1 Object Type
PlantHeatPumpWaterHeater ,!- Component 1 Name
HPWH Use Inlet Node , !- Component 1 Inlet Node Name
1.24. GROUP – WATER HEATERS AND THERMAL STORAGE 997
WaterHeater:Stratified ,
HPWHPlantTank , !- Name
Water Heater , !- End -Use Subcategory
0.287691 , !- Tank Volume {m3}
1.594 , !- Tank Height {m}
VerticalCylinder , !- Tank Shape
, !- Tank Perimeter {m}
100, !- Maximum Temperature Limit {C}
MasterSlave , !- Heater Priority Control
Plant Hot Water Setpoint Temp Schedule , !- Heater 1 Setpoint Temperature Schedule Name
18.5, !- Heater 1 Deadband Temperature Difference {deltaC}
4500, !- Heater 1 Capacity {W}
1.129 , !- Heater 1 Height {m}
Plant Hot Water Setpoint Temp Schedule , !- Heater 2 Setpoint Temperature Schedule Name
18.5, !- Heater 2 Deadband Temperature Difference {deltaC}
0, !- Heater 2 Capacity {W}
0.266 , !- Heater 2 Height {m}
Electricity , !- Heater Fuel Type
1, !- Heater Thermal Efficiency
8.3, !- Off Cycle Parasitic Fuel Consumption Rate {W}
Electricity , !- Off Cycle Parasitic Fuel Type
0, !- Off Cycle Parasitic Heat Fraction to Tank
1, !- Off Cycle Parasitic Height {m}
8.3, !- On Cycle Parasitic Fuel Consumption Rate {W}
Electricity , !- On Cycle Parasitic Fuel Type
0, !- On Cycle Parasitic Heat Fraction to Tank
1, !- On Cycle Parasitic Height {m}
Outdoors , !- Ambient Temperature Indicator
, !- Ambient Temperature Schedule Name
, !- Ambient Temperature Zone Name
, !- Ambient Temperature Outdoor Air Node Name
0.7878 , !- Uniform Skin Loss Coefficient per Unit Area to Ambient Temperature
{W/m2 -K}
1, !- Skin Loss Fraction to Zone
, !- Off Cycle Flue Loss Coefficient to Ambient Temperature {W/K}
1, !- Off Cycle Flue Loss Fraction to Zone
0.001 , !- Peak Use Flow Rate {m3/s}
, !- Use Flow Rate Fraction Schedule Name
, !- Cold Water Supply Temperature Schedule Name
HPWH Use Inlet Node , !- Use Side Inlet Node Name
HPWH Use Outlet Node , !- Use Side Outlet Node Name
1, !- Use Side Effectiveness
0, !- Use Side Inlet Height {m}
autocalculate , !- Use Side Outlet Height {m}
HPPlantWaterOutletNode , !- Source Side Inlet Node Name
HPPlantWaterInletNode , !- Source Side Outlet Node Name
1, !- Source Side Effectiveness
0.7, !- Source Side Inlet Height {m}
0, !- Source Side Outlet Height {m}
Fixed , !- Inlet Mode
autosize , !- Use Side Design Flow Rate {m3/s}
autosize , !- Source Side Design Flow Rate {m3/s}
1.5, !- Indirect Water Heating Recovery Time {hr}
12; !- Number of Nodes
OutdoorAir:Node ,
HPWHPlantTank OA Node; !- Name
Fan:OnOff ,
HPWHPlantFan , !- Name
PlantHPWHSch , !- Availability Schedule Name
0.1722 , !- Fan Total Efficiency
65, !- Pressure Rise {Pa}
0.2279 , !- Maximum Flow Rate {m3/s}
1, !- Motor Efficiency
0, !- Motor In Airstream Fraction
HPPlantAirInletNode , !- Air Inlet Node Name
HPPlantFanAirOutletNode ; !- Air Outlet Node Name
1.24.6.2 Outputs
that the parasitic power does not contribute to heating the water, but it can impact the zone air
heat balance depending on user inputs. The parasitic electric consumption outputs are also added
to a meter with Resource Type = Electricity, End Use Key = DHW, Group Key = Plant (ref.
Output:Meter objects).
– ThermalStorage:Ice:Simple
– ThermalStorage:Ice:Detailed
– ThermalStorage:ChilledWater:Mixed
– ThermalStorage:ChilledWater:Stratified
These objects are typically placed on the supply side of a primary chilled water loop in series or
in parallel with one or more chillers. Using the the component set point (PlantEquipmentOper-
ation:ComponentSetpoint) plant operation scheme type, the chiller and storage tank setpoints are
used to control operation. Using a SetpointManager:Scheduled object (or other appropriate type
of set point manager), the setpoints on the chiller outlet node and the ice storage outlet node can
be used to control how the cooling load is shared and when charging of storage occurs. Example
setpoints to use for various modes of operation are shown in the table below:
Example files have been developed for three common storage configurations:
1. Series – Chiller Upstream: In this configuration, a chiller is placed first on the same branch as
the storage unit.
2. Series – Chiller Downstream: In this configuration, a chiller is placed second on the same branch
as the storage unit.
3. Parallel: In this configuration, the chiller is on a branch parallel to the storage unit branch
when it is not charging. During charging mode, valves will be changed so that the chiller is in
series upstream of the storage. To accomplish this in EnergyPlus, the chiller must be modeled
using two different chiller objects to represent the same chiller. One chiller object on a parallel
branch operates only when storage is not being charged. The other chiller object, in series
upstream of the storage unit operates only during charging mode.
1000 CHAPTER 1. INPUT-OUTPUT REFERENCE
– In the PlantLoop object, the “Minimum Loop Temperature” must be set equal to or less than
the lowest setpoint to be used anywhere in the loop.
– To end the storage charging cycle, use a AvailabilityManager:LowTemperatureTurnOff to shut
off the primary chilled water loop when the temperature leaving the storage tank nears the
charging mode chiller setpoint indicating that the tank is fully charged. For example, if the
chiller is set to provide –5C chilled water during charging, then charging can be shut down
when the water temperature leaving the storage unit reaches –4C. When using a primary-
secondary loop arrangement, it may be necessary to schedule this availability manager to be
active only when the HVAC systems are off to avoid fighting between the demand controls and
the availability manager.
1.24.8 ThermalStorage:Ice:Simple
This thermal storage model is based on a simple simulation of an ice storage tank with a fixed
capacity. The tank is charged, or frozen, in an ice-on-coil configuration where ice builds up on the
outside of the tubes carrying the brine or glycol solution from the chiller. There are two discharge
(melt) options, internal or external. Internal melt uses the same fluid tubes for charging and dis-
charging. External melt uses a separate fluid path for discharge such that the outer layers of ice melt
first. The ice storage model includes an implied 3-way valve to control the amount of charge/dis-
charge based on the incoming water temperature and the outlet node setpoint temperature. The
storage tank is assumed to be fully charged (full of ice) at the beginning of each environment. The
tank is then allowed to charge and discharge during the warmup days of the environment. The tank
is best controlled using the PlantEquipmentOperation:ComponentSetpoint plant operation scheme,
and requires that a setpoint be placed by a set point manager on the ice storage Plant Outlet Node.
The input fields for the object are described in detail below:
1.24.8.1 Inputs
ThermalStorage:Ice:Simple ,
ITS , !- Ice Storage Name
IceOnCoilInternal , !- Ice Storage Type
1.5, !- Ice Storage Capacity {GJ}
ITS Inlet Node , !- Plant Loop Inlet Node
ITS Outlet Node; !- Plant Loop Outlet Node
1.24.8.2 Outputs
The following outputs are available for simple Ice Storage model:
1.24.9 ThermalStorage:Ice:Detailed
The detailed ice storage model allows the users of EnergyPlus to model more closely specific manu-
facturers’ ice storage units. This is possible due to the use of curve fits to simulate the performance
of the ice storage unit during charging and discharging. In this implementation, both charging and
discharging are a function of the fraction charged/discharged as well as the log mean temperature
difference across the storage unit. More information on the model is provided in the Engineering
Reference for EnergyPlus. The remainder of this section describes the input required for the detailed
ice storage model and the output that it can produce.
1.24.9.1 Inputs
– FractionChargedLMTD (where Fraction Charged is the first independent variable and LMTD
is the second independent variable)
– FractionDischargedLMTD (where Fraction Discharged is the first independent variable and
LMTD is the second independent variable)
– LMTDMassFlow (where LMTD is the first independent variable and Mass Flow rate is the
second independent variable)
– LMTDFractionCharged (where LMTD is the first independent variable and Fraction Charged
is the second independent variable)
More information on curve types can be found in the section on Curves. For additional information
on how these curves are used in the Detailed Ice Storage model, please consult the Engineering
Reference.
– FractionChargedLMTD (where Fraction Charged is the first independent variable and LMTD
is the second independent variable)
– FractionDischargedLMTD (where Fraction Discharged is the first independent variable and
LMTD is the second independent variable)
– LMTDMassFlow (where LMTD is the first independent variable and Mass Flow rate is the
second independent variable)
1004 CHAPTER 1. INPUT-OUTPUT REFERENCE
– LMTDFractionCharged (where LMTD is the first independent variable and Fraction Charged
is the second independent variable)
More information on curve types can be found in the section on Curves. For additional information
on how these curves are used in the Detailed Ice Storage model, please consult the Engineering
Reference.
parameter using the “InsideMelt” option for this field. Other systems melt the ice from the outside,
leaving ice still on the charging surface when charging begins. These systems are modeled using the
“OutsideMelt” option. For systems that have a charging process that does not vary significantly
with fraction charged can ignore this input by accepting the default value. The default value for
this field is “OutsideMelt”.
An IDF example:
ThermalStorage:Ice:Detailed ,
Ice Tank , !- Ice Storage Name
ON , !- Ice Storage availability schedule
0.5, !- Ice Storage Capacity {GJ}
Ice Tank Inlet Node , !- Plant Loop Inlet Node
Ice Tank Outlet Node , !- Plant Loop Outlet Node
FractionDischargedLMTD , !- Discharging Curve Fit Type
DischargeCurve , !- Discharging Curve Name
FractionChargedLMTD , !- Charging Curve Fit Type
ChargeCurve , !- Charging Curve Name
1.0, !- Timestep of Curve Fit Data
0.0001 , !- Parasitic electric load during discharging
0.0002 , !- Parasitic electric load during charging
0.0003 , !- Tank loss coefficient
0.0; !- Freezing temperature [C]
1.24.9.2 Outputs
1.24.10 ThermalStorage:ChilledWater:Mixed
The ThermalStorage:ChilledWater:Mixed object analytically solves the differential equation govern-
ing the energy balance of the water tank. The chilled water is “used” by drawing from the “Use
Side” of the water tank. The tank is indirectly charged by circulating cold water through the
“Source Side” of the water tank.
Control is based on cycling flow through the source side. When the tank temperature rises above a
“cut-in” temperature, source side flow is requested. Source side flow will continue until the tank is
cooled to below the tank set point or “cut-out” temperature.
For heat gains from the ambient environment, the ambient air temperature can be taken from a
schedule, a zone, or the exterior. When used with a zone, the skin gains are removed from the zone
heat balance as negative internal heat gains.
1.24.10.1 Inputs
ThermalStorage:ChilledWater:Mixed ,
Chilled Water Storage Tank 1 , !- Name
4.0 , !- Tank Volume
CW -Tank -Temp -Schedule , !- Setpoint Temperature Schedule Name
3.5, !- Deadband Temperature Difference
1.0 , !- Minimum Temperature Limit
25000 , !- Nominal Cooling Capacity
Zone , !- Ambient Temperature Indicator
, !- Ambient Temperature Schedule Name
ZN_1_FLR_1_SEC_5 , !- Ambient Temperature Zone Name
, !- Ambient Temperature Outdoor Air Node Name
5.0 , !- Heat Gain Coefficient from Ambient Temperature
CW Tank Discharge Inlet node , !- Use Side Inlet Node Name
CW Tank Discharge Outlet node , !- Use Side Outlet Node Name
1.0 , !- Use Side Effectiveness
TES Use Schedule , !- Use Side Availability Schedule Name
Autosize , !- Use Side Design Flow Rate
CW Tank Charge Inlet Node , !- Source Side Inlet Node Name
CW Tank Charge Outlet Node , !- Source Side Outlet Node Name
1.0, !- Source Side Effectiveness
TES Charge Schedule , !- Source Side Availability Schedule Name
Autosize , !- Source Side Design Flow Rate
4.0; !- Tank Recovery Time
1.24.10.2 Outputs
The following output variables are reported for chilled water thermal storage tanks.
– Chilled Water Thermal Storage Source Side Mass Flow Rate !- HVAC Average [kg/s]
– Chilled Water Thermal Storage Source Side Inlet Temperature !- HVAC Average [C]
– Chilled Water Thermal Storage Source Side Outlet Temperature !- HVAC Average [C]
– Chilled Water Thermal Storage Source Side Heat Transfer Rate !- HVAC Average
[W]
– Chilled Water Thermal Storage Source Side Heat Transfer Energy !- HVAC Sum [J]
1.24.10.2.3 Chilled Water Thermal Storage Tank Heat Gain Rate [W]
The average heat exchange rate to the storage tank from the surrounding ambient. This is usually
positive with surrounding ambient heating the storage tank.
1.24.10.2.4 Chilled Water Thermal Storage Tank Heat Gain Energy [J]
The energy exchange to the storage tank from the surrounding ambient. This is usually positive
with surrounding ambient heating the storage tank.
1.24.10.2.5 Chilled Water Thermal Storage Use Side Mass Flow Rate [kg/s]
The use side mass flow rate.
1.24.10.2.6 Chilled Water Thermal Storage Use Side Inlet Temperature [C]
The inlet temperature on the use side.
1.24.10.2.7 Chilled Water Thermal Storage Use Side Outlet Temperature [C]
The outlet temperature on the use side.
1.24.10.2.8 Chilled Water Thermal Storage Use Side Heat Transfer Rate [W]
The average heat transfer rate between the use side water and the tank water.
1.24.10.2.9 Chilled Water Thermal Storage Use Side Heat Transfer Energy [J]
The heat transfer energy between the use side water and the tank water.
1.24.10.2.10 Chilled Water Thermal Storage Source Side Mass Flow Rate [kg/s]
1.24.10.2.11 Chilled Water Thermal Storage Source Side Inlet Temperature [C]
1.24.10.2.13 Chilled Water Thermal Storage Source Side Heat Transfer Rate [W]
The average heat transfer rate between the source side water and the tank water.
1.24.10.2.14 Chilled Water Thermal Storage Source Side Heat Transfer Energy
[J]
The heat transfer energy between the source side water and the tank water.
1.24.11 ThermalStorage:ChilledWater:Stratified
The ThermalStorage:ChilledWater:Stratified object divides the water tank into multiple nodes of
equal volume. The nodes are coupled by vertical conduction effects, internode fluid flow, and tem-
perature inversion mixing. The object simultaneously solves the differential equations governing
the energy balances on the nodes using a numerical method. The system timestep is divided into
many small substeps that allow the simulation to capture events that occur on a very short time
scale. The chilled water is “used” by drawing from the “Use Side” of the water tank. The tank is
indirectly charged by circulating cold water through the “Source Side” of the water tank.
Control is based on cycling flow through the source side. When the tank temperature rises above a
“cut-in” temperature, source side flow is requested. Source side flow will continue until the tank is
cooled to below the tank set point or “cut-out” temperature.
For heat gains from the ambient environment, the ambient air temperature can be taken from a
schedule, a zone, or the exterior. When used with a zone, the skin gains are removed from the zone
heat balance as negative internal heat gains.
1.24.11.1 Inputs
1.24.11.1.15 Field: Uniform Skin Loss Coefficient per Unit Area to Ambient
Temperature
The uniform skin loss coefficient [W/m2 -K] or U-Value of the tank to the ambient air temperature.
The uniform skin loss accounts for the tank insulation. The overall losses at any particular tank node
can be further modified using the Additional Loss Coefficient fields to account for thermal shorting
due to pipe penetrations, tank feet, and any other loss effects.
ThermalStorage:ChilledWater:Stratified ,
Chilled Water Storage Tank 1 , !- Name
4.0 , !- Tank Volume
2.0 , !- Tank Height
1.24. GROUP – WATER HEATERS AND THERMAL STORAGE 1017
1.24.11.2 Outputs
The following output variables are reported for stratified chilled water thermal storage tanks.
1.24.11.2.3 Chilled Water Thermal Storage Tank Heat Gain Rate [W]
The average heat exchange rate to the storage tank from the surrounding ambient. This is usually
positive with surrounding ambient heating the storage tank.
1.24.11.2.4 Chilled Water Thermal Storage Tank Heat Gain Energy [J]
The energy exchange to the storage tank from the surrounding ambient. This is usually positive
with surrounding ambient heating the storage tank.
1.24.11.2.5 Chilled Water Thermal Storage Use Side Mass Flow Rate [kg/s]
The use side mass flow rate.
1.24.11.2.6 Chilled Water Thermal Storage Use Side Inlet Temperature [C]
The inlet temperature on the use side.
1.24.11.2.7 Chilled Water Thermal Storage Use Side Outlet Temperature [C]
The outlet temperature on the use side.
1.24.11.2.8 Chilled Water Thermal Storage Use Side Heat Transfer Rate [W]
The average heat transfer rate between the use side water and the tank water.
1.24.11.2.9 Chilled Water Thermal Storage Use Side Heat Transfer Energy [J]
The heat transfer energy between the use side water and the tank water.
1.24.11.2.10 Chilled Water Thermal Storage Source Side Mass Flow Rate [kg/s]
1.24.11.2.11 Chilled Water Thermal Storage Source Side Inlet Temperature [C]
1.24.11.2.13 Chilled Water Thermal Storage Source Side Heat Transfer Rate [W]
The average heat transfer rate between the source side water and the tank water.
1.24.11.2.14 Chilled Water Thermal Storage Source Side Heat Transfer Energy
[J]
The heat transfer energy between the source side water and the tank water.
1.24.11.2.16 Chilled Water Thermal Storage Final Temperature Node 1-10 [C]
1.25.2 CoolingTower:SingleSpeed
Cooling towers are components that may be assigned to condenser loops. The cooling tower is mod-
eled as a counterflow heat exchanger with a single-speed fan (induced draft configuration) based
on Merkel’s theory. The user must define tower performance via one of two methods: design heat
transfer coefficient-area product (UA) and design water flow rate, or nominal tower capacity at a
specific rating point. Regardless of which method is chosen, the design airflow rate and correspond-
ing fan power must be specified. The model will also account for tower performance in the “free
convection” regime, when the tower fan is off but the water pump remains on and heat transfer still
occurs (albeit at a low level). If the user wants the model to account for “free convection”, they
must specify the corresponding airflow rate and heat transfer coefficient-area product (UA), or the
nominal tower capacity during this mode of operation.
The cooling tower seeks to maintain the temperature of the water exiting the cooling tower at (or
below) a set point. The set point schedule value is defined by the field “Condenser Loop Temper-
ature Setpoint Node Name or Reference” for the CondenserLoop object. The model first checks to
1020 CHAPTER 1. INPUT-OUTPUT REFERENCE
determine the impact of “free convection”, if specified by the user, on the tower exiting water tem-
perature. If the exiting water temperature based on “free convection” is at or below the set point,
then the tower fan is not turned on. If the exiting water temperature based on “free convection” is
below the set point, the tower will operate in FluidBypass mode – portion of the water goes through
the tower media and gets cooled while the remaining water flow gets bypassed, two water flows
then mix together trying to meet the water setpoint temperature. If the exiting water temperature
remains above the set point after “free convection” is modeled, then the tower fan is turned on to
reduce the exiting water temperature to the set point. If the capacity control is FanCycling, the
model assumes that part-load operation is represented by a simple linear interpolation between two
steady-state regimes (i.e., tower fan on for the entire simulation timestep and tower fan off for the
entire simulation timestep). Cyclic losses are not taken into account. If the capacity control is
FluidBypass, the model determines the fraction of water flow to be bypassed while the remaining
water goes through the tower cooling media and gets cooled, then the two water flows mix to meet
the setpoint temperature. In this case, the fan runs at full speed for the entire timestep.
Cooling towers here are “wet” and consume water through evaporation, drift, and blowdown. The
model can be used to predict water consumed by the towers. The last six input fields are optional and
provide methods of controlling details of the water consumption calculations. The user can specify
connections to the rest of the buildings water system by providing the name of a water storage tanks
(i.e. WaterUse:Storage objects).
For the operation of multi-cell towers, the first step is to determine the number of cells to operate
based on the cell control method – between the minimum number of cells subject to the maximum
water flow rate fraction per cell, and maximum number of cells subject to the minimum water flow
rate fraction per cell. If the calculated cells do not meet the loads, additional cells will be operating
to help meet the loads. Inside each cell, the existing capacity controls still apply.
For multi-cell towers, the following inputs are assumed to be for the entire tower including all cells:
– Design Water Flow Rate; Design Air Flow Rate; Fan Power at Design Air Flow Rate;
– Air Flow Rate in Free Convection Regime; Nominal Capacity; Free Convection Capacity
– BASIN HEATER (we assume that there is a common basin)
1.25.2.1 Inputs
sprayed on the outside of the heat exchange coil). If the input field “Performance Input Method” is
specified as “UFactorTimesAreaAndDesignWaterFlowRate”, then a water flow rate greater than zero
must be defined or the field can be autosized. If autosized, a Plant Sizing object must be defined and
the design water flow rate is derived from the design load to be rejected by the condenser loop and
the design loop delta T (Ref. Sizing and Input for Design Calculations and Component Autosizing
sections). If “Performance Input Method” is specified as “NominalCapacity”, then this field must
be left blank since the model automatically assumes a water flow rate of 5.382E-8 m3/s per watt (3
gpm/ton) of tower capacity specified in the field “Nominal Capacity”.
F an power = 0.0105 · ρwater · Cp,water · Design W ater F low Rate · Design Loop∆T (1.94)
is used.
If“Performance Input Method” is specified as “NominalCapacity”, then
is used.
1.25.2.1.9 Field: Free Convection Regime Air Flow Rate Sizing Factor
This numeric field contains the sizing factor to use when calculating the free convection regime air
flow rate. The default is 0.1.
1.25.2.1.11 Field: Free Convection U-Factor Times Area Value Sizing Factor
This numeric field contains the sizing factor to use when calculating the free convection regime
U-Factor times area value. The default is 0.1.
1.25.2.1.13 Field: Heat Rejection Capacity and Nominal Capacity Sizing Ratio
This numeric field contains the value for the ratio of actual tower heat rejection to nominal capac-
ity. This ratio is defined at entering water at 35C (95F), leaving water at 29.4C (85F), entering air
1.25. GROUP – CONDENSER EQUIPMENT 1023
at 25.6C (78F) wetbulb and 35C (95F) drybulb temperatures. Historically this ratio has been set at
1.25 based on the assumption that the tower must dissipate 0.25 W of compressor power for every
what of heat removed at the chiller evaporator. The default is 1.25.
CoolingTower:SingleSpeed ,
My Tower , !- Name
Condenser Tower Inlet Node , !- Water Inlet Node Name
Condenser Tower Outlet Node , !- Water Outlet Node Name
.0011 , !- Design Water Flow Rate {m3/s}
16.0, !- Design Air Flow Rate {m3/s}
10000. , !- Design Fan Power {W}
3500. , !- Design U-Factor Times Area Value {W/K}
0.0, !- Free Convection Air Flow Rate {m3/s}
, !- Free Convection Air Flow Rate Sizing Factor
0.0, !- Free Convection U-Factor Times Area Value {W/K}
, !- Free Convection U-Factor Times Area Value Sizing Factor
UFactorTimesAreaAndDesignWaterFlowRate , !- Performance Input Method
, !- Heat Rejection Capacity and Nominal Capacity Sizing Ratio
, !- Nominal Capacity {W}
, !- Free Convection Capacity {W}
, !- Free Convection Nominal Capacity Sizing Factor
, !- Design Inlet Air Dry -Bulb Temperature {C}
, !- Design Inlet Air Wet -Bulb Temperature {C}
, !- Design Approach Temperature {deltaC}
, !- Design Range Temperature {deltaC}
, !- Basin Heater Capacity {W/K}
, !- Basin Heater Setpoint Temperature {C}
, !- Basin Heater Operating Schedule Name
, !- Evaporation Loss Mode
, !- Evaporation Loss Factor {percent/K}
, !- Drift Loss Percent {percent}
, !- Blowdown Calculation Mode
, !- Blowdown Concentration Ratio
, !- Blowdown Makeup Water Usage Schedule Name
, !- Supply Water Storage Tank Name
, !- Outdoor Air Inlet Node Name
FluidBypass , !- Capacity Control
4, !- Number of Cells
MinimalCell , !- Cell Control
, !- Cell Minimum Water Flow Rate Fraction
, !- Cell Maximum Water Flow Rate Fraction
1.0000; !- Sizing Factor
CoolingTower:SingleSpeed ,
My Tower , !- Name
Condenser Tower Inlet Node , !- Water Inlet Node Name
Condenser Tower Outlet Node ,!- Water Outlet Node Name
, !- Design Water Flow Rate {m3/s}
1028 CHAPTER 1. INPUT-OUTPUT REFERENCE
CoolingTower:SingleSpeed ,
TowerWaterSys CoolTower , !- Name
TowerWaterSys Pump -TowerWaterSys CoolTowerNode , !- Water Inlet Node Name
TowerWaterSys Supply Equipment Outlet Node , !- Water Outlet Node Name
AUTOSIZE , !- Design Water Flow Rate {m3/s}
AUTOSIZE , !- Design Air Flow Rate {m3/s}
AUTOSIZE , !- Design Fan Power {W}
AUTOSIZE , !- Design U-Factor Times Area Value {W/K}
autocalculate , !- Free Convection Air Flow Rate {m3/s}
, !- Free Convection Air Flow Rate Sizing Factor
autocalculate , !- Free Convection U-Factor Times Area Value {W/K}
, !- Free Convection U-Factor Times Area Value Sizing Factor
UFactorTimesAreaAndDesignWaterFlowRate , !- Performance Input Method
, !- Heat Rejection Capacity and Nominal Capacity Sizing Ratio
, !- Nominal Capacity {W}
, !- Free Convection Capacity {W}
, !- Free Convection Nominal Capacity Sizing Factor
, !- Design Inlet Air Dry -Bulb Temperature {C}
, !- Design Inlet Air Wet -Bulb Temperature {C}
, !- Design Approach Temperature {deltaC}
, !- Design Range Temperature {deltaC}
, !- Basin Heater Capacity {W/K}
, !- Basin Heater Setpoint Temperature {C}
, !- Basin Heater Operating Schedule Name
SaturatedExit , !- Evaporation Loss Mode
, !- Evaporation Loss Factor {percent/K}
0.0080 , !- Drift Loss Percent {percent}
ConcentrationRatio , !- Blowdown Calculation Mode
3.0000 , !- Blowdown Concentration Ratio
, !- Blowdown Makeup Water Usage Schedule Name
, !- Supply Water Storage Tank Name
TowerWaterSys CoolTower OA ref Node , !- Outdoor Air Inlet Node Name
FanCycling , !- Capacity Control
4, !- Number of Cells
MinimalCell , !- Cell Control
, !- Cell Minimum Water Flow Rate Fraction
, !- Cell Maximum Water Flow Rate Fraction
1.0000; !- Sizing Factor
OutdoorAir:Node ,
TowerWaterSys CoolTower OA ref Node; !- Name
1.25.2.2 Outputs
A tower uses either mains water or storage tank for make-up water.
When mains water is used:
IF specified:
1.25.2.2.18 Cooling Tower Storage Tank Water Volume Flow Rate [m3/s]
1.25. GROUP – CONDENSER EQUIPMENT 1031
1.25.2.2.20 Cooling Tower Starved Storage Tank Water Volume Flow Rate
[m3/s]
1.25.3 CoolingTower:TwoSpeed
The two-speed cooling tower is modeled in a similar fashion to the single-speed tower. The cooling
tower is modeled as a counterflow heat exchanger with a two-speed fan (induced draft configuration)
based on Merkel’s theory. The user must define tower performance via one of two methods: heat
transfer coefficient-area product (UA) and design water flow rate, or nominal tower capacity at a
specific rating point. Regardless of which method is chosen, the airflow rate and corresponding fan
power at both high and low fan speed must be specified. The model will also account for tower
performance in the “free convection” regime, when the tower fan is off but the water pump remains
on and heat transfer still occurs (albeit at a low level). If the user wants the model to account for
“free convection”, they must specify the corresponding air flow rate and heat transfer coefficient-area
product (UA), or the nominal tower capacity during this mode of operation.
The cooling tower seeks to maintain the temperature of the water exiting the cooling tower at (or
below) a set point. The set point schedule value is defined by the field “Condenser Loop Temper-
ature Setpoint Node Name or Reference” for the CondenserLoop object. The model first checks
to determine the impact of “free convection”, if specified by the user, on the tower exiting water
temperature. If the exiting water temperature based on “free convection” is at or below the set
point, then the tower fan is not turned on. If the exiting water temperature remains above the set
point after “free convection” is modeled, then the tower fan is turned on at low speed to reduce the
exiting water temperature. If operating the tower fan at low speed does not reduce the exiting water
temperature to the set point, then the tower fan is increased to its high speed.
The model assumes that part-load operation is represented by a simple linear interpolation between
two steady-state regimes (i.e., tower fan at high speed for the entire simulation timestep and tower fan
1032 CHAPTER 1. INPUT-OUTPUT REFERENCE
at low speed for the entire simulation timestep, or tower fan at low speed for the entire simulation
timestep and tower fan off for the entire simulation timestep). Cyclic losses are not taken into
account.
Cooling towers here are “wet” and consume water through evaporation, drift, and blowdown. The
model can be used to predict water consumed by the towers. The last six input fields are optional and
provide methods of controlling details of the water consumption calculations. The user can specifiy
connections to the rest of the buildings water system by providing the name of a WaterUse:Storage
object.
For the operation of multi-cell towers, the first step is to determine the number of cells to operate
based on the cell control method – between the minimum number of cells subject to the maximum
water flow rate fraction per cell, and maximum number of cells subject to the minimum water flow
rate fraction per cell. If the calculated cells do not meet the loads, additional cells will be operating
to help meet the loads. Inside each cell, the existing capacity controls still apply.
For multi-cell towers, the following inputs are assumed to be for the entire tower including all cells:
– Design Water Flow Rate; Design Air Flow Rate; Fan Power at Design Air Flow Rate;
– Air Flow Rate in Free Convection Regime; Nominal Capacity; Free Convection Capacity
– BASIN HEATER (we assume that there is a common basin)
1.25.3.1 Inputs
where a fan pressure rise of 190 Pascals and total fan efficiency of 0.5 are assumed.
Field: High Fan Speed Fan Power
This numeric field contains the fan power (in Watts) at the high-speed air flow rate specified in the
previous field. A value greater than zero must be specified regardless of the tower performance input
method, or this field can be autosized. If autosized, the fan power is calculated as follows:
If“Performance Input Method” is specified as “UFactorTimesAreaAndDesignWaterFlowRate”, then
F an powerHigh F an Speed = 0.0105 · ρwater · Cp,water · Design W ater F low Rate · Design Loop∆T
(1.97)
is used.
If“Performance Input Method” is specified as “NominalCapacity”, then
is used.
1.25.3.1.8 Field: Low Fan Speed Air Flow Rate Sizing Factor
This numeric field contains the sizing factor to use when calculating the low fan speed air flow
rate. The default is 0.5.
1.25.3.1.12 Field: Low Fan Speed U-Factor Times Area Sizing Factor
This numeric field contains the sizing factor to use when calculating the low speed heat transfer
coefficient-area product (UA). The default is 0.6.
1.25.3.1.16 Field: Free Convection U-Factor Times Area Value Sizing Factor
This numeric field contains the sizing factor to use when calculating the free convection regime
U-Factor times area value. The default is 0.1.
1.25.3.1.18 Field: Heat Rejection Capacity and Nominal Capacity Sizing Ratio
This numeric field contains the value for the ratio of actual tower heat rejection to nominal capac-
ity. This ratio is defined at entering water at 35C (95F), leaving water at 29.4C (85F), entering air
at 25.6C (78F) wetbulb and 35C (95F) drybulb temperatures. Historically this ratio has been set at
1.25 based on the assumption that the tower must dissipate 0.25 W of compressor power for every
what of heat removed at the chiller evaporator. The default is 1.25.
be the outlet water temperature minus the inlet air wet-bulb temperature at design conditions. This
parameter is autosizable and when autosized it is set to 3.9 ◦C.
The evaporation loss is then calculated as a fraction of the circulating condenser water flow and
varies with the temperature change in the condenser water. The value entered here is in units of
percent-per-degree Kelvin. The evaporation rate will equal this value times each degree Kelvin of
temperature drop in the condenser water. Typical values are from 0.15 to 0.27 [percent/K]. The
default is 0.2.
CoolingTower:TwoSpeed ,
My Tower , !- Name
Condenser Tower Inlet Node , !- Water Inlet Node Name
Condenser Tower Outlet Node , !- Water Outlet Node Name
.0011 , !- Design Water Flow Rate {m3/s}
16.0, !- High Fan Speed Air Flow Rate {m3/s}
10000. , !- High Fan Speed Fan Power {W}
3500. , !- High Fan Speed U-Factor Times Area Value {W/K}
8.0, !- Low Fan Speed Air Flow Rate {m3/s}
, !- Low Fan Speed Air Flow Rate Sizing Factor
1600. , !- Low Fan Speed Fan Power {W}
, !- Low Fan Speed Fan Power Sizing Factor
2100. , !- Low Fan Speed U-Factor Times Area Value {W/K}
, !- Low Fan Speed U-Factor Times Area Sizing Factor
1.6, !- Free Convection Regime Air Flow Rate {m3/s}
, !- Free Convection Regime Air Flow Rate Sizing Factor
350., !- Free Convection Regime U-Factor Times Area Value {W/K}
, !- Free Convection U-Factor Times Area Value Sizing Factor
UFactorTimesAreaAndDesignWaterFlowRate ; !- Performance Input Method
CoolingTower:TwoSpeed ,
My Tower , !- Name
Condenser Tower Inlet Node , !- Water Inlet Node Name
Condenser Tower Outlet Node , !- Water Outlet Node Name
, !- Design Water Flow Rate {m3/s}
8.0, !- High Fan Speed Air Flow Rate {m3/s}
500, !- High Fan Speed Fan Power {W}
, !- High Fan Speed U-Factor Times Area Value {W/K}
4.0, !- Low Fan Speed Air Flow Rate {m3/s}
, !- Low Fan Speed Air Flow Rate Sizing Factor
125, !- Low Fan Speed Fan Power {W}
, !- Low Fan Speed Fan Power Sizing Factor
, !- Low Fan Speed U-Factor Times Area Value {W/K}
, !- Low Fan Speed U-Factor Times Area Sizing Factor
0.8, !- Free Convection Regime Air Flow Rate {m3/s}
1.25. GROUP – CONDENSER EQUIPMENT 1041
CoolingTower:TwoSpeed ,
Big Tower1 , !- Name
Condenser Tower Inlet Node , !- Water Inlet Node Name
Condenser Tower Outlet Node , !- Water Outlet Node Name
, !- Design Water Flow Rate {m3/s}
8.0, !- High Fan Speed Air Flow Rate {m3/s}
500, !- High Fan Speed Fan Power {W}
, !- High Fan Speed U-Factor Times Area Value {W/K}
4.0, !- Low Fan Speed Air Flow Rate {m3/s}
, !- Low Fan Speed Air Flow Rate Sizing Factor
125, !- Low Fan Speed Fan Power {W}
, !- Low Fan Speed Fan Power Sizing Factor
, !- Low Fan Speed U-Factor Times Area Value {W/K}
, !- Low Fan Speed U-Factor Times Area Sizing Factor
0.8, !- Free Convection Regime Air Flow Rate {m3/s}
, !- Free Convection Regime Air Flow Rate Sizing Factor
, !- Free Convection Regime U-Factor Times Area Value {W/K}
, !- Free Convection U-Factor Times Area Value Sizing Factor
NominalCapacity , !- Performance Input Method
, !- Heat Rejection Capacity and Nominal Capacity Sizing Ratio
20000.0 , !- High Speed Nominal Capacity {W}
10000.0 , !- Low Speed Nominal Capacity {W}
, !- Low Speed Nominal Capacity Sizing Factor
2000.0 , !- Free Convection Nominal Capacity {W}
; !- Free Convection Nominal Capacity Sizing Factor
, !- Design Inlet Air Dry -Bulb Temperature {C}
, !- Design Inlet Air Wet -Bulb Temperature {C}
, !- Design Approach Temperature {deltaC}
, !- Design Range Temperature {deltaC}
, !- Basin Heater Capacity {W/K}
, !- Basin Heater Setpoint Temperature {C}
, !- Basin Heater Operating Schedule Name
SaturatedExit , !- Evaporation Loss Mode
, !- Evaporation Loss Factor {percent/K}
0.0080 , !- Drift Loss Percent {percent}
ConcentrationRatio , !- Blowdown Calculation Mode
3.0000 , !- Blowdown Concentration Ratio
, !- Blowdown Makeup Water Usage Schedule Name
Recovery Tank; !- Supply Water Storage Tank Name
CoolingTower:TwoSpeed ,
TowerWaterSys CoolTower , !- Name
TowerWaterSys Pump -TowerWaterSys CoolTowerNode , !- Water Inlet Node Name
TowerWaterSys Supply Equipment Outlet Node , !- Water Outlet Node Name
AUTOSIZE , !- Design Water Flow Rate {m3/s}
AUTOSIZE , !- High Fan Speed Air Flow Rate {m3/s}
AUTOSIZE , !- High Fan Speed Fan Power {W}
AUTOSIZE , !- High Fan Speed U-Factor Times Area Value {W/K}
autocalculate , !- Low Fan Speed Air Flow Rate {m3/s}
, !- Low Fan Speed Air Flow Rate Sizing Factor
autocalculate , !- Low Fan Speed Fan Power {W}
, !- Low Fan Speed Fan Power Sizing Factor
autocalculate , !- Low Fan Speed U-Factor Times Area Value {W/K}
, !- Low Fan Speed U-Factor Times Area Sizing Factor
autocalculate , !- Free Convection Regime Air Flow Rate {m3/s}
, !- Free Convection Regime Air Flow Rate Sizing Factor
autocalculate , !- Free Convection Regime U-Factor Times Area Value {W/K}
1042 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.25.3.2 Outputs
A tower uses either mains water or storage tank for make-up water.
When mains water is used:
IF specified:
1.25.3.2.18 Cooling Tower Storage Tank Water Volume Flow Rate [m3/s]
1.25.3.2.20 Cooling Tower Starved Storage Tank Water Volume Flow Rate
[m3/s]
1.25.4 CoolingTower:VariableSpeed:Merkel
This variable speed tower model is based on Merkel’s theory and is similar to the single-speed and
two-speed tower models. The open wet cooling tower is modeled as a counter flow heat exchanger
with a variable-speed fan drawing air through the tower (induced-draft configuration). The model
also includes a “free convection” regime where cooling tower performance is modeled with the fan
off.
For this model, Merkel’s theory is modified to include adjustments developed by Scheier to alter the
heat transfer effectiveness based on current wetbulb, air flow rates, and water flow rates. The input
requires performance curves or lookup tables to describe these three adjustment factors.
For a multi-cell tower, the capacity and air/water flow rate inputs are for the entire tower.
1.25.4.1 Inputs
1.25.4.1.5 Field: Heat Rejection Capacity and Nominal Capacity Sizing Ratio
This numeric field contains the value for the ratio of actual tower heat rejection to nominal capac-
ity. This ratio is defined at entering water at 35C (95F), leaving water at 29.4C (85F), entering air
at 25.6C (78F) wetbulb and 35C (95F) drybulb temperatures. Historically this ratio has been set at
1.25 based on the assumption that the tower must dissipate 0.25 W of compressor power for every
what of heat removed at the chiller evaporator. The default is 1.25.
1.25.4.1.10 Field: Design Water Flow Rate per Unit of Nominal Capacity
This numeric field contains a scalable sizing factor for design water flow rate that scales with nominal
capacity, in units of m3 /s/W. The default value is 5.382*10−8 . This field is only used if the previous
1.25. GROUP – CONDENSER EQUIPMENT 1047
field is set to autocalculate and performance input method is NominalCapacity. (If the performance
input method is set to UFactorTimesAreaAndDesignWaterFlowRate then the design water flow rate
is obtained from the plant sizing result.)
1.25.4.1.12 Field: Design Air Flow Rate Per Unit of Nominal Capacity
This numeric field contains the sizing factor to use when calculating the design air flow rate from the
nominal capacity, in units of m3 /s/W. The default is 2.76316*10−5 . When this field is left blank,
then the default value is used but the flow rate is also scaled to account for elevation (with larger
volume flow rates at higher altitudes). When a hard value is entered, even if it is the same as the
default, then the design air flow rate is not also adjusted for elevation and the scaling factor is used
directly.
1.25.4.1.16 Field: Fan Power Modifier Function of Air Flow Rate Ratio Curve
Name
This alpha field contains the name of a curve or table object that describes fan power ratio (fan
power/design fan power) as a function of air flow rate ratio (air flow rate/design air flow rate).
The curve or table object must be for one independent variable, typically a cubic, and should be
normalized to 1.0 at an air flow rate ratio of 1.0. This field is required.
1048 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.25.4.1.18 Field: Free Convection Regime Air Flow Rate Sizing Factor
This numeric field contains the sizing factor to use when calculating the free convection regime air
flow rate. The default is 0.1.
1.25.4.1.19 Field: Design Air Flow Rate U-Factor Times Area Value
This numeric field contains the heat transfer coefficient-area product (UA) in watts per Kelvin cor-
responding to the design air and water flow rates specified above. If the input field “Performance
Input Method” is specified as “UFactorTimesAreaAndDesignWaterFlowRate”, then a UA value
greater than zero but less than or equal to 300,000 must be defined, or the field can be autosized. If
autosized, a Plant Sizing object must be defined and the design tower UA value is derived from the
design load to be rejected by the condenser loop and the design loop delta T (Ref. Sizing and Input
for Design Calculations and Component Autosizing sections), assuming a tower water inlet temper-
ature of 35C and tower inlet air at 35C drybulb/25.6C wetbulb. If “Performance Input Method”
is specified as “NominalCapacity”, then this field must be left blank since the model automatically
calculates the tower UA based on the tower capacity specified in the field “Nominal Capacity”.
1.25.4.1.21 Field: Free Convection U-Factor Times Area Value Sizing Factor
This numeric field contains the sizing factor to use when calculating the free convection regime U-
Factor times area value. The default is 0.1. This field is only used if the previous field is set to
autocalculate and the performance input method is UFactorTimesAreaAndDesignWaterFlowRate.
1.25. GROUP – CONDENSER EQUIPMENT 1049
1.25.4.1.22 Field: U-Factor Times Area Modifier Function of Air Flow Ratio
Curve Name
This alpha field contains the name of a curve or table object that describes how the UA value varies
as a function of air flow rate ratio (air flow rate/design air flow rate). The result of this curve is
multiplied by the design UA value to adjust for air flow rate, along with the two other modifiers
discussed below. The curve or table object must be for one independent variable and should be
normalized to 1.0 at an air flow rate ratio of 1.0. This field is required.
1.25.4.1.24 Field: U-Factor Times Area Modifier Function of Water Flow Ratio
Curve Name
This alpha field contains the name of a curve or table object that describes how the UA value varies
as a function of the current water flow rate ratio (water flow rate/design water flow rate). The result
of this curve is multiplied by the design UA value to adjust for water flow rates that differ from
design level, along with the other two modifiers discussed above. The curve or table object must be
for one independent variable and should be normalized to 1.0 at a water flow ratio of 1.0. This field
is required
inlet water temperature minus the outlet water temperature at design conditions. This parameter
is autosizable and when autosized it is set to 5.5 ◦C.
CoolingTower:VariableSpeed:Merkel ,
Big Tower1 , !- Name
Condenser Tower 1 Inlet Node , !- Water Inlet Node Name
Condenser Tower 1 Outlet Node , !- Water Outlet Node Name
NominalCapacity , !- Performance Input Method
1.25, !- Heat Rejection Capacity and Nominal Capacity Sizing Ratio
20000.0 , !- Nominal Capacity {W}
1.25. GROUP – CONDENSER EQUIPMENT 1053
Curve:Cubic ,
VS tower fan power mod func air flow ratio , !- Name
0.02 , !- Coefficient1 Constant
0.0 , !- Coefficient2 x
0.0 , !- Coefficient3 x**2
0.98 , !- Coefficient4 x**3
0.2, !- Minimum Value of x
1.0 , !- Maximum Value of x
0.0 , !- Minimum Curve Output
1.0 , !- Maximum Curve Output
Dimensionless , !- Input Unit Type for X
Dimensionless; !- Output Unit Type
Curve:Quadratic ,
VS tower UA mod func air flow ratio , !- Name
0.0 , !- Coefficient1 Constant
1.3 , !- Coefficient2 x
-0.3 , !- Coefficient3 x**2
0.2 , !- Minimum Value of x
1.0 , !- Maximum Value of x
0.0 , !- Minimum Curve Output
1.0 , !- Maximum Curve Output
Dimensionless , !- Input Unit Type for X
Dimensionless; !- Output Unit Type
1054 CHAPTER 1. INPUT-OUTPUT REFERENCE
Curve:Linear ,
VS tower UA mod func wetbulb difference , !- Name
1.0 , !- Coefficient1 Constant
0.0081 , !- Coefficient2 x
-10 , !- Minimum Value of x
25.0 , !- Maximum Value of x
0.85 , !- Minimum Curve Output
1.3 , !- Maximum Curve Output
Dimensionless , !- Input Unit Type for X
Dimensionless; !- Output Unit Type
Curve:Quadratic ,
VS tower UA mod func water flow ratio , !- Name
0.1082 , !- Coefficient1 Constant
1.667 , !- Coefficient2 x
-0.7713 , !- Coefficient3 x**2
0.3 , !- Minimum Value of x
1.0 , !- Maximum Value of x
0.5 , !- Minimum Curve Output
1.1 , !- Maximum Curve Output
Dimensionless , !- Input Unit Type for X
Dimensionless; !- Output Unit Type
1.25.4.2 Outputs
A tower uses either mains water or storage tank for make-up water.
When mains water is used:
IF specified:
1.25.4.2.20 Cooling Tower Storage Tank Water Volume Flow Rate [m3/s]
1.25.4.2.22 Cooling Tower Starved Storage Tank Water Volume Flow Rate
[m3/s]
1.25.5 CoolingTower:VariableSpeed
The variable speed tower model is based on empirical curve fits of manufacturer’s performance data
or field measurements. The user specifies tower performance at design conditions, and empirical
curves are used to determine the approach temperature and fan power at off-design conditions. The
user defines tower performance by entering the inlet air wet-bulb temperature, tower range, and
tower approach temperature at the design conditions. The corresponding water flow rate (within
±25% of the tower’s rated water mass flow rate), air flow rate, and fan power must also be specified.
The model will account for tower performance in the “free convection” regime, when the tower fan is
off but the water pump remains on and heat transfer still occurs (albeit at a low level). Basin heater
operation and makeup water usage (due to evaporation, drift, and blowdown) are also modeled.
The cooling tower seeks to maintain the temperature of the water exiting the cooling tower at (or
below) a set point. The set point schedule is defined by the field “Condenser Loop Temperature
Setpoint Node Name or Reference” for the CondenserLoop object. The model first checks to deter-
mine the impact of “free convection” on the tower exiting water temperature. If the exiting water
temperature based on “free convection” is at or below the set point, then the variable-speed tower
fan is not turned on. If the exiting water temperature is above the set point after “free convection”
is modeled, then the variable-speed tower fan is turned on to reduce the exiting water temperature.
Tower fan power is calculated based on the tower air flow rate required to achieve the exiting water
set point temperature.
Cooling towers here are “wet” and consume water through evaporation, drift, and blowdown. The
model can be used to predict water consumed by the towers. The last six input fields are optional and
provide methods of controlling details of the water consumption calculations. The user can specifiy
connections to the rest of the buildings water system by providing the name of a WaterUse:Storage
object.
For the operation of multi-cell towers, the first step is to determine the number of cells to operate
based on the cell control method – between the minimum number of cells subject to the maximum
water flow rate fraction per cell, and maximum number of cells subject to the minimum water flow
rate fraction per cell. If the calculated cells do not meet the loads, additional cells will be operating
to help meet the loads. Inside each cell, the existing capacity controls still apply.
For multi-cell towers, the following inputs are assumed to be for the entire tower including all cells:
– Design Water Flow Rate; Design Air Flow Rate; Fan Power at Design Air Flow Rate;
– Air Flow Rate in Free Convection Regime; Nominal Capacity; Free Convection Capacity
– BASIN HEATER (we assume that there is a common basin)
1.25.5.1 Inputs
This value is the flow rate of the condenser loop water being cooled by the tower. A value greater
than zero must be specified or this field can be autosized. A Plant Sizing object must be defined if
the field is autosized and the design water flow rate is then derived from the design load to be rejected
by the condenser loop and the design loop delta T (Ref. Sizing and Input for Design Calculations
and Component Autosizing sections). The design water flow rate should correspond with the design
values specified for the inlet air wet-bulb temperature, approach temperature, range temperature,
and air flow rate. When this field is not autosized, the condenser loop flow rate specified in other
objects should be within ±25% of the tower’s rated water flow rate (different range is permissible if
Model Type is “User Defined”).
0.5(F an power at Design Air F low Rate) 101325.
Design Air F low Rate = (1.99)
190. Patm
Design f an power = 0.0105 · ρwater · Cp,water · Design W ater F low Rate · Design Loop∆T (1.100)
1.25.5.1.12 Field: Fan Power Ratio Function of Air Flow Rate Ratio Curve Name
This alpha field contains the curve object name for fan power ratio (fan power/design fan power)
as a function of air flow rate ratio (air flow rate/design air flow rate) [ref. Performance Curves].
The curve object must be a cubic curve and should be normalized to 1.0 at an air flow rate ratio of
1.0. If this field is left blank, a theoretical fan curve is assumed where fan power ratio is directly
proportional to the air flow rate ratio cubed.
varies with the temperature change in the condenser water. The value entered here is in units of
percent-per-degree Kelvin. The evaporation rate will equal this value times each degree Kelvin of
temperature drop in the condenser water. Typical values are from 0.15 to 0.27 [percent/K]. The
default is 0.2.
CoolingTower:VariableSpeed ,
Big Tower1 , !- Tower Name
Condenser 1 Inlet Node , !- Water Inlet Node Name
Condenser 1 Outlet Node , !- Water Outlet Node Name
YorkCalc , !- Tower Model Type
, !- Tower Model Coefficient Name
25.5556 , !- Design Inlet Air Wet -Bulb Temperature {C}
3.8889 , !- Design Approach Temperature {C}
5.5556 , !- Design Range Temperature {C}
0.0015 , !- Design Water Flow Rate {m3/s}
1.6435 , !- Design Air Flow Rate {m3/s}
275, !- Design Fan Power {W}
FanRatioCurve , !- Fan Power Ratio - function of Air Flow Rate Curve Name
0.2, !- Minimum Air Flow Rate Ratio
0.125 , !- Fraction of Tower Capacity in Free Convection Regime
450.0 , !- Basin Heater Capacity {W/K}
4.5, !- Basin Heater Set Point Temperature {C}
BasinSchedule , !- Basin Heater Operating Schedule Name
SaturatedExit , !- Evaporation Loss Mode
, !- Evaporation Loss Factor
0.05, !- Makeup Water Usage due to Drift {percent}
ScheduledRate , !- Blowdown Calculation Mode
BlowDownSchedule , !- Schedule Name for Makeup Water Usage due to Blowdown
, !- Name of Water Storage Tank for Supply
, !- Outdoor Air Inlet Node Name
4, !- Number of Cells
MinimalCell , !- Cell Control
, !- Cell Minimum Water Flow Rate Fraction
, !- Cell Maximum Water Flow Rate Fraction
1.000 ; !- Sizing Factor
1.25.5.2 Outputs
A tower uses either mains water or storage tank for make-up water.
When mains water is used:
1064 CHAPTER 1. INPUT-OUTPUT REFERENCE
IF specified:
1.25.5.2.20 Cooling Tower Storage Tank Water Volume Flow Rate [m3/s]
1.25.5.2.22 Cooling Tower Starved Storage Tank Water Volume Flow Rate
[m3/s]
1.25.6 CoolingTowerPerformance:CoolTools
Variable speed cooling towers can be modeled by EnergyPlus with user-selectable performance
based on the CoolTools correlation, YorkCalc correlation, or user-defined coefficients for either the
CoolTools or YorkCalc correlations.The empirical CoolTools tower correlation uses a set of 35 co-
efficients to model the thermal performance (approach temperature) of a cooling tower based on
four independent variables. If the user specifies Model Type = CoolToolsCrossFlow in the Cooling-
Tower:VariableSpeed object, then the 35 coefficients derived for the CoolTools simulation model are
used and these coefficients are already defined within EnergyPlus. If the user specifies Model Type
= CoolToolsUserDefined, then the user must enter a CoolingTowerPerformance:CoolTools object to
define the 35 coefficients that will be used by the CoolTools correlation.
The user must specify a name for the model coefficient object, and this name must be used in
the CoolingTower:VariableSpeed object (field Model Coefficient Name) to tell the program to use
these coefficients. Next, the user enters the minimum and maximum values for inlet air wet-bulb
temperature, range temperature, approach temperature, and water mass flow rate ratio to specify
the valid range for which the model coefficients were derived. For all of these variables, the program
issues warnings if the actual values are beyond the minimum/maximum values specified. For inlet
air wet-bulb temperature and water mass flow rate ratio, the values of these variables used in the
calculation of approach temperature are limited to be within the valid minimum/maximum range
specified. For approach and range, the warnings are issued if the values are beyond the specified
minimum/maximum range but the actual values are still used.
The CoolTools correlation has four independent variables: inlet air wet-bulb temperature (Twb),
tower range temperature (Tr), water flow rate ratio (FRwater), and air flow rate ratio (FRair).
Temperatures are in units of ˚C and flow rate ratios are dimensionless (actual flow rate divided by
1.25. GROUP – CONDENSER EQUIPMENT 1067
design flow rate). Using these independent variables, tower approach temperature (˚C) is calculated
as follows:
Approach = Coeff(1) + Coeff(2)•FRair + Coeff(3)•(FRair)2 +
Coeff(4)•(FRair)3 + Coeff(5)•FRwater +
Coeff(6)•FRair•FRwater + Coeff(7)•(FRair)2 •FRwater +
Coeff(8)•(FRwater)2 + Coeff(9)•FRair•(FRwater)2 +
Coeff(10)•(FRwater)3 + Coeff(11)•Twb + Coeff(12)•FRair•Twb +
Coeff(13)•(FRair)2 •Twb + Coeff(14)•FRwater•Twb +
Coeff(15)•FRair•FRwater•Twb + Coeff(16)•(FRwater)2 •Twb +
Coeff(17)•(Twb)2 + Coeff(18)•FRair•(Twb)2 +
Coeff(19)•FRwater•(Twb)2 + Coeff(20)•(Twb)3 + Coeff(21)•Tr +
Coeff(22)•FRair•Tr + Coeff(23)•FRair•FRair•Tr +
Coeff(24)•FRwater•Tr + Coeff(25)•FRair•FRwater•Tr +
Coeff(26)•(FRwater)2 •Tr + Coeff(27)•Twb•Tr +
Coeff(28)•FRair•Twb•Tr + Coeff(29)•FRwater•Twb•Tr +
Coeff(30)•(Twb)2 •Tr + Coeff(31)•(Tr)2 + Coeff(32)•FRair•(Tr)2 +
Coeff(33)•FRwater•(Tr)2 + Coeff(34)•Twb•(Tr)2 + Coeff(35)•(Tr)3
This object allows the user to specify model coefficients for use with the CoolTools correlation shown
above. It is recommended that a broad set of cooling tower performance data be used to generate
these model coefficients. The data set used to create the model coefficients should cover the entire
range of water and air flow rate ratios and inlet air wet-bulb, range, and approach temperatures
expected during the simulation.
1.25.6.1 Inputs
CoolingTowerPerformance :CoolTools ,
CoolTools CrossFlow Default Model , !- Tower Model Coefficient Name
-1.0, !- Minimum Inlet Air Wet -Bulb Temperature {C}
26.6667 , !- Maximum Inlet Air Wet -Bulb Temperature {C}
1.1111 , !- Minimum Range Temperature {C}
1.25. GROUP – CONDENSER EQUIPMENT 1069
1.25.6.2 Outputs
No additional cooling tower output variables are output when this object is used.
1.25.7 CoolingTowerPerformance:YorkCalc
Variable speed cooling towers can be modeled by EnergyPlus with user-selectable performance
based on the CoolTools correlation, YorkCalc correlation, or user-defined coefficients for either the
CoolTools or YorkCalc correlations.The empirical YorkCalc tower correlation uses a set of 27 co-
efficients to model the thermal performance (approach temperature) of a variable speed cooling
tower based on three independent variables. If the user specifies Tower Model Type = YorkCalc
in the CoolingTower:VariableSpeed object, then the 27 coefficients derived for the YorkCalc sim-
ulation model are used and these coefficients are already defined within EnergyPlus. If the user
specifies Tower Model Type = YorkCalcUserDefined, then the user must enter a CoolingTowerPer-
formance:YorkCalc object to define the 27 coefficients that will be used by the YorkCalc correlation.
The user must specify a name for the model coefficient object, and this name must be used in
the CoolingTower:VariableSpeed object (field Model Coefficient Name) to tell the program to use
these coefficients. Next, the user enters the minimum and maximum values for inlet air wet-bulb
1070 CHAPTER 1. INPUT-OUTPUT REFERENCE
temperature, range temperature, approach temperature, and water mass flow rate ratio to specify
the valid range for which the model coefficients were derived. The user also specifies the maximum
valid liquid-to-gas ratio. For all of these variables, the program issues warnings if the actual values
are beyond the minimum/maximum values specified. For inlet air wet-bulb temperature and water
mass flow rate ratio, the values of these variables used in the calculation of approach temperature
are limited to be within the valid minimum/maximum range specified. For approach, range, and
liquid-to-gas ratio the warnings are issued if the values are beyond the specified minimum/maximum
range but the actual values are still used.
The YorkCalc correlation has three independent variables: inlet air wet-bulb temperature (Twb),
tower range temperature (Tr), and the liquid-to-gas ratio (ratio of water flow rate ratio to air flow
rate ratio = LGRatio). Temperatures are in units of ˚C and liquid-to-gas ratio is dimensionless.
Using these independent variables, an approach temperature (˚C) is calculated as follows:
Approach = Coeff(1) + Coeff(2)•Twb + Coeff(3)•Twb2 + Coeff(4)•Tr +
Coeff(5)•Twb•Tr + Coeff(6)•Twb2 •Tr + Coeff(7)•Tr2 +
Coeff(8)•Twb•Tr2 + Coeff(9)•Twb2 •Tr2 + Coeff(10)•LGRatio +
Coeff(11)•Twb•LGRatio + Coeff(12)•Twb2 •LGRatio +
Coeff(13)•Tr•LGRatio + Coeff(14)•Twb•Tr•LGRatio +
Coeff(15)•Twb2 •Tr•LGRatio + Coeff(16)•Tr2 •LGRatio +
Coeff(17)•Twb•Tr2 •LGRatio + Coeff(18)•Twb2 •Tr2 •LGRatio +
Coeff(19)•LGRatio2 + Coeff(20)•Twb•LGRatio2 +
Coeff(21)• Twb2 •LGRatio2 + Coeff(22)•Tr•LGRatio2 +
Coeff(23)•Twb•Tr•LGRatio2 + Coeff(24)•Twb2 •Tr•LGRatio2 +
Coeff(25)•Tr2 •LGRatio2 + Coeff(26)•Twb•Tr2 •LGRatio2 +
Coeff(27)•Twb2 •Tr2 •LGRatio2
This object allows the user to specify model coefficients for use with the YorkCalc correlation shown
above. It is recommended that a broad set of cooling tower performance data be used to generate
these model coefficients. The data set used to create the model coefficients should cover the entire
range of water and air flow rate ratios and inlet air wet-bulb, range, and approach temperatures
expected during the simulation.
1.25.7.1 Inputs
CoolingTowerPerformance :YorkCalc
YorkCalc Default Tower Model , !- Tower Model Coefficient Name
-34.4, !- Minimum Inlet Air Wet -Bulb Temperature {C}
26.6667 , !- Maximum Inlet Air Wet -Bulb Temperature {C}
1.1111 , !- Minimum Range Temperature {C}
22.2222 , !- Maximum Range Temperature {C}
1.1111 , !- Minimum Approach Temperature {C}
40.0, !- Maximum Approach Temperature {C}
0.75, !- Minimum Water Flow Rate Ratio
1.25, !- Maximum Water Flow Rate Ratio
8.0, !- Maximum Liquid to Gas Ratio
-0.359741205 , !- Coefficient 1
-0.055053608 , !- Coefficient 2
0.0023850432 , !- Coefficient 3
0.173926877 , !- Coefficient 4
-0.0248473764 , !- Coefficient 5
0.00048430224 , !- Coefficient 6
-0.005589849456 , !- Coefficient 7
0.0005770079712 , !- Coefficient 8
-0.00001342427256 , !- Coefficient 9
2.84765801111111 , !- Coefficient 10
-0.121765149 , !- Coefficient 11
0.0014599242 , !- Coefficient 12
1.680428651 , !- Coefficient 13
-0.0166920786 , !- Coefficient 14
-0.0007190532 , !- Coefficient 15
-0.025485194448 , !- Coefficient 16
0.0000487491696 , !- Coefficient 17
0.00002719234152 , !- Coefficient 18
-0.0653766255555556 , !- Coefficient 19
-0.002278167 , !- Coefficient 20
0.0002500254 , !- Coefficient 21
-0.0910565458 , !- Coefficient 22
0.00318176316 , !- Coefficient 23
0.000038621772 , !- Coefficient 24
-0.0034285382352 , !- Coefficient 25
0.00000856589904 , !- Coefficient 26
-0.000001516821552; !- Coefficient 27
1.25.7.2 Outputs
No additional cooling tower output variables are output when this object is used.
1.25. GROUP – CONDENSER EQUIPMENT 1073
1.25.8 EvaporativeFluidCooler:SingleSpeed
Evaporative fluid coolers are components that may be assigned to condenser loops. The Evapora-
tive fluid cooler is modeled as a counter flow heat exchanger with single-speed fans (induced draft
configuration). The user must define fluid cooler performance via one of three methods: design heat
transfer coefficient-area product (UA) and design water flow rate, or standard fluid cooler design
capacity at a specific rating point or design capacity at non standard conditions. Regardless of which
method is chosen, the design airflow rate and corresponding fan power must be specified.
The evaporative fluid cooler seeks to maintain the temperature of the water exiting the evaporative
fluid cooler at (or below) a set point. The set point schedule value is defined by the field “Condenser
Loop Temperature Setpoint Node Name or Reference” for the CondenserLoop object. The model
first checks to see whether inlet water temperature is at or below the set point. If so, then the fluid
cooler fan is not turned on and all the flow goes through bypass. If the inlet water temperature is
above the set point then the fluid cooler fan is turned on to reduce the exiting water temperature
to the set point. If the capacity control is FanCycling, the model assumes that part-load operation
is represented by a simple linear interpolation between two steady-state regimes (i.e., fluid cooler
fan on for the entire simulation timestep and fluid cooler fan off for the entire simulation timestep).
Cyclic losses are not taken into account. If the capacity control is FluidBypass, the model determines
the fraction of water flow to be bypassed while the remaining water goes through the fluid cooler
cooling media and gets cooled, then the two water flows mix to meet the setpoint temperature. In
this case, the fan runs at full speed for the entire timestep.
Evaporative fluid coolers consume water through evaporation, drift, and blowdown. The model can
be used to predict water consumed by the fluid coolers. For this purpose, the last seven input
fields can either be provided in the input or if nothing is specified then the default values for these
fields will be used. These fields provide the methods of controlling details of the water consumption
calculations. The user can specify connections to the rest of the building’s water system by providing
the name of a water storage tanks (i.e. WaterUse:Storage objects). The schematic of the system is
shown below:
Where,
– h = Enthalpy (j/kg-K)
– m = mass flow rate (kg/s)
– Subscripts
– a = air
– w = water
– wb = wet-bulb
– in = inlet
– out = outlet
1.25.8.1 Inputs
1.25.8.1.9 Field: Heat Rejection Capacity and Nominal Capacity Sizing Ratio
This numeric field contains the value for the ratio of actual tower heat rejection to nominal capac-
ity. This ratio is defined at entering water at 35C (95F), leaving water at 29.4C (85F), entering air
at 25.6C (78F) wetbulb and 35C (95F) drybulb temperatures. Historically this ratio has been set at
1.25 based on the assumption that the tower must dissipate 0.25 W of compressor power for every
what of heat removed at the chiller evaporator. The default is 1.25.
1076 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.25.8.1.11 Field: Design Air Flow Rate U-factor Times Area Value
This numeric field contains the heat transfer coefficient-area product (UA) in watts per Kelvin cor-
responding to the design air and water flow rates specified above. If the input field “Performance
Input Method” is specified as “UFactorTimesAreaAndDesignWaterFlowRate”, then a UA value
greater than zero but less than or equal to 300,000 must be defined, or the field can be autosized. If
autosized, a Plant Sizing object must be defined and the design fluid cooler UA value is derived from
the design load to be rejected by the condenser loop and the design loop delta T (Ref. Sizing and
Input for Design Calculations and Component Autosizing sections), the fluid cooler inlet air dry-bulb
and wetbulb temperature are taken from the input. This field is only used for performance input
method = ” UFactorTimesAreaAndDesignWaterFlowRate”. For other performance input methods,
this field is ignored.
the water the evaporative fluid cooler needs, then the evaporative fluid cooler will still operate and
obtain the rest of the water it needs from the mains (referred to as ‘Starved’ water).
An IDF specification for this object is shown below:
EvaporativeFluidCooler:SingleSpeed ,
Big EvaporativeFluidCooler , !- Name
Condenser EvaporativeFluidcooler Inlet Node , !- Water Inlet Node Name
Condenser EvaporativeFluidcooler Outlet Node , !- Water Outlet Node Name
3.02, !- Design Air Flow Rate {m3/s}
2250, !- Design Air Flow Rate Fan Power {W}
0.002208 , !- Design Spray Water Flow Rate {m3/s}
UserSpecifiedDesignCapacity , !- Performance Input Method
, !- Outdoor Air Inlet Node Name
1.25, !- Heat Rejection Capacity and Nominal Capacity Sizing Ratio
, !- Standard Design Capacity {W}
, !- Design Air Flow Rate U-factor Times Area Value {W/K}
0.001703 , !- Design Water Flow Rate {m3/s}
87921 , !- User Specified Design Capacity {W}
46.11 , !- Design Entering Water Temperature {C}
35, !- Design Entering Air Temperature {C}
25.6; !- Design Entering Air Wet -bulb Temperature {C}
1.25.8.2 Outputs
1.25.8.2.17 Cooling Tower Storage Tank Water Volume Flow Rate [m3/s]
1.25.8.2.19 Cooling Tower Starved Storage Tank Water Volume Flow Rate
[m3/s]
1.25.9 EvaporativeFluidCooler:TwoSpeed
The two-speed evaporative fluid cooler is modeled in a similar fashion to the single-speed evaporative
fluid cooler. The evaporative fluid cooler is modeled as a counter flow heat exchanger with two-speed
fan (induced draft configuration. See schematic diagram in EvaporativeFluidCooler:SingleSpeed
section). The user must define fluid cooler performance via one of the three methods: design heat
transfer coefficient-area product (UA) and design water flow rate, or standard fluid cooler design
capacity at a specific rating point or design capacity at non standard conditions. Regardless of which
method is chosen, the design airflow rate and corresponding fan power must be specified.
The evaporative fluid cooler seeks to maintain the temperature of the water exiting the evaporative
fluid cooler at (or below) a set point. The set point schedule value is defined by the field “Condenser
Loop Temperature Setpoint Node Name or Reference” for the CondenserLoop object. The model
first checks to see whether inlet water temperature is at or below the set point. If so, then the fluid
cooler fan is not turned on and all the flow goes through bypass. If the inlet water temperature is
above the set point then the fluid cooler fan is turned on at low speed to reduce the exiting water
temperature to the set point. If operating the fluid cooler fan at low speed does not reduce the
exiting water temperature to the set point, then the fluid cooler fan is increased to its high speed.
The model assumes that part-load operation is represented by a simple linear interpolation between
two steady-state regimes (i.e., fluid cooler fan at high speed for the entire simulation timestep and
1082 CHAPTER 1. INPUT-OUTPUT REFERENCE
fluid cooler fan at low speed for the entire simulation timestep, or fluid cooler fan at low speed for
the entire simulation timestep and fluid cooler fan off for the entire simulation timestep). Cyclic
losses are not taken into account.
Evaporative fluid coolers consume water through evaporation, drift, and blowdown. The model can
be used to predict water consumed by the evaporative fluid coolers. For this purpose, the last seven
input fields can either be provided in the input or if nothing is specified then the default values for
these fields will be used. These fields provide methods of controlling details of the water consumption
calculations. The user can specify connections to the rest of the buildings water system by providing
the name of a water storage tanks (i.e. WaterUse:Storage objects).
1.25.9.1 Inputs
1.25.9.1.7 Field: Low Fan Speed Air Flow Rate Sizing Factor
This numeric field contains the sizing factor for calculating the low fan speed air flow rate as a
fraction of the high fan speed air flow rate. The default is 0.5.
1.25. GROUP – CONDENSER EQUIPMENT 1083
1.25.9.1.13 Field: Heat Rejection Capacity and Nominal Capacity Sizing Ratio
This numeric field contains the value for the ratio of actual tower heat rejection to nominal capac-
ity. This ratio is defined at entering water at 35C (95F), leaving water at 29.4C (85F), entering air
at 25.6C (78F) wetbulb and 35C (95F) drybulb temperatures. Historically this ratio has been set at
1.25 based on the assumption that the tower must dissipate 0.25 W of compressor power for every
what of heat removed at the chiller evaporator. The default is 1.25.
mentioned above for “standard design capacity” are already specified in the EnergyPlus. So the
input fields such as design entering water temp., design entering air wet-bulb and dry-bulb temp.
and design water flow rate, if provided in the input, will be ignored for the StandardDesignCapacity
performance input method. Also, the standard conditions are for water as a fluid type so this
performance input method can only be used with water as a fluid type (ref. CondenserLoop object).
Speed” determined in the following field. This field is only used for performance input method = ”
UFactorTimesAreaAndDesignWaterFlowRate”. For other input methods this field is ignored.
1.25.9.1.19 Field: Low Fan Speed U-Factor Times Area Sizing Factor
This field contains the sizing factor to use when calculating the Low Fan Speed U-Factor Times Area
Value. The default is 0.6.
1.25.9.1.23 Field: Low Speed User Specified Design Capacity Sizing Factor
This field contains the sizing factor to use when calculating the Low-Speed User Specified Design
Capacity. The default is 0.5.
EvaporativeFluidCooler:TwoSpeed ,
Big EvaporativeFluidCooler , !- Name
Condenser EvaporativeFluidcooler Inlet Node , !- Water Inlet Node Name
Condenser EvaporativeFluidcooler Outlet Node , !- Water Outlet Node Name
9.911 , !- High Fan Speed Air Flow Rate {m3/s}
autosize , !- High Fan Speed Fan Power {W}
4.911 , !- Low Fan Speed Air Flow Rate {m3/s}
1088 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.25.9.2 Outputs
1.25.9.2.16 Cooling Tower Storage Tank Water Volume Flow Rate [m3/s]
1.25.9.2.18 Cooling Tower Starved Storage Tank Water Volume Flow Rate
[m3/s]
1.25.10 FluidCooler:SingleSpeed
Fluid coolers are components that may be assigned to condenser loops. The Fluid cooler is mod-
eled as a cross flow heat exchanger (both streams unmixed) with single-speed fans (induced draft
configuration). The user must define fluid cooler performance via one of the two methods: design
heat transfer coefficient-area product (UA) and design water flow rate, or nominal fluid cooler ca-
pacity at a specific rating point. Regardless of which method is chosen, the design airflow rate and
corresponding fan power must be specified.
The fluid cooler seeks to maintain the temperature of the water exiting the fluid cooler at (or below)
a set point. The set point schedule value is defined by the field “Condenser Loop Temperature
Setpoint Node Name or Reference” for the CondenserLoop object. The model assumes that part-
load operation is represented by a simple linear interpolation between two steady-state regimes (i.e.,
fluid cooler fan on for the entire simulation timestep and fluid cooler fan off for the entire simulation
timestep). Cyclic losses are not taken into account.
1.25.10.1 Inputs
1.25.10.1.5 Field: Design Air Flow Rate U-factor Times Area Value
This numeric field contains the heat transfer coefficient-area product (UA) in watts per Kelvin
corresponding to the design air and water flow rates specified above. If the input field “Perfor-
mance Input Method” is specified as “UFactorTimesAreaAndDesignWaterFlowRate”, then a UA
value greater than zero but less than or equal to 300,000 must be defined, or the field can be au-
tosized. If autosized, a Plant Sizing object must be defined and the design fluid cooler UA value is
derived from the design load to be rejected by the condenser loop and the design loop delta T (Ref.
Sizing and Input for Design Calculations and Component Autosizing sections), the fluid cooler inlet
air dry-bulb and wetbulb temperature are taken from the input. If “Performance Input Method”
is specified as “NominalCapacity”, then this field must be left blank since the model automatically
calculates the fluid cooler UA based on the fluid cooler capacity and nominal conditions specified in
input file.
FluidCooler:SingleSpeed ,
Big FLUIDCOOLER1 , !- Name
Condenser FLUIDCOOLER 1 Inlet Node , !- Water Inlet Node Name
Condenser FLUIDCOOLER 1 Outlet Node , !- Water Outlet Node Name
NominalCapacity , !- Performance Input Method
, !- Design Air Flow Rate U-factor Times Area Value {W/K}
58601. , !- Nominal Capacity {W}
51.67 , !- Design Entering Water Temperature {C}
35, !- Design Entering Air Temperature {C}
25.6, !- Design Entering Air Wetbulb Temperature {C}
0.001388 , !- Design Water Flow Rate{m3/s}
9.911 , !- Design Air Flow Rate {m3/s}
Autosize; !- Design Air Flow Rate Fan Power {W}
1.25.10.2 Outputs
1.25.11 FluidCooler:TwoSpeed
The two-speed fluid cooler is modeled in a similar fashion to the single-speed fluid cooler. The fluid
cooler is modeled as a cross flow heat exchanger (both stream unmixed) with two-speed fans (induced
draft configuration). The user must define fluid cooler performance via one of two methods: heat
transfer coefficient-area product (UA) and design water flow rate, or nominal fluid cooler capacity
at a specific rating point. Regardless of which method is chosen, the airflow rate and corresponding
fan power at both high and low fan speed must be specified. The Fluid Cooler seeks to maintain
the temperature of the water exiting the Fluid Cooler at (or below) a set point. The set point
schedule is defined by the field “Condenser Loop Temperature Setpoint Node Name or Reference”
for the CondenserLoop object. The model first runs at low speed and calculates the fluid cooler
exiting water temperature. If the exiting water temperature based on “low speed” is at or below
the set point, then the fluid cooler fan runs at this speed or below this speed. If the exiting water
temperature remains above the set point after “low speed” is modeled, then the fluid cooler fan runs
at high speed to reduce the exiting water temperature.
The model assumes that part-load operation is represented by a simple linear interpolation between
two steady-state regimes (i.e., fluid cooler fan at high speed for the entire simulation timestep and
fluid cooler fan at low speed for the entire simulation timestep,). Cyclic losses are not taken into
account.
1094 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.25.11.1 Inputs
1.25.11.1.7 Field: Low Fan Speed U-Factor Times Area Sizing Factor
This numeric field contains the sizing factor to use when calculating the Low Fan Speed U-factor
Times Area Value. The default is 0.6.
1.25. GROUP – CONDENSER EQUIPMENT 1095
1.25.11.1.18 Field: Low Fan Speed Air Flow Rate Sizing Factor
This numeric field contains the sizing factor to use when calculating the Low Fan Speed Air Flow
Rate. The default is 0.5.
FluidCooler:TwoSpeed ,
Big FLUIDCOOLER1 , !- Name
Condenser FLUIDCOOLER 1 inlet Node , !- Water Inlet Node Name
Condenser FLUIDCOOLER 1 Outlet Node , !- Water Outlet Node Name
NominalCapacity , !- Performance Input Method
, !- High Fan Speed U-factor Times Area Value {W/K}
, !- Low Fan Speed U-factor Times Area Value {W/K}
, !- Low Fan Speed U-Factor Times Area Sizing Factor
58601. , !- High Speed Nominal Capacity {W}
28601. , !- Low Speed Nominal Capacity {W}
. 0.6, !- Low Speed Nominal Capacity Sizing Factor
51.67 , !- Design Entering Water tempereture {C}
35, !- Design Entering Air tempereture {C}
1.25. GROUP – CONDENSER EQUIPMENT 1097
1.25.11.2 Outputs
1.25.12 GroundHeatExchanger:System
The EnergyPlus ground loop heat exchanger is a condenser component which serves the condenser
supply side in addition to the cooling towers and other condensing components. Figure 1.99 shows
the Ground Heat Exchanger in the simulation environment.
The heat exchanger response is defined by a g-function which is a non-dimensional function that is
used to calculate the response to square heat pulses of different duration. (This function is not the
same as ‘G-factors’ referred to in the ASHRAE Applications Handbook). This continuous function
is specified by a series of data pairs (LNTTSi, GFNCi) where,
The g-function is different for each borehole field configuration (i.e. a 4 × 4 field has a different
response than a 80 × 80 field). It is also dependent on the ratio of borehole spacing to depth.
g-function values, for accurate simulation, have to be computed for each specific heat exchanger
design. The GroundHeatExchanger:System object will accept three different types of input in order
to define the g-functions necessary for the ground heat exchanger calculations.
A small number of reference datasets containing example input data for 1 × 2, 4 × 4 and 8 × 8
configurations and for both standard and thermally enhanced grout are provided as well.
Definitions for the input fields are provided below.
1.25.12.1 Inputs
GroundHeatExchanger :Vertical:Properties ,
GHE -1 Props , !- Name
1, !- Depth of Top of Borehole {m}
100, !- Borehole Length {m}
0.114 , !- Borehole Diameter {m}
0.7443 , !- Grout Thermal Conductivity {W/m-K}
3.90E+06, !- Grout Thermal Heat Capacity {J/m3 -K}
0.3895 , !- Pipe Thermal Conductivity {W/m-K}
1.77E+06, !- Pipe Thermal Heat Capacity {J/m3 -K}
0.03341 , !- Pipe Outer Diameter {m}
0.002984 , !- Pipe Thickness {m}
0.04913; !- U-Tube Distance {m}
GroundHeatExchanger :Vertical:Array ,
GHE -Array , !- Name
GHE -1 Props , !- GHE Properties
2, !- Number of Boreholes in X Direction
2, !- Number of Boreholes in Y Direction
5; !- Borehole Spacing {m}
The second example uses the GroundHeatExchanger:Vertical:Single object. The g-functions will be
generated automatically by EnergyPlus and cached for later use.
GroundHeatExchanger :System ,
Vertical GHE 1x4 Std , !- Name
GLHE Inlet , !- Inlet Node Name
GLHE Outlet , !- Outlet Node Name
0.00100944 , !- Design Flow Rate {m3/s}
Site: GroundTemperature :Undisturbed:KusudaAchenbach , !- Undisturbed Ground Temperature Model
Type
KATemps , !- Undisturbed Ground Temperature Model Name
2.5, !- Ground Thermal Conductivity {W/m-K}
2.5E+06, !- Ground Thermal Heat Capacity {J/m3 -K}
, !- Response Factors Object Name
UBHWTcalc , !- g-Function Calculation Method
, !- GHE Array Object Name
GHE -1, !- GHE Borehole Definition 1
GHE -2, !- GHE Borehole Definition 2
GHE -3, !- GHE Borehole Definition 3
GHE -4; !- GHE Borehole Definition 4
GroundHeatExchanger :Vertical:Properties ,
GHE -1 Props , !- Name
1, !- Depth of Top of Borehole {m}
100, !- Borehole Length {m}
0.114 , !- Borehole Diameter {m}
0.7443 , !- Grout Thermal Conductivity {W/m-K}
3.90E+06, !- Grout Thermal Heat Capacity {J/m3 -K}
0.3895 , !- Pipe Thermal Conductivity {W/m-K}
1.77E+06, !- Pipe Thermal Heat Capacity {J/m3 -K}
0.03341 , !- Pipe Outer Diameter {m}
0.002984 , !- Pipe Thickness {m}
0.04913; !- U-Tube Distance {m}
GroundHeatExchanger :Vertical:Single ,
GHE -1, !- Name
GHE -1 Props , !- GHE Properties
0, !- X Location {m}
0; !- Y Location {m}
GroundHeatExchanger :Vertical:Single ,
GHE -2, !- Name
1102 CHAPTER 1. INPUT-OUTPUT REFERENCE
GroundHeatExchanger :Vertical:Single ,
GHE -3, !- Name
GHE -1 Props , !- GHE Properties
0, !- X Location {m}
5; !- Y Location {m}
GroundHeatExchanger :Vertical:Single ,
GHE -4, !- Name
GHE -1 Props , !- GHE Properties
5, !- X Location {m}
5; !- Y Location {m}
The final example uses the ResponseFactors object to provide third-party g-functions.
GroundHeatExchanger :System ,
Vertical GHE 1x4 Std , !- Name
GLHE Inlet , !- Inlet Node Name
GLHE Outlet , !- Outlet Node Name
0.00100944 , !- Design Flow Rate {m3/s}
Site: GroundTemperature :Undisturbed:KusudaAchenbach , !- Undisturbed Ground Temperature Model
Type
KATemps , !- Undisturbed Ground Temperature Model Name
2.5, !- Ground Thermal Conductivity {W/m-K}
2.5E+06, !- Ground Thermal Heat Capacity {J/m3 -K}
GHE -1 g-functions; !- Response Factors Object Name
GroundHeatExchanger :Vertical:Properties ,
GHE -1 Props , !- Name
1, !- Depth of Top of Borehole {m}
100, !- Borehole Length {m}
0.114 , !- Borehole Diameter {m}
0.7443 , !- Grout Thermal Conductivity {W/m-K}
3.90E+06, !- Grout Thermal Heat Capacity {J/m3 -K}
0.3895 , !- Pipe Thermal Conductivity {W/m-K}
1.77E+06, !- Pipe Thermal Heat Capacity {J/m3 -K}
0.03341 , !- Pipe Outer Diameter {m}
0.002984 , !- Pipe Thickness {m}
0.04913; !- U-Tube Distance {m}
GroundHeatExchanger :ResponseFactors ,
GHE -1 g-functions , !- Name
GHE -1 Props , !- GHE Properties
4, !- Number of Boreholes
0.00043 , !- G-Function Reference Ratio {dimensionless}
-15.585075 , !- G-Function Ln(T/Ts) Value 1
-2.672011 , !- G-Function G Value 1
-15.440481 , !- G-Function Ln(T/Ts) Value 2
-2.575897 , !- G-Function G Value 2
-15.295888 , !- G-Function Ln(T/Ts) Value 3
-2.476279 , !- G-Function G Value 3
-15.151295 , !- G-Function Ln(T/Ts) Value 4
-2.372609 , !- G-Function G Value 4
...,
12.365217 , !- G-Function G Value 70
1.112000 , !- G-Function Ln(T/Ts) Value 71
12.469007 , !- G-Function G Value 71
1.335000 , !- G-Function Ln(T/Ts) Value 72
12.547123 , !- G-Function G Value 72
1.679000; !- G-Function Ln(T/Ts) Value 73
1.25.12.2 Outputs
1.25.13 GroundHeatExchanger:Vertical:Properties
This object defines several borehole parameters.
1.25.13.1 Inputs
1.25.14 GroundHeatExchanger:Vertical:Array
This object defines the borehole locations for a rectangular array of boreholes.
1.25.15 GroundHeatExchanger:Vertical:Single
This object defines a single borehole heat exchanger.
1.25.15.1 Inputs
1.25.16 GroundHeatExchanger:ResponseFactors
This object is used to provide third-party g-functions which are generated by other tools.
1.25.16.1 Inputs
– If the g-functions have not had a correction applied, then the g-functions are still based on a
reference of 0.0005, so use a value of 0.0005 in this field. EnergyPlus will adjust the g-functions
internally to create the properly referenced g-function.
– If the correction has already been applied, then the input g-functions are based on a reference
to the actual (physical) radius/length ratio, so enter the physical radius/length in this field.
Entering the actual value will nullify any internal corrections, which will avoid re-basing the
g-function set.
The software GLHEPro has been making this “pre-correction” to the data sets since version 3.1 of
that software, so this input field should match the actual (physical) radius/length ratio.
1.25.17 GroundHeatExchanger:Slinky
The GroundHeatExchanger:Slinky use the g-functions to calculate the GHX temperature response,
similar to the GroundHeatExchanger:Vertical model, however for this model g-functions are auto-
matically calculated by EnergyPlus without the need of external software or data.
Horizontal slinky-loop ground heat exchangers (GHXs) consist of coiled tubing, with the individual
rings spread out along the direction of the trench either horizontally or vertically, as shown in
Figure. A schematic of a slinky GHX can be seen in Figure. Compared to conventional straight
tube horizontal GHXs, slinky loops have a higher tube density; hence, with the same cooling/heating
loads, slinky-loop GHXs require less land area and excavation work than straight tube HGHXs.
Figure: Slinky Ground Heat Exchanger Configurations.
Figure: Schematic of Slinky HX.
An example GroundHeatExchanger:Slinky object is shown below.
GroundHeatExchanger :Slinky ,
Slinky GHX , !- Name
GHE Inlet Node , !- Inlet Node
GHE Outlet Node , !- Outlet Node
0.0033 , !- Design Flow Rate [m3/s]
1.2, !- Soil Thermal Conductivity [W/m-K]
3200, !- Soil Density [kg/m3]
850, !- Soil Specific Heat [J/kg -K]
1.8, !- Pipe Thermal Conductivity [W/m-K]
920, !- Pipe Density [kg/m3]
2200, !- Pipe Specific Heat [J/kg -K]
0.02667 , !- Pipe Outside Diameter [m]
0.002413 , !- Pipe Wall Thickness [m]
Vertical , !- Heat Exchanger Configuration (Vertical , Horizontal)
1, !- Coil Diameter [m]
0.2, !- Coil Pitch [m]
1108 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.25.17.1 Inputs
1.25.17.2 Outputs
1.25.18 GroundHeatExchanger:Pond
The pond heat exchanger model represents a shallow pond with submerged hydronic tubes through
which the heat transfer fluid is circulated. The model represents a ‘shallow’ pond in that no attempt
is made to model any stratification effects that may be present in deeper ponds.
This type of heat exchanger is intended to be connected to the supply side of a condenser loop, and
can be used with any type of plant loop. The pond may be specified as the only heat exchanger
on the condenser loop (as shown in Figure 1.102) or it may be connected in parallel with other
condenser loop heat exchangers (such as cooling towers, ground surface heat exchangers) as shown
in the second figure below.
1112 CHAPTER 1. INPUT-OUTPUT REFERENCE
Figure 1.102: Example of Pond Ground Heat Exchanger as only heat exchanger on condenser loop
Figure 1.103: Pond Ground Heat Exchanger with other heat exchangers on condenser loop
1.25. GROUP – CONDENSER EQUIPMENT 1113
1.25.18.1 Inputs
GroundHeatExchanger :Pond ,
Pond 1, !- Name
Condenser Tower 1 Inlet Node , !- Fluid Inlet Node Name
Condenser Tower 1 Outlet Node , !- Fluid Outlet Node Name
2.0, !- Pond Depth {m}
1000.0 , !- Pond Area {m2}
0.02, !- Hydronic Tubing Inside Diameter {m}
1114 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.25.18.2 Outputs
1.25.19 GroundHeatExchanger:Surface
The surface heat exchanger model is to simulate hydronic surface ground heat exchangers. This
includes pavement surfaces with embedded pipes for snow-melting or heat rejection from hybrid
ground source heat pump systems.
The heat exchanger may be ground coupled or not. In the latter case the bottom surface is exposed
to the wind but not solar gains. This type of heat exchanger is intended to be connected to the
supply side of a condenser loop, and can be used with any type of plant loop. The surface heat
exchanger may be specified as the only heat exchanger on the condenser loop (as shown in the first
figure below) or it may be connected in parallel with other condenser loop heat exchangers (such as
cooling towers, ground surface heat exchangers) as shown in the second figure below.
1.25. GROUP – CONDENSER EQUIPMENT 1115
Figure 1.104: Example of Surface Ground Heat Exchanger as only heat exchanger on condenser
loop
Figure 1.105: Surface Ground Heat Exchanger with other heat exchangers on condenser loop
1116 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.25.19.1 Inputs
GroundHeatExchanger :Surface ,
SURFACE 1, !- Name
Outside Surface Construction , !- Construction Name
Condenser Tower 1 Inlet Node , !- Fluid Inlet Node Name
Condenser Tower 1 Outlet Node , !- Fluid Outlet Node Name
0.02, !- Hydronic Tubing Inside Diameter {m}
10.0, !- Number of Tubing Circuits
0.3, !- Hydronic Tube Spacing {m}
100.0 , !- Surface Length {m}
100.0 , !- Surface Width {m}
GROUND; !- Lower Surface Environment
1.25. GROUP – CONDENSER EQUIPMENT 1117
1.25.19.2 Outputs
1.25.19.2.9 Ground Heat Exchanger Top Surface Heat Transfer Energy per
Area [J/m2 ]
1.25.19.2.10 Ground Heat Exchanger Bottom Surface Heat Transfer Energy per
Area [J/m2 ]
These outputs are the surface heat exchanger top and bottom surface flux.
1118 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.25.20 GroundHeatExchanger:HorizontalTrench
The horizontal trench ground heat exchanger object provides an alternate interface to the detailed
PipingSystem:Underground:* objects. The same underlying simulation algorithm is utilized, pro-
viding a transient numerical simulation of soil with buried pipes and a detailed surface heat bal-
ance. The input syntax is much smaller and useful for simple applications. For full flexibility,
use the PipingSystem:Underground:* objects to build a detailed simulation domain and piping cir-
cuit. For information regarding the simulation algorithms, see the engineering reference document
section covering the buried piping system objects.
Field: Name
This alpha field is used as an identifying field for the ground heat exchanger.
Field: Inlet Node Name
This alpha field is the name of the inlet node of this component on a plant loop, and must match
other topology definitions such as branch objects.
Field: Outlet Node Name
This alpha field is the name of the outlet node of this component on a plant loop, and must match
other topology definitions such as branch objects.
Field: Design Flow Rate [m3/s]
This numeric field is the designed flow rate for this heat exchanger; the plant loop solver will attempt
to meet this request based on flow and loop conditions.
Field: Trench Length in Pipe Axial Direction [m]
This numeric field represents the axial length of each pipe trench. Each pipe defined for this ground
heat exchanger will have the same length. If different pipes have different lengths, they must use
separate GroundHeatExchanger:HorizontalTrench objects with different lengths.
Field: Number of Trenches
This integer field is the number of trenches for this heat exchanger. Since each trench has a single
pipe, this defines the number of “pipe segments” for this overall heat exchanger. The total piping
length is then calculated as the trench length times the number of trenches.
Field: Horizontal Spacing Between Pipes [m]
This numeric field represents the horizontal spacing (pipe centroid to pipe centroid) between
pipes/trenches.
Field: Pipe Inner Diameter [m]
This numeric field is the inner diameter of the pipe. The same pipe properties are used for all pipes
in this heat exchanger.
Field: Pipe Outer Diameter [m]
1.25. GROUP – CONDENSER EQUIPMENT 1119
This numeric field is the outer diameter of the pipe. The same pipe properties are used for all pipes
in this heat exchanger.
Field: Burial Depth [m]
This numeric field is the burial depth of each pipe, from ground surface to pipe cross section centroid.
The same pipe depth is used for all pipes in this heat exchanger.
Field: Soil Thermal Conductivity [W/mK]
This numeric field is the soil thermal conductivity.
Field: Soil Density [kg/m3]
This numeric field is the soil density.
Field: Soil Specific Heat [J/kgK]
This numeric field is the nominal soil specific heat, but is corrected for moisture content and in
freezing conditions.
Field: Pipe Thermal Conductivity [W/mK]
This numeric field is the pipe thermal conductivity.
Field: Pipe Density [kg/m3]
This numeric field is the pipe density.
Field: Pipe Specific Heat [J/kgK]
This numeric field is the pipe specific heat.
Field: Soil Moisture Content Percent [%]
This numeric field represents the volume fraction, in percent, of water content in the soil.
Field: Soil Moisture Content Percent at Saturation [%]
This numeric field represents the volume fraction, in percent, of water content in the soil which
results in saturation.
1.25.20.1 Inputs
GroundHeatExchanger :HorizontalTrench ,
My Pipe Circuit , !- Name
Plant Supply Intermediate Node , !- Inlet Node Name
Plant Supply Outlet Node , !- Outlet Node Name
0.004 , !- Design Flow Rate
75, !- Trench Length in Pipe Axial Direction
2, !- Number of Trenches
2.0, !- Horizontal Spacing Between Pipes
0.016 , !- Pipe Inner Diameter
0.02667 , !- Pipe Outer Diameter
1.25, !- Burial Depth
1.08, !- Soil Thermal Conductivity
962, !- Soil Density
2576, !- Soil Specific Heat
0.3895 , !- Pipe Thermal Conductivity {W/m-K}
641, !- Pipe Density {kg/m3}
2405, !- Pipe Specific Heat {J/kg -K}
30, !- Soil Moisture Content Volume Fraction {percent}
50, !- Soil Moisture Content Volume Fraction at Saturation {percent}
Site: GroundTemperature :Undisturbed:KusudaAchenbach , !- Type of Undisturbed Ground Temperature
Object
KATemps , !- Name of Undisturbed Ground Temperature Object
0.408; !- Evapotranspiration Ground Cover Parameter
1.25.20.2 Outputs
1.25.21 HeatExchanger:FluidToFluid
A fluid-to-fluid heat exchanger designed to couple the supply side of one plant or condenser loop to
the demand side of another plant or condenser loop. This heat exchanger is fairly general and can
be configured for use in any application where any two loops need to be connected together. The
only constraints are that that one side must be connected to the supply side of one loop and the
other side connected to the demand side of a different loop.
1.25. GROUP – CONDENSER EQUIPMENT 1121
Because the heat exchanger is intended to be generic, its two sides are distinguished by the nature
of loop side being connected. One side is called Loop Supply Side to indicate the heat exchanger
is situated on the supply side of a loop. The other side is called Loop Demand Side to indicate
it is on the demand side of a loop. The heat exchanger is intended to act as a supply component
for the loop connected to it as the “Loop Supply Side” and as a demand component for the loop
connected to it as the “Loop Demand Side.” From the point of view of the heat exchanger model
itself, the Loop Demand Side fluid serves as the source/sink to supply heating/cooling to the fluid
in the Loop Supply Side.
This heat exchanger can be used for a wide variety of applications including chilled water, hot water,
condenser, ground source, primary-secondary systems, etc. Heat transfer is calculated and reported
using a sign convention from chilled water applications where positive heat transfer indicates
energy was extracted from the Loop Supply Side and added to the Loop Demand Side.
Note: Only hydronic “plant” fluids are allowed (excepting Fluid Type ”Steam”), no air-side con-
nections are possible with this heat exchanger.
– The heat transfer between the two sides can be modeled using one of seven different models
for different types of heat exchangers.
– There are also eleven options for different ways to control the heat exchanger.
1122 CHAPTER 1. INPUT-OUTPUT REFERENCE
∗ One general type of control is OnOff where the flow through the heat exchanger is either
fully on or fully off.
∗ Another type of control is Modulated where the flow through the Loop Demand Side is
controlled to try and meet a target setpoint or load on the Loop Supply Side.
As of Version 8.0, this object replaces three separate objects that were available prior to
version 8.0 of EnergyPlus.
1.25.21.1 Inputs
For effectiveness of each heat exchanger model type in detail, See ”Heat Exchangers: Plant Loop
Fluid-to-Fluid Heat Exchanger” Section in Engineering Reference.
1124 CHAPTER 1. INPUT-OUTPUT REFERENCE
– UncontrolledOn. This control mode is applicable to situations where the heat exchanger
is passively running all the time and always transfers as much heat as possible between the
fluid streams. However there is one aspect of control in that it will only request flow on the
Loop Demand Side when there is non-zero flow into the heat exchanger on the Loop Supply
Side. This control mode corresponds to that available in the HeatExchanger:Plate object prior
to version 8.0.
– OperationSchemeModulated. This control mode is applicable to situations where the
heat exchanger is controlled by an operation scheme (see objects called PlantEquipmentOp-
erationScheme or CondenserEquipmentOperationSchemes). When using this control mode
the heat exchanger must be listed in PlantEquipmentList or a CondenserEquipmentList and it
serves as a supply component. The operation scheme will dispatch a load request to the heat
exchanger which it will try meet by conditioning the fluid stream connected as the Loop Supply
Side. If the heat exchanger could exceed the load request, then the flow through the fluid
stream connected as the Loop Demand Side will be modulated to just meet the load request.
– OperationSchemeOnOff. This control mode is applicable to situations where the heat
exchanger is controlled by an operation scheme (see objects called PlantEquipmentOpera-
tionScheme or CondenserEquipmentOperationSchemes). When using this control mode the
heat exchanger must be listed in PlantEquipmentList or a CondenserEquipmentList and it
serves as a supply component. The operation scheme will dispatch a load request to the heat
exchanger which it will use as an on/off signal to decide if the heat exchange should run or
not. If it runs, it will run at full capacity and may exceed the load request.
– HeatingSetpointModulated. This control mode is applicable to situations where the Loop
Demand Side can provide useful heating to the Loop Supply Side. A heating setpoint is
obtained from a node named in the following field. If the setpoint and inlet temperatures are
such that heat exchanger could transfer heat from the Loop Demand Side to the Loop Supply
Side to meet the heating setpoint, then the heat exchanger will run. The inlet temperatures
must differ by more than the value set in the field called Minimum Temperature Difference
to Activate Heat Exchanger for the heat exchanger to operate. If the heat exchanger could
overshoot the setpoint, then the flow through the fluid stream connected as the Loop Demand
Side will be modulated to just meet the setpoint.
– HeatingSetpointOnOff. This control mode is applicable to situations where the Loop De-
mand Side can provide useful heating to the Loop Supply Side. A heating setpoint is obtained
from a node named in the following field. If the setpoints and inlet temperatures are such that
heat exchanger could transfer heat from the Loop Demand Side to the Loop Supply Side to
1.25. GROUP – CONDENSER EQUIPMENT 1125
meet the heating setpoint, then the heat exchanger will run. The inlet temperatures must differ
by more than the value set in the field called Minimum Temperature Difference to Activate
Heat Exchanger for the heat exchanger to operate. If it runs, it will run at full capacity and
may overshoot the setpoint.
– CoolingSetpointModulated. This control mode is applicable to situations where the Loop
Demand Side can provide useful cooling to the Loop Supply Side. A cooling setpoint is
obtained from a node named in the following field. If the setpoints and inlet temperatures are
such that heat exchanger could transfer heat from the Loop Supply Side to the Loop Demand
Side to meet the cooling setpoint, then the heat exchanger will run. The inlet temperatures
must differ by more than the value set in the field called Minimum Temperature Difference
to Activate Heat Exchanger for the heat exchanger to operate. If the heat exchanger could
undershoot the setpoint, then the flow through the fluid stream connected as the Loop Demand
Side will be modulated to just meet the setpoint.
– CoolingSetpointOnOff. This control mode is applicable to situations where the Loop De-
mand Side can provide useful cooling to the Loop Supply Side. A cooling setpoint is obtained
from a node named in the following field. If the setpoints and inlet temperatures are such
that heat exchanger could transfer heat from the Loop Supply Side to the Loop Demand Side
to meet the cooling setpoint, then the heat exchanger will run. The inlet temperatures must
differ by more than the value set in the field called Minimum Temperature Difference to Acti-
vate Heat Exchanger for the heat exchanger to operate. If it runs, it will run at full capacity
and may undershoot the setpoint. This control mode corresponds to that available in the
HeatExchanger:WatersideEconomizer object prior to version 8.0.
– DualDeadbandSetpointModulated. This control mode is applicable to situations where
the Loop Demand Side can provide either useful cooling or heating to the Loop Supply Side. A
dual deadband setpoint is obtained from a node named in the following field. If the setpoints
and inlet temperatures are such that heat exchanger could transfer heat from the Loop Demand
Side to the Loop Supply Side to meet the lower setpoint, then the heat exchanger will run.
If the setpoints and inlet temperatures are such that heat exchanger could transfer heat from
the Loop Supply Side to the Loop Demand Side to meet the high setpoint, then the heat
exchanger will run. The inlet temperatures must differ by more than the value set in the field
called Minimum Temperature Difference to Activate Heat Exchanger for the heat exchanger to
operate. If the heat exchanger could overshoot the lower setpoint, or undershoot the higher
setpoint, then the flow through the fluid stream connected as the Loop Demand Side will be
modulated to just meet the deadband setpoint.
– DualDeadbandSetpointOnOff. This control mode is applicable to situations where the
Loop Demand Side can provide either useful cooling or heating to the Loop Supply Side. A
dual deadband setpoint is obtained from a node named in the following field. If the setpoints
and inlet temperatures are such that heat exchanger could transfer heat from the Loop Demand
Side to the Loop Supply Side to meet the lower setpoint, then the heat exchanger will run.
If the setpoints and inlet temperatures are such that heat exchanger could transfer heat from
the Loop Supply Side to the Loop Demand Side to meet the high setpoint, then the heat
exchanger will run. The inlet temperatures must differ by more than the value set in the field
called Minimum Temperature Difference to Activate Heat Exchanger for the heat exchanger to
operate. If the heat exchanger runs, it will run at full capacity and may overshoot the lower
setpoint or undershoot the higher setpoint.
– CoolingDifferentialOnOff. This control mode is applicable to situations where the Loop
Demand Side can provide useful cooling to the Loop Supply Side. This mode is similar to
1126 CHAPTER 1. INPUT-OUTPUT REFERENCE
CoolingSetpointOnOff except that it ignores any cooling setpoint and its control is based only
on the temperature difference between Loop Demand Side and the Loop Supply Side. The inlet
temperatures must differ by more than the value set in the field called Minimum Temperature
Difference to Activate Heat Exchanger for the heat exchanger to operate. This control
mode corresponds to that available in the HeatExchanger:WatersideEconomizer object prior
to version 8.0.
– CoolingSetpointOnOffWithComponentOverride. This control mode is applicable to sit-
uations where the heat exchanger operation is integrated with the operation of a specific chiller.
Typically the heat exchanger and chiller are in parallel on separate branches. When conditions
are favorable for the heat exchanger to provide cooling to the Loop Supply Side, the heat ex-
changer is run and the integrated chiller is turned off. When conditions are not favorable, the
heat exchanger is competely off and the chiller is allowed to run as usual. A cooling setpoint is
obtained from a node named in the following field. If it runs it will run at full capacity and may
undershoot the setpoint. The chiller that is integrated with the heat exchanger is identified by
entering the names of the chiller’s inlet nodes in the input fields below. The control decision
can be based on one of three different temperature signals selected in the field below called
Component Override Cooling Control Temperature Mode. The setpoint and control signal
temperatures must differ by more than the value set in the field called Minimum Temperature
Difference to Activate Heat Exchanger for the heat exchanger to operate. This control mode
corresponds to that available in the HeatExchanger:Hydronic object prior to version 8.0.
1.25.21.1.15 Field: Component Override Loop Supply Side Inlet Node Name
This field specifies the name of an inlet node for the remote component that will be integrated with
this heat exchanger. This inlet should be on the supply side of a loop – typically chilled water
1.25. GROUP – CONDENSER EQUIPMENT 1127
inlet or return for a chiller. This field and the next two are only used for the control type called
CoolingSetpointOnOffWithComponentOverride.
1.25.21.1.16 Field: Component Override Loop Demand Side Inlet Node Name
This field specifies the name of an inlet node for the remote component that will be integrated
with this heat exchanger. This inlet should be on the demand side of a loop – typically condenser
water inlet or return for a water-cooled chiller. This field is only used for the control type called
CoolingSetpointOnOffWithComponentOverride.
HeatExchanger:FluidToFluid ,
CondenserLoop HX ,!- Name
ALWAYS_ON , !- Availability Schedule Name
CondenserLoop HX HX Inlet Node , !- Loop Demand Side Inlet Node Name
CondenserLoop HX HX Outlet Node , !- Loop Demand Side Outlet Node Name
autosize , !- Loop Demand Side Design Flow Rate
CondenserLoop Pump - HXNode , !- Loop Supply Side Inlet Node Name
CondenserLoop HX - ChillerNode ,!- Loop Supply Side Outlet Node Name
autosize , !- Loop Supply Side Design Flow Rate
CounterFlow , !- Heat Exchange Model Type
autosize , !- Heat Exchanger U-Factor Times Area Value
CoolingDifferentialOnOff , !- Control Type
, !- Heat Exchanger Setpoint Node Name
2.0, !- Minimum Temperature Difference to Activate Heat Exchanger
FreeCooling; !- Heat Transfer Metering End Use Type
1128 CHAPTER 1. INPUT-OUTPUT REFERENCE
HeatExchanger:FluidToFluid ,
SOURCE to TRANSFER HX , !- Name
AlwaysOnSchedule , !- Availability Schedule Name
SOURCE Demand HX Inlet Node , !- Loop Demand Side Inlet Node Name
SOURCE Demand HX Outlet Node , !- Loop Demand Side Outlet Node Name
0.003 , !- Loop Demand Side Design Flow Rate
TRANSFER HX Supply Inlet Node , !- Loop Supply Side Inlet Node Name
TRANSFER HX Supply Outlet Node , !- Loop Supply Side Outlet Node Name
0.003 , !- Loop Supply Side Design Flow Rate
CrossFlow , !- Heat Exchange Model Type
15000 , !- Heat Exchanger U-Factor Times Area Value
DualDeadbandSetpointModulated , !- Control Type
TRANSFER Supply Outlet Node , !- Heat Exchanger Setpoint Node Name
0.2 , !- Minimum Temperature Difference to Activate Heat Exchanger
LoopToLoop; !- Heat Transfer Metering End Use Type
1.25.21.2 Outputs
1.25.21.2.3 Fluid Heat Exchanger Loop Supply Side Mass Flow Rate [kg/s]
This is the system mass flow of fluid through the heat exchanger side connected as the Loop Supply
Side, in kg/s.
1.25.21.2.4 Fluid Heat Exchanger Loop Supply Side Inlet Temperature [C]
This is the temperature, in degrees Celsius, of the fluid entering the heat exchanger on the side
connected as the Loop Supply Side.
1.25.21.2.5 Fluid Heat Exchanger Loop Supply Side Outlet Temperature [C]
This is the temperature, in degrees Celsius, of the fluid leaving the heat exchanger on the side
connected as the Loop Supply Side.
1.25.21.2.6 Fluid Heat Exchanger Loop Demand Side Mass Flow Rate [kg/s]
This is the system mass flow of fluid through the heat exchanger side connected as the Loop Demand
Side, in kg/s.
1.25.21.2.7 Fluid Heat Exchanger Loop Demand Side Inlet Temperature [C]
This is the temperature, in degrees Celsius, of the fluid entering the heat exchanger on the side
connected as the Loop Demand Side.
1.26. GROUP – AIR DISTRIBUTION 1129
1.25.21.2.8 Fluid Heat Exchanger Loop Demand Side Outlet Temperature [C]
This is the temperature, in degrees Celsius, of the fluid leaving the heat exchanger on the side
connected as the Loop Demand Side.
determine what runs or doesn’t run. If a component other than the supply fan is scheduled off, then
it will remain off even if the night cycle manager turns on the system.
1.26.1.1 Inputs
1.26.1.1.11 Field: Design Return Air Flow Fraction of Supply Air Flow
This field specifies the design air loop return air flow rate as a fraction of the supply flow rate when
there is no exhaust flow. It may be used to set zero return air flow for a DOAS system or to model
a pressurized system where the return flow is a fraction of the supply flow. The return air flow rate
will never be greater than the current supply air flow rate multiplied by this fraction. It may be less
if there is unbalanced exhaust from any zones served by this airloop. The default is 1.0. If the air
loop has no return path, then this field is ignored.
An example of this statement in an IDF is:
AirLoopHVAC ,
Main Dual Duct Air Loop , !- Name
Dual Duct System 1 Controllers , !- Controller List Name
Dual Duct System 1 Schedule List , !- Availability Manager List Name
1.3 , !- Design Supply Air Flow Rate {m3/s}
Dual Duct Air Loop Branches , !- Branch List Name
Dual Duct Connectors , !- Connector List Name
Supply Fan Inlet Node , !- Supply Side Inlet Node Name
Return Air Mixer Outlet , !- Demand Side Outlet Node Name
Zone Equipment Inlet Node List , !- Demand Side Inlet Node Names
Air Loop Outlet Node List , !- Supply Side Outlet Node Names
1.0; !- Design Return Air Flow Fraction of Supply Air Flow
1.26.1.2 Outputs
1.26.1.2.2 HVAC System Solver Iteration Count [] This field reports the total number
of HVAC System solver iterations in the current system time step or the maximum iterations possible
for this solver if the simulation has not yet converged before it reached the maximum iterations.
1.26.1.2.3 Air System Solver Iteration Count [] This field reports the total number of
Air System solver iterations in the current system time step or the maximum iterations possible for
this solver if the simulation has not yet converged before it reached the maximum iterations.
1.26.1.2.4 Air System Simulation Maximum Iteration Count [] This field reports
the maximum number of iterations possible for an Air System simulation.
1.26.1.2.5 Air System Simulation Iteration Count [] This field reports the total num-
ber of Air System iterations in the current system time step or the maximum iterations possible for
this solver if the simulation has not yet converged before it reached the maximum iterations.
1.26.1.3 Outputs
This section provides more detailed information on the reporting available for outdoor air ventila-
tion. Sixteen cooling and heating load variables and eight energy summary variables are available
that report the impact of system outdoor air on zone loads, system demand and total energy use.
The representative air system shown in the diagram below shows outdoor air (OA), return air (RA),
supply air (SA) and mixed air (MA).
The overall effect of outdoor air on the system shown above can be summarized by considering the
mixing box. In this system, part or all of the return air is replaced by outdoor air. The presence
of any heat recovery will already be taken into account and thus will automatically be accounted
for by using the outdoor air inlet conditions to the mixing box (point OA in the diagram) rather
than actual outdoor air conditions. Thus, the overall energy impact of outdoor air (ventilation) on
a particular system can be evaluated by multiplying the outdoor air mass flow rate by the enthalpy
difference between the outdoor air entering the mixing box (OA) and the return air entering the
mixing box (RA’) as shown in the following equation.
1134 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.26.1.3.9 Zone Target Voz Ventilation Flow Rate [m3/s] The target ventilation flow
rate Voz−dyn at standard density at the current timestep as defined by the zone Design Specification
Outdoor Air Object (DesignSpecification:OutdoorAir or DesignSpecification:OutdoorAir:SpaceList).
1.26. GROUP – AIR DISTRIBUTION 1135
1.26.1.3.10 Zone Ventilation Below Target Voz Time [hr] The time that the zone
total ventilation rate (mechanical ventilation plus natural ventilation) is more than 1% below the
Zone Target Voz Ventilation Flow Rate.
1.26.1.3.11 Zone Ventilation At Target Voz Time [hr] The time that the zone total
ventilation rate (mechanical ventilation plus natural ventilation) is within 1% of the Zone Target
Voz Ventilation Flow Rate.
1.26.1.3.12 Zone Ventilation Above Target Voz Time [hr] The time that the zone
total ventilation rate (mechanical ventilation plus natural ventilation) is more than 1% above the
Zone Target Voz Ventilation Flow Rate.
1.26.1.3.13 Zone Ventilation When Unoccupied Time [hr] The time that the zone
total ventilation rate (mechanical ventilation plus natural ventilation) is greater than zero when the
zone is unoccupied.
1.26.1.3.14 Facility Any Zone Ventilation Below Target Voz Time [hr] The time
that any zone’s total ventilation rate (mechanical ventilation plus natural ventilation) is more than
1% below the Zone Target Voz Ventilation Flow Rate.
1.26.1.3.15 Facility All Zones Ventilation At Target Voz Time [hr] The time that
every zone’s total ventilation rate (mechanical ventilation plus natural ventilation) is within 1% of
the Zone Target Voz Ventilation Flow Rate.
1.26.1.3.16 Facility Any Zone Ventilation Above Target Voz Time [hr] The time
that any zone’s total ventilation rate (mechanical ventilation plus natural ventilation) is more than
1% above the Zone Target Voz Ventilation Flow Rate.
1.26.1.3.17 Facility Any Zone Ventilation When Unoccupied Time [hr] The time
that any zone’s total ventilation rate (mechanical ventilation plus natural ventilation) is greater than
zero when the zone is unoccupied.
1.26.1.3.18 Air System Mechanical Ventilation Flow Rate [m3/s] The current
airloop mechanical ventilation flow rate at standard density.
1.26.1.3.19 Air System Natural Ventilation Flow Rate [m3/s] The sum of the nat-
ural ventilation flow rate at standard density at the current timestep for each zone on the airloop.
If any zone terminal unit has a Design Specification Air Terminal Sizing Object (DesignSpecifica-
tion:AirTerminal:Sizing) then the natural ventilation rate for that zone is scaled by the Fraction of
Minimum Outdoor Air Flow value.
1.26.1.3.20 Air System Target Voz Ventilation Flow Rate [m3/s] The sum of
the target ventilation flow rates Voz−dyn at standard density at the current timestep for each zone
on the airloop. If any zone terminal unit has a Design Specification Air Terminal Sizing Object
(DesignSpecification:AirTerminal:Sizing) then the target ventilation rate for that zone is scaled by
the Fraction of Minimum Outdoor Air Flow value.
1136 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.26.1.3.21 Air System Ventilation Below Target Voz Time [hr] The time that the
airloop total ventilation rate (mechanical ventilation plus natural ventilation) is more than 1% below
the Zone Target Voz Ventilation Flow Rate.
1.26.1.3.22 Air System Ventilation At Target Voz Time [hr] The time that the
airloop total ventilation rate (mechanical ventilation plus natural ventilation) is within 1% of the
Zone Target Voz Ventilation Flow Rate.
1.26.1.3.23 Air System Ventilation Above Target Voz Time [hr] The time that
the airloop total ventilation rate (mechanical ventilation plus natural ventilation) is more than 1%
above the Zone Target Voz Ventilation Flow Rate.
1.26.1.3.24 Air System Ventilation When Unoccupied Time [hr] The time that
the airloop total ventilation rate (mechanical ventilation plus natural ventilation) is greater than
zero when all of the zones on the airloop are unoccupied.
The example syntax below shows the basic ventilation flow variables reported on an hourly basis.
AirPX
athN um
ṁn
q̇OA,Zone 1 = q̇OA (1.102)
ṁsys
n=1
Four output variables each for cooling and heating report the impact of the ventilation air on the
zone load in the absence of ventilation air system interactions. The ventilation load output variables
are:
Ventilation Cooling Zone Mechanical Ven- Zone Mechanical Ven- Zone Mechanical Ven-
tilation No Load Heat tilation Cooling Load tilation Heating Load
Removal Energy Decrease Energy Increase Energy
Zone Mechanical Ven-
tilation Heating Load
Increase Due to Over-
cooling Energy
Ventilation Heating Zone Mechanical Ven- Zone Mechanical Ven- Zone Mechanical Ven-
tilation No Load Heat tilation Cooling Load tilation Heating Load
Addition Energy Increase Energy Decrease Energy
Zone Mechanical Ven-
tilation Cooling Load
Increase Due to Over-
heating Energy
1.26. GROUP – AIR DISTRIBUTION 1139
The example syntax below shows the basic ventilation load variables reported on a monthly basis.
Reporting on a timestep or hourly level would produce a detailed report with variables intermingled
with the other output variables that might be requested in the input file.
Another method will more easily encapsulate the report:
Output:Table:Monthly ,
Ventilation Loads , !- Name
, !- DigitsAfterDecimal
Zone Mechanical Ventilation No Load Heat Removal Energy ,
SumOrAverage ,
Zone Mechanical Ventilation Cooling Load Increase Due to Overheating Energy ,
SumOrAverage ,
Zone Mechanical Ventilation Cooling Load Decrease Energy ,
SumOrAverage ,
Zone Mechanical Ventilation Cooling Load Increase Energy ,
SumOrAverage ,
Zone Mechanical Ventilation No Load Heat Addition Energy ,
SumOrAverage ,
Zone Mechanical Ventilation Heating Load Increase Due to Overcooling Energy ,
SumOrAverage ,
Zone Mechanical Ventilation Heating Load Decrease Energy ,
SumOrAverage ,
Zone Mechanical Ventilation Heating Load Increase Energy ,
SumOrAverage;
This combination will report the ventilation loads on a monthly basis in a HTML style report that
can be easily read in a web browser. Review the Output:Table:Monthly object for other methods of
display or further options on this report item.
Heat Removal from the Air Loop (Sum of all components) in Joules
In ‘Output:Table:Monthly’ format shown below.
OutputControl:Table:Style ,HTML;
Output:Table:Monthly ,
System Loads , !- Name
, !- DigitsAfterDecimal
Air System Total Heating Energy , SumOrAverage ,
Air System Total Cooling Energy , SumOrAverage;
Water Consumption for the system (humidifiers and evaporative coolers) (m3).
The Standard reports file includes these variables reporting in the Tabular report form as “Air Loop
System Energy and Water Use”.
OutputControl:Table:Style ,HTML;
Output:Table:Monthly ,
Air Loop System Energy and Water Use , !- Name
, !- DigitsAfterDecimal
Air System Hot Water Energy , SumOrAverage ,
Air System Steam Energy , SumOrAverage ,
Air System Chilled Water Energy , SumOrAverage ,
Air System Electricity Energy , SumOrAverage ,
Air System NaturalGas Energy , SumOrAverage ,
Air System Water Volume , SumOrAverage;
OutputControl:Table:Style ,HTML;
Output:Table:Monthly ,
Air Loop System Component Loads , !- Name
, !- DigitsAfterDecimal
Air System Fan Air Heating Energy , SumOrAverage ,
Air System Cooling Coil Total Cooling Energy , SumOrAverage ,
Air System Heating Coil Total Heating Energy , SumOrAverage ,
Air System Heat Exchanger Total Heating Energy , SumOrAverage ,
Air System Heat Exchanger Total Cooling Energy , SumOrAverage ,
Air System Humidifier Total Heating Energy , SumOrAverage ,
Air System Evaporative Cooler Total Cooling Energy , SumOrAverage ,
Air System Desiccant Dehumidifier Total Cooling Energy , SumOrAverage;
Energy added to air loop by air-to-air heat recovery heat exchangers (Joules)
Energy removed from air loop by air-to-air heat recovery heat exchangers (Joules)
1.26.5.11 Air System User Defined Air Terminal Total Heating Energy
Energy added to air loop by user defined air terminal units (Joules)
1.26.5.12 Air System User Defined Air Terminal Total Cooling Energy
Energy removed from air loop by user defined air terminal units (Joules)
1144 CHAPTER 1. INPUT-OUTPUT REFERENCE
Consumption for heating coil hot water (both purchased and plant supplied) (Joules)
Consumption for cooling coil chilled water (both purchased and plant supplied) (Joules)
OutputControl:Table:Style ,HTML;
Output:Table:Monthly ,
Air Loop System Component Energy Use , !- Name
, !- DigitsAfterDecimal
Air System Fan Electricity Energy , SumOrAverage ,
Air System Heating Coil Hot Water Energy , SumOrAverage ,
Air System Cooling Coil Chilled Water Energy , SumOrAverage ,
Air System DX Heating Coil Electricity Energy , SumOrAverage ,
Air System DX Cooling Coil Electricity Energy , SumOrAverage ,
Air System Heating Coil Electricity Energy , SumOrAverage ,
Air System Heating Coil Gas Energy , SumOrAverage ,
Air System Heating Coil Steam Energy , SumOrAverage ,
Air System Humidifier Electricity Energy , SumOrAverage ,
Air System Evaporative Cooler Electricity Energy , SumOrAverage ,
Air System Desiccant Dehumidifier Electricity Energy , SumOrAverage;
1.26.8 AirLoopHVAC:ControllerList
The syntax for the AirLoopHVAC:ControllerList definition is shown below. As with other lists in
EnergyPlus input, the object title and identifying name are followed by type-name pairs. In this
case, the types are controller types. The order in which controllers appear on this list also define
the priority as described below. The identifying name refers back to the name recorded in the
AirLoopHVAC statement.
1.26.8.1 Inputs
AirLoopHVAC:ControllerList ,
Dual Duct System 1 Controllers ,
Controller:WaterCoil , Main Cooling Coil Controller ,
Controller:WaterCoil , Main Heating Coil Controller;
1.26.9 AvailabilityManagerAssignmentList
The AvailabilityManagerAssignmentList defines the applicable managers used for an AirLoopHVAC
or PlantLoop. The priority of availability managers is based on a set of rules and are specific to the
type of loop. The output from each Availability Manager is an availability status flag. This flag can
have the values NoAction, ForceOff, CycleOn, or CycleOnZoneFansOnly (used only for air loops).
The availability status flags for the Availability Managers referenced by an air or plant loop are used
to set the availability status flag for each loop. For the air loops, ForceOff takes precedence: if any
of the loop’s availability managers are showing status ForceOff, the loop status will be ForceOff.
Next in precedence is CycleOnZoneFansOnly, followed by CycleOn, and NoAction. For the plant
loops, there is no precedence among the Availability Manager status flag values. Instead, the first
availability manager giving a status flag value other than NoAction sets the status for the loop. The
Availability Managers are executed in Availability Manager List order.
Special rules also apply for which managers may be listed in an Availability Manager list. The Hybrid
Ventilation Control Manager (object: AvailabilityManager:HybridVentilation) is a special type of
manager and is never specified in an Availability Manager List (it is used stand-alone for a specific
air loop). All other types of availability managers may be listed in the Availability Manager List
used for AirLoopHVACs. For Plant Loops, the Night Cycle and Night Ventilation managers (objects:
AvailabilityManager:NightCycle and AvailabilityManager:NightVentilation) are not allowed in the
Availability Manager List.
1.26.9.1 Inputs
calculated each simulation timestep. These output variables can be used to prioritize the managers
according to the required control strategy. Six managers are accomodated in the list by default.
This object is extensible, so additional pairs of the next two fields may be added.
AvailabilityManagerAssignmentList ,
Collector Loop Availability Manager List , !- Name
AvailabilityManager :HighTemperatureTurnOff , !- System Availability Manager Type 1
High Temperature Turn Off Availability Manager , !- System Availability Manager Name 1
AvailabilityManager : LowTemperatureTurnOn , !- System Availability Manager Type 2
Low Temperature Turn On Availability Manager , !- System Availability Manager Name 2
AvailabilityManager :DifferentialThermostat , !- System Availability Manager Type 3
Differential Thermostat Availability Manager; !- System Availability Manager Name 3
1.26.10 AirLoopHVAC:OutdoorAirSystem
The Outside Air System (object AirLoopHVAC:OutdoorAirSystem) is a subsystem of an AirLoopH-
VAC. It handles the mixed air portion of the primary air system: the system relief air, the outside
air inlet, and any components and controllers associated with the system relief air and outside air
streams. From the perspective of the primary air loop the Outside Air System is treated as a single
component. As a subsystem, it can contain one or more components and controllers.
The input for the Outside Air System consists of a system name, a controller list name, and an
equipment list name. The controller list simply lists, by type and unique name, all the controllers
in the subsystem. The controllers will be simulated in list order. The equipment list lists all the
components in the subsystem, by type and name. The equipment is simulated in list order.
The equipment inlet/outlet must be sequential with no loops - the simulation can only handle a
straight-through air path, both on the primary air side and on the secondary air side, if any. Heat
exchanger secondary air inlets need to be independent of the primary air stream – usually relief air
is used.
The Outside Air System (object AirLoopHVAC:OutdoorAirSystem) can also be defined as a
subsystem of an AirLoopHVAC:DedicatedOutdoorAirSystem. When this subsystem is referred
in AirLoopHVAC:DedicatedOutdoorAirSystem, the Controller:OutdoorAir can not be listed in
the AirLoopHVAC:ControllerList, because the outdoor air flow rate will not be determined
by Controller:OutdoorAir. Instead, the outdoor air flow rate will be specified by AirLoopH-
VAC:DedicatedOutdoorAirSystem. In addition, the OutdoorAir:Mixer will not be allowed in the
AirLoopHVAC:OutdoorAirSystem:EquipmentList as a component, because no mix is needed due to
100% outdoor incoming airflow determined by AirLoopHVAC:DedicatedOutdoorAirSystem.
1.26.10.1 Inputs
The unique, user assigned name for a single instance of an Outside Air System. Any other object
referencing this Outside Air System will use this name.
AirLoopHVAC:ControllerList ,
Reheat System 1 Controllers ,
Controller:WaterCoil , Main Cooling Coil Controller;
AirLoopHVAC:OutdoorAirSystem ,
OA Sys 1,
OA Sys 1 Controllers ,
OA Sys 1 Equipment;
AirLoopHVAC:ControllerList ,
OA Sys 1 Controllers ,
Controller:OutdoorAir , OA Controller 1;
AirLoopHVAC:OutdoorAirSystem:EquipmentList ,
OA Sys 1 Equipment ,
HeatExchanger:AirToAir:FlatPlate ,OA Heat Recovery 1,
OutdoorAir:Mixer , OA Mixing Box 1;
1.26.10.2 Outputs
The impact of using outside air/mechanical ventilation is described in the section: Outdoor Air
Ventilation Outputs.
1.26.11 AirLoopHVAC:OutdoorAirSystem:EquipmentList
Used to specify the components in the outdoor air system. The components will be simulated in the
order in which they occur in the list.
The following HVAC equipment types are allowed as outdoor air system equipment. The component
matrix (Figure 1.110) shows which coils and fans are allowed with which equipment models.
1.26.11.1 Inputs
AirLoopHVAC:OutdoorAirSystem:EquipmentList ,
OA Sys 1 Equipment ,
HeatExchanger:AirToAir:FlatPlate ,OA Heat Recovery 1,
OutdoorAir:Mixer , OA Mixing Box 1;
1.26.12 OutdoorAir:Node
The OutdoorAir:Node object declares an HVAC system node for outdoor air conditions. The program
automatically sets the air conditions at these nodes to correspond to the ambient environmental
conditions at the beginning of every timestep. The outdoor air node is typically used as the inlet
air node to an HVAC component such as the OutdoorAir:Mixer object. Multiple OutdoorAir:Node
objects can be used in an input file, however, duplicate node names are not allowed.
The Height Above Ground field is used to adjust the weather file air conditions, e.g., outdoor dry-
bulb and wet-bulb air temperatures, for atmospheric variation with height. This variation can
become a significant factor when modeling tall buildings. See the Engineering Reference section on
Atmospheric Variation for a description of the algorithm for variation of atmospheric properties with
height. A blank entry or a value less than zero for this field indicates that the height will be ignored
and the weather file conditions will be used.
OutdoorAir:Node and OutdoorAir:NodeList both set a node to outdoor air conditions.
OutdoorAir:Node modifies the weather file conditions if a height has been specified. Out-
doorAir:NodeList does not have a height input and always uses the weather file conditions
without modification. The same node name may not be used with both of these objects.
When declared in surface property objects SurfaceProperty:LocalEnvironment, in zone prop-
erty objects ZoneProperty:LocalEnvironment, or as an external node in the airflow network
calculation linking to a surface node AirflowNetwork:Multizone:Surface, the object can also be
used to define local outdoor air conditions for surfaces, zones or air loop components. The local
outdoor air conditions would be used in the EnergyPlus calculations for:
1152 CHAPTER 1. INPUT-OUTPUT REFERENCE
When used in these cases, optional schedule inputs of local ambient air conditions, including dry-
bulb temperature, wet-bulb temperature, wind velocity, and wind direction, can be defined in the
optional fields. When used in the airflow network for wind pressure calculation, the wind pressure
coefficient curve name and calculation details should also be defined.
1.26.12.1 Inputs
OutdoorAir:Node ,
OA Node 1; !- Name
OutdoorAir:Node ,
Floor 10 Outdoor air Inlet Node , !- Name
30.0; !- Height Above Ground {m}
OutdoorAir:Node ,
LocalOutdoorAirNode :0001 , !- Name
, !- Height Above Ground
OutdoorAirNodeDryBulb :0001 , !- Drybulb Temperature Schedule Name
OutdoorAirNodeWetBulb :0001 , !- Wetbulb Temperature Schedule Name
OutdoorAirNodeWindSpeed :0001 , !- Wind Speed Schedule Name
OutdoorAirNodeWindDir :0001; !- Wind Direction Schedule Name
NFacade_WPCValue , !- Wind Pressure Coefficient Curve Name
No , !- Symmetric Wind Pressure Coefficient Curve
Absolute; !- Wind Angle Type
e.g.
Output:Variable ,
Floor 10 Outdoor air Inlet Node ,
System Node Temperature ,
Hourly;
1.26.14 OutdoorAir:NodeList
The program needs to know which HVAC system nodes are inlets for outdoor air. Knowing this, the
program can set the conditions at these nodes to the outdoor conditions at the start of each major
timestep. The OutdoorAir:NodeList provides the means for specifying which nodes are outdoor air
nodes.
The input is flexible: there may be one or more OutdoorAir:NodeList in each input file. Each list
contains up to 25 names. The names can be the name of a unique HVAC system node, or the name
of a Node List which will contain the actual node names. Duplicate node names are ignored.
OutdoorAir:Node and OutdoorAir:NodeList both set a node to outdoor air conditions.
OutdoorAir:Node modifies the weather file conditions if a height has been specified. Out-
doorAir:NodeList does not have a height input and always uses the weather file conditions
without modification. The same node name may not be used with both of these objects.
1.26.14.1 Inputs
OutdoorAir:NodeList ,
OutsideAirInletNodes ;
NodeList ,OutsideAirInletNodes ,
Outdoor air Inlet Node;
1.26.15 OutdoorAir:Mixer
The OutdoorAir:Mixer is the most common component used in an outdoor air system. The outdoor
air mixer has 2 inlet air streams: the system return air and the outdoor air. It has 2 outlet air
streams: the system relief air and the mixed air. This is a passive component. It takes the inlet
mass flows and conditions plus the relief air mass flow and calculates the mixed air flow rate and
conditions (as well as the relief air conditions). The inlet and relief mass flow must be set outside
the component – most commonly by an outdoor air controller. The OutdoorAir:Mixer can also be
used in compound components such as a fan coil unit.
Input for this object is very simple: a unique name plus the node names of the 2 inlet nodes and the
2 outlet nodes.
1.27. GROUP – AIRFLOW NETWORK 1155
1.26.15.1 Inputs
OutdoorAir:Mixer ,
Zone1WindACOAMixer , ! name
Zone1WindACOAMixerOutletNode , ! mixer outlet node
Zone1WindACOAInNode , ! mixer OA node
Zone1WindACExhNode , ! mixer relief node
Zone1WindACAirInletNode ; ! mixer inlet node
– Simulate zone pressures due to envelope leakage and forced air distribution during HVAC
system fan operation
– Simulate node pressures in a forced air distribution system during HVAC system fan operation
– Calculate multizone airflows due to forced air, wind, and surface leakage, including adjacent
zones and outdoors, during HVAC system fan operation
1156 CHAPTER 1. INPUT-OUTPUT REFERENCE
– Simulate distribution system airflows, including supply and return air leaks, during HVAC
system fan operation
– Simulate air distribution system node temperatures and humidity ratios during HVAC system
fan operation
– Calculate duct conduction losses during HVAC system fan operation
– Calculate vapor diffusion losses of ducts during HVAC system fan operation
– Calculate sensible and latent loads on the surrounding zones due to supply and return air leaks
in the air distribution system during HVAC system fan operation
– Simulate zone pressures due to envelope leakage driven by wind when the HVAC system fan
is off or if no air distribution system is specified
– Calculate multizone airflows due to wind and surface leakage, including adjacent zones and
outdoors when the HVAC system fan is off or if no air distribution system is specified
– Allow zone exhaust fans to be included as part of the airflow network
– For airflow networks with a forced air distribution system, calculate zone sensible and la-
tent loads for two different supply air fan operation modes as required: cycling fan, cycling
compressor (CyclingFanAndCompressor) and continuous fan, cycling compressor (Continuous-
FanWithCyclingCompressor)
– When multiple forced air systems (AirloopHVAC) are present in the idf, all systems must be
used in the Airflow Network model.
AirflowNetwork:IntraZone:Linkage
AirflowNetwork:Distribution:Node
AirflowNetwork:Distribution:Component:Leak
AirflowNetwork:Distribution:Component:LeakageRatio
AirflowNetwork:Distribution:Component:Duct
AirflowNetwork:Distribution:Component:ConstantPressureDrop
AirflowNetwork:Distribution:Component:Fan
AirflowNetwork:Distribution:Component:Coil
AirflowNetwork:Distribution:Component:HeatExchanger
AirflowNetwork:Distribution:Component:TerminalUnit
AirflowNetwork:Distribution:Component:OutdoorAirFlow
AirflowNetwork:Distribution:Component:ReliefAirFlow
AirflowNetwork:Distribution:Linkage
– AirflowNetwork:SimulationControl defines basic run parameters for the air flow calcula-
tions and specifies whether wind pressure coefficients are input by the user or, for rectangular
buildings, calculated by the program.
– The AirflowNetwork:MultiZone:Zone object specifies the ventilation control that applies
to all of the openable exterior and interior windows and doors in the corresponding thermal
zone. Surface-level ventilation control can be used to override the zone-level ventilation control
if required (see AirflowNetwork: MultiZone:Surface object below).
– AirflowNetwork:MultiZone:Surface object indicates whether a heat transfer surface (wall,
window, etc.) has a crack or opening and references an object in the list below that gives
the air flow characteristics of that crack, opening, or zone exhaust fan. The AirflowNet-
work:MultiZone:Surface object can also be used to specify individual ventilation control for
openable exterior and interior windows and doors.
∗ AirflowNetwork:MultiZone:Surface:Crack
∗ AirflowNetwork:MultiZone:Surface:EffectiveLeakageArea
∗ AirflowNetwork:MultiZone:SpecifiedFlowRate
∗ AirflowNetwork:MultiZone:Component:SimpleOpening
∗ AirflowNetwork:Multi-Zone:Component:DetailedOpening
∗ AirflowNetwork:MultiZone:Component:HorizontalOpening
∗ AirflowNetwork:Multi-Zone:Component:ZoneExhaustFan
– AirflowNetwork:MultiZone:ReferenceCrackConditions is used to normalize crack in-
formation that is based on measurements of crack air flow.
– AirflowNetwork:Distribution:Node represents air distribution system nodes for the Air-
flowNetwork model. A set of an AirLoopHVAC and ZoneHVAC:EquipmentList nodes is a
subset of the AirflowNetwork:Distribution:Nodes.
– AirflowNetwork:Distribution:Component objects consist of Leak, LeakageRatio,
Duct, ConstantPressureDrop, Fan, Coil, TerminalUnit, OutdoorAirFlow and
ReliefAirFlow. The components provide a relationship between pressure and airflow. The
1158 CHAPTER 1. INPUT-OUTPUT REFERENCE
Leak and Leakage components can be used to simulate supply and/or return leaks in an air
distribution system. The Duct and ConstantPressureDrop components can be used to
deliver forced air into conditioned spaces. The components Fan, Coil, and TerminalUnit
reference normal EnergyPlus objects. OutdoorAirFlow, and ReliefAirFlow specify the
outdoor air flow rate set by the Controller:OutdoorAir object in the model. The Airflow
Network model gets information from these objects to perform an airflow network simulation.
– AirflowNetwork:Distribution:Linkage object represents a connection between two
node objects and an AirflowNetwork component. The node objects can be an Air-
flowNetwork:Distribution:Node, AirflowNetwork:MultiZone:ExternalNode or AirflowNet-
work:MultiZone:Zone.
Figure 1.111: Relationships among AirflowNetwork objects (right-hand side) and between Air-
flowNetwork objects and regular EnergyPlus objects. An arrow from object A to object B means
that A references B.
1160 CHAPTER 1. INPUT-OUTPUT REFERENCE
distribution seen by the exterior windows? (2) Are the exterior windows open or closed, and if open,
how far are they open? (3) Are the interior doors open or closed? (4) What are the air temperature
differences between zones and between zones and the outdoor air (which affect buoyancy flows)?
Figure 1.112: Plan view of a simple air flow network showing a possible air flow pattern in which
all of the windows and doors are open.
Figure 1.112 shows a possible air flow pattern in which all of the windows and doors are
open. Associated with the external nodes are wind pressure coefficient distributions as a
function of wind direction that are input using two AirflowNetwork:MultiZone:Wind Pres-
sure Coefficient objects. The nature of the air flows through the windows and doors
is specified using AirflowNetwork:MultiZone:Component:DetailedOpening and AirflowNet-
work:MultiZone:Component:SimpleOpening objects. The Airflow Network model calculates the
flows each system timestep depending on various factors, including wind direction and speed, size
and vertical position of openings, outdoor air temperature, and zone air temperatures.
– AirflowNetwork_MultiZone_House.idf
– AirflowNetwork_MultiZone_House_OvercoolDehumid.idf
– AirflowNetwork_MultiZone_House_TwoSpeed.idf
– AirflowNetwork_MultiZone_LocalNode.idf
– AirflowNetwork_MultiZone_SmallOffice.idf
– AirflowNetwork_MultiZone_SmallOffice_CoilHXAssistedDX.idf
– AirflowNetwork_MultiZone_SmallOffice_GenericContam.idf
– AirflowNetwork_MultiZone_SmallOffice_HeatRecoveryHXSL.idf
– AirflowNetwork_MultiZone_SmallOffice_VAV.idf
– AirflowNetwork_MultiZone_HorizontalOpening.idf
– AirflowNetwor_PressureControl.idf
– CrossVent_1Zone_AirflowNetwork.idf
– CrossVent_1Zone_AirflowNetwork_with2CrossflowJets.idf
– DisplacementVent_Nat_AirflowNetwork.idf
– DisplacementVent_Nat_AirflowNetwork_AdaptiveComfort.idf
– EMSAirflowNetworkOpeningControlByHumidity.idf
– HybridVentilationControl.idf
– RoomAirflowNetwork.idf
1.27.4.1 Can Do
12. When duct leakage is modeled and the HVAC system is on, interzone airflow or infiltration/ex-
filtration can occur due to changes in zone pressure.
13. Bi-directional flow through large openings. See discussion below under AirflowNet-
work:MultiZone:Component:DetailedOpening, AirflowNetwork:MultiZone:Component:HorizontalOpening,
and AirflowNetwork:MultiZone:Component:SimpleOpening.
14. Calculate air flows and pressures in ducts or other components of a forced air distribution
system.
15. Calculate zone loads when the supply air fan cycles on and off during a system timestep using
the CyclingFanAndCompressor fan operation mode (Fan:OnOff).
16. Determine the impact of zone exhaust fans on air flows, pressures, air temperatures/humidity
levels and energy consumption.
1. The model is restricted to using a constant volume or variable volume fan (Fan:ConstantVolume,
Fan:OnOff, and Fan:VariableVolume).
2. Air circulation and/or air temperature stratification within a thermal zone. For example, you
should not try to divide a high space, such as an atrium, into subzones separated by artificial
horizontal surfaces that have cracks or openings with the expectation that AirflowNetwork will
give you a realistic temperature in each subzone and/or a realistic air flow between subzones.
3. The model is restricted to eleven types of coils that can be in the air distribution system
(Coil:Cooling:DX:SingleSpeed, Coil:Heating:Fuel, Coil:Heating:Electric, Coil:Heating:DX:SingleSpeed,
Coil:Cooling:Water, Coil:Heating:Water, Coil:Cooling:Water:DetailedGeometry, Coil:Cooling:DX:TwoStag
Coil:Cooling:DX:MultiSpeed, Coil:Heating:DX:MultiSpeed, and Coil:Heating:Desuperheater).
4. The model is restricted to two types of air distribution equipment terminal units (AirTermi-
nal:SingleDuct:ConstantVolume:Reheat and AirTerminal:SingleDuct:VAV:Reheat).
5. Supply and return leaks are not allowed in an AirLoopHVAC. They can only be modeled in
the Zone Equipment portion of the air loop (i.e., return leaks may be modeled between the
zone return node and the zone mixer inlet or the zone mixer outlet and the zone equipment
loop outlet; and supply leaks may be modeled between the zone equipment loop inlet and the
AirLoopHVAC:ZoneSplitter inlet node or the AirLoopHVAC:ZoneSplitter outlet node and the
zone supply node).
6. An air distribution system must be located inside the building (i.e., the ducts must pass through
zones within the building).
7. Zone exhaust fans must be defined in ZoneHVAC:EquipmentConnections objects.
1.27.5 AirflowNetwork:SimulationControl
The basic run parameters for this model are defined in this unique object which has the following
input specifications:
1.27. GROUP – AIRFLOW NETWORK 1163
1.27.5.1 Inputs
Long Axis” (see description of these fields below). With this choice you do not have to enter any
of the following objects: AirflowNetwork:MultiZone: Wind Pressure Coefficient Array, AirflowNet-
work:MultiZone:ExternalNode and AirflowNetwork:MultiZone:WindPressureCoefficientValues.
1.27.5.1.12 Field: Ratio of Building Width Along Short Axis to Width Along
Long Axis
This is the aspect ratio of a rectangular footprint. It is given by the width of the footprint along its
short axis divided by the width along the long axis (see Figure 1.113). If the footprint is square, the
value of this field is 1.0. Used only if Wind Pressure Coefficient Type = SurfaceAverageCalculation.
The range for this input is > 0 to 1, with the default value being 1.
Figure 1.113: Footprint of a rectangular building showing variables used by the program to calculate
surface-average wind pressure coefficients. The angle a is the “Azimuth Angle of Long Axis of
Building.” wshort /wlong is the “Ratio of Building Width Along Short Axis to Width Along Long
Axis.”
1.27. GROUP – AIRFLOW NETWORK 1167
AirflowNetwork:SimulationControl ,
AirflowNetwork_All , !- Name
MultiZoneWithDistribution , !- AirflowNetwork Control
Input , !- Wind Pressure Coefficient Type
Every 30 Degrees , !- AirflowNetwork Wind Pressure Coefficient Array Name
OpeningHeight , !- Height Selection for Local Wind Speed Calculation
LowRise , !- Building Type
500, !- Maximum Number of Iterations {dimensionless}
ZeroNodePressures , !- Initialization Type
1.0E-05, !- Relative Airflow Convergence Tolerance {dimensionless}
1.0E-06, !- Absolute Airflow Convergence Tolerance {kg/s}
-0.5, !- Convergence Acceleration Limit {dimensionless}
0.0, !- Azimuth Angle of Long Axis of Building {deg}
1.0; !- Ratio of Building Width Along Short Axis to Width Along Long Axis
If the AirflowNetwork:SimulationControl object is not provided in an input file, the default input
object will be created by the program internally, as long as following conditions are satisfied:
AirflowNetwork:MultiZone data objects are used to calculate multizone airflows. This section de-
scribes the input requirements for the following objects:
– AirflowNetwork:MultiZone:Zone
AirflowNetwork:MultiZone data objects are used to calculate multizone airflows. This section de-
scribes the input requirements for the following objects:
– AirflowNetwork:MultiZone:Zone
– AirflowNetwork:MultiZone:Surface
– AirflowNetwork:MultiZone:Surface:Crack
– AirflowNetwork:MultiZone:ReferenceCrackConditions
– AirflowNetwork:MultiZone:Surface:EffectiveLeakageArea
– AirflowNetwork:MultiZone:Component:DetailedOpening
– AirflowNetwork:MultiZone:Component:SimpleOpening
– AirflowNetwork:MultiZone:Component:HorizontalOpening
– AirflowNetwork:MultiZone:Component:ZoneExhaustFan
– AirflowNetwork:MultiZone:ExternalNode
1168 CHAPTER 1. INPUT-OUTPUT REFERENCE
– AirflowNetwork:MultiZone:WindPressureCoefficientArray
– AirflowNetwork:MultiZone:WindPressureCoefficientValues
1.27.6 AirflowNetwork:MultiZone:Zone
This object allows control of natural ventilation through exterior and interior openings in
a zone, where “opening” is defined as an openable window or door. (Note that only
window, door or glass door subsurfaces in a zone that are specified using AirflowNet-
work:MultiZone:Component:DetailedOpening, AirflowNetwork:MultiZone:Component:HorizontalOpening
or AirflowNetwork:MultiZone:Component:SimpleOpening and have an associated AirflowNet-
work:MultiZone:Surface object are considered to be openings). The control will be applied in the
same way to all of the openings in the zone.
This object is required to perform Airflow Network calculations. Note that ventilation control for
all openings is provided at the zone level as default and individual ventilation control of a surface
opening can be used to override the zone-level control (see the AirflowNetwork:MultiZone:Surface
object description below).
The name of the EnergyPlus thermal zone corresponding to the AirflowNetwork zone.
CEN15251Adaptive: All of the zone’s operable windows and doors are opened if the operative
temperature is greater than the comfort temperature (central line) calculated from the CEN15251
adaptive comfort model and Venting Availability Schedule allows venting.
The name of a schedule of zone air temperature set points that controls the opening of windows and
doors in the thermal zone to provide natural ventilation. This setpoint is the temperature above
which all the openable windows and doors in the zone will be opened if the conditions described in
the previous field Ventilation Control Mode are met.
The Ventilation Control Zone Temperature Setpoint Schedule Name applies only to windows and
doors in the zone that are specified using AirflowNetwork:MultiZone:Component:DetailedOpening,
AirflowNetwork:MultiZone:Component:HorizontalOpening or AirflowNetwork:MultiZone:Component:SimpleOp
and have an associated AirflowNetwork:MultiZone:Surface object.
(The discussion under the field Window/Door Opening Factor in the AirflowNetwork:MultiZone:Surface
object describes how the actual opening area of a window or door in a particular timestep is deter-
mined.)
Modulation of Openings
The following five fields can be used to modulate the window/door openings when Ventilation Control
Mode = Temperature or Enthalpy. These fields determine a factor between 0 and 1 that multiplies
the opening factor of each window and door in the zone according to the control action shown
in Figure 1.115 for Ventilation Control Mode = Temperature and in Figure 1.116 for Ventilation
Control Mode = Enthalpy. Modulation of the openings can reduce the large temperature swings
that can occur if the windows/doors are open too far when they are venting, especially when there
is a large inside-outside temperature difference.
The modulation takes the following form when Ventilation Control Mode = Temperature:
if Tzone - Tout < = [Lower Value on Inside/Outside Temperature Difference for Modulating the
Venting Open Factor] then Multiplication factor = 1.0
if [Lower Value on Inside/Outside Temperature Difference for Modulating the Venting Open Factor]
< Tzone - Tout < [Upper Value on Inside/Outside Temperature Difference for Modulating the Venting
Open Factor] then Multiplication factor varies linearly from 1.0 to [Limit Value on Multiplier for
Modulating Venting Open Factor]
if Tzone - Tout > = [Upper Value on Inside/Outside Temperature Difference for Modulating
the Venting Open Factor] then Multiplication factor = [Limit Value on Multiplier for Modulating
Venting Open Factor]
One way of “tuning” the following modulation control parameters is to perform a sensitivity analysis
for winter and/or summer design days to determine what combination of values causes the biggest
reduction in zone air temperature fluctuations due to venting.
Note that the default values for the following fields are such that, if none of the fields are specified,
the default values are assigned.
See Figure 1.115 or Figure 1.116. This field applies only if Ventilation Control Mode = Temperature
or Enthalpy. This value may be from zero to 1.0, with the default being 0.0.
1170 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.27.6.5 Field: Indoor and Outdoor Temperature Difference Lower Limit For
Maximum Venting Open Factor
See Figure 1.115. This field applies only if Ventilation Control Mode = Temperature. This value
may be from zero to less than 100 ◦C, with the default being 0 ◦C. The value for this field must be
less than the value specified for the following field.
1.27.6.6 Field: Indoor and Outdoor Temperature Difference Upper Limit for
Minimun Venting Open Factor
See Figure 1.115. This field applies only if Ventilation Control Mode = Temperature. This value
must be greater than 0 ◦C, with the default being 100 ◦C. The value for this field must be greater
than the value specified for the previous field..
1.27.6.7 Field: Indoor and Outdoor Enthalpy Difference Lower Limit For Max-
imum Venting Open Factor
See Figure 1.116. This field applies only if Ventilation Control Mode = Enthalpy. This value may
be from zero to less than 300,000 J/kg, with the default being 0 J/kg. The value for this field must
be less than the value specified for the following field.
1.27.6.8 Field: Indoor and Outdoor Enthalpy Difference Upper Limit for Min-
imun Venting Open Factor
See Figure 1.116. This field applies only if Ventilation Control Mode = Enthalpy. This value must
be greater than zero, with the default being 300,000 J/kg. The value for this field must be greater
than the value specified for the previous field.
The name of a schedule that specifies when venting is available. A zero or negative schedule value
means venting is not allowed. A value greater than zero means venting can occur if other venting
control conditions (specified by Ventilation Control Mode and Vent Temperature Schedule Name)
are satisfied. This schedule name should not be confused with Vent Temperature Schedule Name.
If a Venting Availability Schedule Name is not specified, it is assumed that venting is always available.
Using Venting Availability Schedule allows you to turn off venting at certain times of the day (at
night, for example), of the week (on weekends, for example), or of the year (during the winter, for
example).
If used with Ventilation Control Mode = Constant, the ventilation rate is constant only when this
schedule allows venting; otherwise the ventilation rate is set to zero.
If Ventilation Control Mode = NoVent, this schedule has no effect.
1.27. GROUP – AIRFLOW NETWORK 1171
Specifies the type of single sided wind pressure coefficient algorithm to be used for the zone. This field
is optional and is only used if Wind Pressure Coefficient Type is set to SurfaceAverageCalculation.
The default is Standard and the two valid choices are:
Standard: A single wind pressure coefficient is applied to all openings in the zone, as calculated
using SurfaceAverageCalculation.
Advanced: EnergyPlus calculates modified wind pressure coefficients for the two openings in the
zone. This model is only valid for zones with two openings, both of which are on a single façade (i.e.
are coplanar). For zones with more than two openings, consider combining the openings into two.
The modified wind pressure coefficients account for wind direction and turbulence effects on single
sided ventilation rates. See the Engineering Reference for a detailed description of the Advanced
algorithm. When the Advanced algorithm is selected, the difference between the two modified wind
pressure coefficients are output to the .eio file.
This is the whole building width along the direction of the facade of this zone, or WF in Figure 1.114.
This field is used in the Single Sided Wind Pressure Coefficient Algorithm. This field is optional and
is only used if the Single Sided Wind Pressure Coefficient Algorithm is set to Advanced. The value
must be greater than 0.0 m, with the default being 10 m.
Figure 1.114: Footprint of a rectangular building showing WF , the “Façade Width”, used by the
Single Sided Wind Pressure Coefficient Algorithm.
1172 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.27.7 AirflowNetwork:MultiZone:Surface
The AirflowNetwork:MultiZone:Surface object specifies the properties of a surface “linkage” through
which air flows. This linkage is always associated with a building surface (wall, roof, floor, or a
ceiling) or subsurface (door, glass door, or window) with both faces exposed to air. The linkage
specifies two connected nodes: two zone nodes defined in AirflowNetwork:MultiZone:Zone objects
based on inside and outside face environment for an interior surface, or a zone node defined in
an AirflowNetwork:MultiZone:Zone object based on inside face environment and an external node
defined in an AirflowNetwork:MultiZone:ExternalNode object for an exterior surface. The associated
leakage component for this surface can be a crack (or surface effective leakage area) in an exterior
or interior heat transfer surface or subsurface, or an exterior or interior window, door or glass door
(heat transfer subsurface) that can be opened to allow air flow. The allowed surface air leakage
components are:
– AirflowNetwork:MultiZone:Surface:Crack
– AirflowNetwork:MultiZone:Surface:EffectiveLeakageArea
– AirflowNetwork:MultiZone:SpecifiedFlowRate
– AirflowNetwork:MultiZone:Component:DetailedOpening
– AirflowNetwork:MultiZone:Component:HorizontalOpening
– AirflowNetwork:MultiZone:Component:SimpleOpening
– AirflowNetwork:MultiZone:Component:ZoneExhaustFan
The three “opening” components are used to modulate openness based on required conditions.
The AirflowNetwork:MultiZone:Surface object allows a heat transfer surface or subsurface to have
one crack (or one surface effective leakage area object), or a subsurface (i.e., window, door or glass
door) to have one opening (detailed, simple, or horizontal).
An interior heat transfer surface (BuildingSurface:Detailed) whose surface name is used as
the input for the Outside Boundary Condition Object field is adiabatic and is not allowed
as an AirflowNetwork:MultiZone:Surface. A heat transfer surface defined in the BuildingSur-
face:Detailed:ExteriorNaturalVentedCavity is also not allowed.
When a non-rectangular subsurface is used, the model will automatically convert it into a rectan-
gular subsurface using equivalent width and height based on an entered choice from the Equivalent
Rectangle Method field or a default choice.
When an air boundary surface or subsurface is used (Construction:AirBoundary), all types of leakage
component are allowed except AirflowNetwork:MultiZone:Component:ZoneExhaustFan. The only
1.27. GROUP – AIRFLOW NETWORK 1175
allowed venting control type for an air boundary surface is Constant, and the venting schedule
is ignored (which means the opening is always fully open at the specified Window/Door Opening
Factor, or Crack Factor). EnergyManagementSystem:Actuator “AirFlow Network Window/Door
Opening” is available for special applications where control of the air boundary opening is required.
This is the name of the corresponding surface (wall, roof, ceiling, floor, window, door or glass door).
Information on this surface is used by the program as follows:
– For a linkage associated with an exterior heat transfer surface: air flow through this linkage is
between the outside environment and the thermal zone to which the surface belongs.
– For a linkage associated with an interior (i.e., interzone) heat transfer surface: air flow through
this linkage is between the thermal zones separated by the surface (i.e., the thermal zone
associated with the inside face environment and the thermal zone associated with the outside
face environment).
– This heat transfer surface determines the height of the linkage, which is used in calculating
buoyancy-related flow through the linkage.
– The surface may be an air boundary surface or subsurface (Construction:AirBoundary).
Note: It is possible to define an interzone surface twice in EnergyPlus, once in each of the zones
that the surface separates. Previously this was a requirement of EnergyPlus (prior to version 2.0),
but now it is optional and the user also has the option of only defining the surface once (EnergyPlus
defines the second surface automatically within the program). For each interzone surface, use only
one (of possible two) interzone surface names in the AirflowNetwork:MultiZone:Surface object for
“Surface Name.” Do not enter two AirflowNetwork:MultiZone:Surface objects corresponding to the
two possible interzone names. This would cause the air flow through the surface to be counted twice.
defined in the Zone Name field for this heat transfer surface must be the same zone name defined in
the ZoneHVAC:EquipmentConnections object (which references a ZoneHVAC:EquipmentList con-
taining the name of the corresponding zone exhaust fan).Otherwise an error message will be reported.
When this zone exhaust fan is operating for a simulation timestep, all surface-level controls described
below are ignored for that timestep.
Where
Q is the air mass flow (kg/s)
CQ is the air mass flow coefficient (kg/s @ 1 Pa)
CT is the reference condition temperature correction factor (dimensionless). See AirflowNet-
work:MultiZone:Surface:Crack object.
1.27. GROUP – AIRFLOW NETWORK 1177
and Venting Availability Schedule allows venting, where Hadjacent zone is the adjacent zone specific
enthalpy.
The name of a schedule of zone air temperature set points that controls the opening of a window
or door associated with this surface to provide natural ventilation. This setpoint is the temperature
above which this openable window or door will be opened if the conditions described in the previous
field Ventilation Control Mode are met.
The Ventilation Control Zone Temperature Setpoint Schedule applies only to a window or door at-
tached to this surface that is specified using AirflowNetwork:MultiZone:Component:DetailedOpening
or AirflowNetwork:MultiZone:Component:SimpleOpening.
(The discussion under the field Window/Door Opening Factor in this object describes how the actual
opening area of a window or door in a particular timestep is determined.)
Modulation of Openings
The following five fields can be used to modulate this window/door opening when Ventilation Control
Mode = Temperature or Enthalpy. These fields determine a factor between 0 and 1 that multiplies
the opening factor of this window or door according to the control action shown in Figure 1.115
for Ventilation Control Mode = Temperature and in Figure 1.116 for Ventilation Control Mode =
Enthalpy. Modulation of this opening can reduce the large temperature swings that can occur if
the window/door is open too far when it is venting, especially when there is a large inside-outside
temperature difference.
The modulation takes the following form when Ventilation Control Mode = Temperature:
if Tzone - Tout < = [Lower Value on Inside/Outside Temperature Difference for Modulating the
Venting Open Factor] then Multiplication factor = 1.0
if [Lower Value on Inside/Outside Temperature Difference for Modulating the Venting Open Factor]
< Tzone - Tout < [Upper Value on Inside/Outside Temperature Difference for Modulating the Venting
Open Factor] then Multiplication factor varies linearly from 1.0 to [Limit Value on Multiplier for
Modulating Venting Open Factor]
if Tzone - Tout > = [Upper Value on Inside/Outside Temperature Difference for Modulating the
Venting Open Factor] then Multiplication factor = [Limit Value on Multiplier for Modulating
Venting Open Factor]
One way of “tuning” the following modulation control parameters is to perform a sensitivity analysis
for winter and/or summer design days to determine what combination of values causes the biggest
reduction in zone air temperature fluctuations due to venting.
Note that the default values for the following fields are such that, if none of the fields are specified,
modulation will not occur.
See Figure 1.115 or Figure 1.116. This field applies only if Ventilation Control Mode = Temperature
or Enthalpy. This value may be from zero to 1.0, with the default being 0.0.
1.27. GROUP – AIRFLOW NETWORK 1179
1.27.7.8 Field: Indoor and Outdoor Temperature Difference Lower Limit For
Maximum Venting Open Factor
See Figure 1.115. This field applies only if Ventilation Control Mode = Temperature. This value
may be from zero to less than 100°C, with the default being 0°C. The value for this field must be
less than the value specified for the following field.
1.27.7.9 Field: Indoor and Outdoor Temperature Difference Upper Limit for
Minimun Venting Open Factor
See Figure 1.115. This field applies only if Ventilation Control Mode = Temperature. This value
must be greater than 0°C, with the default being 100°C. The value for this field must be greater
than the value specified for the previous field.
1.27.7.10 Field: Indoor and Outdoor Enthalpy Difference Lower Limit For Max-
imum Venting Open Factor
See Figure 1.116. This field applies only if Ventilation Control Mode = Enthalpy. This value may
be from zero to less than 300,000 J/kg, with the default being 0 J/kg. The value for this field must
be less than the value specified for the following field.
1.27.7.11 Field: Indoor and Outdoor Enthalpy Difference Upper Limit for Min-
imun Venting Open Factor
See Figure 1.116. This field applies only if Ventilation Control Mode = Enthalpy. This value must
be greater than zero, with the default being 300,000 J/kg. The value for this field must be greater
than the value specified for the previous field.
The name of a schedule that specifies when venting is available. A zero or negative schedule value
means venting is not allowed. A value greater than zero means venting can occur if other venting
control conditions (specified by Ventilation Control Mode and Vent Temperature Schedule Name)
are satisfied. This schedule name should not be confused with Vent Temperature Schedule Name.
If the surface is an air boundary (Construction:AirBoundary) then this field is ignored and venting
is always available.
If a Venting Availability Schedule Name is not specified, it is assumed that venting is always available.
Using Venting Availability Schedule allows you to turn off venting at certain times of the day (at
night, for example), week (on weekends, for example), or year (during the winter, for example).
If used with Ventilation Control Mode = Constant, the ventilation rate is constant only when this
schedule allows venting; otherwise the ventilation rate is set to zero.
If Ventilation Control Mode = NoVent, this schedule has no effect.
Note: In order to establish an airflow network, each AirflowNetwork:MultiZone:Zone object must
have at least two surfaces defined with AirflowNetwork:MultiZone:Surface objects, so that air can
flow from one zone into other zones (or to outdoors) through the network (air mass flow conserved).
1180 CHAPTER 1. INPUT-OUTPUT REFERENCE
In addition, for all AirflowNetwork:MultiZone:Surface objects facing the same Zone Name (ref. Build-
ingSurface:Detailed), at least two different environments must be defined for the other side of these
surfaces (e.g., an external node and an adjacent zone, two adjacent zones, or two external nodes).
This field is applied to a non-rectangular window or door. The equivalent rectangular surface has
the same area as the non-rectangular one. The valid choices are: PolygonHeight, BaseSurfaceAspec-
tRatio, and UserDefinedAspectRatio, with the default of PolygonHeight. When PolygonHeight is
entered, the equivalent width is equal to the area divided by the PolygonHeight for a non-horizontal
surface. When a surface is horizontal with the same height for all vertices, the model will automati-
cally switch a choice to BaseSurfaceAspectRatio if a base surface is rectangular, or UserDefinedAspec-
tRatio with the default value if a base surface is non-rectangular. When BaseSurfaceAspectRatio is
entered for a rectangular base surface, the equivalent height is equal to Square Root of Area divided
by the base surface aspect ratio. The equivalent width is equal to the equivalent height times the
base surface aspect ratio. When a base surface is non-rectangular, the model will automatically
switch the choice to PolygonHeight for a non-horizontal base surface, and UserDefinedAspectRatio
with the default value if a base surface is horizontal. When UserDefinedAspectRatio is entered,
the equivalent height is equal to Square Root of Area divided by UserDefinedAspectRatio. The
equivalent width is equal to the equivalent height times the user-defined aspect ratio.
This field applies only if Equivalent Rectangle Method = UserDefinedAspectRatio. This value must
be greater than zero, with the default being 1.0.
IDF examples are provided below:
AirflowNetwork:MultiZone:Surface ,
Zn001:Wall001 , !- Name of Associated Heat Transfer Surface
CR -1, !- Leakage Component Name
SFacade , !- External Node Name
1.0; !- Window/Door Opening Factor , or Crack Factor {dimensionless}
AirflowNetwork:MultiZone:Surface ,
Zn001:Wall001:Win001 , !- Name of Associated Heat Transfer Surface
WiOpen1 , !- Leakage Component Name
SFacade , !- External Node Name
0.5; !- Window/Door Opening Factor , or Crack Factor {dimensionless}
AirflowNetwork:MultiZone:Surface ,
Zn003:Wall003 , !- Name of Associated Heat Transfer Surface
Zone3 Exhaust Fan , !- Leakage Component Name
EFacade , !- External Node Name
1.0; !- Window/Door Opening Factor , or Crack Factor {dimensionless}
AirflowNetwork:MultiZone:Surface ,
Zn001:Wall001:Win002 , !- Name of Associated Heat Transfer Surface
1.27. GROUP – AIRFLOW NETWORK 1181
1.27.8 AirflowNetwork:MultiZone:ReferenceCrackConditions
This object specifies the reference conditions for temperature, humidity, and pressure which corre-
spond to the AirflowNetwork:MultiZone:Surface:Crack object.
1.27.8.1 Inputs
1.27.9 AirflowNetwork:MultiZone:Surface:Crack
This object specifies the properties of air flow through a crack and the associated measurement
conditions. The following power law form is used that gives air flow through the crack as a function
of the pressure difference across the crack:
Where
Q = air mass flow (kg/s)
CQ = air mass flow coefficient (kg/s-Pan @ 1 Pa)
CT = reference condition temperature correction factor (dimensionless)
∆P = pressure difference across crack (Pa)
n = air flow exponent (dimensionless)
n−1 h
ρo νo i2n−1
CT = (1.105)
ρ ν
where
ρ = Air density at the specific air temperature and humidity ratio conditions [kg/m3 ]
ν = Air kinetic viscosity at the specific air temperature condition [m2 /s]
ρo = Air density at the reference air conditions provided by the object AirflowNetwork:MultiZone:-
ReferenceCrackConditions specified in the field Reference Crack Conditions [kg/m3 ]
νo = Air kinetic viscosity at the reference air temperature provided by the object AirflowNetwork:-
MultiZone:ReferenceCrackConditions specified in the field Reference Crack Conditions [m2 /s]
Note: The correction factor shown above is use for this particular component as specified.
1.27.9.1 Inputs
1.27.10 AirflowNetwork:MultiZone:Surface:EffectiveLeakageArea
The effective leakage area (ELA) object is used to define surface air leakage. It has
five fields. The relationship between pressure and airflow may be expressed as:
p
ṁ = ELA ∗ Cd 2ρ ∗ (∆Pr )0.5−n (∆P )n (1.106)
where
ṁ = Air mass flow rate [kg/s]
ELA = Effective leakage area [m2 ]
ρ = Air density [kg/m3 ]
∆Pr = Reference pressure difference [Pa]
∆P = Pressure difference across this component [Pa]
Cd = Discharge coefficient [dimensionless]
n = Air mass flow exponent [dimensionless]
1.27.10.1 Inputs
Note: There are two common sets of reference conditions: Cd = 1.0 and ∆P = 4 Pa, or Cd =
0.6 and ∆P = 10 Pa
1.27.11 AirflowNetwork:MultiZone:SpecifiedFlowRate
The specified flow object is used to specify flow through a surface. The object has three fields and
will cause the mass flow ṁ to be set appropriately as
ṁ = F (1.107)
ṁ = ρQ (1.108)
when the volume flow rate Q is specified. A positive value of the flow directs the flow from node 1
of the linkage to node 2, and a negative value directs the flow from node 2 to node 1 of the linkage.
For surface linkages that are part of the building envelope, a positive value means flow from inside
to the outdoors (exfiltration) and a negative value is a flow from the outside to inside (infiltration).
1.27.11.1 Inputs
1.27.12 AirflowNetwork:MultiZone:Component:DetailedOpening
This object specifies the properties of air flow through windows and doors (window, door and glass
door heat transfer subsurfaces) when they are closed or open. The fields are similar to those for
AirflowNetwork:MultiZone:SurfaceCrack object when the window or door is closed, but additional
fields are required to describe the air flow characteristics when the window or door is open. These
additional fields include opening type, opening dimensions, degree of opening, and opening schedule.
The AirflowNetwork model assumes that open windows or doors are vertical or close to vertical;
for this reason they are called “Large Vertical Openings.” Such openings can have air flow moving
simultaneously in two different directions depending on stack effects and wind conditions (for exam-
ple, flow from inside to outside at the top of a window and from outside to inside at the bottom).
AirflowNetwork models such two-directional flow, but only for vertical openings.
It is assumed that the air flow through a window opening is unaffected by the presence of a shading
device such as a shade or blind on the window. Also, the calculation of conductive heat transfer and
solar gain through a window or door assumes that the window or door is closed.
The AirflowNetwork model does not have a model for bi-directional flow through large horizon-
tal openings in exterior surfaces. For this reason, AirflowNetwork:MultiZone:Component:-
DetailedOpening should not be used for exterior horizontal openings. The best modeling
technique in this case is to put an AirflowNetwork:MultiZone:Surface:Crack object in a horizontal
surface and use a large air mass flow coefficient. Crack flow is assumed to be uni-directional in any
given timestep (but can reverse flow direction from timestep to timestep).
For large horizontal openings in interior surfaces, see AirflowNetwork:MultiZone:Component:-
HorizontalOpening.
A subsurface multiplier may be used to represent multiple subsurfaces and calculates total air flow
when the subsurface (window, glassdoor, or door) is either closed or open. The total airflow across the
surface is equal to the airflow based on the surface geometry multiplied by the subsurface multiplier.
1.27.12.1 Inputs
Figure 1.117: Window (or door) showing geometrical factors associated with an opening through
which air flows.
1.27.13 AirflowNetwork:MultiZone:Component:HorizontalOpening
This object specifies the properties of air flow through windows, doors and glass doors (heat trans-
fer subsurfaces defined as a subset of FenestrationSurface:Detailed objects) when they are closed or
open. This AirflowNetwork model assumes that these openings are horizontal or close to horizontal
and are interzone surfaces. The second and third input fields are similar to those for AirflowNet-
work:MultiZone:Surface:Crack, when the window or door is closed, but additional information is
required to describe the air flow characteristics when the window or door is open. This additional
information is specified in the last two input fields. The airflow across the opening consists of two
types of flows: forced and buoyancy. The forced flow is caused by the pressure difference between
two zones, while the buoyancy flow only occurs when the air density in the upper zone is greater
than the air density in the lower zone. This opening also allows for the possibility of two-way flow
when forced and buoyancy flows co-exist. This object’s openness can also be modulated based on the
same opening factor control as an AirflowNetwork:MultiZone:Component:DetailedOpening object.
However, the opening factor is only applied to the subsurface width. The opening width is equal to
opening factor multiplied by the subsurface width.
A subsurface multiplier may be used to represent multiple subsurfaces and calculates total air flow
when the subsurface (window, glassdoor, or door) is either closed or open. The total airflow across the
surface is equal to the airflow based on the surface geometry multiplied by the subsurface multiplier.
1.27.13.1 Inputs
1.27.14 AirflowNetwork:MultiZone:Component:SimpleOpening
This object specifies the properties of air flow through windows, doors and glass doors (heat transfer
subsurfaces) when they are closed or open. The AirflowNetwork model assumes that open win-
dows or doors are vertical or close to vertical. The second and third fields are similar to those
for AirflowNetwork:MultiZone:Surface:Crack, when the window or door is closed, but additional
information is required to describe the air flow characteristics when the window or door is open.
This additional information is specified in the last two fields. Compared to the object AirflowNet-
work:MultiZone:Component:DetailedOpening, which requires more inputs at different opening fac-
tors, this object needs comparatively less inputs. For this reason it is called a simple opening. This
opening also allows for the possibility of two-way flow due to temperature and resulting density dif-
ferences. Therefore, it is possible to have a positive pressure difference at the top of the opening, and
a negative pressure difference at the bottom (or vice versa) when the neutral height is between the
bottom and top heights of the associated surface. This object’s openness can also be modulated based
on the same opening factor control as an AirflowNetwork:MultiZone:Component:DetailedOpening
object. However, the opening factor is only applied to the subsurface width. The opening width is
equal to opening factor multiplied by the subsurface width.
A subsurface multiplier may be used to represent multiple subsurfaces and calculates total air flow
when the subsurface (window, glassdoor, or door) is either closed or open. The total airflow across the
surface is equal to the airflow based on the surface geometry multiplied by the subsurface multiplier.
1.27.14.1 Inputs
1.27.15 AirflowNetwork:MultiZone:Component:ZoneExhaustFan
This object specifies the properties of air flow through an exterior heat transfer surface with a zone
exhaust fan. The zone exhaust fan turns on or off based on the availability schedule defined in the
corresponding Fan:ZoneExhaust object. When the exhaust fan mass flow rate is greater than zero,
the airflow network model treats this object as a constant volume fan. When the fan is off based on
the availability schedule, the model treats this object as a crack.
When the fan is on, the air mass flow rate modeled for the airflow network is based on the value
defined in the MaximumFlow Rate field of the Fan:ZoneExhaust object. The airflow direction is
from the corresponding zone to outdoors.
When the fan is off, the following power law form is used that gives air flow through the crack as a
function of the pressure difference across the crack:
Where
Q = air mass flow (kg/s)
CQ = air mass flow coefficient (kg/s-Pan @ 1 Pa)
CT = reference condition temperature correction factor (dimensionless)
∆P = pressure difference across crack (Pa)
n = air flow exponent (dimensionless)
n−1 h
ρo νo i2n−1
CT = (1.110)
ρ ν
where
ρ = Air density at the specific air temperature and humidity ratio conditions [kg/m3 ]
ν = Air kinetic viscosity at the specific air temperature condition [m2 /s]
1192 CHAPTER 1. INPUT-OUTPUT REFERENCE
ρo = Air density at the reference air conditions provided by the object AirflowNetwork:MultiZone:-
ReferenceCrackConditions specified in the field Reference Crack Conditions [kg/m3 ]
νo = Air kinetic viscosity at the reference air temperature provided by the object AirflowNetwork:-
MultiZone:ReferenceCrackConditions specified in the field Reference Crack Conditions [m2 /s]
Note: The correction factor shown above is used when the exhaust fan is off. The airflow direction
is based on the pressure difference between the zone and outdoors.
1.27.15.1 Inputs
1.27.15.1.2 Field: Air Mass Flow Coefficient When the Zone Exhaust Fan is Off
at Reference Conditions
The value of the air mass flow coefficient,CQ , in the crack air flow equation. It has units of kg/s at
1Pa. This value must be greater than zero. The value is used when the fan is off.
1.27.15.1.3 Field: Air Mass Flow Exponent When the Zone Exhaust Fan is Off
The value of the exponent, n, in the crack air flow equation. The valid range is 0.5 to 1.0, with the
default value being 0.65. The value is used when the fan is off.
AirflowNetwork:MultiZone:Component:ZoneExhaustFan ,
Zone3 Exhaust Fan , !- Name
0.01, !- Air Mass Flow Coefficient When the Zone Exhaust Fan is Off at Reference
Conditions {kg/s}
0.667; !- Air Mass Flow Exponent When the Zone Exhaust Fan is Off{dimensionless}
ReferenceCrackConditions ; !- Reference Crack Conditions
1.27.16 AirflowNetwork:MultiZone:ExternalNode
External nodes in the AirflowNetwork model define environmental conditions outside of the building.
These conditions include wind pressure coefficients that vary from façade to façade and can be highly
dependent on the building geometry.
1.27. GROUP – AIRFLOW NETWORK 1193
1.27.16.1 Inputs
1.27.16.1.4 Field: Symmetric Wind Pressure Coefficient Curve Specifies the sym-
metry of the above named curve. The default is No, meaning that the curve will be evaluated from
0 to 360 degrees. Specify Yes for a curve that is symmetric about zero and is evaluated only up to
180 degrees. For this type of curve, an angle of 270 degrees is passed to the curve as 90 degrees.
1.27.16.1.5 Field: Wind Angle Type Specifies which wind angle should be used to calcu-
late the wind pressure coefficient. The default is Absolute, meaning that the absolute wind direction
angle will be used. Specifying Relative means that the angle will be relative to the surface normal.
For a surface facing due east, the angle 0 corresponds to wind blowing perpendicular to and at the
surface with absolute direction 90 degrees, while 90 degrees corresponds to wind blowing parallel to
the surface from the right (facing outward) with an absolute direction of 180 degrees.
IDF examples are provided below:
AirflowNetwork:MultiZone:ExternalNode ,
NFacade , !- Name
1.524 , !- External Node Height {m}
NFacade_WPCValue; !- Wind Pressure Coefficient Curve Name
AirflowNetwork:MultiZone:ExternalNode ,
EFacade , !- Name
1.524 , !- External Node Height {m}
EFacade_WPCValue; !- Wind Pressure Coefficient Curve Name
AirflowNetwork:MultiZone:ExternalNode ,
SFacade , !- Name
1.524 , !- External Node Height {m}
SFacade_WPCValue; !- Wind Pressure Coefficient Curve Name
AirflowNetwork:MultiZone:ExternalNode ,
WFacade , !- Name
1.524 , !- External Node Height {m}
WFacade_WPCValue; !- Wind Pressure Coefficient Curve Name
1194 CHAPTER 1. INPUT-OUTPUT REFERENCE
AirflowNetwork:MultiZone:ExternalNode ,
Horizontal , !- Name
3.028 , !- External Node Height {m}
Horizontal_WPCValue ; !- Wind Pressure Coefficient Curve Name
1.27.17 AirflowNetwork:MultiZone:WindPressureCoefficientArray
The reference height and wind directions are first specified under the AirflowNetwork:MultiZone:WindPressureCo
object. The user may specify up to 36 different wind directions in ascending order. These are then
referenced by AirflowNetwork:MultiZone:WindPressureCoefficientValues objects defined for each
AirflowNetwork:MultiZone:ExternalNode.
The AirflowNetwork:MultiZone:WindPressureCoefficientArray object is unique and needs to be en-
tered only if Wind Pressure Coefficient Type = INPUT in the AirflowNetwork:SimulationControl
object. If Wind Pressure Coefficient Type = SurfaceAverageCalculation, this object is not required.
1.27.17.1 Inputs
1.27.18 AirflowNetwork:MultiZone:WindPressureCoefficientValues
This object specifies up to 36 wind pressure coefficients (WPCs) for an AirflowNetwork:MultiZone:ExternalNode.
These coefficients are defined for each of the wind directions defined in the unique AirflowNet-
work:MultiZone:WindPressureCoefficientArray object. In the air flow calculation, interpolation of
the specified WPC values is done for time-step values of wind direction.
AirflowNetwork:MultiZone:WindPressureCoefficientValues objects need to be entered only if the
Wind Pressure Coefficient Type = INPUT in the AirflowNetwork:SimulationControl object. If Wind
Pressure Coefficient Type = SurfaceAverageCalculation, this object is not required and is not used.
1.27.18.1 Inputs
AirflowNetwork Model:Wind Pressure Coefficients , EFACADE , -0.56 ,4.00E -002 ,0.48 ,0.60 ,0.48 ,4.00E
-002 , -0.56 , -0.56 , -0.42 , -0.37 , -0.42 , -0.56
AirflowNetwork Model:Wind Pressure Coefficients , SFACADE , -0.37 , -0.42 , -0.56 , -0.56 ,4.00E
-002 ,0.48 ,0.60 ,0.48 ,4.00E-002 , -0.56 , -0.56 , -0.42
AirflowNetwork Model:Wind Pressure Coefficients , WFACADE ,
-0.56 , -0.56 , -0.42 , -0.37 , -0.42 , -0.56 , -0.56 ,4.00E -002 ,0.48 ,0.60 ,0.48 ,4.00E -002
1.27.19 AirflowNetwork:OccupantVentilationControl
The AirflowNetwork:OccupantVentilationControl object provides control options with minimum
opening and closing time checks and opening and closing probability values. In general, the proba-
bility values could be a constant or a specific function. Due to lack of real data, two schedules are
selected to represent probability values. If real data are available, this object may be modified to
adopt new data.
1.27.19.1 Inputs
where
AirlowNetwork:OccupantVentilationControl ,
VentilationControl , !- Name
5.0, !- Minimum Opening Time
5.0, !- Minimum Opening Time
ComfortLowTempCurve , !- Thermal Comfort Low Temperature Curve Name
10.0, !- Thermal Comfort Temperature Boundary Point
ComfortHighTempCurve , !- Thermal Comfort High Temperature Curve Name
10.0, !- Maximum Threshold for Persons Dissatisfied PPD
Yes , !- Occupancy Check
OpeningProbabilitySch , !- Opening Probability Schedule Name
ClosingProbabilitySch; !- Closing Probability Schedule Name
1.27.20 AirflowNetwork:ZoneControl:PressureController
The AirflowNetwork:ZoneControl:PressureController object is used to control a zone to a specified
indoor level of pressure using the AirflowNetwork model. The specified pressure setpoint is used to
calculate the required zone exhaust fan flow rate in a controlled zone or relief air flow rate in an
AirLoop.
The object has a similar function as ZoneControl:Thermostat. When an AirLoop serves multiple
zones, the controlled zone will reach the specified setpoint, while other zones will not be controlled
precisely.
1.27.20.1 Inputs
1.27.22 AirflowNetwork:IntraZone:Node
This object allows users to input multiple nodes in a zone. A single object represent a node. If there
is only one node per zone, then use the AirflowNetwork:MultiZone:Zone input object. The zone node
is not defined in this object.
The name identifies the node for later reference and in the output listing. Each node should have a
unique name. This name can be referenced as AirflowNetworkNodeNames.
The name of a zone object, which is also defined in a AirflowNetwork:MultiZone:Zone object (zone
based).
1.27.23 AirflowNetwork:IntraZone:Linkage
The input object specifies a connection between two AirflowNetwork:IntraZone:Node objects and
an AiflowNetwork component defined elsewhere. The object also allow users to specify a connec-
tion between an AirflowNetwork:IntraZone:Node and an adjacent zone defined in an AirflowNet-
work:MultiZone:Zone object. This object provides flexibility to define a linkage either in the same
zone or in two different zones.
The name identifies the linkage for later reference and in the output listing. Each linkage should
have a unique name.
The input designates a node name where airflow starts. The node name should be defined in an
AirflowNetwork:IntraZone:Node object or an AirflowNetwork:MultiZone:Zone object.
The input designates a node name where airflow ends. The node name should be defined in an
AirflowNetwork:IntraZone:Node object or an AirflowNetwork:MultiZone:Zone object.
Note: One of Node 1 and Node 2 should be defined as an AirflowNetwork:IntraZone:Node object.
In other words, both nodes cannot be defined as AirflowNetwork:MultiZone:Zone object. This type
of connection should be defined as an AirflowNetwork:MultiZone:Surface object.
1.27. GROUP – AIRFLOW NETWORK 1201
The input designates an AirflowNetwork component name associated with the two nodes. The
component name should be one of the AirflowNetwork:MultiZone:Component object names. The
component is used for intrazone node connection only. If the next field is specified, the input of this
field could be a blank.
It should be pointed out that an AirflowNetwork:MultiZone:Surface object allows following five
AirflowNetwork:MultiZone:Component objects:
– AirflowNetwork:MultiZone:Component:DetailedOpening,
– AirflowNetwork:MultiZone:Component:SimpleOpening,
– AirflowNetwork:MultiZone:Surface:Crack,
– AirflowNetwork:MultiZone:Surface:EffectiveLeakageArea,
– AirflowNetwork:MultiZone:Component:HorizontalOpening
– AirflowNetwork:MultiZone:Surface:Crack,
– AirflowNetwork:MultiZone:Surface:EffectiveLeakageArea,
The input specifies an AirflowNetwork:MultiZone:Surface object name, when the nodes defined above
are not located in the same zone. The surface linkage will be connected by the above two nodes,
instead of zone nodes in normal definition. In other words, the connection defined in an AirflowNet-
work:MultiZone:Surface is removed. Instead, this new connection replaces the the connection spec-
ified before. A warning message is issued to let users be aware of the changes. Since each Air-
flowNetwork:MultiZone:Surface object has its own component defined in the Leakage Component
Name field, the input of the Component Name field in this object will be ignored.
An IDF example is provided below:
AirflowNetwork:IntraZone:Linkage ,
IntraZoneMiddleUpperLink , !- Name
LeftUpper , !- Node 1 Name
CentralUpper , !- Node 2 Name
CR -1; !- Component Name
AirflowNetwork:IntraZone:Linkage ,
IntraZoneLeftUpperLink ,
LeftUpper , !- Node 1 Name
EAST_ZONE_T , !- Node 2 Name
CR -1, !- Component Name
Surface_11_T; !- Surface Name
The previous sections of this AirflowNetwork model discussion describe input objects used for mul-
tizone airflow calculations. The following sections describe input objects used for air distribution
system simulations. These objects work when control option “MultiZone with Distribution” or “Mul-
tiZone with Distribution Only During Fan Operation” is defined in the AirflowNetwork Control field
in the AirflowNetwork:SimulationControl object.
The first section presents the input object for distribution system nodes. Although thermal zones
are required to perform air distribution system simulations, the thermal zones are already defined
1202 CHAPTER 1. INPUT-OUTPUT REFERENCE
in the multizone input section (described previously), so that there is no need to repeat the inputs
for thermal zones when modeling an air distribution system. The same is also true for surface air
leakage. This section has only one object: AirflowNetwork:Distribution:Node.
1.27.24 AirflowNetwork:Distribution:DuctViewFactors
The AirflowNetwork:Distribution:DuctViewFactors object is used to represent the information
needed for simplified surface-to-duct radiation heat transfer. View factors from each duct object to
each referenced surface are provided by the user. EnergyPlus calculates the heat gain to the duct
from the referenced surfaces. If the object is included, radiation is calculated for the referenced
duct; radiation is neglected of the object is omitted.
1.27.24.0.1 Field: Name of Linkage Name of the linkage object in which the view factors
are applied.
1.27.24.0.2 Field: Surface Exposure Fraction The fraction, range 0 to 1, of the duct
surface that is exposed to the zone for a partially buried duct (dimensionless).
1.27.24.0.3 Field: Surface Emittance The air duct surface emittance factor in the range
0 to 1 based on the material properties (dimensionless).
1.27.24.0.4 Field: Surface <#> Name This field specifies the name of the surface seen
by the duct.
1.27.24.0.5 Field: View Factor <#> This field specifies the view factor from the duct
to the surface.
This object is extensible, so additional pairs of the last two fields can be added to the end of this
object.
An IDF example is provided below:
AirflowNetwork:Distribution:DuctViewFactors ,
Main Link 1, !- Name of linkage
0.5, !- Surface exposure fraction
0.9, !- Duct surface emittance
Lshaped Zone:Wall 1, !- To Surface 1
0.2, !- View Factor 1
Lshaped Zone:Wall 2, !- To Surface 2
0.05, !- View Factor 2
Lshaped Zone:Wall 3, !- To Surface 3
0.5, !- View Factor 3
Lshaped Zone:Wall 4, !- To Surface 4
0.25; !- View Factor 4
1.27.25 AirflowNetwork:Distribution:Node
The AirflowNetwork:Distribution:Node object is used to represent air distribution system nodes for
the AirflowNetwork model. The EnergyPlus nodes defined in an AirLoopHVAC are a subset of the
nodes used to simulate the distribution system using the AirflowNetwork model. For example, the
1.27. GROUP – AIRFLOW NETWORK 1203
inlet node of a fan and the outlet node of a coil defined in an AirLoopHVAC must be defined as
nodes using the AirflowNetwork:Distribution:Node object. A set of EnergyPlus Zone Equipment
nodes is also a subset of the AirflowNetwork:Distribution:Nodes. For example, zone inlet and outlet
nodes must be defined as nodes using the AirflowNetwork:Distribution: Node object. In addition,
although mixers and splitters are defined as objects with inlet and outlet nodes within EnergyPlus,
the AirflowNetwork:Distribution:Node object treats mixers and splitters as single nodes. The node
objects are referenced by AirflowNetwork:Distribution:Linkage objects.
In summary, all nodes used to define an AirLoopHVAC (except splitters, mixers, and outdoor
air systems which are treated as single nodes) and its connections to a thermal zone must
be specified as AirflowNetwork:Distribution:Nodes. If distribution system air leaks are to be
modeled, additional AirflowNetwork:Distribution:Nodes may be defined along with AirflowNet-
work:Distribution:Components (e.g., leak or leak ratio) to define the air leakage characteristics.
Note: Supply and return leaks are not allowed in an AirLoopHVAC. They can only be modeled in
the Zone Equipment Loop (i.e., return leaks may be modeled between the zone return node and the
zone mixer inlet or the zone mixer outlet and the zone equipment loop outlet; and supply leaks may
be modeled between the zone equipment loop inlet and the AirLoopHVAC:ZoneSplitter inlet node
or the AirLoopHVAC:ZoneSplitter outlet node and the zone supply node).
1.27.25.1 Inputs
Note: Both the OutdoorAir:NodeList and OutdoorAir:Node node types represent a node to out-
door air conditions. Either one of these node types can be used to represent an external node
when an air-to-air heat exchanger is used to recover energy from the exhaust air stream as part of
an AirLoopHVAC:OutdoorAirSystem object. Node type OAMixerOutdoorAirStreamNode does not
represent an external node when an OutdoorAir:NodeList or OutdoorAir:Node object is specified.
If no exhaust heat recovery system (i.e., air-to-air heat exchanger) is specified in the AirLoopH-
VAC:OutdoorAirSystem, the node type OAMixerOutdoorAirStreamNode represents an external
node.
AirflowNetwork:Distribution:Node ,
SupplyMainNode , !- Name
, !- Component Name or Node Name
Other , !- Component Object Type or Node Type
3.0; !- Node Height {m}
AirflowNetwork:Distribution:Node ,
MainSplitterNode , !- Name
, !- Component Name or Node Name
AirLoopHVAC:ZoneSplitter , !- Component Object Type or Node Type
3.0; !- Node Height {m}
AirflowNetwork:Distribution:Node ,
MainSplitterNode , !- Name of Node
, !- Name of Associated EnergyPlus Node or Object
AirLoopHVAC:ZoneSplitter , !- EnergyPlus Object or Node Type
3.0; !- Node Height {m}
The next section describes AirflowNetwork Distribution Components, with 7 available types listed
below. All required fields for each component represent a relationship between pressure difference
and airflow. The components are referenced in AirflowNetwork:Distribution:Linkage objects.
– AirflowNetwork:Distribution:Component:Leak
– AirflowNetwork:Distribution:Component:LeakageRatio
1.27. GROUP – AIRFLOW NETWORK 1205
– AirflowNetwork:Distribution:Component:Duct
– AirflowNetwork:Distribution:Component:Fan
– AirflowNetwork:Distribution:Component:Coil
– AirflowNetwork:Distribution:Component:HeatExchanger
– AirflowNetwork:Distribution:Component:TerminalUnit
– AirflowNetwork:Distribution:Component:ConstantPressureDrop
1.27.26 AirflowNetwork:Distribution:Component:Leak
This component may be also called a power law component and is used to represent a supply or
return air leak in an air distribution system. Its relationship between pressure difference and airflow
may be expressed as:
ṁ = CT C(∆P )n (1.112)
where
ṁ = Air mass flow rate through the component [kg/s]
C = Air mass flow coefficient (kg/s at 1 Pa pressure difference)
∆P = Total pressure loss across the element [Pa]
n = Air mass flow exponent
CT = Temperature correction factor
n−1 h
ρo νo i2n−1
CT = (1.113)
ρ ν
where
ρ = Air density at the specific air temperature and humidity ratio conditions [kg/m3 ]
ν = Air kinetic viscosity at the specific air temperature condition [m2 /s]
ρo = Air density at air conditions of 20°C, 0 kg/kg and 101325 Pa [kg/m3 ]
νo = Air kinetic viscosity at an air temperature of 20°C [m2 /s]
Note: The correction factor shown above is use for this particular component as specified.
1.27.26.1 Inputs
AirflowNetwork:Distribution:Component:Leak ,
ZoneSupplyLeak , !- Name of Supply or Return Leak
0.01, !- Air Mass Flow Coefficient {kg/s}
0.65; !- Air Mass Flow Exponent {dimensionless}
1.27.27 AirflowNetwork:Distribution:Component:LeakageRatio
The leakage ratio component is generally used to define supply and return leaks with respect to a
constant fan flow. This object requires 5 inputs. The relationship between pressure and airflow may
be expressed as a power law element:
where
ρ = Air density [kg/m3 ]
∆P = Total pressure loss across the element [Pa]
n = Air mass flow exponent
Cequ = Equivalent air mass flow coefficient
where
ρ = Effective leakage ratio [dimensionless]
Qr = Maximum airflow rate [m3 /s]
∆Pr = Reference pressure difference [Pa]
n = Air mass flow exponent [dimensionless]
The above calculation is valid only for a HVAC system using a constant volume supply fan:
Fan:ConstantVolume or Fan:OnOff.
1.27.27.1 Inputs
AirflowNetwork:Distribution:Component:LeakageRatio ,
Zone1SupplyLeakELA , !- Name of Effective Leakage Ratio
0.043527 , !- Effective Leakage Ratio {dimensionless}
1.0, !- Maximum Flow Rate {m3/s}
20.0, !- Reference Pressure Difference {Pa}
0.65; !- Air Mass Flow Exponent {dimensionless}
1.27.28 AirflowNetwork:Distribution:Component:Duct
This object represents a duct component and requires 9 input fields, one alpha field and 8 numeric
fields. An additional two fields can be used to define the convection coefficients on the inner and
outer surfaces of the duct. The relationship between pressure and airflow across the component may
be expressed as (2001 ASHRAE Handbook of Fundamentals, Chapter 34):
s
2ρA2 ∆P
ṁ = P (1.116)
f L/D + Cd
where
ṁ = Mass flow rate of air through the component [kg/s]
r = Air density [kg/m3 ]
A = Cross sectional area [m2 ]
∆P = Total pressure loss across the component [Pa]
L = Duct length [m]
D = Hydraulic diameter [m]
Cd = Dynamic loss coefficient due to fitting [dimensionless]
f = Friction factor
The friction factor can be calculated using the nonlinear Colebrook equation (ASHRAE Handbook
of Fundamentals, 1997. p. 2.9, Eq. 29b)
1 D 9.3
√ = 1.44 + 2 ∗ log − 2 ∗ log 1 + √ (1.117)
f ε Re ∗ ε/D ∗ f
where
e = Surface roughness [m]
ρV D
Re = Reynolds number = µ
1.27.28.1 Inputs
4A
Dh = (1.118)
P
where
Dh = Hydraulic diameter [m]
A = Duct cross sectional area [m2 ]
P = Perimeter of cross section [m]
1.27.28.1.7 Field: Heat Transmittance Coefficient (U-Factor) for Duct Wall Con-
struction
This numeric field is defines the heat transmittance coefficient (U value, W/m2 -K) for the duct wall
construction. Film coefficents are calculated automatically, unless directly specified below.
AirflowNetwork:Distribution:Component:Duct ,
MainTruck1 , !- Name of Duct Component
3.0, !- Duct Length {m}
0.6, !- Hydraulic Diameter {m}
0.2827 , !- Cross Section Area {m2}
0.0009 , !- Surface Roughness {m}
0.01, !- Coefficient for local dynamic loss due to fitting {dimensionless}
0.772 , !- Heat Transmittance Coefficient (U-Factor) for Duct Wall
Construction {W/m2 -K}
0.0001; !- Overall moisture transmittance coefficient from air to air {kg/m2
}
1.27.29 AirflowNetwork:Distribution:Component:Fan
This component represents a constant or variable volume fan in the air distribution system (Air-
LoopHVAC). The air flow rate and air conditions (temperature and humidity) are obtained from the
associated Fan:ConstantVolume, Fan:OnOff, Fan:VariableVolume, or Fan:SystemModel object.
1.27.29.1 Inputs
AirflowNetwork:Distribution:Component:Fan ,
Supply Fan 1, !- Name of Constant Volume Fan
Fan:ConstantVolume; !- Supply fan type
1.27.30 AirflowNetwork:Distribution:Component:Coil
This component represents a cooling or heating coil. The main purpose for this object is to get
calculated values (air flow and temperature/humidity conditions) from the associated coil models.
1.27. GROUP – AIRFLOW NETWORK 1211
1.27.30.1 Inputs
– Coil:Cooling:DX:SingleSpeed
– Coil:Heating:Fuel
– Coil:Heating:Electric
– Coil:Heating:DX:SingleSpeed
– Coil:Cooling:Water
– Coil:Heating:Water
– Coil:Cooling:Water:DetailedGeometry
– Coil:Cooling:DX:TwoStageWithHumidityControlMode
– Coil:Cooling:DX:MultiSpeed
– Coil:Heating:DX:MultiSpeed
– Coil:Heating:Desuperheater
4A
Dh = (1.119)
P
where
Dh = Hydraulic diameter [m]
A = Duct cross section area [m2 ]
P = Perimeter of cross section [m]
For this component, the relationship between airflow and pressure is similar to the component Air-
flowNetwork:Distribution:Component:Duct. However, the model assumes very small surface rough-
ness (10−4 ) and no local dynamic loss due to fittings for this component. Therefore, this component
only requires two numerical fields. Heat and moisture exchange from surroundings is ignored.
1212 CHAPTER 1. INPUT-OUTPUT REFERENCE
Note: Make sure that the volumetric air flow rates for the fan, coils, and parent components (e.g.,
unitary system or furnace) are the same so that fan energy and air distribution system losses/gains
are properly calculated.
An IDF example is provided below:
AirflowNetwork:Distribution:Component:Coil ,
ACDXCoil 1, !- Name of Associated EnergyPlus Coil
Coil:Cooling:DX:SingleSpeed , !- EnergyPlus Coil Type
0.1, !- Air Path Length {m}
1.00; !- Air Path Hydraulic Diameter {m}
AirflowNetwork:Distribution:Component:Coil ,
HP Heating Coil 1, !- Name of Associated EnergyPlus Coil
Coil:Heating:DX:SingleSpeed , !- EnergyPlus Coil Type
0.1, !- Air Path Length {m}
1.00; !- Air Path Hydraulic Diameter {m}
1.27.31 AirflowNetwork:Distribution:Component:HeatExchanger
This component represents an air-to-air heat exchanger typically used in combination with a cool-
ing coil to enhance dehumidification or in an outside air system to recover energy from exhaust
air to pretreat incoming outdoor ventilation air. The cooling coils with enhanced dehumidifica-
tion are defined in the two objects CoilSystem:Cooling:DX:HeatExchangerAssisted and CoilSys-
tem:Cooling:Water:HeatExchangerAssisted using one of three heat exchanger objects specified be-
low. The exhaust air energy recovery system also has the same restriction using the one of three
heat exchanger objects. The main purpose for this object is to obtain calculated values (air flow
and temperature/humidity conditions) from the associated heat exchanger models for the airflow
network calculations.
1.27.31.1 Inputs
– HeatExchanger:AirToAir:FlatPlate
– HeatExchanger:AirToAir:SensibleAndLatent
– HeatExchanger:Desiccant:BalancedFlow
4A
Dh = (1.120)
P
where
Dh = Hydraulic diameter [m]
A = Duct cross section area [m2 ]
P = Perimeter of cross section [m]
For this component, the relationship between airflow and pressure is similar to the component Air-
flowNetwork:Distribution:Component:Duct. However, the model assumes very small surface rough-
ness (10−4 ) and no local dynamic loss due to fittings for this component. Therefore, this component
only requires two numerical fields. Heat and moisture exchange from surroundings are ignored.
Note: When a heat exchanger is used as a component of either CoilSystem:Cooling:DX:HeatExchangerAssisted
or CoilSystem:Cooling:Water:HeatExchangerAssisted, the heat exchanger acts as two components
in an air primary loop. For example, an air-to-air heat exchanger has a component connected
to the supply air side (equivalent to a supply coil) and a component connected to exhaust air
side (equivalent to an exhaust coil). The desiccant heat exchanger has a component connected to
regeneration air side (equivalent to a regeneration air coil) and a component connected to process
air side (equivalent to a process air coil). Therefore, each air-to-air heat exchanger used in this
configuration requires two linkage objects (instead of only one linkage object as required for other
AirflowNetwork components).
When a heat exchanger is used in an exhaust air energy recovery system (i.e., in an AirLoopH-
VAC:OutdoorAirSystem object to recover waste heat from exhaust air to pretreat incoming outdoor
ventilation air), the heat exchanger is treated as a single component. The AirflowNetwork model
only connects the two nodes associated with the incoming outdoor ventilation air, while the two
exhaust nodes are not defined as part of the AirflowNetwork model. Therefore, each heat exchanger
component used in an exhaust air energy recovery system has only one linkage object, similar to
AirflowNetwork coil components.
An IDF example is provided below:
AirflowNetwork:Distribution:Component:HeatExchanger ,
OA Heat Recovery 1, !- HeatExchanger Name
HeatExchanger:AirToAir:SensibleAndLatent , !- HeatExchanger Object Type
0.1, !- Air Path Length {m}
1.00; !- Air Path Hydraulic Diameter {m}
AirflowNetwork:Distribution:Component:HeatExchanger ,
Desiccant Heat Exchanger 1, !- HeatExchanger Name
HeatExchanger:Desiccant:BalancedFlow , !- HeatExchanger Object Type
0.1, !- Air Path Length {m}
1.00; !- Air Path Hydraulic Diameter {m}
1.27.32 AirflowNetwork:Distribution:Component:TerminalUnit
This component represents a terminal unit for reheating the incoming supply air. The main purpose
is to get calculated values from the terminal unit models.
1214 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.27.32.1 Inputs
4A
Dh = (1.121)
P
where
Dh = Hydraulic diameter [m]
A = Duct cross section area [m2 ]
P = Perimeter of cross section [m]
It should be noted that the relationship for this component between airflow and pressure is simi-
lar to the component AirflowNetwork:Distribution:Component:Duct. However, the model assumes
very small surface roughness (10−4 ) and no local dynamic loss due to fittings for this component.
Therefore, this component only requires two numerical fields. Heat and moisture exchange from
surroundings is ignored.
Note: The AirflowNetwork:Distribution:Component:TerminalUnit object is used to represent an
AirTerminal:SingleDuct:ConstantVolume:Reheat or an AirTerminal:SingleDuct:VAV:Reheat object
in an AirflowNetwork simulation. The AirflowNetwork:Distribution:Component:TerminalUnit
should not be used to represent any other air terminal unit types. When the Zone-
HVAC:EquipmentList object specifies an Air:Terminal:SingleDuct:ConstantVolume:NoReheat
object, the AirflowNetwork:Distribution:Component:Duct object should be used instead.
The AirTerminal:SingleDuct:VAV:Reheat object has two components: a damper and a reheat
coil. When the AirTerminal:SingleDuct:VAV:Reheat type is used, two objects of AirflowNet-
work:Distribution:Linkage have to be used to make two links, one of which is a link to connect two
nodes for a damper, and the other is a link to connect two nodes for a reheat coil.
1.27. GROUP – AIRFLOW NETWORK 1215
When a VAV system is used with Supply Fan Object Type = Fan:VariableVolume in the Air-
flowNetwork:Distribution:Component:Fan object, the type of all terminals has to be AirTermi-
nal:SingleDuct:VAV:Reheat. The object of Air:Terminal:SingleDuct:ConstantVolume:NoReheat is
not allowed.
An IDF example is provided below:
AirflowNetwork:Distribution:Component:TerminalUnit ,
Reheat Zone 1, !- Name of Associated Energyplus Terminal Unit
AirTerminal:SingleDuct:ConstantVolume:Reheat , !- EnergyPlus Terminal Unit Type
0.1, !- Air Path Length {m}
0.44; !- Air Path Hydraulic Diameter {m}
1.27.33 AirflowNetwork:Distribution:Component:ConstantPressureDrop
This component represents a constant pressure drop component. It is generally used to simulate a
constant pressure drop filter. The mathematical equation may be written as:
∆P = const (1.122)
1.27.33.1 Inputs
AirflowNetwork:Distribution:Component:ConstantPressureDrop ,
SupplyCPDComp , ! Name of Constant Pressure Drop Component
1.0; ! Pressure Difference Across the Component [Pa]
1.27.34 AirflowNetwork:Distribution:Component:OutdoorAirFlow
The AirflowNetwork:Distribution:Component:OutdoorAirFlow object is used to allow the Air-
flowNetwork model to include the outdoor air flow rate in the airflow network. When the outdoor
air mass flow rate is greater than zero, the airflow network model treats this object as a constant
volume fan and the flow rate is provided by the Controller:OutdoorAir object. When there is no
outdoor air flow rate, the model treats this object as a crack and a power law is assumed.
1216 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.27.34.1 Inputs
1.27.34.1.3 Field: Air Mass Flow Coefficient When No Outdoor Air Flow at
Reference Conditions
The value of the air mass flow coefficient, CQ , in the crack air flow equation. It has units of kg/s
at 1Pa. This value must be greater than zero. The value is used when when the outdoor mass flow
rate is zero from the Controller:OutdoorAir object.
1.27.34.1.4 Field: Air Mass Flow Exponent When No Outdoor Air Flow
The value of the exponent, n, in the crack air flow equation. The valid range is 0.5 to 1.0, with
the default value being 0.65. The value is used when the outdoor mass flow rate is zero from the
Controller:OutdoorAir object.
AirflowNetwork:MultiZone:Component:OutdoorAirFlow ,
OAFlow , !- Name
OA Mixer 1, !- Outdoor Air Mixer Name
0.01, !- Air Mass Flow Coefficient When No Outdoor Air Flow at Reference
Conditions {kg/s}
0.667; !- Air Mass Flow Exponent When No Outdoor Air Flow {dimensionless}
AirflowNetwork:Distribution:Node ,
OA System Node , !- Name
, !- Component Name or Node Name
AirLoopHVAC:OutdoorAirSystem , !- Component Object Type or Node Type
3.0; !- Node Height {m}
AirflowNetwork:Distribution:Node ,
OA Inlet Node , !- Name
Outside Air Inlet Node , !- Component Name or Node Name
OAMixerOutdoorAirStreamNode , !- Component Object Type or Node Type
1.5; !- Node Height {m}
1.27. GROUP – AIRFLOW NETWORK 1217
AirflowNetwork:Distribution:Linkage ,
OASystemFanLink , !- Name
OA Inlet Node , !- Node 1 Name
OA System Node , !- Node 2 Name
OAFlow; !- Component Name
1.27.35 AirflowNetwork:Distribution:Component:ReliefAirFlow
The AirflowNetwork:Distribution:Component:ReliefAirFlow object is used to allow the AirflowNet-
work model to perform pressure control by varying the amount of relief air flow rate between 0 and
the flow rate specified by the Controller:OutdoorAir object. When the outdoor air mass flow rate is
greater than zero, the airflow network model treats this object as a constant volume fan and the flow
rate is varied to reach pressure control. When there is no outdoor air flow rate, the model treats
this object as a crack and a power law is assumed.
1.27.35.1 Inputs
1.27.35.1.3 Field: Air Mass Flow Coefficient When No Outdoor Air Flow at
Reference Conditions
The value of the air mass flow coefficient, CQ , in the crack air flow equation. It has units of kg/s at
1Pa. This value must be greater than zero. The value is used when the outdoor mass flow rate is
zero from the Controller:OutdoorAir object.
1.27.35.1.4 Field: Air Mass Flow Exponent When No Outdoor Air Flow
The value of the exponent, n, in the crack air flow equation. The valid range is 0.5 to 1.0, with
the default value being 0.65. The value is used when the outdoor mass flow rate is zero from the
Controller:OutdoorAir object.
AirflowNetwork:ZoneControl:PressureController ,
Pressure Controller1 , !- Name
EAST ZONE , !- Controlled Zone Name
AirflowNetwork:Distribution:Component:ReliefAirFlow , !- Control Object type
ReliefFlow , !- Control Name
PressureAvailSchedule , !- Pressure Control Availability Schedule Name
PressureSetpointSchedule ; !- Pressure Setpoint Schedule Name
AirflowNetwork:MultiZone:Component:ReliefAirFlow ,
ReliefFlow , !- Name
OA Mixer 1, !- Outdoor Air Mixer Name
0.01, !- Air Mass Flow Coefficient When No Outdoor Air Flow at
Reference Conditions {kg/s}
0.667; !- Air Mass Flow Exponent When No Outdoor Air Flow {dimensionless
}
AirflowNetwork:Distribution:Node ,
OA System Node , !- Name
, !- Component Name or Node Name
AirLoopHVAC:OutdoorAirSystem , !- Component Object Type or Node Type
3.0; !- Node Height {m}
AirflowNetwork:Distribution:Node ,
OA Inlet Node , !- Name
Outside Air Inlet Node , !- Component Name or Node Name
OAMixerOutdoorAirStreamNode , !- Component Object Type or Node Type
1.5; !- Node Height {m}
AirflowNetwork:Distribution:Linkage ,
OASystemFanLink , !- Name
OA System Node , !- Node 1 Name
OA Inlet Node , !- Node 2 Name
ReliefFlow; !- Component Name
1.27.36 AirflowNetwork:Distribution:Linkage
The AirflowNetwork:Distribution:Linkage represents a connection between two AirflowNet-
work:Distribution:Node objects and an AirflowNetwork component defined above. In addition, the
relative height from node height to linkage height for each node is required.
1.27.36.1 Inputs
AirflowNetwork:Distribution:Linkage ,
Main Link 1, !- Name of Linkage
EquipmentInletNode , !- Node 1 Name
SupplyMainNode , !- Node 2 Name
MainTruck1 , !- Component Name
Attic Zone; !- Thermal Zone Name
1.27.36.2 Outputs
The AirflowNetwork nodes in the following output variables includes zones defined in AirflowNet-
work:MultiZone:Zone objects, external nodes defined in AirflowNetwork:MultiZone:ExternalNode
objects, and nodes defined in AirflowNetwork:Distribution:Node objects.
The AirflowNetwork linkage used in following output variables includes surfaces defined in Air-
flowNetwork:MultiZone:Surface objects, and linkages defined in AirflowNetwork:Distribution:Linkage
objects. The surface linkages represent airflows through surface cracks or openings between two
zones or between a zone and outdoors. The distribution linkages represent airflows in an air
distribution system.
The following output variables are reported only when a Fan:OnOff object is used:
– HVAC,Average,AFN Surface Venting Window or Door Opening Factor at Previous Time Step
[]
– HVAC,Average,AFN Surface Opening Elapsed Time [min]
– HVAC,Average,AFN Surface Closing Elapsed Time [min]
– HVAC,Average,AFN Surface Opening Status at Previous Time Step []
– HVAC,Average,AFN Surface Opening Status []
– HVAC,Average,AFN Surface Opening Probability Status []
– HVAC,Average,AFN Surface Closing Probability Status []
The following are reported only when an integrated model of RoomAir and AirflowNet-
work is used:
In this case, the output represents the wind pressures for the five external nodes defined above.
1224 CHAPTER 1. INPUT-OUTPUT REFERENCE
This is the AirflowNetwork linkage average mass flow rate in kg/s in the direction from Node 2 to
Node 1 defined in the AirflowNetwork:MultiZone:Surface objects. This output is only available when
a Fan:OnOff object is used in the air distribution system. The average mass flow rate is weighted
by the system fan part-load ratio using the calculated air mass flow rates during the fan on and off
periods for the system timestep. The system fan part-load ratio is defined as the ratio of the air
distribution system mass flow rate (average for the simulation timestep) to the system design mass
flow rate.
1.27.36.2.14 AFN Linkage Node 1 to Node 2 Volume Flow Rate [m3 /s]
This is the AirflowNetwork linkage volume flow rate output in m3 /s in the direction from the Node
1 to Node 2. It is defined in the same manner as AFN Linkage Node 1 to Node 2 Mass Flow Rate.
When a Fan:OnOff object is used, the air volume flow rates reported for the AirflowNet-
work:Distribution:Linkage objects are the values when the fan is operating (ON). It is assumed that
the air volume flow rates when the fan is off are zero for the distribution system air linkage objects.
The air volume flow rates for the AirflowNetwork:MultiZone:Surface object are reported in different
output variables (below).
1.27.36.2.15 AFN Linkage Node 2 to Node 1 Volume Flow Rate [m3 /s]
This is the AirflowNetwork linkage volume flow rate output in m3 /s in the direction from Node 2 to
Node 1. It is defined in the same manner as AFN Linkage Node 2 to Node 1 Mass Flow Rate.
When a Fan:OnOff object is used, the air volume flow rates reported for the AirflowNet-
work:Distribution:Linkage objects are the values when the fan is operating (ON). It is assumed that
the air volume flow rates when the fan is off are zero for the distribution system air linkage objects.
The air volume flow rates for the AirflowNetwork:MultiZone:Surface object are reported in different
output variables (below).
1.27.36.2.16 AFN Linkage Node 1 to 2 Average Volume Flow Rate [m3 /s]
This is the AirflowNetwork linkage average volume flow rate in m3 /s in the direction from Node 1 to
Node 2 defined in the AirflowNetwork:MultiZone:Surface objects. This output is only available when
a Fan:OnOff object is used. The average volume flow rate is weighted by the system fan part-load
ratio using the calculated air volume flow rates during the fan on and off periods for the system
timestep.
Average surface volume flow rate = (Surface volume flow rate during on cycle * Part-load ratio) +
Surface volume flow rate during off cycle * (1.0 – Part-load ratio)
1.27.36.2.17 AFN Linkage Node 2 to 1 Average Volume Flow Rate [m3 /s]
This is the AirflowNetwork linkage average volume flow rate in m3 /s in the direction from Node 2 to
Node 1 defined in the AirflowNetwork:MultiZone:Surface objects. This output is only available when
a Fan:OnOff object is used. The average volume flow rate is weighted by the system fan part-load
ratio using the calculated air volume flow rates during the fan on and off periods for the system
timestep.
1226 CHAPTER 1. INPUT-OUTPUT REFERENCE
When modulation is in effect the value of the multiplier is between 0.0 and 1.0. When modulation
does not apply the value of the multiplier may be –1.0. When modulation applies but the surface
is not venting, the value is –1.0. This is summarized in the following table. In this table, “Zone”
means a thermal zone for which AirflowNetwork:MultiZone:Zone has been specified. See object
AirflowNetwork: MultiZone:Zone for definition of “Ventilation Control Mode.”
NoVent No -1.0
Ventilation Latent Gain Rate = (Ventilation Latent Gain Rate during on cycle * Run time fraction)
+ Ventilation Latent Gain Rate during off cycle * (1.0 – Run time fraction)
gain from Zone 3 with respect to Zone 1. The energy received from Zone 2 is considered as a sensible
loss, instead of a gain, because the air temperature in Zone 2 is lower than in Zone 1.
When a Fan:OnOff object is used, the reported value is weighted by the system run time fraction
using the calculated mixing sensible gain rate during the system on and off cycles for the reporting
period:
Mixing Sensible Gain Rate = (Mixing Sensible Gain Rate during on cycle * Run time fraction) +
Mixing Sensible Gain Rate during off cycle * (1.0 – Run time fraction)
1.27.36.2.51 AFN Zone Mixing Generic Air Contaminant Mass Flow Rate [kg/s]
This is a sum of mass flow rates from adjacent zones multiplied by the corresponding zone generic
contaminant concentration level to the receiving zone. When a Fan:OnOff object is used, the reported
value is weighted by the system fan part-load ratio using the mixing mass flow rate calculated during
the fan on and off periods for the simulation timestep.
1.27.36.2.52 AFN Zone Duct Leaked Air Sensible Heat Gain Rate [W]
This is the average sensible heat gain rate, in Watts, to a specific zone due to supply air leaks from
the forced air distribution system. This value is averaged over the reporting period. A sensible heat
gain occurs when duct air is warmer than zone air. It should be pointed out that when multiple
supply air leaks are present in a single zone, the output value is the summation of all the supply air
leak gains in this zone. When a Fan:OnOff object is used, the reported value is for the system on
cycle.
1234 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.27.36.2.53 AFN Zone Duct Leaked Air Sensible Heat Gain Energy [J]
This is the total sensible heat gain, in Joules, to a specific zone due to supply air leaks summed
over the reporting period. When a Fan:OnOff object is used, the reported value is for the system on
cycle.
1.27.36.2.54 AFN Zone Duct Leaked Air Sensible Heat Loss Rate [W]
This is the average sensible heat loss rate, in Watts, to a specific zone due to supply air leaks from
the forced air distribution system. This value is averaged over the reporting period. A sensible heat
loss occurs when duct air is cooler than zone air. It should be pointed out that when multiple supply
air leaks are present in this zone, the output value is the summation of all the supply air leak losses
in this zone. When a Fan:OnOff object is used, the reported value is for the system on cycle.
1.27.36.2.55 AFN Zone Duct Leaked Air Sensible Heat Loss Energy [J]
This is the total sensible heat loss, in Joules, to a specific zone due to supply air leaks summed over
the reporting period. When a Fan:OnOff object is used, the reported value is for the system on
cycle.
1.27.36.2.56 AFN Zone Duct Leaked Air Latent Heat Gain Rate [W]
This is the average latent heat gain rate, in Watts, to a specific zone due to supply air leaks from
the forced air distribution system for the reported time period. When a Fan:OnOff object is used,
the reported value is for the system on cycle.
1.27.36.2.57 AFN Zone Duct Leaked Air Latent Heat Gain Energy [J]
This is the total latent heat gain, in Joules, to a specific zone due to supply air leaks summed over
the reporting period. When a Fan:OnOff object is used, the reported value is for the system on
cycle.
1.27.36.2.58 AFN Zone Duct Leaked Air Latent Heat Loss Rate [W]
This is the average latent heat loss rate, in Watts, to a specific zone due to supply air leaks from the
forced air distribution system for the reported time period. When a Fan:OnOff object is used, the
reported value is for the system on cycle.
1.27.36.2.59 AFN Zone Duct Leaked Air Latent Heat Loss Energy [J]
This is the total latent heat loss, in Joules, to a specific zone due to supply air leaks summed over
the reporting period. When a Fan:OnOff object is used, the reported value is for the system on
cycle.
1.27.36.2.60 AFN Zone Duct Conduction Sensible Heat Gain Rate [W]
This is the average sensible heat gain rate, in Watts, of duct conduction to a specific zone where
the ducts are located. This value is averaged over the reporting period. A sensible heat gain occurs
when duct air is warmer than the zone air. It should be pointed out that when ducts are located in
different zones, the total duct conduction loss should be the summation of the duct conduction losses
in these zones. When a Fan:OnOff object is used, the reported value is for the system on cycle.
1.27. GROUP – AIRFLOW NETWORK 1235
1.27.36.2.61 AFN Zone Duct Conduction Sensible Heat Gain Energy [J]
This is the total sensible heat gain, in Joules, to a specific zone due to duct conduction summed
over the reporting period. When a Fan:OnOff object is used, the reported value is for the system on
cycle.
1.27.36.2.62 AFN Zone Duct Conduction Sensible Heat Loss Rate [W]
This is the average sensible heat loss rate, in Watts, of duct conduction to a specific zone where the
ducts are located. This value is averaged over the reporting period. A sensible heat loss occurs when
duct air is cooler than the zone air. When a Fan:OnOff object is used, the reported value is for the
system on cycle.
1.27.36.2.63 AFN Zone Duct Conduction Sensible Heat Loss Energy [J]
This is the total sensible heat loss, in Joules, to a specific zone due to duct conduction summed
over the reporting period. When a Fan:OnOff object is used, the reported value is for the system on
cycle.
1.27.36.2.64 AFN Zone Duct Diffusion Latent Heat Gain Rate [W]
This is the average latent heat gain rate, in Watts, of vapor diffusion through the walls of the air
distribution system to a specific zone where the ducts are located. This value is averaged over the
reporting period. When a Fan:OnOff object is used, the reported value is for the system on cycle.
1.27.36.2.65 AFN Zone Duct Diffusion Latent Heat Gain Energy [J]
This is the total latent heat gain, in Joules, to a specific zone due to duct vapor diffusion summed
over the reporting period. When a Fan:OnOff object is used, the reported value is for the system on
cycle.
1.27.36.2.66 AFN Zone Duct Diffusion Latent Heat Loss Rate [W]
This is the average latent heat loss rate, in Watts, of duct vapor diffusion to a specific zone where
the ducts are located. This value is averaged over the reporting period. When a Fan:OnOff object
is used, the reported value is for the system on cycle.
1.27.36.2.67 AFN Zone Duct Diffusion Latent Heat Loss Energy [J]
This is the total latent heat loss, in Joules, to a specific zone due to duct vapor diffusion summed
over the reporting period. When a Fan:OnOff object is used, the reported value is for the system on
cycle.
using the ventilation air change rate calculated during the fan on and off periods for the simulation
timestep.
1.27.36.2.87 AFN Zone Outdoor Air CO2 Mass Flow Rate [kg/s]
This is a sum of mass flow rates from outdoors multiplied by the outdoor carbon dioxide concentration
level to the receiving zone. When a Fan:OnOff object is used, the reported value is weighted by the
system fan part-load ratio using the outdoor mass flow rate calculated during the fan on and off
periods for the simulation timestep.
1.27.36.2.88 AFN Zone Outdoor Air Generic Air Contaminant Mass Flow Rate
[kg/s]
This is a sum of mass flow rates from outdoors multiplied by the outdoor generic air contaminant
concentration level to the receiving zone. When a Fan:OnOff object is used, the reported value is
weighted by the system fan part-load ratio using the outdoor mass flow rate calculated during the
fan on and off periods for the simulation timestep
1.27.36.2.91 AFN Zone Total Generic Air Contaminant Mass Flow Rate [kg/s]
This is a sum of mass flow rates from adjacent zones or outdoors multiplied by the generic contam-
inant concentration differences between the corresponding zone and the receiving zone.
The following output variables are reported only when an AirflowNetwork:OccupantVentilationControl
object is used:
door is forced to open when the opening status is 0. A value of 2 denotes that the status at the
previous time step will be kept.
These output variables represent the heat emitted to ambient from exfiltration in Watts. The
exfiltration rate is calculated by solving a mass flow balance on the zone airflow network including
infiltration, ventilation, outdoor air mixing, zone-to-zone mixing, and all of the zone inlet, exhaust,
and return nodes. The latent parts are determined by taking the difference between the total and
the sensible rate. Positive values indicate the zone injects heat to the environment, while negative
values indicate the building extracts heat from the environment.
The following Figure 1.120 “Air Loop/Zone Equipment Node Diagram” illustrates the connection
between the zone equipment and the air loop systems.
1244 CHAPTER 1. INPUT-OUTPUT REFERENCE
Each zone served by an HVAC system must have three additional statements to complete the
zone equipment specification. An ZoneHVAC:AirDistributionUnit allows equipment typically found
within the zone inlet ductwork (such as dampers, reheat coils, etc.) to be attached to the supply
air stream for a particular zone. A ZoneControl statement will allow the conditions in the zone to
be managed. Finally, a ZoneHVAC:EquipmentConnections statement describes all of the pertinent
information about the zone from an HVAC perspective. Each of these statements is described in
more detail below.
1.28.1 ZoneHVAC:AirDistributionUnit
The ZoneHVAC:AirDistributionUnit object gives further information on what air loop equipment
(air terminal units) will be serving a particular zone. The ZoneHVAC:AirDistributionUnit is the part
of the system that is supplied from a common main air handler simulated in the Air Loop Simulation
and includes the equipment that controls or tempers the air going to each individual zone according to
the desired thermostatic control. The current options for ZoneHVAC:AirDistributionUnit terminal
unit types are:
– AirTerminal:DualDuct:ConstantVolume
– AirTerminal:DualDuct:VAV
– AirTerminal:DualDuct:VAV:OutdoorAir
– AirTerminal:SingleDuct:ConstantVolume:Reheat
– AirTerminal:SingleDuct:VAV:Reheat
– AirTerminal:SingleDuct:VAV:NoReheat
– AirTerminal:SingleDuct:SeriesPIU:Reheat
1.28. GROUP - ZONE EQUIPMENT 1245
– AirTerminal:SingleDuct:ParallelPIU:Reheat
– AirTerminal:SingleDuct:ConstantVolume:FourPipeInduction
– AirTerminal:SingleDuct:VAV:Reheat:VariableSpeedFan
– AirTerminal:SingleDuct:VAV:HeatAndCool:Reheat
– AirTerminal:SingleDuct:VAV:HeatAndCool:NoReheat
– AirTerminal:SingleDuct:ConstantVolume:CooledBeam
– AirTerminal:SingleDuct:UserDefined
– AirTerminal:SingleDuct:Mixer
Connections between the air distribution unit, the supply air duct, and the zone are specified in the
input syntax for the air distribution unit and the AirLoopHVAC:ZoneSplitter. The input syntax
also explicitly defines an outlet identifier. This implies a connection to a zone through a NodeList
for zone inlets (see the ZoneHVAC:EquipmentConnections statement). Each air distribution unit
is essentially a combined component-controller. Since controls are normally based on the zone
thermostat, they can work in parallel or series in complex fashion. Each air distribution unit operates
to meet all or part of the remaining thermostat load as specified in ZoneHVAC:EquipmentList.
The Air Distribution unit also allows the user to specify leaks in the supply air duct system. These
inputs are used in the EnergyPlus Simplified Duct Leakage Model (SDLM). This model simulates
a specific configuration: supply leaks to a return plenum in a commercial VAV or CV system. The
system must have a constant static pressure setpoint. Within these limitations SDLM allows the
user to easily evaluate the energy penalty due to duct leakage.
1.28.1.1 Inputs
1.28.1.2 Outputs
– HVAC,Sum,Zone Air Terminal Sensible Heating Energy [J]
– HVAC,Sum,Zone Air Terminal Sensible Cooling Energy [J]
– HVAC,Average,Zone Air Terminal Sensible Heating Rate [W]
– HVAC,Average,Zone Air Terminal Sensible Cooling Rate [W]
– HVAC,Average,Zone Air Terminal Outdoor Air Volume Flow Rate [m3/s]
1.28.1.2.5 Zone Air Terminal Outdoor Air Volume Flow Rate [m3/s]
This output is the amount of outdoor air entering the zone. This is the average value over the
frequency being reported. The amount of outdoor air is defined as the terminal unit air volume
flow rate multiplied by the fraction of outdoor air entering the air loop’s outside air system.
Two example IDF excerpts (one with duct leakage, one without):
ZoneHVAC:AirDistributionUnit ,
SPACE1 -1 ATU , !- Air Distribution Unit Name
SPACE1 -1 In Node , !- Air Dist Unit Outlet Node Name
AIRTERMINAL:SINGLEDUCT:VAV:REHEAT , !- KEY --System Component Type 1
SPACE1 -1 VAV Reheat; !- Component Name 1
ZoneHVAC:AirDistributionUnit ,
1.28. GROUP - ZONE EQUIPMENT 1247
1.28.2 ZoneHVAC:EquipmentConnections
Finally, the ZoneHVAC:EquipmentConnections statement defines the remaining details about each
thermal zone from an HVAC perspective (besides the controls which were defined above). As with
other statements, the first two items in this object are the keyword and an identifying name which
links the zone back to its geometrical input, internal gains, etc. and other statements in the HVAC
section of the input. The next three items are names of lists (equipment, air inlet nodes, and air
exhaust nodes) that are described in more detail below. Note that if there are no air exhaust nodes
from the zone that field is left blank. And if there are no air inlet nodes, that field is left blank.
Finally, two node names are necessary to complete the zone-HVAC description. The first node is the
main air node for the zone upon which the air heat balance is performed. The other node(s) begins
the return air path(s) from the zone.
Note that all nodes mentioned in the ZoneHVAC:EquipmentConnections input must be
unique. That is, all nodes in all the ZoneHVAC:EquipmentConnections statements refer-
enced by the “Zone Air Inlet Nodes”, “Zone Air Exhaust Nodes”, “Zone Air Node Name” and
“Zone Return Air Node Name” cannot have any node name appearing more than once.
1.28.2.1 Inputs
and ventilators, and window air conditioners. For each such component attached to a zone there
should be a unique zone exhaust node acting as the inlet node to the component. If there is only
one node – its name can be put in this field. If there is more than one node, this must be the name
of a node list object (a node list object can also contain only one node name). If there are no air
exhaust nodes, this field should be blank.
1.28.2.1.7 Field: Zone Return Air Node 1 Flow Rate Fraction Schedule Name
The name of a schedule to specify the return air flow rate for the first return air node as a fraction
of the base return air. If the next field is blank, then the return air flow rate is the total supply inlet
flow rate to the zone less the total exhaust node flow rate from the zone multiplied by this schedule
name. If this field is left blank, the schedule defaults to 1.0 at all times.
1.28.2.1.8 Field: Zone Return Air Node 1 Flow Rate Basis Node or NodeList
Name
The name of a node or list of nodes (NodeList) that is used to calculate the return air flow rate for
the first return air node in this zone. The sum of the current flow rates for this node(s) multiplied
by the Zone Return Air Node 1 Flow Rate Fraction Schedule determines the return air flow rate.
If this field is blank, then the base return air flow rate is the total supply inlet flow rate to the
zone less the total exhaust node flow rate from the zone in the case of a single air loop serving this
zone. If there are multiple air loops serving this zone, the base return air flow rate is governed by
the corresponding supply inlet flow rate and the AirloopHVAC Design Return Air Flow Fraction of
Supply Air Flow.
An example of this statement in an IDF is:
ZoneHVAC:EquipmentConnections ,
SPACE3 -1, !- Zone Name
SPACE3 -1 Eq , !- List Name: Zone Equipment
SPACE3 -1 In Nodes , !- List Name: Zone Air Inlet Nodes
, !- List Name: Zone Air Exhaust Nodes
SPACE3 -1 Node , !- Zone Air Node Name
SPACE3 -1 Out Node; !- Zone Return Air Node or NodeList Name
The following HVAC equipment types are allowed as zone equipment. The component matrix shows
which coils and fans are allowed with which equipment models.
1.28. GROUP - ZONE EQUIPMENT 1249
Figure 1.121:
1250 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.28.3 ZoneHVAC:EquipmentList
The first list encountered in the ZoneHVAC:EquipmentConnections statement is the Zone-
HVAC:EquipmentList. This object lists all HVAC equipment serving the zone. Each item in the list
has four fields associated with it: Object Type, Name, Cooling Sequence and Heating or No-Load
Sequence The Object Type and Name identify the specific equipment object. Cooling Sequence and
Heating or No-Load Sequence specify the order of simulation for zones with more than one type of
HVAC equipment.
Note that a ZoneHVAC:AirDistributionUnit must be listed in this statement if there is a forced air
system serving the zone from an air loop.
1.28.3.1 Inputs
– SequentialLoad loads each piece of available equipment sequentially with the full remaining
load.
– UniformLoad evenly distributes the total load equally among all available components on the
equipment list for the current load type.
– UniformPLR evenly distributes the total load among all available components on the equipment
list for the current load type at a uniform part load ratio (PLR).
– SequentialUniformPLR determines how many of the available components are required to meet
the current load, then distributes the load at a uniform part load ratio (PLR).
1.28.3.1.3 Field Set (Zone Equipment: Object Type, Name, Cooling Sequence,
Heating or No-Load Sequence, Sequential Cooling Fraction Schedule, Sequential
Heating Fraction Schedule)
This set is used together in order to sequence the equipment for heating and cooling. The #1
sequence equipment will try to meet the entire demand with its capacity and then pass the results
on to the #2 and so on for both heating and cooling. This object is extensible, so additional groups
of the following four fields can be added to the end of this object.
Equipment is simulated in the order specified by Zone Equipment Cooling Sequence and Zone Equip-
ment Heating or No-Load Sequence, depending on the current thermostat request. For equipment
of similar type, assign sequence 1 to the first system intended to serve that type of load, assign
sequence 2 to the next system, and so on. For situations where one or more equipment types has
limited capacity or limited control capability, order the sequence so that the most controllable piece
of equipment runs last. For example, with a dedicated outdoor air system (DOAS), the air terminal
for the DOAS should be assigned Heating Sequence = 1 and Cooling Sequence = 1. Any other
equipment should be assigned sequence 2 or higher so that it will see the net load after the DOAS
air is added to the zone.
1.28. GROUP - ZONE EQUIPMENT 1251
Fan:ZoneExhaust
WaterHeater:HeatPump:PumpedCondenser
WaterHeater:HeatPump:WrappedCondenser
ZoneHVAC:AirDistributionUnit
ZoneHVAC:Baseboard:Convective:Electric
ZoneHVAC:Baseboard:Convective:Water
ZoneHVAC:Baseboard:RadiantConvective:Electric
ZoneHVAC:Baseboard:RadiantConvective:Water
ZoneHVAC:Baseboard:RadiantConvective:Steam
ZoneHVAC:Dehumidifier:DX
ZoneHVAC:EnergyRecoveryVentilator
ZoneHVAC:FourPipeFanCoil
ZoneHVAC:HighTemperatureRadiant
ZoneHVAC:IdealLoadsAirSystem
ZoneHVAC:LowTemperatureRadiant:ConstantFlow
ZoneHVAC:LowTemperatureRadiant:Electric
ZoneHVAC:LowTemperatureRadiant:VariableFlow
ZoneHVAC:OutdoorAirUnit
ZoneHVAC:PackagedTerminalAirConditioner
ZoneHVAC:PackagedTerminalHeatPump
ZoneHVAC:RefrigerationChillerSet
ZoneHVAC:UnitHeater
ZoneHVAC:UnitVentilator
ZoneHVAC:WindowAirConditioner
ZoneHVAC:WaterToAirHeatPump
ZoneHVAC:VentilatedSlab
ZoneHVAC:EquipmentList ,
Zone1Equipment , !- Name
SequentialLoad , !- Load Distribution Scheme
ZoneHVAC:AirDistributionUnit , !- Zone Equipment 1 Object Type
Zone1TermReheat , !- Zone Equipment 1 Name
1, !- Zone Equipment 1 Cooling Sequence
1, !- Zone Equipment 1 Heating or No -Load Sequence
, !- Zone Equipment 1 Sequential Cooling Fraction Schedule Name
; !- Zone Equipment 1 Sequential Heating Fraction Schedule Name
ZoneHVAC:EquipmentList ,
Zone1Equipment , !- Name
SequentialLoad , !- Load Distribution Scheme
ZoneHVAC:AirDistributionUnit , !- Zone Equipment 1 Object Type
Zone1TermReheat , !- Zone Equipment 1 Name
1, !- Zone Equipment 1 Cooling Sequence
1, !- Zone Equipment 1 Heating or No -Load Sequence
0.5, !- Zone Equipment 1 Sequential Cooling Fraction
0.5, !- Zone Equipment 1 Sequential Heating Fraction
ZoneHVAC:WaterToAirHeatPump , !- Zone Equipment 2 Object Type
Zone1WTAHP , !- Zone Equipment 2 Name
2, !- Zone Equipment 2 Cooling Sequence
2, !- Zone Equipment 2 Heating or No -Load Sequence
0.5, !- Zone Equipment 2 Sequential Cooling Fraction
0.5; !- Zone Equipment 2 Sequential Heating Fraction
1.29.1 AirTerminal:SingleDuct:ConstantVolume:Reheat
The AirTerminal:SingleDuct:ConstantVolume:Reheat or terminal reheat system is a constant volume
reheat system. The systems cooling capabilities are provided by way of cooling coil that supplies
cooling to the entire supply air volume. The cooling coil is controlled by a controller setpoint specified
for the cooling coil. Zone control is accomplished by heating (reheating) the airflow into each zone
as determined by the zone thermostat. Currently the reheat can be supplied by a electric, gas, or
hot water coil that tries to meet the zone demand.
1.29.1.1 Inputs
– Coil:Heating:Water
– Coil:Heating:Electric
– Coil:Heating:Fuel
– Coil:Heating:Steam
1.29.1.2 Outputs
– HVAC,Average,Zone Air Terminal Outdoor Air Volume Flow Rate [m3/s]
1.29.1.2.1 Zone Air Terminal Outdoor Air Volume Flow Rate [m3/s]
This output is the amount of outdoor air entering the zone. This is the average value over the
frequency being reported. The amount of outdoor air is defined as the terminal unit air volume flow
rate multiplied by the fraction of outdoor air entering the air loop’s outside air system.
An IDF example:
AirTerminal:SingleDuct:ConstantVolume:Reheat ,
Reheat Zone 1, !- Name of System
FanAndCoilAvailSched , !- Availability schedule for VAV System
Zone 1 Reheat Air Outlet Node , !- Unit Air Outlet Node
Zone 1 Reheat Air Inlet Node , !- Unit Air Inlet Node
0.59, !- Maximum air flow rate {m3/s}
COIL:Gas:Heating , !- Reheat Component Object
Reheat Coil Zone 1, !- Name of Reheat Component
0.0, !- Max Reheat Water Flow {m3/s}
0.0, !- Min Reheat Water Flow {m3/s}
0.001; !- Convergence Tolerance
1.29. GROUP – ZONE HVAC AIR LOOP TERMINAL UNITS 1255
1.29.2 AirTerminal:SingleDuct:ConstantVolume:NoReheat
The AirTerminal:SingleDuct:ConstantVolume:NoReheat object creates the capability of supplying
central system air directly to a zone without any zone level thermostat control. The supply air
temperature is controlled by the central system controller. It is typically used with a unitary system
and furnaces which controls the system supply temperature and flow rate with continuous or cycling
fan. When used without the Design Specification Outdoor Air Object Name, the terminal unit is
passive and accepts any flow rate supplied by the central system, but will never exceed the maximum
air flow rate.
This object allows the program to know what zone this branch of the air system is attached to,
and input fields for availability schedule, air inlet and outlet nodes, the maximum air flow rate, and
other two optional input fields. The air inlet node should be the same as one of the AirLoopH-
VAC:ZoneSplitter or AirLoopHVAC:SupplyPlenum component outlet nodes. The air outlet node
name should be same as zone air inlet node name and the air distribution unit air outlet node name.
The last two optional input fields: Design Specification Outdoor Air Object Name, and Per Person
Ventilation Rate Mode are used for modulating the outdoor air requirement of an air terminal unit
depending on the method.
1.29.2.1 Inputs
non-zero, then the outdoor air requirement will be computed based on either the current or design
occupancy as specified in the Per Person Ventilation Rate Mode input field below. At no time will
the supply air flow rate exceed the value for Maximum Air Flow Rate. The requested flow rate
may not be fully met if the system is operating with cycling fan. The volume flow rate is converted
to mass flow rate using the standard density of air at Pressure = 101325 Pa, Temperature = 20C,
and Humidity Ratio = 0.0. If this field is blank, then the terminal unit will not be controlled for
outdoor air flow. This field is optional.
1.29.2.2 Outputs
1.29.2.2.1 Zone Air Terminal Outdoor Air Volume Flow Rate [m3/s]
This output is the amount of outdoor air entering the zone. This is the average value over the
frequency being reported. The amount of outdoor air is defined as the terminal unit air volume flow
rate multiplied by the fraction of outdoor air entering the air loop’s outside air system.
An IDF example:
AirTerminal:SingleDuct:ConstantVolume:NoReheat ,
NoReheat Zone 1, !- Name of System
AlwaysOnFanAvailSched , !- Availability Schedule Name
Zone 1 Unit Air Inlet Node , !- Air Inlet Node Name
Zone 1 Unit Air Outlet Node , !- Air Outlet Node Name
0.60, !- Maximum Air Flow Rate {m3/s}
, !- Design Specification Outdoor Air Object Name
; !- Per Person Ventilation Rate Mode
1.29.3 AirTerminal:SingleDuct:VAV:Reheat
AirTerminal:SingleDuct:VAV:Reheat - Variable air volume (VAV) systems control the dry-bulb tem-
perature inside a zone by varying the supply air volume instead of the air temperature. At full
cooling the VAV damper is fully open supplying the specified maximum air flow rate. As the cooling
load decreases, the damper closes until it reaches the minimum stop specified by the zone minimum
air flow fraction. The zone minimum supply air flow can be further adjusted using scheduled fraction
values specified in the field Minimum Air Flow Turndown Schedule Name.
VAV systems can be used for interior or perimeter zones with a common fan system, air temperature
control, and reheating devices. The VAV concept may vary according to the VAV box locations,
air temperature controls and types of heating elements. Heating can usually be provided by use of
reheat coils or thermostatic baseboard.
1.29. GROUP – ZONE HVAC AIR LOOP TERMINAL UNITS 1257
1.29.3.1 Inputs
This field is autosizable and defaulted to autosize. The autosized flow fraction is calculated using
the maximum flow rate derived from the design outdoor air flow (including VRP adjustments) and
the Sizing:Zone input fields “Cooling Minimum Air Flow per Zone Floor Area”, “Cooling Minimum
Air Flow”, and “Cooling Minimum Air Flow Fraction”. If there is no sizing calculation the defaults
of 0.000762 cubic meters per second per square meter of zone floor area (0.15 cfm/ft2) and 0.2 are
used. The autosized flow fraction is calculated according to the ASHRAE Standard 62.1 Simplified
Procedure if the Sizing:System’s “System Outdoor Air Method” associated with this terminal is
set to Standard62.1SimplifiedProcedure, see the System Outdoor Air Method of the Sizing:System
object.
– Coil:Heating:Water
1.29. GROUP – ZONE HVAC AIR LOOP TERMINAL UNITS 1259
– Coil:Heating:Electric
– Coil:Heating:Fuel
– Coil:Heating:Steam
With Reverse and ReverseWithLimits (the default) action, as the heating load increases, the
unit starts at minimum air flow and minimum hot water flow. The hot water flow is increased until
it reaches maximum flow or the user-specified maximum reheat air temperature is reached, then the
air damper starts to open to meet the load. For Reverse the damper can open all the way. For
ReverseWithLimitss the damper can only partially open to a maximum flow rate given by the
following two fields. These options are used if the minimum air flow rate is not adequate to serve
the peak heating load. This is sometimes called the dual maximum control logic as illustrated in
following figure. For heating coil types other than the hot-water coil, e.g. electric, steam, and gas,
the reverse action works the same as the normal action – always keeping the air flow at the minimum
during heating.
The dual-max control currently applies to the AirTerminal:SingleDuct:VAV:Reheat objects with
reverse acting dampers and hot-water coils.
1.29.3.1.18 Field: Maximum Flow per Zone Floor Area During Reheat
This factor (m3 /s-m2 ) is multiplied by the zone area, to determine the maximum volume flow rate
(m3 /s) allowed during reheat operation (see detailed explanation above). This field is autosizable
and its default is autosize. If autosize is selected or the field is blank, the value is filled from the
similar inputs in Sizing:Zone. If there is no sizing calculation the value is set to 0.002032 m3 /s-m2
(0.4 cfm/ft2 ). If this field and the following field are entered, the greater of the two inputs is used.
This field and the following field are only used if Damper Heating Action = ReverseWithLimits.
AirTerminal:SingleDuct:VAV:Reheat ,
SPACE2 -1 VAV Reheat , !- Name of System
ReheatCoilAvailSched , !- Availability schedule for VAV System
SPACE2 -1 Zone Coil Air In Node , !- Damper Air Outlet Node
SPACE2 -1 ATU In Node , !- Unit Air Inlet Node
autosize , !- Maximum air flow rate {m3/s}
Constant , !- Zone Minimum Air Flow Input Method
0.3, !- Constant Minimum Air Flow Fraction
, !- Fixed Minimum Air Flow Rate
, !- Minimum Air Flow Fraction Schedule Name
COIL:Gas:Heating , !- Reheat Component Object
SPACE2 -1 Zone Coil , !- Name of Reheat Component
0.0, !- Max Reheat Water Flow {m3/s}
0.0, !- Min Reheat Water Flow {m3/s}
SPACE2 -1 In Node , !- Unit Air Outlet Node
0.001 , !- Convergence Tolerance
ReverseWithLimits , !- Damper Heating Action
, !- Maximum Flow per Zone Floor Area During Reheat
, !- Maximum Flow Fraction During Reheat
35.0, !- Maximum Reheat Air Temperature {C}
, !- Design Specification Outdoor Air Object Name
TurndownMinAirFlowSch ; !- Minimum Air Flow Turndown Schedule Name
DesignSpecification :OutdoorAir ,
ZoneMinOARequirements , !- Name
Sum , !- Outdoor Air Method
0.00472 , !- Outdoor Air Flow per Person {m3/s}
0.000508 , !- Outdoor Air Flow per Zone Floor Area {m3/s-m2}
, !- Outdoor Air Flow per Zone
, !- Outdoor Air Flow Air Changes per Hour
Min OARequirements Sched; !- Outdoor Air Flow Rate Fraction Schedule Name
Schedule:Compact ,
Min OARequirements Sched , !- Name
Any Number , !- Schedule Type Limits Name
Through: 12/31 , !- Field 1
For: Weekdays SummerDesignDay WinterDesignDay , !- Field 2
Until: 24:00 ,1.0 , !- Field 7
For: AllOtherDays , !- Field 9
Until: 24:00 ,0.25; !- Field 10
COIL:Heating:Fuel ,
SPACE1 -1 Zone Coil , !- Coil Name
1.29. GROUP – ZONE HVAC AIR LOOP TERMINAL UNITS 1263
Schedule:Compact ,
TurndownMinAirFlowSch , !- Name
Fraction , !- Schedule Type Limits Name
Through: 12/31 , !- Field 1
For: Weekdays , !- Field 2
Until: 7:00 ,0.50 , !- Field 3
Until: 17:00 ,0.75 , !- Field 4
Until: 24:00 ,0.50 , !- Field 5
For: SummerDesignDay WinterDesignDay , !- Field 6
Until: 24:00 ,1.0 , !- Field 7
For: Weekends Holidays CustomDay1 CustomDay2 , !- Field 8
Until: 24:00 ,0.25; !- Field 9
1.29.3.2 Outputs
1.29.3.2.3 Zone Air Terminal Outdoor Air Volume Flow Rate [m3/s]
This output is the amount of outdoor air entering the zone. This is the average value over the
frequency being reported. The amount of outdoor air is defined as the terminal unit air volume flow
rate multiplied by the fraction of outdoor air entering the air loop’s outside air system.
1.29.4 AirTerminal:SingleDuct:VAV:Reheat:VariableSpeedFan
The VAV terminal unit with variable-speed fan and reheat coil is an air system terminal unit con-
sisting of a variable speed fan in series with a heating coil. These units are usually employed in
underfloor air distribution (UFAD) systems where the air is supplied at low static pressure through
an underfloor plenum. The fan is used to control the flow of conditioned air that enters the space.
When the fan is off the plenum pressure drives the minimum air flow through the terminal unit. At
maximum cooling the fan runs at its maximum speed. At full heating the fan runs at its heating
1264 CHAPTER 1. INPUT-OUTPUT REFERENCE
maximum – usually less than the cooling maximum flow rate. Thus this unit has two separate
maximum flow rates – one for heating and one for cooling.
For cooling, control is maintained simply by varying the fan speed. For heating, the unit first tries
to meet the heating load by varying the heating coil output while keeping the air flow at minimum
(fan off). If this is not adequate the fan turns on and operates in variable flow mode up to the
heating maximum flow rate. The zone fan-off minimum supply air flow can be further adjusted
using scheduled fraction values specified in the field Minimum Air Flow Turndown Schedule Name.
This unit is modeled in EnergyPlus as a compound component – a variable speed fan and a heating
coil in series in the air stream. The unit is blow through – the fan is upstream of the heating coil.
1.29.4.1 Inputs
– Coil:Heating:Water
– Coil:Heating:Electric
– Coil:Heating:Fuel
– Coil:Heating:Steam
|Qunit,out − Qzoneload |
≤ ConvergenceTolerance (1.123)
Qzoneload
Coil:Heating:Water ,
SPACE2 -1 Zone Coil , !- Coil Name
ReheatCoilAvailSched , !- Availability Schedule Name
autosize , !- UA of the Coil {W/K}
autosize , !- Max Water Flow Rate of Coil {m3/s}
SPACE2 -1 Zone Coil Water In Node , !- Coil_Water_Inlet_Node
SPACE2 -1 Zone Coil Water Out Node , !- Coil_Water_Outlet_Node
SPACE2 -1 Zone Coil Air In Node , !- Coil_Air_Inlet_Node
SPACE2 -1 In Node; !- Coil_Air_Outlet_Node
Fan:VariableVolume ,
SPACE2 -1 Zone Fan , !- Fan Name
FanAvailSched , !- Availability Schedule Name
0.7, !- Fan Total Efficiency
125.0 , !- Delta Pressure {Pa}
autosize , !- Max Flow Rate {m3/s}
0.0, !- Min Flow Rate {m3/s}
0.9, !- Motor Efficiency
1.0, !- Motor In Airstream Fraction
0.00153028 , !- FanCoefficient 1
0.00520806 , !- FanCoefficient 2
1.1086242 , !- FanCoefficient 3
-.11635563 , !- FanCoefficient 4
0.000 , !- FanCoefficient 5
SPACE2 -1 ATU In Node , !- Fan_Inlet_Node
SPACE2 -1 Zone Coil AirIn Node; !- Fan_Outlet_Node
Schedule:Compact ,
TurndownMinAirFlowSch , !- Name
Fraction , !- Schedule Type Limits Name
Through: 12/31 , !- Field 1
For: Weekdays , !- Field 2
Until: 7:00 ,0.50 , !- Field 3
Until: 17:00 ,0.75 , !- Field 4
Until: 24:00 ,0.50 , !- Field 5
For: SummerDesignDay WinterDesignDay , !- Field 6
Until: 24:00 ,1.0 , !- Field 7
For: Weekends Holidays CustomDay1 CustomDay2 , !- Field 8
Until: 24:00 ,0.25; !- Field 9
1.29. GROUP – ZONE HVAC AIR LOOP TERMINAL UNITS 1267
1.29.4.2 Outputs
1.29.4.2.2 Zone Air Terminal Outdoor Air Volume Flow Rate [m3/s]
This output is the amount of outdoor air entering the zone. This is the average value over the
frequency being reported. The amount of outdoor air is defined as the terminal unit air volume flow
rate multiplied by the fraction of outdoor air entering the air loop’s outside air system.
1.29.5 AirTerminal:SingleDuct:VAV:HeatAndCool:Reheat
Variable air volume (VAV) systems typically control the dry-bulb temperature inside a zone
by varying the supply air volume instead of the supply air temperature (ref: AirTermi-
nal:SingleDuct:VAV:NoReheat). Reheat coils may be required to avoid overcooling (ref:
AirTerminal:SingleDuct:VAV:Reheat).
This terminal unit is slightly different from the AirTerminal:SingleDuct:VAV:Reheat terminal unit.
Both operate the same in cooling mode: the damper opens as needed to provide additional sensible
cooling to the zone. The difference between the two is in heating mode. For the Single Duct VAV
Reheat terminal unit, the air flow rate is reduced to the minimum value (max air flow rate x zone
minimum air flow fraction) when zone heating is required and the reheat coil output is modulated
to meet the zone heating load. The zone minimum supply air flow can be further adjusted using
scheduled fraction values specified in the field Minimum Air Flow Turndown Schedule Name. For
the AirTerminal:SingleDuct:VAV:HeatAndCool:Reheat terminal unit, the air flow rate in heating
mode is increased to meet higher zone heating loads (similar to what is done in cooling mode). If
additional heat is required (beyond what the terminal unit can provide with its damper fully open),
then the reheat coil is modulated as needed to meet the additional heating load.
This terminal unit model was originally developed and tested for use with the changeover-bypass
VAV unitary system.
1.29.5.1 Inputs
Figure 1.124: Single Duct VAV Heat and Cool Reheat Schematic
– Coil:Heating:Water
– Coil:Heating:Electric
– Coil:Heating:Fuel
– Coil:Heating:Steam
AirTerminal:SingleDuct:VAV:HeatAndCool:Reheat ,
Zone 1 VAV System , !- Name of System
FanAndCoilAvailSched , !- System Availability schedule
Zone 1 Reheat Air Inlet Node , !- DAMPER Air Outlet Node
Zone 1 VAV Inlet Node , !- UNIT Air Inlet Node
0.583 , !- Maximum air flow rate {m3/s}
0.25, !- Zone Minimum Air Flow Fraction
Coil:Heating:Electric , !- Reheat Component Object
Reheat Coil Zone 1, !- Name of Reheat Component
0.0, !- Max Reheat Water Flow {m3/s}
0.0, !- Min Reheat Water Flow {m3/s}
Zone 1 Reheat Air Outlet Node , !- UNIT Air Outlet Node
0.001; !- Convergence Tolerance
Coil:Heating:Electric ,
Reheat Coil Zone 1, !- Coil Name
FanAndCoilAvailSched , !- Availability Schedule Name
1.0, !- Efficiency of the Coil
3000.0 , !- Nominal Capacity of the Coil {W}
Zone 1 Reheat Air Inlet Node , !- Coil_Air_Inlet_Node
Zone 1 Reheat Air Outlet Node; !- Coil_Air_Outlet_Node
1.29.5.2 Outputs
1.29.5.2.2 Zone Air Terminal Outdoor Air Volume Flow Rate [m3/s]
This output is the amount of outdoor air entering the zone. This is the average value over the
frequency being reported. The amount of outdoor air is defined as the terminal unit air volume flow
rate multiplied by the fraction of outdoor air entering the air loop’s outside air system.
1.29.6 AirTerminal:SingleDuct:VAV:NoReheat
Variable air volume (VAV) systems control the dry-bulb temperature inside a zone by varying the
supply air volume instead of the air temperature. At full cooling the VAV damper is fully open
supplying the specified maximum air flow rate. As the cooling load decreases, the damper closes until
it reaches the minimum stop specified by the zone minimum air flow fraction. The zone minimum
supply air flow can be adjusted using scheduled fraction values specified in the field Minimum Air
Flow Turndown Schedule Name.
VAV systems can be used for interior or perimeter zones with a common fan system and air temper-
ature control. The VAV concept may vary according to the VAV box locations and air temperature
controls. Heating can be provided if necessary by use of baseboard.
1.29. GROUP – ZONE HVAC AIR LOOP TERMINAL UNITS 1271
1.29.6.1 Inputs
AirTerminal:SingleDuct:VAV:NoReheat ,
Zone 1 VAV System , !- Name
FanAndCoilAvailSched , !- Availability Schedule Name
Zone 1 Reheat Air Outlet Node , !- Air Outlet Node Name
Zone 1 Damper Inlet Node ,!- Air Inlet Node Name
0.47, !- Maximum Air Flow Rate {m3/s}
Constant , !- Zone Minimum Air Flow Input Method
0.3, !- Constant Minimum Air Flow Fraction
, !- Fixed Minimum Air Flow Rate
, !- Minimum Air Flow Fraction Schedule Name
1.29. GROUP – ZONE HVAC AIR LOOP TERMINAL UNITS 1273
DesignSpecification :OutdoorAir ,
ZoneOAData , !- Name
Sum , !- Outdoor Air Method
0.00236 , !- Outdoor Air Flow per Person {m3/s}
0.00305 , !- Outdoor Air Flow per Zone Floor Area {m3/s-m2}
, !- Outdoor Air Flow per Zone {m3/s}
, !- Outdoor Air Flow Air Changes per Hour
OARequirements Sched; !- Outdoor Air Flow Rate Fraction Schedule Name
Schedule:Compact ,
OARequirements Sched , !- Name
Any Number , !- Schedule Type Limits Name
Through: 12/31 , !- Field 1
For: Weekdays SummerDesignDay WinterDesignDay , !- Field 2
Until: 24:00 , 1.0, !- Field 4
For: AllOtherDays , !- Field 5
Until: 24:00 , 0.5; !- Field 7
Schedule:Compact ,
TurndownMinAirFlowSch , !- Name
Fraction , !- Schedule Type Limits Name
Through: 12/31 , !- Field 1
For: Weekdays , !- Field 2
Until: 7:00 ,0.50 , !- Field 3
Until: 17:00 ,0.75 , !- Field 4
Until: 24:00 ,0.50 , !- Field 5
For: SummerDesignDay WinterDesignDay , !- Field 6
Until: 24:00 ,1.0 , !- Field 7
For: Weekends Holidays CustomDay1 CustomDay2 , !- Field 8
Until: 24:00 ,0.25; !- Field 9
1.29.6.2 Outputs
1.29.6.2.2 Zone Air Terminal Outdoor Air Volume Flow Rate [m3/s]
This output is the amount of outdoor air entering the zone. This is the average value over the
frequency being reported. The amount of outdoor air is defined as the terminal unit air volume flow
rate multiplied by the fraction of outdoor air entering the air loop’s outside air system.
1.29.7 AirTerminal:SingleDuct:VAV:HeatAndCool:NoReheat
Variable air volume (VAV) systems typically control the dry-bulb temperature inside a zone
by varying the supply air volume instead of the supply air temperature (ref: AirTermi-
nal:SingleDuct:VAV:NoReheat). Reheat coils may be required to avoid overcooling (ref:
AirTerminal:SingleDuct:VAV:Reheat).
1274 CHAPTER 1. INPUT-OUTPUT REFERENCE
Figure 1.125: Single Duct VAV Heat and Cool NoReheat Schematic
1.29.7.1 Inputs
AirTerminal:SingleDuct:VAV:HeatAndCool:NoReheat ,
Zone 3 VAV System , !- Name of System
FanAndCoilAvailSched , !- System Availability schedule
Zone 3 Reheat Air Outlet Node , !- UNIT Air Outlet Node
Zone 3 VAV Inlet Node , !- UNIT Air Inlet Node
0.584 , !- Maximum air flow rate {m3/s}
0.25; !- Zone Minimum Air Flow Fraction
1.29.7.2 Outputs
1.29.7.2.2 Zone Air Terminal Outdoor Air Volume Flow Rate [m3/s]
This output is the amount of outdoor air entering the zone. This is the average value over the
frequency being reported. The amount of outdoor air is defined as the terminal unit air volume flow
rate multiplied by the fraction of outdoor air entering the air loop’s outside air system.
1276 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.29.8 AirTerminal:SingleDuct:SeriesPIU:Reheat
The series powered induction unit is an air system terminal unit that mixes varying amounts of
secondary (recirculated) air and primary (conditioned supply) air to produce a fixed flow of air to
a zone. The unit contains a small fan that acts to induce the secondary air and a heating coil for
heating the mixed secondary and primary air. The fan runs at a constant volume flow rate whenever
the unit is on (and the fan’s availability schedule is on or it is activated by an availability manager).
The fan is downstream of the primary and secondary air inlets. The variable mixing is accomplished
by a damper in the unit’s primary air supply inlet duct. This damper can move from fully open
(100% primary air. 0% secondary air) to a minimum stop that is specified in the input description.
At full cooling the damper will be fully open. At minimum cooling and for heating the damper will
be at the minimum stop and the secondary air flow will be at its maximum. During night cycle
operation, if the availability manager status is CycleOnZoneFansOnly, then the fan will run only
if there is a heating load. If the status is CycleOn, then the fan will run according to the normal
controls.
The EnergyPlus model of the series PIU terminal unit is composed of three components: a zone
mixer, a constant volume fan, and a heating coil (hot water, electric, or gas).
1.29.8.1 Inputs
– Coil:Heating:Water
– Coil:Heating:Electric
– Coil:Heating:Fuel
– Coil:Heating:Steam
In other words, the PIU may have a hot water, gas, electric or steam reheat coil.
AirTerminal:SingleDuct:SeriesPIU:Reheat ,
Zone 1 SPIU ATU , ! Name of air terminal unit
FanAndCoilAvailSched , ! Availability schedule for series PIU ATU
0.47, ! Total volume flow rate through ATU
0.47, ! Maximum primary air flow rate through terminal unit
0.3, ! Minimum primary air flow rate (fraction of max)
Zone 1 PIU Pri Air Inlet Node , ! Air Terminal unit supply air inlet node
Zone 1 PIU Sec Air Inlet Node , ! Air Terminal unit secondary air inlet node
Zone 1 PIU Air Outlet Node , ! Air Terminal unit outlet node
Zone 1 Reheat Air Inlet Node , ! Reheat coil air inlet node (fan outlet node)
Zone 1 PIU Mixer , ! Air terminal unit mixer name
Zone 1 PIU Fan , ! Air terminal unit fan name
COIL:Heating:Water , ! type of air terminal unit reheat coil
Reheat Coil Zone 1, ! name of air terminal unit reheat coil
1.29. GROUP – ZONE HVAC AIR LOOP TERMINAL UNITS 1279
1.29.8.2 Outputs
1.29.8.2.6 Zone Air Terminal Outdoor Air Volume Flow Rate [m3/s]
This output is the amount of outdoor air entering the zone. This is the average value over the
frequency being reported. The amount of outdoor air is defined as the terminal unit air volume flow
rate multiplied by the fraction of outdoor air entering the air loop’s outside air system.
1280 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.29.9 AirTerminal:SingleDuct:ParallelPIU:Reheat
The parallel powered induction unit is an air system terminal unit that mixes varying amounts of
secondary (recirculated) air and primary (conditioned supply) air to produce a variable total flow
of air to a zone. The unit contains a small fan that acts to induce the secondary air and a heating
coil for heating the mixed secondary and primary air. The secondary and primary air streams enter
the unit in parallel. The fan sits in the secondary air stream and runs only when the primary air
flow is below the Fan On Flow Fraction and the fan’s availability schedule is on or it is activated
by an availability manager. The primary air inlet contains a damper that can move from fully open
(maximum primary air) to a minimum stop (minimum primary air).
At full cooling load the primary air damper is fully open and the fan is off. The primary air flow is
at maximum and there is little or no secondary air flow. As the cooling load decreases, the primary
air damper gradually closes and the secondary air flow remains close to zero. At some point, usually
when the primary air flow has reached the minimum, the fan switches on and secondary air is
induced. The heating coil will switch on as needed to meet any heating demand. The Fan On Flow
Fraction field controls the fan operation; see this field description for more details.
The EnergyPlus model of the parallel PIU terminal unit is composed of three components: a constant
volume fan, a zone mixer, and a heating coil (hot water, electric, or gas).
1.29.9.1 Inputs
– Coil:Heating:Water
– Coil:Heating:Electric
– Coil:Heating:Fuel
– Coil:Heating:Steam
In other words, the PIU may have a hot water, gas, electric or steam reheat coil.
AirTerminal:SingleDuct:ParallelPIU:Reheat ,
Zone 3 PPIU ATU , ! Name of air terminal unit
FanAndCoilAvailSched , ! Availability schedule for series PIU ATU
0.47, ! Maximum primary air flow rate through terminal unit
0.375 , ! Maximum secondary air flow rate through the terminal unit
0.1, ! Minimum primary air flow rate (fraction of max)
0.1, ! fan on flow fraction
Zone 3 PIU Pri Air Inlet Node , ! Air Terminal unit supply air inlet node
Zone 3 PIU Sec Air Inlet Node , ! Air Terminal unit secondary air inlet node
Zone 3 PIU Air Outlet Node , ! Air Terminal unit outlet node
Zone 3 Reheat Air Inlet Node , ! Reheat coil air inlet node (fan outlet node)
Zone 3 PIU Mixer , ! Air terminal unit mixer name
Zone 3 PIU Fan , ! Air terminal unit fan name
Coil:Heating:Water , ! type of air terminal unit reheat coil
Reheat Coil Zone 3, ! name of air terminal unit reheat coil
0.0013 , ! Max Reheat Water Flow {Flow: m3/sec}
0.0, ! Min Reheat Water Flow {Flow: m3/sec}
0.001; ! Convergence tolerance
1.29.9.2 Outputs
1.29.9.2.6 Zone Air Terminal Outdoor Air Volume Flow Rate [m3/s]
This output is the amount of outdoor air entering the zone. This is the average value over the
frequency being reported. The amount of outdoor air is defined as the terminal unit air volume flow
rate multiplied by the fraction of outdoor air entering the air loop’s outside air system.
1.29.10 AirTerminal:SingleDuct:ConstantVolume:FourPipeInduction
The four pipe induction terminal unit provides local hot water heating or chilled water cooling of
induced zone air which then mixes with centrally conditioned supply air. An air conditioning system
consisting of these terminal units is effectively a mixed central air / local hydronic system. The
centrally conditioned air supplied to the induction terminal units is constant volume at quite high
pressure. The central air is discharged through a nozzle in the terminal unit, inducing a flow of room
air over a hydronic heating/cooling coil. The coil is connected either to a single inlet and outlet pipe
(2 pipe unit) or to 2 inlets and 2 outlets (4 pipe unit). The heated or cooled induced air mixes with
the centrally conditioned air before being discharged into the zone. The terminal units are usually
expected to do only sensible cooling – any dehumidification is done by the central air conditioning
system.
The EnergyPlus model of the four pipe induction terminal unit is a compound component consisting
of a hot water heating coil, a chilled water cooling coil, and an air mixer. The unit has two inlet air
streams: the centrally conditioned supply air and the induced air from the zone. The induced air
passes first through the heating coil, then through the cooling coil and finally through the mixer.
The central supply air goes directly into the mixer. The water flow through the hot or cold water coil
is varied to meet the zone air conditioning requirement. Note that EnergyPlus models the four pipe
induction terminal unit as having separate heating and cooling coils whereas real units have only a
single coil used for both heating and cooling. Note also that the four pipe induction unit model can
be used to model a two pipe unit by simply adjusting the heating and cooling coil schedules so that
the heating coil is off when the cooling coil is on and vice versa.
1.29. GROUP – ZONE HVAC AIR LOOP TERMINAL UNITS 1285
1.29.10.1 Inputs
– Coil:Heating:Water
In other words, the unit may have a hot water coil only.
– Coil:Cooling:Water
– Coil:Cooling:Water:DetailedGeometry
In other words, the unit must use only the water cooling coils.
AirTerminal:SingleDuct:ConstantVolume:FourPipeInduction ,
SPACE2 -1 FPIU , !- Name of System
ReheatCoilAvailSched , !- System Availability schedule
autosize , !- Maximum total air volume flow rate
1.0, !- Induction ratio
SPACE2 -1 ATU Supply Node , !- Terminal unit supply air inlet node
SPACE2 -1 ATU Induc Node , !- Terminal unit induced air inlet node
SPACE2 -1 In Node , !- Terminal unit air outlet node
COIL:Heating:Water , !- Heating coil object
SPACE2 -1 HW Coil , !- Heating coil name
autosize , !- Max hot water flow
0.0, !- Min hot water flow
0.001 , !- Heating Convergence Tolerance
COIL:Cooling:Water , !- Cooling coil object
SPACE2 -1 CW Coil , !- Cooling coil name
autosize , !- Max cold water flow
0.0, !- Min cold water flow
0.001 , !- Cooling Convergence Tolerance
SPACE2 -1 ATU Mixer; !- Zone mixer component name
COIL:Heating:Water ,
SPACE2 -1 HW Coil , !- Coil Name
ReheatCoilAvailSched , !- Availability Schedule Name
autosize , !- UA of the Coil {W/K}
autosize , !- Max Water Flow Rate of Coil {m3/s}
SPACE2 -1 HW Coil Water In Node , !- Coil_Water_Inlet_Node
SPACE2 -1 HW Coil Water Out Node , !- Coil_Water_Outlet_Node
SPACE2 -1 ATU Induc Node , !- Coil_Air_Inlet_Node
SPACE2 -1 HW Coil Air Out Node; !- Coil_Air_Outlet_Node
COIL:Cooling:Water ,
SPACE2 -1 CW Coil , !- Coil Name
CWCoilAvailSched , !- Availability Schedule
autosize , !- UA of the Coil
autosize , !- Max Water Flow Rate of Coil
, !- Leaving Relative Humidity of Coil
SPACE2 -1 CW Coil Water In Node , !- Coil_Water_Inlet_Node
SPACE2 -1 CW Coil Water Out Node , !- Coil_Water_Outlet_Node
SPACE2 -1 HW Coil Air Out Node , !- Coil_Air_Inlet_Node
SPACE2 -1 CW Coil Air Out Node; !- Coil_Air_Outlet_Node
AirLoopHVAC:ZoneMixer ,
SPACE2 -1 ATU Mixer , !- Mixer Name
SPACE2 -1 In Node , !- Outlet_Node
SPACE2 -1 ATU Supply Node , !- Inlet_Node_1
SPACE2 -1 CW Coil Air Out Node; !- Inlet_Node_2
1.29.10.2 Outputs
1.29.10.2.1 Zone Air Terminal Outdoor Air Volume Flow Rate [m3/s]
1288 CHAPTER 1. INPUT-OUTPUT REFERENCE
This output is the amount of outdoor air entering the zone. This is the average value over the
frequency being reported. The amount of outdoor air is defined as the terminal unit air volume flow
rate multiplied by the fraction of outdoor air entering the air loop’s outside air system.
1.29.11 AirTerminal:SingleDuct:ConstantVolume:FourPipeBeam
The four-pipe beam air terminal system is a mixed air-hydronic system. A central, single-duct
forced-air system that supplies conditioned air to the zones. Chilled water circulates through ceiling-
mounted fin-tube convector units to provide sensible cooling. Hot water circulates through the
same convectors to provide heating. Water flow rate through the beam unit is varied to meet
the zone sensible cooling or heating load. Any dehumidification is done by the central forced-
air system. Thermodynamically, the cooled beam system resembles the four-pipe induction unit
(AirTerminal:SingleDuct:ConstantVolume:FourPipeInduction).
To model a typical four-pipe beam system the user will need to define a conventional central constant
volume forced air system in order to deliver primary air to the beam. This central system (usually)
provides outside air for ventilation. Primary air is normally delivered at a fixed temperature but
could be reset by a schedule or using an outdoor air reset setpoint manager. On the supply side of
this air loop there will be the usual central conditioning equipment: outside air mixer, fan, heating
and cooling coil. On the zone equipment (demand) side of the loop, the four-pipe beams will be
represented as air terminal units. Because the four-pipe beam can provide heating the system can
avoid over-cooling zones during times of low load with cool primary air temperatures, similar to the
action of a reheat coil in a VAV terminal. Therefore, it is not necessary to have additional zone
equipment (such as baseboard heaters) to handle heating (or reheating) loads.
Although the four-pipe beam equipment in a zone is treated by the program as a single terminal
unit, the actual installation will often have multiple beam units in each zone. In this model, it is
only the total length of all the beams and the total air flow of all the units that are described, not
the number of individual beam units.
If needed, the program (in its sizing calculation for the system) determines the total length of beams
and primary supply air flow that is needed to meet the zone design loads. The four pipe beam air
terminal sizing differs from other air terminals in that the primary supply air flow rate is sized using
the entire performance model and the flow rate is not the direct result from the Sizing:Zone and
Sizing:System calculations. The flow rates will be somewhere between what an air terminal would
size out using VentilationRequirement or Sensible in the Sizing:System object (either setting can be
used).
The model includes two different types of inputs for flow rates, “design” and “rated … per-meter.”
The design values are the actual sizes of the flow rates as viewed from the zone and central air
handler (but before zone multipliers). The design values include all the individual beam units and
their lengths. The rated per-meter values are used to characterize product performance at nominal
rating conditions in such a way that it can be scaled to match the size of a zone. The performance
characteristics at the rating point are not fixed in the program and can be entered by the user when
they differ from default values. The rated per meter values are normalized by the linear dimensions
of the beam and are generally obtained from product catalog data by dividing by the length of the
beam. The rated primary air flow rate is assumed to be for sea level conditions while the design
primary air flow rate is modeled for the location elevation above sea level.
1.29. GROUP – ZONE HVAC AIR LOOP TERMINAL UNITS 1289
1.29.11.1 Inputs
1.29.11.1.13 Field: Rated Primary Air Flow Rate per Beam Length (m3/s-m)
This is the primary air volume flow rate at rating conditions divided by the length of the beam,
in m3/s-m. This “catalog” value for volume flow rate input is converted to a mass flow rate using
standard air density at sea level. This value will be used for sizing the design primary air volume
flow rate if the total beam length is not also autosized. The default is 0.035 m3/s-m.
1.29.11.1.14 Field: Beam Rated Cooling Capacity per Beam Length (W/m)
This is the beam cooling capacity at rating conditions divided by the length of the beam, in W/m.
This is only the cooling contributed by the chilled water circulating through the convector and is
separate from any cooling (or heating) that may also be provided by the primary air. The default is
600 W/m.
1.29.11.1.15 Field: Beam Rated Cooling Room Air Chilled Water Temperature
Difference (Delta C)
This input defines the value of the temperature difference between the room air and entering chilled
water at the rating point, in delta Celsius. This “catalog” input helps to define the operating
conditions that correspond with Rated Beam Cooling Capacity per Meter. It is used to normalize
the independent variable in the input field called Beam Cooling Capacity Temperature Difference
Modification Factor Curve or Table Name. The default is 10.0 delta C.
1.29.11.1.16 Field: Beam Rated Chilled Water Volume Flow Rate per Beam
Length (m3/s-m)
This input defines the value of the chilled water flow rate per meter length of beam at the rating
point, in m3/s-m. This input helps to define the operating conditions that correspond with Rated
Beam Cooling Capacity per Meter. It is used to normalize the independent variable in the input
field called Beam Cooling Capacity Chilled Water Flow Modification Factor Curve or Table Name.
The default is 0.00005 m3/s-m.
1.29. GROUP – ZONE HVAC AIR LOOP TERMINAL UNITS 1291
1.29.11.1.18 Field: Beam Cooling Capacity Air Flow Modification Factor Curve
Name
This field is the name of a curve or table object that describes how the beam convector’s cooling
capacity varies as a function of the primary air flow rate. The single independent variable is the
ratio of the current primary air flow rate and the primary air flow rate at the rating point. The
result of the curve or table is multiplied by the rated capacity to adjust the cooling capacity. The
factor is useful to adjust for a range of primary air flow rates that a given product can accommodate.
However, since this is a constant volume air terminal, the modification does not typically vary during
the simulation and the range of independent variable does not need to be all that broad in practice.
1.29.11.1.20 Field: Beam Rated Heating Capacity per Beam Length (W/m)
This is the beam heating capacity at rating conditions divided by the length of the beam, in W/m.
This is only the heating contributed by the hot water circulating through the convector and is
separate from any heating (or cooling) that may also be provided by the primary air. The default is
1.200 W/m.
1.29.11.1.21 Field: Beam Rated Heating Room Air Hot Water Temperature
Difference (Delta C)
This input defines the value of the temperature difference between the entering hot water and the
room air at the rating point, in delta Celsius. This input helps to define the operating conditions that
correspond with Rated Beam Heating Capacity per Meter. It is used to normalize the independent
variable in the input field called Beam Heating Capacity Temperature Difference Modification Factor
Curve or Table Name. The default is 27.8 delta C.
1.29.11.1.22 Field: Beam Rated Hot Water Volume Flow Rate per Beam Length
(m3/s-m)
This input defines the value of the hot water flow rate per meter length of beam at the rating
point, in m3/s/m, or more strictly m3/s-m. This input helps to define the operating conditions that
1292 CHAPTER 1. INPUT-OUTPUT REFERENCE
correspond with Rated Beam Heating Capacity per Meter. It is used to normalize the independent
variable in the input field called Beam Heating Capacity Hot Water Flow Modification Factor Curve
or Table Name. The default is 0.00005 m3/s-m.
1.29.11.1.24 Field: Beam Heating Capacity Air Flow Modification Factor Curve
Name
This field is the name of a curve or table object that describes how the beam convectors heating
capacity varies as a function of the primary air flow rate. The single independent variable is the
ratio of the current primary air flow rate and the primary air flow rate at the rating point. The
result of the curve or table is multiplied by the rated capacity to adjust the heating capacity. The
factor is useful to adjust for a range of primary air rates that a given product can accommodate.
However, since this is a constant volume air terminal, the modification does not typically vary during
the simulation and the range of independent variable does not need to be all that broad in practice.
1.29.11.1.25 Field: Beam Heating Capacity Hot Water Flow Modification Factor
Curve Name
This field is the name of a curve or table object that describes how the beam convector’s heating
capacity varies as a function of the water flow rate. The single independent variable is the ratio of
the current fluid flow rate to the fluid flow rate at the rating point. The result of the curve or table
is multiplied by the rated capacity to adjust the heating capacity. The model will adjust the hot
water flow rate to vary heating power to meet the zone load, so for control purposes, the range of
the independent variable must include all the way down to zero flow, with zero capacity at zero flow.
An example input follows:
AirTerminal:SingleDuct:ConstantVolume:FourPipeBeam ,
Zone One 4pipe Beam , !- Name
ALWAYS_ON , !- Primary Air Availability Schedule Name
ALWAYS_ON , !- Cooling Availability Schedule Name
ALWAYS_ON , !- Heating Availability Schedule Name
Zone One 4pipe Beam Inlet Node Name , !- Primary Air Inlet Node Name
Zone One 4pipe Beam Outlet Node Name , !- Primary Air Outlet Node Name
Zone One 4pipe Beam CW Inlet Node , !- Chilled Water Inlet Node Name
Zone One 4pipe Beam CW Outlet Node , !- Chilled Water Outlet Node Name
AUTOSIZE , !- Design Primary Air Volume Flow Rate
AUTOSIZE , !- Design Chilled Water Volume Flow Rate
AUTOSIZE , !- Design Hot Water Volume Flow Rate
AUTOSIZE , !- Zone Total Beam Length
0.036 , !- Rated Primary Air Flow Rate per Beam Length
597 , !- Rated Beam Cooling Capacity per Beam Length
10.0 , !- Rated Cooling Room Air Chilled Water Temperature Difference
5.2E-5 , !- Rated Chilled Water Volume Flow Rate per Beam Length
CapModFuncOfTempDiff , !- Beam Cooling Capacity Temperature Difference Modification Factor Curve
or Table Name
CoolCapModFuncOfSAFlow , !- Beam Cooling Capacity Air Flow Modification Factor Curve or Table
Name
1.29. GROUP – ZONE HVAC AIR LOOP TERMINAL UNITS 1293
CapModFuncOfWaterFlow , !- Beam Cooling Capacity Chilled Water Flow Modification Factor Curve or
Table Name
1548 , !- Rated Beam Heating Capacity per Beam Length
27.8, !- Rated Heating Room Air Hot Water Temperature Difference
5.2E-5, !- Rated Hot Water Volume Flow Rate per Beam Length
CapModFuncOfTempDiff , !- Beam Heating Capacity Temperature Difference Modification Factor Curve
or Table Name
HeatCapModFuncOfSAFlow , !- Beam Heating Capacity Air Flow Modification Factor Curve or Table
Name
CapModFuncOfWaterFlow ; !- Beam Heating Capacity Hot Water Flow Modification Factor Curve or
Table Name
1.29.11.2 Outputs
1.29.11.2.5 Zone Air Terminal Primary Air Sensible Cooling Rate [W]
Sensible cooling by the primary air to the zone, exclusive of any cooling or heating done by the
beams.
1.29.11.2.6 Zone Air Terminal Primary Air Sensible Cooling Energy [J]
Sensible cooling by the primary air to the zone, exclusive of any cooling or heating done by the
beams.
1.29.11.2.7 Zone Air Terminal Primary Air Sensible Heating Rate [W]
Heating by the primary air to the zone, exclusive of any cooling or heating done by the beams.
1.29.11.2.8 Zone Air Terminal Primary Air Sensible Heating Energy [J]
Heating by the primary air to the zone, exclusive of any cooling or heating done by the beams.
1.29.11.2.10 Zone Air Terminal Outdoor Air Volume Flow Rate [m3/s]
This output is the amount of outdoor air entering the zone. This is the average value over the
frequency being reported. The amount of outdoor air is defined as the terminal unit air volume flow
rate multiplied by the fraction of outdoor air entering the air loop’s outside air system.
1.29.12 AirTerminal:SingleDuct:ConstantVolume:CooledBeam
The Cooled Beam system is a mixed air-hydronic system. A central, single-duct forced-air system
supplies conditioned ventilation air to the zones. Sensible cooling is done by chilled water circulating
through ceiling mounted cooled beam units. Chilled water flow rate through the cooled beam units is
varied to meet the zone sensible cooling load. Any dehumidification is done by the central ventilation
air system. Heating is usually accomplished with hot water radiators. Thermodynamically, the
cooled beam system resembles the four-pipe induction unit.
To model a typical cooled beam system the user will need to define a conventional central constant
volume forced air system. This system will normally be 100% outside air delivered at a fixed supply
temperature (which could be reset by schedule or by outside air temperature). On the supply side
of this air loop there will be the usual central AC equipment: outside air mixer, fan, heating and
cooling coil. On the zone equipment (demand) side of the loop, the chilled beams will be represented
as terminal units. Additional zone equipment (such as baseboard heaters) will be needed to handle
heating loads.
Although the cooled beam equipment in a zone is treated by the program as a single terminal unit,
the actual installation will have multiple beams in each zone. The program (in its sizing calculation
for the system) figures out how many beams of what length are needed to meet the zone design load.
1.29.12.1 Inputs
AirTerminal:SingleDuct:ConstantVolume:CooledBeam ,
SPACE2 -1 CB , !- Name
CWCoilAvailSched , !- Availability Schedule Name
Active , !- Cooled Beam Type
SPACE2 -1 ATU Supply Node ,!- Supply Air Inlet Node Name
SPACE2 -1 In Node , !- Supply Air Outlet Node Name
SPACE2 -1 CW Coil Water In Node , !- Chilled Water Inlet Node Name
SPACE2 -1 CW Coil Water Out Node , !- Chilled Water Outlet Node Name
, !- Supply Air Volumetric Flow Rate
, !- Maximum Total Chilled Water Volumetric Flow Rate
, !- Number of Beams
, !- Beam Length
, !- Design Inlet Water Temperature
, !- Design Outlet Water temperature
, !- Coil Surface Area per Coil Length
, !- Model Parameter a
, !- Model Parameter n1
, !- Model Parameter n2
, !- Model Parameter n3
, !- Model Parameter a0
, !- Model Parameter K1
, !- Model Parameter n
, !- Coefficient of Induction Kin
; !- Leaving Pipe Inside Diameter
1.29.12.2 Outputs
1.29.12.2.3 Zone Air Terminal Supply Air Sensible Cooling Rate [W]
Sensible cooling by the supply air to the zone, exclusive of any cooling done by the beams.
1.29.12.2.4 Zone Air Terminal Supply Air Sensible Cooling Energy [J]
Sensible cooling by the supply air to the zone, exclusive of any cooling done by the beams.
1.29.12.2.5 Zone Air Terminal Supply Air Sensible Heating Rate [W]
Heating by the supply air to the zone, exclusive of any cooling done by the beams.
1.29.12.2.6 Zone Air Terminal Supply Air Sensible Heating Energy [J]
Heating by the supply air to the zone, exclusive of any cooling done by the beams.
1.29.12.2.8 Zone Air Terminal Outdoor Air Volume Flow Rate [m3/s]
This output is the amount of outdoor air entering the zone. This is the average value over the
frequency being reported. The amount of outdoor air is defined as the terminal unit air volume flow
rate multiplied by the fraction of outdoor air entering the air loop’s outside air system.
1.29.13 AirTerminal:SingleDuct:Mixer
The air terminal mixer provides a means of supplying central system air either to air inlet or supply
side of a ZoneHVAC equipment such as a four pipe fan coil. Normally the central air would be
ventilation air from a dedicated outside air system (DOAS).
This terminal mixer object mixes conditioned outdoor air (primary air) from DOAS air loop and
recirculating (secondary air) and deliver it either to inlet or supply side of a local ZoneHVAC equip-
ment. The terminal mixer can be connected either to the inlet or supply side of the local ZoneHVAC
equipment and the connection type is specified in the input field Mixer Connection Type. If the
AirTerminal:SingleDuct:Mixer object is connected to the supply side, a mix of conditioned outdoor
air from a central dedicated outdoor air system (DOAS) with conditioned recirculation air from the
local ZoneHVAC equipment is supplied as a single stream to the conditioned zone at its inlet node.
If the AirTerminal:SingleDuct:Mixer object is connected to the inlet side, a mix of outdoor air from
the a central dedicated outdoor air system (DOAS) with un-conditioned recirculation air from a
zone exhaust node is supplied to the ZoneHVAC equipment inlet node. The mixer model will sum
the two air streams and average the air properties. The AirTerminal:SingleDuct:Mixer is used with:
– ZoneHVAC:FourPipeFanCoil
– ZoneHVAC:WaterToAirHeatPump
– ZoneHVAC:PackagedTerminalAirConditioner
– ZoneHVAC:PackagedTerminalHeatPump
– ZoneHVAC:TerminalUnit:VariableRefrigerantFlow
– ZoneHVAC:UnitVentilator
– AirLoopHVAC:UnitarySystem
1.29. GROUP – ZONE HVAC AIR LOOP TERMINAL UNITS 1299
Figure 1.128: Inlet Side Mixer Air Terminal Unit with ZoneHVAC Equipment
1.29.13.1 Inputs
– ZoneHVAC:FourPipeFanCoil
– ZoneHVAC:WaterToAirHeatPump
– ZoneHVAC:PackagedTerminalAirConditioner
– ZoneHVAC:PackagedTerminalHeatPump
1300 CHAPTER 1. INPUT-OUTPUT REFERENCE
Figure 1.129: Supply Side Mixer Air Terminal Unit with ZoneHVAC equipment
1.29. GROUP – ZONE HVAC AIR LOOP TERMINAL UNITS 1301
– ZoneHVAC:TerminalUnit:VariableRefrigerantFlow
– ZoneHVAC:UnitVentilator
– AirLoopHVAC:UnitarySystem
1.0, as for a dedicated outdoor air system, the air flow rate will match the outdoor air requirement.
When the outdoor air fraction is less than 1.0, as for a recirculating air system, the terminal air
flow will be modulated upward to account for the increased total air flow needed to provide the
required flow rate of outdoor air. The total air flow rate will not exceed the Maximum Air Flow
Rate specified above. The volume flow rate is converted to mass flow rate using the standard density
of air at Pressure = 101325 Pa, Temperature = 20C, and Humidity Ratio = 0.0.
AirTerminal:SingleDuct:Mixer ,
SPACE2 -1 DOAS Air Terminal , !- Name
ZoneHVAC:FourPipeFanCoil , !- ZoneHVAC Unit Object Type
SPACE2 -1 Fan Coil , !- ZoneHVAC Unit Object Name
SPACE2 -1 Fan Coil Inlet , !- Mixer Outlet Node Name
SPACE2 -1 ATM Primary Inlet , !- Mixer Primary Air Inlet Node Name
SPACE2 -1 ATM Secondary Inlet ,!- Mixer Secondary Air Inlet Node Name
InletSide; !- Mixer Connection Type
AirTerminal:SingleDuct:Mixer ,
SPACE1 -1 DOAS Air Terminal , !- Name
ZoneHVAC:FourPipeFanCoil , !- ZoneHVAC Unit Object Type
SPACE1 -1 Fan Coil , !- ZoneHVAC Unit Object Name
SPACE1 -1 Supply Inlet , !- Mixer Outlet Node Name
SPACE1 -1 ATM Primary Inlet , !- Mixer Primary Air Inlet Node Name
SPACE1 -1 Fan Coil Outlet , !- Mixer Secondary Air Inlet Node Name
SupplySide; !- Mixer Connection Type
1.29.14 AirTerminal:DualDuct:ConstantVolume
The AirTerminal:DualDuct:ConstantVolume simulation or the typical Multizone is described by
this Air Distribution Unit (ADU). Multizone systems condition all the air in a central apparatus
and distribute it to the conditioned zones through two parallel ducts. One duct carries cold air
and the other warm air, providing air sources for both heating and cooling at all times. In each
conditioned zone, a mixing valve responsive to a room thermostat mixes the warm and cold air in
proper proportions to satisfy the prevailing heating or cooling load of the space. The Multizone ADU
is the specific component that leads to the zone containing the mixer and the mixing damper and
then connecting to the zone. The total airflow to each room is kept constant while the proportion
of hot air to cold air is adjusted to maintain the temperature in each zone at the desired level.
1.29.14.1 Inputs
AirTerminal:DualDuct:ConstantVolume ,
Zone2MixDamp , !- Name
FanAndCoilAvailSched , !- Availability Schedule
Zone 2 Dual Duct Outlet , !- Unit Air Outlet Node
Zone 2 Dual Duct Hot Inlet , !- Unit Hot Air Inlet Node
Zone 2 Dual Duct Cold Inlet , !- Unit Cold Air Inlet Node
0.36; !- Max Air Flow Rate {m3/s}
1.29.14.2 Outputs
1.29.15 AirTerminal:DualDuct:VAV
AirTerminal:DualDuct:VAV (i.e., Dual duct variable air volume (DDVAV)) systems are used to
obtain zone temperature control by mixing the cold and warm air in various volume combinations.
The fan is sized for the anticipated maximum coincident hot or cold volume, not the sum of the
instantaneous peaks. This system has an advantage of a true single path VAV system, except for
warm port leakage. When cold air is modulated for control before mixing, it operates similar to the
VAV induction when mixing occurs without hot deck reheat. It is similar to a reheat system when
mixing occurs while the hot deck is using the reheat coil. It uses more energy than a true VAV
system, but less than a constant volume dual duct system.
The zone minimum supply air flow can be further adjusted using scheduled fraction values specified
in the field Minimum Air Flow Turndown Schedule Name.
1.29.15.1 Inputs
AirTerminal:DualDuct:VAV ,
Zone1MixDamp , !- Name
FanAndCoilAvailSched , !- Availability Schedule Name
Zone 1 Dual Duct Outlet , !- Air Outlet Node Name
Zone 1 Dual Duct Hot Inlet , !- Hot Air Inlet Node Name
Zone 1 Dual Duct Cold Inlet , !- Cold Air Inlet Node Name
autosize , !- Maximum Air Flow Rate {m3/s}
0.1, !- Zone Minimum Air Flow Fraction
ZoneMinOARequirements , !- Design Specification Outdoor Air Object Name
TurndownMinAirFlowSch ; !- Minimum Air Flow Turndown Schedule Name
Schedule:Compact ,
Min OARequirements Sched , !- Name
Any Number , !- Schedule Type Limits Name
Through: 12/31 , !- Field 1
For: Weekdays SummerDesignDay WinterDesignDay , !- Field 2
Until: 24:00 ,1.0 , !- Field 7
For: AllOtherDays , !- Field 9
Until: 24:00 ,0.25; !- Field 10
Schedule:Compact ,
TurndownMinAirFlowSch , !- Name
Fraction , !- Schedule Type Limits Name
Through: 12/31 , !- Field 1
For: Weekdays , !- Field 2
Until: 7:00 ,0.50 , !- Field 3
Until: 17:00 ,0.75 , !- Field 4
Until: 24:00 ,0.50 , !- Field 5
For: SummerDesignDay WinterDesignDay , !- Field 6
Until: 24:00 ,1.0 , !- Field 7
For: Weekends Holidays CustomDay1 CustomDay2 , !- Field 8
1306 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.29.15.2 Outputs
1.29.15.2.3 Zone Air Terminal Outdoor Air Volume Flow Rate [m3/s]
This output is the amount of outdoor air entering the zone. This is the average value over the
frequency being reported. The amount of outdoor air is defined as the terminal unit air volume flow
rate multiplied by the fraction of outdoor air entering the air loop’s outdoor air system.
1.29.16 AirTerminal:DualDuct:VAV:OutdoorAir
AirTerminal:DualDuct:VAV:OutdoorAir provides a model for a type of dual duct air system in which
one duct provides outdoor air ventilation and the other provides VAV cooling. The Outdoor Air
stream and the Recirculated Air stream are conditioned and supplied through separate air streams as
part of a centralized dedicated outdoor air (DOAS) distribution system. The dual duct arrangement
allows the ventilation air to be controlled separately using schedules or occupancy demand while the
recirculated air is controlled to meet the dry-bulb zone temperature setpoint. The two airstreams
remain decoupled until the terminal box where they are mixed. The terminal unit is meant for
systems regulating outdoor air based only on demand control or code minimum settings and not on
economizer operation.
This air terminal does not have heating coils and is not configured for conditions zones that need
heat. Additional ZoneHVAC equipment, such as baseboards or fan coil units, are needed to provide
heating to the zone when using this air terminal.
Although this air terminal is primarily for dual duct system, it is allowed to use just the outdoor air
side in a single duct system. This can be useful for modeling single duct DOAS when the required
volume of outdoor air varies over time.
1.29. GROUP – ZONE HVAC AIR LOOP TERMINAL UNITS 1307
1.29.16.1 Inputs
AirTerminal:DualDuct:VAV:OutdoorAir ,
Media_Center Dual Duct Box Component , !- Name
ALWAYS_ON , !- Availability Schedule Name
Media_Center Dual Duct Box Outlet Node Name , !- Air Outlet Node Name
Media_Center Dual Duct Box Inlet Node Name , !- Outdoor Air Inlet Node Name
RC Media_Center Dual Duct Box Inlet Node Name , !- Recirculated Air Inlet Node Name
AUTOSIZE , !- Maximum Terminal Air Flow Rate {m3/s}
Media_Center Dual Duct Box OA Design Spec , !- Design Specification Outdoor Air Object
Name
CurrentOccupancy; !- Per Person Ventilation Rate Mode
DesignSpecification :OutdoorAir ,
Media_Center Dual Duct Box OA Design Spec , !- Name
Sum , !- Outdoor Air Method
0.004719 , !- Outdoor Air Flow per Person {m3/s-person}
0.00061 , !- Outdoor Air Flow per Zone Floor Area {m3/s-m2}
0.0, !- Outdoor Air Flow per Zone {m3/s}
0.0, !- Outdoor Air Flow Air Changes per Hour
MinOA_Sched; !- Outdoor Air Flow Rate Fraction Schedule Name
1.29.16.2 Outputs
1.30.1 ZoneHVAC:IdealLoadsAirSystem
The simplest piece of zone equipment is the ZoneHVAC:IdealLoadsAirSystem component. Zone-
HVAC:IdealLoadsAirSystem is used in situations where the user wishes to study the performance
of a building without modeling a full HVAC system. In such a case, the Ideal Loads Air System is
usually the sole conditioning component: the user does not need to specify air loops, water loops,
etc. All that is needed for the ideal system are zone controls, zone equipment configurations, and
the ideal loads system component. The use of a return plenum is optional and will require use of
the AirloopHVAC:ReturnPlenum object.
This component can be operated with infinite or finite heating and cooling capacity. For either mode
– infinite or limited capacity – the user can also specify on/off schedules for heating and cooling
and outdoor air controls. There are also optional controls for dehumidification, humidification,
economizer, and heat recovery. This component may be used in combination with other HVAC
equipment serving the same zone.
This component can be thought of as an ideal unit that mixes air at the zone exhaust condition (or
plenum outlet condition when a plenum is attached) with the specified amount of outdoor air and
then adds or removes heat and moisture at 100% efficiency in order to produce a supply air stream
at the specified conditions. The energy required to condition the supply air is metered and reported
as DistrictHeating and DistrictCooling.
Notes: The ideal loads system uses the zone return node or an optional zone exhaust node to extract
air from the zone. When the AirloopHVAC:ReturnPlenum is used the inlet of the ideal loads system
is connected to the plenum outlet air node while the outlet of the ideal loads system is connected to
a zone inlet node. The node name connected between the zone exhaust air node and plenum inlet
air node must match in the ZoneHVAC:EquipmentConnections and AirloopHVAC:ReturnPlenum
objects. Every zone served by an HVAC component must have a return air node, even though this
node may not be connected to anything. If more than one ideals loads air systems are connected to
the same AirloopHVAC:ReturnPlenum then one of the ideal loads air systems will connect to the
ZoneHVAC:ReturnPlenum outlet air node and the remaining ideal loads air systems connected to
the same return plenum will connect to the ZoneHVAC:ReturnPlenum induced air outlet nodes.
The ideal loads system was significantly expanded in version 7.0 (October 2011). As part of this
upgrade, any change in the moisture content of the supply air stream results in a latent cooling
(dehumidification) or latent heating (humidification) load which is metered as DistrictCooling and
DistrictHeating energy consumption. Prior to version 7.0, when the ideal loads system was in heat-
ing mode, only the energy for sensible heating was metered. This results in significant changes in
reported energy use compared to earlier versions, especially when using the ConstantSupplyHu-
midityRatio option for Humidification Control Type.
Older idf files which are transitioned to version 7.0 will automatically be set to use the ConstantSup-
plyHumidityRatio option for both dehumidification and humidification controls, because this is
1310 CHAPTER 1. INPUT-OUTPUT REFERENCE
equivalent to the controls used in the older version of this system. However, the user should review
all of the humidity control options and select the one which best reflects the goal of the simulation.
1.30.1.1 Inputs
– None means that the design occupancy level will be used when computing the minimum
outdoor air flow rate based on the inputs in the Design Specification Outdoor Air Object (see
previous field).
– OccupancySchedule means that the current occupancy level will be used when computing
the minimum outdoor air flow rate based on the inputs in the Design Specification Outdoor
Air Object (see previous field).
– CO2Setpoint means that the design occupancy level will be used when computing the mini-
mum outdoor air flow rate based on the inputs in the Design Specification Outdoor Air Object
(see previous field). In addition, the minimum outdoor air flow rate may be increased if nec-
essary to maintain the level of indoor air carbon dioxide at or below the setpoint defined in a
ZoneControl:ContaminantController object.
1314 CHAPTER 1. INPUT-OUTPUT REFERENCE
ZoneHVAC:IdealLoadsAirSystem ,
Zone1 Ideal Loads System , !- Name
AlwaysOn , !- Availability Schedule Name
Zone1 Ideal Loads Supply Node , !- Zone Supply Air Node Name
Zone1 Ideal Loads Return Node , ! Zone Exhaust Air Node Name
50, !- Maximum Heating Supply Air Temperature {C}
13, !- Minimum Cooling Supply Air Temperature {C}
0.0156 , !- Maximum Heating Supply Air Humidity Ratio {kgWater/kgDryAir}
0.0077 , !- Minimum Cooling Supply Air Humidity Ratio {kgWater/kgDryAir}
NoLimit , !- Heating Limit
, !- Maximum Heating Air Flow Rate {m3/s}
, !- Maximum Sensible Heating Capacity {W}
NoLimit , !- Cooling Limit
, !- Maximum Cooling Air Flow Rate {m3/s}
, !- Maximum Total Cooling Capacity {W}
1.30. GROUP – ZONE FORCED AIR UNITS 1315
1.30.1.2 Outputs
The Ideal Loads air system outdoor air load variables are only calculated when there is active heating
or cooling (or humidification/dehumidification).
1.30.1.2.2 Zone Ideal Loads Supply Air Sensible Heating Energy [J]
1.30.1.2.3 Zone Ideal Loads Supply Air Sensible Heating Rate [W]
The sensible heating energy (or rate) added to raise the temperature of the mixed air stream to the
temperature of the supply air stream. This is the ideal “heating coil” load.
1.30.1.2.4 Zone Ideal Loads Supply Air Latent Heating Energy [J]
1.30.1.2.5 Zone Ideal Loads Supply Air Latent Heating Rate [W]
The latent heating energy (or rate) added to raise the humidity ratio of the mixed air stream to the
temperature of the supply air stream. This is the ideal “humidifier” load.
1.30.1.2.6 Zone Ideal Loads Supply Air Total Heating Energy [J]
1.30.1.2.7 Zone Ideal Loads Supply Air Total Heating Rate [W]
The total (sensible and latent) heating energy (or rate) added to raise the mixed air stream to the
temperature and humidity ratio of the supply air stream. Zone Ideal Loads Supply Air Total Heating
Energy is metered as DistrictHeating energy.
1.30.1.2.8 Zone Ideal Loads Supply Air Sensible Cooling Energy [J]
1318 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.30.1.2.9 Zone Ideal Loads Supply Air Sensible Cooling Rate [W]
The sensible cooling energy (or rate) removed to lower the temperature of the mixed air stream to
the temperature of the supply air stream. This is the ideal “cooling coil” sensible load.
1.30.1.2.10 Zone Ideal Loads Supply Air Latent Cooling Energy [J]
1.30.1.2.11 Zone Ideal Loads Supply Air Latent Cooling Rate [W]
The latent cooling energy (or rate) removed to lower the humidity ratio of the mixed air stream to
the temperature of the supply air stream. This is the ideal “cooling coil” latent load.
1.30.1.2.12 Zone Ideal Loads Supply Air Total Cooling Energy [J]
1.30.1.2.13 Zone Ideal Loads Supply Air Total Cooling Rate [W]
The total (sensible and latent) cooling energy (or rate) removed to lower the mixed air stream to
the temperature and humidity ratio of the supply air stream. Zone Ideal Loads Supply Air Total
Cooling Energy is metered as DistrictCooling energy. This is the ideal “cooling coil” total load.
1.30.1.2.26 Zone Ideal Loads Outdoor Air Sensible Heating Energy [J]
1.30.1.2.27 Zone Ideal Loads Outdoor Air Sensible Heating Rate [W]
The sensible heating energy (or rate) required to raise the temperature of the outdoor air to the
zone exhaust air temperature. This value will be calculated only when heating is active.
1.30.1.2.28 Zone Ideal Loads Outdoor Air Latent Heating Energy [J]
1.30.1.2.29 Zone Ideal Loads Outdoor Air Latent Heating Rate [W]
The latent heating energy (or rate) required to raise the humidity ratio of the outdoor air to the
zone exhaust air humidity ratio. This value will be calculated only when humidification is active.
1.30.1.2.30 Zone Ideal Loads Outdoor Air Total Heating Energy [J]
1.30.1.2.31 Zone Ideal Loads Outdoor Air Total Heating Rate [W]
The total (sensible and latent) heating energy (or rate) required to raise the temperature and hu-
midity ratio of the outdoor air to the zone exhaust air humidity ratio. This value will be calculated
only when heating or humidification is active.
1.30.1.2.32 Zone Ideal Loads Outdoor Air Sensible Cooling Energy [J]
1.30.1.2.33 Zone Ideal Loads Outdoor Air Sensible Cooling Rate [W]
The sensible cooling energy (or rate) required to lower (or raise) the temperature of the outdoor air
to the zone exhaust air temperature. This value will be calculated only when cooling is active.
1.30.1.2.34 Zone Ideal Loads Outdoor Air Latent Cooling Energy [J]
1.30.1.2.35 Zone Ideal Loads Outdoor Air Latent Cooling Rate [W]
The latent cooling energy (or rate) required to lower (or raise) the humidity ratio of the outdoor air
to the zone exhaust air humidity ratio. This will be calculated only when dehumidification is active.
1.30.1.2.36 Zone Ideal Loads Outdoor Air Total Cooling Energy [J]
1.30.1.2.37 Zone Ideal Loads Outdoor Air Total Cooling Rate [W]
The total (sensible and latent) cooling energy (or rate) required to lower the temperature and
humidity ratio of the outdoor air to the zone exhaust air temperature and humidity ratio. This
value will be calculated only when cooling or dehumidification is active.
1320 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.30.1.2.38 Zone Ideal Loads Heat Recovery Sensible Heating Energy [J]
1.30.1.2.39 Zone Ideal Loads Heat Recovery Sensible Heating Rate [W]
The sensible heating energy (or rate) added to the outdoor air stream from heat recovery.
1.30.1.2.40 Zone Ideal Loads Heat Recovery Latent Heating Energy [J]
1.30.1.2.41 Zone Ideal Loads Heat Recovery Latent Heating Rate [W]
The latent heating energy (or rate) added to the outdoor air stream from heat recovery.
1.30.1.2.42 Zone Ideal Loads Heat Recovery Total Heating Energy [J]
1.30.1.2.43 Zone Ideal Loads Heat Recovery Total Heating Rate [W]
The total (sensible and latent) heating energy (or rate) added to the outdoor air stream from heat
recovery.
1.30.1.2.44 Zone Ideal Loads Heat Recovery Sensible Cooling Energy [J]
1.30.1.2.45 Zone Ideal Loads Heat Recovery Sensible Cooling Rate [W]
The sensible cooling energy (or rate) removed from the outdoor air stream from heat recovery.
1.30.1.2.46 Zone Ideal Loads Heat Recovery Latent Cooling Energy [J]
1.30.1.2.47 Zone Ideal Loads Heat Recovery Latent Cooling Rate [W]
The latent cooling energy (or rate) removed from the outdoor air stream from heat recovery.
1.30.1.2.48 Zone Ideal Loads Heat Recovery Total Cooling Energy [J]
1.30.1.2.49 Zone Ideal Loads Heat Recovery Total Cooling Rate [W]
The total (sensible and latent) cooling energy (or rate) removed from the outdoor air stream from
heat recovery.
1.30.1.2.53 Zone Ideal Loads Outdoor Air Mass Flow Rate [kg/s]
The mass flow rate of the outdoor air stream in kg/s.
1.30.1.2.54 Zone Ideal Loads Outdoor Air Standard Density Volume Flow Rate
[m3/s]
The volume flow rate of the outdoor air stream in m3/s using the standard density. The standard
density is determined for dry air at the standard barometric pressure for the location’s elevation and
a temperature of 20.0◦C. The standard density does not vary over time.
1.30.1.2.55 Zone Ideal Loads Supply Air Mass Flow Rate [kg/s]
The mass flow rate of the supply air stream in kg/s.
1.30.1.2.56 Zone Ideal Loads Supply Air Standard Density Volume Flow Rate
[m3/s]
The volume flow rate of the supply air stream in m3/s using the standard density. The standard
density is determined for dry air at the standard barometric pressure for the location’s elevation and
a temperature of 20.0◦C. The standard density does not vary over time.
1.30.2 ZoneHVAC:FourPipeFanCoil
What is a fan coil unit? Like many HVAC terms, “fan coil unit” is used rather loosely. Sometimes
it is used for terminal units that would be better described as powered induction units. Carrier and
others use the term for the room side of refrigerant-based split systems. Here we are modeling in-room
forced-convection hydronic units. The hydronic heating coil may be replaced with an electric heating
coil. Typically these units are small (200 – 1200 cfm) and self-contained. They are mostly used in
exterior zones, usually in hotels, apartments, or offices. They may be connected to ducted outside
air, or have a direct outside air vent, but they do not have outside air economizers. Units with outside
air economizers are marketed (in the United States) as unit ventilators. Unit ventilators are typically
bigger than fan coils and are widely used in classrooms or other applications where ventilation is a
priority. If a zonal unit with an outside economizer is desired, ZoneHVAC:UnitVentilator should be
used.
The heating or cooling output of the fan coil unit is controlled by varying the air flow rate, the
water flow rate, or both. Air flow rate can be controlled by cycling the fan on/off or with a variable
speed fan drive. The most common setup is a two or three speed fan with the speed selected by
hand. The fan then cycles on/off to control heating / cooling output. The controls are often a wall
mounted thermostat with hand selection of heating/cooling and fan speed (off/low/medium/high).
These controls may also be mounted on the unit.
Carrier offers a retrofit VSD motor for fan coil units. It claims up to 45% energy savings from such
a retrofit, as well as increased comfort and less noise compared to a cycling fan (fan coil fans are
typically noisy and inefficient). Some other manufacturers are also offering units with VSD fans.
Variable speed fans appear to offer an easy way to significantly increase the efficiency of what have
typically been very inefficient units.
EnergyPlus provides 6 capacity control methods for this unit:
In EnergyPlus the fan coil units are modeled as compound components. That is, they are assembled
from other components. Fan coils contain an outdoor air mixer, a fan, a heating coil and a cooling
coil. These components are described elsewhere in this document. The fan coil input simply requires
the names of these four components, which have to be described elsewhere in the input. The input
also requires the name of an availability schedule, maximum airflow rate, outdoor airflow rate, and
maximum and minimum hot (for hydronic heating coil only) and cold water volumetric flow rates.
The unit is connected to the zone inlet and exhaust nodes and the outdoor air by specifying unit
inlet, and outlet air node names and the outdoor air mixer object name. The outdoor air mixer
child object provides the outdoor air and relief air nodes names. Note that the unit air inlet node
should be the same as a zone exhaust node and the unit outlet node should be the same as a zone
inlet node. The fan coil unit is connected to a hot water loop through its hot water coil or with no
hot water loop when using an electric coil (demand side) and to a chilled water loop (demand side)
through its cooling coil.
1.30. GROUP – ZONE FORCED AIR UNITS 1323
Note that the type of fan component associated with the fan coil unit depends on the type of capacity
control method chosen. For ConstantFanVariableFlow a Fan:OnOff or Fan:ConstantVolume should
be used. For CyclingFan, a Fan:OnOff should be used, for VariableFanVariableFlow or Variable-
FanConstantFlow a Fan:VariableVolume, for MultiSpeedFan a Fan:OnOff should be used, and for
ASHRAE90VariableFan, a Fan:OnOff or Fan:VariableVolume should be chosen.
Fan coil units can be 4-pipe or 2-pipe. For 4-pipe units there are 2 supply pipes and 2 return pipes.
For 2-pipe units there is a single supply pipe and a single return pipe and the supply is switched
between hot and chilled water depending on the season. EnergyPlus models 4-pipe units, but the
4-pipe model can be used to model 2-pipe units by using the coil availability schedules to make sure
that either hot or chilled water is exclusively available. Fan coil units with hydronic heat can instead
be modeled using an electric heating coil if desired (i.e., replace the hydronic heating coil with an
electric heating coil).
1.30.2.1 Inputs
Note: when ASHRAE90VariableFan is selected, if the the Minimum Supply Air Tem-
perature in Cooling/Heating Mode inputs are not specified, the simulation must include
zone sizing to calculate the zone design sensible cooling and heating load used to modu-
late the fan speed and, for water coils, the water flow rate or for electric heating coils,
the part load ratio.
MultiSpeedFan: for a given load, the fan cycles between speeds when fan speed selected is higher
than the minimum speed or the fan cycles on-off when the fan speed selected is the minimum and
the fan operating schedule is cycling fan. When the fan is operating as a continuous fan, then the fan
runs at minimum speed even when there is no load to meet. When the speed selected is higher than
the minimum speed, then the fan cycles between consecutive speed regardless of the fan operating
schedule type. The model selects at what fan speed to run depending on cooling or heating load.
– OutdoorAir:Mixer
This input field should be left blank when the FanCoil is connected to an AirTermi-
nal:SingleDuct:Mixer object. If this field is left blank, an outdoor air mixer object is not
simulated.
– Fan:SystemModel
– Fan:OnOff
– Fan:ConstantVolume
– Fan:VariableVolume
Note that Fan:SystemModel was added as of version 8.6 and is recommended for use in new models.
Fan:OnOff, Fan:ConstantVolume, and Fan:VariableVolume may be deprecated in a future version.
– Coil:Cooling:Water
– Coil:Cooling:Water:DetailedGeometry
– CoilSystem:Cooling:Water:HeatExchangerAssisted
The input requirements for these chilled water coil objects are described elsewhere in this document.
– Coil:Cooling:Water
– Coil:Cooling:Water:DetailedGeometry
– CoilSystem:Cooling:Water:HeatExchangerAssisted
– Coil:Heating:Water
– Coil:Heating:Electric
1.30. GROUP – ZONE FORCED AIR UNITS 1327
– Coil:Heating:Water
– Coil:Heating:Electric
ZoneHVAC:FourPipeFanCoil ,
Zone1FanCoil , !- Name
FanAndCoilAvailSched , !- Availability Schedule Name
ConstantFanVariableFlow , !- Capacity Control Method
autosize , !- Maximum Supply Air Flow Rate {m3/s}
, !- Low Speed Supply Air Flow Ratio
, !- Medium Speed Supply Air Flow Ratio
autosize , !- Maximum Outdoor Air Flow Rate {m3/s}
OUTAIRFANCOILSCHEDULE , !- Outdoor Air Schedule Name
Zone1FanCoilAirInletNode ,!- Air Inlet Node Name
Zone1FanCoilAirOutletNode , !- Air Outlet Node Name
OutdoorAir:Mixer , !- Outdoor Air Mixer Object Type
Zone1FanCoilOAMixer , !- Outdoor Air Mixer Name
Fan:ConstantVolume , !- Supply Air Fan Object Type
Zone1FanCoilFan , !- Supply Air Fan Name
Coil:Cooling:Water , !- Cooling Coil Object Type
Zone1FanCoilCoolingCoil , !- Cooling Coil Name
autosize , !- Maximum Cold Water Flow Rate {m3/s}
0.0, !- Minimum Cold Water Flow Rate {m3/s}
0.001 , !- Cooling Convergence Tolerance
Coil:Heating:Water , !- Heating Coil Object Type
Zone1FanCoilHeatingCoil , !- Heating Coil Name
autosize , !- Maximum Hot Water Flow Rate {m3/s}
0.0, !- Minimum Hot Water Flow Rate {m3/s}
1.30. GROUP – ZONE FORCED AIR UNITS 1329
OutdoorAir:Mixer ,
Zone1FanCoilOAMixer , ! name
Zone1FanCoilOAMixerOutletNode , !Mixed Air Node Name
Zone1FanCoilOAInNode , !Outdoor Air Stream Node Name
Zone1FanCoilExhNode , !Relief Air Stream Node Name
Zone1FanCoilAirInletNode ; !Return Air Stream Node Name
Fan:OnOff ,
Zone1FanCoilFan , !- Name
FanAndCoilAvailSched , !- Availability Schedule Name
0.5, !- Fan Total Efficiency
75.0, !- Pressure Rise {Pa}
autosize , !- Maximum Flow Rate {m3/s}
0.9, !- Motor Efficiency
1.0, !- Motor In Airstream Fraction
Zone1FanCoilOAMixerOutletNode , !- Air Inlet Node Name
Zone1FanCoilFanOutletNode , !-Air Outlet Node Name
FanPowerRatioCurve , !- Fan Power Ratio Function of Speed Ratio Curve Name
FanEffRatioCurve; !- Fan Efficiency Ratio Function of Speed Ratio Curve Name
Coil:Cooling:Water ,
Zone1FanCoilCoolingCoil , !- Name
FanAndCoilAvailSched , !- Availability Schedule Name
autosize , !- Design Water Flow Rate {m3/s}
autosize , !- Design Air Flow Rate {m3/s}
autosize , !- Design Inlet Water Temperature {C}
autosize , !- Design Inlet Air Temperature {C}
autosize , !- Design Outlet Air Temperature {C}
autosize , !- Design Inlet Air Humidity Ratio {kgWater/kgDryAir}
autosize , !- Design Outlet Air Humidity Ratio {kgWater/kgDryAir}
Zone1FanCoilChWInletNode ,!- Water Inlet Node Name
Zone1FanCoilChWOutletNode , !- Water Outlet Node Name
Zone1FanCoilFanOutletNode , !- Air Inlet Node Name
Zone1FanCoilCCOutletNode ,!-Air Outlet Node Name
SimpleAnalysis , !- Type of Analysis
CrossFlow; !- Heat Exchanger Configuration
Coil:Heating:Water ,
Zone1FanCoilHeatingCoil , !- Name
FanAndCoilAvailSched , !- Availability Schedule Name
autosize , !- U-Factor Times Area Value {W/K}
autosize , !- Maximum Water Flow Rate {m3/s}
Zone1FanCoilHWInletNode , !- Water Inlet Node Name
Zone1FanCoilHWOutletNode ,!- Water Outlet Node Name
Zone1FanCoilCCOutletNode ,!- Air Inlet Node Name
Zone1FanCoilAirOutletNode , !-Air Outlet Node Name
UFactorTimesAreaAndDesignWaterFlowRate , !- Performance Input Method
autosize , !- Nominal Capacity {W}
82.2, !- Design Inlet Water Temperature {C}
16.6, !- Design Inlet Air Temperature {C}
71.1, !- Design Outlet Water Temperature {C}
32.2; !- Design Outlet Air Temperature {C}
Curve:Exponent ,
FanPowerRatioCurve , !- Name
0.0, !- Coefficient1 Constant
1.0, !- Coefficient2 Constant
3.0, !- Coefficient3 Constant
0.0, !- Minimum Value of x
1.5, !- Maximum Value of x
0.01, !- Minimum Curve Output
1.5; !- Maximum Curve Output
Curve:Cubic ,
FanEffRatioCurve , !- Name
0.33856828 , !- Coefficient1 Constant
1.72644131 , !- Coefficient2 x
-1.49280132 , !- Coefficient3 x**2
1330 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.30.2.2 Outputs
(0), ForceOff (1), CycleOn (2), and CycleOnZoneFansOnly (3). Since the status output is averaged,
the output result may not correspond to the values described here when output variable frequencies
other than detailed are used. Use the “detailed” reporting frequency (Ref. Output:Variable object)
to view the availability status at each simulation timestep.
1.30.3 ZoneHVAC:UnitVentilator
Unit ventilators are zone equipment units which are assembled from other components. They contain
a built-in outdoor air mixer, a fan, a heating coil, and a cooling coil. These components are described
elsewhere in this document, except the built-in outdoor air mixer which is contained within the unit
ventilator statement. The unit ventilator input simply requires the names of these other three
components, which have to be described elsewhere in the input. The input also requires the name
of an availability schedule, maximum airflow rate, outdoor air control information (control type and
schedules), an outdoor airflow rate, and maximum and minimum hot and cold water mass flow rates.
The unit is connected to the zone inlet and exhaust nodes and the outdoor air by specifying unit
inlet, outlet, outdoor air and exhaust (relief) air node names. Note that if the Unit Ventilator is
not connected to central dedicated outdoor air (DOA), then the unit air inlet node should be the
same as a zone exhaust air node and the unit air outlet node should be the same as a zone air
inlet node. The three node name input fields: Outdoor Air Node Name, Exhaust Air Node Name,
and Mixed Air Node Name are required fields only when the built-in outdoor air mixer is used to
provide outdoor air. If the Unit Ventilator is connected to a central dedicated outdoor air (DOA)
via AirTerminal:SingleDuct:Mixer, then the above three node name input fields are not required and
must be left blank. In the later case the Unit Ventilator node connection to the zone air exhaust
node and the zone air inlet node are described in AirTerminal:SingleDuct:Mixer object. In general,
the unit ventilator input is very similar to the fan coil unit input, and the unit is connected to a
hot water loop (demand side) through its hot water coil and to a chilled water loop (demand side)
through its cooling coil.
The main difference between the fan coil and unit ventilator input is that the unit ventilator has a
built-in outdoor air mixer with its own specialized controls. The outdoor air control type can be
selected from one of the following options: “variable percent”, “fixed temperature” or “fixed amount”.
In fixed temperature control, the amount of outdoor air is varied between the minimum outdoor air
fraction (specified by a schedule) and 100% outdoor air to obtain a mixed air temperature as close as
possible to the temperature schedule defined in the input. Variable percent control will also vary the
amount of outdoor air between the minimum and maximum fractions (both specified in input by the
user) to meet the load without the use of a coil if possible. In fixed amount control, the outdoor air
flow rate is fixed to the specified value by the user. In this control strategy, the maximum outdoor air
flow rate and schedule are automatically set to be equal to the minimum outdoor air flow rate and
schedule. These control types are based on the 2004 ASHRAE Systems and Equipment Handbook
1.30. GROUP – ZONE FORCED AIR UNITS 1333
(pp. 31.1-31.3) description of unit ventilator systems. The three outdoor air control strategies are
also valid and available when the Unit Ventilator is connected to central DOA.
The unit is controlled to meet the zone (remaining) heating or cooling demand. If there is a heating
demand, the cooling coil is off and the hot water flow through the heating coil is throttled to meet
the demand. The hot water control node must be specified (same as the hot water coil inlet node). If
there is a cooling demand from the zone, the hot water coil is off and the chilled water flow through
the cooling coil is throttled to meet the load. The cooling coil control node must be specified (same
as the cooling coil inlet node). Finally both heating and cooling require a convergence tolerance,
which is the tolerance denoting how closely the fan coil unit will meet the heating or cooling load.
The tolerance is always relative to the zone load.
Overall, control of the unit must consider the outdoor air. Here is a more detailed description of the
overall unit control:
Off: Unit is schedule off or there is no load on it. All flow rates are set to zero and the temperatures
are set to zone conditions (except for the outdoor air inlet). Outdoor air requirements will not
override this condition.
Heating/No Coil/VariablePercent: The unit is on, there is a heating load, no heating coil
is present or it has been scheduled off, and variable percent outdoor air control type has been
specified. In this case, the variable percent outdoor air controls what happens with the outdoor air.
If the outside temperature is greater than the return temperature, then the outdoor air is set to
the maximum as defined by the user input. If the outdoor air temperature is less than the return
temperature from the zone, then the outdoor air is set to the minimum outdoor air flow rate as
defined by the user. Since a coil is not present to further condition the supply air, the zone simply
receives whatever temperature air results from the outdoor air controls.
Heating/No Coil/FixedTemperature: The unit is on, there is a heating load, no heating coil is
present or it has been scheduled off, and fixed temperature has been specified. The unit ventilator
tries to use outdoor air as best as possible to meet the temperature goal. If it cannot meet this
goal because the temperature goal is not between the zone return temperature and the outdoor air
temperature, then the unit ventilator will either use the maximum or minimum outdoor air flow
rate.
Heating/No Coil/FixedAmount: The unit is on, there is a heating load, no heating coil is present
or it has been scheduled off, and fixed amount control has been specified. The unit ventilator fixes
the outdoor air flow rate as defined by the user and sets the maximum and minimum outdoor air
flow rate to be equal in order to avoid the variation of outdoor air flow rate between the maximum
and minimum values. Since a coil is not present to further condition the supply air, the zone simply
receives whatever temperature air results from the outdoor air controls.
Heating /With Coil/VariablePercent: The unit is on, there is a heating load, and variable
percent control is specified. The outdoor air fraction is set to the minimum outdoor air fraction
(schedule based), and the heating coil is activated. The heating coil attempts to meet the remaining
load on the zone being served by the unit ventilator.
Heating /With Coil/FixedAmount: The unit is on, there is a heating load, a heating coil is
present and is scheduled on, and fixed amount control has been specified. The unit ventilator fixes
the outdoor air flow rate as defined by the user and sets the maximum and minimum outdoor air
flow rate to be equal in order to avoid the variation of outdoor air flow rate between the maximum
and minimum values. The heating coil then attempts to meet any remaining zone heating load.
Cooling/No Coil/VariablePercent: The unit is on, there is a cooling load, no coil is present or
it has been scheduled off, and variable percent outdoor air control type has been specified. In this
1334 CHAPTER 1. INPUT-OUTPUT REFERENCE
case, the variable percent outdoor air controls what happens with the outdoor air. If the outside
temperature is greater than the return temperature, then the outdoor air is set to the minimum
as defined by the user input. If the outdoor air temperature is less than the return temperature
from the zone, then the outdoor air is varied up to the maximum flow rate to try to meet whatever
cooling load is present. Since a coil is not present to further condition the supply air, the zone simply
receives whatever temperature air results from the outdoor air controls.
Cooling/No Coil/FixedTemperature: The unit is on, there is a cooling load, no cooling coil is
present or it has been scheduled off, and fixed temperature has been specified. The unit ventilator
tries to use outdoor air as best as possible to meet the temperature goal. If it cannot meet this
goal because the temperature goal is not between the zone return temperature and the outdoor air
temperature, then the unit ventilator will either use the maximum or minimum outdoor air flow rate
in the same fashion as the variable percent outdoor air control.
Cooling/No Coil/FixedAmount: The unit is on, there is a cooling load, no cooling coil is present
or it has been scheduled off, and fixed amount control has been specified. The unit ventilator fixes
the outdoor air flow rate as defined by the user and sets the maximum and minimum outdoor air
flow rate to be equal in order to avoid the variation of outdoor air flow rate between the maximum
and minimum values. Since a coil is not present to further condition the supply air, the zone simply
receives whatever temperature air results from the outside air controls.
Cooling/With Coil/VariablePercent: The unit is on, there is a cooling load, a coil is present and
is scheduled on, and variable percent outdoor air control type has been specified. In this case, the
variable percent outdoor air controls what happens with the outdoor air. If the outside temperature
is greater than the return temperature, then the outdoor air is set to the minimum as defined by
the user input. If the outdoor air temperature is less than the return temperature from the zone,
then the outdoor air is varied up to the maximum flow rate to try to meet whatever cooling load is
present. The coil then attempts to meet any remaining zone load.
Cooling/With Coil/FixedTemperature: The unit is on, there is a cooling load, a cooling coil is
present and is scheduled on, and fixed temperature has been specified. The unit ventilator tries to
use outdoor air as best as possible to meet the temperature goal. If it cannot meet this goal because
the temperature goal is not between the zone return temperature and the outdoor air temperature,
then the unit ventilator will either use the maximum or minimum outdoor air flow rate in the same
fashion as the fixed temperature outdoor air control for the “no coil” conditions. The cooling coil
then attempts to meet any remaining zone load.
Cooling/With Coil/FixedAmount: The unit is on, there is a cooling load, a cooling coil is
present and is scheduled on, and fixed amount control has been specified. The unit ventilator fixes
the outdoor air flow rate as defined by the user and sets the maximum and minimum outdoor air
flow rate to be equal in order to avoid the variation of outdoor air flow rate between the maximum
and minimum values. The cooling coil then attempts to meet any remaining zone cooling load.
Note: the unit ventilator controls are strictly temperature based and do not factor humidity into
the equation (not an enthalpy economy cycle but rather a simple return air economy cycle). In
addition, temperature predictions are not strict energy balances here in the control routine though
in the mixing routine an energy balance is preserved.
1.30.3.1 Inputs
in the input data file. Like all other names in EnergyPlus, it is assumed that this is a unique character
string and that no other unit ventilators use this same name.
type is selected as the outdoor air control strategy, the actual outdoor air flow rate will be this
number multiplied by the minimum outdoor air flow rate in the field above. The unit ventilator
will automatically set the maximum and minimum outdoor air schedule to be equal by ignoring the
maximum outdoor air schedule.
– Fan:SystemModel
– Fan:OnOff
– Fan:ConstantVolume
– Fan:VariableVolume
Note that Fan:SystemModel was added as of version 8.7 and is recommended for use in new models.
Fan:OnOff, Fan:ConstantVolume, and Fan:VariableVolume may be deprecated in a future version.
– Coil:Heating:Water
– Coil:Heating:Electric
– Coil:Heating:Fuel
– Coil:Heating:Steam
– Coil:Cooling:Water
– Coil:Cooling:Water:DetailedGeometry
– CoilSystem:Cooling:Water:HeatExchangerAssisted
Maximum Air Flow Rate in this Unit Ventilator zone HVAC object. The scaled Maximum Air Flow
Rate in turn is used to size cooling and heating capacity of the unit.
An example input for a unit ventilator, including its constituent components, is shown below.
ZoneHVAC:UnitVentilator ,
Zone1UnitVent , !- Name
UnitVentAvailability , !- Availability Schedule Name
0.84, !- Maximum Supply Air Flow Rate {m3/s}
VariablePercent , !- Outdoor Air Control Type
0.168 , !- Minimum Outdoor Air Flow Rate {m3/s}
UnitVentMinOA , !- Minimum Outdoor Air Schedule Name
0.84, !- Maximum Outdoor Air Flow Rate {m3/s}
UnitVentMaxOA , !- Maximum Outdoor Air Fraction or Temperature Schedule Name
Zone1UnitVentAirInletNode , !- Air Inlet Node Name
Zone1UnitVentAirOutletNode , !- Air Outlet Node Name
Zone1UnitVentOAInNode , !- Outdoor Air Node Name
Zone1UnitVentExhNode , !- Exhaust Air Node Name
Zone1UnitVentOAMixerOutletNode , !- Mixed Air Node Name
Fan:ConstantVolume , !- Supply Air Fan Object Type
Zone1UnitVentFan , !- Fan Name
HeatingAndCooling , !- Coil Option
Coil:Heating:Water , !- Heating Coil Object Type
Zone1UnitVentHeatingCoil ,!- Heating Coil Name
0.001 , !- Heating Convergence Tolerance
Coil:Cooling:Water , !- Cooling Coil Object Type
Zone1UnitVentCoolingCoil ,!- Cooling Coil Name
0.001; !- Cooling Convergence Tolerance
OutdoorAir:Node ,
Zone1UnitVentOAInNode , !- Name
-1.0; !- Height Above Ground {m}
Fan:ConstantVolume ,
Zone1UnitVentFan , !- Name
UnitVentAvailability , !- Availability Schedule Name
0.5, !- Fan Total Efficiency
75.0, !- Pressure Rise {Pa}
0.84, !- Maximum Flow Rate {m3/s}
0.9, !- Motor Efficiency
1.0, !- Motor In Airstream Fraction
Zone1UnitVentOAMixerOutletNode , !- Fan Inlet Node Name
Zone1UnitVentFanOutletNode ; !- Fan Outlet Node Name
Coil:Cooling:Water ,
Zone1UnitVentCoolingCoil ,!- Name
FanAndCoilAvailSched , !- Availability Schedule Name
0.0010 , !- Design Water Flow Rate {m3/s}
0.84, !- Design Air Flow Rate {m3/s}
6.67, !- Design Inlet Water Temperature {C}
30, !- Design Inlet Air Temperature {C}
12, !- Design Outlet Air Temperature {C}
0.013 , !- Design Inlet Air Humidity Ratio {kgWater/kgDryAir}
0.008 , !- Design Outlet Air Humidity Ratio {kgWater/kgDryAir}
Zone1UnitVentChWInletNode , !- Water Inlet Node Name
Zone1UnitVentChWOutletNode , !- Water Outlet Node Name
Zone1UnitVentFanOutletNode , !- Air Inlet Node Name
Zone1UnitVentCCOutletNode , !- Air Outlet Node Name
SimpleAnalysis , !- Type of Analysis
CrossFlow; !- Heat Exchanger Configuration
Coil:Heating:Water ,
Zone1UnitVentHeatingCoil ,!- Name
FanAndCoilAvailSched , !- Availability Schedule Name
400., !- U-Factor Times Area Value {W/K}
0.0005 , !- Maximum Water Flow Rate {m3/s}
Zone1UnitVentHWInletNode ,!- Water Inlet Node Name
Zone1UnitVentHWOutletNode , !- Water Outlet Node Name
Zone1UnitVentCCOutletNode , !- Air Inlet Node Name
1.30. GROUP – ZONE FORCED AIR UNITS 1341
1.30.3.2 Outputs
1.30.4 ZoneHVAC:UnitHeater
Unit heaters are zone equipment units which are assembled from other components and are a sim-
plification of unit ventilators. They contain only a fan and a heating coil. These components are
described elsewhere in this document. The unit heater input simply requires the names of these
components, which have to be described elsewhere in the input. The input also requires the name of
an availability schedule, maximum airflow rate, and maximum and minimum hot water volumetric
flow rates. The unit is connected to the zone inlet and exhaust nodes by specifying unit inlet and
1.30. GROUP – ZONE FORCED AIR UNITS 1343
outlet node names. Note that the unit air inlet node should be the same as a zone exhaust node and
the unit outlet node should be the same as a zone inlet node.
While the control of the heating coil is similar to the fan coil units and the unit ventilator, the overall
control of the unit heater is much different. There are four different modes in which a unit heat can
operate based on the user input:
Off: Unit is schedule off. All flow rates are set to zero and the temperatures are set to zone
conditions.
NoLoad OR Cooling/”No” is specified in input field “Supply Air Fan Operation During No
Heating”: Unit is available, but there is no heating load. With “No” specified for “Supply Air Fan
Operation During No Heating” and the supply fan operating mode set to 0, the fan will be off
since there is no heating load. All flow rates are set to zero and the temperatures are set to zone
conditions.
NoLoad OR Cooling/”Yes” is specified in input field “Supply Air Fan Operation During No
Heating”: Unit is available, the supply fan operating mode schedule value is greater than 0 (for
OnOff Fan) and the fan is running (if it is scheduled to be available also). No heating is provided,
only air circulation via the fan running. However, any heat added by the fan is introduced into the
space with the circulation of the air.
Heating: The unit is on/available and there is a heating load. The heating coil is modulated
(constant fan speed) to meet the heating load. When the fan type is not an OnOff fan then the control
of the heating coil and its flow rate is identical to the fan coil unit. In the case of OnOff fan, the
fan cycles with heating coil if the current timestep supply fan operating mode is schedule value is 0,
or else if the current timestep supply fan operating mode schedule value is greater than 0, then the
supply fan runs continuously for the entire timestep.
1.30.4.1 Inputs
– Fan:SystemModel
– Fan:OnOff
– Fan:ConstantVolume
– Fan:VariableVolume
Note that Fan:SystemModel was added as of version 8.7 and is recommended for use in new models.
Fan:OnOff, Fan:ConstantVolume, and Fan:VariableVolume may be deprecated in a future version.
– Coil:Heating:Water
– Coil:Heating:Electric
– Coil:Heating:Fuel
– Coil:Heating:Steam
ZoneHVAC:UnitHeater ,
Zone1UnitHeat , !- Name
UnitHeatAvailability , !- Availability Schedule Name
Zone1UnitHeatAirInletNode , !- Air Inlet Node Name
Zone1UnitHeatAirOutletNode , !- Air Outlet Node Name
Fan:ConstantVolume , !- Supply Air Fan Object Type
Zone1UnitHeatFan , !- Fan Name
0.84, !- Maximum Supply Air Flow Rate {m3/s}
Continuous , !- Fan Control Type
Coil:Heating:Water , !- Heating Coil Object Type
Zone1UnitHeatHeatingCoil ,!- Heating Coil Name
0.0005 , !- Maximum Hot Water or Steam Flow Rate {m3/s}
0.0, !- Minimum Hot Water or Steam Flow Rate {m3/s}
0.001; !- Heating Convergence Tolerance
Fan:ConstantVolume ,
Zone1UnitHeatFan , !- Name
UnitHeatAvailability , !- Availability Schedule Name
0.5, !- Fan Total Efficiency
75.0, !- Pressure Rise {Pa}
0.84, !- Maximum Flow Rate {m3/s}
0.9, !- Motor Efficiency
1.0, !- Motor In Airstream Fraction
Zone1UnitHeatAirInletNode , !- Fan Inlet Node Name
Zone1UnitHeatFanOutletNode ; !- Fan Outlet Node Name
Coil:Heating:Water ,
Zone1UnitHeatHeatingCoil ,!- Name
FanAndCoilAvailSched , !- Availability Schedule Name
400., !- U-Factor Times Area Value {W/K}
0.0005 , !- Maximum Water Flow Rate {m3/s}
Zone1UnitHeatHWInletNode ,!- Water Inlet Node Name
Zone1UnitHeatHWOutletNode , !- Water Outlet Node Name
Zone1UnitHeatFanOutletNode , !- Air Inlet Node Name
Zone1UnitHeatAirOutletNode , !- Air Outlet Node Name
UFactorTimesAreaAndDesignWaterFlowRate , !- Performance Input Method
1.30. GROUP – ZONE FORCED AIR UNITS 1347
1.30.4.2 Outputs
1.30.5 ZoneHVAC:EvaporativeCoolerUnit
The zone evaporative cooler unit is a compound object made up of a fan and one or two evaporative
cooler components. This unit serves a single thermal zone as a forced-convection, cooling-only unit
with supply fan. It always draws 100% of its supply air from the outside, passes the air through a
supply fan and evaporative cooler(s) and then into the zone. The fan can be positioned upstream
of the cooler(s) for a blow through placement. Or it can be positioned downstream of the cooler(s)
for a draw through placement. If there is more than one evaporative cooler, then should be in series
with the first cooler immediately upstream of the second cooler. There is an option to include a
relief zone exhaust node to balance the air in the zone.
The unit can have either constant or variable speed fans. When a constant speed fan is specified and
the Cooler Unit Control Method is either ZoneTemperatureDeadbandOnOffCycling or ZoneCoolin-
gLoadOnOffCycling, this zone unit runs just like other constant speed forced-air zone units in that
its controls allow the unit to cycle based on a part-load formulation with averaged air flow rates.
When a variable speed fan is specified and the Cooler Unit Control Method is ZoneCoolingLoad-
VariableSpeedFan, then the unit can modulate fan speed to meet cooling loads just like other zone
HVAC units with variable speed fan.
1.30.5.1 Inputs
1.30.5.1.13 Field: Cooling Load Control Threshold Heat Transfer Rate [W]
This numeric input field defines the magnitude, in Watts, of a significant zone cooling load to use
with zone-load-to-setpoint based control. This value is used when the unit’s control method is
ZoneCoolingLoadOnOffCycling or ZoneCoolingLoadVariableSpeedFan. This is a sensible cooling
load that is used as a threshold to determine when the cooling load is significant. When the predicted
zone load to cooling setpoint is less than this threshold, the cooler unit’s control will consider the
load to be too small to trigger operation. The default is 100W.
This alpha input field defines the type of evaporative cooler used in the unit. The zone
evaporative cooler unit can have one or two separate cooler components and this field
is for the first cooler. There are five types of evaporative cooler component models to
choose from: EvaporativeCooler:Direct:CelDekPad, EvaporativeCooler:Direct:ResearchSpecial,
EvaporativeCooler:Indirect:CelDekPad, EvaporativeCooler:Indirect:WetCoil, or Evaporative-
Cooler:Indirect:ResearchSpecial.
ZoneHVAC:EvaporativeCoolerUnit ,
Zone Evap Unit , !- Name
System Availability Schedule , !- Availability Schedule Name
, !- Availability Manager List Name
Cooler Unit OA inlet , !- Outdoor Air Inlet Node Name
Main Zone Inlet Node , !- Cooler Outlet Node Name
Main Zone Relief Node , !- Zone Relief Air Node Name
Fan:SystemModel , !- Supply Air Fan Object Type
Supply Fan , !- Supply Air Fan Name
2.0, !- Design Supply Air Flow Rate
DrawThrough , !- Fan Placement
1352 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.30.5.2 Outputs
1.30.6 ZoneHVAC:OutdoorAirUnit
The zone outdoor air unit (ZoneHVAC:OutdoorAirUnit) in EnergyPlus is intended to model dedi-
cated outdoor air systems (DOAS) and other similar systems which aim to provide either additional
outside air or some limited amount of sensible and/or latent conditioning. The zone outdoor air
1354 CHAPTER 1. INPUT-OUTPUT REFERENCE
unit is a piece of zone equipment that can consist of a supply fan, an exhaust fan (optional), heat-
ing and cooling coils, and heat recovery. The outdoor air unit input simply requires information
about flow rates, schedules, node names, and a list of component that are part of the unit. These
components require additional input as per the requirements for these components. In addition,
the input includes information about controls for the unit. It should be noted that the components
that make up the zone outdoor air unit do not require additional controls or setpoints. The unit
input defines how the unit outlet temperature is controlled as described below.
When an AirloopHVAC serves the same zone, it is strongly recommended that the outdoor and
exhaust air flow rates are balanced. In addition, the exhaust airflow rate and air schedule should
be the same as outdoor air flow rate and outdoor air schedule, respectively. Otherwise, possible
unbalanced flows will cause improper return airflow unless ZoneAirMassFlowConservation is active.
The full input for zone outdoor air units is described below using a variety of fields.
1.30.6.1 Inputs
air unit can be on during the time period. A value less than or equal to 0 (usually 0 is used) denotes
that the outdoor air unit must be off for the time period. If this field is blank, the schedule has
values of 1 for all time periods. For any schedule value greater than zero, the outdoor air unit is
considered available and will operate at the supply and exhaust flow rates defined by input field
described below.
– BlowThrough
– DrawThrough
If the user does not select a fan placement type, DrawThrough is assumed as default by EnergyPlus.
– NeutralControl
– TemperatureControl
If the user does not select a unit control type, NeutralControl is assumed as the default by
EnergyPlus.
field has a valid availability manager assignment list name, then the availability managers in the list
determine when and if the fan of this outdoor air unit object should be on or off.
An example of this object defined in an input data file is shown below:
ZoneHVAC:OutdoorAirUnit ,
Zone5DXOutAir , !- Name
OAUnitOASched , !- Availability Schedule Name
SPACE5 -1, !- Zone Name
0.42, !- Outdoor Air Flow Rate {m3/s}
OAUnitOASched , !- Outdoor Air Schedule Name
Zone5OAUFan1 , !- Supply Fan Name
BlowThrough , !- Supply Fan Placement
, !- Exhaust Fan Name
, !- Exhaust Air Flow Rate {m3/s}
, !- Exhaust Air Schedule Name
TemperatureControl , !- Unit Control Type
OAUHitemp2 , !- High Air Control Temperature Schedule Name
OAULotemp2 , !- Low Air Control Temperature Schedule Name
Zone5OAUOANode , !- Outdoor Air Node Name
Zone5OAUZoneInletNode , !- AirOutlet Node Name
Zone5OAUZoneOutletNode , !- AirInlet Node Name
Zone5OAUFanOutletNode , !- Supply FanOutlet Node Name
Zone5OAUEquip1; !- Outdoor Air Unit List Name
1.30.6.2 Outputs
1.30.6.2.15 Zone Outdoor Air Unit Air Mass Flow Rate [kg/s]
This field reports the air mass flow rate of the zone outdoor air unit Outdoor Air Unit in kilograms
per second.
1.30.7 ZoneHVAC:OutdoorAirUnit:EquipmentList
This input syntax is used to specify the components in a zone outdoor air unit. The components
will be simulated in the order in which they occur in this list.
1.30.7.1 Inputs
1.30.7.1.2 Field Set (Component Object Type, Component Name, Control Node
Name) up to 8
After the identifying name, the list consists of up to 8 pairs of data items.
ZoneHVAC:OutdoorAirUnit:EquipmentList ,
Zone5OAUEquip1 , !- Name
Dehumidifier:Desiccant:NoFans , !- Component 1 Object Type
Z5Dessicant , !- Component 1 Name
HeatExchanger:AirToAir:FlatPlate , !- Component 2 Object Type
Zone5A2AHeat Recovery , !- Component 2 Name
CoilSystem:Cooling:DX , !- Component 3 Object Type
DX Cooling Coil System 5,!- Component 3 Name
Coil:Heating:Electric , !- Component 4 Object Type
Zone5DESHCoil; !- Component 4 Name
1.30.8 ZoneHVAC:WindowAirConditioner
The Window Air Conditioner is a unit of zone equipment made up of other components. Each window
air conditioner consists of an outdoor air mixer, a fan, and a direct expansion (DX) cooling coil.
These components are described elsewhere in this document. The input for a window air conditioner
requires the names of these three pieces of equipment, which are then specified individually elsewhere
in the input. The input for a window air conditioner also requires the name of an availability
schedule, the maximum unit airflow rate, and the maximum outdoor airflow rate for the unit.
The unit is connected to a zone by specifying an air inlet node, which must be the same as a
zone exhaust node; and an air outlet node, which must be the same as a zone inlet node (ref.
ZoneHVAC:EquipmentConnections).
A supply air fan operating mode schedule must also be specified. The supply air fan operating
mode schedule value determines if the supply air fan can run continuously with the DX coil cycling
on/off to match the zone cooling demand or the fan and DX coil can cycle on/off together to meet
the cooling demand. The placement of the supply air fan, in relation to the DX coil, must also
be specified (blow through or draw through). The cooling convergence tolerance is required, which
is the tolerance denoting how closely the window air conditioner will meet the cooling load. The
tolerance is always relative to the zone load (i.e., the unit will operate to meet the zone load to
within the tolerance value times the zone load for each simulation timestep). Finally, the DX cooling
coil type must be specified.
1.30.8.1 Inputs
The name of the schedule (ref: Schedule) that denotes whether the window air conditioner unit can
run during a given time period. A schedule value greater than 0 (usually 1 is used) indicates that
the unit can be on during the time period. A value less than or equal to 0 (usually 0 is used) denotes
that the unit must be off for the time period. If this field is blank, the schedule has values of 1 for
all time periods.
– Fan:SystemModel
1.30. GROUP – ZONE FORCED AIR UNITS 1363
– Fan:OnOff
– Fan:ConstantVolume
Note that Fan:SystemModel was added as of version 8.7 and is recommended for use in new models.
Fan:OnOff and Fan:ConstantVolumemay be deprecated in a future version.
– Coil:Cooling:DX:SingleSpeed
– Coil:Cooling:DX:VariableSpeed
– CoilSystem:Cooling:DX:HeatExchangerAssisted
|QZoneLoad − QW indowAirConditioner,out )|
≤ Cooling ConvergenceT olerance (1.133)
QZoneLoad
The maximum number of iterations is limited, with a warning message generated if the above
equation is not satisfied within the maximum number of iterations.
ZoneHVAC:WindowAirConditioner ,
Zone3WindAC , ! name of window AC unit
FanAndCoilAvailSched , ! Availability Schedule Name
1.30. GROUP – ZONE FORCED AIR UNITS 1365
Schedule:Compact ,
CyclingFanSch , !- Name
Fraction , !- ScheduleType
Through: 12/31 , !- Complex Field \#1
For: AllDays , !- Complex Field \#2
Until: 24:00 , !- Complex Field \#7
0.0; !- Complex Field \#8
OutdoorAir:Mixer ,
Zone3WindACOAMixer , ! Name
Zone3WindACOAMixerOutletNode , ! Mixed Air Node Name
Zone3WindACOAInNode , ! Outdoor Air Stream Node Name
Zone3WindACExhNode , ! Relief Air Stream Node Name
Zone3WindACAirInletNode ; ! Return Air Stream Node Name
Fan:SystemModel ,
Zone3WindACFan , !- Name
FanAndCoilAvailSched , !- Availability Schedule Name
Zone3WindACDXOutletNode , !- Air Inlet Node Name
Zone3WindACAirOutletNode , !- Air Outlet Node Name
0.6 , !- Design Maximum Air Flow Rate
Discrete , !- Speed Control Method
0.0, !- Electric Power Minimum Flow Rate Fraction
75.0, !- Design Pressure Rise
0.9 , !- Motor Efficiency
1.0 , !- Motor In Air Stream Fraction
AUTOSIZE , !- Design Electric Power Consumption
TotalEfficiencyAndPressure , !- Design Power Sizing Method
, !- Electric Power Per Unit Flow Rate
, !- Electric Power Per Unit Flow Rate Per Unit Pressure
0.5; !- Fan Total Efficiency
Coil:Cooling:DX:SingleSpeed ,
Zone3WindACDXCoil , !- Name
CoolingCoilAvailSched , !- Availability Schedule Name
autosize , !- Rated Total Cooling Capacity {W}
autosize , !- Rated Sensible Heat Ratio
3.0, !- Rated COP
autosize , !- Rated Air Flow Rate {m3/s}
Zone3WindACOAMixerOutletNode , !- Air Inlet Node Name
Zone3WindACDXOutletNode , !- Air Outlet Node Name
WindACCoolCapFT , !- Total Cooling Capacity Function of Temperature Curve Name
WindACCoolCapFFF , !- Total Cooling Capacity Function of Flow Fraction Curve Name
WindACEIRFT , !- Energy Input Ratio Function of Temperature Curve Name
WindACEIRFFF , !- Energy Input Ratio Function of Flow Fraction Curve Name
WindACPLFFPLR; !- Part Load Fraction Correlation Curve Name
1.30.8.2 Outputs
1.30.9 ZoneHVAC:PackagedTerminalAirConditioner
The packaged terminal air conditioner (PTAC) is a compound object made up of other components.
Each PTAC consists of an outdoor air mixer, direct expansion (DX) cooling coil, heating coil (gas,
electric, hot water, or steam) and a supply air fan. While the figure below shows the PTAC with
draw through fan placement, blow through fan placement can also be modeled by positioning the
supply air fan between the outdoor air mixer and the DX cooling coil. The packaged terminal
air conditioner coordinates the operation of these components and is modeled as a type of zone
equipment (Ref. ZoneHVAC:EquipmentList and ZoneHVAC:EquipmentConnections).
Links to the PTAC’s supply air fan, DX cooling coil, heating coil, and outdoor air mixer specifications
are provided in the air conditioner’s input syntax. Additional inputs include supply and outdoor
air flow rates during cooling operation, heating operation, and when neither cooling or heating is
required. A description of each input field for the packaged terminal air conditioner compound
object is provided below.
1368 CHAPTER 1. INPUT-OUTPUT REFERENCE
Figure 1.131: Schematic of a packaged terminal air conditioner with draw through fan placement
1.30.9.1 Inputs
This alpha field defines the name of the HVAC system node to which the air conditioner
sends its outlet air. This node name must be the name of a zone air inlet node (Ref. Zone-
HVAC:EquipmentConnections).
– OutdoorAir:Mixer
This input field should be left blank when the PTAC is connected to an AirTerminal:SingleDuct:Mixer
object. If this field is left blank, an outdoor air mixer object is not simulated.
conditioner’s supply air volumetric flow rate during cooling operation. This field is set to zero flow
when the PTAC is connected to an AirTerminal:SingleDuct:Mixer object.
– Coil:Heating:Water
– Coil:Heating:Electric
– Coil:Heating:Fuel
– Coil:Heating:Steam
– Coil:Cooling:DX:SingleSpeed
– CoilSystem:Cooling:DX:HeatExchangerAssisted
– Coil:Cooling:DX:VariableSpeed
ZoneHVAC:PackagedTerminalAirConditioner ,
Zone2PTAC , !- Name
FanAndCoilAvailSched , !- Availability Schedule Name
Zone2PTACAirInletNode , !- Air Inlet Node Name
Zone2PTACAirOutletNode , !- Air Outlet Node Name
OutdoorAir:Mixer , !- Outdoor Air Mixer Object Type
Zone2PTACOAMixer , !- Outdoor Air Mixer Name
autosize , !- Cooling Supply Air Flow Rate {m3/s}
autosize , !- Heating Supply Air Flow Rate operation {m3/s}
autosize , !- No Load Supply Air Flow Rate {m3/s}
autosize , !- Cooling Outdoor Air Flow Rate {m3/s}
autosize , !- Heating Outdoor Air Flow Rate {m3/s}
autosize , !- No Load Outdoor Air Flow Rate {m3/s}
Fan:OnOff , !- Supply Air Fan Object Type
Zone2PTACFan , !- Supply Air Fan Name
Coil:Heating:Electric , !- Heating Coil Object Type
Zone2PTACHeatCoil , !- Heating Coil Name
Coil:Cooling:DX:SingleSpeed , !- Cooling Coil Object Type
Zone2PTACDXCoolCoil , !- Cooling Coil Name
BlowThrough , !- Fan Placement
SupplyFanSch; !- Supply Air Fan Operating Mode Schedule Name
Schedule:Compact ,
SupplyFanSch , !- Name
Fraction , !- ScheduleType
Through: 12/31 , !- Complex Field \#1
For: AllDays , !- Complex Field \#2
Until: 7:00, !- Complex Field \#3
0.0, !- Complex Field \#4
Until: 18:00 , !- Complex Field \#5
1.0, !- Complex Field \#6
Until: 24:00 , !- Complex Field \#7
0.0; !- Complex Field \#8
OutdoorAir:Mixer ,
Zone2PTACOAMixer , !- Name
Zone2PTACOAMixerOutletNode , !-Mixed Air Node Name
Zone2PTACOAInNode , !-Outdoor Air Stream Node Name
Zone2PTACExhNode , !- Relief Air Stream Node Name
Zone2PTACAirInletNode ; !- Return Air Stream Node Name
Fan:OnOff ,
Zone2PTACFan , !- Name
FanAndCoilAvailSched , !- Availability Schedule Name
0.5, !- Fan Total Efficiency
75.0, !- Pressure Rise {Pa}
autosize , !- Maximum Flow Rate{m3/s}
0.9, !- Motor Efficiency
1.0, !- Motor In Airstream Fraction
1374 CHAPTER 1. INPUT-OUTPUT REFERENCE
Coil:Cooling:DX:SingleSpeed ,
Zone2PTACDXCoolCoil , !- Coil Name
CoolingCoilAvailSched , !- Availability Schedule Name
autosize , !- Rated Total Cooling Capacity (gross) {W}
autosize , !- Rated SHR
3.0, !- Rated COP
autosize , !- Rated Air Volume Flow Rate {m3/s}
Zone2PTACFanOutletNode , !- Coil Air Inlet Node
Zone2PTACCoolCoilOutletNode , !-Coil Air Outlet Node
HPACCoolCapFT , !- Total Cooling Capacity Modifier Curve (function of
temperature)
HPACCoolCapFFF , !- Total Cooling Capacity Modifier Curve (function of flow
fraction)
HPACEIRFT , !- Energy Input Ratio Modifier Curve (function of temperature)
HPACEIRFFF , !- Energy Input Ratio Modifier Curve (function of flow fraction)
HPACPLFFPLR; !- Part Load Fraction Correlation (function of part load ratio)
Coil:Heating:Electric ,
Zone2PTACHeatCoil , !- Coil Name
HeatingCoilAvailSched , !- Availability Schedule Name
1.0, !- Efficiency
autosize , !- Nominal Capacity {W}
Zone2PTACCoolCoilOutletNode , !- Air Inlet Node Name
Zone2PTACAirOutletNode ; !- Air Outlet Node Name
1.30.9.2 Outputs
1.30.9.2.1 Zone Packaged Terminal Air Conditioner Total Heating Rate [W]
This output field is the total (enthalpy) heat addition rate of the packaged terminal air conditioner
to the zone it is serving in Watts. This value is calculated using the enthalpy difference of the air
conditioner outlet air and inlet air streams, and the air mass flow rate through the air conditioner.
This value is calculated for each HVAC system timestep being simulated, and the results (enthalpy
addition only) are averaged for the timestep being reported.
1.30.9.2.2 Zone Packaged Terminal Air Conditioner Total Heating Energy [J]
This output field is the total (enthalpy) heat addition of the packaged terminal air conditioner to
the zone it is serving in Joules over the timestep being reported. This value is calculated using
the enthalpy difference of the air conditioner outlet air and inlet air streams, the air mass flow rate
through the air conditioner, and the HVAC simulation timestep. This value is calculated for each
HVAC system timestep being simulated, and the results (enthalpy addition only) are summed for
the timestep being reported.
1.30.9.2.3 Zone Packaged Terminal Air Conditioner Total Cooling Rate [W]
This output field is the total (enthalpy) heat extraction rate of the packaged terminal air conditioner
from the zone it is serving in Watts. This value is calculated using the enthalpy difference of the air
conditioner outlet air and inlet air streams, and the air mass flow rate through the air conditioner.
This value is calculated for each HVAC system timestep being simulated, and the results (enthalpy
extraction only) are averaged for the timestep being reported.
1.30.9.2.4 Zone Packaged Terminal Air Conditioner Total Cooling Energy [J]
This output field is the total (enthalpy) heat extraction of the packaged terminal air conditioner
from the zone it is serving in Joules over the timestep being reported. This value is calculated using
the enthalpy difference of the air conditioner outlet air and inlet air streams, the air mass flow rate
through the air conditioner, and the HVAC simulation timestep. This value is calculated for each
HVAC system timestep being simulated, and the results (enthalpy extraction only) are summed for
the timestep being reported.
1.30.9.2.5 Zone Packaged Terminal Air Conditioner Sensible Heating Rate [W]
This output field is the sensible heat addition rate of the packaged terminal air conditioner to the
zone it is serving in Watts. This value is calculated using the enthalpy difference of the air conditioner
outlet air and inlet air streams at a constant humidity ratio, and the air mass flow rate through the
air conditioner. This value is calculated for each HVAC system timestep being simulated, and the
results (heating only) are averaged for the timestep being reported.
1.30.9.2.6 Zone Packaged Terminal Air Conditioner Sensible Heating Energy [J]
This output field is the sensible heat addition of the packaged terminal air conditioner to the zone
it is serving in Joules over the timestep being reported. This value is calculated using the enthalpy
difference of the air conditioner outlet air and inlet air streams at a constant humidity ratio, the
air mass flow rate through the air conditioner, and the HVAC simulation timestep. This value
is calculated for each HVAC system timestep being simulated, and the results (heating only) are
summed for the timestep being reported.
1376 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.30.9.2.7 Zone Packaged Terminal Air Conditioner Sensible Cooling Rate [W]
This output field reports the moist air sensible heat extraction rate of the packaged terminal air
conditioner from the zone it is serving in Watts. This value is calculated using the enthalpy difference
of the air conditioner outlet air and inlet air streams at a constant humidity ratio, and the air mass
flow rate through the air conditioner. This value is calculated for each HVAC system timestep being
simulated, and the results (cooling only) are averaged for the timestep being reported.
1.30.9.2.8 Zone Packaged Terminal Air Conditioner Sensible Cooling Energy [J]
This output field reports the moist air sensible heat extraction of the packaged terminal air condi-
tioner from the zone it is serving in Joules over the timestep being reported. This value is calculated
using the enthalpy difference of the air conditioner outlet air and inlet air streams at a constant hu-
midity ratio, the air mass flow rate through the air conditioner, and the HVAC simulation timestep.
This value is calculated for each HVAC system timestep being simulated, and the results (cooling
only) are summed for the timestep being reported.
1.30.9.2.9 Zone Packaged Terminal Air Conditioner Latent Heating Rate [W]
This output field is the latent heat addition (humidification) rate of the packaged terminal air
conditioner to the zone it is serving in Watts. This value is calculated as the difference between the
total energy rate and the sensible energy rate provided by the packaged terminal air conditioner.
This value is calculated for each HVAC system timestep being simulated, and the results (latent
heat addition only) are averaged for the timestep being reported.
1.30.9.2.10 Zone Packaged Terminal Air Conditioner Latent Heating Energy [J]
This output field is the latent heat addition (humidification) of the packaged terminal air conditioner
to the zone it is serving in Joules over the timestep being reported. This value is calculated as the
difference between the total energy delivered to the zone and the sensible energy delivered to the
zone by the packaged terminal air conditioner. This value is calculated for each HVAC system
timestep being simulated, and the results (latent heat addition only) are summed for the timestep
being reported.
1.30.9.2.11 Zone Packaged Terminal Air Conditioner Latent Cooling Rate [W]
This output field is the latent heat extraction (dehumidification) rate of the packaged terminal air
conditioner from the zone it is serving in Watts. This value is calculated as the difference between
the total energy rate and the sensible energy rate provided by the packaged terminal air conditioner.
This value is calculated for each HVAC system timestep being simulated, and the results (latent
heat extraction only) are averaged for the timestep being reported.
1.30.9.2.12 Zone Packaged Terminal Air Conditioner Latent Cooling Energy [J]
This output field is the latent heat extraction (dehumidification) of the packaged terminal air condi-
tioner from the zone it is serving in Joules over the timestep being reported. This value is calculated
1.30. GROUP – ZONE FORCED AIR UNITS 1377
as the difference between the total energy delivered to the zone and the sensible energy delivered to
the zone by the packaged terminal air conditioner. This value is calculated for each HVAC system
timestep being simulated, and the results (latent heat extraction only) are summed for the timestep
being reported.
1.30.9.2.15 Zone Packaged Terminal Air Conditioner Fan Part Load Ratio []
This output field is the part-load ratio of the fan. The fan part-load ratio is defined as the average
supply air mass flow rate divided by the maximum supply air mass flow rate. The maximum supply
air mass flow rate depends on whether heating, cooling, or no heating or cooling is required during
the timestep. This value is calculated for each HVAC system timestep being simulated, and the
results are averaged for the timestep being reported.
1.30.9.2.16 Zone Packaged Terminal Air Conditioner Compressor Part Load Ra-
tio []
This output field is the part-load ratio used by the coils (cooling and heating). Part-load ratio is
defined as the total coil load divided by the coil steady-state capacity. This value is calculated for
each HVAC system timestep being simulated, and the results are averaged for the timestep being
reported.
integers 0 through 3. These integers represent NoAction (0), ForceOff (1), CycleOn (2), and Cy-
cleOnZoneFansOnly (3). Since the status output is averaged, the output result may not correspond
to the values described here when output variable frequencies other than detailed are used. Use the
“detailed” reporting frequency (Ref. Output:Variable object) to view the availability status at each
simulation timestep.
1.30.10 ZoneHVAC:PackagedTerminalHeatPump
The packaged terminal heat pump (PTHP) is a compound object made up of other components.
Each PTHP consists of an outdoor air mixer, direct expansion (DX) cooling coil, DX heating coil,
supply air fan, and a supplemental heating coil as shown in the figure below. These individual
components are described elsewhere in this document. The packaged terminal heat pump coordi-
nates the operation of these components and is modeled as a type of zone equipment (Ref. Zone-
HVAC:EquipmentList and ZoneHVAC:EquipmentConnections).
Figure 1.132: Schematic of a packaged terminal heat pump (draw through fan placement)
Links to the PTHP’s supply air fan, DX coils, supplemental heating coil, and outdoor air mixer
specifications are provided in the heat pump’s input syntax. Additional inputs include supply and
outdoor air flow rates during cooling operation, heating operation, and when neither cooling or
heating is required. A description of each input field for the packaged terminal heat pump compound
object is provided below.
1.30.10.1 Inputs
– OutdoorAir:Mixer
This input field should be left blank when the PTHP is connected to an AirTermi-
nal:SingleDuct:Mixer object. If this field is left blank, an outdoor air mixer object is not
simulated.
mode (see Supply Air Fan Operating Mode Schedule field below). The input requirements for these
fan objects are described elsewhere in this document.
The maximum number of iterations is limited, with a warning message generated if the above
equation is not satisfied within the maximum number of iterations.
– Coil:Cooling:DX:SingleSpeed
– CoilSystem:Cooling:DX:HeatExchangerAssisted
– Coil:Cooling:DX:VariableSpeed
– Coil:Heating:Electric
– Coil:Heating:Fuel
– Coil:Heating:Water
– Coil:Heating:Steam
ZoneHVAC:PackagedTerminalHeatPump ,
Zone2PTHP , !- Name
FanAndCoilAvailSched , !- Availability Schedule Name
Zone2PTHPAirInletNode , !- Air Inlet Node Name
1.30. GROUP – ZONE FORCED AIR UNITS 1385
Schedule:Compact ,
CyclingFanSch , !- Name
Fraction , !- ScheduleType
Through: 12/31 , !- Complex Field \#1
For: AllDays , !- Complex Field \#2
Until: 24:00 , !- Complex Field \#7
0.0; !- Complex Field \#8
OutdoorAir:Mixer ,
Zone2PTHPOAMixer , !- Name
Zone2PTHPOAMixerOutletNode , !-Mixed Air Node Name
Zone2PTHPOAInNode , !-Outdoor Air Stream Node Name
Zone2PTHPExhNode , !- Relief Air Stream Node Name
Zone2PTHPAirInletNode ; !- Return Air Stream Node Name
Fan:OnOff ,
Zone2PTHPFan , !- Name
FanAndCoilAvailSched , !- Availability Schedule Name
0.5, !- Fan Total Efficiency
75.0, !- Pressure Rise {Pa}
autosize , !- Maximum Flow Rate {m3/s}
0.9, !- Motor Efficiency
1.0, !- Motor In Airstream Fraction
Zone2PTHPOAMixerOutletNode , !- Air Inlet Node Name
Zone2PTHPFanOutletNode ; !- Air Outlet Node Name
Coil:Cooling:DX:SingleSpeed ,
Zone2PTHPDXCoolCoil , !- Coil Name
CoolingCoilAvailSched , !- Availability Schedule
autosize , !- Rated Total Cooling Capacity (gross) {W}
autosize , !- Rated SHR
3.0, !- Rated COP
autosize , !- Rated Air Volume Flow Rate {m3/s}
Zone2PTHPFanOutletNode , !- Coil Air Inlet Node
Zone2PTHPCoolCoilOutletNode , !- Coil Air Outlet Node
HPACCoolCapFT , !- Total Cooling Capacity Modifier Curve (function of
temperature)
HPACCoolCapFFF , !- Total Cooling Capacity Modifier Curve (function of flow
fraction)
HPACEIRFT , !- Energy Input Ratio Modifier Curve (function of temperature)
HPACEIRFFF , !- Energy Input Ratio Modifier Curve (function of flow fraction)
HPACPLFFPLR; !- Part Load Fraction Correlation (function of part load ratio)
COIL:Heating:DX:SingleSpeed ,
1386 CHAPTER 1. INPUT-OUTPUT REFERENCE
Coil:Heating:Electric ,
Zone2PTHPSupHeater , !- Name
HeatingCoilAvailSched , !- Availability Schedule Name
1.0, !- Efficiency
autosize , !- Nominal Capacity {W}
Zone2PTHPDXHeatCoilOutletNode , !- Air Inlet Node Name
Zone2PTHPAirOutletNode ; !- Air Outlet Node Name
1.30.10.2 Outputs
1.30.10.2.1 Zone Packaged Terminal Heat Pump Total Heating Rate [W]
This output field is the total (enthalpy) heat addition rate of the packaged terminal heat pump to
the zone it is serving in Watts. This value is calculated using the enthalpy difference of the heat
pump outlet air and inlet air streams, and the air mass flow rate through the heat pump. This value
is calculated for each HVAC system timestep being simulated, and the results (enthalpy addition
only) are averaged for the timestep being reported.
1.30.10.2.2 Zone Packaged Terminal Heat Pump Total Heating Energy [J]
This output field is the total (enthalpy) heat addition of the packaged terminal heat pump to the
zone it is serving in Joules over the timestep being reported. This value is calculated using the
enthalpy difference of the heat pump outlet air and inlet air streams, the air mass flow rate through
the heat pump, and the HVAC simulation timestep. This value is calculated for each HVAC system
timestep being simulated, and the results (enthalpy addition only) are summed for the timestep
being reported.
1.30.10.2.3 Zone Packaged Terminal Heat Pump Total Cooling Rate [W]
This output field is the total (enthalpy) heat extraction rate of the packaged terminal heat pump
from the zone it is serving in Watts. This value is calculated using the enthalpy difference of the heat
pump outlet air and inlet air streams, and the air mass flow rate through the heat pump. This value
is calculated for each HVAC system timestep being simulated, and the results (enthalpy extraction
only) are averaged for the timestep being reported.
1.30.10.2.4 Zone Packaged Terminal Heat Pump Total Cooling Energy [J]
This output field is the total (enthalpy) heat extraction of the packaged terminal heat pump from
the zone it is serving in Joules over the timestep being reported. This value is calculated using the
enthalpy difference of the heat pump outlet air and inlet air streams, the air mass flow rate through
the heat pump, and the HVAC simulation timestep. This value is calculated for each HVAC system
timestep being simulated, and the results (enthalpy extraction only) are summed for the timestep
being reported.
1.30.10.2.5 Zone Packaged Terminal Heat Pump Sensible Heating Rate [W]
This output field is the sensible heat addition rate of the packaged terminal heat pump to the zone
it is serving in Watts. This value is calculated using the enthalpy difference of the heat pump outlet
air and inlet air streams at a constant humidity ratio, and the air mass flow rate through the heat
pump. This value is calculated for each HVAC system timestep being simulated, and the results
(heating only) are averaged for the timestep being reported.
1.30.10.2.6 Zone Packaged Terminal Heat Pump Sensible Heating Energy [J]
This output field is the sensible heat addition of the packaged terminal heat pump to the zone it
is serving in Joules over the timestep being reported. This value is calculated using the enthalpy
difference of the heat pump outlet air and inlet air streams at a constant humidity ratio, the air
mass flow rate through the heat pump, and the HVAC simulation timestep. This value is calculated
for each HVAC system timestep being simulated, and the results (heating only) are summed for the
timestep being reported.
1388 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.30.10.2.7 Zone Packaged Terminal Heat Pump Sensible Cooling Rate [W]
This output field reports the moist air sensible heat extraction rate of the packaged terminal heat
pump from the zone it is serving in Watts. This value is calculated using the enthalpy difference
of the heat pump outlet air and inlet air streams at a constant humidity ratio, and the air mass
flow rate through the heat pump. This value is calculated for each HVAC system timestep being
simulated, and the results (cooling only) are averaged for the timestep being reported.
1.30.10.2.8 Zone Packaged Terminal Heat Pump Sensible Cooling Energy [J]
This output field reports the moist air sensible heat extraction of the packaged terminal heat pump
from the zone it is serving in Joules over the timestep being reported. This value is calculated using
the enthalpy difference of the heat pump outlet air and inlet air streams at a constant humidity
ratio, the air mass flow rate through the heat pump, and the HVAC simulation timestep. This value
is calculated for each HVAC system timestep being simulated, and the results (cooling only) are
summed for the timestep being reported.
1.30.10.2.9 Zone Packaged Terminal Heat Pump Latent Heating Rate [W]
This output field is the latent heat addition (humidification) rate of the packaged terminal heat
pump to the zone it is serving in Watts. This value is calculated as the difference between the total
energy rate and the sensible energy rate provided by the packaged terminal heat pump. This value
is calculated for each HVAC system timestep being simulated, and the results (latent heat addition
only) are averaged for the timestep being reported.
1.30.10.2.10 Zone Packaged Terminal Heat Pump Latent Heating Energy [J]
This output field is the latent heat addition (humidification) of the packaged terminal heat pump
to the zone it is serving in Joules over the timestep being reported. This value is calculated as the
difference between the total energy delivered to the zone and the sensible energy delivered to the zone
by the packaged terminal heat pump. This value is calculated for each HVAC system timestep being
simulated, and the results (latent heat addition only) are summed for the timestep being reported.
1.30.10.2.11 Zone Packaged Terminal Heat Pump Latent Cooling Rate [W]
This output field is the latent heat extraction (dehumidification) rate of the packaged terminal heat
pump from the zone it is serving in Watts. This value is calculated as the difference between the
total energy rate and the sensible energy rate provided by the packaged terminal heat pump. This
value is calculated for each HVAC system timestep being simulated, and the results (latent heat
extraction only) are averaged for the timestep being reported.
1.30.10.2.12 Zone Packaged Terminal Heat Pump Latent Cooling Energy [J]
This output field is the latent heat extraction (dehumidification) of the packaged terminal heat pump
from the zone it is serving in Joules over the timestep being reported. This value is calculated as
the difference between the total energy delivered to the zone and the sensible energy delivered to the
zone by the packaged terminal heat pump. This value is calculated for each HVAC system timestep
being simulated, and the results (latent heat extraction only) are summed for the timestep being
reported.
1.30. GROUP – ZONE FORCED AIR UNITS 1389
1.30.10.2.15 Zone Packaged Terminal Heat Pump Fan Part Load Ratio []
This output field is the part-load ratio of the fan. The fan part-load ratio is defined as the average
supply air mass flow rate divided by the maximum supply air mass flow rate. The maximum supply
air mass flow rate depends on whether heating, cooling, or no heating or cooling is required during
the timestep. This value is calculated for each HVAC system timestep being simulated, and the
results are averaged for the timestep being reported.
1.30.10.2.16 Zone Packaged Terminal Heat Pump Compressor Part Load Ratio
[]
This output field is the part-load ratio of the compressor used by the DX coils (cooling and heating).
Compressor part-load ratio is defined as the total coil load divided by the coil steady-state capacity.
This value is calculated for each HVAC system timestep being simulated, and the results are averaged
for the timestep being reported.
1.30.11 ZoneHVAC:RefrigerationChillerSet
The ZoneHVAC:RefrigerationChillerSet object works in conjunction with one or multiple air
chillers, compressor racks, refrigeration systems, or refrigeration secondary system objects
(Ref. Refrigeration:AirChiller Refrigeration:CompressorRack, Refrigeration:System, or Refrigera-
tion:SecondarySystem) to simulate the performance of a group of air chillers cooling a single zone.
The chiller set model passes information about the zone conditions to determine the performance
of individual chiller coils within the set, thus providing the sensible and latent heat exchange with
the zone environment.
The refrigeration chiller set object inputs include a name, an availability schedule name, the name
of the zone cooled by the chiller set, the air inlet node name, the air outlet node name, and an
extensible list of air chiller names (Ref. Refrigeration:AirChiller).
1.30.11.1 Inputs
ZoneHVAC:RefrigerationChillerSet ,
SubFreezerChillerSet , !- Name
, !- Availability Schedule Name
SubFreezer , !- Zone Name
NODE_142 , !- Air Inlet Node Name
NODE_141 , !- Air Outlet Node Name
SubFreezerAirChiller_1 , !- Air Chiller \#1 Name
SubFreezerAirChiller_2 , !- Air Chiller \#2 Name
SubFreezerAirChiller_3 ; !- Air Chiller \#3 Name
There are no outputs variables for a ZoneHVAC:RefrigerationChillerSet. Outputs for the refrigera-
tion impact on any zone are listed in the Group:Refrigeration.
1.30.12 ZoneHVAC:WaterToAirHeatPump
The zone water-to-air heat pump is a compound component consisting of a fan, water-to-air cooling
and heating coils, and a supplemental heating coil. Links to the fan, WaterToAirHeatPump cooling
coil, WaterToAirHeatPump heating coil, and supplementary heating coil specifications are provided
in the heat pump’s input data syntax. The heat pump switches between cooling and heating de-
pending on the zone’s demand. The load side (air) of the zone water-to-air heat pump consists of an
On/Off fan component, a WaterToAirHeatPump cooling coil component, a WaterToAirHeatPump
heating coil component, and a Gas or Electric supplemental heating coil component. The source
side (water) of the heat pump is connected to a condenser loop with a heat exchanger (ground
heat exchanger or other type) or a plant loop with a heating source such as a boiler and a cooling
source such as a chiller or cooling tower. The diagram below shows the setup and connection of
the heat pump for the source side and load side for a ground heat exchanger configuration. Note
that on the load side, the WaterToAirHeatPump cooling coil must always be placed before the
WaterToAirHeatPump heating coil.
For this zone heat pump,there are two types of WaterToAirHeatPump coil model allowed:
– Coil:Cooling:WaterToAirHeatPump:EquationFit
– Coil:Heating:WaterToAirHeatPump:EquationFit
– Coil:Cooling:WaterToAirHeatPump:VariableSpeedEquationFit
– Coil:Heating:WaterToAirHeatPump:VariableSpeedEquationFit
1392 CHAPTER 1. INPUT-OUTPUT REFERENCE
Figure 1.133: Zone Water to Air Heat Pump Schematic for a DrawThrough Configuration with
Ground Heat Exchanger
1.30. GROUP – ZONE FORCED AIR UNITS 1393
1.30.12.1 Inputs
– OutdoorAir:Mixer
This input field should be left blank when the WaterToAirHeatPump is connected to an AirTermi-
nal:SingleDuct:Mixer object. If this field is left blank, an outdoor air mixer object is not simulated.
1.30.12.1.12 Field: No Load Outdoor Air Flow Rate When No Cooling or Heat-
ing is Needed
This numeric field defines the outdoor air flow rate through the heat pump in cubic meters per second
when neither cooling or heating is required (i.e., DX coils and supplemental heater are off but the
supply air fan operates). Values must be greater than or equal to 0, or this field is autosizable. Note
that the no load outdoor air flow rate cannot change during the simulation. In addition, the no load
outdoor air flow rate cannot be greater than the heat pump’s no load supply air flow rate. This
field is only used when the heat pump’s supply air fan operating mode schedule specifies continuous
fan operation. If the heat pump’s supply air fan operating mode schedule specifies continuous fan
operation and the field “No Load Supply Air Flow Rate” is set to zero or is left blank, then the
model assumes that the no load outdoor air flow rate is equal to the outdoor air flow rate when the
cooling or heating coil was last operating (for cooling operation [i.e., Cooling outdoor air flow rate]
or heating operation [i.e., Heating outdoor air flow rate]) and this field is not used. This input field
1.30. GROUP – ZONE FORCED AIR UNITS 1395
Figure 1.134:
Figure 1.135:
Figure 1.136:
– Coil:Heating:Electric
– Coil:Heating:Fuel
1.30. GROUP – ZONE FORCED AIR UNITS 1397
– Coil:Heating:Water
– Coil:Heating:Steam
– On/Off fan
– WatertoAirHeatPump cooling coil (EquationFit only)
– WatertoAirHeatPump heating coil (EquationFit only)
– Supplementary heating coil
– Outdoor air mixer
– Condenser loop or plant loop demand branches
– Cycling
– Constant
– CyclingOnDemand
Cycling varies water flow through the coil based on the heat pump Part Load Ratio. This control
method is appropriate for modeling heat pumps that are outfitted with a soleniod valve which allows
water to flow through the coil only when the compressor is active. This is the default for EnergyPlus
V8 and later.
Constant provides a constant water flow regardless of heat pump operation. Remember that En-
ergyPlus has two coils (a heating coil and a cooling coil) to approximate the operation of one coil
that can operate in either heating mode or cooling mode. Therefore, when the water flow mode is
constant, there will be full flow through either the heating coil or the cooling coil, but not both at
the same time.
ConstantOnDemand provides full flow through the coil whenever there is a load. When there is
no load, there is zero flow through the coil. This control strategy represents the way EnergyPlus
modeled heat pump water flow prior to Version 8.
ZoneHVAC:WaterToAirHeatPump ,
Zone1WTAHP , !- Name
FanAndCoilAvailSched , !- Availability Schedule Name
Zone 1 Outlet Node , !- Air Inlet Node Name
Zone 1 Inlet Node , !- Air Outlet Node Name
OutdoorAir:Mixer , !- Outdoor air mixer object type
Zone 1 Mixer , !- Outdoor Air Mixer Name
Autosize , !- Cooling Supply Air Flow Rate {m3/s}
Autosize , !- Heating Supply Air Flow Rate {m3/s}
, !- No Load Supply Air Flow Rate {m3/s}
0.0, !- Cooling Outdoor Air Flow Rate {m3/s}
0.0, !- Heating Outdoor Air Flow Rate {m3/s}
, !- No Load Outdoor Air Flow Rate {m3/s}
Fan:OnOff , !- Supply Air Fan Object Type
Zone 1 Fan , !- Supply Air Fan Name
Coil:Heating: WaterToAirHeatPump :EquationFit , !- Heating Coil Object Type
Sys 1 Heat Pump Heating Mode , !- Heating Coil Name
Coil:Cooling: WaterToAirHeatPump :EquationFit , !- Cooling Coil Object Type
Sys 1 Heat Pump Cooling Mode , !- Cooling Coil Name
2.5, !- Maximum Cycling Rate
60.0, !- Heat Pump Time Constant
0.01, !- Fraction of On -Cycle Power Use
60, !- Heat Pump Fan Delay Time
Coil:Heating:Fuel , !- Supplemental Heating Coil Object Type
Heat Pump DX Supp Heating Coil 1, !- Supplemental Heating Coil Name
60.0, !- Maximum Supply Air Temperature from Supplemental Heater {C}
20.0, !- Maximum Outdoor Dry -Bulb Temperature for Supplemental Heater Operation
{C}
Sys 1 Outside Air Inlet Node , !- Outdoor Dry -Bulb Temperature Sensor Node Name
BlowThrough , !- Fan Placement
CyclingFanSch; !- Supply Air Fan Operating Mode Schedule Name
Schedule:Compact ,
CyclingFanSch , !- Name
Fraction , !- Schedule Type Limits Name
Through: 12/31 , !- Field 1
For: AllDays , !- Field 2
Until: 24:00 , !- Field 3
0.0; !- Field 4
OutdoorAir:Mixer ,
Zone 1 Mixer , !- Name
Sys 1 Mixed Air Node , !- Mixed Air Node Name
Sys 1 Outside Air Inlet Node , !- Outdoor Air Stream Node Name
Sys 1 Relief Air Outlet Node , !- Relief Air Stream Node Name
Zone 1 Outlet Node; !- Return Air Stream Node Name
Fan:OnOff ,
1400 CHAPTER 1. INPUT-OUTPUT REFERENCE
Coil:Heating:Fuel ,
Heat Pump DX Supp Heating Coil 1, !- Name
FanAndCoilAvailSched , !- Availability Schedule Name
NaturalGas , !- Fuel Type
0.8, !- Gas Burner Efficiency
32000 , !- Nominal Capacity {W}
Sys 1 SuppHeating Coil Air Inlet Node , !- Air Inlet Node Name
Zone 1 Inlet Node; !-Air Outlet Node Name
BRANCH ,
Gshp Cooling Condenser Branch , !- Name
, !- Pressure Drop Curve Name
Coil:Cooling: WaterToAirHeatPump :ParameterEstimation , !- Component 1 Object Type
Heat Pump Cooling Mode , !- Component 1 Name
Water to Air Heat Pump Source Side1 Inlet Node , !- Component 1 Inlet Node Name
Water to Air Heat Pump Source Side1 Outlet Node; !- Component 1 Outlet Node Name
BRANCH ,
Gshp Heating Condenser Branch , !- Name
, !- Pressure Drop Curve Name
Coil:Heating: WaterToAirHeatPump :ParameterEstimation , !- Component 1 Object Type
Heat Pump Heating Mode , !- Component 1 Name
Water to Air Heat Pump Source Side2 Inlet Node , !- Component 1 Inlet Node Name
Water to Air Heat Pump Source Side2 Outlet Node; !- Component 1 Outlet Node Name
1.30.12.2 Outputs
1.30.12.2.1 Zone Water to Air Heat Pump Total Heating Rate [W]
This output field is the total (enthalpy) heat addition rate of the Water to Air Heat Pump to the
zone it is serving in Watts. This value is calculated using the enthalpy difference of the heat pump
outlet air and inlet air streams, and the air mass flow rate through the heat pump. This value is
calculated for each HVAC system time step being simulated, and the results (enthalpy addition only)
are averaged for the time step being reported.
1.30.12.2.2 Zone Water to Air Heat Pump Total Heating Energy [J]
This output field is the total (enthalpy) heat addition of the Water to Air Heat Pump to the zone
it is serving in Joules over the time step being reported. This value is calculated using the enthalpy
difference of the heat pump outlet air and inlet air streams, the air mass flow rate through the heat
pump, and the HVAC simulation time step. This value is calculated for each HVAC system time
step being simulated, and the results (enthalpy addition only) are summed for the time step being
reported.
1.30.12.2.3 Zone Water to Air Heat Pump Total Cooling Rate [W]
This output field is the total (enthalpy) heat extraction rate of the Water to Air Heat Pump from
the zone it is serving in Watts. This value is calculated using the enthalpy difference of the heat
pump outlet air and inlet air streams, and the air mass flow rate through the heat pump. This value
is calculated for each HVAC system time step being simulated, and the results (enthalpy extraction
only) are averaged for the time step being reported.
1.30.12.2.4 Zone Water to Air Heat Pump Total Cooling Energy [J]
This output field is the total (enthalpy) heat extraction of the Water to Air Heat Pump from the
zone it is serving in Joules over the time step being reported. This value is calculated using the
enthalpy difference of the heat pump outlet air and inlet air streams, the air mass flow rate through
the heat pump, and the HVAC simulation time step. This value is calculated for each HVAC system
time step being simulated, and the results (enthalpy extraction only) are summed for the time step
being reported.
1.30.12.2.5 Zone Water to Air Heat Pump Sensible Heating Rate [W]
This output field is the sensible heat addition rate of the Water to Air Heat Pump to the zone it
is serving in Watts. This value is calculated using the enthalpy difference of the heat pump outlet
air and inlet air streams at a constant humidity ratio, and the air mass flow rate through the heat
pump. This value is calculated for each HVAC system time step being simulated, and the results
(heating only) are averaged for the time step being reported.
1.30.12.2.6 Zone Water to Air Heat Pump Sensible Heating Energy [J]
This output field is the sensible heat addition of the Water to Air Heat Pump to the zone it is serving
in Joules over the time step being reported. This value is calculated using the enthalpy difference
of the heat pump outlet air and inlet air streams at a constant humidity ratio, the air mass flow
rate through the heat pump, and the HVAC simulation time step. This value is calculated for each
HVAC system time step being simulated, and the results (heating only) are summed for the time
step being reported.
1402 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.30.12.2.7 Zone Water to Air Heat Pump Sensible Cooling Rate [W]
This output field reports the moist air sensible heat extraction rate of the Water to Air Heat Pump
from the zone it is serving in Watts. This value is calculated using the enthalpy difference of the
heat pump outlet air and inlet air streams at a constant humidity ratio, and the air mass flow rate
through the heat pump. This value is calculated for each HVAC system time step being simulated,
and the results (cooling only) are averaged for the time step being reported.
1.30.12.2.8 Zone Water to Air Heat Pump Sensible Cooling Energy [J]
This output field reports the moist air sensible heat extraction of the Water to Air Heat Pump from
the zone it is serving in Joules over the time step being reported. This value is calculated using the
enthalpy difference of the heat pump outlet air and inlet air streams at a constant humidity ratio,
the air mass flow rate through the heat pump, and the HVAC simulation time step. This value
is calculated for each HVAC system time step being simulated, and the results (cooling only) are
summed for the time step being reported.
1.30.12.2.9 Zone Water to Air Heat Pump Latent Heating Rate [W]
This output field is the latent heat addition (humidification) rate of the Water to Air Heat Pump to
the zone it is serving in Watts. This value is calculated as the difference between the total energy
rate and the sensible energy rate provided by the WaterToAirHP heat pump. This value is calculated
for each HVAC system time step being simulated, and the results (latent heat addition only) are
averaged for the time step being reported.
1.30.12.2.10 Zone Water to Air Heat Pump Latent Heating Energy [J]
This output field is the latent heat addition (humidification) of the Water to Air Heat Pump to
the zone it is serving in Joules over the time step being reported. This value is calculated as the
difference between the total energy delivered to the zone and the sensible energy delivered to the
zone by the WaterToAirHP heat pump. This value is calculated for each HVAC system time step
being simulated, and the results (latent heat addition only) are summed for the time step being
reported.
1.30.12.2.11 Zone Water to Air Heat Pump Latent Cooling Rate [W]
This output field is the latent heat extraction (dehumidification) rate of the Water to Air Heat Pump
from the zone it is serving in Watts. This value is calculated as the difference between the total
energy rate and the sensible energy rate provided by the WaterToAirHP heat pump. This value is
calculated for each HVAC system time step being simulated, and the results (latent heat extraction
only) are averaged for the time step being reported.
1.30.12.2.12 Zone Water to Air Heat Pump Latent Cooling Energy [J]
This output field is the latent heat extraction (dehumidification) of the Water to Air Heat Pump
from the zone it is serving in Joules over the time step being reported. This value is calculated as
the difference between the total energy delivered to the zone and the sensible energy delivered to the
zone by the WaterToAirHP heat pump. This value is calculated for each HVAC system time step
being simulated, and the results (latent heat extraction only) are summed for the time step being
reported.
1.30. GROUP – ZONE FORCED AIR UNITS 1403
1.30.12.2.15 Zone Water to Air Heat Pump Fan Part Load Ratio []
This output field is the part-load ratio of the fan. The fan part-load ratio is defined as the average
supply air mass flow rate divided by the maximum supply air mass flow rate. The maximum supply
air mass flow rate depends on whether heating, cooling, or no heating or cooling is required during
the time step. This value is calculated for each HVAC system time step being simulated, and the
results are averaged for the time step being reported.
1.30.12.2.16 Zone Water to Air Heat Pump Compressor Part Load Ratio []
This output field is the part-load ratio of the compressor used by the DX coils (cooling and heating).
Compressor part-load ratio is defined as the total coil load divided by the coil steady-state capacity.
This value is calculated for each HVAC system time step being simulated, and the results are averaged
for the time step being reported.
1.30.13 ZoneHVAC:Dehumidifier:DX
This object can be used for modeling conventional mechanical dehumidifiers. These systems use a
direct expansion (DX) cooling coil to cool and dehumidify an airstream. Heat from the DX system’s
1404 CHAPTER 1. INPUT-OUTPUT REFERENCE
condenser section is rejected into the cool/dehumidified airstream, resulting in warm dry air being
supplied from the unit. In EnergyPlus, this object is modeled as a type of zone equipment (ref.
ZoneHVAC:EquipmentList and ZoneHVAC:EquipmentConnections).
The model has inputs for water removal, energy factor and air flow rate at rated conditions (26.7◦C,
60% RH). Curve objects must be specified to describe performance at off-rated conditions. A part-
load cycling curve input must also be specified to account for inefficiencies due to cycling. Other
inputs including minimum and maximum operating temperatures for dehumidifier operation, off-
cycle parasitic load, and an input to direct the removed water to a storage tank.
The model assumes that this equipment dehumidifies and heats the air. If used in tandem with an-
other system that cools and dehumidifies the zone air, then the zone dehumidifier should be specified
as the lowest cooling priority in the ZoneHVAC:EquipmentList object for best control of zone tem-
perature and humidity levels (e.g., if there are 3 pieces of equipment in ZoneHVAC:EquipmentList,
then the zone dehumidifier should have Cooling Priority = 3). With this zone equipment prioriti-
zation, the other cooling and dehumidification system would operate first to meet the temperature
setpoint (and possibly meet the high humidity setpoint as well). If additional dehumidification is
needed, then the zone dehumidifier would operate. The sensible heat generated by the dehumidifier
is carried over to the zone air heat balance for the next HVAC time step.
1.30.13.1 Inputs
This alpha field defines the name of the schedule (ref: Schedule) that denotes whether the dehumid-
ifier operates during a given time period. A schedule value equal to 0 denotes that the dehumidifier
will not operate for that time period. A value greater than 0 denotes that the dehumidifier is avail-
able to operate during that time period. If this field is left blank, the schedule has a value of 1 for
all time periods.
ZoneHVAC:Dehumidifier:DX ,
North Zone Dehumidifier , !- Name
ON , !- Availability Schedule Name
Zone3DehumidifierInlet , !- Air Inlet Node Name
Dehumidifier Outlet Node , !- Air Outlet Node Name
50.16 , !- Rated Water Removal {L/day} (106 pints/day)
3.412 , !- Rated Energy Factor {L/kWh} (7.21 pints/kWh)
0.12036 , !- Rated Air Flow Rate {m3/s} (255 cfm)
ZoneDehumidWaterRemoval , !- Water Removal Curve Name
ZoneDehumidEnergyFactor , !- Energy Factor Curve Name
ZoneDehumidPLFFPLR , !- Part Load Fraction Correlation Curve Name
10.0, !- Minimum Dry -Bulb Temperature for Compressor Operation {C}
32.0, !- Maximum Dry -Bulb Temperature for Compressor Operation {C}
0.0; !- Off Cycle Parasitic Electric Load {W}
ZoneControl:Humidistat ,
Zone 3 Humidistat , !- Name
NORTH ZONE , !- Zone Name
Seasonal Relative Humidity Sch; !- Relative Humidity Setpoint Schedule Name
1.30.13.2 Outputs
1.30.14 ZoneHVAC:EnergyRecoveryVentilator
The ZoneHVAC:EnergyRecoveryVentilator - stand alone energy recovery ventilator (ERV) is a single-
zone HVAC component used for exhaust air heat recovery (Figure 1.138). This compound object
consists of 3 required components: a generic air-to-air heat exchanger (see object Heat Exchanger:Air
to Air:Generic), a supply air fan, and an exhaust air fan (see object Fan:OnOff).
An optional controller (see object ZoneHVAC:EnergyRecoveryVentilator:Controller) may be used to
simulate economizer (free cooling) operation, modify air flow rates based on high indoor humidity,
or simulate a “push-button” type economizer controller.
This compound object models the basic operation of supply and exhaust air fans and an air-to-
air heat exchanger. The stand alone ERV operates whenever the unit is scheduled to be available
1410 CHAPTER 1. INPUT-OUTPUT REFERENCE
(Availability schedule). The stand alone ERV object can be used in conjunction with an economizer
feature whereby heat exchange is suspended whenever free cooling is available (i.e., air flow is fully
bypassed around a fixed-plate heat exchanger or the rotation of a rotary heat exchanger is stopped).
The economizer feature may also be activated based on a time-of-day schedule. Heat exchange is
also suspended when air flow rates through the heat exchanger are modified in response to a zone
humidistat. When an economizer is used in conjunction with high humidity control, high humidity
control has the priority.
To model a stand alone ERV connected to a single zone, the input data file should include the
following objects:
– ZoneHVAC:EnergyRecoveryVentilator
– HeatExchanger:AirToAir:SensibleAndLatent
– Fan:OnOff (supply air)
– Fan:OnOff (exhaust air)
– ZoneHVAC:EnergyRecoveryVentilator:Controller (if economizer [free cooling] mode or high hu-
midity control operation is desired)
– ZoneControl:Humidistat (required for high humidity control option)
– SetpointManager:Scheduled (if supply air outlet temperature control is used, Ref. Heat Ex-
changer:Air to Air:Generic for additional guidance)
– ZoneHVAC:EquipmentConnections
– ZoneHVAC:EquipmentList
– OutdoorAir:NodeList
A description of each input field for this compound object is provided below.
1.30. GROUP – ZONE FORCED AIR UNITS 1411
1.30.14.1 Inputs
Note that this flow rate must be within the valid air flow range for the heat exchanger (ref: Hea-
tExchanger:AirToAir:SensibleAndLatent in the Engineering Document). In addition, this flow rate
must be less than or equal to the exhaust fan air flow rate (Fan:OnOff). If the exhaust air flow rate is
greater than the supply air flow rate, the zone infiltration (ref: ZoneInfiltration) should be specified
accordingly (the infiltration induced by imbalanced air flows is not accounted for automatically).
The ERV exhaust air flow rate may also be autosized using the ventilation rate per floor area and/or
ventilation rate per occupant fields below. When autosizing, the heat exchanger and fan air flow
rates should also be autosized.
Note: The exhaust air inlet node specified in the generic heat exchanger object must be a zone air
exhaust node (ref: ZoneHVAC:EquipmentConnections).
ZoneHVAC:EnergyRecoveryVentilator ,
Stand Alone ERV 1, !- Stand alone ERV name
FanAndCoilAvailSched , !- Availability schedule name
OA Heat Recovery 1, !- Heat exchanger name
0.05, !- Supply air flow rate {m3/s}
0.05, !- Exhaust air flow rate {m3/s}
Stand Alone ERV Supply Fan , !- Supply air fan name
1.30. GROUP – ZONE FORCED AIR UNITS 1413
OutdoorAir:NodeLine ,
OutsideAirInletNodes ; !- 1st Node name or node list name
NodeList ,
OutsideAirInletNodes , !- Node List Name
ERV Outdoor air Inlet Node; !- Node_ID_1
ZoneHVAC:EquipmentConnections ,
RESISTIVE ZONE , !- Zone Name
Zone1Equipment , !- List Name: Zone Equipment
Zone1Inlets , !- List Name: Zone Inlet Nodes
Zone1Exhausts , !- List Name: Zone Exhaust Nodes
Zone 1 Node , !- Zone Air Node Name
Zone 1 Outlet Node; !- Zone Return Air Node Name
ZoneHVAC:EquipmentList ,
Zone1Equipment , !-Name
ZoneHVAC:EnergyRecoveryVentilator , !- KEY --Zone Equipment Type 1
Stand Alone ERV 1, !- Type Name 1
1, !- Cooling Priority
1; !- Heating Priority
NodeList ,
Zone1Inlets , !- Node List Name
Stand Alone ERV Supply Fan Outlet Node; !- Node_ID_1
NodeList ,
Zone1Exhausts , !- Node List Name
Zone 1 Exhaust Node; !- Node_ID_1
HeatExchanger:AirToAir:SensibleAndLatent ,
OA Heat Recovery 1, !- Heat exchanger name
FanAndCoilAvailSched , !- Availability schedule name
0.05, !- Nominal supply air flow rate {m3/s}
.76, !- Sensible effectiveness at 100% airflow heating condition
.68, !- Latent effectiveness at 100% airflow heating condition
.81, !- Sensible effectiveness at 75% airflow heating condition
.73, !- Latent effectiveness at 75% airflow heating condition
.76, !- Sensible effectiveness at 100% airflow cooling condition
.68, !- Latent effectiveness at 100% airflow cooling condition
.81, !- Sensible effectiveness at 75% airflow cooling condition
.73, !- Latent effectiveness at 75% airflow cooling condition
ERV Outdoor air Inlet Node , !- Supply air inlet node name
Heat Recovery Outlet Node , !- Supply air outlet node name
Zone 1 Exhaust Node , !- Exhaust air inlet node name
Heat Recovery Secondary Outlet Node , !- Exhaust air outlet node name
1414 CHAPTER 1. INPUT-OUTPUT REFERENCE
Fan:OnOff ,
Stand Alone ERV Supply Fan , !- Fan Name
FanAndCoilAvailSched , !- Availability Schedule Name
0.5, !- Fan Total Efficiency
75.0, !- Delta Pressure {Pa}
0.05, !- Max Flow Rate {m3/s}
0.9, !- Motor Efficiency
1.0, !- Motor In Airstream Fraction
Heat Recovery Outlet Node , !- Fan_Inlet_Node
Stand Alone ERV Supply Fan Outlet Node; !- Fan_Outlet_Node
Fan:OnOff ,
Stand Alone ERV Exhaust Fan , !- Fan Name
FanAndCoilAvailSched , !- Availability Schedule Name
0.5, !- Fan Total Efficiency
75.0, !- Delta Pressure {Pa}
0.05, !- Max Flow Rate {m3/s}
0.9, !- Motor Efficiency
1.0, !- Motor In Airstream Fraction
Heat Recovery Secondary Outlet Node , !- Fan_Inlet_Node
Stand Alone ERV Exhaust Fan Outlet Node; !- Fan_Outlet_Node
SetpointManager:Scheduled ,
Heat Exhchanger Supply Air Temp Manager , !- Name
Temperature , !- Control variable
Heat Exchanger Supply Air Temp Sch , !- Schedule Name
Heat Exchanger Supply Air Nodes; !- Name of the set point Node List
NodeList ,
Heat Exchanger Supply Air Nodes , !- Node List Name
Heat Recovery Outlet Node; !- Node_ID_1
1.30.14.2 Outputs
1.30.15 ZoneHVAC:TerminalUnit:VariableRefrigerantFlow
Terminal units with variable refrigerant flow compound HVAC object are used exclusively with vari-
able refrigerant flow (VRF) air conditioning systems (Ref. AirConditioner:VariableRefrigerantFlow
objects). The VRF terminal unit may be used as zone, air loop or outside air system equipment.
The VRF terminal unit compound object contains an optional outdoor air mixer, a DX cooling coil,
a DX heating coil, a supply fan (optional for air loop and outdoor air system equipment), and an
optional supplemental heating coil object.
Note: The terminal unit may be used in the air loop and/or outdoor air system, however, at
this time only constant flow (or limited variation within the limits allowed for DX coils) through
the unit is allowed. Using a wide range of outdoor air flow rates will cause the DX coil model
to fail. For example, if the minimum outdoor air flow rate is allowed to fall near 0, the DX
coil model will calculate very low, even very negative, coil outlet temperatures. This can cause
psychrometric warnings to occur and cause the simulation to end prematurely.
1418 CHAPTER 1. INPUT-OUTPUT REFERENCE
For zone equipment the terminal units are connected to a zone using the inlet and exhaust node
names specified in a ZoneHVAC:EquipmentConnections object. The zone exhaust node has the
same name as the terminal unit air inlet node. The zone inlet node has the same name as the
terminal unit air outlet node. The zone terminal unit is also listed in a zone’s equipment list and
will typically be the first equipment operating for both cooling and heating (i.e., Sequence = 1 in
the ZoneHVAC:EquipmentList). Other ZoneHVAC equipment may be used in the same zone and
should be sequenced to operate after the zone terminal units (i.e., sequence = 2 or higher).
For air loop equipment and outdoor air system equipment the VRF terminal unit inlet and outlet
nodes define the location of the system in the air loop and outdoor air system. The node names
must define the path of the air stream in order from the beginning of the air loop or outdoor air
system to the outlet of that system.
This VRF terminal unit can be controlled based on a load or set point. When the system is used
as zone equipment, load control is always used. When the VRF terminal unit is used in an air loop
and the control zone name or thermostat location is specified, the system is controlled based on zone
load. If the control zone name or thermostat location is not specified the VRF terminal unit will be
controlled based on termninal unit or coil outlet node set point temperature. When set point based
control is used the node temperature set points may be placed at the outlet of the terminal unit or
at individual coil outlet nodes. If the VRF terminal unit is used in an air loop’s outdoor air system,
control is always based on a termninal unit or coil outlet node temperature set point.
The terminal units operate to satisfy a heating or cooling load in a zone based on a zone thermostat
temperature set point. A direct-expansion (DX) cooling and/or DX heating coil is specified depend-
ing on the operating mode required. Both a DX cooling and DX heating coil will typically be installed
in the terminal unit, however only one may be used if desired. An optional supplemental heating coil
can also be added to the terminal unit to provide additional heating when the main DX heating coil
could not meet the entire heating load of a zone during cold outdoor conditions. The Supplemental
Heating Coil Object Type must be Coil:Heating:Electric, Coil:Heating:Fuel, Coil:Heating:Water, or
Coil:Heating:Steam. Outdoor ventilation air is modeled with the use of an optional outside air mixer
object. Outside air may be provided to the zone only when the coil is operating or can be supplied
continuously even when the coil is not operating.
A supply air fan can be modeled as either draw through or blow through. The supply air fan is
required for zone equipment and optional for air loop and outdoor air system equipment. The Supply
Air Fan Object Type must be Fan:SystemModel, Fan:OnOff, or Fan:ConstantVolume if AirCondi-
tioner:VariableRefrigerantFlow is used to model the VRF outdoor unit. The Supply Air Fan Object
Type must be Fan:SystemModel or Fan:VariableVolume if AirConditioner:VariableRefrigerantFlow:-
FluidTemperatureControl or AirConditioner:VariableRefrigerantFlow:FluidTemperatureControl:HR
is used to model the VRF outdoor unit.
1.30.15.1 Inputs
This alpha field defines the name of the schedule (ref: Schedule) that denotes whether the terminal
unit operates during a given time period. A schedule value equal to 0 denotes that the terminal unit
must be off for that time period. A value greater than 0 denotes that the terminal unit is available
to operate during that time period. This schedule may be used to completely disable the terminal
unit as required. If this field is left blank, the schedule has a value of 1 for all time periods.
1.30.15.1.23 Field: Zone Terminal Unit Off Parasitic Electric Energy Use
This numeric field defines the parasitic electrical energy use of the zone terminal unit when the
terminal unit coil(s) is not operating. When the previous mode was cooling, this electric energy
use is reported in a zone terminal unit cooling electric consumption output variable. When the
previous mode was heating, this electric energy use is reported in a zone terminal unit heating
electric consumption output variable.
1422 CHAPTER 1. INPUT-OUTPUT REFERENCE
ZoneHVAC:TerminalUnit:VariableRefrigerantFlow ,
Zone 1 TU , !- Zone Terminal Unit Name
TU Availability Schedule ,!- Terminal Unit Availability schedule
TU1 Inlet Node , !- Terminal Unit Air Inlet Node Name
TU1 Outlet Node , !- Terminal Unit Air Outlet Node Name
0.005 , !- Cooling Supply Air Flow Rate {m3/s}
0, !- No Cooling Supply Air Flow Rate {m3/s}
0.005 , !- Heating Supply Air Flow Rate {m3/s}
0, !- No Heating Supply Air Flow Rate {m3/s}
0.001 , !- Cooling Outdoor Air Flow Rate
0.001 , !- Heating Outdoor Air Flow Rate
0, !- No Load Outdoor Air Flow Rate
TU1 Fan Op Schedule , !- Supply Air Fan Operating Mode Schedule Name
drawthrough , !- Supply Air Fan placement
Fan:ConstantVolume , !- Supply Air Fan Object Type
TU1 SA Fan , !- Supply Air Fan Object Name
OutdoorAir:Mixer , !- Outside Air Mixer Object Type
TU1 OA Mixer , !- Outside Air Mixer Object Name
COIL:Cooling:DX:VariableRefrigerantFlow , !- Cooling Coil Object Type
TU1 VRF DX Cooling Coil , !- Cooling Coil Object Name
COIL:Heating:DX:VariableRefrigerantFlow , !- Heating Coil Object Type
TU1 VRF DX Heating Coil , !- Heating Coil Object Name
30, !- Zone Terminal Unit On Parasitic Electric Energy Use {W}
20, !- Zone Terminal Unit Off Parasitic Electric Energy Use {W}
, !- Rated Total Heating Capacity Sizing Ratio {W/W}
, !- Availability Manager List Name
, !- Design Specification ZoneHVAC Sizing Object Name
Coil:Heating:Electric , !- Supplemental Heating Coil Object Type
TU1 Supp Heating Coil , !- Supplemental Heating Coil Name
autosize , !- Maximum Supply Air Temperature from Supplemental Heater
, !- Maximum Outdoor Dry -Bulb Temperature for Supplemental Heater
Operation
; !- Controlling Zone or Thermostat Location
1.30.15.2 Outputs
step being simulated, and the results are averaged for the time step being reported. The terminal
unit parasitic on and off electricity is reported in this cooling output variable when the unit operates
in cooling mode or the most recent operation was for cooling.
1.30.16 ZoneHVAC:HybridUnitaryHVAC
ZoneHVAC:Hybrid UnitaryHVAC is a black-box model for packaged forced air equipment with
multiple discrete operating modes. Generally, a ”hybrid“ is any system that exhibits both continuous
and discrete dynamic behavior – a system that can both flow (as could be described by a differential
equation) and jump (as must be described by distinct modes). Equipment in this category may utilize
a wide variety technologies including, but not limited to: indirect evaporative cooling, desiccant
dehumidification, heat recovery, vapor compression, adsorption, or ventilation cooling. Each hybrid
system packages multiple technologies into a single integrated system. There are a multitude of
unique hybrid system architectures, and each unique system may have numerous unique operating
modes.
tables (see Table:Lookup) are required to map each dependent variable in each discrete operating
mode. The model can accommodate up to 26 discrete operating modes, including a standby mode.
Each mode is limited to operate within independently specified ranges of indoor and outdoor psy-
chrometric conditions. The standby mode is not limited by either indoor or outdoor psychrometric
conditions.
1.30.16.1 Inputs
1.30.16.1.2 Field: Availability Schedule Name This alpha input field specifies the name
of the schedule (ref: Group – Schedules) that specifies when the ZoneHVAC:HybridUnitaryHVAC
unit can operate. A schedule value greater than 0 means the unit can be available. A schedule value
equal to zero means the unit cannot operate. Availability of the unit is governed by the availability
schedule and by availability managers. The availability schedule may be used to completely disable
the unit. If this field is blank, the unit can always be available. If the unit is available but there is
no sensible load, no latent load, and no need for ventilation, the unit will operate in a standby mode
(mode 0).
1.30.16.1.3 Field: Availability Manager List Name This optional alpha input field is
the name of an AvailabilityManagerAssignmentList object. (ref: Group - Air Distribution, Availabil-
ityManagerAssignmentList, and Group - System Availability Managers). Availability of the unit is
governed by the availability schedule and by availability managers specified in the list named here.
If the unit is available but there is no sensible load, no latent load, and no need for ventilation, the
unit will operate in a standby mode (mode 0).
1.30.16.1.4 Field: Minimum Supply Air Temperature Schedule Name This op-
tional alpha input field specifies the name of the schedule (ref: Group – Schedules) that specifies the
minimum supply air temperature allowed in each time step. Values in this schedule are used as a
constraint in choosing the feasible settings for supply air flow rate and outdoor air fraction in each
operating mode. If this field is blank, no minimum is imposed.
1.30.16.1.5 Field: Maximum Supply Air Temperature Schedule Name This op-
tional alpha input field specifies the name of the schedule (ref: Group – Schedules) that specifies the
maximum supply air temperature allowed in each time step. Values in this schedule are used as a
constraint in choosing the feasible settings for supply air flow rate and outdoor air fraction in each
operating mode. If this field is blank, no maximum is imposed.
1.30.16.1.6 Field: Minimum Supply Air Humidity Ratio Schedule Name This
optional alpha input field specifies the name of the schedule (ref: Group – Schedules) that specifies
the minimum supply air humidity ratio allowed in each time step. Values in this schedule are used
as a constraint in choosing the feasible settings for supply air flow rate and outdoor air fraction in
each operating mode. If this field is blank, no minimum is imposed.
1.30.16.1.7 Field: Maximum Supply Air Humidity Ratio Schedule Name This
optional alpha input field specifies the name of the schedule (ref: Group – Schedules) that specifies
the maximum supply air humidity raio allowed in each time step. Values in this schedule are used
as a constraint in choosing the feasible settings for supply air flow rate and outdoor air fraction in
each operating mode. If this field is blank, no maximum is imposed.
1430 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.30.16.1.8 Field: Method to Choose Controlled Inputs and Part Runtime Frac-
tion This alpha input field specifies the method that will be used to choose operating mode(s),
supply air flow rate(s), outdoor air fraction(s) and part runtime fraction(s) in each time step. The
only valid choices are ”Automatic“ and ”User Defined“, ”Automatic“ chooses the controlled inde-
pendent variables to minimize resource use within each time step, subject to constraints, while best
satisfying zone sensible loads, latent loads, and the scheduled ventilation rate. ”User Defined“ indi-
cates that the user will provide a custom control sequence, using Energy Management System objects
or other means, to choose the controlled independent variables and determine system outputs in each
time step.
1.30.16.1.9 Field: Return Air Node Name This alpha input field specifies the
name of the HVAC system node from which the hybrid unit draws return air. This node
name must also be specified as a zone return air node in a ZoneHVAC:EquipmentConnections
object. It may also be included in NodeList object that is specified as a zone return air
node in a ZoneHVAC:EquipmentConnections object. (Ref. Group - Zone Equipment Zone-
HVAC:EquipmentConnections and Group - Node-Branch Management NodeList).
1.30.16.1.10 Field: Outdoor Air Node Name This alpha input field specifies the name
of the HVAC system node from which the hybrid unit draws outdoor air. This node name must also
be specified in an OutdoorAir:Node or OutdoorAir:NodeList object. (Ref. Group - Node-Branch
Management OutdoorAir:Node and OutdoorAir:NodeList).
1.30.16.1.11 Field: Supply Air Node Name This alpha input field specifies the name
of the HVAC system node to which the hybrid unit sends supply air. This node name must also be
specified as zone inlet node in a ZoneHVAC:EquipmentConnections object. It may also be included
in NodeList object that is specified as a zone inlet node in a ZoneHVAC:EquipmentConnections
object. (Ref. Group - Zone Equipment ZoneHVAC:EquipmentConnections and Group - Node-
Branch Management NodeList).
1.30.16.1.12 Field: Relief Node Name This optional alpha input field specifies the name
of an HVAC system node which can extract air from the zone to balance the air supplied to the zone
by the unit. This node name would match the name of a zone exhaust air node.
1.30.16.1.13 Field: System Maximum Supply Air Volume Flow Rate This nu-
meric input field specifies the maximum standard density supply air volume flow rate among all
operating modes. The field allows custom resizing of the hybrid unit. The values specified in each
Table:Lookup object associated with a hybrid unit represent performance data for a specific product
of a particular size, but the value output from each Table:Lookup object is augmented by a nor-
malization reference (Ref: Group - Performance Tables Table:Lookup). The normalization reference
specified for all Table:Lookup objects associated with a hybrid unit should be the maximum supply
air mass flow rate for the real hybrid unit that was used to create the performance data included
in each table object. The value in this field is used to rescale the normalized values output from
tables for extensive dependent variables. If the standard density supply air volume flow rate input
to this field is equivalent to the system maximum supply air mass flow rate used as the normaliza-
tion reference – given appropriate unit conversions – then the resulting output from the model will
exactly match the original performance data specified in each table. If the value in this field is larger
or smaller, the values for extensive dependent variables will be scaled proportionally. The values
1.30. GROUP – ZONE FORCED AIR UNITS 1431
of intensive dependent variables are rescaled by the normalization reference value, so will always
match the original performance data specified in each table object. The value in this field should be
specified as standard density volume flow rate. Standard density in EnergyPlus corresponds to dry
air at 20◦C drybulb, and 101,325 Pa.
1.30.16.1.15 Field: Fan Heat Included in Lookup Tables This alpha field specifies if
the fan heat gain was taken into account in the lookup tables specified for each mode. Valid choices
are Yes and No. If No, the fan heat is calculated based on the fan power and the next two fields
specify the location and fraction of the fan heat gain to the air stream, otherwise the fan heat gain
is not calculated.
1.30.16.1.16 Field: Fan Heat Gain Location This optional alpha field specifies the
location that the fan heat gain should be applied if not included in the lookup tables. Valid choices
include: MixedAirStream and SupplyAirStream. MixedAirStream is upstream of the cooling
medium while SupplyAirStream is downstream of the cooling medium.
1.30.16.1.17 Field: Fan Heat Gain in Airstream Fraction This optional numeric field
is the fraction of the fan heat that is added to the air stream if not included in the lookup tables. A
value of 0 means that the fan heat is completely outside the air stream. A value of 1 means that all
of the fan heat loss will go into the air stream and act to cause a temperature rise. Must be between
0 and 1. The default is 1.0.
1.30.16.1.18 Field: Scaling Factor This optional numeric field scales all extensive depen-
dent variables including: supply air mass flow rate, electricity use, fuel uses, and water use. The
value in this field acts together with the value in field System Maximum Standard Density Supply
Air Volume Flow Rate to allow custom resizing of the hybrid unit.
1.30.16.1.19 Field: Minimum Time Between Mode Change This numeric field spec-
ifies the minimum time that must pass before the hybrid unit can change mode. If the value in this
field is larger than each timestep, the mode selected in one time step will persist in later time steps
until the minimum time between mode change is satisfied. If the value in this field is smaller than
each timestep, it will determine the minimum part runtime fraction allowed for any mode. Supply
air mass flow rate and outdoor air fraction within a mode are not subject to minimum runtime and
may change in every time step, or with any part runtime fraction. Mode 0 does not have a minimum
time. If this field is blank, the default minimum time between mode change is 10 minutes.
1432 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.30.16.1.20 Field: First Fuel Type This alpha field specifies the fuel type associated
with the Table:Lookup object specified in field ”System Electric Power Power Lookup Table“. Valid
choices include: None, Electricity, NaturalGas, Propane, FuelOilNo1, FuelOilNo2, Diesel, Gasoline,
Coal, OtherFuel1, OtherFuel2, Steam, DistrictHeating and DistrictCooling. If this field is blank, the
default first fuel type is Electricity.
1.30.16.1.21 Field: Second Fuel Type This alpha field specifies the fuel type associated
with the Table:Lookup object specified in field ”System Second Fuel Consumption Lookup Table“.
Valid choices include: None, Electricity, NaturalGas, Propane, FuelOilNo1, FuelOilNo2, Diesel,
Gasoline, Coal, OtherFuel1, OtherFuel2, Steam, DistrictHeating and DistrictCooling. If this field is
blank, the default second fuel type is None.
1.30.16.1.22 Field: Third Fuel Type This alpha field specifies the fuel type associated
with the Table:Lookup object specified in field ”System Third Fuel Consumption Lookup Table“.
Valid choices include: None, Electricity, NaturalGas, Propane, FuelOilNo1, FuelOilNo2, Diesel,
Gasoline, Coal, OtherFuel1, OtherFuel2, Steam, DistrictHeating and DistrictCooling. If this field is
blank, the default second fuel type is None.
1.30.16.1.24 Field: Design Specification Outdoor Air Object Name This alpha
field specifies the name of a DesignSpecification:OutdoorAir object which specifies the a schedule for
the required standard density volume of outdoor air. If this field is blank, the system may still supply
outdoor air, if it is capable, when doing so is the most efficient way to satisfy other constraints.
1.30.16.1.25 Field: Mode 0 Name This alpha input field specifies a unique user-assigned
descriptive name for Mode 0. Mode 0 describes performance when the hybrid unit is in standby.
Mode 0 is usually characterized by electricity use for controls and crankcase heaters, or other standby
resource consumption. Mode 0 will be chosen for any timestep, or portion of timestep, when the
unit is available, but there is no sensible load, latent load, or scheduled ventilation. Mode 0 is not
constrained by limits on indoor or outdoor conditions.
1.30.16.1.26 Field: Mode 0 Supply Air Temperature Lookup Table Name This
optional alpha input field specifies the name of a Table:Lookup object that describes supply air
temperature for Mode 0 as a function of six independent variables: outdoor air temperature, outdoor
air humidity ratio, return air temperature, return air humidity ratio, supply air mass flow rate, and
outdoor air fraction. If this field is blank, Mode 0 will not be considered for any period that requires
ventilation, heating, cooling, humidification, or dehumidification. If this field is blank, when Mode 0
is chosen (during standby periods) the supply air temperature will equal the return air temperature.
1.30. GROUP – ZONE FORCED AIR UNITS 1433
1.30.16.1.27 Field: Mode 0 Supply Air Humidity Ratio Lookup Table Name
This optional alpha input field specifies the name of a Table:Lookup object that describes supply
air humidity ratio for Mode 0 as a function of six independent variables: outdoor air temperature,
outdoor air humidity ratio, return air temperature, return air humidity ratio, supply air mass flow
rate, and outdoor air fraction. If this field is blank, Mode 0 will not be considered for any period
that requires ventilation, heating, cooling, humidification, or dehumidification. If this field is blank,
when Mode 0 is chosen (during standby periods) the supply air humidity ratio will equal the return
air humidity ratio.
1.30.16.1.28 Field: Mode 0 System Electric Power Lookup Table Name This
optional alpha input field specifies the name of a Table:Lookup object that describes electric power
consumption for Mode 0 as a function of six independent variables: outdoor air temperature, outdoor
air humidity ratio, return air temperature, return air humidity ratio, supply air mass flow rate, and
outdoor air fraction. If this field is blank, Mode 0 does not consume electricity.
1.30.16.1.29 Field: Mode 0 Supply Fan Electric Power Lookup Table Name
This optional alpha input field specifies the name of a Table:Lookup object that describes supply
fan electric power consumption for Mode 0 as a function of six independent variables: outdoor air
temperature, outdoor air humidity ratio, return air temperature, return air humidity ratio, supply
air mass flow rate, and outdoor air fraction. If this field is blank, Mode 0 does not consume electricity
for supply fan.
1.30.16.1.30 Field: Mode 0 External Static Pressure Lookup Table Name This
optional alpha input field specifies the name of a Table:Lookup object that describes external static
pressure for Mode 0 as a function of six independent variables: outdoor air temperature, outdoor
air humidity ratio, return air temperature, return air humidity ratio, supply air mass flow rate, and
outdoor air fraction. If this field is blank, external static pressure will not be reported.
1.30.16.1.32 Field: Mode 0 System Third Fuel Consumption Lookup Table Name
This optional alpha input field specifies the name of a Table:Lookup object that describes third
fuel consumption for Mode 0 as a function of six independent variables: outdoor air temperature,
outdoor air humidity ratio, return air temperature, return air humidity ratio, supply air mass flow
rate, and outdoor air fraction. If this field is blank, Mode 0 does not consume a third fuel.
1.30.16.1.33 Field: Mode 0 System Water Use Lookup Table Name This optional
alpha input field specifies the name of a Table:Lookup object that describes water consumption for
Mode 0 as a function of six independent variables: outdoor air temperature, outdoor air humidity
ratio, return air temperature, return air humidity ratio, supply air mass flow rate, and outdoor air
fraction. If this field is blank, Mode 0 does not consume water.
1434 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.30.16.1.34 Field: Mode 0 Outdoor Air Fraction This optional numeric input field
specifies the outdoor air fraction for Mode 0. Outdoor air fraction is not a controlled independent
variable in Mode 0, it must be set to a particular value for all times that Mode 0 operates. Typically
Mode 0 would have zero supply air, in which case this value would be irrelevant. If this field is blank,
the outdoor air fraction for Mode 0 will be 0.00.
1.30.16.1.35 Field: Mode 0 Supply Air Mass Flow Rate Ratio This optional nu-
meric field specifies the supply air mass flow rate ratio for Mode 0. Mass flow rate is not a controlled
independent variable in Mode 0, it must be set to a particular value for all times that Mode 0
operates. Supply air mass flow rate ratio describes supply air mass flow rate as a fraction of the
mass flow rate associated with the value in field: ”System Maximum Standard Density Supply Air
Volume Flow Rate“. If this field is blank, the supply air mass flow rate ratio for Mode 0 will be 0.00.
1.30.16.1.37 Field: Mode # Name This alpha input field specifies a unique user-assigned
descriptive name for Mode #. Each desired mode must have a mode name in order for that mode
to be included in the simulation.
1.30.16.1.38 Field: Mode # Supply Air Temperature Lookup Table Name This
optional alpha input field specifies the name of a Table:Lookup object that describes supply air
temperature for Mode # as a function of six independent variables: outdoor air temperature, outdoor
air humidity ratio, return air temperature, return air humidity ratio, supply air mass flow rate, and
outdoor air fraction. If this field is blank, Mode # will not be considered for any time step that
requires ventilation, heating, cooling, humidification, or dehumidification.
1.30.16.1.39 Field: Mode # Supply Air Humidity Ratio Lookup Table Name
This optional alpha input field specifies the name of a Table:Lookup object that describes supply
air humidity ratio for Mode # as a function of six independent variables: outdoor air temperature,
outdoor air humidity ratio, return air temperature, return air humidity ratio, supply air mass flow
rate, and outdoor air fraction. If this field is blank, Mode # will not be considered for any period
that requires ventilation, heating, cooling, humidification, or dehumidification.
1.30.16.1.40 Field: Mode # System Electric Power Lookup Table Name This
optional alpha input field specifies the name of a Table:Lookup object that describes system electric
power consumption for Mode # as a function of six independent variables: outdoor air temperature,
outdoor air humidity ratio, return air temperature, return air humidity ratio, supply air mass flow
rate, and outdoor air fraction. If this field is blank, Mode # does not consume electricity.
1.30. GROUP – ZONE FORCED AIR UNITS 1435
1.30.16.1.41 Field: Mode # Supply Fan Electric Power Lookup Table Name
This optional alpha input field specifies the name of a Table:Lookup object that describes supply
fan electric power consumption for Mode # as a function of six independent variables: outdoor air
temperature, outdoor air humidity ratio, return air temperature, return air humidity ratio, supply air
mass flow rate, and outdoor air fraction. If this field is blank, Mode # does not consume electricity
for supply fan.
1.30.16.1.42 Field: Mode # External Static Pressure Lookup Table Name This
optional alpha input field specifies the name of a Table:Lookup object that describes external static
pressure for Mode # as a function of six independent variables: outdoor air temperature, outdoor
air humidity ratio, return air temperature, return air humidity ratio, supply air mass flow rate, and
outdoor air fraction. If this field is blank, external static pressure will not be reported for Mode #.
1.30.16.1.45 Field: Mode # System Water Use Lookup Table Name This optional
alpha input field specifies the name of a Table:Lookup object that describes water consumption for
Mode # as a function of six independent variables: outdoor air temperature, outdoor air humidity
ratio, return air temperature, return air humidity ratio, supply air mass flow rate, and outdoor air
fraction. If this field is blank, Mode # does not consume water.
1.30.16.1.48 Field: Mode # Minimum Outdoor Air Humidity Ratio This optional
numeric input field specifies the minimum outdoor air humidity ratio at which Mode # is allowed.
When outdoor air humidity ratio is below this value all settings in Mode # will be excluded from the
feasible set. This value may be beyond the extents of the data in Table:Lookup objects associated
with Mode1, in which case this value sets the limit for extrapolation from the data table. If this
field is blank, there will be no lower constraint on outdoor air humidity ratio for Mode #.
1.30.16.1.49 Field: Mode # Maximum Outdoor Air Humidity Ratio This op-
tional numeric input field specifies the maximum outdoor air humidity ratio at which Mode # is
allowed. When outdoor air humidity ratio is above this value all settings in Mode # will be excluded
from the feasible set. This value may be beyond the extents of the data in Table:Lookup objects
associated with Mode1, in which case this value sets the limit for extrapolation from the data table.
If this field is blank, there will be no upper constraint on outdoor air humidity ratio for Mode #.
1.30.16.1.54 Field: Mode # Minimum Return Air Humidity Ratio This optional
numeric input field specifies the minimum return air humidity ratio at which Mode # mode one is
allowed. When return air humidity ratio is below this value all settings in Mode # will be excluded
from the feasible set. This value may be beyond the extents of the data in Table:Lookup objects
1.30. GROUP – ZONE FORCED AIR UNITS 1437
associated with Mode1, in which case this value sets the limit for extrapolation from the data table.
If this field is blank, there will be no lower constraint on return air humidity ratio for Mode #.
1.30.16.1.55 Field: Mode # Maximum Return Air Humidity Ratio This optional
numeric input field specifies the maximum return air humidity ratio at which Mode # is allowed.
When return air humidity ratio is above this value all settings in Mode # will be excluded from the
feasible set. This value may be beyond the extents of the data in Table:Lookup objects associated
with Mode1, in which case this value sets the limit for extrapolation from the data table. If this
field is blank, there will be no upper constraint on return air humidity ratio for Mode #.
1.30.16.1.56 Field: Mode # Minimum Return Air Relative Humidity This op-
tional numeric input field specifies the minimum return air relative humidity at which Mode # is
allowed. When return air relative humidity is below this value all settings in Mode # will be excluded
from the feasible set. This value may be beyond the extents of the data in Table:Lookup objects
associated with Mode1, in which case this value sets the limit for extrapolation from the data table.
If this field is blank, the lower constraint on return air relative humidity will be 0.00
1.30.16.1.57 Field: Mode # Maximum Return Air Relative Humidity This op-
tional numeric input field specifies the maximum return air relative humidity at which Mode # is
allowed. When return air relative humidity is above this value all settings in Mode # will be ex-
cluded from the feasible set. This value may be beyond than the extents of the data in Table:Lookup
objects associated with Mode1, in which case this value sets the limit for extrapolation from the data
table. If this field is blank, the upper constraint on return air relative humidity will be 100
1.30.16.1.58 Field: Mode # Minimum Outdoor Air Fraction This optional numeric
input field specifies the minimum outdoor air fraction allowed in Mode #. Outdoor air fractions
below this value will be excluded from the feasible set within Mode #. This value may be beyond
than the extents of the data in Table:Lookup objects associated with Mode1, in which case this value
sets the limit for extrapolation from the data table. If this field is blank, the lower constraint on
outdoor air fraction will be 0.00 for Mode #.
1.30.16.1.59 Field: Mode # Maximum Outdoor Air Fraction This optional numeric
input field specifies the maximum outdoor air fraction allowed in Mode #. Outdoor air fractions
above this value will be excluded from the feasible set within Mode #. This value may be beyond
than the extents of the data in Table:Lookup objects associated with Mode1, in which case this value
sets the limit for extrapolation from the data table. If this field is blank, the upper constraint on
outdoor air fraction will be 1.00 for Mode #.
1.30.16.1.60 Field: Mode # Minimum Supply Air Mass Flow Rate Ratio This
optional numeric input field specifies the minimum supply air mass flow rate ratio allowed in Mode
#. Supply air mass flow rate ratios below this value will be excluded from the feasible set within
Mode #. This value may be beyond the extents of the data in Table:Lookup objects associated with
Mode1, in which case this value sets the limit for extrapolation from the data table. If this field is
blank, the lower constraint on supply air mass flow rate ratio will be 0.00 for Mode #.
1438 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.30.16.1.61 Field: Mode # Maximum Supply Air Mass Flow Rate Ratio This
optional numeric input field specifies the maximum supply air mass flow rate ratio allowed in Mode
#. Supply air mass flow rate ratios above this value will be excluded from the feasible set within
Mode #. This value may be beyond the extents of the data in Table:Lookup objects associated with
Mode1, in which case this value sets the limit for extrapolation from the data table. If this field is
blank, the upper constraint on supply air mass flow rate ratio will be 1.00 for Mode #.
1.30.16.2 Outputs
HVAC ,Average ,Zone Hybrid Unitary HVAC System Total Cooling Rate [W]
HVAC ,Average ,Zone Hybrid Unitary HVAC System Total Cooling Energy [J]
HVAC ,Average ,Zone Hybrid Unitary HVAC System Sensible Cooling Rate [W]
HVAC ,Average ,Zone Hybrid Unitary HVAC System Sensible Cooling Energy [J]
HVAC ,Average ,Zone Hybrid Unitary HVAC System Latent Cooling Rate [W]
HVAC ,Average ,Zone Hybrid Unitary HVAC System Latent Cooling Energy [J]
HVAC ,Average ,Zone Hybrid Unitary HVAC Zone Total Cooling Rate [W]
HVAC ,Average ,Zone Hybrid Unitary HVAC Zone Total Cooling Energy [J]
HVAC ,Average ,Zone Hybrid Unitary HVAC Zone Sensible Cooling Rate [W]
HVAC ,Average ,Zone Hybrid Unitary HVAC Zone Sensible Cooling Energy [J]
HVAC ,Average ,Zone Hybrid Unitary HVAC Zone Latent Cooling Rate [W]
HVAC ,Average ,Zone Hybrid Unitary HVAC Zone Latent Cooling Energy [J]
HVAC ,Average ,Zone Hybrid Unitary HVAC System Total Heating Rate [W]
HVAC ,Average ,Zone Hybrid Unitary HVAC System Total Heating Energy [J]
HVAC ,Average ,Zone Hybrid Unitary HVAC System Sensible Heating Rate [W]
HVAC ,Average ,Zone Hybrid Unitary HVAC System Sensible Heating Energy [J]
HVAC ,Average ,Zone Hybrid Unitary HVAC System Latent Heating Rate [W]
HVAC ,Average ,Zone Hybrid Unitary HVAC System Latent Heating Energy [J]
HVAC ,Average ,Zone Hybrid Unitary HVAC Zone Total Heating Rate [W]
HVAC ,Average ,Zone Hybrid Unitary HVAC Zone Total Heating Energy [J]
HVAC ,Average ,Zone Hybrid Unitary HVAC Zone Sensible Heating Rate [W]
HVAC ,Average ,Zone Hybrid Unitary HVAC Zone Sensible Heating Energy [J]
HVAC ,Average ,Zone Hybrid Unitary HVAC Zone Latent Heating Rate [W]
HVAC ,Average ,Zone Hybrid Unitary HVAC Zone Latent Heating Energy [J]
HVAC ,Average ,Zone Hybrid Unitary HVAC Predicted Sensible Load to Setpoint Heat Transfer Rate [W]
HVAC ,Average ,Zone Hybrid Unitary HVAC Predicted Latent Load to Humidistat Setpoint Heat Transfer
Rate [W]
HVAC ,Average ,Zone Hybrid Unitary HVAC Predicted Moisture Load to Humidistat Setpoint Moisture
Transfer Rate [kgWater/s]
HVAC ,Average ,Zone Hybrid Unitary HVAC Supply Air Temperature [C]
HVAC ,Average ,Zone Hybrid Unitary HVAC Return Air Temperature [C]
HVAC ,Average ,Zone Hybrid Unitary HVAC Outdoor Air Temperature [C]
HVAC ,Average ,Zone Hybrid Unitary HVAC Supply Air Humidity Ratio [kgWater/kgDryAir]
HVAC ,Average ,Zone Hybrid Unitary HVAC Return Air Humidity Ratio [kgWater/kgDryAir]
HVAC ,Average ,Zone Hybrid Unitary HVAC Outdoor Air Humidity Ratio [kgWater/kgDryAir]
HVAC ,Average ,Zone Hybrid Unitary HVAC Supply Air Relative Humidity [%]
HVAC ,Average ,Zone Hybrid Unitary HVAC Return Air Relative Humidity [%]
HVAC ,Average ,Zone Hybrid Unitary HVAC Outdoor Air Relative Humidity [%]
HVAC ,Average ,Zone Hybrid Unitary HVAC Supply Air Mass Flow Rate [kg/s]
HVAC ,Average ,Zone Hybrid Unitary HVAC Supply Air Standard Density Volume Flow Rate [m3/s]
HVAC ,Average ,Zone Hybrid Unitary HVAC Ventilation Air Standard Density Volume Flow Rate [m3/s]
HVAC ,Average ,Zone Hybrid Unitary HVAC Electricity Rate [W]
HVAC ,Average ,Zone Hybrid Unitary HVAC Electricity Energy [J]
Water use
Second Fuel Use
Third Fuel Use
Supply Fan Electricity Rate
External Static Pressure
HVAC ,Average ,Zone Hybrid Unitary HVAC Requested Outdoor Air Ventilation Mass Flow Rate [kg/s]
HVAC ,Average ,Zone Hybrid Unitary HVAC Ventilation Air Mass Flow Rate [kg/s]
HVAC ,Average ,Zone Hybrid Unitary HVAC Availability Status []
HVAC ,Average ,Zone Hybrid Unitary HVAC Outdoor Air Fraction []
HVAC ,Average ,Zone Hybrid Unitary HVAC Dehumidification Load to Humidistat Setpoint Moisture
Transfer Rate [kg/s]
HVAC ,Average ,Zone Hybrid Unitary HVAC Runtime Fraction in Setting 0 []
HVAC ,Average ,Zone Hybrid Unitary HVAC Runtime Fraction in Setting 1 []
HVAC ,Average ,Zone Hybrid Unitary HVAC Runtime Fraction in Setting 2 []
1.30. GROUP – ZONE FORCED AIR UNITS 1439
1.30.16.2.1 Zone Hybrid Unitary HVAC System Total Cooling Rate [W] This
output reports the rate at which enthalpy is removed by the system. It is calculated as the difference
between the enthalpy of the mixture of return air and outdoor air and the enthalpy of the supply air.
This output is positive when enthalpy is removed by the system, otherwise it is zero. This output is
an average rate over the reporting period.
1.30.16.2.2 Zone Hybrid Unitary HVAC System Total Cooling Energy [J] This
output reports the amount of enthalpy removed by the system. It is calculated as the difference
between the enthalpy of the mixture of return air and outdoor air, and the enthalpy of the supply
air. This output is positive when enthalpy is removed by the system, otherwise the output is zero.
This output is a sum over the reporting period.
1.30.16.2.3 Zone Hybrid Unitary HVAC System Sensible Cooling Rate [W]
This output reports the rate at which sensible heat is removed by the system. It is calculated as
the difference between the enthalpy of dry air at the temperature of the mixture of return air and
outdoor air, and the enthalpy of dry air at the temperature of the supply air. This output is positive
when sensible heat is removed by the system, otherwise it is zero. This output is an average rate
over the reporting period.
1.30.16.2.4 Zone Hybrid Unitary HVAC System Sensible Cooling Energy [J]
This output reports the amount of sensible heat removed by the system. It is calculated as the
difference between the enthalpy of dry air at the temperature of the mixture of return air and
outdoor air, and the enthalpy of dry air at the temperature of the supply air. This output is positive
when sensible heat is removed by the system, otherwise it is zero. This output is a sum over the
reporting period.
1.30.16.2.5 Zone Hybrid Unitary HVAC System Latent Cooling Rate [W] This
output reports the rate at which latent heat is removed by the system. It is calculated as the enthalpy
difference associated with the difference between absolute humidity of the mixture of return air and
outdoor air, and the absolute humidity of the supply air. This is the phase change energy associated
1440 CHAPTER 1. INPUT-OUTPUT REFERENCE
with moisture removed by the system. This output is positive when latent heat is removed by the
system, otherwise it is zero. This output is an average rate over the reporting period.
1.30.16.2.6 Zone Hybrid Unitary HVAC System Latent Cooling Energy [J] This
output reports the amount of latent heat removed by the system. It is calculated as the enthalpy
difference associated with the difference between absolute humidity of the mixture of return air and
outdoor air, and the absolute humidity of the supply air. This is the phase change energy associated
with moisture removed by the system. This output is positive when latent heat is removed by the
system, otherwise it is zero. This output is a sum over the reporting period.
1.30.16.2.7 Zone Hybrid Unitary HVAC Zone Total Cooling Rate [W] This
output reports the rate at which enthalpy is removed from the zone. It is calculated as the difference
between the enthalpy of the return air and the enthalpy of the supply air. This output is positive
when enthalpy is removed from the zone, otherwise it is zero. This output is an average rate over
the reporting period.
1.30.16.2.8 Zone Hybrid Unitary HVAC Zone Total Cooling Energy [J] This
output reports the amount of enthalpy removed from the zone. It is calculated as the difference
between the enthalpy of the return air and the enthalpy of the supply air. This output is positive
when enthalpy is removed from the zone, otherwise it is zero. This output is a sum over the reporting
period.
1.30.16.2.9 Zone Hybrid Unitary HVAC Zone Sensible Cooling Rate [W] This
output reports the rate at which sensible heat is removed from the zone. It is calculated as the
difference between the enthalpy of dry air at the temperature of the return air and the enthalpy of
dry air at the temperature of the supply air. This output is positive when sensible heat is removed
from the zone, otherwise it is zero. This output is an average rate over the reporting period.
1.30.16.2.10 Zone Hybrid Unitary HVAC Zone Sensible Cooling Energy [J] This
output reports the amount of sensible heat removed from the zone. It is calculated as the difference
between the enthalpy of dry air at the temperature of the return air and the enthalpy of dry air at
the temperature of the supply air. This output is positive when sensible heat is removed from the
zone, otherwise it is zero. This output is a sum over the reporting period.
1.30.16.2.11 Zone Hybrid Unitary HVAC Zone Latent Cooling Rate [W] This
output reports the rate at which latent heat is removed from the zone. It is calculated as the
enthalpy difference associated with the difference between the absolute humidity of the return air,
and the absolute humidity of the supply air. This is the phase change energy associated with moisture
removed from the zone. This output is positive when latent heat is removed from the zone, otherwise
it is zero. This output is an average rate over the reporting period.
1.30.16.2.12 Zone Hybrid Unitary HVAC Zone Latent Cooling Energy [J] This
output reports the amount of latent heat removed from the zone. It is calculated as the enthalpy
difference associated with the difference between the absolute humidity of the return air, and the
absolute humidity of the supply air. This is the phase change energy associated with moisture
removed from the zone. This output is positive when latent heat is removed from the zone, otherwise
it is zero. This output is a sum over the reporting period.
1.30. GROUP – ZONE FORCED AIR UNITS 1441
1.30.16.2.13 Zone Hybrid Unitary HVAC System Total Heating Rate [W] This
output reports the rate at which enthalpy is added by the system. It is calculated as the difference
between the enthalpy of the mixture of return air and outdoor air and the enthalpy of the supply
air. This output is positive when enthalpy is added by the system, otherwise it is zero. This output
is an average rate over the reporting period.
1.30.16.2.14 Zone Hybrid Unitary HVAC System Total Heating Energy [J] This
output reports the amount of enthalpy added by the system. It is calculated as the difference between
the enthalpy of the mixture of return air and outdoor air, and the enthalpy of the supply air. This
output is positive when enthalpy is added by the system, otherwise the output is zero. This output
is a sum over the reporting period.
1.30.16.2.15 Zone Hybrid Unitary HVAC System Sensible Heating Rate [W]
This output reports the rate at which sensible heat is added by the system. It is calculated as
the difference between the enthalpy of dry air at the temperature of the mixture of return air and
outdoor air, and the enthalpy of dry air at the temperature of the supply air. This output is positive
when sensible heat is added by the system, otherwise it is zero. This output is an average rate over
the reporting period.
1.30.16.2.16 Zone Hybrid Unitary HVAC System Sensible Heating Energy [J]
This output reports the amount of sensible heat added by the system. It is calculated as the difference
between the enthalpy of dry air at the temperature of the mixture of return air and outdoor air, and
the enthalpy of dry air at the temperature of the supply air. This output is positive when sensible
heat is added by the system, otherwise it is zero. This output is a sum over the reporting period.
1.30.16.2.17 Zone Hybrid Unitary HVAC System Latent Heating Rate [W] This
output reports the rate at which latent heat is added by the system. It is calculated as the enthalpy
difference associated with the difference between absolute humidity of the mixture of return air and
outdoor air, and the absolute humidity of the supply air. This is the phase change energy associated
with moisture added by the system. This output is positive when latent heat is added by the system,
otherwise it is zero. This output is an average rate over the reporting period.
1.30.16.2.18 Zone Hybrid Unitary HVAC System Latent Heating Energy [J]
This output reports the amount of latent heat added by the system. It is calculated as the enthalpy
difference associated with the difference between absolute humidity of the mixture of return air and
outdoor air, and the absolute humidity of the supply air. This is the phase change energy associated
with moisture added by the system. This output is positive when latent heat is added by the system,
otherwise it is zero. This output is a sum over the reporting period.
1.30.16.2.19 Zone Hybrid Unitary HVAC Zone Total Heating Rate [W] This
output reports the rate at which enthalpy is added to the zone. It is calculated as the difference
between the enthalpy of the return air and the enthalpy of the supply air. This output is positive
when enthalpy is added to the zone, otherwise it is zero. This output is an average rate over the
reporting period.
1442 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.30.16.2.20 Zone Hybrid Unitary HVAC Zone Total Heating Energy [J] This
output reports the amount of enthalpy added to the zone. It is calculated as the difference between
the enthalpy of the return air and the enthalpy of the supply air. This output is positive when
enthalpy is added to the zone, otherwise it is zero. This output is a sum over the reporting period.
1.30.16.2.21 Zone Hybrid Unitary HVAC Zone Sensible Heating Rate [W] This
output reports the rate at which sensible heat is added to the zone. It is calculated as the difference
between the enthalpy of dry air at the temperature of the return air and the enthalpy of dry air at
the temperature of the supply air. This output is positive when sensible heat is added to the zone,
otherwise it is zero. This output is an average rate over the reporting period.
1.30.16.2.22 Zone Hybrid Unitary HVAC Zone Sensible Heating Energy [J]
This output reports the amount of sensible heat added to the zone. It is calculated as the difference
between the enthalpy of dry air at the temperature of the return air and the enthalpy of dry air at
the temperature of the supply air. This output is positive when sensible heat is added to the zone,
otherwise it is zero. This output is a sum over the reporting period.
1.30.16.2.23 Zone Hybrid Unitary HVAC Zone Latent Heating Rate [W] This
output reports the rate at which latent heat is added to the zone. It is calculated as the enthalpy
difference associated with the difference between the absolute humidity of the return air, and the
absolute humidity of the supply air. This is the phase change energy associated with moisture added
to the zone. This output is positive when latent heat is added to the zone, otherwise it is zero. This
output is an average rate over the reporting period.
1.30.16.2.24 Zone Hybrid Unitary HVAC Zone Latent Heating Energy [J] This
output reports the amount of latent heat added to the zone. It is calculated as the enthalpy difference
associated with the difference between the absolute humidity of the return air, and the absolute
humidity of the supply air. This is the phase change energy associated with moisture added to the
zone. This output is positive when latent heat is added to the zone, otherwise it is zero. This output
is a sum over the reporting period.
a soft inequality constraint in the constrained optimization problem that determines system settings
in each time step. The output is the average over the reporting period.
1.30.16.2.28 Zone Hybrid Unitary HVAC Supply Air Temperature [◦C] This
output reports the supply air temperature. For each timestep the value is calculated as a supply air
mass weighted average of the supply air temperature for each of the settings selected for the time
step. For example, if the system operates for half of the timestep with supply air mass flow rate of
1 kg/s and supply air temperature of 16◦C, and for half of the timestep at 2 kg/s and 10◦C, the
supply air temperature calculated for the time step would be 12 ◦C. The output is the average over
the reporting period.
1.30.16.2.29 Zone Hybrid Unitary HVAC Return Air Temperature [◦C] This out-
put reports the return air temperature. The return air temperature is inherited from the associated
zone outlet node in each timestep. The output is the average over the reporting period.
1.30.16.2.30 Zone Hybrid Unitary HVAC Outdoor Air Temperature [◦C] This
output reports the outdoor air temperature. The outdoor air temperature is inherited from the
associated outdoor air node in each timestep. The output is the average over the reporting period.
1.30.16.2.31 Zone Hybrid Unitary HVAC Supply Air Humidity Ratio [kgWa-
ter/kgDryAir] This output reports the supply air humidity ratio. For each timestep the value
is calculated as a supply air mass weighted average of the supply air humidity ratio for each of the
settings selected for the time step. For example, if the system operates for half of the timestep with
supply air mass flow rate of 1 kg/s and supply air humidity ratio of 0.016 kgWater/kgDryAir, and for
half of the timestep at 2 kg/s and 0.010 kgWater/kgDryAir, the supply air humidity ratio calculated
for the time step would be 0.012 kgWater/kgDryAir. The output is the average over the reporting
period.
1.30.16.2.32 Zone Hybrid Unitary HVAC Return Air Humidity Ratio [kgWa-
ter/kgDryAir] This output reports the return air humidity ratio. The return air humidity
ratio is inherited from the associated zone outlet node in each timestep. The output is the average
over the reporting period.
1.30.16.2.33 Zone Hybrid Unitary HVAC Outdoor Air Humidity Ratio [kgWa-
ter/kgDryAir] This output reports the outdoor air humidity ratio. The outdoor air humidity
ratio is inherited from the associated outdoor air node in each timestep. The output is the average
over the reporting period.
1444 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.30.16.2.34 Zone Hybrid Unitary HVAC Supply Air Relative Humidity [%]
This output reports the supply air relative humidity. For each timestep the value is calculated
from the supply air temperature and supply air humidity ratio according to standard psychrometric
relationships. The output is the time weighted average over the reporting period.
1.30.16.2.35 Zone Hybrid Unitary HVAC Return Air Relative Humidity [%]
This output reports the return air relative humidity. The return air relative humidity is inherited
from the associated zone outlet node in each timestep. The output is the average over the reporting
period.
1.30.16.2.36 Zone Hybrid Unitary HVAC Outdoor Air Relative Humidity [%]
This output reports the outdoor air relative humidity. The outdoor air relative humidity is inherited
from the associated outdoor air node in each timestep. The output is the average over the reporting
period.
1.30.16.2.37 Zone Hybrid Unitary HVAC Supply Air Mass Flow Rate [kg/s]
This output reports the supply air mass flow rate. For each timestep the value is calculated as a
time weighted average of the supply air mass flow rate for each of the settings selected for the time
step. The output is the average over the reporting period.
1.30.16.2.38 Zone Hybrid Unitary HVAC Supply Air Standard Density Volume
Flow Rate [m3/s] This output reports the supply air flow as a standard density volume flow
rate. Standard density in EnergyPlus corresponds to dry air at 20◦C drybulb, and 101,325 Pa. The
output is the average over the reporting period.
1.30.16.2.39 Zone Hybrid Unitary HVAC Ventilation Air Standard Density Vol-
ume Flow Rate [m3/s] This output reports the outdoor air (ventilation) flow as a standard
density volume flow rate. Standard density in EnergyPlus corresponds to dry air at 20◦C drybulb,
and 101,325 Pa. The output is the average over the reporting period.
1.30.16.2.40 Zone Hybrid Unitary HVAC Electricity Rate [W] This output reports
the electric power input to the system. For each timestep the value is calculated as a time weighted
average of the electric power for each of the settings selected for the time step. The output is the
average over the reporting period.
1.30.16.2.41 Zone Hybrid Unitary HVAC Electricity Energy [J] This output re-
ports the electric energy consumed by the system. For each timestep the value is calculated from
the average electric power. The output is the sum over the reporting period.
1.30.16.2.43 Zone Hybrid Unitary HVAC Ventilation Mass Flow Rate [kg/s]
This output reports the mass flow rate of outdoor air (ventilation) supplied by the system. The
output is the average over the reporting period.
1.30.16.2.44 Zone Hybrid Unitary HVAC Availability Status [] This output reports
whether or not the system is available. A value of 1.0 means the system will operate in an attempt to
satisfy the predicted sensible load, latent load, and requested ventilation rate. For standby periods
– when the system is available, but there are no loads, and no request for ventilation – the system
operates in Mode 0. A value of 0.0 means the system will not operate under any circumstance.
1.30.16.2.45 Zone Hybrid Unitary HVAC Outdoor Air Fraction [] This output
reports the outdoor air fraction – the portion of the supply air mass flow rate that is composed of
ventilation air. For each timestep the value is calculated as a time weighted average of the outdoor
air fraction for each of the settings selected for the time step. The output is the average over the
reporting period.
1.30.16.2.47 Zone Hybrid Unitary HVAC Mode in Setting X [] Thy hybrid system
may operate in multiple settings within each time step. Each setting represents a combination of
operating mode, supply air mass flow rate, and outdoor air fraction. The combination associated
with each setting number may be unique in each time step. These outputs report the mode number
associated with each setting in each time step.
1.30.16.2.49 Zone Hybrid Unitary HVAC Supply Air Mass Flow Rate in Setting
X [kg/s] Thy hybrid system may operate in multiple settings within each time step. Each setting
represents a combination of operating mode, supply air mass flow rate, and outdoor air fraction. The
combination associated with each setting number may be unique in each time step. These outputs
report the supply air mass flow rate associated with each setting in each time step.
1.30.16.2.50 Zone Hybrid Unitary HVAC Supply Air Mass Flow Rate Ratio in
Setting X [] Thy hybrid system may operate in multiple settings within each time step. Each
setting represents a combination of operating mode, supply air mass flow rate, and outdoor air
fraction. The combination associated with each setting number may be unique in each time step.
These output reports the supply air mass flow rate ratio associated with each setting in each time
step. The supply air mass flow rate ratio is the ratio of the current supply air mass flow rate to the
system maximum supply air flow rate.
1446 CHAPTER 1. INPUT-OUTPUT REFERENCE
– AirLoopHVAC:UnitarySystem
– AirLoopHVAC:Unitary:Furnace:HeatOnly
– AirLoopHVAC:Unitary:Furnace:HeatCool
– AirLoopHVAC:UnitaryHeatOnly
– AirLoopHVAC:UnitaryHeatCool
– AirLoopHVAC:UnitaryHeatPump:AirToAir
– AirLoopHVAC:UnitaryHeatPump:AirToAir:MultiSpeed
are compound components usually placed in the primary air loop as the sole component. On the
zone equipment side they are usually connected to one or more zones through uncontrolled terminal
units (i.e., AirTerminal:SingleDuct:ConstantVolume:NoReheat objects). The maximum or design
air flow rate through the furnace or unitary system should usually be set equal to the sum of the
maximum air flow rates through the terminal unit objects. However, the simulation program can
usually account for unequal air flows if the user wishes to model this scenario.
The following HVAC equipment types are allowed in the air loop. The component matrix shows
which coils and fans are allowed with which equipment models.
1.31.2 AirLoopHVAC:UnitarySystem
The AirloopHVAC:UnitarySystem object is intended to replace all other air loop equipment,
although other system types are still available. This system is unique in that it can accommo-
date all fan and coil types whereas other system types are specific to the type of fan and coil
available for simulation. Additionally, although the AirloopHVAC:UnitarySystem is intended
for use in the primary airloop, this object can be modeled as zone equipment (i.e., listed in a
ZoneHVAC:EquipmentList) or as an outside air system component (i.e., listed in a AirLoopH-
VAC:OutdoorAirSystem:EquipmentList). Water coil controllers are not required when these coil
types are used with the AirloopHVAC:UnitarySystem object (i.e., leave the controller list name
blank in the AirLoopHVAC object if water coils are used exclusively within the Unitary System).
The AirLoopHVAC:UnitarySystem object is a “virtual” component that consists of a fan component
(OnOff, ConstantVolume, VariableVolume, or ComponentModel), a cooling coil component, a heat-
ing coil component, and a reheat coil as shown in Figure 1.142. When a draw through configuration
is desired, the fan is placed directly after the heating coil. If dehumidification control is selected, a
reheat coil component is also required. If the reheat coil is present and the dehumidification control
type input is not specified as CoolReheat, the reheat coil will not be active. All of the fan and coil
components are optional which allows the AirLoopHVAC:UnitarySystem object to be configured for
fan-only, heating-only, cooling-only, or both heating and cooling. It may also be applied without a
fan, controlling one or more coils, similar to the function of CoilSystem:Cooling:DX.
Links to the fan, cooling coil, heating coil and reheat coil specifications are provided in the unitary
system input data syntax. In addition, the control zone name and the system design operating
conditions are specified by the unitary system inputs.
1.31. GROUP – UNITARY EQUIPMENT 1447
Figure 1.141:
1448 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.31.2.1 Inputs
– Coil:Heating:DX:SingleSpeed
– Coil:Heating:DX:TwoSpeed
– Coil:Heating:DX:MultiSpeed
– Coil:Heating:DX:VariableSpeed
– Coil:Heating:WaterToAirHeatPump:ParameterEstimation
– Coil:Heating:WaterToAirHeatPump:EquationFit
– Coil:Heating:WaterToAirHeatPump:VariableSpeedEquationFit
1452 CHAPTER 1. INPUT-OUTPUT REFERENCE
– Coil:Heating:Fuel
– Coil:Heating:Gas:MultiStage
– Coil:Heating:Electric
– Coil:Heating:Electric:MultiStage
– Coil:Heating:Water
– Coil:Heating:Steam
– Coil:Heating:Desuperheater
– Coil:UserDefined
– Coil:Cooling:DX:SingleSpeed
– Coil:Cooling:DX:SingleSpeed:ThermalStorage
– Coil:Cooling:DX:TwoSpeed
– Coil:Cooling:DX:MultiSpeed
– Coil:Cooling:DX:VariableSpeed
– Coil:Cooling:DX:TwoStageWithHumidityControlMode
– CoilSystem:Cooling:DX:HeatExchangerAssisted
– Coil:Cooling:WaterToAirHeatPump:ParameterEstimation
– Coil:Cooling:WaterToAirHeatPump:EquationFit
– Coil:Cooling:WaterToAirHeatPump:VariableSpeedEquationFit
– Coil:Cooling:Water
– Coil:Cooling:Water:DetailedGeometry
– CoilSystem:Cooling:Water:HeatExchangerAssisted
– Coil:UserDefined
– Coil:Heating:Electric
– Coil:Heating:Fuel
– Coil:Heating:Desuperheater
– Coil:Heating:Water
– Coil:Heating:Steam
– Coil:UserDefined
1454 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.31.2.1.24 Field: Cooling Supply Air Flow Rate Per Floor Area
This numeric field defines the supply air flow rate per floor area leaving the unitary system in meters
per second when the cooling coil is operating. Values must be greater than 0 if the cooling coil is
present or this field is autosizable. Required field when Cooling Supply Air Flow Rate Method is
FlowPerFloorArea.
1.31.2.1.25 Field: Cooling Fraction of Autosized Design Cooling Supply Air Flow
Rate
This numeric field defines the fraction of autosized supply air flow rate leaving the unitary system
when the cooling coil is operating. Values must be greater than 0 if the cooling coil is present or this
field is autosizable. Required field when Cooling Supply Air Flow Rate Method is FractionOfAu-
tosizedCoolingValue.
1.31.2.1.26 Field: Cooling Supply Air Flow Rate Per Unit of Capacity
This numeric field defines the supply air flow rate per unit of capacity leaving the unitary system
when the cooling coil is operating. Values must be greater than 0 if the cooling coil is present or this
field is autosizable. Required field when Cooling Supply Air Flow Rate Method is FlowPerCool-
ingCapacity.
1.31.2.1.29 Field: Heating Supply Air Flow Rate Per Floor Area
This numeric field defines the supply air flow rate per floor area leaving the unitary system in meters
per second when the heating coil is operating. Values must be greater than 0 if the heating coil is
present or this field is autosizable. Required field when Heating Supply Air Flow Rate Method is
FlowPerFloorArea.
1.31.2.1.31 Field: Heating Supply Air Flow Rate Per Unit of Capacity
This numeric field defines the supply air flow rate per unit of capacity leaving the unitary system
when the heating coil is operating. Values must be greater than 0 if the heating coil is present or
this field is autosizable. Required field when Heating Supply Air Flow Rate Method is FlowPer-
HeatingCapacity.
when no cooling/heating is needed is equal to the supply air flow rate when the compressor was
last operating (for cooling operation or heating operation). This field should not be set to 0 when
Control Type is specified as SingleZoneVAV.
1.31.2.1.34 Field: No Load Supply Air Flow Rate Per Floor Area
This numeric field defines the supply air flow rate per floor area leaving the unitary system in meters
per second when neither cooling or heating coil is operating. Values must be greater than or equal
to 0 or this field is autosizable. Required field when No Load Supply Air Flow Rate Method During
is FlowPerFloorArea.
1.31.2.1.35 Field: No Load Fraction of Autosized Cooling Supply Air Flow Rate
This numeric field defines the fraction of autosized supply air flow rate leaving the unitary system
when neither cooling or heating coil is operating. Values must be greater than or equal to 0 or this
field is autosizable. Required field when No Load Supply Air Flow Rate Method is FractionOfAu-
tosizedCoolingValue.
1.31.2.1.36 Field: No Load Fraction of Autosized Heating Supply Air Flow Rate
This numeric field defines the fraction of autosized supply air flow rate leaving the unitary sys-
tem when the neither cooling or heating coil is operating. Values must be greater than or equal
to 0 or this field is autosizable. Required field when No Load Supply Air Flow Rate Method is
FractionOfAutosizedHeatingValue.
1.31.2.1.37 Field: No Load Supply Air Flow Rate Per Unit of Capacity During
Cooling Operation
This numeric field defines the supply air flow rate per unit of capacity leaving the unitary system
when neither cooling or heating is operating. Values must be greater than or equal to 0 or this field
is autosizable. Required field when No Load Supply Air Flow Rate Method is FlowPerCooling-
Capacity.
1.31.2.1.38 Field: No Load Supply Air Flow Rate Per Unit of Capacity During
Heating Operation
This numeric field defines the supply air flow rate per unit of capacity leaving the unitary system
when neither cooling or heating is operating. Values must be greater than or equal to 0 or this field
is autosizable. Required field when No Load Supply Air Flow Rate Method is FlowPerHeating-
Capacity.
AirLoopHVAC:UnitarySystem ,
DXAC Heat Pump 1, !- Name
Load , !- Control Type
East Zone , !- Controlling Zone or Thermostat Location
, !- Dehumidification Control Type
FanAndCoilAvailSched , !- Availability Schedule Name
Mixed Air Node , !- Air Inlet Node Name
1460 CHAPTER 1. INPUT-OUTPUT REFERENCE
UnitarySystemPerformance :Multispeed ,
MyMultispeedHPSpec , !- Name
4, !- Number of Speeds for Heating
4, !- Number of Speeds for Cooling
No , !- Single Mode Operation
, !- No Load Supply Air Flow Rate Ratio
0.235294118 , !- Heating Speed 1 Supply Air Flow Ratio
0.235294118 , !- Cooling Speed 1 Supply Air Flow Ratio
0.470588235 , !- Heating Speed 2 Supply Air Flow Ratio
0.470588235 , !- Cooling Speed 2 Supply Air Flow Ratio
0.705882353 , !- Heating Speed 3 Supply Air Flow Ratio
0.705882353 , !- Cooling Speed 3 Supply Air Flow Ratio
1.0, !- Heating Speed 4 Supply Air Flow Ratio
1.0; !- Cooling Speed 4 Supply Air Flow Ratio
1.31. GROUP – UNITARY EQUIPMENT 1461
1.31.2.2 Outputs
– HVAC,Average,Unitary System Predicted Sensible Load to Setpoint Heat Transfer Rate [W]
– HVAC,Average,Unitary System Predicted Moisture Load to Setpoint Heat Transfer Rate [W]
unitary system outlet air and inlet air streams at a constant humidity ratio, and the air mass flow
rate through the unitary system. This value is calculated for each HVAC system timestep being
simulated, and the results (heating only) are averaged for the timestep being reported. For load or
single zone VAV control this value is calculated using the outlet air and zone air conditions.
1.31.2.2.21 Unitary System Heat Recovery Fluid Mass Flow Rate [kg/s]
These outputs are the heat recovery inlet and outlet temperatures and water mass flow rate for
unitary systems with heat recovery.
1.31.3 UnitarySystemPerformance:Multispeed
1.31.3.1 Inputs
1.31.4 AirLoopHVAC:Unitary:Furnace:HeatCool
The heat/cool furnace is a “virtual” component that consists of a fan component (OnOff or Con-
stantVolume), a DX cooling coil component, and a Gas or Electric heating coil component. The
blow through furnace configuration is shown in Figure 1.146 below. When a draw through furnace
configuration is desired, the fan is placed directly after the heating coil. If the dehumidification
control type is specified as CoolReheat, a reheat coil component is also required. If the reheat coil is
present and the dehumidification control type input is not specified as CoolReheat, the reheat coil
will not be active,
Note: the coil order shown here has been revised from previous versions (prior to V4.0) of Energyplus
to configure the cooling coil upstream of the heating coil. This configuration provides uniformity
with all unitary equipment. However, for unitary HeatCool systems that do not use a reheat coil,
the heating coil can also be placed upstream of the cooling coil. This optional coil placement is
retained to allow compatibility with previous versions of Energyplus. For input files developed using
1470 CHAPTER 1. INPUT-OUTPUT REFERENCE
previous versions of Energyplus, it is recommended that the coil order be revised according to the
figure above.
Links to the fan, heating coil, DX cooling coil and optional reheat coil specifications are provided in
the furnace input data syntax. In addition, the control zone name and the furnace design operating
conditions are specified by the furnace inputs.
1.31.4.1 Inputs
– Coil:Heating:Electric
– Coil:Heating:Fuel
– Coil:Heating:Water
– Coil:Heating:Steam
1472 CHAPTER 1. INPUT-OUTPUT REFERENCE
– Coil:Cooling:DX:SingleSpeed
– CoilSystem:Cooling:DX:HeatExchangerAssisted
– Coil:Cooling:DX:VariableSpeed
The default is None. For the other dehumidification control modes, the maximum humidity setpoint
is used. This must be set using a ZoneControl:Humidistat object. When extra dehumidification
is required, the system may not be able to meet the humidity setpoint if its full capacity is not
adequate. If the dehumidification control type is specified as CoolReheat, then two additional
inputs (reheat coil type and name) are also required as shown below. Although the reheat coil
is required only when CoolRheat is selected, the optional reheat coil may be present for any of
the allowed Dehumidification Control Types. If the reheat coil is present and the dehumidification
control type is not specified as CoolReheat, the reheat coil will not be active,
– Coil:Heating:Electric
– Coil:Heating:Fuel
– Coil:Heating:Desuperheater
– Coil:Heating:Water
– Coil:Heating:Steam
Note: the furnace’s fan, cooling coil, heating coil and optional reheat coil must be connected in the
air loop according to the configuration shown above (Figure 1.146) when CoolReheat is selected as
the dehujmidificaiton control type. In addition, the volumetric air flow rate specified in the terminal
air unit for the controlling zone should properly reflect the fractional volumetric air flow rate specified
in the furnace object.
AirLoopHVAC:Unitary:Furnace:HeatCool ,
GasHeat DXAC Furnace 1, !- Name of furnace
FanAndCoilAvailSched , !- Availability schedule
Air Loop Inlet Node , !- Furnace inlet node name
Air Loop Outlet Node , !- Furnace outlet node name
CycFanSchedule , !- Supply Air Fan Operating Mode Schedule Name
80, !- Maximum supply air temperature from furnace heater {C}
1.3, !- Cooling Supply Air Flow Rate {m3/s}
1.3, !- Heating Supply Air Flow Rate {m3/s}
0.0, !- No Load Supply Air Flow Rate {m3/s}
East Zone , !- Controlling zone or thermostat location
Fan:OnOff , !- Supply fan type
Supply Fan 1, !- Supply fan name
BlowThrough , !- Fan Placement
Coil:Heating:Fuel , !- Heating coil type
Furnace Heating Coil 1, !- Heating coil name
Coil:Cooling:DX:SingleSpeed , !- Cooling coil type
Furnace ACDXCoil 1, !- Cooling coil name
None; !- Dehumidificatioin Control Type
Coil:Heating:Fuel ,
Furnace Heating Coil 1, !- Coil Name
FanAndCoilAvailSched , !- Availability Schedule Name
NaturalGas , !- Fuel Type
0.8, !- Gas Burner Efficiency of the Coil
25000 , !- Nominal Capacity of the Coil {W}
Heating Coil Air Inlet Node , !- Coil\_Air\_Inlet\_Node
Air Loop Outlet Node; !- Coil\_Air\_Outlet\_Node
1474 CHAPTER 1. INPUT-OUTPUT REFERENCE
Coil:Cooling:DX:SingleSpeed ,
Furnace ACDXCoil 1, !- Coil Name
FanAndCoilAvailSched , !- Availability Schedule
25000 , !- Rated Total Cooling Capacity (gross) {W}
0.75, !- Rated SHR
3.0, !- Rated COP
1.3, !- Rated Air Volume Flow Rate {m3/s}
DX Cooling Coil Air Inlet Node , !- Coil Air Inlet Node
Heating Coil Air Inlet Node , !- Coil Air Outlet Node
WindACCoolCapFT , !- Total Cooling Capacity Modifier Curve (function of temperature)
WindACCoolCapFFF , !- Total Cooling Capacity Modifier Curve (function of flow fraction)
WindACEIRFT , !- Energy Input Ratio Modifier Curve (function of temperature)
WindACEIRFFF , !- Energy Input Ratio Modifier Curve (function of flow fraction)
WindACPLFFPLR , !- Part Load Fraction Correlation (function of part load ratio)
CyclingFanAndCompressor ; !- Supply Air Fan Operation Mode
Fan:OnOff ,
Supply Fan 1, !- Fan Name
FanAndCoilAvailSched , !- Availability Schedule Name
0.7, !- Fan Total Efficiency
600.0 , !- Delta Pressure {Pa}
1.3, !- Max Flow Rate {m3/s}
0.9, !- Motor Efficiency
1.0, !- Motor In Airstream Fraction
Air Loop Inlet Node , !- Fan\_Inlet\_Node
DX Cooling Coil Air Inlet Node; !- Fan\_Outlet\_Node
AirTerminal:SingleDuct:ConstantVolume:NoReheat ,
Zone1DirectAir , !- Name
, !- Availability Schedule Name
Zone 1 Terminal Inlet Node , !- Air Inlet Node Name
Zone 1 Supply Node , !- Air Outlet Node Name
0.47; !- Maximum air flow rate {m3/s}
AirTerminal:SingleDuct:ConstantVolume:NoReheat ,
Zone2DirectAir , !- Name
, !- Availability Schedule Name
Zone 2 Terminal Inlet Node , !- Air Inlet Node Name
Zone 2 Supply Node , !- Air Outlet Node Name
0.36; !- Maximum air flow rate {m3/s}
AirTerminal:SingleDuct:ConstantVolume:NoReheat ,
Zone3DirectAir , !- Name
, !- Availability Schedule Name
Zone 3 Terminal Inlet Node , !- Air Inlet Node Name
Zone 3 Supply Node , !- Air Outlet Node Name
0.47; !- Maximum air flow rate {m3/s}
1.31.4.2 Outputs
furnace heating (or cooling) capacity. For the cycling fan mode, the runtime fraction for the furnace
fan may be different from the fan part-load ratio reported here due the part-load performance of
the furnace’s heating (or cooling) coil (delay at start-up to reach steady-state output). In general,
runtime fractions are reported by individual components where appropriate (e.g., Fan:OnOff).
Unitary System Compressor Part Load Ratio []
1.31.5 AirLoopHVAC:UnitaryHeatCool
The AirLoopHVAC:UnitaryHeatCool object is the identical model to the AirLoopHAVC:Unitary:Furnace:HeatCo
object. The heat/cool unitary system is a “virtual” component that consists of a fan component
(OnOff or ConstantVolume), a DX cooling coil component and a Gas or Electric heating coil
component as shown in Figure 1.147. When a draw through configuration is desired, the fan is
placed directly after the heating coil. If dehumidification control is selected, a reheat coil component
is also required. If the reheat coil is present and the dehumidification control type input is not
specified as CoolReheat, the reheat coil will not be active,
Note: the coil order shown here has been revised from previous versions (prior to V4.0) of Energyplus
to configure the cooling coil upstream of the heating coil. This configuration provides uniformity
with all unitary equipment. However, for unitary HeatCool systems that do not use a reheat coil,
the heating coil can also be placed upstream of the cooling coil. This optional coil placement is
retained to allow compatibility with previous versions of Energyplus. For input files developed using
previous versions of Energyplus, it is recommended that the coil order be revised according to the
figure above.
Links to the fan, DX cooling coil, heating coil and optional reheat coil specifications are provided
in the unitary system input data syntax. In addition, the control zone name and the system design
operating conditions are specified by the unitary system inputs.
This alpha field contains the identifying name for the unitary system.
This alpha field contains the schedule name which contains information on the availability of the
unitary system to operate. A schedule value equal to 0 denotes that the unitary system must be off
for that time period. A value greater than 0 denotes that the unitary system is available to operate
during that time period. This schedule may be used to completely disable the unitary system as
required. If this field is left blank, the schedule has a value of 1 for all time periods.
This alpha field contains the unitary system inlet node name.
This alpha field contains the unitary system outlet node name.
1476 CHAPTER 1. INPUT-OUTPUT REFERENCE
This alpha field specifies the name of the supply air fan operating mode schedule. The supply air
fan operating mode may vary during the simulation based on time-of-day or with a change of season.
Schedule values of 0 denote that the unitary system supply air fan and the heating or cooling coil
cycle on and off together to meet the heating or cooling load (a.k.a. AUTO fan). Schedule values
other than 0 denote that the supply fan runs continuously while the heating or cooling coil cycles to
meet the load.
This numeric field contains the design operating air outlet temperature in degrees C when the unitary
system is heating. If this input field is left blank, the default value is 80 C.
This numeric field defines the supply air flow rate leaving the unitary system in cubic meters per
second when the DX cooling coil is operating. Values must be greater than 0 or this field is autosiz-
able.
This numeric field defines the supply air flow rate leaving the unitary system in cubic meters per
second when the DX heating coil and/or supplemental heater are operating. Values must be greater
than 0 or this field is autosizable.
This numeric field defines the supply air flow rate leaving the unitary system in cubic meters per
second when neither cooling or heating is required (i.e., DX coils and supplemental heater are off
but the supply air fan operates). This field is only used when the unitary system operating mode is
specified as continuous fan operation. Values must be greater than or equal to zero, or this field is
autosizable. If the unitary system operating mode is specified as continuous fan operation and this
value is set to zero or this field is left blank, then the model assumes that the supply air flow rate
when no cooling/heating is needed is equal to the supply air flow rate when the compressor was last
operating (for cooling operation or heating operation).
This alpha field contains the identifying zone name where the thermostat controlling the unitary
system is located.
This alpha field contains the identifying type of supply air fan specified for the unitary system. Fan
type must be Fan:OnOff or Fan:ConstantVolume. Fan:ConstantVolume is used when the Supply
Air Fan Operating Mode Schedule values are never 0 and the fan operates continuously. Fan:OnOff
1478 CHAPTER 1. INPUT-OUTPUT REFERENCE
is used when the fan cycles on and off with the cooling or heating coil (i.e. Supply Air Fan Operating
Mode Schedule values are at times 0).
This alpha field contains the identifying name given to the unitary system fan.
This alpha field has two choices: BlowThrough or DrawThrough. The first choice stands for
“blow through fan”. This means that the unit consists of a fan followed by the DX coils and
supplemental heating coil. The fan “blows through” the cooling and heating coils. The second
choice stands for “draw through fan”. This means that the unit consists of the DX coil(s) followed
by a fan, with the supplemental heater located at the outlet of the fan. The fan “draws air through”
the DX coil(s). If this field is left blank, the default is blow through.
This alpha field contains the identifying type of heating coil specified in the unitary system. The
hot water and steam heating coils require specifying plant loop, branches, and connector objects to
support the heating coils, and are placed on the demand side of the plantloop. The hot water flow
modulation through the heating coil does not require additional controller or Controller:WaterCoil
object. The parent object (Unitary Heat and Cool System) itself provides the “controller” function
of modulating water flow. Allowable coil types are:
– Coil:Heating:Electric
– Coil:Heating:Fuel
– Coil:Heating:Water
– Coil:Heating:Steam
This alpha field contains the identifying name given to the unitary system heating coil.
This alpha field contains the identifying type of cooling coil specified in the unitary system. Only
allowable coil types are:
– Coil:Cooling:DX:SingleSpeed
– CoilSystem:Cooling:DX:HeatExchangerAssisted
– Coil:Cooling:DX:VariableSpeed
This alpha field contains the identifying name given to the unitary system cooling coil.
1.31. GROUP – UNITARY EQUIPMENT 1479
This alpha field contains the type of dehumidification control. The following options are valid for
this field:
The default is None. For the other dehumidification control modes, the maximum humidity setpoint
is used. This must be set using a ZoneControl:Humidistat object. When extra dehumidification
is required, the system may not be able to meet the humidity setpoint if its full capacity is not
adequate. If the dehumidification control type is specified as CoolReheat, then two additional
inputs (reheat coil type and name) are also required as shown below. Although the reheat coil is
required only when CoolReheat is selected, the optional reheat coil may be present for any of
the allowed Dehumidification Control Types. If the reheat coil is present and the dehumidification
control type is not specified as CoolReheat, the reheat coil will not be active,
This alpha field contains the identifying type of reheat coil specified in the unitary system. The
hot water and steam heating coils require specifying plant loop, branches, and connector objects to
support the heating coils, and are placed on the demand side of the plantloop. The hot water flow
modulation through the reheat coil does not require additional controller or Controller:WaterCoil
object. The parent object (Unitary Heat and Cool System) itself provides the “controller” function
of modulating water flow. Reheat coil type must be one of:
– Coil:Heating:Electric
– Coil:Heating:Fuel
– Coil:Heating:Desuperheater
– Coil:Heating:Water
– Coil:Heating:Steam
This alpha field contains the identifying name given to the unitary system reheat coil.
As shown in the example below, correct specification of the heat/cool unitary system requires spec-
ification of the following objects in addition to the unitary system object:
1) Fan (Fan:OnOff or Fan:ConstantVolume)
2) Cooling coil (Coil:Cooling:DX:SingleSpeed or CoilSystem:Cooling:DX:HeatExchangerAssisted)
1480 CHAPTER 1. INPUT-OUTPUT REFERENCE
AirLoopHVAC:Unitary:Furnace:HeatCool ,
GasHeat DXAC Unitary System 1, !- Name of unitary system
FanAndCoilAvailSched , !- Availability schedule
Air Loop Inlet Node , !- Unitary system inlet node name
Air Loop Outlet Node , !- Unitary system outlet node name
CycFanSchedule , !- Supply Air Fan Operating Mode Schedule Name
80, !- Maximum supply air temperature from unitary system heater {C}
1.3, !- Cooling Supply Air Flow Rate {m3/s}
1.3, !- Heating Supply Air Flow Rate {m3/s}
0.0, !- No Load Supply Air Flow Rate {m3/s}
East Zone , !- Controlling zone or thermostat location
Fan:OnOff , !- Supply fan type
Supply Fan 1, !- Supply fan name
BlowThrough , !- Fan Placement
Coil:Heating:Fuel , !- Heating coil type
Unitary System Heating Coil 1, !- Heating coil name
Coil:Cooling:DX:SingleSpeed , !- Cooling coil type
Unitary System ACDXCoil 1, !- Cooling coil name
None; !- High humidity control
Coil:Heating:Fuel ,
Unitary System Heating Coil 1, !- Coil Name
FanAndCoilAvailSched , !- Availability Schedule Name
NaturalGas , !- Fuel Type
0.8, !- Gas Burner Efficiency of the Coil
25000 , !- Nominal Capacity of the Coil {W}
Heating Coil Air Inlet Node , !- Coil\_Air\_Inlet\_Node
Air Loop Outlet Node; !- Coil\_Air\_Outlet\_Node
Coil:Cooling:DX:SingleSpeed ,
Unitary System ACDXCoil 1, !- Coil Name
FanAndCoilAvailSched , !- Availability Schedule
25000 , !- Rated Total Cooling Capacity (gross) {W}
0.75, !- Rated SHR
3.0, !- Rated COP
1.3, !- Rated Air Volume Flow Rate {m3/s}
DX Cooling Coil Air Inlet Node , !- Coil Air Inlet Node
Heating Coil Air Inlet Node , !- Coil Air Outlet Node
WindACCoolCapFT , !- Total Cooling Capacity Modifier Curve (function of temperature)
WindACCoolCapFFF , !- Total Cooling Capacity Modifier Curve (function of flow fraction)
WindACEIRFT , !- Energy Input Ratio Modifier Curve (function of temperature)
WindACEIRFFF , !- Energy Input Ratio Modifier Curve (function of flow fraction)
WindACPLFFPLR , !- Part Load Fraction Correlation (function of part load ratio)
CyclingFanAndCompressor ; !- Supply Air Fan Operation Mode
Fan:OnOff ,
Supply Fan 1, !- Fan Name
FanAndCoilAvailSched , !- Availability Schedule Name
0.7, !- Fan Total Efficiency
600.0 , !- Delta Pressure {Pa}
1.3, !- Max Flow Rate {m3/s}
0.9, !- Motor Efficiency
1.0, !- Motor In Airstream Fraction
Air Loop Inlet Node , !- Fan\_Inlet\_Node
1.31. GROUP – UNITARY EQUIPMENT 1481
AirTerminal:SingleDuct:ConstantVolume:NoReheat ,
Zone1DirectAir , !- Name
, !- Availability Schedule Name
Zone 1 Terminal Inlet Node , !- Air Inlet Node Name
Zone 1 Supply Node , !- Air Outlet Node Name
0.47; !- Maximum air flow rate {m3/s}
AirTerminal:SingleDuct:ConstantVolume:NoReheat ,
Zone2DirectAir , !- Name
, !- Availability Schedule Name
Zone 2 Terminal Inlet Node , !- Air Inlet Node Name
Zone 2 Supply Node , !- Air Outlet Node Name
0.36; !- Maximum air flow rate {m3/s}
AirTerminal:SingleDuct:ConstantVolume:NoReheat ,
Zone3DirectAir , !- Name
, !- Availability Schedule Name
Zone 3 Terminal Inlet Node , !- Air Inlet Node Name
Zone 3 Supply Node , !- Air Outlet Node Name
0.47; !- Maximum air flow rate {m3/s}
This output variable is the ratio of actual air mass flow rate through the unitary system to the
system’s design air mass flow rate (i.e., design volumetric flow rate converted to dry air mass flow
rate). For continuous fan operation mode, this variable is always 1.0 when the unitary system is
available (based on the availability schedule). For cycling fan/cycling coil operation mode, the actual
air mass flow rate is calculated based on the ratio of the sensible heating (or cooling) load to the
steady-state unitary system heating (or cooling) capacity. For the cycling fan mode, the runtime
fraction for the unitary system fan may be different from the fan part-load ratio reported here
due the part-load performance of the system’s heating (or cooling) coil (delay at start-up to reach
steady-state output). In general, runtime fractions are reported by individual components where
appropriate (e.g., Fan:OnOff).
This output variable is the ratio of the sensible cooling load to the steady-state cooling capacity
of the unitary system’s DX cooling coil. The runtime fraction for the DX cooling coil compressor
may be different from the compressor part-load ratio reported here due the part-load performance
of the cooling coil (delay at start-up to reach steady-state output). In general, runtime fractions are
reported by individual components where appropriate.
1482 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.31.7 AirLoopHVAC:UnitaryHeatPump:AirToAir
The unitary air-to-air heat pump is a “virtual” component that consists of a fan component (OnOff
or ConstantVolume), a DX cooling coil component, a DX heating coil component, and a Gas or
Electric supplementary heating coil component as shown in the Figure below.
Figure 1.148: Schematic of EnergyPlus Unitary Air-to-Air Heat Pump (Blow Through Configura-
tion)
Links to the fan, DX cooling coil, DX heating coil, and supplementary heating coil specifications are
provided in the heat pump’s input data syntax. In addition the control zone name and the system
design operating conditions are specified by the heat pump inputs.
1.31.7.1 Inputs
– Coil:Cooling:DX:SingleSpeed
– CoilSystem:Cooling:DX:HeatExchangerAssisted
– Coil:Cooling:DX:VariableSpeed
– Coil:Heating:Electric
– Coil:Heating:Fuel
– Coil:Heating:Water
– Coil:Heating:Steam
This numeric field defines the maximum allowed supply air temperature exiting the heat pump
supplemental heating coil.
– CoolReheat - cool beyond the dry-bulb temperature set point as required to meet
the high humidity setpoint. The excess cooling beyond the cooling set point tem-
perature is offset by the supplemental heating coil. If cooling coil type = CoilSys-
tem:Cooling:DX:HeatExchangerAssisted, then the heat exchanger is assumed to always
transfer energy between the cooling coil’s inlet and outlet airstreams when the cooling coil is
operating.
The default is None. For the other dehumidification control modes, the maximum humidity setpoint
is required. This must be set using a ZoneControl:Humidistat object. When extra dehumidifi-
cation is required, the system may not be able to meet the humidity setpoint if its full capacity is
not adequate. Supplemental heating coil (supplemental heating coil type and name) is a required
input in AirToAir HeatPumps. The supplemental heating coil capacity must be adequate enough to
meet the heating coil load and offset the excess cooling load due to extra dehumidification required
to meet the high relative humidity setpoint.
Note: the air-to-air heat pump’s fan, cooling coil, heating coil and supplementary heating coil must
be connected in the air loop according to the configuration shown above (Figure 118) for the blow-
through fan configuration. The only other valid configuration is with a draw-through fan placement,
where the fan is located between the DX heating coil and the supplementary heating coil.
AirLoopHVAC:UnitaryHeatPump:AirToAir ,
DXAC Heat Pump 1, ! Heat Pump name
FanAndCoilAvailSched , ! Heat Pump availability schedule
Mixed Air Node , ! Heat Pump air inlet node
Air Loop Outlet Node , ! Heat Pump air outlet node
1.3, !- Cooling Supply Air Flow Rate {m3/s}
1.3, !- Heating Supply Air Flow Rate {m3/s}
0.0, !- No Load Suuply Air Flow Rate {m3/s}
East Zone , ! Controlling zone or thermostat location
Fan:OnOff , ! Supply air fan type
Supply Fan 1, ! Supply air fan name –- same name used in fan object
Coil:Heating:DX:SingleSpeed , ! Heating coil type
Heat Pump DX Heating Coil 1, ! Heating coil name –- same name used in DX heating coil
object
Coil:Cooling:DX:SingleSpeed , ! Cooling coil type
Heat Pump ACDXCoil 1, ! Cooling coil name –- same name used in DX cooling coil
object
Coil:Heating:Fuel , ! Supplemental heating coil type
Heat Pump DX Supp Heating Coil 1, ! Supplemental heating coil –name - same as in heating
coil object
50, ! Maximum supply air temperature from supplemental heater [C]
21, ! Maximum outdoor dry -bulb temp for supplemental heating coil
operation [C]
BlowThrough , ! Fan placement
CycFanSchedule , ! Supply air fan operating mode schedule name
CoolReheat; !- Dehumidification Control Type
Coil:Heating:DX:SingleSpeed ,
Heat Pump DX Heating Coil 1, ! Name of heating coil
FanAndCoilAvailSched , ! Heating coil schedule
35000 , ! Rated total heating capacity [W] (at 21.11C/8.33C)
2.75, ! Rated heating COP
1.7, ! Rated air flow rate [m3/s]
Heating Coil Air Inlet Node , ! Coil air inlet node
SuppHeating Coil Air Inlet Node , ! Coil air outlet node
HPACHeatCapFT , ! Heating capacity modifier curve (temperature ,C)
HPACHeatCapFFF , ! Heating capacity modifier curve (flow fraction)
HPACHeatEIRFT , ! Energy input ratio modifier curve (temperature ,C)
1.31. GROUP – UNITARY EQUIPMENT 1487
Coil:Cooling:DX:SingleSpeed ,
Heat Pump ACDXCoil 1, ! Name of cooling coil
FanAndCoilAvailSched , ! Availability schedule
32000 , ! Rated total cooling capacity [W]
0.75, ! Rated sensible heat ratio
3.0, ! Rated COP
1.7, ! Rated air flow rate [m3/s]
DX Cooling Coil Air Inlet Node , ! Coil air inlet node
Heating Coil Air Inlet Node , ! Coil air outlet node
HPACCoolCapFT , ! Cooling capacity modifier curve (temperature ,C)
HPACCoolCapFFF , ! Cooling capacity modifier curve (flow fraction)
HPACCoolEIRFT , ! Energy input ratio modifier curve (temperature ,C)
HPACCoolEIRFFF , ! Energy input ratio modifier curve (flow fraction)
HPACCoolPLFFPLR , ! Part load factor modifier curve (function of part -load
ratio)
CyclingFanAndCompressor ; ! Operation mode (cycling fan , cycling
compressor)
Coil:Heating:Fuel ,
Heat Pump DX Supp Heating Coil 1, ! Name of heating coil
FanAndCoilAvailSched , ! Availability schedule
NaturalGas , ! Fuel Type
0.8 , ! Gas Burner Efficiency of the Coil
32000 , ! Nominal Capacity of the Coil [W]
SuppHeating Coil Air Inlet Node , ! Supplementary heating coil air side inlet node
Air Loop Outlet Node; ! Supplementary heating coil air side outlet node
Fan:OnOff ,
Supply Fan 1, ! Fan Name
FanAndCoilAvailSched , ! Fan Schedule
0.7, ! Fan Total Efficiency
300.0 , ! Delta Pressure [N/M^2]
1.7, ! Max Vol Flow Rate [m^3/ Sec]
0.9, ! motor efficiency
1.0, ! motor in air stream fraction
Mixed Air Node , ! fan inlet node
DX Cooling Coil Air Inlet Node; ! fan outlet node
AirTerminal:SingleDuct:ConstantVolume:NoReheat ,
Zone1DirectAir , !- Name
, !- Availability Schedule Name
Zone 1 Terminal Inlet Node , !- Air Inlet Node Name
Zone 1 Supply Node , !- Air Outlet Node Name
0.612; !- Maximum air flow rate {m3/s}
AirTerminal:SingleDuct:ConstantVolume:NoReheat ,
Zone2DirectAir , !- Name
, !- Availability Schedule Name
Zone 2 Terminal Inlet Node , !- Air Inlet Node Name
Zone 2 Supply Node , !- Air Outlet Node Name
0.476; !- Maximum air flow rate {m3/s}
AirTerminal:SingleDuct:ConstantVolume:NoReheat ,
1488 CHAPTER 1. INPUT-OUTPUT REFERENCE
Zone3DirectAir , !- Name
, !- Availability Schedule Name
Zone 3 Terminal Inlet Node , !- Air Inlet Node Name
Zone 3 Supply Node , !- Air Outlet Node Name
0.612; !- Maximum air flow rate {m3/s}
1.31.7.2 Outputs
This output variable is the additional heating demand rate of the supplemental heating coil of an Air-
to-Air heat pumps in Watts. This additional heating demand is induced when zone air overshoots
the heating setpoint due to extra dehumidification requirement to meet the high humidity setpoint.
This value is always positive. This value is calculated for each HVAC system timestep, and the
results are averaged for the timestep being reported.
1.31.8 AirLoopHVAC:UnitaryHeatPump:AirToAir:MultiSpeed
The multispeed air-to-air heat pump is a “virtual” component that consists of a fan component
(On/Off or ConstVolume), a DX multispeed cooling coil component, a DX multispeed heating coil
component, and a Gas or Electric supplemental heating coil component. This system also includes the
option to use available waste energy to heat water. A schematic diagram of the air-to-air multispeed
heat pump is shown below. The component connection sequence for the blow through option (shown
1.31. GROUP – UNITARY EQUIPMENT 1489
below) from inlet to outlet is fan, cooling coil, heating coil, and supplemental heater. The connection
sequence for the draw through option is cooling coil, heating coil, fan, and supplemental heater.
The main difference between this heat pump object and other EnergyPlus heat pump objects is that
this object allows from two to four discrete compressor speeds for heating and cooling operation
(instead of a single speed for each mode). The lowest speed is called Speed 1, and the highest speed
is called Speed n (2, 3 or 4 as specified in the input syntax). This object allows a different number of
speeds for cooling and heating, and each speed has an associated airflow rate. The airflow rates for
the various heating speeds can be different from the airflow rates for the cooling speeds. In addition,
the airflow rate when no cooling or heating is needed can also be defined. The number of cooling
and heating speeds defined by the user in this heat pump object must equal the number of speeds
defined in the associated coils (child objects). For example, the number of speeds for cooling defined
in this heat pump object must be equal to the number of speeds defined in the associated cooling
coil object.
Links to the fan, DX multispeed cooling coil, DX multispeed heating coil, and supplementary heating
coil specifications are provided in the heat pump’s input data syntax. In addition, the control zone
name and airflow rates at the corresponding compressor speeds are specified by the heat pump
syntax.
If the ZoneControl:Thermostat:StagedDualSetpoint object and other zone control thermostat and
humidistat are assigned to the same controlled zone in the Controlling Zone or Thermostat Loca-
tion field, the ZoneControl:Thermostat:StagedDualSetpoint object takes precedence and the stage
number provided by the the ZoneControl:Thermostat:StagedDualSetpoint object is used to set the
speed number.
1.31.8.1 Inputs
Figure 1.149: Schematic of EnergyPlus Unitary Air-to-Air Multi Speed Heat Pump
1.31. GROUP – UNITARY EQUIPMENT 1491
– Coil:Heating:Electric
– Coil:Heating:Fuel
– Coil:Heating:Water
– Coil:Heating:Steam
This numeric field defines the maximum allowed supply air temperature (in degrees C) exiting
the heat pump supplemental heating coil. If the calculated supply air temperature exiting the
supplemental heater exceeds this value, then it is reset to this maximum temperature. This field is
autosizable.
AirLoopHVAC:UnitaryHeatPump:AirToAir:MultiSpeed ,
DXAC Heat Pump 1, !- Name of multispeed heat pump
FanAndCoilAvailSched , !- Availability schedule
Mixed Air Node , !- Heat pump air inlet node name
Air Loop Outlet Node , !- Heat pump air outlet node name
East Zone , !- Controlling zone or thermostat location
Fan:OnOff , !- Supply air fan type
Supply Fan 1, !- Supply air fan name
BlowThrough , !- Supply air fan placement
FanModeSchedule , !- Supply air fan operating mode schedule name
Coil:Heating:DX:MultiSpeed , Heat Pump DX Heating Coil 1, !- Heating coil type & name
-8.0, !- Minimum outdoor dry -bulb temperature for compressor operation
Coil:Cooling:DX:MultiSpeed , Heat Pump ACDXCoil 1, !- Cooling coil type & name
1496 CHAPTER 1. INPUT-OUTPUT REFERENCE
Coil:Heating:DX:MultiSpeed ,
Heat Pump DX Heating Coil 1, !- Name of heat pump heating coil
FanAndCoilAvailSched , !- Availability Schedule
Heating Coil Air Inlet Node , !- Coil Air Inlet Node
SuppHeating Coil Air Inlet Node , !- Coil Air Outlet Node
CyclingFanAndCompressor , !- Supply Air Fan Operation Mode
-8.0, !- Minimum Outdoor Dry -bulb Temperature for Compressor Operation {C}
200.0 , !- Crankcase Heater Capacity {W}
10.0, !- Maximum Outdoor Dry -bulb Temperature for Crankcase Heater
!- Operation {C}
HPACDefrostCAPFT , !- Defrost energy input ratio modifier curve (temperature)
7.22, !- Maximum Outdoor Dry -bulb Temperature for Defrost Operation
reverse -cycle , !- Defrost Strategy
timed , !- Defrost Control
0.058333 , !- Defrost Time Period Fraction
2000.0 , !- Resistive Defrost Heater Capacity {W}
No , !- Apply Part Load Fraction to Speeds greater than 1
NaturalGas , !- Fuel type
4, !- Number of speeds
7500, !- Rated Total Heating Capacity , Speed 1 {W}
2.75, !- Rated COP , Speed 1
0.45, !- Rated Air Volume Flow Rate , Speed 1 {m3/s}
HPACHeatCapFT Speed 1, !- Total Heating Capacity Modifier Curve , Speed 1 (temperature)
HPACHeatCapFF Speed 1, !- Total Heating capacity modifier curve , Speed 1 (flow fraction)
HPACHeatEIRFT Speed 1, !- Energy input ratio modifier curve , Speed 1 (temperature)
HPACHeatEIRFF Speed 1, !- Energy input ratio modifier curve , Speed 1 (flow fraction)
HPACHeatPLFFPLR Speed 1, !- Part load fraction correlation , Speed 1 (part load ratio)
0.2, !- Rated waste heat fraction of power input , Speed 1
HAPCHeatWHFT Speed 1, !- Waste heat modifier curve , Speed 1 (temperature)
17500 , !- Rated Total Heating Capacity , Speed 2 {W}
2.75, !- Rated COP , Speed 2
0.85, !- Rated Air Volume Flow Rate , Speed 2 {m3/s}
HPACHeatCapFT Speed 2, !- Total Heating Capacity Modifier Curve , Speed 2 (temperature)
HPACHeatCapFF Speed 2, !- Total Heating capacity modifier curve , Speed 2 (flow fraction)
HPACHeatEIRFT Speed 2, !- Energy input ratio modifier curve , Speed 2 (temperature)
HPACHeatEIRFF Speed 2, !- Energy input ratio modifier curve , Speed 2 (flow fraction)
HPACHeatPLFFPLR Speed 2, !- Part load fraction correlation , Speed 2 (part load ratio)
0.2, !- Rated waste heat fraction of power input , Speed 2
HAPCHeatWHFT Speed 2, !- Waste heat modifier curve , Speed 2 (temperature)
25500 , !- Rated Total Heating Capacity , Speed 3 {W}
2.75, !- Rated COP , Speed 3
1.25, !- Rated Air Volume Flow Rate , Speed 3 {m3/s}
HPACHeatCapFT Speed 3, !- Total Heating Capacity Modifier Curve , Speed 3 (temperature)
HPACHeatCapFF Speed 3, !- Total Heating capacity modifier curve , Speed 3 (flow fraction)
HPACHeatEIRFT Speed 3, !- Energy input ratio modifier curve , Speed 3 (temperature)
HPACHeatEIRFF Speed 3, !- Energy input ratio modifier curve , Speed 3 (flow fraction)
HPACHeatPLFFPLR Speed 3, !- Part load fraction correlation , Speed 3 (part load ratio)
0.2, !- Rated waste heat fraction of power input , Speed 3
HAPCHeatWHFT Speed 3, !- Waste heat modifier curve , Speed 3 (temperature)
1.31. GROUP – UNITARY EQUIPMENT 1497
COIL:Cooling:DX:MultiSpeed ,
Heat Pump ACDXCoil 1, !- Coil Name
FanAndCoilAvailSched , !- Availability Schedule
DX Cooling Coil Air Inlet Node , !- Coil Air Inlet Node
Heating Coil Air Inlet Node , !- Coil Air Outlet Node
CyclingFanAndCompressor , !- Supply Air Fan Operation Mode
Outdoor Condenser Air Node , !- Condenser Air Inlet Node Name
AirCooled , !- Condenser Type
, !- Name of Water Storage Tank for Supply
, !- Name of Water Storage Tank for Condensate Collection
No , !- Apply Part Load Fraction to Speeds greater than 1
No , !- Apply Latent Degradation to Speeds greater than 1
200.0 , !- Crankcase Heater Capacity {W}
10.0, !- Maximum Outdoor Dry -bulb Temperature for Crankcase Heater
Operation {C}
NaturalGas , !- Fuel type
4, !- Number of speeds
7500, !- Rated Total Cooling Capacity , Speed 1 (gross) {W}
0.75, !- Rated SHR , Speed 1
3.0, !- Rated COP , Speed 1
0.40, !- Rated Air Volume Flow Rate , Speed 1 {m3/s}
HPACCoolCapFT Speed 1, !- Total Cooling Capacity Modifier Curve , Speed 1 (temperature)
HPACCoolCapFF Speed 1, !- Total Cooling Capacity Modifier Curve , Speed 1 (flow fraction)
HPACCOOLEIRFT Speed 1, !- Energy Input Ratio Modifier Curve , Speed 1 (temperature)
HPACCOOLEIRFF Speed 1, !- Energy Input Ratio Modifier Curve , Speed 1 (flow fraction)
HPACCOOLPLFFPLR Speed 1, !- Part Load Fraction Correlation , Speed 1 (part load ratio)
1000.0 , !- Nominal Time for Condensate Removal to Begin , Speed 1 {s}
1.5, !- Ratio of Initial Moisture Evaporation Rate and Steady -state
Latent Capacity , Speed 1 {dimensionless}
3.0, !- Maximum ON/OFF Cycling Rate , Speed 1 {cycles/hr}
45.0, !- Latent Capacity Time Constant , Speed 1 {s}
0.2, !- Rated waste heat fraction of power input , Speed 1 {dimensionless}
HAPCCoolWHFT Speed 1, !- Waste heat modifier curve , Speed 1 (temperature)
0.9, !- Evaporative Condenser Effectiveness , Speed 1 {dimensionless}
0.05, !- Evaporative Condenser Air Volume Flow Rate , Speed 1 {m3/s}
50, !- Evaporative Condenser Pump Rated Power Consumption , Speed 1 {W}
17500 , !- Rated Total Cooling Capacity , Speed 2 (gross) {W}
0.75, !- Rated SHR , Speed 2
3.0, !- Rated COP , Speed 2
0.85, !- Rated Air Volume Flow Rate , Speed 2 {m3/s}
HPACCoolCapFT Speed 2, !- Total Cooling Capacity Modifier Curve , Speed 2 (temperature)
HPACCoolCapFF Speed 2, !- Total Cooling Capacity Modifier Curve , Speed 2 (flow fraction)
HPACCOOLEIRFT Speed 2, !- Energy Input Ratio Modifier Curve , Speed 2 (temperature)
HPACCOOLEIRFF Speed 2, !- Energy Input Ratio Modifier Curve , Speed 2 (flow fraction)
HPACCOOLPLFFPLR Speed 1, !- Part Load Fraction Correlation , Speed 2 (part load ratio)
1000.0 , !- Nominal Time for Condensate Removal to Begin , Speed 2 {s}
1.5, !- Ratio of Initial Moisture Evaporation Rate and Steady -state
Latent Capacity , Speed 2 {dimensionless}
3.0, !- Maximum ON/OFF Cycling Rate , Speed 2 {cycles/hr}
45.0, !- Latent Capacity Time Constant , Speed 2 {s}
0.2, !- Rated waste heat fraction of power input , Speed 2 {dimensionless}
HAPCCoolWHFT Speed 2, !- Waste heat modifier curve , Speed 2 (temperature)
0.9, !- Evaporative Condenser Effectiveness , Speed 2 {dimensionless}
0.1, !- Evaporative Condenser Air Volume Flow Rate , Speed 2 {m3/s}
60, !- Evaporative Condenser Pump Rated Power Consumption , Speed 2 {W}
25500 , !- Rated Total Cooling Capacity , Speed 3 (gross) {W}
0.75, !- Rated SHR , Speed 3
3.0, !- Rated COP , Speed 3
1498 CHAPTER 1. INPUT-OUTPUT REFERENCE
Coil:Heating:Fuel ,
Supp Gas Heating Coil 1, !- Coil Name
FanAndCoilAvailSched , !- Availability Schedule Name
NaturalGas , !- Fuel Type
0.8, !- Gas Burner Efficiency of the Coil
45000 , !- Nominal Capacity of the Coil {W}
SuppHeating Coil Air Inlet Node , !- Coil\_Air\_Inlet\_Node
Air Loop Outlet Node; !- Coil\_Air\_Outlet\_Node
Fan:OnOff ,
Supply Fan 1, !- Fan Name
FanAndCoilAvailSched , !- Availability Schedule Name
0.7, !- Fan Total Efficiency
300.0 , !- Delta Pressure {Pa}
1.7, !- Max Flow Rate {m3/s}
0.9, !- Motor Efficiency
1.0, !- Motor In Airstream Fraction
Mixed Air Node , !- Fan\_Inlet\_Node
DX Cooling Coil Air Inlet Node; !- Fan\_Outlet\_Node
AirTerminal:SingleDuct:ConstantVolume:NoReheat ,
Zone1DirectAir , !- Name
, !- Availability Schedule Name
Zone 1 Terminal Inlet Node , !- Air Inlet Node Name
Zone 1 Supply Node , !- Air Outlet Node Name
0.612; !- Maximum air flow rate {m3/s}
AirTerminal:SingleDuct:ConstantVolume:NoReheat ,
Zone2DirectAir , !- Name
, !- Availability Schedule Name
Zone 2 Terminal Inlet Node , !- Air Inlet Node Name
Zone 2 Supply Node , !- Air Outlet Node Name
0.476; !- Maximum air flow rate {m3/s}
1.31. GROUP – UNITARY EQUIPMENT 1499
AirTerminal:SingleDuct:ConstantVolume:NoReheat ,
Zone3DirectAir , !- Name
, !- Availability Schedule Name
Zone 3 Terminal Inlet Node , !- Air Inlet Node Name
Zone 3 Supply Node , !- Air Outlet Node Name
0.612; !- Maximum air flow rate {m3/s}
1.31.8.2 Outputs
outlet air and inlet air streams, and the air mass flow rate through the heat pump. This value is
calculated for each HVAC system timestep being simulated, and the results (enthalpy addition only)
are averaged for the timestep being reported.
is calculated for each HVAC system timestep being simulated, and the results are averaged for the
timestep being reported. Any non-electric energy use is not reported by the heat pump object but
is reported in the associated coil objects as appropriate.
1.31.8.2.19 Unitary System Heat Recovery Fluid Mass Flow Rate [kg/s]
These outputs are the heat recovery inlet and outlet temperatures and water mass flow rate for
multispeed heat pumps with heat recovery.
1.31.9 AirLoopHVAC:Unitary:Furnace:HeatOnly
The EnergyPlus furnace is a “virtual” component that consists of a fan component (OnOff or Con-
stantVolume) and a Gas or Electric heating coil component. The blow through furnace configuration
is shown in the Figure below.
Links to the fan and heating coil specifications are provided in the furnace input data syntax. In
addition the control zone name and the furnace design operating conditions are specified by the
furnace inputs.
1.31.9.1 Inputs
– Coil:Heating:Electric
– Coil:Heating:Fuel
– Coil:Heating:Water
– Coil:Heating:Steam
AirLoopHVAC:Unitary:Furnace:HeatOnly ,
Gas Furnace 1, !- Name
FanAndCoilAvailSched , !- Availability Schedule Name
Air Loop Inlet Node , !- Furnace Air Inlet Node Name
Air Loop Outlet Node , !- Furnace Air Outlet Node Name
CycFanSchedule , !- Supply Air Fan Operating Mode Schedule Name
80, !- Maximum Supply Air Temperature {C}
1.3, !- Heating Supply Air Flow Rate {m3/s}
East Zone , !- Controlling Zone or Thermostat Location
Fan:OnOff , !- Supply Fan Object Type
Supply Fan 1, !- Supply Fan Fame
BlowThrough , !- Fan Placement
Coil:Heating:Fuel , !- Heating Coil Object Type
Furnace Coil; !- Heating Coil Name
1506 CHAPTER 1. INPUT-OUTPUT REFERENCE
Coil:Heating:Fuel ,
Furnace Coil , !- Coil Name
FanAndCoilAvailSched , !- Availability Schedule Name
NaturalGas , !- Fuel Type
0.8, !- Gas Burner Efficiency of the Coil
20000 , !- Nominal Capacity of the Coil {W}
Heating Coil Air Inlet Node , !- Coil_Air_Inlet_Node
Air Loop Outlet Node , !- Coil_Air_Outlet_Node
, !- Coil_Temp_Setpoint_Node
100, !- Parasitic Electric Load {W}
PLFCurveforGasFurnace , !- Part load fraction correlation (function of part load ratio)
10; !- Parasitic Gas Load {W}
Curve:Cubic ,
PLFCurveforGasFurnace , !- Name
0.8, !- Coefficient1 Constant
0.2, !- Coefficient2 x
0.0, !- Coefficient3 x**2
0.0, !- Coefficient4 x**3
0, !- Minimum Value of x
1; !- Maximum Value of x
Fan:OnOff ,
Supply Fan 1, !- Fan Name
FanAndCoilAvailSched , !- Availability Schedule Name
0.7, !- Fan Total Efficiency
600.0 , !- Delta Pressure {Pa}
1.3, !- Max Flow Rate {m3/s}
0.9, !- Motor Efficiency
1.0, !- Motor In Airstream Fraction
Air Loop Inlet Node , !- Fan_Inlet_Node
Heating Coil Air Inlet Node; !- Fan_Outlet_Node
AirTerminal:SingleDuct:ConstantVolume:NoReheat ,
Zone1DirectAir , !- Name
, !- Availability Schedule Name
Zone 1 Terminal Inlet Node , !- Air Inlet Node Name
Zone 1 Supply Node , !- Air Outlet Node Name
0.47; !- Maximum air flow rate {m3/s}
AirTerminal:SingleDuct:ConstantVolume:NoReheat ,
Zone2DirectAir , !- Name
, !- Availability Schedule Name
Zone 2 Terminal Inlet Node , !- Air Inlet Node Name
Zone 2 Supply Node , !- Air Outlet Node Name
0.36; !- Maximum air flow rate {m3/s}
AirTerminal:SingleDuct:ConstantVolume:NoReheat ,
Zone3DirectAir , !- Name
, !- Availability Schedule Name
Zone 3 Terminal Inlet Node , !- Air Inlet Node Name
Zone 3 Supply Node , !- Air Outlet Node Name
0.47; !- Maximum air flow rate {m3/s}
1.31.9.2 Outputs
This output variable is the ratio of actual air mass flow rate through the furnace to the furnace’s
design air mass flow rate (i.e., design volumetric flow rate converted to dry air mass flow rate). For
continuous fan operation mode, this variable is always 1.0 when the furnace is available (based on
the availability schedule). For cycling fan/cycling coil operation mode, the actual air mass flow rate
is calculated based on the ratio of the sensible heating load to the furnace heating capacity. For the
cycling fan mode, the runtime fraction for the furnace fan may be different from the fan part-load
ratio reported here due the part-load performance of the furnace’s heating coil (delay at start-up
to reach steady-state heating output). In general, runtime fractions are reported by individual
components where appropriate (e.g., Fan:OnOff).
1.31.10 AirLoopHVAC:UnitaryHeatOnly
The AirLoopHVAC:UnitaryHeatOnly is identical to the AirLoopHVAC:Unitary:Furnace:HeatOnly
model. The heat-only unitary system is a “virtual” component that consists of a fan component
(OnOff or ConstantVolume) and a Gas or Electric heating coil component. The blow through
unitary system configuraion is shown in the Figure below.
Links to the fan and heating coil specifications are provided in the unitary system input data syntax.
In addition, the control zone name and the unitary system design operating conditions are specified
by the unitary system syntax.
1.31.10.1 Inputs
– Coil:Heating:Electric
– Coil:Heating:Fuel
– Coil:Heating:Water
– Coil:Heating:Steam
1510 CHAPTER 1. INPUT-OUTPUT REFERENCE
AirLoopHVAC:UnitaryHeatOnly ,
Gas Unitary System 1, !- Name
FanAndCoilAvailSched , !- Availability Schedule Name
Air Loop Inlet Node , !- Unitary System Air Inlet Node Name
Air Loop Outlet Node , !- Unitary System Air Outlet Node Name
CycFanSchedule , !- Supply Air Fan Operating Mode Schedule Name
80, !- Maximum Supply Air Temperature {C}
1.3, !- Heating Supply Air Flow Rate {m3/s}
East Zone , !- Controlling Zone or Thermostat Location
Fan:OnOff , !- Supply Fan Object Type
Supply Fan 1, !- Supply Fan Name
BlowThrough , !- Fan Placement
Coil:Heating:Fuel , !- Heating Coil Object Type
Unitary System Heating Coil; !- Heating Coil Name
Coil:Heating:Fuel ,
Unitary System Heating Coil , !- Coil Name
FanAndCoilAvailSched , !- Availability Schedule Name
NaturalGas , !- Fuel Type
0.8, !- Gas Burner Efficiency of the Coil
20000 , !- Nominal Capacity of the Coil {W}
Heating Coil Air Inlet Node , !- Coil_Air_Inlet_Node
Air Loop Outlet Node , !- Coil_Air_Outlet_Node
, !- Coil_Temp_Setpoint_Node
100, !- Parasitic Electric Load {W}
PLFCurveforUnitarySystem , !- Part load fraction correlation (function of part load ratio)
10; !- Parasitic Gas Load {W}
Curve:Cubic ,
PLFCurveforUnitarySystem , !- Name
0.8, !- Coefficient1 Constant
0.2, !- Coefficient2 x
0.0, !- Coefficient3 x**2
0.0, !- Coefficient4 x**3
0, !- Minimum Value of x
1; !- Maximum Value of x
Fan:OnOff ,
Supply Fan 1, !- Fan Name
FanAndCoilAvailSched , !- Availability Schedule Name
0.7, !- Fan Total Efficiency
600.0 , !- Delta Pressure {Pa}
1.3, !- Max Flow Rate {m3/s}
0.9, !- Motor Efficiency
1.31. GROUP – UNITARY EQUIPMENT 1511
AirTerminal:SingleDuct:ConstantVolume:NoReheat ,
Zone1DirectAir , !- Name
, !- Availability Schedule Name
Zone 1 Terminal Inlet Node , !- Air Inlet Node Name
Zone 1 Supply Node , !- Air Outlet Node Name
0.47; !- Maximum air flow rate {m3/s}
AirTerminal:SingleDuct:ConstantVolume:NoReheat ,
Zone2DirectAir , !- Name
, !- Availability Schedule Name
Zone 2 Terminal Inlet Node , !- Air Inlet Node Name
Zone 2 Supply Node , !- Air Outlet Node Name
0.36; !- Maximum air flow rate {m3/s}
AirTerminal:SingleDuct:ConstantVolume:NoReheat ,
Zone3DirectAir , !- Name
, !- Availability Schedule Name
Zone 3 Terminal Inlet Node , !- Air Inlet Node Name
Zone 3 Supply Node , !- Air Outlet Node Name
0.47; !- Maximum air flow rate {m3/s}
1.31.10.2 Outputs
1.31.11 AirLoopHVAC:UnitaryHeatPump:WaterToAir
The unitary water-to-air heat pump is similar to the unitary air-to-air heat pump except water is
used on the source side. Links to the fan, WaterToAirHeatPump cooling coil, WaterToAirHeatPump
heating coil, and supplementary heating coil specifications are provided in the heat pump’s input
data syntax. The heat pump switches between cooling and heating depending on the zone’s demand.
The load side (air) of the unitary water-to-air heat pump consists of an On/Off fan component, a
WaterToAirHeatPump cooling coil component, a WaterToAirHeatPump heating coil component, and
a Gas, Electric, Steam, or Hot Water supplemental heating coil component. The source side (water)
of the heat pump is connected to a condenser loop with a heat exchanger (ground heat exchanger
or other type) or a plant loop with a heating source such as a boiler and a cooling source such as a
chiller or cooling tower. The diagram below shows the setup and connection of the heat pump for the
1512 CHAPTER 1. INPUT-OUTPUT REFERENCE
source side and load side for a ground heat exchanger configuration. Note that on the load side, the
WaterToAirHeatPump cooling coil must always be placed before the WaterToAirHeatPump heating
coil.
There are three type of WaterToAirHeatPump coil models available:
– Coil:Cooling:WaterToAirHeatPump:ParameterEstimation
– Coil:Heating:WaterToAirHeatPump:ParameterEstimation
– Coil:Cooling:WaterToAirHeatPump:EquationFit
– Coil:Heating:WaterToAirHeatPump:EquationFit
– Coil:Cooling:WatertoAirHeatPump:VariableSpeedEquationFit
– Coil:Heating:WatertoAirHeatPump:VariableSpeedEquationFit
In addition, the control zone name and the system design operating conditions are specified by the
heat pump inputs.
1.31.11.1 Inputs
Figure 1.152: Water to Air Heat Pump Schematic for a BlowThrough Configuration with Ground
Heat Exchanger
1514 CHAPTER 1. INPUT-OUTPUT REFERENCE
– Coil:Heating:WaterToAirHeatPump:ParameterEstimation
– Coil:Heating:WaterToAirHeatPump:EquationFit
– Coil:Heating:WaterToAirHeatPump:VariableSpeedEquationFit
– Coil:Cooling:WaterToAirHeatPump:ParameterEstimation
– Coil:Cooling:WaterToAirHeatPump:EquationFit
– Coil:Cooling:WaterToAirHeatPump:VariableSpeedEquationFit
Figure 1.153:
Figure 1.154:
Figure 1.155:
– Coil:Heating:Electric
– Coil:Heating:Fuel
– Coil:Heating:Water
– Coil:Heating:Steam
– On/Off fan
– WaterToAirHeatPump cooling coil
– WaterToAirHeatPump heating coil
– Supplementary heating coil
– Direct air unit for each zone served by the heat pump
– Condenser demand branches
It should be noted that the volumetric air flow rate specified in the direct air unit for the controlling
zone should properly reflect the fractional volumetric air flow rate specified in the heat pump object.
The default is None. For CoolReheat dehumidification control modes, the maximum humidity
setpoint is required. This must be set using a ZoneControl:Humidistat object. When extra
dehumidification is required, the system may not be able to meet the humidity setpoint if its full
capacity is not adequate. Supplemental heating coil (supplemental heating coil type and name) is
a required input in WaterToAir HeatPumps. When dehumidification control is active the heating
and the reheat load due to extra dehumidification are met with supplemetal heating coil. The
supplemental heating coil capacity must be adequate enough to meet the heating coil load and offset
the excess cooling load due to extra dehumidification. The dehumidification control type CoolReheat
works only with Coil:Cooling:WaterToAirHeatPump:EquationFit cooling coil type.
– Cycling
– Constant
– CyclingOnDemand
Cycling varies water flow through the coil based on the heat pump Part Load Ratio. This control
method is appropriate for modeling heat pumps that are outfitted with a soleniod valve which allows
water to flow through the coil only when the compressor is active. This is the default for EnergyPlus
V8 and later.
Constant provides a constant water flow regardless of heat pump operation. Remember that
EnergyPlus has two coils (a heating coil and a cooling coil) to approximate the operation of one coil
that can operate in either heating mode or cooling mode. Therefore, when the water flow mode is
constant, there will be full flow through either the heating coil or the cooling coil, but not both at
the same time.
ConstantOnDemand provides full flow through the coil whenever there is a load. When there is
no load, there is zero flow through the coil. This control strategy represents the way EnergyPlus
modeled heat pump water flow prior to Version 8.
Following is an example of IDF usage:
AirLoopHVAC:UnitaryHeatPump:WaterToAir ,
DXAC Heat Pump 1, !- Name
FanAndCoilAvailSched , !- Availability Schedule Name
Mixed Air Node , !- Air Inlet Node Name
Air Loop Outlet Node , !- Air Outlet Node Name
2, !- Supply Air Flow Fate {m3/s}
East Zone , !- Controlling Zone or Thermostat Location
Fan:OnOff , !- Supply Air Fan Object Type
Supply Fan 1, !- Supply Air Fan Name
Coil:Heating: WaterToAirHeatPump :ParameterEstimation , !- Heating Coil Object Type
Heat Pump Heating Mode , !- Heating Coil Name
0.001 , !- Heating Convergence
Coil:Cooling: WaterToAirHeatPump :ParameterEstimation , !- Cooling Coil Object Type
Heat Pump Cooling Mode , !- Cooling Coil Name
0.001 , !- Cooling Convergence
2.5, !- Maximum Cycling Rate {cycles/hr}
60, !- Heat Pump Time Constant {s}
0.01, !- Fraction of On -Cycle Power Use
60, !- Heat Pump Fan Delay Time {s}
Coil:Heating:Fuel , !- Supplemental Heating Coil Object Type
Heat Pump DX Supp Heating Coil 1, !- Supplemental Heating Coil Name
1.31. GROUP – UNITARY EQUIPMENT 1519
Schedule:Compact ,
CyclingFanSch , !- Name
Fraction , !- Schedule Type Limits Name
Through: 12/31 , !- Field 1
For: AllDays , !- Field 2
Until: 24:00 , !- Field 3
0.0; !- Field 4
Coil:Heating:Fuel ,
Heat Pump DX Supp Heating Coil 1, !- Name
FanAndCoilAvailSched , !- Availability Schedule Name
NaturalGas , !- Fuel Type
0.8, !- Gas Burner Efficiency
32000 , !- Nominal Capacity {W}
SuppHeating Coil Air Inlet Node , !- Air Inlet Node Name
Air Loop Outlet Node; !- Air Outlet Node Name
BRANCH ,
Gshp Cooling Condenser Branch , !- Name
, !- Pressure Drop Curve Name
Coil:Cooling: WaterToAirHeatPump :ParameterEstimation , !- Component 1 Object Type
Heat Pump Cooling Mode , !- Component 1 Name
Water to Air Heat Pump Source Side1 Inlet Node , !- Component 1 Inlet Node Name
Water to Air Heat Pump Source Side1 Outlet Node; !- Component 1 Outlet Node Name
BRANCH ,
Gshp Heating Condenser Branch , !- Name
, !- Pressure Drop Curve Name
Coil:Heating: WaterToAirHeatPump :ParameterEstimation , !- Component 1 Object Type
Heat Pump Heating Mode , !- Component 1 Name
Water to Air Heat Pump Source Side2 Inlet Node , !- Component 1 Inlet Node Name
Water to Air Heat Pump Source Side2 Outlet Node; !- Component 1 Outlet Node Name
Fan:OnOff ,
Supply Fan 1, !- Name
FanAndCoilAvailSched , !- Availability Schedule Name
0.7, !- FanTotal Efficiency
300.0 , –! Pressure Rise {Pa}
2.0, !- Maximum Flow Rate {m3/s}
0.9, !- Motor Efficiency
1.0, !- Motor In Airstream Fraction
Mixed Air Node , !- Air Inlet_Node Name
Cooling Coil Air Inlet Node; !- Air Outlet Node Name
AirTerminal:SingleDuct:ConstantVolume:NoReheat ,
Zone1DirectAir , !- Name
, !- Availability Schedule Name
Zone 1 Terminal Inlet Node , !- Air Inlet Node Name
Zone 1 Supply Node , !- Air Outlet Node Name
0.7; !- Maximum air flow rate {m3/s}
AirTerminal:SingleDuct:ConstantVolume:NoReheat ,
Zone2DirectAir , !- Name
, !- Availability Schedule Name
Zone 2 Terminal Inlet Node , !- Air Inlet Node Name
Zone 2 Supply Node , !- Air Outlet Node Name
0.6; !- Maximum air flow rate {m3/s}
AirTerminal:SingleDuct:ConstantVolume:NoReheat ,
Zone3DirectAir , !- Name
, !- Availability Schedule Name
Zone 3 Terminal Inlet Node , !- Air Inlet Node Name
Zone 3 Supply Node , !- Air Outlet Node Name
0.7; !- Maximum air flow rate {m3/s}
1.31. GROUP – UNITARY EQUIPMENT 1521
1.31.11.2 Outputs
Energy use reporting for the water-to-air heat pump is documented under the heat pump coil object
types:
– Coil:Cooling:WaterToAirHeatPump:ParameterEstimation
– Coil:Heating:WaterToAirHeatPump:ParameterEstimation
– Coil:Cooling:WaterToAirHeatPump:EquationFit
– Coil:Heating:WaterToAirHeatPump:EquationFit
The heat pump demand as well as the compressor and fan part-load ratios may be obtained with
the output variables shown below.
1.31.12 AirLoopHVAC:UnitaryHeatCool:VAVChangeoverBypass
The changeover-bypass variable air volume (CBVAV) unitary system is a compound object made
up of other components. Each CBVAV system consists of an outdoor air mixer, direct expansion
(DX) cooling coil, heating coil, and a supply air fan as shown in the figures below. Zone thermostats
and terminal units are required in each zone served by this system. The terminal units are specific
to this system type and are either AirTerminal:SingleDuct:VAV:HeatAndCool:Reheat or AirTermi-
nal:SingleDuct:VAV:HeatAndCool:NoReheat. A zone humidistat and single zone max humidity set
point manager may also be specified to help control high humidity levels. These individual com-
ponents are described elsewhere in this document. The system may also be connected to an inlet
node of either the AirLoopHVAC:ZoneMixer or AirLoopHVAC:ReturnPlenum to more accurately
model the AirLoopHVAC:OutdoorAirSystem. The CBVAV unitary system object coordinates the
operation of these components and is modeled as a type of air loop equipment (Ref. AirLoopHVAC).
Links to the CBVAV system’s supply air fan, coils, and outdoor air mixer specifications are provided
in the object’s input syntax. Additional inputs include system and outdoor air flow rates during
heating and cooling operation, the priority control mode, and dehumidification control type. A
description of each input field for the CBVAV unitary system compound object is provided below.
1.31.12.1 Inputs
Figure 1.156: Schematic of a CBVAV unitary system (draw through fan placement)
Figure 1.157: Schematic of a CBVAV unitary system (blow through fan placement)
1524 CHAPTER 1. INPUT-OUTPUT REFERENCE
Figure 1.158: Schematic of a CBVAV unitary system used with outdoor air system
Field: Outdoor air volumetric flow rate multiplier schedule name). For any simulation timestep, the
Cooling Outdoor Air Flow Rate cannot exceed the system air volumetric flow rate during cooling
operation.
1.31.12.1.8 Field: No Load Outdoor Air Flow Rate When No Cooling or Heating
is Needed
This numeric field defines the outdoor air flow rate through the system (i.e., through the Outdoor air
Mixer’s Outside_Air_Stream_Node) in cubic meters per second when neither cooling nor heating
is required (i.e., the DX cooling coil and heating coil are off but the supply air fan operates). Values
must be greater than or equal to 0, or this field is autosizable. Note that the no load outdoor air
flow rate can be changed during the simulation using a multiplier schedule (Ref. Field: Outdoor air
volumetric flow rate multiplier schedule name). For any simulation timestep, the no load outdoor
air flow rate cannot exceed the no load supply air flow rate. This field is only used when the unitary
system’s supply air fan operating mode is specified as continuous fan operation (Ref. Field: Supply
air fan operating mode schedule name). If the system’s supply air fan operating mode is specified
as continuous fan operation and this value is set to zero or the field is left blank, then the model
assumes that the no load outdoor air flow rate is equal to the outdoor air flow rate when the coils
were last operating (for cooling operation [i.e. Cooling outdoor air flow rate] or heating operation
[i.e. Heating outdoor air flow rate]) and this field is not used.
– OutdoorAir:Mixer
– Coil:Cooling:DX:SingleSpeed
– Coil:Cooling:DX:VariableSpeed
– CoilSystem:Cooling:DX:HeatExchangerAssisted
– Coil:Cooling:DX:TwoStageWithHumidityControlMode
The input requirements for these cooling coil objects are described elsewhere in this document.
– Coil:Heating:Electric
– Coil:Heating:Fuel
– Coil:Heating:DX:SingleSpeed
– Coil:Heating:DX:VariableSpeed
– Coil:Heating:Water
– Coil:Heating:Steam
The input requirements for these heating coil objects are described elsewhere in this document.
1528 CHAPTER 1. INPUT-OUTPUT REFERENCE
– CoolingPriority
– HeatingPriority
– ZonePriority
– LoadPriority
If CoolingPriority is selected, the system operates to meet the cooling load if any zone served by
this system (air loop) requires cooling. If no zones require cooling, then the system operates in
heating mode if needed. If HeatingPriority is selected, the system operates to meet the heating
load if any zone requires heating. If no zones require heating, then the system operates in cooling
mode if needed. If ZonePriority is selected, the system operates based on the maximum number of
zones requiring either heating or cooling. If the number of zones requiring cooling is greater than the
number of zones requiring heating, then the system operates in cooling mode. If the number of zones
requiring heating is greater than the number of zones requiring cooling, then the system operates
in heating mode. If the number of zones requiring cooling equals the number of zones requiring
heating, then the largest combined load (i.e., the sum of the cooling loads for zones requiring cooling
compared to the sum of the heating loads for zones that require heating) sets the cooling or heating
operating mode for the system during that simulation timestep. If LoadPriority is selected, the
system operates based on the largest combined load (i.e., the sum of the cooling loads for zones
requiring cooling compared to the sum of the heating loads for zones that require heating). If the
toal load for zones requiring cooling is greater than the toal load for zones requiring heating, then
the system operates in cooling mode. Similar logic is used for heating mode selection. If the toal
cooling load equals the toal heating load, then cooling or heating operation reverts to the total
number of zones requiring cooling or heating (and if equal reverts to cooling mode if the cooling load
is non-zero, otherwise, heating mode.
This numeric field defines the minimum outlet air temperature leaving the system when the unit is
operating to provide cooling. Values are specified in degrees Celsius and must be greater than 0. The
default value is 8°C. This value must be less than or equal to the maximum outlet air temperature
during heating operation.
– SetpointManager:SingleZone:Humidity:Maximum
– SetpointManager:MultiZone:Humidity:Maximum
– SetpointManager:MultiZone:MaximumHumidity:Average
objects. When extra dehumidification is required, the system may not be able to meet the humidity
setpoint if its full capacity is not adequate.
As shown in the example below, correct specification of the CBVAV unitary system requires specifica-
tion of the following objects in addition to the AirLoopHVAC:UnitaryHeatCool:VAVChangeoverBypass
object:
1) outdoor air mixer (OutdoorAir:Mixer)
2) fan (Fan:SystemModel, Fan:OnOff, or Fan:ConstantVolume)
3) cooling coil (Coil:Cooling:DX:SingleSpeed, CoilSystem:Cooling:DX:HeatExchangerAssisted, or
Coil:Cooling:DX:TwoStageWithHumidityControlMode)
4) heating coil (Coil:Heating:Fuel, Coil:Heating:Electric, or Coil:Heating:DX:SingleSpeed)
5) terminal unit for each zone being served by this system (AirTerminal:SingleDuct:VAV:HeatAndCool:Reheat
or AirTerminal:SingleDuct:VAV:HeatAndCool:NoReheat)
1530 CHAPTER 1. INPUT-OUTPUT REFERENCE
6) When the Plenum or Mixer Inlet Node Name is specified, this node name must connect
to either the AirLoopHVAC:ZoneMixer or AirLoopHVAC:ReturnPlenum and the AirLoopH-
VAC:OutdoorAirSystem may then be used to control the outdoor air flow rates. When using
the AirloopHVAC:OutdoorAirSystem it is recommended that the Cooling, Heating and No Load
Outdoor Air Flow Rate inputs are set to 0, otherwise the amount of outdoor air is increased and
the coils may not autosize properly.
Note: The fan, heating coil, cooling coil, and outdoor air mixer must be connected in the air loop
according to the configurations shown above (Figure 1.156, Figure 1.157 or Figure 1.158).
AirLoopHVAC:UnitaryHeatCool:VAVChangeoverBypass ,
GasHeat CBVAV System , !- Name of unitary system
FanAndCoilAvailSched , !- Availability schedule name
1.8, !- Cooling Supply Air Flow Rate {m3/s}
1.7, !- Heating Supply Air Flow Rate {m3/s}
1.6, !- No Load Supply Air Flow Rate {m3/s}
0.32, !- Cooling Outdoor Air Flow Rate {m3/s}
0.3, !- Heating Outdoor Air Flow Rate {m3/s}
0.27, !- No Load Outdoor Air Flow Rate {m3/s}
Outdoor Air Multiplier Schedule , !- Outdoor air volumetric flow rate multiplier schedule name
Air Loop Inlet Node , !- Air inlet node name
Mixer Inlet Node , !- Bypass duct mixer node name
Heating Coil Air Outlet Node , !- Bypass duct splitter node name
Air Loop Outlet Node , !- Air outlet node name
OutdoorAir:Mixer , !- Outdoor Air Mixer Object Type
Outdoor air Mixer , !- Outdoor air mixer name
Fan:OnOff , !- Supply air fan type
Supply Fan 1, !- Supply air fan name
BlowThrough , !- Supply air fan placement
Fan OpMode Schedule , !- Supply air fan operating mode schedule name
Coil:Cooling:DX:TwoStageWithHumidityControlMode , !- Cooling coil type
ACDXCoil 2, !- Cooling coil name
Coil:Heating:Fuel , !- Heating coil type
Furnace Heating Coil 1, !- Heating coil name
CoolingPriority , !- Priority control mode
10.0, !- Minimum outlet air temperature during cooling operation {C}
50.0, !- Maximum outlet air temperature during heating operation {C}
None; !- Dehumidification control type
OutdoorAir:Mixer ,
Outdoor air Mixer , !- Name
Mixed Air Node , !- Mixed Air Node Name
Outdoor air Inlet Node , !- Outdoor Air Stream Node
Relief Air Outlet Node , !- Relief Air Stream Node Name
Mixer Inlet Node; !- Return Air Stream Node Name
Fan:OnOff ,
Supply Fan 1, !- Fan Name
FanAndCoilAvailSched , !- Availability Schedule Name
0.7, !- Fan Total Efficiency
600.0 , !- Delta Pressure {Pa}
1.8, !- Max Flow Rate {m3/s}
0.9, !- Motor Efficiency
1.0, !- Motor In Airstream Fraction
Mixed Air Node , !- Fan\_Inlet\_Node
DX Cooling Coil Air Inlet Node; !- Fan\_Outlet\_Node
Coil:Cooling:DX:TwoStageWithHumidityControlMode ,
ACDXCoil 2, !- Coil Name
FanAndCoilAvailSched , !- Availability Schedule
DX Cooling Coil Air Inlet Node , !- Coil Air Inlet Node
Heating Coil Air Inlet Node , !- Coil Air Outlet Node
, !- Crankcase Heater Capacity {W}
, !- Maximum Outdoor Dry -bulb Temperature for Crankcase Heater
Operation {C}
2, !- Number of Capacity Stages
0, !- Number of Enhanced Dehumidification Modes
1.31. GROUP – UNITARY EQUIPMENT 1531
Coil:Heating:Fuel ,
Furnace Heating Coil 1, !- Coil Name
FanAndCoilAvailSched , !- Availability Schedule Name
NaturalGas , !- Fuel Type
0.8, !- Gas Burner Efficiency of the Coil
35000 , !- Nominal Capacity of the Coil {W}
Heating Coil Air Inlet Node , !- Coil\_Air\_Inlet\_Node
Heating Coil Air Outlet Node; !- Coil\_Air\_Outlet\_Node
AirTerminal:SingleDuct:VAV:HeatAndCool:Reheat ,
Zone 1 VAV System , !- Name of System
FanAndCoilAvailSched , !- System Availability schedule
Zone 1 Reheat Air Inlet Node , !- DAMPER Air Outlet Node
Zone 1 VAV Inlet Node , !-UNIT Air Inlet Node
0.583 , !- Maximum air flow rate {m3/s}
0.25, !- Zone Minimum Air Flow Fraction
, !- Control node
Coil:Heating:Electric , !- Reheat Component Object
Reheat Coil Zone 1, !- Name of Reheat Component
0.0, !- Max Reheat Water Flow {m3/s}
0.0, !- Min Reheat Water Flow {m3/s}
Zone 1 Reheat Air Outlet Node , !- UNIT Air Outlet Node
0.001; !- Convergence Tolerance
AirTerminal:SingleDuct:VAV:HeatAndCool:Reheat ,
Zone 2 VAV System , !- Name of System
FanAndCoilAvailSched , !- System Availability schedule
Zone 2 Reheat Air Inlet Node , !- DAMPER Air Outlet Node
Zone 2 VAV Inlet Node , !-UNIT Air Inlet Node
0.583 , !- Maximum air flow rate {m3/s}
0.25, !- Zone Minimum Air Flow Fraction
, !- Control node
Coil:Heating:Electric , !- Reheat Component Object
Reheat Coil Zone 2, !- Name of Reheat Component
0.0, !- Max Reheat Water Flow {m3/s}
0.0, !- Min Reheat Water Flow {m3/s}
Zone 2 Reheat Air Outlet Node , !- UNIT Air Outlet Node
0.001; !- Convergence Tolerance
AirTerminal:SingleDuct:VAV:HeatAndCool:NoReheat ,
Zone 3 VAV System , !- Name of System
FanAndCoilAvailSched , !- System Availability schedule
Zone 3 Reheat Air Outlet Node , !- UNIT Air Outlet Node
Zone 3 VAV Inlet Node , !-UNIT Air Inlet Node
0.584 , !- Maximum air flow rate {m3/s}
0.25; !- Zone Minimum Air Flow Fraction
1.31.12.2 Outputs
provided by the system. This value is calculated for each HVAC system timestep being simulated,
and the results (latent heat extraction only) are averaged for the timestep being reported.
1. System curve based model (VRF-SysCurve). In this model, a number of system level
curves are used to describe the VRF system performance. This model corresponds to the
AirConditioner:VariableRefrigerantFlow object.
2. Physics based model (VRF-FluidTCtrl). This model is able to consider the dynamics
of more operational parameters and is applicable for fluid temperature control. This model
corresponds to the AirConditioner:VariableRefrigerantFlow:FluidTemperatureControl object.
(Please refer to the engineering reference for more technical details of the two models).
In the VRF system model, direct-expansion cooling and/or heating coils with an optional sup-
plemental heating coil are configured in a zone terminal unit, which is connected to a zone via
the zone inlet and exhaust nodes, connected to an air loop main branch or installed in the air
loop’s outdoor air system. The terminal units are identified in a ZoneTerminalUnitList object, the
name of which is entered as an input to the AirConditioner:VariableRefrigerantFlow or AirCondi-
tioner:VariableRefrigerantFlow:FluidTemperatureControl object.
1536 CHAPTER 1. INPUT-OUTPUT REFERENCE
The EnergyPlus connection methodology is shown as dashed and greyed arrows in Figure 1.159
according to the following rules:
– For zone equipment the zone inlet and zone exhaust node names are defined in a Zone-
HVAC:EquipmentConnections object (bottom of figure) and the terminal unit type and name
are specified in a ZoneHVAC:EquipmentList object. For air loop equipment the terminal unit
type and name and inlet and outlet node names are defined in the AirloopHVAC branch (top
left of figure). For outside air system equipment the terminal unit type and name are defined
in the AirLoopHVAC:OutdoorAirSystem:EquipmentList (top right of figure) and the terminal
unit inlet node will typically (but not necessarily) be an outside air node and the terminal unit
outlet node will typically connect to the OutdoorAir:Mixer object.
– A ZoneHVAC:TerminalUnit:VariableRefrigerantFlow object will specify the terminal unit’s air
inlet and air outlet node names. For zone equipment the zone exhaust node is the terminal unit
inlet node and the zone inlet node is the terminal unit outlet node. For air loop and outdoor
air system equipment the terminal unit inlet and outlet node names identify the order of the
equipment in the air loop.
– All zone terminal units that are connected to the same AirConditioner:VariableRefrigerantFlow
or AirConditioner:VariableRefrigerantFlow:FluidTemperatureControl object are listed in a
ZoneTerminalUnitList object.
– The name of the ZoneTerminalUnitList object is an input to the AirConditioner:VariableRefrigerantFlow
or AirConditioner:VariableRefrigerantFlow:FluidTemperatureControl object.
– The AirConditioner:VariableRefrigerantFlow:FluidTemperatureControl or AirConditioner:Variable-
RefrigerantFlow object is not listed in an AirloopHVAC object, and therefore, can only be
simulated if the terminal units are connected to the AirConditioner:VariableRefrigerantFlow or
AirConditioner:VariableRefrigerantFlow:FluidTemperatureControl object using the ZoneTer-
minalUnitList.
– Secondary ZoneHVAC equipment objects may be used in the same zones as the terminal units
for other purposes (e.g., code compliance)
1.32.1 AirConditioner:VariableRefrigerantFlow
1.32.1.1 Inputs
be off for that time period. A value other than 0 denotes that the heat pump is available to operate
during that time period. This schedule may be used to completely disable the heat pump (and all
of its terminal units) as required. If this field is blank, the unit is enabled the entire simulation.
This numeric field defines the minimum source inlet temperature allowed for cooling operation. For
air-cooled equipment outdoor dry-bulb temperature is used. For water-cooled equipment inlet water
temperature is used. Below this temperature, cooling is disabled. If this field is left blank, the
default value is -6ºC.
This numeric field defines the maximum source inlet temperature allowed for cooling operation. For
air-cooled equipment outdoor dry-bulb temperature is used. For water-cooled equipment inlet water
temperature is used. Above this temperature, cooling is disabled. If this field is left blank, the
default value is 43ºC.
air dry-bulb temperature as a function of indoor air wet-bulb temperature. This curve is used when
the trend in cooling capacity changes dramatically as outdoor temperature changes. If the cooling
capacity does not change dramatically with changes in outdoor conditions, this field may be left
blank. See the Engineering Reference for more discussion on using this input field.
1.32.1.1.10 Field: Cooling Energy Input Ratio Modifier Function of Low Tem-
perature Curve Name
This alpha field defines the cooling energy input ratio modifier at low outdoor temperatures. This
curve is a bi-quadratic equation with a weighted average indoor wet-bulb temperature and con-
denser entering air dry-bulb temperature as the independent variables. If the Condenser Type is
WaterCooled, then the cooling energy input ratio modifier curve will be function of weighted average
indoor air wet-bulb temperature and outdoor condenser entering water temperature. This perfor-
mance curve can be used to describe the cooling energy input ratio at low outdoor temperatures
(i.e., the following two curves are used) or can be used to describe the performance for all outdoor
temperatures (i.e., the following two curves are not used). For this system type it is likely that all
three of these performance curves will be required. See the Engineering Reference for more discussion
on using this input field.
1.32.1.1.12 Field: Cooling Energy Input Ratio Modifier Function of High Tem-
perature Curve Name
This alpha field defines the cooling energy input ratio modifier at high outdoor temperatures. This
curve is a bi-quadratic equation with weighted average indoor wet-bulb temperature and condenser
entering air dry-bulb temperature as the independent variables. This curve is used when the trend
in cooling energy changes dramatically as outdoor temperature changes. If the cooling energy does
not change dramatically with changes in outdoor conditions, this field may be left blank. See the
Engineering Reference for more discussion on using this input field.
1.32. GROUP – VARIABLE REFRIGERANT FLOW EQUIPMENT 1541
1.32.1.1.13 Field: Cooling Energy Input Ratio Modifier Function of Low Part-
Load Ratio Curve Name
This alpha field defines the cooling energy input ratio modifier (function of part-load ratio when
PLR is less than or equal to 1) curve name. This curve is a linear, quadratic or cubic equation with
cooling part-load ratio used as the independent variable. The cooling energy input ratio modifier
curve is normalized to 1 at a part-load ratio of 1 and is used only when the operating part-load ratio
is less than or equal to 1. This curve’s minimum PLR value must be less or equal to the value in
the field Minimum Heat Pump Part-Load Ratio.
1.32.1.1.14 Field: Cooling Energy Input Ratio Modifier Function of HIgh Part-
Load Ratio Curve Name
This alpha field defines the cooling energy input ratio modifier (function of part-load ratio when
PLR is greater than 1) curve name. This curve is a linear, quadratic or cubic equation with cooling
part-load ratio used as the independent variable. The cooling energy input ratio modifier curve is
normalized to 1 at a part-load ratio of 1 and is used only when the operating part-load ratio is
greater than 1.
capacity regardless of the value entered in the terminal unit objects. When the heating capacity
is not autosized, the gross rated heating capacity will be equal to the value specified in the Gross
Rated Heating Capacity input field and this value will be compared to the sum of the terminal
unit heating coil size. If these values are more than 10% different, a warning will be issued when
Output:Diagnostics, DisplayExtraWarnings; is included in the input file. If this field is blank and
the terminal unit sizing ratio input is also blank, then the heating capacity sizing ratio is assumed
to be 1. If this field is not blank and the heating capacity sizing ratio in the terminal unit object(s)
is blank, then this ratio also applies to each heating coil. If this field is not blank and the heating
capacity sizing ratio in the terminal units is also not blank, then the terminal unit heating coil
capacity sizing ratio input applies to each heating coil.
1.32.1.1.25 Field: Heating Energy Input Ratio Modifier Function of Low Tem-
perature Curve Name
This alpha field defines the heating energy input ratio modifier at low temperature curve name. This
curve is a bi-quadratic equation with a weighted average indoor dry-bulb temperature and condenser
entering air dry-bulb or wet-bulb temperature as the independent variables. Since manufacturers
may provide performance data using either outdoor dry-bulb or wet-bulb temperatures, either of
these temperature types may be used for heating performance curves as specified in the Heating
Performance Curve Outdoor Temperature Type input field below. This performance curve can be
used to describe the heating energy input ratio at low outdoor temperatures (i.e., the following two
curves are used) or can be used to describe the performance for all outdoor temperatures (i.e., the
following two curves are not used).
1.32.1.1.27 Field: Heating Energy Input Ratio Modifier Function of High Tem-
perature Curve Name
This alpha field defines the heating energy input ratio modifier at high temperature curve name. This
curve is a bi-quadratic equation with a weighted average indoor dry-bulb temperature and condenser
entering air dry-bulb or wet-bulb temperature as the independent variables. Since manufacturers
may provide performance data using either outdoor dry-bulb or wet-bulb temperatures, either of
these temperature types may be used for heating performance curves as specified in the Heating
Performance Curve Outdoor Temperature Type input field below. This curve is used when the
trend in heating energy changes dramatically as outdoor temperature changes. If the heating energy
does not change dramatically with changes in outdoor conditions, this field may be left blank.
1.32.1.1.29 Field: Heating Energy Input Ratio Modifier Function of Low Part-
Load Ratio Curve Name
This alpha field defines the heating energy input ratio modifier (function of part-load ratio when
PLR is less than or equal to 1) curve name. This curve is a linear, quadratic, or cubic equation with
heating part-load ratio used as the independent variable. The heating energy input ratio modifier
curve is normalized to 1 at a part-load ratio of 1 and is used only when the part-load ratio is less
than or equal to 1. This curve’s minimum PLR value must be less or equal to the value in the field
Minimum Heat Pump Part-Load Ratio.
1.32.1.1.30 Field: Heating Energy Input Ratio Modifier Function of High Part-
Load Ratio Curve Name
This alpha field defines the heating energy input ratio modifier (function of part-load ratio when
PLR is greater than 1) curve name. This curve is a linear, quadratic, or cubic equation with heating
part-load ratio used as the independent variable. The heating energy input ratio modifier curve is
normalized to 1 at a part-load ratio of 1 and is used only when the part-load ratio is greater than 1.
of x, the multiplier is linearly interpolated. For combination ratio’s less than 1, capacity is directly
proportional to part-load ratio and this curve will not be used. If this field is left blank, the Cooling
Combination Ratio Correction factor will be used.
1.32.1.1.39 Field: Equivalent Piping Length used for Piping Correction Factor
in Cooling Mode
This numeric field defines the equivalent pipe length in meters between the farthest terminal unit and
the heat pump condenser. This value includes the gas refrigerant line length (for both horizontal and
vertical distances), fitting losses, pipe bends, and other connections that contribute to piping losses.
This field is used to calculate the piping correction factor in cooling mode. This value defines the
head losses due to the pipe length between the farthest terminal unit and the heat pump condenser
and impacts the maximum available capacity in cooling mode.
1.32.1.1.41 Field: Piping Correction Factor for Length in Cooling Mode Curve
Name
This alpha field defines the linear, quadratic, or cubic curve name used to calculate the piping
correction factor for length in cooling mode. Piping losses are a function of piping length. If
sufficient piping loss information is available where piping losses are also a function of combination
ratio (i.e., in addition to length), a biquadratic performance curve may be used.
1.32. GROUP – VARIABLE REFRIGERANT FLOW EQUIPMENT 1547
1.32.1.1.42 Field: Piping Correction Factor for Height in Cooling Mode Coeffi-
cient
This numeric field defines the coefficient used to calculate the piping correction factor for height in
cooling mode.
1.32.1.1.43 Field: Equivalent Piping Length used for Piping Correction Factor
in Heating Mode
This numeric field defines the equivalent pipe length in meters between the farthest terminal unit and
the heat pump condenser. This value includes the liquid refrigerant line length (for both horizontal
and vertical distances), fitting losses, pipe bends, and other connections that contribute to piping
losses. This field is used to calculate the piping correction factor in heating mode. This value
defines the head losses due to the pipe length between the farthest terminal unit and the heat pump
condenser and impacts the maximum available capacity in heating mode.
1.32.1.1.44 Field: Piping Correction Factor for Length in Heating Mode Curve
Name
This alpha field defines the linear, quadratic, or cubic curve name used to calculate the piping
correction factor for length in heating mode. Piping losses are a function of piping length. If
sufficient piping loss information is available where piping losses are also a function of combination
ratio (i.e., in addition to length), a biquadratic performance curve may be used.
1.32.1.1.45 Field: Piping Correction Factor for Height in Heating Mode Coeffi-
cient
This numeric field defines the coefficient used to calculate the piping correction factor for height in
heating mode.
temperature for crankcase heater operation. The minimum value for this field is 1. If this field is
left blank, the default value is 2. This field is only used to calculate crankcase heater power and has
no impact on heat pump performance.
is multiplied by the coil capacity, the fractional defrost time period and the runtime fraction of the
heating coil to give the defrost power at the specific temperatures at which the indoor and outdoor
coils are operating. The curve is normalized to a value of 1.0 at the rating point conditions.
where
Tcondinlet = the temperature of the air entering the condenser coil (C)
Twb,o = the wet-bulb temperature of the outdoor air (C)
Tdb,o = the dry-bulb temperature of the outdoor air (C)
The resulting condenser inlet air temperature is used by the Cooling Capacity Ratio Modifier Curve
(function of temperature) and the Cooling Energy Input Ratio Modifier Curve (function of tem-
perature). The default value for this field is 0.9, although valid entries can range from 0.0 to 1.0.
This field is not used when Condenser Type = Air Cooled and the simulation is calculating heating
performance.
If the user wants to model an air-cooled condenser, they should simply specify AirCooled in the field
Condenser Type. In this case, the Cooling Capacity Ratio Modifier Curve (function of temperature)
and the Cooling Energy Input Ratio Modifier Curve (function of temperature) input fields for this
object should reference performance curves that are a function of outdoor dry-bulb temperature.
If the user wishes to model an evaporative-cooled condenser AND they have performance curves that
are a function of the wet-bulb temperature of air entering the condenser coil, then the user should
specify Condenser Type = EvapCooled and the evaporative condenser effectiveness value should be
entered as 1.0. In this case, the Cooling Capacity Ratio Modifier Curve (function of temperature)
and the Cooling Energy Input Ratio Modifier Curve (function of temperature) input fields for this
object should reference performance curves that are a function of the wet-bulb temperature of air
entering the condenser coil.
If the user wishes to model an air-cooled condenser that has evaporative media placed in front
of it to cool the air entering the condenser coil, then the user should specify Condenser Type =
EvapCooled. The user must also enter the appropriate evaporative effectiveness for the media. In
this case, the Cooling Capacity Ratio Modifier Curve (function of temperature) and the Cooling
Energy Input Ratio Modifier Curve (function of temperature) input fields for this object should
reference performance curves that are a function of outdoor dry-bulb temperature. Be aware that
the evaporative media will significantly reduce the dry-bulb temperature of the air entering the
condenser coil, so the Cooling Capacity and Cooling EIR Modifier Curves must be valid for the
expected range of dry-bulb temperatures that will be entering the condenser coil.
reduction in cooling capacity at the start of heat recovery mode). The system will recovery according
to the time constant entered in Heat Recovery Cooling Capacity Time Constant input field. If the
transition period will not be modeled, this input field must be set to 1. This input is only used
when Heat Pump Waste Heat Recovery is selected as Yes and the system changes from cooling only
mode to heat recovery mode. Refer to the engineering reference document discussion on the variable
refrigerant flow heat pump model section for transition from cooling only mode to heat recovery
mode for a more detailed description.
This numeric field defines the cooling energy time constant, in hours, used to model the time it takes
for the system to transition from cooling only operation to simultaneous cooling and heating. Total
response time is defined as 5 time constants. If this field is left blank, a default value of 0.0 is used.
If the transition period will not be modeled, the Initial Heat Recovery Cooling Energy Fraction field
must be set to 1. This input is only used when Heat Pump Waste Heat Recovery is selected as Yes
and the system changes from cooling only mode to heat recovery mode. Refer to the engineering
reference document discussion on the variable refrigerant flow heat pump model section for transition
from cooling only mode to heat recovery mode for a more detailed description.
AirConditioner:VariableRefrigerantFlow ,
VRF Heat Pump , !- Heat Pump Name
VRFCondAvailSched , !- Availability Schedule Name
autosize , !- Gross Rated Total Cooling Capacity {W}
3.16038 , !- Gross Rated Cooling COP {W}
-5, !- Minimum Condenser Inlet Node Temperature in Cooling Mode {C}
43, !- Maximum Condenser Inlet Node Temperature in Cooling Mode {C}
VRFCoolCapFT , !- Cooling Capacity Ratio Modifier Function of Low Temperature Curve Name
VRFCoolCapFTBoundary , !- Cooling Capacity Ratio Boundary Curve Name
VRFCoolCapFTHi , !- Cooling Capacity Ratio Modifier Function of High Temperature Curve
Name
1556 CHAPTER 1. INPUT-OUTPUT REFERENCE
VRFCoolEIRFT , !- Cooling Energy Input Ratio Modifier Function of Low Temperature Curve
Name
VRFCoolEIRFTBoundary , !- Cooling Energy Input Ratio Boundary Curve Name
VRFCoolEIRFTHi , !- Cooling Energy Input Ratio Modifier Function of High Temperature Curve
Name
CoolingEIRLowPLR , !- Cooling Energy Input Ratio Modifier Function of Low Part -Load Ratio
Curve Name
CoolingEIRHiPLR , !- Cooling Energy Input Ratio Modifier Function of High Part -Load Ratio
Curve Name
CoolingCombRatio , !- Cooling Combination Ratio Correction Factor Curve Name
VRFCPLFFPLR , !- Cooling Part -Load Fraction Correlation Curve Name
autosize , !- Gross Rated Heating Capacity {W}
, !- Rated Heating Capacity Sizing Ratio (W/W)
3.40909 , !- Gross Rated Heating COP
-20, !- Minimum Condenser Inlet Node Temperature in Heating Mode {C}
15.5, !- Maximum Condenser Inlet Node Temperature in Heating Mode {C}
VRFHeatCapFT , !- Heating Capacity Ratio Modifier Function of Low Temperature Curve Name
VRFHeatCapFTBoundary , !- Heating Capacity Ratio Boundary Curve Name
VRFHeatCapFTHi , !- Heating Capacity Ratio Modifier Function of High Temperature Curve
Name
VRFHeatEIRFT , !- Heating Energy Input Ratio Modifier Function of Low Temperature Curve
Name
VRFHeatEIRFTBoundary , !- Heating Energy Input Ratio Boundary Curve Name
VRFHeatEIRFTHi , !- Heating Energy Input Ratio Modifier Function of High Temperature Curve
Name
WetBulbTemperature , !- Heating Performance Curve Outdoor Temperature Type
HeatingEIRLowPLR , !- Heating Energy Input Ratio Modifier Function of Low Part -Load Ratio
Curve Name
HeatingEIRHiPLR , !- Heating Energy Input Ratio Modifier Function of High Part -Load Ratio
Curve Name
HeatingCombRatio , !- Heating Combination Ratio Correction Factor Curve Name
VRFCPLFFPLR , !- Heating Part -Load Fraction Correlation Curve Name
0.25, !- Minimum Heat Pump Part -Load Ratio
SPACE1 -1, !- Zone Name for Master Thermostat Location
LoadPriority , !- Master Thermostat Priority Control Type
, !- Thermostat Priority Schedule Name
VRF Heat Pump TU List , !- Zone Terminal Unit List Name
No , !- Heat Pump Waste Heat Recovery
30, !- Equivalent Piping Length used for Piping Correction Factor in Cooling
Mode {m}
10, !- Vertical Height used for Piping Correction Factor {m}
CoolingLengthCorrectionFactor , !- Piping Correction Factor for Length in Cooling Mode Curve
Name
-0.000386 , !- Piping Correction Factor for Height in Cooling Mode Coefficient
30, !- Equivalent Piping Length used for Piping Correction Factor in Heating
Mode {m}
, !- Piping Correction Factor for Length in Heating Mode Curve Name
, !- Piping Correction Factor for Height in Heating Mode Coefficient
15, !- Crankcase Heater Power per Compressor {W}
3, !- Number of Compressors
0.33, !- Ratio of Compressor Size to Total Compressor Capacity
7, !- Maximum Outdoor Dry -bulb Temperature for Crankcase Heater {C}
Resistive , !- Defrost Strategy
Timed , !- Defrost Control
, !- Defrost Energy Input Ratio Modifier Function of Temperature Curve Name
, !- Defrost Time Period Fraction
autosize , !- Resistive Defrost Heater Capacity {W}
7, !- Maximum Outdoor Dry -bulb Temperature for Defrost Operation {C}
EvaporativelyCooled , !- Condenser Type
MyVRFOANode , !- Condenser Inlet Node Name
, !- Condenser Outlet Node Name
, !- Water Condenser Volume Flow Rate
, !- Evaporative Condenser Effectiveness {dimensionless}
autosize , !- Evaporative Condenser Air Flow Rate {m3/s}
autosize , !- Evaporative Condenser Pump Rated Power Consumption {W}
, !- Supply Water Storage Tank Name
200, !- Basin Heater Capacity {W/K}
, !- Basin Heater Set Point Temperature (C)
, !- Basin Heater Operating Schedule Name
, !- Fuel Type
1.32. GROUP – VARIABLE REFRIGERANT FLOW EQUIPMENT 1557
1.32.1.2 Outputs
Heat Recovery:
Evap-cooled:
Water-cooled:
Electric defrost always used for Defrost Strategy = Resistive regardless of fuel type
Note: refer to the rdd file after a simulation for exact output variable names
operating conditions. This value is calculated for each HVAC system time step being simulated, and
the results are averaged for the time step being reported.
1.32.1.2.23 VRF Heat Pump Terminal Unit Cooling Load Rate [W]
This output field is the sum of the terminal unit cooling coil loads in Watts for the current time
step being reported. This value is derived directly from the cooling coils and represents the total
cooling load on the VRF system after piping losses have been accounted for. The total cooling load
will be less than the variable refrigerant flow total cooling capacity reported when piping losses are
modeled (i.e., when piping losses are < 1).
1.32.1.2.24 VRF Heat Pump Terminal Unit Heating Load Rate [W]
This output field is the sum of the terminal unit heating coil loads in Watts for the current time
step being reported. This value is derived directly from the heating coils and represents the total
heating load on the VRF system after piping losses have been accounted for. The total heating load
will be less than the variable refrigerant flow total heating capacity reported when piping losses are
modeled (i.e., when piping losses are < 1).
1.32.1.2.27 VRF Heat Pump Evaporative Condenser Water Use Volume [m3]
This output is the amount of water used to evaporatively cool the condenser coil inlet air, in cubic
meters. This output is also added to a meter with Resource Type = Water, End Use Key = Cooling,
Group Key = System (ref. Output:Meter objects).
1.32.1.2.28 VRF Heat Pump Evaporative Condenser Pump Electricity Rate [W]
This is the average electricity consumption rate of the evaporative condenser water pump in Watts
for the time step being reported.
1.32.2 AirConditioner:VariableRefrigerantFlow:FluidTemperatureControl
1.32.2.1 Inputs
1.32.2.1.8 Field: Rated Compressor Power Per Unit of Rated Evaporative Ca-
pacity
This numeric field defines the rated compressor power per Watt of rated evaporative capacity. Rated
compressor power corresponds to the max compressor speed at rated conditions. The actual com-
pressor power is obtained by multiplying the rated power with the modification factor calculated by
Compressor Power Multiplier Function of Temperature Curve. The value must be greater than 0. If
this field is left blank, a default value of 0.35 W/W is assumed.
This alpha field specifies the algorithm for the refrigerant temperature control. Two choices are
available: ConstantTemp or VariableTemp. The indoor unit evaporating temperature at cooling
mode or condensing temperature at heating are fixed in the ConstantTemp algorithm, while in
VariableTemp algorithm they can be varied.
This numeric field defines the minimum evaporating temperature for the indoor unit when VRF
runs at cooling mode. This field is required if Refrigerant Temperature Control Algorithm is Vari-
ableTemp. If this field is blank, the default value of 4.0ºC is used.
This numeric field defines the maximum evaporating temperature for the indoor unit when VRF
runs at cooling mode. This field is required if Refrigerant Temperature Control Algorithm is Vari-
ableTemp. If this field is blank, the default value of 13.0ºC is used.
This numeric field defines the minimum condensing temperature for the indoor unit when VRF
runs at heating mode. This field is required if Refrigerant Temperature Control Algorithm is Vari-
ableTemp. If this field is blank, the default value of 42.0ºC is used.
This numeric field defines the maximum condensing temperature for the indoor unit when VRF
runs at heating mode. This field is required if Refrigerant Temperature Control Algorithm is Vari-
ableTemp. If this field is blank, the default value of 46.0ºC is used.
1.32.2.1.22 Field: Outdoor Unit Fan Power Per Unit of Rated Evaporative Ca-
pacity
This numeric field defines the outdoor unit fan power per watt of rated evaporative capacity. If this
field is blank, the default value of 4.25E-3 W/W is used.
1.32. GROUP – VARIABLE REFRIGERANT FLOW EQUIPMENT 1567
1.32.2.1.23 Field: Outdoor Unit Fan Flow Rate Per Unit of Rated Evaporative
Capacity
This numeric field defines the outdoor unit fan volumetric flow rate per watt of rated evaporative
capacity. If this field is blank, the default value of 7.50E-5 m3 /s-W is used.
1.32.2.1.26 Field: Diameter of Main Pipe Connecting Outdoor Unit to the First
Branch Joint
This numeric field defines the diameter of main pipe connecting the outdoor unit to the first branch
joint. This value is used to calculate the piping loss of the refrigerant when going through the main
pipe, including the heat loss and pressure drop. If this field is blank, the default value of 0.0254m is
used.
1.32.2.1.27 Field: Length of Main Pipe Connecting Outdoor Unit to the First
Branch Joint
This numeric field defines the length of main pipe connecting the outdoor unit to the first branch
joint. This value is used to calculate the heat loss of the refrigerant when going through the main
pipe. The value should be greater than 0. If this field is blank, the default value of 30m is used.
1.32.2.1.29 Field: Height Difference Between Outdoor Unit and Indoor Units
This numeric field defines the height difference between the outdoor unit node and indoor unit node
of the main pipe. This value is used to calculate the piping loss of the refrigerant when going through
the main pipe. The value can be positive, zero, or negative. Positive means outdoor unit is higher
than indoor unit, while negative means outdoor unit is lower than indoor unit.
1568 CHAPTER 1. INPUT-OUTPUT REFERENCE
This numeric field defines the maximum outdoor temperature, in degrees Celsius, below which the
crankcase heater will operate. If this field is left blank, the default value is 5°C. This field is only
used to calculate crankcase heater power and has no impact on heat pump performance.
AirConditioner:VariableRefrigerantFlow :FluidTemperatureControl ,
VRF Heat Pump , !- Heat Pump Name
VRFCondAvailSched , !- Availability Schedule Name
VRF Heat Pump TU List , !- Zone Terminal Unit List Name
R410A , !- Refrigerant Type
41300 , !- Rated Evaporative Capacity {W}
0.344 , !- Rated Compressor Power Per Unit of Rated Evaporative Capacity {W/W}
, !- Minimum Outdoor Air Temperature in Cooling Mode {C}
1.32. GROUP – VARIABLE REFRIGERANT FLOW EQUIPMENT 1571
Curve:Quadratic ,
OUEvapTempCurve , !- Name
0, !- Coefficient1 Constant
6.05E-1, !- Coefficient2 x
2.50E-2, !- Coefficient3 x**2
0, !- Minimum Value of x
15, !- Maximum Value of x
, !- Minimum Curve Output
, !- Maximum Curve Output
Temperature , !- Input Unit Type for X
Temperature; !- Output Unit Type
Curve:Quadratic ,
1572 CHAPTER 1. INPUT-OUTPUT REFERENCE
OUCondTempCurve , !- Name
0, !- Coefficient1 Constant
-2.91, !- Coefficient2 x
1.180 , !- Coefficient3 x**2
0, !- Minimum Value of x
5, !- Maximum Value of x
, !- Minimum Curve Output
, !- Maximum Curve Output
Temperature , !- Input Unit Type for X
Temperature; !- Output Unit Type
Curve:Biquadratic ,
MinSpdCooling , !- Name
3.19E-01, !- Coefficient1 Constant
-1.26E-03, !- Coefficient2 x
-2.15E-05, !- Coefficient3 x**2
1.20E-02, !- Coefficient4 y
1.05E-04, !- Coefficient5 y**2
-8.66E-05, !- Coefficient6 x*y
15, !- Minimum Value of x
65, !- Maximum Value of x
-30, !- Minimum Value of y
15, !- Maximum Value of y
, !- Minimum Curve Output
, !- Maximum Curve Output
Temperature , !- Input Unit Type for X
Temperature , !- Input Unit Type for Y
Dimensionless; !- Output Unit Type
Curve:Biquadratic ,
MinSpdPower , !- Name
8.79E-02 , !- Coefficient1 Constant
-1.72E-04, !- Coefficient2 x
6.93E-05 , !- Coefficient3 x**2
-3.38E-05, !- Coefficient4 y
-8.10E-06, !- Coefficient5 y**2
-1.04E-05, !- Coefficient6 x*y
15, !- Minimum Value of x
65, !- Maximum Value of x
-30, !- Minimum Value of y
15, !- Maximum Value of y
, !- Minimum Curve Output
, !- Maximum Curve Output
Temperature , !- Input Unit Type for X
Temperature , !- Input Unit Type for Y
Dimensionless; !- Output Unit Type
Curve:Biquadratic ,
Spd1Cooling , !- Name
8.12E-01 , !- Coefficient1 Constant
-4.23E-03, !- Coefficient2 x
-4.11E-05, !- Coefficient3 x**2
2.97E-02 , !- Coefficient4 y
2.67E-04 , !- Coefficient5 y**2
-2.23E-04, !- Coefficient6 x*y
15, !- Minimum Value of x
65, !- Maximum Value of x
-30, !- Minimum Value of y
15, !- Maximum Value of y
, !- Minimum Curve Output
, !- Maximum Curve Output
Temperature , !- Input Unit Type for X
Temperature , !- Input Unit Type for Y
Dimensionless; !- Output Unit Type
Curve:Biquadratic ,
Spd1Power , !- Name
3.26E-01 , !- Coefficient1 Constant
-2.20E-03, !- Coefficient2 x
1.42E-04 , !- Coefficient3 x**2
1.32. GROUP – VARIABLE REFRIGERANT FLOW EQUIPMENT 1573
2.82E-03 , !- Coefficient4 y
2.86E-05 , !- Coefficient5 y**2
-3.50E-05, !- Coefficient6 x*y
15, !- Minimum Value of x
65, !- Maximum Value of x
-30, !- Minimum Value of y
15, !- Maximum Value of y
, !- Minimum Curve Output
, !- Maximum Curve Output
Temperature , !- Input Unit Type for X
Temperature , !- Input Unit Type for Y
Dimensionless; !- Output Unit Type
Curve:Biquadratic ,
Spd2Cooling , !- Name
1.32E+00 , !- Coefficient1 Constant
-6.20E-03, !- Coefficient2 x
-7.10E-05, !- Coefficient3 x**2
4.89E-02 , !- Coefficient4 y
4.59E-04 , !- Coefficient5 y**2
-3.67E-04, !- Coefficient6 x*y
15, !- Minimum Value of x
65, !- Maximum Value of x
-30, !- Minimum Value of y
15, !- Maximum Value of y
, !- Minimum Curve Output
, !- Maximum Curve Output
Temperature , !- Input Unit Type for X
Temperature , !- Input Unit Type for Y
Dimensionless; !- Output Unit Type
Curve:Biquadratic ,
Spd2Power , !- Name
6.56E-01 , !- Coefficient1 Constant
-3.71E-03, !- Coefficient2 x
2.07E-04 , !- Coefficient3 x**2
1.05E-02 , !- Coefficient4 y
7.36E-05 , !- Coefficient5 y**2
-1.57E-04, !- Coefficient6 x*y
15, !- Minimum Value of x
65, !- Maximum Value of x
-30, !- Minimum Value of y
15, !- Maximum Value of y
, !- Minimum Curve Output
, !- Maximum Curve Output
Temperature , !- Input Unit Type for X
Temperature , !- Input Unit Type for Y
Dimensionless; !- Output Unit Type
1.32.2.2 Outputs
In addition to the output variables described for the VRF-SysCurve model in Section 1.32.1, the
VRF-FluidTCtrl model also provides the following output variables:
Note: refer to the rdd file after a simulation for exact output variable names
1.32.2.2.8 VRF Heat Pump Cooling Capacity at Max Compressor Speed [W]
This output field is the maximum cooling capacity of the variable refrigerant flow system at particular
operational conditions, corresponding to the maximum compressor speed. This value is calculated
for each HVAC system time step being simulated, and the results are averaged for the time step
being reported. This output only applies for the VRF-FluidTCtrl model.
1.32.2.2.9 VRF Heat Pump Heating Capacity at Max Compressor Speed [W]
This output field is the maximum heating capacity of the variable refrigerant flow system at particular
operational conditions, corresponding to the maximum compressor speed. This value is calculated
for each HVAC system time step being simulated, and the results are averaged for the time step
being reported. This output only applies for the VRF-FluidTCtrl model.
1.32.2.2.10 VRF Heat Pump Outdoor Unit Evaporator Heat Extract Rate [W]
This output field is the heat extract rate of the VRF outdoor unit evaporator in Watts. This value
is calculated for each HVAC system time step being simulated, and the results are averaged for the
time step being reported. This output only applies for the VRF-FluidTCtrl model.
1.32.2.2.11 VRF Heat Pump Outdoor Unit Condenser Heat Release Rate [W]
This output field is the heat release rate of the VRF outdoor unit condenser in Watts. This value
is calculated for each HVAC system time step being simulated, and the results are averaged for the
time step being reported. This output only applies for the VRF-FluidTCtrl model. This output
only applies for the VRF-FluidTCtrl model.
1.32.3 AirConditioner:VariableRefrigerantFlow:FluidTemperatureControl:
1.32.3.1 Inputs
1.32.3.1.6 Field: Rated Compressor Power Per Unit of Rated Evaporative Ca-
pacity
This numeric field defines the rated compressor power per Watt of rated evaporative capacity. Rated
compressor power corresponds to the max compressor speed at rated conditions. The actual com-
pressor power is obtained by multiplying the rated power with the modification factor calculated by
Compressor Power Multiplier Function of Temperature Curve. The value must be greater than 0. If
this field is left blank, a default value of 0.35 W/W is assumed.
This numeric field defines the maximum outdoor temperature allowed for heating only mode. Above
this temperature, heating is disabled. If this field is left blank, the default value is 16ºC.
1.32. GROUP – VARIABLE REFRIGERANT FLOW EQUIPMENT 1577
This numeric field defines the maximum outdoor temperature allowed for heat recovery operations.
Below this temperature, heat recovery operations is disabled. If this field is left blank, the default
value is -20ºC.
This numeric field defines the maximum outdoor temperature allowed for heat recovery operations.
Above this temperature, heat recovery operations is disabled. If this field is left blank, the default
value is 43ºC.
This alpha field specifies the algorithm for the refrigerant temperature control. Two choices are
available: ConstantTemp or VariableTemp. The indoor unit evaporating temperature at cooling
mode or condensing temperature at heating are fixed in the ConstantTemp algorithm, while in
VariableTemp algorithm they can be varied.
This numeric field defines the minimum evaporating temperature for the indoor unit when VRF
runs at cooling mode. This field is required if Refrigerant Temperature Control Algorithm is Vari-
ableTemp. If this field is blank, the default value of 4.0ºC is used.
This numeric field defines the maximum evaporating temperature for the indoor unit when VRF
runs at cooling mode. This field is required if Refrigerant Temperature Control Algorithm is Vari-
ableTemp. If this field is blank, the default value of 13.0ºC is used.
1578 CHAPTER 1. INPUT-OUTPUT REFERENCE
This numeric field defines the minimum condensing temperature for the indoor unit when VRF
runs at heating mode. This field is required if Refrigerant Temperature Control Algorithm is Vari-
ableTemp. If this field is blank, the default value of 42.0ºC is used.
This numeric field defines the maximum condensing temperature for the indoor unit when VRF
runs at heating mode. This field is required if Refrigerant Temperature Control Algorithm is Vari-
ableTemp. If this field is blank, the default value of 46.0ºC is used.
1.32.3.1.26 Field: Outdoor Unit Fan Power Per Unit of Rated Evaporative Ca-
pacity
This numeric field defines the outdoor unit fan power per watt of rated evaporative capacity. If this
field is blank, the default value of 4.25E-3 W/W is used.
1.32. GROUP – VARIABLE REFRIGERANT FLOW EQUIPMENT 1579
1.32.3.1.27 Field: Outdoor Unit Fan Flow Rate Per Unit of Rated Evaporative
Capacity
This numeric field defines the outdoor unit fan volumetric flow rate per watt of rated evaporative
capacity. If this field is blank, the default value of 7.50E-5 m3 /s-W is used.
1.32.3.1.32 Field: Length of Main Pipe Connecting Outdoor Unit to the First
Branch Joint
This numeric field defines the length of main pipe connecting outdoor unit to the first branch joint.
This value is used to calculate the heat loss of the refrigerant when going through the main pipe.
The value should be greater than 0. If this field is blank, the default value of 30m is used.
1.32.3.1.34 Field: Height Difference Between Outdoor Unit and Indoor Units
This numeric field defines the height difference between the outdoor unit node and indoor unit node
of the main pipe. This value is used to calculate the piping loss of the refrigerant when going through
the main pipe. The value can be positive, zero, or negative. Positive means outdoor unit is higher
than indoor unit, while negative means outdoor unit is lower than indoor unit.
the 2nd stage compressor and all additional compressors are assumed to be equally sized. This field
is only used to calculate crankcase heater power and has no impact on VRF system performance.
entered in Heat Recovery Heating Capacity Time Constant input field. If the transition period will
not be modeled, this input field must be set to 1.
Curve:Quadratic ,
OUEvapTempCurve , !- Name
0, !- Coefficient1 Constant
6.05E-1, !- Coefficient2 x
2.50E-2, !- Coefficient3 x**2
0, !- Minimum Value of x
15, !- Maximum Value of x
, !- Minimum Curve Output
, !- Maximum Curve Output
Temperature , !- Input Unit Type for X
Temperature; !- Output Unit Type
Curve:Quadratic ,
OUCondTempCurve , !- Name
0, !- Coefficient1 Constant
-2.91, !- Coefficient2 x
1.180 , !- Coefficient3 x**2
0, !- Minimum Value of x
5, !- Maximum Value of x
, !- Minimum Curve Output
, !- Maximum Curve Output
Temperature , !- Input Unit Type for X
1586 CHAPTER 1. INPUT-OUTPUT REFERENCE
Curve:Biquadratic ,
MinSpdCooling , !- Name
3.19E-01, !- Coefficient1 Constant
-1.26E-03, !- Coefficient2 x
-2.15E-05, !- Coefficient3 x**2
1.20E-02, !- Coefficient4 y
1.05E-04, !- Coefficient5 y**2
-8.66E-05, !- Coefficient6 x*y
15, !- Minimum Value of x
65, !- Maximum Value of x
-30, !- Minimum Value of y
15, !- Maximum Value of y
, !- Minimum Curve Output
, !- Maximum Curve Output
Temperature , !- Input Unit Type for X
Temperature , !- Input Unit Type for Y
Dimensionless; !- Output Unit Type
Curve:Biquadratic ,
MinSpdPower , !- Name
8.79E-02 , !- Coefficient1 Constant
-1.72E-04, !- Coefficient2 x
6.93E-05 , !- Coefficient3 x**2
-3.38E-05, !- Coefficient4 y
-8.10E-06, !- Coefficient5 y**2
-1.04E-05, !- Coefficient6 x*y
15, !- Minimum Value of x
65, !- Maximum Value of x
-30, !- Minimum Value of y
15, !- Maximum Value of y
, !- Minimum Curve Output
, !- Maximum Curve Output
Temperature , !- Input Unit Type for X
Temperature , !- Input Unit Type for Y
Dimensionless; !- Output Unit Type
Curve:Biquadratic ,
Spd1Cooling , !- Name
8.12E-01 , !- Coefficient1 Constant
-4.23E-03, !- Coefficient2 x
-4.11E-05, !- Coefficient3 x**2
2.97E-02 , !- Coefficient4 y
2.67E-04 , !- Coefficient5 y**2
-2.23E-04, !- Coefficient6 x*y
15, !- Minimum Value of x
65, !- Maximum Value of x
-30, !- Minimum Value of y
15, !- Maximum Value of y
, !- Minimum Curve Output
, !- Maximum Curve Output
Temperature , !- Input Unit Type for X
Temperature , !- Input Unit Type for Y
Dimensionless; !- Output Unit Type
Curve:Biquadratic ,
Spd1Power , !- Name
3.26E-01 , !- Coefficient1 Constant
-2.20E-03, !- Coefficient2 x
1.42E-04 , !- Coefficient3 x**2
2.82E-03 , !- Coefficient4 y
2.86E-05 , !- Coefficient5 y**2
-3.50E-05, !- Coefficient6 x*y
15, !- Minimum Value of x
65, !- Maximum Value of x
-30, !- Minimum Value of y
15, !- Maximum Value of y
, !- Minimum Curve Output
, !- Maximum Curve Output
1.32. GROUP – VARIABLE REFRIGERANT FLOW EQUIPMENT 1587
Curve:Biquadratic ,
Spd2Cooling , !- Name
1.32E+00 , !- Coefficient1 Constant
-6.20E-03, !- Coefficient2 x
-7.10E-05, !- Coefficient3 x**2
4.89E-02 , !- Coefficient4 y
4.59E-04 , !- Coefficient5 y**2
-3.67E-04, !- Coefficient6 x*y
15, !- Minimum Value of x
65, !- Maximum Value of x
-30, !- Minimum Value of y
15, !- Maximum Value of y
, !- Minimum Curve Output
, !- Maximum Curve Output
Temperature , !- Input Unit Type for X
Temperature , !- Input Unit Type for Y
Dimensionless; !- Output Unit Type
Curve:Biquadratic ,
Spd2Power , !- Name
6.56E-01 , !- Coefficient1 Constant
-3.71E-03, !- Coefficient2 x
2.07E-04 , !- Coefficient3 x**2
1.05E-02 , !- Coefficient4 y
7.36E-05 , !- Coefficient5 y**2
-1.57E-04, !- Coefficient6 x*y
15, !- Minimum Value of x
65, !- Maximum Value of x
-30, !- Minimum Value of y
15, !- Maximum Value of y
, !- Minimum Curve Output
, !- Maximum Curve Output
Temperature , !- Input Unit Type for X
Temperature , !- Input Unit Type for Y
Dimensionless; !- Output Unit Type
1.32.4 ZoneTerminalUnitList
The zone terminal unit list defines the names of the terminal units connected to a single variable
refrigerant flow air-conditioning system. The zone terminal unit list is used exclusively in the variable
refrigerant flow (VRF) air conditioner object (ref: AirConditioner:VariableRefrigerantFlow). Up to
20 terminal units may be connected to a single VRF outdoor condensing unit. This list is extensible
if additional indoor terminal units are required. The name of this zone terminal unit list object
is then input into the corresponding variable refrigerant flow air conditioner object. The following
figure demonstrates this concept.
1.32.4.1 Inputs
This alpha field defines the name of the zone terminal unit used in a variable refrigerant
air conditioner. The zone terminal unit must be connected to a zone using the Zone-
HVAC:EquipmentConnections object. The terminal unit air inlet node is the same name as
a zone exhaust node. The terminal unit air outlet node is the same name as a zone inlet node. This
object is extensible, so additional fields of this type can be added to the end of this object.
Following is an example input for a ZoneTerminalUnitList object.
ZoneTerminalUnitList ,
VRF Heat Pump TU List , !- Zone Terminal Unit List Name
TU3 , !- Zone Terminal Unit Name 1
TU4 , !- Zone Terminal Unit Name 2
TU1 , !- Zone Terminal Unit Name 3
TU2 , !- Zone Terminal Unit Name 4
TU5; !- Zone Terminal Unit Name 5
– ZoneHVAC:Baseboard:Convective:Electric
– ZoneHVAC:Baseboard:RadiantConvective:Water
– ZoneHVAC:Baseboard:RadiantConvective:Steam
– ZoneHVAC:Baseboard:RadiantConvective:Electric
1.33. GROUP – RADIATIVE / CONVECTIVE UNITS 1589
– ZoneHVAC:CoolingPanel:RadiantConvective:Water
– ZoneHVAC:Baseboard:Convective:Water
– ZoneHVAC:HighTemperatureRadiant
– ZoneHVAC:LowTemperatureRadiant:ConstantFlow
– ZoneHVAC:LowTemperatureRadiant:Electric
– ZoneHVAC:LowTemperatureRadiant:VariableFlow
1.33.1 ZoneHVAC:Baseboard:RadiantConvective:Water
The objective of this model is to calculate the convective and radiant heat transfer from water
baseboard heaters to the people and the surfaces within a zone so that surface heat balances can
take into account the radiant heat transfer to the surfaces and thus enhance the accuracy of thermal
comfort predictions within the space. The radiant heat gains are distributed to the surfaces by
fractions defined by user input.
1.33.1.1 Inputs
X
F ractionIndicentOnP eople + F ractionT oSurf aces = 1 (1.137)
ZoneHVAC:Baseboard:RadiantConvective:Water ,
SPACE4 -1 Baseboard , !- Name
SPACE4 -1 Baseboard Design , !- Design Object Name
ReheatCoilAvailSched , !- Availability Schedule Name
SPACE4 -1 Zone Coil Water In Node , !- Inlet Node Name
SPACE4 -1 Zone Coil Water Out Node , !- Outlet Node Name
82.22 , !- Rated Average Water Temperature
0.063 , !- Rated Water Mass Flow Rate
autosize , !- Heating Design Capacity
autosize , !- Maximum Water Flow Rate
LEFT -1, !- Surface 1 Name
0.4, !- fraction of radiant energy from heater distributed to
surface 1
C4 -1, !- Surface 2 Name
0.2, !- fraction of radiant energy from heater distributed to
surface 2
SB45 , !- Surface 3 Name
0.1; !- fraction of radiant energy from heater distributed to
surface 3
SB23 , !- Surface 4 Name
0.1, !- fraction of radiant energy from heater distributed to
surface 4
SB25 , !- Surface 5 Name
0.1, !- fraction of radiant energy from heater distributed to
surface 5
WR -1, !- Surface 6 Name
0.1; !- fraction of radiant energy from heater distributed to
surface 6
1.33.1.2 ZoneHVAC:Baseboard:RadiantConvective:Water:Design
This object contains the design fields for ZoneHVAC:Baseboard:RadiantConvective:Water. The in-
formation from one ZoneHVAC:Baseboard:RadiantConvective:Water:Design object can be shared
with several ZoneHVAC:Baseboard:RadiantConvective:Water objects.
radiant baseboard unit and the heating capacity per unit floor area value specified by the user. This
field may be left blank.
|(Qbb,out − QZoneLoad )|
≤ ConvergenceT olerance (1.138)
QZoneLoad
ZoneHVAC:Baseboard:RadiantConvective:Water:Design ,
SPACE2 -1 Baseboard Design , !- Design Object Name
HeatingDesignCapacity , !- Heating Design Capacity Method
, !- Heating Design Capacity Per Floor Area
, !- Fraction of Autosized Heating Design Capacity
0.001 , !- Convergence Tolerance
0.3, !- Fraction Radiant
0.3; !- Fraction of Radiant Energy Incident on People
1.33. GROUP – RADIATIVE / CONVECTIVE UNITS 1593
1.33.1.3 Outputs
1.33.2 ZoneHVAC:Baseboard:RadiantConvective:Steam
The objective of this model is to calculate the convective and radiant heat transfer from steam
baseboard heaters to the people and the surfaces within a zone so that surface heat balances can
take into account the radiant heat transfer to the surfaces and thus enhance the accuracy of thermal
comfort predictions within the space. The radiant heat gains are distributed to the surfaces by
fractions defined by the user. Users are requested to provide degree of sub cooling to estimate the
outlet conditions of the condensate.
1.33.2.1 Inputs
input by the user. These fractions to people and surfaces must add up to 1.0. In other words, in an
input file, the following relation should be maintained by the user input:
X
F ractionIndicentOnP eople + F ractionT oSurf aces = 1 (1.139)
ZoneHVAC:Baseboard:RadiantConvective:Steam ,
SPACE1 -1 Baseboard , !- Name
SPACE1 -1 Baseboard Design , !- Design Object Name
REHEATCOILAVAILSCHED , !- Availability Schedule Name
SPACE1 -1 Reheat Coil Steam Inlet , !- Inlet Node Name
SPACE1 -1 Reheat Coil Steam Outlet , !- Outlet Node Name
Autosize , !- Heating Design Capacity
5, !- Degree of SubCooling
autosize , !- Maximum Steam Flow Rate
FRONT -1, !- Surface 1 Name
0.4, !- Fraction of radiant energy from heater distributed to
surface 1
C1 -1, !- Surface 2 Name
0.2, !- Fraction of radiant energy from heater distributed to
surface 2
SB15 , !- Surface 3 Name
0.1; !- Fraction of radiant energy from heater distributed to
surface 3
Floor , !- Surface 4 Name
0.1; !- Fraction of radiant energy from heater distributed to
surface 4
1.33.2.2 ZoneHVAC:Baseboard:RadiantConvective:Steam:Design
|(Qbb,out − QZoneLoad )|
≤ ConvergenceT olerance (1.140)
QZoneLoad
ZoneHVAC:Baseboard:RadiantConvective:Steam:Design ,
SPACE1 -1 Baseboard Design , !- Design Object Name
HeatingDesignCapacity , !- Heating Design Capacity Method
, !- Heating Design Capacity Per Floor Area
, !- Fraction of Autosized Heating Design Capacity
1598 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.33.2.3 Outputs
1.33.3 ZoneHVAC:Baseboard:RadiantConvective:Electric
The electric baseboard heater is a component in the zone equipment simulation. Heat from this
device is radiated to people and surfaces and also convected to the surrounding air. The electric
baseboard model includes the impact of the radiant heat addition to people and surfaces so that the
thermal comfort and surface heat balances are impacted. The component is controlled to meet any
remaining zone load not met by other equipment baseboard operates to meet the remaining zone
load and the total electric consumption is calculated by dividing by the efficiency of the baseboard.
1.33.3.1 Inputs
ZoneHVAC:Baseboard:RadiantConvective:Electric ,
Baseboard 1, !- Name
BB Schedule , !- Availability Schedule Name
HeatingDesignCapacity , !- Heating Design Capacity Method
5000, !- Heating Design Capacity{ W }
, !- Heating Design Capacity Per Floor Area{ W / m2 }
, !- Fraction of Autosized Heating Design Capacity{ -}
0.97, !- Efficiency of the baseboard
0.3, !- Fraction radiant
0.3, !- Fraction of radiant energy that is incident directly on people
EastWall , !- Surface 1 name
0.3, !- Fraction of radiant energy from heater distributed to surface 1
WestWall , !- Surface 2 name
0.1, !- Fraction of radiant energy from heater distributed to surface 2
NorthWall , !- Surface 3 name
1602 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.33.3.2 Outputs
1.33.4 ZoneHVAC:CoolingPanel:RadiantConvective:Water
The radiant/convective cooling panel is a type of zone equipment. Chilled water is supplied by
the plant and circulated through the panel. Through radiation and convective heat transfer, the
panel absorbs energy contained within the zone to provide cooling. Control of the panel is achieved
using the methodology used for low temperature radiant systems—a piecewise linear control profile
that varies the flow rate to the panel based on a control parameter defined by the user. This is
different than being controlled to meet any remaining load like the air-based systems. However,
due to the radiant nature of these devices, it is not possible to control precisely on a zone air-based
load since this will result in overcooling at the next time step. Despite this, in addition to the
piecewise linear controls that have been used with low temperature radiant systems in the past, two
new controls are available for this simple model: one that varies the convective output of the system
to meet the remaining zone load and one that varies the total convective output of the system to
meet the remaining zone load. In these two zone load control types, the user must enter the typical
zone thermostat object to replace the setpoint and throttling range input in this object. In this
component, control is accomplished by throttling the chilled water flow to the device. Capacity
rating information is required as input and is used to calculate a UA value of the unit. The unit
is connected to a chilled water loop (demand side) with an inlet and outlet node. The input data
dictionary definition of the unit is as follows.
1.33.4.1 Inputs
– MeanAirTemperature
– MeanRadiantTemperature
– OperativeTemperature
1606 CHAPTER 1. INPUT-OUTPUT REFERENCE
– OutdoorDryBulbTemperature
– OutdoorWetBulbTemperature
– ZoneConvectiveLoad
– ZoneTotalLoad
Operative temperature for radiant system controls is the average of Mean Air Temperature and
Mean Radiant Temperature. If the user does not select a control type, MeanAirTemperature control
is assumed by EnergyPlus. See the throttling range and control temperature schedule fields below
for more information.
dewpoint temperature and the inlet water temperature, this will allow some flexibility in controlling
when the panel will shutdown to avoid condensation. There are three options for handling potential
condensation: Off, SimpleOff, and VariableOff. This parameter is optional and will default to
SimpleOff.
– Off - EnergyPlus will not do anything other than produce a warning message when condensation
is predicted to occur. The program will simply continue on; no moisture will be removed from
the zone air and there will be no adjustment of the surface temperature as a result of the
condensation.
– SimpleOff - the program will predict cases where condensation will occur and shut-off the
radiant system to avoid this situation. With this option, the user also has the option to adjust
when the system will shut down. This is specified with the next parameter (field: Condensation
Differential Parameter).
– VariableOff - the program will attempt to reduce the inlet temperature to the panel by locally
recirculating some of the water leaving the panel and mixing it with water from the overall
demand side flow. This also means that some of the demand side water will bypass the panel.
In reality, this would require a pump to achieve such mixing and recirculation, but due to the
simple nature of this model, no pump definition will be required. Like the SimpleOff option,
the VariableOff option uses the condensation dewpoint offset parameter to adjust when the
system will try to adjust for the possibility of condensation.
calculate how much of the energy being absorbed by the unit is radiant energy. This parameter can
be difficult to quantify as the fraction radiant can vary with zone conditions. However, by definition,
a radiant system like this radiant cooling panel exchanges at least half of its energy to the zone
via radiation. One study has shown that a fraction radiant between 0.6 and 0.7 is a reasonable
estimation. For more information, see the EnergyPlus Engineering Reference in section Radiant
System Models, subsection Simple Radiant Cooling Panel.
a colder surface would violate the Second Law of Thermodynamics. However, in keeping with the
simple nature of this model, EnergyPlus will monitor the inlet water temperature to the panel and
produce a warning message if this temperature is lower than any of the surface temperature of the
surfaces with which this system is interacting.
An example input for the radiant cooling panel is shown below.
ZoneHVAC:CoolingPanel: RadiantConvective:Water ,
Radiant Cooling Panel 1, !- Name
RCP Schedule 1, !- Availability schedule
RCP Water Inlet Node , !- Water Inlet node name
RCP Water Outlet Node , !- Water Outlet node name
5.0, !- Rated Water Inlet Temperature {C}
24.0, !- Rated Space Temperature {C}
0.063 , !- Rated Water Mass Flow Rate {kg/s}
5000.0 , !- Rated cooling capacity {W}
0.1, !- Maximum water flow rate {m3/s}
MeanAirTemperature , !- Temperature Control Type
1.0, !- Cooling Control Throttling Range
RCP Temp Schedule , !- Cooling Control Temperature Schedule Name
SimpleOff , !- Condensation Control Type
1.0, !- Condensation Control Dewpoint Offset
0.65, !- Fraction Radiant
0.2, !- Fraction of Radiant Energy Incident on People
Zone 1 Floor , !- Surface 1 Name
0.5, !- Fraction of Radiant Energy to Surface 1
Zone 1 West Wall , !- Surface 2 Name
0.25, !- Fraction of Radiant Energy to Surface 2
Zone 1 South Wall , !- Surface 3 Name
0.25; !- Fraction of Radiant Energy to Surface 3
1.33.4.2 Outputs
1.33.5 ZoneHVAC:Baseboard:Convective:Water
The hot water baseboard heater is a component of zone equipment. The component is controlled
to meet any remaining zone load not met by other equipment in the zone that have higher heating
priority. The control is accomplished by throttling the hot water flow. Input resembles that for the
simple heating coil: there is an availability schedule, an overall UA, and a maximum hot water mass
flow rate. The unit is connected to a hot water loop (demand side) with an inlet and outlet node.
Finally, there is the convergence tolerance, which is the tolerance on how closely the baseboard outlet
will meet the zone load. Of course, this tolerance is relative to the zone load.
1.33.5.1 Inputs
where q is the heat transferred from water to the air in watts; Twater,avg is the average water
temperature in degrees C; and Tair,avg is the average air temperature in degrees C. Or the LMTD
temperature difference can be used.
|(Qbb,out − QZoneLoad )|
≤ ConvergenceT olerance (1.144)
QZoneLoad
ZoneHVAC:Baseboard:Convective:Water ,
Zone3Baseboard , !- name
FanAndCoilAvailSched , !- on/off schedule
Zone 3 Reheat Water Inlet Node , !- water inlet node
Zone 3 Reheat Water Outlet Node , !- water outlet node
HeatingDesignCapacity , !- Heating Design Capacity Method
autosize , !- Heating Design Capacity{ W }
, !- Heating Design Capacity Per Floor Area{ W / m2 }
, !- Fraction of Autosized Heating Design Capacity{ -}
500., !- UA
0.0013 , !- maximum water flow rate m3/s
0.001; !- tolerance
1.33.5.2 Outputs
1.33.6 ZoneHVAC:Baseboard:Convective:Electric
The electric baseboard heater is a component in the zone equipment simulation. The component is
controlled to meet any remaining zone load not met by other equipment in the zone that have higher
heating priority. The control is accomplished by taking the remaining zone load and dividing by the
efficiency of the baseboard.
1.33.6.1 Inputs
ZoneHVAC:Baseboard:Convective:Electric ,
Zone1Baseboard , !- Baseboard Name
FanAndCoilAvailSched , !- Availability Schedule Name
HeatingDesignCapacity , !- Heating Design Capacity Method
5000, !- Heating Design Capacity{ W }
, !- Heating Design Capacity Per Floor Area{ W / m2 }
, !- Fraction of Autosized Heating Design Capacity{ -}
0.97; !- Efficiency of the BaseBoard
1.33.6.2 Outputs
1.33.7 ZoneHVAC:LowTemperatureRadiant:VariableFlow
This low temperature radiant system (hydronic) is a component of zone equipment that is intended
to model any “radiant system” where water is used to supply/remove energy to/from a building
surface (wall, ceiling, or floor). The component is controlled to meet any remaining zone load not
met by other equipment in the zone that have higher priority. The control is accomplished by
throttling the hot or chilled water flow to the unit. Note that this system will only control based on
the radiant system controls defined by this input syntax and not via a zone thermostat such as is
used for forced air systems. Note also that because this unit does not require a thermostat that in
cases where no other systems are serving the zone in which this system resides that it will use the
heating equipment priority to determine which system will run first. If the radiant system is serving
a zone with forced air equipment, the radiant system will follow the priority order established by the
zone thermostat but will still base its response on the controls defined by the user for the radiant
system.
This model covers a wide range of low temperature radiant systems: heating and/or cooling, panel or
embedded pipes, etc. It is not intended to simulate high temperature electric or gas radiant heaters.
Those devices will be handled by a separate model and different input syntax. Low temperature
radiant systems that use electric resistance heating should also be defined using separate input
syntax (ref: ZoneHVAC:LowTemperatureRadiant:Electric). The key characteristic of this variable
flow low temperature radiant system is that the actual fluid flow rate being supplied to the radiant
system changes as conditions within the zone change. While the fluid temperature is determined
by the plant loops defined by other user input, this type of radiant system will control fluid flow
in an attempt to meet the remaining zone heating or cooling load based on the controls outlined
below. Low temperature radiant systems that vary the inlet temperature while keeping the fluid
flow rate through the radiant system constant should also be defined using separate input syntax
(ref: ZoneHVAC:LowTemperatureRadiant:ConstantFlow).
1.33.7.1 Inputs
the maximum flow rate specified in this field as the lower and upper bounds, respectively. Note that
if the user elects to autosize this field that a standard zone thermostat such as would be used for a
forced air system must be defined as autosizing calculations are based on the zone thermostat value
and not on the radiant system control values.
1.33.7.2 ZoneHVAC:LowTemperatureRadiant:VariableFlow:Design
This object contains the design fields for ZoneHVAC:LowTemperatureRadiant:VariableFlow. The in-
formation from one ZoneHVAC:LowTemperatureRadiant:VariableFlow:Design object can be shared
with several ZoneHVAC:LowTemperatureRadiant:VariableFlow objects.
– ConvectionOnly - This is the default mode and the method that was implemented when the
radiant model was first introduced into EnergyPlus. In this modeling option, it is assumed
1620 CHAPTER 1. INPUT-OUTPUT REFERENCE
that the impact of the tube material on heat exchange between the fluid and the radiant
system and that only the convection between the fluid and the radiant system is the only
critical heat transfer mechanism to take into account. The reasoning behind this included the
fact that there are other simplifications in the method for calculating heat transfer and that
this simplification would not result in any significant difference in the simulated heat transfer
performance of the system. Convection between the fluid and the pipe wall of the system is
related to physical parameters of the system (pipe/tube inner diameter and length) as well as
the flow characteristics.
– ISOStandard - This method is based on the ISO Standard 11855, Part 2 (2012) document
entitled “Building environment design — Design, dimensioning, installation and control of
embedded radiant heating and cooling systems — Part 2: Determination of the design heating
and cooling capacity”, Reference Number ISO 11855-2:2012(E). This standard recommends
equations (see Appendix B of this document) to include the effects of convective heat transfer
between the fluid and the inside of the piping and conduction through the pipe wall. This model
requires both the inner and outer diameter of the pipe/tube, the length of the pipe/tube, and
the thermal conductivity of the pipe/tube material. Note that as part of the implementation
of this model in EnergyPlus, flow within the piping/tubing is always assumed to be turbulent.
choice of temperature is controlled by the current field–temperature control type. The user must
select from the following options:
– MeanAirTemperature - The mean air temperature of the zone being controlled by this radiant
system.
– MeanRadiantTemperature - The mean radiant temperature of the zone being controlled by
this radiant system.
– OperativeTemperature - The operative temperature of the zone being controlled by the radint
system. Operative temperature for radiant system controls is the average of Mean Air Tem-
perature and Mean Radiant Temperature.
– OutdoorDryBulbTemperature - The outdoor dry-bulb temperature of the current outdoor en-
vironment.
– OutdoorWetBulbTemperature - The outdoor wet-bulb temperature of the current outdoor
environment.
– SurfaceFaceTemperature - This option allows the user to control the radiant system using the
inside face surface temperature of the radiant system (the inside surface temperature).
– SurfaceInteriorTemperature - This option will allow the user to control the radiant system
using a surface temperature that is calculated inside the radiant system. This point will
be defined by the ConstructionProperty:InternalHeatSource description for the system. In
that input, the user has the option to calculate a temperature at a particular point in the
construction. The radiant system will then use this information for controlling the slab not
just producing temperatures for outputting at that point. Users should consult the input for
Field: Temperature Calculation Requested After Layer Number for more information. Note
that for the SurfaceFaceTemperature and SurfaceInteriorTemperature the surface being used
for control is the surface listed above in the field for Surface Name. If the user enters a group of
surfaces for that input, the first surface in the radiant group is the surface for control purposes.
If the user does not select a control type, MeanAirTemperature control is assumed by EnergyPlus.
See the throttling range and control temperature schedule fields below for more information on how
the setpoint temperature is established for this particular radiant system.
will vary the flow linearly between zero for when the control temperature is at 15°C to full flow at
13°C.
Control Temperature Schedule specifies the “setpoint” temperature that is to be met. This is used
in conjunction with the Setpoint Type which defines whether the flow rate of the system is at zero
flow or half flow when the parameter defined by the Temperature Control Type is equal to the
setpoint temperature defined by the Cooling Control Temperature Schedule. See these other input
parameters of this radiant system for more information on these different parameters. Note that
when the throttling range is set to zero that this approximates an on-off system that is either fully
on or totally off.
For clarity, here is an example of how the flow rate to the system will be set. In this example, it is
assumed that cooling control temperature setpoint is currently 25°C, the cooling throttling range is
2°C, and that the setpoint type is HalfFlowPower. The water flow rate to the radiant system will be
zero when the controlling temperature (MAT, MRT, Operative Temperature, etc.; see control type
field above) is at or below 24°C and the maximum flow rate when the controlling temperature is at
or above 26°C. This represents a throttling range of 2°C around the setpoint of 25°C. In between
24°C and 26°C, the flow rate to the radiant system is varied linearly from zero flow at a control
temperature of 24°C to half flow at 15°C to full flow at w6°C. If the throttling range is changed to
0°C or on-off control, then the system will be on above 25°C and off below 25°C. However, if the
throttling range is kept at 2°C and the setpoint type is changed to ZeroFlowPower, then the system
will vary the flow linearly between zero for when the control temperature is at 25°C to full flow at
27°C.
– Off - EnergyPlus will not do anything other than produce a warning message when condensation
is predicted to occur. The program will simply continue on, no moisture will be removed from
the zone air, and there will be no adjustment of the surface temperature as a result of the
condensation.
– SimpleOff - the program will predict cases where condensation will occur and shut-off the
radiant system to avoid this situation. With this option, the users also have the opportunity
to adjust when the system will shut down. This is specified with the next parameter (field:
Condensation Control Dewpoint Offset).
1.33. GROUP – RADIATIVE / CONVECTIVE UNITS 1625
– VariableOff - the program will determine whether condensation is predicted for the flow rate
determined by the unit control scheme. If condensation is predicted, the unit makes one
attempt to reduce the flow rate using linear interpolation between the controlled flow rate and
a zero flow rate to achieve a surface temperature that would match the dew-point temperature
modified by the condensation control dew-point offset (field: Condensation Control Dewpoint
Offset). For example, if the controlled flow rate results in a surface temperature of 10°C, a zero
flow rate results in a surface temperature of 12°C, and the modified condensation dew-point
temperature is 11°C, then the reduced flow rate would be half of the controlled flow rate. If
this reduced flow approximation does not result in condensation, then this reduced flow is used
for the unit. If the reduced flow approximation still results in condensation, then the unit is
turned off to avoid excessive iterations.
1.33.7.3 Outputs
1.33.8 ZoneHVAC:LowTemperatureRadiant:ConstantFlow
This low temperature radiant system (hydronic) is a component of zone equipment that is intended
to model any “radiant system” where water is used to supply/remove energy to/from a building
surface (wall, ceiling, or floor). The component is controlled via control schedules as described in
the syntax below and does not require a zone thermostat. Note that because this unit does not
require a thermostat that in cases where no other systems are serving the zone in which this system
resides that it will use the heating equipment priority to determine which system will run first. If
the radiant system is serving a zone with forced air equipment, the radiant system will follow the
priority order established by the zone thermostat but will still base its response on the controls
defined by the user for the radiant system.
The constant flow system differs from the variable flow system describe above in what it controls.
The variable flow system varies the flow rate through the radiant system based on some control
temperature. The constant flow system keeps flow rate through the radiant system constant. In
order to meet the zone load, the constant flow system will varies the water temperature that is
sent to the radiant system. This is accomplished with a mixing valve that is controlled by a sensor
and a local recirculation pump. This model covers a wide range of low temperature radiant systems:
heating and/or cooling, panel or embedded pipes, etc. It is not intended to simulate high temperature
electric or gas radiant heaters. Those devices will be handled by a separate model and different input
syntax. Low temperature radiant systems that use electric resistance heating should also be defined
1628 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.33.8.1 Inputs
current control temperature (see Temperature Control Type above) is compared to the high and low
control temperatures at the current time. If the control temperature is above the high temperature,
then the inlet water temperature is set to the low water temperature. If the control temperature
is below the low temperature, then system will be turned off and the water mass flow rate will be
zero. If the control temperature is between the high and low value, then the inlet water temperature
is linearly interpolated between the low and high water temperature values. For more information
and a graph of how the water and control schedules affect the system operation, please consult the
Engineering Reference document.
1.33.8.2 ZoneHVAC:LowTemperatureRadiant:ConstantFlow:Design
– ConvectionOnly - This is the default mode and the method that was implemented when the
radiant model was first introduced into EnergyPlus. In this modeling option, it is assumed
1.33. GROUP – RADIATIVE / CONVECTIVE UNITS 1633
that the impact of the tube material on heat exchange between the fluid and the radiant
system and that only the convection between the fluid and the radiant system is the only
critical heat transfer mechanism to take into account. The reasoning behind this included the
fact that there are other simplifications in the method for calculating heat transfer and that
this simplification would not result in any significant difference in the simulated heat transfer
performance of the system. Convection between the fluid and the pipe wall of the system is
related to physical parameters of the system (pipe/tube inner diameter and length) as well as
the flow characteristics.
– ISOStandard - This method is based on the ISO Standard 11855, Part 2 (2012) document
entitled “Building environment design — Design, dimensioning, installation and control of
embedded radiant heating and cooling systems — Part 2: Determination of the design heating
and cooling capacity”, Reference Number ISO 11855-2:2012(E). This standard recommends
equations (see Appendix B of this document) to include the effects of convective heat transfer
between the fluid and the inside of the piping and conduction through the pipe wall. This model
requires both the inner and outer diameter of the pipe/tube, the length of the pipe/tube, and
the thermal conductivity of the pipe/tube material. Note that as part of the implementation
of this model in EnergyPlus, flow within the piping/tubing is always assumed to be turbulent.
– MeanAirTemperature - The mean air temperature of the zone being controlled by this radiant
system.
– MeanRadiantTemperature - The mean radiant temperature of the zone being controlled by
this radiant system.
– OperativeTemperature - The operative temperature of the zone being controlled by the radint
system. Operative temperature for radiant system controls is the average of Mean Air Tem-
perature and Mean Radiant Temperature.
– OutdoorDryBulbTemperature - The outdoor dry-bulb temperature of the current outdoor en-
vironment.
– OutdoorWetBulbTemperature - The outdoor wet-bulb temperature of the current outdoor
environment.
– SurfaceFaceTemperature - This option allows the user to control the radiant system using the
inside face surface temperature of the radiant system (the inside surface temperature).
– SurfaceInteriorTemperature - This option will allow the user to control the radiant system
using a surface temperature that is calculated inside the radiant system. This point will be
defined by the Construction:InternalSource description for the system. In that input, the user
has the option to calculate a temperature at a particular point in the construction. The radiant
system will then use this information for controlling the slab not just producing temperatures
for outputting at that point. Users should consult the input for Field: Temperature Calculation
1634 CHAPTER 1. INPUT-OUTPUT REFERENCE
Requested After Layer Number for more information. Note that for the SurfaceFaceTemper-
ature and SurfaceInteriorTemperature the surface being used for control is the surface listed
above in the field for Surface Name. If the user enters a group of surfaces for that input, the
first surface in the radiant group is the surface for control purposes.
– RunningMeanOutdoorDryBulbTemperature - This option will allow the user to control the inlet
water temperature to the system as a function of the running mean outdoor air temperature.
The next field (Running Mean Outdoor Dry-Bulb Temperature Weighting Factor) will define
how this temperature is actually calculated within EnergyPlus.
If the user does not select a control type, MeanAirTemperature control is assumed by EnergyPlus.
See the throttling range and control temperature schedule fields below for more information on how
the setpoint temperature is established for this particular radiant system.
where:
Θrm is the current running mean outdoor dry-bulb temperature that is used to control the radiant
system
Θed−1 is the average outdoor dry-bulb temperature from the previous day
Θrm−1 is the running mean outdoor dry-bulb temperature from the previous day
α is the user defined weighting factor that is defined by this field. It controls the weighting of the
running mean outdoor dry-bulb temperature from the previous day and the average outdoor dry-
bulb temperature from the previous day for the purposes of calculating the running mean outdoor
dry-bulb temperature for the current day. The value for this weighting factor must be between zero
and 1.
– Off - EnergyPlus will not do anything other than produce a warning message when condensation
is predicted to occur. The program will simply continue on; no moisture will be removed from
the zone air and there will be no adjustment of the surface temperature as a result of the
condensation.
– SimpleOff - the program will predict cases where condensation will occur and shut-off the
radiant system to avoid this situation. With this option, the users also have the opportunity
to adjust when the system will shut down. This is specified with the next parameter (field:
Condensation Control Dewpoint Offset).
– VariableOff - the program will determine whether condensation is predicted for the flow rate
determined by the unit control scheme. If condensation is predicted, the unit makes one attempt
to avoid condensation by increasing the water inlet temperature to the system to match the dew-
point temperature modified by the condensation control dew-point offset (field: Condensation
Control Dewpoint Offset). For example, if a surface in the space is predicted to be 15°C and the
modified condensation dew-point temperature is 17°C, then the inlet water temperature to the
unit is reset to 17°C and the system is simulated again with this new inlet water temperature.
If this increased inlet water temperature does not result in condensation, then the simulation
continues using this operating condition for the system. If the increased inlet water temperature
still results in condensation, then the unit is turned off to avoid excessive iterations.
this parameter is zero, the radiant system will shut down or reduce the flow rate when the surface
temperature drops to the dew-point temperature or below. When this parameter is positive, the
radiant system will shut down or reduce the flow rate when the surface is the number of degrees
Celsius above the dew-point temperature. This allows some extra safety to avoid condensation.
When this parameter is negative, the radiant system will shut down or reduce the flow rate when
the surface temperature is the number of degrees Celsius below the dew-point temperature. While
not recommended, this strategy allows the user to simulate a situation where small amounts of
condensation are tolerable. The default value for this parameter is 1°C.
1.33.8.3 Outputs
1.33.8.3.14 Zone Radiant HVAC Pump Fluid Heat Gain Rate [W]
This field reports the rate at which heat is added to the fluid stream as it passes through the pump
in Watts. This heat is reflected in the radiant system inlet temperature which will be different from
the pump inlet temperature if this field has a non-zero value.
1.33. GROUP – RADIATIVE / CONVECTIVE UNITS 1639
1.33.8.3.15 Zone Radiant HVAC Pump Fluid Heat Gain Energy [J]
This field reports the amount of heat energy added to the fluid stream as it passes through the pump
in Joules. This heat is reflected in the radiant system inlet temperature which will be different from
the pump inlet temperature if this field has a non-zero value.
1.33.8.3.17 Zone Radiant HVAC Cooling Fluid Heat Transfer Energy [J]
The heat transfer energy for the cooling fluid connection, in Joules.
1.33.8.3.18 Zone Radiant HVAC Heating Fluid Heat Transfer Energy [J]
The heat transfer energy for the heating fluid connection, in Joules.
1.33.8.3.20 Zone Radiant HVAC Previous Day Running Mean Outdoor Dry-
Bulb Temperature [C]
This field reports the running mean outdoor dry-bulb temperature of the previous day in Celsius.
This value is used to calculate the running mean outdoor dry-bulb temperature when the user opts
to use the RunningMeanOutdoorDryBulbTemperature control type.
1.33.8.3.21 Zone Radiant HVAC Previous Day Average Outdoor Dry-Bulb Tem-
perature [C]
This field reports the average of the outdoor dry-bulb temperature for the previous day in Celsius.
This value is used to calculate the running mean outdoor dry-bulb temperature when the user opts
to use the RunningMeanOutdoorDryBulbTemperature control type.
1.33.9 ZoneHVAC:LowTemperatureRadiant:Electric
This low temperature radiant system (electric) is a component of zone equipment that is intended
to model any “radiant system” where electric resistance heating is used to supply energy (heat) to a
building surface (wall, ceiling, or floor). The component is controlled by the radiant system controls
that are defined in the syntax below and this control does not require the use of a zone thermostat
unless the unit is being autosized. Note also that because this unit does not require a thermostat
that in cases where no other systems are serving the zone in which this system resides that it will
1640 CHAPTER 1. INPUT-OUTPUT REFERENCE
use the heating equipment priority to determine which system will run first. If the radiant system is
serving a zone with forced air equipment, the radiant system will follow the priority order established
by the zone thermostat but will still base its response on the controls defined by the user for the
radiant system.
The control is accomplished by varying the electrical power supplied to the unit. This model covers
either a radiant panel system or wires embedded in entire walls, floors, or ceilings. It is not intended to
simulate high temperature electric or gas radiant heaters. Those devices will be handled by a separate
model (ref: ZoneHVAC:HighTemperatureRadiant) and different input syntax. Low temperature
radiant systems that use water flowing through tubes to provide heat to the system should also
be defined using separate input syntax (ref: ZoneHVAC:LowTemperatureRadiant:VariableFlow or
ZoneHVAC:LowTemperatureRadiant:ConstantFlow).
1.33.9.1 Inputs
– MeanAirTemperature - The mean air temperature of the zone being controlled by this radiant
system.
– MeanRadiantTemperature - The mean radiant temperature of the zone being controlled by
this radiant system.
– OperativeTemperature - The operative temperature of the zone being controlled by the radint
system. Operative temperature for radiant system controls is the average of Mean Air Tem-
perature and Mean Radiant Temperature.
– OutdoorDryBulbTemperature - The outdoor dry-bulb temperature of the current outdoor en-
vironment.
– OutdoorWetBulbTemperature - The outdoor wet-bulb temperature of the current outdoor
environment.
– SurfaceFaceTemperature - This option allows the user to control the radiant system using the
inside face surface temperature of the radiant system (the inside surface temperature).
– SurfaceInteriorTemperature - This option will allow the user to control the radiant system
using a surface temperature that is calculated inside the radiant system. This point will
be defined by the ConstructionProperty:InternalHeatSource description for the system. In
that input, the user has the option to calculate a temperature at a particular point in the
construction. The radiant system will then use this information for controlling the slab not
just producing temperatures for outputting at that point. Users should consult the input for
Field: Temperature Calculation Requested After Layer Number for more information. Note
that for the SurfaceFaceTemperature and SurfaceInteriorTemperature the surface being used
for control is the surface listed above in the field for Surface Name. If the user enters a group of
surfaces for that input, the first surface in the radiant group is the surface for control purposes.
If the user does not select a control type, MeanAirTemperature control is assumed by EnergyPlus.
See the throttling range and control temperature schedule fields below for more information on how
the setpoint temperature is established for this particular radiant system.
The Heating Setpoint Temperature Schedule specifies the “setpoint” temperature that is to be met.
This is used in conjunction with the Setpoint Type which defines whether the flow rate of the system
is at zero heat input or half heat input when the parameter defined by the Temperature Control
Type is equal to the setpoint temperature defined by the Heating Control Temperature Schedule.
See these other input parameters of this radiant system for more information on these different
parameters. Note that when the throttling range is set to zero that this approximates an on-off
system that is either fully on or totally off.
For clarity, here is an example of how the heat input fraction (of the unit capacity) to the system will
be set. In this example, it is assumed that heating control temperature setpoint is currently 15°C,
the heating throttling range is 2°C, and that the setpoint type is HalfFlowPower. The heat input
rate to the radiant system will be zero when the controlling temperature (MAT, MRT, Operative
Temperature, etc.; see control type field above) is at or above 16°C and the maximum heat input
when the controlling temperature is at or below 14°C. This represents a throttling range of 2°C
around the setpoint of 15°C. In between 14°C and 16°C, the heat input rate to the radiant system
is varied linearly from full heat input at a control temperature of 14°C to half heat input at 15°C
to zero heat input at 16°C. If the throttling range is changed to 0°C or on-off control, then the
system will be off above 15°C and on below 15°C. However, if the throttling range is kept at 2°C and
the setpoint type is changed to ZeroFlowPower, then the system will vary the heat input linearly
between zero for when the control temperature is at 15°C to full heat input at 13°C.
1.33.9.2 Outputs
1.33.10 ZoneHVAC:LowTemperatureRadiant:SurfaceGroup
A low temperature radiant system (hydronic or electric) may consist of multiple active surfaces that
serve to condition the space. Surfaces that act serially can be specified as multiple radiant systems
using the standard radiant system input described above. However, if the multiple surfaces act in
parallel, the Radiant System Surface Group input line is used to specify which surfaces are acting
in a coordinated fashion and how energy flow is split between the surfaces. This list of surfaces
(the name it is assigned) replaces the name of a single surface in the radiant system input described
above. Note that all of the surfaces within a single list do not need to be in the same zone so the
zones of these surfaces do not need to match the zone the radiant system is attempting to condition.
Keep in mind, however, that if the surfaces within a single surface group do not reside in the zone
that these zones must all have the same zone multipliers.
1.33.10.1 Inputs
1.33.11 ZoneHVAC:HighTemperatureRadiant
The high temperature radiant system (gas-fired or electric) is a component of zone equipment that
is intended to model any “high temperature” or “high intensity” radiant system where electric
resistance or gas-fired combustion heating is used to supply energy (heat) to a building occupants
directly as well as the building surfaces (wall, ceiling, or floor). The component is controlled by
the radiant system controls defined in the syntax below and this control does not require the use
of a zone thermostat unless the unit is being autosized. Note also that because this unit does not
require a thermostat that in cases where no other systems are serving the zone in which this system
resides that it will use the heating equipment priority to determine which system will run first. If
the radiant system is serving a zone with forced air equipment, the radiant system will follow the
priority order established by the zone thermostat but will still base its response on the controls
defined by the user for the radiant system.
The control is accomplished by varying the electrical power supplied to or gas consumed by the unit.
It is not intended to simulate low temperature electric or hydronic radiant systems. Those devices
will be handled by a separate model and different input syntax (ref: the low temperature systems
described elsewhere).
1.33.11.1 Inputs
– MeanAirTemperature
– MeanRadiantTemperature
– OperativeTemperature
– MeanAirTemperatureSetpoint
– MeanRadiantTemperatureSetpoint
1648 CHAPTER 1. INPUT-OUTPUT REFERENCE
– OperativeTemperatureSetpoint
If the user does not select a control type, OperativeTemperature control is assumed by EnergyPlus.
For the setpoint control strategies (those ending in Setpoint above), EnergyPlus will attempt to find
the correct heater output to meet the heating setpoint temperature (see below) through iteration and
interpolation. This will more closely match the operation of an actual thermostat, but it will require
significantly longer execution times. For more information on the standard piecewise linear control
algorithm used by the Mean Air Temperature, Mean Radiant Temperature, and Operative Temper-
ature control types (the “non-Setpoint” controls), see the throttling range and control temperature
schedule fields below for more information.
1.33.11.2 Outputs
1.33.12 ZoneHVAC:VentilatedSlab
Ventilated slab systems in general use outdoor air to “precool” slabs with colder nighttime air. This
method of precooling the thermal mass of a space can be very effective when nighttime temperatures
are low and the mass of the system is high enough to provide a significant amount of cooling potential
during the day to counteract internal heat gains within a zone. Nearly all ventilated slabs are simple
1.33. GROUP – RADIATIVE / CONVECTIVE UNITS 1651
systems such as that shown in the right side of Figure 1.162. The fan is shown in a blow through
position, but the model will allow either a blow or draw through configuration.
1.33.12.1 Inputs
This field contains a schedule name (ref: Schedule) that should contain values for the minimum
outdoor air used by the ventilated slab system for IAQ or other reasons. Note that if the ventilated
slab is scheduled off or if there is no load sensed in the zone that the system will not operate even
to achieve the minimum air fraction. However, if the system is operating, it will always bring
in at least this fraction of the minimum air flow rate (see minimum air flow rate field above). If
“FixedAmount” type is selected as the outdoor air control strategy, the actual outdoor air flow
rate will be this number multiplied by the minimum outdoor air flow rate in the field above. The
ventilated slab will automatically set the maximum and minimum outdoor air schedule to be equal
by ignoring the maximum outdoor air schedule.
– SlabOnly
– SlabAndZone
– SeriesSlabs
In the SlabOnly, the ventilation air is sent to the slab only and does not enter the zone. In
the SlabAndZone, the air first enters the slab and then is delivered to the zone before
returning to the system. With the SeriesSlabs option, the user specifies a list of slabs (Zone-
HVAC:VentilatedSlab:SlabGroup). This list determines the order of slabs through which the air
passes. In this option, air is not delivered to any zone.
1654 CHAPTER 1. INPUT-OUTPUT REFERENCE
– MeanAirTemperature
– MeanRadiantTemperature
– OperativeTemperature
– OutdoorDryBulbTemperature
– OutdoorWetBulbTemperature
– SurfaceTemperature
– ZoneAirDewPointTemperature
If the user does not select a control type, MeanAirTemperature control is assumed by EnergyPlus.
See the control temperature schedule fields below for more information.
– None
– Heating
– Cooling
– HeatingAndCooling
If None is selected, the ventilated slab does not have any coils, and any other input will be ignored. If
either Heating or Cooling is selected, only a heating or cooling coil, respectively, is present. Thus,
only four more inputs will be expected. If HeatingAndCooling is selected, both heating and
cooling coil input must be entered, and the ventilated slab will have both a heating and a cooling
coil.
ZoneHVAC:VentilatedSlab ,
Zone4VentSlab , !- Name
VentSlabAvailability , !- Availability Schedule Name
SPACE4 -1, !- Zone Name
F4 -1, !- Surface Name or Radiant Surface Group Name
0.84, !- Maximum Air Flow Rate {m3/s}
VariablePercent , !- Outdoor Air Control Type
0.168 , !- Minimum Outdoor Air Flow Rate {m3/s}
U2MinOASched , !- Minimum Outdoor Air Schedule Name
0.84, !- Maximum Outdoor Air Flow Rate {m3/s}
VentSlabMaxOA , !- Maximum Outdoor Air Fraction or Temperature Schedule Name
SlabAndZone , !- System Configuration Type
0.050 , !- Hollow Core Inside Diameter {m}
15.0, !- Hollow Core Length {m}
50.0, !- Number of Cores
MeanRadiantTemperature , !- Temperature Control Type
VentSlabHotHighAir , !- Heating High Air Temperature Schedule Name
VentSlabHotLowAir , !- Heating Low Air Temperature Schedule Name
VentSlabHotHighControl , !- Heating High Control Temperature Schedule Name
VentSlabHotLowControl , !- Heating Low Control Temperature Schedule Name
VentSlabCoolHighAir , !- Cooling High Air Temperature Schedule Name
VentSlabCoolLowAir , !- Cooling Low Air Temperature Schedule Name
VentSlabCoolHighControl , !- Cooling High Control Temperature Schedule Name
VentSlabCoolLowControl , !- Cooling Low Control Temperature Schedule Name
Zone4VentSlabReturnAirNode , !- Return Air Node Name
Zone4VentslabSlabInNode , !- Slab In Node Name
Zone4Inlets , !-Zone Supply Air Node Name
Zone4VentSlabOAInNode , !- Outdoor Air Node Name
Zone4VentSlabExhNode , !- Relief Air Node Name
Zone4VentSlabOAMixerOutletNode , !-Outdoor Air Mixer Outlet Node Name
Zone4VentSlabFanOutletNode , !- Fan Outlet Node Name
Zone4VentSlabFan , !- Fan Name
HeatingAndCooling , !- Coil Option Type
Coil:Heating:Electric , !- Heating Coil Object Type
Zone4VentSlabHeatingCoil ,!- Heating Coil Name
, !- Hot Water or Steam Inlet Node Name
Coil:Cooling:Water , !- Cooling Coil Object Type
1.33. GROUP – RADIATIVE / CONVECTIVE UNITS 1659
1.33.12.2 Outputs
availability status are described in the section ‘Group – System Availability Managers’. The control
status outputs are represented using integers 0 through 3. These integers represent NoAction (0),
ForceOff (1), CycleOn (2), and CycleOnZoneFansOnly (3). Since the status output is averaged, the
output result may not correspond to the values described here when output variable frequencies
other than detailed are used. Use the “detailed” reporting frequency (Ref. Output:Variable object)
to view the availability status at each simulation timestep.
1.33.13 ZoneHVAC:VentilatedSlab:SlabGroup
A ventilated slab system may consist of multiple active slabs that are serving to condition the zone.
Slabs that act serially can be specified as multiple radiant systems using the standard ventilated slab
input described above. This list of surfaces (the name it is assigned) replcaces the name of a single
surface in the ventilated slab system input described above.
1.33.13.1 Inputs
ZoneHVAC:VentilatedSlab:SlabGroup ,
Z125 , !- Name
SPACE1 -1, !- Zone 1 Name
C1 -1, !- Surface 1 Name
0.05, !- Core Diameter for Surface 1
30, !- Core Length for Surface 1
20, !- Core Numbers for Surface 1
Z1VentslabIn , !- Slab In Node Name for Surface 1
Z1VentSlabout , !- Slab Outlet Node Name for Surface 1
SPACE2 -1, !- Zone 2 Name
C2 -1, !- Surface 2 Name
0.05, !- Core Diameter for Surface 2
15, !- Core Length for Surface 2
20, !- Core Numbers for Surface 2
Z2VentSlabIn , !- Slab In Node Name for Surface 2
Z2VentSlabOut , !- Slab Outlet Node Name for Surface 2
SPACE5 -1, !- Zone 3 Name
C5 -1, !- Surface 3 Name
0.05, !- Core Diameter for Surface 3
30, !- Core Length for Surface 3
20, !- Core Numbers for Surface 3
Z5VentSlabIn , !- Slab In Node Name for Surface 3
Z5VentSlabOut; !- Slab Outlet Node Name for Surface 3
The second approach requires more input objects but also allows the user to model more complex
systems. This detailed approach must be used whenever loads are transferred from one system to
another, such as with secondary loops, cascade condensers, or mechanical subcoolers. Again lists are
used to enter multiple load or compressor names.
For the detailed approach, the input objects needed are:
Output variables are also available to describe the total heat exchange between all refrigeration
objects and the zones containing these objects. These variables are described at the end of this
section after all the refrigeration objects.
1.34.1 Refrigeration:CompressorRack
The refrigeration compressor rack object works in conjunction with the refrigeration case and walkin
objects (Ref. Refrigeration:Case and Refrigeration:WalkIn) to simulate the performance of a re-
frigerated case system. This object models the electric consumption of the rack compressors and
the condenser fans. Heat removed from the refrigerated cases, walkins, and compressor/condenser
fan heat can be rejected either outdoors or to a zone. Compressor rack waste heat can also be
reclaimed for use by an optional air- or water-heating coil (Ref. Coil:Heating:Desuperheater and
Coil:WaterHeating:Desuperheater).
If heat is rejected outdoors, condenser cooling can either be accomplished by direct air flow, evap-
orative water cooling, or a by water-cooled condenser with appropriate plant loop piping. With
evaporative cooling, water is sprayed through the air stream to effectively lower the air temperature
1.34. GROUP – REFRIGERATION 1665
experienced by the condenser coil as a result of water evaporation. The use of a water-cooled con-
denser requires the definition of a plant loop to supply cooling to the condenser. Waste heat can
be reclaimed and stored using a water storage device.
The inputs for the compressor rack object include a name, the heat rejection location, the compressor
rack coefficient of performance (COP) at design conditions, the design condenser fan power, and the
type of condenser cooling. The model requires two curve objects to describe performance at off-design
conditions. If the condenser is water-cooled, the inlet and outlet node names as well as the water
outlet temperature schedule name are required. If the condenser has evaporative cooling, additional
inputs for evaporative condenser effectiveness, condenser air flow rate, basin heater parameters,
water pump power, water source, and an evaporative cooling availability schedule are available. The
names of refrigerated cases and walkins connected to the compressor rack are the final inputs to the
model.
1.34.1.1 Inputs
The name of the curve object defining the change in compressor rack COP as a function of the
temperature of air entering the condenser. The curve object will be evaluated using the zone air
dry-bulb temperature when rack heat rejection location equals “Zone” and the outdoor air dry-bulb
temperature when rack heat rejection location equals “Outdoors” and the condenser type is air-
cooled. As explained below, if the condenser is cooled by evaporative or water loop cooling, the
1666 CHAPTER 1. INPUT-OUTPUT REFERENCE
curve object is evaluated using an effective temperature. The output from this curve is multiplied by
the design compressor rack COP to yield the actual COP at the specific air temperature entering the
condenser. This curve must be cubic or quadratic (Curve:Cubic or Curve:Quadratic), and should
be normalized to 1.0 at the condenser entering air temperature at which the design compressor rack
COP occurs. This curve should represent the compressor rack COP corresponding to the lowest
evaporating temperature of any case served by the rack.
When the condenser type is “WaterCooled”, and when the water-cooled loop flow type is “Variable
Flow”, the name of a schedule (Ref: Schedule) that defines the desired condenser water outlet
temperature must be provided. The schedule may define an outlet temperature that varies through
time.
When the condenser type is “WaterCooled”, this field specifies the minimum allowed water temper-
ature in degrees C entering the compressor rack condenser. The default value is 10 degrees C. Refer
to additional discussion in the Engineering Reference.
climates, evaporative cooling is periodically discontinued and the basin sumps drained to avoid freez-
ing. In these times, the condenser runs as a typical dry air cooled condenser, and related evaporative
cooling systems (e.g., water pump, basin heaters) do not operate. Use of this optional schedule
permits modeling of planned, seasonal interruptions of evaporative cooling. All schedule values must
be greater than or equal to zero. Typically, an ON/OFF schedule type is used with values being
either 0 or 1. A schedule value of 1 indicates that evaporative cooling is available during the defined
time period, and a value of 0 denotes that evaporative cooling is not available during the defined
time period. If the schedule name is omitted (blank) and Condenser Type = “Evap Cooled”, then
the model assumes that evaporative cooling of the condenser is available for the entire simulation
period.
where:
Tef f ective = effective dry-bulb temperature of air entering the condenser cooling coil (°C)
Towb = outdoor air wet-bulb temperature (°C)
Todb = outdoor air dry-bulb temperature (°C)
ε = evaporative condenser effectiveness.
The resulting condenser inlet air temperature is used by the Compressor Rack COP as a Function of
Temperature Curve and the Condenser Fan Power as a Function of Temperature Curve. The default
value for this field is 0.9, although valid entries can range from 0.0 to 1.0.
If the two function-of-temperature curves (i.e., Compressor Rack COP as a Function of Tempera-
ture Curve and Condenser Fan Power as a Function of Temperature Curve) are based on wet-bulb
temperature rather than dry-bulb temperature, the evaporative condenser effectiveness should be
set to 1.0 for consistency.
heater set point temperature and the dry-bulb temperature of the condenser coil inlet air. The basin
heater only operates when the condenser fan is off (i.e., no compressor heat rejection). The basin
heater capacity must be greater than or equal to zero, with a default value of 200 W/K if this field
is left blank.
Refrigeration:CompressorRack ,
MediumTempRack , !- Name
Outdoors , !- Heat Rejection Location
1.7, !- Design Compressor Rack COP {W/W}
RackCOPfTCurve , !- Compressor Rack COP as a Function of Temperature Curve Name
1025.0 , !- Design Condenser Fan Power {W}
RackCondFanCurve , !- Condenser Fan Power as a Function of Temperature Curve Name
WaterCooled , !- Condenser Type
Condenser Inlet Node , !- Water -cooled Condenser Inlet Node Name
Condenser Outlet Node , !- Water -cooled Condenser Outlet Node Name
VariableFlow , !- Water -cooled Loop Flow Type
Cond Outlet Temp Sch , !- Water -cooled Condenser Outlet Temperature Schedule Name
, !- Water -cooled Condenser Design Flow Rate {m3/s}
0.003 , !- Water -cooled Condenser Maximum Flow Rate {m3/s}
55, !- Water -cooled Condenser Maximum Water Outlet Temperature {C}
, !- Water -cooled Condenser Minimum Water Inlet Temperature {C}
, !- Evaporative Condenser Availability Schedule Name
, !- Evaporative Condenser Effectiveness {dimensionless}
, !- Evaporative Condenser Air Volume Flow Rate {m3/s}
, !- Basin Heater Capacity {W/K}
, !- Basin Heater Set Point Temperature {C}
, !- Design Evaporative Condenser Water Pump Power {W}
, !- Evaporative Water Supply Tank Name
, !- Condenser Air Inlet Node Name
, !- End -Use Subcategory
MediumTempCaseList; !- Refrigeration Case Name or WalkIn Name or CaseAndWalkInList Name
1.34.1.2 Outputs
– System,Average, Refrigeration Compressor Rack Condenser Refrigerant Mass Flow Rate [kg/s]
– System,Average, Refrigeration Compressor Rack Condenser Heat Transfer Rate [W]
– System,Sum, Refrigeration Compressor Rack Condenser Heat Transfer Energy [J]
– HVAC,Average, Refrigeration Air Chiller Compressor Rack Evaporative Condenser Pump Elec-
tricity Rate [W]
1672 CHAPTER 1. INPUT-OUTPUT REFERENCE
– HVAC,Sum, Refrigeration Air Chiller Compressor Rack Evaporative Condenser Pump Elec-
tricity Energy [J]
– HVAC,Average, Refrigeration Air Chiller Compressor Rack Evaporative Condenser Basin
Heater Electricity Rate [W]
– HVAC,Sum, Refrigeration Air Chiller Compressor Rack Electric PowerRefrigeration Air Chiller
Compressor Rack Evaporative Condenser Basin Heater Electricity Energy [J]
– HVAC,Average, Refrigeration Air Chiller Compressor Rack Evaporative Condenser Water Vol-
ume Flow Rate [m3/s]
– HVAC,Sum, Refrigeration Air Chiller Compressor Rack Evaporative Condenser Water Volume
[m3]
– HVAC,Average, Refrigeration Air Chiller Compressor Rack Zone Sensible Heating Rate [W]
– HVAC,Sum,Refrigeration Air Chiller Compressor Rack Zone Sensible Heating Energy [J]
– HVAC,Average, Refrigeration Air Chiller Compressor Rack Return Air Sensible Heating Rate
[W]
– HVAC,Sum,Refrigeration Air Chiller Compressor Rack Return Air Sensible Heating Energy [J]
When condenser type is Water Cooled, this is the total heat energy flowing across the condenser for
the timestep being reported.
This output is the electric input to the rack condenser fan(s) in Watts.
This is the electricity consumption of the rack condenser fan(s) in Joules for the timestep being
reported. This output is also added to a meter with Resource Type = Electricity, End Use Key =
Refrigeration, Group Key = Plant (Ref. Output:Meter objects).
1.34.1.2.29 Refrigeration Air Chiller Compressor Rack Total Heat Transfer Rate
[W]
This output is the total heat transfer rate of the refrigeration compressor rack in Watts. It is the
sum of all of the heat transfer rates for the refrigerated cases and walk-ins that are connected to this
rack. This value does not include compressor or condenser fan heat.
1.34.1.2.30 Refrigeration Air Chiller Compressor Rack Total Heat Transfer En-
ergy [J]
This is the total heat transfer of the refrigeration compressor rack in Joules for the timestep being
reported. This output is also added to a meter with Resource Type = EnergyTransfer, End Use Key
= Refrigeration, Group Key = Plant (Ref. Output:Meter objects).
1676 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.34.2 Refrigeration:Case
The Refrigeration Case object works in conjunction with a compressor rack, a refrigeration sys-
tem, or a secondary loop object (Refrigeration:CompressorRack, Refrigeration:System, or Refriger-
ation:SecondarySystem) to simulate the performance of a refrigerated case system. The refrigerated
case model uses performance information at rated conditions along with performance curves for la-
tent case credits and defrost heat load to determine performance at off-rated conditions. Energy use
for lights, fans and anti-sweat heaters is modeled based on inputs for nominal power, schedules, and
control type. The refrigerated case model accounts for the sensible and latent heat exchange with
the surrounding environment (termed “case credits”) which impacts the temperature and humidity
in the zone where the case is located.
A dataset has been provided containing refrigerated case input data for a large number
of refrigerated cases from multiple manufacturers. See RefrigerationCases.idf.
The Refrigeration Case object inputs include a case name, an availability schedule name, the zone
name for the location of the case, and the temperature and relative humidity of the ambient (zone)
air surrounding the refrigerated case at the rating conditions for case performance. Additional inputs
include the total cooling capacity, latent heat ratio, and run time fraction of the refrigerated case at
rated conditions. The case length and operating temperature (average temperature of air/products
within the case) must also be specified.
The refrigerated case model requires two curves to describe performance at off-rated conditions (i.e.,
at different zone temperature and humidity levels): the latent case credit curve and the defrost energy
correction curve. The user must enter cubic performance curves with the independent variable being
user selectable (case temperature, zone relative humidity, or zone dewpoint temperature).
The user can select from eight case defrost types, with additional inputs being required depending
on the type selected. The user must enter a defrost schedule (unless Case Defrost Type = None),
and an optional defrost drip-down schedule can be specified to allow additional time for melted frost
to drain from the cooling coil following the regular defrost period.
1678 CHAPTER 1. INPUT-OUTPUT REFERENCE
Inputs are required for case fans, lights, and anti-sweat heaters. Case lighting can be controlled by
the user through entering a schedule. The case fans operate whenever the cooling coil is operating
and during defrost periods for certain case defrost types. Anti-sweat heater power can be controlled
by several methods which are user selectable. The model assumes that the fans are contained within
the thermal envelope of the case and provide a direct heat load on the case cooling coil. For lighting
and anti-sweat heaters, the user can specify the fraction of their respective heat loads that directly
impact the case cooling coil (with the remainder of their heat load impacting the surrounding zone
air).
The user has the option of specifying a case restocking schedule and a schedule for modifying the
case credits if needed. Finally, the user can specify the under case HVAC return air fraction which
determines the portion of the case credits that directly impact the HVAC return air conditions (with
the remainder of the case credits impacting the zone sensible and latent loads).
1.34.2.1 Inputs
– CaseTemperatureMethod
This method defines the variation in latent case credits as a cubic function of Case Operating Tem-
perature. The result from the cubic curve is multiplied by the difference between the rated ambient
relative humidity and the actual zone relative humidity, and one minus this value is multiplied by
the Rated LHR to give the operating LHR at the actual zone humidity condition. (Representative
1680 CHAPTER 1. INPUT-OUTPUT REFERENCE
cooefficient values for single-shelf horizontal and multi-shelf vertical display cases are given in the
EnergyPlus Engineering Reference.)
– RelativeHumidityMethod
This method defines the variation in latent case credits as a cubic function of ambient (zone) air
relative humidity.
– DewpointMethod
This method defines the variation in latent case credits as a cubic function of ambient (zone) air
dewpoint temperature.
The default curve type is the Case Temperature Method. Refer to the Engineering Reference for
further information on how latent case credits are modeled.
Installed Case Lighting Power per Unit Length to be modeled for each timestep of the simulation
period. The entered value for this field must be greater than or equal to zero, and the value is set
equal to the standard case lighting power if the field is blank.
the defrost drip-down period is over. The refrigerated case manufacturer typically provides this
information with the product literature.
Each defrost drip-down period specified in this schedule should start at the same time as the cor-
responding defrost period specified in the schedule for Case Defrost Schedule, and the drip-down
schedule defrost period should always be longer than or equal to the length of the defrost schedule
time period. For example, if the case defrost schedule contains a defrost period from 7:00 to 7:15,
you would specify a case defrost drip-down period from 7:00 to 7:20 if you wanted to model a 5
minute condensate drip-down period after the regular defrost period. If no drip-down schedule is
entered, then the case defrost schedule (specified for the previous input field) will be used. The use
of Compact Schedules (ref. Schedules) are ideal for this purpose.
– None
This choice specifies that a defrost energy correction curve will not be used.
– CaseTemperatureMethod
This method defines the variation in defrost energy as a cubic function of Case Operating Temper-
ature. The result from the cubic curve is multiplied by the difference between the rated ambient
relative humidity and the actual zone relative humidity, and one minus this value is multiplied by
the Case Defrost Power to give the (average) operating defrost power at the actual zone humid-
ity condition. (Representative cooefficient values for single-shelf horizontal and multi-shelf vertical
display cases are given in the EnergyPlus Engineering Reference.)
– RelativeHumidityMethod
This method defines the variation in defrost energy as a cubic function of ambient (zone) air relative
humidity.
– DewpointMethod
This method defines the variation in defrost energy as a cubic function of ambient (zone) air dewpoint
temperature.
The default curve type is None. The methods described here (e.g. Case Temperature, Relative
Humidity, and Dewpoint) are applicable only to Electric with Temperature Termination, Hot-Gas
with Temperature Termination, and Hot-Brine with Temperature Termination case defrost types.
Refer to the Engineering Reference for further information on how the defrost energy correction
types are modeled.
1684 CHAPTER 1. INPUT-OUTPUT REFERENCE
The value of this numeric field is used only with the detailed refrigeration system and is not read
for the compressor-rack system. For the refrigeration system, it is used to evaluate compressor
performance and is also used when the evaporator pressure and temperature are allowed to float
at loads less than the design load. If the case is cooled by a secondary system (ref: Refrigera-
tion:SecondarySystem), this value is the brine inlet temperature. The minimum value is -70C and
the maximum value is 40C. The default value is 5C less than the case temperature.
1.34. GROUP – REFRIGERATION 1685
Refrigeration:Case ,
Multi -Deck Dairy/Deli Merchandiser with Synergy -E, !- Name [Based on Hill Phoenix 6DMLH -NRG]
, !- Availability Schedule [Used to turn case on/off including all power draws (ie fans ,
lights , etc)]
UserProvideZoneName , !- Zone Name [Location of Fixture]
23.89 , !- Rated Ambient Temperature {C} [75øF]
55, !- Rated Ambient Relative Humidity {percent}
1394, !- Rated Total Cooling Capacity per Unit length {W/m} [1 ,450 Btu/hr/ft = 11 ,600
Btu/hr]
0.30, !- Rated Latent Heat Ratio [ Rated Latent Capacity]
0.85, !- Rated Runtime Fraction
2.4, !- Case Length {m} [8 ft]
3.33, !- Case Operating Temperature {C} [38øF]
CaseTemperatureMethod , !- Latent Case Credit Curve Type
Multi_Shelf_Vertical_Latent_Case_Credit_Curve , !- Latent Case Credit Curve Name
27.3, !- Standard Case Fan Power per Unit Length {W/m} [8.3 W/ft]
27.3, !- Operating Case Fan Power per Unit Length {W/m} [8.3 W/ft = 67 W]
0.0, !- Standard Case Lighting Power per Unit Length {W/m} [0.0 W/ft]
114.8 , !- Installed Case Lighting Power per Unit Length {W/m} [35.0 W/ft =
280 W]
, !- Case Lighting Schedule Name
1.0, !- Fraction Of Lighting Energy To Case
0.0, !- Case Anti -Sweat Heater Power per Unit Length {W/m} [0.0 W/ft = 0 W]
, !- Minimum Anti -Sweat Heater Power per Unit Length {W/m} []
None , !- Anti -Sweat Heater Control Type
, !- Humidity At Zero Anti -Sweat Heater Energy {%}
, !- Case Height {m} []
1.0, !- Fraction of Anti -Sweat Heater Energy To Case
0.0, !- Case Defrost Power per Unit Length {W/m} [0.0 W/ft 0 W]
Off Cycle , !- Case Defrost Type
UserProvideDefSched6PerDay45MinEa , !- Case Defrost Schedule Name
UserProvideDefSched4PerDay42MinEa , !- Case Defrost Drip -Down Schedule
CaseTemperatureMethod , !- Defrost Energy Correction Curve Type
Multi Shelf Vertical , !- Defrost Energy Correction Curve Name
0.00, !- Under Case HVAC Return Air Fraction
, !- Refrigerated Case Restocking Schedule Name [Not modeling any
restocking]
, !- Case Credit Fraction Schedule Name
-3.33, !- Design Evaporator Temperature or Brine Inlet Temperature {C} [26øF]
; !- Average Refrigerant Charge Inventory {kg/m} [ = ]
1.34.2.2 Outputs
then this latent energy is actually provided to the zone air instead (even though a non-zero value is
reported here).
1.34.3 Refrigeration:CaseAndWalkInList
This object provides a list of all the refrigerated cases and/or walk in coolers cooled by a single refrig-
eration system (ref: Refrigeraion:CompressorRack and Refrigeration:System). This list is extensible.
Note that the names of all cases, walk-ins,air chillers, and caseandwalkinlists must be unique. That
is, you cannot give a list the same name as one of the cases. Similarly, a walkin cannot have the
same name as a case.This list may contain a combination of case and walk-in names OR a list of air
chiller names. Air chillers may not be included in any list that also includes cases or walk-ins.
1.34.3.1 Inputs
Refrigeration:CaseAndWalkInList ,
MediumTempCaselist , !- Name
UprightDairyCase , !- Refrigeration Case or WalkIn Name \#1
LunchmeatCase , !- Refrigeration Case or WalkIn Name \#2
MeatWalkIn , !- Refrigeration Case or WalkIn Name \#3
DeliCaseOne; !- Refrigeration Case or WalkIn Name \#4
1.34.4 Refrigeration:WalkIn
The Refrigeration WalkIn object works in conjunction with a compressor rack, a refrigeration sys-
tem, or a refrigeration secondary system object (Ref. Refrigeration:CompressorRack, Refrigera-
tion:System, or Refrigeration:SecondarySystem) to simulate the performance of a walk-in cooler.
The walk-in cooler model uses information at rated conditions along with input descriptions for heat
transfer surfaces facing multiple zones to determine performance. Energy use for lights, fans, and
1.34. GROUP – REFRIGERATION 1691
floor and anti-sweat heaters is modeled based on inputs for nominal power, schedules, and control
type. The walk-in cooler model accounts for the sensible and latent heat exchange with the sur-
rounding environment (termed “case credits”) which impacts the temperature and humidity in each
zone adjacent to the walk-in.
The walk-in cooler object inputs include a name, an availability schedule name, the rated cooling
capacity, the rated operating temperature, the rated cooling source temperature, the rated total
heating power and heating power schedule, the rated fan and lighting power and schedules, defrost
type, defrost control type, defrost schedule name, drip-down schedule name, defrost power, the
portion of the defrost energy used to melt ice (only for temperature termination control type),
restocking schedule, refrigerant inventory, and the floor area and U-value.
For each zone adjacent to the walk-in, the user must input the zone name and the insulated surface
area and U-value facing that zone. The user must also specify, for two types of doors, the door area,
height, U-value, door opening schedule name, and any door opening protection.
Under case HVAC return air fraction, available for refrigerated cases, is not available for walk-in
coolers.
A unique user-assigned name for an instance of a refrigerated walk-in. Any reference to this walk-in
by another object will use this name.
The name of the schedule (ref: Schedule) that denotes whether the walk in can operate during a
given time period. A schedule value greater than 0 (maximum schedule value of 1.0 is typically used)
indicates that the walkin will operate during a given time period. A value equal to 0 denotes that
the case does not operate (everything is OFF: refrigeration, fans, lights, anti-sweat, etc.). Typically
the walkin will operate throughout the day (i.e., the schedule will contain 1 for all time periods);
however, walkins require maintenance and/or cleaning and this can be modeled accordingly using
this schedule if desired. If this field is left blank, the default schedule has a value of 1 for all time
periods.
The total, full load cooling capacity (sensible plus latent) in watts (W) at rated conditions The value
entered for this field must be greater than zero, with no default value.
The rated average temperature of the air and products within the walk-in cooler in ˚C. The entered
value for this field must be less than 20˚C. There is no default value.
For a DX evaporator coil, enter the saturated evaporating temperature in ˚C. For a fluid coil, enter
the fluid coil entrance temperature in ˚C. There is no default value. This number is used, with
1692 CHAPTER 1. INPUT-OUTPUT REFERENCE
temperatures for other refrigeration loads on any one system, to set that system’s minimum suction
pressure or minimum circulating fluid temperature. (This value is not used if the walkin is cooled
by a compressor rack object.)
The total heating power in watts including all anti-sweat, door, drip-pan, and floor heaters (W).
This value is required and has no default value.
The name of the schedule (ref: Schedule) that denotes the fraction of heater power that operates
during a given time period. A schedule value of zero denotes that all heaters are off. A schedule
value greater than 0 indicates that some portion of the total heater power will operate during that
time period (maximum schedule value of 1.0 means all heaters are fully on). For example, if door
and floor heaters represent 50% of the total heater power and are on all the time, the minimum
schedule value would be 0.5. If anti-sweat heaters represent 40% of the total heater power and are
only on during certain hours, the schedule value during those hours would be increased by 0.4. If
this field is left blank, the default schedule has a value of 1 for all time periods.
The cooling coil fan power in watts (W). This value has a default value of 375W. This fan is assumed
to run continuously except during electric, hot brine, or hot gas defrost periods.
The circulation fan power in watts (W). This value has a default value of 0 W. This fan is assumed
to run continuously.
The total lighting power in watts including both display and task lighting (W). This value is required
and has no default value.
The name of the schedule (ref: Schedule) that denotes the fraction of walk-in lights that operate
during a given time period. A schedule value greater than 0 indicates that the lights will operate
during that time period (maximum schedule value of 1.0 means lights are fully on). A schedule value
of zero denotes that the lights are off. If this field is left blank, the default schedule has a value of 1
for all time periods.
1.34. GROUP – REFRIGERATION 1693
The type of defrost used for this walk-in. Valid choices are None, Off-Cycle, HotFluid, and Electric.
The default defrost type is Electric if the field is blank. HotFluid includes both hot gas and hot
brine defrost systems. Refer to the Engineering Reference for further information on how the different
defrost types are modeled.
The type of defrost control used for this walkin. Valid choices are TimeSchedule and TemperatureTer-
mination. The default is TimeSchedule if the field is blank. Refer to the Engineering Reference for
further information on how the different defrost controls are modeled.
The name of the schedule (ref: Schedule) that denotes when the walkin requires defrosting. A
schedule value of 1.0 indicates that defrost will be on during a given time period if the defrost
control type is “TimeSchedule”. For the TemperatureTermination defrost control type, the defrost
will start with the schedule value changes from 0 to 1, but will end when the ice is melted. A
value equal to 0 denotes that the defrost is off. Defrost schedules normally repeat the duration
and number of defrost cycles for each day of the year. The walkin manufacturer typically provides
this information with the product literature. If TemperatureTermination control type is used, the
defrost schedule is used for the defrost cycle start time and the defrost cycle end time is not allowed
to extend beyond the scheduled off time. The use of Compact Schedules (ref. Schedules) are ideal
for this purpose.
The name of the schedule (ref: Schedule) that denotes whether the walkin requires additional time
for draining condensate after the defrost period. A schedule value of 1.0 indicates that the defrost
drip-down period is on during a given time period. A value equal to 0 denotes that the defrost drip-
down period is over. The walkin manufacturer typically provides this information with the product
literature.
Each defrost drip-down period specified in this schedule should start at the same time as the corre-
sponding defrost period specified in the schedule for Defrost Schedule, and the drip-down schedule
defrost period should always be longer than or equal to the length of the defrost schedule time period.
For example, if the defrost schedule contains a defrost period from 7:00 to 7:15, you would specify
a case defrost drip-down period from 7:00 to 7:20 if you wanted to model a 5 minute condensate
drip-down period after the regular defrost period. If no drip-down schedule is entered, then the
defrost schedule (specified for the previous input field) will be used. The use of Compact Schedules
(ref. Schedules) are ideal for this purpose.
The defrost power in watts. This input is required for hot-fluid (hot gas or hot brine), or electric
defrost types. Walkin manufacturers do not typically provide information on the heat input for hot
gas and hot brine defrost. Information provided for electric defrost power can be substituted here
1694 CHAPTER 1. INPUT-OUTPUT REFERENCE
for walkins using hot-gas or hot-brine defrost if other information is not available. Only electric
Defrost Types consume electricity during the defrost period. The entered value for this field must
be greater than or equal to zero.
When cooling coils go through a defrost cycle, only a portion of the defrost energy is actually used to
melt the ice. The rest of the defrost energy goes to increasing the temperature of the coils themselves
and to the walkin environment. The Temperature Termination defrost control type calculates the
end of the defrost cycle that corresponds to melting all the ice. Therefore, the user must input this
fractional value. The default value is 0.7 for electric defrost and 0.3 for hot fluid defrost. Refer to the
Engineering Reference for further information on how the defrost energy control types are modeled.
The name of the schedule (ref: Schedule) that denotes whether the walkin is being restocked with
product. The schedule should contain values in units of Watts (note this is different from the
restocking schedule values for cases that are entered per unit length). This field can be used to denote
the additional load imposed on the walkin from stocking the walkin with product that is warmer than
the walkin temperature. This information is difficult to find and may required additional research
for proper modeling; however, this schedule is available for this purpose if desired. If restocking of
the refrigerated walkin will not be simulated, enter a schedule with values of zero for all time periods
or leave this field blank.
The value of this optional field is the refrigerant inventory present in the walkin during ordinary
operation. The value is used to produce an estimate of the total refrigerant present in the refrigeration
system. The value is entered in kg.
The floor area in square meters. This value is required and has no default value.
The floor themal transmittance (in W/m2 -K). This value has a default value of 0.3154. (This
corresponds to R18 in Archaic American Insulation Units. To convert other R-values to thermal
transmittance, divide 5.678 by the R-value. For example, R15 is 0.3785 W/m2 -K and R5 is 1.136
W/m2 -K.)
THE REMAINING 12 FIELDS FOR THE WALK-IN COOLER MUST BE RE-
PEATED FOR EACH ZONE WHICH IS IN CONTACT WITH A WALK-IN WALL,
CEILING, OR DOOR. This object is extensible, so additional fields of this type can be
added to the end of this object by repeating the last 12 fields in the object.
1.34. GROUP – REFRIGERATION 1695
The name of a zone adjoining the walkin. The walkin will impact the air heat balance in
this zone. This zone must represent a conditioned space, that is, it must appear in a Zone-
HVAC:EquipmentConnections object.
The total surface area (walls and ceilings) facing this particular zone in square meters. This value
is required and has no default value.
The surface (walls and ceilings) themal transmittance (in W/m2 -K). This value has a default value of
0.3154. (This corresponds to R18 in Archaic American Insulation Units. To convert other R-values
to thermal transmittance, divide 5.678 by the R-value. For example, R15 is 0.3785 W/m2 -K and
R5 is 1.136 W/m2 -K.)
The total area of glass doors facing this particular zone in square meters. The default is 0.0.
The glass door themal transmittance (in W/m2 -K). This field has a default value of 1.136. (This
corresponds to R5 in Archaic American Insulation Units.)
1.34.4.28 Field: Glass Reach In Door Opening Schedule Name Facing Zone <x>
The name of the schedule (ref: Schedule) that denotes the fraction of time glass doors are open
during a given time period. The schedule values should be between 0 and 1.0. If no schedule is
specified, the doors are assumed to be open 5% of the time (corresponding to a schedule value of
0.05).
The total area of stock doors facing this particular zone in square meters. The default is 0.0.
The stocking door themal transmittance (in W/m2 -K). This value has a default value of 0.3785.
(This corresponds to R15 in Archaic American Insulation Units.)
1.34.4.32 Field: Stocking Door Opening Schedule Name Facing Zone <x>
The name of the schedule (ref: Schedule) that denotes the fraction of time stocking doors are open
during a given time period. The schedule values should be between 0 and 1.0. If no schedule is
specified, the doors are assumed to be open 5% of the time (corresponding to a schedule value of
0.05).
1.34.4.33 Field: Stocking Door Opening Protection Type Facing Zone <x>
The type of stocking door opening protection used for this walkin. Valid choices are None, AirCur-
tain, and StripCurtain. The default is AirCurtain if the field is blank. Use the type, StripCurtain,
for both hanging strips and airlock vestibules. Refer to the Engineering Reference for further infor-
mation on how the door protection types are modeled.
The following is an example input for a refrigeration walkin.
Refrigeration:WalkIn ,
WalkInFreezer , !- Name
CaseOperatingSched , !- Availability Schedule Name
4690. , !- Rated Coil Cooling Capacity {W}
-2.22, !- Operating Temperature {C}
-6.67, !- Rated Cooling Source Temperature {C}
0.0, !- Rated Total Heating Power {W}
CaseOperatingSched , !- Heating Power Schedule Name
735., !- Rated Cooling Coil Fan Power {W}
0.0, !- Rated Circulation Fan Power {W}
120., !- Rated Total Lighting Power {W}
CaseLightingSched2 , !- Lighting Schedule Name
Electric , !- Defrost Type
TimeSchedule , !- Defrost Control Type
CaseDefrostSched3 , !- Defrost Schedule Name
CaseDripDownSched3 , !- Defrost Drip -Down Schedule Name
5512. , !- Defrost Power {W}
, !- Temperature Termination Defrost Fraction to Ice {dimensionless}
WalkInStockingSched , !- Restocking Schedule Name
, !- Average Refrigerant Charge Inventory {kg}
13.0, !- Insulated Floor Surface Area {m2}
0.207 , !- Insulated Floor U-Value {W/m2 -C}
BackRoom , !- Zone Name
43.4, !- Total Insulated Surface Area Facing this Zone {m2}
.235, !- Insulated Surface U-Value Facing this Zone {W/m2 -C}
, !- Area of Glass Reach In Doors Facing this Zone {m2}
, !- Height of Glass Reach In Doors Facing this Zone {m}
, !- Glass Reach In Door U Value Facing this Zone {W/m2 -C}
, !- Glass Reach In Door Opening Schedule Name Facing this Zone
2.0, !- Area of Stocking Doors Facing this Zone {m2}
2.0, !- Height of Stocking Doors Facing this Zone {m}
, !- Stocking Door U Value Facing this Zone {W/m2 -C}
WIStockDoorOpenSch , !- Stocking Door Opening Schedule Name Facing this Zone
StripCurtain; !- Stocking Door Opening Protection Type Facing this Zone
This field is the total (sensible plus latent) cooling rate of the WalkIn evaporator coil in Watts.
This field is the total (sensible plus latent) cooling of the WalkIn evaporator coil in Joules over the
timestep being reported. This output is also added to a meter with Resource Type = EnergyTransfer,
End Use Key = Refrigeration, Group Key = Building (Ref. Output:Meter objects).
This field is the sensible cooling rate of the WalkIn evaporator coil in Watts.
1698 CHAPTER 1. INPUT-OUTPUT REFERENCE
This field is the sensible cooling of the WalkIn evaporator coil in Joules over the timestep being
reported.
This field is the latent cooling (dehumidification) rate of the WalkIn evaporator coil in Watts.
This field is the latent cooling (dehumidification) of the WalkIn evaporator coil in Joules over the
timestep being reported.
This field is the total electricity (fan, heaters, lights, and electric defrost) used by the walkin in
Watts.
This field is the electricity (fan, heaters, lights, and electric defrost)used by the WalkIn in Joules
over the timestep being reported.
This field is the electric power input to the WalkIn fan(s) in Watts.
This field is the electricity consumption of the WalkIn fan(s) in Joules over the timestep being
reported. This output is also added to a meter with Resource Type = Electricity, End Use Key =
Refrigeration, Group Key = Building (Ref. Output:Meter objects).
This field is the electric power input to the WalkIn lights in Watts.
This field is the electricity consumption of the WalkIn lights in Joules over the timestep being
reported. This output is also added to a meter with Resource Type = Electricity, End Use Key =
Refrigeration, Group Key = Building (Ref. Output:Meter objects).
This field is the electric power input to the WalkIn heaters in Watts.
1.34. GROUP – REFRIGERATION 1699
This field is the total electricity consumption of the WalkIn heaters in Joules over the timestep being
reported. This output is also added to a meter with Resource Type = Electricity, End Use Key =
Refrigeration, Group Key = Building (Ref. Output:Meter objects).
This field is the electric power input to the WalkIn electric defrost heater(s) in Watts. This output
is available if case defrost type is Electric.
This field is the total electricity consumption of the WalkIn electric defrost heater(s) in Joules over
the timestep being reported. This output is also added to a meter with Resource Type = Electricity,
End Use Key = Refrigeration, Group Key = Building (Ref. Output:Meter objects). This output is
available if case defrost type is Electric.
The following output variables are available for each zone adjacent to the walkin. An output variable
identification is created for each zone exchanging energy with the walkin. For example if the walkin,
“DairyWalkIn”, were exchanging energy with the zone, “SalesArea”, the output variable identification
would be “DairyWalkInInZoneSalesArea”.
This field is the rate of sensible cooling case credits delivered to the zone in Watts. A positive value
is reported when the zone is cooled by sensible case credits, otherwise a zero is reported.
This field is the amount of sensible cooling case credit energy delivered to the zone in Joules. A
positive value is reported when the zone is cooled by sensible case credits, otherwise a zero is reported.
This field is the rate of sensible heating case credits delivered to the zone in Watts. A positive value
is reported when the zone is heated by sensible case credits, otherwise a zero is reported.
This field is the amount of sensible heating case credit energy delivered to the zone in Joules. A
positive value is reported when the zone is heated by sensible case credits, otherwise a zero is
reported.
This field is the rate of latent cooling (dehumidification) case credits delivered to the zone in Watts.
A negative value (or zero) will be reported when the WalkIn provides dehumidification (thereby
reducing the zone latent load).
1700 CHAPTER 1. INPUT-OUTPUT REFERENCE
This field is the amount of latent cooling (dehumidification) case credit energy delivered to the zone
in Joules. A negative value (or zero) will be reported when the WalkIn provides dehumidification
(thereby reducing the zone latent load).
1.34.6 Refrigeration:System
The refrigeration system object simulates the performance of a supermarket refrigeration system
when used along with other objects to define the refrigeration load(s), the compressor(s), and the
condenser.
At least one refrigeration load object must be defined which may be one of four types of load, a
refrigerated case, a walk-in cooler, a chiller providing refrigeration to a secondary loop, or a cascade
condenser which absorbs heat rejected by a lower-temperature system (Ref. Refrigeration:Case, Re-
frigeration:WalkIn, Refrigeration:SecondarySystem, and Refrigeration:Condenser:Cascade) If multi-
ple loads are served by the same system , the user should use one or both of the list objects available
to assign loads to the system. The first list includes all cases and walkins cooled directly by this
system (Ref. Refrigeration:CaseAndWalkInList). The second list includes any ‘transfer’ loads, that
is refrigeration loads borne by this system that are transferred from another refrigeration system via
either a secondary loop chiller or a cascade condenser (Ref. Refrigeration:TransferLoadList, see the
Engineering Reference for more information about these types of systems).
The refrigeration system object is capable of modeling both single-stage and two-stage compression
refrigeration systems. The name of at least one compressor must be defined and a list object is
available if the system is served by more than one compressor (Ref. Refrigeration:Compressor and
Refrigeration:CompressorList).
Heat is rejected outdoors in a condenser by direct air flow, evaporative water cooling,
by a water-cooled condenser with appropriate plant loop piping, or to a cascade con-
denser cooled by another refrigeration system(ref: Refrigeration:Condenser:AirCooled, Re-
frigeration:Condenser:EvaporativeCooled, Refrigeration:Condenser:WaterCooled, Refrigera-
tion:Condenser:Cascade). With evaporative cooling, water is sprayed through the air stream
to effectively lower the air temperature experienced by the condenser coil as a result of water
evaporation. The use of a water-cooled condenser requires the definition of a plant loop to supply
cooling to the condenser. If a cascade condenser is specified, the refrigeration system absorbing the
rejected heat must also be defined.
The refrigeration system may also include a liquid suction and/or mechanical subcooler (Ref. Re-
frigeration:Subcooler).
The system object coordinates the energy flows between the other refrigeration objects and is used
to set system parameters. Compressor waste heat can also be reclaimed for use by an optional air-
or water-heating coil (Ref. Coil:Heating:Desuperheater and Coil:WaterHeating:Desuperheater).
The inputs for the refrigeration system object, in addition to the names of the other refrigeration
objects described above, include a name for this system, the minimum condensing temperature, the
refrigeration system working fluid, and the type of saturated suction temperature control. Optional
input fields are also provided for users seeking to keep track of refrigerant inventory and suction pipe
heat gains.
1.34. GROUP – REFRIGERATION 1701
1.34.6.1 Inputs
systems. If two stages of compression are selected, then an intercooler will be used between the
compressor stages to cool the discharge of the low-stage compressors. The default value is “1”.
Refrigeration:System ,
MediumTempSystem , !- Refrigeration System Name
MediumTempCaselist , !- Refrigeration Case or Walkin or CaseAndWalkInList Name
, !- Refrigeration Transfer Load or TransferLoad List Name
AirCooledCondenserA , !- Refrigeration Condenser Name
MediumTempCompressorlist , !- Refrigeration Compressor or CompressorList Name
25.0, !- Minimum Condensing Temperture {C}
R134a , !- Refrigeration System Working Fluid
ConstantSuctionTemperature , !- Suction Temperature Control Type
, !- Optional mechanical subcooler name
, !- Optional LSHX subcooler name
, !- Sum UA Distribution Piping {W/K}
, !- Distribution Piping Zone Name
MedTempRefrig; !- End -Use Subcategory
Refrigeration:System ,
LowTempSystem , !- Refrigeration System Name
LowTempCaselist , !- Refrigeration Case or Walkin or CaseAndWalkInList Name
, !- Refrigeration Transfer Load or TransferLoad List Name
AirCooledCondenserB , !- Refrigeration Condenser Name
LowStageCompressorList , !- Refrigeration Compressor or CompressorList Name
25.0, !- Minimum Condensing Temperture {C}
R404A , !- Refrigeration System Working Fluid
ConstantSuctionTemperature , !- Suction Temperature Control
, !- Optional mechanical subcooler name
, !- Optional LSHX subcooler name
, !- Sum UA Distribution Piping {W/K}
, !- Distribution Piping Zone Name
LowTempRefrig , !- End -Use Subcategory
2, !- Number of Compressor Stages
1704 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.34.6.2 Outputs
THE FOLLOWING OUTPUTS ARE AVAILABLE FOR SYSTEMS THAT SERVE CASES
AND/OR WALKINS:
– Zone,Sum,Refrigeration System Total Low Stage Compressor Heat Transfer Energy [J]
– Zone,Average,Refrigeration System Total Low Stage Compressor Heat Transfer Rate [W]
– Zone,Average,Refrigeration System Estimated Low Stage Refrigerant Mass Flow Rate [kg/s]
THE FOLLOWING OUTPUTS ARE AVAILABLE FOR SYSTEMS THAT SERVE AIR
CHILLERS:
– HVAC,Average, Refrigeration Air Chiller System Total Compressor Electricity Rate [W]
– HVAC,Sum, Refrigeration Air Chiller System Total Compressor Electricity Energy [J]
– HVAC,Average, Refrigeration Air Chiller System Average Compressor COP [W/W]
– HVAC,Average, Refrigeration Air Chiller System Total Compressor Heat Transfer Rate [W]
– HVAC,Sum, Refrigeration Air Chiller System Total Compressor Heat Transfer Energy [J]
– HVAC,Average, Refrigeration Air Chiller System Total Air Chiller Heat Transfer Rate [W]
– HVAC,Sum, Refrigeration Air Chiller System Total Case and Walk In Heat Transfer Energy
[J]
– HVAC,Average, Refrigeration Air Chiller System Total Transferred Load Heat Transfer Rate
[W]
– HVAC,Sum, Refrigeration Air Chiller System Total Transferred Load Heat Transfer Energy [J]
– HVAC,Average, Refrigeration Air Chiller System Total Suction Pipe Heat Gain Rate [W]
– HVAC,Sum, Refrigeration Air Chiller System Total Suction Pipe Heat Gain Energy [J]
– HVAC,Average, Refrigeration Air Chiller System Net Rejected Heat Transfer Rate [W]
– HVAC,Sum, Refrigeration Air Chiller System Net Rejected Heat Transfer Energy [J]
– HVAC,Average, Refrigeration Air Chiller System Liquid Suction Subcooler Heat Transfer Rate
[W]
– HVAC, Sum, Refrigeration Air Chiller System Liquid Suction Subcooler Heat Transfer Energy
[J]
– HVAC,Average, Refrigeration Air Chiller System Estimated Refrigerant Inventory Mass [kg]
– HVAC,Average, Refrigeration Air Chiller System Estimated Refrigerant Mass Flow Rate [kg/s]
– HVAC,Average,Refrigeration Air Chiller System Intercooler Temperature [C]
– HVAC,Average,Refrigeration Air Chiller System Intercooler Pressure [Pa]
– HVAC,Average, Refrigeration Air Chiller System Condensing Temperature [C]’
– HVAC,Average, Refrigeration Air Chiller System Evaporating Temperature [C]
– HVAC,Average, Refrigeration Air Chiller System Suction Temperature [C]
– HVAC,Average, Refrigeration Air Chiller System TXV Liquid Temperature [C]
– HVAC,Average,Refrigeration Air Chiller System Estimated High Stage Refrigerant Mass Flow
Rate [kg/s]
– HVAC,Sum,Refrigeration Air Chiller System Total High Stage Compressor Electricity Energy
[J]
– HVAC,Average,Refrigeration Air Chiller System Total High Stage Compressor Electricity Rate
[W]
1706 CHAPTER 1. INPUT-OUTPUT REFERENCE
– HVAC,Sum,Refrigeration Air Chiller System Total High Stage Compressor Heat Transfer En-
ergy [J]
– HVAC,Average,Refrigeration Air Chiller System Total High Stage Compressor Heat Transfer
Rate [W]
– HVAC,Sum, Refrigeration Air Chiller System Total Low and High Stage Compressor Electricity
Energy [J]
– HVAC,Sum,Refrigeration Air Chiller System Total Low Stage Compressor Electricity Energy
[J]
– HVAC,Average,Refrigeration Air Chiller System Total Low Stage Compressor Electricity Rate
[W]
– HVAC,Sum, Refrigeration Air Chiller System Total Low Stage Compressor Heat Transfer En-
ergy [J]
– HVAC,Average,Refrigeration Air Chiller System Total Low Stage Compressor Heat Transfer
Rate [W]
– HVAC,Average,Refrigeration Air Chiller System Estimated Low Stage Refrigerant Mass Flow
Rate [kg/s]
1.34.6.2.8 Refrigeration System Total Low and High Stage Compressor Electric-
ity Energy [J]
This is the total electricity consumption of the system’s low- and high-stage compressor(s) in Joules
for the timestep being reported. The individual consumption for each compressor is also added to a
meter with Resource Type = Electricity, End Use Key = Refrigeration, Group Key = Plant (Ref.
Output:Meter objects). This output is valid only for two-stage compression systems.
1.34.6.2.16 Refrigeration System Total Cases and Walk Ins Heat Transfer Rate
[W]
This output is the total heat transfer rate from the refrigerated cases and walk-ins served directly
by this system in Watts. It is the sum of all of the heat transfer rates for the refrigerated cases
and walk-ins that are connected directly to this system. This value does not include compressor or
condenser fan heat or the heat transfer for cases and walk-ins served by any connected secondary
systems.
1.34.6.2.17 Refrigeration System Total Cases and Walk Ins Heat Transfer Energy
[J]
This output is the total heat transfer energy from the refrigerated cases and walk-ins served directly
by this system in Joules. It is the sum of all of the heat transfered for the refrigerated cases and
walk-ins that are connected directly to this system. This value does not include compressor or
condenser fan heat or the heat transfer for cases and walk-ins served by any connected secondary
systems.
1.34.6.2.18 Refrigeration System Total Transferred Load Heat Transfer Rate [W]
This output is the sum of the heat transfer rates for any secondary loops, cascade condensers,
and mechanical subcoolers cooled by this system, minus the benefit of any mechanical subcooler
providing cooling to this system in Watts. Therefore, if the only transfer load between two systems
is a mechanical subcooler, the same amount will show as a negative value for the system receiving the
cooling effect and as a positive number for the system serving that cooling load. It also includes the
pump energy for any secondary loops and the compressor energy for any cascade condenser systems
that are cooled by this system. (See the Engineering Reference for more details about the loads
placed by secondary systems upon the primary system.)
This output is the sum of the heat transfered for any secondary loops, cascade condensers, and
mechanical subcoolers cooled by this system, minus the benefit of any mechanical subcooler providing
cooling to this system in Joules. Therefore, if the only transfer load between two systems is a
mechanical subcooler, the same amount will show as a negative value for the system receiving the
cooling effect and as a positive number for the system serving that cooling load. It also includes the
pump energy for any secondary loops and the compressor energy for any cascade condenser systems
that are cooled by this system. (See the Engineering Reference for more details about the loads
placed by secondary systems upon the primary system.)
1.34.6.2.20 Refrigeration System Total Suction Pipe Heat Gain Rate [W]
This output is the total heat transfer rate for suction piping served by this system in Watts. Note
this is an optional input, and is only available if the user has described the suction piping heat gain
characteristics in the input.
1.34.6.2.21 Refrigeration System Total Suction Pipe Heat Gain Energy [J]
This output is the total heat transfer rate for suction piping served by this system in Watts. Note
this is an optional input, and is only available if the user has described the suction piping heat gain
characteristics in the input.
This output is the calculated refrigerant mass flow through the compressors for this system.
1.34.6.2.39 Refrigeration Air Chiller System Total Low Stage Compressor Elec-
tricity Rate [W]
This output is the total electric power input to the system’s low-stage compressor(s) in Watts. This
output is valid only for two-stage compression systems.
1.34.6.2.40 Refrigeration Air Chiller System Total Low Stage Compressor Elec-
tricity Energy [J]
This is the electricity consumption of the system’s low-stage compressor(s) in Joules for the timestep
being reported. The individual consumption for each compressor is also added to a meter with
Resource Type = Electricity, End Use Key = Refrigeration, Group Key = Plant (Ref. Output:Meter
objects). This output is valid only for two-stage compression systems.
1.34.6.2.41 Refrigeration Air Chiller System Total High Stage Compressor Elec-
tricity Rate [W]
This output is the total electric power input to the system’s high-stage compressor(s) in Watts. This
output is valid only for two-stage compression systems.
1.34.6.2.42 Refrigeration Air Chiller System Total High Stage Compressor Elec-
tricity Energy [J]
This is the electricity consumption of the system’s high-stage compressor(s) in Joules for the timestep
being reported. The individual consumption for each compressor is also added to a meter with
Resource Type = Electricity, End Use Key = Refrigeration, Group Key = Plant (Ref. Output:Meter
objects). This output is valid only for two-stage compression systems.
1.34.6.2.43 Refrigeration Air Chiller System Total Low and High Stage Com-
pressor Electricity Energy [J]
This is the total electricity consumption of the system’s low- and high-stage compressor(s) in Joules
for the timestep being reported. The individual consumption for each compressor is also added to a
meter with Resource Type = Electricity, End Use Key = Refrigeration, Group Key = Plant (Ref.
Output:Meter objects). This output is valid only for two-stage compression systems.
This output is the system average compressor COP, the total refrigeration effect divided by the total
power to the compressors
1712 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.34.6.2.47 Refrigeration Air Chiller System Total Low Stage Compressor Heat
Transfer Rate [W]
This output is the total heat transfer rate of the low-stage compressors in Watts. It is the sum of all
of the heat transfer rates for the refrigerated cases, walk-ins, secondary loops, cascade condensers,
and mechanical subcoolers that are cooled by this system. This value does not include compressor
or condenser fan heat. If specified as in input value, the suction pipe heat gains are included in this
value. This output is valid only for two-stage compression systems.
1.34.6.2.48 Refrigeration Air Chiller System Total Low Stage Compressor Heat
Transfer Energy [J]
This is the total heat transfer of the low-stage compressors in Joules for the timestep being reported.
This output is also added to a meter with Resource Type = EnergyTransfer, End Use Key =
Refrigeration, Group Key = Plant (Ref. Output:Meter objects). This output is valid only for
two-stage compression systems.
1.34.6.2.49 Refrigeration Air Chiller System Total High Stage Compressor Heat
Transfer Rate [W]
This output is the total heat transfer rate of the high-stage compressors in Watts. It is the sum of all
of the heat transfer rates for the refrigerated cases, walk-ins, secondary loops, cascade condensers,
and mechanical subcoolers that are cooled by this system. This value does not include compressor
or condenser fan heat. If specified as in input value, the suction pipe heat gains are included in this
value. This output is valid only for two-stage compression systems.
1.34.6.2.50 Refrigeration Air Chiller System Total High Stage Compressor Heat
Transfer Energy [J]
This is the total heat transfer of the high-stage compressors in Joules for the timestep being reported.
This output is also added to a meter with Resource Type = EnergyTransfer, End Use Key =
Refrigeration, Group Key = Plant (Ref. Output:Meter objects). This output is valid only for
two-stage compression systems.
1.34. GROUP – REFRIGERATION 1713
1.34.6.2.51 Refrigeration Air Chiller System Total Air Chiller Heat Transfer
Rate [W]
This output is the total heat transfer rate from the refrigerated cases and walk-ins served directly
by this system in Watts. It is the sum of all of the heat transfer rates for the refrigerated cases
and walk-ins that are connected directly to this system. This value does not include compressor or
condenser fan heat or the heat transfer for cases and walk-ins served by any connected secondary
systems.
1.34.6.2.52 Refrigeration Air Chiller System Total Case and Walk In Heat Trans-
fer Energy [J]
This output is the total heat transfer energy from the refrigerated cases and walk-ins served directly
by this system in Joules. It is the sum of all of the heat transfered for the refrigerated cases and
walk-ins that are connected directly to this system. This value does not include compressor or
condenser fan heat or the heat transfer for cases and walk-ins served by any connected secondary
systems.
1.34.6.2.53 Refrigeration Air Chiller System Total Transferred Load Heat Trans-
fer Rate [W]
This output is the sum of the heat transfer rates for any secondary loops, cascade condensers,
and mechanical subcoolers cooled by this system, minus the benefit of any mechanical subcooler
providing cooling to this system in Watts. Therefore, if the only transfer load between two systems
is a mechanical subcooler, the same amount will show as a negative value for the system receiving the
cooling effect and as a positive number for the system serving that cooling load. It also includes the
pump energy for any secondary loops and the compressor energy for any cascade condenser systems
that are cooled by this system. (See the Engineering Reference for more details about the loads
placed by secondary systems upon the primary system.)
1.34.6.2.54 Refrigeration Air Chiller System Total Transferred Load Heat Trans-
fer Energy [J]
This output is the sum of the heat transfered for any secondary loops, cascade condensers, and
mechanical subcoolers cooled by this system, minus the benefit of any mechanical subcooler providing
cooling to this system in Joules. Therefore, if the only transfer load between two systems is a
mechanical subcooler, the same amount will show as a negative value for the system receiving the
cooling effect and as a positive number for the system serving that cooling load. It also includes the
pump energy for any secondary loops and the compressor energy for any cascade condenser systems
that are cooled by this system. (See the Engineering Reference for more details about the loads
placed by secondary systems upon the primary system.)
1.34.6.2.55 Refrigeration Air Chiller System Total Suction Pipe Heat Gain Rate
[W]
This output is the total heat transfer rate for suction piping served by this system in Watts. Note
this is an optional input, and is only available if the user has described the suction piping heat gain
characteristics in the input.
1714 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.34.6.2.56 Refrigeration Air Chiller System Total Suction Pipe Heat Gain En-
ergy [J]
This output is the total heat transfer rate for suction piping served by this system in Watts. Note
this is an optional input, and is only available if the user has described the suction piping heat gain
characteristics in the input.
1.34.6.2.57 Refrigeration Air Chiller System Net Rejected Heat Transfer Rate
[W]
This output is the total heat rejected by this system to the system condenser in Watts. It does not
include system heat rejection that has been recovered for useful purposes. However, if a water-cooled
condenser was used to provide heat to a separate water loop, the energy transferred to that loop is
included here.
1.34.6.2.58 Refrigeration Air Chiller System Net Rejected Heat Transfer Energy
[J]
This output is the total heat rejected by this system to the system condenser in Joules for the
timestep being reported. It does not include system heat rejection that has been recovered for useful
purposes. However, if a water-cooled condenser was used to provide heat to a separate water loop,
the energy transferred to that loop is included here.
1.34.7 Refrigeration:TranscriticalSystem
The Refrigeration:TranscriticalSystem object allows users to model detailed transcritical carbon
dioxide (CO2 ) booster refrigeration systems used in supermarkets. The object allows for modeling
either a single stage system with medium-temperature loads or a two stage system with both medium-
and low-temperature loads.
The input objects required to model a detailed transcritical CO2 refrigeration system include the
following:
– At least one refrigeration load object which may include any combination of the following:
– Refrigeration:Case,
– Refrigeration:WalkIn,
– Refrigeration:CaseAndWalkInList (may include both cases and/or walk-in cooler names),
– At least one Refrigeration:Compressor object (multiple compressors are entered using a Refrig-
eration:CompressorList),
– One Refrigeration:GasCooler:AirCooled object,
Output variables are available to describe the total heat exchange between all the refrigeration
objects and the zones containing these objects. These variables are described at the end of this
section.
At least one refrigeration load object must be defined which may be one of two types of loads,
including a refrigerated display case and a walk-in cooler, (Ref. Refrigeration:Case, and Refrigera-
tion:WalkIn). If multiple loads are served by the same system, the user should use the refrigerated
case and walk-in list object available to assign all cases and walk-ins cooled directly by this system
(Ref. Refrigeration:CaseAndWalkInList).
The name of at least one compressor must be defined and a list object is available if the
system is served by more than one compressor (Ref. Refrigeration:Compressor and Refrigera-
tion:CompressorList).
Heat is rejected to the outdoors via an air-cooled gas cooler (Ref. Refrigeration:GasCooler:AirCooled).
The Refrigeration:TranscriticalSystem object coordinates the energy flows between the other refrig-
eration objects and is used to set system parameters.
The inputs for the refrigeration system object, in addition to the names of the other refrigeration
objects described above, include a name for this system, the receiver pressure, the subcooler effec-
tiveness, and the refrigeration system working fluid. Optional input fields are also provided for
users seeking to keep track of suction pipe heat gains.
A detailed description of the transcritical CO2 booster refrigeration system may be found in the
Refrigeration section of the Engineering Reference.
1.34.7.1 Inputs
by Subcategory table and in the LEED Summary EAp2-4/5 Performance Rating Method Compliance
table. If this field is left blank, the equipment will be assigned to the “General” end-use subcategory.
The following is an example input for a transcritical CO2 refrigeration system.
Refrigeration:TranscriticalSystem ,
TransRefrigSys , !- Name
TwoStage , !- System Type
MTLoads , !- Medium Temperature Refrigerated Case or Walkin or
CaseAndWalkInList Name
LTLoads , !- Low Temperature Refrigerated Case or Walkin or CaseAndWalkInList
Name
RefrigGasCooler , !- Refrigeration Gas Cooler Name
HPCompressors , !- High Pressure Compressor or CompressorList Name
LPCompressors , !- Low Pressure Compressor or CompressorList Name
4000000 , !- Receiver Pressure
0.4, !- Subcooler Effectiveness
R744 , !- Refrigeration System Working Fluid Type
, !- Sum UA Suction Piping for Medium Temperature Loads
, !- Medium Temperature Suction Piping Zone Name
, !- Sum UA Suction Piping for Low Temperature Loads
, !- Low Temperature Suction Piping Zone Name
TransRefrigSys; !- End -Use Subcategory
1.34.7.2 Outputs
– Zone,Average, Refrigeration Transcritical System Low Temperature Suction Pipe Heat Transfer
Rate [W]
– Zone,Sum, Refrigeration Transcritical System Low Temperature Suction Pipe Heat Transfer
Energy [J]
– Zone,Average, Refrigeration Transcritical System High Pressure Compressor Heat Transfer
Rate [W]
– Zone,Sum, Refrigeration Transcritical System High Pressure Compressor Heat Transfer Energy
[J]
– Zone,Average, Refrigeration Transcritical System Low Pressure Compressor Heat Transfer Rate
[W]
– Zone,Sum, Refrigeration Transcritical System Low Pressure Compressor Heat Transfer Energy
[J]
– Zone,Average, Refrigeration Transcritical System Net Rejected Heat Transfer Rate [W]
– Zone,Sum, Refrigeration Transcritical System Net Rejected Heat Transfer Energy [J]
– Zone,Average, Refrigeration Transcritical System Estimated Refrigerant Inventory Mass [kg]
– Zone,Average, Refrigeration Transcritical System Refrigerant Mass Flow Rate [kg/s]
– Zone,Average, Refrigeration Transcritical System Medium Temperature Evaporating Temper-
ature [C]
– Zone,Average, Refrigeration Transcritical System Medium Temperature Suction Temperature
[C]
– Zone,Average, Refrigeration Transcritical System Low Temperature Evaporating Temperature
[C]
– Zone,Average, Refrigeration Transcritical System Low Temperature Suction Temperature [C]
1.34.7.2.11 Refrigeration Transcritical System Total Cases and Walk Ins Heat
Transfer Energy [J]
This output is the total heat transfer energy from all the low- and medium-temperature refrigerated
cases and walk-ins served directly by this system in Joules. It is the sum of all of the heat transferred
for all the refrigerated cases and walk-ins that are connected directly to this system.
1722 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.34.8 Refrigeration:Compressor
The compressors are described here using manufacturer’s data for curves that provide the efficiency,
cooling capacity, and power consumption. The corresponding rated values for cycle superheat and
subcooling are also required.
A dataset has been provided containing the compressor rating data, including the
performance curve inputs, for a large number of compressors. See RefrigerationCom-
pressorCurves.idf.
1.34.8.1 Inputs
bicubic curve does not match the ARI 540 standard order. When this curve is entered, the user
should use the following assignments:
N1 is ARI C1 and N2 is ARI C2.
N3 is ARI C4 and N4 is ARI C3.
N5 is ARI C6 and N6 is ARI C5,
N7 is ARI C7.
N8 is ARI C10, N9 is ARI C8, and N10 is ARI C9.
N11 is the Minimum saturated suction temperature.
N12 is the Maximum saturated suction temperature.
N13 is the the Minimum gas cooler pressure and N14 is the Maximum gas cooler pressure.
If Transcritical is selected as Mode of Operation, then this input field is required.
Refrigeration:Compressor ,
CompressorA , !- Name
PowerCurveCompA , !- Refrigeration Compressor Power Curve Name
CapCurveCompA , !- Refrigeration Compressor Capacity Curve Name
10.0, ! – Rated Superheat {delta C}
, !- Rated Return Gas Temperature {C}
, ! – Rated Liquid Temperature{C}
15.0, !- Rated Subcooling {delta C}
MedTempRefrig; !- End -Use Subcategory
1.34. GROUP – REFRIGERATION 1727
1.34.8.2 Outputs
THE FOLLOWING OUTPUTS ARE AVAILABLE FOR SYSTEMS THAT SERVE CASES
AND/OR WALKINS:
THE FOLLOWING OUTPUTS ARE AVAILABLE FOR SYSTEMS THAT SERVE AIR
CHILLERS:
1.34.9 Refrigeration:CompressorList
This object provides a list of all the compressors included within a single refrigeration system (Ref:
Refrigeration:System). Each list must contain at least one compressor. The order in which the
individual compressors are listed here will be the order in which the compressors are dispatched to
meet the system load. That is, at very low loads, only compressor #1 will be operating. As the
load increases, the first two compressors will be operating, and so on.
1.34.9.1 Inputs
Refrigeration:CompressorList ,
MediumTempCompressorlist , !- Refrigeration Compressor List Name
CompressorA , !- Refrigeration Compressor Name \#1
CompressorB , !- Refrigeration Compressor Name \#2
CompressorC; !- Refrigeration Compressor Name \#3
1.34.10 Refrigeration:Subcooler
Two types of subcoolers are modeled by the detailed refrigeration system. As described in the
Engineering Reference, the liquid suction heat exchanger uses cool suction gas to subcool the hot
condensate after it leaves the condenser and before it reaches the thermal expansion valve. For
the liquid suction heat exchanger, both the source and sink of energy are located within the same
refrigeration system. In contrast, a mechanical subcooler is used to transfer cooling capacity from
one refrigeration system to another. The mechanical subcooler is listed as a part of the system for
which the condensate is cooled. However, the input data for the mechanical subcooler includes a
field that identifies the system that provides the cooling capacity.
1.34.10.1 Inputs
REFRIGERATION:SUBCOOLER ,
SampleLSHx , !Subcooler Name
LiquidSuction , !subcooler type
6, !design liquid suction subcooling {deltaC}
16, !design inlet temperature on liquid side {C}
0, !design inlet temperature on vapor side {C}
, !Refrigeration System Detailed Name providing cooling capacity
; !Control Temperature Out for subcooled liquid {C}
! Mechanical Subcooler (uses Med Temp System to cool low temp liquid to 10C)
REFRIGERATION:SUBCOOLER ,
SampleMSC , !Subcooler Name
Mechanical , !subcooler type
, !design liquid suction subcooling {C}
, !design inlet temperature on liquid side {C}
, !design inlet temperature on vapor side {C}
MediumTempSystem , !Refrigeration System Detailed Name providing cooling capacity
10; !Control Temperature Out for subcooled liquid {C}
1.34.10.2 Outputs
– Zone,Average, Refrigeration Air Chiller System Mechanical Subcooler Heat Transfer Rate [W]
– Zone,Sum, Refrigeration Air Chiller System Mechanical Subcooler Heat Transfer Energy [J]
This output is the cooling energy transferred from one system’s compressor group to the refrigerant
leaving the condenser for another refrigeration system in Watts.
1.34. GROUP – REFRIGERATION 1731
1.34.11 Refrigeration:Condenser:AirCooled
The refrigeration system requires a single condenser to reject the system heat. The air cooled
condenser object is one of four options for this condenser. In an air-cooled condenser, the total
heat of rejection is characterized by a linear relationship between the difference between the inlet air
(usually the outside drybulb) and condensing temperatures. This curve is commonly found in the
condenser manufacturers’ literature. This rating curve, which corresponds to ARI 460 standards,
also has an associated rated value for subcooling that should be entered. The rated condenser fan
power and fan speed control type must be specified. If the condenser is not at ground level, the
user may specify an air inlet node name (ref: OutdoorAir:Node name). If the condenser is located
inside a conditioned zone, the zone name may be specified(ref: bbbZoneNamebbb). Optional input
is provided to help the user compare refrigerant inventories for different systems. These inputs
represent the design values for the refrigerant inventory within the condenser, within a receiver
beneath the condenser, and in the liquid pipes between the condenser and the refrigerated cases.
1.34.11.1 Inputs
1.34.11.1.2 Field: Rated Effective Total Heat Rejection Rate Curve Name
This field is the name of a curve object defining the condenser heat rejection as a function of
the difference between the condensing and entering air temperatures. The curve should be linear
(Curve:Linear). See the Engineering Reference for more discussion on the curve coefficients.
1732 CHAPTER 1. INPUT-OUTPUT REFERENCE
Refrigeration:Condenser:AirCooled ,
MediumTempCondenser , !- Name of condenser
MediumTempCondenserHRCurve , !-name of condenser heat of rejection curve , linear
0., ! Rated subcooling {deltaC}
VariableSpeed , ! Fan speed control type
4000. , ! Design condenser fan power {W}
0.25, !Minimum air flow fraction through condenser fan {dimensionless}
Refrigeration MediumTempSystem CondenserNode , !- Condenser Air Inlet Node Name or Zone Name
MediumTempRefrig; !- End -Use Subcategory
1.34.11.2 Outputs
– HVAC,Average, Refrigeration Air Chiller System Condenser Defrost Recovered Heat Transfer
Rate [W]
– HVAC, Sum, Refrigeration Air Chiller System Condenser Defrost Recovered Heat Transfer
Energy [J]
1.34.11.2.15 Refrigeration Air Chiller System Condenser Heat Transfer Rate [W]
This is the total heat transfer across the condenser (i.e., compressor energy and refrigeration load
minus any heat recovered for defrost or other purposes).
1.34.12 Refrigeration:Condenser:EvaporativeCooled
Each refrigeration system requires a single condenser. The evaporative cooled condenser object is
one of four options for this condenser. In an evaporative-cooled condenser, the total heat of rejection
is characterized by a four-factor relationship between the condensing temperature and the difference
between the outside wetbulb and condensing temperatures. This curve must be developed by regres-
sion from the condenser manufacturers’ literature. This rating curve, which is based upon rated data
taken according to ARI 460 standards, also has an associated rated value for subcooling that should
be entered. The rated condenser fan power and fan speed control type must be specified. If the
condenser is not at ground level, the user may specify an air inlet node name (ref: OutdoorAir:Node
name). Optional input is provided to help the user compare refrigerant inventories for different
systems. These input represent the design values for the refrigerant inventory within the condenser,
within a receiver beneath the condenser, and in the liquid pipes between the condenser and the
refrigerated cases.
Additional inputs are needed for basin heater parameters, water pump power, and water source. An
evaporative cooling availability schedule is available.
1.34.12.1 Inputs
This numeric field is the value for A3 and has a default value of 17.93, a minimum of 0, and a
maximum of 30 (C).
Refrigeration:Condenser:EvaporativeCooled ,
MedTempEvapCooledCondenser , !- Refrigeration Condenser Name
64800. , !- Rated Total Heat Rejection Effect , {W}
0. , !- Rated Subcooling
VariableSpeed , !- Condenser Fan Speed Control
746., !- Rated Condenser Fan Power
0.25, !- Minimum air flow fraction through condenser fan {dimensionless
}
6.63 , !- Evaporative Condenser Approach Temp Const , {C}
0.468 , !- Evaporative Condenser Approach Temp HRCF Cooefficient
17.93 , !- Evaporative Condenser Approach Temp 1/ hrcf coefficient
-0.322, !- Evaporative Condenser Approach Temp Twb coefficient {1/C}
0.6 , !- Minimum Condenser Capacity Factor
4.8 , !- Maximum Condenser Capacity Factor
Outside Air Inlet Node , !- Condenser Air Inlet Node Name
1.79 , !- Rated Air Flow Rate {m3/s}
66.7 , !- Basin Heater Capacity {W/C}
1.0 , !- Basin Heater Set Point Temperature {C}
250. , !- Rated Water Pump Power {W}
EvapWaterStorageTank , !- Evaporative Water Supply Tank Name
EvapCondAvail , !- Evaporative Condenser Availability Schedule Name
, !- End -UseSubcategory
21.9 , !- Condenser Refrigerant Operating Charge {kg}
10. , !- Condensate Receiver Refrigerant Inventory
25. ; !- Condensate Piping Refrigerant Inventory
1.34.12.2 Outputs
– HVAC,Average, Refrigeration Air Chiller System Condenser Heat Transfer Rate [W]
– HVAC, Sum, Refrigeration Air Chiller System Condenser Heat Transfer Energy [J]
– HVAC,Average, Refrigeration Air Chiller System Condenser Total Recovered Heat Transfer
Rate [W]
– HVAC, Sum, Refrigeration Air Chiller System Condenser Total Recovered Heat Transfer En-
ergy [J]
– HVAC,Average, Refrigeration Air Chiller System Condenser Non Refrigeration Recovered Heat
Transfer Rate [W]
– HVAC, Sum, Refrigeration Air Chiller System Condenser Non Refrigeration Recovered Heat
Transfer Energy [J]
– HVAC,Average, Refrigeration Air Chiller System Condenser Defrost Recovered Heat Transfer
Rate [W]
– HVAC, Sum, Refrigeration Air Chiller System Condenser Defrost Recovered Heat Transfer
Energy [J]
– HVAC,Average, Refrigeration Air Chiller System Condenser Pump Electricity Rate [W]
– HVAC, Sum, Refrigeration Air Chiller System Condenser Pump Electricity Energy [J]
– HVAC,Average, Refrigeration Air Chiller System Condenser Basin Heater Electricity Rate [W]
– HVAC, Sum, Refrigeration Air Chiller System Condenser Basin Heater Electricity Energy [J]
– HVAC,Average, Refrigeration Air Chiller System Condenser Evaporated Water Volume Flow
Rate [m3/s]
– HVAC, Sum, Refrigeration Air Chiller System Condenser Evaporated Water Volume [m3]
This is the electrical power requirement in Watts for the timestep being reported for the water heater
in the basin of the evaporative system used to cool the condenser.
1.34.12.2.21 Refrigeration Air Chiller System Condenser Heat Transfer Rate [W]
This is the total heat transfer across the condenser (i.e., compressor energy and refrigeration loads)
in Watts.
1.34.13 Refrigeration:Condenser:WaterCooled
The refrigeration system requires a single condenser. The water cooled condenser object is one of
four options for this condenser. Manufacturer’s data is required for the rated total heat rejection,
the rated condensing temperature, and the rated leaving liquid refrigerant temperature, all per ARI
450. These values are used to calculate the subcooling included in the rated capacity. The inlet and
outlet node names as well as the water outlet temperature schedule name are required. Optional
input is provided to help the user compare refrigerant inventories for different systems. These input
represent the design values for the refrigerant inventory within the condenser, within a receiver
beneath the condenser, and in the liquid pipes between the condenser and the refrigerated cases.
1746 CHAPTER 1. INPUT-OUTPUT REFERENCE
1.34.13.1 Inputs
Refrigeration:Condenser:WaterCooled ,
MediumTempCondenser , !- Name
58000. , !- Rated Effective Total Heat Rejection Rate {W}
29.4 , !- Rated Condensing Temperature {C}
0.0 , !- Rated Subcooling Temperature Difference{deltaC}
10.0, !- Rated Water Inlet Temperature {C}
Condenser Inlet Node , !- Water Inlet Node Name
Condenser Outlet Node , !- Water - Outlet Node Name
Variable Flow , !- Water -cooled Loop Flow Type
Cond Outlet Temp Sch , !- Water Outlet Temperature Schedule Name
, !- Water Design Flow Rate {m3/s}
0.003 , !- Water Maximum Flow Rate {m3/s}
55., !- Maximum Water Outlet Temperature {C}
, !- Minimum Water Inlet Temperature {C}
, !- End -Use Subcategory
30. , !- Condenser Refrigerant Operating Charge {kg}
65. , !- Condensate Receiver Refrigerant Inventory {kg}
20. ; !- Condensate Piping Refrigerant Inventory {kg}
1.34.13.2 Outputs
– HVAC,Average, Refrigeration Air Chiller System Condenser Heat Transfer Rate [W]
– HVAC, Sum, Refrigeration Air Chiller System Condenser Heat Transfer Energy [J]
– HVAC,Average, Refrigeration Air Chiller System Condenser Total Recovered Heat Transfer
Rate [W] HVAC, Sum, Refrigeration Air Chiller System Condenser Total Recovered Heat
Transfer Energy [J]
– HVAC,Average, Refrigeration Air Chiller System Condenser Non Refrigeration Recovered Heat
Transfer Rate [W]
– HVAC, Sum, Refrigeration Air Chiller System Condenser Non Refrigeration Recovered Heat
Transfer Energy [J]
– HVAC,Average, Refrigeration Air Chiller System Condenser Defrost Recovered Heat Transfer
Rate [W]
– HVAC, Sum, Refrigeration Air Chiller System Condenser Defrost Recovered Heat Transfer
Energy [J]
– HVAC,Average, Refrigeration Air Chiller System Condenser Fluid Mass Flow Rate [kg/s]
1.34. GROUP – REFRIGERATION 1749
1.34.13.2.12 Refrigeration Air Chiller System Condenser Heat Transfer Rate [W]
This is the total heat transfer across the condenser (i.e., compressor energy and refrigeration loads)
in Watts.
1.34.13.2.20 Refrigeration Air Chiller System Condenser Fluid Mass Flow Rate
[kg/s]
This is the mass flow rate of the water used to cool the condenser in kg/s.
1.34.14 Refrigeration:Condenser:Cascade
The refrigeration system requires a single condenser. The cascade condenser object is one of four
options for this condenser. The cascade condenser is unlike the other condenser options because it re-
jects heat to another, higher-temperature, refrigeration system. That is, the cascade condenser acts
as a heat rejection object for one system, but acts as a refrigeration load for another system. There-
fore, this object will be referenced twice: first for the system rejecting heat (see the field Refrigeration
Condenser Name for the object Refrigeration:System), and second for the system absorbing the heat
(see the input for the field Refrigeration Transfer Load or TransferLoad List Name for the object
Refrigeration:System or the field Cascade Condenser Name or Secondary System Name for the object
Refrigeration:TransferLoadList).
Manufacturer’s data is required for the rated condensing temperature and the rated approach tem-
perature difference. The user must also specify the condensing temperature control type. There are
two choices. The user can specify “Fixed” and the condensing temperature will be held constant at
the input value. The user can specify “Float” if they want the condensing temperature to be set by
other refrigeration loads served by the higher-temperature system.
The rated heat rejection capacity is not used except as a rough input value check on the overall
system sizing. Optional input is provided to help the user compare refrigerant inventories for different
systems. These inputs represent the design values for the refrigerant inventory within the condenser,
within a receiver beneath the condenser, and in the liquid pipes between the condenser and the
refrigerated cases.
1.34.14.1 Inputs
Refrigeration:Condenser:Cascade ,
CascadeCondenser1 , !- Name
-4. , !- Rated Condensing Temperature {C}
3. , !- Rated Approach Temperature Difference {DeltaC}
20000.0 , !- Rated Effective Total Heat Rejection Rate {W}
Fixed; !- Condensing Temperature Control Type
1.34.14.2 Outputs
– HVAC,Average, Refrigeration Air Chiller System Condenser Heat Transfer Rate [W]
– HVAC, Sum, Refrigeration Air Chiller System Condenser Heat Transfer Energy [J]
1.34.14.2.5 Refrigeration Air Chiller System Condenser Heat Transfer Rate [W]
This is the total heat transfer across the condenser (i.e., compressor energy and refrigeration loads)
in Watts.
1.34.15 Refrigeration:GasCooler:AirCooled
The transcritical refrigeration system requires a single gas cooler to reject the system heat. The
total heat of rejection is characterized by a linear relationship between the difference between the
outside dry-bulb and gas cooler outlet temperatures. The rated gas cooler fan power and fan speed
control type must be specified. If the gas cooler is not at ground level, the user may specify an air
inlet node name (Ref. OutdoorAir:Node name). Optional input is provided to help the user track
refrigerant inventories. These inputs represent the design values for the refrigerant inventory within
the gas cooler, within a receiver, and in the liquid pipes between the gas cooler and the refrigerated
cases.
1.34.15.1 Inputs
Refrigeration:GasCooler:AirCooled ,
RefrigGasCooler , !- Name
GasCoolerHRCurve , !- Rated Total Heat Rejection Rate Curve Name
Fixed , !- Gas Cooler Fan Speed Control Type
6400, !- Rated Fan Power
0.2, !- Minimum Fan Air Flow Ratio
27.0, !- Transition Temperature
3.0, !- Transcritical Approach Temperature
10.0, !- Subcritical Temperature Difference
10.0, !- Minimum Condensing Temperature
, !- Air Inlet Node Name
RefrigGasCooler , !- End -Use Subcategory
, !- Gas Cooler Refrigerant Operating Charge Inventory
, !- Gas Cooler Receiver Refrigerant Inventory
; !- Gas Cooler Outlet Piping Refrigerant Inventory
1.34.15.2 Outputs
– Zone,Average, Refrigeration Transcritical System Gas Cooler Heat Transfer Rate [W]
– Zone,Sum, Refrigeration Transcritical System Gas Cooler Heat Transfer Energy [J]
– Zone,Average, Refrigeration Transcritical System Gas Cooler Fan Electricity Rate [W]
– Zone,Sum, Refrigeration Transcritical System Gas Cooler Fan Electricity Energy [J]
– Zone,Average, Refrigeration Transcritical System Gas Cooler Outlet Temperature [C]
– Zone,Average, Refrigeration Transcritical System Gas Cooler Outlet Pressure [Pa]
1756 CHAPTER 1. INPUT-OUTPUT REFERENCE
– Zone,Average, Refrigeration Transcritical System Gas Cooler Defrost Recovered Heat Transfer
Rate [W]
– Zone,Sum, Refrigeration Transcritical System Gas Cooler Defrost Recovered Heat Transfer
Energy [J]
This output is the pressure (in Pa) of the refrigerant exiting the gas cooler.
1.34.16 Refrigeration:TransferLoadList
A refrigeration system may provide cooling to other, secondary, systems through either a
secondary loop or a cascade condenser (Ref. Refrigeration:SecondarySystem and Refrigera-
tion:Condenser:Cascade). If multiple transfer loads are served by a single primary system, use
this list to group them together for reference by the primary system (see the field “Refrigeration
Transfer Load or TransferLoad List Name” in the Refrigeration:System object).
1.34.16.1 Inputs
Refrigeration:TransferLoadList ,
MedTempTransferLoads , !- Name
CascadeCondFrozen , !- Cascade Condenser Name or Secondary System Name
SecondLoopDairy; !- Cascade Condenser Name or Secondary System Name
1.34.17 Refrigeration:SecondarySystem
A refrigeration secondary system works in conjunction with refrigerated cases and walkins (Ref.
Refrigeration:SecondarySystem, Refrigeration:CaseAndWalkInList, Refrigeration:Case, and Refrig-
eration:WalkIn) to simulate the performance of a secondary loop supermarket refrigeration system.
Heat from the refrigeration loads served by the secondary loop is absorbed by a primary refrigeration
system (ref: Refrigeration:System). The SecondarySystem object simulates a heat exchanger that is
an evaporator, or refrigeration load, on the primary refrigeration system.
The inputs for the refrigeration secondary system object include a name, which is also referenced to
identify the load placed upon the primary refrigeration system. The inputs that describe the loads
placed upon the secondary loop include the name of a single refrigerated case, the name of a single
walk-in cooler, or a list of cases and walkin coolers. The circulating fluid type specifies whether
or not the secondary fluid remains in the liquid state throughout the loop (e.g., a glycol or brine
solution) or undergoes a partial phase change while serving the refrigeration loads (e.g., a CO2 liquid
overfeed system). The circulating fluid name must also be specified and must correspond to a name
used to provide the fluid properties.
If the secondary fluid remains a liquid, the heat exchanger between the primary and secondary sys-
tems functions as an evaporator on the primary side and chills the circulating fluid on the secondary
1758 CHAPTER 1. INPUT-OUTPUT REFERENCE
side. Inputs that describe the evaporator performance at rated conditions are used to calculate the
heat exchanger effectiveness. These values include the rated evaporator capacity (which can be spec-
ified in terms of energy or fluid flow rate), the rated evaporating temperature, the rated approach
temperature difference, and the rated range temperature difference.
If the secondary fluid undergoes a partial phase change, the heat exchanger between the primary
and secondary systems functions as an evaporator on the primary side and as a condenser on the
secondary side. The evaporator capacity, evaporating temperature, and approach temperature dif-
ference, all at full-load design conditions, are input.
The balance of the secondary system object describes the pumping system. The pumping options
include a single constant speed pump, multiple constant speed pumps, or a variable frequency-drive
pump. The user can also keep track of distribution piping and receiver shell heat gains.
1.34.17.1 Inputs
Refrigeration:SecondarySystem ,
SecondaryMedLoop , !- Name
MedTempCaseList , !- Refrigerated Case or Walkin or CaseAndWalkInList Name
FluidAlwaysLiquid , !- Circulating Fluid Type
ProGly30Percent , !- Circulating Fluid Name
3.5E4 , !- Evaporator Capacity {W}
0.0021 , !- Evaporator Flow Rate for Secondary Fluid {M3/s}
-12.6, !- Evaporator Evaporating Temperature {C}
2.7, !- Evaporator Approach Temperature Difference {DeltaC}
4., !- Evaporator Range Temperature Difference {DeltaC}
3, !- Number of Pumps in Loop
.0023 , !- Total Pump Flow Rate {M3/s}
, !- Total Pump Power {W}
2.09E5 , !- Total Pump Head {Pa}
, !- PhaseChange Circulating Rate
1762 CHAPTER 1. INPUT-OUTPUT REFERENCE
Refrigeration:SecondarySystem ,
SecondaryLowLoop , !- Name
LowTempCaseList , !- Refrigerated Case or Walkin or CaseAndWalkInList Name
FluidPhaseChange , !- Circulating Fluid Type
R744 , !- Circulating Fluid Name
, !- Evaporator Capacity {W}
, !- Evaporator Flow Rate for Secondary Fluid {M3/s}
-39.2, !- Evaporator Evaporating Temperature {C}
2., !- Evaporator Approach Temperature Difference {DeltaC}
, !- Evaporator Range Temperature Difference {DeltaC}
3, !- Number of Pumps in Loop
, !- Total Pump Flow Rate {M3/s}
, !- Total Pump Power {W}
2.09E5 , !- Total Pump Head {Pa}
2.5, !- PhaseChange Circulating Rate
Variable , !- Pump Drive Type
SecondaryVarSpeedPump , !- Variable Speed Pump Cubic Curve Name
1.0, !- Pump Motor Heat to Fluid
10.4, !- Sum UA Distribution Piping {W/C}
SalesFloor , !- Distribution Piping Zone Name
1.4, !- Sum UA Receiver/Separator Shell
BackRoom , !- Receiver/Separator Zone Name
, !- Evaporator Refrigerant Inventory {kg}
; !- End -Use Subcategory
1.34.17.2 Outputs
1.34.17.2.17 Refrigeration Air Chiller Secondary Loop Load Heat Transfer Rate
[W]
This is the amount of refrigeration provided to the air chillers served by the secondary loop in W.
1.34. GROUP – REFRIGERATION 1765
1.34.17.2.18 Refrigeration Air Chiller Secondary Loop Load Heat Transfer En-
ergy [J]
This is the amount of refrigeration provided to the air chillers served by the secondary loop in Joules
for the timestep being reported.
1.34.17.2.19 Refrigeration Air Chiller Secondary Loop Total Heat Transfer Rate
[W]
This is the total amount of refrigeration load placed upon the primary refrigeration system (including
loads due to the air chillers plus the loads from the secondary loop pumps and any energy absorbed
by the loop via pipe heat gains) in W.
1.34.17.2.20 Refrigeration Air Chiller Secondary Loop Total Heat Transfer En-
ergy [J]
This is the total amount of energy placed upon the primary refrigeration system by the secondary
loop in Joules for the timestep being reported.
1.34.17.2.22 Refrigeration Air Chiller Secondary Loop Volume Flow Rate [m3/]s
This output is the calculated volume flow of coolant through the pumps for this secondary loop.
1.34.17.2.23 Refrigeration Air Chiller Secondary Loop Pipe Heat Gain Rate [W]
1.34.17.2.24 Refrigeration Air Chiller Secondary Loop Pipe Heat Gain Energy
[J]
This is the total heat transferred to the pipes in Joules for the timestep being reported.
1.34.17.2.26 Refrigeration Air Chiller Secondary Loop Receiver Heat Gain En-
ergy [J]
This is the total heat transferred to the receiver in Joules for the timestep being reported.
1766 CHAPTER 1. INPUT-OUTPUT REFERENCE
– Zone,Average, Refrigeration Zone Case and Walk In Sensible Cooling Rate [W]
– Zone,Sum, Refrigeration Zone Case and Walk In Sensible Cooling Energy [J]
– Zone,Average, Refrigeration Zone Case and Walk In Heating Rate [W]
– Zone,Sum, Refrigeration Zone Case and Walk In Heating Energy [J]
– Zone,Average, Refrigeration Zone Case and Walk In Total Sensible Cooling Rate [W]
– Zone,Sum, Refrigeration Zone Case and Walk In Total Sensible Cooling Energy [J]
– Zone,Average, Refrigeration Zone Case and Walk In Total Latent Cooling Rate [W]
– Zone,Sum, Refrigeration Zone Case and Walk In Total Latent Cooling Energy [J]
– Zone,Sum, Refrigeration Zone Case and Walk In Total Cooling Energy [J]
– Zone,Average,Refrigeration Zone Case and Walk In Total Cooling Rate [W]
– Zone,Average, Refrigeration Zone Case and Walk In Total Heat Transfer Rate [W]
– Zone,Sum, Refrigeration Zone Case and Walk In Total Heat Transfer Energy [J]
– HVAC,Average, Refrigeration Zone Air Chiller Sensible Heat Transfer Rate [W]
– HVAC,Sum, Refrigeration Zone Air Chiller Sensible Heat Transfer Energy [J]
– HVAC,Average, Refrigeration Zone Air Chiller Latent Cooling Rate [W]
– HVAC,Sum, Refrigeration Zone Air Chiller Latent Cooling Energy [J]
– HVAC,Average, Refrigeration Zone Air Chiller Total Cooling Rate [W]
– HVAC,Sum, Refrigeration Zone Air Chiller Total Cooling Energy [J]
1.34.19.2 Refrigeration Zone Case and Walk In Total Sensible Cooling Rate [W]
This output is the total sensible heat transfer between all refrigeration objects located in the zone in
Watts. A negative value will be reported when the refrigeration objects cool (that is, remove heat
from) the zone.
1.34. GROUP – REFRIGERATION 1767
Refrigeration Zone Case and Walk In Total Sensible Cooling Energy [J]
This is the total sensible heat transfer between all refrigeration objects located in the zone in Joules
for for the timestep being reported. A negative value will be reported when the refrigeration objects
cool (that is, remove heat from) the zone.
1.34.19.3 Refrigeration Zone Case and Walk In Total Latent Cooling Rate [W]
This output is the total latent heat transfer between all refrigeration objects located in the zone in
Watts. A negative value will be reported when the refrigeration equipment provides dehumidification
(thereby reducing the zone latent load).
Refrigeration Zone Case and Walk In Total Latent Cooling Energy [J]
This is the total latent heat transfer between all refrigeration objects located in the zone in Joules for
for the timestep being reported. A negative value will be reported when the refrigeration equipment
provides dehumidification (thereby reducing the zone latent load).
1.34.19.4 Refrigeration Zone Case and Walk In Total Heat Transfer Rate [W]
This output is the total heat transfer (sensible plus latent) between all refrigeration objects located
in the zone in Watts. A negative value will be reported when the refrigeration objects cool (that is,
remove heat from) the zone.
Refrigeration Zone Case and Walk In Total Heat Transfer Energy [J]
This is the total heat transfer (sensible plus latent) between all refrigeration objects located in the
zone in Joules for for the timestep being reported. A negative value will be reported when the
refrigeration objects cool (that is, remove heat from) the zone.
1.34.19.5 Refrigeration Zone Case and Walk In Sensible Cooling Rate [W]
This output is the total sensible cooling from all refrigeration objects located in the zone in Watts.
Refrigeration Zone Case and Walk In Sensible Cooling Energy [J]
This is the total sensible cooling from all refrigeration objects located in the zone in Joules for for
the timestep being reported.
This output is the total heating from all refrigeration objects located in the zone in Watts.
Refrigeration Zone Case and Walk In Heating Energy [J]
This is the total heating from all refrigeration objects located in the zone in Joules for for the timestep
being reported.
1.34.19.7 Refrigeration Zone Case and Walk In Total Cooling Rate [W]
This output is the total cooling (sensible plus latent) from all refrigeration objects located in the
zone in Watts.
Refrigeration Zone Case and Walk In Total Cooling Energy [J]
1768 CHAPTER 1. INPUT-OUTPUT REFERENCE
This is the total cooling (sensible plus latent) from all refrigeration objects located in the zone in
Joules for for the timestep being reported.
This output is the total heating from all air chillers located in the zone in Watts.
Refrigeration Zone Air Chiller Heating Energy [J]
This is the total heating from all air chillers located in the zone in Joules for for the timestep being
reported.
This output is the total sensible cooling from all air chillers located in the zone in Watts.
Refrigeration Zone Air Chiller Sensible Cooling Energy [J]
This is the total sensible cooling from all air chillers located in the zone in Joules for for the timestep
being reported.
1.34.19.11 Refrigeration Zone Air Chiller Sensible Heat Transfer Rate [W]
This output is the total sensible heat transfer from all air chillers located in the zone in Watts. A
negative value will be reported when the refrigeration objects cool (that is, remove heat from) the
zone.
1.34.19.12 Refrigeration Zone Air Chiller Sensible Heat Transfer Energy [J]
This is the total sensible heat transfer from all air chillers located in the zone in Joules for for the
timestep being reported. A negative value will be reported when the refrigeration objects cool (that
is, remove heat from) the zone.
This output is the total latent cooling from all air chillers located in the zone in Watts.
Refrigeration Zone Air Chiller Latent Cooling Energy [J]
This is the total latent cooling from all air chillers located in the zone in Joules for for the timestep
being reported.
This is the total amount of water removed by all air chillers located in the zone in kg/s for for the
timestep being reported.
1.34. GROUP – REFRIGERATION 1769
This output is the total cooling (sensible plus latent) from all air chillers located in the zone in
Watts.
Refrigeration Zone Air Chiller Total Cooling Energy [J]
This is the total cooling (sensible plus latent) from all air chillers located in the zone in Joules for
for the timestep being reported.
1.34.20 Refrigeration:AirChiller
The Refrigeration:AirChiller object works in conjunction with a refrigeration chiller set, com-
pressor rack, a refrigeration system, or a refrigeration secondary system object (Ref. Zone-
Hvac:RefrigerationChillerSet, and a Refrigeration:CompressorRack, Refrigeration:System, or
Refrigeration:SecondarySystem) to simulate the performance of an air chiller, similar to one found
in a refrigerated warehouse. The air chiller model uses information at rated conditions along with
the zone conditions to determine performance. Energy use for fans and heaters is modeled based on
inputs for nominal power, schedules, and control type. The refrigeration chiller model accounts for
the sensible and latent heat exchange with the surrounding environment.
The refrigeration chiller cooler object inputs include a name, an availability schedule name, the rated
cooling capacity, the rated operating temperature, the rated cooling source temperature, the rated
total heating power and heating power schedule, the rated fan power and schedules, defrost type,
defrost control type, defrost schedule name, drip-down schedule name, defrost power, the portion of
the defrost energy used to melt ice (only for temperature termination control type), and refrigerant
inventory.
Chiller coils are rated under multiple conventions. Each rating is typically based upon a selected fin
material and refrigerant cycle, with correction factors for other materials or refrigerants. Fields are
provided here for those correction factors. The performance of all chiller coils depends upon the inlet
air temperature, relative humidity, and flow rate. Multiple methods of expressing this relationship
are provided here to accommodate the way information is provided by different manufacturers.
1.34.20.1 Inputs
air temperature to the coil inlet air temperature. Refer to the Engineering Reference for further
information on how the different vertical locations are modeled.
Refrigeration:AirChiller ,
Freezer_1AirChiller_1 , !- Name
AvailAllYear , !- Availability Schedule Name
UnitLoadFactorSensibleOnly , !- Capacity Rating Type
10900. , !- Rated Unit Load Factor {W/deltaC}
, !- Rated Capacity {W}
, !- Rated Relative Humidity
-26., !- Rated Cooling Source Temperature {C}
8., !- Rated Temperature Difference DT1 {DeltaC}
11., !- Maximum Temperature Difference DT1 {DeltaC}
, !- Material Correction Factor
, !- Refrigerant Correction Factor
LinearSHR60 , !- Capacity Correction Curve Type
, !- Capacity Correction Curve Name
1.5, !- SHR60 Correction Factor {dimensionless}
200., !- Rated Total Heating Power {W}
AirChillerDripDownSched1 , !- Heating Power Schedule Name
, !- Fan Speed Control Type
375., !- Rated Fan Power {W}
12.4, !- Rated Air Flow {m3/s}
, !- Minimum Fan Air Flow Ratio
Electric , !- Defrost Type
TimeSchedule , !- Defrost Control Type
AirChillerDefrostSched1 , !- Defrost Schedule Name
AirChillerDripDownSched1 , !- Defrost Drip -Down Schedule Name
55066. , !- Defrost Power {W}
, !- Temperature Termination Defrost Fraction to Ice
, !- Vertical Location
; !- Average Refrigerant Charge Inventory {kg}
Refrigeration:AirChiller ,
Freezer_1AirChiller_1 , !- Name
AvailAllYear , !- Availability Schedule Name
UnitLoadFactorSensibleOnly , !- Capacity Rating Type
10900. , !- Rated Unit Load Factor {W/deltaC}
, !- Rated Capacity {W}
, !- Rated Relative Humidity
-26., !- Rated Cooling Source Temperature {C}
8., !- Rated Temperature Difference DT1 {DeltaC}
11., !- Maximum Temperature Difference DT1 {DeltaC}
, !- Material Correction Factor
, !- Refrigerant Correction Factor
LinearSHR60 , !- Capacity Correction Curve Type
, !- Capacity Correction Curve Name
1.5, !- SHR60 Correction Factor {dimensionless}
200., !- Rated Total Heating Power {W}
AirChillerDripDownSched1 , !- Heating Power Schedule Name
, !- Fan Speed Control Type
375., !- Rated Fan Power {W}
12.4, !- Rated Air Flow {m3/s}
, !- Minimum Fan Air Flow Ratio
Electric , !- Defrost Type
1.34. GROUP – REFRIGERATION 1775
1.34.20.2 Outputs
Report for each Zone exchanging energy with the Air Chiller