DesignBuilder v7.3 LEED-ASHRAE901 Modelling Guide
DesignBuilder v7.3 LEED-ASHRAE901 Modelling Guide
DesignBuilder v7.3
July 2024
DesignBuilder © No part of the manual is to be copied or reproduced in any form without the express agreement
of DesignBuilder Software Ltd
Contents
6.2 Set up baseline HVAC systems using baseline HVAC wizard ...................................................... 39
6.2.1 Run the Baseline HVAC wizard ...............................................................................................................40
6.2.2 Fine tuning (manual adjustment) ...........................................................................................................52
As DesignBuilder only currently uses ASHRAE 90.1 App G PRM for LEED models, unless otherwise stated, the
terms ASHRAE 90.1 App G PRM (or in short App G PRM) or simply ASHRAE 90.1 mean the same in this
document.
This LEED Modelling Guide generally focuses only on LEED-specific functionality. It is assumed that the modeller
has sufficient experience and knowledge of DesignBuilder regarding creation of the actual (Proposed) building
model, which is typically created prior to the baseline building. More general (non-LEED specific) DesignBuilder
information can be accessed from the DesignBuilder Help system.
The DesignBuilder App G PRM modelling tool is tightly integrated into the EnergyPlus modelling environment in
the software. An App G PRM model looks very much like a standard DesignBuilder EnergyPlus model, but it
includes various extra functionality that specifically meet ASHRAE 90.1 App G PRM requirements.
To use DesignBuilder LEED you will need the following licence modules:
• LEED
• Simulation,
• HVAC and
• Cost (for utility tariff).
These can be purchased most conveniently and cost-effectively through the Engineering Essentials package.
By following ASHRAE 90.1 App G PRM definitions, the DesignBuilder LEED tool generates data for LEED EAc1
and earns points based on energy cost saving from the proposed building over the baseline building. The baseline
building can be automatically generated from the proposed building using two simple wizards.
• LEED approved EnergyPlus simulation engine (refer to Clause G2.2 Simulation Program in ASHRAE
90.1 Standard 2007).
• The tool meets the Appendix G Performance Rating Method requirements of the ASHRAE 90.1 2007’
2010, 2013 or 2016 standards.
• A wide range of pre-configured templates and libraries to speed up model definition.
• To automate the baseline building generation the proposed model should be created first. The baseline
building can be created first if required, but this is not the recommended workflow.
• DesignBuilder LEED includes two separate wizards. One baseline building wizard that deals with
geometry and other non-HVAC related data, and a baseline HVAC wizard that sets up the HVAC system.
Some further manual checks and changes to the baseline HVAC system are usually required.
• The proposed and baseline building models are stored and manipulated in a single project file, which
provides an easy data check and more secure model quality.
• In cases where four rotated baseline building simulations are required, they are run simultaneously in
parallel using DesignBuilder’s Simulation Manager to speed up the simulations.
• DesignBuilder provides an output comparing proposed and aggregated baseline building results.
The usual workflow is to create the proposed building model first and then automatically create the corresponding
baseline model from that. In this case, the two models are contained in the same dsb file. However, for cases
where, for any reason, it is more convenient to use separate files for the two models DesignBuilder’s LEED tool
allows this. Figure 1 also shows that the proposed building can be created either from scratch or converted from
a non-ASHRAE 90.1 model.
This document describes the step-by-step process of modelling a full LEED project from proposed to baseline
within the same dsb file. It does not cover the process used for modelling the baseline and proposed buildings in
separate files.
Alternatively, if you already have a model that you wish to convert to an ASHRAE 90.1 model, you can change
the energy code for the model by editing data at site level. DesignBuilder currently supports the “ASHRAE 90.1-
2007”, “ASHRAE 90.1-2010”, “ASHRAE 90.1-2013” and “ASHRAE 90.1-2016” codes and the appropriate
selection can be made in an existing model by changing the “Mandatory energy code” on the “Region” tab at site
Figure 2 ASHRAE 90.1 energy code to enable App G PRM model functionality
Figure 3 Options for choosing Units and currency (as well as interface language)
The climate zone setting in the model will affect the constructions and glazing selected when the baseline building
is created using the baseline building wizard. It can also affect the selection of details in the baseline HVAC
system. The ASHRAE climate zone shown on the interface is preloaded from the location template (Figure 6).
Figure 7 A confirmation message is shown when overriding the default climate zone
Note: Two new climate zones (0A and 0B) have been added to ASHRAE 90.1 2016, where 0A is for extremely
hot humid climate while 0B extremely hot dry climate.
Although a baseline building could be modeled first, DesignBuilder recommends creating the proposed building
first and then using the built-in wizards to generate the baseline building. This offers a much faster and more
automated approach than manually creating the baseline model.
When the “ASHRAE 90.1” type is set DesignBuilder will load some appropriate model data settings such as
detailed HVAC (a mandatory requirement for App G PRM models in DesignBuilder) and 6 time steps per hour for
simulating the proposed and baseline building models.
If you chose to use the “External measurements” template for example you will find that the baseline building
surface areas, floor area and zone volumes are different after loading the baseline constructions because these
generally have a different thickness to those selected for the proposed building. If you choose to use a geometry
convention other than “ASHRAE 90.1” please refer to the Geometry conventions information in the Program Help
and ensure you fully understand the implications of any alternative setting.
Figure 10 ASHRAE 62.1 activity templates ready for App G PRM use
The “ASHRAE 90.1 building type” defines whether the building is 1-Proposed or 2-Baseline. DesignBuilder does
not recommend switching between ASHRAE 90.1 building types unless you understand the risk and there is a
need to do so.
The “Primary building condition category” can be either 1-Non-residential or 2-Residential, which is used to define
primary building use. This is especially useful when modelling mixed use buildings because it controls
constructions, HVAC selections etc according to its condition category.
The “Heating source” defines the building’s heating use as either electric or fossil fuel. This will affect the baseline
model HVAC system selection (Table G3.1.1A and Table G3.1.1B in ASHRAE 90.1 Standard).
The “ASHRAE 90.1 lighting category”, “ASHRAE 90.1 floor definition” and “ASHRAE 90.1 building area type”
inputs will be discussed in more detail below.
DesignBuilder version 7.3 supports LEED v4.1 Minimum Energy Performance Calculator (MEPC) generation, and
this is only applicable for ASHRAE 90.1 – 2016. Figure 11 (c) indicates an additional “LEED submittal version”
dropdown list when ASHRAE 90.1 – 2016 energy code is selected at the site level.
4.3.2.2 ASHRAE 90.1 settings on Activity tab at block and zone levels
The “ASHRAE 90.1 lighting category” and “ASHRAE 90.1 floor definition” inputs are available at block and zone
levels. (Figure 12 ASHRAE 90.1 settings at zone level(a) and (b)). The “ASHRAE 90.1 building area type” item of
2013 and 2016 energy code is also shown at block and zone levels (Figure 12 ASHRAE 90.1 settings at zone
level(b)).
Additional inputs at block/zone levels define whether the current zone is conditioned, unconditioned or semi-
heated (Figure 12). You must also define whether the zone is conditioned, and set the "Space condition category”..
The non-residential or residential category denotes whether or not the zone falls under the building level primary
building condition category. If it is the same at both zone and building level, the zone will fall into the primary
condition category, otherwise the zone will fall into the non-predominant condition category.
The building area types shown in Figure 12 (b) will be further discussed in section 4.3.2.5 ASHRAE 90.1 building
area type.
Figure 14 Lighting power density allowances using space-by-space method in ASHRAE 90.1 -2016 (IP Edition)
Users must ensure that the correct “ASHRAE 90.1 lighting category” is selected (Figure 15). If you are not able
to find a perfectly matching record in the list, you could choose one that is closest to your application.
The ASHRAE 90.1 floors will be used in the HVAC wizard discussed in section 06.2.1.4 Systems #5 – #8 – each
floor to have a separate HVAC system later.
Figure 16 Baseline building window to wall ratio (WWR) defined by Building Area Types
DesignBuilder provides an option on the Activity tab to allow any of these building area types be selected (Figure
17).
In ASHRAE 90.1 2013 and 2016, for building area types included in Table G3.1.1-1 (Figure 16), vertical
fenestration areas for new buildings and additions shall be as defined in Table G3.1.1-1 based on the area of
gross above-grade walls that separate conditioned spaces and semi-heated spaces from the exterior. Where a
building has multiple building area types, each type shall use the values in the table.
For building areas not shown in the table, vertical fenestration areas for new buildings and additions shall follow
the rule as per ASHRAE 90.1 2007 or 2010, i.e. they equal window to wall ratios in the proposed design or 40%
of gross above-grade wall area, whichever is smaller.
The DesignBuilder ASHRAE 90.1 building wizard handles this new feature for ASHRAE 90.1 2013 or 2016 models.
The use of ASHRAE 90.1 building area type will be further explained in Section 6.1.2.3 Baseline building vertical
fenestration on building area types.
Computers and office equipment always use electricity as the fuel source, hence there is not a fuel type to choose
from and subsequently there is not an end-use subcategory applied. They require gain density and associated
operational schedule to be entered (Figure 18).
Miscellaneous, Catering and Process gains allow “Fans – Parking garage” and “Elevators and escalators” (under
Miscellaneous load definition), “Cooking” (under Catering load definition) and “Industrial process” (under Process
load definition) to define the end-use subcategory (Figure 19) for the input. These loads are reported in the LEED
summary report after the simulation.
When a site is created or when the climate zone is changed, the appropriate corresponding baseline construction
and glazing templates are generated in DesignBuilder so that they can be assigned to the model when the
baseline building is created. The ASHRAE 90.1 templates in the model could be copied and edited for use in the
proposed building where appropriate.
A list of baseline wall constructions for climate zone 5 (CZ5) is shown in Figure 21 as an example.
The terminology used in the ASHRAE 90.1 constructions list gives the climate zone, the description of the
construction, insulation level(s) in IP units and the U-value in IP units and in brackets the values in SI units. For
example, the construction:
indicates a non-residential steel framed wall for climate zone 4 (CZ4) with internal insulation levels of two layers
of minimum 13.1 and 7.4 ft2-°F/(Btu/hr) in IP units (2.3 and 1.3 m2-K/W in SI units) and a U-value of 0.064 Btu/hr-
ft2-°F in IP units (0.365 W/m2-K in SI units).
When running Heating or Cooling design calculations, if the “FCFactorMethod ground temperatures source data”
at site level has “1-Hourly weather file” selected, the calculations will use the undisturbed ground temperature
data contained within the weather file. This will be automatically downloaded (if not yet in your weather file folder
on your computer) prior to the calculations. If “2-Model data” is selected, the Heating and Cooling design
calculations do not require the weather file (Figure 24).
Note: The Simple glazing definition type (WindowMaterial:SimpleGlazingSystem object in EnergyPlus) is used to
model glazing in the baseline building model. The U-factor and other input values for this simple glazing type
already include the effect of the frame, so the “Has a frame/dividers?” checkbox under the “Frame and Dividers”
header on “Openings” tab should be left unchecked in the baseline building model.
4.3.5 Lighting
Lighting including lighting power density (LPD) should be input from the actual lighting or as designed for each
zone (Figure 26).
For modelling the proposed building, DesignBuilder provides a set of predefined lighting templates (these are the
ones used in the baseline building when it is generated) that can be used directly or copied and edited as required
(Figure 27).
Table G3.1-6 in ASHRAE 90.1 Standard indicates that credit may be taken for the use of automatic controls for
daylight utilization. In DesignBuilder, automatic daylight control can be modeled in the proposed building using
the Lighting Control settings (Figure 28).
EnergyPlus will report this exterior lighting consumption in output summary tables. Detailed input of exterior
lighting zone selection and the lighting definition on tradable/nontradable surfaces are not allowed. Please see
DesignBuilder LEED v4.1 Data Reporting User Guide for more details for how to report the exterior lighting in
LEED MEPC.
As a minimum, data on the Tariff tab (Figure 31) and Charge tab (Figure 32) should be set up for utility cost
calculations to work. On the Tariff tab, users need to input general tariff settings, such as the output meter used,
schedules for defining seasonal or time of day charges, monthly service charge and minimum monthly charge etc.
The charge tab provides options to input simple or complex charges from the utility company (Figure 32). A
maximum of 10 charges can be input as a combination of either the simple charge format or the block charge
format, which provides more complex charge patterns. The charge can apply on both energy and demand
readings depending on the source variable to be used.
ASHRAE 90.1 indicates that annual energy costs shall be determined using either actual rates for purchased
energy or state average energy prices published by DOE’s Energy Information Administration (EIA) for
commercial building customers. However, rates from different sources may not be mixed in the same project.
For example, a graphical layout of a “VAV Reheat, Water-cooled Chiller” system is illustrated in Figure 34, which
includes a chilled water loop, a condenser loop a hot water loop, and an air loop that contains an air handling unit
(AHU).
To set up the HVAC system exactly as required, including service hot water or SHW systems (called domestic
hot water or DHW systems in DesignBuilder), users need to edit the Loop and component dialogs to define the
performance characteristics and controls. Users can modify a pre-defined template to represent their design
system or create a system from scratch by adding loops and components using the HVAC tools in DesignBuilder
(Figure 35 and Figure 36).
4.4.2 Variety of pre-configured HVAC systems including GSHP, VRF and Generic Unitary
System
DesignBuilder Detailed HVAC template database contains a wide range of predefined HVAC systems (Figure 33)
that are ready to be loaded into the model. In addition to common fan coil unit system and constant air or variable
air systems, water-to-air and air-to-water heat pump systems are on the HVAC template list. Also, ground source
heat pump (GSHP) systems and variable refrigerant flow (VRF) systems can be modeled in DesignBuilder, where
the templates based on the typical use of these components are also pre-defined, which helps set up proposed
HVAC systems quickly (Figure 37 and Figure 38 illustrate the layout of these two systems respectively as
examples).
Although a number of GSHP and VRF template data sets from different manufacturers are already incorporated
into the GSHP and VRF database to speed up data entry, DesignBuilder also offers GSHP and VRF performance
curve tools to help you generate performance curves for systems such as VRF and GSHP from manufacturer’s
catalogue data, where available.
If VRF is selected as part of the HVAC system for the proposed building, you need to use manufacturer
performance data, if it is available, to derive the performance curves for the actual VRF unit (they are normally
hard sized) rather than EnergyPlus example VRF model curves. In DesignBuilder version 7.3, you can also find
a generic air loop unitary system (see Figure 39), which is a composite object that can accommodate all fan and
coil types. It is ready to model ASHRAE 90.1 baseline system #11, which is designated to model the computer
room HVAC system.
Since the proposed building is the modelling counterpart of the actual building that is to be certified, where the
HVAC systems are already adopted or designated, the proposed model inputs should be consistent with the
design documents. In addition to that, the modeler should apply 90.1 Standard mandatory provisions to the
modeled HVAC systems and components.
System #11 is preconfigured in DesignBuilder as a Detailed HVAC template. As this is not included in the Baseline
HVAC System Types defined in Table G3.1.1-3, you can load it to the model where the computer room meets
one of the above room cooling load thresholds.
There are two different system types #11 differentiated by the heating source:
When using one of these systems you will need to manually apply some specific configuration settings following
requirements in G3.1.2.6.1 Computer Room Economizers, G3.1.3.9 Chilled-Water Supply Temperature Reset
Exception 1, G3.1.3.10 Chilled-Water Pumps and G3.1.3.11 Heat Rejection.
Click “Yes” in response to the pop up message box (Figure 41) to confirm that you understand the impact of the
conversion and are happy to continue, otherwise click “No” to keep the old energy code without converting.
After the conversion the remaining steps of LEED modelling for the proposed building are the same as described
in section 4. Create an ASHRAE 90.1 Project – Proposed Building above.
When viewing the proposed building at building level the “Create Baseline Building” icon is visible in the
toolbar (Figure 42).
ASHRAE 90.1 covers buildings except low-rise residential buildings, e.g. dwellings with less than 4 floors. To
ensure the modeled building fulfils ASHRAE 90.1 Standard definitions, DesignBuilder issues a warning message
for low-rise residential buildings before the baseline building wizard runs (Figure 43). Normally, when this warning
message is displayed, you should click “No” to close the message box and check the model and make any
changes where appropriate. However, this is based on the number of floors estimated by the software. If it differs
from the project designation due to the complexity of accurately defining floor numbers, you can click “Yes” to
continue loading Baseline Building Wizard.
The LEED submittal version is included on the Building Use summary page (see Figure 45 (a)). This data comes
from the definition on Activity tab of the proposed building. ASHRAE 90.1 building area types are also summarised
and displayed on the Fenestration Details page (Figure 45 (b)).
If any of the summary information is incorrect you should cancel the wizard, edit the model and then re-run the
wizard.
Of the information displayed on the wizard, perhaps the most important is the summary of the window to wall ratio
and skylight to roof area ratio of the proposed building. This indicates the glazing ratios that will be used for the
• Vertical fenestration areas for new buildings and additions shall equal that in the proposed design or 40%
of gross above-grade wall area, whichever is smaller, and shall be distributed on each face of the building
in the same proportions as in the proposed design.
• Skylight area shall be equal to that in the proposed building design or 5% of the gross roof area that is
part of the building envelope, whichever is smaller. If the skylight area of the proposed building design is
greater than 5% of the gross roof area, baseline skylight area shall be decreased by an identical
percentage in all roof components in which skylights are located to reach the 5% skylight-to-roof ratio.
Skylight orientation and tilt shall be the same as in the proposed building design.
• If ASHRAE 90.1 building area types are used in the model (for ASHRAE 90.1 2013 and 2016 only), the
WWR will follow the definition in section 4.3.2.5 ASHRAE 90.1 building area type.
6.1.2.2 Override input for window to wall area ratio and skylight to roof area ratio
In order to provide some flexibility for the input of window to wall ratio (WWR) or skylight to roof area ratio (SRR),
for example to meet Canadian NECB project requirements, it is possible to hard-set the WWR or SRR in the
LEED v4.0 Baseline Building wizard (Figure 46). If you are intending to make such a change you must ensure
that it is justified and you understand the consequences before doing so.
Figure 46 Window to wall area ratio and skylight to roof area ratio are allowed to change
If all data on the wizard is correct, click the “Finish” button (on final page) and the software will generate a baseline
building so that both buildings are displayed in the model side by side (Figure 47).
• When windows on a surface cannot be scaled up to the required size due to an obstruction, such as a door
or a vent, a warning is issued that says “One or more windows could not be scaled to the required size. You
should redraw the windows on the proposed model so when scaled they fit on the surface or, if necessary,
manually redraw the baseline windows to be the correct area”. DesignBuilder does not apply window scaling
up or apply default facade method in this case, so the baseline surface layout stays the same as in the
proposed building.
• When windows on a surface that contains no other opening types cannot be scaled up to the required size as
they would need to overlap an edge, a note is issued to indicate the default facade method has been applied
to this surface to generate appropriately sized windows.
• In the case of Zone 1 shown in Figure 48, only one wall contains windows, so when applying window scaling
following the ASHRAE 90.1 WWR rules mentioned above, this wall would need the WWR to exceed 100%
which of course is not possible.
In this case, DesignBuilder displays a message that says “The vertical fenestration area required on one
surface in this zone exceeds the gross above-grade wall area on that Surface. You may need to manually
set this surface to 100% fenestration and increase the vertical fenestration area on other surfaces in
proportion to the gross above-grade wall area of those surfaces such that the total baseline zone vertical
fenestration area is equal to that calculated following Table G3.1.1-1”.
This requires you to manually increase the windows to occupy the whole surface of this wall and distribute
the remaining opening area in an equal percentage across the other remaining walls, even if they did not
have windows originally. This requirement will appear in ASHRAE 90.1 Standard 2022 version.
Depending on the proposed building details, various changes in the baseline building relative to the proposed
building will generally be seen:
• Constructions/glazing will be assigned constructions with names starting CZ# (# denotes the climate zone
number) in the construction’s title/name.
Note: If significant changes need to be made to the proposed building after the baseline building has been created,
it usually best to delete the baseline building, edit the proposed building and re-run the baseline generation wizard.
Figure 49 ASHRAE 90.1 settings on activity tab at building level of baseline building
At zone level of the baseline building (Figure 50 below) the data shown is similar to that of the proposed building
(Figure 12).
If the LEED submittal version is “2-LEED v4.1”, i.e. the ASHRAE 90.1 – 2016 energy code is applied, the auto-
assigned constructions will come from the ASHRAE 90.1 Standard 2016 Appendix G Table G3.4 (Figure 52).
Note: Constructions such as internal partitions that are not covered by ASHRAE 90.1 are modeled as per the
proposed building.
ASHRAE 90.1 defines slab-on-grade floor, which needs to use F-factor construction, as the portion of a slab floor
of the building envelope that is in contact with the ground and that is either above grade or is slightly below the
grade (less than or equal to 24 inch, or 600 mm, below the final elevation of the nearest exterior grade). The F-
factor represents the heat transfer through the floor, induced by a unit temperature difference between the outside
and inside air temperature per linear length of the exposed perimeter of the floor. F-Factor constructions should
only be selected for Ground adjacent surfaces with exposed perimeter greater than zero.
Basement ground floors were introduced into DesignBuilder for ASHRAE 90.1 models only to distinguish floors
from slab-on-grade floors. They are normally outside the scope of slab-on-grade floor definition described in
ASHRAE 90.1 and are not regulated by the 90.1 Standard. The baseline model takes the same construction for
basement ground floors as that used in the proposed model, where a standard layered floor construction is
normally used.
During the IDF generation process, if a ground floor surface is assigned an F-Factor ground floor construction,
but its exposed perimeter is calculated as zero, the software will use the currently selected Basement ground floor
construction instead. Furthermore, in this case, if the Basement ground floor has an F-Factor construction selected,
a message is displayed advising the use of a layered ground floor construction instead of F-Factor construction
(Figure 53).
Figure 53 DesignBuilder error message when an F-Factor ground floor has zero exposed perimeter
As for opaque constructions, if the LEED submittal version is “2-LEED v4.1”, i.e. ASHRAE 90.1 – 2016 energy
code is applied, the auto-assigned glazing constructions will come from ASHRAE 90.1 Standard 2016 Appendix
G Table G3.4 (Figure 55).
Figure 55 Baseline glazing consistent to ASHRAE 90.1 2016 Appendix G Table G3.4
For the projects located in climate zone 3, ASHRAE 90.1 2016 distinguishes baseline glazing for climate zone
suffix A, B and C separately (Figure 56 and Figure 57).
Figure 56 Climate Zone 3 A and B baseline glazing for ASHRAE 90.1 2016
Figure 58 Lighting template and lighting power density (LPD) for 2010 version
However, for ASHRAE 90.1 2016 version, the auto-assigned lighting template is from Appendix Table G3.7
(Figure 59).
Figure 59 Lighting template and lighting power density (LPD) for 2016 version
DesignBuilder includes templates for all baseline HVAC systems, and the Baseline HVAC wizard helps you
choose the appropriate HVAC template for primary conditioned zones. However, for non-predominant zones, you
should select and add the system manually.
At the top of the wizard, DesignBuilder recommends an HVAC system for use in the baseline building model. The
recommendation is based on the information shown on this page. If system #7 or #8 is recommended, the wizard
will show a cooling design calculation section if the cooling design calculation has not been run prior to calling the
baseline HVAC wizard. The total peak cooling load results from the cooling design calculation will define how
many chillers are needed for system #7 or #8 according to ASHRAE 90.1 2010 Appendix G Table G3.1.3.7. The
Next button is greyed out so that you cannot continue until the cooling design calculation has been run.
The number of floors shown on the page is an estimated figure based on the calculation using total building height
dividing by a calculated average floor height from modeled building. This field is editable so you can change it to
a number that matches the building design specifications of the project. Be aware that changes to this value will
sometimes result in a change of HVAC system type.
The recommended HVAC system will preload and be previewed on the second wizard page (Figure 63). You can
change the baseline HVAC system manually here should you need to.
The “Use as primary HVAC system” option on the baseline HVAC wizard is useful in helping process data for the
DesignBuilder LEED MEPC reporting tool if you plan to use this tool after the simulations. The MEPC tool is
described in a separate user guide which can be assessed online from a link in Section 8.3 Data reporting tool.
After running the Baseline HVAC wizard, this primary HVAC system selection is stored and displayed on HVAC
tab at building level (Figure 64).
Figure 64 Building level HVAC tab stores Baseline primary HVAC system information
Click the Finish button to close the wizard and load the HVAC system to the layout screen. The behavior of the
“Load HVAC Template” wizard depends on the baseline HVAC system selected, as described below.
Figure 66 ASHRAE 90.1 2010 baseline HVAC system types are decided by building type and fuel type
From ASHRAE 90.1 2013, the primary baseline HVAC system is decided by the building type and its application
together with the climate zone where the project is located. The details are shown in Figure 67 below (ASHRAE
Figure 67 ASHRAE 90.1 2016 baseline HVAC system types are decided by building type and climate zone
When system #3 has been selected as the baseline HVAC system, the example screenshot below shows four
zones selected to be served by this system on the zones page (Figure 68).
For option “3-User specified floor definition”, please refer to section 4.3.2.4 ASHRAE 90.1 floor definition for how
user-specified floors are defined.
Using the example shown in Figure 70, the HVAC system will be generated on the layout screen with three HVAC
zone groups, each containing four zones under each floor definition. The number of chillers and boilers will be
correctly set (Figure 71) based on ASHRAE 90.1 App G Sections G3.1.3.2 and G3.1.3.7. The template is currently
configured with a maximum of three chillers. If more than three chillers are required for large buildings, the extra
chiller(s) can be added manually by navigating to the chilled water loop supply side.
Note for Systems #9 and #10: For ASHRAE 90.1 2010, systems #9 and #10 should be applied to single zones,
while in ASHRAE 90.1 2013 and 2016, these two systems should apply to each floor. The Baseline HVAC wizard
implements this change so the systems can be loaded into an appropriate arrangement based on the version of
the ASHRAE 90.1 energy code selected.
It is worth noting that the HVAC wizard can be run multiple times to override the existing system or to add
additional HVAC systems, such as non-predominant HVAC systems, service hot water (SHW) a.k.a. domestic hot
water (DHW) systems etc.
Note: Normally, you need to enable the “Override template defaults” option, which is shown as the second
checkbox in Figure 65 and Figure 70 above, and then set the relevant parameter(s) in the wizard pages that follow.
This will be discussed in detail in the following section.
6.2.1.5 Configuration of multiple chillers for systems #7, #8, #11, #12 and #13
ASHRAE 90.1 App G PRM Heat Rejection section states: “Each chiller shall be modeled with separate condenser
water and chilled-water pumps interlocked to operate with the associated chiller”. The correct interpretation of this
section is to model one cooling tower (one cell per tower) for each baseline building chiller. Each baseline building
chiller has its own condenser water pump that operates with the chiller.
Figure 72 below, shows how, when two chillers are needed for a baseline HVAC system, the second condenser
loop (highlighted in red) can be added manually, and each chiller is connected to a separate condenser loop.
Note: Any further modifications that need to be made to the baseline HVAC system can be made manually to
system components after the selected system has been loaded to the model.
Figure 74 shows how the default input to the air handling unit can be changed, if required, by ASHRAE 90.1
Standard definitions.
The system fan power defined in ASHRAE 90.1 Standard Appendix G (in short App G) G3.1.2.9 together with
Table G3.1.2.9 is already included in the default normalized fan pressure rise input setting in DesignBuilder. This
is equivalent to the fan power to air flow rate ratio. However, if the fan pressure drop adjustments defined in
ASHRAE 90.1 Standard section 6.5.3.1.1 are to be considered, then users need to calculate a revised fan
pressure rise and enter it here.
For detailed baseline fan pressure rise explanation and calculation, see Appendix B.
For ASHRAE 90.1 2007 and 2010, outdoor air economizers must be included in baseline HVAC Systems #3 to
#8 if the climate zone meets the conditions specified in App G Table G3.1.2.6A. Baseline HVAC systems #1 or
#2 do not require an outdoor air economizer. For ASHRAE 90.1 2013, similar requirements are defined in Tables
G3.1.2.7 and G3.1.2.8, while in ASHRAE 90.1 2016 Tables G3.1.2.6 and G3.1.2.7 define the requirements. The
requirement for the economizer and high-limit shutoff temperatures are automatically set in the software.
Users can make changes here if they don’t agree with the default settings proposed by the wizard.
App G G3.1.2.10 section requires a complex check (normally based on the known design supply air capacity) to
decide whether or not the exhaust air energy recovery is needed.
Note: DesignBuilder sets heat recovery to be on with an effectiveness of 0.5 by default. However a manual check
of these settings is required and manual changes are often needed.
The hot water system default settings are shown in Figure 75 below.
Hot water pump power for baseline HVAC systems #1, #5 and #7 (other systems do not have hot water loops), is
defined in App G G3.1.3.5, which requires baseline building design hot-water pump power to be 19 W/gpm. This
figure is included into DesignBuilder pump head input which represents the pump power to water flow rate ratio.
Similar to hot water systems, the chilled water system pump head includes consideration of the 22W/gpm for
baseline building design pump power required by App G G3.1.3.10 (Figure 76).
Likewise, the condenser pump head includes consideration of the 19W/gpm for baseline building design
condenser-water pump power defined in App G G3.1.3.11 (Figure 77).
The final page of the wizard allows a simple HVAC template to be set (Figure 78). This updates the data on the
HVAC tab at zone level for consistency with the Detailed HVAC system most recently loaded for that zone. This
is especially important for running cooling or heating design calculations.
Note: After the HVAC system has been loaded for the baseline building, further changes can be made by manually
editing data on HVAC loops and components.
• You should check that the prescriptive requirements have been met in the ASHRAE 90.1 proposed model,
such as checking the equipment minimum efficiencies required by Appendix G clause G3.1.2.1, together
with section 6.4 of ASHRAE 90.1 Standard, which references Tables 6.8.1A through 6.8.1K that define
the minimum equipment efficiency requirements. For DX coil efficiency input, see Appendix A.
• Check whether preheat coils are required in the baseline HVAC system based on Clause G3.1.2.3.
• Check whether the baseline HVAC system needs to enable exhaust air energy recovery following the
definitions of G3.1.2.10. Then make appropriate settings on the air handling unit (AHU) dialog “Outdoor
Air System” tab.
• Set the baseline HVAC hot water pump type to either variable speed or constant speed per Appendix G
section G3.1.3.5. Likewise, set the chilled water pump type to either variable or constant speed per section
G3.1.3.10.
• If the baseline HVAC system is either #6 or #8, size the fans in parallel VAV fan-powered boxes properly
as per section G3.1.3.14 (see Appendix C for more details).
• If applicable, set the baseline chiller condenser heat recovery per section 6.5.6.2.1.
While we consider these to be the main manual interventions that are likely to be required, you should check the
whole HVAC system to ensure it fully meets ASHRAE 90.1 requirements.
DesignBuilder advises running the first simulation for the Proposed building level to generate those results, then
selecting the Baseline building model to run the 4 automated baseline building simulations, or a single simulation
if the baseline model meets the criteria of the exception (see the note below).
Note: For ASHRAE 90.1 2010 and later, there is an exemption that allows the baseline simulations to be run
without rotation if certain criteria for window-to-wall ratios are met. This exemption is handled automatically by
DesignBuilder (see Figure 80).
The Simulation Manager allows the four rotated baseline buildings (if they are needed) to be run simultaneously
in parallel and fully automates that process.
• LEED Summary
• Annual Building Utility Performance Summary (ABUPS)
The other non-essential output options can be checked if required when additional data is required, however you
should leave these unchecked if you do not require this data:
Four different rotated baseline buildings have a suffix related to each of their output results, i.e. _B000, _B090,
_B180 and _B270 that indicate the baseline building has been rotated for 0°, 90°, 180° and 270° respectively
(Figure 84), while proposed building results are differentiated with a suffix of _p000.
You must also undertake appropriate quality control checks prior to running the final proposed and baseline
building simulations for ASHRAE 90.1 purposes. As a minimum, we advise that you check all model data inputs
then run shorter test simulations to check key sub-hourly results. For example, run summer and winter design
week simulations to check cooling and heating plant operation, and swing season weeks to check whether
controls that should prevent inappropriate simultaneous heating and cooling are operating correctly. The
DesignBuilder Results Viewer tool can help you to visualize correct operation down to the HVAC system node
level. Then finally run an annual simulation to view annual and monthly results to “sanity-check” key energy
consumption values and unmet load hours against appropriate metrics.
The LEED-specific summary report outputs described above should be reviewed. Examples of these are shown
in Tables 1, 2 and 3 below. DesignBuilder results can also be displayed in “Grid” form and exported to a
spreadsheet in .csv format for further analysis if required.
LEED EAp2-4/5 (Table 1), EAp2-6 (Table 2) and EAp2-7 (Table 3) are examples (from a proposed building
simulation) of how EnergyPlus output summaries fit the LEED EA Prerequisite 2: Minimum Energy Performance
document.
The “Unmet hours” of a building are the summation of the number of hours when the heating or the cooling set
point temperature of a zone is not met either by the HVAC system or by the plant.
• The unmet load hours for both the proposed design and the baseline building design shall not exceed
300 hours per year (of the 8760 hours simulated).
• The unmet load hours for the proposed design shall not exceed the number of unmet load hours for the
baseline building design by more than 50.
If unmet load hours for either the proposed design or baseline building design exceed 300, then the simulated
capacities shall be increased incrementally, and the building with unmet loads shall be re-simulated until the
unmet load hours are reduced to 300 or less. For the proposed building, this means that the construction drawings
may need to be modified and larger equipment specified.
Alternatively in some cases, unmet load hours exceeding these limits may be accepted at the discretion of the
rating authority, provided that sufficient justification is given indicating that the accuracy of the simulation is not
significantly compromised by these unmet loads.
However, in all cases it is important that the unmet load hours of the proposed design do not exceed that of the
baseline design by more than the stated 50 hours. This is to ensure that energy savings are not claimed in the
proposed design by providing a lower level of performance than in the baseline building.
On the energy costs comparison graph, points credited are displayed based on the energy costs saving
percentage shown on the same graph, as well as LEED options selected from Display Options (Figure 88).
LEED v4 and v4.1 Minimum Energy Performance Calculator Reporting - User Guide.
For Baseline HVAC Systems #1 through #6, calculate the minimum COPnfcooling and COPnfheating using the equation
for the applicable performance rating as indicated in Tables 6.8.1-1 through 6.8.1-4. Where a full- and part-load
efficiency rating is provided in Tables 6.8.1-1 through 6.8.1-4.
Where, COPnfcooling and COPnfheating are the packaged HVAC equipment cooling and heating energy efficiency,
respectively, to be used in the baseline building design, which excludes supply fan power, and Q is the AHRI-
rated cooling capacity in Btu/h. EER, SEER, COP, and HSPF shall be at AHRI test conditions.
The above calculation requires a sizing run to the model as the cooling capacity is an input.
A standalone utility is available to help calculate this performance efficiency (COP) input. It includes the
calculations for both cooling and heating coils for baseline systems #1 through #6. The utility can be downloaded
here.
𝑷 𝒉𝒐𝒓𝒔𝒆𝒑𝒐𝒘𝒆𝒓
∆𝑯[𝒊𝒏. 𝒘. 𝒄. ] = [ ] × 𝜼 × 𝟔𝟑𝟓𝟔
𝑸 𝑪𝑭𝑴
Where, P is fan power (horsepower), Q is fan volumetric flow rate (CFM), ∆H is fan pressure rise (in.w.c. that
stands for inch water column) and η is fan total efficiency (-).
B2. Fan pressure rise input for Baseline HVAC systems defined in ASHRAE 90.1 App G
ASHRAE 90.1-2007 states in clause G3.1.2.9 System Fan Power:
As a value for fan efficiency of 0.6 (60%) being used, the fan pressure rise for each baseline HVAC system can
be calculated in the table below.
* These calculations do not take into account the fan pressure drop adjustment which has been defined in Table
6.5.3.1.1A and Table 6.5.3.1.1B that are listed in the appendix.
** PFP fans and motors typically do not have the same efficiency as larger fans and motors, so efficiency value
of 60% may not be very realistic.
This configuration requires a sizing run to the model. To do that, perform a short period (e.g., on typical summer
week) simulation with default Autosize settings for Parallel PIU objects (Figure 90).
Following the definition in G3.1.3.14, obtain the minimum primary air flow fraction, which in this case is 0.3,
determined by the maximum of 0.3 and 0.055615, where 0.055615 is the Design Size Minimum Primary Air
Flow Fraction read from the table in Figure 91 above.
Calculate the maximum secondary air flow rate, in this case, 1.01 * 0.5 = 0.505 m3/s.
Edit to ADU: Parallel PIU dialog gain, input 0.505 for maximum secondary air flow rate, 0.3 for minimum primary
air flow fraction. Input 0.3 for fan on flow fraction as well (Figure 92).
Also, check that the associated fan dialog (Figure 93), has the maximum flow rate of 0.505m3/s.