Lecture 4: Simulation Control,

Location, and Weather Input

Material prepared by GARD Analytics, Inc. and University of Illinois

at Urbana-Champaign under contract to the National Renewable Energy
Laboratory. All material Copyright 2002-2003 U.S.D.O.E. - All rights reserved
Importance of this Lecture to the
Simulation of Buildings
Every building is different in many ways:
Location and exterior thermal environment

Construction

HVAC system

Exterior thermal environment is a driving force that

determines how a building will respond
Energy efficient design requires an understanding of
and a response to the exterior thermal environment
Thermal simulation requires information on the
exterior thermal environment to properly analyze the
building from an energy perspective

2
 Purpose of this Lecture

Gain an understanding of how to control

the exterior environment of the
simulation
Building Location
Weather and Ground Temperature Data
Length of Simulation
Other General Features of the Input

3
Keywords Covered in this Lecture

Version
Run Control
Location
DesignDay
SpecialDayPeriod
RunPeriod
DaylightSavingPeriod
GroundTemperature
GroundReflectance
Snow Ground Reflectance Modifiers
4
 Quick Review of Relationship
Between IDD and IDF Files
IDD: Input Data Dictionary
File which defines what information should
be located in the user input file
This file should NOT be modified

IDF: Input Data File

User input file containing information about
the building and its primary and secondary
systems
This file can be modified using a text editor
or using the IDF Editor
5
 Keyword: Version

IDD Description
VERSION,
\unique-object
A1 ; \field Version Identifier
\required-field

Notes
\unique-object means only one of these
are allowed per IDF file
\required-field means this field must be
present in the description
6
 Keyword Example: Version
IDF Examples
Version, 1.1; ! Shortened input format
Version,
1.1; !- Version Identifier
Notes:
The Version identifier refers to a version of the
EnergyPlus program
Updates in the EnergyPlus program may result in
changes to the IDD
An error message will result if the IDF file version
does not correspond to the version of EnergyPlus
being run
This course is based on EnergyPlus Version 1.1

7
 Keyword: Location

IDD Description (shortened)

Location,
A1 , \field Location Name
N1 , \field Latitude
N2 , \field Longitude
N3 , \field TimeZone
N4 ; \field Elevation

IDD Description (detailed)

Location,
\unique-object Only one per IDF file
\min-fields 5
All five fields are required
A1 , \field Location Name
\required-field Information expected: a name
\type alpha
Field is a character string 8
 Keyword: Location

IDD Description (detailed, continued)

N1 , \field Latitude Building site latitude (global position)
\units deg
\minimum -90.0 N1 in degrees
\maximum +90.0
\default 0.0 Limits (-90N1+90) and Default Value
\note + is North, - is South, degree minutes represented
\note in decimal (i.e. 30 minutes is .5)
\type real Interpretation
Field is a decimal value
N2 , \field Longitude information
\units deg
Building site longitude (global position)
\minimum -180.0
\maximum +180.0
\default 0.0
\note - is West, + is East, degree minutes represented
\note in decimal (i.e. 30 minutes is .5)
\type real 9
 Keyword: Location

IDD Description (detailed, continued)

N3 , \field Time Zone Political time zone
\units hr
\minimum -12.0 N3 in hours
\maximum +12.0
\default 0.0 Note
\note Time relative to GMT. Decimal hours.
\type real
N4 ; \field Elevation Building site elevation
\units m
\minimum -300.0 N4 in meters
\maximum< 6096.0
\default 0.0
\type real

10
 Keyword Example: Location

IDF Example
Location, DENVER, 39.750, -104.870, -7.0, 1610.26;
or
Location,
DENVER COLORADO, !- LocationName
39.750, !- Latitude {deg}
-104.870, !- Longitude {deg}
-7.0, !- TimeZone {hr (decimal)}
1610.26; !- Elevation {m}
Notes:
Location affects the sun angles, air properties, etc.
that the building experiences

11
 Keyword: DesignDay

IDD Description (shortened)

DesignDay,
A1 , \field DesignDayName
N1 , \field Maximum Dry-Bulb Temperature
N2 , \field Daily Temperature Range
N3 , \field Wet-Bulb Temperature At MaxTemp
N4 , \field Barometric Pressure
N5 , \field Wind Speed
N6 , \field Wind Direction
N7 , \field Sky Clearness
N8 , \field Rain Indicator
N9 , \field Snow Indicator
N10, \field Day Of Month
N11, \field Month
A2 , \field Day Type
N12; \field Daylight Saving Time Indicator
12
 Keyword: DesignDay

Purpose: the DesignDay input syntax

defines a single day of weather
information
Design day simulations are often used
for peak load or sizing calculations
Data required for this keyword can be
found in a variety of places (see next
slide)

13
 DesignDay Sources
MacroDataSets folder
US, Canada, and International

2001 ASHRAE data

Datasets
US locations

pre-1997 ASHRAE data, from BLAST library

*.ddy files
Included in weather data zip files on web site

2001 ASHRAE data

14
 Keyword: DesignDay

IDD Description (detailed)

DesignDay, Keywordnote all one word
\min-fields 14
14 fields (all) required
A1 , \field DesignDayName
\type alpha Unique character string
\required-field name for design day
\reference DesignDays
N1 , \field Maximum Dry-Bulb Temperature Other
\required-field references to
\units C a design day
N1 is the maximum in the IDF will
\minimum> -70
dry bulb temperature expect an
\maximum< 70
experience for this existing
\note
design day in degrees design day
\type real
Celsius name
15
 Keyword: DesignDay

IDD Description (detailed)

N2 , \field Daily Temperature Range
\required-field
Range of temperatures expected
\units deltaC
\minimum 0 Units are DC
\type real Must be zero or greater
\note must still produce appropriate maximum dry bulb
N3 , \field Wet-Bulb Temperature At MaxTemp
\required-field
\units C Mean coincident wet-bulb
\minimum> -70 temperature in C
\maximum< 70
\type real

16
 Keyword: DesignDay

IDD Description (detailed)

N4 , \field Barometric Pressure Outdoor barometric
\required-field pressure (assumed
\units Pa constant for entire
\minimum> 70000 day) in Pascals
\maximum< 120000
\type real IP Units if interface
\ip-units inHg accepts these units
N5 , \field Wind Speed
\required-field Wind speed
\units m/s (assumed constant
\minimum 0 for entire day) in
\maximum 40 meters per second
\ip-units miles/hr
\type real
17
 Keyword: DesignDay

IDD Description (detailed)

N6 , \field Wind Direction Wind direction
\required-field (assumed constant
\units deg for entire day) in
\minimum 0 degrees (assumes
\maximum 359.9 North is 0, East is
\note North=0.0 East=90.0 90, South is 180,
\type real etc.)
N7 , \field Sky Clearness
\required-field Sky clearness
\minimum 0.0 (assumed constant
Maximum allows for
\maximum 1.2 for entire day)
altitude adjustment
\default 0.0
\note 0.0 is totally unclear, 1.0 is totally clear
\type real
18
 Keyword: DesignDay

IDD Description (detailed)

N8 , \field Rain Indicator Rain flag (assumed
\minimum 0 constant for entire
\maximum 1 day) affects
\default 0 exterior convection
\note 1 is raining, 0 is not coefficients
\type integer
N9 , \field Snow Indicator Rain flag (assumed
\minimum 0 constant for entire
\maximum 1 day) affects ground
\default 0 reflectance
\note 1 is Snow on Ground, 0 is no Snow on Ground
\type integer
Should be an
integer value not a
decimal number
19
 Keyword: DesignDay

IDD Description (detailed)

Numerical day of
N10, \field Day Of Month
month (must be
\required-field
valid for month
\minimum 1
chosen)
\maximum 31
\type integer
\note must be valid for Month field
N11, \field Month
\required-field Numerical month of
\minimum 1 the year
\maximum 12
\type integer

20
 Keyword: DesignDay
Type of day/day of
IDD Description (detailed) the week for design
A2 , \field Day Type day (may affect
\required-field schedule values)
\note Day Type selects the schedules appropriate
\note for this design day
\type choice This field is a choice
\key Sunday of one of the
\key Monday options listed as
\key Tuesday \key
\key Wednesday
\key Thursday This field must
\key Friday equal one of these
\key Saturday choices of keywords
\key Holiday (note that none of
\key SummerDesignDay these keywords has
\key WinterDesignDay spaces)
\key CustomDay1
\key CustomDay2 21
 Keyword: DesignDay

IDD Description (detailed)

N12; \field Daylight Saving Time Indicator
\minimum 0
\maximum 1 Whether daylight
\default 0 savings time should be
\note 1=Yes, 0=No in effect for this design
\type integer day

22
Keyword Example: DesignDay

IDF Example
DesignDay,
DENVER COLORADO SUMMER, !- DesignDayName
32.8, !- Maximum Dry-Bulb Temperature {C}
17.8, !- Daily Temperature Range {C}
15.0, !- Wet-Bulb Temperature At MaxTemp {C}
84060.0, !- Barometric Pressure {Pa}
3.97, !- Wind Speed {m/s}
146.0, !- Wind Direction {deg}
1.10, !- Sky Clearness
0, !- Rain Indicator
0, !- Snow Indicator
21, !- Day Of Month
7, !- Month
Monday, !- Day Type
0; !- Daylight Saving Time Indicator
23
Keyword: DaylightSavingPeriod

IDD Description (shortened)

DaylightSavingPeriod,
A1, \field StartDate
A2; \field EndDate

Purpose: define the time frame during which

daylight savings rules should apply
Note that this can be specific to location (not
all sites use daylight savings time in the
summer)

24
 Keyword:
DaylightSavingPeriod
IDD Description (detailed)
DaylightSavingPeriod, Keywordnote all one word
\unique-object
\min-fields 2
\memo This object sets up the daylight saving period
\memo for any RunPeriod.
\memo Ignores any daylightsavingperiod values on the
\memo weather file and uses this definition.
\memo (These are not used with DesignDay objects.)
A1, \field StartDate
\required-field Note: not used for design
days and will override any
information found on the
Date when daylight
weather file
savings goes into effect
(details on format on next
slide) 25
 Keyword:
DaylightSavingPeriod
IDD Description (detailed)
A2; \field EndDate Date when daylight
\required-field savings period ends
\memo Dates can be several formats:
\memo <number>/<number> (month/day) Format information
\memo <number> <Month> for start and end date
\memo <Month> <number> of daylight savings
\memo <Nth> <Weekday> in <Month) time (see examples
\memo Last <WeekDay> in <Month> below)
\memo <Month> can be January, February, March, etc.
\memo Months can be the first 3 letters of the month
\memo <Weekday> can be Sunday, Monday, Tuesday, etc.
\memo <Nth> can be 1 or 1st, 2 or 2nd, etc. up to 5(?)
Date examples:4/11 OR 11 April OR April 11
1st Sunday in April OR 1 Sunday in Apr
Last Sunday in October 26
 Keyword Example:
DaylightSavingPeriod
IDF Examples
DaylightSavingPeriod,
1st Sunday in April, !- Start Date
Last Sunday in October; !- End Date

or
DaylightSavingPeriod,
4/1, !- Start Date
31 October; !- End Date

27
 Keyword: SpecialDayPeriod

IDD Description (shortened)

SpecialDayPeriod,
A1, \field Holiday Name
A2, \field StartDate
N1, \field duration (number of days)
A3; \field SpecialDayType

Purpose: to set up the occurrence of special

days throughout the year or to override the
values set in a weather file
Note: this information does not apply to
design days
28
 Keyword: SpecialDayPeriod

IDD Description (detailed)

SpecialDayPeriod, Keywordnote all one word
\min-fields 4
\memo This object sets up holidays/special days to be
\memo used during weather file run periods.
\memo (These are not used with DesignDay objects.)
\memo Depending on the value in the run period, days
\memo on the weather file may also be used. However,
\memo the weather file specification will take
\memo precedence over any specification shown here.
\memo (No error message on duplicate days or
\memo overlapping days).
A1, \field Holiday Name Unique identifying name
\required-field

29
 Keyword: SpecialDayPeriod

IDD Description (detailed)

A2, \field StartDate Date when period
\required-field starts; format
\memo Dates can be several formats: similar to dates for
\memo <number>/<number> (month/day) daylight savings
\memo <number> <Month> time
\memo <Month> <number>
\memo <Nth> <Weekday> in <Month)
\memo Last <WeekDay> in <Month>
\memo <Month> can be January, February, March, etc.
\memo Months can be the first 3 letters of the month
\memo <Weekday> can be Sunday, Monday, Tuesday, etc.
\memo <Nth> can be 1 or 1st, 2 or 2nd, etc. up to 5(?)
N1, \field duration (number of days)
\minimum 1
\maximum 366 Length of special
\default 1 period in days 30
 Keyword: SpecialDayPeriod

IDD Description (detailed)

A3; \field SpecialDayType Type of day
\required-field (see
\note SpecialDayType selects the schedules choices
\note appropriate for each day so labeled given in
\type choice the \key
\key Holiday Note the list) this
\key SummerDesignDay impact on should be
\key WinterDesignDay schedules considered
\key CustomDay1
\key CustomDay2
\default Holiday

31
 Keyword Example:
SpecialDayPeriod
IDF Example
SpecialDayPeriod,
Memorial Day, !- Holiday Name
Last Monday in May, !- Start Date
1, !- duration (number of days)
Holiday; !- SpecialDayType

32
 Keyword: RunPeriod
IDD Description (shortened)
RunPeriod,
N1 , \field Begin Month
N2 , \field Begin Day Of Month
N3 , \field End Month
N4 , \field End Day Of Month
A1 , \field Day Of Week For Start Day
A2, \field Use WeatherFile Holidays/Special Days
A3, \field Use WeatherFile DaylightSavingPeriod
A4, \field Apply Weekend Holiday Rule
A5, \field Use WeatherFile Rain Indicators
A6; \field Use WeatherFile Snow Indicators
Purpose: to define the simulation period for
EnergyPlus (program does not assume entire year
simulation)
33
 Keyword: RunPeriod

IDD Description (detailed)

RunPeriod, Keywordnote all one word
\min-fields 10
N1 , \field Begin Month
\required-field
\minimum 1
\maximum 12 Starting date for period
\type integer to be simulated;
N2 , \field Begin Day Of Month entered as two separate
\required-field fields, both integer
\minimum 1 values
\maximum 31
\type integer

34
 Keyword: RunPeriod

IDD Description (detailed, continued)

N3 , \field End Month
\required-field
\minimum 1
Ending date for period
\maximum 12
to be simulated;
\type integer
entered as two separate
N4 , \field End Day Of Month
fields, both integer
\required-field
values
\minimum 1
\maximum 31
\type integer

35
 Keyword: RunPeriod

IDD Description (detailed, continued)

A1 , \field Day Of Week For Start Day
\note =<blank - use WeatherFile>
\default UseWeatherFile
Note that Day of week for starting
\type choice
this is not a date; can be used to
\key Sunday
required override day of week
\key Monday
field due to specified on the weather file
\key Tuesday
the lack of \key Wednesday
the line that \key Thursday Options for day of week
says \key Friday for starting date
\required- \key Saturday
field; all \key UseWeatherFile
fields after
this point are
also optional
36
 Keyword: RunPeriod

IDD Description (detailed, continued)

A2, \field Use WeatherFile Holidays/Special Days
\note If yes or blank, use holidays on Weatherfile.
\note If no, do not use the holidays on Weatherfile.
\note Note: You can still specify holidays/special days
\note using the SpecialDayPeriod object(s).
\type choice These two input fields are used to override the
\default Yes definition of holidays and daylight savings time
\key Yes period from the weather file.
\key No
A3, \field Use WeatherFile DaylightSavingPeriod
\note If yes or blank, use period specified on Weatherfile.
\note If no, do not use period as specified on Weatherfile.
\type choice
\default Yes The choices for these fields are
\key Yes simply a yes or a no. 37
\key No
 Keyword: RunPeriod

IDD Description (detailed, continued)

A4, \field Apply Weekend Holiday Rule
\note if yes and single day holiday falls on weekend,
\note "holiday" occurs on following Monday
\type choice
\key Yes These three input
\key No fields are used to
\default No override the
A5, \field Use WeatherFile Rain Indicators definition of holiday
\type choice weekend rules,
\key Yes presence of rain
\key No
indicators, and
\default Yes
A6; \field Use WeatherFile Snow Indicators
presence of snow
\type choice indicators from the
\key Yes weather file.
\key No
\default Yes The choices for these fields are
simply a yes or a no. 38
Keyword Example: RunPeriod

IDF Example
RunPeriod,
1, !- Begin Month
1, !- Begin Day Of Month
3, !- End Month
31; !- End Day Of Month

or
RunPeriod,
1, !- Begin Month
1, !- Begin Day Of Month
3, !- End Month
31, !- End Day Of Month
Tuesday, !- Day of Week for Start Day
Yes, Yes, Yes, Yes, Yes; !- Special Weather File Flags
39
 Keyword: Run Control

IDD Description (shortened)

RUN CONTROL,
A1, \field Do the zone sizing calculation
A2, \field Do the system sizing calculation
A3, \field Do the plant sizing calculation
A4, \field Do the design day simulations
A5; \field Do the weather file simulation

Purpose: overall control of what the

user wants EnergyPlus to simulate
(design days and/or weather file runs,
perform auto-sizing)
40
 Keyword: Run Control
Keyword
IDD Description (detailed) note that
RUN CONTROL, there IS a
\unique-object space
A1, \field Do the zone sizing calculation between the
\type choice two words
\key Yes
\key No
\default No
A2, \field Do the system sizing calculation These
\type choice will be
\key Yes discussed
\key No later in
\default No the
A3, \field Do the plant sizing calculation semester
\type choice
\key Yes
\key No
41
\default No
 Keyword: Run Control

IDD Description (detailed, continued)

A4, \field Do the design day simulations
\type choice
\key Yes Choices for both fields are
\key No simply yes or no
\default Yes
A5; \field Do the weather file simulation
\type choice
\key Yes Fields define whether or not to
\key No simulate design days (defined by the
\default Yes DesignDay input line) or an attached
weather file (see RunPeriod input
line)

42
 Keyword Example: Run
Control
IDF Example
RUN CONTROL, No, No, No, No, Yes;

or
RUN CONTROL,
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

43
Keyword: GroundTemperatures

IDD Description (shortened)

GroundTemperatures,
N1 , \field January Ground Temperature
N2 , \field February Ground Temperature
N3 , \field March Ground Temperature
. . . etc . . .
N12; \field December Ground Temperature

Purpose: to set the ground temperatures

experienced at the building location (impact
on places where the ground is in contact with
the building)

44
Keyword: GroundTemperatures

IDD Description (detailed)

GroundTemperatures, Keywordnote all one word
\unique-object
\min-fields 12 12 values, one per month
N1 , \field January Ground Temperature
\required-field Repeated for
\units C each month of
\type real the year
\default 13

Temperatures in Celsius; note

that these are temperatures at
the outside surface not deep
ground temperatures

45
 Keyword Example:
GroundTemperatures
IDF Example
GroundTemperatures, 20.03, 20.03, 20.13, 20.30, 20.43, 20.52,
or 20.62, 20.77, 20.78, 20.55, 20.44, 20.20;
GroundTemperatures,
20.03, !- January Ground Temperature {C}
20.03, !- February Ground Temperature {C}
20.13, !- March Ground Temperature {C}
20.30, !- April Ground Temperature {C}
20.43, !- May Ground Temperature {C}
20.52, !- June Ground Temperature {C}
20.62, !- July Ground Temperature {C}
20.77, !- August Ground Temperature {C}
20.78, !- September Ground Temperature {C}
20.55, !- October Ground Temperature {C}
20.44, !- November Ground Temperature {C}
20.20; !- December Ground Temperature {C}
46
Keyword: GroundReflectances

IDD Description (shortened)

GroundReflectances,
N1 , \field January Ground Reflectance
N2 , \field February Ground Reflectance
N3 , \field March Ground Reflectance
. . . etc . . .
N12; \field December Ground Reflectance

Purpose: to set the reflectance of the

ground surrounding the building (affects
radiation incident on building surfaces)

47
Keyword: GroundReflectances

IDD Description (detailed)

GroundReflectances, Keywordnote all one word
\unique-object
\min-fields 12 12 values, one per month
N1 , \field January Ground Reflectance
\default 0.2
\type real Repeated for
\minimum 0.0 each month of
\maximum 1.0 the year
\units dimensionless

Note: values for reflectance are

highly dependent on the type of
ground cover around the
buildinggrass, dirt, concrete,
asphalt, etc.
48
 Keyword Example:
GroundReflectances
IDF Example
GroundReflectances, 0.2, 0.2, 0.2, 0.2, 0.2, 0.2,
or 0.2, 0.2, 0.2, 0.2, 0.2, 0.2;
GroundReflectances,
0.2, !- January Ground Reflectance
0.2, !- February Ground Reflectance
0.2, !- March Ground Reflectance
0.2, !- April Ground Reflectance
0.2, !- May Ground Reflectance
0.2, !- June Ground Reflectance
0.2, !- July Ground Reflectance
0.2, !- August Ground Reflectance
0.2, !- September Ground Reflectance
0.2, !- October Ground Reflectance
0.2, !- November Ground Reflectance
0.2; !- December Ground Reflectance
49
 Keyword: Snow Ground
Reflectance Modifiers
IDD Description (shortened)
Snow Ground Reflectance Modifiers,
N1, \field Ground Reflected Solar Modifier
\minimum 0.0
\default 1.0
N2; \field Daylighting Ground Reflected Solar Modifier
\minimum 0.0
\default 1.0

Purpose: to account for the presence of snow

and how that impacts the ground reflectance
(weather files will indicate whether or not
there is snow on the ground)

50
 Keyword: Snow Ground
Reflectance Modifiers
IDD Description (detailed)
Snow Ground Reflectance Modifiers,
N1, \field Ground Reflected Solar Modifier
\minimum 0.0
\default 1.0
\note Value for modifying the "normal" ground reflectance
\note when Snow is on ground when calculating the
\note "Ground Reflected Solar Radiation Value a value of
\note 1.0 here uses the "normal" ground reflectance
\note Ground Reflected Solar = (BeamSolar*CosSunZenith
\note + DiffuseSolar)*GroundReflectance
\note This would be further modified by the Snow Ground
\note Reflectance Modifier when Snow was on the ground
\note When Snow on ground, effective GroundReflectance is
\note GroundReflectance*"Ground Reflectance Snow Modifier"
\note Ground Reflectance achieved in this manner will be
51
\note restricted to [0.0,1.0]
 Keyword: Snow Ground
Reflectance Modifiers
IDD Description (detailed)
N2; \field Daylighting Ground Reflected Solar Modifier
\minimum 0.0
\default 1.0
\note Value for modifying the "normal daylighting
\note ground reflectance when Snow is on ground
\note When calculating the "Ground Reflected Solar
\note Radiation Value a value of 1.0 here uses the
\note normal ground reflectance
\note Ground Reflected Solar = (BeamSolar*CosSunZenith
\note + DiffuseSolar)*GroundReflectance
\note This would be further modified by the Snow Ground
\note Reflectance Modifier when Snow was on the ground
\note When Snow on ground, effective GroundReflectance is
\note GroundReflectance*"Ground Reflectance Snow Modifier"
\note Ground Reflectance achieved in this manner will be
52
\note restricted to [0.0,1.0]
Keyword Example: Snow Ground
Reflectance Modifiers
IDF Example
Snow Ground Reflectance Modifiers, 1.5, 2.0;
or
Snow Ground Reflectance Modifiers,
1.5, !- Ground Reflected Solar Modifier
2.0; !- Daylighting Ground Reflected Solar Modifier

53
 Summary
Location and exterior thermal environment
play a critical role in determine the thermal
loads/energy consumption of a building
Many input keywords in EnergyPlus control
what is being simulated
For example: Version, Run Control, Location,
DesignDay, SpecialDayPeriod, RunPeriod,
DaylightSavingPeriod, GroundTemperature,
GroundReflectance, Snow Ground Reflectance
Modifiers
EnergyPlus flexibility also results in user
responsibility (having to define various
parameters in the input file)
54