Skip to main content
Zemerc
Operate · Asset Integrity & Reliability

Asset integrity, from inspection through action.

Keep operating assets available, maintained, inspected and supportable through governed asset records.

4
Applications
5
Stages in the flow
Why this area

Asset 360

Keep operating assets available, maintained, inspected and supportable through governed asset records.

  • Asset 360

    A consolidated asset view brings together inspection findings, barrier status and other governed asset information.

  • Quantitative reliability analysis

    RBD, FMECA, fault trees and Weibull analysis inform availability and maintenance decisions.

  • Supportability decisions made early

    Obsolescence risk and lifetime-buy decisions are recorded against where an item is used.

How the work moves

5 stages, each owned by an application.

Each stage shown here is supported by a Zemerc application, and every application remains independently operable. Operating areas are a way to understand related work, not a mandatory commercial bundle.

Asset
Inspection
Reliability
Maintenance
Supportability
Stage 1 of 5AIRMS
Asset

The governed asset register and consolidated asset view.

Inside the application

AIRMS: Asset Integrity & Reliability Management System

Integrity, inspection, corrosion and barrier records with an Asset 360 view.

AIRMS barrier assurance: performance standards with their governing standard and assurance frequency, the assurance activities carried out against each barrier with their conformance and verification state, and the degradations and impairments recorded against barriers with their restoration position

Barrier-health and criticality positions are not calculated unless an approved method exists. Performance criteria are organisation-defined, and assurance outcomes remain recorded engineering judgements.

  • A blank field means unknown
    An unrecorded value is not treated as zero, and the application identifies the evidence required before a figure can be produced.
  • Immutable where required
    Thickness readings and approved assessment revisions are not edited in place; corrections create new governed revisions with their own provenance.
  • Independent verification
    A work order is completed by one authorised person and closed by another where policy requires separation of duties.
How the record moves

Integrity defines the requirement. Maintenance executes the work.

Asset integrity, maintenance execution, quantitative reliability and obsolescence answer different questions about the same equipment. Their value depends on a consistent governed asset identity across those disciplines.

  1. Integrity
    Maintenance

    A defect with evidence-gated closure becomes governed work with an owner and due date.

  2. Maintenance
    Reliability

    Failure events and recorded exposure feed quantitative reliability analysis

  3. Reliability
    Obsolescence

    Spare-parts strategy must consider whether required items will remain supportable and available.

Workshop · failure analysis

Bring one asset and its last inspection.

Failure events coded to a standard taxonomy support reliable analysis and reuse. Free-text descriptions alone provide limited analytical value.

  • Integrity record; AIRMS governs integrity, inspection, corrosion, RBI and fitness-for-service records, including barrier-related evidence where applicable.
  • Quantitative reliability; RAMS models reliability, availability and maintainability with recognised methods.
  • Maintenance execution; EAMS runs work orders, preventive maintenance, inventory and calibration.
From engineering judgement to governed work

Lifecycle state and operational state are distinct controls

Operating state and maintenance priority are separate controls. An asset may remain in service while replacement is planned, or remain available while on standby. Keeping those states distinct allows work to be prioritised by operational consequence rather than by arrival order.

  • Criticality is recorded as an engineering judgement and then used consistently rather than recalculated ad hoc.
  • Attention is reported as overdue work, overdue inspection or outstanding analysis
  • Completion and closure are kept distinct, with independent verification between them
Plant · preventive maintenance

Where this operating area is managed in practice

Usage-based maintenance becomes due when equipment reaches defined operating thresholds, not only when calendar time elapses. This depends on governed meter readings rather than estimated utilisation.

  • Obsolescence cases; OMS records supportability risk and lifetime-buy decisions with where-used impact.
Questions we are asked

Before the first working session

  • Which applications belong here?

    AIRMS, RAMS, EAMS and OMS.

  • How do the four applications work together?

    AIRMS governs integrity and inspection records, RAMS governs reliability analysis, EAMS governs maintenance execution, and OMS governs obsolescence risk. Each application retains its own governed records and remains independently operable.

  • Which application should come first?

    Start with AIRMS where inspection and integrity records require stronger control, or EAMS where the primary need is maintenance execution.

  • Integrity record

    AIRMS governs integrity, inspection, corrosion, RBI and fitness-for-service records, including barrier-related evidence where applicable.

  • Quantitative reliability

    RAMS models reliability, availability and maintainability with recognised methods.

  • Maintenance execution

    EAMS runs work orders, preventive maintenance, inventory and calibration.

  • Obsolescence cases

    OMS records supportability risk and lifetime-buy decisions with where-used impact.

AIRMS

Bring one asset and its last inspection

The demonstration will show the governed integrity record and the decisions or work it supports.