Operator Responsibility is not an abstract liability issue, but a daily task: it's about organization, record-keeping, and legally compliant fulfillment of inspection and maintenance obligations in buildings. This article summarizes the relevant legal bases, highlights typical liability traps, and provides a practice-oriented roadmap with prioritized measures and digital tools such as CAFM, IoT and document management, so that facility managers and technical directors have concrete to-dos and selection criteria for implementation.

Legal Basis and Binding Standards for Operator Responsibility

Key takeaway: The Operator Responsibility relies on a few binding legal sources; those who know them can derive and document obligations specifically. Important starting points are the Ordinance on Industrial Safety and Healthmanagement, Occupational Safety Act, state building codes, as well as DGUV regulations and VDI guidelines. Read the texts in their original version: BetrSichV, ArbSchG, DGUV, BAuA, VDI.

What the Most Important Standards Practically Require

Ordinance on Industrial Safety and Health (BetrSichV): Operators must risk assessments for systems, appoint responsible persons, and set inspection intervals. Furthermore, safety-relevant changes must be documented, and recurring deadlines must be met.

Occupational Safety and Health Act (ArbSchG): Employers and operators are obliged to design workplaces safely, conduct training, and implement protective measures. The risk assessment must be in writing and updated when changes occur.

DGUV and VDI/Guidelines: DGUV regulations specify testing procedures (e.g., DGUV V3 for electrical installations). VDI guidelines such as VDI 6022 are not laws but are considered the state of the art and are incorporated into the testing requirements of authorities and insurers.

• Documents during inspections: Risk assessments, inspection logs (DGUV V3, Elevators, fire alarm systems), maintenance plans, operator instructions, training certificates, and contracts with external companies.
• What authorities expect: Traceable responsibilities, complete inspection history, and an audit trail, no loose Excel-lists without version control.
• Practical Test Case: If a signed proof is missing, inspectors often consider the measure as not having been carried out.

Precision of the term operator: An operator is not automatically the owner. The operator can be the user, the contractually responsible party, or an external FM service provider party. The decisive factor is the actual control and organizational power over the operation of the facility.

Trade-off and Limitation: Documentation alone does not protect against liability – it is a condition, not a substitute for proper technology and organization. Digital systems facilitate record-keeping but increase dependence on data quality; poor Master Data quickly turn a CAFM into a paper archive 2.0.

Concrete example: In a hospital, compliance with VDI 6022 for ventilation systems is a regular inspection subject. The operator has the duty to prove regulated inspection intervals, keep inspection logs, and define responsibilities between hospital management and external FM service provider must be contractually defined. Without a verifiable audit trail, responsibility can fall back to the operator during a hygiene inspection.

Next Step: Identify the three to five systems with the highest risk potential and compare existing evidence against the mentioned standard requirements. This is the only way to make legal certainty from documents practical and verifiable.

Frequently Asked Questions

Key takeaway: Frequently asked questions about Operator Responsibility are not aimed at general knowledge, but at practical decisions: who signs which protocols, which evidence is sufficient during an inspection, and how to integrate digital tools into the documentation process.

Is operator responsibility fully delegable to an external FM service provider?

Short answer: No. Operational tasks can be delegated, but the overall legal responsibility usually remains with the operator. Practical consequence: Contracts must include inspection mechanisms, reporting obligations, and escalation paths so that the operator can prove their inspection duties towards authorities and insurers.

What documents do supervisory authorities typically require during an inspection?

Most important Documents: Risk assessments, verified inspection protocols (e.g., DGUV V3), maintenance plans, operator instructions, and training records. Authorities check the traceability of responsibilities and whether inspection results have actually been implemented; incomplete or unverified logs are often considered non-existent.

Which CAFM functions are indispensable for fulfilling these documentation requirements?

Essential Functions: a robust asset register with unique IDs, automated inspection plans, mobile inspection checklists, a seamless audit trail, and document management for certificates. Trade-off: Many systems provide reports – the problem is rarely the lack of functions, but poor Master Data and a lack of process integration.

How quickly does the introduction of CAFM pay off in the context of operator responsibility?

Realistic Expectation: Amortization typically lies between 12 and 36 months, depending on property size, number of inspection cycles, and the initial condition of the Data. Limit: If you only map paper processes 1:1, the benefit remains low; invest first in cleaning up critical master data and Standardization of inspection workflows.

What technical requirements are needed for a clean IoT connection to CAFM?

Minimum Equipment: Real-time events for critical alarms, standardized asset IDs, timestamps, and reliable interfaces such as REST or OPC-UA. Constraint: Live-Data only help if rules exist that translate alarms into inspection or escalation workflows; otherwise, you just create more notifications without consequences.

What role does insurance play in the documentation process?

Practical Finding: In the event of damage, insurers require proof that reasonable Operator Responsibilities have been complied with. Incomplete documentation can lead to reduced benefits. Actual Benefits of Digital Logs: A clean audit trail significantly reduces points of contention — provided the data is immutable and the process is documented.

Concrete example: In an industrial plant, temperature increases in switchgear triggered an IoT-alarm; the system automatically created a ticket in the CAFM, documented measured values, and the measures initiated from them. In case of a later damage, the insurer accepted the complete logs as proof of immediate countermeasures, thus avoiding disputes over negligence.

False assumption I often see: Uploading certificates to a system once does not replace regular checks. Authorities and insurers look at consistent processes, not just file completeness.

Next steps that have an immediate impact: 1) List the ten most critical assets and link them to existing inspection protocols; 2) Set up an audit trail for these assets in your CAFM and test it against a hypothetical authority request; 3) Supplement contracts with service providers to include the obligation for digital handover of signed protocols; 4) Pilot IoT-connection for a critical system and measure the response time until ticket creation.