#1173 Forced air chilled beams

Hiroko Masuda Fri 1 Aug

I have many variations of chilled beam systems to characterize using Haystack. One of them is forced-air chilled beams. I put airRef on the chilledBeam equip, but it appears to be violating the Haystack scheme because a chilledBeam equip doesn't have an air-input. Since forced-air chilled beam is a pretty common system in the industry, I thought it would allow users to select whether it is active or passive. What's odd is that there is a tag called chilledBeamZone, which is for AHUs. That means Haystack knows some AHU supply air to chilled beams. But it doesn't allow users to reference the air source on the chilled beam equipment. Am I missing something?

If anyone has a well-established method for tagging the water-side and air-side of chilled beam systems, could you share your tagging scheme here? I know we have to create our own scheme or method eventually to cater to our applications, but I want to learn from other users as much as possible.

The air path of the chilled beam system I mentioned above is: AHU - VAV/CAV - primary air of multiple chilled beams. And the same AHU serves VAVs/CAVs that don't have chilled beams also. And, of course, the water-side zoning doesn't match the air-side zoning.

Login or Signup to reply.