Import Infrastructure
This pages describes how to import infrastructure and components in Pathfinder.
Select the import infrastructure option from the import and export section.
You can import locations, nested infrastructures and nested components into your Pathfinder network to manage.
Â
Â
Select Scheme
Â
The ability to import infrastructure allows you to quickly and easily create a large amount of infrastructure and components in a nested hierarchy in Pathfinder.
Select the type of scheme you want and click Next.
You can also load schemes and save as templates here.
Please make sure to set your column headers with the same title as the current scheme. The fields are case sensitive.
Â
Select File
Â
Click on load from file to import the file from your local system. The function supports Excel file types for import.
Click on in Pathfinder Next to execute the file import.
Â
Here is an example schema file and the corresponding excel infrastructure import file. You can use this template as the base for your network.
Â
Import Infrastructure Schema File:
Â
Import Infrastructure Excel File:
Â
Â
Fields for Importing Infrastructure
The constants are unique names in the system and refers to an importable field. Identifying constants are used for clear distinction between entries. For floors and rooms the identifying constant can either be its name or its number.
Â
Identifying constant | Mandatory fields | Data type | Description |
---|---|---|---|
CampusLatitude | Â | Double | Latitudinal position of the location |
CampusLongitude | Â | Double | Longitudinal position of the location |
CampusName | X | Text | Location name |
CampusShortName | Â | Text | Location short name |
CampusStreet | Â | Text | Location street |
CampusZip | Â | Text | Location ZIP |
CampusCity | Â | Text | Location city |
CampusCountry | Â | Text | Location country |
CampusDescription | Â | Text | Location description |
BuildingLatitude | Â | Double | Latitudinal position of the building |
BuildingLongitude | Â | Double | Longitudinal position of the building |
BuildingName | X | Text | Building name |
BuildingShortName | Â | Text | Building short name |
FloorName | Â | Text | Floor name |
FloorNumber | (X) | Text | Floor number |
FloorShortName | (X) | Text | Floor short name |
FloorFilePath | Â | Text | Path to a file attached to a floor |
FloorFileMode | Â | Text | Valid values: Link, DB, LinkAsBg, DBAsBg Link = as a link to the file DB = file is saved in database LinkAsBg =Â as a link to the file and used as background DBAsBg = file is saved in database and used as background default value: DB |
RoomName | (X) | Text | Room name |
RoomShortName | Â | Text | Room short name |
RoomNumber | (X) | Text | Room number |
RoomDescription | Â | Text | Room description |
RoomHeight | Â | Text | Room height (optional) |
RoomWidth | Â | Text | Room width (optional) |
RoomLength | Â | Floating-point number | Room length (optional) |
RoomArea | Â | Floating-point number | Room area (optional) |
ComponentDefName | X | Text | Component definition name (must match catalog) |
ComponentName | X | Text | Component name (must be unique in its room) |
ComponentNameNew | Â | Text | Use this to update a component name |
ComponentDescription | Â | Text | Component description (optional) |
ComponentComment | Â | Text | Component comment (optional) |
ComponentSlotPosition | Â | Text | Slot position in parent component (only required for built-in components) |
ParentSlotNumber | Â | Integer | Slot number in parent component for the module |
ComponentImportAsModule | Â | Boolean | Define whether the component is a module or not |
ComponentBayPosition | Â | Text | Bay position in parent component (only required for built-in components) |
ComponentLayerNumber | Â | Integer | Layer in a cabinet, default=1 (optional) |
ComponentLeftOffsetMM | Â | Integer | Component left offset in a cabinet (optional) |
ComponentBurdenCentre | Â | Text | Burden center (optional) |
ComponentInventoryNumber | Â | Text | Inventory number (optional) |
ComponentSerialNumber | Â | Text | Serial number (optional) |
ComponentServiceNumber | Â | Text | Service number (optional) |
ComponentGuarantee |  | Text | Guarantee (optional) |
ComponentLastMaintenance | Â | Date | Last Maintenance (optional) |
ComponentMaintenanceCycle | Â | Text | Maintenance Cycle (optional) |
ComponentEAN | Â | Text | European article number (optional) |
ComponentPurchaseDate | Â | Date | Purchase Date (optional) |
ComponentInstallationDate | Â | Date | Installation Date (optional) |
ComponentWarrantyContract |  | Text | Warranty Contract (optional) |
ComponentWarrantyEnds | Â | Date | End of Warranty (optional) |
ComponentKnownIssues | Â | Text | Known Issues (optional) |
ComponentMacAddress | Â | Text | Mac address (optional) |
ComponentReverseMounting | Â | Integer | Reverse mounting (0=no, 1=yes) (otional) |
ComponentValue | Â | Floating-point number | Component value (optional) |
ComponentDepreciationDate | Â | Date | Depreciation date (optional) |
ComponentFQDN | Â | Text | Fully qualified domain name (optional) |
ComponentOS | Â | Text | Operating system (optional) |
ComponentConfiguration | Â | Text | Configuration (optional) |
ComponentResponsibleContact |  | Text | Responsible Contact (optional) |
ComponentURL | Â | Text | URL (optional) |
ComponentExternalRef | Â | Tex | External Reference (optional) |
ParentComponentName | X | Text | Parent component name (must be unique in its room, can be left empty) |
SlotName | X | Text | Slot name |
PortName | Â | Text | Port name |
PortNumber | X | Integer | Port number |
PortNumberNew | Â | Integer | New value for port number |
PortDescription | Â | Text | Port Description |
InletDefName | X | Text | Inlet's component definition name (must match catalog) |
InletName | X | Text | Inlet name |
CustomString1 (to 8) | Â | Text | Custom Text fields |
CustomInteger1 (and 2) | Â | Integer | Custom Integer Fields |
CustomDate1 (and 2) | Â | Date | Custom Date Fields |
CustomFloat1 (and 2) | Â | Floating-point number | Custom Floating-point number Fields |
Â
Â
Â