Congratulations, once again! You have another strategy paper in front of you, promising to save your operational safety with a "well-maintained maintenance manual." As someone who has spent the last twenty years picking up the pieces of failed maintenance projects, I tell you: a maintenance manual is nothing at first. It's either a dust collector in the master craftsman's office or data garbage on drive Z.
However, if you want to tackle the topic seriously – in a way that the operating inspector won't call your liability insurance with a smirk – the next few minutes require your undivided attention. Here is the unvarnished truth about how to build a functioning CAFM system from legal requirements without suffocating in your own bureaucracy first.
1. Legal Framework & Governance: Why your folder on the shelf won't save you from any judge
Let's start with the favorite sport of German managers: collecting standards.
One likes to adorn oneself with DIN EN 13306 for the nomenclature, solemnly quotes the ISO 55001/55002 for asset management and garnishes the whole thing with the GoBD, because someone once heard at GEFMA that it had something to do with digital audit security. The reality? Usually, there's an impressive ISO certification on the wall, while in the hall, the control cabinet is held together with duct tape, and nobody knows who signed off on the last inspection.
Governance doesn't mean writing 50 pages of responsibilities. Governance means: Who takes the blame when the pump stops?
- Standards are not an end in themselves: You are the minimal shield against the public prosecutor's office.
- Mountains of documents do not equal legal certainty: The auditor isn't looking for quantity. They are looking for the one gap in the audit trail that proves you don't have your own processes under control.
- The tragic misconception: "We'll quickly make it a fillable PDF." Save yourself the trouble. A fillable PDF is digital hazardous waste without consistent master data logic. Anyone who starts with CAFM or ERP systems like SAP EAM, IBM Maximo, or Planon without central data mapping is simply creating data garbage with a warning.
From the consultant's practice: A medium-sized company with three plants wanted to harmonize maintenance. The approach: a lean, digital approval system with a clear audit trail template instead of mountains of files. The result after one year? No magical doubling of the profit margin, but the first audit since the company's founding without high blood pressure in the management and noticeably fewer externally paid service providers.
2. Structure & Templates: Stop creative writing in maintenance
When I look at unprepared maintenance documents, I often read prose that is more reminiscent of maintenance poetry than technical documentation. That stops now. A legally compliant maintenance document requires a strict structure – nothing more, nothing less:
- Asset Register (What do we even own?)
- Maintenance Plans & Work Instructions (What do we do, when, and how?)
- Safety & Emergency Protocols (How do we prevent personal injury?)
- Spare Parts Catalog & Change Management (What do we install where, and who approved it?)
The specification sheet for your data fields
Every asset – from industrial robots to fire alarm systems – needs clean nomenclature. Deviating here means losing.
| Field label | Validation & Format | Why you can't do without it |
|---|---|---|
| Asset ID | Alphanumeric, unique | The key to the entire CAFM world. No duplicates! |
| Location | Location-Based Assignment (Hierarchy: Property, Building, Floor, Room, possibly Zone) | If the technician searches for the control cabinet in the wrong plant, things will get heated. |
| Maintenance Interval | Time- or performance-oriented | Defined according to manufacturer specifications or own risk assessment. |
| Approval Status | Draft / Under Review / Approved | Those who work without a status are relying on half-knowledge. |
| Audit Log | Timestamp + User ID | The GoBD life insurance for legal cases. |
The compromise: Don't even try to design a separate special form for every exotic piece of equipment in your fleet. Use a robust standard template for 80% of the systems and add special fields only where absolutely necessary. Risk it is absolutely necessary.
3. The Data Model: The heart of your maintenance
The most beautiful frontend won't help you if the backend is a garbage dump. You need a Canonical Data Model – the one, undeniable truth about your systems.
A functioning model links your entities in a clear hierarchy:
- Asset Master (1:N): The central asset (ID, location, type, year of construction) refers to several subordinate Maintenance Tasks (Interval, inspector, work instruction).
- Documents & Audit Trails (1:N): Each asset has a unique history of approvals, certificates, and change logs.
- Spare Parts & Suppliers (N:N): Maintenance tasks are flexibly linked with required spare parts, components, and external service providers.
Anyone who thinks they can leave master data maintenance to the shift supervisor 'on the side' might as well burn their money directly. It's almost a full-time job (perhaps you have a working student for it?). If asset IDs in SAP EAM are named differently than in your CAFM system, you don't have a software problem, but a management problem.
4. The 8-Week Implementation Plan: Stop discussing and start delivering
Forget two-year transformation projects. The pilot must be ready after eight weeks, otherwise the organization will lose interest.
- Weeks 1-2: The Big Cleanup. Inventory, consolidate asset register, ruthlessly delete duplicates. Match serial numbers on-site, don't copy from old Excel spreadsheets.
- Weeks 3-4: The Prioritization. Risk assessment by criticality. A-assets (production stoppage upon failure) receive immediate attention, C-assets wait.
- Weeks 5-6: The Content. Definition of intervals, creation of work instructions, and linking with asset types. Minimum Viable Documentation is the goal.
- Week 7: The Setup. GoBD configuration in CAFM, role and permission assignment, setup of digital signature paths.
- Week 8: The Real Test. Training of technicians (on tablets, not in a training room), go-live in the pilot area, and preparation for rollout.
Tip from countless audits: Start with a site. Anyone who tries to impose an unfinished data model on five plants simultaneously will only create fivefold chaos.
5. Audit Security & CAFM: From paper tiger to digital management tool
At the end of the day, the entire construct serves only one purpose: if something goes wrong, you must prove prove who maintained, changed, or released what and when.
A CAFM system is not a miracle cure, but merely the digital enforcer of your rules of play. If you haven't implemented clear release processes (four-eyes principle) and automatic audit trails there, even the most expensive software license won't protect you from liability risks.
Conclusion for Management
A legally compliant maintenance manual is not a project that you complete once and then solemnly link in the intranet. It is a living, digital operating system. Rely on a clean data basis, uncompromising governance, and the right software support.
Everything else is a waste of time – and you already have too little of that in your daily operations anyway.
