Skip to main content
Zemerc
Company · application philosophy

27 applications. No suite to buy first.

Every Zemerc application must provide complete value on its own. That requirement shapes the portfolio and the trade-offs it accepts.

The principles

6 principles, each with a practical consequence.

A principle is meaningful only when it has practical consequences. Each principle therefore states what Zemerc must do differently or deliberately give up.

  1. 01

    Independently operable

    Each application runs on its own, with its own users, data and release.

    So: No Zemerc application requires another product to be purchased first or to remain operational.

  2. 02

    Commercially standalone

    A customer can adopt one application for one team without committing to additional Zemerc products.

    So: Adopting another operating area is a commercial decision made when that team has its own requirement, not a technical dependency created by the first application.

  3. 03

    Connected where records relate

    Applications exchange records only where the underlying work genuinely connects.

    So: Readiness, barrier assurance and disclosure remain governed by their respective source records, with information exchanged only where the underlying work genuinely connects.

  4. 04

    Computed, not declared

    Statuses are read from the records rather than typed into a field.

    So: Where methods are defined, readiness, effectiveness and compliance are derived from governed evidence so discrepancies can be traced to the underlying record.

  5. 05

    Refusal is a feature

    Where evidence does not support a figure, the application does not produce one.

    So: Where no supportable index can be produced, the application reports that limitation rather than presenting an unsupported number.

  6. 06

    Claims follow evidence

    Public claims about an application are limited to capabilities that can be demonstrated.

    So: Mock-backed or unfinished capability is not described as live on the website or in demonstrations.

The trade

A single platform is a valid model. Zemerc has chosen a different one.

An integrated platform offers genuine advantages. This page sets out the trade-offs between that model and Zemerc's portfolio of independently operable applications.

The alternative

What a single platform gives you

  • One vendor relationship and one contract
  • Single sign-on and one administrative surface
  • Tighter integration because modules share one application and data model

Zemerc chooses the portfolio model because industrial records are governed by different disciplines, assurance rules and renewal cycles. Product depth is prioritised over forcing unrelated disciplines into one application.

What it comes back to

Eventually, the underlying record must withstand scrutiny.

When a figure is challenged by an auditor, regulator, partner or engineer, the decisive evidence is the governed record beneath it.

  • Readings, approved revisions and audit trails are immutable, so the original survives
  • Effective dating lets a closed period be re-run on the method that was in force then
  • Approval is segregated by identity so the record retains who authorised it
What follows

Three outcomes this philosophy makes possible.

  • A first adoption without portfolio lock-in

    One team can adopt one application and stop there if no further application is required.

  • Depth where the discipline needs it

    Each application can go as deep as its discipline requires without being constrained by a single shared product model.

  • Replace one application without a portfolio-wide programme

    Find an application can be replaced on its own. Nothing else in the portfolio stops working when it goes.

Adopt one application without committing to the rest of the portfolio.

This is a genuine operating model, not a trial constraint. A client may begin with the application that addresses the clearest current requirement.