Hexagon EAM's Data Model
Hexagon EAM (formerly Infor EAM and DATASTREAM 7i) uses a slightly different data model from Maximo and SAP PM. Understanding the key differences before you start an import will save significant rework.
ORGANIZATION is the top-level entity in Hexagon — equivalent to Maximo's ORGID. All equipment, locations, and classes exist within an organisation. The ORGANIZATION value in your import file must exactly match an existing Organisation record in Hexagon, including case sensitivity.
CLASS is Hexagon's equipment classification system — equivalent to Maximo's CLASSSTRUCTUREID. Classes are hierarchical and must be created before equipment can be assigned to them. For mine sites, a typical class hierarchy looks like: MOBILE > HAUL-TRUCK > CAT-793F.
DEPARTMENT maps to Hexagon's Department entity — equivalent to a cost centre or maintenance area. It is optional but strongly recommended for mine-site records where cost centre allocation is required for maintenance budgeting.
Required Fields
EQUIPMENT — The equipment identifier, unique within an ORGANIZATION. Maximum 25 characters. Hexagon will automatically convert to uppercase.
CLASS — The equipment class code. Must exactly match an existing Class record in Hexagon.
ORGANIZATION — The Hexagon Organisation code. Must exactly match an existing Organisation record. Case-sensitive.
STATUS — Single-character status code: I (Installed), O (Out of Service), D (Disposed), S (Stored). No other values are accepted.
Recommended Fields for Mine Sites
MANUFACTURER — The OEM name. Should match a Manufacturer record in Hexagon if you want automatic spare parts linkage.
MODEL — The model code.
SERIALNUMBER — The equipment serial number.
DEPARTMENT — The department or cost centre code.
LOCATION — The physical location (mine area, plant, workshop).
COSTCODE — The cost code for maintenance cost allocation.
Common Errors and Fixes
ORGANIZATION not found — Your ORGANIZATION value does not match any Organisation record in Hexagon. Check the Organisation screen for the exact code, including case.
CLASS not found — The CLASS code in your CSV does not exist in Hexagon's Equipment Class hierarchy. Create the class first, or remove the CLASS column and classify equipment manually after import.
Invalid STATUS code — Your STATUS value is not one of I, O, D, S. Map your source status values to these four codes before import.
EQUIPMENT too long — The EQUIPMENT value exceeds 25 characters. Truncate or abbreviate your asset identifiers before import.
Using Struktive for Hexagon EAM Imports
Struktive generates a Hexagon EAM-ready CSV with all required fields pre-populated, CLASS codes mapped from mining equipment categories, and STATUS values mapped to Hexagon's single-character codes. The pre-flight report shows exactly which rows will fail before you touch Hexagon — upload your messy equipment register, download the Hexagon import file, and complete a clean import in a single session.