Gateway 3 forces the industry to turn a messy pile of PDFs into a working digital asset that facilities teams can trust on day one. Programme pressure, late design changes and commissioning squeeze make that hard. The answer is not more binders—it’s a clear playbook that ties the O&M deliverable to the golden thread using tech the site can actually operate.
TL;DR
/>
– Lock down Asset Information Requirements and Exchange Information Requirements early, including classifications and COBie fields.
– Set up a Common Data Environment with an asset register workflow, mobile field capture and approval gates.
– Tag maintainable assets as they’re installed; scan serials and link photos, test packs and warranties to each record.
– Validate data against agreed schemas and assemble digital O&M, H&S and fire information with traceable approvals.
– Prove the export into the client’s CAFM/IWMS before completion so the transfer isn’t a mad scramble.
Gateway 3 playbook: essential O&M tech that actually delivers
# Stage 1: Set the information rules and choose tools
/> Before the first procurement package lands, agree the Asset Information Requirements (AIR) and Exchange Information Requirements (EIR) with the client and FM team. Define the classification system (typically Uniclass 2015), asset breakdown structure, and what “maintainable” means by discipline. Map the required fields for each asset type—location, tag, model ID, manufacturer, serial, spares, warranty, commissioning results, and PPM hints—against a schema such as COBie or equivalent. Select a Common Data Environment (CDE) that supports structured asset data, controlled workflows, and model/document linkage in line with BS EN ISO 19650. Publish a single BIM Execution Plan and Responsibility Matrix that pins tasks on named roles: design team, MEP subcontractors, commissioning specialists, and the principal contractor.
# Stage 2: Build the asset register early
/> Don’t wait for practical completion to think about O&M. Seed the asset register at Stage 4–5 using design schedules and model properties, flagging which items will become maintainable assets. Create templated forms and data capture checklists per asset family in the CDE so installers know exactly what to collect. Plan physical identification: durable QR tags or engraved labels, placed where FM can actually find them. Confirm zone and room coding matches the drawings and fire strategy. Train package managers and supervisors so the register becomes part of normal progress tracking, not an extra chore.
# Stage 3: Capture installation data in the field
/> Use mobile apps to attach photos, serial numbers and method statements to each tagged asset as it goes in. Link 360 imagery or point cloud scans to areas with congested MEP so maintainers can “see behind” finishes later. Record product submittal approvals and deviations directly against the asset record so there’s one source of truth. If a substitution is agreed on a Friday afternoon, flag it in the register and push the change downstream to commissioning sheets and O&M templates. Push incomplete fields back to the installing subcontractor with a clear due date, not a generic email blast.
# Stage 4: Link commissioning, tests and approvals
/> Commissioning programmes rarely survive contact with reality, so the tech has to keep pace. Capture functional test results, balancing logs, BMS trend snapshots and witness sign-offs as structured attachments against each system and asset. Use digital sign-off workflows for hold points, with the commissioning manager and client’s representative in the loop. Validate COBie or equivalent exports weekly against naming, classifications and mandatory fields so surprises are found early. Store certificates (pressure tests, fire stopping, LEV, lift inspections) in the CDE and reference them in the Health & Safety File and asset records.
# Stage 5: Assemble O&M, H&S and fire information for transfer
/> Build the O&M deliverable as a live package, not a month-end panic. Pull manufacturer manuals, spares lists and training videos into the CDE and link them to assets and systems. Collate the Health & Safety File and, where required for higher-risk residential buildings, ensure fire safety information is coherent and consistent with the as-built model and drawings. Keep version histories—clients increasingly expect to see who approved what and when. Produce a human-readable index alongside the data drops so FM teams know where to start on day one.
# Stage 6: Prove the handover and embed the golden thread
/> Before completion, run a witnessed rehearsal: export the asset data and documents in the formats the client’s CAFM/IWMS requires and load a sample. Fix mapping issues then, not in the week you’re chasing the certificate of completion. Agree how post-completion changes will be captured—small works, warranty swaps, seasonal commissioning—and keep the CDE open for a soft landings period. Hand over credentials, folder structures, tag registers and naming conventions so operations can maintain the thread without guesswork. Record training sessions and store them against relevant systems; day-two teams change.
On a South Coast hospital refurbishment, the principal contractor hit a three-week weather delay that pushed commissioning into a narrow window before winter pressures. The MEP contractor had swapped two fan coil models due to supply lead-ins, and the FM lead wanted full serial and warranty records before taking on risk. The site team used QR tags on plant and scanned each as it was hung, attaching installation photos and datasheets on a tablet. When commissioning started, test packs and BMS trend screenshots were linked straight to the affected systems. A dry-run export into the Trust’s CAFM flagged that room codes didn’t match estates’ conventions; the team fixed the mapping in two days rather than two months. At Gateway 3, the digital O&M, H&S File and fire safety information were already aligned, and the client acceptance session took hours, not weeks.
# Gateway 3 digital handover checklist
/>
– Confirm AIR/EIR, classifications and asset types with the client/FM team and record acceptance in the CDE.
– Configure the asset register, mobile forms and approval workflows; brief all package managers and key subcontractors.
– Issue QR/label standards and zone/room coding; start tagging maintainable assets at first fix.
– Capture serials, commissioning data, and certificates against asset records; require digital signatures for hold points.
– Validate COBie or equivalent exports weekly; correct naming, location and mandatory fields as part of progress control.
– Assemble O&M, H&S and fire safety content continuously; maintain a clear index and version control.
– Rehearse the export into the client’s CAFM/IWMS and close mapping gaps prior to completion.
# Common mistakes
/>
– Treating O&M as a document dump at PC. Without structured asset data, FM teams can’t run PPM or locate plant efficiently.
– Leaving asset tagging to the end. Retrofitting labels behind ceilings or in risers wastes time and misses items.
– Ignoring the client’s CAFM format until handover. Mismatched fields and codes lead to rework just when you need sign-off.
– Allowing uncontrolled substitutions. If product swaps aren’t reflected in the register and manuals, warranties and spares become guesswork.
Get the information rules straight, tie them to workflows the site can actually use, and prove the export before the certificate is in sight. The projects worth watching next are those aligning reality capture with live asset registers and building FM-ready twins, not just pretty models.
FAQ
# What asset data fields do clients usually expect at Gateway 3?
/> Most UK clients want a consistent set covering location, classification, unique tag, manufacturer details, serial numbers, warranty terms, spares, and commissioning outcomes. Many will also ask for links to O&M manuals, drawings and test certificates. Agree the exact fields against the AIR/EIR early and map them to COBie or an equivalent structure.
# How do we get subcontractors to contribute quality data?
/> Bake data capture into each package’s scope and payment schedule, and provide simple mobile forms tied to the CDE. Show installers how the asset tag and form relate to their test packs and sign-offs, so it feels part of completion, not admin. Escalate missing fields through the commercial route, not just email reminders.
# Do we need a full BIM model to deliver a digital O&M?
/> A well-structured model helps, but it’s not the only route. You can build a robust asset register from schedules and field capture, provided classification, locations and tags are consistent. The key is coherence between drawings, registers and documents so operations can trust the data.
# How should we handle changes after handover?
/> Agree a post-completion change process with the client, covering small works, warranty replacements and seasonal commissioning. Keep the CDE accessible during soft landings and use the same tagging and naming rules so updates don’t break the golden thread. Log revisions with dates and approvers so there’s traceability for safety and maintenance.
# What’s the best way to integrate with a client’s CAFM?
/> Get the CAFM export templates and field dictionaries at the start and test a small data drop mid-project. Use mapping tables to align your codes with theirs and fix differences before completion. If the client doesn’t yet have a CAFM, provide open, portable formats and a clear index so they can onboard later without rework.
