Initial implementation is resulting in HERS flags triggered for MinimumAirflow, FanEfficacy & DuctSealing.
Given that these are "Proposed=Standard" systems, my guess is that these HERS flags should NOT be triggered.
CEC please confirm.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The only issue I find is that the ducted equipment comes in with 0 CFM. This should be 350. Please add a range check to prevent it from running (I noticed it runs with 0, reports 0, but also requires airflow testing; if 350 is entered it runs, reports 350, requires airflow. Results are the same.)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Some guidance is needed from the CEC on this ticket.
Several new systems were added to CBECC-Res in version 2019.1.3, including those described above - ductless, ducted and ducted+ductless mini-split, multi-split and VRF AC and HP equipment. The AC units in this group allow input of CFM per Ton (with no default) while the HP units do not allow specification of CFMperTon.
Entry of performance characteristics on this screen do not effect analysis, but do impact compliance reports - namely reporting of Airflow Target on the Heat Pump and Cooling HERS Verification tables. When not specified, Airflow Target is documented in the CF1R as 0, and when specified (for AC units), the user entered value is reported here.
Primary question is this - should CFM per Ton be specified for any of these equipment types?
If so, then what limits should be placed on these inputs?
And if not, then should we alter the CF1R's Airflow Target reporting in these HERS Verification tables to list 'n/a' as opposed to '0' (via schema and possibly report template updates)?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For the AC systems we should continue to allow the user to specify CFM per Ton. Additionally, we should perform a range check to prevent the program from running when the user does not specify a value or enters '0'.
For the heat pump systems, CFM per Ton should continue to be hidden, and I prefer that we report 'n/a' rather than '0'.
Last edit: Michael Shewmaker 2021-03-25
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Initial implementation is resulting in HERS flags triggered for MinimumAirflow, FanEfficacy & DuctSealing.
Given that these are "Proposed=Standard" systems, my guess is that these HERS flags should NOT be triggered.
CEC please confirm.
Initial selections, UI, defaulting and analysis checked into SVN @ r1846
No word yet on label wording or ACM descriptions and no discussions yet re: CF1R reporting updates (& no schema updates initiated).
The only issue I find is that the ducted equipment comes in with 0 CFM. This should be 350. Please add a range check to prevent it from running (I noticed it runs with 0, reports 0, but also requires airflow testing; if 350 is entered it runs, reports 350, requires airflow. Results are the same.)
Some guidance is needed from the CEC on this ticket.
Several new systems were added to CBECC-Res in version 2019.1.3, including those described above - ductless, ducted and ducted+ductless mini-split, multi-split and VRF AC and HP equipment. The AC units in this group allow input of CFM per Ton (with no default) while the HP units do not allow specification of CFMperTon.
Entry of performance characteristics on this screen do not effect analysis, but do impact compliance reports - namely reporting of Airflow Target on the Heat Pump and Cooling HERS Verification tables. When not specified, Airflow Target is documented in the CF1R as 0, and when specified (for AC units), the user entered value is reported here.
Primary question is this - should CFM per Ton be specified for any of these equipment types?
If so, then what limits should be placed on these inputs?
And if not, then should we alter the CF1R's Airflow Target reporting in these HERS Verification tables to list 'n/a' as opposed to '0' (via schema and possibly report template updates)?
For the AC systems we should continue to allow the user to specify CFM per Ton. Additionally, we should perform a range check to prevent the program from running when the user does not specify a value or enters '0'.
For the heat pump systems, CFM per Ton should continue to be hidden, and I prefer that we report 'n/a' rather than '0'.
Last edit: Michael Shewmaker 2021-03-25
Verified using CBECC-Res 2019.2.0 SP2.