Can I speak to one of your clients before we sign anything?

Yes, during proposal. We match the reference to your sector, the size of your estate and the service in scope, ask that client for permission, and abide by the answer. The call runs on their terms. On the embedded engagement in the gas distribution network, reference conversations are arranged under an NDA.

Do you have a client in my sector?

The six above are the sectors with published work: airports, maritime, oil and gas, gas distribution, building materials and industrial services. Where yours is absent we say so, and offer the engagement whose manoeuvre matches instead. Sector delivery sets out the operating constraints we work under in each.

Can UK public bodies buy without running a tender?

Yes. MaxIron Ltd is on G-Cloud 14 as supplier 721548, so implementation, MAS upgrade, managed hosting and application support are callable off framework terms. A framework listing establishes the buying route and nothing about delivery quality, and we describe it in those terms on the recognition page.

Client evidence

Six engagements, with the scope and the duration named.

Client names are withheld under the contracts. Sector, situation, scope, outcome and duration are published in full, and a named reference is introduced during proposal.

Request a sector-matched reference Read the six write-ups

Delivery evidence

Named sector, named scope, named duration, checkable outcome

A UK airport operator

Transport and airports

Situation

Terminal and airside assets held on separate records, inside a safety case that stayed in force while the work happened.

What changed

IBM MAS 9 on Red Hat OpenShift across terminal and airside in 9 months, with mobile execution and building management integrated. Permits are never issued or approved inside Maximo, and that boundary held.
Read the case study →
A UK ferry operator

Maritime

Situation

IBM Maximo 7.6 on ageing infrastructure, a year-round timetable, and one usable cutover window before a fixed support date.

What changed

MAS 9.0.1 in 7 months, with the database converted from SQL Server to DB2 inside the same programme, so one production outage was spent rather than two.
Read the case study →
A global oil and gas major, UK Continental Shelf

Oil and gas

Situation

Failure coding that has to survive a regulator, on a taxonomy shared with a global estate.

What changed

A standards model inside Maximo aligned to ISO 14224, API RP 14C and ISO 15926 in 12 months, with legacy classification crosswalked rather than overwritten, so work history stays interpretable.
Read the case study →
A UK gas distribution network

Utilities and gas distribution

Situation

Regulator-grade reporting on a fixed cycle, and a platform team already at capacity.

What changed

A Maximo data lead and a developer embedded in the operator team on a multi-year engagement, inside their own change control, producing a written data standard and remediation delivered as small reversible changes.
Read the case study →
A UK and Ireland building materials group

Building materials

Situation

SAP PM across business units that named assets differently, and a legacy platform to leave.

What changed

One operating model on IBM Maximo across 13 months, the UK migration inside 8, DB2 conversion taken during the build, and a second territory moved to cloud in under 3 months.
Read the case study →
A UK industrial joint venture

Industrial services

Situation

A live production estate mid-contract, an inherited configuration nobody had documented, and a service that could not stop.

What changed

Transition from the outgoing supplier completed in 2 months, stabilised in order of operational consequence, with governance stood up during the transition rather than after it.
Read the case study →

Durations belong to the estate they came from. What sets yours is the live customisation and interface count, whether the database platform has to change, and how many production windows your operating calendar offers.

Engagement shape

What the six had in common on the operator side

The durations above bound the set. The requirement below appears in all six write-ups.

Shortest: 2 months
Longest: 13 months
Written up in full: 6 of 6

Present in every one of the six

A named data owner per business unit, deciding what is still true about the asset register.
Planners, supervisors and stores controllers in the mapping decisions, not only in the training that followed.
Someone inside the operator holding priorities and accepting the platform at each stage.
The regulatory position. We produce the evidence; your accountable people sign it.

Terms as we use them

Four kinds of client evidence, and what each one settles

These four arrive in almost every shortlist request, and they answer different questions.

Anonymised engagement write-up: One estate at procedure level: the constraints, the decision taken inside each step, the duration, and the sequencing judgement we would change. Six are published.; Often read as a programme plan for a different estate.
Sector match: An operator under comparable constraints: airside permits and closure slots, sailing schedules and dry dock, or a regulatory reporting cycle that cannot be missed.; Often read as evidence that the manoeuvre itself has been run.
Manoeuvre match: The same piece of work, whichever sector it came from: an upgrade against a fixed support date, a platform migration, a supplier transition on a live estate, a standards programme.; Often read as a claim about your own site rules.
Reference call: A named client, matched to your sector and estate size, on how MaxIron conducted itself when something went wrong. Arranged during proposal, with their permission.; Often read as technical due diligence, which the customisation inventory carries.

Why no client is named above

Client names are withheld because the contracts require it, and because several of these estates sit in critical national infrastructure, where an operator named alongside its platform version, integrations and reporting cycle is a disclosure we will not make.

Withholding the name lets a write-up carry decisions, constraints and sequencing judgements. Your engagement would be published on the same terms: sector, constraints, duration, outcome, no name.

Reference requests

How a client name is released

Three gates, and the client holds the last two.

Gate 1 Match proposed

Signed by MaxIron delivery lead

Passes

The closest engagement named, with the point where the match breaks down stated in the same email.

Held back

A write-up stretched to cover a sector or a manoeuvre we have no published work in.
Gate 2 Client permission

Signed by The client

Passes

An introduction the client has agreed to, having been told who is asking and what they want settled.

Held back

Their name in a deck, a proposal or a call before that agreement exists.
Gate 3 The call itself

Signed by The client

Passes

Their format, their availability, their boundaries, and MaxIron off the call unless both sides want us on it.

Held back

Questions about their commercial terms with us.

Scope of the evidence

Three boundaries on the evidence above

Published figures are limited to what a register holds

A client count, retention figure or satisfaction score would be unverifiable from where you sit, and we run no survey that would survive an audit. What we publish carries a reference: certificate 27274 with ISOQAR, G-Cloud 14 supplier 721548, IBM Partner Plus company 8294, each listed on recognition and credentials with what it does not prove.

An absent sector means nothing is published

Where yours is not in the six above, we have no written engagement to show you. We say so on the call, then point at the engagement whose manoeuvre matches instead.

A reference call establishes conduct

It tells you how we behaved on somebody else’s estate. Whether your own customisations survive an upgrade is settled by the customisation inventory and a trial upgrade in a non-production environment.

Clients and references, questions we are asked first

Can I speak to one of your clients before we sign anything?: Yes, during proposal. We match the reference to your sector, the size of your estate and the service in scope, ask that client for permission, and abide by the answer. The call runs on their terms. On the embedded engagement in the gas distribution network, reference conversations are arranged under an NDA.
Do you have a client in my sector?: The six above are the sectors with published work: airports, maritime, oil and gas, gas distribution, building materials and industrial services. Where yours is absent we say so, and offer the engagement whose manoeuvre matches instead. Sector delivery sets out the operating constraints we work under in each.
Can UK public bodies buy without running a tender?: Yes. MaxIron Ltd is on G-Cloud 14 as supplier 721548, so implementation, MAS upgrade, managed hosting and application support are callable off framework terms. A framework listing establishes the buying route and nothing about delivery quality, and we describe it in those terms on the recognition page.

Name your constraints and we will name the closest engagement.

Thirty minutes with a senior engineer. We will say which of the six is the nearest match, where the match breaks down, and whether a reference call in your sector can be arranged.

Useful to have on the call

Your sector, the number of sites and roughly how many Maximo users
The manoeuvre ahead: upgrade, migration, supplier change or data programme
The regulator, framework or standard your reporting has to satisfy
The contract or support arrangement that is ending, and when