Revision history [back]

EnergyPlus HVAC system models are scalable. What this means is that for a specific hardware configuration and associated performance, the model assumes a different size system would perform similarly (i.e., use the same performance curves or input criteria). This is not always true in real life where a range of HVAC system sizes uses the same chassis leading to slight differences in performance as capacity changes through the manufacturer line of systems using this chassis.

To use the scalable sizing methodology, use autosize for all inputs. This method will scale the HVAC system to meet the loads in the simulated building. If you want to model a specific HVAC system for a specific building, then enter the actual capacity and air flow (and other information as needed). If you know only the capacity, search for manufacturers data for that specific HAVC model to fill in the blanks (air flow, SHR, COP). If you can not find manufacturers data use rule of thumb data. For example, if you have capacity and not air flow, use air flow = capacity * 0.00054 (or about 400 cfm/ton which is typical of DX equipment), SHR = 0.78 and COP = ~3.5. Of course, these numbers do vary with different HVAC systems.

If this air flow ( capacity * 0.00054 ) is much different than that predicted by EnergyPlus, then either the building loads are not similar to the real building (i.e., the building or internal loads are different) or the Sizing* objects do not reflect the correct information.

The bottom line is that your choices are to fully autosize the HVAC system or enter all values for autosizable fields. It is very risky to autosize some fields and enter values for other autosizable fields.

EnergyPlus HVAC system models are scalable. What this means is that for a specific hardware configuration and associated performance, the model assumes a different size system would perform similarly (i.e., use the same performance curves or input criteria). This is not always true in real life where a range of HVAC system sizes uses the same chassis leading to slight differences in performance as capacity changes through the manufacturer line of systems using this chassis.

To use the scalable sizing methodology, use autosize for all inputs. This method will scale the HVAC system to meet the loads in the simulated building. If you want to model a specific HVAC system for a specific building, then enter the actual capacity and air flow (and other information as needed). If you know only the capacity, search for manufacturers data for that specific HAVC model to fill in the blanks (air flow, SHR, COP). If you can not find manufacturers data use rule of thumb data. For example, if you have capacity and not air flow, use air flow = capacity * 0.00054 (or about 400 cfm/ton which is typical of DX equipment), SHR = 0.78 and COP = ~3.5. Of course, these numbers do vary with different HVAC systems.

If this air flow ( capacity * 0.00054 ) is much different than that predicted by EnergyPlus, then either the building loads are not similar to the real building (i.e., the building or internal loads are different) or the Sizing* objects do not reflect the correct information.

The bottom line is that your choices are to fully autosize the HVAC system or enter all values for autosizable fields. It is very risky to autosize some fields and enter values for other autosizable fields.

** Warning ** ProcessScheduleInput: Schedule:Compact="OCUP_OFICINA" has missing day types in Through=12/31
**   ~~~   ** Last "For" field=FOR: WEEKENDS HOLIDAY
**   ~~~   ** Missing day types="SummerDesignDay","WinterDesignDay","CustomDay1","CustomDay2"
**   ~~~   ** Missing day types will have 0.0 as Schedule Values

Z1:MALAGA ANN HTG 99.6% CONDNS DB:Des Heat Load [W] = 12200
Z1:MALAGA ANN CLG .4% CONDNS DB=>MWB:Des Sens Cool Load [W] = 24900
Z1:MALAGA ANN HTG 99.6% CONDNS DB:Des Heat Mass Flow [kg/s] = 0.413
Z1:MALAGA ANN CLG .4% CONDNS DB=>MWB:Des Cool Mass Flow [kg/s] = 2.98

EnergyPlus HVAC system models are scalable. What this means is that for a specific hardware configuration and associated performance, the model assumes a different size system would perform similarly (i.e., use the same performance curves or input criteria). This is not always true in real life where a range of HVAC system sizes uses the same chassis leading to slight differences in performance as capacity changes through the manufacturer line of systems using this chassis.

To use the scalable sizing methodology, use autosize for all inputs. This method will scale the HVAC system to meet the loads in the simulated building. If you want to model a specific HVAC system for a specific building, then enter the actual capacity and air flow (and other information as needed). If you know only the capacity, search for manufacturers data for that specific HAVC model to fill in the blanks (air flow, SHR, COP). If you can not find manufacturers data use rule of thumb data. For example, if you have capacity and not air flow, use air flow = capacity * 0.00054 (or about 400 cfm/ton which is typical of DX equipment), SHR = 0.78 and COP = ~3.5. Of course, these numbers do vary with different HVAC systems.

If this air flow ( capacity * 0.00054 ) is much different than that predicted by EnergyPlus, then either the building loads are not similar to the real building (i.e., the building or internal loads are different) or the Sizing* objects do not reflect the correct information.

The bottom line is that your choices are to fully autosize the HVAC system or enter all values for autosizable fields. It is very risky to autosize some fields and enter values for other autosizable fields.

Running your file in V8.7 shows several warnings like this:

** Warning ** ProcessScheduleInput: Schedule:Compact="OCUP_OFICINA" has missing day types in Through=12/31
**   ~~~   ** Last "For" field=FOR: WEEKENDS HOLIDAY
**   ~~~   ** Missing day types="SummerDesignDay","WinterDesignDay","CustomDay1","CustomDay2"
**   ~~~   ** Missing day types will have 0.0 as Schedule Values

This can lead to incorrect HVAC system sizing, more so for the summer period since internal gains add to the load.

The eio file shows air flow to capacity ratio = 0.0000604 which is at the high end of the range of allowed air flow ratios. This means that the calculated zone air flow is high compared to the loads and the DX coil model increased the system capacity to stay within a predetermined air flow per capacity range.

The zone sizing results (*zsz.csv) shows why the top end of the air flow to capacity range was used, where cooling dominates and peak air flow to capacity = 2.98/24900 = 0.00012 (about 900 cfm/ton which is way too high). I should mention that I used Chicago weather so your numbers will be different. So if you enter these values directly into the DX coil, the errors tell you that the capacity and air flow are not within a range typical for DX equipment.

Z1:MALAGA ANN HTG 99.6% CONDNS DB:Des Heat Load [W] = 12200
Z1:MALAGA ANN CLG .4% CONDNS DB=>MWB:Des Sens Cool Load [W] = 24900
Z1:MALAGA ANN HTG 99.6% CONDNS DB:Des Heat Mass Flow [kg/s] = 0.413
Z1:MALAGA ANN CLG .4% CONDNS DB=>MWB:Des Cool Mass Flow [kg/s] = 2.98

If you correct the schedules, the zone cooling loads will increase, but maybe not to a point where the air flow to capacity ratio is within a valid range. range since zone cooling air flow will also increase. I also see 100% OA in the eio file so this can cause the system capacity to be larger than the zone load.

EnergyPlus HVAC system models are scalable. What this means is that for a specific hardware configuration and associated performance, the model assumes a different size system would perform similarly (i.e., use the same performance curves or input criteria). This is not always true in real life where a range of HVAC system sizes uses the same chassis leading to slight differences in performance as capacity changes through the manufacturer line of systems using this chassis.

To use the scalable sizing methodology, use autosize for all inputs. This method will scale the HVAC system to meet the loads in the simulated building. If you want to model a specific HVAC system for a specific building, then enter the actual capacity and air flow (and other information as needed). If you know only the capacity, search for manufacturers data for that specific HAVC HVAC model to fill in the blanks (air flow, SHR, COP). If you can not find manufacturers data use rule of thumb data. For example, if you have capacity and not air flow, use air flow = capacity * 0.00054 (or about 400 cfm/ton which is typical of DX equipment), SHR = 0.78 and COP = ~3.5. Of course, these numbers do vary with different HVAC systems.

If this air flow ( capacity * 0.00054 ) is much different than that predicted by EnergyPlus, then either the building loads are not similar to the real building (i.e., the building or internal loads are different) or the Sizing* objects do not reflect the correct information.

The bottom line is that your choices are to fully autosize the HVAC system or enter all values for autosizable fields. It is very risky to autosize some fields and enter values for other autosizable fields.

Running your file in V8.7 shows several warnings like this:

** Warning ** ProcessScheduleInput: Schedule:Compact="OCUP_OFICINA" has missing day types in Through=12/31
**   ~~~   ** Last "For" field=FOR: WEEKENDS HOLIDAY
**   ~~~   ** Missing day types="SummerDesignDay","WinterDesignDay","CustomDay1","CustomDay2"
**   ~~~   ** Missing day types will have 0.0 as Schedule Values

This can lead to incorrect HVAC system sizing, more so for the summer period since internal gains add to the load.

The eio file shows air flow to capacity ratio = 0.0000604 which is at the high end of the range of allowed air flow ratios. This means that the calculated zone air flow is high compared to the loads and the DX coil model increased the system capacity to stay within a predetermined air flow per capacity range.

The zone sizing results (*zsz.csv) shows why the top end of the air flow to capacity range was used, where cooling dominates and peak air flow to capacity = 2.98/24900 = 0.00012 (about 900 cfm/ton which is way too high). I should mention that I used Chicago weather so your numbers will be different. So if you enter these values directly into the DX coil, the errors tell you that the capacity and air flow are not within a range typical for DX equipment.

Z1:MALAGA ANN HTG 99.6% CONDNS DB:Des Heat Load [W] = 12200
Z1:MALAGA ANN CLG .4% CONDNS DB=>MWB:Des Sens Cool Load [W] = 24900
Z1:MALAGA ANN HTG 99.6% CONDNS DB:Des Heat Mass Flow [kg/s] = 0.413
Z1:MALAGA ANN CLG .4% CONDNS DB=>MWB:Des Cool Mass Flow [kg/s] = 2.98

If you correct the schedules, the zone cooling loads will increase, but maybe not to a point where the air flow to capacity ratio is within a valid range since zone cooling air flow will also increase. I also see 100% OA in the eio file so this can cause the system capacity to be larger than the zone load.