Skip to main content
Zemerc
Resources · application guides

One guide per application, written from the governed record and workflow outward.

Each guide explains what the application governs, the workflow it follows and representative screens from the application itself.

What each guide contains

Four questions every guide should answer.

Defined product limits are often one of the quickest ways to assess whether an application fits the requirement.

  • The record it governs

    The class of record the application governs and the team responsible for it.

  • The governed workflow

    The sequence of governed states and actions the application supports, stated in its own terminology.

  • Representative application screens

    Representative application screens are shown directly rather than replaced with conceptual illustrations.

  • What it deliberately does not do

    The figures it deliberately does not compute and the product claims it does not make.

Guide structure

CCMS: Completion, Commissioning & Handover Management System

Inspection and test records, punch lists, certificate sequence and turnover packages.

ITRPunch listCertificate chainTurnover package
CCMS visual tracker showing facilities with ready-for-commissioning, ready-for-start-up and handover positions as completed against total, together with areas, Category A punch items and open punches

Readiness shown as completed records against required records, with supporting areas and open punch visible

All application guides

27 applications, grouped by broad operating stage.

Four broad operating stages, eight operating areas and one guide for each application.

Deliver
How to read a guide

Start with the application's defined limits.

Each guide states important calculation and product boundaries alongside supported capability so users can understand what the application does not claim.

  • The governed workflow is specific to the application rather than a generic lifecycle.
  • Representative screens are shown at proportions that preserve their application context
  • Capability that is unfinished or mock-backed is not described as live

Read a guide, then see the application demonstrated.

Guides explain the product. A working session shows how it behaves against representative client records.