Vertical Asset information may be added to an InfoAsset Planner project in a number of ways discussed below.
In this interface in the main InfoAsset Planner drop-down menu, you may import vertical asset information. This import process is similar to the import process associated with other facility data.
Like in other areas of InfoAsset Planner, you can select a table to import into the InfoAsset Planner vertical asset table. The main difference is that unless a custom vertical asset table has already been brought into the InfoAsset Planner project database and mapped using the Facility and Asset Type Manager, all vertical assets imported with this option will be added to a generic vertical asset table.
Another difference is that only set fields can be directly imported to: Level, Type Name, ID, Description, and depending on the import option Parent ID. Fields can be added and manipulated later with the DB Editor or ArcGIS tools, but direct import can only handle these fields.
Import by Hierarchy
With this option your vertical assets must be in the correct order for InfoAsset Planner to organize them in the structured hierarchy. In the basic example shown, the Pump is the facility type and the overall root asset. It is specified as Level 0 then and the unique Facility ID is 'SEW_PUMP1'. Its vertical assets must directly follow it. In the example shown, three vertical assets directly follow it and are on Level 1, while one Level 2 asset is a child asset of PUMPUNIT1 since it is directly beneath it. With this import method, the order of assets is very important.
Import by Parent ID
With this option, vertical assets do not need to be in a specific order. Instead child assets are related to parent assets by specifying a Parent ID. With this import option, an extra field (Parent ID) is necessary in order to import successfully. The Level field is still used to specify where in the hierarchy a particular vertical asset should be placed.