What is ERIK?
ERIK stands for Estate Resources Information Kiosk, the Department of Defence's online portal for the design, construction, maintenance and operation of the Defence estate (every base, training area, port and depot owned or leased by Defence across Australia). It is the renamed successor to DEQMS, the Defence Estate Quality Management System, and now sits under the Estate Resources & Data banner together with the Data Supplier Toolkit.
Where private-sector projects are governed by AS/NZS ISO 9001:2015 plus the contract's own quality clauses, Defence projects must additionally comply with the requirements published on ERIK. This means more prescriptive documentation, more frequent inspection and test reporting and a higher bar on traceability between design intent, installed work and as-built records.
In practical terms, the requirements ERIK publishes dictate:
- The format and content of contractor Quality Management Plans (QMP)
- Inspection and Test Plans (ITP): what gets inspected, by whom, at what hold/witness points
- Non-Conformance Reports (NCR) workflow and close-out evidence
- Operations & Maintenance manual structure and minimum contents
- Handover documentation: what must be transferred at Practical Completion, what at Final Completion and what at end of the Defects Liability Period
- Asset data captured for the Defence Asset Management Information System (DAMIS) and downstream facility management systems
If you're a Managing Contractor on a Head Contract, the QMP is yours to write. If you're a subcontractor, you inherit ERIK obligations flowed down through the Managing Contractor's contract.
Who has to comply with ERIK?
Every party touching the Defence estate has ERIK responsibilities, scoped to their role:
Managing Contractors
Hold the Head Contract with Defence. Responsible for the project's overall QMP, the integration of subcontractor quality records and the final Defence-acceptable handover package. They sit between Defence and the trade subcontractors and are the ones audited against ERIK most directly.
Head Contract & subcontractor packages
Trade subcontractors (mechanical, electrical, hydraulic, fire, security, building services) carry their own ITPs and NCRs and must produce O&M manual content that complies with the ERIK template structure. Most defects raised during the Defects Liability Period (DLP) trace back to gaps in subcontractor records: incomplete commissioning, missing test results or O&M sections lifted from a previous project without updating.
Facility Management contractors
EMOS and PAS (Property & Asset Services) contractors operating the estate post-handover inherit ERIK obligations for ongoing maintenance, asset inspection and configuration management. Their work order systems and CMMS must align with ERIK data schemas.
Consultants & superintendents
Design consultants, project managers and the Defence superintendent all reference ERIK in their oversight role, particularly in the design review, FAT/SAT and Practical Completion certification stages.
What's in an ERIK-compliant Quality Management Plan?
A QMP that survives Defence review typically includes the following sections, each cross-referenced to ERIK requirements:
- Scope, project context, applicable contracts: names of the Head Contract, SoFC reference, work package boundary
- Roles, responsibilities, authority matrix: including the nominated Quality Manager and their alternates
- Document control procedures: versioning, distribution, transmittals, redline workflow
- Quality risk register: design, construction, commissioning, handover risks
- Inspection and Test Plans (ITPs): one per discipline or work package
- Non-Conformance and Corrective Action procedures
- Audit programme: internal audits, surveillance audits, Defence-led audits
- Records management and the O&M manual development plan
- Handover and transition plan: including DLP arrangements
- Continual improvement and lessons-learned process
The Defence Managing Contractor Contract templates published on defence.gov.au provide the structural baseline. Procom's platform aligns its O&M manual templates with this structure so that QMP Section 8, records management and O&M manual development, comes pre-configured.
ERIK and the O&M Manual
The O&M (Operations and Maintenance) manual is the single highest-risk ERIK deliverable. Most Defence project disputes during handover and DLP come down to O&M manual gaps. The ERIK-compliant O&M manual is not a single bound document. It's a structured collection of:
- As-built drawings (PDF + native CAD/Revit)
- Manufacturer technical literature for every installed asset
- Commissioning test results with signed witness sheets
- Maintenance schedules by discipline and asset
- Spare parts and consumables lists
- Warranty certificates with start/end dates and contact details
- Operating procedures and emergency response
- Asset register matching the DAMIS schema
- Training records for the FM contractor's operations team
ERIK is explicit about file naming, folder structure and metadata. A common rejection cause is submitting an O&M manual that's complete in content but doesn't match the Defence template structure. Defence will return it without reading it.
This is where dedicated O&M manual platforms, Procom's defence O&M manual platform included, replace the email-and-shared-drive model that historically dominated. The platform enforces the structure at upload time, so subcontractor submissions cannot bypass the template. The result: fewer rejections, faster Practical Completion and a cleaner DLP transition.
ERIK Transition: What's Changing in 2026 and Beyond
Defence is currently running the Estate Resources Information Kiosk (ERIK) transition programme, modernising the framework that originated in the early 2010s under the Suite of Facilities Contracts. The transition aligns ERIK with:
- ISO 9001:2015 language and structure (high-level structure, risk-based thinking)
- Digital handover expectations: searchable, hyperlinked, BIM-integrated manuals rather than bound paper or flat PDFs
- Asset data interoperability: DAMIS-aligned data schemas so that handover records flow into Defence's facility management systems without re-keying
- Cyber & information security classifications on technical documentation
For contractors, the practical implication is that legacy O&M manual templates, Word documents with attached PDFs in a folder structure, are being phased out in favour of structured, queryable, machine-readable deliverables. Platforms that support BIM links, asset metadata and digital signatures are the direction of travel.
Procom Solutions has aligned its file structure templates with the ERIK transition framework so that manuals produced today meet both the current Defence requirements and the structure flagged in transition documents.
Common ERIK Compliance Failures (and how to avoid them)
Drawing from public ANAO audit reports on Defence base services and from anonymised observations across Australian construction project handovers, the recurring ERIK compliance failures are:
1. Incomplete commissioning records
A system is installed and tested, but the witness sheets are unsigned, undated or missing the subcontractor's QA stamp. At handover this is the single most common rejection. Fix: enforce signature workflows in the O&M platform; reject uploads without all required signatures.
2. As-built drawings not reconciled with NCRs
The drawing shows the original design; the NCR closed out a variation; the manual contains both, and they conflict. Fix: maintain a single source of truth for as-built drawings, with NCR cross-references tracked in the platform.
3. Warranty start dates inconsistent with Practical Completion
Subcontractors stamp warranties from supply date, but Defence requires them from Practical Completion. Fix: enforce a warranty start-date field that defaults to the Practical Completion date.
4. Spare parts lists without supplier contacts
Defence's FM contractor inherits the spares list but cannot procure replacements because supplier details are missing or stale. Fix: mandatory supplier contact fields with last-verified date.
5. Asset register schema mismatches
The contractor uses their own asset numbering; Defence requires DAMIS-aligned identifiers. Fix: configure the asset register template upfront to match the project's DAMIS instance, never retrofit it at handover.
6. O&M manual content lifted from a previous project
Subcontractors copy a manual from a prior job and forget to update site-specific details. Defence audits will catch this. Fix: template lockouts on site-specific fields that force fresh entry per project.
ERIK, EMOS and the Bigger Picture
ERIK doesn't exist in isolation. It sits inside Defence's broader estate management ecosystem:
- EMOS: Estate Maintenance and Operations Services, the prime contracts (currently held by Downer for the east coast, others for west coast and territories) that deliver day-to-day FM on Defence bases. EMOS contractors are the downstream consumers of every O&M manual produced under ERIK. Bad ERIK compliance = bad EMOS operations.
- PAS: Property & Asset Services, the contract suite that EMOS sits under, defining the broader Defence FM commercial framework.
- DAMIS: Defence Asset Management Information System, the data backbone. Asset records must flow into DAMIS to be recognised by Defence as operationally controlled.
- SoFC: Suite of Facilities Contracts, the contract template library ERIK quality requirements are embedded in.
If you are a contractor or subcontractor producing handover documentation, what hits your desk is ERIK. But what your client (Defence + their EMOS contractor) ultimately consumes is data that flows from ERIK into DAMIS and then into the EMOS contractor's CMMS. Compliance is not just about getting the manual signed off. It's about the manual being usable downstream.
For more detail on EMOS specifically and how subcontractors meet EMOS expectations, see our EMOS Defence explained guide.
How Procom Solutions Helps with ERIK Compliance
Procom's platform was built around the ERIK file structure. Specifically:
- Pre-configured templates matching the Defence O&M manual structure: including the asset register schema, commissioning record sections, warranty register and spares list
- Subcontractor submission portal that rejects uploads missing required metadata (signatures, dates, drawing references)
- Real-time progress dashboard so the Managing Contractor sees ERIK completion percentage across every subcontractor at any time, not just at the panic-week before Practical Completion
- PDF export and electronic manual generation aligned with the Defence template structure
- DLP defects workflow that links every defect back to the relevant O&M section, NCR or commissioning record, closing the audit trail Defence expects
Procom is Brisbane-based, with experience across Australian Defence construction handovers. We don't claim a Defence partnership. What we offer is software built by people who've worked on Defence projects and know the gaps that ERIK audits catch.