ApacheHVAC Part A - Overview and Fundamentals

ApacheHVAC User Guide
Part A: Overview and Fundamentals

IES Virtual Environment
Copyright © 2017 Integrated Environmental Solutions Limited. All rights reserved.
No part of the manual is to be copied or reproduced in any form without the express agreement of
Integrated Environmental Solutions Limited.
VE 2016 ApacheHVAC User Guide part A: Overview and fundamentals i

Contents
1 Overview ....................................................................................................................................2
1.1 What is ApacheHVAC and where does it fit within the Virtual Environment? ........................2
1.2 Model Setup for ApacheHVAC..............................................................................................3
1.2.1 ModelIt/Apache Space Types ...................................................................................................................... 3
1.2.2 Return & Supply Air Plenums ....................................................................................................................... 4
1.2.3 HVAC Methodology ..................................................................................................................................... 5
1.2.4 Thermal Templates for Plenums and Voids ................................................................................................. 7
1.2.5 HVAC Zones and Zone Groups ..................................................................................................................... 7
1.3 ApacheHVAC Interface Overview ....................................................................................... 10
1.3.1 Virtual Environment Menu Bar .................................................................................................................. 10
1.3.2 ApacheHVAC Menu Bar ............................................................................................................................. 10
1.3.3 ApacheHVAC Toolbars ............................................................................................................................... 10
1.3.4 View Toolbar .............................................................................................................................................. 12
1.3.5 Model Workspace ...................................................................................................................................... 13
1.3.6 Performance Curve Library ........................................................................................................................ 15
1.3.7 Zone Airflow Distribution........................................................................................................................... 16
1.3.8 Component browser .................................................................................................................................. 17
1.3.9 Mouse controls .......................................................................................................................................... 18
1.3.10 Mouse/key operations summary ............................................................................................................... 18
1.4 A Component-based Approach to System Simulation ......................................................... 19
1.5 ApacheHVAC Workflow using the System Parameters Interface ......................................... 20
1.6 ASHRAE Loads and ApacheHVAC System Sizing .................................................................. 21
1.6.1 ASHRAE Loads ............................................................................................................................................ 21
1.6.2 System Sizing ............................................................................................................................................. 22
1.7 HVAC System, Node, and Component results ..................................................................... 24
2 System Modeling Fundamentals ............................................................................................... 28
2.1.1 Preparation ................................................................................................................................................ 28
2.1.2 Efficient workflow ...................................................................................................................................... 29
2.1.3 Constructing Airside System Networks ...................................................................................................... 30
2.1.4 Network drawing tool ................................................................................................................................ 31
2.1.5 Room components..................................................................................................................................... 32
2.1.6 Zone components ...................................................................................................................................... 32
2.2 HVAC System Components................................................................................................. 35
2.2.1 Waterside plant equipment and water loops ............................................................................................ 35
2.2.2 Airside plant equipment and system components .................................................................................... 35
2.2.3 Room units – zone equipment applied within Room components ........................................................... 35
3 Managed systems ..................................................................................................................... 37
VE 2016 ApacheHVAC User Guide part A: Overview and fundamentals ii

3.1 System frame .................................................................................................................... 38
3.2 System Parameters dialogs ................................................................................................ 39
3.3 Tabbed sections for System Parameters and Zones Tabular Edit dialogs ............................. 40
3.4 System Parameter interface toolbar buttons ...................................................................... 40
3.5 System Parameter Links ..................................................................................................... 41
3.5.1 Overriding linked values ............................................................................................................................ 42
3.5.2 System Parameter Links – Complete listing ............................................................................................... 43
3.6 System Prototypes & Sizing workflow navigator ................................................................. 46
3.6.1 System Prototypes & Sizing workflow summary ....................................................................................... 47
4 Library ...................................................................................................................................... 49
4.1 Import from library ............................................................................................................ 49
4.1.1 Import options ........................................................................................................................................... 50
4.2 Export to library................................................................................................................. 54
4.2.1 Export options............................................................................................................................................ 55
5 Multiplexing HVAC System Networks ........................................................................................ 56
5.1.1 Multiplex Toolbar ...................................................................................................................................... 57
5.2 Creating a Multiplex – Overview ........................................................................................ 57
5.2.1 Rules for Multiplexes and controllers within them ................................................................................... 61
5.3 Create Multiplex ................................................................................................................ 62
5.3.1 Description ................................................................................................................................................. 62
5.3.2 Layers ......................................................................................................................................................... 62
5.4 Prototype layers ................................................................................................................ 63
5.4.1 Layer type .................................................................................................................................................. 64
5.4.2 Sorting by Layer Type................................................................................................................................. 65
5.4.3 Select same prototype layers .................................................................................................................... 65
5.4.4 Hide non-selected layers ........................................................................................................................... 65
5.4.5 Collapse to prototype layers ...................................................................................................................... 65
5.4.6 Add, Insert, and Copy with respect to prototype layers ............................................................................ 66
5.5 Principal vs. Non-principal multiplex .................................................................................. 66
5.6 Principal Rooms ................................................................................................................. 69
5.6.1 Assign from Room Group ........................................................................................................................... 71
5.6.2 Room(s) assigned ....................................................................................................................................... 72
5.7 Edit Multiplex .................................................................................................................... 73
5.7.1 Edit Multiplex Dialog .................................................................................................................................. 73
5.7.2 Editing Mode.............................................................................................................................................. 73
5.8 Editing Components and Controllers in multiplex ............................................................... 74
5.8.1 Tabular Editing ........................................................................................................................................... 74
5.8.2 Touch Edits................................................................................................................................................. 74
5.8.3 Edit Room Component Instances and Room Unit Controllers ................................................................... 74
5.9 Tabular Editing .................................................................................................................. 75
5.9.2 Paste to Data Table using tabular edit view .............................................................................................. 77
VE 2016 ApacheHVAC User Guide part A: Overview and fundamentals iii

5.10 Node Numbering ............................................................................................................... 79
5.11 Delete Multiplex ................................................................................................................ 80
6 System Loads, Ventilation, and Autosizing ................................................................................ 81
6.1 Overview ........................................................................................................................... 81
6.2 Zone-level loads, sizing, and related system setup procedures ........................................... 82
6.2.1 Model set up for zone-level system autosizing steps ................................................................................ 83
6.2.2 Loading HVAC systems from library or project folders .............................................................................. 83
6.2.3 System Sizing toolbar ................................................................................................................................. 85
6.2.4 System Schedules and Setpoints ............................................................................................................... 85
6.3 System equipment and plant loads and sizing .................................................................... 92
6.3.1 Unmet Load Hours tests ............................................................................................................................ 95
6.3.2 Understanding loads for ApacheHVAC components in Vista Results ........................................................ 99
6.4 Load sizing and ventilation reports ..................................................................................... 99
VE 2016 ApacheHVAC User Guide part A: Overview and fundamentals iv

ApacheHVAC User Guide part A: Overview and Fundamentals
The ApacheHVAC User Guide is divided into five parts—five separate documents—each of which covers a
set of related topics. Ten ApacheHVAC User Guide Appendices provide additional information.
A: Overview and Fundamentals

Part A describes general functions, toolbars, tree, canvas, drawing tools, overlays and
annotations, HVAC prototypes library, constructing systems, multiplexing basics, types of
components and controllers, essential rules, Integrated System Management (ISM) basics,
overview of the System Parameters UI, typical workflow, and results view.
Many of these topics are appear again in parts B–E where they are covered in greater detail.
B: Equipment, Loops, Components, and Controls

 Plant Equipment and Water Loops
 Airside Components and Controllers
 Room Unit Components and Controllers
C: Working with Prototype HVAC Networks

 Prototype HVAC Systems Library
 Rooms, Zones, Layers, and Multiplexing
 Integrated System Management (ISM), emphasizing broader VE context as in ISM phases
1b and 2, and productivity tools in phase 3; will cover phases 1-3 as they are released.
 System Setup, System Parameters, Zones Tabular Edit, Loads, Ventilation, Autosizing,
Loads Reports, and Results Analysis workflow and essential steps.
D: System Parameters Interface for HVAC Networks

 Description of each individual parameter and control in the System Parameters dialog.
 See also Appendix B: System Parameter Dialog Data Mapping.
E: Prototype Systems
 System types and common features of Prototype Systems in the HVAC Systems Library
Appendix A: Rules for Air Flow Specification

Appendix B: System Parameter Dialog Data Mapping
Appendix C: ApacheHVAC Component and Controller Limits
Appendix D: HVAC Systems Modeling Guidance for the ASHRAE 90.1 Performance Rating Method
Appendix E: Ground-Source Heat Pump Modeling with ApacheHVAC and Gaia Geothermal GLD
Appendix F: VRF systems in ApacheHVAC
Appendix G: Hydronic Radiant Heating and Cooling Systems in ApacheHVAC
Appendix H: UFAD and Displacement Ventilation in ApacheHVAC
Appendix I: Solar Hot Water Applications in ApacheHVAC
Appendix J: Pre-ISM Zone Loads, Ventilation, and Autosizing using the Loads Data Spreadsheet and
original System Schedules interface (VE2015 and earlier versions)
 Zone Loads, Ventilation, and Autosizing using the Loads Data Spreadsheet
 System Schedules dialog and HVAC controller profiles relative to setpoints
 Manual Adjustment of Throttling Range for Space Temp & Humidity
VE 2016 ApacheHVAC User Guide part C: Working with Prototype HVAC Networks 1
1 Overview
1.1 What is ApacheHVAC and where does it fit within the Virtual Environment?
ApacheHVAC is used for modeling heating, ventilating, and air-conditioning (HVAC) systems, and falls
within the Virtual Environment’s Thermal application category.
IES Virtual Environment
Thermal, Solar, Daylighting, Airflow, and both simple and detailed HVAC applications
ASHRAE 90.1 Performance Rating Method Navigator
ApacheHVAC ASHRAE Loads ApacheSim VistaPro
ApacheHVAC supports the detailed definition, configuration, control, and modeling of HVAC systems. It
interacts ASHRAE Loads for system sizing and, via Apache Thermal during simulation, with other thermal
applications, such as MacroFlo. The simulation program itself is run from within Apache Thermal.
ApacheHVAC is invoked as an adjunct to Apache Simulation by linking to a particular HVAC system file
when the building model simulation is run, as described in the Apache User Guide.
There are two distinct means of space conditioning and HVAC simulation in the IES Virtual Environment,
and these are suitable for very different tasks, levels of analysis, and stages of design.
Apache Systems – Simplified system modeling for schematic design and code compliance in ApacheSim:
 Autosized and ideally controlled systems condition spaces exactly to set points via pre-defined
HVAC system-type algorithms and minimal room, system, and plant inputs within ApacheSim.
This simplified HVAC modeling is fully integrated with the thermal, solar, and bulk-airflow
modeling at every simulation time step. However, because the systems are approximated, it is
far less representative of actual system equipment, configurations, and controls. Thus, while it
may be very useful in early design phases and space loads analyses, this type of modeling is
not generally used in detailed design development, documentation of energy use for the
ASHRAE 90.1 performance rating method, thermal comfort studies, or other detailed analysis.
ApacheHVAC – Detailed HVAC systems modeling:
 Detailed dynamic modeling of systems, equipment, and controls in ApacheHVAC is also fully
integrated with the thermal, solar, and bulk-airflow modeling at every simulation time step.
Component-based system models can be built from scratch or by modifying autosizable
prototype systems, or the prototype systems can be used in their pre-defined configuration.
When ApacheHVAC is invoked, all spaces in the model that are assigned to a room component in the
active ApacheHVAC system at the time of simulation will be served by that system. So long as this is true,
these rooms will not be served by the simpler systems otherwise defined in the Apache Systems dialog.
Like infiltration, however, air changes or flow rates for Auxiliary ventilation and Natural ventilation as
defined in the Air Exchanges tab of the Thermal Conditions template or Room Data remain in effect for all
rooms to which they have been applied, regardless of whether or not these rooms are served by an
ApacheHVAC system.
1.2 Model Setup for ApacheHVAC
1.2.1 ModelIt/Apache Space Types

Three new space types, selectable within Shape Settings and space Properties, provide improved
workflow through ‘smart plenum’ associations and user-friendly modeling of convective lighting gains for
flush-mounted fixtures.
New Space types provide improved support of HVAC Design calculations and building simulation.
 Return Air Plenum
 Supply Air Plenum
 Void
These space types can be applied three ways:
1. Shape Settings
2. Properties (right-click on browser tree)
3. Plenum/Void Creator tool
The Thermal Template specific to each new space type is automatically assigned.
Figure 1-1: Shape Settings and Properties dialogs for geometry within ModelIT. Thermal templates are
specific to the Object Sub-type.
1.2.2 Return & Supply Air Plenums
Return Air Plenums are automatically associated with the rooms below them (users can override this if
desired).
The ‘smart plenum’ association automatically directs user-designated fraction of convective lighting gains
(defined globally for a particular lighting gain) to the RA Plenum space that is above the space in which the
lighting gain is located.
The ‘smart plenum’ association also facilitates the automated management of RA Plenum model spaces in
relation to the rooms they serve when those rooms are assigned to HVAC Zones in the model and when
those room or zones are assigned to ApacheHVAC networks:
1) When a room is assigned to a zone by either drag & drop or other means, the associated
plenum comes with it automatically.
2) When a room or zone is assigned to a Principal Room or Zone component in a multiplexed
ApacheHVAC network, any associated plenum serving that space is automatically assigned to
the appropriate plenum component on the same multiplex layer.
3) If there is a void rather than a plenum above the conditioned space, then plenum component
on the HVAC layer is automatically neutralized on he network (set to ‘Adiabatic’), as there will
in this case be no return or supply air flowing through the void space above the conditioned
space in the model.
RA Plenums can be tempered for Room Loads analyses as means of avoiding inappropriate transfer of
thermal loads from a plenum to an adjacent room during the Room Loads analysis when there is not yet
any return air flowing through the plenum cavity.
For example, if the RA Plenum is adjacent to a roof that gets notably hot in the summer and cold in the
winter, the actual plenum in the real building will be very close to the room temperature during building
operation as a result of return air flowing through it. During the Room Loads analysis, however, there isn’t
yet an HVAC network operating or any sized airflows even to approximate that. Therefore, the software
not supports the tempering of RA plenums via user-specified offset from the room Heating and Cooling
setpoint values.
For very detailed design analyses, the full dynamic model with HVAC system can be set up, sized, and
simulated to refine these offsets for subsequent refinement of load calculations.
RA Plenums feature as a column of values (for each of many contributing plenum gains and losses) within
the new Loads Reports.
Figure 1-2: Return Air Plenum features including ‘smart plenum’ association, convective lighting gain
fractions, room load temperature offsets, and graphical representation within ApHVAC.
Supply Air Plenums are automatically associated with the rooms above them (users can override this if
desired).
Supply Air Plenums have the same ‘smart plenum’ association features as described above for RA
Plenums, with the difference being that they are auto-assigned to Supply Air Plenum components (rather
than RA Plenum components) in ApacheHVAC. There is no relationship to lighting gains and no user input
for tempering. SA Plenums also feature within the new Loads Reports, but just as a single line item for
gains and losses and the contribution of these to relevant coil loads.
1.2.3 HVAC Methodology

The HVAC Methodology setting enables new functionality and provides a more appropriate and
streamlined set of thermal template parameters for ApacheHVAC users, without altering the features and
functions that Apache Systems users are accustomed to.
Users can establish the methodology for a new model and all subsequent models and imported templates
via the Create New Project dialog and the Setting menu. HVAC Methodology is set to either ApSys or
ApHVAC only at the template level, but also determines the functionality and parameters displayed in the
Space Data dialogs (Rom Data and Zone Data).
Selecting the ApSys HVAC Methodology maintains all parameters within the Thermal Templates as they
were in VE2016. This is also the default for all legacy models.
Figure 1-3: HVAC Methodology options in the Building Template Manager and associated settings
Selecting the ApHVAC HVAC Methodology enables new functionality:

 Smart Plenum features are enabled for associating RA and SA Plenums with Rooms, and thus
the features made possible by this association.
 Users can designate rooms as Conditioned; Unconditioned with free-floating temperature in
Room Loads analysis; or Unconditioned during simulation, but held at a user-specified
temperature for Room Loads analysis.
For example, an appropriately ventilated parking garage under a building would not be conditioned (not
actively heated or cooled), but might use expelled air from the building or ventilation with outside air for
partial conditioning (e.g., to minimize excessive heat buildup or extreme cold temperatures). Accurate
analyses of the loads for conditioned spaces immediately above the parking garage depends on this space
being held at an appropriate temperature during Room Loads analyses.
The “System outside air supply” condition includes a new checkbox for inclusion with Room Loads, and
this is unchecked by default, as most systems modeled in ApacheHVAC condition all outside air at the
system level (i.e., it is not a room load, but is a coil load for the system that is addressed in the system-
level sizing run). When this is checked, the default settings are appropriate for ApacheHVAC users, and all
necessary edits can be made from within the Template (not need to go into ApSys dialogs for this, as was
previously required, except where automated by the PRM Navigator).
All template parameters that are not relevant to ApacheHVAC are hidden to remove potential sources of
confusion, which is particularly beneficial for new users.
1.2.4 Thermal Templates for Plenums and Voids
Plenum and Void model spaces now have dedicated thermal templates that include just the parameters
that are relevant to these space types.
Templates specific to RA Plenums provide access to parameters that would be out-off place in a Room
template. The minimization of parameters in all three Plenum and Void templates types facilitates more
efficient workflow by minimizing sources of distraction, confusion, and potential user error.
Return Air Plenum and Supply Air Plenum templates are used only with the ApHVAC Methodology (which
is forced selected for them).
Return Air Plenum, Supply Air Plenum, and Void templates are automatically assigned to these types of
spaces when they are created and/or designated as such in the model.
While some of the many uses for Voids include modeling segmented earth tube for pre-conditioning
outside air, passive solar spaces for heating of ducted air, or double-skin facades, the templates have no
special features for these applications. Rather, the user has the opportunity to define materials for their
construction and interior surface properties (including air-film resistance/convective heat transfer
coefficient) just the same as for any other geometric space in the model. The realization of these
applications thus depends on how the Void spaces are represented in the 3D model and then how they
are located within an ApacheHVAC airside network if they are to directly influence the thermal conditions
of air flowing in the HVAC system.
Figure 1-4: Thermal template options for Return Air Plenum space types shown in the Building Template
Manager
1.2.5 HVAC Zones and Zone Groups

HVAC Zones and Zone Groups is a protected browser tree grouping scheme set up specifically for
organizing Rooms into HVAC Zones, and then grouping those HVAC Zones for assignment to HVAC
Systems in ApacheHVAC.
Figure 1-5: HVAC zones and zone groups within the browser tree (example includes supply and return air
plenums associated with the zones)
A Zone Group will normally represent either all zones on a system or a significant subset of that same
group the user want to work with as a set (e.g., all zones on one floor or in one wing of the building, or for
a given building program area, in a case where the system serves multiple floors, wings, or program areas
within the building).
Each HVAC Zone within that group represents a set of one or more rooms for which there is a single
thermostat and associated means of modulating space conditioning. Multi-room zones are typical means
of minimizing costs for thermostats, VAV boxes, re-heat coils, etc. where the rooms in the zone (e.g., a set
of identical offices) are considered to have sufficiently similar load profiles.
A Master Room is designated within each HVAC Zone as the room in which the thermostat will be located.
Drag & drop functionality is provided for moving Rooms into and among defined HVAC Zones, for the
automated creation of HVAC Zones corresponding to each room when rooms are dropped on a Zone
Group, and from adding Zones to Zone Groups.
A right-click menu provides additional tools for moving rooms or zones by cut & paste, renaming zones,
accessing the Properties dialog, setting the Master Room, combining plenums when there are more than
one of any type serving the rooms within a zone, and re-synchronization of the browser tree when model
rooms are added or sub-divided.
While the HVAC Zones and Zone Groups could be used as an additional nested grouping scheme, it has no
relevant functions in relation to ApSys, as that approach to modeling space conditioning would not treat
the rooms any different as part of an HVAC vs. each room on its own (the setting of the Master Room as
thermostat location in each HVAC Zone has no bearing on ApSys).
HVAC Zones selection mode facilities single-click selection of all rooms in a zone, access to the Zone Data
dialog for a selected zone, and reporting of aggregated results for all rooms in each selected zone. When
this selection mode is engaged, clicking any Room on the model or in the browser tree selects the entire
Zone (all rooms within that zone). In VistaPro, HVAC. Zones selection mode automatically aggregates the
Room results for all rooms in each selected zone.
Figure 1-6: HVAC zone selection mode option and functionality
The Zone Data dialog is accessed by entering the HVAC Zones selection mode, selecting a zone, and
clicking the query button. This dialog confirmed template settings for HVAC Methodology and
Conditioned status and provides means of viewing and revising for the Master Room, the associated
Plenum to be used for the overall HVAC Zone, zone Heating and Cooling setpoints profiles, and Return
Plenum temperature offsets. Setting for these parameters in Zone Data override equivalent Room-level
and Template settings. For example, changing the Return Plenum temperature offsets in Zone Data will
override and update the same value for all RA Plenums associated with Rooms in the selected HVAC Zone.
Figure 1-7: Zone Data dialog within Apache, accessed in HVAC zone selection mode
1.3 ApacheHVAC Interface Overview
Figure 1-8: The ApacheHVAC view or module within the IES Virtual Environment.
The ApacheHVAC view comprises the interface features described below.
1.3.1 Virtual Environment Menu Bar
…
These menus provide functions used throughout the Virtual environment. Please refer to the Virtual
Environment User Guide for further information.
1.3.2 ApacheHVAC Menu Bar
These pull-down menus provide functions specific to the ApacheHVAC view.
1.3.3 ApacheHVAC Toolbars
The toolbars provide quick access to menu functions, selection of components and controllers to be
placed on the system schematic, creation and editing of system of multiplexes, and access to system
prototypes.
 New
 Open
 Save
 Hot water loops  Direct-acting heater/cooler types

 Generic heat sources  Heating coil
 Air-to-air heat pump types  Cooling coil
 Heat transfer loops  Air-to-air heat / enthalpy exchanger
 Water-to-air heat pump types  Steam humidifier
 Chilled water loops  Spray chamber / evaporative cooler
 Generic cooling sources  Fan – left intake
 Dedicated waterside economizer types  Fan – right intake
 DX Cooling types  Mixing damper set
 Unitary cooling system types  Return air damper set
 Radiator / radiant panel types  Duct heat gain / loss – horizontal
 Chilled ceiling /radiant panel types  Duct heat gain / loss – vertical
 Import HVAC networks from libraries, etc.  Export HVAC networks (entire, subset, plant, etc.)
 Create multiplex  Layers selected of layers in multiplex

 Edit multiplex  Current multiplex display layer
 Local / global edit mode  Layer up / down
 Room or thermal zone component  Junction / flow splitters (four)

 Air inlet  Straight connectors (two)
 Air outlet  Elbow connectors (four)
 Network drawing tool  Crossover connector
 Independent time switch controller  Dependent time switch controller  AND connection
 Independent controller with sensor  Dependent controller with sensor  OR connection
 Independent differential controller  Dependent differential controller
 System schedules and setpoints
 System parameters
 Zones tabular edit view
 Global system parameter assign
 Room and zone-level sizing
 System equipment and plant sizing
 System loads, sizing, and ventilation reports
 Move
 Copy
 Query item
 Check network
 Assign zones
 Apache profiles
 Delete
 Enable/disable component tooltips
 Show/hide link for all overlays
 Show/hide overlays
 Remove all overlays
 Preferences
 Add new loop

 Edit selected loop
 Copy selected loop
 Remove selected loop
 Open loop list dialog
The last ten of the toolbar buttons above will be available along with the graphic waerside interface in
ApacheHVAC and detailed component-level results in Vista-Pro as of VE 2012 Feature Pack 2.
1.3.4 View Toolbar
This provides functions for manipulating the view of the system schematic, including zoom to HVAC
network extents, window, in, out, pan, previous, and next.
1.3.5 Model Workspace
Figure 1-9: The initial model workspace or canvas displays the HVAC system airside schematic and
provides a graphical means of selecting, configuring, organizing, and editing airside component and
controller objects. While plant equipment other than that associated with water loops is accessed while
remaining in this view, this is what we refer to as the airside HVAC or airside network view.
Figure 1-10: There are also three parallel waterside graphic views, as shown above with a range of
possible options engaged. These are accessed via the three corresponding toolbar buttons shown below:
Hot water loops
Heat transfer loops
Chilled water loops

These three buttons are toggles that take you back to the airside view when un-clicked.
1.3.6 Performance Curve Library

The Performance Curves Library is the first of a set of tools for loading, visualizing, and customizing
polynomial fit curve performance data for HVAC equipment. Initially, this covers a large number of
generic (entering condenser temperature based) and actual (leaving condenser temperature based)
electric water-cooled chiller models. It will later be expanded to include other HVAC plant equipment.
The new curves interface provides exceptional visualization and access to curve parameters. Articulated
3D plot and two different 2D plots are provided for each of Capacity – temperature dependence, EIR –
temperature dependence, and EIR – part-load dependence curves.
Figure 1-11: Performance curves library showing a 3D plot of Capacity – temperature dependence for a
model-specific LCT-based curve set
1.3.7 Zone Airflow Distribution
The Zone Airflow Distribution table provides for viewing all zone airflows and for viewing and editing the
default distribution of airflow among rooms within each zone.
 As with the outcome of duct sizing and testing & balancing procedures in an actual buildings,
airflow from a zone-level VAV box or similar must be appropriately distributed among the
rooms that it serves.
 Distribution of air among rooms within a zone for space conditioning is by default according to
the relative load in each space.
 Users can override this by editing either the distribution percentages or the individual room
airflow values, if desired. (Zone-level airflow overrides are provided in the System Parameters
and Zones Tabular Edits dialogs where that airflow is otherwise determined.)
 Rather than directly overwriting user edits, the autosizing process maintains the proportional
relationship among rooms in each zone, as established by manual user edits of the default
values.
 Ventilation columns are included only when one or more systems has Dual-Inlet Zones.
Ventilation air is otherwise distributed as mixed with Primary Air from the air handler for
heating and cooling.
 The designation of the Master Room in each zone is also visible and can be edited here.
Figure 1-12: Zone airflow distribution table shown with autosized and manually adjusted airflow
distributions within different zones
1.3.8 Component browser
Browser show/hide toolbar button.
Figure 1-13: Component browser tree with HVAC network components and controllers.
The component browser provides a listing of all components in the current ApacheHVAC file. This can be
used to locate and/or select a particular type of component or controller within a large or complex HVAC
network. Selecting the component or controller within the browser causes it to be highlighted on the
network in the model space. The browser can also be useful in determining how many of a particular
component or controller type are present.
It is not necessary to hide the component browser for most HVAC system networks, as the speed of this
has been significantly improved over earlier versions. When working on exceptionally large or complex
HVAC networks, if the opening of component and controller dialogs does begin to slow noticeably, the
component browser can be turned OFF by clicking the browser show/hide button on the toolbar. This will
further increase the speed with which component and controller dialogs open.
1.3.9 Mouse controls

The left mouse button is used for selecting and placing component and controllers. When placing these,
the current selection persists until cancelled by clicking the right mouse button. The mouse scroll wheel
can be used to zoom in and out of the systems view. The pan function accessed provided by moving the
mouse while depressing the scroll wheel.
1.3.10 Mouse/key operations summary

The combined keyboard and mouse actions described in the left column below can be used to complete
the corresponding operations listed in all capital letters in the right column.
1.3.10.1 Selected airside network objects

Drag MOVE
Ctrl + Drag COPY
Ctrl-C COPY TO CLIPBOARD
Ctrl-V PASTE FROM CLIPBOARD (within current HVAC session)
1.3.10.2 Elements of a selected controller (applies only when a single controller is selected)
Click & Drag MOVE NODE (round sensor bulb or control lead end with arrowhead)
Shift + Drag MOVE CONTROL BOX
1.3.10.3 DURING “PENCIL” DRAWING

Click on object or in blank cell START NEW PATH
Click object after starting path CONNECT or CREATE JUNCTION
Click bare end after starting path CONNECT or CREATE JUNCTION
Click bare end after starting path CREATE CUSP or 90° BEND
Double-click in a blank cell TERMINATE CURRENT PATH (as bare end)
Ctrl-Z (up to 10 times) UNDO SECTION to PREVIOUS CUSP/OBJECT
1.4 A Component-based Approach to System Simulation
Energy simulation programs have in the past provided models of only certain fixed system types (VAV,
induction, fan coils, etc). In practice, building systems do not conform to these rigid system types, and so
it was necessary to accept a degree of compromise in the realism of the model.
Figure 1-14: A multi-zone HVAC network—in this case variable-air-volume with indirect-direct evaporative
cooling, energy recovery, variation of static pressure with bypass of heat exchangers, duct heat gain,
return air plenums, controls for mixed-mode operation with natural ventilation, and primary, transfer,
and exhaust airflow paths available to each of the zones in the layered multiplex region.
ApacheHVAC has been designed to impose minimal restrictions on the user in defining the system model.
The user is offered a number of basic blocks, each describing a generic type of equipment (heating coil,
fan, humidifier, etc.). These basic blocks can be assembled as required to model an actual system
configuration, rather than an idealized simplification. The complexity of the model is limited only by the
types of block available and some basic rules concerning their interconnection. Within these constraints,
it is possible to assemble models of many different system and control configurations and to explore the
benefits of variations on standard system types.
An item of plant or control can be described once, and then copied or referenced as many times as may
be required to define the system.
1.5 ApacheHVAC Workflow using the System Parameters Interface
1) Set up HVAC zone groups and AHU/system groups in model.
2) Edit HVAC schedules and setpoints via the current System Schedules & Setpoints dialog.
3) Load HVAC networks or Managed Systems (having a system frame) from the HVAC library.
4) Set up waterside loops, plant equipment, etc., as desired; or leave this step for later.
5) Set up prototype layers, if desired. This is an optional preparation similar to steps 6 and 7 below, but
setting up multiplex layers and system parameters data for types of zone or layers, rather than for
specific zones or layers. This can also be done ahead of time in saved user-library prototype systems.
6) Click the ‘Edit Multiplex’ toolbar button or double-click the top bar of the green multiplex frame in a
system to assign model zones to the principal room/zone component on each multiplex layer. If
prototype layers have been set up, assign zones accordingly to reduce the number of edits to be made
later for individual zones or selected set of zones.
7) Click the ‘System Parameters’ toolbar button Double-click the gray system frame to perform edits in
the System Parameters dialogs at the level of systems and zones to complete system set-up.
ApacheHVAC User Guide part D: System Parameters Interface for HVAC Networks provides
comprehensive and detailed guidance and information regarding this dialog.
8) Run Room/zone autosizing from HVAC toolbar button or from the ASHRAE Loads dialog.
9) Open the System Parameters dialog again for each system, or via the toolbar and then select the
system to edit within the dialog to view and edit the following as needed:
 System input parameters, such as supply air temperatures;
 Zone-level loads, input parameters, and settings;
 Resulting autosized and derived parameters, such as required zone airflows, zone ventilation
rates, system flow rates, and engineering checks.
10) Transfer the edits made in System Parameters dialogs to component level using the ‘Assign’ button.
11) Data can be directly edited at component level via individual component and controller dialogs,
overriding settings passed down from the associated system parameters dialog. This may be necessary
for departures from system prototypes or to edit parameters not included/editable within the System
Parameters dialog. Direct component-level edits to any parameters that are editable in the System
Parameters dialog will be overwritten by subsequent ‘Assign’ operations in System Parameters dialog.
Setting the system parameter link to ‘None <Select>’ will preserve any user edits of this nature,
preventing them from being overwritten. Selecting any system parameter link or retaining the default
link and clicking the ‘Re-apply’ button will override component-level edits.
12) Set up waterside loops, plant equipment, etc., if not already completed (step 4).
13) Run System-level autosizing from ApacheHVAC toolbar or from the ASHRAE Loads dialog.
14) View updated derivations as needed in the System Parameters dialog, as the autosizing of the supply
fan according to simulated peak coincident flow on each network may have affected these. In some
cases, it may be appropriate to override the autosized supply fan flow rate within the System
Parameters dialog to match actual fan sizing and to address related engineering checks.
15) If necessary, adjust user setting and inputs, re-assign resulting values to components and controls, and
re-run the system-level autosizing.
16) Inspect waterside/equipment dialogs for other autosized values, noting the effects of system sizing
with respect to water loops, boilers, chillers, heat pumps, etc.
17) Generate and view System Loads and Sizing reports.
18) Perform simulations and view results.
1.6 ASHRAE Loads and ApacheHVAC System Sizing
1.6.1 ASHRAE Loads

ASHRAE Loads supports flexible user control and differentiation between Room & Zone Loads, System
Loads, and Dynamic Simulation. The following can be independently determined for the different types of
loads analyses, with settings for each being retained by the software:
 Inclusion of internal gains;
 Diversity for internal gains;
 Saturation of profiles for internal gains, and if so, during all hours of non-zero profile values or
just during occupied hours;
 Use of Design Day profiles when specialized gain profiles are needed specifically for Loads
Analyses;
 A separate setting for inclusion of Diversity factors in dynamic simulations is provided in the
ApacheSim dialog.
The user settings above are retained as user preferences for future loads and simulation runs.
Figure 1-15: ASHRAE Loads dialog utilizing Design Day profiles with Diversity applied to internal gains
1.6.2 System Sizing

A consolidated “Generate system loads and sizing reports” dialog provides one place to generate a broad
range of new and existing reports for buildings, system, zone, and room loads, sizing, and ventilation. This
provides user control over:
1. The results file to be used for generating reports;
2. Which of the new PDF Loads reports will be generated;
3. Selection of the relevant coils for reporting of gains and losses contributing to coil loads at the
time of the coil peak;
4. The inclusion or exclusion of oversizing factors, which will be indicated one way or the other
on the reports generated.
Available reports include:
 Project and climate (building, weather, etc.)
 Plant loops & equipment (capacity, flows, etc.)
 System summary (space loads & ventilation)
 System loads (detailed loads breakdown, coil capacities, airflows, engineering checks, etc.)
 Zone Loads (same as for System)
 Room Loads (same as for Zones)
 VE2016 System Sizing reports
 ASHRAE 62.1 Ventilation (App. A method)
Figure 1-16: Generate system loads and sizing reports dialog with relevant peak settings shown
1.7 HVAC System, Node, and Component results
Simulation results for detailed HVAC system modeling in ApacheHVAC can be viewed and analyzed in both
Vista and Vista-Pro modules. In addition to the model-level system results and more detailed room-level
results, the standard Vista results view offers access to results for airside HVAC network nodes (essentially
as shown in VistaPro, below) as well as node-based results for a small number of airside components.
VistaPro provides access to all HVAC results, including those associated with thermal zones (rooms or
other spaces in the model), nodes on the airside HVAC network, components on both airside and
waterside networks, and all HVAC plant equipment.
Figure 1-17: Selected results for two airside network nodes and a cooling coil component in VistaPro.
Figure 1-18: Selected results for a chilled water loop, chiller, and fluid cooler in VistaPro.
Figure 1-19: Detailed component-level results can be analyzed over the course of a day to understand the
influence and interactions of water- and air-side system configuration and control options.
Figure 1-20: When a particular component is selected on the waterside component browser tree in
VistaPro, the appropriate set of component output variables becomes available for that component.
Figure 1-21: Component variables can be locked via the Chart Data dialog (access by clicking the plot area)
to include many details on a single plot. Above, energy and operating capacity for ten water-loop heat
pumps have been plotted with select performance parameters for the heat exchanger and cooling tower
used to reject heat from the heat pumps and the common heat transfer loop that couples them.
2 System Modeling Fundamentals
2.1.1 Preparation
The speed, efficiency, and effectiveness with which an ApacheHVAC system can be set and all thermal
zones assigned to it is significantly dependent upon the extent to which the model has been appropriately
organized prior to doing so. Therefore, it is important to complete the following in ModelIt, before
attempting to assign rooms or zones to an ApacheHVAC system:
 Begin by using the Connect Spaces tool to couple any rooms in the model that will share a
common thermostat or related means of controlling space conditions (e.g., they will all be
served by a single VAV box). The resulting thermal zone will thus be represented as a single
“Room” component in ApacheHVAC. This will facilitate use of multiplexing, pre-defined
systems, and efficient system layout, while avoiding unnecessary complexity.
o When connecting spaces, if they will be separated by physical partitions in the actual
building, these partitions should be retained, as their thermal mass and ability or
receive solar gain or other radiant, conductive, and convective heat transfer will
contribute to the accuracy of thermal and energy modeling.
o If any of the zones has absolute internal gains (W or Btu/h) rather than internal gains
defined according to floor area (W/m2 or W/ft2), the absolute gains will have to be
manually added in the composite zone. However, if they are assigned per unit floor
area, no action is required, as no floor area will be lost.
 In addition to conditioned spaces, create geometry for any other spaces or zones that will
need to be represented in ApacheHVAC, such as return-air plenums (typically one per floor or
as designed), underfloor air distribution (UFAD) supply plenums, thermally stratified zones,
radiant heating or cooling slabs, earth tubes, solar chimneys, etc.
 It is important to set up a Grouping Scheme in ModelIt that sorts thermal zones into groups
such as System-1, -2, -3, etc. or AHU-1, -2, -3, etc. and other space types, such as Return air
plenums, Solar chimney segments, Unconditioned zones, etc.
 If the model includes UFAD of thermal displacement ventilation (DV), it is essential to ensure
that the number and order of Stratified zones exactly matches the number and order of
corresponding Occupied zones in any one AHU group. Doing so will facilitate system
multiplexing, autosizing, and other fundamental aspects of system modeling. If there are some
mixed (non-stratified zones) on the same system, either place them in a separate group of
occupied zones or create dummy stratified zones (e.g., a series of small super-insulated boxes
with no internal gains) in the model that can fill out the list of stratified zones to make it
parallel the list of occupied zones on the same system. Occupied and Stratified should be in
separate groups with the AHU Assignment scheme.
2.1.2 Efficient workflow

The following are recommended whenever starting a complex project, testing custom configurations and
controls, exploring ApacheHVAC capabilities, or experimenting with HVAC strategies for a large project:
1. Start with a small model that represents what you’re exploring is the simplest terms, then save to
a new name just before trying something new so that the experiment can be discarded and
started over again without significant loss of investment. Many iterations with smaller models can
often be more instructive and rewarding than just a few iterations with a larger model.
2. Use short simulation runs of one to three select days (very hot, very cold, should season, etc.) to
explore new configurations of models and systems prior to running full annual simulations. This
facilitates rapid and efficient cycles of experimentation and learning.
3. When setting up the model of the full project, combine separate rooms into thermal zones within
ModelIt to the extent feasible, given the diversity of space uses, solar exposures, other loads, and
the required resolution of results. All actual internal partitions should be retained. In most cases,
there should be no fewer thermal zones than there will be actual thermostats in the building;
however, if numerous zones are truly identical with respect to internal gains, constructions,
fenestration, façade orientation, solar exposure (e.g., when local or roof shading is the same and
there are no adjacent buildings), then these zones might best be further combined as “thermal
blocks” (composite “rooms” in ModelIT). Again, all internal partitions should be retained.
4. If already underway with a large model and you need to test a new HVAC system configuration or
controls—especially if this is a custom configuration—testing first with a small subset of the
model and, again, over a short simulation period, saves time. It will provide short simulation runs
and thus quick feedback for confirming and/or trouble-shooting the intended system operation.
Test simulation runs can be performed for just a few notably important or representative spaces
in the model with all other zones and multiplex layers temporarily removed from the system. This
significantly reduces simulation run times and bounds the experiment, improving the ease of
initial analyses and detection of input and configuration errors. This can be valuable when
attempting adjusted, new, complex, or innovative configurations and control strategies.
To test a new system with a simulation run for just a portion of the model, place the thermal
zones that will best represent the test case—e.g., all zones on one particular HVAC air handler
that is to be uniquely controlled—on a designated layer within Model-It. Then, within Model-It
Layer Properties, set all other populated model layers to OFF (inactive). If there are other systems
or networks in the same HVAC system file, save a copy of the file to a new name and remove all
but the airside system network required for the experiment. Similarly, if a test is to be performed
for just a few zones on a large system with many zones, save the HVAC file to a new name and
remove all inactive zones and associated multiplex layers from the test system (the simulation will
not run if there are ApacheHVAC systems referring to rooms or zone on inactive model layers).
When refinements and/or corrections to the new system and controls have been competed in
this simplified context, re-introduce other building zones, systems, etc., and perform additional
short simulation runs to test and refine this complete model. Finally, perform longer runs to
generate needed whole-building annual results and so forth.
2.1.3 Constructing Airside System Networks
Airside system networks are constructed by picking components from the toolbars. Airside components
take the form of ‘tiles’ that are placed on the canvas to build up a schematic of the airside system.
Controllers can also be drawn, together with lines indicating the associated sensor and control points.
Certain components, such as plant equipment, do not appear on the schematic, but are instead linked to
other components via text references.
Each component has a set of parameters characterizing its operation. Facilities for editing these
parameters are accessed by double-clicking on the component or through the menus. Once placed,
groups of components may be selected, deleted, moved, or copied using functions on the toolbar. Every
closed loop that can be traced in the HVAC airside network must pass through at least one room that is
assigned to a space in the model.
Multiplexing, described in section 6, provides an efficient means of assigning groups of spaces to a set of
room components and of replicating and editing HVAC components, controllers, and configurations
thereof. The associated Tabular Edit view supports efficiently editing and checking numerous inputs for
components and controllers.
When drawing HVAC airside schematics, it is helpful to keep in mind the following principles:
 When first building an HVAC system from scratch or modifying and exiting system, it is advisable to
keep the system simple. This makes it easy to test the control principles involved. The system can
later be expanded to introduce additional rooms and control refinements.
 Set up the minimum number of air flow controls necessary to define or deduce the flow on all
branches of the system. In other words, airflow must be specified in all parts of the system, except
where the flow can be deduced from other specified flows by addition and subtraction of known
values at junctions. Specifying flows on more branches than is strictly necessary is not forbidden,
but always ensure that the specified flows are mutually consistent. In most cases, it will be much
easier to allow flows to be calculated wherever possible, thus avoiding “over-constrained” airflows.
 Every closed loop in an airside network must pass through at least one room component that is
assigned to a space in the model. It cannot satisfy this rule if it remains set as an adiabatic duct.
 In the case a room or HVAC zone, it is necessary to specify only the supply or the extract flow, but
not both, unless the extract is a separate branch diverting some or all of the flow from a return air
path for any given layer in a multiplex (most of the pre-defined systems are configured this way).
The program will then set the other flow on the assumption of equality of inflow and outflow.
 In specialized applications, such as when MacroFlo is running in tandem with ApacheHVAC, room
inflow and outflow may be set to different values. Any imbalance between inflow and outflow will
be picked up by MacroFlo, and the difference will be made up with flows through openings in the
building. An imbalance can also be meaningful if MacroFlo is not in use. For example, if more air is
supplied to a room than is extracted, the excess will be assumed to be vented to outside. For a full
account of the rules for airflow specification see Appendix A: Rules for airflow specification.
 The schematic may include multiple System Inlet and System Outlet components. These are used to
represent the main air inlet and outlet of a mechanical system and other paths, such a dedicated
exhaust, fume hood, or explicit exfiltration in the case of a pressurized building.
 Most components placed on the airside network must have appropriate controllers attached in
order to function. See component sections for details.
 The Check network button can identify many kinds of errors in a schematic. It also numbers the
nodes of the network, providing a reference that is useful when viewing simulation results. To
remove the node numbering, if desired, simply re-open the same ApacheHVAC file.
Details of all equipment to be included in the simulation are entered in ApacheHVAC. The extent of data
input depends on the scope of the simulation, which is at the discretion of the user. For instance if it is
required to calculate the net energy consumption of a low-temperature hot water (LTHW) heating coil, it
will be necessary to specify a coil and a heat source to serve it. However, it will not be necessary to input
the characteristics of the LTHW system. In such a case, the distribution losses of the LTHW system and
pump power should be entered as zero and the heat source efficiency taken as 100%.
Note that the capacity (duty) of equipment for simulation can be set as the components are placed or can
be provided by the autosizing process. In many cases, it is necessary to specify or autosize the system to
provide a capacity that equals or exceeds any requirement subsequently called for; however, the hot and
chilled water loops and the advanced heating and cooling coils are capable of accurately representing
system performance when heating or cooling plant equipment are undersized (whether the undersizing is
intentional or otherwise). This can be useful for modeling systems intentionally designed to be heavily
dependent on mixed-mode operation with natural ventilation, waterside economizer operation, lake or
well-water heat exchange, solar hot water systems, or to directly address all but transient peak loads,
leaving the transients to be mitigated by the effects of thermal mass or similar passive strategies. The
simulation can provide evidence of energy saving benefits, consistency of thermal comfort, and system
performance and the effectiveness of design and control strategies under challenging conditions.
2.1.4 Network drawing tool

The “Pencil” icon on the lower toolbar can be used to enter a network drawing mode, shown by the
cursor changing to a pencil. While in this mode, all of the simple connectors, elbows, and junctions of a
network can be quickly drawn by a minimal number of successive mouse clicks.
An airflow path is initiated by clicking either in a blank cell or on an existing network component. In the
case of the latter, the path may continue from any free connection of that component.
The behaviors of different types of mouse click, during the drawing of a path, are listed below.
 Having initiated the airflow path, a subsequent click in a blank cell sets that cell as the location of
a right-angle bend (a cusp), and the next click can be in any of the 3 possible orthogonal directions
from there; connections are permitted in orthogonal directions only—i.e., not diagonally.
 Clicking on a network component will incorporate it in the path, which may then be continued
from any remaining free connections on that component. This makes it easy to connect network
components that have already been placed on the canvas.
 Clicking on either an existing straight connector at right angles to the path, or an existing bend,
will generate a new “indeterminate” junction bearing a red question mark, to indicate that its
flow directions are undefined. As long as indeterminate junctions exist, the network is invalid and
thus they need to have their flow directions individually defined later (using the normal double-
click or query), before attempting either to check the network or to use it in a simulation.
 Clicking twice in a blank cell terminates the current path with a bare half-connector. You are still
in the drawing mode, and can start a new path elsewhere by clicking in any other blank cell, or on
any object with free connections. You can also continue the path from any bare half-connector.
Drawing a path past, and at right angles to, a bare half-connector will generate a junction at that
location. As with indeterminate junctions, a network containing bare half-connectors is invalid, so
these need to be connected up before a network check or simulation run.
At any time, up to 10 previous segments of the path can be undone using Ctrl-Z, or Undo on Edit menu.
There are three ways to exit the drawing mode: Right click on canvas; Esc key; click another toolbar icon.
2.1.5 Room components
There are a number of important points to note with regard to the arrangement of room components in
the air system and the specification of supply airflow rates:
 A “Room” in the VE is any 3D space that is to be modeled as a distinct thermal zone. This can
be multiple rooms combined in ModelIt as a thermal zone, a single room, or a subdivided
potion of room volume, such as a perimeter zone in an open-plan space or the occupied or
stratified zone within a space served by displacement ventilation. The ApacheHVAC “Room”
component can also refer to a space that would not or could not be occupied, but which plays
a role in the dynamic thermal interaction with HVAC systems. Examples include a return-air
plenum, an underfloor air distribution (UFAD) plenum, a segment within an earth tube, a space
within a vented double-skin façade, or even a concrete slab that will be directly heated or
cooled by a hydronic loop.
 It is permissible to use the same room component more than once in the air system network
description, such as when more than one system supplies air to the same room. For example,
consider a case where room type A has separate air supplies for heating and cooling; there
may only be one actual room type A, but we can use two in the system network description -
one in the heating branch and one in the cooling branch. The result is exactly the same as if
you had mixed the heating and cooling supply branches together through a combining junction
and supplied this mixed air to a single room type A. The use of multiple room components in
this way reduces the need for large numbers of mixing and dividing junctions.
 Once the system air has entered a room component, the program assumes that the air within
the room (or bounded thermal zone assigned to a room component) is fully mixed. It is not
possible to differentiate between, say, air entering from a ceiling diffuser and air entering from
a perimeter unit or a floor outlet. You can, if you wish, describe a single room as several room
types for the purposes of the computer simulation—e.g., the core and perimeter zones of an
open plan office could be described as separate room types. However, you should appreciate
that there are a number of complex mechanisms of heat transfer involved in such a situation
(wind, stack, and induced air movement, radiant heat exchange, etc.) and the program can
only approximately analyze some of these.
 Some situations are best modeled by putting two room components in series. For example,
you may wish to model a building in which the return air is extracted via the ceiling void. This
can be achieved by describing the occupied space and the ceiling void as two separate room
types and then connecting them in series.
Direct acting units, radiators, and chilled ceilings can be added to spaces for heating and/or cooling
purposes. Room units can be added to spaces contained within HVAC zones as well as directly to spaces
in an un-zoned model. It is recommended that users work with Room components within ApHVAC,
instead of Zone components, when large numbers of room units are to be implemented as editing of the
units will be quicker and more efficient.
2.1.6 Zone components

ApacheHVAC users have the option to work with Zone components in order to gain access to associated
features, or to work with Room components as in VE 2016 and other earlier versions of the software.
Settings in the ApacheHVAC Preferences dialog and the HVAC System Library Import dialog determine
whether prototype systems will be loaded with Zones or Rooms and whether the Zone/Room placement
tool will default to placing a Zone or Room component on the canvas.
When working with Zones, assignment of model spaces is by Zone or Zone Group. The group can be all
zones on a system or any subset therefore, as might be desired for maintaining separate sub-groups
within the Zone Groups.
Figure 2-1: The default preference in ApacheHVAC is to load Prototype systems with Zone components. A
radio button within the dialog allows users to load networks with Room components instead. A setting in
the ApacheHVAC Preferences dialog allows users to change the default preference of the software.
Figure 2-2: Any Room Component on the network canvas can be converted to a Zone Components, or vice
versa.
Direct acting units, radiators, and chilled ceilings can be added to spaces for heating and/or cooling
purposes. Room units can be added to spaces contained within HVAC zones as well as directly to spaces
in an un-zoned model. It is recommended that users work with Room components within ApHVAC,
instead of Zone components, when large numbers of room units are to be implemented as editing of the
units will be quicker and more efficient.
The air inlet of any Zone can be converted to a Dual-Inlet, with designated inlets for Ventilation and Space
Conditioning. This is necessary for a system wherein Ventilation air is meant to be delivered separately to
Rooms within multi-room HVAC Zones.* For example, in a dedicated outside-air system with ventilation
air diffusers in each room and separately supplied airflow from zone-level fan-coil units, the apportioning
of ventilation air and air for space conditioning needs to be separately determined.
Whereas distribution of air among rooms within a zone for space conditioning is by default according to
the relative load in each space, the default basis for the distribution of Ventilation air among Rooms in a
Dual-Inlet Zone is according to the relative floor area of the rooms.
*This is not needed when the space conditioning is at the Room level (as if there were a fan-coil unit in
each room), as the rooms in that case would each need to be a separate zone with its own thermostat
(i.e., air would not be distributed among rooms within a zone, as there would be just one room in each
zone).
Figure 2-3: A dual-inlet zone component is used when an HVAC Zone comprises rooms with Ventilation
separately delivered to each room, and therefore this needs to be apportioned separately from the
airflow for space conditioning.
2.2 HVAC System Components
Figure 2-4: HVAC components toolbar

ApacheHVAC provides for modeling a comprehensive range of HVAC components, as listed below.
2.2.1 Waterside plant equipment and water loops

 Heat sources: hot-water loops and pumps, equipment sequencing, boilers, generic heat
sources, air-source heat pumps, solar hot-water, furnaces, electric-resistance heat, etc.
 Chilled water loops: sequenced operation of chillers and other cooling equipment, primary and
secondary chilled-water loops, pumps, condenser loops, cooling towers, wet or dry fluid
coolers, condenser heat recovery, integrated waterside economizer, etc.
 Chillers: electric water-cooled, air-cooled, other similar water cooling sources
 Waterside economizers (integrated, non-integrated, or dedicated)
 Water-source heat pump upgrade of heat recovered from a condenser-loop
 Air-to-air heat pumps (1 to 1 relationship with coil on airside; backup heat source)
 Direct-expansion (DX) cooling (1 to 1 relationship with a coil on the airside network)
 Unitary cooling systems (complete unit is represented by a coil on the airside network)
2.2.2 Airside plant equipment and system components

 Room components (representing any geometric/thermal space in the model)
 Heating coils (simple and advanced models for hot-water, generic, and AAHP sources)
 Cooling coils (simple and advanced models for chilled-water, DX, WSE, and UCS sources)
 Air-to-air heat/energy/enthalpy recovery devices
 Fans
 Spray chamber humidifiers
 Steam injection humidifiers
 Damper sets, including mixing dampers and controlled flow splitters
 Ductwork components with thermal properties for modeling heat gain or loss
2.2.3 Room units – zone equipment applied within Room components

 Radiators and similar terminal heating devices, such as baseboard heaters
 Direct-acting heater/coolers
 Chilled ceiling panels, chilled beams, and similar terminal cooling devices
The first set of these are defined mainly in plant equipment dialogs. Components in the middle set are
dealt with mainly on the airside network. The last set, room units, differ from other HVAC components in
that they are defined in terms of “types” but then located within a room component or thermal zone
(including in non-occupied space or a heated or cooled slab zone) rather than on the airside network.
The modeling of plant components is quasi-steady-state in that the program does not attempt to model
transient behavior between simulation time steps. However, because time steps in ApacheSim are
typically only 6-10 minutes, and can be as little as 1 minute, if desired, constant plant behavior over a time
step is an appropriate assumption. Furthermore, there is interaction between the HVAC system and
conditioned spaces (including natural ventilation, stack-vent double-skin facades, etc. when running
MacroFlo) at every simulation time step.
The solution algorithm also provides for modeling intentionally undersized heating and cooling plant
equipment or sources. Coils and other connected devices on a hot or chilled water loop will receive off-
design water loop temperatures in keeping with the capability of the modeled plant equipment when the
load exceeds the heating or cooling capacity.
Data entered for fans represents a special case in that fans are not controlled directly and fan component
inputs are used only to calculate consequential energy consumption and effect on air temperature. The
value entered in a fan component does not determine airflow through the system. Rather, the fan
component acts like a meter with a defined set of performance characteristics. The airflow through the
fan is determined by flow controllers on network branches.
All pre-defined HVAC equipment performance curves, such as those provided for Electric Water-Cooled
Chillers, DX Cooling, Hot-Water Boilers, and Water-to-Air Heat Pumps, are valid only at the reference or
Rated conditions that were used to derive the curves from the performance data. (Reference condition is
the condition to which all other performance data are normalized.) The default Rated condition
temperatures—for example, the rated entering condenser water temp and rated chilled water supply
temperature for the EWC chillers—as shown in the Rated condition tab of the chiller editing dialog are
those used as the reference conditions for the currently selected set of performance curves. Therefore,
except when intending either to edit the performance curves or add new performance curves based on
different reference condition temperatures, avoid editing the default rated condition temperatures.
Loads and sizing data for room/zone loads, ventilation rates, zone/terminal equipment, primary airside
equipment, and heating and cooling plant are provided in design sizing reports.
Simulation results are provided for each reporting time step (1 hour maximum; 6 minutes minimum).
Results are reported separately for each plant equipment category and fuel/energy type. Coil
psychrometrics can be assessed for each time step. Thermal, moisture, and air flow results for each
airside node can be queried for individual time steps. Energy used by room units at each time step is
accounted for and reported separately from airside HVAC heating and cooling components.
Room units can be added to spaces contained within HVAC zones as well as directly to spaces in an un-
zoned model. It is recommended that users work with Room components within ApHVAC, instead of
Zone components, when large numbers of room units are to be implemented as editing of the units will
be quicker and more efficient.
3 Managed systems
The System Parameters dialog works with ‘managed systems’. A managed system has a system frame and a
multiplexed set of zones and related components and controllers.
Each managed system in the ApacheHVAC file has a System Parameters dialog that provides a user-friendly
means of editing and in many cases deriving its component level parameters; with user inputs alongside zone
loads, sizing parameters, derived values, and engineering checks.
While the entire system must be contained within the system frame, it can be connected via airflow paths to
other systems, which may or may not also be managed systems. However, only the components and
controllers within the system frame can be linked to the System Parameters dialog.
The System Parameters dialog is accessed either by double-clicking top bar of the system frame or by clicking
the System Parameters toolbar button shown above, and then selecting the ‘System to edit’.
3.1 System frame
The system frame is a container, a clickable element, and a means for providing feedback. The system frame
changes color, has symbols added or removed at the right end of the top bar, and provides ToolTip information
to indicate the current status of the system with regard to user edits, autosizing, and error conditions.
Summary of System Frame Status and ToolTips

User action or trigger Frame, top bar, and text color ToolTip
System unchanged from HVAC “HVAC network unaltered since being
library; no user edits or loaded from system or user HVAC
autosizing. systems library—no user edits or auto-
sizing yet”
User edits have been made and “User edits have been saved, but not
saved, but not yet assigned. assigned to the components and
controllers in the HVAC network.”
User edits completed and “User edits have been saved and assigned
assigned to components and to the components and controllers in the
controllers. HVAC network. If previously auto-sized,
at least one or more auto-sized value has
been overridden by a saved user edit.
Unaltered auto-sized values remain in
green text.”
Error condition in System “There is an error in a user-edited value
Parameters; must be corrected or derived parameter. This error is
before assigning. highlighted in the dialog and must be
cleared prior to the Assign operation or
any simulation of the HVAC system”.
List of the parameters in error is
provided following this text.
Zone-level sizing has been “Zone-level auto-sizing has been
completed and completed and sized values have been
assigned/updated (auto or assigned to components and controllers
manual). in the HVAC network.”
Zone-level sizing or Zone- and “Zone-level autosizing or zone- and then
then System-level sizing has system-level autosizing have been
been completed but not completed, but sized values have not
assigned/updated either been assigned either automatically (via
automatically or manually. the ASHRAE Loads interface) or
manually.”
Zone-level sizing has been “Zone-level sizing completed, but revised
completed & assigned, but data associated with subsequent user
subsequent edits have not been edits has not been assigned. System-level
applied to the components sizing, if previously completed, will need
and/or controllers. to be re-run to account for changes.”
System-level sizing completed, “System-level autosizing have been
but zone-level sizing for this completed and applied, but zone level
system has not been completed autosizing has not.”
(e.g., if intentionally set up and
sized manually at zone level,
then auto-sized only at system
level for coils, fans, and plant
equipment/loops).
Autosizing at zone and system “Both zone- and system-level auto-sizing
level have been completed and have been completed and sized values
values assigned to components assigned to components and controllers
and controllers. in the HVAC network.”
3.2 System Parameters dialogs
The System Parameters dialog displays data applying to both system level and zone level.
A few basis system-level parameters, including the system name, option to autosize the system, fundamental
type of configuration, variable-air-volume (VAV) vs. constant-air-volume (CAV), edit mode, current layer, access
to the Edit Multiplex dialog, and a toggle for IP vs SI units are provided at the top of the dialog so as to remain
visible and accessible whenever the dialog is open.
The tabbed middle section provides access to most user inputs, options, and autosized or derived values. The
remainder of this user guide is dedicated mainly to describing each of these in detail.
Text color is used to indicate values that are from Room Data (magenta), will be directly autosized (light blue),
have been autosized (green), edited and differ from the same parameter on other layers (orange), or are in
error and must be addressed (red). These colors can be customized via the ApacheHVAC Preferences dialog.
Conditional formatting is used to highlight certain fields containing values that will significantly influence the
system minimum outside air or that may bring into question the system capability to provide this at all times.
The bottom section provides access to the Zones Tabular Edit dialog described below (also accessible via the
toolbar), along with copy & paste functions to copy all data for a tab from one layer to another, two save
options for saving edits without applying them, and ‘Assign’, which applies values to the components and
controls on the associated system network.
3.3 Tabbed sections for System Parameters and Zones Tabular Edit dialogs
Zones Tabular Edit is a customizable spreadsheet-like dialog for viewing and editing all parameters from the
System Parameters dialog (excepting only systems Schedules) for all zones on the system in a single view. This
is also the means by which data can be exported for documentation or manipulation in spreadsheets, etc., and
can be imported specifically with respect to editable columns of data.
Fields or ‘cells’ for select zone-level parameters use conditional formatting color scheme to draw attention to
the zones that are driving system minimum ventilation rates or to draw attention to a value that may be of
concern, but which is not strictly speaking in error.
Both the System Parameters dialog and its counterpart, the Zones Tabular Edit dialog, are organized with tabs
for system- and zone-level parameters. These are more or less the same tabs and provide access to all of the
same parameters; however, the Zones Tabular Edit dialog excludes the system-level ‘Schedules’ tab, subdivides
some of the tabs to make the number of default columns more manageable, and places ‘Loads Data’ first.
System Parameters dialog tabs (fixed): Zones Tabular Edit dialog tabs (customizable):
 Schedules  Loads Data
 System Parameters  System Parameters
 Zone Temp, Humidity & Equipment  Zone Temp, Humidity & Equipment
 Zone Ventilation & Exhaust  OA Ventilation
 Zone Loads & Supply Airflows  Air Changes & Exhaust
 Zone Airflows, Turndown & Engineering  Cooling Airflows
Checks  Heating Airflows
 Zone Design Airflows
 Engineering Checks
3.4 System Parameter interface toolbar buttons

Toolbar buttons for ‘System Parameters’, ‘Zones Tabular Edit’, and ‘Global System Parameters Assignment’
are the 2nd, 3rd, and 4th buttons on the system sizing section of the ApacheHVAC toolbar shown below:

The first two simply open the System Parameters and Zones Tabular Edit dialogs, as described elsewhere. The
‘Global System Parameters Assignment’ simultaneously assigns values from system parameters dialogs for all
HVAC networks in the currently open ApacheHVAC file to the components and controllers in those networks.
3.5 System Parameter Links
Each parameter in the dialogs is either coupled directly to one or more components or controllers or is used in
a calculation within the dialog—i.e., to derive a value for a component or controller. The coupling is provided
by unique system parameter links that are set with the individual component and controller edit dialogs.
System parameter links couple each

unique component and controller
application to a set of values in the
System Parameters dialog.
The alpha-numeric prefixes in
component and controller Reference
field previously used to connect to
the Loads Data spreadsheets are no
longer necessary; where these do
remain in place, they are for user
reference only.
Selecting a particular link within a component or controller determines which values will be assigned to it from
the System Parameters dialog. Changing the link or clicking ‘Re-apply’ immediately refreshes the linked values.
The list of available links is context-specific, with its content determined by the component or controller type
and, in the case of controllers, by the ‘Controlled variable’ selection in the controller dialog.
VE 2016 ApacheHVAC User Guide part A: Overview and fundamentals 41

In the System Parameters dialog, parameters are grayed out and disabled when the required link or links are
not present within the system frame. Hovering over any parameter that is disabled for this reason provides a
ToolTip listing the required links and type of component or controller that they apply to. If a parameter is
disabled and there is no such ToolTip, this is because the parameter must be enabled by other means (a
checkbox in the dialog, a particular system configuration, or another parameter upon which it depends).
For all prototype systems from the HVAC library, these links are pre-set; however, they can be changed if
needed and can be set as desired when adding a new component or control. It is acceptable to completely
revise any pre-defined managed system to set up a fully custom system using the links as desired; however, it
is recommended that you start with existing prototype system of similar configuration both as an illustrative
example and to minimize the additional time and effort required to build the system from scratch.
To facilitate use of the System Parameters dialog for editing of component-level values for an HVAC network,
HVAC zone components and all other associated zone-level components and controllers within a managed
system must be contained in a multiplex, as shown above.
3.5.1 Overriding linked values

Data can still be directly edited at component level via individual component and controller dialogs, overriding
settings passed down from the associated system parameters dialog. This may be necessary for departures
from system prototypes or to edit parameters not included/editable within the System Parameters dialog.
Direct component-level edits to any parameters that are editable in the System Parameters dialog will be
overwritten by subsequent ‘Assign’ operations in System Parameters dialog.
Setting the system parameter link to ‘None <Select>’ will preserve any user edits of this nature, preventing
them from being overwritten. Selecting any system parameter link or retaining the default link and clicking the
‘Re-apply’ button will override component-level edits.

3.5.2 System Parameter Links – Complete listing
Where links are active, clicking ‘Re-apply’ will refresh the linked values within the component or controller
dialog, turning them green to indicate that they have been passed down from the System Parameters dialog. A
small fraction of the available links, such as those for Room/Zone components, will not be coupled to any data
until associated features and capabilities are added in a subsequent release. Until then, they function only as
an informative label for the component or controller. Additional links will be added over time, as part of the
evolution of the complete System Parameters interface.
COMPONENTS
Fans Filter Dampers
None <Select> None <Select> None <Select>
Supply fan Filter pressure & change Outside air min + econ
Supply fan – TSP addition Outside air no min econ
Return/Relief fan Outside air fixed min
Exhaust fan Outside air variable min
FCU fan Energy recovery bypass
FPB fan Heat-pipe/RR/whl bypass
Package terminal unit fan Zone mixing box damper
Unit heater fan
Duct heat gain/loss Heating coils Cooling coils

SA duct heat loss/gain AHU pre-heat coil AHU cooling coil
RA duct heat loss/gain AHU heating coil FCU/act-beam cool coil
Zone reheat coil PTAC/PTHP cooling coil
FCU/act-beam heat coil UCS cooling coil
PTAC/PTHP heating coil
Elec heat coil 2nd stage
Heat/enthalpy exchangers Moisture addition/evaporative cooling Thermal battery

Energy recovery HX/wheel Steam humidifier DOAS/AHU cooling device
Heat-pipe/Run-Rnd/wheel Direct-evap/spray Zone cooling device
Indirect-evap/spray
Room or Zone component Room or Zone without air supply

None <Select> None <Select>
Occupied zone (default) Occupied zone (default)
Thermally stratified zone Heated/cooled slab zone
SA/UFAD plenum
Return Air (RA) plenum
Adjacent room w EA fan

INDEPENDENT CONTROLLER WITH SENSOR
Flow Rate Dry-bulb Temperature Relative Humidity
Cooling airflow VAV/CAV OA econ target & DBT limit Indirect-evap cooling
Heating airflow VAV/CAV OA econ target reset Direct-evap cooling
DOAS vent airflow CAV/DCV ER bypass temp target Evap/spray humid per Zn RH
FCU Cooling airflow CAV/2sp/VAV ER target – cool mode Steam humid per Zn RH
FCU Heating airflow CAV/2sp/VAV ER target – heat mode
FPB Primary airflow CAV/VAV ER target – PSZ heat-cool
FPB Secondary airflow CAV/2sp/VAV ER bypass temp target -- PSZ
Act bm/IU Primary air CAV/VAV cool Zone mixing variable DBT target
Act bm/IU Primary air CAV/VAV heat Cooling coil – AHU cool LAT
Act beam/IU Induced airflow Cooling coil – AHU dehum LAT
DOAS PTAC/PTHP Cooling airflow
Cool coil – AHU extend dehum LAT
CAV/2sp/VAV
DOAS PTAC/PTHP Heating airflow
Cooling coil – AHU supply air DPT
CAV/2sp/VAV
Dual-fan-dual duct zn heat airflow Heating coil – min SAT w reset
PSZ Cooling airflow CAV/2sp/VAV Cooling coil – DOAS tempering
PSZ Heating airflow CAV/2sp/VAV Cooling coil – zone variable LAT
PTAC/PTHP cool airflow CAV/2sp/VAV Cooling coil – full cooling LAT band
PTAC/PTHP heat airflow CAV/2sp/VAV Cooling coil – full dehum LAT band
UCS Cooling airflow Heating coil – full heating LAT band
Cooling-only sys airflow Cooling coil – full h/c LAT band
Heating-only sys airflow Cooling coil – full h/c/dehum LAT
Zone DCV stage1 – VAV ctrl Heating coil – full h/c LAT band
OA min reset - Occupied zone CO2 Heating coil – zn fix LAT stage 1
Stratified zn re-mix airflow Heating coil – zn fix LAT stage 2
Wet-bulb Temperature Dewpoint Temperature Percentage Flow
OA variable min %
OA min reset - zone CO2
OA min reset - zn VAV flow %
OA min reset - Occupied zn
VAV%
OA min reset - Unocc zn VAV%
Zone mixing % primary air
Heat Transfer Moisture Input Enthalpy

INDEPENDENT TIME SWITCH
Flow Rate Dry-bulb Temperature Relative Humidity
DOAS vent airflow HP/RRcoil/wheel bypass temp Evap/spray humid SA RH
CAV airflow – occupied hours RA bypass mixed-air target temp Steam humid SA RH
CAV airflow – nighttime setback Zone mixing fixed DBT damper target
Min fan airflow Pre-heat coil – AHU min EAT
Zone/RA transfer airflow Heating coil – AHU min SAT
Exhaust/CV hood airflow Heating coil – zone variable LAT
Exhaust driven ventilation airflow Heating coil – DOAS tempering
OA min reset - Unocc zone Cooling coil – zone fixed LAT
Heating coil – zone fixed LAT
Wet-bulb Temperature Dew-point Temperature Percentage Flow
Cooling coil – coil leaving DPT EA% (vs. return or transfer)
EA% available to Energy
Recovery
RA% to alt path or zone
OA fixed %
Heat Transfer Moisture Input Enthalpy

3.6 System Prototypes & Sizing workflow navigator
The System Prototypes & Sizing Navigator walks users through the process of ApacheHVAC system setup
and sizing. It firstly facilitates acquiring useful templates, profiles, fuel codes, and other data from a
‘prototype data model’ data. All aspects of this required for use with prototype HVAC systems is also
automatically acquired when loading a prototype systems from the HVAC library.
Users can place their own ‘prototype data model’ in the folder accessed by this navigator as means of
efficiently loading templates, profiles, fuel codes, and other data from a custom ‘prototype’ model.
The System Prototypes & Sizing Navigator also walks users through loading selected prototype systems
from the library into an ApacheHVAC file named proposed.asp; assigning rooms/zones to the systems;
entering schedules of operation, temperature control setpoints, setback control strategies; accessing the
System Parameters dialog to further configure system options and other design parameters; autosizing
the systems and zone level and then at system level; and finally generating and viewing sizing reports. As
with all other VE workflow navigators, this navigator supports entering notes for later reference as well as
tracking the completion of each step.
Beyond the initial data acquisition step, the System Prototypes & Sizing Navigator is in effect like stepping
through the HVAC library and system parameters and sizing toolbar buttons in ApacheHVAC:

System Prototypes & Sizing Navigator provides a two-stage (room/zone level then system/plant level)
autosizing process that includes tools for calculating ASHRAE 62.1 ventilation rates, numerous
opportunities for user intervention, and ultimately system sizing reports. System performance can then
be analyzed using the full array of VE simulation tools. Pre-defined systems can also be further modified in
ApacheHVAC and resized at one or both levels, as needed. This facilitates more efficient exploration and
comparison of system alternatives in all stages of design.
Figure 3-1: System Prototypes & Sizing Navigator

3.6.1 System Prototypes & Sizing workflow summary
The navigators provide a step-by-step process to guide users through system setup, load calculations,
sizing, and generating system sizing reports in preparation for simulation. The summary of this process
below is followed by more detailed descriptions of each step.
 Acquire prototype data: This step loads the blank Loads Data spreadsheet, HVAC profiles, and
other essential data into the project. This also includes non-essential data, such as example
thermal templates with internal gains for office spaces and restrooms, profiles for daylight
dimming and natural ventilation, and grouping schemes for model spaces. Users that prefer to
load only the essential items can select the System_prototypes_only.mit data model.
 Model preparation: Having defined internal gains, assigned constructions, and selected design
weather data, the user sets up room or zone groups in Model-IT, using a grouping scheme that
organizes spaces in the model according to the systems that will serve them. Grouping spaces
according to system assignment is the key to efficient addition and assignment of zones to
systems in ApacheHVAC.
 Assign rooms/zones: This step simply provides informational instruction regarding the use of
the Edit Multiplex facility in ApacheHVAC to assign rooms or zones from groups in the model
to particular systems. This is meant to emphasize the value of grouping spaces according to
system assignment prior to loading and setting up systems in ApacheHVAC.
 Prototype system: Clicking this link opens a blank ApacheHVAC file named “proposed.asp” and
launches the library of detailed prototype HVAC system models to choose from. This is
required for the zone-level sizing process through v6.4 (in v6.5 and onward, the user simply
selects a target system at the zone level the same as for the system level).
 System Schedules & Setpoints: This dialog provides inputs for system operating schedules and
set points in terms of occupied and unoccupied times, setback temperatures, start-up and
post-occupancy space conditioning, and system operating schemes for unoccupied hours. It
includes a facility for generating an alternate set of these inputs that can be separately applied
to specific zones and systems. The SYS profiles linked to this dialog are also used for checking
unmet load hours (via Range Check in Vista Results for any project; included in 90.1 PRM
Navigator reports).
 System Parameters: System- and zone-level parameters, such as zone heating and cooling
load oversizing factors, air-handler coil leaving-air-temperature settings, operation as a 100%
outside-air system, inclusion of energy recovery, and related inputs can be changed using the
 Room/zone-level load calculations: This link initiates zone-level loads calculation using the
ASHRAE heat-balance method to determine heating and cooling loads. This is quasi-dynamic
with respect to heating loads (the outdoor design temperature is held constant) and fully
dynamic with respect to cooling loads (i.e., outdoor temperatures, solar loads, internal gains
all vary as they would in a dynamic thermal and energy simulation). Loads are for an “ideal”
system that meets the space temperature setpoints under all conditions. If it is not yet present
in the project, a separate copy of the Loads Data spreadsheet will be generated for each
system in the “proposed.asp” file (or in the current open ApacheHVAC file for v6.5) and saved
within the project directory. The system-specific spreadsheets are auto-populated with zone
heating and cooling loads and data on setpoints, zone volumes, ventilation, rates, and so forth.
 Assign system parameters room/zone-level sizing data: This assigns component and
controller inputs from the System Parameters interface to their respective ApacheHVAC
systems in the “proposed.asp” file (or the selected target file in v6.5 and onward). The
additional inputs and settings available within the System Parameters dialog for each system

are optional, and the assignment of values from the System Parameters dialog to the
components and controllers is automatically completed at the end of each zone and system-
level sizing run (assuming the ‘Update ApacheHVAC zone/system autosizing’ checkbox in
ASHRAE Loads remains ticked as it is by default). Therefore, this step is necessary only if edits
have be made in the System Parameters dialog, and if so can be completed by clicking the
‘Assign’ button in that dialog immediately following the edits.
The user can repeatedly re-size systems after changes to the building model. So long as
individual autosized values are manually overridden within the System Parameters dialog,
these overrides can be maintained in future sizing runs and sizing data assignments.
The user is free, as always, to manually edit component and controller parameters and inputs
within ApacheHVAC. While appropriate knowledge and experience are highly recommended,
system, component, and controller configurations can also be substantially modified without
breaking the overall system autosizing functionality.
See ‘System Parameter Links’ for more information regarding the coupling of components and
controllers on a system airside network with the System Parameters dialog.
 System/plant loads calculation and sizing: The fully detailed system(s) within the selected
ApacheHVAC file are run in a dynamic simulation of the model under the selected design day
conditions (steady state OA temperature for heating loads and typically sinusoidal variation, as
in ASHRAE design weather data, for multiple cooling design days). The system operates within
the bounds of current zone-level sizing for airflow controls, coil leaving temperatures, etc. to
meet design loads. This step records system loads data for reports and updates the selected
ApacheHVAC file with respect to fan airflows, coil capacities (and sizing conditions for
advanced coils), water loops capacities, and capacities for all heating and cooling equipment.
 Sizing reports: The action generates and displays reports for system-level sizing runs. These
reports list equipment loads (excluding equipment oversizing factors entered in ApacheHVAC)
as seen by the equipment at the peak design conditions. When Detailed room loads is ticked
within the Report preferences dialog in Vista Results, the reports include details of room/zone
loads, conditions, and airflows, as well as basic engineering checks.
 ASHRAE 62.1 report: This action opens a report of ventilation rates and indicates whether
these meet or exceed ASHRAE 62.1 requirements (this requires selection of appropriate space
occupancy types in the 62.1 Calcs tab of the Loads Data spreadsheet or via the PRM navigator).
Finally, the user returns to the ApacheThermal view to simulate the building and systems. Whether in
system-level autosizing or subsequent simulation for thermal comfort and energy analyses, there is
interaction between the building zone loads (outdoor conditions, solar gain, room air nodes, surface
temperatures, constructions, and internal gains), detailed solar calculations (if SunCast has been run),
detailed daylighting data for sensors placed in the spaces (when RadianceIES sensors have been set up),
bulk-airflow modeling of natural ventilation (when MacroFlo openings are included), and ApacheHVAC
systems at each simulation time step. Time steps can be anywhere from 30 minutes for rough initial runs
down to 1 minute for detailed analyses, with 6 minutes recommended for final runs in most projects.
Simulations can be carried out for the entire building project or just a small subset of it, as might be
desirable when setting up and optimizing system configurations and zone-level controls. Having optimized
the system using a small number of select zones and select dates or conditions from the simulation
weather file, the user can assign additional zones to the ApacheHVAC systems, repeat the zone-level
sizing run, and then perform system-level sizing for coil loads, plant equipment, and so forth. Because
systems within ApacheHVAC are created or modified independently of the thermal model, the VE allows
users to create multiple systems that can be run with same the thermal model in Apache Sim.

4 Library
The Library facility has been designed to give the user complete control over import/export operations,
covering any element(s) of an ApacheHVAC file (network components, plant components, profiles…).
It supersedes previous import-only facilities which were limited to ASHRAE 90.1 PRM baseline systems
and variants thereof (“Prototype systems”), sharing a single common set of plant equipment and profiles.
4.1 Import from library

The Import from library button on the toolbar brings up the Import Systems dialog, as below.
The tree hierarchy consists of the following folders, in order:

 Prototype systems – standard, fully autosizable (See Section 8)

 Prototype systems – advanced, partially autosizable (See Section 8)
 User exported systems – Local User-defined hierarchy of folders and files in a central location on
this computer, populated by previous usage of the standard Export facility (Section 5.2).
 User exported systems – Any There are two possibilities here:
- The user can browse to an .asp anywhere on their computer or connected LAN, if any.
- Below this is a list of all .asp files that have been previously exported (by this computer) to
“Any” location (Section 5.2).
 Simplified systems These are the same as the legacy Wizard systems (Section 5.3) but with a 1-
layer multiplex (unassigned) instead of the zone replication facility. Multiplexes are (in network
terms) equivalent to replicated zones, but provide much extra functionality (see Section 6).
 90.1 PRM Baseline systems (See Section 8)
 Prototype equip, profiles, fuel codes only This provides only the plant equipment, profiles and
fuels referenced by all PRM Baseline systems and Prototype systems. No network objects.
 Folders containing systems tailored to specific methods or rating systems, other than PRM: for
example GreenMark (Singapore). The relevant help facility may have guidance on their use.
In both “User exported systems” folders, only .asp files that can be opened by the current <VE> version
will be listed.
As you select each file in the tree in turn, the displayed Network diagram and Description text will both
update. The Network diagram can also be zoomed in or out, or fitted to view using the three buttons at
top left.
For placing the imported network within the current open network, two methods are available as follows.
If Stay in dialog is left unchecked, the Import button will close the dialog and provide the user with a
floating image of the import which they must anchor anywhere in the canvas by clicking at a valid
location. Alternatively, the placement functionality available in previous releases can be replicated by
checking Stay in dialog then using the (now enabled) arrows to select automatic placement by the Import
button either to the right of, or below, all existing network objects.
When staying in dialog, the Exit button is used to close the dialog.
There is an optional checkbox Show at startup to have the Import library dialog always shown at the start
of each ApacheHVAC session, in a similar fashion to the ApacheHVAC wizard in earlier releases.
4.1.1 Import options

The Import options tab is shown below.

For each non-network element of the selected file you have complete control over how, or whether, it is
imported.
For plant equipment there are two types of control, firstly on object comparisons and secondly on
presence or usage of objects.
4.1.1.1 Object comparison

When comparing objects in the proposed import file (or “source”) against those in the currently open file
(or “target”), you may match on either unique ID only, or on all content data. In this context “content
data” will include profiles, and data within any linked objects. (Exception: Heat recovery providers (cooling
plant) compare only the names of the Recipients (heating plant), not their data).
You would prefer to match on ID when importing between two files that are known to have common
plant (in particular the PRM baseline systems and Prototype systems based on them) and you want to
guarantee no duplication, even if any plant in the source file has been autosized, or otherwise has
modified content.
Note: plant IDs are an internal concept only, and are not visible anywhere in the user interface. They
should be thought of simply as a way of addressing a set of systems with common plant, such as the
installed PRM Baseline systems and Prototype systems.

You would prefer to match on Content when the target and source files are known to have different plant
data (in particular, as a result of previous autosizing on either or both sides), and you wish to preserve
this. Another scenario would be where the origin (and hence IDs) of the plant data are either non-
standard or unknown.
The default object comparisons are as follows:
 for all pre-installed systems: Match on ID
 for user-exported systems (either Local or Any): Match on Content
4.1.1.2 Presence or usage

The options None / Unique / Referenced / All function, in conjunction with the currently set Matching
rule, as follows and listed in order of increasing inclusivity:
 None: No plant of this type will be imported.

 Unique: Only referenced plant of this type which is unique (under current Matching rule) to the
source file will be imported.
 Referenced : All plant of this type which is referenced by objects in the source file will be
imported. Any that Match plant in the target file will be duplicated.
 All: All plant of this type in the source file will be imported. Any that Match plant in the target
filewill be duplicated.
Note 1: Unique is the only option which may demand plant reassignment in imported network objects, in
order to pick up the appropriate plant items already present in the target file.
Note 2: The numbers “(1)”, “(2)” etc will be added to any imported Reference where this is necessary to
avoid duplication of References in the final network.
Note 3: The Heat source assignment to DHW (if any) in the target file is not modifiable by an Import
operation, therefore the DHW assignment (if any) in an imported Heat source will be automatically
removed and the user informed.
The default presence/usage options, listed below, are intended to facilitate the import of needed
plant/equipment items while avoiding unwanted duplicates:
 When the first library system is imported to empty HVAC file, the default import option = All
 When any subsequent installed system is imported into a non-empty file, the default = None,
only if no extra required/referenced equipment is present; if not, the default = Referenced
 When any subsequent User-defined system is imported, the default import option = Unique
On either selecting any None option, or changing the selected network while None option(s) are selected:
if one or more of the None options would produce an invalid network after the import, the Import button
is disabled and a checkbox with red warning text is exposed. The user must check this checkbox to enable
the Import button, thereby showing that they understand that the resulting network will be invalid.

A note for upgraders regarding the two previous v6.4.0.5 options for importing into non-empty networks:
“Duplicate heating/cooling plant” ON in v6.4.0.5 equates to Match ID / All in VE2012 onwards.

“Duplicate heating/cooling plant” OFF in v6.4.0.5 equates to Match ID / None in VE2012 onwards.
4.1.1.3 Profiles options

The options for merging profiles build on the previously available functionality, in that the Prototype /
PRM profiles are still distinctly labeled as such. These are the profiles required by, and are the default
option for, all the installed systems, with the exception of the Simplified systems.
For Simplified systems and all User-exported systems, the default Profile option is None.
The user can export profiles with a system (see 5.2), and the option Profiles exported with this Library
system is available to merge these when re-importing that system.
The final profiles option Other project folder allows the user to browse to any project folder (at the .mit
level) and that project’s profiles will be merged in the same way as they would be through the Building
Template Manager. Note: when the import is via User Exported systems – Any, and the browsed folder
is a project folder containing profiles, then this folder will be automatically copied to the profile option
Other project folder.
4.1.1.4 Fuel type options

The options for setting (NB: not merging) fuel types build on the previously available functionality, in that
the PRM energy end-use categories are still distinctly labeled as such. These are required by, and are the
default option for, all the installed systems, with the exception of the Simplified systems.
For Simplified systems and all User-exported systems, the default Fuel type option is None.
The user can export fuel types with a system (see 5.2), and the option Fuel types exported with this
Library system is available to set these when re-importing that system.
The final profiles option Other project folder allows the user to browse to any project folder (at the .mit
level) and that project’s fuel types will be imported. Note: when the import is via User Exported systems
– Any, and the browsed folder is a project folder containing fuel types, then this folder will be
automatically copied to the profile option Other project folder.

4.2 Export to library
The Export to library button on the toolbar brings up the Export dialog, as below.
Note that (by default) the Network diagram shows only those network objects that were selected prior to
initiation of the Export. This can be changed to None or All on the Options tab, see 5.2.1.
When first exporting to the Local hierarchy, a folder must be created by entering its name in the field next
to New Library then clicking the button. This new folder becomes the selected export destination folder.
If desired later, any number of additional folders and sub-folders can be created by use of New Library.
When exporting to the Any destination, click in the tree to browse to any folder on the current machine
or LAN (if any). New Library will change to Folder: and the OK’ed folder will be echoed here.
Filename and Description are both compulsory, as indicated by red asterisks. The Filename must be
unique within the currently selected destination folder. When the following three conditions hold:
 A Local destination folder has been selected or Any folder has been browsed to

 A valid filename has been entered
 Description text has been entered
the Export button becomes enabled. This button performs the export operation and also closes the
dialog.
4.2.1 Export options
When Include profiles is checked, the project’s current profiles will be exported.
When Include fuels is checked, the project’s current fuel codes will be exported.
The Plant options define how each of the seven distinct plant equipment types will be exported.
 None: No plant of this type will be exported. (Note: such a file is not valid on its own).
 Ref’d (default): Export all plant of this type which is referenced by those objects to be exported.
 All: Export all plant of this type.

5 Multiplexing HVAC System Networks
Multiplexing allows users to more efficiently create, populate, modify, and edit large ApacheHVAC
networks, considerably reducing the project workload. Multiplexing gives users the ability to condense
any ApacheHVAC network to a more manageable format.
Multiplex Toolbar
The multiplex feature can be used on a total system level, just at the zone level, or for nearly any other
subset of a system (see rules for multiplexes, below). The example below is a 4-zone network with fan-coil
units for each zone and a common outside air system. Figure 5-1 shows the network setup without the
multiplex feature; Figure 5-2 shows the equivalent multiplexed network.
Figure 5-1: Non-multiplexed ApacheHVAC network
Figure 5-2: Equivalent ApacheHVAC network with Multiplex. The image on the right is depicting the
additional layers that are effectively hidden “under” the currently selected Display Layer.

5.1.1 Multiplex Toolbar
The multiplex toolbar is active when any component or controller in a multiplex is selected.
5.1.1.1 Create Multiplex

This button opens the Create Multiplex dialog. This is used to add or remove layers, assign principal rooms
or zones.
5.1.1.2 Edit Multiplex

This button opens the Edit Multiplex dialog. This is used to add or remove layers, assign principal rooms or
zones, and select layers for editing in the same way as the Create Multiplex dialog described earlier.
5.1.1.3 Edit Mode

Choose between Local or Global Editing.
Local Edit Mode – edits apply only to the current ‘Display Layer’.
Global Edit Mode – edits apply to ‘All selected layers’, as shown in the Create/Edit multiplex dialog and on
the multiplex toolbar.
5.1.1.4 Number of layers selected

This field displays the number of layers currently selected for edit as a subset of the number of layers in
the multiplex—e.g., “6 of 43” means six of the 43 total layers in the multiplex are selected for editing.
5.1.1.5 Display Layer

The currently active layer is displayed by and can be chosen via this dropdown selector. It is identified by
layer number and name of the assigned principal room. It is the editable layer in ‘Local Edit’ (Current
layer) edit mode. It is also the layer that will be viewed and serves as the interface in ‘Global Edit’ (All
selected layers) edit mode, prior to entering a Data Table component edit or the Zones Tabular Edit view.
Use the up and down arrow buttons to move to the next layer on the list or expand the dropdown to
select a layer from the list.
The current display layer can be changed while a room, component, or controller dialog is active, and the
contents of that dialog will update to reflect the newly selected layer.
5.2 Creating a Multiplex – Overview
A multiplex is created by selecting the Multiplex button in the main toolbar & dragging the green
multiplex box from the bottom left to the top right corner of the desired multiplex region. Rules for
multiplexes and multiplexed controllers are provided below, following the illustration of basic steps.

Step 1: Position the green multiplex box at the bottom left corner of the area of network that you wish to
multiplex.
Step 2: Holding down the left mouse button drag the green multiplex box from the bottom left to the top
right of the desired multiplex region and release the button.

Step 3: Once the rectangular boundary for the multiplex region of the system has been dragged over the network
components, the Create Multiplex dialog will appear.
Rooms or zones in the model are assigned to multiplex layers either by adding layers and manually selecting the spaces
from the Principal Room drop-down list on each layer or by using the “Assign from Room Group” feature. These are
described in more detail under Create Multiplex, below.

Step 4: Once a multiplex has been created, the network components and controllers can be populated with input values
appropriate to the zones and desired control functions on each layer. Calculated flow rates, set points, cooling coil
capacities, reference formula profiles, etc. can be entered into the network controllers layer by layer (Local editing), in all
currently selected layers (Global editing), or pasted from a spreadsheet into a range of selected layers via a tabular Data
Table edit view (Global editing). For autosizing of values within multiplexed components and controllers, see the System
Prototypes & Sizing section of this User Guide.

5.2.1 Rules for Multiplexes and controllers within them
When defining the multiplex region, some rules must be followed:

 The multiplexed region of the network must contain at least one room component.
 A multiplex boundary must not abut or overlap an existing multiplex.
 It must satisfy the rules for controllers in a multiplex, as follows;
1. A controller is in a multiplex if its control box is inside the multiplex boundary.
2. Any controller outside a multiplex may only sense or control non-multiplexed nodes.
3. A controller inside a multiplex can sense and control any nodes inside or outside the multiplex.
4. A controller inside a multiplex may not sense and control nodes in another multiplex.
5. AND or OR connections cannot connect a controller in one multiplex to a controller in another
multiplex.
 A multiplex must not contain any sections of a network that consist only of connectors (see Figure 5-3
below).
 Any connection between multiplexes must contain at least one component or junction so that nodes can
be generated (see Figure 6-3 below).
Figure 5-3: Disallowed use of connector segments through a multiplex and between multiplexes
Figure 5-3 provides examples of network branches consisting solely of connecting segments that are not
permitted within a multiplex. In cases such as that shown on the left, either re-route the connectors
around the anticipated multiplex region or move the controller box downwards so that the multiplex with
not overlap the upper path. Direct connections between multiplexes consisting solely of connecting
segments (straight or elbow), such as illustrated on the right-hand side of this figure, are not permitted. The
network must be revised so that there is a junction or other component between the multiplexes.
Note: It will be common to have multiple-layer instances of a controller pointing to one component
control node. In such cases, the controller will “compete” for or “vote” on the value of the controlled
variable at every simulation time step. The value that prevails depends upon the controlled variable and
type of component being controlled. For example, while the highest temperature will prevail in the case
of a heating coil, the lowest temperature will prevail for a cooling coil.

Warning: Where multiple airflow controls are present on one branch, these must all point to the same
node if their operation will ever compete for control. An attempt to simultaneously control airflow from
two different nodes on a single branch will result in an over-constrained flow.
5.3 Create Multiplex

When a new multiplex is created by defining its boundary, the Create Multiplex dialog is displayed. The
name and description of the multiplex, the number of layers contained in the multiplex, and the principal
room assignment to each layer are entered here.
Figure 5-4: Create Multiplex dialog shown as seen prior to adding any layers or zones.
5.3.1 Description
Enter a name and description here to identify the multiplex and manage complex systems.
5.3.2 Layers
A principal room or zone is assigned to each layer. This can be done for an individual layer via the
dropdown selector in the Principal Room/Zone column on any layer row.

Assign from Room Group, as described the section dedicated to that below, is the most efficient way to
add and populate the correct number of layers in a system multiplex with a single action.
Alternatively, select the number of layers to be added to or inserted into the multiplex and click Insert
Layers (new layers are inserted at the selected layer) or Add Layers (layers are appended to the bottom of
the list).
Select layers then click Delete Layers to remove them from the list (note: it is not possible to delete all
layers from a multiplex, but all room/zone assignments can be removed).
The Ctrl and Shift keys are used to add or remove individual layers to or from the current selection set
and to hold the view from scrolling when there are more layers than can be viewed at once.
5.4 Prototype layers
A facility has been provided within the Multiplex Edit dialog for tagging layers of a multiplex as prototype
layers.

The purpose of prototype layers is to provide a means for selected layers of a multiplex to form the basis of a
standard or custom system prototype. In this context a prototype layer represents a kind of template for a
particular type of layer when the prototype is imported to create a system, or when a system is copied on the
ApacheHVAC canvas prior to being populated with a similar range of space (e.g., in another wing of the same
building). Examples of prototype layers for a hospital are ‘Office’, ‘Patient room’, ‘Short stay’, and ‘Operating
theatre’. Generally, prototype layers will be most useful for large projects wherein there are many spaces in
the same functional or occupancy category that will tend to share a significant number of settings within the
Prototype layers are labeled on the multiplex layers list so they can be readily located. They function as
ordinary layers as well as having special functions with respect to parent-child relationships (initially with
respect content when a child copy is made, and thereafter in name only), layer filtering (according to the
parent name), and semi-protected status within the multiplex.
5.4.1 Layer type
Clicking on the ‘Layer type’ dropdown selector on any layer row in the Multiplex Edit dialog opens a
nested dialog for
Any layer can be designated as a prototype layer. If it was created as a child of an existing prototype layer,
the association with the source layer will be decoupled when its type is changed from child to prototype.
When designated as a prototype layer, a name for the prototype (e.g., “Conference room”) will be
required.
New layers can be created as a copy or child of any selected prototype layer. Any layer created as a copy
of the prototype will retain reference to the source prototype layer by name for sorting and selection
purposes, not related data content of the layer). A child layer created as a copy of a prototype will, just as
with a copy of any layer, initially share all data and settings for the source layer within the System
Parameters interface, excepting the Room of Zone assigned to the source layer. The child will retain this
data only until edited. There is no persistent parent-child link with respect to data.

Mechanisms are provided for designating any multiplex layer as a prototype layer, and for removing this
designation (see the Layer Type column in screen captures above and mechanism within drop-down
selectors in that column shown in screen captures below):
 Prototype layer {designating a layer as a prototype flags as such and allows the user to give it a
name}
 Prototype child {designating a layer as a child provides means of selecting any currently defined
prototype layer in the multiplex as the parent with which it will be associated—essentially just
adding it to a selection and sorting group.}
 Standard layer {this default state indicated by a simple double dash “–“ breaks association of a child
with a parent layer or removes the designation if it was a prototype. De-prototyping a layer should
clear the prototype name and child designation from all associated child layers.
Adding Layers as children (copies) of a Prototype Layer:
 Copying a prototype layer (which has either been imported with the system prototype or created
subsequently) causes the new layer to reference the prototype layer from which it was created.
 All components, controls, and current data associated with these will be copied, as usual, from the
parent Prototype Layer to all Child Layers made from it. There will, however, be no linking of any
content or data between layers: once created, editing of the parent or child will not affect the other.
 Deleting a prototype layer deletes all references to that layer.
The child of the prototype references the name of the parent prototype layer in uneditable text so that
one can tell which parent it was created from. Once the copy has been made, it will share only this linked
prototype name for the purpose of identification and selection and the parent-child relationship.
5.4.2 Sorting by Layer Type

Clicking the “Layer Type” column heading sorts all rows according to the names of the prototypes and
their children.
5.4.3 Select same prototype layers

This selects all layers—parent and children—sharing the same prototype layer name. This function is
available when current selection is a single prototype layer or includes only children of a single prototype.
5.4.4 Hide non-selected layers

Whether selected in relation to a prototype layer or otherwise, this hides all non-selected layers. In the
context of prototype layers, this is useful as means of selecting all layers of the same time and then hiding
others to aid in navigating a long list of multiplex layers.
5.4.5 Collapse to prototype layers

Collapse to prototype layers is special one-time operation for each HVAC network on par with de-
prototyping a prototype system. This is equivalent to opening the Edit Multiplex dialog and clicking Select
all non-prototype layers, then clicking Delete. Therefore, this operation is generally intended for use on a
copy of an HVAC network that is to be firstly collapsed to just the prototype layers, and then re-populated
with a new set of zones using the prototype layers to reduce setup time required for the newly added
spaces.

When collapsing a system to prototype layers only, you have the option to keep the zone assignments for
those layers (the prototype layers that will be retained), or to re-set them to unassigned or empty layers.
5.4.6 Add, Insert, and Copy with respect to prototype layers

The combined effect of the three radio-button options and the Add, Insert, and Copy buttons is best
described via the matrix of operations and outcomes below:
Radio buttons Add Layers button Insert Layers button Copy Layers button
Determines New layer(s) appended to end New layer(s) inserted just New layer(s) appended
type of new of layers list; number of layers above first (lowest numbered) to end of layers list;
layer, per set by dropdown selector. of the currently selected number of new layers =
options below. layers; number of layers set by number of layers
dropdown selector. selected.
New layer with Principal room: Unset Principal room: Unset
default System Layer type: Standard layer Layer type: Standard layer Principal room: Same
Parameters System Parameters: Default System Parameters: Default as selected layer(s)
values values
Copy of last Principal room: Unset Principal room: Unset Layer type: Same as
(highest selected layer(s); for
Layer type: Same type as last Layer type: Same type as last
numbered) each selected layer that
(highest numbered) selected (highest numbered) selected
selected layer layer; if this is a prototype layer; if this is a prototype is a prototype layer, the
layer, the added layer is a layer, the inserted layer is a appended new layer is
a child of that particular
child of this prototype layer. child of this prototype layer.
prototype layer.
System Parameters: Copy of System Parameters: Copy of
data for the last selected layer data for the last selected layer
(same as copying a layer and (same as copying a layer and System Parameters:
changing Principal Room to changing Principal Room to Copies of selected
Unset). Unset). layer(s)
Child (copy) of Principal room: Unset Principal room: Unset
prototype layer Layer type: Child of the Layer type: Child of the
prototype layer in the prototype layer in the As noted above.
dropdown selector. dropdown selector.
System Parameters: Copy of System Parameters: Copy of
data for the prototype layer data for the prototype layer
(same as copying a layer and (same as copying a layer and
changing Principal Room to changing Principal Room to
Unset). Unset).
5.5 Principal vs. Non-principal multiplex

The Principal multiplex must be designated whenever there is a secondary, non-principal, multiplex within
the same system frame. The System Parameters dialog will be coupled only to the zone layers,
components, and controllers in the Principal multiplex.
The inclusion of secondary, non-principal, multiplex within the same system frame is not permitted for
single-zone (system types 03 and 04) or packaged terminal units (system types 01 and 02) which are not
coupled to a DOAS (as is system types 09j and 09k).
The inclusion of secondary, non-principal, multiplex within the same system frame should be necessary
only when there are multiple zones that must be included on the same airside network either before or
after, rather than in parallel to, the main set of zones on the system. The network below provides an
example of this.

 Non-principal multiplexes will be highlighted in blue, similar to non-principal rooms. For a legacy
system having more than one multiplex within the system frame, the multiplex with the greatest
number of layers will automatically be set as the principal multiplex when the system is first loaded,
and thus upgraded.
 The multiplex dialog has a new ‘Principal multiplex’ checkbox that is visible only if the system
contains more than one multiplex. This is forced ticked and grayed out for the current or default
principal multiplex, and is enabled and unticked for any non-principal multiplex. These checkboxes
function as radio buttons in that only one multiplex can be designated as the Principal multiplex.
 When checking this box for a currently non-principal multiplex, the following warning message will
be displayed on clicking OK in the dialog:

The same message is also displayed if the principal multiplex is deleted, de-multiplexed, or moved
out from the system.
 System links set for components and controllers in a non-principal multiplex won’t be coupled to of
affect the parameters in the System Parameters dialog, nor will these links assign any data to these
components or controllers when you click either of the Assign buttons in System Parameters dialog.
 As the normal behavior of assigning data from System Parameters UI to the component or controller
being edited when a system link is first selected would be inappropriate, the system link drop-down
selector and re-apply button are hidden for components and controllers in a non-principal multiplex.
 Any single-multiplex legacy system of type 03 or 04 will have its multiplex resized automatically to
contain all the components and controllers first time it is loaded in VE2016, thus automatically
converting it to be correctly recognized by the System Parameters UI with ‘Single-zone systems’
displayed the ‘Configuration’ field. Any systems of this type containing two or more multiplexes,
which is not permissible, will not be upgraded. Instead, the following warning message will be
presented to the user:
‘One or more of the airside networks in this ApacheHVAC file cannot be upgraded as required for use with
the ISM System Parameters user interface. These are airside system networks of type 03 or 04, which are
meant to be ‘packaged single-zone’ systems. For this system configuration, the upgrade requires that
there is not more than one multiplex within the system frame. For single-zone systems, secondary
multiplexes can be connected to a primary multiplex, but must be set up either as separate systems
(within a separate system frame) or at very least outside of the system frame for the packaged single-
zone system.’

5.6 Principal Rooms
By default, the first room in the multiplex network is nominated as the Principal
Room and indicated as a green room component on the network.
Each layer in the multiplex is assigned a Principal Room to help identify the layer.
Double click the Principal Room column for any Layer to select the Principal room
from the list of rooms in the model.
Each layer in a multiplex can have more than one Room component on it. All
layers, however, must include the same number of Room components. Three
examples of this are provided below.
Room components can have duplicate assignments across multiple layers. This is
most typically used for non-principal rooms (see examples 1 and 3 below).
Non-principal room components can remain unused on selected layers. This
requires only that they are set via their Room assignment to act as an “Adiabatic duct,” rather than being
associated with a room or zone in the 3D model (see examples 1 and 2 below).
To change a room component on the network from a non-principal room (blue outline) for all layers to
the Principal Room for all layers, double-click the desired room component and then tick the box next to
Principal Room within the Room dialog. As this is equivalent to adding or deleting a component, the
determination of the component that is the Principal Room must be consistent across all layers in a
multiplex.
When including more than one room component on each multiplex layer, the principal Room is typically
the occupied space with which a thermostat or other sensors and controls are associated.
Example 1: It is common to have a return air (RA) plenum void in commercial spaces. This should be
modeled as a separate thermal zone over top of all of the zones it serves. There may, for example, be one
plenum for each floor of the building. These RA plenums would be represented by a non-principal “room”
component directly downstream of the occupied space on all multiplex layers. However, the Principal
Room component on each layer will typically be assigned a different space in the model. Therefore, if
there were one RA plenum for entire 1st floor, it would need to be associated with all occupied thermal
zones on that floor, and thus the same RA plenum space in the model should be assigned to the plenum
room components on each of the layers that contain a room on the first floor that has a return-air grill.
If there are spaces on the first floor in this example that have supply air and either a ducted return or no
return (perhaps they are exhausted), they would not be coupled with the RA plenum. For layers assigned
to these spaces, the RA plenum component should be set as an Adiabatic duct.

Example 2: There may be a principal room that contains a thermostat (sensors
and controllers) and an adjacent room, such as a lavatory, that draws transfer
air from the principal room and has no thermostat or other sensors associated
with it. There must, however, be means of determining the airflow through it,
even if the flow is intentionally set to zero. Typically, such rooms will have a
path to either an exhaust fan or a return fan. This will draw air from an
adjacent space, as in the lavatory in the illustration to the right.
As it is very unlikely that there would be a lavatory or similar space drawing
transfer air adjacent to the Principal Room on every layer, this non-principal
room component would be set as an Adiabatic duct on all layers for which it is
to remain unused.
Example 3: In the case of an underfloor air distribution
(UFAD) system, each layer would typically include the
UFAD supply plenum, an occupied zone, a stratified zone,
and possibly also a return-air (RA) plenum. The occupied
spaces would normally be the Principal Room on each
layer. As the UFAD plenum would be before this on the
network, the component representing the occupied zone
on the network would need to be changed from a non-
principal room to the Principal Room for all layers, as
described above.
As with the RA plenum in Example 1, each UFAD supply
plenum serving more than one zone would be assigned to
the designated UFAD plenum component on more
multiple layers (the same layers as the occupied zones it
serves).
For occupied zones served by the UFAD plenum, there
would be a corresponding stratified zone assigned to a
non-principal room component downstream of the
Principal Room. If there is an RA plenum, this would be
yet another non-principal room downstream of the
stratified zone.
If there are spaces receiving supply air from the same
airside system but not via the UFAD plenum, the UFAD
plenum would be set to Adiabatic on those layers.
Similarly, if those or other spaces were to be fully mixed
zones using overhead diffusers, the stratified zone room
component would be set to Adiabatic on those layers.

5.6.1 Assign from Room Group
The Assign from Room Group tool can be used to assign rooms to selected layers. It can also be used to
automatically add layers to the multiplex for each room in a selected room group—i.e., to create exactly
the number of additional layers that will be required for all rooms or thermal zones in the group.
The ‘Assign from Room Group’ button opens the ‘Assign Rooms from Room Group’ dialog showing the
Grouping Schemes in the project.
Select a Grouping Scheme and Room Group then click the OK button to assign each room or thermal zone
in the selected Group as a Principal Room on a multiplex layer.
Hold the Ctrl key to select multiple groups.

If there are more rooms or zones in the group than layers currently selected in the multiplex, three optons
are provided:
1. Replace selected layers and append enough layers for remainder of the group.
2. Keep selected layers and append layers for all of the group.
3. Replace selected layers only, do not add more layers.
5.6.2 Room(s) assigned

The column of check boxes at the right-hand side of the Create/Edit Multiplex dialog indicates whether or
not all Room components on a given multiplex layer have been assigned. The check boxes are not user-
editable, but will include a check mark when assignments are complete for a layer. Assigning an ‘Adiabatic
duct’ rather than an actual space in the model to a Room component does count as an assignment.

5.7 Edit Multiplex
5.7.1 Edit Multiplex Dialog

When cycling through layers on the multiplex toolbar while the selection is locked, a warning will be
displayed if any locked layer is selected. The user has the option to unlock that layer or revert to the
previously selected current display layer.
5.7.2 Editing Mode

Current layer: Edit in components, controllers, and System Parameters dialog apply to just one layer.
All selected layers: All parameters edits will apply across the complete set of selected layers.

5.7.2.1 Lock Layer Selection
When multiple layers are selected (selection must be set while in Global Edit mode) tick Lock Layer
Selection to avoid accidentally editing an unselected layer—e.g., after switching layers on the toolbar. The
locked state applies to both Global and Local edit modes.
5.8 Editing Components and Controllers in multiplex

Once a multiplex has been created, the components and controllers within it can be edited in much the
same way as those on any other part of the network.
Click once inside the multiplex region or on any component within it to make it active. This will update the
toolbar with information regarding the current display layer, selection set, and editing mode for that
multiplex. It is then possible to edit the components, controllers, and connectors within the multiplex
much as is done outside a multiplex; however, edits are applied according to the layer selection set and
edit mode. Select Local or Global Edit mode from the multiplex toolbar then edit properties of the
network components.
Note: It is important to be aware when editing within a multiplex that, at least presently, changes cannot
be undone.
Note: Because all layers must contain the same set of components, controllers, and connectors in the
same layout (though not with the same settings, profiles, etc.), moving, copying, and deleting any item
within the multiplex region must be done in Global Edit mode with all layers selected.
In Local edit mode the properties for the controller or component on the current Display layer are
displayed and can be modified.
The properties displayed will be updated if a different Display Layer is selected from the multiplex toolbar
via either the drop-down list or up/down arrows.
In Global edit mode, changes to controller or component parameters that are made in the normal (non-
tabular-edit) dialog are applied to all layers in the current selection. Global edits apply more broadly in the
case of Room Unit controllers (see next section below).
5.8.1 Tabular Editing

When in Global Edit mode, click the button containing the name or label for any variable input field in a
component or controller dialog to use the tabular editing Data Table view to efficiently view and edit
values on multiple layers (see the Tabular Editing section below for more information).
5.8.2 Touch Edits

When editing a controller or component in Global edit mode, double-clicking in any variable input field
will update that variable in all other layers to match the value in the display layer. The variable input field
will be colored orange to indicate that a Touch Edit has been completed. Clicking OK applies all Touch
Edits made in the current dialog (these can be verified in the Data Table edit view). Canceling one or more
Touch Edits in a component or controller dialog is done by Cancelling out of the dialog.
5.8.3 Edit Room Component Instances and Room Unit Controllers

Room Unit component instances (Radiators, Direct Acting Heaters, Chilled Ceilings) and their controllers,
as located within multiplexed rooms, can be edited locally or globally. Room Unit controllers should
generally be edited in Local Edit mode, except when replicating a controller and ALL of its settings. The list

of room units in any given room is sorted first by Unit Type, with multiple instances of a Room Unit Type
grouped together.
Global edits to room units within a multiplex apply to the currently selected room unit and those in other
selected layers that are of the same type and position within the ordered list of units of that type (if such a
room unit exists in the rooms on the other layers). Clicking OK in a Room Unit controller when in Global
Edit mode will apply not only newly edited values but ALL inputs and settings in that dialog to all
corresponding room unit controllers.
In the Room dialog, the column to the left of the room units description indicates the unit type for each
particular room unit instance in that room. This type plays an important role: Whenever a room unit is
selected for editing or deleting while in Global Edit mode, it is associated with corresponding room units
in each of the other selected layers by means of its type and position within the ordered list of units of
that type. For example, editing the second instance of radiator type ”Rad1_14-kW” in the principal room
on the display layer would result in the edits being applied to the second radiator of type ”Rad1_14-kW”
within the principal room on each currently selected layer in the multiplex.
5.8.3.1 Copying only modified parameters

As of version 6.3, only those parameters just modified on the display layer to be copied to the matching
Room units (if any) in all selected layers when OK is clicked.
Figure 5-5: In Global Edit mode there are two OK buttons for multiplexed Room unit controller dialogs, as
shown here. OK & Copy All replicates the data in all the controller fields on the display layer to controllers
for corresponding room units on other currently selected layers, whereas OK replicates only the data that
has just been modified and not yet saved.
5.9 Tabular Editing

Tabular Editing allows input values for components and controllers on all layers to be reviewed or edited
in a data table format. When in Global Edit mode with more than one layer currently selected, open the
properties dialog of any controller or component then select the variable to be edited. This is not yet
supported for Room Unit controllers.
5.9.1.1 Multiple Edit

To select multiple variables for tabular editing, hold the Shift key and select the desired variables; then
click the “Multiple Edit” button. This opens a data table displaying the values for the selected
parameter(s) and/or variable(s) of the component or controller on each selected layer.

Figure 5-6: Illustration of Multiple Edit function in the dialog of a multiplexed component or controller

5.9.2 Paste to Data Table using tabular edit view
Values from a spreadsheet or comma-separated value (CSV) file can be pasted directly into a Data Table
column in tabular edit view. You can thus update unique values for a selected variable on multiple layers.
Select and copy source data from a column or row, then select the uppermost variable cell you would like
to edit in the Data Table and click the Paste button to the right of the table. The paste will begin with the
selected cell and continue downwards, entering new values on each layer up to the total number of
values present in the copied selection set.
Figure 5-7: Illustration of using copy & paste from a spreadsheet to tabular edit view

Figure 5-8: Copy & paste from a CSV file to tabular edit view
Note: If the Paste is performed without first clicking on any cell in the Data Table, and multiple variables
have been selected for inclusion in the Data Table view, the copied values will be assigned to the last
variable column (at the right side of the table). The paste will begin with the current Display Layer (row
highlighted in yellow) and continue downwards, entering new values on each layer up to the total number
of values present in the copied selection set.
Note: It is possible to paste numeric or text characters. However, any pasted text must exactly match the
available options for that input (e.g., Profile names must exactly match the names of available profiles in
the ApPro database; Boiler names must exactly match those defined in the Heat Sources dialog; etc.).
Note: Tabular Editing of Room Unit controller parameters and input data is not yet supported. Room Unit
controllers should be edited in Local Edit mode with just one exception: Use Global Edit mode when the
intent is to apply ALL settings within a particular Room Unit controller to ALL other controllers for that
unit Type within the currently selected Rooms.

5.10 Node Numbering
At the boundary of a multiplex an extra node number is generated. This is hidden, as it effectively includes
both a node on the outside of the boundary (corresponding to the last labeled node outside the
multiplex) and another node for each layer on the inside of the boundary, corresponding to the nearest
labeled node on the inside. Together, these hidden nodes form a junction where the network branches
into layers—i.e., from layer zero on the outside to each the numbered layers of the multiplex.
In the example below, the multiplex junction exists between nodes 4 and 13 and between nodes 14 and 7:
Figure 5-9: Node numbering in a multiplexed system
Node numbers are not always sequential across multiplex boundaries. This is merely an artifact of how
the multiplexed network is handled by the software, and may change in future versions.
As viewed either in Vista Results or in an error message, node numbers within a multiplexed ApacheHVAC
network are numbered 1, 2, 3,… as in a normal network, but with the layer number appended to indicate
the layer—e.g., the nodes on layer zero are 1/0, 2/0, 3/0, … and on layer 1 are 1/1, 2/1. 3/1, … and on
layer 2 are 1/2, 2/2, 3/2,….and so forth.
Note: Some non-multiplexed nodes may be numbered 1/ , with layer zero being assumed. This is most
likely to be seen in a message regarding insufficient flow definition, over-constrained flow, or similar.

5.11 Delete Multiplex
A multiplex can be “de-multiplexed” (collapsed to just the current display layer) or deleted by selecting
any cell in the multiplex region on the network diagram then clicking the Delete button (trashcan) on the
toolbar.
Figure 5-10: When de-multiplexing or deleting a multiplex, a pop-up dialog requires a choice between
deleting the entire multiplex and all items within it, or simply de-multiplexing.
5.11.1.1 Delete multiplex

The multiplex is removed and all components and controllers within the multiplex are completely deleted
from the network.
5.11.1.2 De-multiplex
The multiplex is removed but the current Display Layer is retained in the network (on layer zero). This is
the default action. Prior to de-multiplexing, check the currently selected layer if you intend to retain a
layer containing a particular set of inputs to components and controllers.

6 System Loads, Ventilation, and Autosizing
6.1 Overview
Pre-defined prototype systems are autosizable with respect to zone- and system-level equipment and
controls, and both levels are required in sequence to fully autosize a system. These two levels of loads
analysis and autosizing can also be applied to a broad range of user-modified variants of prototype
systems. While care must be taken to maintain desired zone-level autosizing links when modifying
prototypes, any system, including any user-defined configuration, can be autosized with respect to system
coils, fans, water loops, and plant equipment without special preparations.
For pre-defined prototype systems and variants thereof, a broad range of system elements are sized in
each of two stages—first at the room/zone level, then at the system/plant level—with opportunity for
user intervention between the two. ASHRAE Loads calculations are linked to target ApacheHVAC systems
for both stages of the sizing process:
 Zone-level loads and sizing must be completed either manually or through the autosizing
procedure described below. The resulting values for zone heating, cooling, and ventilation
airflows, room unit water flow rates, and other controller settings are then assigned to the
HVAC system for the spaces to be conditioned accordingly.
Zone flow rates and other controller settings can also be overridden or set manually.
 System-level loads and sizing scales the capacities and performance curves or data for coils,
fans, water loops, chillers, boilers, DX cooling, air and water-source heat pumps, and similar
equipment, to model appropriate performance and energy consumption. All of these
components “see” the load during the system-level sizing run, and this applies to all
ApacheHVAC systems, regardless of how and when they were created.
Equipment sizing and capacities can also be overridden or set manually.
Figure 6-1: Systems setup and sizing toolbar in ApacheHVAC.
From left to right, the toolbar buttons in Figure 6-1 provide the following functions.
 Zone airflow distribution
Once an autosizable system (one with a gray system frame around it) has been loaded from the HVAC
library and zones have been assigned to it, the toolbar buttons are listed above are used to access dialogs
for systems setup and sizing, as described in the pages that follow below.

6.2 Zone-level loads, sizing, and related system setup procedures
The zone-level autosizing process sets zone-level and airside control inputs in the context of basic system-
level parameters. Depending upon the specific system type, these include the following parameters:
 zone-level heating and cooling load oversizing factors
 zone-level airflow for VAV boxes, fan-coil units, fan-powered boxes, active chilled beams, etc.
 outside-air ventilation rates as well as CO2 sensor control thresholds, where DCV is employed
 exhaust airflow and inter-zonal transfer airflows (typically as make-up air for exhausted air)
 reheat coil leaving air temperatures and flow rates
 radiator and chilled ceiling panel water flow rates (as of version 6.5)
 outside-air economizer damper minimum flow rates (incl. optional ASHRAE 62.1 calculations)
 outside-air economizer dry-bulb temperature high limits*
 energy recovery engagement, sensible and latent effectiveness, and device power*
 coil leaving air temperatures, temperature resets, and zone humidity control*
For prototype systems, the zone-level autosizing process provides means of engaging or disengaging
system features, such as outside air economizers and airside energy recovery, from within the System
Parameters dialog, in addition to manually changing these within the Loads Data spreadsheet for each
system or within the ApacheHVAC airside network itself. The controllers in pre-defined systems also use
pre-defined control profiles (which you may also use as you see fit). This allows system-operating schemes
for unoccupied hours—e.g., temperature setback only, setback with fan cycling, or setback with fan
cycling but no outside air—to be selected along with system schedules and setpoints. While these
parameters and operating schemes can be manually changed, the dialogs provide basic inputs and
automation for pre-defined systems.
While rooms or zones may be adequately conditioned with just the first stage of sizing completed, energy
consumption for grossly over or undersized equipment will be far from what is should be. This will be
particularly true in the case of performance for grossly oversized hot-water boilers and air-cooled or
water-cooled chillers using pre-defined bi-quadratic performance curves. System-level loads calculation
and sizing, which applies to coils, fans, water loops, chillers, DX cooling, boilers, heat pumps, etc., must be
completed in order to appropriately scale equipment capacities and performance curves and thus to
obtain performance and energy consumption results that reflect real-world applications.
The System Schedules and Setpoints dialog (see additional description below) sets room heating and
cooling set points, operating schedules, including start-up and after-hours operation, and the control
scheme to be used during unoccupied hours. It does so via automated editing of a pre-defined set of
profiles that are referenced within the prototype systems and also applied to Room Data in the Apache
Thermal view. The application of heating and cooling set points from the System Schedules dialog to Room
Data for each conditioned space provides the fundamental basis for autosizing.
The System Parameters dialog (see additional description below) provides initial inputs for many of the
zone- and system-level parameters in the list above, such as zone load oversizing factors and both air-
handler and zone coil leaving air temperatures, as inputs to the autosizing of zone-level airflows, etc. It
should be noted that oversizing factors are separately set with coils, water loops, and other heating and
cooling equipment that is autosized only in the system-level stage of the process.
The ASHRAE 90.1 Performance Rating Method (PRM) Navigator within the VE provides additional
interface dialogs and tools for ASHRAE 62.1 ventilation rates, exhaust airflow settings, and application of
PRM Baseline fan curve inputs. The PRM Navigator interface is described in a separate user guide. The
ApacheHVAC path to these parameters is described below.

The System Prototypes & Sizing navigator is an optional path for autosizing that is functionally equivalent
to the set of five toolbar buttons within the ApacheHVAC view (Error! Reference source not found.).
Using this workflow navigator, which includes some minor additional features, requires that the target
ApacheHVAC system file is named “proposed.asp”. This file name must be in place prior to using either
System Parameters or Room Load Calculations. If not, the parameter changes and/or sizing process will
not populate the Loads Data spreadsheet according to the rooms or zones assigned to the correct target
system. When using this workflow navigator, the “proposed.asp” target system name must also remain in
place (or be reinstated) for the Assign system parameters and room sizing data action within the
navigator. The ApacheHVAC file name can be subsequently changed without consequence.
The naming convention described above is not be required when using the five-button toolbar within
ApacheHVAC for System Schedules and Setpoints, System Parameters, Room and Zone Sizing, System and
Plant Equipment Sizing, and System Sizing Reports, as described below.
6.2.1 Model set up for zone-level system autosizing steps

Unless the model has exceptionally small number of thermal zones, conditioned spaces and related
thermal zones in model should first be grouped according to system or air-handler assignment using an
appropriate Room Grouping Scheme.
6.2.2 Loading HVAC systems from library or project folders
Figure 6-2: Open ApacheHVAC, load selected systems from the HVAC Prototype Systems Library as
needed, and save the file.
Additional systems can be loaded at any time and additional sizing runs performed as needed. Prototype
systems can be modified or used as resources from which to copy elements for customizing or extending
the capabilities of a particular system. For all but advanced users, however, it is recommended that initial
system sizing and brief test simulations are completed prior to modifying the system configuration,
components, or controls (substantial experience with ApacheHVAC is also recommended).

Figure 6-3: Use Edit Multiplex to assign user-defined groups of rooms or zones to each prototype system.
TIP: If you hold down the Ctrl key and clicking on the Room Group Index Numbers, you can select more
than one Room Group for simultaneous assignment to a single HVAC network.
Once the rooms or zones have been assigned to all HVAC system networks in the current HVAC system
file, proceed to using the following five buttons of the System Sizing toolbar in ApacheHVAC to set up and
autosize the systems.

6.2.3 System Sizing toolbar
From left to right, the System sizing toolbar buttons provide the following functions:
 Zone airflow distribution
6.2.4 System Schedules and Setpoints

Figure 6-4: The System Schedules and Setpoints dialog has two tabs: the first tab is for editing and
creating sets of coordinated HVAC profiles used in system controllers and Room Data; the second is for
Assigning these profiles to specific HVAC networks and groups of room or zones served by that system.
Figure 6-5: The list window at the left of the System Schedules and Setpoints dialog is the means of
selecting an existing HVAC profile set to be edited, assigned, or copied. Additional sets of profiles should
be set up when the project includes an HVAC system and zones served by that system that will be
operated with setpoints, schedules, or setback strategies that differ from that of other systems in the
same project. A New HVAC profile set will start with default values, whereas a Copy will start with the

values of the currently selected set. In either case, you will be prompted to add a prefix the schedule set
name (up to four characters) that will be applied to all daily and weekly HVAC and SYS profiles in the
automatically generated set.
Figure 6-6: The Edit tab in the System Schedules and Setpoints dialog provides coordinated editing of the
selected set of HVAC… and SYS… profiles used in HVAC system controllers and Room Data.
Figure 6-7: System HVAC Profiles are renamed to clarify values relative to setpoints, making it easier to
apply and modify these profiles for custom airside control sequencing. This is a transitional step toward a
much more flexible and streamlined approach to HVAC profiles in a future release.

Figure 6-8: The Assign tab in the System Schedules dialog provides options for assigning a coordinated set
of profiles to the components and controllers of a selected HVAC system and to Room Data. The standard
set of “System HVAC profiles” is already assigned, by default, to all pre-defined prototype HVAC networks
in the systems library. Therefore, profiles need be assigned to systems only when setting up an additional
or alternate set of HVAC profiles. For rooms or zones in the model, however, the SYS profiles must be
assigned to Room Data at least once prior to autosizing any ApacheHVAC networks for the project.
For a project wherein all zones use the same schedules and setpoints, simply leave the standard set of
“System HVAC profiles” is assigned to all pre-defined prototype HVAC networks (as they are by default);
edit and update as desired via the Edit tab of the dialog, and then go to the Assign tab (at least once) and
select Assign to all rooms prior to clicking Assign Profiles.
NOTE regarding 24-hour operation: If 24-hour operation is to be used for all day types, simply select the
Setback strategy called “None (24-hr. conditioned to Oc. Setpoints).” To specify 24-hour “opening times”
with respect to HVAC operation for some but not all day types, set both the Open time and Close time for
the desired day types to 0:00—for this to work correctly, however, After Hours Operation must be set to
zero (0.0).

Figure 6-9: The Room/Zone Load Calculations toolbar button (or the equivalent step in the System
Prototypes & Sizing navigator) runs ASHRAE Loads and populates the System Parameters interface for
each network with loads results. Other relevant data, such as room volumes, is populated when rooms or
zones are assigned to multiplex layers. The loads data and other settings in the System Parameters dialog
for zone-specific airflow configurations and calculation of ASHRAE 62.1 ventilation rates feed into the
calculation of zone airflows and related parameters.

Figure 6-10: Options for running ASHRAE Loads including diversity for internal gains, internal gain profile
saturation, and design day profiles

Analyses;
ApacheSim dialog.
The user setting above are retained as user preferences for future loads and simulation runs.

Figure 6-11: The System Parameters dialog provides access to viewing and editing numerous parameters
for system configuration, sizing, and control options. Edited parameters are applied to system
components and controllers through ‘system parameter links’ upon clicking ‘Assign’. The ApacheHVAC
User Guide part D - System Parameters Interface for HVAC Networks describes this in greater detail.

The Assign button in the System Parameters dialog assigns values to system components and controllers.
This is also done automatically upon completion of zone-level autosizing when the ‘Update ApacheHVAC
zone-level autosizing’ box is checked in ASHRAE Loads. Viewing the zone cooling and heating airflow rates
for all multiplex layers confirms that this stage of autosizing has been satisfactorily completed.
6.3 System equipment and plant loads and sizing

System equipment and plant autosizing—the second or “system-level” sizing stage—runs the selected
ApacheHVAC system to determine design sizing for system and plant equipment. Sizing at this level is thus
the combined result of the zone loads for the design-day conditions, setpoints (including setback in the
case of cooling), system configuration, and controller settings for the selected ApacheHVAC system.
This stage of the sizing process can be applied to system-level equipment for any (pre-defined or user-
defined) functional ApacheHVAC system, and no Loads Data spreadsheets are required. Furthermore,
except in the context of the Workflow Navigator for ASHRAE 90.1 PRM, system sizing does not require a
specific ApacheHVAC target file name. Rather, the target HVAC system file is simply selected when the
system level sizing is performed (when system sizing is launched form the ApacheHVAC toolbar, the
system sizing target defaults to the currently open ApacheHVAC file).
System-level autosizing applies to the following components within ApacheHVAC:

 heating coils
 cooling coils
 fans
 boilers
 chillers
 hot water loops
 chilled water loops
 heat transfer loops
 DX cooling
 air-source heat pumps
 water loop heat pumps
 furnaces
 water-source heat exchangers
 other heating & cooling sources
A coil, for example, is sized according to the maximum load it “sees” during the design sizing run, given
the settings within controls for leaving air temperature, dehumidification, air flow rates, and so forth.
System-level autosizing does not use or require the Loads Data spreadsheet for each system. Loads Data
spreadsheets are required only for zone-level autosizing and for expediting setup of common component
parameters, such leaving air temperature setting for coils, via the System Parameters dialog. Regardless of
where they exist in the system (AHU or zone level) all coils and fans are autosized along with plant
equipment during the system-level sizing run, which does not depend on the spreadsheets.

Figure 6-12: System-level sizing and System Loads report buttons on the Systems setup and sizing toolbar.
System load calculations and autosizing can be run from the System-level sizing button on the
ApacheHVAC toolbar (Figure 3-1 above), directly from within the ASHRAE Loads dialog (Figure 6-13
below), or from the System load calculations action item in the System Prototypes & Sizing navigator. This
third option is further described under in the System Prototypes & Sizing workflow navigator section
below.
Figure 6-13: ApacheHVAC system loads analysis type in ASHRAE Loads dialog


Analyses;
ApacheSim dialog.
The user setting above are retained as user preferences for future loads and simulation runs.
In addition to the System Loads Calculation reports, there are also a number of tools available for
checking the number of “unmet load hours” according to various criteria. This is explained in the next
subsection immediately below.

6.3.1 Unmet Load Hours tests
Unmet load hours are any hours of operation when conditioned spaces are outside the throttling range
for heating or cooling controls. While this test is performed automatically in the 90.1 Performance Rating
Method (PRM) Navigator for the associated reports, this can readily be done as a manual check within
Vista Results. To do so, complete all of the following steps (an example is provided below):
1. In Vista Results, select the conditioned spaces in the model from the Room Browser tree at left.
2. Select the Air temperature results variable.
3. Open the Range Test tool.
4. Date/Time: check the tick box below the list of week days and select When conditioned (incl.
setback) from the drop-down menu next to this tick box.
5. Test: Between room setpoints (+/- differential tolerances)
6. Under Test temperatures in controlled band, tolerances in °F (or, for metric users, … in °C ), enter 2
for both heating and cooling if working in IP units and 1.11 for both if working in metric units
(these settings will apply for most user most of the time; see further notes below).
7. Check the tick box for Averaged, shared hours (for ‘unmet hours’ test).
8. Click Apply.
The range test below shows results for a system autosized perfectly to meet all loads for the simulation
period of eight days in January (this test was aimed at confirming heating performance). This outcome
may actually be less than ideal if meeting all loads under the most extreme conditions causes the system
to be significantly oversized relative to more typical conditions. And, over a full year, even autosized
systems will normally have some unmet heating or cooling hours as a result of varying conditions and
related system dynamics or differences between the design sizing conditions vs. the simulation weather
file. The results of an unmet loads hours test should, however, generally appear as in this example.

Figure 6-14: Unmet Load Hours test performed using the Range Test tool in Vista Results

Figure 6-15: Heating setpoint profile (purple), Cooling setpoint profile (blue), zone air temperature
(green), and plant profile (red) for a selected space in the model.
As can be seen in Figure 6-15: Heating setpoint profile (purple), Cooling setpoint profile (blue), zone air
temperature (green), and plant profile (red) for a selected space in the model. above, the profiles set in
the Room Data dialog for a particular space (either via a Thermal Template, via System Schedules dialog,
or manually) for heating and cooling setpoints are recorded at the time of simulation and can readily be
placed on graph along with the zone/room air temperature. The profiles show the setpoints for occupied
hours and setback for unoccupied hours.
The right-hand graph shows the heating setpoint and room temperature once again with the Plant profile
(red). The plant profile toggles between 0 and 1 to indicate the times during which the normal daytime
setpoint should be fully met (future versions of the VE may use this profile to provide more detailed
information regarding system status relative to setpoints, night-cycle operation, and so forth).
It is important to keep in mind that the heating and cooling profiles show the setpoint for occupied hours
as a target for the morning start-up and after-hours operating periods. Thus you may see the room
temperature lagging behind the setpoint profile, particularly in the early morning hours. The definitions
below describe how unmet load hour tests use nighttime setback values while the modeled spaces are
transitioning between nighttime setback and daytime setpoint. This avoids over-counting unmet hours.
Note that in the illustrative example on the preceding page there are some spaces in the model for which
the hours in all three columns are zero. These spaces are plenums and an unconditioned vestibule. While
they still have profiles assigned to them in Room Data (via System Schedules or manually) for timed
heating and cooling setpoints and setback, they have their heating and cooling on/off profiles (on/off
schedules) in Room Data set either individually or via thermal templates to “off continuously.” This is the
essential means of indicating that a space in unconditioned with respect to unmet load hours tests.
When the VE detects heating and cooling on/off profiles set to “off continuously” and thus determines
that a particular room is fully unconditioned, a nominal unconditioned values range of 20C +/-80C (68F
+/-144F) is applied. This equates to an unconditioned heating value of -76F (-60C) just shy of the -80F
lowest external temperature ever recorded in the US, and an unconditioned cooling value of 212F
(100C)—the boiling point of water. These values are recorded at the time of simulation as continuous
setpoints for any fully unconditioned space.

6.3.1.1 Definitions of terms used in the Unmet Load Hours range test
The terminology used in the range test tools for unmet load hours is somewhat specialized. The following
definitions may therefore be helpful in using the Range Test dialog for unmet load hour tests:
 When Occupied: All times for any particular room when occupancy is greater than zero.
 When room heated or cooled: Tests for hours out of range relative to the setpoint profiles at all
times for each particular room, so long as the value for the on/off profile for either heating or
cooling = on. If there are warm-up and after-hours operating periods over which the daytime
setpoints are extended, this test will use daytime setpoints during these time periods. This test
does not allow for room temperature transition from setback to setpoint.
 When plant profile on full: All times for a particular room during which the normal daytime
setpoint should be fully met—i.e., fully excluding unoccupied/nighttime operation (outside of
“opening hours”) and both morning start-up and after-hours operation.
 When conditioned (incl. setback): Tests for hours out of range relative to setpoints, applying
the unoccupied/nighttime setback values to any morning start-up and after-hours operating
periods during all times for a particular room when the on/off heating or cooling profile = ON.
This test assumes, for example, that the full morning warm-up period will be needed to raise a
particular zone from the setback temperature to the daytime setpoint, and therefore does
allow for room temperature transition from setback to setpoint.
 Between room setpoints (+/- differential tolerances): Test to count hours in three categories:
o Below the heating setpoint minus the heating control band tolerances
o Between room setpoints, +/- the set control band tolerances
o Above the cooling setpoint plus the heating control band tolerances
 Test temperatures in controlled band, tolerances in °F: These values set the added tolerance
above and below the setpoints that should be applied to determine when a temperature is
“out of range.” The tolerances allow for the throttling or control of HVAC parameters such as
variable water and air flow rates in coils and ducts to address loads. The pre-defined systems
all reference profiles that have names beginning with “HVAC,” and so long as they are changed
only via the System Schedules dialog, these profiles are maintained with standard throttling
ranges relative to the heating and cooling setpoints. Unless you’ve set up your own HVAC
controller profiles or have revised values in the pre-defined “HVAC” profiles within ApPro, the
standard 2F for both heating and cooling when working in IP units (1.11C when in metric)
should be used here. If you have set up custom control profiles, you will need to set these
tolerance values to allow for the throttling range in the custom profiles.
 Averaged, shared hours (for ‘unmet hours’ test): This looks at average temperature over the
full one-hour period in each room for each hour and then adds any particular out-of-range
hour to the total “shared hours” tally only once, regardless of how many rooms or zones were
out of range during that hour. The “shared hours” total of each column is displayed in the
bottom row of the table.
With all conditioned spaces selected, the total of shared hours reported in the bottom row as
outside the control ranges for both heating and cooling are collectively the Unmet Load Hours.
A space temperature is considered out of range (under-heated or under-cooled) for any hour
when the average temperature for that hour is below the heating setpoint less the control
band tolerance or above the cooling setpoint plus the control band tolerance. The “shared
hours” might be thought of as a logical ‘OR’ test, with each hour counted only once when any
one or more rooms in the currently selected set of rooms is/are out of range.

6.3.2 Understanding loads for ApacheHVAC components in Vista Results
It’s important to understand what you’re looking at when viewing loads for ApacheHVAC components
within Vista Results view. The following is meant to touch on just a few points that may be less obvious in
terms of how the numbers you see in the results relate to the capacity of the components and the loads
that they convey to heating and cooling plant equipment.
Coils are relatively more straightforward in that their capacity or loading is a function of design inputs:
 For simple coils, the capacity set in the coil dialog will be the capacity, regardless of conditions on
either the air or water side of the coil. Regardless of system-level plant equipment capacity, in the
case of a simple coil all simulated load up to the capacity set in the dialog will be passed to the
connected water loop or directly to the heating or cooling source if no water loop is present.
 For advanced coils, the capacity of the coil is a function of the relationship between the design
conditions and the actual conditions at any given time step, including the temperature and flow
rate of the connected water loop. The coil will be restricted to delivering only as much heating or
cooling as is feasible given the combination of sensible and latent loads it sees and the loop water
temperature and flow rate it has to work with at that time. The resulting load will be passed to
the associated water loop.
Water loops will contribute to the load seen by a boiler or chiller: heat rejected to the water loop by
pumps will add to or subtract from the load placed upon the loop by coils and other devices.
Room units, unlike coils, have heating and cooling effects associated with the presence of their thermal
mass within the conditioned space: Regardless of whether it is OFF (i.e., not active or presently engaged)
or ON, the thermal mass of any room unit will play a role in adding heat to or removing heat from the
space. All room units will thus have a load profile differing at least somewhat from the load profile seen
by the heating or cooling source or loop to which they are coupled.
For example, a radiator will heat a room less as its mass is warming up and will continue to heat the room
after the flow of hot water to it is turned off. And, even if it never turns on, a radiator will absorb a minor
cooling load while sitting idle in a space as the space grows warmer. Thus at the end of a hot summer day
when the air conditioning runs just to closing time, a radiator may contribute ApHVAC Room Unit Cooling
Load (via stored “coolth”) when the airside AC system shuts down and the room begins to grow warmer.
6.4 Load sizing and ventilation reports

A consolidated “Generate system loads and sizing reports” dialog provides one place to generate a broad
range of new and existing reports for buildings, system, zone, and room loads, sizing, and ventilation. This
provides user control over:
 The results file to be used for generating reports;
 Which of the PDF Loads reports will be generated;
 Selection of the relevant coils for reporting of gains and losses contributing to coil loads at the
time of the coil peak;
 The inclusion or exclusion of oversizing factors, which will be indicated one way or the other
on the reports generated;
 This dialog also includes the option to generate the older style (VE2016 & earlier) HTML
System Loads and ASHRAE 62.1 Ventilation reports.
Reports include:
 Project and climate (building, weather, etc.)

 Plant loops & equipment (capacity, flows, etc.)
 System summary (space loads & ventilation)
 System loads (detailed loads breakdown, coil capacities, airflows, engineering checks, etc.)
 Zone Loads (same as for System)
 Room Loads (same as for Zones)
 VE2016 System Sizing reports
 ASHRAE 62.1 Ventilation (App. A method)
Figure 6-16: Generate system loads and sizing reports dialog with options for setting relevant peaks
The project and climate report provides top-level data regarding the building geometry, site, climate,
design weather, loads conditions, and overall building loads.

Figure 6-17: Project and climate PDF report for an example project
Plant Loops and Equipment report provides all essential data regarding HVAC plant water loops and the
equipment serving the loads on those loops. Data reported for plant loops includes:
 Chilled Water Loop(s)

o Cooling capacity
o Primary design flow rate
o Primary pump power
o Secondary design flow rate
o Secondary pump power
o Condenser loop design capacity
o Condenser loop design flow rate
o Condenser loop pump power
o Pre-cooling loop capacity
o Chillers/cooling equipment capacities
 Hot Water Loop(s) > same as for CHWL, plus…
o Pre-heating equipment capacities
o CHR capacity as % CWL
o CHR WWHP capacity as % CWL
o AWHP capacity

o CHP thermal capacity
o Boilers /heating equipment capacities
 Heat Transfer Loop(s) > same as for HWL, plus…
o Heat acquisition equipment capacities
o Water-source heat exchanger Heating/Cooling capacity
o Heating equipment capacity
o Heat rejection equipment capacity
Figure 6-18: Plant loops and equipment PDF report for a chilled water and hot water loop
Space Loads and Ventilation report summarizes the design loads, heating and cooling airflows, and
ventilation for each system, the zones it serves, and the rooms within each zone. The report includes
system peak coincident cooling and heating loads and airflows for conditioned spaces, zone and room
non-coincident peak loads and design primary airflows, and outside air ventilation.

Figure 6-19: Space loads and ventilation PDF report showing multiple zones and spaces
System, Zone, and Room Loads reports provide a comprehensive set of loads data with respect to space
geometry, envelope gains/losses, internal gains/losses, mechanical gains/losses, contribution of those to
coil loads, plus coil sizing, system and room air temperatures, airflow rates, ventilation requirements, and
engineering checks.
System, zone, and room loads report include:
 Detailed breakdown of loads at the time

of the selected relevant cooling and
heating coil peaks and the zone peak:
o Envelope gains/losses
o Internal building gains/losses
o Internal gains
o Mechanical system gains/losses
 Capacities and sizing conditions for all cooling and heating coils and room units
 Summary of surface and glazing areas for conditioned spaces.
 Temperatures for supply air, room vs. setpoints, return plenums, etc.
 Airflows: supply design/actual, ventilation req./actual, leakage, exhaust, return, etc.
 Engineering checks

Many report parameters have been added, as compared to the previous HTML system sizing reports.
There is a new report generator engine to support the new parameters and to improve the robustness of
the reports.
As the reports are generated via Python scripts, all reporting can be automated through scripting and
ultimately it is possible for user to script the writing of report values to custom spreadsheets and other
user-defined formats.
Figure 6-20: System loads PDF report for a variable air volume air handling unit served by a chilled water
and hot water loop, including terminal units with hot water reheat

ApacheHVAC Part A - Overview and Fundamentals

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

ApacheHVAC Part A - Overview and Fundamentals

Enviado por

Direitos autorais:

Formatos disponíveis

ApacheHVAC User Guide

Part A: Overview and Fundamentals

Copyright © 2017 Integrated Environmental Solutions Limited. All rights reserved.

VE 2016 ApacheHVAC User Guide part A: Overview and fundamentals i

VE 2016 ApacheHVAC User Guide part A: Overview and fundamentals ii

VE 2016 ApacheHVAC User Guide part A: Overview and fundamentals iii

VE 2016 ApacheHVAC User Guide part A: Overview and fundamentals iv

A: Overview and Fundamentals

B: Equipment, Loops, Components, and Controls

C: Working with Prototype HVAC Networks

D: System Parameters Interface for HVAC Networks

Appendix A: Rules for Air Flow Specification

ASHRAE 90.1 Performance Rating Method Navigator

ApacheHVAC ASHRAE Loads ApacheSim VistaPro

1.2.1 ModelIt/Apache Space Types

1.2.3 HVAC Methodology

Selecting the ApHVAC HVAC Methodology enables new functionality:

1.2.5 HVAC Zones and Zone Groups

1.3.1 Virtual Environment Menu Bar

1.3.2 ApacheHVAC Menu Bar

These pull-down menus provide functions specific to the ApacheHVAC view.

1.3.3 ApacheHVAC Toolbars

 Hot water loops  Direct-acting heater/cooler types

 Create multiplex  Layers selected of layers in multiplex

 Room or thermal zone component  Junction / flow splitters (four)

 Add new loop

1.3.4 View Toolbar

Heat transfer loops

Chilled water loops

1.3.6 Performance Curve Library

1.3.9 Mouse controls

1.3.10 Mouse/key operations summary

1.3.10.1 Selected airside network objects

1.3.10.3 DURING “PENCIL” DRAWING

1.6 ASHRAE Loads and ApacheHVAC System Sizing

1.6.1 ASHRAE Loads

1.6.2 System Sizing

2.1.2 Efficient workflow

2.1.4 Network drawing tool

2.1.6 Zone components

Figure 2-4: HVAC components toolbar

2.2.1 Waterside plant equipment and water loops

2.2.2 Airside plant equipment and system components

2.2.3 Room units – zone equipment applied within Room components

Summary of System Frame Status and ToolTips

3.4 System Parameter interface toolbar buttons

System parameter links couple each

VE 2016 ApacheHVAC User Guide part A: Overview and fundamentals 41

3.5.1 Overriding linked values

VE 2016 ApacheHVAC User Guide part A: Overview and fundamentals 42

Duct heat gain/loss Heating coils Cooling coils

Heat/enthalpy exchangers Moisture addition/evaporative cooling Thermal battery

Room or Zone component Room or Zone without air supply

VE 2016 ApacheHVAC User Guide part A: Overview and fundamentals 43

VE 2016 ApacheHVAC User Guide part A: Overview and fundamentals 44

VE 2016 ApacheHVAC User Guide part A: Overview and fundamentals 45

Figure 3-1: System Prototypes & Sizing Navigator

VE 2016 ApacheHVAC User Guide part A: Overview and fundamentals 46

VE 2016 ApacheHVAC User Guide part A: Overview and fundamentals 47

VE 2016 ApacheHVAC User Guide part A: Overview and fundamentals 48

4.1 Import from library

The tree hierarchy consists of the following folders, in order:

VE 2016 ApacheHVAC User Guide part A: Overview and fundamentals 49