Requirements for Asset Data
- Last updated
- Save as PDF
General Information
If you want to use an import that contains existing data, then you can download the 150 Asset Export Report, refer to Download a report and prepare an import.
Asset Import
- Each row must represent a single workpoint.
Identify a Building
The import uses the following columns to identify a building and you must include both or one of the columns in the import.
- Building Number
- Building
Identify a Floor
The import uses the following columns to identify a floor and you must include both or one of the columns in the import.
- Floor Number
- Floor
Identify a Container, Asset Name, and Asset Type
The Asset Import also requires the following columns:
- Container - this column is required and must contain a value. If there is no container on the floorplan to link the asset to directly, you can use the floor number instead.
In Serraview you can manually add a new asset without a container but in the import, you cannot add a new asset without a container in an import. If the container does not exist, then use the Zone as the container.
Serraview recommends that you always have a non-zone container - manual or import. This is useful if you want to create custom visual reports or for Locator.
- Asset Name - this column is required
- Asset Type - this column is required
Current Owner and Future Owner columns
These columns only accept the Employee Number.
You can update the future owner the following ways:
- populate the Future Owner column in import and this will populate the Next Step column in the Storage, Lockers or Car Parks grid.
- populate the Current Owner column in import and this will populate the Owner / Contact column in the Storage, Lockers or Car Parks grid.
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. |
Text |
20 |
Yes |
Yes |
Yes |
|
Building Name |
Name of building e.g. 'Headquarters', 'Park Tower', '210 Park Ave'. |
Text |
150 |
Yes |
Yes |
Yes |
|
Floor Name |
Name of the floor e.g. Ground Floor, Mezzanine, 2nd Floor, 3rd Floor. |
Text |
20 |
Yes |
Yes |
Yes |
|
Floor |
Unique identifier for the floor e.g. 02. |
Text |
20 |
Yes |
Yes |
Yes |
|
Container |
This is the container that the asset will be linked to. |
Text |
100 |
Yes |
Yes |
No |
|
Team |
Allocate the asset to a team. |
Text |
100 |
No |
No |
No |
|
Team Id |
Unique identifier of the team. |
Text |
20 |
No |
No |
No |
|
Hood |
Allocate the asset to a hood. |
Text |
50 |
No |
No |
No |
|
Cost Centre |
The cost center of the org unit allocated to this space. |
Text |
20 |
No |
No |
No |
|
Asset Name |
The name of the asset. |
Text |
180 |
No |
No |
No |
|
Asset Type |
The type of asset and the types can be updated in the Asset Category keyword, refer to Keywords. |
Text |
400 |
No |
No |
No |
|
Current Owner |
The name of the person who owns the assets. |
Text |
100 |
No |
No |
Yes |
|
Future Owner |
The name of the person will own the asset in the future. |
Text |
100 |
No |
No |
No |
|
Asset Number |
Unique identifier of the asset. |
Text |
180 |
No |
No |
No |
|
Serial Number |
Unique serial number (or barrel number) of the asset. |
Text |
180 |
No |
No |
No |
|
Comments |
Comments about the asset. |
Text |
3000 |
No |
No |
No |
|
Asset GUID |
The Globally Unique Identifier (GUID) of the asset. |
GUID |
N/A |
No |
No |
No |
|
New Assets Name |
The new name of the asset. |
Text |
180 |
No |
No |
No |
| Any custom fields? |