Skip to main content
Zemerc
The portfolio

27 applications. Start with the industrial record or workflow you need to govern.

Zemerc is a portfolio of independently operable applications. Each one governs a defined class of industrial record and can be adopted on its own. Start with the record or workflow that needs control, then add other applications only where the operation requires them.

How it is sold

A portfolio of independently operable applications not dependent modules within a single platform.

This distinction matters commercially and operationally. Clients may purchase and operate one application without buying the wider portfolio or depending on another Zemerc product.

  • Every application operates independently

    Each application has its own users, data, controls and release lifecycle. It remains fully operable as a standalone product.

  • Adopt one application independently

    A client may adopt one application for one team without any requirement to purchase another. Expanding the portfolio remains a separate decision, not a dependency.

  • Connected only where records genuinely relate

    Applications exchange defined records only where the underlying work crosses a genuine operational boundary.

Find your application

Narrow the portfolio to the application that matches your requirement.

Filter by operating stage and operating area, or search using the record or workflow you manage, such as a punch list, sealed tender, barrier or meter reading.

Search matches application names, governed records and lifecycle stages.

Operating stage
Operating area

27 applications in the portfolio

In depth · Governance

PDMS: Project Delivery Management System

Portfolio governance, project workspaces and stage-gate evidence.

PDMS executive workspace showing active projects, controlled documents, critical and high risks, portfolio condition, current attention items and discipline positions across schedule, progress, cost, construction, engineering, governance, procurement and readiness

Portfolio, programme and project records are governed within one structure, with stage gates derived from workspace registers rather than manually entered status. Where the available history does not support a completion forecast, no forecast is produced.

0
Applications in the portfolio
0
Operating areas
0
Stages of the operation
In depth · Evidence

Barrier assurance depends on activity that was performed, not on policy statements alone.

Performance standards carry their governing standard and assurance frequency. Each assurance activity records what was performed and what was found, and degradations are tracked through to restoration.

  • No integrity score, health index or readiness score is calculated unless a defined and supportable method exists
  • Thickness readings and approved assessment revisions are retained as immutable governed records
  • A defect cannot close until the required supporting evidence is complete
In depth · Reproducibility

Every quantity is traceable to the reading that produced it.

Readings are retained immutably with governed substitution. Each reading is classified by its validation state as valid, warning or suspect rather than being silently accepted.

  • Effective-dated calculations rerun a historical period using the method that was in force at the time.
  • Allocated quantities reconcile against counterparty statements
  • Record lineage is retained through close-out, when traceability is most important.
Where to start

22 operational problems and the applications designed to address them.

Most organisations start with a requirement rather than an application name. These examples link common operational problems to the applications designed to govern the relevant records or workflows.

How applications relate

Applications connect only where operational records genuinely intersect.

Applications do not share data merely because they are sold within one portfolio. Controlled interfaces exchange named records only where work genuinely passes from one team or process to another.

  • PMSLGMS

    Receipt: a received item can trigger the logistics activity required to move it

  • LGMSCCMS

    Delivered item: receipt and acceptance records support installation and testing readiness

  • CCMSSPIR

    Completed system: verified completion evidence becomes part of the handover record

  • QMSCCMS

    Inspection and test record: quality evidence can become completion evidence

  • IFMSPDMS

    Open interface: an unresolved boundary can become a delivery exposure

  • TSMPSM

    Safety-critical element: a design definition becomes an operational assurance obligation

  • PSMAIRMS

    Barrier assurance: an assurance obligation can become an inspection or integrity activity

  • AIRMSEAMS

    Defect: an integrity finding can generate maintenance work with a verification step

Selecting an application

Choose the first application based on the team and record that need stronger control.

Application selection should begin with the team that owns the relevant record or workflow, rather than with a suite-level procurement decision. That team is best placed to test whether the application supports the work.

  • Each application operates independently, so initial adoption creates no dependency on another Zemerc application.
  • Cross-area relevance is shown explicitly, with one primary area and any additional areas served.
  • Each application page presents the application’s own interface and screens rather than generic illustrations.
The complete directory

All 27 applications by operating stage and area

Every application in the portfolio, with its primary operating area and any additional areas it supports.

See the applications working with your own records

A working session built around one of your own registers, projects or assets, showing the application against representative records and controls.