IBM Maximo Asset Import: A Practical Guide for Mine Site Engineers

Before You Start

Maximo's bulk asset import is one of the most powerful data migration tools available for mine-site EAM implementations — and one of the most unforgiving. A single mismatched SITEID will fail the entire batch. A CLASSSTRUCTUREID that does not exist in your Maximo instance will reject every row that references it.

This guide covers the complete import process for mine-site equipment registers: field mapping, pre-flight validation, common errors, and the exact CSV format Maximo expects. SAP EAM holds 48.3% of the ANZ market, but IBM Maximo remains the dominant platform in mining — and its import process is unforgiving enough that data quality problems surface immediately at go-live rather than quietly accumulating afterward.

Required Fields

Every row in your Maximo asset import CSV must include these fields:

ASSETNUM — The asset identifier, unique within a SITEID. Maximo uses a composite key of ASSETNUM + SITEID, so two different sites can have the same asset number. Maximum 25 characters.

SITEID — The Maximo Site ID. Must exactly match an existing Site record in the Maximo Sites application. Case-sensitive.

ORGID — The Maximo Organisation ID. Must exactly match an existing Organisation record.

STATUS — Must be one of: ACTIVE, INACTIVE, OPERATING, DECOMMISSIONED, DISPOSED. Any other value will fail the row.

Recommended Fields for Mine Sites

CLASSSTRUCTUREID — Maps to Maximo's Classification hierarchy. This is how Maximo knows whether an asset is a Haul Truck, a Crusher, or a Conveyor Belt. The classification structure must pre-exist in Maximo before import. If your Maximo instance does not have a mining classification hierarchy, you will need to create one first.

LOCATION — Maps to a Maximo Location record. Locations represent physical places in the mine — pits, plants, workshops. They must be created in the Maximo Locations application before assets can be assigned to them.

SERIALNUM — The equipment serial number. Maximo uses this for warranty tracking and duplicate detection.

MANUFACTURER — The OEM name. Must match a Manufacturer record in Maximo's Manufacturers application. "Cat" and "Caterpillar" are different strings — Maximo will not automatically resolve them.

MODELNUM — The model number. Used for equipment specifications and spare parts linkage.

The Import Process

1. Open the Asset application in Maximo.
2. Select More Actions → Import Assets.
3. Upload your CSV file.
4. Map columns to Maximo fields if the auto-mapping is incorrect.
5. Run a validation pass — Maximo will show you which rows have errors before committing.
6. Review errors, fix the source data, and re-upload.
7. Commit the import.

Always run a 10-row test import before the full dataset. This surfaces SITEID mismatches, CLASSSTRUCTUREID errors, and LOCATION issues cheaply — before you have committed 5,000 rows and need to roll back.

Common Errors and Fixes

BMXAA4211E: SITEID does not exist — Your SITEID value does not match any Site record in Maximo. Check the Sites application for the exact SITEID string, including case.

BMXAA4215E: CLASSSTRUCTUREID does not exist — The classification ID in your CSV does not exist in Maximo's Classification hierarchy. Either create the classification structure first, or remove the CLASSSTRUCTUREID column and classify assets manually after import.

BMXAA4219E: LOCATION does not exist — The LOCATION value in your CSV does not match any Location record. Create the location hierarchy in the Locations application first.

Duplicate ASSETNUM within SITEID — Maximo will reject rows where the ASSETNUM + SITEID combination already exists. Either update the existing record or use a different ASSETNUM.

Using Struktive for Maximo Imports

Struktive generates a Maximo-ready CSV with all required fields pre-populated, CLASSSTRUCTUREID mapped from mining equipment categories, and a pre-flight report showing exactly which rows will fail before you touch Maximo. Upload your messy equipment register, download the Maximo import file, and complete a clean import in a single session.