Skip to main content
Zemerc
CCMSDeliver · Completions, Quality & Handover

Completion, Commissioning & Handover Management System

Certificates are gates, not progress bars.

The completion and commissioning lifecycle is governed within one project record, covering systemisation, inspection and test records, punch control, certificate progression and the evidence required for handover.

Request a CCMS demoThe certificate sequence
0
Work areas
0
Controlled registers
0
Report definitions
0
Certificate types
The certificate sequence

A gate opens on completed deliverables, not on a number.

Six controlled certificate types in a sequence configured once per project and then locked. Whether mechanical completion or ready-for-pre-commissioning comes first is a project decision; that it cannot drift afterwards is not.

Systemisation
Engineering register
Inspection and test
Execution
Punch clearance
Punch list
Mechanical completion
Certificate workspace
Ready for commissioning
Commissioning
Handover
Certificates & handover

Systemisation. The plant is broken into systems and subsystems and every engineering item is registered against one. Nothing is counted as complete before there is something definite to complete.

Inside CCMS

Every plant object registered, and every template that governs it.

Open a system and the application shows its place in the plant hierarchy, the controlled certificate templates that apply to it, and the inspection and test record categories and punch items that stand between it and its next gate.

The CCMS systems register with a system open beside it: the plant hierarchy from area through system to subsystem, the controlled certificate templates that apply to it, and the completion modules showing inspection and test record categories and punch items

Completion is shown as records reached against records required, so the figure can always be taken apart.

  • Traceable to the revision
    An executed record keeps the exact template revision it was signed against, however long ago that was.
  • Category A blocks the gate
    Punch is counted by category against the system it belongs to, not aggregated into a single cleared percentage.
  • Dual-party signature
    Contractor and client signatories are recorded on the certificate itself, with the approval parties behind them.
From systemisation to handover

The population narrows at every gate.

Each stage reduces what is outstanding, and every reduction is evidenced by a record that a named person signed. Nothing advances because a date arrived.

SystemisationEngineering register

The plant is broken into systems and subsystems and every engineering item is registered against one. Nothing is counted as complete before there is something definite to complete.

Inspection and testExecution

Category A, B and C inspection and test records are executed against approved template revisions, with check sheets, loop checks and test packs behind them.

Punch clearancePunch list

Punch items are raised and cleared by category. Category A must clear before the gate it blocks, and the count is carried against the system rather than aggregated away.

Mechanical completionCertificate workspace

The first certificate gate. It is issued against completed deliverables, and the sequence can be configured so that ready-for-pre-commissioning comes first instead.

Ready for commissioningCommissioning

Commissioning proceeds on the systems whose evidence supports it, through site acceptance testing and start-up.

HandoverCertificates & handover

Pre-start-up safety review, ready for start-up and the final handover certificate, with turnover packages and dossiers assembled from the records that produced them.

Capability architecture

Fourteen work areas, one engineering register beneath them.

The application's own sidebar, grouped the way a completions team works. Every chip is a page.

  • Systemisation

    The engineering register is the single source of truth. Plant, area, system, subsystem, package, equipment and tag, with the line, valve, instrument, cable and loop lists that hang beneath them.

    • Areas
    • Systems
    • Subsystems
    • Packages
    • Equipment
    • Tags
    • Line Lists
    • Loops
    • Engineering Register

  • Controlled templates

    Inspection and test records, check sheets and certificate templates live in an approved library with revision management, so an executed record can always be read back against the exact revision it was signed against.

    • Template Library
    • Approval Workspace
    • Revision Management

  • Execution

    Inspection and test records in categories A, B and C, check sheets, loop checks, test packs and the punch list, through pre-commissioning, commissioning, site acceptance testing, start-up and performance tests.

    • ITRs
    • Check Sheets
    • Loop Checks
    • Test Packs
    • Punch List
    • Precommissioning
    • Commissioning
    • Site Acceptance Tests
    • Startup
    • Performance Tests

  • Certificates and handover

    A configurable, lockable certificate sequence with dual-party signatures, then phase and area handover certificates, turnover packages and the event matrix behind them.

    • Certificate Workspace
    • Stage Sequence
    • Phase Handover
    • Area Handover
    • Turnover Packages
    • Event Matrix

  • Deliverables and spares

    Documents, drawings, single-line diagrams, piping and instrumentation diagrams, isometrics, vendor documents, calibration certificates, inspection and test plans and as-builts, with spares and interchangeability records beside them.

    • Documents
    • Drawings
    • SLDs
    • P&IDs
    • Isometrics
    • Vendor Docs
    • Calibration Certificates
    • ITPs
    • As-Builts
    • Spares & SPIRs

  • Quality and knowledge

    Technical queries, non-conformance reports, management of change and lessons learned, with preservation, the knowledge platform and the data management workspace supporting them.

    • Technical Queries
    • NCRs
    • Management of Change
    • Lessons Learned
    • Preservation
    • Knowledge Platform
    • Data Management
The systemisation spine

Twenty thousand objects, and each one knows its templates.

Lines, valves, instruments, cables and loops all live in one register with their discipline, system, subsystem and area. Select any of them and the applicable controlled templates are listed by inspection and test record category, with what is already in project and at which revision.

  • Plant, area, system, subsystem, package, equipment and tag in one hierarchy
  • Register-backed traceability from any row
  • Temporary systems held distinctly from permanent ones
Who signs

The person who signs is the person who checked.

Commissioning engineers, inspectors and both parties' signatories work the same records. A certificate carries the people who executed it and the people who approved it, and it stays readable against the template revision in force on the day.

  • Project tiers for general user, super user and administrator
  • Execution signatories and approval parties recorded on the certificate
  • Barcode and QR scanning so records are raised where the equipment is
Progress and reporting

Now the percentage means something, because it is derived.

Overall progress, mechanical completion, commissioned equipment, punch clearance and certificate approval are calculated from the underlying records, with planned and actual positions visible together.

CCMS progress: overall progress with mechanical completion, commissioned equipment, punch cleared, inspection and test records completed and certificates approved, the planned-against-actual schedule curve, and progress by discipline, by system and by subsystem

  • Deliverable-driven, never percentage-driven

    A certificate is issued against completed deliverables. A percentage is something the application derives afterwards for reporting; it is never what opens a gate.

  • Signed against a revision

    An executed record keeps the exact template revision it was signed against, so a record executed two years ago can still be read against the rules that applied then.

  • Dual-party signature

    Certificates carry both contractor and client signatories, with the execution signatories and approval parties recorded against the certificate itself.

  • The sequence locks per project

    Whether mechanical completion or ready-for-pre-commissioning comes first is configured once and then locked, so the gate order cannot drift mid-project.

Also in CCMS

More of what the application covers.

  • Visual tracker and facility three-dimensional view
  • Schedule curve of planned against actual
  • Barcode and QR scanning on site
  • Print and document packs
  • Guided imports and a migration workspace
  • Preservation registers with due dates
  • Eighty-nine governed report definitions
  • Tenant administration with project tiers
Works alongside

Completion and handover, beside the registers they draw on.

Completions solutions
CCMS

See CCMS with one of your systems on screen.

Bring one system and its inspection and test records. We will walk it from systemisation through punch clearance to the certificate gate, with the template revision each record was signed against.

Request a CCMS demoCompletions solutions