Skip to main content
Zemerc
EAMSOperate · Asset Integrity & Reliability

Enterprise Asset Management System

Prioritise blocking maintenance work before the remaining backlog.

A governed system of record for the asset lifecycle, including the asset register, work management, preventive maintenance, inventory and spares, inspection, calibration and reliability. Work queues are prioritised by operational constraint and required action rather than by simple arrival order.

0
Module groups
0
Record types
0
Action types prioritised
0
Roles
One work order across six roles

Controlled hand-offs connect each maintenance stage of the maintenance workflow.

An observation on an asset becomes planned work, scheduled work, completed execution with materials recorded against it, and finally an independently verified maintenance record. Each stage produces a defined input to the next.

Operator · opens Work requests

Reports what was observed on the unit; a leak, a noise, a reading out of range; against the asset itself rather than as a message to a person.

Hands-on viewA work request with the asset and the observation on it

The verification policy

Completion and closure are distinct governed actions

Technicians complete work and authorised verifiers close it. EAMS maintains completion and verification as separate governed actions.

The consequence shows up in the numbers: a maintenance-compliance figure means work that was done and checked, and an asset’s history contains verified records rather than self-reported ones.

Work order
Requested
Planned
Scheduled
In progress
Completed
Verified
Returned for rework
Inside EAMS

Every asset retains criticality, lifecycle state, operational state and outstanding attention

Lifecycle and operational state are held separately because an asset may remain operational while planned for replacement or remain available while on standby. Attention is reported against the asset as overdue work, overdue inspection or outstanding analysis.

EAMS asset register showing functional location, asset type, criticality, lifecycle and operational state, attention items, and filters for location, criticality, lifecycle and kind

Where supporting operational data is unavailable, measures are reported as unavailable rather than zero.

  • Two states kept distinct
    Lifecycle and operational state are separate fields, allowing combinations such as planned replacement while operating or in service while on standby.
  • Criticality is recorded
    It remains an engineering judgement associated with the asset and is used by the work queue rather than recalculated automatically.
  • Attention is specific
    Assets show the overdue work, inspection or analysis that requires action rather than a generic warning state.
Capability architecture

Ten module groups organised around enterprise asset-management workflows

EAMS is organised around asset records, work management, inventory, condition, evidence and the operational work queue.

  • Asset management

    The asset register governs relationships, functional locations, classes, manufacturers, models and warranty as part of the asset record.

    • Asset register
    • Functional locations
    • Asset reference data
    • Warranty
    • Import assets
  • Work management

    Work requests become work orders that follow a defined lifecycle, with backlog visible by stage, crafts and contractors assigned, and approval rules applied before execution.

    • Work orders
    • Work requests
    • Maintenance backlog
    • Preventive maintenance
    • Job plans and crafts
    • Maintenance policy
  • Inventory and spares

    Stock and spare parts are managed across stores and locations through an immutable movement ledger, reorder-driven replenishment and stocktake reconciliation.

    • Stock
    • Spare parts
    • Stores and locations
    • Stock movements
    • Replenishment
    • Stocktake
  • Inspection and calibration

    Inspections with their due dates, a calibration programme carrying actual readings so an out-of-tolerance result is a recorded measurement, and failure events with analysis and a failure taxonomy.

    • Inspections
    • Calibration programme
    • Failure events
    • Analysis and assessments
    • Failure taxonomy
  • Documents and evidence

    Document control with a review and approval trail, the evidence held against the record that needs it, and certificates kept with the asset they belong to.

    • Document control
    • Evidence
    • Certificates
  • Work queue and reporting

    A personal work queue ranks sixteen pending-action types with blocking items first, supported by an operational calendar, report history, dashboards and notification rules.

    • My Work
    • Operational calendar
    • Reports
    • Report library
    • Dashboards
    • Inbox
    • Rules and channels
The maintenance programme

Maintenance plans generate work; meter readings determine usage-based due points

A maintenance plan identifies the asset, maintenance basis, frequency and next due point. Where maintenance is usage-based, governed meter readings drive the due position so work becomes due from actual equipment use rather than elapsed calendar time alone.

  • Overdue preventive plans are reported separately from generated work that has not been completed
  • Job plans and crafts are maintained separately from the preventive-maintenance plans that invoke them
  • Maintenance policy defines which work requires approval before proceeding
Who it is for

Eleven operational roles across the maintenance workflow

Operators, planners, schedulers, technicians, supervisors, store personnel, inspectors, calibration technicians, asset managers, document controllers and administrators work from the same governed records.

  • Sixteen pending-action types ranked with blocking items first
  • Operational calendar across crafts and contractors
  • Approval rules define which work requires authorisation before proceeding
Governed data

Sixty-two record types with defined lifecycle actions

Import, export, bulk update, historical migration, documents, evidence, templates and organisation-level extracts are governed through defined data-management routes. Round-trip support is stated explicitly for each record type.

EAMS data-management view showing supported record types, export and import capability, round-trip support, bulk update, historical migration, documents, evidence, templates, starter packs and recent data-management runs
  • Independent verification

    Work-order completion and closure are separate actions performed by authorised roles. Verification requirements are configured as policy rather than left to informal practice.

  • An immutable stock ledger

    Stock movements are appended rather than edited. Issues remain attributable to the relevant work order, and stocktake reconciles against the ledger rather than replacing it.

  • Unavailable data is not treated as zero

    Where supporting operational data is unavailable, the measure is reported as unavailable rather than zero so missing readings are not interpreted as positive results.

  • Blocking work is prioritised first

    The personal queue ranks sixteen pending-action types by operational blocking effect rather than arrival time.

Also in EAMS

More of what the application covers

  • Asset 360 view with relationships across relevant modules
  • Functional-location hierarchy from business unit to area
  • Warranty recorded against the asset
  • Meter-driven maintenance from recorded readings
  • Stores and locations with replenishment
  • Operational calendar across crafts and contractors
  • Engineering knowledge library
  • Starter packs for units, notification rules and failure codes
EAMS

Review EAMS using one of your maintenance backlogs.

Bring one asset and its open work. The demonstration will show the resulting queue, verification requirements and associated stock movements.