By role
Four accountabilities, four first conversations.
The rest of this site is organised by service, product and sector. These pages start from the pressure you carry and route into the parts of the site that match it.
The index
Four roles, and the pressure each page is written to
Pick the row that describes the conversation already in your calendar. Codes R1 to R4 are stable so a bid writer can cite one by reference.
| Ref | Role page | Written for | The pressure | First step it recommends |
|---|---|---|---|---|
| R1 | IBM Maximo for Maintenance Directors | Maintenance Director, Head of Maintenance, Maintenance & Reliability Manager, Engineering Director | Measured on unplanned work and schedule compliance, and asked to explain a repeat failure from a record closed with a free-text comment. | Book a 30-minute review of the failure record |
| R2 | IBM Maximo for CIOs | CIO, CTO, IT Director, Director of Enterprise Applications, Head of EAM Platform | Give the board a date and a number for the platform, then live with both, while patching and certificate work consumes the team hired to improve the estate. | Ask for an upgrade rehearsal scope |
| R3 | IBM Maximo for Heads of Asset Management | Head of Asset Management, Asset Management Director, Head of Reliability, Asset Strategy Lead | Own the policy and the evidence behind every decision taken in its name, while the system that should enforce the model belongs to somebody else. | Walk the criticality model against one asset |
| R4 | IBM Maximo for Procurement and Commercial Leads | Head of Procurement, Commercial Director, Sourcing Manager, IT Procurement Lead, Category Manager | Accountable for an award whose consequences arrive eighteen months later, usually to somebody else, usually as change requests nobody scoped. | Open the RFP question library |
A fifth page covers operators whose Maximo estate is smaller than the references on this site imply: IBM Maximo for smaller estates.
Adjacent routes
Where the four pages send readers next
- Smaller estates IBM Maximo for smaller estates
When the question is whether Maximo is proportionate at your size, before any role page.
- Company Why customers choose MaxIron
The reasons buyers give us, stated plainly enough to test in a reference call.
- Evidence MaxIron clients
Six anonymised engagements with scope and duration named.
- Start Book a 30-minute review
When the meeting in the calendar needs a structured read of the estate first.
Why four pages
The same estate failure is a reliability question, an evidence question, a run-cost question or a scope question, depending on whose chair you sit in.
All four readings are correct. They lead to different first steps, which is why the site keeps them on separate pages rather than collapsing them into one brochure.
Before you open a role page
Difficulty on a Maximo estate is usually budget cycle, operating model, how data is captured on a shift, and regulatory load.
Each role page routes into a handful of services, products, sectors and anonymised case studies that match its problem, with a line on why each is worth the time. Where two pages meet on the same problem, each links to the other.
What a role page can claim
Three limits on what these pages describe
Each one is worth knowing before you read further.
They describe patterns across estates
Everything here comes from the estates we run and the ones we are asked to assess. Where a page describes effort or shape, it is illustrative and labelled as such.
They cover four roles
Planners, supervisors, reliability engineers and finance business partners have no page of their own yet. For those roles, the closest of the four is usually the right starting point.
They overlap on purpose
Asset management and maintenance leadership read the same failure differently, and both are needed. Where two pages meet on the same problem, each links to the other.
Bring the meeting already in your calendar.
Tell us the conversation you would rather prepare for: a failure review, a board number, an assessor request or a scope argument. We will say what would have to be true for it to be answered from the system rather than assembled by hand.
Useful to have in front of you
- The meeting, the date, and who is in the room
- The question you expect to be asked that you cannot currently answer from the system
- Where the answer lives today, and how many people it takes to assemble it