Beginning with OTbase Asset Center 6.5, you can import data directly from Excel without the need for an intermediate Python script under certain conditions.
Naming Convention for Device Data Spreadsheet
When importing a spreadsheet that contains device metadata, your column headers must correspond to the field names used by OTbase Asset Center. In other words, make sure your file's column headers match up with the ones used by OTbase Asset Center. Doing this allows OTbase to better understand the values being imported.
The following field names should be used as the column headers in your device data spreadsheet.
Column Header | Description |
---|---|
deviceId | required if Device name isn’t present |
name | required if Device ID isn’t present |
description | device description (e.g. "access switch conveyer belt 5") |
stage | device lifecycle stage (installed, operational, testing, ...) |
serialNumber | serial number |
zone | network zone |
safety | device safety classification (not identical to criticality) |
criticality | device criticality rating (e.g. SAFETY) |
hardware.vendor | manufacturer of the device (e.g. Cisco) |
hardware.model | product model (e.g. ENBT/A) |
hardware.type | hardware type (PLC, Printer, RTU, ...) |
hardware.version | hardware product version |
hardware.orderNumber | hardware order number |
hardware.description | hardware product description |
context.location | location name (use "/" to indicate hierarchy) |
context.locationId | location ID |
context.otSystem | OT system association, e.g. machine line |
context.deviceGroup | device group association |
extended.columnName | references a custom field defined in OTbase Asset Center |
When using a spreadsheet to update device metadata, you must include a column for either the deviceId
or device name
. (The latter will work only if there are no duplicate devices using the same device name). Referring to devices by their deviceId
or name
allows the system to correctly identify and update the devices, preventing potential errors. So, when preparing your spreadsheet, be sure to add this essential information for accurate and efficient updates.
Note: If you will be creating new devices, you must include a deviceId
column in your spreadsheet import.
Handling Extended Fields
In Asset Center, users can define custom fields, which are fields that are specific to their needs and are referred to as extended fields in OTbase. Extended fields can also be updated via Excel spreadsheet and follows the format of extended.columnName where columnName is a placeholder for your custom field name. For example, if you defined a field named MTTR in Asset Center, then column name in your Excel spreadsheet should be extended.MTTR.
Naming Convention for Location Data Spreadsheet
For locations you can use the following column names:
Column Header | Description |
---|---|
locationid | A short location id for the location is required |
name | The name of the location is also required |
description | location description |
referencelocation | is this location a reference location? (Yes | No) |
address | postal address (street, city, state, ...) |
gps | GPS lat/lon |
company | company owning or operating the location |
group | location group |
Note: Your Excel spreadsheet must always contain a column labeled locationId.
Importing Your Excel Spreadsheet
After you have properly formatted your Excel spreadsheet, you can now import it into OTbase Asset Center.
For devices, use the first dialog. For locations, use the second dialog and for systems, use the third.
You will be prompted to select your local file, which will then be processed.
Note: If you are not sure about the accuracy of your column names and the validity of your data set, it might be a good idea to create a backup of the existing database before performing the import, so that you can always go back to the previous state if things go south.
Comments
0 comments
Please sign in to leave a comment.