Out Put Details and Examples
Out Put Details and Examples
Out Put Details and Examples
0 Documentation
Build: 87ed9199d4
COPYRIGHT (c) 1996-2023 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 Introduction 7
2 Output Files 8
2.1 Output File List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.2 eplusout.audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.3 eplusout.bnd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2.4 eplusout.dbg . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
2.5 eplusout.dxf . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.6 eplusout.edd . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.7 eplusout.eio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.7.1 Simulation Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.7.2 Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.7.3 Timestep . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.7.4 SimulationControl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.7.5 Building . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.7.6 Inside Convection Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.7.7 Outside Convection Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.7.8 Solution Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.7.9 Sky Radiance Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.7.10 Site Atmospheric Variation . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.7.11 Shadowing/Sun Position Calculations . . . . . . . . . . . . . . . . . . . . . . 23
2.7.12 Daylighting:Illuminance Maps . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.7.13 Daylighting:Illuminance Maps:Detail . . . . . . . . . . . . . . . . . . . . . . 24
2.7.14 Enclosure/Window Adjacency Daylighting Counts . . . . . . . . . . . . . . . 24
2.7.15 Enclosure/Window Adjacency Daylighting Matrix . . . . . . . . . . . . . . . 25
2.7.16 Sky Daylight Factors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.7.17 AirflowNetwork Model:Control . . . . . . . . . . . . . . . . . . . . . . . . . 26
2.7.18 AirflowNetwork Model:Wind Direction . . . . . . . . . . . . . . . . . . . . . 26
2.7.19 AirflowNetwork Model:Wind Pressure Coefficients . . . . . . . . . . . . . . . 26
2.7.20 Zone Volume Capacitance Multiplier . . . . . . . . . . . . . . . . . . . . . . 27
2.7.21 Climate Group Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.7.22 Climate Group – Simple Outputs . . . . . . . . . . . . . . . . . . . . . . . . 30
2.7.23 Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.7.24 Site Water Mains Temperature . . . . . . . . . . . . . . . . . . . . . . . . . 30
2.7.25 Weather Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
2.7.26 Site Atmospheric Variation . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2
CONTENTS 3
Introduction
This document is intended to give an in-depth look at the various output files produced by En-
ergyPlus. Some of these may be referenced in various other parts of the documentation but are
presented here with more details.
The scripts that assist in running EnergyPlus will usually rename the standard names used in the
program. The two scripts that are distributed with EnergyPlus are: EPL-Run.bat (which is used
by the EP-Launch program) and RunEPlus.bat (which can be used from the command line). The
RunEPlus batch file can also be used to string together several runs such as usually termed “batch
processing”. In renaming the files created by the program or its post-processing program(s), usually
the file extension will be retained. The following table will illustrate the native EnergyPlus file name,
a description of its contents and the EP-Launch “version” of the file. In this table, <filename> refers
to the source/original file name (without extension) selected. Files are presented in alphabetic order.
For output purposes, the most important files to understand are the eplusout.eso, eplusout.mtr and
eplusout.err files. The first two are manipulated with the ReadVarsESO post processing program.
The latter will contain any critical errors that were encountered during the run.
7
Chapter 2
Output Files
8
2.1. OUTPUT FILE LIST 9
In addition to the basic output files from EnergyPlus there are three standard “hybrid” output
files. These are called “hybrid” because they are a result of post-processing after EnergyPlus has
completed. Note that if there is an error during processing, these will not normally be “complete”.
2.2. EPLUSOUT.AUDIT 11
Now, each file will be described in more detail with some examples of use.
2.2 eplusout.audit
This file is simply the echo of the inputs to the EnergyPlus program – the Energy+.idd (data
dictionary) and in.idf (<filename>.idf – the input data file). Every attempt has been made to not
require this file to be saved – errors are interpreted as much as possible and encapsulated onto
the eplusout.err file. Any errors in the data dictionary processing should be accomplished during
development – users should never see errors there. Thus, this file is not “saved” after processing by
the standard script file. Occasionally, you may wish to view this file because of something obscure.
An excerpt of the file follows. Lines in green are notes produced from EnergyPlus (some of
these are more useful to developers than users). Lines in red are lines with error messages shown
to illustrate context. The other lines are echoes from inputs (with line numbers).
In all the examples, the actual version of the EnergyPlus exe would appear. In the examples
these will be shown as: <version>.
Processing Data Dictionary (Energy +.idd) File -- Start
1 !IDD_Version <version >
2 ! **************************************************************************
3 !
<reduced for brevity >
13000 \key DETAILS
13001 \key Vertices
13002 \key DetailsWithVertices
Processing Data Dictionary (Energy +.idd) File -- Complete
Maximum number of Alpha Args= 4500
Maximum number of Numeric Args= 1800
Number of Object Definitions= 473
Number of Section Definitions= 2
Processing Input Data File (in.idf) -- Start
12 CHAPTER 2. OUTPUT FILES
2.3 eplusout.bnd
The “branch node details” (bnd) file is intended to give enough information that one could (with
a chosen software) diagram the nodes and components of the HVAC system. It may or may not
achieve that objective. Of more use may be its illustration of node connection/branch errors that
aren’t detected by the software. This file has the details to support any “node connection” errors
that will be noted in the eplusout.err file. Branch validation is shown in this file. Branches are
checked to assure that each output node of the branch element is an input node to the next branch
element. Cross-branch checking is not done directly within the program though the details will
illustrate some problems of that nature.
Supply and Return Air Paths are also checked and feedback about each item are shown.
As is standard with many EnergyPlus output files, this file is CSV (comma-delimited) such that
it can be read by spreadsheet programs for further manipulation by the user.
An example will illustrate. Notes about the reporting are highlighted in green.
Program Version,EnergyPlus, <version>
! This file shows details about the branches, nodes, and other
! elements of the flow connections.
! This file is intended for use in “debugging” potential problems
! that may also be detected by the program, but may be more easily
! identified by “eye”.
! This file is also intended to support software which draws a
! schematic diagram of the HVAC system.
! =====================================
==========================
! #Nodes,<Number of Unique Nodes>
2.3. EPLUSOUT.BND 13
#Nodes,11
List of all nodes follows. # references may be an indication of faulty node spec (or
not)
! <Node>,<NodeNumber>,<Node Name>,<Node Fluid Type>,<# Times Node Referenced
After Definition>
Node,1,SUPPLY INLET NODE,Air,3
Node,2,FAN INLET NODE,Air,4
<reduced for brevity>
Node,10,ZONE EQUIPMENT OUTLET NODE,Air,2
Node,11,RELIEF AIR OUTLET NODE,Air,1
! =====================================
==========================
! Suspicious nodes have 0 references. It is normal for some nodes, however.
! Suspicious nodes have 0 references. It is normal for some nodes, however.
! Listing nodes with 0 references (culled from previous list):
! <Suspicious Node>,<NodeNumber>,<Node Name>,<Node Fluid Type>,<# Times Node
Referenced After Definition>
Suspicious Node,7,MAIN ZONE NODE,Air,0
List of branches follow.
! <#Branch Lists>,<Number of Branch Lists>
#Branch Lists,1
! <Branch List>,<Branch List Count>,<Branch List Name>,<Loop Name>,<Loop
Type>,<Number of Branches>
! <Branch>,<Branch Count>,<Branch Name>,<Loop Name>,<Loop Type>,<Branch Inlet
Node Name>,<Branch Outlet Node Name>
Branch List,1,AIR LOOP BRANCHES,EVAP COOLER SYSTEM,Air,1
Branch,AIR LOOP MAIN BRANCH,EVAP COOLER SYSTEM,Air,SUPPLY INLET
NODE,SUPPLY OUTLET NODE
! =====================================
==========================
! <#Supply Air Paths>,<Number of Supply Air Paths>
! <#Supply Air Paths>,<Number of Supply Air Paths>
#Supply Air Paths,1
! <Supply Air Path>,<Supply Air Path Count>,<Supply Air Path Name>,<AirLoopHVAC
Name>
! <#Components on Supply Air Path>,<Number of Components>
! <Supply Air Path Component>,<Component Count>,<Component Type>,<Component
Name>,<AirLoopHVAC Name>
! <#Outlet Nodes on Supply Air Path Component>,<Number of Nodes>
! <Supply Air Path Component Nodes>,<Node Count>,<Component Type>,<Component
Name>,<Inlet Node Name>,<Outlet Node Name>,<AirLoopHVAC Name>
Supply Air Path,1,ZONE SUPPLY AIR PATH,EVAP COOLER SYSTEM
#Components on Supply Air Path,1
Supply Air Path Component,1,AIRLOOPHVAC:ZONESPLITTER,ZONE SUPPLY AIR
SPLITTER,EVAP COOLER SYSTEM
#Outlet Nodes on Supply Air Path Component,1
14 CHAPTER 2. OUTPUT FILES
! =====================================
==========================
Component sets. Very important for node connection error detection.
! <#Component Sets>,<Number of Component Sets>
#Component Sets,4
! <Component Set>,<Component Set Count>,<Parent Object Type>,<Parent Ob-
ject Name>,<Component Type>,<Component Name>,<Inlet Node ID>,<Outlet Node
ID>,<Description>
Component Set,1,BRANCH,AIR LOOP MAIN BRANCH,AIRLOOPHVAC:OUTDOORAIRSYSTEM,OU
AIR SYSTEM,SUPPLY INLET NODE,FAN INLET NODE,Air Nodes
Component Set,2,BRANCH,AIR LOOP MAIN BRANCH,FAN:CONSTANTVOLUME,SUPPLY
FAN,FAN INLET NODE,EVAP COOLER INLET NODE,Air Nodes
Component Set,3,BRANCH,AIR LOOP MAIN BRANCH,EVAPORATIVECOOLER:DIRECT:CELDEKP
COOLER,EVAP COOLER INLET NODE,SUPPLY OUTLET NODE,Evap Air Nodes
Component Set,4,AIRLOOPHVAC:OUTDOORAIRSYSTEM,OUTSIDE AIR SYS-
TEM,OUTDOORAIR:MIXER,OUTSIDE AIR MIXING BOX,OUTSIDE AIR INLET NODE,FAN
INLET NODE,Air Nodes
Similar details for Plant Loops, Condenser Loops, Controlled Zones, etc.
2.4 eplusout.dbg
Developers use this file during debugging and can be “turned on” by the DEBUG OUTPUT object
in the input file. The only reason a user might specify this flag would be to send a file to the support
group.
Output:DebuggingData, 1, 0; ! standard debug output, during simulation days
The standard debug output appears like this:
Day of Sim Hour of Day Time
1 1 0.166666666666667
node # Temp MassMinAv MassMaxAv TempSP MassFlow MassMin Mass-
Max MassSP Press Enthal HumRat Fluid Type
1 -12.500 0.000 0.000 0.000 0.0000 0.0000 0.0000 0.0000 100344.00 -
9363.63 0.00129 Air
2 -12.500 0.000 0.000 0.000 0.0000 0.0000 0.0000 0.0000 100344.00 -
9363.63 0.00129 Air
3 -12.500 0.000 0.000 0.000 0.0000 0.0000 0.0000 0.0000 100344.00 -
9363.63 0.00129 Air
4 -12.500 0.000 0.000 0.000 0.0000 0.0000 0.0000 0.0000 100344.00 -
9363.63 0.00129 Air
5 50.000 0.000 0.000 0.000 0.0320 0.0000 0.0000 0.0000 100344.00 60617.55 0.00400 Ai
6 50.000 0.000 0.000 0.000 0.0326 0.0000 0.0000 0.0000 100344.00 60617.55 0.00400 Ai
7 50.000 0.000 0.000 0.000 0.1636 0.0000 0.0000 0.0000 100344.00 60617.55 0.00400 Ai
8 50.000 0.000 0.000 0.000 0.1648 0.0000 0.0000 0.0000 100344.00 60617.55 0.00400 Ai
9 0.000 0.000 0.000 0.000 0.0000 0.0000 0.0000 0.0000 0.00 0.00 0.00000 blank
10 0.000 0.000 0.000 0.000 0.0000 0.0000 0.0000 0.0000 0.00 0.00 0.00000 blank
11 0.000 0.000 0.000 0.000 0.0000 0.0000 0.0000 0.0000 0.00 0.00 0.00000 blank
16 CHAPTER 2. OUTPUT FILES
12 0.000 0.000 0.000 0.000 0.0000 0.0000 0.0000 0.0000 0.00 0.00 0.00000 blank
2.5 eplusout.dxf
The DXF output report file is formatted according to the “Data Exchange Format” standard rules
for representing CADD type coordinates. The file can be used in several inexpensive, shareware
or freeware viewers. Quickview PlusTM can display DXF files as shown in Figure 2.1 below. A
free program originally from AutocadTM , Voloview ExpressTM , can display solid model rendering as
shown in Figure 2.2. Other viewers are available from MicrostationTM , VisioTM and other shareware
or freeware vendors.
This file is generated when the following line is included in the IDF.
Output:Surfaces:Drawing, DXF;
You can ask it to triangulate surfaces with >4 sides:
Output:Surfaces:Drawing, DXF, Triangulate3dface;
In addition to the building shape (including detached shading elements), the DXF view includes
a “true north” arrow (at ground level) and the name from the BUILDING object.
Even in the Quick View version, you can see that the different building elements have different
colors. These are the “original” colors used in EnergyPlus. The current default color scheme is
shown in the following figure of the solid model.
The DXF file of itself is an ASCII file, with a specific structure as specified in the standard. An
excerpt of the file is shown below:
2.5. EPLUSOUT.DXF 17
SECTION
2
ENTITIES
0
TEXT
8
1
6
CONTINUOUS
62
3
10
-11.00000
20
3.00000
30
0.10000
40
.25
1
True North
41
0.0
7
MONOTXT
210
0.0
220
0.0
230
1.0
0
3DFACE
8
1
62
3
10
-10.00000
20
3.00000
30
0.10000
11
-10.00000
21
3.00000
31
0.00000
12
-10.00000
22
0.00000
32
0.00000
13
-10.00000
23
0.00000
33
0.10000
0
ENDSEC
0
EOF
999
DXF created from EnergyPlus
999
2.6. EPLUSOUT.EDD 19
2.6 eplusout.edd
This file is invoked by including an Output:EnergyManagementSystem input object. The EDD
file contains three different types of information related to the Energy Management System (EMS)
including: (1) listing of available actuators, (2) listing of available internal variables, and (3) a
record of the execution of user’s programs for the EnergyPlus Runtime Language (Erl).
The EMS feature in EnergyPlus uses “Actuators” to do control operations. The actuators avail-
able in a given model depend on the non-EMS-related content of the input file. Similar to how
EnergyPlus reports the available output variables to the RDD file, a list of available actuators can
be written to the EDD file. There are three settings in the Output:EnergyManagementSystem input
object that control how actuators are listed. Selecting “None” directs the program to not list the
available actuators. Selecting “NotByUniqueKeyNames” directs the program to provide a concise
listing of the available actuators that does not include their enumeration by unique name. Selecting
“Verbose” directs the program to provide a complete listing of the available actuators including the
unique identifying names. An example listing of actuators using the “NotByUniqueKeyNames” op-
tion follows.
! <EnergyManagementSystem:Actuator Available>, *, Component Type, ’Control Type, Units
EnergyManagementSystem:Actuator Available, *,Schedule:Compact,Schedule Value,[ ]
EnergyManagementSystem:Actuator Available, *,People,Number of People,[each]
EnergyManagementSystem:Actuator Available, *,Lights,Electricity Rate,[W]
EnergyManagementSystem:Actuator Available, *,ElectricEquipment,Electricity Rate,[W]
EnergyManagementSystem:Actuator Available, *,Window Shading Control,Control Sta-
tus,[ShadeStatus]
EnergyManagementSystem:Actuator Available, *,Zone Temperature Control,Heating Set-
point,[C]
EnergyManagementSystem:Actuator Available, *,Zone Temperature Control,Cooling Set-
point,[C]
EnergyManagementSystem:Actuator Available, *,Surface,Interior Surface Convection Heat
Transfer Coefficient,[W/m2-K]
EnergyManagementSystem:Actuator Available, *,Surface,Exterior Surface Convection Heat
Transfer Coefficient,[W/m2-K]
EnergyManagementSystem:Actuator Available, *,Ideal Loads Air System,Air Mass Flow
Rate,[kg/s]
The EMS feature in EnergyPlus uses “Internal Variables” to obtain input data for use in scaling
the results of control calculations. The internal variables available in a give model depend on the
non-EMS-related content of the input file. Similar to how EnergyPlus reports the available output
variables to the RDD file, a list of available internal variables can be written to the EDD file. There
are three settings in the Output:EnergyManagementSystem input object that control how internal
variables are listed. Selecting “None” directs the program to not list the available internal variables.
Selecting “NotByUniqueKeyNames” directs the program to provide a concise listing of the available
internal variables that does not include their enumeration by unique name. Selecting “Verbose”
directs the program to provide a complete listing of the available internal variables including the
20 CHAPTER 2. OUTPUT FILES
unique identifying names. An example listing of actuators using the “NotByUniqueKeyNames” op-
tion follows.
! <EnergyManagementSystem:InternalVariable Available>, *, Internal Data Type
EnergyManagementSystem:InternalVariable Available, *,People Count Design Level,[each]
EnergyManagementSystem:InternalVariable Available, *,Lighting Power Design Level,[W]
EnergyManagementSystem:InternalVariable Available, *,Plug and Process Power Design
Level,[W]
EnergyManagementSystem:InternalVariable Available, *,Zone List Multiplier,[ ]
EnergyManagementSystem:InternalVariable Available, *,Zone Floor Area,[m2]
EnergyManagementSystem:InternalVariable Available, *,Zone Air Volume,[m3]
EnergyManagementSystem:InternalVariable Available, *,Zone Multiplier,[ ]
EnergyManagementSystem:InternalVariable Available, *,Zone List Multiplier,[ ]
The EMS uses the EnergyPlus Runtime Language, or Erl, to do custom controlling. When Erl
programs are being developed, the EDD becomes a primary source of information for debugging.
When a line of Erl code is executed, the program can output records called “line traces” that are
useful for debugging because they show the outcome of each line of code. There are three settings
in the Output:EnergyManagementSystem input object that control how line traces are reported.
Selecting “None” directs the program to not write out any line traces. Selecting “ErrorsOnly”
directs the program to only write line traces when computation errors are encountered (such as
divide by zero). Selecting “Verbose” directs the program to write out line traces for each and every
line of Erl program code that is executed.
It is very important to be careful with the EDD file. The Verbose option should be used with
care because a full line-by-line trace of Erl program execution for an annual run can easily create an
enormous computer file that is too large for most computer systems. It is possible for EnergyPlus
to generate an EDD file that cannot be opened in traditional text editors.
2.7 eplusout.eio
This file contains some standard and some optional “reports”. It is intended to be a somewhat
intelligent report of input conditions when they don’t fit well in other places or when they aren’t
substantial enough for their own “file”. (e.g. eplusout.bnd) Contents of the file are somewhat
documented in various places in the Input Output Reference document – as results of objects.
This file or portions of it can be easily imported into spreadsheet programs and more analysis
done there. Contents of this file include construction details, location information, site water mains
temperature information, “environment” information, number of “warmup” days required in each
environment.
The form of the file is a data dictionary line followed by the data. In this case, the data
dictionary line precedes the first “data” line though there may be several defining “dictionary
lines”. Each dictionary line will show the field as <field name> followed by other fields that will be
in the data lines. Data will be displayed similarly. Each field of dictionary or data will be separated
from the next by a comma “,” – and produce a comma delimited file. However, the lines for data
will not be contiguous – some follow a stream of consciousness of the EnergyPlus execution.
This section is subdivided into grouped sections by type.
Note that the lines in the eplusout.eio file can be extremely long (current limit is 500 characters).
2.7. EPLUSOUT.EIO 21
2.7.2 Version
! <Version>, Version ID
Version, <version>
This is the version of the IDF as entered in the IDF file. If it does not match the current
EnergyPlus Version, a warning will be issued and show in the eplusout.err file.
2.7.3 Timestep
! <Timesteps per Hour>, #TimeSteps, Minutes per TimeStep
Timesteps Per Hour, 4, 15
This is the number of timesteps in hour as entered in the IDF file as well as showing how many
minutes will encompass each timestep (i.e. 4 timesteps in hour = 15 minutes per timestep).
2.7.4 SimulationControl
! <Run Control>, Do Zone Sizing, Do System Sizing, Do Plant Sizing, Do Design Days, Do Weather
Simulation, Do HVAC Sizing Simulation
Run Control, Yes, Yes, Yes, No, Yes, No
This shows how the sizing and running (design days vs. weather file) will be accomplished.
Design days are required for sizing but do not necessarily need to be “run” after sizing has completed.
Thus, the user can choose to do sizing, not do a “normal” calculation with the design day definitions
but then go ahead and run the full simulation year. Some advanced sizing methods require also
running HVAC Sizing Simulations.
2.7.5 Building
! <Building Information>, Building Name,North Axis {deg},Terrain, Loads Convergence Toler-
ance Value,Temperature Convergence Tolerance Value, Solar Distribution,Maximum Number of
Warmup Days
Building Information, BUILDING, 30.000,City, 0.04000, 0.40000,FullExterior,25
This shows the values put in for the Building Object in the IDF.
This shows the global inside (interior) convection algorithm selected by the IDF value. This
may be overridden by zone entries or even surface entries.
overlap can be increased if necessary for the model. There are two calculation methods available:
AverageOverDaysInFrequency (default) and DetailedTimestepIntegration.
Note that in this display, using “weekend rule” and specific date holidays, the actual observed
dates are shown in the output display – in the example above, Independence Day (July 4) is actually
observed on July 5.
2.7.23 Location
This output represents the location data used for the simulation. Note that if a runperiod is used,
the IDF “Location” is ignored and the location from the weather file is used instead.
( )WindExponentmet (
WindBoundaryLayerThicknessmet HeightAboveGround
LocalWindSpeed = WindSpeedmet
AirSensorHeightmet WindBoundaryLayer
(2.1)
The Wind Speed Modifier Coefficient [Internal] simplifies the equation to:
32 CHAPTER 2. OUTPUT FILES
( )SiteWindExponent
HeightAboveGroundsite/component
LocalWindSpeed = WindSpeedmet (WindSpeedModifier)
WindBoundaryLayerThicknesssite
(2.2)
Where the Wind Speed Modifier encapsulates:
( )WindExponentmet
WindBoundaryLayerThicknessmet
WindSpeedModifier = (2.3)
AirSensorHeightmet
Where
2.7.32.2 Field Set (1-12) – Monthly Snow Ground Reflectances for Daylighting
There will be a set of 12 numbers – the ground reflectances by month: January, February, March,
April, May, June, July, August, September, October, November, December.
2.7. EPLUSOUT.EIO 35
2.7.35.2 Field:DayOfYear
This is the Julian day of year for the design day (i.e. Jan 1 is 1, Jan 31 is 31).
Like the ceiling height, this user can also enter this value in the IDF. Volume is also heuristically
calculated using the ceiling height (entered or calculated) as well as the calculated floor area (see
later field). If entered here, this value will be used rather than the calculated value. A minor
warning message will be issued if the calculated value is significantly different than the entered
value. Units are m3 .
The interior convection algorithm shown earlier (entire building) can be overridden for each zone
by an entry in the individual Zone object. This field will show which method is operational for the
zone.
This field is calculated from the floor surfaces entered for the zone. Units are m2 .
This field is calculated from the exterior wall surfaces entered for the zone. Units are m2 .
This field is calculated from the exterior wall surfaces entered for the zone. Any sub-surface area is
subtracted from the gross area to determine the net area. Units are m2 .
This field is calculated from the exterior window surfaces entered for the zone. Units are m2 .
This field is a count of the number of subsurfaces (windows, doors, glass doors and the list) in the
zone.
This field is a count of the number of shading surfaces (overhangs, fins) for the zone.
2.7. EPLUSOUT.EIO 41
People Internal Gains, SPACE5-1 PEOPLE 1, OCCUPY-1, SPACE5-1, 182.49, 20.0, 20.0,
0.110, 9.125, 0.300, 0.700, AutoCalculate, ACTSCHD, No, 3.8200E-008, 0, 20
This field shows the end-use category for this lights statement. Usage can be reported by end-use
category.
This numeric field is the calculated minimum amount of lighting in Watts based on the calculated
lighting level (above) * the minimum value (annual) for the lights schedule. It may be useful in
diagnosing errors that occur during simulation.
This numeric field is the calculated maximum amount of lighting in Watts based on the calculated
lighting level (above) * the maximum value (annual) for the lights schedule. It may be useful in
diagnosing errors that occur during simulation.
This field will contain the type of equipment internal gain in each line (i.e. Electric Equipment
Internal Gains, Gas Equipment Internal Gains, …).
This field contains the name of the equipment statement from the IDF file.
48 CHAPTER 2. OUTPUT FILES
2.7.50 Infiltration
! <Infiltration Airflow Stats - Nominal>,Name,Schedule Name,Zone Name, Zone Floor Area
{m2}, # Zone Occupants,Design Volume Flow Rate {m3/s},Volume Flow Rate/Floor Area
{m3/s/m2},Volume Flow Rate/Exterior Surface Area {m3/s/m2},ACH - Air Changes per
Hour,Equation A - Constant Term Coefficient {},Equation B - Temperature Term Coefficient
{1/C},Equation C - Velocity Term Coefficient {s/m}, Equation D - Velocity Squared Term
Coefficient {s2/m2}
ZoneInfiltration Airflow Stats, SPACE1-1 INFIL 1,INFIL-SCH,SPACE1-1,99.16,11.0,3.200E-
002,3.227E-004,4.372E-004,0.482,0.000,0.000,0.224,0.000
ZoneInfiltration Airflow Stats, SPACE2-1 INFIL 1,INFIL-SCH,SPACE2-1,42.74,5.0,1.400E-
002,3.276E-004,3.838E-004,0.488,0.000,0.000,0.224,0.000
ZoneInfiltration Airflow Stats, SPACE3-1 INFIL 1,INFIL-SCH,SPACE3-1,96.48,11.0,3.200E-
002,3.317E-004,4.372E-004,0.482,0.000,0.000,0.224,0.000
ZoneInfiltration Airflow Stats, SPACE4-1 INFIL 1,INFIL-SCH,SPACE4-1,42.74,5.0,1.400E-
002,3.276E-004,3.838E-004,0.488,0.000,0.000,0.224,0.000
ZoneInfiltration Airflow Stats, SPACE5-1 INFIL 1,INFIL-SCH,SPACE5-1,182.49,20.0,6.200E-
002,3.397E-004,N/A,0.499,0.000,0.000,0.224,0.000
[ ( )]
Infiltration = Idesign Fschedule A + B |Tzone − Todb | + C (WindSpeed) + D WindSpeed2 (2.8)
2.7.51 Ventilation
! <Ventilation Airflow Stats - Nominal>,Name,Schedule Name,Zone Name, Zone Floor Area
{m2}, # Zone Occupants,Design Volume Flow Rate {m3/s},Volume Flow Rate/Floor Area
{m3/s/m2},Volume Flow Rate/person Area {m3/s/person},ACH - Air Changes per Hour,Fan
Type {Exhaust;Intake;Natural/None},Fan Pressure Rise {?},Fan Efficiency {},Equation A -
Constant Term Coefficient {},Equation B - Temperature Term Coefficient {1/C},Equation
C - Velocity Term Coefficient {s/m}, Equation D - Velocity Squared Term Coefficient
{s2/m2},Minimum Indoor Temperature/Schedule,Maximum Indoor Temperature/Schedule,Delta
Temperature/Schedule,Minimum Outdoor Temperature/Schedule,Maximum Outdoor Tempera-
ture/Schedule,Maximum WindSpeed
Ventilation Airflow Stats, SPACE1-1 VENTL 1,NIGHTVENTSCHED,SPACE1-1,99.16,11.0,5.295E-
002,5.340E-004,4.814E-003,0.797,Intake,67.000,0.7,1.000,0.000,0.000,0.000,MININDOORTEMP,MAXINDOOR
Ventilation Airflow Stats, SPACE1-1 VENTL 2,NIGHTVENTSCHED,SPACE1-1,99.16,11.0,5.295E-
002,5.340E-004,4.814E-003,0.797,Intake,67.000,0.7,1.000,0.000,0.000,0.000,MININDOORTEMP,MAXINDOOR
Ventilation Airflow Stats, SPACE2-1 VENTL 1,NIGHTVENTSCHED,SPACE2-1,42.74,5.0,7.030E-
002,1.645E-003,1.406E-002,2.450,Intake,67.000,0.7,1.000,0.000,0.000,0.000,18.00,100.00,2.00,-
100.00,100.00,40.00
Ventilation Airflow Stats, RESISTIVE ZONE VENTL 1,INF-SCHED,RESISTIVE ZONE,37.16,3.0,2.000E-
002,5.382E-004,6.667E-003,0.636,Natural,0.000,1.0,0.606,2.020E-002,5.980E-004,0.000,18.00,100.00,1.00,-
100.00,100.00,40.00
Ventilation Airflow Stats, EAST ZONE VENTL 1,INF-SCHED,EAST ZONE,37.16,3.0,2.000E-
002,5.382E-004,6.667E-003,0.636,Natural,0.000,1.0,0.606,2.020E-002,5.980E-004,0.000,18.00,100.00,1.00,-
100.00,100.00,40.00
Ventilation Airflow Stats, NORTH ZONE VENTL 1,INF-SCHED,NORTH ZONE,55.74,4.0,2.000E-
002,3.588E-004,5.000E-003,0.424,Natural,0.000,1.0,0.606,2.020E-002,5.980E-004,0.000,18.00,100.00,1.00,-
100.00,100.00,40.00
[ ( )]
Ventilation = Vdesign Fschedule A + B |Tzone − Todb | + C (WindSpeed) + D WindSpeed2 (2.9)
2.7.52 Mixing
! <Mixing Airflow Stats - Nominal>,Name,Schedule Name,Zone Name, Zone Floor Area
{m2}, # Zone Occupants,Design Volume Flow Rate {m3/s},Volume Flow Rate/Floor
Area {m3/s/m2},Volume Flow Rate/person Area {m3/s/person},ACH - Air Changes per
Hour,From/Source Zone,Delta Temperature {C}
2.7. EPLUSOUT.EIO 57
NOTE: The resulting “Nominal U with film coefs” is only for comparison purposes with the
ASHRAE 90.1 requirements. Actual film coefficients are calculated during the simulation and are
dependent on several factors that may change during the simulation time period. It should be
noted that the Nominal U-values with film coefficients that are listed in this report do not account
for whether or not the surface in question is considered a ”semi-exterior” surface. For such ”semi-
exterior” surfaces, use the Nominal U-value without film coefficients listed and then factor in the
film coefficients for such surfaces listed in the literature (e.g., ASHRAE Standard 90.1). For surfaces
that use Other Side Coefficients, the exterior film coefficient that is used in this calculation is based
on the value entered by the user in the Other Side Coefficients input.
When surfaces are entered, the gross area of the surface is calculated from the vertices (except for
Internal Mass where it is entered directly). As net area is needed in the calculations, any sub-
surfaces to the primary surface are subtracted from the original gross area. This field will show the
final “net” area for the surface. For example, walls with windows will have the multiplier (of the
window) * window area subtracted from the gross amount. Likewise, any divider area (including
multipliers) for the window will be subtracted. Units for this field are m2 .
This field shows the gross area of the surface. Units for this field are m2 .
This field shows the net area for the purposes of sunlit/shading calculations. For these, only 1 unit
of a multiplied window/door is subtracted from the gross area of a wall that the window/door is
on. This net area includes the frame area (if any) for the windows on the wall. For windows, this
value includes the divider area of the window. Thus for both frames and dividers, there will be a *
in this field – since the areas are included in the wall/window areas. Units for this field are m2 .
Using the specified vertices for the surface (and order of entry), EnergyPlus can determine the
outward facing normal angle for the surface. That angle is displayed in this field. Units for this
field are degrees.
2.7. EPLUSOUT.EIO 65
user, it will display User Supplied Value. The standard values may also be displayed here (e.g.
ASHRAEDetailed).
2.7.59.6 Field: Coefficient modifying the external dry bulb temperature term
This field defines a constant coefficient that is applied to the outdoor air dry-bulb temperature.
This parameter is shown as C3 in the equation. This parameter is dimensionless.
2.7. EPLUSOUT.EIO 71
transfer functions labeled “Outside” and “Cross” to calculate the heat flux at the outside surface.
Inside and outside coefficients will be identical for symmetric walls.
Conduction through constructions such as walls, roofs, floors, etc. is generally characterized as
one-dimensional and transient within EnergyPlus. The solution to this partial differential equation
results in “conduction transfer functions” or CTFs. In a CTF equation, the current heat transfer flux
due to conduction through a construction is a function of the current temperature at either face of
the surface as well as the history of temperatures at either face and the history of conductive fluxes
at this face. CTFs are a simplification of response factors which are based solely on temperature
histories and require an “infinite” history. The inclusion of heat flux history terms reduces the
overall number of terms in the equation for conductive flux significantly, resulting in a more efficient
solution.
For each unique combination of materials, there are a unique set of CTFs. While there are other
procedures to determine the CTFs for a particular construction, EnergyPlus uses a state-space
method (see conduction transfer function documentation) to obtain the CTF coefficients. These
coefficients are calculated once at the beginning of the simulation and are constant for a particular
construction. The CTF equation itself is a linear equation with these constant coefficients.
Conduction heat transfer flux at the outside face of a particular surface is a function of the
construction of the surface (which leads to the CTF coefficients), the current and previous temper-
atures at both the inside and outside face of the surface, and the previous conduction heat transfer
fluxes at the outside surface. The CTF coefficients that would be used in this equation would be the
“Outside” (multiplied by the temperature history at the outside face) terms, the “Cross” (multiplied
by the temperature history at the inside face) terms, and the “Flux” (multiplied by the flux history
at the outside face) terms. Solving for the conductive flux at the inside surface would require the
use of the “Inside” (multiplied by the temperature history at the inside face) terms, the “Cross”
(multiplied by the temperature history at the outside face) terms, and the “Flux” (multiplied by
the flux history at the inside face) terms. A textual example is given below for illustration purposes:
Current Outside Conductive Flux = (Outside Term 0) * (Current Outside Face Temperature)
+(Outside Term 1) * (Previous Outside Face Temperature)
+(Outside Term 2) * (Outside Face Temperature 2 Time Steps Ago)
+(Outside Term 3) * (Outside Face Temperature 3 Time Steps Ago)
+…
+(Cross Term 0) * (Current Inside Face Temperature)
+(Cross Term 1) * (Previous Inside Face Temperature)
+(Cross Term 2) * (Inside Face Temperature 2 Time Steps Ago)
+(Cross Term 3) * (Inside Face Temperature 3 Time Steps Ago)
+…
+(Flux Term 1) * (Previous Outside Face Flux)
+(Flux Term 2) * (Outside Face Flux 2 Time Steps Ago)
+(Flux Term 3) * (Outside Face Flux 3 Time Steps Ago)
+…
The number of terms is based on the CTF coefficient calculation routine and is related to
the amount of thermal mass contained within a particular construction. Actual signs (positive or
negative) of various terms in the preceding equation will vary based on their definition and use
within the equation. Those interested in more details on the use and calculation of CTFs are
encouraged to read the Engineering Documentation.
76 CHAPTER 2. OUTPUT FILES
! <WindowMaterial:Glazing >, Material Name , Optical Data Type , Spectral Data Set Name , Thickness {m},
Solar Transmittance ,Front Solar Reflectance , Back Solar Reflectance , Visible Transmittance , Front
Visible Reflectance ,Back Visible Reflectance ,Infrared Transmittance , Front Thermal Emissivity , Back
Thermal Emissivity ,Conductivity {W/m-K},Dirt Factor ,Solar Diffusing
WindowMaterial:Glazing ,GLASS - CLEAR SHEET 1 / 8 IN ,SpectralAverage ,, 0.00300 , 0.83700 , 0.07500 , 0.07500 ,
0.89800 , 0.08100 , 0.08100 , 0.00000 , 0.84000 , 0.84000 , 0.90000 , 1.00000 , No
! <WindowMaterial:Gas >,Material Name ,GasType ,Thickness {m}
WindowMaterial:Gas ,WINAIRB1 - AIRSPACE RESISTANCE ,Air , 1.300E-02
! <WindowMaterial:Shade >,Material Name ,Thickness {m},Conductivity {W/m-K},ThermalAbsorptance ,
Transmittance ,VisibleTransmittance , ShadeReflectance
WindowMaterial:Shade ,SHADE ROLL - LIGHT OPAQUE , 0.003 , 1.000E-01, 0.900 , 0.050 , 0.050 , 0.500
! <WindowMaterial:Screen >,Material Name ,Thickness {m},Conductivity {W/m-K},ThermalAbsorptance ,
Transmittance ,Reflectance ,VisibleReflectance ,DiffuseReflectance ,DiffuseVisibleReflectance ,
ScreenMaterialDiameterToSpacingRatio , ScreenToGlassDistance {m}
WindowMaterial:Screen ,BRIGHT ALUMINUM SCREEN 1, 0.00025 , 2.210E+02, 0.272 , 0.697 , 0.166 , 0.166 , 0.195 ,
0.195 , 0.165 , 0.025
! <WindowMaterial:Blind >,Material Name ,SlatWidth {m},SlatSeparation {m},SlatThickness {m},SlatAngle {deg
},SlatBeamSolarTransmittance ,SlatBeamSolarFrontReflectance , BlindToGlassDistance {m}
WindowMaterial:Blind ,INTERIOR BLIND , 0.0010 , 0.0022 , 0.0010 , 0.000 , 0.000 , 0.200 , 0.025
2.7. EPLUSOUT.EIO 77
2.7.62.14 WindowMaterial:Glazing
2.7.62.15 Field: <WindowMaterial:Glazing>
This will be filled with the constant “WindowMaterial:Glazing” for each material of this type in
the construction.
2.7.62.29 WindowMaterial:Gas
2.7.62.30 Field: <WindowMaterial:Gas>
This will be filled with the constant “WindowMaterial:Gas” for each material of this type in the
construction.
80 CHAPTER 2. OUTPUT FILES
2.7.62.34 WindowMaterial:Shade
2.7.62.35 Field: <WindowMaterial:Shade>
This will be filled with the constant “WindowMaterial:Shade” for each material of this type in the
construction.
2.7.62.43 WindowMaterial:Blind
This will be filled with the constant “WindowMaterial:Blind” for each material of this type in the
construction.
2.7.62.53 WindowMaterial:Screen
2.7.62.54 Field: <WindowMaterial:Screen>
This will be filled with the constant “WindowMaterial:Screen” for each material of this type in the
construction.
Then, there will be a list of window constructions reported with each one corresponding to
a particular temperature of the thermochromic glazing layer. For example, the following excerpt
shows a list of window constructions for the thermochromic window TCWINDOW at different
temperature of the thermochromic layer - TCWINDOW_TC_25 at 25°C, TCWINDOW_TC_27
at 27°C, and TCWINDOW_TC_29 at 29°C. Detailed properties of the thermochromic glazing layer
are also listed for each temperature - WO18RT25 at 25°C, WO18RT27 at 27°C, and WO18RT29
at 29°C.
WindowConstruction ,TCWINDOW\_TC\_25 ,~~ 5,VerySmooth ,~~ 1.666 ,~~ 1.666 ,~~ 1.000 ,~~ 0.429 ,~~ 0.242 ,~~ 0.520
WindowMaterial:Glazing ,CLEAR3PPG ,Spectral ,CLEAR3PPGSP ,~ 0.00328 ,~ 0.00000 ,~ 0.00000 ,~ 0.00000 ,~ 0.00000 ,~
0.00000 ,~ 0.00000 ,~ 0.00000 ,~ 0.84000 ,~ 0.84000 ,~ 1.00000 ,~ 1.00000 , No
84 CHAPTER 2. OUTPUT FILES
be able to meet any load or change in load no matter how large or abrupt. In reality air flow rates
are limited by duct sizes and fan capacities. The idealized zone design flow calculation may result
in unrealistically large flow rates, especially if the user is performing the sizing calculations using
thermostat schedules with night setup or setback. The calculated zone design flow rates are always
averaged over the load timestep. The user may want to perform a broader average to mitigate
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 windowto 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.
System Sizing Information, VAV SYS 1, User Heating Design Air Flow Rate [m3/s], 0.43343
2.7.69.1 Field:
This field simply contains the words “Plant Sizing Coincident Flow Algorithm.”
This field contains the nominal cooling coil surface area in square meter.
Note: values labeled “Nominal” are calculated using the rated inlet conditions: inlet air dry
bulb temperature = 26.67C, inlet air wet bulb temperature = 19.44C, inlet chilled water temperature
= 6.67C.
Refrigerated Cases, and Orphaned Refrigerated Case) followed by the information associated with
each description.
A final set of “header” records and descriptions are output only when a refrigeration object is
found in the IDF but is not connected to a refrigeration compressor rack or refrigeration system
object (i.e., orphaned).
The following fields define each description and associated information.
The number of the orphaned refrigerated case found in the IDF. The refrigerated case numbers are
assigned sequentially according to the order in which these objects are defined in the IDF.
The name of the orphaned refrigerated case which is not connected to a compressor rack or detailed
refrigeration system. Echoes the field Name in object Refrigeration:Case from the IDF.
The name of the zone where the refrigerated case is located. Echoes the field Zone Name in object
Refrigeration:Case from the IDF.
The number of the zone node (connection to the air loop) where the refrigerated case is located.
This is the number of the zone node as found in the eplusout.bnd file.
The name of the zone node where the orphaned refrigerated case is located. This orphaned refrig-
erated case will not impact the air heat balance in this zone.
This triggers EnergyPlus to produce a special output section in the file eplusout.eio. This file,
which is csv format, can be opened in Excel, and will show detailed information about the surfaces
in all the zones.
In order to get user view factors ready for inclusion in an input file, several steps much be taken.
First, because EnergyPlus has a data structure for zones that only is defined at initialization, it is
necessary to use EnergyPlus to determine the surface numbers (i,j) before a UserViewFactors object
can be constructed. (This is a known defect – a new object is being defined that will make this
unnecessary). THIS STILL NEEDS TO BE REVISED BASE ON IF WE GO FOR NEW INPUT
OR NOT.
! <Surface View Factor and Grey Interchange Information>
! <View Factor - Zone Information>,Zone Name,Number of Surfaces
! <View Factor - Surface Information>,Surface Name,Surface Class,Area {m2},Azimuth,Tilt,Thermal
Emissivity,#Sides,Vertices
! <View Factor / Grey Interchange Type>,Surface Name(s)
! <View Factor>,Surface Name,Surface Class,Row Sum,View Factors for each Surface
Surface View Factor - Zone Information,ZONE ONE,6
Surface View Factor - Surface Information, ZN001:WALL001,Wall,69.6773,180.0000,90.0000,0.9000,4,
0.0000,0.0000,4.5720,0.0000,0.0000,0.0000,15.2400,0.0000,0.0000,15.2400,0.0000,4.5720,
Surface View Factor - Surface Information,ZN001:WALL002,Wall,69.6773,90.0000,90.0000,0.9000,4,
15.2400,0.0000,4.5720,15.2400,0.0000,0.0000,15.2400,15.2400,0.0000,15.2400,15.2400,4.5720,
Surface View Factor - Surface Information,ZN001:WALL003,Wall,69.6773,0.0000,90.0000,0.9000,4,
15.2400,15.2400,4.5720,15.2400,15.2400,0.0000,0.0000,15.2400,0.0000,0.0000,15.2400,4.5720,
Surface View Factor - Surface Information,ZN001:WALL004,Wall,69.6773,270.0000,90.0000,0.9000,4,
0.0000,15.2400,4.5720,0.0000,15.2400,0.0000,0.0000,0.0000,0.0000,0.0000,0.0000,4.5720,
Surface View Factor - Surface Information,ZN001:FLR001,Floor,232.2576,90.0000,180.0000,0.9000,4,
15.2400,0.0000,0.0000,0.0000,0.0000,0.0000,0.0000,15.2400,0.0000,15.2400,15.2400,0.0000,
Surface View Factor - Surface Information,ZN001:ROOF001,Roof,232.2576,180.0000,0.0000,0.9000,4,
0.0000,15.2400,4.5720,0.0000,0.0000,4.5720,15.2400,0.0000,4.5720,15.2400,15.2400,4.5720,
Approximate or User Input ViewFactors,To Surface,Surface Class,RowSum,ZN001:WALL001,ZN001:WALL
View Factor,ZN001:WALL001,Wall,1.0000,0.0000,0.1034,0.1034,0.1034,0.3448,0.3448,
View Factor,ZN001:WALL002,Wall,1.0000,0.1034,0.0000,0.1034,0.1034,0.3448,0.3448,
View Factor,ZN001:WALL003,Wall,1.0000,0.1034,0.1034,0.0000,0.1034,0.3448,0.3448,
View Factor,ZN001:WALL004,Wall,1.0000,0.1034,0.1034,0.1034,0.0000,0.3448,0.3448,
View Factor,ZN001:FLR001,Floor,1.0000,0.1364,0.1364,0.1364,0.1364,0.0000,0.4545,
View Factor,ZN001:ROOF001,Roof,1.0000,0.1364,0.1364,0.1364,0.1364,0.4545,0.0000,
Final ViewFactors,To Surface,Surface Class,RowSum,ZN001:WALL001,ZN001:WALL002,ZN001:WALL003
View Factor,ZN001:WALL001,Wall,1.0000,0.0000,0.1034,0.1034,0.1034,0.3448,0.3448,
View Factor,ZN001:WALL002,Wall,1.0000,0.1034,0.0000,0.1034,0.1034,0.3448,0.3448,
View Factor,ZN001:WALL003,Wall,1.0000,0.1034,0.1034,0.0000,0.1034,0.3448,0.3448,
View Factor,ZN001:WALL004,Wall,1.0000,0.1034,0.1034,0.1034,0.0000,0.3448,0.3448,
View Factor,ZN001:FLR001,Floor,1.0000,0.1364,0.1364,0.1364,0.1364,0.0000,0.4545,
View Factor,ZN001:ROOF001,Roof,1.0000,0.1364,0.1364,0.1364,0.1364,0.4545,0.0000,
Script F Factors,X Surface,ZN001:WALL001,ZN001:WALL002,ZN001:WALL003,ZN001:WALL004,ZN001:F
Script F Factor,ZN001:WALL001,1.1191E-002,9.4126E-002,9.4126E-002,9.4126E-002,0.3032,0.3032,
Script F Factor,ZN001:WALL002,9.4126E-002,1.1191E-002,9.4126E-002,9.4126E-002,0.3032,0.3032,
Script F Factor,ZN001:WALL003,9.4126E-002,9.4126E-002,1.1191E-002,9.4126E-002,0.3032,0.3032,
2.7. EPLUSOUT.EIO 119
Script F Factor,ZN001:WALL004,9.4126E-002,9.4126E-002,9.4126E-002,1.1191E-002,0.3032,0.3032,
Script F Factor,ZN001:FLR001,0.1199,0.1199,0.1199,0.1199,3.4097E-002,0.3863,
Script F Factor,ZN001:ROOF001,0.1199,0.1199,0.1199,0.1199,0.3863,3.4097E-002,
includes the supply fan power as well. The total electric power input is reported for class I, II, III
and IV test conditions.
! <DX Heating Coil Standard Rating Information >, Component Type , Component Name , High Temperature Heating
Standard (Net) Rating Capacity {W}, Low Temperature Heating Standard (Net) Rating Capacity {W}, HSPF
{Btu/W-h, Region Number
DX Heating Coil Standard Rating Information , Coil:Heating:DX:SingleSpeed , PSZ -AC\_1:1\ _HEATC DXCOIL ,
10476.1 , 5833.2 , 6.10, 4
2.7.78.3 Field: High Temperature Heating Standard (Net) Rating Capacity {W}
The standard rating (net) heating capacity for this DX heating coil at high temperature. Units
are Watts. See the EnergyPlus Engineering Reference (Single Speed DX Heating Coil, Standard
Ratings) for details on how this value is calculated.
2.7.78.4 Field: Low Temperature Heating Standard (Net) Rating Capacity {W}
The standard rating (net) heating capacity for this DX heating coil at low temperature. Units
are Watts. See the EnergyPlus Engineering Reference (Single Speed DX Heating Coil, Standard
Ratings) for details on how this value is calculated.
..Max Temp Comparison = 8.46E -005 vs Temperature Convergence Tolerance = 0.40 - Pass Convergence
..Min Temp Comparison = 7.05E -002 vs Temperature Convergence Tolerance = 0.40 - Pass Convergence
..Max Heat Load Comparison = 9.8513E -002 vs Loads Convergence Tolerance = 4.00E -002 - Fail Convergence
..Max Cool Load Comparison = 8.2481E -003 vs Loads Convergence Tolerance = 4.00E -002 - Pass Convergence
2.7. EPLUSOUT.EIO 125
Warmup Convergence Information ,PLENUM -1, RunPeriod: Chicago Ohare Intl Ap IL USA TMY3 WMO# =
725300 ,0.1459548118 ,7.6866834879E-002,Pass ,Pass ,6.4148162842E -002 ,0.1344412193 , Pass ,Pass
Warmup Convergence Information ,SPACE1 -1, RunPeriod: Chicago Ohare Intl Ap IL USA TMY3 WMO# =
725300 ,0.1205887641 ,0.2962564087 , Pass ,Pass ,0.6840608138 ,3.7598304674 , Pass ,Pass
Warmup Convergence Information ,SPACE2 -1, RunPeriod: Chicago Ohare Intl Ap IL USA TMY3 WMO# =
725300 ,0.1494584750 ,0.4540146507 , Pass ,Pass ,0.7552649309 ,3.0925096445 , Pass ,Pass
Warmup Convergence Information ,SPACE3 -1, RunPeriod: Chicago Ohare Intl Ap IL USA TMY3 WMO# =
725300 ,0.1150550710 ,0.2873890950 , Pass ,Pass ,7.0443709912 ,61.6558566585 , Pass ,Pass
Warmup Convergence Information ,SPACE4 -1, RunPeriod: Chicago Ohare Intl Ap IL USA TMY3 WMO# =
725300 ,0.1153798692 ,0.4838241280 , Pass ,Pass ,2.4744275587 ,18.1154149427 , Pass ,Pass
Warmup Convergence Information ,SPACE5 -1, RunPeriod: Chicago Ohare Intl Ap IL USA TMY3 WMO# =
725300 ,0.1208173250 ,0.2114200039 , Pass ,Pass ,0.4984428726 ,2.8997025264 , Pass ,Pass
2.8 eplusout.end
This is a simple one line synopsis of the simulation. Successful or Not Successful, including number
of errors/warnings:
EnergyPlus Completed Successfully -- 8 Warning; 0 Severe Errors
If no file is produced, it is really not successful and EnergyPlus has probably crashed during
the run. This file and its contents are intended for interfaces that will put friendly front-ends onto
EnergyPlus. This file is also used by the EP-Launch program so that it can determine if the run was
successful or not – if not, the user should review the eplusout.err file. (Actually, the eplusout.err
file should always be reviewed but often is ignored in haste to view the results.)
2.9 eplusout.epmidf
If you use an EPMacro file (usual extension is .imf) as your basis for input, then this file is the “idf”
that the EPMacro program produces.
2.10 eplusout.epmdet
If you use an EPMacro file (usual extension is .imf) as your basis for input, then this file is the
details of the EPMacro run (including any error messages).
2.11 eplusout.err
This file is very important to every simulation run. All of the warnings, errors, etc that occur during
the run will show up in this file. They may show up in other files as well. The first line of the error
file is also significant:
Program Version ,EnergyPlus , <version >,IDD_Version <version >
This shows not only the current version of the program but the “version” of the Energy+.idd
file that was used.
128 CHAPTER 2. OUTPUT FILES
The previous table illustrates the three levels of errors that occur in the eplusout.err file. Several
other message lines may be shown as well. For example:
** Warning ** World Coordinate System selected. Any non -zero Building/Zone North Axes or non -zero Zone
Origins are ignored.
** ~~~ ** These may be used in daylighting reference point coordinate calculations but not in normal
geometry inputs.
The line that includes the “~~~” is a “continue” error line. It continues from the previous line
to help describe the context of the error.
Some common errors, their consequences, and what to do about them follows:
** Severe ** IP: Possible incorrect IDD File
** Fatal ** IP: Errors occurred on processing IDF file. Preceding condition(s) cause termination.
The previous errors cause program termination. The most likely cause is that you have an “old”
IDF and have not converted it to work with the current version of the program. In this case, you
will likely has some other hints such as alphas in numeric fields or too many fields in an object.
Energyplus also has built in range checking:
** Severe ** Out of range value Numeric Field #7 (Sky Clearness), value = 100.00000 , range = {> = 0.0 and
< = 1.2}, in SIZINGPERIOD:DESIGNDAY = CHICAGO ANN CLG .4% CONDNS WB = >MDB
If these occur during the initial processing of the IDF, you will see a termination clause:
** Severe ** IP: Out of "range" values found in input
** Severe ** IP: Out of "range" values and/or blank required fields found in input
** Fatal ** IP: Errors occurred on processing IDF file. Preceding condition(s) cause termination.
The error message should supply you with enough information to find the line with the error.
More details on error message formatting and some standard error messages are described in the
Tips & Tricks document.
2.12 eplusout.eso
The standard output file from EnergyPlus. It includes all the applicable variables selected with the
“Output:Variable” commands as well as those with the “Output:Meter” commands. All levels of
frequency of reporting are included intermingled as occurs in the running of the program. The form
of the file is a data dictionary, followed by the data.
In this case, the dictionary portion of the file comes first followed by an “end of data dictionary
line” and then the data makes up the rest of the file.
2.12. EPLUSOUT.ESO 129
As with the IDF structure, there are rules associated with the interpretation of the standard
output data dictionary. These rules are summarized as follows:
• The first item on each line is an integer which represents the “report code”. This “report code”
will be listed in the data section where it will also be the first item on each line, identifying
the data. Only 2 lines in the output file will not have an integer as the first item (“End of
Data Dictionary” and “End of Data” lines).
• The second item on each line is also an integer. This integer corresponds to the number of
items left on the dictionary line. Each string consists of a variable name and units in square
brackets. Square brackets are required for all strings. If there are no units associated with a
particular variable, then there are no characters between the brackets.
Six standard items appear at the start of every EnergyPlus Standard Output File Data Dictio-
nary:
Program Version ,EnergyPlus <version number indicated >
1,5, Environment Title[], Latitude[deg],Longitude[deg],Time Zone[], Elevation[m]
2,6,Day of Simulation [],Month[],Day of Month[],DST Indicator [1 = yes 0 = no],Hour[], StartMinute [],
EndMinute [], DayType
3,3, Cumulative Day of Simulation [],Month[],Day of Month[],DST Indicator [1 = yes 0 = no],DayType ! When
Daily Report Variables Requested
4,2, Cumulative Days of Simulation [],Month [] ! When Monthly Report Variables Requested
5,1, Cumulative Days of Simulation [] ! When Run Period Report Variables Requested
This example illustrates the non-consecutive nature of the “report codes”. Internally, EnergyPlus
counts each variable that *could* be reported. This is the assigned “report code”. However, the user
may not request each possible variable for reporting. Note that, currently, the requested reporting
frequency is shown as a comment (!) line in the standard output file.
The data is produced when the actual simulation is performed (after the warmup days unless the
Output:Diagnostics requesting ReportDuringWarmup is used). Data output is simpler in format
than the data dictionary lines. From the dictionary above:
130 CHAPTER 2. OUTPUT FILES
This output file can be easily turned into a form that is read into commonly used spreadsheet
programs where it can be further analyzed, graphed, etc.
Each report variable (ref: eplusout.rdd) is assigned an identification number, as in the line:
486,2, NORTH ZONE ,Zone Air Temperature [C] !Hourly
#486 is the id number of the Zone/Sys Air Temperature value for the North Zone.
2 – is the number of parameters on the line
North Zone – the identifying “key name” for the line
Zone Air Temperature [C] – the actual report variable name along with units [C]
! Hourly – the ! is the standard comment character, information following this character
reminds the user how frequently this data will appear in the following.
As another example:
Each Output:Variable object causes a specific number assignment for outputs. For example,
you could request separate reporting for the outside temperature:
Output:Variable ,*, Site Outdoor Air Drybulb Temperature ,timestep;
Output:Variable ,*, Site Outdoor Air Drybulb Temperature ,hourly;
Output:Variable ,*, Site Outdoor Air Drybulb Temperature ,monthly;
Item # 6 will be listed following the TimeStep timestamp for each timestep. Item #7 will be
listed following an hourly timestamp. And item #8 will be listed following a monthly timestamp
and has additional fields (because it is an “average” variable) that show the minimum and maximum
values with identifying times for those minimum and maximum. An excerpt will illustrate:
2, 1, 7,21, 0, 1, 0.00 ,15.00 , Monday ** – timestep timestamp **
6 ,17.08889
48 ,21.39851
49 ,0.0000000E+00
53 ,0.0000000E+00
60 ,21.87214
2, 1, 7,21, 0, 1, 0.00 ,60.00 , Monday ** – hourly timestamp **
7 ,16.75555
4, 1, 7** – monthly timestamp **
8 ,22.77037 ,15.00000 ,21 , 4 ,60 ,32.77778 ,21 ,14 ,60
132 CHAPTER 2. OUTPUT FILES
To interpret, the first value (#6) is 17.09 C, #7 is 16.76 C (average for the hour), and #8 is
22.77 C, the average for the month with the low (minimum) of 15 C occurring on 7/21 4:60 (or
5:00) and the high (maximum) occurring on 7/21 14:60 (or 15:00).
2.13 eplusout.mtd
This file contains the “meter details” for the run. This shows what report variables are on which
meters and vice versa – which meters contain what report variables.
The meter details file consists of two parts:
• For report variables that are on meters, it shows all the meters that the report variable is
on. In the following example, “Meters for ” <report variable #>, <report variable name>
is shown and then the meters that accumulate the value of that variable as a “meter”.
• For each meter, the report variables that make up that meter are shown. In the following
example, “For Meter = ” <name of meter>, “contents are:” and then each variable that
occurs on that “meter” are shown.
This shows the meters on which the Zone: Lights Electric Energy appear as well as the contents
of the Electricity:Facility meter.
134 CHAPTER 2. OUTPUT FILES
2.14 eplusout.mtr
This is the equivalent file to the eplusout.eso file but contains only the Report Meter requests. The
format and style of the file is identical to the eplusout.eso file.
2.15 eplusout_perflog.csv
An output file ending with _perflog.csv is created whenever the PerformancePrecisionTradeoffs
object is present. This log file consists of echoing the settings in the PerformancePrecisionTradeoffs
object, some overall building energy results, the runtime of the simulation, oscillation outputs, and
the number of warning and severe messages. The _perflog.csv file is appended to instead of replaced
each time a simulation is run to facilitate evaluation of the performance objects options and their
impact on the runtime and other factors so the user can determine which combination is best for
their particular input file. It includes a timestamp. Since it is a CSV (comma separated value) file,
it is easily opened in spreadsheet software. Please ensure that file is not open in the spreadsheet
while EnergyPlus is running so that the file can be appended to. If the spreadsheet program is open
with the file, it will be locked and not able to be appended. The fields in the file are shown below.
• Program
• Version
• TimeStamp
• Override Mode
• SuppressAllBeginEnvironmentResets
• MaxZoneTempDiff
• Number of Warnings
• Number of Severe
When using this file it is good to set PerformancePrecisionTradeoffs to default values the first
time to establish a baseline then change one input at a time and rerunning to understand the impact
of that input. The total runtime decrease and the impact on energy and the ocscillation variables
should be considered prior to committing to a specific PerformancePrecisionTradeoffs scheme.
2.16 eplusout.rdd
This file (from the Output:VariableDictionary,regular; and Output:VariableDictionary,IDF;
commands) shows all the report variables along with their “availability” for the current input file.
Each simulation may have different output variables though some are constant (for example the
environmental/outdoor variables! A user must first run the simulation (at least semi-successfully)
before the available output variables are known. This output file is available in two flavors: regular
(listed as they are in the Input Output Reference) and IDF (ready to be copied and pasted into
your Input File). Once this file is generated, the IDF editor can use them for Output:Variable
keys. You can also ask for the outputs to be sorted by name.
Output:VariableDictionary ,regular ,Name;
“Zone” variables are calculated and can be reported after each Zone/Heat Balance timestep
(ref: TimeSteps in Hour command). “HVAC” variables are calculated and can be reported with
each variable HVAC timestep. “Average” variables will be averaged over the time interval being
reported whereas “sum” variables are summed over that time interval.
There are two mitigating factors for this output variable list. One is the “Advanced Report
Variables” and the other is the “Create Minimal Surface Variables”.
<reduced >
HVAC ,Sum , Zone Mechanical Ventilation No Load Heat Removal Energy [J]
HVAC ,Sum ,Zone Mechanical Ventilation Cooling Load Increase Energy [J]
HVAC ,Sum , Zone Mechanical Ventilation Cooling Load Increase Due to Overheating Energy [J]
HVAC ,Sum ,Zone Mechanical Ventilation Cooling Load Decrease Energy [J]
HVAC ,Sum ,Zone Mechanical Ventilation No Load Heat Addition [J]
HVAC ,Sum ,Zone Mechanical Ventilation Heating Load Increase Energy [J]
HVAC ,Sum , Zone Mechanical Ventilation Heating Load Increase Due to Overcooling Energy[J]
HVAC ,Sum ,Zone Mechanical Ventilation Heating Load Decrease Energy [J]
HVAC ,Average ,Zone Mechanical Ventilation Mass Flow Rate [kg/s]
HVAC ,Average , Zone Mechanical Ventilation Standard Density Volume Flow Rate [m3/s]
HVAC ,Sum ,Zone Mechanical Ventilation Standard Density Volume [m3]
HVAC ,Sum ,Zone Mechanical Ventilation Mass [kg]
HVAC ,Average ,Zone Mechanical Ventilation Air Changes per Hour [ach]
! Program Version , <version >, <date/time of run >,IDD\_Version <IDD version >
! Output:Variable Objects (applicable to this run)
Output:Variable ,\*, Site Outdoor Air Drybulb Temperature ,hourly; !- Zone Average [C]
Output:Variable ,\*, Site Outdoor Air Dewpoint Temperature ,hourly; !- Zone Average [C]
Output:Variable ,\*, Site Outdoor Air Wetbulb Temperature ,hourly; !- Zone Average [C]
Output:Variable ,\*, Site Outdoor Air Humidity Ratio ,hourly; !- Zone Average [kgWater/kgDryAir]
Output:Variable ,\*, Site Outdoor Air Relative Humidity ,hourly; !- Zone Average [%]
Output:Variable ,\*, Site Outdoor Air Barometric Pressure ,hourly; !- Zone Average [Pa]
Output:Variable ,\*, Site Wind Speed ,hourly; !- Zone Average [m/s]
Output:Variable ,\*, Site Wind Direction ,hourly; !- Zone Average [deg]
2.17 eplusout.mdd
This file (from the Output:VariableDictionary,regular; and Output:VariableDictionary,IDF;
commands) shows all the report meters along with their “availability” for the current input file. A
user must first run the simulation (at least semi-successfully) before the available output meters
are known. This output file is available in two flavors: regular (listed as they are in the Input
Output Reference) and IDF (ready to be copied and pasted into your Input File). Once this file is
generated, the IDF editor can use them for Output:Meter and Output:CumulativeMeter keys.
Note that meters are always accumulated to the Zone timestep. They are always “summed”
variables.
• <ResourceType>:<name> Or
• <EndUseType>:<ResourceType>:<name> Or
• <EndUseSubcategory>:<EndUseType>:<ResourceType>:<name>.
The user requests reporting by either specifying the full name above (without Units) or a
“wildcard” representation of that name (to obtain all meters of a type). For example, entering
“Electricity:*” for the meter name will report on all the Electricity: meters (Electricity:Facility,
Electricity:Building, Electricity:Zone:Resistive Zone, Electricity:Zone:East Zone, Electricity:North
Zone in the example above). Both the resource types and end-use types are set within the program
by the developers. End-use subcategories are user-defined and are an input field for certain objects.
To summarize the previous paragraph, you could use:
Output:Meter ,Electricity :\*;
From a three zone file that had no HVAC electricity (i.e., had only electric equipment or lighting
equipment in an uncontrolled three zone building).
Current resource types are shown in the table below:
2.17. EPLUSOUT.MDD 139
Utility/Fuel Types
Electricity Gas
Gasoline Diesel
Coal FuelOilNo1
FuelOilNo2 Propane
Water Steam
DistrictCooling DistrictHeating
The end use types are shown in the following table (note that certain end use types apply only
to the EnergyTransfer resource):
The end use types are shown in the following table:
Specific meter types are then used for grouping the fuel type meters:
140 CHAPTER 2. OUTPUT FILES
Meters
Facility
Building
Zone
System
Plant
Facility meters contain all the energy of a fuel type. Building meters contain the sum of each
zone’s energy. System meters contain the energy from the system components. Plant meters contain
the energy from the plant equipments.
Thus, the following relationships should be observed:
∑
Facility = (Building + System + Plant + Exterior) (2.11)
∑
#Zones
Building = Zone (2.12)
i
Custom Meters, (review Input Output Reference, objects: Meter:Custom and Me-
ter:CustomDecrement) for further requirements, are reported in the same way as pre-defined
meters.
For example, one might put the Building Infiltration Heat Loss & Heat Gain on a set of custom
meters:
Meter:Custom ,
Building Infiltration Heat Loss , !- Name
Generic , !- Fuel Type
*, !- Key Name 1
Zone Infiltration Total Heat Loss Energy; !- Output Variable Name 1
Meter:Custom ,
Building Infiltration Heat Gain , !- Name
Generic , !- Fuel 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.
2.18 eplusout.shd
This file contains details of the shadow casting, back and receiving surfaces for the building. The
Engineering Reference explains the shadowing calculations in more detail; this report file merely
shows the level of interactions that the calculations will use. The report shows the Solar Distribution
algorithm (in the example Full Interior and Exterior) and then proceeds to illustrate which surfaces
shade (possibly) which other surfaces.
Note, a casting surface – a shadow casting surface or general casting surface (so called in the
file) – is one that casts a shadow on other surfaces. A receiving surface - a shadow receiving surface
2.19. EPLUSOUT.SLN 141
– is one that receives shadows from other surfaces (i.e. casting surfaces). A back surface – an inside
surface – is one that may be partially sunlit/receive solar transmission for interior solar distribution.
An example follows:
Shadowing Combinations
.. Solar Distribution = FullInteriorAndExterior
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Surface = ZN001:WALL001 is used as Receiving Surface in calculations.
Number of general casting surfaces = 0
Number of back surfaces = 5
... Surface = ZN001:WALL002
... Surface = ZN001:WALL003
... Surface = ZN001:WALL004
... Surface = ZN001:FLR001
... Surface = ZN001:ROOF001
Number of receiving sub surfaces = 1
.... Surface = ZN001:WALL001:WIN001
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Surface = ZN001:WALL001:WIN001 is not used as Receiving Surface in calculations.
Number of general casting surfaces = 0
Number of back surfaces = 0
Number of receiving sub surfaces = 0
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Surface = ZN001:WALL002 is used as Receiving Surface in calculations.
Number of general casting surfaces = 0
Number of back surfaces = 0
Number of receiving sub surfaces = 0
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Surface = ZN001:WALL003 is not used as Receiving Surface in calculations.
Number of general casting surfaces = 0
Number of back surfaces = 0
Number of receiving sub surfaces = 0
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Surface = ZN001:WALL004 is not used as Receiving Surface in calculations.
Number of general casting surfaces = 0
Number of back surfaces = 0
Number of receiving sub surfaces = 0
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Surface = ZN001:FLR001 is not used as Receiving Surface in calculations.
Number of general casting surfaces = 0
Number of back surfaces = 0
Number of receiving sub surfaces = 0
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Surface = ZN001:ROOF001 is used as Receiving Surface in calculations.
Number of general casting surfaces = 0
Number of back surfaces = 0
Number of receiving sub surfaces = 0
2.19 eplusout.sln
The following shows an excerpt of “lines” report (eplusout.sln) for a single surface. It gives the sur-
face name and then the coordinates in the “standard” EnergyPlus fashion (that is, UpperLeftCorner
first and proceeding around, in this case, the four vertices in the surface.
SPACE1 -1: MAIN SOUTH OVERHANG
-0.65 , -1.13, 2.20, 0.00, 0.00, 2.20
0.00, 0.00, 2.20, 17.15 , -9.90, 2.20
17.15 , -9.90, 2.20, 16.50 , -11.03, 2.20
16.50 , -11.03, 2.20, -0.65, -1.13, 2.20
The following shows an excerpt of “lines, IDF” report (eplusout.sln) for a single surface. It
gives the coordinates in the “standard” EnergyPlus fashion (that is, UpperLeftCorner first and
142 CHAPTER 2. OUTPUT FILES
proceeding around, in this case, the four vertices in the surface. Note that this is NOT a complete
description of the surface but enough to change your IDF file, if you want to.
Building North Axis = 0
GlobalGeometryRules ,UpperLeftCorner ,CounterClockwise ,WorldCoordinates;
Surface = SHADING , Name = ROOMSOUTH SURF6 -VFIN1 -6
4, !- Number of (X,Y,Z) groups in this surface
-23.34, -14.85, 2.41, !- X,Y,Z = = > Vertex 1
-23.34, -14.76, 2.49, !- X,Y,Z = = > Vertex 2
-18.13, -14.76, 2.49, !- X,Y,Z = = > Vertex 3
-18.13, -14.85, 2.41; !- X,Y,Z = = > Vertex 4
Surface = WALL , Name = ROOMNORTH SURF3 -1
4, !- Number of (X,Y,Z) groups in this surface
-15.94, -5.34, 3.00, !- X,Y,Z = = > Vertex 1
-15.94, -5.34, 0.00, !- X,Y,Z = = > Vertex 2
-18.91, -5.34, 0.00, !- X,Y,Z = = > Vertex 3
-18.91, -5.34, 3.00; !- X,Y,Z = = > Vertex 4
Surface = WALL , Name = ROOMNORTH SURF4 -1
4, !- Number of (X,Y,Z) groups in this surface
-18.91, -5.34, 3.00, !- X,Y,Z = = > Vertex 1
-18.91, -5.34, 0.00, !- X,Y,Z = = > Vertex 2
-22.65, -5.34, 0.00, !- X,Y,Z = = > Vertex 3
-22.65, -5.34, 3.00; !- X,Y,Z = = > Vertex 4
Surface = WINDOW , Name = ROOMNORTH SURF5 -1- NOSHADE
4, !- Number of (X,Y,Z) groups in this surface
-19.02, -5.34, 2.59, !- X,Y,Z = = > Vertex 1
-19.02, -5.34, 0.41, !- X,Y,Z = = > Vertex 2
-22.54, -5.34, 0.41, !- X,Y,Z = = > Vertex 3
-22.54, -5.34, 2.59; !- X,Y,Z = = > Vertex 4
2.20 eplusout.sql
eplusout.sql is an optional output format for EnergyPlus. The eplusout.sql output file is a sqlite3
database file (see https://www.sqlite.org) and includes all of the data found in EnergyPlus’ eplustbl.*
files, eplusout.eso and eplusout.mtr output files (i.e., EnergyPlus’ standard variable and meter
output files) plus a number of reports that are found in the eplusout.eio output file.
A discussion of the individual data tables is presented below followed by a discussion about how
to access data within the SQL file.
• ComponentSizes Table
• ConstructionLayers Table
• Constructions Table
• Materials Table
• NominalBaseboardHeaters Table
• NominalElectricEquipment Table
• NominalGasEquipment Table
2.20. EPLUSOUT.SQL 143
• NominalHotWaterEquipment Table
• NominalInfiltration Table
• NominalLighting Table
• NominalOtherEquipment Table
• NominalPeople Table
• NominalSteamEquipment Table
• NominalVentilation Table
• ReportData Table
• ReportDataDictionary Table
• ReportExtendedData Table
• RoomAirModels Table
• Schedules Table
• Surfaces Table
• SystemSizes Table
• Time Table
• ZoneGroups Table
• Zones Table
• ZoneLists Table
• ZoneSizes Table
• ZoneInfoLists Table
• Simulations Table
• EnvironmentPeriods Table
• TabularData Table
• Strings Table
• StringTypes Table
• TabularDataWithStrings Table
• Errors Table
A short discussion of contents of each of the above SQL tables is given in the sections that
follow.
144 CHAPTER 2. OUTPUT FILES
Please see the Zone object in the Group-Thermal Zone Description/Geometry section of the
Input-Output Reference for more information.
Please see the People object in the Group-Internal Gains section of the Input-Output Reference
for more information.
Please see the LIGHTS object in the Group-Internal Gains section of the Input-Output Reference
for more information.
Please see the Electric Equipment object in the Group-Internal Gains section of the Input-
Output Reference for more information.
Please see the Gas Equipment object in the Group-Internal Gains section of the Input-Output
Reference for more information.
Please see the Steam Equipment object in the Group-Internal Gains section of the Input-Output
Reference for more information.
Please see the Hot Water Equipment object in the Group-Internal Gains section of the Input-
Output Reference for more information.
Please see the Other Equipment object in the Group-Internal Gains section of the Input-Output
Reference for more information.
Please see the Baseboard Heat object in the Group-Internal Gains section of the Input-Output
Reference for more information.
Please see the Infiltration object in the Group-Airflow section of the Input-Output Reference
for more information.
Please see the Ventilation object in the Group-Airflow section of the Input-Output Reference
for more information.
Please see the Surface(s) object in the Group-Thermal Zone Description/Geometry section of
the Input-Output Reference for more information.
Please see the Construction object in the Group-Surface Construction Elements section of the
Input-Output Reference for more information.
Please see the Construction object in the Group-Surface Construction Elements section of the
Input-Output Reference for more information.
Please see the Materials object in the Group-Surface Construction Elements section of the Input-
Output Reference for more information.
Please see the Sizing object in the Group-Design Objects section of the Input-Output Reference
for more information.
Please see the Zone Sizing object in the Group-Design Objects section of the Input-Output
Reference for more information.
Please see the Zone Group object in the Group-Thermal Zone Description/Geometry section of
the Input-Output Reference for more information.
158 CHAPTER 2. OUTPUT FILES
Please see the Zone List object in the Group-Thermal Zone Description/Geometry section of
the Input-Output Reference for more information.
This is a join table to represent the many-to-many relationship of zones and zone lists.
ZoneListIndex and ZoneIndex together are the Primary Key for this table.
Please see the Group-Schedules section of the Input-Output Reference for more information.
2.20. EPLUSOUT.SQL 159
One of the simplest ways to access the data in the SQL database is by way of the SQL command
line tool (i.e., sqlite3). A brief description of how to use sqlite3 for each computing platform is given
below.
While Windows does not ship with sqlite3 installed, the sqlite3 binary can be downloaded from
the SQLite webpage (www.sqlite.org/download.html). After downloading the precompiled binary,
install it in the EnergyPlus directory.
Once the sqlite3 executable is installed, access the program from the command line by typing
“sqlite3” at the DOS prompt.
2.20.5.3 Linux
The sqlite3 command line tool comes preinstalled on a number of more recent Linux releases. To
see if sqlite3 is available (and which version is installed), type “sqlite3 –version” from the command
line. If sqlite3 is not installed, the sqlite3 binary, as well as source code, can be downloaded from
the SQLite webpage (https://www.sqlite.org/download.html) and installed in the directory of your
choice.
164 CHAPTER 2. OUTPUT FILES
2.20.5.4 Macintosh OS X
The sqlite3 program comes standard on MacOS X 10.5. From the command line, type “sqlite3
–version” to see which version of sqlite3 is installed. In order to access the database created by
EnergyPlus, version 3 or later is required.
at the command line, where <database name > is the name of the SQL database (e.g., sqlite3
eplusout.sql).
The sqlite.org website gives examples of how sqlite3 can be used to access and output data in
various formats.
2.20.5.6 ODBC
ODBC allows access to the SQL database from a variety of programs, including Microsoft Excel,
Microsoft Access, and FileMaker. How to install and use ODBC drivers is outside the scope of this
document, and more information can be found at the following websites:
Macintosh ODBC drivers:
https://www.actualtechnologies.com/
Windows and Linux ODBC information and drivers:
https://www.sqlite.org/cvstrac/wiki?p=SqliteOdbc
https://www.ch-werner.de/sqliteodbc/
2.20.5.7 API
Sqlite3 includes a rich C++ API (detailed on the SQLite website www.sqlite.org/cintro.html), and
wrappers for the API interface are available in a variety of programming languages, including For-
tran, TCL, and Ruby (see www.sqlite.org/cvstrac/wiki?p = SqliteWrappers for more information).
2.21 eplusssz.<ext>
This file is the result of the system sizing calculation. As usual, the file can be read into a spreadsheet
for easy viewing. System Sizing (see Sizing:System object) performs a special calculation that, to
oversimplify, sums up the results of the zone sizing calculation and saves the results in the system
sizing arrays for reporting on component size requirements.
An excerpt of the file:
Time,:Des Heat Mass Flow [kg/s],:Des Cool Mass Flow [kg/s],:Des Heat Cap [W],:Des Sens Cool
Cap [W],
00:15:00,1.063942E+00,0.000000E+00,5.944201E+03,0.000000E+00,
00:30:00,1.063942E+00,0.000000E+00,5.944201E+03,0.000000E+00,
00:45:00,1.063942E+00,0.000000E+00,5.944201E+03,0.000000E+00,
01:00:00,1.063942E+00,0.000000E+00,5.944201E+03,0.000000E+00,
2.21. EPLUSSSZ.<EXT> 165
01:15:00,1.063942E+00,0.000000E+00,5.944200E+03,0.000000E+00,
01:30:00,1.063942E+00,0.000000E+00,5.944200E+03,0.000000E+00,
01:45:00,1.063942E+00,0.000000E+00,5.944200E+03,0.000000E+00,
02:00:00,1.063942E+00,0.000000E+00,5.944200E+03,0.000000E+00,
02:15:00,1.063942E+00,0.000000E+00,5.944200E+03,0.000000E+00,
02:30:00,1.063942E+00,0.000000E+00,5.944200E+03,0.000000E+00,
02:45:00,1.063942E+00,0.000000E+00,5.944200E+03,0.000000E+00,
03:00:00,1.063942E+00,0.000000E+00,5.944200E+03,0.000000E+00,
03:15:00,1.063942E+00,0.000000E+00,5.944200E+03,0.000000E+00,
03:30:00,1.063942E+00,0.000000E+00,5.944200E+03,0.000000E+00,
03:45:00,1.063942E+00,0.000000E+00,5.944200E+03,0.000000E+00,
04:00:00,1.063942E+00,0.000000E+00,5.944200E+03,0.000000E+00,
04:15:00,1.063942E+00,0.000000E+00,5.944200E+03,0.000000E+00,
04:30:00,1.063942E+00,0.000000E+00,5.944200E+03,0.000000E+00,
04:45:00,1.063942E+00,0.000000E+00,5.944200E+03,0.000000E+00,
05:00:00,1.063942E+00,0.000000E+00,5.944200E+03,0.000000E+00,
05:15:00,1.063942E+00,0.000000E+00,5.944200E+03,0.000000E+00,
05:30:00,1.063942E+00,0.000000E+00,5.944200E+03,0.000000E+00, = = = reduced for brevity
===
Coinc Peak ,1.063943E+00,1.378986E+00,5.944199E+03,2.165922E+04,
NonCoinc Peak,1.063943E+00,1.553319E+00,5.944199E+03,2.165922E+04,
2.22 epluszsz.<ext>
This file is a result of the zone sizing calculation. 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. The file has a similar
format to the eplusssz.<ext> file.
An excerpt (this is a direct copy of the CSV data, so you can copy it to a spreadsheet to view
it easier):
Time ,SPACE1 -1: CHICAGO_IL_USA ANNUAL HEATING 99% DESIGN CONDITIONS DB:Des Heat Load [W],SPACE1 -1:
CHICAGO_IL_USA ANNUAL COOLING 1% DESIGN CONDITIONS DB/MCWB:Des Sens Cool Load [W],SPACE1 -1:
CHICAGO_IL_USA ANNUAL HEATING 99% DESIGN CONDITIONS DB:Des Heat Mass Flow [kg/s],SPACE1 -1:
CHICAGO_IL_USA ANNUAL COOLING 1% DESIGN CONDITIONS DB/MCWB:Des Cool Mass Flow [kg/s],SPACE2 -1:
CHICAGO_IL_USA ANNUAL HEATING 99% DESIGN CONDITIONS DB:Des Heat Load [W],SPACE2 -1: CHICAGO_IL_USA
ANNUAL COOLING 1% DESIGN CONDITIONS DB/MCWB:Des Sens Cool Load [W],SPACE2 -1: CHICAGO_IL_USA ANNUAL
HEATING 99% DESIGN CONDITIONS DB:Des Heat Mass Flow [kg/s],SPACE2 -1: CHICAGO_IL_USA ANNUAL COOLING 1%
2.22. EPLUSZSZ.<EXT> 167
DESIGN CONDITIONS DB/MCWB:Des Cool Mass Flow [kg/s],SPACE3 -1: CHICAGO_IL_USA ANNUAL HEATING 99% DESIGN
CONDITIONS DB:Des Heat Load [W],SPACE3 -1: CHICAGO_IL_USA ANNUAL COOLING 1% DESIGN CONDITIONS DB/MCWB:
Des Sens Cool Load [W],SPACE3 -1: CHICAGO_IL_USA ANNUAL HEATING 99% DESIGN CONDITIONS DB:Des Heat Mass
Flow [kg/s],SPACE3 -1: CHICAGO_IL_USA ANNUAL COOLING 1% DESIGN CONDITIONS DB/MCWB:Des Cool Mass Flow [
kg/s],SPACE4 -1: CHICAGO_IL_USA ANNUAL HEATING 99% DESIGN CONDITIONS DB:Des Heat Load [W],SPACE4 -1:
CHICAGO_IL_USA ANNUAL COOLING 1% DESIGN CONDITIONS DB/MCWB:Des Sens Cool Load [W],SPACE4 -1:
CHICAGO_IL_USA ANNUAL HEATING 99% DESIGN CONDITIONS DB:Des Heat Mass Flow [kg/s],SPACE4 -1:
CHICAGO_IL_USA ANNUAL COOLING 1% DESIGN CONDITIONS DB/MCWB:Des Cool Mass Flow [kg/s],SPACE5 -1:
CHICAGO_IL_USA ANNUAL HEATING 99% DESIGN CONDITIONS DB:Des Heat Load [W],SPACE5 -1: CHICAGO_IL_USA
ANNUAL COOLING 1\% DESIGN CONDITIONS DB/MCWB:Des Sens Cool Load [W],SPACE5 -1: CHICAGO_IL_USA ANNUAL
HEATING 99% DESIGN CONDITIONS DB:Des Heat Mass Flow [kg/s],SPACE5 -1: CHICAGO_IL_USA ANNUAL COOLING 1%
DESIGN CONDITIONS DB/MCWB:Des Cool Mass Flow [kg/s]
Peak ,3.860764E+03 ,2.647331E+03 ,1.371872E -01 ,2.618408E -01 ,1.625149E+03 ,2.234379E+03 ,5.774764E -02 ,2.209833E
-01 ,3.753069E+03 ,2.506339E+03 ,1.333603E -01 ,2.478849E -01 ,1.625149E+03 ,2.464720E+03 ,5.774764E
-02 ,2.437670E -01 ,2.981568E+03 ,2.628694E+03 ,1.059457E -01 ,2.599981E-01
Peak Vol Flow (m3/s) , , ,1.166672E -01 ,2.226756E-01 , , ,4.910995E -02 ,1.879294E -01 , , ,1.134128E -01 ,2.108072E
-01 , , ,4.910995E -02 ,2.073052E -01 , , ,9.009871E -02 ,2.211085E-01
These are repeated for the number of zones in the sizing calculation.
2.23 eplusout.<ext>
The eplusout.csv (or txt or tab extension) is a file that can be produced with OutputControl:Files
or by post-processing on the eplusout.eso file. EnergyPlus distributes a post-processing program
(ReadVarsESO – see next section) with the installation.
2.24. EPLUSMTR.<EXT> 169
2.24 eplusmtr.<ext>
The eplusmtr.csv (or txt or tab extension) is a file that can be produced with OutputControl:Files
or by post-processing on the eplusout.mtr file. EnergyPlus distributes a post-processing program
(ReadVarsESO – see next section) with the installation.
2.25 eplusmap.<ext>
The eplusmap.csv (or txt or tab extension) is a file that is generated by the Output:IlluminanceMap
object. These are calculated for the Daylighting:Controls daylighting option. By default, this is a
comma delimited text file (csv) that can be imported into a spreadsheet program. For example, the
input for the Output:IlluminanceMap object shown below:
Output:IlluminanceMap ,
Daylit Map , !- Map Name
Daylit Zone , !- Zone Name
0.8, !- 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
generates the following output in csv format when viewed with Microsoft Excel. Note that if
the point is outside the zone a “*” will be shown.
170 CHAPTER 2. OUTPUT FILES
Each cell reports the illuminance (in lux) at the location specified by the (X;Y) coordinates in
the column and row headers. These are XY pairs separated by a semi-colon for ease in importing
into the spreadsheet. The Z coordinate of the map is shown in the title (the illuminance map is set
in a plane). The date and time are indicated in the upper left cell of the map. One map is reported
for every hour of the simulation.
The illuminance values are organized to allow the user to rapidly plot a visualization of the data
using Microsoft Excel’s standard “3-D Column” graph. A 3-D graph is shown below for the data
in a single day similar to the earlier example.
The following figure illustrates a similar map for the tubular daylighting device example file that
is included with the installation.
Individual 3-D graphs can be generated for each hour of a given day and collected to generate
a sequence of graphs representing the progression of daylighting conditions over the course of the
day. Using additional software tools (not provided with EnergyPlus) the user can do further post-
processing to link screenshots of the graphs into an animated sequence.
172 CHAPTER 2. OUTPUT FILES
Figure 2.9: A 3D illuminance map for the tubular daylighting device file
2.27. EPLUSSCREEN.CSV 173
2.26 eplusout.dfs
The daylight factors report contains the pre-calculated hourly daylight factors for the four CIE sky
types (clear, clear turbid, intermediate, and overcast sky), for each daylight reference points for
each exterior window of a daylight enclosure which consists of one or more spaces. The file is CSV
formatted – ready for spreadsheet viewing. The input for requesting the report is simple:
Output:DaylightFactors ,
SizingDays; !- Reporting Days
The following shows an excerpt the daylight factors for a window without shade:
This file contains daylight factors for all exterior windows of daylight zones.
MonthAndDay ,Enclosure Name , Zone Name ,Window Name ,Window State
Hour ,Reference Point ,Daylight Factor for Clear Sky ,Daylight Factor for Clear Turbid Sky ,Daylight Factor
for Intermediate Sky ,Daylight Factor for Overcast Sky
01/21 , Enclosure 1,ZN_1 ,ZN_1_WALL_NORTH_WINDOW ,Base Window
1,ZN_1_DAYLREFPT1 ,0.00000 ,0.00000 ,0.00000 ,0.00000
1,ZN_1_DAYLREFPT2 ,0.00000 ,0.00000 ,0.00000 ,0.00000
1,ZN_1_DAYLREFPT3 ,0.00000 ,0.00000 ,0.00000 ,0.00000
[...]
9,ZN_1_DAYLREFPT1 ,2.14657E -002 ,1.73681E -002 ,1.38241E -002 ,1.41272E -002
9,ZN_1_DAYLREFPT2 ,2.14657E -002 ,1.73680E -002 ,1.38240E -002 ,1.41273E -002
9,ZN_1_DAYLREFPT3 ,2.14655E -002 ,1.73678E -002 ,1.38239E -002 ,1.41274E -002
[...]
24, ZN_1_DAYLREFPT1 ,0.00000 ,0.00000 ,0.00000 ,0.00000
24, ZN_1_DAYLREFPT2 ,0.00000 ,0.00000 ,0.00000 ,0.00000
24, ZN_1_DAYLREFPT3 ,0.00000 ,0.00000 ,0.00000 ,0.00000
The Window State column has three possible outputs – “Base Window” indicating windows
without shades; a numeric value, from 0.0 to 180.0 for every 10.0 step, indicating the slat angle (in
degrees) of the blind shading the window; “Blind or Slat Applied” indicating windows in shaded
state by shades, screens, and blinds with fixed slat angle.
The lines after it describes the hourly daylight factors at each reference point:
Table 2.46: Hourly Daylight Factors for the considered window at each refer-
ence point and 4 CIE Sky Conditions
Hour Reference Point Daylight Factor for Daylight Factor for Daylight Factor for Daylight Factor for
Clear Sky Clear Turbid Sky Intermediate Sky Overcast Sky
9 ZN_1_DAYLREFPT1 0.021466 0.017368 0.013824 0.014127
9 ZN_1_DAYLREFPT2 0.021466 0.017368 0.013824 0.014127
9 ZN_1_DAYLREFPT3 0.021465 0.017368 0.013824 0.014127
10 ZN_1_DAYLREFPT1 0.020245 0.016029 0.012201 0.014127
2.27 eplusscreen.csv
Results of the window screen transmittance map. This file can be used to create a 3-D Column
chart for graphically viewing the direct beam and reflected beam transmittance at various relative
azimuth and relative altitude angles. The “relative” angles in this file are the incident solar angles
174 CHAPTER 2. OUTPUT FILES
with respect to the outward surface normal. The figures below are example 3-D charts generated
using the data provided in this output file.
2.28 eplustbl.<ext>
The eplustbl file contains the tabular output results that are created when using the following
objects:
• Output:Table:SummaryReports
• Output:Table:TimeBins
• Output:Table:Monthly
• UtilityCost:Tariff
• ComponentCost:Line Item
The format and the extension for the file depends on the setting of the ColumnSeparator field
of the Output:Table:Style object. The choices of HTML, tab, fixed, comma, and XML result in
eplustbl.htm, eplustbl.tab, eplustbl.txt, eplustbl.csv, eplustbl.xml respectively. The HTML version
of the report also includes a table of contents that allows easier navigation through the file.
By default the energy units reported in all of the eplustbl files are in Joules (J) but the Unit-
Conversion field of the Output:Table:Style object allows for the values to be reported in MJ, GJ or
in kWh. In addition, the Output:Table:Style object can specify for the tables to be in IP units for
all fields.
2.28. EPLUSTBL.<EXT> 175
2.28.1 Output:Table:SummaryReports
Several predefined reports are available from the Output:Table:SummaryReports object including
the following. (spaces are inserted in names for readability; keys are included in the Input Data
Dictionary or by just removing the spaces):
• All Summary
• All Monthly
Lists all following applicable tables with both “Summary” and “Monthly” in the name. This
does not include the Zone Component Load Summary report.
Lists the All Summary tables as well as the Zone Component Load report (currently the only
Sizing Period report). Please note that the Zone Component Load report does increase the run
time because it repeats sizing periods.
Lists the All Summary tables, the Monthly tables as well as the Zone Component Load report
(currently the only Sizing Period report). Please note that the Zone Component Load report does
increase the run time because it repeats sizing periods.
• Equipment Summary
• Envelope Summary
• Shading Summary
• Lighting Summary
• System Summary
• Energy Meters
• DX Report Monthly
Each of these reports is made up of several sub-tables of information. Examples of some of the
tables are shown below. To enable all of the reports the single All Summary may be specified.
Building Area
Area (m2)
Total Building Area 927.20
Net Conditioned Building Area 927.20
Unconditioned Building Area 0.00
End Uses
Electricity (GJ) Natural Gas Other Fuel (GJ) District Cooling District Heating Water (m3)
(GJ) (GJ) (GJ)
Electricity (GJ) Natural Gas Other Fuel (GJ) District Cooling District Heating Water (m3)
(GJ) (GJ) (GJ)
Note: Natural gas appears to be the principal heating source based on energy usage.
End Uses By Subcategory
Subcategory Electricity Natural Gas Other Fuel District District Water (m3)
(GJ) (GJ) (GJ) Cooling (GJ) Heating (GJ)
Normalized Metrics
Utility Use Per Conditioned Floor Area
Facility (Hours)
Time Set Point Not Met During Occupied Heating 0.00
Time Set Point Not Met During Occupied Cooling 406.00
Time Not Comfortable Based on Simple ASHRAE 55-2004 1033.00
Note 1: An asterisk (*) indicates that the feature is not yet implemented.
Value
Program Version and Build EnergyPlus, Version 3.1
Weather Chicago IL United States TMY2 94846
WMO#=725340
Latitude (deg) 41.78
Longitude (deg) -87.8
Elevation (m) 190.00
Time Zone -6.0
North Axis Angle (deg) 30.00
Hours Simulated (hrs) 8760.00
ENVELOPE
Window-Wall Ratio
Skylight-Roof Ratio
Total
Gross Roof Area (m2) 463.60
Skylight Area (m2) 0.00
Skylight-Roof Ratio (%) 0.00
PERFORMANCE
Zone Summary
Note: In order to properly read the summary rows of this table, the following rules apply:
• If the Zone Part of Total Floor Area is set to ‘No’, then it will only be counted towards the “Not
Part of Total” row
• Otherwise, it is added to the “Total” row. Then, if the zone is also conditioned, it is added
to the “Conditioned Total” row; If unconditioned, it is added to the “Unconditioned Total”
row.
184 CHAPTER 2. OUTPUT FILES
Area Conditioned Part of Volume Multi- Above Underground Window Opening Lighting People Plug
[m2] (Y/N) Total [m3] pliers Ground Gross Wall Glass Area [W/m2] [m2 per and
Floor Gross Area [m2] Area [m2] person] Process
Area Wall [m2] [W/m2]
(Y/N) Area
[m2]
SPACE-1 200 Yes No 400 1 20 0 0 0 4 300 4
SPACE-2 100 No No 200 1 50 0 0 0 1 100 1
SPACE-3 1000 Yes Yes 2000 1 180 0 40 5 20 10 10
SPACE-4 500 No Yes 1000 1 110 10 10 0 5 45 4
Total 1500 3000 290 10 50 5 15 13.5 8
Conditioned Total 1000 2000 180 0 40 5 20 10 10
Unconditioned 500 1000 110 10 10 0 5 45 4
Total
Not Part of Total 300 600 70 0 0 0 3 180 3
Electricity (W) Natural Gas Propane (W) District Cooling Steam (W) Water (m3/s)
(W) (W)
Subcategory Electricity Natural Gas Propane (W) District Steam (W) Water (m3/s)
(W) (W) Cooling (W)
Subcategory Electricity Natural Gas Propane (W) District Steam (W) Water (m3/s)
(W) (W) Cooling (W)
Normalized Metrics
Source Energy End Use Components Per Conditioned Floor Area
Cooling Coils
Heating Coils
Fans
Type Total Delta Max Flow Rated Power Motor Heat In End Use
Efficiency Pressure (pa) Rate (m3/s) (W) Air Fraction
(W/W)
Pumps
Construction Reflectance U-Factor U-Factor Gross Area Azimuth Tilt (deg) Cardinal
with Film no Film (m2) (deg) Direction
(W/m2-K) (W/m2-K)
Construction Reflectance U-Factor U-Factor Gross Area Azimuth Tilt (deg) Cardinal
with Film no Film (m2) (deg) Direction
(W/m2-K) (W/m2-K)
Exterior Fenestration
The Exterior Fenestration table has been enhanced to show additional columns of data but an
explicit example will not fit well on a page so instead the list of columns is shown below:
• Window Name
• Construction
• Glass SHGC
• Assembly SHGC
• Parent Surface
• Azimuth [deg]
• Tilt [deg]
• Cardinal Direction
WF-1 0.00 0.00 0.43 0.00 0.00 0.00 0.30 0.52 0.86
DF-1 0.73 0.26 0.62 0.00 0.00 0.28 0.90 0.69 0.92
WR-1 1.00 1.00 0.00 1.00 1.00 0.00 1.00 1.00 0.00
WB-1 0.00 0.00 0.00 1.00 0.00 0.00 0.00 0.00 0.00
DB-1 0.00 0.00 0.00 1.00 0.00 0.00 0.00 0.00 0.00
WL-1 0.00 0.00 1.00 0.00 0.00 1.00 0.00 0.00 1.00
Window Control
2.28. EPLUSTBL.<EXT> 193
Zone Lighting Zone Total End Use Schedule Scheduled Hours/WeekFull Return ConditionedCon
Power Area Power Subcate- Name Hours/Week> 1% Load Air (Y/N) [GJ
Density [m2] [W] gory [hr] [hr] Hours/WeekFraction
[W/m2] [hr]
Daylighting
194 CHAPTER 2. OUTPUT FILES
Exterior Lighting
The encyclopedic documentation that follows is important because in many cases, very similar
data are available from up to three separate fields and one must be careful to understand the subtle
differences and be aware that there is some repetition of the similar types of data in the fields. This
is mainly because coil performance changes with the conditions under which it operates and so an
important part of this table is describing each coil under different sets of operating conditions.
There are three broad groupings of data fields in the table:
• Meta data. The meta data fields include string names to identify the coil, where it is being
used, names and types of IDF objects involved, what some of the various sizing method input
choices were set to, and information about the supply fan and plant found to be associated
with the coil. 40 fields.
• Ideal loads sizing summary. The collection of fields whose names end with “at Ideal Loads
Peak” are all related to the sizing calculations done by the ideal loads zone sizing routines
and the system sizing routines based on them. Many of the values reported here come from
Sizing:Zone and/or Sizing:System input. The operating conditions occurring during Ideal
Loads sizing calculations are unlikely to match the conditions used in the definitions for coil
input data. 36 fields.
• Rating point summary. This is a collection of fields with names that end in “at Rating
Conditions.” The model input data for many types of coils is based on defined set of conditions
variously referred to as the rating point, reference, nominal, or design. The coil models are
calculated with conditions set to match the rating point and the inputs and outputs from that
are reported here. Many of the values here are from the input documentation that defines
the conditions at the rating point. The coil capacities and leaving conditions are the results
from the running complete coil model. Some coil models do not have a rating point as part of
the model definition, because the models are not sensitive to operating conditions, and those
coils will have -999.0 in these fields. 11 fields.
The following is a comprehensive listing of each column/field in the coil summary table with a
brief definition and/or summary.
Coil Type The input object class name in IDF syntax. Text string.
Coil Location The broad type of HVAC this coil is being used in. “AirLoop” means the coil
is part of a central air system, such as a main coil in a multizone air handler. “Zone Equipment”
means that the coil is part of Zone equipment like a PTAC, or in the zone terminal unit of an
airhandler like a VAV reheat coil. Text string.
HVAC Type This is more specifically what HVAC the coil is used in. The values are the input
object class name, in IDF syntax, found to be associated with the coil. Text string.
HVAC Name This is the unique user name input for the HVAC Type. The strings will be
converted to upper case compared to what is in the actual input data file. Text string.
Zone Name(s) This is the zone, or list of zones, found to be associated with this coil. The zone
name is defined by the user in the Zone object. For multizone systems, the coils can have a list of
zone names with the individual names separated by a semicolon. The zones listed here are those
used to generate (aggregate and volume-weighted average) values for the room conditions and loads.
Text string.
System Sizing Method Concurrence This field applies to “AirLoop” coils. It describes if the
central air system sizing was done using “Coincident” or “Non-Coincident” method. This refers to
196 CHAPTER 2. OUTPUT FILES
how the ideal loads sizing routines process the time sequence of zone loads. The concurrent sum
of peaks, or coincident or “block”, is often lower than the sum of the individual peaks regardless
of when they occur, or non-coincident sum. This field is not applicable to “Zone Equipment” coils
and will show “N/A” here. This corresponds to the input field called Type of Zone Sum to Use in
the Sizing:System input object. Text string.
System Sizing Method Capacity This field applies to “AirLoop” coils. It describes what was
chosen for the method of determining coil capacity during ideal loads sizing routines. The values
here will match the input key choices available for the the Sizing:System object’s input fields called
Cooling Design Capacity Method, for cooling coils, and Heating Design Capacity Method, for heating
coils. Values here of “HeatingDesignCapacity” or “CoolingDesignCapacity” mean that the coil was
sized using the design loads calculated from the zone ideal loads results. When sizing was scaled
using floor area the value here would be “CapacityPerFloorArea.” Values of FractionOfAutosized-
HeatingCapacity and FractionOfAutosizeCoolingCapacity mean that the usual design load based
results were further scaled by a separate user scaling factor. This field is not applicable to “Zone
Equipment” coils and will show “N/A” here. Text string.
System Sizing Method Air Flow This field applies to “AirLoop” coils. It describes what was
chosen for the method of determining the system air flow rate during ideal loads sizing routines.
This field is not applicable to “Zone Equipment” coils and will show “N/A” here. Text string.
Autosized Coil Capacity? This field describes if the coil capacity was autosized or not. Values
here will be “Yes” or “No.” A “No” means that the size of the coil was set at input, hard sized,
and no capacity sizing calculations were done for the coil. A “Yes” means that coil’s capacity was
autosized. Text string.
Autosized Coil Airflow? This field describes if the coil’s airflow rate was autosized or not. Values
here will be “Yes” or “No.” A “No” means that the airflow rate used to size the coil’s capacity was
set at input, hard sized. This means that the coil’s capacity was set for an airflow rate that was
not autosized. A “Yes” means that the airflow rate for the coil came from sizing calculations. Text
string.
Autosized Coil Water Flow? This field describes if the coil’s water flow rate was autosized or
not. Values here will be “Yes” or “No.” A “No” means that the water flow rate used to size the
coil’s capacity was set at input, hard sized. This means that the coil’s capacity was set for a water
flow rate that was not autosized. A “Yes” means that the water flow rate for the coil came from
sizing calculations. This field is only applicable to water-to-air coils. Text string.
OA Pretreated prior to coil inlet? This field describes if the coil’s sizing calculations are based on
the outdoor air being preconditioned, as with a separate coil, or if the outdoor air is unconditioned.
Values here will be “Yes” or “No.” A “No” means that the outdoor air is not preconditioned. A
“Yes” means that the outdoor is preconditioned. This field only really applies to central air system
coils. The outdoor air may be mixed with return air before the coil, but that mixed air may be
based on either treated or untreated outdoor air, depending on Sizing:System input. Text string.
Coil Final Gross Total Capacity [W] This field describes the coil’s gross total capacity, in units
of W. No fan impact. This field will generally be the main value the model uses for capacity as a
result of the sizing calculations. However if a coil was not autosized, the capacity was hard sized on
input, then this field will be filled with the hard sized coil capacity (if that is a parameter in the coil
model). This field is very similar to the field called Coil Total Capacity at Rating Conditions with
the difference being that this one is the model input while that other one is the result of running
the full coil model at the rating point conditions. Water heating coil models using UA and design
water flow rate performance input method do not have a single design capacity in Watts and this
2.28. EPLUSTBL.<EXT> 197
field will show as -99999.0 (and the coil is better characterized using the field called Coil U-value
Times Area Value). Real number.
Coil Final Gross Sensible Capacity [W] Real number. This field describes the coil’s gross sensible
capacity, if available, in units of W. No fan impact. This field is generally the total capacity
multiplied by the sensible heat ratio if both are defined in the model. Real number.
Coil Final Reference Air Volume Flow Rate [m3/s] This field describes the coil’s rated/refer-
ence/nominal air flow rate, in units of m3/s. This field will generally be the model input (or autosize
result) for the process air flow rate through the coil at the rating point. Some coil models do not
have any rated/reference/nominal air flow rate as part of the model description (d.g. electric and
gas heating coils) and these will have -999.0 in this field. Real number.
Coil Final Reference Plant Fluid Volume Flow Rate [m3/s] This field describes the coil’s rat-
ed/reference/nominal water flow rate, in units of m3/s. This field will be the model input or autosize
result for the source water, or other plant fluid type, flow rate through the coil at the design or
rating point. Many coils have no water source and these will have -999.0 in this field. Real number.
Coil U-value Times Area Value [W/K] This field describes the coil’s overall UA value, in units
of W/K. This is mainly for the Coil:Heating:Water coil using the Performance Input method of
UFactorTimesAirAndDesignWaterFlowRate and is not available for other coils. This will be the
result from the ideal loads sizing calculations or the hard sized entry. Real number.
Terminal Unit Reheat Coil Multiplier This field describes the coil sizing multiplier that might
have affected the calculated size of a coil used as a reheat coil in a zone air terminal unit. This is a
non-dimensional scaling factor. Real number.
DX Coil Capacity Increase Ratio from Too Low Flow/Capacity Ratio This field describes sizing
adjustments that can occur for DX coils when the combination of capacity and air flow rate is
outside of prescribed limits. If the air flow to capacity ratio was too low this will ratio will show
how the capacity was increased to force the result into the prescribed range. Real Number.
DX Coil Capacity Decrease Ratio from Too High Flow/Capacity Ratio This field describes sizing
adjustments that can occur for DX coils when the combination of capacity and air flow rate is
outside of prescribed limits. If the air flow to capacity ratio was too high this will ratio will show
how the capacity was decreased to force the result into the prescribed range. Real Number.
Moist Air Heat Capacity [J/kg-K] This is the moist air heat capacity, cp, that is applicable to
coil calculations. Real number.
Dry Air Heat Capacity [J/kg-K] This is the dry air heat capacity, cp, that is applicable to coil
calculations. Real number.
Standard Air Density Adjusted for Elevation [kg/m3] This is the dry air density, adjusted for
elevation above sea level, that is applicable to coil calculations. Real number.
Supply Fan Name for Coil The program tries to detect the supply fan associated with the coil.
This field is the user-defined name for that fan. Text string.
Supply Fan Type for Coil The program tries to detect the supply fan associated with the coil.
The values are the input object class name, in IDF syntax, for the fan. Text string.
Supply Fan Maximum Air Volume Flow Rate [m3/s] This field is the design volume flow rate,
in units of m3/s, for the fan found to be associated with the coil. Real number
Supply Fan Maximum Air Mass Flow Rate [kg/s] This field is the design mass flow rate, in kg/s,
for the fan found to be associated with the coil. Real number
Plant Name for Coil If the coil is a water-to-air or steam coil, then the program tries to detect
the central plant system serving the coil. This field is the user-defined name for that plant system.
This will be the name in the PlantLoop and Sizing:Plant objects. The next nine fields provides
198 CHAPTER 2. OUTPUT FILES
various results for that the central plant loop system. If the coil is not a water or steam coil, then
this field will have “unknown” as the value. Text string.
Plant Fluid Specific Heat Capacity [J/kg-K] This is the specific heat of the fluid circulating
through the plant and serving the coil, in units of J/kg-K. This is evaluated at the temperature
used for sizing calculations. The plant need not always be water, glycol mixtures and steam are
supported and this value will be adjusted accordingly. If the coil is not served by a plant, then this
field will have -999.0 as the value. Real number.
Plant Fluid Density [kg/m3] This is the density of the fluid circulating through the plant and
serving the coil, in units of kg/m3. This is evaluated at the temperature used for sizing calculations.
The plant need not always be water, glycol mixtures are supported and this value will be adjusted
accordingly. If the coil is not served by a plant, then this field will have -999.0 as the value. Real
number.
Plant Maximum Fluid Mass Flow Rate [kg/s] This field is the design flow rate for the (entire)
central plant system serving the coil, in units of kg/s. This value is the final outcome from plant
sizing calculations, or perhaps from the hard-sized value entered in the PlantLoop object for the
maximum volume flow rate. If the coil is not served by a plant, then this field will have -999.0 as
the value. Real number.
Plant Design Fluid Return Temperature [C] This is the value, in degrees Celsius, used in sizing
calculations for the temperature of the fluid returning to the supply side of the plant system.
It is derived from values entered in the Sizing:Plant object (except for steam which depends on
subcooling input). If the coil is not served by a plant, then this field will have -999.0 as the value.
Real number.
Plant Design Fluid Supply Temperature [C] This is the value, in degrees Celsius, used in the
sizing calculations for the temperature of the fluid leaving the supply side of the plant system and
going into the coils. This is the value entered in the Sizing:Plant object in the input field called
Design Loop Exit Temperature (except for steam which is 100 C). If the coil is not served by a
plant, then this field will have -999.0 as the value. Real number.
Plant Design Fluid Temperature Difference [Delta C] This is the value, in degrees Celsius (dif-
ference), used in the sizing calculations for the temperature difference between the plant supply and
return temperatures. This is the value entered in the Sizing:Plant object in the input field called
Loop Design Temperature Difference (except for steam it is the amount of subcooling in the coil).
If the coil is not served by a plant, then this field will have -999.0 as the value. Real number.
Plant Design Capacity [W] This is the design capacity of the central plant system, in Watts,
that is the result of the sizing calculations. For steam plants it is the capacity of the steam boiler
attached to the supply side of the plant. If the coil is not served by a plant, then this field will have
-999.0 as the value. Real number.
Coil Capacity Percentage of Plant Design Capacity [%] The coil being reported on here will be
one among many others that might be also be attached to the same plant. This field compares this
coil’s (design gross) total capacity to the central plant’s design capacity, W/W, and gives a value
in percentage from 0.0 to 100.0. If the coil is not served by a plant, then this field will have -999.0
as the value. Real Number.
Coil Fluid Flow Rate Percentage of Plant Design Flow Rate [%] The coil being reported on
here will be one among many others that might be also be attached to the same plant. This field
compares this coil’s design flow rate to the central plant’s design flow rate, kg/s/kg/s, and gives a
value in percentage from 0.0 to 100.0. If the coil is not served by a plant, then this field will have
-999.0 as the value. Real Number.
2.28. EPLUSTBL.<EXT> 199
Design Day Name at Sensible Ideal Loads Peak This field is the name of the design day selected
to have the sensible load peak for ideal loads sizing calculations. The text here will be from the
user-defined names entered in the name field of the SizingPeriod:DesignDay objects. If this is a
cooling coil, the load peak will be for sensible cooling loads and the name here will be from one of
the cooling design days. If this is a heating coil, the load peak will be for sensible heating loads and
the name from the heating design days. Text String.
Date/Time at Sensible Ideal Loads Peak This field provides the result for the date and time of
day when the sensible load peak was found to occur. The format is (M)M/(D)D HH:MM:00, eg.
1/1 06:00:00 or 12/11 06:00:00. There is no specific year associated with design days. Text String.
Design Day Name at Total Ideal Loads Peak The name of the design day selected to have the
total load peak for ideal loads sizing calculations. The text here will be from the user-defined names
entered in the name field of the SizingPeriod:DesignDay objects. If this is a cooling coil, the load
peak will be for total cooling loads and the name here will be from one of the cooling design days.
If this is a heating coil, this field usually “unknown” because EnergyPlus does not use a total load
for heating sizing. Text String.
Date/Time at Total Ideal Loads Peak This field provides the result for the date and time of day
when the total load peak was found to occur during ideal loads sizing. The format is (M)M/(D)D
HH:MM:00, eg. 1/1 06:00:00 or 12/11 06:00:00. There is no specific year associated with design
days. If the ideal loads sizing calculations never determine a total load the value here will be
“unknown.” Text String.
Design Day Name at Air Flow Ideal Loads Peak This field is the name of the design day selected
to have the air flow peak for ideal loads sizing calculations. The text here will be from the user-
defined names entered in the name field of the SizingPeriod:DesignDay objects. If this is a cooling
coil, the air flow peak might be calculated separately and the name here will be from one of the
cooling design days. If this is a heating coil, the air flow peak will be the same as the sensible load
peak. Text String.
Date/Time at Air Flow Ideal Loads Peak This field provides the result for the date and time of
day when the air flow peak was found to occur. The format is (M)M/(D)D HH:MM:00, eg. 1/1
06:00:00 or 12/11 06:00:00. There is no specific year associated with design days. Text String.
Coil Total Capacity at Ideal Loads Peak [W] This field is the coil’s gross total capacity, in Watts,
resulting from the ideal loads sizing calculations. This is the total, sensible plus latent, capacity
under the conditions used for ideal loads sizing described in other “Ideal Loads Peak” fields. This
does not include the supply fan impacts. Real Number.
Coil Sensible Capacity at Ideal Loads Peak [W] This field is the coil’s gross sensible capacity,
in Watts, resulting from the ideal loads sizing calculations. This is the sensible capacity under the
conditions used for ideal loads sizing described in the other “Ideal Loads Peak” fields. This does
not include the supply fan impacts. Real number.
Coil Off-Rating Capacity Modifier at Ideal Loads Peak [ ] This field is the capacity modification
factor for the conditions during ideal loads sizing. The coil model may have performance curves
that alter the capacity as a function of the conditions experienced by the coil. When the ideal loads
sizing conditions are different than the conditions that the performance curves are normalized to,
the rating point, the coil is being sized at “Off-rating.” This value can be used to convert the Coil
Total Capacity at Ideal Loads Peak to what the capacity should be at the rating point. The ideal
loads sizing is often not at the rating point because of a fraction of outdoor air has been mixed into
the entering air. Real number.
Coil Air Mass Flow Rate at Ideal Loads Peak [kg/s] This field is the coil’s air mass flow rate, in
200 CHAPTER 2. OUTPUT FILES
kg/s, resulting from, and/or used during, the ideal loads sizing calculations. Real number.
Coil Air Volume Flow Rate at Ideal Loads Peak [m3/s] This field is the coil’s air volume flow
rate, in m3/s, resulting from, and/or used during, the ideal loads sizing calculations. Real number.
Coil Entering Air Drybulb at Ideal Loads Peak [C] This field is the drybulb temperature, in
degrees Celsius, of the air entering the coil during ideal loads sizing calculations. Real number.
Coil Entering Air Wetbulb at Ideal Loads Peak [C] This field is the wetbulb temperature, in
degrees Celsius, of the air entering the coil during ideal loads sizing calculations. Real number.
Coil Entering Air Humidity Ratio at Ideal Loads Peak [kg-H2O/kg-DryAir] This field is the hu-
midity ratio, in kg-water/kg-dryAir, of the air entering the coil during ideal loads sizing calculations.
Real number.
Coil Entering Air Enthalpy at Ideal Loads Peak [J/(kg-K)] This field is the enthalpy, in J/kg-K
(base 0.0 at drybulb = 0.0◦ C), of the air entering the coil during ideal loads sizing calculations.
Real number.
Coil Leaving Air Drybulb at Ideal Loads Peak [C] This field is the drybulb temperature, in
degrees Celsius, of the air leaving the coil during the ideal loads sizing calculations for the coil.
Real number.
Coil Leaving Air Wetbulb at Ideal Loads Peak [C] This field is the wetbulb temperature, in
degrees Celsius, of the air leaving the coil during ideal loads sizing calculations. Real number.
Coil Leaving Air Humidity Ratio at Ideal Loads Peak [C] This field is the humidity ratio, in
kg-water/kg-dryAir, of the air leaving the coil during ideal loads sizing calculations. Real number.
Coil Leaving Air Enthalpy at Ideal Loads Peak [J/(kg-K)] This field is the enthalpy, in J/kg-K
(base 0.0 at drybulb = 0.0◦ C), of the air leaving the coil during ideal loads sizing calculations. Real
number.
Coil Plant Fluid Mass Flow Rate at Ideal Loads Peak [kg/s] This field is the design or maximum
water flow rate, in kg/s, of the plant fluid serving the coil during ideal loads sizing calculations. If
the coil is not a water coil then this field will have a value of -999.0. Real number.
Coil Entering Plant Fluid Temperature at Ideal Loads Peak [C] This field is the water temper-
ature, in degrees Celsius, of the plant fluid entering the coil during ideal loads sizing calculations.
If the coil is not a water coil then this field will have a value of -999.0. Real number.
Coil Leaving Plant Fluid Temperature at Ideal Loads Peak [C] This field is the water temperature,
in degrees Celsius, of the plant fluid leaving the coil during ideal loads sizing calculations. If the
coil is not a water coil then this field will have a value of -999.0. Real number.
Coil Plant Fluid Temperature Difference at Ideal Loads Peak [Delta C] This field is the water
temperature difference across the coil, in degrees Celsius (difference), of the plant fluid passing
through the coil during ideal loads sizing calculations. If the coil is not a water coil then this field
will have a value of -999.0. Real number.
Supply Fan Air Heat Gain at Ideal Loads Peak [W] This field is the fan load that was included in
the ideal loads sizing calculations. This may only be included in calculations for central air system
cooling coils. If the coil was not sized with fan heat gain taken into account, then this value will be
0.0 (even though there still is a fan with heat during normal operation). Real number.
Coil and Fan Net Total Capacity at Ideal Loads Peak [W] This field shows the net coil total
capacity which is the gross total capacity with the fan heat gain, if any was calculated. Real number.
Outdoor Air Drybulb at Ideal Loads Peak [C] This field is the outdoor air drybulb temperature,
in degrees Celsius, used during the ideal loads sizing calculations. Real number.
Outdoor Air Humidity Ratio at Ideal Loads Peak [kg-H2O/kg-DryAir] This field is the outdoor
air humidity ratio, in kg of water per kg of dry air, used during the ideal loads sizing calculations.
2.28. EPLUSTBL.<EXT> 201
Real number.
Outdoor Air Wetbulb at Ideal Loads Peak [C] This field is the outdoor air wetbulb temperature,
in degrees Celsius, used during the ideal loads sizing calculations. Real number.
Outdoor Air Volume Flow Rate at Ideal Loads Peak [m3/s] This field is the outdoor air volume
flow rate, in m3/s, that occurred during the ideal loads sizing calculations. Real number.
Outdoor Air Flow Percentage at Ideal Loads Peak [%] This field is the percentage of outdoor air
in the air entering the coil that occurred during the ideal loads sizing calculations. Real number.
System Return Air Drybulb at Ideal Loads Peak [C] This field is the drybulb temperature,
in degrees C, of air returning into the HVAC system that occurred during the ideal loads sizing
calculations. Real number.
System Return Air Humidity Ratio at Ideal Loads Peak [kg-H2O/kg-DryAir] This field is the
humidity ratio, in kg of water per kg of dry air, of air returning into the HVAC system that occurred
during the ideal loads sizing calculations. Real number.
Zone Air Drybulb at Ideal Loads Peak [C] This field is the drybulb temperature, in degrees C,
of the zone air that occurred during the ideal loads sizing calculations. For multizone system this
is the supply-air-volume-flow-weighted average. Real number.
Zone Air Humidity Ratio at Ideal Loads Peak [kg-H2O/kg-DryAir] This field is the humidity
ratio, in kg of water per kg of dry air, of the zone air that occurred during the ideal loads sizing
calculations. For multizone system this is the supply-air-volume-flow-weighted-weighted average.
Real number.
Zone Air Relative Humidity at Ideal Loads Peak [%] This field is the percent relative humidity
of the zone air that occurred during the ideal loads sizing calculations. For multizone system this
is the supply-air-volume-flow-weighted-weighted average. Real number.
Zone Sensible Heat Gain at Ideal Loads Peak [W] This field is the zone sensible load, in Watts,
found during ideal loads sizing. For multizone system it is the sum of all the zones on the air system.
Real number.
Zone Latent Heat Gain at Ideal Loads Peak [W] This field is the zone latent load, in Watts,
found during ideal loads sizing. For multizone system it is the sum of all the zones on the air system.
Real number.
Coil Total Capacity at Rating Conditions [W] This field is the gross total capacity of the coil
when operated at the rating point conditions, in units of Watts. This is the result from calculating
the full coil model under the operating conditions specified for the rating point. Real number.
Coil Sensible Capacity at Rating Conditions [W] This field is the gross sensible capacity of
the coil when operated at the rating point conditions, in units of Watts. This is the result from
calculating the full coil model under the operating conditions specified for the rating point. Real
number.
Coil Air Mass Flow Rate at Rating Conditions [kg/s] This field is the air mass flow rate, in units
of kg/s, used when calculating the full coil model under the operating conditions specified for the
rating point. Real number.
Coil Entering Air Drybulb at Rating Conditions [C] This field is the coil air inlet drybulb
temperature, in degrees Celsius, used when calculating the full coil model under the operating
conditions specified for the rating point. The value should match the definition of the rating point
as described in the coil model input documentation. For DX cooling coils, this will be 26.6667C or
80F. Real number.
Coil Entering Air Wetbulb at Rating Conditions [C] This field is the coil air inlet wetbulb
temperature, in degrees Celsius, used when calculating the full coil model under the operating
202 CHAPTER 2. OUTPUT FILES
conditions specified for the rating point. The value should match the definition of the rating point
as described in the coil model input documentation. For DX cooling coils, this will be 19.444C or
67F. Real number
Coil Entering Air Humidity Ratio at Rating Conditions [kg-H2O/kg-DryAir] This field is the
coil air inlet humidity ratio, in kg-water/kg-dryAir, used when calculating the full coil model under
the operating conditions specified for the rating point. Real number.
Coil Entering Air Enthalpy at Rating Conditions [J/(kg-K)] This field is the coil air inlet
enthalpy, in J/kg-K with zero base at 0.0◦ C, used when calculating the full coil model under the
operating conditions specified for the rating point. Real number.
Coil Leaving Air Drybulb at Rating Conditions [C] This field is the coil air outlet drybulb, in
degrees Celsius, from calculating the full coil model under the operating conditions specified for the
rating point. Real number.
Coil Leaving Air Wetbulb at Rating Conditions [C] This field is the coil air outlet wetbulb, in
degrees Celsius, from calculating the full coil model under the operating conditions specified for the
rating point. Real number.
Coil Leaving Air Humidity Ratio at Rating Conditions [kg-H2O/kg-DryAir] This field is the
coil air outlet humidity ratio, in kg-water/kg-dryair, from calculating the full coil model under the
operating conditions specified for the rating point. Real number.
Coil Leaving Air Enthalpy at Rating Conditions [J/(kg-K)] This field is the coil air outlet
enthalpy, in J/kg-K with zero base at 0.0◦ C, from calculating the full coil model under the operating
conditions specified for the rating point. Real number. Directly following is an example of the report.
The key used to obtain this report is HVACSizingSummary.
Report: HVAC Sizing Summary
For: Entire Facility
** Timestamp: **2011-09-23 15:09:34
Zone Sensible Cooling
Calculated User Design Calculated User Design Design Day Date/Time Temperature Humidity
Design Load Load [W] Design Air Air Flow Name Of Peak at Peak [C] Ratio at
[W] Flow [m3/s] [m3/s] Peak [kgWa-
ter/kgAir]
Calculated User Design Calculated User Design Design Day Date/Time Temperature Humidity
Design Load Load [W] Design Air Air Flow Name Of Peak at Peak [C] Ratio at
[W] Flow [m3/s] [m3/s] Peak [kgWa-
ter/kgAir]
Calculated User Design Calculated User Design Design Day Date/Time Temperature Humidity
Design Load Load [W] Design Air Air Flow Name Of Peak at Peak [C] Ratio at
[W] Flow [m3/s] [m3/s] Peak [kgWa-
ter/kgAir]
Calculated User Design Calculated User Design Design Day Date/Time Temperature Humidity
Design Load Load [W] Design Air Air Flow Name Of Peak at Peak [C] Ratio at
[W] Flow [m3/s] [m3/s] Peak [kgWa-
ter/kgAir]
Previous Algorithm Coincident Coincident Peak Sizing Peak Day Peak Hour Peak Step
Design Volume Design Size Period into Period Of Day Start
Volume Flow Rate Volume Adjusted Name Minute
Flow Rate [m3/s] Flow Rate
[m3/s] [m3/s]
Summary.
Report: System Summary
For: Entire Facility
Timestamp: 2007-10-17 08:54:27
Economizer
Maximum air flow rate [m3/s] Max Reheat Water Flow [m3/s]
SPACE1-1 VAV 0.226630 0.000059
REHEAT
SPACE2-1 VAV 0.176548 0.000046
REHEAT
SPACE3-1 VAV 0.209331 0.000054
REHEAT
SPACE4-1 VAV 0.222526 0.000058
REHEAT
SPACE5-1 VAV 0.221695 0.000057
REHEAT
COIL:Water:SimpleHeating
BRANCH
CONTROLLER:OUTSIDE AIR
maximum outside air flow rate minimum outside air flow rate
[m3/s] [m3/s]
OA CONTROLLER 1.06 0.264118
1
COIL:Water:Cooling
FAN:SIMPLE:VARIABLEVOLUME
CONTROLLER:SIMPLE
PLANT LOOP
BOILER:SIMPLE
CHILLER:ELECTRIC
2.28. EPLUSTBL.<EXT> 209
PUMP:VARIABLE SPEED
Average Number of Occupants Average number of occupants during occupied times (occupants
> 0) for the simulation period.
Nominal Number of Occupants Total number of people for all People objects in this zone (ig-
noring schedules).
Design Zone Outdoor Airflow - Voz The design outdoor air flow rate specified in the Design-
Specification:OutdoorAir object for this zone in m3 /s. This is the outdoor air flow rate used
for sizing without any schedule modifier.
Minimum Dynamic Target Ventilation - Voz−dyn−min The minimum outdoor air flow rate
specified in the DesignSpecification:OutdoorAir object for this zone in m3 /s. This is the
outdoor air flow rate for the minimum number of occupants without any schedule modifier.
Natural Ventilation The total outdoor air delivered to this zone by natural ventilation (Zon-
eVentilation:* or AirflowNetwork) in m3 .
2.28. EPLUSTBL.<EXT> 211
Infiltration The total outdoor air delivered to this zone by infiltration (ZoneInfiltration:* or Air-
flowNetwork) in m3 (Output:Variable Zone Infiltration Standard Density Volume Flow Rate).
Total Ventilation and Infiltration The sum of Mechanical and Natural Ventilation and Infil-
tration in m3 .
Dynamic Target Ventilation - Voz−dyn The total dynamic outdoor air flow rate specified in the
DesignSpecification:OutdoorAir object for this zone in m3 /s. This is the zone target venti-
lation flow rate Voz−dyn at standard density at the current timestep including any schedule
modifier (Output:Variable Zone Target Voz Ventilation Flow Rate).
Time Below Voz−dyn The time in hours that the Total Ventilation rate (mechanical ventilation
plus natural ventilation) is more than 1% below the Dynamic Target Ventilation - Voz−dyn
flow rate (Output:Variable Zone Ventilation Below Target Voz Time).
Time At Voz−dyn The time in hours that the Total Ventilation rate (mechanical ventilation plus
natural ventilation) is within 1% of the Dynamic Target Ventilation - Voz−dyn flow rate (Out-
put:Variable Zone Ventilation At Target Voz Time).
Time Above Voz−dyn The time in hours that the Total Ventilation rate (mechanical ventilation
plus natural ventilation) is more than 1% above the Dynamic Target Ventilation - Voz−dyn
flow rate (Output:Variable Zone Ventilation Above Target Voz Time).
Time Above Zero When Unoccupied The time in hours that the Total Ventilation rate (me-
chanical ventilation plus natural ventilation) is greater than zero when the zone is unoccupied
(Output:Variable Zone Ventilation When Unoccupied Time).
Natural Ventilation The total outdoor air delivered to the zones on this air loop by natural venti-
lation (ZoneVentilation:* or AirflowNetwork) in m3 (Output:Variable Air System Natural Ven-
tilation Flow Rate). If any zone terminal unit has a DesignSpecification:AirTerminal:Sizing
object then the natural ventilation rate for that zone is scaled by the Fraction of Minimum
Outdoor Air Flow value.
Sum Zone Dynamic Target Ventilation - Voz−dyn The total dynamic outdoor air flow rate
specified in the DesignSpecification:OutdoorAir object for the zones on this air loop in
m3 /s. This is the sum of the zone target ventilation flow rates Voz−dyn at standard density
212 CHAPTER 2. OUTPUT FILES
at the current timestep including any schedule modifier (Output:Variable Air System
Target Voz Ventilation Flow Rate). If any zone terminal unit has a DesignSpecifica-
tion:AirTerminal:Sizing object then the target ventilation rate for that zone is scaled by the
Fraction of Minimum Outdoor Air Flow value.
Time Below Voz−dyn The time in hours that the Total Ventilation rate (mechanical ventilation
plus natural ventilation) is more than 1% below the Sum Zone Dynamic Target Ventilation -
Voz−dyn flow rate (Output:Variable Air System Ventilation Below Target Voz Time).
Time At Voz−dyn The time in hours that the Total Ventilation rate (mechanical ventilation plus
natural ventilation) is within 1% of the Sum Zone Dynamic Target Ventilation - Voz−dyn flow
rate (Output:Variable Air System Ventilation At Target Voz Time).
Time Above Voz−dyn The time in hours that the Total Ventilation rate (mechanical ventilation
plus natural ventilation) is more than 1% above the Sum Zone Dynamic Target Ventilation -
Voz−dyn flow rate (Output:Variable Air System Ventilation Above Target Voz Time).
Time Above Zero When Unoccupied The time in hours that the Total Ventilation rate (me-
chanical ventilation plus natural ventilation) is greater than zero when the all zones on this
air loop are unoccupied (Output:Variable Air System Ventilation When Unoccupied Time).
Limits and Scheduled Limits Fixed limits such as Controller:OutdoorAir Minimum Outdoor
Air Flow Rate, Maximum Outdoor Air Flow Rate, Minimum Fraction of Outdoor Air Schedule
Name, Maximum Fraction of Outdoor Air Schedule Name.
Economizer Economizer is active and sets the flow greater than the minimum outdoor air fraction.
Exhaust Flow Outdoor air flow rate equals the total zone exhaust flow rate.
Mixed Air Flow Outdoor air flow rate is limited by the current mixed air flow rate.
Demand Limiting DemandManager:Ventilation has reduced the outdoor air flow rate.
2.28. EPLUSTBL.<EXT> 213
Value
Reference USA_Chicago-OHare_TMY2
Site:Location Chicago IL USA
Latitude N 41° 58’
Longitude W 87° 54’
Time Zone GMT -6.0 Hours
Elevation 190m above sea level
Standard Pressure at 99063Pa
Elevation
Data Source Release Test
WMO Station 725300
Design Conditions Climate Design Data 2005 ASHRAE Handbook
Heating Design -20.6
Temperature 99.6% (C)
Heating Design -17.3
Temperature 99% (C)
Cooling Design 33.2
Temperature 0.4% (C)
Cooling Design 31.5
Temperature 1% (C)
Cooling Design 29.9
Temperature 2% (C)
Maximum Dry Bulb 35.6°
Temperature (C)
Maximum Dry Bulb Occurs Jul 9
on
Minimum Dry Bulb -22.8°
Temperature (C)
Minimum Dry Bulb Occurs Jan 7
on
Maximum Dew Point 25.6
Temperature (C)
Maximum Dew Point Aug 4
Occurs on
Minimum Dew Point -28.9
Temperature (C)
Minimum Dew Point Dec 31
Occurs on
Heating Degree-Days (base 1745
10°C)
2.28. EPLUSTBL.<EXT> 215
Value
Cooling Degree-Days (base 464
18°C)
Köppen Classification Dfa
Köppen Description Humid continental (hot summer, cold winter, no dry
season, lat. 30-60°N)
Köppen Recommendation Unbearably humid periods in summer, but passive
cooling is possible
ASHRAE Climate Zone 5A
ASHRAE Description Cool-Humid
Total Outdoors
Wall 24 8
Floor 10 5
Roof 6 1
Internal Mass 0 0
Building Detached Shading 0 0
Fixed Detached Shading 0 0
Window 6 6
Door 0 0
Glass Door 0 0
Shading 4 4
Overhang 0 0
Fin 0 0
Tubular Daylighting Device Dome 0 0
Tubular Daylighting Device Diffuser 0 0
HVAC
216 CHAPTER 2. OUTPUT FILES
Count
HVAC Air Loops 1
Conditioned Zones 6
Unconditioned Zones 0
Supply Plenums 0
Return Plenums 1
Data
Heating Degree Days 1748
Cooling Degree Days 506
Climate Zone 5A
Weather File Chicago Ohare Intl Ap IL USA TMY3
WMO#=725300
HDD and CDD data source Weather File Stat
Total gross floor area [m2] 927.20
Principal Heating Source Natural Gas
Data
Number of hours heating loads not met 0.00
Number of hours cooling loads not met 10.75
Number of hours not met 10.75
Electricity [MJ/m2]
Interior Lighting 87.62
Space Heating 0.00
Space Cooling 19.02
Fans-Interior 7.56
Service Water Heating 0.00
Receptacle Equipment 51.44
Miscellaneous 1.66
Subtotal 167.30
Other [MJ/m2]
Miscellaneous 0.00
Subtotal 0.00
Percent [%]
Interior Lighting 18.93
Space Heating 24.22
Space Cooling 4.11
Fans-Interior 1.63
Service Water Heating 0.00
Receptacle Equipment 11.11
Miscellaneous 39.99
Equivalent Full Load Hours of Operation Per Year [hr] Hours > 1% [hr]
OCCUPY-1 2532. 3393.
LIGHTS-1 3009. 8760.
EQUIP-1 2650. 8760.
INFIL-SCH 3624. 3624.
SHADETRANSSCH 0. 0.
MIN OA SCHED 3245. 8760.
FANAVAILSCHED 5678. 5678.
COOLINGCOILAVAILSCHED 1310. 1310.
REHEATCOILAVAILSCHED 5678. 5678.
First Month 11am First Days with 11pm First Days with
Object Assumed Wednesday Same 11am Wednesday Same 11pm
Used [C] Value [C] Value
HTG- HEATING January 21.10 365 12.80 365
SETP-SCH SET-
POINT
PLENUM- PLENUM January 12.80 365 12.80 365
HTG- HEATING
SETP-SCH SET-
POINT
CLG- COOLING July 25.00 122 25.00 122
SETP- SET-
SCH3 POINT
PLENUM- PLENUM July 40.00 365 40.00 365
CLG- COOLING
SETP-SCH SET-
POINT
CLG- DUAL July 23.90 365 40.00 365
SETP-SCH SET-
POINT
This report is not reproduced here since it is well documented in the section in this document for
the eplusout.eio file.
2.28. EPLUSTBL.<EXT> 223
PlantLoopCoolingDemand-
62.41 0.00 01-JAN-00:15 27050.46 17-JUL-15:00
:Facility
PlantLoopCoolingDemand-
62.41 0.00 01-JAN-00:15 27050.46 17-JUL-15:00
:HVAC
CoolingCoils- 62.41 0.00 01-JAN-00:15 27050.46 17-JUL-15:00
:PlantLoopCoolingDemand
HVAC HVAC HVAC HVAC People Lights EquipmentWindow Interzone InfiltrationOpaque EquipmentWindow Interzone InfiltrationOpaque
Input Input Input Input Sensi- Sensi- Sensi- Heat Air Heat Sur- Sensi- Heat Air Heat Sur-
Sensi- Sensi- Heated Cooled ble ble ble Addi- Trans- Addi- face ble Re- Trans- Re- face
ble ble Sur- Sur- Heat Heat Heat tion fer tion Con- Heat moval fer moval Con-
Air Air face face Addi- Addi- Addi- [GJ] Heat [GJ] duc- Re- [GJ] Heat [GJ] duc-
Heat- Cool- Heat- Cool- tion tion tion Addi- tion moval Re- tion
ing ing ing ing [GJ] [GJ] [GJ] tion and [GJ] moval and
[GJ] [GJ] [GJ] [GJ] [GJ] Other [GJ] Other
Heat Heat
Addi- Re-
tion moval
[GJ] [GJ]
SPACE- 0.096 -0.070 0.000 0.000 0.035 0.131 0.065 0.220 0.000 0.000 0.001 0.000 -0.078 0.000 -0.004 -0.395
1-1
SPACE- 0.051 -0.038 0.000 0.000 0.014 0.056 0.028 0.173 0.000 0.000 0.001 0.000 -0.029 0.000 -0.002 -0.253
2-1
SPACE- 0.093 -0.030 0.000 0.000 0.034 0.131 0.065 0.157 0.000 0.000 0.000 0.000 -0.082 0.000 -0.004 -0.363
3-1
SPACE- 0.055 -0.015 0.000 0.000 0.015 0.056 0.028 0.105 0.000 0.000 0.000 0.000 -0.032 0.000 -0.002 -0.211
4-1
SPACE- 0.032 -0.072 0.000 0.000 0.073 0.244 0.121 0.000 0.000 0.000 0.000 0.000 0.000 0.000 -0.007 -0.392
5-1
PLE- 0.118 -0.024 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 0.000 -0.094
NUM-
1
Total 0.445 -0.248 0.000 0.000 0.170 0.618 0.307 0.655 0.000 0.000 0.002 0.000 -0.221 0.000 -0.017 -1.709
Facil-
ity
Time HVAC HVAC HVAC HVAC People Lights EquipmentWindow Interzone InfiltrationOpaque EquipmentWindow Interzone InfiltrationOp
of Input Input Input Input Sensi- Sensi- Sensi- Heat Air Heat Sur- Sensi- Heat Air Heat Su
Peak Sensi- Sensi- Heated Cooled ble ble ble Addi- Trans- Addi- face ble Re- Trans- Re- fac
ble ble Sur- Sur- Heat Heat Heat tion fer tion Con- Heat moval fer moval Co
Air Air face face Addi- Addi- Addi- [W] Heat [W] duc- Re- [W] Heat [W] du
Heat- Cool- Heat- Cool- tion tion tion Addi- tion moval Re- tio
ing ing ing ing [W] [W] [W] tion and [W] moval an
[W] [W] [W] [W] [W] Other [W] Ot
Heat He
Addi- Re
tion mo
[W] [W
SPACE- 14- 0.00 - 0.00 0.00 724.60 1584.00 739.20 9347.85 0.00 0.00 0.00 0.00 0.00 0.00 0.00 -
1-1 JAN- 3502.16 88
15:00
SPACE- 14- 0.00 - 0.00 0.00 345.99 684.00 410.40 4684.27 0.00 0.00 0.00 0.00 0.00 0.00 0.00 -
2-1 JAN- 1738.94 43
10:07
SPACE- 14- 0.00 - 0.00 0.00 761.13 1584.00 844.80 356.87 0.00 0.00 0.00 0.00 0.00 0.00 0.00 -
3-1 JAN- 1095.49 24
14:45
SPACE- 14- 0.00 - 0.00 0.00 345.95 684.00 228.00 1157.98 0.00 0.00 0.00 0.00 0.00 0.00 0.00 -
4-1 JAN- 736.19 16
16:00
SPACE- 14- 0.00 - 0.00 0.00 1135.19 2667.60 1778.40 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 -
5-1 JAN- 2315.43 32
13:35
PLE- 07- 0.00 - 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 1579.40 0.00 0.00 0.00 0.00 0.0
NUM- JUL- 1579.40
1 19:46
Total 14- 0.00 - 0.00 0.00 3561.18 7500.00 3500.00 10470.76 0.00 0.00 0.00 0.00 0.00 0.00 0.00 -
Facil- JAN- 7822.86 17
ity 15:00
Time HVAC HVAC HVAC HVAC People Lights EquipmentWindow Interzone InfiltrationOpaque EquipmentWindow Interzone InfiltrationOp
of Input Input Input Input Sensi- Sensi- Sensi- Heat Air Heat Sur- Sensi- Heat Air Heat Su
Peak Sensi- Sensi- Heated Cooled ble ble ble Addi- Trans- Addi- face ble Re- Trans- Re- fac
ble ble Sur- Sur- Heat Heat Heat tion fer tion Con- Heat moval fer moval Co
Air Air face face Addi- Addi- Addi- [W] Heat [W] duc- Re- [W] Heat [W] du
Heat- Cool- Heat- Cool- tion tion tion Addi- tion moval Re- tio
ing ing ing ing [W] [W] [W] tion and [W] moval an
[W] [W] [W] [W] [W] Other [W] Ot
Heat He
Addi- Re
tion mo
[W] [W
SPACE1- 14- 10652.50 0.00 0.00 0.00 0.00 79.20 21.12 0.00 0.00 0.00 0.00 0.00 - 0.00 0.00 -
1 JAN- 1551.57 92
07:00
SPACE2- 14- 7816.55 0.00 0.00 0.00 0.00 34.20 9.12 0.00 0.00 0.00 0.00 0.00 - 0.00 0.00 -
1 JAN- 594.65 72
07:00
SPACE3- 14- 11495.41 0.00 0.00 0.00 0.00 79.20 21.12 0.00 0.00 0.00 0.00 0.00 - 0.00 0.00 -
1 JAN- 1539.09 10
07:00
SPACE4- 14- 8837.62 0.00 0.00 0.00 0.00 34.20 9.12 0.00 0.00 0.00 0.00 0.00 - 0.00 0.00 -
1 JAN- 604.20 82
07:00
SPACE5- 14- 12359.25 0.00 0.00 0.00 0.00 148.20 39.52 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 -
1 JAN- 12
07:00
PLENUM-14- 5275.99 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 -
1 JAN- 52
07:18
Total 14- 55720.39 0.00 0.00 0.00 0.00 375.00 100.00 0.00 0.00 0.00 0.00 0.00 - 0.00 0.00 -
Facil- JAN- 4289.51 51
ity 07:15
Sum of System Sum of Occupant Uncorrected System Average System Outdoor Percent
Zone Popula- Zone Pop- Diversity - Outdoor Primary Outdoor Ventila- Air Intake Outdoor
Primary tion - ulation - D Air Intake Airflow - Air tion Flow - Air -
Air Flow - Ps Pz-sum Airflow - Vps Fraction - Efficiency Vot %OA
Vpz-sum Vou [m3/s] Xs - Ev [m3/s]
[m3/s] [m3/s]
VAV SYS 1.05 52.00 52.00 1.00 0.26 1.05 0.252 1.000 0.27 0.26
1
Sum of System Sum of Occupant Uncorrected System Average System Outdoor Percent
Zone Popula- Zone Pop- Diversity - Outdoor Primary Outdoor Ventila- Air Intake Outdoor
Primary tion - ulation - D Air Intake Airflow - Air tion Flow Vot Air -
Air Flow - Ps Pz-sum Airflow - Vps Fraction - Efficiency [m3/s] %OA
Vpz-sum Vou [m3/s] Xs - Ev
[m3/s] [m3/s]
VAV SYS 1.05 0.00 0.00 1.00 0.26 0.43 0.967 1.000 0.27 0.26
1
AirLoop People Zone Pop- Area Zone Breathing Cooling Cooling Heating Heating
Name Outdoor ulation - Outdoor Floor Zone Zone Air Zone Zone Air Zone
Air Rate - Pz Air Rate - Area - Az Outdoor Distribu- Outdoor Distribu- Outdoor
Rp [m3/s- Ra [m2] Airflow - tion Airflow - tion Airflow -
person] [m3/s-m2] Vbz Effective- Voz-clg Effective- Voz-htg
[m3/s] ness - [m3/s] ness - [m3/s]
Ez-clg Ez-htg
SPACE1- VAV SYS 0.002360 11.00 0.000305 99.16 0.0562 0.900 0.0624
1 1
SPACE2- VAV SYS 0.002360 5.00 0.000305 42.73 0.0248 0.900 0.0276
1 1
SPACE3- VAV SYS 0.002360 11.00 0.000305 96.48 0.0554 1.000 0.0554
1 1
SPACE4- VAV SYS 0.002360 5.00 0.000305 42.73 0.0248 1.000 0.0248
1 1
SPACE5- VAV SYS 0.002360 20.00 0.000305 182.49 0.1029 1.000 0.1029
1 1
People Sum of Zone Area Outdoor Sum of Zone Breathing Cooling Zone Heating Zone
Outdoor Air Population - Air Rate - Ra Floor Area - Zone Outdoor Outdoor Outdoor
Rate - Rp Pz-sum [m3/s-m2] Az-sum [m2] Airflow - Vbz Airflow - Airflow -
[m3/s-person] [m3/s] Voz-clg [m3/s] Voz-htg
[m3/s]
AirLoop Box Zone Zone Dis- Minimum Zone Primary Primary Secondary Supply Mixed Outdoor Z
Name Type Primary charge Zone Pri- Outdoor Outdoor Air Frac- Recircu- Air Air Frac- Air Frac- V
Airflow Airflow mary Airflow Air Frac- tion - lation Fraction- tion - tion - la
- Vpz - Vdz Airflow - Cooling tion - Ep Fraction- Fa Fb Fc E
[m3/s] [m3/s] Vpz-min - Voz-clg Zpz Er ci
[m3/s] [m3/s] E
AirLoop Box Zone Zone Dis- Minimum Zone Primary Primary Secondary Supply Mixed Outdoor Z
Name Type Primary charge Zone Pri- Outdoor Outdoor Air Frac- Recircu- Air Air Frac- Air Frac- V
Airflow Airflow mary Airflow Air Frac- tion - lation Fraction- tion - tion - la
- Vpz - Vdz Airflow - Cooling tion - Ep Fraction- Fa Fb Fc E
[m3/s] [m3/s] Vpz-min - Voz-clg Zpz Er ci
[m3/s] [m3/s] E
Sum of Zone System Primary Sum of Zone Minimum Zone Zone Outdoor Zone Ventilation
Primary Airflow Airflow - Vps Discharge Primary Airflow Airflow Cooling Efficiency -
- Vpz-sum [m3/s] Airflow - - Vpz-min - Voz-clg [m3/s] Evz-min
[m3/s] Vdz-sum [m3/s] [m3/s]
AirLoop Box Zone Zone Minimum Zone Primary Primary Secondary Supply Mixed Outdoor Z
Name Type Pri- Dis- Zone Out- Out- Air Recir- Air Air Air V
mary charge Pri- door door Frac- culation Fraction- Frac- Frac- ti
Airflow Airflow mary Airflow Air tion - Fraction- tion - tion - E
- Vpz - Vdz Airflow Heating Frac- Ep Fa Fb Fc c
[m3/s] [m3/s] - Vpz- - tion - Er E
min Voz-htg Zpz
[m3/s] [m3/s]
None
Sum of Zone System Primary Sum of Zone Minimum Zone Zone Outdoor Zone Ventilation
Primary Airflow Airflow - Vps Discharge Primary Airflow Airflow Heating Efficiency -
- Vpz-sum [m3/s] Airflow - - Vpz-min - Voz-htg [m3/s] Evz-min
[m3/s] Vdz-sum [m3/s] [m3/s]
have been added showing some ratios that may be useful in checking the results. When the report
is called the zone sizing calculations are repeated twice so this may result in longer simulation
times. The key used to obtain these reports are ZoneComponentLoadSummary, AirLoopCompo-
nentLoadSummary, FacilityComponentLoadSummary.
Report: ZoneComponentLoadSummary
For: SPACE1-1
Timestamp: 2012-09-21 15:48:46
Estimated Cooling Peak Load Components
Sensible - Sensible - Sensible - Latent [W] Total [W] %Grand Related Total per
Instant [W] Delayed [W] Return Air Total Area [m2] Area
[W] [W/m2]
Value
Value
Sensible - Sensible - Sensible - Latent [W] Total [W] %Grand Related Total per
Instant [W] Delayed [W] Return Air Total Area [m2] Area
[W] [W/m2]
Sensible - Sensible - Sensible - Latent [W] Total [W] %Grand Related Total per
Instant [W] Delayed [W] Return Air Total Area [m2] Area
[W] [W/m2]
Value
Value
Value
2.28.25 Output:Table:TimeBins
A TimeBins report shows a grid of the number of hours that specific report variable spend in a range
of values. The first table is broken into two parts. The first part is monthly and the second part is
for each hour of the day. The columns show the range of values. A second table is provided to show
some statistics on the report variable for the entire year including the maximum and minimum.
These statistics are helpful in setting the field values for the interval in the Output Table:TimeBins
object. Due to this, it is often necessary to run two simulations to fully utilize the TimeBins report
with the first run used to find the minimum and maximum of the variable, these values are then
used in the TimeBins object and the second run a better table of binned results are displayed.
Report: PURCHASEDCOOLING:FACILITY J per second
For: Meter
Timestamp: 2006-08-30 07:48:55
Values in table are in hours.
1 2 3 4 5 6 7 8 9 10
Interval less than 0. < = 2000. < 4000. < 6000. < 8000. < 10000. < 12000. < 14000. < 16000. < 18000. < equal to R
Start = = = = = = = = = or more
than
Interval 0. 2000. > 4000. > 6000. > 8000. > 10000. > 12000. > 14000. > 16000. > 18000. > 20000. > 20000. T
End
January 0.00 744.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 7
February 0.00 672.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 6
March 0.00 744.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 7
April 0.00 524.17 40.67 40.33 45.67 45.50 19.67 4.00 0.00 0.00 0.00 0.00 7
May 0.00 480.33 44.50 55.50 41.00 53.50 38.17 20.67 10.33 0.00 0.00 0.00 7
June 0.00 393.50 31.83 55.33 19.83 53.00 65.83 62.83 24.00 13.83 0.00 0.00 7
July 0.00 372.67 30.83 40.83 45.67 53.83 42.83 48.33 45.33 47.83 15.83 0.00 7
August 0.00 373.50 24.50 37.17 44.50 64.50 56.67 50.67 52.33 35.00 5.17 0.00 7
September 0.00 406.33 52.00 42.50 14.83 54.50 64.67 54.50 27.17 3.50 0.00 0.00 7
October 0.00 744.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 7
November 0.00 720.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 7
December 0.00 744.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 7
12:01 to 0.00 365.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3
1:00 am
1:01 to 0.00 365.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3
2:00 am
2:01 to 0.00 365.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3
3:00 am
3:01 to 0.00 365.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3
4:00 am
4:01 to 0.00 365.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3
5:00 am
5:01 to 0.00 365.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3
6:00 am
6:01 to 0.00 365.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3
7:00 am
7:01 to 0.00 294.33 33.83 25.00 5.17 2.17 1.67 1.17 1.00 0.67 0.00 0.00 3
8:00 am
8:01 to 0.00 238.00 14.17 16.50 17.00 40.33 29.67 9.33 0.00 0.00 0.00 0.00 3
9:00 am
9:01 to 0.00 231.83 14.50 13.00 21.83 38.83 31.83 12.00 1.17 0.00 0.00 0.00 3
10:00 am
10:01 to 0.00 226.33 14.00 12.50 17.50 36.50 31.33 22.17 4.67 0.00 0.00 0.00 3
11:00 am
11:01 to 0.00 221.33 12.17 13.00 14.50 30.67 33.50 27.83 11.00 1.00 0.00 0.00 3
12:00 pm
12:01 to 0.00 211.00 18.00 14.00 14.00 29.17 32.33 25.67 17.67 3.17 0.00 0.00 3
1:00 pm
1:01 to 0.00 208.00 15.00 15.33 11.00 22.17 27.83 27.50 26.83 10.83 0.50 0.00 3
2:00 pm
2:01 to 0.00 205.33 11.83 18.17 11.00 17.50 23.17 29.50 26.17 18.17 4.17 0.00 3
3:00 pm
2.28. EPLUSTBL.<EXT> 235
1 2 3 4 5 6 7 8 9 10
3:01 to 0.00 203.00 9.50 17.67 14.00 16.17 20.67 30.17 22.00 24.83 7.00 0.00 3
4:00 pm
4:01 to 0.00 201.17 10.83 18.83 13.67 16.33 19.50 29.67 22.83 25.17 7.00 0.00 3
5:00 pm
5:01 to 0.00 200.00 13.50 21.33 14.83 22.17 22.67 26.00 25.83 16.33 2.33 0.00 3
6:00 pm
6:01 to 0.00 227.33 29.17 43.17 28.33 27.50 9.50 0.00 0.00 0.00 0.00 0.00 3
7:00 pm
7:01 to 0.00 235.83 27.83 43.17 28.67 25.33 4.17 0.00 0.00 0.00 0.00 0.00 3
8:00 pm
8:01 to 0.00 365.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3
9:00 pm
9:01 to 0.00 365.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3
10:00 pm
10:01 to 0.00 365.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3
11:00 pm
11:01 to 0.00 365.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 3
12:00 am
Total 0.00 6918.50 224.33 271.67 211.50 324.83 287.83 241.00 159.17 100.17 21.00 0.00 8
Statistics
Statistic
Minimum 0.00
Mean minus two standard deviations -6496.35
Mean 1995.71
Mean plus two standard deviations 10487.78
Maximum 19476.00
Standard deviation 4246.03
2.28.26 Output:Table:Monthly
Monthly reports are not predefined. Instead each column is defined when using the Out-
put:Table:Monthly object. In that object each column is defined by a variable and how it should
be aggregated. The StandardReports.idf file is located in DataSets directory where EnergyPlus
is installed and contains a large number of examples of how to use Output:Table:Monthly to get
summaries of the performance of different components in the building model. These examples
include:
• Space Gains
• Chiller Report
• Tower Report
• Boiler Report
• DX Report
• Window Report
2.28. EPLUSTBL.<EXT> 237
• Window AC Report
• Generator Report
• Daylighting Report
• Coil Report
• Fan Report
• Pump Report
ZONE/SYS ZONE/SYS ZONE/SYS OUTDOOR OUTDOOR ZONE ZONE ZONE OUTDOOR OUTDOOR
SENSIBLE SENSIBLE SENSIBLE DRY BULB WET TOTAL TOTAL TOTAL DRY BULB WET
COOLING COOLING COOLING {AT BULB {AT INTERNAL INTERNAL INTERNAL {AT BULB {AT
ENERGY RATE RATE MAX/MIN} MAX/MIN} LATENT LATENT LATENT MAX/MIN} MAX/MIN}
[J] {MAXI- {TIMES- [C] [C] GAIN [J] GAIN GAIN [C] [C]
MUM}[W] TAMP} {MAXI- {TIMES-
MUM}[W] TAMP}
January 281755456.00 1427.84 17-JAN- 8.30 5.48 0.00 0.00 01-JAN- -4.32 -5.53
10:07 00:15
February 306879872.00 1440.59 28-FEB- 11.27 6.67 0.00 0.00 01-FEB- -3.17 -4.91
10:46 00:15
March 419829728.00 1822.13 26-MAR- 3.90 -0.20 0.00 0.00 01-MAR- -1.40 -2.84
09:14 00:15
April 752874688.00 1986.25 29-APR- 21.10 11.44 0.00 0.00 01-APR- 17.12 10.64
10:22 00:15
May 0.100670E+10 2163.18 22-MAY- 25.17 15.42 0.00 0.00 01-MAY- 3.75 1.60
09:45 00:15
June 0.100822E+10 2129.73 28-JUN- 28.02 22.39 0.00 0.00 01-JUN- 17.30 14.95
09:45 00:15
July 0.120671E+10 2312.36 08-JUL- 31.70 23.35 0.00 0.00 01-JUL- 15.60 12.95
09:00 00:15
August 0.109213E+10 2352.64 02-AUG- 27.08 20.48 0.00 0.00 01-AUG- 17.20 15.70
09:45 00:15
September 0.100619E+10 2453.23 06-SEP- 28.35 20.53 0.00 0.00 01-SEP- 16.75 15.45
10:15 00:15
October 771385600.00 2181.25 10-OCT- 15.25 10.12 0.00 0.00 01-OCT- 4.88 3.31
10:16 00:15
November 384831744.00 1566.35 11-NOV- 14.00 8.89 0.00 0.00 01-NOV- 14.65 11.75
10:45 00:15
December 246930448.00 1306.75 11-DEC- 5.00 1.69 0.00 0.00 01-DEC- 1.80 -0.11
10:07 00:15
2.28.27 UtilityCost:Tariff
Two output reports – EconomicResultSummary and TariffReport – are related to the use of Util-
ityCost:Tariff for the calculation of annual utility costs. Since EnergyPlus 8.6, these reports are
no longer generated and need to be specifically requested. To get the reports individually use Eco-
nomicResultSummary and TariffReport in the Output:Table:SummaryReports object. These
are also available when using any of the AllSummary options.
The first report is a summary across multiple tariffs and is called the Economics Results Sum-
mary report and is shown directly below. After that example is an example of the Tariff report
which is created for each of the UtilityCost:Tariff Objects defined in the IDF file (some columns
may be truncated due to page size).
Report: Economics Results Summary Report
For: Entire Facility
Timestamp: 2006-08-29 07:21:57
Annual Cost
Tariff Summary
The following is an example of the Tariff report which is created for each of the UtilityCost:Tariff
objects defined in the file.
Report: Tariff Report
For: EXAMPLEA
Timestamp: 2006-08-29 07:21:57
Parameter
Meter ELECTRICITY:FACILITY
Selected No
Group (none)
Qualified Yes
Disqualifier n/a
Computation automatic
Units kWh
240 CHAPTER 2. OUTPUT FILES
Categories
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Sum
EnergyCharges
181.84 159.97 170.98 178.85 207.28 207.97 249.10 234.09 202.57 191.20 169.19 176.34 2329.36
DemandCharges
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
ServiceCharges
2.51 2.51 2.51 2.51 2.51 2.51 2.51 2.51 2.51 2.51 2.51 2.51 30.12
Basis 184.35 162.48 173.49 181.36 209.79 210.48 251.61 236.60 205.08 193.71 171.70 178.85 2359.48
Adjustment 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
Surcharge 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
Subtotal 184.35 162.48 173.49 181.36 209.79 210.48 251.61 236.60 205.08 193.71 171.70 178.85 2359.48
Taxes 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
Total 184.35 162.48 173.49 181.36 209.79 210.48 251.61 236.60 205.08 193.71 171.70 178.85 2359.48
Charges
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Sum Max
FLAT 181.84 159.97 170.98 178.85 207.28 207.97 249.10 234.09 202.57 191.20 169.19 176.34 2329.36 249.
EN-
ERGY
CHARGE
Ratchets
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Sum Max
Qualifies
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Sum Max
Native Variables
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Sum
Total- 3285.70 2890.52 3089.52 3231.79 3745.42 3757.86 4501.09 4229.79 3660.28 3454.82 3057.13 3186.33 42090.2
Energy
Total- 12.52 12.53 12.53 14.53 17.40 20.71 21.08 19.50 18.63 15.53 12.90 12.55 190.42
Demand
Peak- 3285.70 2890.52 3089.52 3231.79 3745.42 3757.86 4501.09 4229.79 3660.28 3454.82 3057.13 3186.33 42090.2
Energy
Peak- 12.52 12.53 12.53 14.53 17.40 20.71 21.08 19.50 18.63 15.53 12.90 12.55 190.42
Demand
Shoulder- 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
Energy
Shoulder- 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
Demand
OffPeak- 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
Energy
OffPeak- 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
Demand
MidPeak- 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
Energy
MidPeak- 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
Demand
Peak- 12.52 12.53 12.53 14.53 17.40 20.71 21.08 19.50 18.63 15.53 12.90 12.55 190.42
Exceeds-
OffPeak
OffPeak- 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
Exceeds-
Peak
Peak- 12.52 12.53 12.53 14.53 17.40 20.71 21.08 19.50 18.63 15.53 12.90 12.55 190.42
Exceeds-
MidPeak
Mid- 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
Peak-
Exceeds-
Peak
2.28. EPLUSTBL.<EXT> 241
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Sum
Peak- 12.52 12.53 12.53 14.53 17.40 20.71 21.08 19.50 18.63 15.53 12.90 12.55 190.42
Exceeds-
Shoulder
Shoulder- 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
Exceeds-
Peak
IsWinter 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 12.00
IsNot- 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
Winter
IsSpring 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
IsNot- 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 12.00
Spring
Is- 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
Summer
IsNot- 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 12.00
Summer
Is- 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
Autumn
IsNot- 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 1.00 12.00
Autumn
Peak- 3285.70 2890.52 3089.52 3231.79 3745.42 3757.86 4501.09 4229.79 3660.28 3454.82 3057.13 3186.33 42090.2
And-
Shoulder-
Energy
Peak- 12.52 12.53 12.53 14.53 17.40 20.71 21.08 19.50 18.63 15.53 12.90 12.55 190.42
And-
Shoulder-
Demand
Peak- 3285.70 2890.52 3089.52 3231.79 3745.42 3757.86 4501.09 4229.79 3660.28 3454.82 3057.13 3186.33 42090.2
AndMid-
Peak-
Energy
Peak- 12.52 12.53 12.53 14.53 17.40 20.71 21.08 19.50 18.63 15.53 12.90 12.55 190.42
AndMid-
Peak-
Demand
Shoulder- 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
AndOff-
Peak-
Energy
Shoulder- 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
AndOff-
Peak-
Demand
Peak- 3285.70 2890.52 3089.52 3231.79 3745.42 3757.86 4501.09 4229.79 3660.28 3454.82 3057.13 3186.33 42090.2
AndOff-
Peak-
Energy
Peak- 12.52 12.53 12.53 14.53 17.40 20.71 21.08 19.50 18.63 15.53 12.90 12.55 190.42
AndOff-
Peak-
Demand
Other Variables
Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Sum
NotIncluded
0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00 0.00
<SiteAndSourceEnergy>
<name>NetSiteEnergy</name>
<TotalEnergy units = “kBtu”>200671.97</TotalEnergy>
<EnergyPerTotalBuildingArea units = “kBtu/ft2”>143.32</EnergyPerTotalBuildingArea>
<EnergyPerConditionedBuildingArea units = “kBtu/ft2”>143.32</EnergyPerConditionedBuildingArea
</SiteAndSourceEnergy>
<SiteAndSourceEnergy>
<name>TotalSourceEnergy</name>
<TotalEnergy units = “kBtu”>442504.19</TotalEnergy>
<EnergyPerTotalBuildingArea units = “kBtu/ft2”>316.04</EnergyPerTotalBuildingArea>
<EnergyPerConditionedBuildingArea units = “kBtu/ft2”>316.04</EnergyPerConditionedBuildingArea
</SiteAndSourceEnergy>
<SiteAndSourceEnergy>
<name>NetSourceEnergy</name>
<TotalEnergy units = “kBtu”>397810.98</TotalEnergy>
<EnergyPerTotalBuildingArea units = “kBtu/ft2”>284.12</EnergyPerTotalBuildingArea>
<EnergyPerConditionedBuildingArea units = “kBtu/ft2”>284.12</EnergyPerConditionedBuildingArea
</SiteAndSourceEnergy>
An actual file will be much longer than this example but follows this format.
2.29 readvars.rvaudit
This file is available from standard EnergyPlus runs (batch file, EP-Launch, etc) where the included
utility “ReadVarsESO” is used to create .csv or other delimited files. It shows what steps were taken
during the read vars run(s) – in standard EnergyPlus runs there are two: one for the .eso file and
one for the .mtr file. Note that ReadVarsESO will not be run if native CSV output is generated
with OutputControl:Files. Contents might be:
Mon 04/02/2007 19:34:17.09 ReadVars
ReadVarsESO
processing:eplusout.inp
input file:eplusout.eso
output file:eplusout.csv
found/finding:
1 Outdoor Dry Bulb
6 Zone/Sys Air Temperature
6 Zone/Sys Sensible Cooling Rate
6 Zone/Sys Sensible Heating Rate
6 Total Water Heating Coil Rate
1 Total Water Cooling Coil Rate
1 Sensible Water Cooling Coil Rate
2 Plant Loop Cooling Demand
2 Plant Loop Heating Demand
1 Boiler Gas Consumption Rate
1 Boiler Heating Output Rate
1 Chiller Electric Power
2.30. EPLUSOUT.SVG 245
2.30 eplusout.svg
This is a Scalable Vector Graphics (SVG) file that shows a diagram of the HVAC system from the
inputs of the simulation. The diagram is generated for most HVAC systems but a few valid HVAC
configurations cannot be displayed correctly. The SVG file is generated by the HVAC Diagram
utility that is included with EnergyPlus and is run automatically when using EP-Launch.
The SVG format is a graphics format that includes a descriptions of lines, boxes, text, etc. set
in a two dimensional perspective. To learn more about the SVG format see:
https://www.w3.org/Graphics/SVG/
Several viewers are available so that you can view these files including plug-ins for Internet
Explorer by Adobe and Corel. The Adobe SVG plug in can be found at:
https://www.adobe.com/svg/viewer/install/
But many different viewers are available and links are shown at:
https://www.svgi.org/
An example of a diagram generated by HVAC Diagram is shown
A close up of one part of this diagram is shown below
The SVG file format is an XML based format so it is text based. The diagram shown above is
shown below in text (reduced).
<?xml version = “1.0” standalone = “no”?>
<!DOCTYPE svg>
<svg width = “250mm” height = “200mm” viewBox = “0 0 3200 1500” xmlns:ev =
“https://www.w3.org/2001/xml-events” xmlns:xlink = “https://www.w3.org/1999/xlink” xmlns =
“https://www.w3.org/2000/svg” preserveAspectRatio = “xMidYMid meet” zoomAndPan = “mag-
nify”>
<g font-family = “Verdana” font-size = “8”>
246 CHAPTER 2. OUTPUT FILES
Figure 2.11:
Figure 2.12:
2.30. EPLUSOUT.SVG 247
2.31 eplusout.sci
This is the surface cost information report. This report file is obtained by including the following
in the input file:
Output:Surfaces:List, CostInfo;
The intent is to make available a separate file that lists the unique surfaces and their construction
types for potential use in external calculations that need to estimate the cost of construction. Note
that such cost estimating can now also be performed internal to EnergyPlus using Cost Estimate
objects. The listing can also be used to check that the input for surfaces is producing the expected
areas (although the DXF is probably more useful for such checking).
The output file contains a list of the unique surfaces and their net and gross areas. The area
information is calculated by EnergyPlus from the vertices entered for individual surfaces. The
net area is the area remaining after the areas of subsurfaces are subtracted. The file contains six
columns of comma-separate-data as shown in the following table:
Column Description
1 Integer counter for surfaces. The surfaces are listed in the or-
der that they are stored internally in EnergyPlus. Note that in
this report, the algorithms sort out and exclude duplicate sur-
faces that are entered for the interior partitions between adja-
cent thermal zones. Therefore the list is usually not consecutive.
2 The name of the surface entered by the user
3 The name of the construction for the surface entered by the user
4 The type of the surface (e.g. wall, roof, floor, window …)
5 The net area of the surface in m
6 The gross area of the surface in m
2.32 eplusout.wrl
The VRML output report file is formatted according to the “Virtual Reality Modeling Language”
standard rules for representing building type surfaces. The file can be used in several inexpensive,
shareware or freeware viewers. There are a variety of stand alone and viewers integrated within
browsers. A good list of viewers can be found at:
2.32. EPLUSOUT.WRL 249
https://cic.nist.gov/vrml/vbdetect.html
This site detects what, if any, VRML plugin is installed in your browser as well as gives a list
of active ones with links to their sites.
This file is generated when the following line is included in the IDF.
Output:Surfaces:Drawing, VRML;
In addition, like the DXF output, you can ask it to triangulate (algorithm within EnergyPlus)
surfaces with >4 sides:
Output:Surfaces:Drawing, VRML, Triangulate 3dface;
Most viewers will illustrate a solid model by default:
With some/many viewers, you can also see a wireframe model; some will even fill this model.
Also, viewers can triangulate any surface that isn’t labeled as “convex” by the software writing the
file (i.e. EnergyPlus). However, this triangulation may not be correct so you may wish to do it from
within EnergyPlus as illustrated above.
A wireframe model of the same building as above is:
The actual file produced is a text file. EnergyPlus adds some comments, such as the list of
zone names and surface names before each coordinate specification. The line/solid colors are set as
Floor, Wall, etc. so the file is somewhat readable.
#VRML V2.0 utf8
WorldInfo {
title "Building - Building"
info [" EnergyPlus Program Version EnergyPlus <version >, 9/14/2006 1:31 PM"]
}
# Zone Names
# Zone = 1:PLENUM -1
# Zone = 2:SPACE1 -1
250 CHAPTER 2. OUTPUT FILES
# Zone = 3:SPACE2 -1
# Zone = 4:SPACE3 -1
# Zone = 5:SPACE4 -1
# Zone = 6:SPACE5 -1
Shape {
appearance DEF FLOOR Appearance {
material Material { diffuseColor 0.502 0.502 0.502 }
}
}
2.33.2 eplusout.delightout
Following completion of an EnergyPlus run that includes Daylighting:Controls objects that use the
DElight Daylighting Method, an ASCII text file created during the run is given a file name that
consists of the project name appended with DElight.out (e.g., MyProjectDElight.out).
This text file is a formatted DElight output file that was generated by the DElight simulation
engine following the pre-processing daylight factors calculation. This file can be manually reviewed
to see the results of these calculations. The file contains an echo of DElight input data, as well as
the results of intermediate calculations such as geometrical transformations, surface gridding, and
daylight factors, including the following.
Surface Data
• Vertex coordinates in the Building coordinate system. Search for the string “BldgSys-
tem_Surface_Vertices” within the output file.
• Exterior face luminance values under overcast skies, and for each sun position under clear
skies. Search for the string “Surface Exterior Luminance” within the output file.
• Common data for radiosity nodal patches for each surface including Area and Number of
Nodes. Search for the string “Surface_Node_Area” within the output file.
252 CHAPTER 2. OUTPUT FILES
• Individual data for radiosity nodal patches for each node on each surface including: building
coordinate system coordinates; direct and total luminance values under overcast skies, and for
each sun position under clear skies. Search for the string “BldgSystem_Node_Coordinates”
within the output file.
• Illuminance values from the daylighting factors preprocessor for overcast skies, and for each
sun position under clear skies.
• Daylight Factor values from the daylighting factors preprocessor for overcast skies, and for
each sun position under clear skies.
• NOTE: The Monthly Average data for Daylight Illuminances and Electric Lighting Reduction
will all be zero since these data are not calculated as part of the pre-processing done by the
point at which this output file is generated for EnergyPlus.
Chapter 3
The EnergyPlus install includes a sample of example input files. For the most part, the developers
create these files to illustrate and test a specific feature in EnergyPlus. Then, we pass them along
to you for illustrative purposes. The install contains two spreadsheet files related to the example
files:
• ExampleFiles.xls - lists all the files available – whether through the install or through an
external site.
Following convention, each example file should have at the top a set of comments that tell what
the purpose of the file is and the key features.
For example, the file titled “5ZoneAirCooled.idf” has:
! 5ZoneAirCooled.idf
! Basic file description: 1 story building divided into 4 exterior and one interior conditioned zones
and return plenum.
!
! Highlights: Electric chiller with air cooled condenser; autosized preheating and
precooling water coils in the
! outside air stream controlled to preheat and precool setpoints.
!
! Simulation Location/Run: CHICAGO_IL_USA TMY2 -94846 , 2 design days , 2 run periods ,
! Run Control executes the run periods using the weather file
!
! Location: Chicago , IL
!
! Design Days: CHICAGO_IL_USA Annual Heating 99% Design Conditions DB , MaxDB = -17.3°C
! CHICAGO_IL_USA Annual Cooling 1% Design Conditions , MaxDB = 31.5 °C MCWB =
23.0 °C
!
! Run Period (Weather File): Winter 1/14, Summer 7/7, CHICAGO_IL_USA TMY2 -94846
!
! Run Control: Zone and System sizing with weather file run control (no design days run)
!
! Building: Single floor rectangular building 100 ft x 50 ft. 5 zones - 4 exterior , 1 interior , zone
height 8 feet.
! Exterior zone depth is 12 feet. There is a 2 foot high return plenum: the overall building
height is
! 10 feet. There are windows on all 4 facades; the south and north facades have glass doors.
! The south facing glass is shaded by overhangs. The walls are woodshingle over plywood , R11
insulation ,
253
254 CHAPTER 3. EXAMPLE INPUT FILES
! and gypboard. The roof is a gravel built up roof with R-3 mineral board insulation and
plywood sheathing.
! The windows are of various single and double pane construction with 3mm and 6mm glass and
either 6mm or
! 13mm argon or air gap. The window to wall ratio is approxomately 0.29.
! The south wall and door have overhangs.
!
! The building is oriented 30 degrees east of north.
!
In addition to the idf files, usually an .rvi and perhaps a .mvi of the same file set is included.
As discussed previously, the .rvi is used with the ReadVarsESO post-processing program and the
.eso file to create a .csv file which can be read easily into ExcelTM . Like the .rvi, the .mvi file can
be used with the .mtr file to create a similar version for “metered” outputs.
Chapter 4
Data Sets
Data sets are the EnergyPlus answer to “libraries”. Data sets come in two flavors – a simple list and
a “macroized” list. Macroized lists are files that could have the elements extracted using a simple
macro name.
! AirCooledChillers .idf
!
! This dataset includes performance curves for object type Chiller:Electric:EIR
!
! Summary Table for Electric EIR Chiller reference data sets.
! Chillers are listed in order of reference capacity. Reference capacity and COP do not necessarily
! indicate rated capacity and COP at standard rating conditions (e.g. ARI Standard 550/590).
!
! Performance curves developed from information collected from manufacturer 's catalog data
! The nomenclature used for the chiller is as follows:
! ElectricEIRChiller - Manufacturer 's Name - Model - Reference Capacity in kW - Reference COP
!
! Compressor Reference Reference
! Chiller Name Type Capacity COP
! kW (tons)
! ElectricEIRChiller McQuay AGZ010BS 34.5 kW /2.67 COP Scroll 34.5 (9.8) 2.67
! ElectricEIRChiller McQuay AGZ013BS 47.1 kW /2.67 COP Scroll 47.1 (13.4) 2.67
! ElectricEIRChiller York YCAL0019EE 54.2 kW /2.9 COP Scroll 54.2 (15.4) 2.9
! ElectricEIRChiller McQuay AGZ017BS 54.5 kW /2.67 COP Scroll 54.5 (15.5) 2.67
4.1.2 ASHRAE_2005_HOF_Materials.idf
This reference data set contains content from two chapters in the ASHRAE 2005 Handbook of
Fundamentals, Chapter 30 - the Cooling and Heating Loads calculations chapter has both materials
with thermal properties and constructions for Light, Medium, and Heavy buildings. Chapter 25
contains details thermal properties of many materials – no constructions are created from that data.
256
4.1. SIMPLE LIST DATA SETS 257
The following materials and constructions are created from ASHRAE Handbook of Funda-
mentals, 2005, Chapter 30, Table 19 and Table 22. These are representative of materials and
constructions used in Cooling and Heating Load Calculations.
4.1.3 Boilers.idf
This dataset includes performance curves for non-electric boilers. Reference: Condensing Technol-
ogy, Technical Series, Viessmann, 9446 803 - 1 GB Nov. 2004.
4.1.4 California_Title_24-2008.idf
This dataset includes occupancy data and non-residential schedules for California Title 24-2008
compliance calculations when lighting plans are submitted for the Entire Building or when lighting
compliance is not performed. Data is based on Table N2-5 of the 2008 Non-residential ACM Manual.
4.1.5 Chillers.idf
This dataset includes object types for specific (by manufacturer and type) Chiller:Electric:EIR and
Chiller: Electric:ReformulatedEIR and associated performance curves.
Knowing the type of chiller that you want to simulate, you can find it and the associated
performance curves in the dataset file. By example, here is part of the comments in the Chiller.idf
file:
! Summary Table for Electric EIR Chiller reference data sets (Ref. CoolTools project).
! Chillers are listed in order of compressor type and reference capacity (model calibration
! point). Reference capacity and COP do not necessarily indicate rated capacity and COP at
! standard rating conditions (e.g. ARI Standard 550/590).
!
! Performance curves developed from information collected over a 10-year period from 1991 to 2001.
!
! Compressor Reference Reference Unloading
! Chiller Name Type Capacity COP Mechanism
! kW (tons)
!-------------------------------------------------------------------------------------------------
! ElectricEIRChiller McQuay WSC 471kW /5.89 COP/Vanes Centrifugal 471 (134) 5.89 Inlet Vanes
! ElectricEIRChiller York YT 563kW /10.61 COP/Vanes Centrifugal 563 (160) 10.61 Inlet Vanes
! ElectricEIRChiller McQuay PEH 703kW /7.03 COP/Vanes Centrifugal 703 (200) 7.03 Inlet Vanes
! ElectricEIRChiller Carrier 23XL 724kW /6.04 COP/Vanes Centrifugal 724 (206) 6.04 Inlet Vanes
4.1.6 CodeCompliantEquipment.idf
This dataset includes performance curve objects that describe the part load performance of building
energy code minimally compliant equipment. The dataset provides curves for the following Ener-
gyPlus objects: Chiller:Electric:EIR. Sets of curves are provided for the following building energy
codes minimum requirements: ASHRAE Standard 90.1-2019 Table 6.8.1-3, ASHRAE Standard
90.1-2019 Table G3.5.3.
Generating performances curves meeting both full and part load efficiency numbers require
solving a largely underdetermined system of equations. The number of unknowns depend on the
type of curves, which mostly depend on the algorithm used by the software and used in models.
It also means that an infinite number of solutions exists. One way to solve this issue is to turn it
into a constrained problem and use a simple genetic algorithm (GA) with a well-defined objective
258 CHAPTER 4. DATA SETS
or cost function to determine potential solutions with physical significance. A GA can have a
short computational time, be scalable, versatile, find solutions to problems with large number of
parameters to problems with multiple local optima so it is a good candidate for this task. The
algorithm used to generate the curves in this dataset starts with a “seed” set of curves that can be
user-modifiable, target full load, and part load efficiency as inputs.
Among others, a “nearest neighbor” type method was developed to aggregate sets of curves
and generate a generic set of curves for a specific target to be used as “seed” set of curves to the
aforementioned algorithm. This method selects the N sets of performance curves that best match
the targeted equipment characteristics in terms of capacity, full load efficiency, part load efficiency,
and other applicable characteristics. Each selected sets of curves are scored based on how close it is
to the targeted equipment characteristics. A wide mesh of values for each input variable(s) to each
curve is then created and corresponding output calculated. The outputs are then weighted average
based on their previously determined score. A regression and normalization at rated conditions is
then performed to obtain the aggregated curves.
!----------------------------------------------------------
!- Beginning of performance curves for Chiller:Electric:EIR:
Curve:Quadratic ,
ASHRAE901_AppG_wtr_cent_gte150lt300ton_0 .634 kWpton_0 .596 IPLV.IP_eir -f-plr , !- Name
0.30662667381140624 , !- Coefficient1 Constant
0.06295923908320235 , !- Coefficient2 x
0.6358315679053916 , !- Coefficient3 x2
0.0, !- Minimum Value of x
1.0, !- Maximum Value of x
, !- Minimum Curve Output
; !- Maximum Curve Output
4.1.7 CompositeWallConstructions.idf
The Reference Data Set CompositeWallConstructions.idf contains constructions and associated ma-
terials for a set of composite walls. These are walls—such as stud walls—that have complicated
heat-flow paths so that the conduction is two- or three-dimensional.
An example entry in this data set–for an insulated 2”x4” steel-stud wall–looks like:
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 En-
ergy Simulation Programs (1145-TRP),” by Enermodal Engineering Limited, Oak Ridge National
Laboratory, and the Polish Academy of Sciences, January 2001. EnergyPlus will calculate conduc-
tion 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.
Following is a summary of the constructions in the composite wall data set:
! Wall system is made of two 3" concrete slabs separated by 2" rigid insulation.
! The slab connectors are plasic ties with a 0.25" x0 .25" cross section.
! Layers are 3" concrete , 2" polystyrene , 3" concrete.
! Area -average R-Value = 10.582 ft2 -F-h/Btu (1.862 m2 -K/W).
4.1.8 DXCoolingCoil.idf
This dataset includes performance curves for the object types Coil:Cooling:DX:SingleSpeed and
Coil:Cooling:DX:TwoStageWithHumidityControlMode. This data set is developed by using catalog
data published by different manufacturers which are listed in the file.
Here is a synopsis of the DXCoolingCoil.idf:
4.1. SIMPLE LIST DATA SETS 261
! DXCoolingCoil.idf
!
! This dataset includes performance curves for the object types Coil:Cooling:DX:SingleSpeed and
! Coil:Cooling:DX: TwoStageWithHumidityControlMode
!
! Reference capacity at standard rating conditions (ARI 95F OAT , 67F EWBT and air flow rate
! around 400 cfm/Ton).
!
! In the objects Coil:Cooling:DX:SingleSpeed and Coil:Cooling:DX: TwoStageWithHumidityControlMode
! below , input fields 'Availability Schedule Name ', 'Air Inlet Node Name ' and 'Air Outlet Node
! Name ' need to be defined by the user.
!
!------------------------------------------------------------------------------------------------!
Compressor Nominal Reference Reference Refrig Expansion
! Valve
! Name Type Capacity Capacity COP Type Type
! (tons) kW (tons)
!------------------------------------------------------------------------------------------------!
Carrier Centurion 50 PG06 Scroll 5 18.28(5.2) 4.15 R -410A TXV
! Carrier Centurion 50 PG12 Scroll 10 36.79(10.47) 4.05 R -410A TXV
! Carrier Centurion 50 PG24 Scroll 20 73.81(21) 3.95 R -410A TXV
Coil:Cooling:DX:SingleSpeed ,
Carrier Centurion 50PG06 , !- Name
CoolingCoilAvailSched , !- Availability Schedule Name
18276.96 , !- Rated Total Cooling Capacity {W}
0.74, !- Rated Sensible Heat Ratio
4.15, !- Rated COP
0.944 , !- Rated Air Flow Rate {m3/s}
, !- Rated Evaporator Fan Power Per Volume Flow Rate {W/(m3/s)}
DXCoilAirInletNode , !- Air Inlet Node Name
DXCoilAirOutletNode , !- Air Outlet Node Name
CarrierCenturion50PG06CapFT , !- Total Cooling Capacity Function of Temperature Curve Name
CarrierCenturion50PG06CapFFF , !- Total Cooling Capacity Function of Flow Fraction Curve Name
CarrierCenturion50PG06EIRFT , !- Energy Input Ratio Function of Temperature Curve Name
CarrierCenturion50PG06EIRFFF , !- Energy Input Ratio Function of Flow Fraction Curve Name
Carrier Centurion 50 PG06 PLFFPLR; !- Part Load Fraction Correlation Curve Name
Curve:Biquadratic ,
CarrierCenturion50PG06CapFT , !- Name
0.9953455 , !- Coefficient1 Constant
-0.0118418 , !- Coefficient2 x
0.0012277 , !- Coefficient3 x**2
0.0030246 , !- Coefficient4 y
-0.0000702 , !- Coefficient5 y**2
-0.0003685 , !- Coefficient6 x*y
12.22 , !- Minimum Value of x
26.67 , !- Maximum Value of x
15.56 , !- Minimum Value of y
51.67 , !- 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 ,
CarrierCenturion50PG06EIRFT , !- Name
0.3802131 , !- Coefficient1 Constant
0.0199468 , !- Coefficient2 x
-0.0006682 , !- Coefficient3 x**2
262 CHAPTER 4. DATA SETS
0.0058933 , !- Coefficient4 y
0.0004646 , !- Coefficient5 y**2
-0.0004072 , !- Coefficient6 x*y
12.22 , !- Minimum Value of x
26.67 , !- Maximum Value of x
15.56 , !- Minimum Value of y
51.67 , !- 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:Quadratic ,
CarrierCenturion50PG06CapFFF , !- Name
0.7705358 , !- Coefficient1 Constant
0.2848007 , !- Coefficient2 x
-0.0580891 , !- Coefficient3 x**2
0.75, !- Minimum Value of x
1.25; !- Maximum Value of x
Curve:Quadratic ,
CarrierCenturion50PG06EIRFFF , !- Name
1.3439758 , !- Coefficient1 Constant
-0.5111244 , !- Coefficient2 x
0.1732549 , !- Coefficient3 x**2
0.75, !- Minimum Value of x
1.25; !- Maximum Value of x
Curve:Quadratic ,
CarrierCenturion50PG06PLFFPLR , !- Name
0.85, !- Coefficient1 Constant
0.15, !- Coefficient2 x
0.0, !- Coefficient3 x**2
0.0, !- Minimum Value of x
1.0; !- Maximum Value of x
4.1.9 ElectricGenerators.idf
This dataset includes inputs for the GENERATOR:MICROTURBINE object and associated per-
formance curves. The performance curves were developed from manufacturer data collected in
Summer 2007.
Includes data for generators: Capstone C65, Elliott TA100, Ingersoll Rand MT70, Ingersoll
Rand MT250.
Further documentation is contained in the dataset file.
Torcellini, Paul; Long, Nicholas; Judkoff, Ron; “Consumptive Water Use for U.S. Power Produc-
tion”;NREL Report No. TP-550-33905. Golden, CO; 2003; https://www.nrel.gov/docs/fy04osti/
33905.pdf;
or
Torcellini, Paul; Long, Nicholas; Judkoff, Ron; “Consumptive Water Use for U.S. Power Pro-
duction”; ASHRAE Transactions 2003, Vol 110, Part 1. Atlanta, GA; January 2004;
4.1.11 ElectronicEnthalpyEconomizerCurves.idf
These curves approximate the electronic (variable) enthalpy curves used to simulate humidity biased
economizer control. This control scheme adjusts the upper outdoor air humidity ratio based on
outdoor air dry-bulb temperature as shown in the figure below. California Title 24 ACM 2005 lists
the optional economizer control strategies. One of these control strategies is referred to as variable
enthalpy control curve A. This control strategy is also cited in ASHRAE Standard 90.1-2004, using
the term “electronic enthalpy”. Electronic enthalpy curves A-D are included in this dataset.
Figure 4.1: Psychrometric Chart Illustration of the Electronic (Variable) Enthalpy Economizer
Limit Example Curve Objects
For the curves provided, curve A has the highest limit and curve D has the lowest limit. These
curve objects represent a single-point electronic enthalpy control curve with the curve object’s min-
imum value of x (temperature) crossing the psychrometric chart’s saturation line and the curve
object’s maximum value of x crossing the psychrometric chart’s dry-bulb temperature axis. The
264 CHAPTER 4. DATA SETS
curve object’s minimum (maximum) value of x should be just low (high) enough to ensure that the
curve crosses the psychrometric chart’s saturation line (temperature axis). The curves are evaluated
at an outdoor dry-bulb temperature to provide a maximum operating outdoor humidity ratio for
economizer operation. If the outdoor humidity ratio is greater than this maximum value, econo-
mizer operation is terminated. These curves may be used with other economizer limits to create
multi-point economizer control (Temperature Limit, Temperature Low Limit, Enthalpy Limit, and
Dewpoint Temperature Limit).
NOTE: modifying the RH multiplier (-0.144599) tends to “wag” the curvature at the upper
relative humidities. Decreasing the multiplier “wags” the upper portion of the curve downward,
increasing “wags” it upwards. Modifying the constant (K) moves the intersection of the curve with
the Dry-Bulb Temperature axis. Increasing the constant moves the intersection to the left as shown
in the figure, decreasing moves to the right. The minimum and/or maximum x boundaries in the
curve objects may have to be adjusted when modifying the equation.
The method described here was used to create each of the four “cubic” curve objects provided in
the electronic enthalpy economizer control data set.
4.1. SIMPLE LIST DATA SETS 265
Step 1: Substitute the curve constant K for curve A (12) into the electronic enthalpy curve
equation and solve for temperature. Then identify the outdoor air dry-bulb temperatures at known
values of relative humidity (e.g., columns 1 and 2 in the table below). Psychrometric routines are
helpful for this step.
12 − 45.672192 + 0.144599 · RelativeHumidity
Temperature = (4.2)
−1.1559942
Step 2: Identify humidity ratio at each point (e.g. column 3 in the following table). Psychro-
metric routines are helpful for this step.
Step 3: Use multiple linear regression to solve one of the following equations:
Quadratic Curve: Humidity Ratio = A0 + A1*Temperature + A2*Temperature2
Cubic Curve: Humidity Ratio = A0 + A1*Temperature + A2*Temperature2 +
A3*Temperature3
Step 4: Use the coefficients calculated in the multiple linear regression to create a cubic (or
quadratic) curve object.
4.1.14 FluidPropertiesRefData.idf
This data set includes fluid properties reference data. Fluid properties for R404a, R407a, R410a,
R505a, R744, were developed using the NIST Standard Reference Database 23, NIST Reference
Thermodynamic and Transport Properties – REFPROP, April 2007 Version 8.0, National Institute
of Standards and Technology, 2007. The other refrigerants were developed using older versions of
the NIST Standard Reference Database. The entire data set includes:
Refrigerants
R11
R12
R22
R123
R134a
R404a
R410a
R507a
NH3
Steam
R744
To use the data, copy the appropriate data for the refrigerant you desire into your input file.
4.1.15 GlycolPropertiesRefData.idf
This data set includes fluid properties (glycol) reference data. Reference for the data is the ASHRAE
Handbook of Fundamentals. Included are:
Glycols
EthyleneGlycol
PropyleneGlycol
Water
To use the data, copy the appropriate data for the glycol you desire into your input file.
4.1.16 GHLERefData.idf
This file contains sample input for the ground loop heat exchanger model. The response of the bore-
hole/ground is found from the ‘G-function’ that is defined in the input as series of ‘n’ pairs of values
(LNTTSn, GNFCn). It is important to note that the G-functions have to be calculated for specific
GHE configurations and borehole resitance, length and borehole/ length ratio. That is, the param-
eters for the units vary with each design. The data in this file are intended as examples/samples
4.1. SIMPLE LIST DATA SETS 267
• 1 x 2 boreholes
• 4 x 4 boreholes
• 8 x 8 boreholes
Data is given for both ‘standard’ grout (k = 0.744 W/m.K) and ‘thermally enhanced’ grout (k
= 1.471 W/m.K). The flow rate per borehole is .1514 kg/s. The pipe given is 0.75in. Dia. SDR11
HDPE. The fluid is water. The borehole/length ratio is 0.06 (76.2m/4.572m [300ft/15ft])
4.1.17 MoistureMaterials.idf
This data set includes the special moisture materials that can be used with the Moisture Penetration
Depth Conduction Transfer Function (EMPD) and Combined Heat and Moisture Finite Element
(HAMT) calculation procedures.
4.1.18 PerfCurves.idf
This file contains performance curves for various EnergyPlus equipment objects.
• Variable speed DX cooling: These curves are appropriate for small DX cooling units with
variable speed compressors. These curves would be referenced by the EnergyPlus object
Coil:Cooling:DX:TwoSpeed. See the example input file 5ZoneAutoDXVAV for an example of
their use.
• Variable Speed Cooling Tower: These model coefficient objects are appropriate for use with
the variable speed cooling tower object and represent the coefficients used in the YorkCalc
and CoolTools empirical models. These model coefficient objects would be referenced by
the EnergyPlus object Cooling Tower:Variable Speed. See the example input file Cooling-
Tower_VariableSpeed.idf for an example of where these curves could be used (these model
coefficient objects are not specifically used in this idf but could be used by the Cooling
Tower:Variable Speed object). Additional information on variable speed cooling tower model
coefficients can be found in the Input Output Reference and Engineering Reference documents.
• Note that performance curves for the Electric EIR chiller and the Electric Reformulated EIR
chiller are contained in the Chillers.idf dataset.
4.1.19 PrecipitationSchedulesUSA.idf
This file contains schedules (for an entire year) of precipitation for use with the SitePrecipitation
object. Use these schedules for adding rain water to the simulation. The values are in meters per
hour and are scaled to match the average monthly precipitation. They also coincide with the EPW
rain/snow flags from the original source files.
268 CHAPTER 4. DATA SETS
4.1.20 RefrigerationCasesDataSet.idf
All the refrigerated cases included in this database are listed in the following list. Comments before
each refrigeration:case object include the manufacturer’s model number and assumptions about the
fan, lights, defrost etc. The user must ensure that the case names used in the idf file are UNIQUE
and must supply the correct zone name. The user must also supply any required correction curves
or schedules. The defrost and drip-down schedule names included here indicate the frequency and
duration required. The user must ensure that schedules are provided that meet these needs and
that are diversified so that all the cases don’t start their defrost cycles at the same time. Please
see the example cases for supermarkets to see how these case objects are included with the rest of
a supermarket refrigeration system.
• Narrow Glass Door Reach in Frozen Food/Ice Cream Merchandiser: Frozen food
• Narrow Glass Door Reach in Back-toBack Frozen Food/Ice Cream Merchandiser: Ice Cream
274 CHAPTER 4. DATA SETS
• High Narrow Glass Door Reach-in Back-to-Back Frozen Food/Ice Cream: Frozen food
• High Narrow Glass Door Reach-in Back-to-Back Frozen Food/Ice Cream: Ice cream
• Narrow Glass Door Reach in Frozen Food/Ice Cream Merchandiser: Frozen food
• Narrow Glass Door Reach in Frozen Food/Ice Cream Merchandiser: Ice Cream
• High Narrow Glass Door Reach in Back to back Frozen Food/Ice Cream Merchandiser
• Glass Door Reach-in Back too Back Frozen Food/Ice Cream Merchandiser
• Glass Door Reach-in Back too Back Frozen Food/Ice Cream Merchandiser
• Glass Door Reach-in Back too Back Frozen Food/Ice Cream Merchandiser
• Glass Door Reach-in Back too Back Frozen Food/Ice Cream Merchandiser
4.1. SIMPLE LIST DATA SETS 275
• Glass Door Reach-in Back too Back Frozen Food/Ice Cream Merchandiser
• Glass Door Reach-in Back too Back Frozen Food/Ice Cream Merchandiser
• Narrow Glass Door Reach in Frozen Food/Ice Cream Merchandiser: Frozen food
• Narrow Glass Door Reach in Back-toBack Frozen Food/Ice Cream Merchandiser: Ice Cream
• ED1 Impact Service Merchandiser with curved hinged glass 1 display level
• ED1 Impact Service Merchandiser with curved hinged glass 1 display level
• E1 Self Service Single Deck Display for Deli Cheese and Salads
• E1S Self Service Single Deck Display for Deli Cheese and Salads
• E2 Self-Serve Multi-Deck Display For Deli Cheese Pizza Floral Fresh Juice
• E2 Self-Serve Multi-Deck Display For Deli Cheese Pizza Floral Fresh Juice
• E3 Self-Serve Multi-Deck Display For Deli Cheese Pizza Floral Fresh Juice
• ES1S Single-Deck Straight glass Service Case with one display level
• ESBD Curved glass case for deli with blower coil and one display level with optional shelves
• ESBDHV High Volume Curved Glass Blower Coil Service Case for Deli with 3 display levels
• ESBDS Straight glass service case for deli with blower coil and one display level with optional
2 shelves
• ESGM Curved Glass Gravity Coil Service Case for Meat and Seafood
• ESGMS Straight Glass Gravity Coil Service Case for Meat and Seafood
• ESGMVS Vertical hinged glass service case for Deli with Gravity Coil_single display level
• ESGS Curved Glass Gravity Coil Service Case for Meat and Seafood
• ESGSS Straight Glass Gravity Coil Service Case for Meat and Seafood
• ESBDVS Straight hinged glass service case for Deli with Blower Coil_1 display level with
optional shelves
278 CHAPTER 4. DATA SETS
• C6XLRE High Capacity Multi-Deck Convertible Merchandiser with Rear Load-In for Dairy
and Deli
• D5XLRE Multi-Deck Dairy/Deli Merchandiser With Rear Sliding Doors and low front
• F Single Deck Wall Model Merchandiser with solid front for Frozen Food
• F Single Deck Wall Model Merchandiser with solid front for Ice Cream
• F Single Deck Wall Model Merchandiser with solid front for Medium Temp Products
• F2XLG Low Temperature Multi-Deck Merchandiser for Frozen Seafood and Meat
• FG Single Deck Wall Model Merchandiser with glass front for Frozen Food
• FG Single Deck Wall Model Merchandiser r with glass front for Ice Cream
• FG Single Deck Wall Model Merchandiser r with glass front for Medium Temp Products
• FIG Intermediate Island Merchandiser with glass walls for Frozen Food
4.1.21 RefrigerationCompressorCurves.idf
This dataset includes object types for specific (by manufacturer and type) Refrigeration:Compressor
and associated performance curves. Knowing the nominal refrigerating capacity, power, and refrig-
erant for the compressor(s) that you want to simulate, you can find it and the associated performance
curves in the dataset file. By example, here is part of the RefrigerationCompressorCurves.idf file:
! Capacity Curve for Carlyle_R-22_Low_06CC016, !nominal MBtu/h = 18561.0
! Results in Watts, Inputs: Sat Suction Temp (C), Sat Discharge Temp (C)
Curve:Bicubic ,
06CC016_R -22 _Low_qcurv , !- Name
2.350e+004, !- Coefficient1 Constant
816.7 , !- Coefficient2 x
10.70 , !- Coefficient3 x**2
-28.24, !- Coefficient4 y
0.1131 , !- Coefficient5 y**2
-0.4553 , !- Coefficient6 x*y
0.05604 , !- Coefficient7 x**3
-0.004120 , !- Coefficient8 y**3
-0.006728 , !- Coefficient9 x**2*y
0.006782 , !- Coefficient10 x*y**2
-40.0, !- Minimum Value of x
-17.8, !- Maximum Value of x
10.0, !- Minimum Value of y
48.9; !- Maximum Value of y
!Detailed Compressor: Carlyle_R -22 _Low_06CC016 , !nominal MBtu/h = 18561.0 , !nominal kW = 3.1
Refrigeration:Compressor ,
Carlyle_R -22 _Low_06CC016 ,!- Name
06CC016_R -22 _Low_pwrcurv ,!- Refrigeration Compressor Power Curve Name
06CC016_R -22 _Low_qcurv , !- Refrigeration Compressor Capacity Curve Name
, !- Rated Superheat {deltaC}
18.3, !- Compressor Rated Suction Temperature {C}
4.4, !- Rated Liquid Temperature {C}
; !- Compressor Rated Subcooling {C}
282 CHAPTER 4. DATA SETS
4.1.22 RooftopPackagedHeatPump.idf
This dataset includes performance curves for the object types Coil:Cooling:DX:SingleSpeed,
Coil:Cooling:DX:TwoStageWithHumidityControlMode and Coil:Heating:DX:SingleSpeed required
to model rooftop packaged heat pumps in EnergyPlus. Manufacturer’s data used to develop the
data set is also listed in the file. The part of RooftopPackagedHeatPump.idf is shown below.
4.1.23 SandiaPVData.idf
Use these PV statements for implementing PV modules in an EnergyPlus input file when using the
Sandia model.
4.1.24 Schedules.idf
This data set contains the schedule information for various common (e.g. Office Occupancy) schedul-
ing instances. Derived from the Schedules Library issued with the BLAST program. Includes the
building types schedules from ASHRAE 90.1-1989, Section 13. Schedules are listed alphabetically,
with general schedules first, followed by the ten 90.1 building type schedules.
4.1.25 SolarCollectors.idf
Use these SOLAR COLLECTOR PARAMETERS objects for implementing solar collector modules
in an EnergyPlus input file.
Data has been reproduced with permission from: “Directory of SRCC Certified Solar Collector
Ratings” Copyright (c) 2004 by the Solar Rating and Certification Corporation. For more informa-
tion, contact: Solar Rating and Certification Corporation, c/o FSEC, 1679 Clearlake Road, Cocoa,
FL 32922-5703 USA Tel: (321) 638-1537 Fax: (321) 638-1010 , www.solar-rating.org
4.1.26 StandardReports.idf
This file contains the Report Table:Monthly command for some commonly used/desired monthly
reports.
4.1.27 SurfaceColorSchemes.idf
This file offers examples for using custom color schemes for DXF output.
4.1.28 USHolidays-DST.idf
This is the set of US national holidays as well as daylight saving period defaults.
4.1.29 Window5DataFile.dat
This is an example data file from the Window5 program that can be used with EnergyPlus windows.
4.2. MACRO DATA SETS 283
4.1.30 WindowBlindMaterials.idf
This is a data set of Window Blind materials.
4.1.31 WindowConstructs.idf
This is a data set of Window constructions. It does not include the required pieces of the Window
construction (glass materials, gas materials).
4.1.32 WindowGasMaterials.idf
This is a data set of Window Gas materials.
4.1.33 WindowGlassMaterials.idf
This is a data set of Window Glass materials.
4.1.34 WindowShadeMaterials.idf
This is a data set of Window Shade materials.
4.1.35 WindowScreenMaterials.idf
This is a data set of Window Screen materials.
4.2.2 SandiaPVData.idf
Use these PV statements for implementing PV modules in an EnergyPlus input file when using the
Sandia model.
4.2.3 SolarCollectors.idf
Use these SOLAR COLLECTOR PARAMETERS objects for implementing solar collector modules
in an EnergyPlus input file.
284 CHAPTER 4. DATA SETS
Data has been reproduced with permission from: “Directory of SRCC Certified Solar Collector
Ratings” Copyright (c) 2004 by the Solar Rating and Certification Corporation. For more informa-
tion, contact: Solar Rating and Certification Corporation, c/o FSEC, 1679 Clearlake Road, Cocoa,
FL 32922-5703 USA Tel: (321) 638-1537 Fax: (321) 638-1010 , www.solar-rating.org
4.2.4 UtilityTariffObjects.imf
Use the large collections of input objects to model the costs of energy supplied by utility companies.
This file is ready for use in macro processing but the input objects can readily be copied out of the
macro file and used in a regular input file. The data were assembled by NREL researcher Brent
Griffith and represent a best effort at putting together a comprehensive set of utility tariffs for
commercial buildings for the USA as of Spring 2005. Use the data at your own risk and note that
utility tariffs need to be continually updated to reflect current conditions.