Mining Blog/Hexagon EAM Equipment Import: Field Mapping and Common Errors
Hexagon EAM8 min read21 February 2026

Hexagon EAM Equipment Import: Field Mapping and Common Errors

A practical guide to bulk importing mine-site equipment records into Hexagon EAM 11.x and 12.x — covering the EQUIPMENT/CLASS/ORGANIZATION schema, status codes, and pre-flight validation.

Hexagon EAM's Data Import utility is powerful but requires precise field mapping. One mismatched ORGANIZATION code and the entire batch fails. This guide covers the complete import process for mine-site equipment registers — from field mapping to status codes to the exact CSV format Hexagon expects.

S
The Struktive Team
Struktive

Key Takeaways

  • Hexagon EAM uses EQUIPMENT (max 25 chars) as the primary asset identifier — it must be unique within an ORGANIZATION.
  • CLASS maps to Hexagon's Equipment Class hierarchy — the class must pre-exist before import.
  • STATUS codes are single characters: I (Installed), O (Out of Service), D (Disposed), S (Stored).
  • ORGANIZATION must exactly match an existing Organisation record in Hexagon — case-sensitive.
  • Always run a 10-row test import before the full dataset to surface ORGANIZATION and CLASS mismatches cheaply.

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.

Try Struktive on your own data

Upload your equipment register and get back a normalised, EAM-ready export in under 90 seconds. No account required.

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.

Frequently Asked Questions

Hexagon EAMequipment importData Importmine siteEAMequipment class

Put this into practice

Upload your equipment register and get back a normalised, EAM-ready export in under 90 seconds. No login required.

We use a single session cookie to keep you signed in. No advertising or tracking cookies. See our Privacy Policy for details.