Can one Maximo model carry mobile plant and fixed plant?

Yes, and both populations stay first-class. Haul trucks, loaders and tracked crushers run on hours, kilometres and engine hours; kilns, mills and batching plants run on calendar and condition triggers. Rotables and exchange units keep their own history, so a hydraulic pack moving between two crushers carries its cost and warranty with it.

What should be standardised across sites, and what should stay local?

Standardise the asset classification, the failure taxonomy, the PM strategy for common plant types, the storeroom structure and the mobile flows. Leave the working pattern local. A coastal aggregates site and an inland cement works do not run the same day, and forcing one rhythm is the most reliable way to make a rollout slow down.

Does Maximo work alongside SAP, or instead of it?

Both patterns exist in this sector. The common one is Maximo taking asset and work management while SAP stays the finance and procurement spine, with purchase orders, goods receipts, work order costing and inventory valuation flowing back so nobody does double entry. Our reference UK and Ireland programme went live across more than forty sites in eight months on that pattern.

Building materials

IBM Maximo for building materials, quarrying and ready-mix

Maximo for distributed building-materials estates: quarries, cement, asphalt and ready-mix in one platform, mobile and fixed plant first-class, finance still on SAP if you want.

Book a multi-site rollout review Read the multi-site case study

Distributed estates, thin local IT

Sites acquired one at a time arrive with their own engineering culture

Three patterns we are most often called into across quarries, cement works, asphalt plants and ready-mix depots.

The same crusher, maintained four ways

One plant family, a different regime at each site, because each site was bought with its own suppliers and habits and nobody held the mandate to reconcile them.

The van is the office

A mobile fitter covers several sites a week and rarely opens a laptop. Tuesday morning at the quarry is written up on Thursday from a photograph.

Statutory inspections in a separate register

Geotechnical assessments, tip inspections, lifting examinations and weighbridge verifications sit in one person’s spreadsheet, so an overdue item surfaces in a conversation with an inspector.

Mobile plant availability nobody can forecast, and a group engineering function with no comparable cost or downtime data to manage from.

Who keeps score

Six scorekeepers on a quarrying and building-materials estate

Extractives carry statutory duties on top of the usual work-equipment regimes, and several of them require a competent person rather than a completed job.

Ref	Scorekeeper	Asks for	Will not accept
BM1	Health and Safety Executive, Quarries Regulations 1999	Geotechnical assessment of excavations and tips, inspected at the required interval by an appointed competent person.	An inspection recorded without the appointment behind it. The competence of the person is part of the duty.
BM2	Environment Agency, SEPA or Natural Resources Wales, under the site environmental permit	Evidence that permit conditions are met, including maintenance and calibration of abatement and monitoring equipment.	Monitoring data from an instrument with no calibration record. An uncalibrated reading proves nothing about the emission.
BM3	Health and Safety Executive, COSHH and respirable crystalline silica	Dust suppression and extraction maintained in efficient working order and examined at the required interval.	A suppression system marked as installed with no maintenance history. A control measure that is not maintained is not a control.
BM4	Health and Safety Executive, LOLER 1998 and PUWER 1998	Thorough examination of lifting equipment at the required interval, and work equipment maintained in efficient working order.	A report held by the insurer or the inspection contractor with no copy against the asset. It has to be findable from the equipment.
BM5	Trading standards, weights and measures verification	Trade-approved weighbridges verified and maintained, so the weight a customer is charged for is the weight they received.	A weighbridge left in service past its verification. Every ticket issued after that date is commercially exposed.
BM6	Your certification body, ISO 55001	A traceable line from the group asset management policy through to the maintenance work executed at each site.	A group policy carrying forty local interpretations. Consistency is the thing being certified.

Codes BM1 to BM6 are stable, so a bid writer or auditor can cite one by reference.

The mechanism

One pilot, a narrow template, then a cadence

The discipline sits in stage two: what the template contains is always less than a programme board wants it to be.

01

Pilot one site end to end

One site taken through with the mobile fitters and the site engineer in the room, to establish which parts of the operating model are common across the group and which are local for a reason that survives scrutiny.

Owner MaxIron functional lead with your site engineer Typically 8 to 12 weeks
02

Fix the template, and keep it narrow

Asset classification, failure taxonomy, PM strategy for common plant types, storeroom structure and mobile flows. Shift patterns and local supplier arrangements stay local, because every addition is paid for again at every subsequent site.

Owner Group engineering, on a written mandate Typically 3 to 4 weeks
03

Put statutory work in the same plan

Geotechnical assessments, tip inspections, lifting examinations, weighbridge verification and permit checks modelled as work with a competency requirement attached, so an overdue item reaches whoever manages the schedule.

Owner MaxIron configuration analyst Typically 2 weeks
04

Build the finance boundary once

Purchase orders, goods receipts, work order costing and inventory valuation flowing to SAP FI/CO, designed against the template so each site inherits the interface instead of negotiating it. The patterns are on Maximo integrations.

Owner MaxIron integration architect with your finance systems team Typically 4 to 6 weeks
05

Roll out on a cadence, then operate it

Sites go live in sequence, each inheriting the template, with genuine improvements folded back into it. MaxIron runs the estate afterwards, so no site carries platform administration it was never staffed for.

Owner MaxIron delivery lead Typically 3 to 8 weeks per site

Before you commission anything

Five statements about your group, in order

Multi-site rollouts fail for reasons visible before the programme starts. Stop at the first statement that is false: that is where the first phase has to begin.

1
Group engineering can retire a site maintenance regime and replace it, in writing.
2
The same plant family carries the same classification at every site today.
3
A fitter can identify the exact serialised unit at the machine, in gloves, with no signal.
4
Statutory inspections sit in the same plan as maintenance work.
5
No site is expected to provide local IT support for the platform.

If you stopped early

Whichever statement you stopped on sets the first phase. A group without the mandate in statement one gets forty local systems sharing a logo, so the mandate is the work before the software is.

If every statement held

The template can be set from the pilot and enforced, which is the single largest factor in how fast sites two to forty go live.

In conversation with Mark

Mark Seymour

Head of Sales and Business Development · 28+ years in technology product and sales

Mark on running an estate assembled by acquisition

What is different about a building-materials group?: Most of the estate was acquired rather than built. Each site arrived with its own engineering culture and its own idea of how a crusher should be maintained, and nobody was ever given the mandate to reconcile forty of them. That is history, and a configuration workshop does not fix history.
Why IBM Maximo across a group like that?: Fixed plant, mobile plant and rotables have to sit in one model, and the model has to template: the same crusher type at eleven sites is one PM strategy applied eleven times. Maximo does that, and it will run the group without each site looking after it. Site engineering teams here are three or four people, and platform administration is not the job they were hired for.
Where do these programmes go wrong?: The template. Standardise too much and every site resists something that existed for a good local reason. Standardise too little and you have forty local systems. Classification, taxonomy, PM strategy for common plant, stores structure and mobile flows are worth mandating. Shift patterns and local supplier arrangements are not.
What will you not promise?: A group-wide template priced before the pilot has told us what is genuinely common, because pricing that means guessing. And a rollout does not remove the need to persuade a site. It reduces the number of things you have to persuade them about, which is a smaller and real claim.

Mark shapes what a group needs from a Maximo partner before procurement starts, and stays on the engagement through proposal and contract.

Boundaries

Three conditions on a multi-site rollout

Each was learned on a rollout rather than in a workshop, and each is stated before the programme starts.

The group template is written after the pilot site

A standard drafted before one site has run properly carries assumptions that every later site argues with, and the argument costs more than the pilot did.

Standardisation runs on a mandate from group engineering

Some local variation exists for sound reasons. We show where the differences are and what each one costs; the instruction to a site manager comes from group.

Site go-live times follow a trend with real variance

The average falls sharply after the first two sites. Individual sites still carry an unusual plant configuration, an undocumented interface or a change programme of their own, and the plan holds that variance explicitly.

Maximo for building materials, questions we are asked

Can one Maximo model carry mobile plant and fixed plant?: Yes, and both populations stay first-class. Haul trucks, loaders and tracked crushers run on hours, kilometres and engine hours; kilns, mills and batching plants run on calendar and condition triggers. Rotables and exchange units keep their own history, so a hydraulic pack moving between two crushers carries its cost and warranty with it.
What should be standardised across sites, and what should stay local?: Standardise the asset classification, the failure taxonomy, the PM strategy for common plant types, the storeroom structure and the mobile flows. Leave the working pattern local. A coastal aggregates site and an inland cement works do not run the same day, and forcing one rhythm is the most reliable way to make a rollout slow down.
Does Maximo work alongside SAP, or instead of it?: Both patterns exist in this sector. The common one is Maximo taking asset and work management while SAP stays the finance and procurement spine, with purchase orders, goods receipts, work order costing and inventory valuation flowing back so nobody does double entry. Our reference UK and Ireland programme went live across more than forty sites in eight months on that pattern.

Bring two sites that run the same plant differently.

That comparison shows what is genuinely local, what is habit, and how much of your group engineering standard has landed. We walk both operating models through the template we would build and name what the second site inherits.

Bring this to the first call

The PM regime for one plant type at two different sites
The register you use today for statutory quarry inspections
The history of one rotable unit that has moved between sites
The finance interface requirements, if SAP is staying