Skip to content
Use case 12 · Testing & Commissioning

Fire system testing and commissioning assistant

A workflow that selects the test procedures, captures field results and photos, checks results against thresholds, manages defects and retests, and records witness approval. Handover evidence is assembled as the work happens rather than reconstructed afterwards.

Get the requirements document See the flow
Runs standaloneUploads and manual entryWitness signs
Workflow 12 · demo runAwaiting sign-off

Commissioning engineerField tests and their supporting evidence end up spread across forms, photos and phones.

  1. Select proceduresEngineer
    QueuedWorkingDoneSign-off
  2. Capture field resultsEngineer
    QueuedWorkingDoneSign-off
  3. Check thresholdsAutomated
    QueuedWorkingDoneSign-off
  4. Manage defects and retestsEngineer
    QueuedWorkingDoneSign-off
  5. Record witness approvalWitness
    QueuedWorkingDoneSign-off
Stopped for the witness to sign
  • Who uses itCommissioning engineer, witness, project manager
  • Lifecycle stageTesting & Commissioning
  • Buyer groupTrack D · Commissioning & Service
  • RequirementsBRD v0.1, sent as written
At a glance

What goes in, what comes out

Goes in
Test procedures
Installed systems
Readings and photos
Testing & Commissioning AssistantFive steps · one approval gate Witness signs
Comes out
Test sheets
Deficiency log
Retest trail
Signed report
What it does

Testing & Commissioning Assistant, step by step

Five steps, one decision point. The last step is a person, every time.

  1. 01
    Engineer

    Select procedures

    The right test sheets for the systems actually installed.

  2. 02
    Engineer

    Capture field results

    Readings and photographic evidence recorded where the test happens.

  3. 03
    Automated

    Check thresholds

    Results measured against the acceptance criteria, with failures raised immediately.

    Result within the threshold?

    Yes Test passedNo Defect raised, retest scheduled
  4. 04
    Engineer

    Manage defects and retests

    Each defect tracked to closure with its retest evidence attached.

  5. 05
    Witness

    Record witness approval

    A record without a witness signature stays pending. It does not quietly pass.

  6. Output

    What lands at the end

    Test sheets, a deficiency log, the retest trail, a signed commissioning report and a handover evidence manifest.

Who’s involved

Commissioning engineerWitnessProject manager

What you get

  • Test sheets
  • Deficiency log
  • Retest trail
  • Signed report

In the wireframe

A required witness signature is missing, so the record stays pending until captured, then joins a controlled commissioning report.

Use case diagram

Who does what, and who signs

Automated steps prepare the evidence. People make the calls.

Swipe to see the whole diagram

Use case diagram: Testing & Commissioning Assistant People: Commissioning engineer, Witness, Project manager. Steps: 1 Select procedures; 2 Capture field results; 3 Check thresholds; 4 Manage defects and retests; 5 Record witness approval. Witness approves the final step. Testing & Commissioning Assistant«workflow, built with DeX»«inputs»01 Select procedures02 Capture field results03 Check thresholds04 Manage defects and retests05 Record witness approvalCommissioning engineerProject managerWitness«approves»«documents»Test procedures, …
Automated step Done by a person Approval gate Takes part Leads to
What changes

Why this costs you time today

Field tests and their supporting evidence end up spread across forms, photos and phones. Proving at handover that every test was witnessed and every defect closed becomes its own small project.

Task
Today
With this workflow
Evidence
Spread across forms, photos and phones
Captured against the test, on site
Witnessing
Chased at handover
Pending until the witness signs
The handover pack
Its own small project
A manifest built as work happens
The line we do not cross

What this software will not do

Life-safety work. These limits are written into the requirements, not added as a disclaimer.

Specific to this workflow

It does not certify a system or issue a completion certificate on anyone's behalf. It records what was tested, what failed, what was retested and who witnessed it.

It does not decide compliance

The software assembles evidence, retrieves source clauses and shows conflicts. It does not determine whether anything complies. A named engineer does.

It does not stand in for an authority

An approval recorded in the software never implies consent from an AHJ, Civil Defence, building control or a building surveyor.

Nothing leaves without a named reviewer

Every output carries who approved it. Anything unverified keeps a draft marker until someone signs it.

It does not do sealed engineering

Hydraulic network calculation, definitive sprinkler layout, sealed design, BIM geometry authoring and final cost estimates are all out of scope by design.

Your standards, not ours

NFPA, EN, BS, ISO, FM, UL, LPCB and Civil Defence appear in the requirements as examples. None is assumed to apply to your projects until you say so.

~1/10of traditional build time
~30%of traditional cost

That is a claim about how fast Colakin builds software with DeX, and it is supported by delivered projects. It is not a claim about what any of these fifteen workflows will save your business. The requirements deliberately leave that to a pilot, measured against your own baseline.

How an engagement runs

From a question to a pilot, in five steps

Nothing hidden behind a discovery call. Stop at step one and keep the document.

  1. 01

    You ask for the requirements document

    The full BRD for the workflow you care about, sent as written.

    Same day
  2. 02

    A ten-minute wireframe walkthrough

    A clickable prototype of that one workflow.

    10 minutes
  3. 03

    The Fire Fit Check

    Five questions: fit, hours lost, who approves spend, whether your documents can be shared, and timing.

    One call
  4. 04

    A scope built on your rules

    Your standards, your document formats, your approval gates.

    Within a week
  5. 05

    A pilot against your own baseline

    One workflow, your data, your engineers.

    Q1
Same buyer, same week

Also in Commissioning & Service

Each one stands alone. Take one first, then decide whether a second earns its place.

13 · Commissioning & Service

Site Inspection & Maintenance

The client report comes from the record the technician signed.

Signed inspection recordPhoto evidenceCorrective actions
Open the workflow
14 · Commissioning & Service

Digital Asset & Maintenance History

One device, one timeline, a source behind every entry.

Lifecycle timelineCertificate registerMaintenance plan
Open the workflow

All fifteen workflows

Questions

Testing & Commissioning Assistant: questions

What happens if a witness signature is missing?
The record stays pending. It cannot be counted as complete, which is the whole point — a commissioning report assembled from pending records is worth nothing at handover.
Does it work offline on site?
Field capture is specified for site conditions. What that means in practice for your sites is confirmed during scoping rather than promised here.
How are defects closed out?
Each defect carries its retest and the evidence for it. The trail from failure to closure stays attached to the test it came from.
Can we hand the evidence pack straight to the client?
The evidence manifest is built for that. What the client will accept is a matter for your contract, not for the software.
Next step

Ask for the Testing & Commissioning Assistant requirements document

The business requirements document as written, including what it refuses to do. No brochure, no drip sequence.

  • The requirements document, usually the same working day
  • A ten-minute wireframe walkthrough with the people who specified it
  • No claimed percentage saving — your pilot measures it

Request the document

One working day. A person replies, not a sequence.

We use this to reply, nothing else. No list, no newsletter.