Story 1: Archibus to Serraview Data Mapping
(Export Archibus Data to Serraview and Send Data Back to Archibus)
Below is a list of the pre-processors, focusing on the input files, transformations and output files. Note that the output file names indicate the associated import (e.g. sv_exp_dp.csv
will be consumed by 01 OrgUnit, emit a file named orgunit.csv
, and then run an OrgUnit import using that file).
Note:
- Uuids are used to identify data between the systems, and must not change. In case of a reset, back them up.
- Uuids are assigned once per record when the integration is run.
Preprocessor | Input | Transformation | Output |
---|---|---|---|
01 Org Department |
Unit sv_exp_dp.csv
|
Start with "Archibus", "0000", "ROOT" For each row:
|
orgunit.csv
|
02 Building & Floor |
sv_exp_rm.csv
|
Mapping:
For each row:
|
building.csv
floor.csv
|
03 Floorplan | Builing_Floor.dwg | Translates file names by prefixing BuilingName_FloorName.dwg with FloorID_ so file(s) can be imported to correct floor by FloorPlan Importer (FPI). | FloorID_Builing_Floor.dwg |
04 Room | As per preprocessor 02 |
As per preprocessor 02, but with the following additions:
|
workpoint.csv
|
05 Person |
sv_exp_em.csv
|
Mapping:
For each row:
|
person.csv
occupancy.csv
|
See also
Story 1 Overview: Add Serraview Space Planning & Optimization to an Archibus Deployment