Related Posts with Thumbnails

« Making Design Patterns Work in Practice | Main | 2011 Revit Products Unveiled »

March 22, 2010


Feed You can follow this conversation by subscribing to the comment feed for this post.

- Area analysis: floor areas, site areas, floor space ratios
- Space analysis: 3D volumes (internal & external)
- Stack & Blocking
- Adjacencies: links/distances between building functions
- Building function mix: eg. Apartment mix, and corresponding parking and storage requirements
- Travel distances
- Views
- lighting levels
- Disability access requirements
- Fire separation and escape paths

to name but a few . . .

Good point about a word taking on a new meaning. Our definition of "analysis" has evolved nearly to the point of "anything done outside of Revit". The analysis becomes a black box with inputs and outputs. Our conversation is more about the process of communicating with the black box than the actual analysis. We ask ourselves questions like, which inputs are easier done on the Revit side or the analysis side? How is my data transferred, gbXML, DWG, OBDC? Can I import analysis results to Revit? Is the process easy to repeat? Is it parametric?

These questions tend to result in complicated flow diagrams, that when viewed from a distance tells us simply that software interoperability has a long way to go.

To name a few of the "black boxes":
Peak Heating and Cooling Loads
Annual Energy Consumption
Performance Rating Method
Ventilation and Std. 62 calculation
Detailed Airflow balancing (variable exhaust, occ/unocc modes, pressurization, transfer airflow, etc)
Shading/Light Shelf studies
Daylighting Analysis (peak lighting level, glare)
Daylighting Controls (annual energy savings)

code analysis: It involves area separation calculation for a building on a site.

Also exiting calculations based on occupancies.


The comments to this entry are closed.


  • Subscribe