Requirements for Building Data
General Information
Description – A list of the buildings to be managed in Serraview. The building data is used to set up the foundation of your Portfolio data.
Building data such as location, leasing information, budget, rating, the annual cost to maintain a building, and other key building information is collected and loaded into Serraview to create a central repository of all real estate information. This information is collated with data for floors, allocations, and occupancy to provide reporting that gives high visibility over the portfolio.
Common Data Sources – The list may come from existing building management or leasing system (such as an IWMS, CAFM, or HR system) or a manually prepared spreadsheet.
Recommended Refresh Frequency - The building data can be updated in sync with when your Corporate Real Estate team publishes updates.
Custom Fields - If you have any custom fields to be included, then inform your Eptura Onboarding Manager as custom fields must be configured in Serraview prior to import.
Custom fields that are not part of the original scope of work for the implementation, will be considered a modification that will incur an additional cost. Any modifications will require a change request to be created.
File Updates – Data files can be used to update and add buildings. All file updates must be full files, no deltas.
Building Import
The Building Import requires the following:
- Each row must represent a single building.
Identify a Building
The import uses the following columns to identify a building and you must include one of the columns in the import.
- Building Number
- Building
Data Dictionary
The table below lists the columns and the required columns and values are shown in blue text.
|
Column Name |
Description |
Data Type |
Max Length |
Column Required |
Value Required |
Unique in this file |
|---|---|---|---|---|---|---|
|
Building Number |
Unique identifier for the building. It is usually generated by your leasing system. |
Text |
20 |
Yes |
Yes |
Yes |
|
Building Name |
Name of building e.g. 'Headquarters', 'Park Tower', '210 Park Ave'. It is the name that will display on your reports. |
Text |
150 |
Yes |
Yes |
Yes |
|
Short Name |
An abbreviation for your building name e.g. 210 Park, which can be used on reports where space is a premium. A unique name is recommended. |
Text |
20 |
No |
No |
No |
|
Street Address |
Street number and the name. e.g. '1000 Main Street' |
Text |
150 |
Yes |
Yes |
No |
|
City |
City name. |
Text |
100 |
Yes |
Yes |
No |
|
Standarized Country |
Group 'Country identification' Country name from a statndardized list. |
Text Lookup |
Yes |
Yes |
No |
|
|
Standardized State |
State name from a standardized list. |
Text |
No |
No |
No |
|
|
Different Report Location |
Do you want a different report location? Yes; No |
Boolean |
N/A |
No |
No |
No |
|
State |
Use the full name or an abbreviation. Use a consistent standard across the data. |
Text |
100 |
No |
No |
No |
|
Postcode |
Post code or zip code. |
Text |
50 |
No |
No |
No |
|
Country |
Use the full name or an abbreviation. Use a consistent standard across the data. |
Text |
100 |
Yes |
Yes |
No |
|
Region |
Geographic region, e.g. East Coast. The lookup values need to correlate to the configured region hierarchy. See the section on Region Hierarchy Data. |
Text |
200 |
Yes |
Yes |
No |
|
Description |
Building description such as style, condition, primary use, whatever would be useful. |
Text |
2000 |
No |
No |
No |
|
Building Type |
Type of building and can be anything meaningful to your reporting requirements, such as: HQ, Office, Branch. |
Text |
200 |
No |
No |
No |
|
Show in VBS? |
Accepted values: Yes/No, True/False, One (1)/ Zero (0) or Blank (false) |
Boolean |
N/A |
No |
No |
No |
|
Show in Portfolio Dashboard? |
Accepted values: Yes/No, True/False, One (1)/ Zero (0) or Blank (false) |
Boolean |
N/A |
No |
No |
No |
|
Show in Workplace portal? |
Accepted values: Yes/No, True/False, One (1)/ Zero (0) or Blank (false) |
Boolean |
N/A |
No |
No |
No |
|
Show in Mapping? |
Accepted values: Yes/No, True/False, One (1)/ Zero (0) or Blank (false) |
Boolean |
N/A |
No |
No |
No |
|
Show in Wayfinding? |
Accepted values: Yes/No, True/False, One (1)/ Zero (0) or Blank (false) |
Boolean |
N/A |
No |
No |
No |
|
Location Integration |
Accepted values: Yes/No, True/False, One (1)/ Zero (0) or Blank (false) |
Boolean |
N/A |
No |
No |
No |
|
Restricted Access? |
Accepted values: Yes/No, True/False, One (1)/ Zero (0) or Blank (false) |
Boolean |
N/A |
No |
No |
No |
|
Comments |
Additional building information. |
Text |
100 |
No |
No |
No |
|
Location type |
Accepts the following values:
|
Text |
No |
No |
No |
|
|
Latitude |
GIS Information |
Decimal |
(20,9) |
No |
No |
No |
|
Longitude |
GIS Information |
Decimal |
(20,9) |
No |
No |
No |
|
Time Zone |
Accepts valid time zone values from the time zone keyword set. |
Text |
No |
No |
No |
|
|
Lease expiry |
Date of the next lease expiry in the building |
Date |
- |
No |
No |
No |
|
Lease land lord |
Name of the landlord |
Text |
30 |
No |
No |
No |
|
Lease options |
Summary of lease renewal options (e.g. 2x5) |
Text |
30 |
No |
No |
No |
|
Lease type |
Freehold, Leasehold |
Text |
200 |
No |
No |
No |
|
Tags |
Tagging is a labeling system for entities in Serraview; learn more in Tagging. |
Text |
No |
No |
No |
|
|
Any custom fields? |