Why are all six clients anonymised?

Because they asked us to be, and because the detail that makes these accounts useful is the detail a client does not want against their name: safety cases, audit exposure, data quality, a supplier that stopped performing. An accurate anonymised account is worth more to a buyer than a named one with the substance removed. Where a client later agrees to be named, we will name them.

How do I verify any of this before I buy?

Ask for a reference conversation. We arrange them under an NDA once a discussion is serious, with the client and without us on the call if that is what you prefer. That is the point at which anonymised delivery evidence becomes checkable, and it is a fair condition of shortlisting.

Why does every case study name a judgement you would change?

A write-up that only records success says little about how a supplier handles an awkward sequencing call. All six name one. On the embedded gas-network engagement it opens the page; elsewhere it sits near the end.

Are the durations and figures on these pages comparable to my estate?

No. Duration on an upgrade is set by live customisation and interface count, whether the database has to change, and how many production windows the calendar offers. On a data programme it is how much of the estate feeds a regulatory obligation. We size from your estate.

What if my situation sits outside these six?

These six are what we can describe publicly, not the full picture of what we run. If your problem is licensing, integration architecture, mobile adoption or a health check on an estate you have inherited, start from services or tell us the problem directly.

Case studies

Six engagements, and what made each one hard.

Each write-up names the constraint that shaped the decisions, the sequence of work, the outcome, and one sequencing judgement we would not repeat. Start from the problem you recognise rather than from the sector label.

Anonymisation

All six clients are anonymised at their request. Sites, locations, assets, headcounts, contract values and dates that would identify them are left out.

In regulated sectors the useful detail is often what a client cannot publish. A reference conversation under NDA, with the client and without us on the call if you prefer, is available once a discussion is serious.

Route by problem

Which of these situations is yours?

Sector matters less than shape. An airport consolidating two asset systems and a ferry operator upgrading against a fixed date have almost nothing in common operationally, and almost everything in common as a buying problem. Each row names the wrong move from that position, then links to the engagement told for that problem.

Fixed support date, almost no downtime

UK ferry operator, seven months →

You are on it if

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

The wrong move here

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 →

You are on it if

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

The wrong move here

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 →

You are on it if

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

The wrong move here

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 →

You are on it if

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

The wrong move here

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, embedded →

You are on it if

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

The wrong move here

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 →

You are on it if

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

The wrong move here

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

The six engagements

Covers, sectors and durations

Each engagement is anonymised. Open a cover for sector, duration and the detail page.

How to use these

If you are shortlisting suppliers, read three things first

Outcomes lists are easy to write. What tells you how a partner behaves is what they admit, what they descoped, and whether the sequence sounds like something that happened.

Check the constraint is real

A regulator, a support date, a safety case, a contract end. If a case study cannot name what made the work hard, the plan behind it was probably never tested against anything.

Look for what was left out

Every engagement here says what was left out and why. Scope discipline under a fixed date is the skill being bought, and it is visible in what a supplier declined to do.

Ask for the reference call

Anonymised evidence is only worth what the supplier will stand behind privately. Make a reference conversation a condition of shortlisting, with us or with anyone else.

Questions these case studies usually raise

Why are all six clients anonymised?: Because they asked us to be, and because the detail that makes these accounts useful is the detail a client does not want against their name: safety cases, audit exposure, data quality, a supplier that stopped performing. An accurate anonymised account is worth more to a buyer than a named one with the substance removed. Where a client later agrees to be named, we will name them.
How do I verify any of this before I buy?: Ask for a reference conversation. We arrange them under an NDA once a discussion is serious, with the client and without us on the call if that is what you prefer. That is the point at which anonymised delivery evidence becomes checkable, and it is a fair condition of shortlisting.
Why does every case study name a judgement you would change?: A write-up that only records success says little about how a supplier handles an awkward sequencing call. All six name one. On the embedded gas-network engagement it opens the page; elsewhere it sits near the end.
Are the durations and figures on these pages comparable to my estate?: No. Duration on an upgrade is set by live customisation and interface count, whether the database has to change, and how many production windows the calendar offers. On a data programme it is how much of the estate feeds a regulatory obligation. We size from your estate.
What if my situation sits outside these six?: These six are what we can describe publicly, not the full picture of what we run. If your problem is licensing, integration architecture, mobile adoption or a health check on an estate you have inherited, start from services or tell us the problem directly.

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