Activity tab in model data


The Occupancy model data defines the number people in the space and the times of occupancy. This data is used in Simulations and Cooling design calculations together with the Metabolic heat output of the occupants and Holidays to calculate the heat input to the building.


The Occupancy timing settings may also be used to control internal gains and/or HVAC systems depending on the Model option settings.

Occupancy density

When the Occupancy method is set to 1-Occupancy density you can set the number of people per unit floor area. It is usually most convenient to load this data from the Activity template.

Floor area per person

When the Occupancy method is set to 2-Area per person you can set the floor area per person, i.e. the reciprocal of the occupancy density above. You must check the Occupied checkbox first.

Number of people

When the Occupancy method is set to 3-Number of people you can enter the number of people in the zone directly. In this case note that the value entered at block and building level does not normally inherit very effectively, especially in buildings with zones of very different floor areas. In this case enter the number of people for the most common type of zone at building level. Unless you need to enter specific numbers of people in each zone this option is best avoided as it increases the amount of work involved due to the inheritance mechanism not working effectively for gains that are not normalised by floor area.


The way that Occupancy is scheduled depends on the Timing model data option as described below.



Latent fraction

Occupancy latent gains account for moisture from people in the building due to both perspiration (sweating) and from exhaled moisture. The way that latent gains are calculated depends on the Occupancy latent gains model option.


When this option is set to 2-Fixed fraction then you can enter the latent fraction here. A typical default value is 0.5. Alternatively if this setting is left as the default 1-Dynamic calculation option then the latent fraction is calculated within EnergyPlus at runtime based on internal temperatures and metabolic rate and no additional setting is required here.