Glossary of Construction Handover & Asset Information Terms

Definition. ERIK is the Australian Department of Defence’s online portal for the estate works program, and the renamed successor to DEQMS (the Defence Estate Quality Management System). It publishes the mandatory documentation, inspection regimes and acceptance criteria for every contractor working on Defence land, and hosts the Data Supplier Toolkit under the Estate Resources & Data banner.

Origin and governance. Owned by the Defence Estate & Infrastructure Group. Aligned with ISO 9001:2015 principles but extends them with Defence-specific templates and contract requirements. Currently transitioning under the ERIK transition programme published on defence.gov.au.

Usage in practice. A Managing Contractor on a Capital Facilities Infrastructure project must develop an ERIK-compliant Quality Management Plan at mobilisation, execute Inspection and Test Plans aligned to ERIK templates and submit a HOTO Evidence Folder demonstrating compliance at Practical Completion. Subcontractors inherit ERIK obligations through contract flow-down clauses, usually without being briefed on what ERIK actually requires, which is the leading cause of last-minute compliance scrambles.

Used by. Department of Defence, Managing Contractors, Head Contractors, subcontractors, EMOS contractors, Consultant HOTO reviewers.

See full guide: ERIK Explained.
See also: HOTO, EMOS, QMP, SoFC.

Definition. EMOS is the Department of Defence’s contracting framework for outsourcing day-to-day facility management of the Defence estate. EMOS prime contracts cover routine maintenance, asset operations, condition assessments and lifecycle planning across every base, depot and training area.

Origin and governance. Operates under the Property & Asset Services (PAS) framework, which sits inside the Suite of Facilities Contracts (SoFC). Procured through Commonwealth Procurement Rules. Current prime contracts (as of 2026) are held by Downer Group (East Coast, $3.05 billion over 7 years), Ventia, BGIS, Serco and Cushman & Wakefield in various regions and categories.

Usage in practice. A subcontractor performing electrical works on an Army base typically works under flow-down terms from an EMOS prime contractor. The EMOS contractor’s CMMS becomes the immediate destination for the subcontractor’s asset records, work-order completions and warranty data. Defence assets are operated under EMOS contracts for 5-7 years per contract cycle.

Used by. Department of Defence, prime EMOS contractors (Downer, Ventia, BGIS, Serco, Cushman & Wakefield), thousands of trade subcontractors.

See full guide: EMOS Defence Explained.
See also: ERIK, PAS, SoFC, DAMIS.

Definition. HOTO is the Australian Department of Defence’s process for transferring a completed construction project from the contractor to Defence and its EMOS facility-management contractor. It defines the evidence required before Defence accepts an asset and begins operating it.

Origin and governance. A core deliverable inside ERIK. The HOTO Evidence Folder template has evolved through versions v5.5, v6.1, v6.3 (with Planning & Development and Construction as separate templates), v7.1 and v7.3 (current as of mid-2026).

Usage in practice. HOTO is the leading cause of late practical-completion certifications on Defence construction projects. The HOTO Checklist v7.3 (3503_HOTOPLANCHECKLIST_V7.3.xlsx) defines several dozen evidence items across mechanical, electrical, hydraulic, fire, security and project-management disciplines. The Managing Contractor coordinates collection; subcontractors provide discipline-specific evidence; the Consultant HOTO reviews; Defence accepts.

Used by. Every party touching a Defence construction project.

See full guide: The HOTO Process for Australian Defence Construction.
See also: ERIK, Practical Completion, HOTO Evidence Folder, Consultant HOTO.

Definition. The DLP is the contractually-defined period after Practical Completion during which the installing contractor remains responsible for rectifying defects in their work. On Australian Defence projects DLP typically runs 12 or 24 months depending on contract terms.

Origin and governance. Defined by the Head Contract or Subcontract. Begins when Defence accepts the HOTO Evidence Folder and certifies Practical Completion. Ends at Final Completion when all defects are rectified and the warranty period transitions to the EMOS contractor’s responsibility.

Usage in practice. During DLP, defects identified by the EMOS contractor, the Defence estate team or end-users (tenant units) are reported back to the original installing contractor for rectification. Categorisation typically follows: client-raised, builder-raised, trade-raised or tenant-raised; with importance levels low/medium/high/urgent. The original Contractor remains liable for warranty work and must respond within contracted timeframes. Failure to rectify can trigger withholdings or contract claims.

Used by. Original contractors, subcontractors, EMOS contractors, tenant units, Defence estate teams.

See related service: DLP Maintenance Services.
See also: Practical Completion, Final Completion, EMOS.

Definition. An O&M Manual is the consolidated document set that describes how to operate, maintain and replace components of a completed construction asset. On Defence projects, the O&MM is a structured deliverable inside the broader HOTO Evidence Folder, not a synonym for HOTO.

Origin and governance. Defence specifies O&MM structure through the OMM Submission Engineering Guide (SEG). The current SEG (v2.0) defines structure, content requirements, file naming conventions and submission format including the §40-42 requirement that exports over 200 MB be split into clearly labelled volumes.

Usage in practice. A typical Defence O&MM contains as-built drawings, manufacturer technical literature, commissioning records, maintenance schedules, warranty certificates, spare parts lists, training records and asset registers aligned to DAMIS. It is rejected at HOTO if structure doesn’t match the Defence template, even if content is technically complete. Procom’s platform pre-configures the OMM structure to match SEG v2.0 and auto-splits exports per §40-42.

Used by. Contractors, subcontractors, Consultant HOTO, EMOS contractors, Defence.

See full guide: Operations & Maintenance Manuals.
See related: HOTO Evidence Folder, OMM Buildings v1.2, OMM Base Infrastructure v1.2.
See also: HOTO, ERIK, DAMIS.

Organising, storing and controlling project and asset data in digital formats across the construction or asset lifecycle. Ensures consistent document control, real-time access and data quality. Procom’s approach uses structured workflows and a cloud platform to manage drawings, specifications, compliance records and manuals in one place, replacing email chains and shared drives. See full guide: Digital Data Management. See also: Handover Manual, O&MM.

A comprehensive handover manual (or project close-out package) contains all critical information needed at practical completion: as-built drawings, certifications, warranties, system descriptions and maintenance information. Procom compiles and structures this data to facilitate a seamless project handover to owners or facility managers. See full guide: Handover Manuals. See also: Practical Completion, As-Built Drawings, HOTO.

A fire compliance manual (or fire safety manual) consolidates all fire protection system information and statutory documentation: fire alarm and suppression system descriptions, inspection records, maintenance logs and emergency procedures. It ensures ongoing adherence to fire safety regulations and simplifies audits and annual statements. See full guide: Fire Compliance Manuals. See also: Building User Guide, O&MM.

A building user guide is a non-technical reference for occupants and facility staff. It explains key building systems (HVAC, lighting, security), energy features and user responsibilities in plain language, so people understand how to use the building and report issues. Unlike an O&M manual, it is written for everyday users, not technicians. See full guide: Building User Guides. See also: O&MM, Training Guide.

Training guides are targeted manuals, videos or presentations for site teams and operators, covering specific equipment or operational procedures (commissioning, emergency systems, ICT). Used at handover and beyond, they help staff become familiar with the asset and protect against knowledge loss as personnel change over the facility’s life. See related: Platform features. See also: Building User Guide, Handover Manual.

The practice of tracking and resolving defects during the contract’s defect liability period (typically 6–24 months post-completion). A structured DLP process ensures issues are recorded, communicated to contractors and closed out efficiently. Procom’s system automates defect reporting and follow-up, improving accountability and project close-out. See full guide: DLP Management. See also: DLP (the period itself), Final Completion.

The planning and administration of asset upkeep, both preventive and corrective. It ensures regular inspections, servicing and repairs are scheduled and documented, extending asset life and reliability. Procom links maintenance schedules and manuals so facility teams have all necessary maintenance data in one system. See full guide: Maintenance Management. See also: O&MM, DLP Management.

Collecting and maintaining asset information for government portfolios: federal and state buildings and the Defence estate. Includes property registers, compliance records and lifecycle documents. Procom provides structured templates for digital handover (OMM, HOTO, GDL) and ongoing data governance to meet public-sector requirements. See full guide: Government Estate Data Management. See also: HOTO, GDL, DAMIS.

The Defence OMM template for building projects (offices, accommodation, training facilities, hospitals). Defines structure for documenting building services (mechanical, electrical, hydraulic, fire, security, building fabric) in a consistent Defence-acceptable format. Version 1.2 is current as of mid-2026. Procom’s platform pre-configures the structure including discipline tree, asset register schema and warranty register fields. See also: O&MM, OMM Base Infrastructure v1.2.

The Defence OMM template for base infrastructure projects: roads, hardstands, drainage, fuel installations, training ranges. Has a different structural emphasis than OMM Buildings: more weight on civil works, environmental compliance and bulk asset registers. Version 1.2 current. See also: O&MM, OMM Buildings v1.2.

The structured collection of evidence proving a Defence construction project is ready for handover. Template versions in circulation: v5.5, v6.1, v6.3 (with separate Planning & Development and Construction phase templates), v7.1 and v7.3 (most current). The version specified in the Head Contract is the version that applies. Never assume the latest one. See also: HOTO, HOTO process guide.

A general-purpose Defence template used when a project doesn’t fit the Buildings or Base Infrastructure categories cleanly. Provides a structured framework for gathering and submitting project information without the strict OMM template constraints. Less common than OMM Buildings or OMM Base Infrastructure but still in active use on hybrid projects. See also: O&MM, HOTO Evidence Folder.

The Department of Defence’s central asset management system. Holds the master record of every operational asset on the Defence estate. Asset records produced during construction must be DAMIS-compatible (using DAMIS-aligned identifiers, attributes and metadata) to be accepted at HOTO and operated by EMOS contractors. Used by. Defence estate teams, EMOS contractors (consuming asset records), Contractors (producing records). See also: HOTO, EMOS, O&MM.

Defence’s library of contract templates governing construction, maintenance and FM work on the Defence estate. Includes Managing Contractor Contract templates, Head Contract templates and subcontract flow-down clauses. ERIK quality requirements are embedded in the SoFC contract suite. Used by. Defence procurement, Contractors at tender, legal teams. See also: ERIK, PAS.

The contract programme under which EMOS prime contracts sit. Defines the broader Defence FM commercial framework: scope of services, pricing models, performance regimes, KPI structures. EMOS is the operational layer; PAS is the commercial framework. Used by. Defence procurement, EMOS prime contractors, subcontractors under EMOS primes. See also: EMOS, SoFC.

A term used in some Defence contexts (and by Oracle Aconex) to describe digital O&M manuals with interactive features: searchable, hyperlinked, with embedded asset data. Distinct from a flat PDF manual. Defence is moving toward Smart Manual-style outputs as part of the ERIK transition; the OMM SEG v2.0 already permits structured electronic deliverables. See also: O&MM, ERIK.

The Defence guide defining O&M Manual submission structure, content requirements, file naming conventions and submission format. The current SEG (v2.0) includes the §40-42 requirement that exports over 200 MB be split into clearly labelled volumes. See also: O&MM, EBI.

A Defence-specific project or asset identifier used in file naming and asset register entries. OMM export ZIPs are typically named {EBI}_OMM_{Name}_Volume{n}.zip per the SEG v2.0 convention. The EBI is assigned by Defence at project initiation and remains stable through the asset’s lifecycle. Used by. Defence estate teams, Contractors (file naming compliance). See also: O&MM.

A document defining what inspections and tests will be performed during construction, who performs them, at what hold or witness points and what evidence is recorded. ITPs are mandatory under ERIK for every work package. Subcontractors typically have one ITP per discipline; Managing Contractors integrate them into the overall QMP. Used by. Quality Managers, subcontractor QA leads, Consultant HOTO reviewers. See also: QMP, ERIK, NCR.

A formal record raised when work does not meet specification or contract requirement. Defines the non-conformance, the corrective action and the verification evidence proving the issue is resolved. NCRs are closed before HOTO acceptance; open NCRs at HOTO trigger acceptance delays. Used by. Quality Managers, subcontractors, Defence reviewers. See also: ITP, QMP, HOTO.

The project-level quality plan submitted by a Managing Contractor at mobilisation. Defines roles, document control procedures, audit programme, ITP framework, NCR handling and HOTO development plan. Must be ERIK-compliant. The single document Defence reviews first to assess whether a Contractor has the quality maturity to deliver. Used by. Quality Managers, Defence project teams, Consultant HOTO. See also: ERIK, ITP, NCR.

Drawings updated to reflect the asset as actually constructed, including all variations from the original design intent. Distinct from “as-designed” drawings. Required as a HOTO deliverable in both PDF and native CAD/Revit formats. The single most common HOTO inconsistency: as-built drawings that contradict closed NCRs. Used by. Subcontractors (producing), Contractors (integrating), EMOS contractors (consuming long-term). See also: NCR, O&MM.

A nominated reviewer role on Defence projects using the four-tier approval workflow. Reviews and approves the HOTO Evidence Folder content before submission to Defence. Sits between the Contractor’s quality team and Defence-side acceptance, in the internal-review tier ahead of final client sign-off. Used by. Managing Contractor (typically appoints), Defence (approves the nomination). See also: HOTO, SME, ERIK.

A specialist reviewer with domain expertise, typically engaged for technical content review on disciplines like fire systems, security systems or specialist Defence equipment. Has approval authority on the manual nodes assigned to their discipline. Used in the dual-approval variants of the manual workflow. Used by. Managing Contractor (engages), Consultant HOTO (coordinates with). See also: Consultant HOTO, HOTO.

A trade or specialist contractor working under a Managing Contractor or Head Contractor on a Defence project. Subcontractors inherit ERIK quality obligations through contract flow-down and produce discipline-specific content for the HOTO Evidence Folder. Most HOTO acceptance rejections trace back to subcontractor submissions that don’t match the Defence template structure. Used by. Managing Contractors, Head Contractors. See also: HOTO, ERIK.

A representative role for end-users or tenant units on a Defence project. PPS stands for “Plan, Procurement and Sustainment” in some Defence contexts. EMOS/PPS representatives have viewing access during HOTO and the DLP; they raise defects and feedback but do not approve content. Used by. Defence (assigning), Contractors (coordinating with). See also: EMOS, DLP.

The contractual milestone when a construction project is substantially complete and ready for occupation, subject only to minor defects. On Defence projects, Practical Completion is contingent on HOTO Evidence Folder acceptance. Practical Completion triggers: the start of the Defects Liability Period clock, warranty commencement (warranties run from PC, not install date) and the transition of operational responsibility to the EMOS contractor. See also: HOTO, DLP, Final Completion.

The contractual milestone at the end of the Defects Liability Period when all defects identified during DLP have been rectified. Triggers final retention release and ends the Contractor’s project-level liability. The asset transitions fully into the EMOS contractor’s operational regime. See also: Practical Completion, DLP.

See DLP in the Big Five above.

The Commonwealth body responsible for issuing personnel security clearances: Baseline, Negative Vetting 1 (NV1) or Negative Vetting 2 (NV2). Contractors and subcontractor staff working on sensitive Defence sites require AGSVA-issued clearances at the appropriate level. Clearance processing typically takes 3-12 months. Used by. Contractors planning Defence work, Defence security teams. See also: EMOS, HOTO.

The Commonwealth audit body that periodically reviews Defence procurement, programme delivery and FM contracts. ANAO reports on Defence Base Services and the ERIK programme provide publicly-available insight into how Defence projects perform. Often cited in HOTO compliance discussions because ANAO findings drive Defence policy updates. Used by. Public oversight; cited by industry. See also: defence.gov.au, ERIK.

Defence’s major capital works programme for new base facilities, infrastructure and capability assets. Distinct from the smaller Estate Works Program. CFI projects are typically multi-year, multi-million-dollar builds covered by Managing Contractor or Head Contract structures. Used by. Defence Capability Acquisition & Sustainment Group, Managing Contractors at tender, subcontractors. See also: Estate Works Program, HOTO.

Defence’s recurring estate maintenance and minor works programme. Covers refurbishments, equipment replacements and small-to-medium capital improvements on existing Defence facilities. Distinct from CFI (major new build). Estate Works Program tenders are smaller and more frequent than CFI. Used by. Defence estate teams, mid-tier contractors. See also: CFI, EMOS, PAS.