This user guide describes how to use the templates.
The templates are defined at the system level, such as an air handler or a terminal unit (refer to Buildings.Templates.UsersGuide.Conventions for the definition of a system). A template is a self-contained model that can be reconfigured by redeclaring some of its components or modifying some structural parameters. Such configuration does not require any further modification of the template. In particular, all connect clauses between replaceable components are resolved internally without user intervention. The same applies to sensors that are required for a specific control option and instantiated only when that option is selected.
Currently, there is no template that represents a complete HVAC system from the plant to the zone equipment. In order to create a simulation model for a complete HVAC system, one must
When assembling a model for a complete HVAC system, the user must ensure that the control sequence selected for one subsystem is compatible with that selected for another subsystem. For example, the AHU controller may require reset requests that originate from the zone equipment controller. If the controller selected for the zone equipment does not generate such requests, the simulation model will be singular. Selecting controllers from the same reference—e.g., ASHRAE (2021)—is the safest way to ensure consistency throughout the HVAC system model.
Each template contains an instance dat of a record class that
contains all design and operating parameters for parameterizing
the subcomponents of the template.
For example, the multiple-zone VAV template
Buildings.Templates.AirHandlersFans.VAVMultiZone
contains an instance of the record class
Buildings.Templates.AirHandlersFans.Data.VAVMultiZone
which contains the parameters for configuring the heating coil component,
as an instance of the record class
Buildings.Templates.Components.Data.Coil.
All design and operating parameters should be assigned through this record instance
and are propagated down to each subcomponent.
In addition to these parameters, the record class also contains the configuration parameters that define the system layout and control options. These configuration parameters are bound to the values that are assigned via the template's parameter dialog. In this way, only the set of parameters needed for the particular system layout for which the template is configured is displayed in the parameter dialog. Note that these configuration parameters are disabled in the record class to avoid any modification by the user and preserve the bindings with the template parameters.
When creating a model for a complete HVAC system with multiple instances of different templates, the class Buildings.Templates.Data.AllSystems can be used at the top level of the model to assign all design and operating parameters. This class allows the use of Modelica outer components to retrieve the configuration parameter values for each template instance based on the instance name. Thus, it is the avatar in the modeling environment of an HVAC project datasheet. The validation models within Buildings.Templates.AirHandlersFans.Validation illustrate the use of this class.
| Name | Description |
|---|---|
| Conventions | Conventions |