In the previous post we reviewed how to configure a code based key schedule. Now we'll review how that key schedule integrates with a room schedule to determine occupant load based on room area.
Why is it important that the occupancy calculations are integrated with room schedules rather than area schedules? Occupant load is based on the physical area a person can occupy within a room. Room area is defined to the face of bounding elements whereas Areas (defined with area plan) are typically inclusive of wall cavities, plenums, shafts and other building area incorporated in programming by gross-up factors. Occupancy based on Rooms rather than Areas is also important for analysis and determination of air changes and fire protection. Air changes and fire protection calculations are based on volumes of space. Rooms have volumes; Areas do not. It is also useful to define occupancy type and calculate occupant load based on Rooms rather than Areas when using room schedules as the basis for programming room data sheets. The last point to make for using Rooms rather than Areas to calculate occupancy has to do with exiting. I've yet to find a method to integrate occupant load to exit capacity (door width) and exit load (number of occupants divided by number of exits) but verifying this parametrically should be feasible in the near future or when I find someone who can figure out the boolean formula required for this! (And if you can figure that out I'd also like to make travel distance to exits parametric.)
With a big thanks to Group2's Todd Dutton for bringing this to my attention, this Autodesk webcast is for anyone getting started with creating design visualizations. After this 22 minute overview, you should have a pretty good idea of what to expect, the workflow and the tools involved.
