MaxIron Data Loader

Move bulk Maximo data with control over every row

Name: MaxIron Data Loader
Brand: MaxIron

Query, create, update, sync and delete Maximo records from one shared browser workspace. Prepare the rows, check them against Maximo and keep the result of every load.

Review one load against Data Loader

Workspace

Test DU

Prepare asset hierarchy SYNC

MAS Test · Asset hierarchy sync

Connection

MAS Test

Template

Asset hierarchy sync (MXAPIASSET)

Action

SYNC

Batch size

Source rows

Import xlsx or paste rows. Validate checks the template then Maximo setvalue.

Import xlsxValidate rows (template + Maximo)

238 rows 235 passed 3 findings Showing four representative rows

Row	ASSETNUM	LOCATION	PARENT	Status
1	PUMP-1042	DEP-EAST-11	PUMP-GROUP-04	ok
2	PUMP-1043	DEP-EAST-11	PUMP-GROUP-04	ok
3	PUMP-1044	DEP-EAST-XX	PUMP-GROUP-04	error
4	PUMP-1045	DEP-EAST-11	Empty	error

PUMP-1042Passed

Location DEP-EAST-11 · Parent PUMP-GROUP-04

PUMP-1043Passed

Location DEP-EAST-11 · Parent PUMP-GROUP-04

PUMP-1044Domain finding

Location DEP-EAST-XX · Parent PUMP-GROUP-04

PUMP-1045Required finding

Location DEP-EAST-11 · Parent Empty

3 rows failed validation. Fix errors before running.

Run load Schedule run

Illustrative MaxIron Data Loader Workspace with 238 staged rows and three advisory validation findings.

Contents 8 sections

01 Which product Bulk operational work, formal master-data approval, or software promotion.
02 Capabilities Prepare, check and run bulk Maximo work.
03 Loads and evidence See what Maximo accepted and what still needs attention.
04 Acceptance case One representative asset data load.
05 Fit and deployment Quoted after the estate, actions and deployment shape are confirmed.
06 Boundaries No automatic rollback. Validation remains advisory.
07 Questions Operations, dry run and scheduling.
08 Next step Bring one workbook and a test connection.

Contents

Which product
Capabilities
Loads and evidence
Acceptance case
Fit and deployment
Boundaries
Questions
Next step

Choose by need

Choose the control that matches the work

Data Loader handles operational bulk work. Formal approval belongs in the product designed for it.

NeedProductWhy

Query or change Maximo records in bulk

Data Loader

Prepare, validate, run and review row-level outcomes.

Approve formal master-data changes

Data Governance

Use maker-checker, a frozen revision and a stale record check.

Approve software or configuration promotion

Change Control

Record the decision before a tested change moves to production.

Product capabilities

Prepare, check and run bulk Maximo work.

Prepare work from live Maximo: Query the object structures your Maximo API makes available, preview current records and build reusable templates for parent, child and grandchild data. Work in a table, nested JSON or an imported workbook.
Check rows before they save: Run an advisory dry run through Maximo set-value mode, which checks field values without saving the records. Findings appear against the affected rows. Users can correct them and check again. After explicit confirmation, they can still run rows that failed validation.
Run bulk changes with evidence: QUERY, CREATE, UPDATE and SYNC can run now or on a one-off or recurring schedule. DELETE is a deliberate manual action. Each asynchronous job keeps row outcomes, returned values, errors and Call details.

Loads and evidence

See what Maximo accepted and what needs attention.

Large loads run in chosen batch sizes and continue asynchronously after the browser closes. Review values sent and returned, retry failed rows and open Call details for request, response and error evidence.

Loads

Test DU

Load evidence

MAS Test · asset hierarchy sync

Recent loads

Selected connection · MAS Test

Export results

When	Template	Rows	Status
09:42	Asset hierarchy sync	235 succeeded · 3 failed	Completed with errors
09:18	PM frequency update	50 succeeded · 0 failed	Succeeded
08:55	Active locations	500 returned	Succeeded

Asset hierarchy sync09:42

235 succeeded · 3 failed

Completed with errors

PM frequency update09:18

50 succeeded · 0 failed

Succeeded

Active locations08:55

500 returned

Succeeded

Selected failed row

PUMP-1044 · LOCATION

No record saved

LOCATION = DEP-EAST-XX

The location value is not valid for site NORTH.

Retry failed rows Call details

Maximo call evidence

Request: POST /maximo/api/os/MXAPIASSET · PUMP-1044
Response: HTTP 400 · domain validation
Initiated by: Data Operations role
Outcome: No record saved

Illustrative MaxIron Data Loader evidence for a 238-row SYNC completed with three execution errors.

Representative acceptance case

One representative asset data load

The demonstration uses a customer-supplied test workbook and object structure to show the route from staging to Maximo evidence.

This is a qualification demonstration against representative work, not a named customer result. Anonymised customer engagements and reference conversations under NDA sit in the case studies.

What we walk through

Select the live object structure and build a parent, child and grandchild template.
Stage the workbook, run advisory validation and review the affected rows.
Run the SYNC job in test and retry only the rows that fail.

Pass condition

Pass when accepted records reach Maximo and the load record shows what was sent, returned, rejected and retried.

Evidence retained: Load history, row outcomes, assigned keys, errors and Call details.

Boundary that remains: Data Loader does not reverse changes already made in Maximo, and it does not decide whether a business value is correct.

Buying information

How Data Loader is sold and introduced

We confirm the Maximo estate, required actions and deployment shape before providing a quote. We demonstrate the product against a representative load from your estate, to confirm fit, boundaries and implementation requirements.

Review one load against Data Loader

Price: Quote on request.
Pricing basis: Agreed deployment shape, Maximo connections and required data operations.
Compatibility: Maximo object structures exposed through the API, including customer extensions.
Identity: Single sign-on through Azure Entra ID, MAS OIDC or another OIDC provider.
Deployment: Standalone customer service or OpenShift, including alongside a Maximo Application Suite estate.

Product boundaries

Know what remains outside the load

No automatic rollback

Cancellation is checked between batches. A current batch may complete, and changes already made in Maximo are not automatically reversed.

Validation remains advisory

A user can explicitly run rows that failed validation. Set-value validation does not save a record, but evaluating an AutoKey field may advance a Maximo autonumber sequence.

Business ownership stays with people

Data Loader checks structure and Maximo rules. It does not decide whether a hierarchy, classification or business value is correct.

Questions buyers ask

What does MaxIron Data Loader do?

It provides a multi-user browser workspace for querying, creating, updating, syncing and deleting IBM Maximo data in bulk, with reusable templates, advisory validation, queued jobs and row-level evidence.

Does dry-run validation write to Maximo?

No record change is saved. Maximo set-value mode returns findings against the affected rows. Users can correct those rows and check again. After explicit confirmation, they can still run rows that failed validation. Checking an AutoKey field may advance a Maximo autonumber sequence.

Which actions can be scheduled?

QUERY, CREATE, UPDATE and SYNC can run immediately, once at a chosen time, or on a recurring schedule. DELETE is not scheduled and remains a manual Workspace action.

Put one real load through Data Loader

Use a test connection to see how your rows move from template and validation to load evidence.

Bring three things

One real workbook or JSON row set
The Maximo object structure it belongs to
A test connection

Review one load against Data Loader Discuss a migration