Sectors
Every sector answers to a different scorekeeper
A regulator, class society, insurer or auditor rejects different evidence about the same asset. That shapes an IBM Maximo configuration more than the industry label does.
The index
Seven sectors, and the body that audits the record
Each page is built around the argument that decides the purchase in that sector.
| Ref | Sector | Who keeps score | What that page settles | Answered by |
|---|---|---|---|---|
| S1 | Utilities | Ofgem, Ofwat, the HSE and the Drinking Water Inspectorate | The regulatory scoreboard, and the evidence each body turns down. | Ivan Milic |
| S2 | Transport & airports | the Office of Rail and Road, the Civil Aviation Authority and the HSE | Work inside an operating window that never closes: the inspection, the stand, the possession. | Bill Hulbert |
| S3 | Manufacturing | the HSE, your insurer and their engineer surveyors | Two availability figures, held apart until the Monday meeting can end. | Ivan Milic |
| S4 | Maritime | class societies, the flag administration and port state control | An estate that sails away from you, and one defect handled two ways. | Mark Seymour |
| S5 | Oil & gas | the offshore safety regulator, the independent verification body and the insurer | The safety case, and the three evidence chains a verifier examines. | Jonathan Heward |
| S6 | Public sector | the National Audit Office, HM Treasury and departmental security | Procurement and audit, and what the next spending cycle stops paying for. | Robert Carew |
| S7 | Building materials | the HSE under the Quarries Regulations 1999, and the environmental regulator | Distributed sites with thin local IT, and a readiness check before anything is commissioned. | Mark Seymour |
Codes S1 to S7 are stable, so a bid writer can cite one by reference.
One level deeper
Four pages where one MAS module meets one sector
- Utilities and Monitor IBM Maximo Monitor on a regulated network
The tag feed leaving the operational zone, and who accepts an anomaly before it becomes work.
- Utilities and Renewables IBM Maximo Renewables beside a regulated network
Instructed curtailment separated from a real fault, and a dispatch order set by wind speed.
- Oil and gas and Predict IBM Maximo Predict on upstream rotating equipment
ISO 14224 coding read before a model is built, and the technical authority who decides.
- Transport and Visual Inspection IBM Maximo Visual Inspection in a CAA or ORR regime
The competency recorded beside every classification, and the two disagreement paths.
How it starts
Four stages, whichever row you picked
The audit question is answered before the asset model is designed.
- 01
Name the audit and the refusal
Which body examines the record, at what interval, and what it has turned down before.
Owner MaxIron sector lead with your compliance owner Typically 1 workshop
- 02
Watch the work where it happens
In the chamber, on the apron, in the engine room or at the quarry face. What a technician can record in gloves with no signal constrains the form design.
Owner MaxIron functional lead Typically 2 to 5 days per work type
- 03
Build the model so capture rolls up
Asset hierarchy, failure taxonomy, criticality and mobile forms configured so field capture becomes the evidence itself, with no reconciliation step.
Owner MaxIron configuration analyst Typically 6 to 12 weeks
- 04
Operate it and test the evidence path
The estate runs as MaxIron-managed hosting and support, and the path from capture to submission is exercised every period.
Owner MaxIron delivery lead Typically Every reporting period
Common to all seven
Four capabilities carry every sector page above: mobile capture, integrations, data migration and process design. The obligation they are shaped around is what changes.
A sector engagement is priced from those four: Maximo Mobile, integrations, data migration and business process optimisation. Who audits you sets the design decisions inside them.
Scope of sector work
Four boundaries that hold in every sector
The sector pages carry the specifics.
Patterns are reused; the configuration is fitted to your operation
Obligations are shared across operators in a sector, and we carry patterns between them. The operating model, the organisational boundaries and the field conditions are fitted each time.
Analytics are sequenced behind a reliable foundation
Monitor, Predict and Health earn their place where the asset model and the failure coding are already reliable, so they are sequenced behind Manage.
We build the evidence chain; your regulator reaches the verdict
Whether a regulator, a verification body or an auditor is satisfied is settled between them and you.
Judgement stays with the engineer at the point of decision
The engineer, the duty manager and the integrity specialist decide. Design puts the right record in front of them at that moment, which is the claim we can evidence.
Bring the thing you have to defend.
A submission, survey, verification finding or audit question that was hard to answer. We trace it back to the person who produced the evidence and name where the chain breaks.
Bring this to the review
- One report, submission or evidence pack you assemble by hand today
- One field form or job pack as the crew actually receive it
- The list of systems that hold part of the asset record