Skip to main content

#2 - Buildings, Floors, and Floorplans

Eptura Knowledge Center

#2 - Buildings, Floors, and Floorplans

Initial Set up of Regions, Buildings, and Floors


Summary

Below is a summary of the process.

  1. Customer provides a list of buildings and floors and other information such as leases.
  2. Serraview Implementation team creates the regions.
  3. Serraview Implementation team imports in buildings and floors.

Prerequisite

Customer provides a list of buildings and floors and other information such as leases.

Step 1. Manually Set up the Regions (Serraview Implementation team)

Before you load up your Buildings and Floors, your regions must be setup. These are used in the hierarchical grouping of buildings. To understand what data is required, refer to Region Hierarchy Data.

  1. Set up the regions manually, refer to Modify the Regions Keyword.
  2. After the regions are set up you can verify the Region Hierarchy is correct, refer to Validate Region Hierarchy.

Step 2. Set up the Import Files (Serraview Implementation team)

Depending on the number of buildings and floors you have, it may be quicker to add them using a bulk import. To understand the what data is required, refer to:

Building Import Template

The table below lists the columns for the import.

Column Name Building Number  Building Name  Short Name  Street Address City State Postcode Country Region
Column Required? Required
 
Required Optional Required Required Optional Optional Required Required
Description

Unique number for the building. It is usually generated by your leasing system.

Name each building is commonly known as and it is the name that will display on your reports.

An abbreviation for your building name which can be used on reports where space is a premium. A unique name is recommended.

Street number and name. City name.

Use the full name or an abbreviation. Use a consistent standard across the data.

Post code or Zip code.

Use the full name or an abbreviation. Use a consistent standard across the data.

Geographic region. The lookup values need to correlate to the region hierarchy.
Example 102923  210 Park Ave

210 Park

2 Wall street  New York NY 10017 United States  New York

Download the template: Building Import Template.csv

Floor Import Template

The table below lists the columns for the import.

Column Name Building Number Building Name Floor Number Floor Sequence NLA Show in VBS?
Column Required? Required Required Required Required Optional Optional Optional
Description

Unique number for the building. It is usually generated by your leasing system.

Name each building is commonly known as and it is the name that will display on your reports. Unique identifier of the floor. Floor name Order to display floors from the bottom up. For example:
Ground Floor would be 0
1st Floor would be 1
Mezzanine would be 2
2nd Floor would be 3
This information is important to display the floors in the correct order (bottom to top).
Net Lettable Area for each floor. This is the NLA from your lease information. 

Do you want this floor to display in the Visual Block and Stack?

Either Yes;No

Example 102923 210 Park Ave 5 5 5 1,911.11 Yes

Download the template: Floor Import Template.csv

Remember

  • You may have some floors within Serraview that you need for space management, but they are not relevant to employees who use Engage. Therefore, set the value in the Show in Wayfinding? column. When this column is set to Yes, then the floor will be visible to your Engage users.
  • If you need to adjust what buildings and floors are visible, this can be done later, refer to Set up the Space Types for Engage.

Step 3. Import in the Buildings and Floors Data (Serraview Implementation team)

Serraview Implementation team will import in the Building and Floors.

Step 4. Verify the Imported Data (Customer)

After the data has been imported in you can verify the buildings and floors have uploaded correctly, refer to Validate Building and Floors Data.

Initial Set up of Floorplans


We have a Floorplan Importer processor that automates the floorplan drafting and mapping process. Floorplan Importer can read .dwg files and apply the correct polylines and space mapping with minimal intervention, making it quick and easy to upload large portfolios.

Upload Methods

We provide the following methods for uploading new or revised CAD files:

  • Floorplan Importer Tool – This can be used for CAD technicians who want to load plans on their own schedule and change the default settings.
  • File Upload – This can be used for CAD technicians who want to load plans on their own schedule, as the plans are ready. In the File Upload, use the automated floorplan option.
  • SFTP – This can be used for CAD technicians who want to bulk load plans into Serraview.

For the process of how the Floor Importer uploads a new floorplan, updates an existing floorplan, updates space properties, or export, update and then reload the floorplan, refer Floorplan Importer.

Prerequisites

If you want to use the Floorplan Importer, first read Serraview CAD Preparation and Serraview CAD Preparation FAQ and remember the Floorplan Importer must be configured by the Serraview Implementation team.

When the floorplans (DWG format) will need to meet the following required standards:

  • Floorplan file as a DWG (AutoCAD).
  • Floorplan markup identifying workpoint names and space types, if these are not identified in the DWG file.
  • All spaces require unique names. If a space does not have a unique name, we can apply a default unique name on your behalf.

Upload the Floorplans

The following options detail how the floorplans are uploaded.

Option 1. Floorplan Polylining and Migration

  1. Customer provides floorplans that have been prepared as per our Serraview CAD Preparation guide (including supporting document that has the spaces names) via File Upload using the option Other.
  2. Serraview Implementation team sends floorplans to third-party company to complete the polylining.
  3. Serraview Implementation team to set up the DWG Template Schema. The schema is an XML code that will enable Serraview to read the AutoCAD file and translate it into mapped spaces.
  4. Serraview Implementation team uploads the CAD files into Serraview.
  5. Customer verifies the floorplans in the Spaces module.

Option 2. Floorplan Polylining and Upload

  1. Customer sets up the CAD as per our Serraview CAD Preparation guide.
  2. Customer requests to Serraview Implementation team to have the Floorplan Importer set up.
  3. Serraview Implementation team to set up the DWG Template Schema. The schema is an XML code that will enable Serraview to read the AutoCAD file and translate it into mapped spaces.
  4. Customer uploads the floorplans using Floorplan Importer Tool and there are articles on the ways you can use the tool, refer to Floorplan Importer Tool Usage.
  5. Customer verifies the floorplans in the Spaces module.

Initial Set up of Space Types for Engage


You can configure whether the spaces are Hidden, Visible, or Interactive on the floorplan and this is based on their Space Type.

image2021-7-16_8-7-21.png

The following options can be applied to each Space Type:

  1. Hide the space type all together - these spaces appear as "negative space" and indicate to the user that they should be able to walk through that space. All circulation space types (corridors, ground floor atriums, elevator lobbies, etc) should be hidden. 
  2. Show (visible) the space type but do not let the user interact with the space - you normally want to make all non-occupiable spaces visible. They are shown in light-grey and indicate that there's a space there, but there's nothing interesting for the user to interact with
  3. Make the space interactive - all desks and meeting spaces that you want users to interact with via Engage should be interactive. You might want to make some spaces like kitchens or storage spaces interactive if they are important for your users to find out more about.  

For more information, refer to Set up the Space Types for Engage.

Next Onboarding Step


  • Was this article helpful?