joesinger12
commented
3 years ago Discussed on 4/20 call w/ NK. Leaning towards 2) to mitigate stopping existing models, with enhancement (by Scott) to allow moving spaces from one Story to another. Add checks Warning would push users to moving spaces to other Stories. NK will confirm w/ CEC.
Original comment by: joesinger12
Refer to Issue 3180 for further implementation/enhancement of IsResCommon functionality. 2019.1.3 implemented Option 2.
For 2019.2.0 need to decide with CEC on Option 3 or Option 4.
8/31/20 DR : The attached is mode good example of a mix-use multifamily project, where the ground floor has Retail spaces, as well as IsResCommon areas. I’m finding that the baseline system map doesn’t handle this too well. In the attached model:
a) The proposed design has the IsResCommon spaces served by a VAV system, and the Retail spaces identified as Core and Shell. This results in the res common VAV system getting the ResCommon HVAC schedule, and the retail spaces getting a separate baseline system with the Retail HVAC schedule. b) The standard design has the entire first floor (ResCommon and retail spaces) served by one VAV system with the Retail HVAC schedule.
This results in the proposed design first floor ResCommon system having more HVAC run time hours than the standard design.
In other words, the way the current IsResCommon rules are structured, there is nothing that prevents mixing and matching this input on a Story basis. Therefore, in cases where the baseline system type is floor-by-floor, there is no guarantee that the proposed and baseline system HVAC avail schedules will be the same because in the baseline system does not necessarily map to the same system type/scope as the proposed. I can’t recall if we discussed this situation when we initially scoped the IsResCommon, but the way it is currently implemented, it really only seems to be suitable for projects that don’t have mixed-use Stories, i.e. stories with both res common and other non-res spaces on them.
I can only think of a few solutions to this: 1) No not allow the IsResCommon input on floors that mix/match among non-res spaces on a given Story. The user would get a Error that they needed to change the model 2) Ignore the IsResCommon input on floors that mix/match among non-res spaces on a given Story. The user would get a warning that the input was going to be ignored. In this case, all the spaces/zones/systems on the floor will get the same HVAC schedule, regardless of IsResCommon. The schedule used would be based on the predominant schedule type (similar to what we have now). 3) Revise the baseline system map to describe an separate system type for ResCommon areas. This is outside the scope of what we could do for v1.3, but I list here for future consideration 4) Revise the criteria of the Retail system scope to allow it apply to mid/highrise mixed-use residential. This is outside the scope of what we could do for v1.3, but I list here for future consideration
Reported by: joesinger12
Original Ticket: cbecc-com/tickets/3239