This practical handbook helps you systematically understand GEFMA guidelines and directly integrate them into CAFM processes. You will learn how operations, maintenance, space and floor management, and supplier management are mapped with concrete steps, including data quality and approval workflows. In the end, you will have a clear structure for compliance measurement, auditability, and realistic implementation in common tools such as Planon, Archibus, or FM:Systems.
GEFMA Guidelines at a Glance
The GEFMA guidelines do not represent a simple action guide, but rather a normative framework that systematically aligns facility management. They describe how governance, operations, maintenance, and safety are organized so that CAFM data is generated consistently and remains auditable. It is important that they are oriented towards the local context and at the same time can be measured against international references such as ISO 41001. Further details can be found on the official gefma.de website and in the ISO publications. ISO 41001.
The core chapters include Operations and Maintenance, Space and Floor Management, Cost Control and Contract Management, Supplier Governance and SHE - Safety, Health, and Environment. These fields correspond directly with typical CAFM modules: maintenance tools, space occupancy data, contract and supplier management, and audit trails for transparency. The structure facilitates a consistent mapping of guideline processes in your data model.
Practical implementation begins with uncompromising data quality: clear responsibilities, maintained master data, and traceable approval workflows. Mapping guideline processes to CAFM modules is key: Maintenance-processes into the maintenance module, Space and Floor Management into the space module, compliance reports into the reporting module. Example: An office complex with 15 buildings and 120,000 m² of usable space implements GEFMA according to gefma 190. Maintenance orders follow the defined approval workflow, space occupancies are fed from the space database, and supplier contracts are managed through the procurement module. The results appear in a shared key performance indicator dashboard, visible to facility managers and finance.
Audits, compliance, and monitoring utilize checklists, audit trails, and proof of documentation. Key KPIs include maintenance intervals, SLA fulfillment, data completeness, and audit coverage. A practical approach shows in real-time whether all maintenance tasks have been completed on time and if audit documents are fully available. Dashboards should be designed to provide transparency regarding responsibilities and approval processes.
Practical trade-offs: more controls often mean more effort and user friction; too much standardization can limit flexibility. The trick lies in change management: clear approval processes, automated notifications, and a defined escalation scheme, without unnecessarily burdening employees. Those who implement policies purely mechanically may get closer to compliance but miss out on operational agility and responsiveness.
Takeaway: Consistently align your CAFM data models with the GEFMA structure, define clear responsibilities, and utilize audit functions to permanently demonstrate compliance. As a next step, analyze your master data hierarchy and plan targeted training so that new processes are truly lived.
Core Areas of the Guidelines Relevant to CAFM
For CAFM-driven implementation of GEFMA guidelines, the core areas form the bridge between the regulatory framework and operational processes. These areas define which data, workflows, and controls must be modeled in the software so that guidelines actually have a guiding effect rather than just being documented.
- Operations Management, Maintenance, and Servicing: defines maintenance plans, responsibilities, approval processes; mapping to CAFM modules such as maintenance.
- Space and Floor Management: Room occupancy, usage types, area key figures; mapping in CAFM modules for occupancy planning and room management.
- Cost Control, Key Figures, and Contract Management: Budget and cost center control, SLA monitoring, supplier contracts; dashboards and audit-ready key figures.
- Supplier Governance and Auditability: SLA contracts, audit trails, approval workflows, certificates, and proof documentation.
- Safety, Health, and Environment in FM: Risk management, emergency plans, occupational safety documentation, regular training, and documentation obligations.
Important practical example: Data quality and clean master data form the basic constant. Without consistent taxonomies, clear responsibilities, and defined approval workflows, even a well-documented policy in CAFM can hardly lead to real compliance. The challenge lies in mapping: policy processes must be mapped to suitable CAFM modules, otherwise reports remain inconsistent and audits difficult to understand.
Practical example: In an administrative center with two building sections, a standardized maintenance cycle according to GEFMA 190 was implemented. The plan is stored in the CAFM maintenance module, release processes are defined in the workflow, and audit trails document all releases. The result: maintenance failure-related downtimes decreased while costs per maintenance order remained stable.
A common misconception is that guidelines are static documents. In practice, they act as living governance standards that must be regularly reviewed, updated in master data, and translated into dashboards. Without ongoing review cycles, compliance quickly drifts and operating costs reluctantly increase.
Takeaway: Start with a mapping-first view — identify which guideline processes need to be in your CAFM module, define data responsibilities, and build the key performance indicators around them.
Practical Implementation in the CAFM Context
Practical implementation in the CAFM context begins where guidelines are translated into concrete data and process structures. Data Quality and clear master data ownership are the fundamental building blocks; without them, mapping, approvals, or audit trails do not provide reliable compliance. The initial steps depend on which guideline areas can actually be mapped in the CAFM module and how they are lived in practice.
Avoid big-bang implementations. Instead, use a phased model: 1) Capture and prioritize core processes (operations management, maintenance, space and area management); 2) Assign these processes to the appropriate CAFM modules; 3) Plan the rollout, define approvals, conduct training, and document the approvals.
Example: An office building complex with three locations. The GEFMA guidelines require maintenance intervals, supplier management, and auditability in a consistent process. In a CAFM environment, a standardized maintenance order template is created, an approval workflow is established, and audit trails are activated; after a one-month pilot, documentation can be seamlessly integrated into regular operations, and management immediately sees dashboards on SLA fulfillment and cost development.
Data modeling and master data maintenance are the real leverage. Define field groups such as location, building section, asset catalog, maintenance interval, and responsible person, which are directly linked to policy processes. This also means clear naming conventions, consistent key figures, and an assignment of policy elements to CAFM modules. Additionally, according to Planon resources, you will find guidance on aligning CAFM with GEFMA/ISO standards. Planon Resources.
Workflow design and approvals must work in everyday life. Establish a RACI matrix, define approval timeframes, and document each approval as an archived process step. Link approvals with audit trails so that deviations are immediately visible. Store SOPs directly in the CAFM system so that new employees don't have to search for them first.
Compliance measurement is done via targeted KPIs and dashboards. Key metrics include maintenance interval compliance, SLA fulfillment, data completeness, and audit coverage. Conduct regular reviews to promptly reflect process changes and keep documentation up-to-date. This practice increases transparency and minimizes audit risks.
Next steps: Develop a 90-day roadmap with a kick-off, stakeholder plan, data cleansing, and the initial module assignment for operations and maintenance; anchor ownership in a weekly review meeting and utilize existing resources such as Planon Resources as a reference point for concrete mapping practices.
Tools and Systems Supporting GEFMA Guidelines
The right tool selection makes GEFMA Guidelines tangible: they translate normative requirements into concrete configurations for maintenance, space management, and supplier control. Without mapping to the appropriate modules, compliance and auditability remain abstract and difficult to measure.
In practice, Planon, Archibus, and FM:Systems dominate as integrated CAFM platforms; they offer predefined policy building blocks, audit paths, and reporting capabilities that can be directly aligned with GEFMA chapters. Additionally, many operators use iOffice for focused workflow or space management scenarios when the focus is more on quick implementation than on complete overall integration. Planon, Archibus and FM:Systems often provide pre-configured mapping that significantly accelerates the first few months.
Selection Framework
Set up a pragmatic framework that prioritizes mapping quality: first, how a policy point is mapped to which module, then how well this mapping can be technically realized. Consider integrations, data model compatibility, costs, and support roadmap. A solid framework helps avoid suboptimal compromises that may need to be corrected expensively later.
- Criterion 1: Integration Capability (APIs, bidirectional sync, event-driven updates)
- Criterion 2: Mapping quality of the data model; how cleanly can policy processes be mapped into modules**
- Criterion 3: License model, maintenance costs, and scalability with portfolio growth
- Criterion 4: Auditability, versioning, and reporting functions
- Criterion 5: Roadmap and vendor support for national and international requirements
Without a clear data strategy, mapping almost always fails. Master data, taxonomy, and communication logic must be defined in advance so that the chosen tool works consistently and audit trails remain meaningfully usable.
Key point: Governance must run parallel to tool selection; those who only buy a platform but do not clarify approval circles and responsibilities will experience delays later during audits.
Practical example: A university building portfolio with 12 properties uses Planon and maps maintenance, space and floor management, as well as supplier management to the GEFMA chapters. Predefined guideline modules measurably increased data quality, audit trails facilitated annual compliance reviews, and the central dashboard became the common reference for facility management teams.
Deep integration brings benefits, but costs time and money. For medium-sized portfolios, it often makes sense to start with core processes that are most dependent on guidelines, and then gradually connect further modules. This reduces risk, increases transparency early on, and provides concrete, learning experiences for the rollout.
Next step: Start with a targeted pilot project, define the first mapping tiles, and establish the governance criteria. This way, you gain early insights that go beyond pure tool functionality and actually drive implementation in your portfolio.
Audit, Compliance, and Monitoring
In practice, audit, compliance, and monitoring mean that every action in building operations is verifiably documented. Audit trails, approval processes, and change logs form the foundation: from maintenance approvals to budget approvals to safety-relevant measures. Those who only look at the end result here miss the controls that count later with auditors. The requirements can be found in the GEFMA guidelines GEFMA and in ISO 41001, which demand clear responsibilities and reliable evidence that can be directly mapped into CAFM workflows.
A practical trade-off is evident in the balance between strictness and operational speed. Overly strict protocols slow down teams, while overly lax records ruin evidence. Auditable processes must be integrated into daily work, not function as a separate compliance section. Automated approval routes should remain traceable, with clear escalation levels.
Example from a mixed-use office complex: In the CAFM environment, audit trails were linked for all maintenance orders; approval workflows and access logs were managed in compliance with GDPR. After three months, SLA fulfillment and planning accuracy improved noticeably, discrepancies in change orders decreased, and reports provided reliable bases for supplier evaluations.
Practically, it is advisable to define master data standards, establish roles and approval types, and store logs in standardized formats. Anchor audit functions directly in the CAFM modules, including versioning of orders, approval protocols, and clear documentation paths. Additionally, regular data tests help to detect inconsistencies early.
- Audit trails as a mandatory component of every change
- Approval logs with timestamps and responsibilities
- KPI dashboards for compliance, maintenance intervals, and data completeness
- Regular reviews of audit data and process approvals
Important connection: Without consistent auditability, compliance promises remain empty words – firmly anchor audit, approvals, and evidence in the processes.
Next step: Set up a pilot operation in a single property, define clear audit reports, and plan monthly reviews to permanently ensure data quality and approval controls.
Practical Examples and Next Steps
In practice, they deliver GEFMA Guidelines real added value when they are directly integrated into the CAFM workflow and do not remain as an appendix on the shelf. This means anchoring normative requirements in concrete modules – operational management, maintenance, space and floor management, cost and supplier control – and linking them with master data, approval processes, and dashboards.
A central limitation is data quality. Without clean master data, clear responsibilities, and documented approvals, any audit trail will fail. The trade-off becomes apparent when teams work under time pressure: quick, superficial processes save time today but create rework effort and hidden risks tomorrow.
Example University Campus: The facility team maps maintenance plans directly to the CAFM module for maintenance, links equipment to status reports, and implements weekly audit checks to ensure data currency. The result is better maintenance planning, fewer unplanned failures, and verifiable compliance with auditors.
- Step: Inventory of policy processes and master data.
- Step: Map to CAFM modules and define approvals.
- Step: Pilot phase in a building section with short release cycles.
- Step: Rollout and continuous improvement via dashboards.
Consider during rollout: Change management is the linchpin. Train employees specifically and embed evidence directly into processes.
Next step: Start a six-week pilot phase in a building area, define clear KPIs (data completeness, maintenance coverage, audit trail quality), and secure resources for change management.
