Concept Design · Commercial building services

Turn commissioning records into a first service schedule

Transfer verified fire and HVAC assets into the maintenance system with certificates, service requirements and a named owner.

The operating problem

A fire and mechanical services contractor hands over a commercial building in stages. Commissioning certificates are attached to the project record, the asset list is exported separately, and the maintenance coordinator needs serviceable equipment in the job system before the first visit. A last-minute equipment substitution or a plantroom renamed in the drawings can leave the right certificate attached to the wrong asset. A project-level completion flag can also hide an unsigned asset in a stage the service team is already being asked to take over.

Workflow at a glance
  1. Source recordsInstalled asset register, commissioning evidence and maintenance contract scope
  2. ProcessingMatch asset identity, validate revisions and flag missing service inputs
  3. Decision ownerCommissioning lead corrects evidence and service owner accepts the asset
  4. Operational outputMaintenance system receives approved asset records and first service work

Implementation approach

Begin with one completed stage and one asset class. Map each project asset tag to the maintenance asset ID using the site, stage and verified physical location. Carry over the installed model, serial number when available, the current commissioning evidence and its revision, handover status and service-contract reference. Link to the approved schedule and service basis. Have the service owner confirm the first due window before creating planned work in the maintenance platform. Use native imports and APIs for data the two systems can already exchange.

What moves between project and service systems

The project platform keeps commissioning evidence and its revision history. The service platform owns maintenance assets, technicians and work orders. A staging register carries the matching key, the shared fields, who accepted them and the linked evidence. It also records imports and follow-up to support reconciliation when sites are handled in different stages.

If the service team already has a site asset register, match against it before creating anything new. Confirm floor, plantroom and access instructions with the site contact. Keep asset class and contract coverage distinct so a warranty check is assigned to the right person before dispatch.

Where people intervene

Flag an unsigned commissioning sheet, conflicting asset tag, missing service scope or proposed date outside an approved access window. The responsible person decides what evidence is needed and can annotate an accepted exception. Existing compliance and service obligations stay with the teams that approve them.

For a multi-site rollout, agree a shared asset data template and site-level variations. Put import access, queue ownership and failed-job notifications in the handover so a new site can use the same controls after delivery.

Exceptions and operating controls

Use a staging register with asset-level states for submitted, correction required, accepted and scheduled. Keep evidence review with the commissioning lead and maintenance acceptance with the service manager. If two assets match the same location or ID, send the record to review. Treat document revision and asset replacement as explicit changes with before-and-after values.

Illustrative operating scenario

During a staged handover, the maintenance sheet shows the design model for an air-handling unit. The installer fitted a different model and uploaded the updated test record. The record stays in review while the supervisor confirms the physical tag and replaces the outdated schedule entry. The service coordinator accepts the updated record and the contract-approved service window. The integration creates one planned visit, even when the corrected asset file is sent twice.

Acceptance test and handover

Compare a previous handover with the same asset class in a current stage. Count duplicate assets, missing or superseded documents, records accepted on the first submission, time spent preparing the service schedule and approved assets without a confirmed first visit. On rollout, verify that every planned job points to the correct asset, scope and approved timing. Track recurring rework by site or contractor to distinguish bad source data from mapping errors.

Reconcile the accepted staging register against the maintenance import. Test a split-stage handover, duplicate import, late certificate, substituted unit and changed access window. Provide the coordinator with an exception list, the source-evidence link, the import and rollback procedure, and a weekly check for accepted assets with no upcoming job. Retain approval records under the organisation’s access and retention policies.

Victorian School Building Authority · Building handover and commissioning

Country Fire Authority · Essential safety measures for businesses

Autodesk · D&E Air Conditioning project asset and commissioning workflow

Discuss a similar workflow More commercial building services cases