Occupancy settings
Define when a workspace is in use, so that occupancy figures ignore nights, weekends, and closed days.
Occupancy settings tell akenza when the space a workspace represents is actually in use. Hours outside that window are excluded from aggregations (by setting filter working hours on a dashboard component or when querying data using the akenza REST API), so a dashboard reports data during working time rather than averaging it across nights, weekends, and days the building was closed.
This matters because the two are very different numbers. A meeting room used solidly from 09:00 to 17:00 is fully utilized, but measured across the whole 24 hours it looks like a third empty.
Working days and hours
Working days
The days of the week that count. Select the days that apply, for example Monday to Friday.
Working hours
The daily window that counts, given as From and To, for example 09:00 to 17:00.
Lunch break
Optional. A window inside working hours to leave out, for example 12:00 to 13:00.
Times are interpreted in the workspace time zone, which is set at the top of the General settings page.
Public holidays
Exclude public holidays from occupancy aggregation leaves out the public holidays of a regional calendar, shown next to the toggle as a region code such as CH-ZH. Select View the list to see exactly which dates will be excluded before you rely on it.
Excluding and including specific days
Two further toggles handle the days a calendar cannot know about:
Exclude specific days. Individual dates to leave out, such as a company shutdown between Christmas and New Year. Add one date per entry with Add option.
Include specific days. Individual dates to count even though they would otherwise be excluded, such as a Saturday when the site was open for an event.
Included days take precedence, which is what lets you keep a normal working week while making a one-off exception.
Changing these settings changes how data is aggregated. Figures for a period may therefore differ from figures you read before the change, so it is worth agreeing the working pattern with whoever uses the dashboards before adjusting it.
Last updated
Was this helpful?