Product · Foundations
One load record, taken apart field by field.
A depot closed and 1,240 asset rows were reparented inside one maintenance window. This page reads the record that load left behind: what changed on a single asset, the 44 rows validation held back, and who accepted the commit. MaxIron Data Loader is the workspace that produced it.
The artefact
One asset out of 1,240, before and after
Every changed field names what set the new value, so an audit question needs no reconstruction.
Asset PU-04412, centrifugal pump
4 of 6 fields changed
| Field | Before | After | Set by |
|---|---|---|---|
| ASSETNUM | PU-04412 | PU-04412 | Unchanged. Asset identity is never a load target. |
| LOCATION | DEP-NORTH-04 | DEP-EAST-11 | Data lead, on the Locations change parent template |
| PARENT | DEP-NORTH | DEP-EAST | Same row of the same submitted batch |
| PMROUTE | RTE-N-014 | RTE-E-009 | Reparenting carries the maintenance route with the asset |
| STATUS | OPERATING | OPERATING | Unchanged. The template carries no status column. |
| CHANGEBY | MXINTADM | Approver on batch 4471 | Written at commit, with the environment and the template |
Illustrative record, shaped like loads we run.
How that record was produced
The load behind one changed field
The load
- Template
- Locations, change parent. One of over two hundred shipped for standard Maximo objects.
- Target
- One named environment, chosen at connection.
- Starting state
- Exported from that environment on the template structure, so editing began from what Maximo held.
- Preparation
- 1,240 rows edited off the live environment. The highlighter flagged 11 still on the old depot code.
The controls
- Validation basis
- Schema, types, lengths, required fields and the business objects configured in your estate.
- Who may load what
- Template-level and database-level restrictions, per user.
- Commit
- Paced batches inside the agreed window, validated during processing as well as before it.
- Written afterwards
- Template, environment, row count, approver, time. A formal gate is held by MaxIron Change Control.
Runs on Windows, macOS and Linux against one or many environments. In live use on MaxIron-led migrations and day-to-day data operations across utilities, transport, manufacturing, building materials and maritime estates.
The rows that did not go in
Forty four held back, each with its reason
A held row does not half apply. The other 1,196 committed unaffected.
| Ref | Reason held | Rows | What happened next |
|---|---|---|---|
| R1 | Parent location absent from the target environment | 31 | Depot codes in an old format, including the 11 already flagged. Corrected against the location list. |
| R2 | Field length exceeded | 9 | Descriptions longer than the field allows. Shortened, then re-validated. |
| R3 | Duplicate row inside the batch | 4 | Caught where duplicate checking is configured for the object. Removed before resubmission. |
Row counts are illustrative. Four percent of this batch failed in an afternoon, rather than weeks later when preventive maintenance raises work against a closed location.
Chain of custody
Three gates between a workbook and a committed batch
The order holds for twelve rows and for twelve thousand.
-
Gate 1 Validation
Signed by Data Loader, before and during processing
Passes
1,196 rows matching schema, types, lengths, required fields and your configured business objects.
Held back
44 rows, each with its reason and its correction history.
-
Gate 2 Preview against the target
Signed by The data lead preparing the load
Passes
The change read back against the environment it is about to alter.
Held back
A batch aimed at an environment nobody named.
-
Gate 3 Acceptance
Signed by Whoever your governance holds accountable
Passes
One approval, for this template, environment and window.
Held back
A production commit with no name against it.
Coverage
What the template library reaches
Over two hundred templates ship for standard Maximo objects, so a load starts from a known structure.
Assets, locations and hierarchy
Maintenance and planning
People and procurement
Platforms and IBM add-ons
Your own object structures
Scope and boundaries
Where Data Loader hands back to a person
Three questions anyone accountable for data quality asks in the first ten minutes.
It does not decide what your data should say
Validation enforces the structure and the business rules already configured in your estate. Whether a pump belongs to the north depot or the east one stays with the data owner.
Bad source data arrives cleanly
Cleaning the source, and agreeing hierarchy, naming and classification before a thousand records move, is separate work.
A bulk change is still a bulk change
The right permissions with the wrong scope is the expensive mistake here. Restrictions, preview and a named approver matter more than throughput.
MaxIron Data Loader, frequently asked questions
- What does MaxIron Data Loader do?
- Analysts, data leads and business owners query, edit, validate and submit IBM Maximo data in bulk from one tabular workspace, against one or many environments.
- What happens to the rows that fail validation?
- They are held with the reason against each row, and the rest of the batch commits unaffected. Correct, re-validate, resubmit.
- Who approves a bulk change before it lands in production?
- Whoever your governance names. Data Loader restricts who may load which template where, previews the change against the target, and records environment, template, submitter and time.
- Does it work with classic Maximo and MAS?
- Yes, against IBM Maximo 7.5.x and 7.6.x and IBM Maximo Application Suite 8.x and 9.x, including estates on MaxIron managed hosting.
MaxIron products
MaxIron products that work alongside this
Bring the load you have been putting off.
A reparenting, a reclassification, three hundred job plans needing a new task. We run it through Data Loader against a test environment and show what validation holds back, and the record it leaves behind.
Bring this to the session
- The workbook you would otherwise use, macro and all
- The Maximo object and the target environment
- Roughly how many rows, and how often the change recurs
- Who may accept a production data change