Services
IBM Maximo services from implementation to live operation.
MaxIron implements, upgrades, hosts and supports IBM Maximo and MAS estates. Engagements range from a complete programme to a defined data, integration, mobile or configuration work package, with named responsibilities and acceptance evidence.
Where to start
Eight situations, and the engagement that fits each
Scope follows the estate, the operational decision and the responsibilities your team wants MaxIron to hold.
A first implementation of IBM Maximo
IBM Maximo implementation →Operating context
Work is planned on spreadsheets, and no two areas write it down the same way.
Planning consideration
Configuring before hierarchy, criticality and job plans exist. The first design review then argues about data instead of process.
The move off Maximo 7.6
Maximo to MAS upgrade →Operating context
You are on 7.6, and support position, security posture or access to the suite is now the pressure.
Planning consideration
Pricing the work off the version number. The customisation and integration inventory sets the cost, so we quote a fixed price against it.
MaxIron Cloud hosts it and operates it
MaxIron Cloud →Operating context
You want a monthly cost, environments in hours, and an on-call rota that is not one person, without standing up the clusters in your subscription.
Planning consideration
Buying MaxIron Cloud when the clusters must sit in your Azure, AWS or OCI subscription. That is the next row, not a support contract.
It has to run in your Azure, AWS or OCI
Implementation, including your cloud →Operating context
Security or architecture requires MAS in your cloud subscription. You still want MaxIron to design the architecture, build it, and operate it, including multizone OpenShift.
Planning consideration
Assuming that means you host it and we only take tickets. Architecture, clusters and operations are still MaxIron work.
The estate is live and needs an application partner
Maximo and MAS application support →Operating context
Maximo or MAS is in production. Tickets land on a thin internal team, and nobody owns severity targets, a service report or the after-hours rota.
Planning consideration
Treating support as ad-hoc time and materials. Without a named service manager and a change route, every ticket becomes a mini-programme.
A programme that is slipping
Health Check and Heal →Operating context
An implementation has stalled, an upgrade has slipped twice, or nobody can state what is in production.
Planning consideration
Replanning before the facts are in. Change control, environments and failing integrations come back under control first.
One capability, not a programme
Specialist augmentation →Operating context
Mobile, integrations, data migration, configuration or licensing is the gap. The rest holds.
Planning consideration
Buying a programme to close one gap. Each capability below is separately scoped and separately priced.
What comes after Manage
The wider MAS suite →Operating context
Manage is stable, and Monitor, Predict, Health or Visual Inspection are on the table.
Planning consideration
Sequencing by appetite rather than by data. A failure-probability model is worth what its condition history is worth.
Upgrade versus re-implementation
What an upgrade carries forward, and what a re-implementation rebuilds
Both are legitimate programmes, bought differently and carrying different risk. Deciding which one is funded is the most useful hour a steering group spends.
Upgrade
Carry the estate forward: the same configuration, data and processes, on a supported platform with the suite available.
Re-implementation
Rebuild the operating model, using the platform change as the moment to do it.
What the business is asked to do
Regression test what it already knows, and accept a new interface for some roles.
Re-learn how work is planned, assigned, recorded and closed, area by area.
Where the risk sits
Technical: customisations, integrations, the database, and cutover timings inside a fixed window.
Organisational: adoption, training, process ownership, and whether the data is ready to be trusted.
How long it takes
Months, set by the size of the customisation inventory and the number of integrations.
Quarters, set by how many operating areas have to change how they work.
The mistake we see most
Scope drift: an upgrade quietly becomes a rebuild because the wish list was never closed.
Under-funding the change: configuration lands, the process work does not, and old habits return within a year.
Before you commit
How an engagement gets scoped
Five steps from a first call to a scope you can defend in procurement. Each one produces an artefact you keep.
- 01
First call
Forty minutes on version, environments, integrations, volumes and the date that is already fixed. A senior engineer, no slides.
- 02
Evidence pass
Customisation inventory, integration list, environment state and data readiness, written for your board.
- 03
Named scope and price
What is in, what is out, and the assumptions that would move the number. For an upgrade, fixed against that inventory.
- 04
A deliberately small first phase
One area, one site or one asset class, so the operating model is tested while change is still cheap.
- 05
Review gate
Continue, adjust or stop, with the first phase in front of you. Written into the engagement at the start.
For an upgrade, start with the free upgrade quote. For an estate already in service, start with a 30-minute review.
Delivery responsibilities
We take the operating burden. You keep the operating decisions.
The proposal names platform, application and release responsibilities alongside your process, data and regulatory accountabilities.
Still yours
Accountabilities that stay with you
- Deciding what an asset is worth keeping, and at what criticality. We structure the decision and bring the evidence.
- Getting supervisors and planners to work differently: a management task before it is a training task.
- Writing down the job plans, hierarchy and classifications that currently exist only in experienced heads.
- Owning the regulatory position. We produce the evidence; your accountable people sign it.
Off your plate, from the first phase
Work MaxIron can hold under agreed scope
- Environment provisioning, patching and platform upgrades
- Reconstructing what is in production every time an audit asks
- Manual regression testing before every release
- The out-of-hours call landing on the one person who knows
Platform and release work moves to us inside the first phase. Process ownership, data stewardship and adoption stay with you for the life of the estate.
The services contract records the scope, acceptance criteria and shared responsibilities before mobilisation.
Specialist capabilities
Specialist capabilities, each separately scoped and priced
- Evaluate MAS Sandbox Environments
Dedicated MAS evaluation environments with demo data, licensed access and backups. Foundation from £350 or $460 per environment per month.
- Build Maximo configuration
Applications, security, workflow, escalations, KPIs and start centres before anyone writes Java.
-
Legacy Java moved to Automation Scripts and configuration, so the next upgrade costs less to test.
- Connect Maximo integrations
SAP, Oracle, ServiceNow, GIS, SCADA, finance and identity, designed around the decision each interface serves.
-
Migration, cleansing, validation and cutover, so the service starts on information the business will act on.
-
DB2, Oracle and MSSQL in any combination, with a tested cutover and a tested rollback.
- Adopt Maximo Mobile rollouts
Offline scope sized for the round, not the demo, and sync behaviour the technician can predict.
-
Work management, planning, inventory and reliability processes shaped before screens are designed.
- Commercial MAS AppPoints and licensing
AppPoints sizing, BYOL guidance and licence supply as an IBM Gold Partner and MAS reseller.
-
SLA-backed application support with a named service manager, on MaxIron Cloud, in your Azure, AWS or OCI tenancy, or on an estate already live.
- Commercial Maximo 7.6 Extended Support
Stay supported and auditable on 7.6 while the move to MAS is planned, with the cutover path agreed now.
- Beyond Manage Enterprise AI for asset management
Governed data, condition insight and in-Maximo assistance, on estates where the groundwork is in place.
Boundaries
Four boundaries that hold on every engagement
These apply whichever situation you arrived in, and they are in the contract.
Data ownership stays a governance decision
We can show you where the same asset, cost centre or person exists in three systems, and build the interface for whichever answer you choose. Choosing which system is master sits with your organisation, and no scope transfers it.
A fixed date is met with a smaller first phase
Where a date can be met only by cutting process design, data readiness or training, we propose a reduced first phase against the same date instead. Compressing those three produces a go-live that satisfies the plan and not the operation.
The product owner stays inside your organisation
Someone of yours holds priorities, arbitrates between areas and accepts the platform. Where nobody has that time, delivery stalls waiting for decisions, so the role is agreed at the start.
A service commitment requires monitoring and a change route
An SLA covers environments we can see and change. Where monitoring, access or a change route is withheld, support is best-effort and the contract says so.
Questions buyers ask about these engagements
- How quickly can we get a price for a Maximo 7.6 to MAS upgrade?
- The analysis is free. Once we have your customisation and integration inventory, a fixed-price quote follows within 24 hours, and a trial upgrade can run in a test environment inside a week. Start on the free upgrade quote.
- Do you only work on estates you host yourselves?
- No. We implement and operate MAS on MaxIron Cloud, in your Azure, AWS or OCI subscription, in your data centre, or on IBM-hosted MAS. Where the estate must sit in your subscription, we design the architecture, build it and can run it. We do need monitoring and a change route, because a service commitment is only meaningful where the estate is visible. Standing application support is documented on Maximo and MAS application support.
- What does a health check produce?
- A findings document across seven areas, written for a board: what is deployed, what is unsupported, where risk is concentrated, what to fix first and what to defer. Paid work, and the output is yours whether or not the remediation comes to us. See Health Check and Heal.
- Can you take part of an ongoing programme?
- Yes. Architects, consultants, developers and data specialists take a defined part of your delivery, inside your governance and change control, and are responsible for that part. See specialist augmentation.
Start with the customisation inventory.
An inventory records what the estate is holding today, which is what sets cost and risk. A conversation with a senior engineer establishes the assessment scope, dependencies and next decision.
Useful to have on the call
- Your Maximo or MAS version, and how many environments you keep
- The customisation and integration list, however rough
- Work order volume per month, plus users and sites
- The date that is already fixed: an audit, a support expiry, or a season you cannot touch