Emerging Skills Program — no certification exam
Reliability & Asset Integrity
Where reliability engineering and integrity management actually meet — failure data, criticality, maintenance strategy, and the decisions both disciplines own jointly.
Why this matters
The problem this solves
Reliability and integrity are usually two teams, two datasets and two sets of priorities, arguing about the same equipment with different vocabularies.
One team is trying to stop production losses, the other is trying to stop a loss of containment. They share the equipment, most of the failure data and almost none of the language — which is why criticality gets ranked twice, differently, and why the maintenance strategy that results satisfies neither.
This programme works the overlap: a common failure taxonomy under ISO 14224, criticality that both disciplines can sign, RCM done properly against SAE JA1011, and the point where reliability hands over to risk-based inspection rather than duplicating it.
Before you enrol
Is this a certification?
The short answer is no, and it is worth being explicit about it rather than leaving it to be discovered later.
What this programme gives you
- Three days on the overlap between reliability engineering and integrity management
- A criticality method that serves both functions from one assessment
- A worked RCM analysis tested against the SAE JA1011 criteria
- An EIM certificate of completion
What it does not
- Not preparation for a certification exam — no certifying body examines this overlap
- Not a CMRP, CRE or ISO 55001 lead auditor qualification
- Not API 580 preparation — that is a real certification with its own exam
- Not a CMMS or reliability software implementation
If you need a recognised credential, start at certification exam preparation.
Who it's for
Roles this is built around
Reliability engineers
Any level
Working alongside an integrity function and duplicating half of its analysis.
Asset integrity engineers
Any level
Owning the containment risk while maintenance owns the schedule.
Maintenance and planning leads
Any level
Building the strategy that both functions have to live inside.
What it covers
The outline
An outline, not a weighted Body of Knowledge — nobody publishes weights for a subject with no exam behind it.
Two disciplines, one asset
Production loss versus loss of containment, and why the same equipment gets ranked twice.
Failure data that is worth having
ISO 14224 taxonomy, failure modes and the discipline that makes history usable.
Criticality both sides can sign
One assessment serving safety, environmental and production consequence.
Maintenance strategy selection
RCM against SAE JA1011, FMEA, and when a run-to-failure decision is the right one.
Where RBI takes over
The handover from reliability to risk-based inspection, and the overlap that should not be duplicated.
Measuring it
Availability, MTBF and bad-actor analysis, and the metrics that drive the wrong behaviour.
Outcomes
What you will be able to do
- Build a failure taxonomy under ISO 14224 that makes maintenance history analysable
- Run one criticality assessment that both reliability and integrity will accept
- Apply RCM against the SAE JA1011 criteria rather than a vendor’s version of it
- Decide where reliability analysis should stop and risk-based inspection should begin
- Identify bad actors from real failure history rather than from recollection
- Choose reliability metrics that do not quietly reward deferring the right work
Standards referenced
What the programme works from
| Standard | What we use it for | Note |
|---|---|---|
| ISO 14224 | Collection and exchange of reliability and maintenance data | The failure taxonomy |
| SAE JA1011 | Evaluation criteria for RCM processes | What counts as real RCM |
| API RP 691 | Risk-based machinery management | The rotating-equipment bridge |
| ISO 55001 | Asset management — management systems | The governing frame |
| API RP 580 | Risk-Based Inspection | Where the handover happens |
How it runs
Ways to take it
Formats offered — not scheduled dates. Live cohort dates live on the course page, so there is only ever one copy of a date.
| Format | Duration | Group size | Notes |
|---|---|---|---|
| Live online | 3 days | Up to 15 | Split across sessions rather than run as consecutive full days |
| In-house | By arrangement | 6–20 | Delivered against your own equipment, your own findings and your own procedures |
FAQs
Questions people ask first
No. API 580 Risk-Based Inspection is a genuine API certification with a Prometric exam, and EIM prepares people for it through the certification guides. This programme covers where reliability work meets integrity work, and RBI is one boundary of that rather than the subject.
Both, and the split is much of the point. Reliability practice grew up around rotating equipment and integrity practice around static; teams that hold both are usually running two incompatible criticality schemes.
No, though having real maintenance history makes the failure-data and bad-actor modules considerably more useful. For an in-house delivery we would work from your own data where you are able to share it.
Want the full outline?
Tell us your role and what you are trying to fix, and we will send the programme outline and what it would take to run it for your team.