ISO 14224 and API RP 14C standards programme on IBM Maximo for an oil and gas operator
A North Sea operator needed its Maximo data to answer the questions reliability and HSE engineers actually ask, against the same standards regulators and partners use. The clearest way to show what that means is to take one safety-critical element record apart, field by field.
How this is written
As a teardown of the artefact. Nine fields on one record, what each one holds now, and what each one replaced.
After the mergers
Three organisations inside one asset register: three ways of describing the same pump, four failure-mode lists, and a quarterly safety-critical report assembled in spreadsheets.
Regulators, partners and the corporate reliability function asked for ISO 14224-aligned failure data and API RP 14C evidence on request. That requires the standard built into the asset register itself, under a live safety case that stayed in force for the whole programme.
The artefact, taken apart
One safety-critical element record, field by field
A standards programme cannot be judged from a scope list. It can be judged from a record. Nine fields, what each replaced, and who set the new value.
Safety-critical element, anonymised, IBM Maximo
9 of 9 fields changed
| Field | Before | After | Set by |
|---|---|---|---|
| Location and hierarchy position | Divergent location hierarchies inherited from successive mergers. | One normalised location hierarchy position for the element. | Standards committee, after the written hierarchy definition was signed. |
| ISO 14224 taxonomy level | Three internally consistent classification schemes, each correct for the organisation that built it. | Asset class, equipment unit, sub-unit and maintainable item applied for the equipment type. | Reliability function, against the signed ISO 14224 mapping. |
| Legacy scheme reference | Nothing held. Overwriting would have deleted the operator’s own history. | Codes from each previous scheme, held through a maintained crosswalk. | Data governance forum, as a permanent artefact rather than a discarded migration script. |
| Safety-critical element flag | A separately maintained list, reconciled against the register by hand. | Whether the element is safety-critical under API RP 14C, and on what basis. | HSE and reliability, against API RP 14C. |
| Performance standard | Narrative documents held elsewhere, correct but not connected to the asset. | The standard the element must meet, held on the element itself. | HSE, as the verification basis for the element. |
| Verification activities | Quarterly manual assembly of evidence from several sources. | Planned activities on the maintenance schedule that demonstrate the performance standard. | Maintenance planners, once the standard was attached to the element. |
| Deferral rule and approver | Recovery from memory and email after the fact. | What may be deferred, by whom, and the reason, recorded at the moment of deferral. | Named approver for the criticality band, at the time of deferral. |
| Criticality | Values carried forward through two mergers without review. | Criticality re-baselined against the written definition. | Asset management, against the signed criticality definition. |
| Failure mode and mechanism | Four failure-mode lists for the same equipment types. | Codes from managed reference lists on the work record. | Reliability function, after the managed list was agreed. |
Anonymised. Client-identifying tags, locations and element IDs removed.
The decision that made the third field possible
The legacy schemes were mapped, not overwritten, and the crosswalk was kept as a maintained artefact.
An operator that cannot analyse its own history has bought a clean model and lost the reason it wanted one. Every mapping was tested against whether a reliability engineer could still interpret a work order coded fifteen years ago under a scheme that no longer exists.
Around the record
What the programme delivered, and what the model connects to
Cite D1-D4 for deliverables and I1-I4 for integrations when you take this into a scoping paper.
| Ref | Item | What it does |
|---|---|---|
| D1 | ISO 15926 handover templates | New-build and brownfield templates in the contractor scope, so handover arrives Maximo-ready. |
| D2 | Master data remediation | Duplicates merged, hierarchy normalised, work history mapped onto the standardised model. |
| D3 | Reliability layer | MTBF, MTTR and bad-actor reporting as a thin layer over standardised Maximo data, not a second database. |
| D4 | Governance with refuse rights | Data governance forum, Maximo standards owner role, controlled change around the model. |
| I1 | SAP PM / Finance | Bi-directional: cost objects, spares, purchase order and invoice flow. |
| I2 | Reliability analytics | Outbound: MTBF, MTTR, bad-actor analysis from the same work records. |
| I3 | Contractor handover packs | Inbound per project: ISO 15926 templated exchange. |
| I4 | HSE incident system | Inbound link from incidents to assets and safety-critical elements. System of record stays outside Maximo. |
HSE incident system remains the system of record for incidents.
Where the standards sit
The model, and what feeds it
ISO 14224, API RP 14C and ISO 15926 sit on the Maximo register. Reliability analytics and SAP consume the same records; the HSE incident system stays linked, not absorbed.
What each side carries
- Standards inbound
- ISO 14224 taxonomy, API RP 14C safety-critical tagging, ISO 15926 handover templates for new and brownfield projects.
- Analytics outbound
- MTBF, MTTR and bad-actor reporting built as a thin layer over the standardised work record.
- Enterprise links
- SAP PM and finance for cost and spares; operator dashboards for SCE performance.
Boundaries and judgements
Three refusals, and three sequencing changes we would make
A standards programme expands indefinitely unless the edges are written down. The model is live and maintained; these are the edges we held, and the sequencing we would change.
No full taxonomy on all history
A cut-off was agreed for how far back full ISO 14224 detail applies, based on the period reliability analysis uses. Beyond it, the crosswalk preserves interpretation without full re-coding. We would now fix that boundary in writing before touching a record.
HSE incident system stays outside
Out of scope. It remains the system of record for incidents, with a link to assets and safety-critical elements. Absorbing a live safety-related system into a standards programme adds risk without adding evidence.
Validate failure modes with the people who code them
Reference lists were agreed with reliability and the standards committee, then applied by technicians closing work orders offshore. We would now test the list with the people who apply it before it becomes the managed list, and appoint the standards owner at mobilisation.
Where it stands now
The standards model the operator runs today
Standards in force
- Taxonomy
- ISO 14224, three legacy schemes crosswalked rather than overwritten
- Safety-critical
- API RP 14C performance standards and verification on the asset record
- Handover
- ISO 15926-aligned templates for new and brownfield projects only
- Database
- IBM Maximo on DB2
What the operator can produce
- SCE evidence
- API RP 14C performance reporting from Maximo on request
- Reliability
- Comparable failure data across assets and platforms
- Ownership
- Standards owner role and governance forum live under controlled change
- MaxIron role
- Standards and reliability advisor on a retained basis
Anonymised. Client-identifying assets, fields and naming removed.
Programme facts
- Sector
- Oil & gas (upstream / offshore)
- Region
- United Kingdom (UKCS)
- Duration
- 12 months programme + ongoing run-and-improve
- Scope
- Standards model, master data, integration, reliability analytics
- Versions
- IBM Maximo on DB2
If your standards work is next to Maximo rather than inside it
Services and products in this engagement
Questions engineers ask about this programme
- Why is the operator not named?
- Anonymised at their request. Safety-critical element performance and failure history are among the most sensitive data an operator holds. Reference conversations can be arranged under an NDA.
- Does an ISO 14224 programme mean replacing what is already in Maximo?
- No. Every legacy scheme was crosswalked to the target model rather than overwritten, so history coded under the old schemes stays interpretable. The mapping is a maintained artefact, not a migration script that gets thrown away.
- Can API RP 14C evidence really come out of Maximo?
- It can when safety-critical elements carry their performance standards, verification activities and deferral rules in the same place as the asset record. A safety-critical element tagged without its performance standard is a label, and a label cannot be verified.
- Why not build a reliability database instead?
- Because it forks the truth on the day you create it. A thin analytics layer over standardised Maximo data means the reliability engineer and the maintenance planner read the same records. See MaxIron AI Smart Data for the classification volume.
- What stays hard?
- Deciding how far back the standard applies. Retro-fitting full ISO 14224 detail to all historical work orders is effort without a defined end. That boundary is a judgement about analysis value, and it belongs to the operator.
If your safety-critical reporting is assembled by hand every quarter, the problem is upstream of the report.
A standards assessment that maps your current classification schemes against ISO 14224, tests whether your safety-critical elements carry their performance standards, and proposes a historical boundary you can defend. Our Head of Account Management led standards work of this kind at a supermajor operator before joining, and that discipline shapes how we scope it.
Bring this and the assessment can go deep quickly
- Your current classification scheme or schemes, including the ones you inherited.
- Your failure-mode list as it exists today, and who maintains it.
- Your safety-critical element list and how performance standards are currently held.
- The last quarterly safety-critical report, and an honest estimate of how it was produced.
- Your handover data requirement as it appears in contractor scopes today.