HOAI Service Phases and CAFM: How Facility Managers Stay on Top of Construction Projects

Welcome to the next chapter of our popular series "Things that sound great in construction until they hit operational reality".

As a consultant who has spent years trying to reconcile the worlds of architects, civil engineers, IT architects, and calculation-driven facility managers, I can assure you: The HOAI (Fee Structure for Architects and Engineers) and a CAFM system are connected in a classic love-hate relationship.

For the planner, the HOAI is the legal basis for their fee settlement. For the facility manager, it is – if properly mapped in CAFM – the only chance to manage a construction project in such a way that it doesn't land on their desk as an unstructured data junk pile upon handover in service phase 8/9.

Here is the unvarnished, practice-proven guide on how to anchor HOAI service phases 1 to 9 in CAFM without getting bogged down in bureaucracy.

1. Anchor HOAI in CAFM: The data model is not a PDF storage location

The biggest mistake companies make: They treat HOAI phases in CAFM like folder structures on a network drive where PDFs are dumped.

This gives you absolutely no transparency. A HOAI phase in CAFM is object-related status and process attribute. This means: Every building component, every room, every cost item, and every document carries the DNA of the respective HOAI phase within it.

+--------------------------------------------------------------------------+  |                        CAFM CORE DATENMODELL                             |  +--------------------------------------------------------------------------+  |  [ Raum-ID / Asset-ID ]                                                  |  |     ├── HOAI-Status: Phase 3 (Entwurfsplanung)                             |  |     ├── Cost-Attribute: DIN 276 (Soll vs. Ist)                            |  |     ├── BIM-Link: IFC-Guid (LOD 300)                                     |  |     └── Audit-Trail: Freigabe-ID / Timestamp / User-Role                |  +--------------------------------------------------------------------------+  

The four pillars of modeling

• Object-related HOAI Properties: Rooms and M&E assets receive phase attributes (e.g. LPH_Status = 3_EntwurfCAFM-Blog.de

• Standardized workflows: No phase transition (gate check) without digital approval and an unalterable audit trail.

• Cost control according to DIN 276: Linking HOAI phases with cost calculations to see budget deviations (cost estimate phase 2 vs. cost calculation phase 3 vs. final cost estimate phase 6) in real-time on dashboards.

• BIM/IFC Versioning: The IFC model is frozen per HOAI phase (baseline) and assigned an approval ID.

The hard trade-off: Too many data fields per phase paralyze the project team. A structure that is too flat means you can no longer trace later additions. The rule is: As much granularity as necessary to secure costs according to DIN 276 and operator responsibility – but no more attributes.

2. LPH 1 (Basic determination): The foundation before the first groundbreaking

Whoever skimps in Phase 1 pays ten times as much in Phase 8. In the preliminary planning, the CAFM system is set up with the digital room and function book set up.

• Room program & target criteria: Definition of room types, area approaches, target temperatures, and lighting intensities.

• Cost framework: Anchoring the budget in the CAFM system as the first benchmark.

• Governance & Data Dictionary: Definition of naming conventions (taxonomy). If the architect calls the room "Office 01", the MEP tool "R_101", and the CAFM system "FL_EG_001", chaos is programmed from Phase 2 onwards.

Practical Tip: Demand that the planning team adhere to a platform-agnostic Data Dictionariesalready in LPH 1. If the data structure is not established here, you will only be able to correct it in LPH 5 with pain and high consulting costs.

3. LPH 2 & 3 (Preliminary & draft planning): BIM meets CAFM (LOD vs. LOG)

During the preliminary and design planning phases, data exchange between BIM authoring tools (Revit, ArchiCAD) and CAFM is in full swing. This is where the so-called Detail Trap.

[ CAD / BIM-Autorenwerkzeug ]  ---( IFC / AIA )--->  [ CAFM Engine ]       (Erzeugt LOD 300)                                  (Filtert auf Betreiber-LOD)       - Geometrie & Visuals                              - Technische Attribute       - Bewehrungsstähle (müll!)                         - Wartungsintervalle & TGA  

The term of the hour: LOD (Level of Development)

An architect requires detailed geometry (LOD 300) in service phase 3. In this phase, CAFM primarily needs Level of Geometry (LOG) for area calculations and Level of Information (LOI) for initial MEP costs.

• Check the module: Link the IFC model (ideally IFC 4) directly to the CAFM master data.

• Set Freeze Points: Each time the design planning is completed (service phase 3), the status in CAFM is recorded as a version. Budget deviations from service phase 2 must be immediately audited as a change event.

Important Note: BIM is not a guarantee for cost savings in planning. BIM ensures data quality and transparency. Anyone who believes that implementing BIM will save money from day 1 is suffering from a loss of reality.

4. LPH 4 & 5 (Permit & execution planning): Compliance and versioning

In service phases 4 and 5, the focus is no longer primarily on areas, but on compliance obligations, fire protection, permits, and execution details.

This must be stored in CAFM in a legally compliant manner

1. Approval documents: Building permits, fire protection concepts, drainage applications.

2. Tamper-proof audit trails: Who approved which execution plan and when?

3. Approval workflows: Automatic notifications to the future operator (FM trades) to check the "operational readiness" of the execution plan (FM-compliant planning).

Example: If the planner in LPH 5 plans a fire damper in a location where the facility manager would later have to erect an 8-meter-high scaffold for maintenance, the CAFM must capture this defect via a FM Design Review Workflow before drilling occurs.

5. LPH 6 & 7 (Award): Procurement data and award units

In phases 6 and 7, planning becomes market reality. Procurement data becomes central objects in the CAFM.

[ GAEB-Ausschreibung ] ---> [ Angebotseingang (LPH 7) ] ---> [ CAFM / ERP Sync ]                                                                     |                                                           (Vertrags-Asset angelegt)  

The core integration: Synchronize the tender data in the CAFM with your ERP system (e.g., SAP S/4HANA). When the contract is awarded, the order data in the CAFM must be automatically assigned to the components and trades.

6. LPH 8 & 9 (Object monitoring & support): The birth of the operator

This is where the CAFM's moment of truth arrives. Phase 8 (construction supervision) seamlessly transitions into Phase 9 (object management and documentation). What is not structured in the CAFM now will disappear forever in stacks of folders.

+--------------------------------------------------------------------------+  |                  ÜBERGABE-WORKFLOW (LPH 8 --> LPH 9)                     |  +--------------------------------------------------------------------------+  |  1. Mängelerfassung (Mobil per CAFM App vor Ort)                         |  |  2. O&M-Handbücher & Garantien an Assets hängen                           |  |  3. Automatische Generierung von Wartungsplänen (Anlagenstart)           |  |  4. Aktivierung der Gewährleistungsverfolgung (Fristen-Alarm)             |  +--------------------------------------------------------------------------+  

The four core tasks for CAFM takeover

1. Digital defect recording: Assign the elimination of construction defects via app directly to the BIM object or room.

2. Document Linking: O&M manuals (operating and maintenance instructions), declarations of conformity, and inspection certificates are directly attached to the respective MEP asset in the CAFM.

3. Automated maintenance schedule creation: Based on manufacturer specifications and DIN 31051 / VDMA 24186, the CAFM automatically generates future maintenance orders on the day of acceptance.

4. Warranty management (LPH 9): The limitation periods for defect claims (usually 4-5 years) are monitored by the system. The CAFM reminds you 6 months before the deadline to conduct an inspection.

7. C-level conclusion & implementation checklist

Anchoring the HOAI in the CAFM is not an IT toy, but the tool for Liability and construction cost minimization.

Your checklist for the next project

• [ ] Adopt Data Dictionary: Mandatory definition of naming conventions before LPH 1.

• [ ] Define HOAI properties: Anchor LPH status as a mandatory field in the CAFM data model.

• [ ] Adapt BIM BEP (BIM Execution Plan): Precisely prescribe to the planners which LOI/LOD values must be delivered to the CAFM in LPH 2, 3, and 5.

• [ ] Set up Gate Checks: No approval of the next HOAI phase in CAFM without a successful audit trail and budget check according to DIN 276.

• [ ] Activate ERP interface: Mirror award and contract data from LPH 7 directly into the finance system.