Lack of data integrity is the most common reason that Serraview statistics in the Block and Stack (VBS) may appear incorrect. Below details some of the key issues Corporate Real Estate teams encounter and how to fix them:
Org Unit Structure contains Orphans
As your organization changes, you may find that teams in the VBS have become "orphaned". This means that either they or their parent org unit have been changed or moved in the org unit structure, and Serraview no longer recognizes where that team sits within your business. When this happens, you may find unexpected results viewing statistics when selecting org units, particularly at a high level in your org unit structure, as it may not be immediately apparent that a team has been orphaned.
You can find out if any of your teams have been orphaned, by:
- Navigate to the building.
- From the Legend area, click the Advanced button.
- From the Color By drop-down select Org Unit.
- From the Group By drop-down to Org Unit Level 1.
- Click the Teams tab.
- Review the teams listed for any teams that have been orphaned.
Also, you can run 36 Detailed Building Stack Report against Orphan Org Units in the Reports module to see all stacked teams that have been orphaned within your building.
Your System Administrator is responsible for managing the Orphan Org Units. For more information, refer to Update Orphan Org Units.
Incorrect Occupancy Data
If your occupancy data is incorrect, then your People, Occupancy Ratio, Opportunity and Utilization statistics will not display correctly.
The common methods to update VBS occupancy are:
- use the Serraview Workplace portal – refer to Workplace Portal.
- use the Occupancy Import via My Imports – refer to Occupancy Import.
- automate occupancy using a Serraview pre-processor – refer to Methods of Data Transfer.
- manually update occupancy data via the workpoint or team form – refer to Block and Stack (VBS).
Incorrect Space Mapping
If you want to have a space with zero workpoints, it is important to remember which space types count as zero when reviewing statistics in the VBS.It is possible to allocate a space to a team where the space has zero workpoints. This affects the appearance of statistics such as Opportunity and Capacity. This can happen when you choose the wrong space type initially, or you change a space type and forget to check the number of workpoints that the space has.
You can change the workpoint count on an individual space.
From the VBS, complete the following:
- Click the Edit Mode button.
- Navigate to the space.
- Double click the space. The Update space form displays.
- In the Workpoints field, enter in the number of workpoints.
- Click the Update Space button.
If you have multiple spaces that have been mapped incorrectly with zero workpoints, they can be updated in bulk using the following methods. This is usually the responsibility of your System Administrator.
For a select group of spaces, use the Workpoint Import to update the workpoint count for the affected spaces, refer to the Workpoint Import and VBS.
Update All Mapped Spaces
For all mapped spaces of a particular space type.
- Navigate to Admin Settings > Reference Data > Space Types.
- Click on the space type to edit it.
- From the Default Attributes tab, check the Can have workpoints checkbox.
- Click the Update Space Type button.
Incorrect Target Ratios
When setting up Serraview, a default target ratio is applied to the entire portfolio. This target ratio then filters down as the default target ratio for each new Building, Floor, Neighborhood or Team. This default can be overridden.
If you change the target ratio for a building, that default target ratio for the building is the one that gets filtered down as the default to its floors, hoods and teams.
If you change the target ratio for an individual floor, the building target ratio is not affected, however any hoods or teams added to that floor will default to the floor's target ratio.
If you change the target ratio for a neighborhood, the building and floor target ratios are not affected, however any teams created in that neighborhood will have their target ratio default to the neighborhood's target ratio.
If you change the target ratio for a team, the building, floor (or neighborhood) target ratios are not affected.
This flexibility in target ratios can lead to flexible teams being set to a target ratio of 1 (a "fixed" target ratio). This can affect the expected Capacity and Opportunity statistics, particularly when this is viewed at a high level of your Org Unit structure.
Update Target Ratios
On the building, floor, neighborhood, and team forms, there is a Target Ratio checkbox that is checked. This means that the default is being applied, in the cascading order described above: Portfolio, Building, Floor, Neighborhood, then Team.
You can change the target ratio.
- Uncheck the Target Ratio checkbox.
- In the target ratio field, enter the number.
For more information on changing the target ratios, refer to the following topics:
When you overstack a neighborhood or a floor, the Capacity, Opportunity, Occupied, Unoccupied and Occupancy Ratio statistics can all be impacted. For more information, refer to Stack Warnings. It is possible to allocate more desks to teams than could physically fit inside a Neighborhood, or on a Floor. Warnings shown against Floors and Neighborhoods provide a visual of when this has occurred. When this occurs, it is called overstacking.