I have found some situations where equip-level fan tags would be useful on AHUs. I imagine these would be very similar to hotWaterHeat, elecHeat, or chilledWaterCool, and would serve a similar purpose; that is, to indicate the presence of certain ahu sub-components. My initial proposal for the tags are: • dischargeFan: Indicates that a unit has a fan in the discharge section. • returnFan: Indicates that a unit has a fan in the return section. • outsideFan: Indicates that a unit has a fan in the outside section. • exhaustFan: Indicates that a unit has a fan in the exhuast section. Let me know your thoughts.
https://project-haystack.org
Brian FrankFri 1 Mar 2019
For project level work, I see a lot of people do stuff like that. To actually standardize it is tricky, because essentially you could make that case about using a marker tag to note any sub-component of something. We are actually working towards modeling the ductwork in AHUs in WG 551 so some of this might fall out of that.
mr lee Thu 28 Feb 2019
I have found some situations where equip-level fan tags would be useful on AHUs. I imagine these would be very similar to hotWaterHeat, elecHeat, or chilledWaterCool, and would serve a similar purpose; that is, to indicate the presence of certain ahu sub-components. My initial proposal for the tags are: • dischargeFan: Indicates that a unit has a fan in the discharge section. • returnFan: Indicates that a unit has a fan in the return section. • outsideFan: Indicates that a unit has a fan in the outside section. • exhaustFan: Indicates that a unit has a fan in the exhuast section. Let me know your thoughts.
https://project-haystack.org
Brian Frank Fri 1 Mar 2019
For project level work, I see a lot of people do stuff like that. To actually standardize it is tricky, because essentially you could make that case about using a marker tag to note any sub-component of something. We are actually working towards modeling the ductwork in AHUs in WG 551 so some of this might fall out of that.