From a clean representation of the entire plant in SAP to the daily execution of the work backlog: I support plants and sites with structure, processes, roles, rollout, stabilization and training – practical from a maintenance and shopfloor perspective, not only from theory.
Clean structure, clear processes and practical ways of working – from the site model to daily execution.
I bridge the gap between operational reality and SAP project logic.
Training exactly as the plant needs it: clear, practical and directly usable.
Examples of topics that plants commonly need – structured clearly and explained in a practical way.
A pragmatic path that becomes usable quickly and grows with your operations.
Short assessment of structure, roles, working methods, ticket/order situation and typical bottlenecks. Goal: a realistic target picture.
Set functional locations, equipment logic, naming, statuses, mandatory fields, notification types, order types and simple standards.
Structure the work backlog (e.g. IW28), agree filters/views, define responsibilities and make daily execution manageable.
Role-based training (supervisors, maintenance, planning, QM, leadership) with real plant examples and clear checklists.
Add recurring maintenance, KPIs, spare parts/MRO, QM integration and further areas step by step – without project overhead.
Helpful for decision makers and good for SEO: clear answers to real practical questions.
No. Training also works without a running SAP system. In that case the focus is on structure, roles, process logic, notifications and work order flow, and preparing the team for a later rollout or stabilization.
Yes. That is often the most important starting point. A clean asset structure with clear numbering and equipment assignments is the basis for usable PM/QM processes and reliable reporting.
Yes. A key focus is the interface between operational practice and SAP consulting: define requirements clearly, derive test cases, support go-live and reduce misunderstandings.
Yes. The approach is intentionally step by step: first make structure and daily work usable, then expand gradually. This creates visible value quickly without a long-running big project.
If you want to set up, stabilize or digitally improve a plant or site in a pragmatic way, send me a short note with your goal (e.g. structure setup, IW28 work backlog, recurring maintenance, QM integration, training).