Skip to main content
Zemerc
Resources · application guides

One guide per application, written from the interface up.

Each guide says what the application governs, the governed flow it runs on, and shows the application’s own screens rather than an illustration of them.

What you are opening

Four things every guide has to answer.

Including the last one, which is usually the fastest way to judge whether an application is honest about its own limits.

  • What it governs

    The class of record the application owns end to end, and the part of the operation that keeps it.

  • The flow it runs on

    The governed sequence the application actually enforces, stage by stage, in the application’s own terms.

  • The interface itself

    The application’s own screens, shown complete and at their own proportions rather than illustrated.

  • What it will not do

    The figures it declines to compute and the claims it does not make; stated as plainly as the capabilities.

A guide, opened

CCMS: Completion, Commissioning & Handover Management System

ITRs, punch lists, certificate sequence and turnover packages.

ITRPunch listCertificate chainTurnover package
The CCMS visual tracker: every facility in the programme with its ready-for-commissioning, ready-for-start-up and handover position shown as completed against total rather than as a percentage alone, with its areas, category-A punch count and open punches

Every facility in the programme with its readiness position shown as completed against total rather than as a percentage alone, with its areas and open punch.

All the guides

27 applications, grouped by the stage they serve.

Four stages of an industrial operation, eight operating areas, and one guide for every application inside them.

Deliver
How to read one

Start at what it will not tell you.

Every guide states the figures its application declines to compute and the claims it does not make. On industrial software that section is more informative than the capability list, because it is the part nobody writes unless it is true.

  • The governed flow is the application’s own, not a generic lifecycle
  • Screens are shown complete, at the application’s own proportions
  • Where a capability is not yet real, it is not described as live

Read a guide, then see it running.

The guides show the interface. A working session shows it against your own register, which is the part that settles anything.