Skip to content
Release: Australia · Updated: 2025-07-31 · Official documentation · View source

Mandatory fields in the bulk import spreadsheets

A list of the mandatory fields in the model, asset, and model and asset templates for bulk import in the Enterprise Asset Workspace.

Mandatory fields for model template

Field/columnMandatory for creating modelsMandatory for updating models
IndexNote: Representing the row number can be used to identify a specific row. However, you must fill this in manually.YesYes
ManufacturerYesYes
Model NameYesYes
Model NumberYesYes
Model categoryYesYes
Model typeYesYes
Parent model manufacturerYesNote: Not applicable for single models.No
Parent model nameYesNote: Not applicable for single models.No
Parent model numberYesNote: Not applicable for single models.No
Component numberYesNote: Not applicable for single models.No
Component quantityYesNote: Not applicable for single models.No
RequiredYesNote: Not applicable for single models.No
Hot swappableYesNote: Not applicable for single models.No
RepairableYesNote: Not applicable for single models.No

Mandatory fields for asset template

Field/columnMandatory for creating assetsMandatory for updating assets
IndexNote: Representing the row number can be used to identify a specific row. However, you must fill this in manually.YesYes
ManufacturerYesYes
ModelYesYes
Model NameYesYes
Model NumberYesYes
Parent model manufacturerYesNote: Not applicable for single assets.YesNote: Not applicable for single assets.
Parent model nameYesNote: Not applicable for single assets.YesNote: Not applicable for single assets.
Parent model numberYesNote: Not applicable for single assets.YesNote: Not applicable for single assets.
Component numberYesNote: Not applicable for single assets.Yes
Asset TagConditionalNote: At least one unique identifier is required for non-consumables based on model category.ConditionalNote: At least one unique identifier is required for non-consumables based on model category.
Serial NumberConditionalNote: At least one unique identifier is required for non-consumables based on model category.ConditionalNote: At least one unique identifier is required for non-consumables based on model category.
MAC AddressConditionalNote: At least one unique identifier is required for non-consumables based on model category.ConditionalNote: At least one unique identifier is required for non-consumables based on model category.
Parent assetConditionalNote: Required for child assets when parent model information is provided.ConditionalNote: Required for child assets when parent model information is provided.
QuantityConditionalNote: Required for consumable assets (positive number).NoNote: Consumable assets cannot be updated.
StateYesNo
Sub stateYesNo
StockroomConditionalNote: Required for In stock and Build states.ConditionalNote: Required for In stock and Build states.
LocationConditionalNote: Required for In stock, In use, and Build states.ConditionalNote: Required for In stock, In use, and Build states.
Install statusYesYes
SubstatusConditionalNote: Required for In stock state only.ConditionalNote: Required for In stock state only.
Component IDConditionalNote: Required for child assets when applicable.No
OT entityConditionalNote: Required as true for hardware models when the OT Asset Management application is activated.ConditionalNote: Required as true for hardware models when the OT Asset Management application is activated.

Mandatory fields for model and asset template

Field/columnMandatory for creating models and assetsMandatory for updating models and assets
IndexNote: Representing the row number can be used to identify a specific row. However, you must fill this in manually.YesYes
ManufacturerYesYes
Model NameYesYes
Model NumberYesYes
Model categoryYesYes
Model typeYesYes
Parent model manufacturerYesNote: Not applicable for single models and single assets.Yes
Parent model nameYesNote: Not applicable for single models and single assets.Yes
Parent model numberYesNote: Not applicable for single models and single assets.Yes
Component numberYesNote: Not applicable for single models and single assets.No
Component quantityYesNote: Not applicable for single models and single assets.No
RequiredYesNote: Not applicable for single models and single assets.No
Hot swappableYesNote: Not applicable for single models and single assets.No
RepairableYesNote: Not applicable for single models and single assets.No
Asset TagConditionalNote: At least one unique identifier is required for non-consumables based on model category.ConditionalNote: At least one unique identifier is required for non-consumables based on model category.
Serial NumberConditionalNote: At least one unique identifier is required for non-consumables based on model category.ConditionalNote: At least one unique identifier is required for non-consumables based on model category.
MAC AddressConditionalNote: At least one unique identifier is required for non-consumables based on model category.ConditionalNote: At least one unique identifier is required for non-consumables based on model category.
Parent assetYesNote: Not applicable for single models and single assets.No
QuantityYesNo
StateYesNo
Sub stateYesNo
StockroomConditionalNote: Required for In stock and Build states.ConditionalNote: Required for In stock and Build states.
LocationConditionalNote: Required for In stock, In use, and Build states.ConditionalNote: Required for In stock, In use, and Build states.

Unit of measurement fields

Field/columnMandatory for creating modelsMandatory for updating models
Dimensions UnitConditionalNote: Required if length, width, height, or depth is provided.ConditionalNote: Required if length, width, height, or depth is provided.
Weight UnitConditionalNote: Required if the weight_decimal value is provided.ConditionalNote: Required if the weight_decimal value is provided.
Volume UnitConditionalNote: Required if the volume is provided.ConditionalNote: Required if the volume is provided.
Current UnitConditionalNote: Required if the value is provided for Current.ConditionalNote: Required if the value is provided for Current.
Power UnitConditionalNote: Required if the rated_power value is provided.ConditionalNote: Required if rated_power is provided.
Voltage UnitConditionalNote: Required if the voltage value is provided.ConditionalNote: Required if voltage is provided.
Cooling UnitConditionalNote: Required if the cooling value is provided (Enterprise models only).ConditionalNote: Required if the cooling value is provided (Enterprise models only).
Pressure UnitConditionalNote: Required if the pressure value is provided (Enterprise models only).ConditionalNote: Required if the pressure value is provided (Enterprise models only).
Temperature UnitConditionalNote: Required if the temperature value is provided (Enterprise models only).ConditionalNote: Required if the temperature value is provided (Enterprise models only).

Reference fields validation

The values entered in the following columns must exist in the database:

  • Manufacturer
  • Model failure impact
  • Model failure likelihood
  • Owner
  • Stockroom
  • Location
  • Managed by
  • Owned by
  • Reserved for
  • Supported by
  • Vendor
  • Asset failure impact
  • Asset failure likelihood

Parent Topic:Enterprise Asset Management reference

Related topics

Domain separation and Enterprise Asset Management

Components installed with Enterprise Asset Management

OT Asset Workspace roles

Asset fields for enterprise assets

Asset audit fields for enterprise assets

Audit results

Enterprise model categories and corresponding classes

Normalization status for enterprise models

Model fields for Enterprise Asset Management

Contract fields for Enterprise Asset Management

Maintenance plan fields for Enterprise Asset Management

Maintenance schedule fields for Enterprise Asset Management

Work plan fields for Enterprise Asset Management

Work plan schedule fields for Enterprise Asset Management

Expense line fields for Enterprise Asset Management

Fields inherited from a parent asset group to a sub group

Enterprise asset disposal order stages

Terminology for linear assets

Scheduled jobs and tables installed with normalization of firmware models

Asset put away task fields