Defence Housing Maintenance Software: A Practical Guide for DHA and EMOS Contractors
Defence housing maintenance software is a digital platform that handles defect tracking, work-order management and O&M documentation for residential and base infrastructure assets owned or managed by the Australian Department of Defence, including Defence Housing Australia (DHA) portfolios. It bridges the head contractor delivering the housing, the subcontractors uploading commissioning evidence and the EMOS contractor inheriting the assets at handover.
By Procom Solutions Team Updated 7 min read
Who this guide is for
If you’re here, you’re probably one of three people:
- A project manager delivering new Defence housing or refurbishment work who needs to produce a compliant ERIK-aligned handover package.
- A subcontractor on a DHA or base housing project being asked to upload commissioning data, warranties and as-built information into a structured handover system.
- An EMOS subcontractor inheriting a residential portfolio whose lifecycle data lives across three different file formats from three different builders.
Whichever you are, the underlying compliance framework is the same: Defence housing follows the same ERIK and HOTO conventions as the rest of the Defence estate, with residential-specific layers (smoke alarm certification, residential appliance manuals, accessibility compliance) added on top.
What makes Defence housing different to commercial residential
Generic property-maintenance software (Property Tree, MRI, Yardi, etc.) is built for commercial landlords and body corporates. It tracks tenancies, rent rolls and routine maintenance call-outs. Defence housing maintenance has different priorities:
- ERIK structure compliance. Documentation has to be named, formatted and submitted in a way that fits the Estate Resources Information Kiosk (ERIK). Subcontractors who hand over a generic ZIP of PDFs get rejected.
- EMOS handover. The eventual operator is an EMOS prime contractor (Downer, Ventia, BGIS, Serco or Cushman & Wakefield depending on the region), not a strata manager. That contractor needs the data in a structure their CMMS can ingest at takeover.
- DLP defect chain. The Defects Liability Period traces back to the original installing subcontractor (not to the head contractor) for 12-24 months after Practical Completion. Generic CMMS rarely models this contractual chain correctly.
- HOTO Evidence Folder. A residential HOTO package still has to satisfy the current HOTO Plan and Checklist (v7.3 at time of writing), including formal acceptance walkthroughs and signed defect lists.
- Security clearances. Subcontractors working on base housing often need at least Baseline (and sometimes NV1) AGSVA clearances. Maintenance software has to gate documents accordingly.
These five constraints are why Defence housing portfolios tend to end up on purpose-built Defence-handover platforms rather than generic property tools.
The lifecycle, mapped to software functions
- Design and procurement. The head contractor sets up the O&M-manual skeleton against the relevant template (OMM Buildings, OMM Base Infrastructure or a housing-portfolio variant). ERIK-aligned naming applied from day one prevents rework later.
- Construction phase. Subcontractors upload commissioning records, manufacturer literature, warranty certificates and as-built drawings as they finish work packages, not in a panicked sprint at Practical Completion. Missing-data alerts replace email chasing.
- HOTO Evidence Folder finalisation. The platform compiles the Evidence Folder against the current HOTO Plan and Checklist. Defence reviewers and the incoming EMOS contractor walk through acceptance using the structured folder, not a stack of PDFs.
- Practical Completion + Defects Liability Period. The DLP timer starts at PC. Reported defects route to the responsible subcontractor (not the head contractor), with the rectification evidence stored against the original work package. At DLP expiry, the head contractor has a complete defect-resolution record.
- Operations under EMOS. The EMOS contractor ingests the structured handover into their own CMMS. Asset registers align to DAMIS coding. Recurring maintenance schedules pull from the manufacturer data captured during construction.
Common failure modes
These are the patterns we see most often when contractors come to us mid-project:
- "We’ll fix the structure at handover." The Evidence Folder cannot be reverse-engineered from a shared drive of PDFs in two weeks. ERIK-aligned structure has to start at QMP development.
- Generic CMMS for a Defence housing scope. Tools designed for residential strata or commercial property don’t encode ERIK naming, HOTO checklists or the DLP subcontractor chain. Substituting them creates a translation layer at handover.
- One head-contractor account, every sub uploads through it. Audit trails become useless. Each subcontractor needs their own scoped account so DLP-period defects can be traced back to the installer.
- Smoke-alarm and residential-compliance records as scanned PDFs. These need to be machine-readable for EMOS recurring maintenance scheduling. Capture as structured data, not images.
- Underestimating clearance lead times. If a subcontractor needs NV1 to enter base housing on a working day, planning for "we’ll get them cleared during construction" doesn’t survive contact with AGSVA timelines.
How Procom fits
Procom is an Australian-built O&M-compilation platform specialised for Defence handovers. For housing portfolios, it covers:
- ERIK-aligned manual templates including OMM Buildings (the closest template for most DHA-style housing) and OMM Base Infrastructure for site-wide elements.
- Subcontractor-scoped uploads with QR-code onboarding so installers reach the right node in seconds.
- Automatic OMM volume splitting for portfolios that breach the 200 MB SEG v2.0 per-volume ceiling.
- Defect tracking with importance-based reminders and a chain back to the original installing subcontractor for DLP enforcement.
- HOTO Help built around the v7.3 Plan and Checklist.
If you’re scoping software for a Defence housing project, the Defence Handover Guide walks the entire framework end-to-end; the ERIK Guide and EMOS Defence Explained cover the two frameworks most relevant to housing handovers.
Frequently Asked Questions
What is Defence housing maintenance software?
Defence housing maintenance software is a digital platform that handles defect tracking, work-order management, and O&M documentation for residential and base infrastructure assets owned or managed by the Australian Department of Defence (including Defence Housing Australia portfolios). It captures the lifecycle data Defence and its EMOS facility-management contractors need to operate the housing stock after handover.
Who uses Defence housing maintenance software?
Three main users: (1) head contractors delivering new Defence housing or refurbishment projects who need to compile ERIK-aligned handover packages, (2) subcontractors who upload commissioning data, warranties, and as-built information into the handover system, and (3) EMOS contractors who inherit the assets at handover and operate them under their prime contract.
How does this differ from generic property-maintenance software?
Defence housing has stricter compliance requirements than commercial property. Documentation must align with ERIK structure and naming, defect data must support EMOS reporting back to Defence, and handover packages must follow the relevant OMM or HOTO template (Buildings, Base Infrastructure, or housing-specific variants). Generic CMMS tools rarely encode these Defence-specific conventions.
Does the software work for Defence Housing Australia (DHA) portfolios?
Yes. DHA portfolios sit under the same ERIK framework as the rest of the Defence estate. The same O&M-manual structure, HOTO checklists and DLP defect-rectification process apply, with housing-specific items (smoke alarms, residential appliances, ground-floor compliance) layered on top.
What about the Defects Liability Period for housing?
DLP on Defence housing runs 12-24 months from Practical Completion. During this period the installing contractor remains liable for defects in their work, regardless of whether the property is occupied. The maintenance platform tracks reported defects, routes them to the responsible subcontractor, and keeps the rectification evidence trail Defence expects at DLP expiry.
How does HOTO work for housing handovers?
HOTO (Handover/Takeover) for housing follows the same structured Defence process as base infrastructure: the contractor produces an Evidence Folder against the current HOTO Plan and Checklist, Defence (and the incoming EMOS contractor) walk through acceptance, and the residual defect list rolls into DLP. The maintenance platform compiles the evidence folder progressively during construction rather than at handover only.
Working on a Defence housing project?
Book a 20-minute walkthrough on a sample handover, or contact us about the specific portfolio you’re bidding on.