Mandatory fields in the bulk import spreadsheets
- UpdatedJul 31, 2025
- 4 minutes to read
- Zurich
- Enterprise Asset Management
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/column | Mandatory for creating models | Mandatory for updating models |
|---|---|---|
| Index Note: Representing the row number can be used to identify a specific row. However, you need to fill this in manually.
|
Yes | Yes |
| Manufacturer | Yes | Yes |
| Model Name | Yes | Yes |
| Model Number | Yes | Yes |
| Model category | Yes | Yes |
| Model type | Yes | Yes |
| Parent model manufacturer | Yes Note: Not applicable for single models. |
No |
| Parent model name | Yes Note: Not applicable for single models. |
No |
| Parent model number | Yes Note: Not applicable for single models. |
No |
| Component number | Yes Note: Not applicable for single models. |
No |
| Component quantity | Yes Note: Not applicable for single models. |
No |
| Required | Yes Note: Not applicable for single models. |
No |
| Hot swappable | Yes Note: Not applicable for single models. |
No |
| Repairable | Yes Note: Not applicable for single models. |
No |
Mandatory fields for asset template
| Field/column | Mandatory for creating assets | Mandatory for updating assets |
|---|---|---|
| Index Note: Representing the row number can be used to identify a specific row. However, you need to fill this in manually.
|
Yes | Yes |
| Manufacturer | Yes | Yes |
| Model | Yes | Yes |
| Model Name | Yes | Yes |
| Model Number | Yes | Yes |
| Parent model manufacturer | Yes Note: Not applicable for single assets. |
Yes |
| Parent model name | Yes Note: Not applicable for single assets. |
Yes |
| Parent model number | Yes Note: Not applicable for single assets. |
Yes |
| Component number | Yes Note: Not applicable for single assets. |
Yes |
| Asset Tag | Conditional Note: At least one unique identifier is required for non-consumables based on model category. |
Conditional Note: At least one unique identifier is required for non-consumables based on model category. |
| Serial Number | Conditional Note: At least one unique identifier is required for non-consumables based on model category. |
Conditional Note: At least one unique identifier is required for non-consumables based on model category. |
| MAC Address | Conditional Note: At least one unique identifier is required for non-consumables based on model category. |
Conditional Note: At least one unique identifier is required for non-consumables based on model category. |
| Parent asset | Conditional Note: Required for child assets when parent model information is provided. |
Conditional Note: Required for child assets when parent model information is provided. |
| Quantity | Conditional Note: Required for consumable assets (positive number). |
No Note: Consumable assets cannot be updated. |
| State | Yes | No |
| Sub state | Yes | No |
| Stockroom | Conditional Note: Required for In stock and Build states. |
Conditional Note: Required for In stock and Build states. |
| Location | Conditional Note: Required for In stock, In use, and Build states. |
Conditional Note: Required for In stock, In use, and Build states. |
| Install status | Yes | Yes |
| Substatus | Conditional Note: Required for In stock state only. |
Conditional Note: Required for In stock state only. |
| Component ID | Conditional Note: Required for child assets when applicable. |
No |
| OT entity | Conditional Note: Required as true for hardware models when the OT Asset Management application is activated. |
Conditional Note: Required as true for hardware models when the OT Asset Management application is activated. |
Mandatory fields for model and asset template
| Field/column | Mandatory for creating models and assets | Mandatory for updating models and assets |
|---|---|---|
| Index Note: Representing the row number can be used to identify a specific row. However, you need to fill this in manually.
|
Yes | Yes |
| Manufacturer | Yes | Yes |
| Model Name | Yes | Yes |
| Model Number | Yes | Yes |
| Model category | Yes | Yes |
| Model type | Yes | Yes |
| Parent model manufacturer | Yes Note: Not applicable for single models and single assets. |
Yes |
| Parent model name | Yes Note: Not applicable for single models and single assets. |
Yes |
| Parent model number | Yes Note: Not applicable for single models and single assets. |
Yes |
| Component number | Yes Note: Not applicable for single models and single assets. |
No |
| Component quantity | Yes Note: Not applicable for single models and single assets. |
No |
| Required | Yes Note: Not applicable for single models and single assets. |
No |
| Hot swappable | Yes Note: Not applicable for single models and single assets. |
No |
| Repairable | Yes Note: Not applicable for single models and single assets. |
No |
| Asset Tag | Conditional Note: At least one unique identifier is required for non-consumables based on model category. |
Conditional Note: At least one unique identifier is required for non-consumables based on model category. |
| Serial Number | Conditional Note: At least one unique identifier is required for non-consumables based on model category. |
Conditional Note: At least one unique identifier is required for non-consumables based on model category. |
| MAC Address | Conditional Note: At least one unique identifier is required for non-consumables based on model category. |
Conditional Note: At least one unique identifier is required for non-consumables based on model category. |
| Parent asset | Yes Note: Not applicable for single models and single assets. |
No |
| Quantity | Yes | No |
| State | Yes | No |
| Sub state | Yes | No |
| Stockroom | Conditional Note: Required for In stock and Build states. |
Conditional Note: Required for In stock and Build states. |
| Location | Conditional Note: Required for In stock, In use, and Build states. |
Conditional Note: Required for In stock, In use, and Build states. |
Unit of measurement fields
| Field/column | Mandatory for creating models | Mandatory for updating models |
|---|---|---|
| Dimensions Unit | Conditional Note: Required if length, width, height, or depth is provided. |
Conditional Note: Required if length, width, height, or depth is provided. |
| Weight Unit | Conditional Note: Required if the weight_decimal value is provided. |
Conditional Note: Required if the weight_decimal value is provided. |
| Volume Unit | Conditional Note: Required if the volume is provided. |
Conditional Note: Required if the volume is provided. |
| Current Unit | Conditional Note: Required if the value is provided for Current. |
Conditional Note: Required if the value is provided for Current. |
| Power Unit | Conditional Note: Required if the rated_power value is provided. |
Conditional Note: Required if rated_power is provided. |
| Voltage Unit | Conditional Note: Required if the voltage value is provided. |
Conditional Note: Required if voltage is provided. |
| Cooling Unit | Conditional Note: Required if the cooling value is provided (Enterprise models only). |
Conditional Note: Required if the cooling value is provided (Enterprise models only). |
| Pressure Unit | Conditional Note: Required if the pressure value is provided (Enterprise models only). |
Conditional Note: Required if the pressure value is provided (Enterprise models only). |
| Temperature Unit | Conditional Note: Required if the temperature value is provided (Enterprise models only). |
Conditional Note: Required if the temperature value is provided (Enterprise models only). |
Reference fields validation
- PO Number
- Assigned To
- Department
- Company
- Cost Center
- Asset Depreciation
- Aisle Space Location
Related Content
- Domain separation and Enterprise Asset Management
Domain separation is supported in Enterprise Asset Management. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.
- Enterprise Asset Management roles
The following roles help you to configure and use the Enterprise Asset Management application to manage the life cycle of your assets, parts, and their hierarchical relationships.
- OT Asset Workspace roles
The following roles help you to manage the OT Asset Management application.
- Asset fields for enterprise assets
A detailed description of all asset fields in the Enterprise Asset Management application.
- Enterprise model categories and corresponding classes
Enterprise model categories and their corresponding Configuration Management Database (CMDB) configuration item (CI), asset, and model classes.
- Normalization status for enterprise models
Description of the normalization statuses for enterprise models.
- Model fields for Enterprise Asset Management
A detailed description of all model fields in the Enterprise Asset Management application.
- Contract fields for Enterprise Asset Management
A detailed description of all contract fields in the Enterprise Asset Management application.
- Maintenance plan fields for Enterprise Asset Management
A detailed description of all maintenance plan fields in the Enterprise Asset Management application.
- Maintenance schedule fields for Enterprise Asset Management
A detailed description of all maintenance schedule fields in the Enterprise Asset Management application.
- Work plan fields for Enterprise Asset Management
A detailed description of all work plan fields in the Enterprise Asset Management application.
- Work plan schedule fields for Enterprise Asset Management
A detailed description of all the work plan schedule fields in the Enterprise Asset Management application.
- Expense line fields for Enterprise Asset Management
A detailed description of all expense line fields in the Enterprise Asset Management application.
- Fields inherited from a parent asset group to a sub group
A list of all the fields that are inherited from the parent asset group to a subgroup.
- Enterprise asset disposal order stages
An enterprise asset disposal order goes through various stages in the disposal process before it’s completed. With each stage, the task that's associated with that stage changes too.
- Terminology for linear assets
Terms commonly used for linear assets in the Enterprise Asset Management application.
- Installed with Enterprise Asset Management for Healthcare
The user role components, plugins, and applications are installed with activation of the com.sn_eamhc plugin.
- Installed with OT Asset Management
The user role components, plugins, and applications are installed with activation of the com.sn_otam plugin.
- Components installed with Enterprise Asset Management for Data Center and Network Asset Management (DCNAM)
Several types of components are installed with activation of the com.sn_eam_dcnam plugin, including user roles, plugins, and applications.
- Components installed with Enterprise Asset Management for Providers
Several types of components are installed with activation of the com.sn_eam_provider plugin, including user roles, applications, and tables.
- Scheduled jobs and tables installed with normalization of firmware models
Scheduled jobs that run during the normalization of firmware models embedded into Operational Technology (OT) assets and tables that store firmware normalization details are installed with the OT Asset Management application.
- Asset put away task fields
Fields on the Asset put away task form help you create a put away task for the in stock assets.