| Table of Contents | ||
|---|---|---|
|
1. What is this module about
...
The Buildings and Areas module allows you to manage location information and use location this information in other modules. This offers practical benefits in other modules. Some examples:
Requests: Connecting requests to specific buildings or areas helps the Service Desk desk quickly locate and resolve issues.
Reservation ManagementReservations: Reserving areas within buildings, ensuring efficient use of space and better room availability.
Contracts: Linking Buildings buildings or areas to contracts ensures the cost can be tracked per building or area. Leading to better and more data-driven strategic decision-making.
Apart from the use in other modules, the Buildings and Areas module can aid in managing your real estate, as it helps to get insights into the organization's buildings, including details like locationaddresses, ownership, occupancy status, and maintenance history.
...
The next parts will go into more detail on some of the core concepts of this module that are mostly relevant for administrators:
1.1 Categories
Each Every building and area that is created is created in a category. For more general information about categories, see: Categories
The following default categories are available for this module:
Buildings
...
...
Description
...
Building
...
The category for actual buildings uses a page with all the relevant fields to track building information like construction date, owner, status, address, etc.
...
Site
...
The category for sites, e.g., a terrain containing multiple buildings. Has fewer fields than a building.
...
Geographical area
...
The category for Geographical areas, e.g., a complete country or a more conceptual location, does not represent a physical building or site. Containing. Containing even fewer fields.
| Note |
|---|
| Note |
The logical hierarchy based on the building categories is Geographical area -> Site(s) -> Building(s). Buildings with the same category can also have a hierarchy. For example Building -> Sub building(s). The categories do not impact the use of subbuildings and parent/sub buildings. It Technically it is possible to set a building of the category ‘Geographical area’ as a sub building of a ‘building’ category building. However, this might lead to issues if integrations with, for instance, Workplace Experience are used. Other products might have more strict rules for buildings in categories that can be set as children of certain categories. Therefore, if all categories are used, it is advised to use a logic structure (Buildings on the lowest level, followed by sites and on the top level the ‘Geographical area’ buildings) |
Areas
...
Category
...
Description
...
Main area
...
It cannot be selected when creating a new area. Each new building automatically gets a ‘Main area.’ Every additional area is always (directly or indirectly) part of this area.
...
Floor
...
The category for floors. A limited number of fields. It does not contain the options for reservations, as it is not possible to reserve a floor.
...
Meeting room
...
The category for meeting rooms. It also has the option to specify the capacity and can be made reservable (relevant if reservations are used)
...
Workplace
...
The category for workplaces. Has a default capacity of 1 and can be made reservable (relevant if reservations are used)
...
Parking
...
The category for parking spots. Has a default capacity of 1 and can be made reservable (relevant if reservations are used)
...
Area (general)
...
The category for any other type of area that would not fit the other default categories. It also has a capacity field and can be made reservable (relevant if reservations are used)
| Note |
|---|
Areas also have a hierarchical structure. E.g., meeting rooms and workplaces are part of a floor area). The categories do not impact the use of sub-areas and parent areas. It is possible to set an area of the category ‘floor’ as a sub-area of a ‘Workplace’ category area. However, this might lead to issues if integrations with, for instance, Workplace Experience are used. Other products might have more strict rules for the area hierarchy in categories that can be set as children of certain categories. Therefore, if all categories are used, it is advised to use a logical structure (e.g, parking, workplaces, and meeting rooms on the lowest level, followed by floors)have a deviating hierarchy like Building -> Geographical area(s), but this is not advised because this can lead to issues when using Workplace Experience. |
Areas
...
| Note |
|---|
A logical hierarchy based on the area categories is Main area -> Floor(s) -> Meeting room(s) / Workplace(s) / Parking places. It is possible to add another level in the hierarchy between the Floor and the Meeting room / Workplace(s) / Parking places to combine several areas or if it is a specific room with multiple workplaces for example. This extra level can be added with the 'Area (general)' category. |
2. Additional information on this module
...