Hevacomp -> OpenBuildings Designer Transition?

Great to see that OBES will now be able to import Hevacomp's Design Database. I think that users will benefit from the advanced CAD modeling tools available in OBES. Assigning and updating all those fabric materials to the model should be a lot quicker.

I am curious about what happens after the Hevacomp model is imported? Will the model still be hot-linked to Hevacomp so that users can still use Hevacomp to run calcs or make/receive changes?

In any case, are there are any plans for transfering Hevacomp's analytical tools to OpenBuildings Designer.

Electrical Designer: Connect

Mechanical Designer: Netsys

Both I think would be useful in OBD as there is currently very little in the way of analytical / schematic design tools in OBD.

  • Hi Dominic,

    Once a Design Database model is imported, OBES should be used to make any changes to the model and run calculations. Hevacomp calculations such as CIBSE Gain and Heat Loss, along with Dynamic Simulation, are all present in OBES. The Hevacomp project will remain unaffected.

    Many aspects of Netsys are actually complete and available also - single-line duct sizing with the ability to promote to full 3-D duct model is already available in OpenBuildings Designer - please see training on this on the LearnServer at Mechanical BIM M201: HVAC Design. Development on similar for pipe sizing has been ongoing also, and will continue.

    Product management are formulating plans for the electrical aspects, so for the time being users should continue to use Hevacomp for the electrical Connect calculations, however Daylighting aspects of Nimbus are available already - eg see WIki articles here and here.

    Shane Regan | Principle Building Performance Support Engineer

    Hevacomp to OpenBuildings - A complete guide for every user |  Bentley Communities

        

    Answer Verified By: dominic SEAH 

  • Hi Shane,

    Many thanks for the response.

    Hevacomp users have been and continue to be a key part of the ecosystem necessary to create sustainable buildings. I suppose that the biggest benefit it has for its aging users is its familiarity, gained over the years. The challenge will be to transition as many as possible across to the new promised land? Looks like the DB import process is one-way/time only.

    OTOH, looking at the UK Bldg Regs, it is remarkable how much something like Hevacomp can contribute, especially when fully integrated into a multi-disciplinary platform like OBD.

    Part E: I am still hopeful that AES' ASM will incorporate the acoustic dimension of the 'BIM' model one day. So much building performance and fabric material info is already captured spatially in the Design Database / ASM. It would be a shame not to be able to use it to help create better acoustic environments... efficiently.