Case studies

IBM Maximo delivery across six client estates

Each client story records the situation, MaxIron’s responsibility, the delivery mechanism and the outcome. Download a brief for your evaluation team.

Anonymisation

Six anonymised engagements across transport, utilities, oil and gas, building materials and industrial services.

Client-identifying details are withheld. Reference conversations are arranged during evaluation, subject to client permission and an NDA where required.

Route by problem

Choose the constraint closest to your estate

Choose the constraint: a support date, audit, supplier transition, regulatory return, system consolidation or safety-critical report.

Fixed support date, almost no downtime

UK ferry operator, seven months →

Operating context

You are on Maximo 7.x, your cutover windows are short, and the database platform may have to change.

Planning consideration

Starting from a feature list for MAS 9 before the inventory definitions and the production calendar are settled.

Two asset systems on a regulated estate

UK airport operator, boundaries →

Operating context

You have two asset systems, work needs a permit, and an audit cycle is already in the diary.

Planning consideration

Adding a third tool to reconcile the two, or rebuilding the permit system inside Maximo.

Business units that cannot be compared

UK building materials group, three routes →

Operating context

You are consolidating several sites, moving off SAP PM, or your units disagree on definitions.

Planning consideration

Migrating every unit onto one platform exactly as it works today, or buying a reporting layer to paper over the disagreement.

Support arrangement that has stopped working

UK industrial joint venture, failure modes →

Operating context

You are changing supplier, you have no visibility of your own platform, and the backlog is growing.

Planning consideration

Treating the outgoing handover pack as the source of truth, or changing the platform version during the transition.

Asset data nearly good enough for the regulator

UK gas distribution network, data and development →

Operating context

Your data feeds a regulatory return, you need capability rather than hours, and you have no change window.

Planning consideration

Buying bandwidth into a parallel supplier workstream, or re-classifying the whole estate in one irreversible change.

Safety-critical reporting assembled by hand

UK oil and gas operator, one record →

Operating context

You need ISO 14224 failure data, you report on safety-critical elements, and mergers left you several schemes.

Planning consideration

Overwriting legacy schemes, or standing up a separate reliability database that forks the truth on day one.

The six engagements

Scope and result for each engagement

Choose the programme closest to your delivery requirement. Duration reflects each estate’s scope and operating constraints.

For a reference request, state the proposed services, sector, platform and operating constraints. MaxIron identifies a comparable engagement, confirms permission with the client and agrees the subjects and confidentiality requirements for the conversation.

Published durations run from a two-month supplier transition to a multi-year utility data delivery. Completed programmes include a seven-month ferry upgrade to MAS 9.0.1, a nine-month airport go-live and a 12-month ISO 14224 data programme. Each record names the production constraint, accepted scope, accountable client role and the operating responsibility MaxIron carried after delivery.

Questions these case studies usually raise

Why are the client names withheld?
The published engagements are anonymised at the clients’ request. Client-identifying sites, records and commercial terms are withheld while scope, decisions and outcomes remain available for evaluation.
Can we request a reference conversation?
Reference requests are matched to the proposed services and delivery constraints. Each introduction requires the client’s permission and an NDA where applicable.
How should we use the published durations?
Use the durations as context for each engagement. A programme estimate depends on the live customisation and integration inventory, data readiness, approval gates and available production windows.

Discuss an engagement that matches your constraint

A working session on your estate rather than a capability presentation. We will map which engagement your problem resembles, where our sequence would differ, and whether you need less than a full programme.

Bring this and the first session can be specific

  • Your current Maximo or MAS version, database platform and hosting arrangement.
  • The constraint you are working to: a support date, an audit, a contract end, a merger.
  • Whatever documentation you hold on customisations and interfaces, including the out-of-date parts.
  • The reports and returns your business actually depends on.
  • Who inside your organisation can decide what is still true about your asset data.
Discuss your engagement See how we deliver