Getting Started Ep
Getting Started Ep
7 Documentation
Getting Started
1 EnergyPlus Overview 5
1.1 What is EnergyPlus? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 Why does EnergyPlus exist and what were its original goals? . . . . . . . . . 7
1.3 EnergyPlus Documentation Library . . . . . . . . . . . . . . . . . . . . . . . 11
1.3.1 User Information Documents . . . . . . . . . . . . . . . . . . . . . . 12
1.3.2 Engineering Reference Document . . . . . . . . . . . . . . . . . . . . 12
1.3.3 Application Guides . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.3.4 Developer Menu and Developer Information Documents . . . . . . . 14
3 Running EnergyPlus 16
3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.2 EP-Launch Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
3.2.1 Start EP-Launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
3.2.2 Selecting Input and Weather Files . . . . . . . . . . . . . . . . . . . 18
3.2.3 Running a Single Input File . . . . . . . . . . . . . . . . . . . . . . . 18
3.2.4 Looking at the Results . . . . . . . . . . . . . . . . . . . . . . . . . . 18
3.2.5 Viewing the Drawing File without Running a Simulation . . . . . . . 21
3.2.6 Editing the Input Files . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.2.7 File Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.2.8 Edit Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.2.9 View Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
3.2.10 Help Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.2.11 Recently Used Files . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.2.12 Utilities Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3.2.13 Caveats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.2.14 When things go wrong . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.2.15 Bugs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.3 EnergyPlus File Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.3.1 Input Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
3.3.2 Primary Output Files . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.3.3 Other Output Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
2
CONTENTS 3
6 Tutorial Exercise 2 62
6.1 Unitary System and VAV using HVACTemplate Inputs . . . . . . . . . . . . 62
6.1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
6.1.2 Details of the Exercise . . . . . . . . . . . . . . . . . . . . . . . . . . 62
6.2 Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
6.2.1 Exercise 2A. Add Unitary System with DX Cooling and Gas Heating
(Furnace) Serving a Single Zone . . . . . . . . . . . . . . . . . . . . . 64
6.2.2 Exercise 2B. Add VAV System with Reheat Serving Four Zones with
Chiller and Boiler Plant . . . . . . . . . . . . . . . . . . . . . . . . . 66
6.2.3 Exercise 2C. Annual Simulation . . . . . . . . . . . . . . . . . . . . . 67
6.2.4 Solution: Exercise 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
9 Energy Meters 85
9.1 Standard Energy Meters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
9.2 Custom Meters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
EnergyPlus Overview
Welcome to EnergyPlus! This section offers a big picture view of what EnergyPlus is, what
it does, why it exists, and what its goals are AND provides an overview to the EnergyPlus
documentation library. While this document does not provide every detail on the pro-
gram, it does give the reader a macroscopic view of EnergyPlus and how it is intended to fit
into the energy analysis and thermal load simulation software continuum.
Integrated, simultaneous solution where the building response and the primary
and secondary systems are tightly coupled (iteration performed when necessary)
5
6 CHAPTER 1. ENERGYPLUS OVERVIEW
Sub-hourly, user-definable time steps for the interaction between the thermal
zones and the environment; variable time steps for interactions between the thermal
zones and the HVAC systems (automatically varied to ensure solution stability)
ASCII text based weather, input, and output files that include hourly or sub-
hourly environmental conditions, and standard and user definable reports, respectively
Heat balance based solution technique for building thermal loads that allows for
simultaneous calculation of radiant and convective effects at both in the interior and
exterior surface during each time step
Transient heat conduction through building elements such as walls, roofs, floors,
etc. using conduction transfer functions
Combined heat and mass transfer model that accounts for moisture adsorp-
tion/desorption either as a layer-by-layer integration into the conduction transfer func-
tions or as an effective moisture penetration depth model (EMPD)
Thermal comfort models based on activity, inside dry bulb, humidity, etc.
Anisotropic sky model for improved calculation of diffuse solar on tilted surfaces
Loop based configurable HVAC systems (conventional and radiant) that allow
users to model typical systems and slightly modified systems without recompiling the
program source code
Atmospheric pollution calculations that predict CO2 , SOx , NOx , CO, particulate
matter, and hydrocarbon production for both on site and remote energy conversion
More details on each of these features can be found in the various parts of the EnergyPlus
documentation library.
No program is able to handle every simulation situation. However, it is the intent of En-
ergyPlus to handle as many building and HVAC design options either directly or indirectly
1.2. WHY DOES ENERGYPLUS EXIST AND WHAT WERE ITS ORIGINAL GOALS?7
through links to other programs in order to calculate thermal loads and/or energy consump-
tion on for a design day or an extended period of time (up to, including, and beyond a
year). While the first version of the program contained mainly features directly linked to the
thermal aspects of buildings, later versions of the program also included other issues that
are important to the built environment: water, electrical systems, etc.
Although it is important to note what EnergyPlus is, it is also important to remember
what it is not.
EnergyPlus is currently not a life cycle cost analysis tool. It produces results that
can then be fed into an LCC program. In general, calculations of this nature are
better left to smaller utility programs which can respond more quickly to changes
in escalation rates and changes to methodologies as prescribed by state, federal, and
defense agencies.
EnergyPlus is not an architect or design engineer replacement. It does not check input,
verify the acceptability or range of various parameters (expect for a limited number
of very basic checks), or attempt to interpret the results. While many GUI programs
assist the user in fine-tuning and correcting input mistakes, EnergyPlus still operates
under the garbage in, garbage out standard. Engineers and architects will always be
a vital part of the design and thermal engineering process.
1.2 Why does EnergyPlus exist and what were its orig-
inal goals?
The existence of EnergyPlus is directly related to some of the increasingly obvious shortcom-
ings of its predecessor programsBLAST and DOE2. Both programs, though still valid
tools that will continue to have utility in various environments, have begun to show their age
in a variety of ways. Both BLAST and DOE2 were written in older version of FORTRAN
and used features that will eventually be obsolete in new compilers. Both programs consisted
of a significant amount of spaghetti code and outdated structures that made it difficult
to maintain, support, and enhance. Neither BLAST nor DOE2 is able to correctly handle
feedback from the HVAC system to the zone conditions.
Finally, the speed with which new technology in the HVAC field is developed has far
outpaced the ability of the support and development groups of both programs to keep the
programs current and viable. This is really the key issue in the existence of EnergyPlus: there
8 CHAPTER 1. ENERGYPLUS OVERVIEW
simply are not enough researchers worldwide who have enough experience with the complex
code of the programs to keep pace with new technology. In addition, due to the years of
experience necessary to make modifications to either BLAST or DOE2, it is extremely
expensive and time consuming to produce models or train someone to become proficient in
either programs code. The following paragraphs address how the goals of EnergyPlus have
been carefully selected to solve the problems of the legacy programs and to make EnergyPlus
an international repository for algorithms that can be made available to all interested parties.
Structure and Simulation Management: The spaghetti code nature of the parent
programs resulted in great confusion as to how information flowed within the program, when
data was modified or should be modified, and what was happening when. Thus, one of the
goals of EnergyPlus development was to eliminate the interconnections between various
program sections and the need to understand all parts of the code just to make an addition
to a very limited part of the program. This goal was achieved through a program structure
that implemented a manager philosophy. In effect, the program consists of many pieces
(i.e., modulessee next paragraph) which when viewed graphically resemble an inverted
tree. Instead of allowing lower level pieces of the program and calls to those sections of
the code to infiltrate up to the highest level of the simulation, each branch exercises control
over when its sub-branches are called. Thus, this is much like an organization chart where
management over employees proceeds up a chain of command until it reaches the CEO
of the simulation. In EnergyPlus, a subroutine called ManageSimulation serves the CEO
role. This single subroutine controls four of the five main simulation loops (environment,
day, hour, sub-hour time step; the system time step is controlled by the HVAC manager).
In addition, this subroutine also sets global flags that are used by other subroutines and
modules to determine the state of the simulation so that each part of the program knows
whether to read input, initialize, simulate, report, etc. The manager philosophy makes the
links between program modules simple and explicit. Typically, each module is accessible only
through a call to its manager routine. Developers no longer have to worry about hidden and
unexpected connections between and among program subroutines.
Modularity: One of the benefits of the structural improvements over the legacy pro-
grams is that the code can now be much more object-oriented and modular in nature. A
result of the goal for improved structure in EnergyPlus was the definition of a well-organized,
module concept that would facilitate adding features and links to other programs. It was
decided that FORTRAN90 would be used for the initial release of EnergyPlus due to the
fact that it:
The key benefit of modularity is that researchers can develop modules concurrently with-
out interfering with other modules under development and with only a limited knowledge
1.2. WHY DOES ENERGYPLUS EXIST AND WHAT WERE ITS ORIGINAL GOALS?9
of the entire program structure. This feature is critical to promoting both widespread use
and broad development of program models. EnergyPlus can only be successful if the pool
of potential model developers increases significantly so that interest and economics drives
what models are added to the program rather than have its extensions limited by a lack
of intellectual resources. Thus, modularity and structure improvements in EnergyPlus solve
the problems of not having enough experts to keep up with technology and the large start-up
time and expense previously needed to bring someone up to speed on program additions.
Since the original version (2001), EnergyPlus code and structure continued to evolve
and adopt the ever changing Fortran Standard. However, in 2014, a full conversion of the
simulation code to C++ was completed. The development team also adapted workflows and
open sourced the code and posted it on Github. Just like how the Fortran simulation code
utilized modern Fortran standard capabilities, the C++ code utilizes modern (C++11)
C++ standard capabilities.
Established Links: The modularity of EnergyPlus makes it easier for other developers
to quickly add other component simulation modules. This means that it will be significantly
easier to establish links to other programming elements. Since initially the EnergyPlus code
will contain a significant number of existing modules, there will be many places within the
HVAC code where natural links to new programming elements can be established. These
are fully documented to assist other developers in a swift integration of their research into
EnergyPlus. In addition to these more natural links in the HVAC section of the code,
EnergyPlus will also have other more fluid links in areas such as the heat balance that will
allow for interaction where the modules might be more complex or less component based.
Again, the goal of this feature of EnergyPlus is maximize the number of developers who can
quickly integrate their work into EnergyPlus for the minimum investment of resources. The
following diagram depicts how other programs have already been linked to EnergyPlus and
a big picture view of how future work can impact the program.
Integration of Loads, Systems, and Plants: One of the strong points of EnergyPlus
is the integration of all aspects of the simulationloads, systems, and plants. Based on a
research version of the BLAST program called IBLAST, system and plant output is allowed
to directly impact the building thermal response rather than calculating all loads first, then
simulating systems and plants. The simulation is coupled allowing the designer to more
accurately investigate the effect of undersizing fans and equipment and what impact that
might have on the thermal comfort of occupants within the building. The diagram below
shows a basic overview of the integration of these important elements of a building energy
simulation.
Open Source Code: Another advantage of EnergyPlus that it shares with both
BLAST and DOE2 is that the source code of the program will be available and open
for public inspection, revision, etc. The program is not intended to be a black box that is
unintelligible to the users and developers around the world. While there are many conflicting
ideas on what is meant by open, EnergyPlus is certainly not closed since this would be
counter to the goals that have already been stated. The hope is that this access to source
code will improve the accuracy and usability of the program over the long term and allow
many developers to work on the program simultaneously. This developer friendly stance
is critical to keeping EnergyPlus current and in step with technological advances.
In summary, the goals of EnergyPlus are ambitious but achievable via the path described
10 CHAPTER 1. ENERGYPLUS OVERVIEW
above. EnergyPlus aims to be a program that is relatively simple to work with from the
perspective of both the users and the developer. The development team made tremendous
efforts to keep simulation code and algorithms as separate as possible and as modular as
possible to minimize the overall knowledge that someone would need to have to add models to
the program. This will minimize the resource investment and maximize the impact of current
research in the field of building energy analysis and thermal load calculations. Finally, the
full coupling of building envelopes, systems, and plants will provide a better understanding
of how a building responds not only to the environmental factors that impact the building
but also the HVAC system as it attempts to meet the thermal loads on the building.
It is also important to note that testing and verification are key issues in the development
of any new program such as EnergyPlus. While there are large sections of EnergyPlus that
consist of brand new code, the majority of the heat balance code can be traced back to
the original parent programs. It should be noted that while this code has been significantly
reengineered the team used what has been termed an evolutionary reengineering (ER)
process. In ER, program code is modified stepwise in an effort to restructure it, modularize
it, replace old obsolete data structures, etc. The ultimate goal is to bring it up to current
programming standards without starting over with new code. At each step along the way,
the program is exercised over a variety of input files and parameters to insure that what
were intended to be algorithm neutral changes in the program have not resulted in changes
to the output. This process was very successful and bolstered confidence in the program.
In addition, comparisons could be made back to legacy programs to show that the new
program is at a minimum as accurate as its predecessors. Beyond this, EnergyPlus has
also been subjected to a lengthy and rigorous testing plan by an outside agency as well as
numerous beta testers. This level of effort and collaboration is unprecedented in the history
of energy analysis and thermal load calculation programs and has resulted in a much higher
level of confidence in the results produced by EnergyPlus.
The Markdown source for the latest major release is converted to html which is then
available at http://energyplus.net/documentation. The current, or daily documentation
12 CHAPTER 1. ENERGYPLUS OVERVIEW
The Markdown based documentation is structured similarly to the pdfs, though the larger
files are broken into smaller pieces for faster load times due to the dynamic nature of the
math, especially in the engineering reference. Each of the main documentation pieces are
described here.
tains the following information and is structured along the lines of the above illustration
(Figure 1.2. EnergyPlus Internal elements).
Heat Balance Overview and Reference: This section describes the heat balance
calculations that form the basis of the EnergyPlus building model. It includes descriptions
of shadowing calculations and other pieces of the model.
HVAC Overview and Reference:This section contains a description of the loop-
based approach used by EnergyPlus to model the HVAC systems: air loops, water loops,
etc. It includes a description of the higher-level managers that control the simulation flow as
well as some information on the various components that can be linked together to comprise
an HVAC system.
HVAC Branch Based Input Description:This section is a special extension of
both the input document and the HVAC overview document. It contains more detail on
the various HVAC input objects and how these different object link together to form an
HVAC description. It contains vital information mainly for the interface developer but also
provides users with an in-depth look at the inner workings of the loop approach adopted by
EnergyPlus.
Encyclopedic Reference:If the information did not fit in the above categories, then
the last part of the Engineering Reference is a detailed description of the various models.
The remainder of this document is intended to give you a start on using the program with
a few simple tools (EP-Launch to help run the simulation; IDFEditor to help create or look
at input files) as well as some of the features (such as energy meters, simulation results) of
using the program.
For learning about a specific input file, or a specific input object, the install includes two
documents in the ExampleFiles folder:
Example Files Summary (highlights of each example file)
Example Files Links to Objects (for any object, up to 3 files using that object are
shown)
The standard Windows install procedure has put the following information on your com-
puter, in the directories/folders shown.
The main EnergyPlus folder contains: * Energy+.idd * EnergyPlus.exe and dependent
shared libraries (dll files) * RunEPlus.bat and other batch files for running EnergyPlus *
readme file(s), license, etc. * EP-Macro.exe and other support binaries * bugreprt.txt
The general layout of folders from the install looks like:
. EnergyPlus main folder
+-- Documentation
| +-- A link to find the documentation online , and any additional docs packaged with the
installation
+-- DataSets
| +-- Reference Data Sets (libraries)
+-- MacroDataSets
| +-- Macroized Reference Data Sets (libraries)
+-- PreProcess
| +-- FMUParser Tool for external interface specific applications
| +-- IDFEditor Program files for the IDFEditor
| +-- GrndTempCalc Special program to calculate ground temperatures.
| +-- DOE2Translator Simple translator for DOE -2 files
| +-- WeatherConverter Tool for performing weather file creation and conversion
| +-- ParametricPreprocessor Parametric simulation tool
| +-- IDFVersionUpdater Graphical tool for updating old EnergyPlus files to the latest
version
+-- PostProcess
| +-- ReadVarsEso The simple post processor exe.
| +-- EPCompare A graphical tool for comparing two EnergyPlus output sets
+-- ExampleFiles Sample input , output , results files shipped with the program.
+-- WeatherData Sample weather files shipped with the program.
15
Chapter 3
Running EnergyPlus
3.1 Introduction
EnergyPlus is a simulation program designed for modeling buildings with all their associated
heating, ventilating, and air conditioning equipment. EnergyPlus is a simulation engine: it
was designed to be an element within a system of programs that would include a graphical
user interface to describe the building. However, it can be run stand alone without such an
interface. This document describes how to run EnergyPlus in such a stand alone fashion.
This section will introduce you to the EP-Launch program, which helps you run Energy-
Plus. EP-Launch looks and acts pretty much like a standard Windows program, so if you
just want to get started with some exercises, you can skip to the section Tutorial Example
for running EnergyPlus first and come back to this section if you run into problems with
EP-Launch.
Like all simulation programs, EnergyPlus consists of more than just an executable file.
EnergyPlus needs various input files that describe the building to be modeled and the en-
vironment surrounding it. The program produces several output files, which need to be
described or further processed in order to make sense of the results of the simulation. Fi-
nally, even in stand-alone mode, EnergyPlus is usually not executed by hand, but rather
by running a procedure file which takes care of finding input files and storing or further
processing the output files.
To assist those in the Windows environment, we have included the EP-Launch program.
Review the next section for basic instructions. More advanced techniques of executing the
program are contained in the Auxiliary Programs document under Technical Details of
running EnergyPlus, including some advanced uses of the EP-Launch program. If you wish
to learn about DOS/Command Line use for EnergyPlus, you will need to read that section
in the Auxiliary Programs document.
16
3.2. EP-LAUNCH PROGRAM 17
help open a text editor for the input and output files, open a spreadsheet for the postprocessor
results files, a web browser for the tabular results file, and start up a viewer for the selected
drawing file.
This status gives you a quick overview of whether there were warning (should look
at), severe (should probably fix) or fatal (must fix) errors in the run as well as the
time it took for the simulation to complete. After pressing OK from this box, selecting
ERR/EIO/BND Output Files Only from the View menu will display the ERR, EIO, and
BND files useful when errors may have occurred. Alternatively, pressing the F2 function
key will display the same three files.
Another way to open files easily is by using the View Results buttons shown in Figure 3.3.
Two different panels of buttons can be used under View Results, one shown by using the
All tab on the left edge and by using the Sets tab on the left edge. The All tab shows
all the various files by file extension that can be viewed individually. Files available for
view based on the current input file name are enabled (extension names clearly readable).
The contents of each file extension is listed below.
The figure above shows the same main screen of EP-Launch but with the Sets tab
selected on the left edge of the View Results section. The buttons on this tab can open
20 CHAPTER 3. RUNNING ENERGYPLUS
many files at the same time and are a shortcut to opening the files that may be commonly
used. The Text Output Files, Drawing Files, and Spreadsheets buttons cause several different
results files to open at once based on the currently selected Input File. The HTML file opens
just the tabular results file if that file was produced (see OutputContol:Table:Style).
The contents (along with examples) are discussed in the Output Details document.
You can also view the results using one of the three buttons (Text Output Files,
Drawing File and Spreadsheets) in the View Results area of the main EP-Launch
screen.
By pressing the Text Output Files button, a text editor will open each of the text
output files. Up to 29 files will open, if they exist. Selecting Single File from the View
menu displays a menu of all available output files from which any file can be opened
individually. Each file may also be opened with an associated function key. The output files
and function key shortcuts are listed below:
1. Variable tabulated results in comma, tab or space delimited format (generated by
the ReadVarsESO postprocessor) (F4)
2. ESO raw report variable output (F5),
3. RDD list of output variables available from the run (F6).
4. MDD list of output meters available from the run (Shift-Ctrl-F3)
5. EIO additional EnergyPlus results (F7),
6. ERR list of errors and warnings (F8),
7. BND HVAC system node and component connection details (F9),
8. MTR raw report meter output (F11),
9. MTD list of meter component variables (F12)
10. METER File tabulated meter report in comma, tab or space delimited format
(generated by the ReadVarsESO postprocessor) (Ctrl-F4)
11. ZSZ zone sizing details in comma, tab or space delimited format (Ctrl+F5)
12. SSZ system sizing details in comma, tab or space delimited format (Ctrl+F6)
13. AUDIT input file echo with input processor errors and warnings (Ctrl+F8)
14. SLN output from report, surfaces, lines (Ctrl+F9)
15. DBG output from the debug command (Ctrl+F11)
16. SHD output related to shading (Ctrl+F12)
17. SVG - HVAC Diagram (Shift+ F4)
18. EPMIDF clean idf file after EP-Macro processing (Shift+F5)
19. EPMDET EP-Macro detailed output with errors and warnings (Shift+F6)
20. MAP daylighting illuminance map (Shift+F7)
21. TABLE tabulated report of bin and monthly data in comma, tab or space delimited
or HTML format (Shift+F8)
22. VMRL drawing file in VRML (Virtual Reality Markup Language) format (Shift
F+F11)
23. DXF drawing file in AutoCAD DXF format (Shift+F12)
24. Delight IN - DElight input generated from EnergyPlus processed input
(Shift+Ctrl+F4)
25. Delight OUT Detailed DElight output (Shift+Ctrl+F5)
26. Delight ELDMP DElight reference point illuminance per time step (Shift+Ctrl+F6)
27. Delight DFDMP DElight warning and error messages (Shift+Ctrl+F7)
3.2. EP-LAUNCH PROGRAM 21
The View menu (Figure 3.4) duplicates the options in the View Results area of the main
screen (see the Looking at the Results section above) and allows opening of selected output
files. You can also open the folders that contain the active input and weather files. Opening
a single file is under a submenu and is very similar to the Quick Open Panel for Single
Simulation described above. Selecting HTML File from the View menu will open any
user created files saved in the format: <filename>table.html (see OutputControl:Table:Style).
The View menu also accesses the Options menu item shown in Figure 3.5 that is
used to control many of the optional features of EP-Launch. These optional features are
described below:
3.2. EP-LAUNCH PROGRAM 23
Pause During Simulation (Unless Minimized) Stops the progress of the EnergyPlus
run at different points. This does not stop the simulation itself but pauses before or after
important events as files are copied or utility programs are run. It is usually used only for
diagnosing problems with the EPL-RUN batch file. The feature is also described in the
Running a Single Input File section above.
Minimize Single Simulation Command Window For a single input file, minimizes
the Command Window that EP-Launch uses to run EnergyPlus. The command window will
appear only in the Windows taskbar and the command window will not be visible. You can
restore the command window be clicking on the taskbar item labeled EnergyPlus Process.
This option should be used with caution since you will not see any indication of the simulation
being complete other than the EnergyPlus Process taskbar item will disappear.
Minimize Group Simulation Command Window For a group of input files, min-
imizes the Command Window that EP-Launch uses to run EnergyPlus. This is a good
option when working on something else on your computer at the same time as the group of
simulations is running since the command window normally becomes the front window each
time a new simulation starts. This option prevents the command window coming to the
front for each simulation. The command window will appear only in the Windows taskbar
and the command window will not be visible. You can restore the command window be
clicking on the taskbar item labeled EnergyPlus Process. This option should be used with
caution since you will not see any indication of the simulation being complete other than
24 CHAPTER 3. RUNNING ENERGYPLUS
Extra Wide Window Select this option to make the main EP-Launch window wider.
This is useful when files are used with very long file path names.
Alternative layout Changes the layout of the EP-Launch window to an alternative
arrangement of buttons.
Tab Delimited Open with Spreadsheet Selecting Single File and then Main Re-
sults File from the View menu or pressing the F4 function key will open TAB files with
the default spreadsheet application rather than the text editor. Comma-separated variable
(CSV) is the default setting for viewing tabulated results set in the RVI file. If the user
changes the setting for viewing tabulated results to TAB or TXT format, selecting Single
File and then Main Results File from the View menu or pressing the F4 function key
will open the files in the default text editor. TAB files, when selected, will also be opened
by the text editor when the Text Output Files button is pressed after a successful run.
Allow More Than 250 Columns Tabulated data that exceeds 250 columns, the
MS Excel maximum, will be truncated to that limit unless Allow >250 Columns is se-
lected. Excel versions prior to 2007 were limited to 255 columns in a sheet; later versions
allow unlimited number of columns. This limitation may not be true for other spreadsheet
programs.
Check VERSION Prior to Simulation Automatically check the VERSION object
in the selected EnergyPlus input file prior to simulation and if it is an older version than the
current version will run the Transition program to update the file.
Convert ESO/MTR to IP Units Runs the convertESOMTR utility program (see
AuxiliaryPrograms documentation for more information). This utility will convert the ESO
and MTR files into Inch-Pound units. The CSV file created from these files will also be in
Inch-Pound units.
Create Statistics File Runs the CSVProc utility program (see the AuxiliaryPrograms
documentation for more information) and creates the Proc.csv file. This file contains some
simple statistics on each variable in the normal CSV file.
Create Batch File to Run EnergyPlus Traditionally EP-Launch has created a
batch file in order to execute EnergyPlus with the various options chosen. This can cause
problems with some operating systems, such as Windows Vista, when set to a higher secu-
rity setting. This option can be unchecked and a batch file is not created when running
EnergyPlus instead parameters are passed to an existing batch file.
3.2. EP-LAUNCH PROGRAM 25
associated with the CSV file extension and use that program. Auto Find is invoked the first
time EP-Launch is started so that a spreadsheet program is available immediately.
EP-Launch will start a diagramming program to view SVG files from HVAC Diagram. The
diagramming program that will be used is shown but can be changed by either pressing
the Select button, the Auto Find button, the Use Firefox button or the Use Opera button.
The Select button allows you to find the diagramming program of your choice but make
sure it is capable of opening SVG files. The Auto Find button will automatically find the
program that is associated with the SVG file extension and use that program. Auto Find
is invoked the first time EP-Launch is started so that a spreadsheet program is available
immediately. Since both Firefox and Opera web browsers can view SVG files, those buttons
will select those respective browsers if available.
EP-Launch will start a HTML browser program when viewing the tabular results file when
HTML is chosen in OutputControl:Table:Style object. The HTML browser that will be used
is shown but can be changed by either pressing the Select button or by pressing the Auto
Find button. The Select button allows you to find the HTML browser of your choice. The
Auto Find button will automatically find the program that is associated with the HTML file
extension and use that program. Auto Find is invoked the first time EP-Launch is started
so that a HTML browser is available immediately.
By default, ESO files are opened with a text editor. ESO files are the raw output file
containing results from EnergyPlus for Output:Variable objects. They are often processed
into CSV files to make it easier to view them. At least one utility program has been developed
to view ESO files directly (see the EnergyPlus.gov web site under Interfaces & Other Tools,
Third-party EnergyPlus Tools). The Auto Find and Select buttons work the same way as
other viewer selectors. If no special ESO viewer is selected the box will be shown as empty.
It can also be emptied by using the Clear button.
EP-Launch will start a PDF viewer program when opening the EnergyPlus documentation
under the Help menu. The PDF Viewer that will be used is shown but can be changed by
either pressing the Select button or by pressing the Auto Find button. The Select button
allows you to find the PDF Viewer of your choice. The Auto Find button will automatically
find the program that is associated with the PDF file extension and use that program.
Auto Find is invoked the first time EP-Launch is started so that a PDF Viewer is available
immediately.
3.2. EP-LAUNCH PROGRAM 27
When installing EnergyPlus, you are given an option if you want IDF, IMF, and EPG files
associated with EP-Launch. This allows double clicking on files with those extensions and
having EP-Launch start automatically with those files. If during the install that option is
not selected or if you have changed the program that opens IDF, IMF and EPG files and
want to change it back to EP-Launch, the button for this option will do that.
3.2.13 Caveats
Remember to save changes made in the editor before you run another simulation.
The simulation cannot write new results to open files which are locked by another appli-
cation.
You will need to close the spreadsheet program that views the resulting CSV files prior
to another simulation and you may need to close the text editor windows also (depending
on your editor).
The EPL-RUN.BAT batch file is used to run EnergyPlus from the EP-Launch program.
It can be edited with care if other postprocessors or preprocessors are to be used.
3.2.15 Bugs
The EP-Launch program has been through several releases but there is still a chance you
will find bugs. Please report them to the [email protected] address so that we
can fix them prior to the release.
If the pull-down lists ever are shown as blank the reset button may be used. This
unlabeled button is very small in the lower left-hand corner of the main screen. It removes
the items shown in the recently used file list and causes the program to forget the selected
viewers and text editors; and exits the program. When you start EP-Launch again, you will
need to make these selections (viewers and text editors) again.
3.3.1.1 IDD
The input data dictionary (IDD) is an ASCII (text) file containing a list of all possible
EnergyPlus objects and a specification of the data each object requires. This file is analogous
to the DOE-2 keyword file. The Guide for Interface Developers contains a full description
of the input data dictionary.
30 CHAPTER 3. RUNNING ENERGYPLUS
3.3.1.2 idf
The input data file (IDF) is an ASCII file containing the data describing the building and
HVAC system to be simulated. Many example files are installed as part of the Energy-
Plus installation. Additionally, a spreadsheet file ExampleFiles.xls contains columnar
descriptions of each files features.
3.3.1.3 imf
The input macro file (IMF) is an ascii file containing the data describing the building and
HVAC system to be simulated and will have some contents of macro commands. The
Auxiliary programs document describes use of the macro commands and the program that
processes them EP-Macro. Many example files are installed as part of the EnergyPlus
installation.
3.3.1.4 ini
This is the EnergyPlus initialization file. It is an optional ascii input file that allows the
user to specify the path for the directory containing Energy+.idd. This file, using the actual
directories of the install, will be created during the install. Unless you change where the
EnergyPlus.exe file resides, you will not need to change this file.
3.3.1.5 epw
The EnergyPlus weather file is an ascii file containing the hourly or sub-hourly weather data
needed by the simulation program. The data format is described in detail in the Auxiliary
Programs Document. It is also described succinctly in the Input Output Reference document.
3.3.2.1 err
A text file containing the error messages issued by EnergyPlus. This is the first output
that should be examined after a simulation.Error messages may be issued by Energy-
Plus during its input phase or during the simulation. There are three levels of error severity:
fatal, severe, and warning as well as simple information lines. A fatal error causes the
program to terminate immediately. The following table illustrates the necessary actions.
32 CHAPTER 3. RUNNING ENERGYPLUS
3.3.2.2 csv
When run normally, EP-Launch and EnergyPlus automatically creates post-processed stan-
dard output (eso) and meter output (mtr) files into columnar csv (comma separated variable)
files. These files are ready to be read by spreadsheet programs (such as Excel).
3.3.2.3 htm/html
Several of the report options produce html files that can be read in standard Web
browsers. These are very powerful, information packed files. Though wary of information
overload, the easiest way to see everything is to enter the following in your input file:
OutputControl:Table ,
HTML; !- ColumnSeparator
Output:Table:SummaryReports ,
All Summary;
Note that you can also get this file in other formats (the OutputControl:Table option).
3.3.3.2 eso
The EnergyPlus Standard Output (ESO) is a text file containing the time varying simulation
output. The format of the file is discussed in the Guide for Interface Developers and the
3.3. ENERGYPLUS FILE EXTENSIONS 33
3.3.3.3 mtr
The EnergyPlus Meter Output (MTR) is a text file containing the time varying simulation
output. The format of the file is similar to the ESO file. As described in a later section of this
document (see Energy Meters), meters are a powerful reporting tool in EnergyPlus. Values
are grouped onto logical meters and can be viewed the same way that the ESO variables
are used. The contents of the file are controlled by Output:Meter commands in the IDF
file. Although the MTR is a text file, it is not easily interpretable by a human. Usually
postprocessing will be done on this file in order to put it in a format that can be read by
a spreadsheet; however a quick visual inspection of the file does show whether the expected
variables are output at the desired time step.
3.3.3.4 mtd
This file contains all the details (i.e., which report variables are on a meter and, conversely,
what meters contain) about meters.
3.3.3.5 eio
The EnergyPlus Invariant Output (EIO) is a text file containing output that does not vary
with time. For instance, location information (latitude, longitude, time zone, altitude) ap-
pears on this file.
3.3.3.6 rdd
3.3.3.7 mdd
The Report (variable) Data Dictionary (RDD) is a text file listing those variables available
for reporting (on the ESO) for this particular simulation. Which variables are available for
output depends on the actual simulation problem described in the IDF. The Report (meter)
Data Dictionary (MDD) is a text file listing those variables available for reporting (on the
MTR) for this particular simulation. Which meters are available for output depends on the
actual simulation problem described in the IDF. A simulation with no chiller does not permit
the output of any chiller report variables. The user may need to examine the RDD or MDD
to find out which report variables are available in a particular simulation. The RDD and
MDD are written only if the following is included in the IDF file.
Output:Reports , VariableDictionary;
3.3.3.8 dxf
This is a file in AutoCad DXF format showing all the surfaces defined in the IDF file. It
provides a means of viewing the building geometry. The DXF file from EnergyPlus highlights
different building elements (shading, walls, subsurfaces) in differing colors. A number of
programs can read and display DXF files. Output of this file is triggered by
in the IDF.
Chapter 4
The following example is taken directly from the training course Introduction to Energy-
Plus, Exercise 1. Of course, it is presented here without the benefit of classroom pre-
sentation and discussion but when followed step by step, should provide an introduction of
actually using EnergyPlus.
Lightweight construction
The details of the building construction and operation are shown in the following tables
and description. For tutorial purposes, the building is located in Chicago Illinois, one of the
weather files supplied with EnergyPlus. These details are listed in a fashion to make for easy
entry into EnergyPlus.
Material (listed Conductivity Thickness (m) U (W/m-K) R (m-K/W) Density (kg/m) C (J/kg-K)
from outside to (W/m-K)
inside)
Walls
35
36 CHAPTER 4. TUTORIAL EXAMPLE FOR RUNNING ENERGYPLUS
Material (listed Conductivity Thickness (m) U (W/m-K) R (m-K/W) Density (kg/m) C (J/kg-K)
from outside to (W/m-K)
inside)
Type * Clear
Number of panes 2
Pane thickness 0.006 m
Air-gap thickness 0.0032 m
Conductivity of glass 0.9 W/m-K
Type Details
Internal Loads Lights (1000 W), Office Lighting schedule, surface mount
fluorescent
Space Conditioning Heating setpoint 20C, cooling setpoint 24C, no setback
Location Chicago, Illinois, USA; Summer and Winter design days
Simulation Period Annual, Jan 1 - Dec 31
Ground 18.2 C to 22.5 C (from Slab preprocessor, vary monthly)
Temperatures
4.2. INSTRUCTIONS 37
4.2 Instructions
4.2.1 Exercise 1A. Run Pre-Defined Building with no Windows
Objective: Learn to use EP-Launch to run an EnergyPlus input file and view output files.
1. Open EP-Launch.
2. Under Input File, browse for input file Exercise1A.idf. This input file contains the
1-zone model described above without the windows and lights. This is located under the
install folder <root>\ExampleFiles\BasicsFiles,
3. Under Weather File, select No Weather File (at the top of the pull-down list).
4. Press Simulate.
5. When the simulation is complete, review output files:
Press Text Output Files to see all text output. Look especially at the eio and err
output files.
Press Drawing Files to see a dxf drawing of the building envelope. (If using Voloview
Express, right-click to switch between wireframe and shaded orbit view. In DWG True
View, use View -> Visual Styles to switch between wireframe and solid views. In
both programs, use View Named Views to select isometric views.)
An empty svg drawing file will also open (this will show HVAC system components in
later exercises). Note that the Adobe SVG viewer is a plug-in for Internet Explorer
(IE), so IE will open when viewing an SVG file. Depending on the security settings
in IE, you may be prompted with a warning about active content.
Press Spreadsheets to open the numeric csv output files. In Exercise1a.csv, review
the pattern of outdoor conditions and loads. (To make it easier to read the column
38 CHAPTER 4. TUTORIAL EXAMPLE FOR RUNNING ENERGYPLUS
headings, select Row 1, format cells, and turn on wrap text; then select cell B2 and
select freeze panes.) In Exercise1aMeter.csv, review the facility district heating and
cooling meters.
Zone/Sys Air Temperature the zone air temperatures are already being reported.
Outdoor Dry Bulb is being reported (so you can compare to outside temperature)
The meter for the heating in the facility - DistrictHeating:Facility is being reported.
Facility is the entire building.
The meter for the cooling in the facility - DistrictCooling:Facility is being reported.
Using File -> Open Dataset, open the window glass materials dataset file, Window-
GlassMaterials.idf
-Hint: In IDF Editor , View -> Show Classes with Objects Only (or ctl -L) will hide all empty
object types from the class list.
Locate the object which defines the material properties for CLEAR 6MM. Select
this object (by clicking on the column heading).
Using Edit -> Copy Object (or the toolbar button, or ctl-C), copy this object.
Switch windows to file Exercise1B.idf and paste the window material into this
file. (Verify that is had been added by going to WindowMaterial:Glazing to view
the object.)
Use the pulldown list to select CLEAR 6MM for the outside layer, then press Enter
or Return to save this entry and move to the next field.
Select AIR 3MM for Layer 2, and CLEAR 6MM for Layer 3.
5. Add the east window (3m wide by 2m high, centered on wall, see the drawing in
Figure 4.1 to determine coordinates):
Multiplier . = 1
Vertex coordinates = as determined from the drawing Figure 4.1. Coordinates in this
input are in World Coordinates (all relative to the global origin of 0,0,0). Coordinates
are specified as viewed from the outside of the surface, using the rules specified in the
SurfaceGeometry object.
Always review the err file for errors and warnings. Fix problems if needed and re-run.
Are the windows in the right place in the dxf drawing file. (Use the Drawing File
button or select the DXF file from View -> Single File or from the Quick-Open panel).
40 CHAPTER 4. TUTORIAL EXAMPLE FOR RUNNING ENERGYPLUS
Review the surface details report in the eio file, search for Zone/Shading Surfaces
to find this report. (Use the Text Output button, Quick Open eio button, or select
from the single file menu, or use F7). This report is easier to read by pasting this
section into a spreadsheet and using the text to columns function with comma as a
delimiter).
Open the csv output file and compare the heating and cooling loads with the results
from Exercise1A.csv.
Copy the Schedule:Compact object named Office Lighting, and paste it into Ex-
ercise1C.idf.
Copy the ScheduleTypeLimits object named Fraction, and paste it into Exer-
cise1C.idf.
3. In Exercise1C.idf, add a LIGHTS object named ZONE ONE Lights, using the Office
Lighting schedule, peak input is 1000W. Consult the EnergyPlus Input Output Reference
section on Lights for values for the return, radiant, and visible fractions. Assume the lights
are surface mounted fluorescents.
4. Save and close the IDF file, select Exercise1C.idf in EP-Launch, run the simulation
and review outputs.
5. Open the rdd file (the report variable data dictionary) and find report variable names
related to Lights. Add a new Output:Variable object to report the lighting electric
consumption.
6. Run the simulation and review outputs.
3. Add a RunPeriod object to run a full annual simulation, let other fields default or
remain blank.
4. Add a Output:Table:SummaryReports object, and select the following re-
ports: Annual Building Performance Summary (ABUPS), Input Verification and
Results Summary (IVRS), Climate Summary, and Envelope Summary.
5. Add a OutputControl:Table:Style object, and select HTML format (ColumnSepa-
rator).
6. Edit existing Output:Variable and Output:Meter objects and change the reporting
frequency from Hourly to Monthly.
7. Save and close the IDF file, select Exercise1D.idf in EP-Launch.
8. Select Chicago TMY2 weather file (or the weather file of your choice) and run the
simulation.
9. Review outputs.
WindowMaterial:Gas ,
AIR 3MM , !- Name
Air , !- Gas Type
0.0032; !- Thickness {m}
Construction ,
DOUBLE PANE WINDOW , !- Name
CLEAR 6MM , !- Outside Layer
AIR 3MM , !- Layer #2
CLEAR 6MM; !- Layer #3
42 CHAPTER 4. TUTORIAL EXAMPLE FOR RUNNING ENERGYPLUS
FenestrationSurface :Detailed ,
EAST WINDOW , !- User Supplied Surface Name
WINDOW , !- Surface Type
DOUBLE PANE WINDOW , !- Construction Name of the Surface
ZONE SURFACE EAST , !- Base Surface Name
, !- OutsideFaceEnvironment Object
autocalculate , !- View Factor to Ground
, !- Name of shading control
, !- WindowFrameAndDivider Name
1, !- Multiplier
4, !- Number of vertices
8, 1.5, 2.35, !- X,Y,Z 1 {m}
8, 1.5, 0.35, !- X,Y,Z 2 {m}
8, 4.5, 0.35, !- X,Y,Z 3 {m}
8, 4.5, 2.35; !- X,Y,Z 4 {m}
FenestrationSurface :Detailed ,
WEST WINDOW , !- User Supplied Surface Name
WINDOW , !- Surface Type
DOUBLE PANE WINDOW , !- Construction Name of the Surface
ZONE SURFACE WEST , !- Base Surface Name
, !- OutsideFaceEnvironment Object
autocalculate , !- View Factor to Ground
, !- Name of shading control
, !- WindowFrameAndDivider Name
1, !- Multiplier
4, !- Number of Vertices
0, 4.5, 2.35, !- X,Y,Z 1 {m}
0, 4.5, 0.35, !- X,Y,Z 2 {m}
0, 1.5, 0.35, !- X,Y,Z 3 {m}
0, 1.5, 2.35; !- X,Y,Z 4 {m}
Output:Surfaces:List ,Details;
Schedule:Compact ,
Office Lighting , !- Name
Fraction , !- ScheduleType
Through: 12/31 , !- Complex Field #1
For: Weekdays SummerDesignDay , !- Complex Field #2
Until: 05:00 , 0.05, !- Complex Field #4
Until: 07:00 , 0.1, !- Complex Field #6
Until: 08:00 , 0.3, !- Complex Field #8
Until: 17:00 , 0.9, !- Complex Field #10
Until: 18:00 , 0.5, !- Complex Field #12
Until: 20:00 , 0.3, !- Complex Field #14
Until: 22:00 , 0.2, !- Complex Field #16
Until: 23:00 , 0.1, !- Complex Field #18
Until: 24:00 , 0.05, !- Complex Field #20
For: Saturday WinterDesignDay , !- Complex Field #21
Until: 06:00 , 0.05, !- Complex Field #23
Until: 08:00 , 0.1, !- Complex Field #25
Until: 12:00 , 0.3, !- Complex Field #27
Until: 17:00 , 0.15, !- Complex Field #29
Until: 24:00 , 0.05, !- Complex Field #31
For: Sunday Holidays AllOtherDays , !- Complex Field #32
Until: 24:00 , 0.05; !- Complex Field #34
ScheduleTypeLimits ,
Fraction , !- ScheduleType Name
0.0, !- Lower Limit Value
1.0, !- Upper Limit Value
CONTINUOUS; !- Numeric Type
Lights ,
ZONE ONE Lights , !- Name
4.2. INSTRUCTIONS 43
RunPeriod ,
1, !- Begin Month
1, !- Begin Day Of Month
12, !- End Month
31, !- End Day Of Month
UseWeatherFile , !- Day Of Week For Start Day
Yes , !- Use WeatherFile Holidays/Special Days
Yes , !- Use WeatherFile DaylightSavingPeriod
No , !- Apply Weekend Holiday Rule
Yes , !- Use WeatherFile Rain Indicators
Yes , !- Use WeatherFile Snow Indicators
1; !- Number of years of simulation
Output:Table:SummaryReports ,
Annual Building Utility Performance Summary , !- ReportName1
Input Verification and Results Summary , !- ReportName2
Climate Summary , !- ReportName3
Envelope Summary; !- ReportName4
OutputControl:Table ,
HTML; !- ColumnSeparator
SimulationControl ,
No , !- Do the zone sizing calculation
No , !- Do the system sizing calculation
No , !- Do the plant sizing calculation
No , !- Do the design day simulations
Yes; !- Do the weather file simulation
Chapter 5
44
5.2. A METHODOLOGY FOR USING ENERGYPLUS 45
Obtain sufficient central plant information to allow specification and scheduling of the
boilers, chillers and other plant equipment.
load calculated using a more detailed model. The distribution of the load within the building
cannot be estimated with the simplified building model, but its magnitude (such as would
be used in sizing the central plant equipment) can be quickly estimated using a very simple
model. For simplicity, assume there is no ground heat transfer; if you want to simulate
ground heat transfer, you should use the slab and/or basement programs as described in the
Auxiliary Programs document.
Take note of Zone 1, Zone 2, Zone 4, and Zone 7. The two important zoning concepts
can be demonstrated with the zoning to reinforce the idea of a thermal zone and encourage
the use of simplified models.
1. Notice that Zones 4 and 7 include two rooms that are not adjacent to one another but
are served by the same system. Because the air temperature in the two spaces is maintained
at the same uniform temperature, the two spaces, though separated spatially, may be defined
as a single zone. For our purposes, we will define them as separate zones.
2. Notice that Zone 1 and Zone 2 are served by the same fan system and could be
defined as a single zone with 7650 cfm of conditioned air supplied to the space. The space
was split into two zones because the designer expected higher solar loads on the South and
West sides of the wing and wanted to examine the distribution as well as the magnitude of
the load in the space.
5.2.5.1 Step 3.1. Determine heat transfer and heat storage surfaces.
The surfaces of the building can be described in any order; grouping surfaces by zone may
help you read the input file. Specifics of the describing surfaces help categorize the surfaces
heat transfer/storage as well as identify the surface construction information.
The details of inputting surfaces are described in the Input/Output Reference document.
The allowable surface types are shown in the following table:
48CHAPTER 5. OVERALL SCHEME/METHODOLOGY FOR RUNNING ENERGYPLUS
Note that subsurfaces (windows, doors) on these base surfaces will inherit the base surface
properties listed above. The following examples will use a bit more of the Surface definition
to give context.
Surfaces that specify themselves as the outside boundary condition are ceilings, floors
and partitions that divide temperature-controlled spaces. The program assumes that the
surface temperatures on both sides of the surface are the same. This means that even
though heat may be stored in a partition, ceiling, or floor, no heat flows through it.
5.2. A METHODOLOGY FOR USING ENERGYPLUS 51
Heat Storage Surfaces (Use current Surface name for ExteriorEnvironment), e.g.:
Some surfaces divide the temperature controlled space from the outside environment.
Surfaces that are both sun and wind exposed (e.g. exterior walls, exposed floors, roofs)
feel the full effect of both solar radiation and outside temperature, and the outside air film
resistance for these surfaces changes with wind speed and wind direction. Surfaces that
are not sun or wind exposed (a wall to an uncontrolled space) are not affected by solar
radiation, wind speed or direction and have a constant outside convective air film resistance.
Heat Transfer Surfaces Exposed to the Outside Environment, such as Exterior Walls,
Roofs, Exposed Floors:
Surfaces such as basement walls and slab floors separate the space from the earth sur-
rounding the surfaces. Therefore, the outside surface temperatures become the ground tem-
peratures.
Heat Transfer Surfaces in Contact with the Ground, such as Basement Walls or Slab
Floors:
Other surfaces separate zones that may be at different temperatures. These surface types
allow heat transfer (by conduction through the walls) from a zone at a higher temperature
52CHAPTER 5. OVERALL SCHEME/METHODOLOGY FOR RUNNING ENERGYPLUS
to a zone at a lower temperature. The location of the heat storage surface in the zone is
not important except in specialized solar studies. The surface above (wall to uncontrolled
space) would be more correctly modeled as an interzone surface.
Heat Transfer Surfaces Exposed to Another Zone, such as Interzone walls, ceilings or
floors:
BuildingSurface:Detailed ,Zn005:Wall005 , !- Base Surface Name
Wall ,INTERIOR , !- Class and Construction Name
MAINE WING , !- Zone
Surface ,Zn001:Wall009 , !- Exterior Conditions and Target
NoSun , !- Solar Exposure
NoWind , !- Wind Exposure
0.5000000 , !- VF to Ground
4, !-Rectangle
57.90000 , 47.79000 , 10.00000 ,
57.90000 , 47.79000 , 0.0000000E+00,
67.90000 , 47.79000 , 0.0000000E+00,
67.90000 , 47.79000 , 10.00000 ;
devices may require that more windows be specified or combined together. By using the
WindowMaterial:Glazing construction for your glass door, they will be correctly modeled in
EnergyPlus with sunlight transferring into the zone.
The following figure shows the surfaces and subsurfaces required for a one-zone model,
i.e., the education center. Since there were two types of partitions in the building, two heat
storage surfaces (internal mass) of different constructions were defined.
Notes:
(1) The surface type is a wall, floor, roof, window or door.
(2) User supplies name for the element. For this example use name from the DataSet:
ASHRAE_2005_HOF_Materials.idf. Similarly, the window was constructed
from the Windows.idf dataset.
Building North Axis: This syntax simplifies building geometry specification by designat-
ing one wall of the building as the buildings north pointing axis. The building model North
axis is measured from true (compass) North. Surface facing angles (see surface information
below) are then specified relative to the building north axis. The North Axis entry in the
Input Output Reference (duplicated here) illustrates specification of the building north axis.
Zone information:
1. Wall height: In a simple model, one should make all the walls the same height. Then,
the simple, 1 zone model can entirely enclose the space. In more complex models, you
may resize each wall accordingly.
Surface information:
56CHAPTER 5. OVERALL SCHEME/METHODOLOGY FOR RUNNING ENERGYPLUS
1. Base Surface Type: Heat Transfer/Heat Storage Surfaces may be of the following
types: wall, floor, roof, internal mass, or subsurface
2. Construction: The type of construction of the surface (see previous table).
Subsurface information:
1. Subsurfaces are Windows, Doors or GlassDoors
2. Area: Area of the subsurface.
3. Reveal: For windows only, the distance it is inset from the outside surface of a wall.
For simplicity, put all the windows in the same physical plane as the wall they are on.
For the single zone model, the following figure is a schematic representation of a one
zone representation. The figure shows the length of all base surfaces and the areas of all
subsurfaces (windows). Doors are shown and may be entered, if desired. In the table
(Table 5.4), the surfaces are numbered counter-clockwise around the zone beginning at the
lower left corner of the figure. This table is the minimum required zone information compiled
by the user. A few simple conventions should be followed to facilitate the construction of
zone information tables:
1. Number all surfaces in order counter-clockwise around the zone.
2. Keep the subsurfaces with the base surface on which they are located.
3. Specify lengths for base surfaces and areas for subsurfaces and internal mass.
4. Specify the roof and floor as rectangles of the correct size.
Full Building 1 Zone model
The column headings in the previous table have the following meanings:
Type: A shortened notation for the surface type in EnergyPlus to differentiate between
heat storage surfaces and various types of heat transfer surfaces.
Construction: A name for the surface construction types.
Length: The length of base surfaces (i.e. Exterior Walls).
Area: The area of subsurfaces (windows), roofs, floors.
Figure 5.6: Schematic of One Zone Model with Exterior Wall length and Window Areas.
60CHAPTER 5. OVERALL SCHEME/METHODOLOGY FOR RUNNING ENERGYPLUS
As an adjunct to the previous schematic layout for the one zone approach, the following
figure shows the same building but with IP units:
5.2. A METHODOLOGY FOR USING ENERGYPLUS 61
Tutorial Exercise 2
The following example is taken directly from the training course Introduction to Energy-
Plus, Exercise 2. Of course, it is presented here without the benefit of classroom pre-
sentation and discussion but when followed step by step, should provide an introduction of
actually using EnergyPlus.
62
6.1. UNITARY SYSTEM AND VAV USING HVACTEMPLATE INPUTS 63
Walls are wood shingle over plywood, insulation, and gypsum board.
Roof is gravel built up roof with mineral board insulation and plywood sheathing.
Windows and glass doors are double pane Low-e clear glass with argon gap.
Infiltration is 0.25 air changes per hour (always on, proportional to wind speed).
(WindowGlassMaterials.idf)
64 CHAPTER 6. TUTORIAL EXERCISE 2
Cooling setpoints: 23.9C (75F) occupied, 40.0C (104F, system off) unoccupied
6.1.2.3 Environment
Location: Chicago, Illinois, USA
6.2 Instructions
6.2.1 Exercise 2A. Add Unitary System with DX Cooling and Gas
Heating (Furnace) Serving a Single Zone
Objective: Learn how to describe a thermostat and unitary equipment using HVACTemplate
objects.
1) Open Exercise2.idf and save it as Exercise2A.idf. (Exercise2.idf contains the building
envelope, internal loads, and some extra schedules to support the HVAC system descriptions
which will be added in this Exercise.)
2) Add a HVACTemplate:Thermostat object to define the thermostat setpoints for
this simulation.
Choose a name for the thermostat. This name will be referenced in the next step.
For heating setpoints, use pre-defined schedule named Office Heating Setpoints.
For cooling setpoints, use pre-defined schedule named Office Cooling Setpoints.
5) Add a Sizing:Parameters object and set the sizing factor to 1.2 (for 20% oversizing).
6) Edit the SimulationControl object and set the Zone and System sizing flags to
Yes.
7) Run the simulation and review output files, especially:
err, there will be some warnings about meters that do no exist and the ABUPS report
not being a full year. These will go away as more features are added and an annual
run is simulated.
DXF , drawing of building surfaces. (Try selecting the Southwest Isometric named
view, then see how each zone is a separate drawing layer. In Voloview open the View
-> Layers dialog. Click on the light bulbs to toggle display of each zone. In TrueView
click on the Layer Properties Manager toolbar button. To toggle display of a layer,
single-click a layer light bulb, then click apply.)
SVG, block diagram of the HVAC system components. (HINT: right-click in the draw-
ing and read the Help to learn how to navigate in the SVG viewer.)
Add output variables to report operation of the system (furnace) fan, heating coil, and
cooling coil. Reference the RDD output file for variable names.
Note during hour 7 of the summer design day that NORTH PERIMETER:Zone/Sys
Sensible Heating RateW is nonzero, but the heating coil is off and the DX cooling
coil shows a load. Why? This report variable reports the impact of the system on
the zone (not the zones demand for heating or cooling), averaged over the hour. The
system fan is scheduled on at 6 a.m., but the outside air dampers are closed. The
zone is not warm enough from the night to require cooling, so the circulating fan heat
warms the zone slightly for a portion of the hour until the zone temperature exceeds
the cooling setpoint and the DX coil comes on for the remainder of the hour. If the
economizer were active, this would not occur.
66 CHAPTER 6. TUTORIAL EXERCISE 2
6.2.2 Exercise 2B. Add VAV System with Reheat Serving Four
Zones with Chiller and Boiler Plant
Objective: Learn how to describe a VAV system with central plant using HVACTemplate
objects.
1) Save Exercise2A.idf as Exercise2B.idf.
2) Add a HVACTemplate:System:VAV object. Retain the defaults for all fields
except the following:
Specify the same air handler name added in Step 2 (use the dropdown list)
Specify the same thermostat control added in Exercise 2A Step 2 (again, use the
dropdown list).
Note how the heating and cooling rates for the NORTH PERIMETER zone are smaller
than before. Why?
Review the SVG drawing to see the components of the VAV system and water loops.
Browse the expidf file in a text editor (or open in IDF Editor from File, Open, setting
file type to expidf) to see the full detailed description of the HVAC systems using native
EnergyPlus objects (the expanded result of the HVACTemplate preprocessor).
Open the rdd output file for Exercise2B in the text editor and find the following report
variable names to copy and paste into the fields of the Report:Table:Monthly object in
IDF Editor. Variable name and aggregation type are listed in pairs.
HVACTemplate:Thermostat ,
Office Thermostat , !- Thermostat Name
Office Heating Setpoints ,!- Thermostat Heating Setpoint Schedule
, !- Thermostat Constant Heating Setpoint {C}
Office Cooling Setpoints ,!- Thermostat Cooling Setpoint Schedule
; !- Thermostat Constant Cooling Setpoint {C}
HVACTemplate:Zone:Unitary ,
NORTH PERIMETER , !- Zone Name
North Zone Unitary , !- Air Handling System Name
Office Thermostat , !- Thermostat Name
autosize , !- Zone Supply Air Max Flow Rate {m3/s}
, !- Zone Supply Air Sizing Factor
Flow/Person , !- Zone Outside Air Method
0.00944 , !- Zone Outside Air Flow Rate per Person {m3/s}
0.0, !- Zone Outside Air Flow per Zone Area {m3/s-m2}
0.0, !- Zone Outside Air Flow per Zone {m3/s}
, !- Zone Supply Plenum Name
, !- Zone Return Plenum Name
None , !- Baseboard Heating Type
, !- Baseboard Heating Availability Schedule
autosize; !- Baseboard Heating Capacity {W}
HVACTemplate:System:Unitary ,
North Zone Unitary , !- Air Handling System Name
Office HVAC , !- System Availability Schedule
NORTH PERIMETER , !- Control Zone Name or Thermostat Location
autosize , !- Supply Fan Max Flow Rate {m3/s}
Continuous , !- Supply Fan Operating Mode Schedule Name
0.7, !- Supply Fan Total Efficiency
600, !- Supply Fan Delta Pressure {Pa}
0.9, !- Supply Fan Motor Efficiency
1, !- Supply Fan Motor in Air Stream Fraction
Single -speed DX , !- Cooling Coil Type
, !- Cooling Coil Availability Schedule
autosize , !- Cooling Coil Capacity {W}
6.2. INSTRUCTIONS 69
Sizing:Parameters ,
1.2; !- sizing factor
HVACTemplate:System:VAV ,
VAV with Reheat , !- Air Handling System Name
Office HVAC , !- System Availability Schedule
autosize , !- Supply Fan Max Flow Rate {m3/s}
autosize , !- Supply Fan Min Flow Rate {m3/s}
0.7, !- Supply Fan Total Efficiency
1000, !- Supply Fan Delta Pressure {Pa}
0.9, !- Supply Fan Motor Efficiency
1, !- Supply Fan Motor in Air Stream Fraction
ChilledWater , !- Cooling Coil Type
, !- Cooling Coil Availability Schedule
, !- Cooling Coil Setpoint Schedule
13, !- Cooling Coil Design Setpoint {C}
None , !- Heating Coil Type
, !- Heating Coil Availability Schedule
, !- Heating Coil Setpoint Schedule
10.0, !- Heating Coil Design Setpoint {C}
0.8, !- Gas Heating Coil Efficiency
, !- Gas Heating Coil Parasitic Electric Load {W}
None , !- Preheat Coil Type
, !- Preheat Coil Availability Schedule
, !- Preheat Coil Setpoint Schedule
7.2, !- Preheat Coil Design Setpoint {C}
70 CHAPTER 6. TUTORIAL EXERCISE 2
HVACTemplate:Zone:VAV ,
SOUTH PERIMETER , !- Zone Name
VAV with Reheat , !- Air Handling System Name
Office Thermostat , !- Thermostat Name
autosize , !- Zone Supply Air Max Flow Rate {m3/s}
, !- Zone Supply Air Sizing Factor
0.2, !- Zone Supply Air Min Flow Fraction
Flow/Person , !- Zone Outside Air Method
0.00944 , !- Zone Outside Air Flow Rate per Person {m3/s}
0.0, !- Zone Outside Air Flow per Zone Area {m3/s-m2}
0.0, !- Zone Outside Air Flow per Zone {m3/s}
HotWater , !- Reheat Coil Type
, !- Reheat Coil Availability Schedule
Reverse , !- Zone Damper Heating Action
, !- Zone Supply Plenum Name
, !- Zone Return Plenum Name
None , !- Baseboard Heating Type
, !- Baseboard Heating Availability Schedule
autosize; !- Baseboard Heating Capacity {W}
HVACTemplate:Zone:VAV ,
EAST PERIMETER , !- Zone Name
VAV with Reheat , !- Air Handling System Name
Office Thermostat , !- Thermostat Name
autosize , !- Zone Supply Air Max Flow Rate {m3/s}
, !- Zone Supply Air Sizing Factor
0.2, !- Zone Supply Air Min Flow Fraction
Flow/Person , !- Zone Outside Air Method
0.00944 , !- Zone Outside Air Flow Rate per Person {m3/s}
0.0, !- Zone Outside Air Flow per Zone Area {m3/s-m2}
0.0, !- Zone Outside Air Flow per Zone {m3/s}
HotWater , !- Reheat Coil Type
, !- Reheat Coil Availability Schedule
Reverse , !- Zone Damper Heating Action
6.2. INSTRUCTIONS 71
HVACTemplate:Zone:VAV ,
WEST PERIMETER , !- Zone Name
VAV with Reheat , !- Air Handling System Name
Office Thermostat , !- Thermostat Name
autosize , !- Zone Supply Air Max Flow Rate {m3/s}
, !- Zone Supply Air Sizing Factor
0.2, !- Zone Supply Air Min Flow Fraction
Flow/Person , !- Zone Outside Air Method
0.00944 , !- Zone Outside Air Flow Rate per Person {m3/s}
0.0, !- Zone Outside Air Flow per Zone Area {m3/s-m2}
0.0, !- Zone Outside Air Flow per Zone {m3/s}
HotWater , !- Reheat Coil Type
, !- Reheat Coil Availability Schedule
Reverse , !- Zone Damper Heating Action
, !- Zone Supply Plenum Name
, !- Zone Return Plenum Name
None , !- Baseboard Heating Type
, !- Baseboard Heating Availability Schedule
autosize; !- Baseboard Heating Capacity {W}
HVACTemplate:Zone:VAV ,
CORE , !- Zone Name
VAV with Reheat , !- Air Handling System Name
Office Thermostat , !- Thermostat Name
autosize , !- Zone Supply Air Max Flow Rate {m3/s}
, !- Zone Supply Air Sizing Factor
0.2, !- Zone Supply Air Min Flow Fraction
Flow/Person , !- Zone Outside Air Method
0.00944 , !- Zone Outside Air Flow Rate per Person {m3/s}
0.0, !- Zone Outside Air Flow per Zone Area {m3/s-m2}
0.0, !- Zone Outside Air Flow per Zone {m3/s}
HotWater , !- Reheat Coil Type
, !- Reheat Coil Availability Schedule
Reverse , !- Zone Damper Heating Action
, !- Zone Supply Plenum Name
, !- Zone Return Plenum Name
None , !- Baseboard Heating Type
, !- Baseboard Heating Availability Schedule
autosize; !- Baseboard Heating Capacity {W}
HVACTemplate:Plant:ChilledWaterLoop ,
Chilled Water Plant , !- Plant Loop Name
, !- Pump Schedule
Intermittent , !- Pump Control Type
Default , !- Chiller Plant Operation Scheme Type
, !- Chiller Plant Operation Scheme Name
, !- Chilled Water Setpoint Schedule
7.22, !- Chilled Water Design Setpoint {C}
ConstantPrimaryNoSecondary , !- Chilled Water Pump Configuration
179352 , !- Primary Chilled Water Pump Rated Head {Pa}
179352 , !- Secondary Chilled Water Pump Rated Head {Pa}
Default , !- Condenser Plant Operation Scheme Type
, !- Condenser Plant Operation Scheme List Name
SpecifiedSetpoint , !- Condenser Water Temperature Control Type
, !- Condenser Water Setpoint Schedule
29.4, !- Condenser Water Design Setpoint {C}
179352 , !- Condenser Water Pump Rated Head {Pa}
None , !- Chilled Water Setpoint Reset Type
12.2, !- Chilled Water Setpoint at Outdoor Dry Bulb Low {C}
72 CHAPTER 6. TUTORIAL EXERCISE 2
HVACTemplate:Plant:Chiller ,
Chiller 1, !- Chiller Name
ElectricReciprocatingChiller , !- Chiller Type
autosize , !- Capacity {W}
3.6, !- COP {W/W}
WaterCooled , !- Condenser Type
; !- Priority
HVACTemplate:Plant:Tower ,
Tower 1, !- Tower Name
TwoSpeed , !- Tower Type
autosize , !- High -Speed Nominal Capacity {W}
autosize , !- High -Speed Fan Power {W}
autosize , !- Low -Speed Nominal Capacity {W}
autosize , !- Low -Speed Fan Power {W}
autosize , !- Free Convection Capacity {W}
; !- Priority
HVACTemplate:Plant:HotWaterLoop ,
Hot Water Plant , !- Plant Loop Name
, !- Pump Schedule
Intermittent , !- Pump Control Type
Default , !- Hot Water Plant Operation Scheme Type
, !- Hot Water Plant Operation Scheme List Name
, !- Hot Water Setpoint Schedule
82, !- Hot Water Design Setpoint {C}
ConstantFlow , !- Hot Water Pump Configuration
179352 , !- Hot Water Pump Rated Head {Pa}
None , !- Hot Water Setpoint Reset Type
82.2, !- Hot Water Setpoint at Outdoor Dry Bulb Low {C}
-6.7, !- Hot Water Reset Outdoor Dry Bulb Low {C}
65.6, !- Hot Water Setpoint at Outdoor Dry Bulb High {C}
10; !- Hot Water Reset Outdoor Dry Bulb High {C}
HVACTemplate:Plant:Boiler ,
Boiler 1, !- Boiler Name
HotWaterBoiler , !- Boiler Type
autosize , !- Capacity {W}
0.8, !- Efficiency
NaturalGas , !- Fuel Type
; !- Priority
6.2.4.3 Exercise 2C
Output:Table:Monthly ,
Zone Temperature Report , !- Name
2, !- DigitsAfterDecimal
Zone Mean Air Temperature , !- VariableOrMeterName01
6.2. INSTRUCTIONS 73
SumOrAverage , !- AggregationType01
Zone Mean Air Temperature , !- VariableOrMeterName02
Maximum , !- AggregationType02
Zone Mean Air Temperature , !- VariableOrMeterName03
Minimum , !- AggregationType03
Zone People Number of Occupants , !- VariableOrMeterName04
HoursPositive , !- AggregationType04
Zone Mean Air Temperature , !- VariableOrMeterName05
SumOrAverageDuringHoursShown , !- AggregationType05
Zone Mean Air Temperature , !- VariableOrMeterName06
MaximumDuringHoursShown , !- AggregationType06
Zone Mean Air Temperature , !- VariableOrMeterName07
MinimumDuringHoursShown ; !- AggregationType07
Chapter 7
EnergyPlus has several options for the user to create input files. For the purposes of this
document, we will describe briefly the workings of the IDF Editor that is supplied with the
EnergyPlus Installation. The IDF Editor is a simple, intelligent editor that reads the
EnergyPlus Data Dictionary (IDD) and allows creation/revision of EnergyPlus Input Files
(IDF). It can be run from a shortcut in the main EnergyPlus directory (created as part of
the install) or directly from EP-Launch.
Full details of the IDF Editor can be found in the Auxiliary Programs document. IDD
Conventions (to be able to read the IDD) are found in the Input Output Reference document.
EnergyPlus standard units are described in several places, including later in this document.
IDF Editor is an optional component of the EnergyPlus installation. For users who want
a simple way of creating or editing EnergyPlus input data files (IDF), IDF Editor provides
this service. The IDF Editor does not check inputs for validity, although some numeric
fields are highlighted if out of range and some text fields are highlighted if they contain an
invalid reference. For instructions and rules that must be followed when creating an IDF file
the user should refer to the Input/Output Reference document.
74
75
Also on the File menu is the Open DataSet menu and submenu. This allows you to open
any input file that appears in the DataSet subdirectory and copy objects from them into
another file. This is required because EnergyPlus does not read the DataSet files, it is up to
you to include objects from them.
fields that contain invalid references. The Validity Check dialog also shows when an entry
for a field is not one of the possible lists of choices. The Perform Validity Check When
Saving File can be turned on and off and automatically performs the check whenever the file
is saved.
80
8.5. USEFUL PROGRAMS 81
8.6 WeatherData
The E/E+ format is very flexible (as well as being ASCII and somewhat readable). In ad-
dition to the usual weather data (temperatures, solar radiation data), the format embodies
other information from the location and weather data (e.g. design conditions, calculated
ground temperatures, typical and extreme weather periods). The EPW (weather data for-
mat) is described in Auxiliary Programs Document. Other details including statistical
reports, backgrounds on data sources and formats, use of the Weather Converter program
(used both for processing data and reporting) are also provided in the Auxiliary Programs
document.
The web site for EnergyPlus (http://www.energyplus.gov) provides downloadable
weather data for many sites throughout the world from several different formats. In
addition, we are amenable to posting more weather data from users.
8.8 HVAC-Diagram
Another post processing program (EnergyPlus versions 1.2 and later) is the HVAC-Diagram
application. It reads one of the EnergyPlus output files (eplusout.bnd and produces a Scal-
able Vector Graphics (SVG) file. More information on the HVAC Diagram program is found
in the Auxiliary Programs document.
8.9 CSVProc
This simple post processing program uses .csv files (such as created by ReadVarsESO) and
performs some simple statistics on the contents. This program is described more fully in the
Auxiliary Programs document.
8.10 convertESOMTR
This simple post processing program can be used seamlessly with EP-Launch to provide IP
(inch-pound) unit output files rather than SI units. This program is described more fully in
the Auxiliary Programs document.
8.10. CONVERTESOMTR 83
8.11 DataFiles
Some example files are installed during installation (Sample Files option). Each sample
input file should contain comments about its purpose at the start of the file. Other example
files are made available from the website (http://www.energyplus.gov/).
Energy Meters
Meters
Facility
Building
Zone
System
Plant
Both the fuel types and enduse types are set within the program by the developers.
Current Fuel types are shown in the table below. There is also a special category called
EnergyTranser.
85
86 CHAPTER 9. ENERGY METERS
Utility/Fuel Types
Electricity
Gas
Gasoline
Diesel
Coal
FuelOil#1
FuelOil#2
Propane
Water
Steam
DistrictCooling
DistrictHeating
AdditionalTypes
HeatingCoils
CoolingCoils
Chillers
Boilers
Baseboard
HeatRecoveryForCooling
HeatRecoveryForHeating
AdditionalTypes
HeatingCoils
CoolingCoils
Chillers
Boilers
Baseboard
HeatRecoveryForCooling
HeatRecoveryForHeating
EnergyPlus has adopted the standard SI units for input and output.
ASCII with no spaces is used for abbreviations. Note that exponents appear without
any indication of exponentiation: i.e., kg/m3 not kg/m3 or kg/m**3. Also note the use of
dashes. We have W/m2-K not W/m2*K or W/(m2*K).
At the end we note the problem variables the inputs that have non-standard units.
Inputs using these units will have to be changed and the code checked to see how the
quantities are used internally.
89
90 CHAPTER 10. STANDARD ENERGYPLUS UNITS