45th FVI Expert Breakfast

Topic: "When Responsibility Becomes Personal" – Duty of care, traceability, and organizational responsibility in maintenance.

The session demonstrated through a tragic practical case how quickly a technical gap can become a personal liability risk. A fatal workplace accident led to years of criminal and civil proceedings against several technical and organizational leaders.

• Invisible plant components become an organizational risk: A pressurized pipeline was neither correctly classified nor included in the ongoing pressure equipment monitoring. Despite audits, legal management, and extensive approval documents, it remained a "white spot" for years. The case shows: What does not exist in the plant structure tree and inspection processes quickly becomes organizationally invisible.
• "Who writes, stays": In a serious case, it is not what was verbally discussed or supposedly generally known that counts, but what was verifiably documented. A participant reported that after an accident, SAP action logs, user IDs, damage codes, and technical order completions were evaluated as evidence. Entries like "999 – Miscellaneous" or closing an order in a colleague's name can then immediately speak against those responsible.
• Risks must be documented and escalated: Anyone who identifies a safety-critical deviation should not report it just once. If there is no response, the report must be verifiably repeated and, if necessary, escalated to the next management level. The uncomfortable message thus protects not only the reporting maintenance worker but also the plant management and executive board.
• Brownfield safety needs a reliable lifecycle history: Especially in older plants, information about the age of safety-relevant components, previous modifications, or replaced parts is often missing. A practical approach was discussed: inventory, gap analysis, risk assessment, external evaluation, and a step-by-step safety or retrofit project. The key is not to replace everything immediately, but to systematically identify risks, make decisions traceable, and document measures permanently.

Classification: From scattered information to a reliable digital lifecycle record

This episode fits perfectly with the Hahn-PRO strategy because it shows that operational intelligence not only reduces downtime but also improves transparency, accountability, and safety in technical operations.

• Plant gaps in the brownfield: Historical documents, inspection reports, modifications, and technical notes are often scattered across different systems, folders, or personal archives. Critical components thus remain invisible in the data chaos. We deliberately focus on "ADAM-First" and brownfield-native with ADAM: Existing data does not need to be cleaned up for years first. Through hybrid search and vector search, documents, reports, and technical connections can be found and assigned to an asset even with inconsistent designations. This gradually creates a common, plant-centered information base.
• Documentation obligation meets poor user experience: Maintenance workers know that feedback is important. In everyday life, however, quality often fails due to complicated forms, time pressure, and lack of acceptance. ADAM complements existing systems like SAP as an intelligent SaaS and UX layer. Reports, observations, and work feedback can be captured by voice, structured by AI, and transferred to the target system. "Machine checked" becomes usable feedback with asset, findings, measures, and context. ADAM does not replace legal review or audit-proof archiving strategy but creates the basis for more complete and traceable operational data.
• Retrofits without reliable history: In older plants, it is often unclear when safety-relevant components were installed, inspected, modified, or replaced. Decisions about continued operation, replacement measures, or retrofit are thus unnecessarily difficult. With the Digital Lifecycle Record, ADAM bundles inspections, photos, documents, risk assessments, approvals, and measures taken chronologically at the respective machine. No-code workflows can also map escalations, reminders, and defined approval processes. This turns a one-time gap analysis into a permanently usable operational process.

Conclusion: Responsibility should not only become visible after an accident – ADAM creates the digital foundation to make technical risks, decisions, and measures transparent and actionable during ongoing operations.