I don't use Rooms to calculate anything but the net area within a room, or
to use in energy analysis (gbXML export). They certainly would not be
appropriate for BOMA calculations because no matter how you set them up,
they will always calculate to the same location in every wall, regardless of
the condition at the wall. Additionally, frequently a good number of rooms
can be grouped together under the same BOMA classification (Commons Space,
Office or Retail, etc.).
For that reason, Area Plans are the tool of choice for BOMA Calculations.
You can prevent Revit from creating the area boundaries and applying area
rules automatically, therefore you don't have to worry about whether or not
it's putting the boundary lines in the correct place. You can draw all of
them manually, based on your judgement as to where they need to go, whether
to the face of glass or the face of the wall, which face of the wall, etc.
Note the two attached images. One is an area plan, the other shows the
individual rooms - it should be obvious which is which. (Yes, I know this is
an extremely inefficient building - it's a training file).
"Jazzster11" wrote in message news:6402226@discussion.autodesk.com...
> I'm obviously doing a poor job of explaining.
>
> How do YOU go about performing area calculations within Revit?
>
> I usually am just asked to provide GSF numbers, so I have been setting up
> area plans and using area boundaries to ensure that Revit is including
> only what I want it to include.
>
> Others have been asked to provide BOMA based departmental areas, and I
> think we would have to use rooms to calculate this properly. The problem
> is that at least one person in my office has noticed that Revit calculates
> the room boundary at a curtain wall differently than at a window, and BOMA
> has specific guidelines based on wall area for where the boundary should
> be for the net square footage calculation.
>
> In my original post I was attempting to find out whether a solution had
> been developed for this issue since the release of Revit 2009.
>
> Thanks Matt.
>
> - Alex