The verdict in three sentences
In a German plant where SAP PM is already the system of record, the expensive mistake is buying a second full CMMS that duplicates asset data and splits the maintenance history. The better question is how to get technicians on the shop floor to log work orders quickly, which a custom mobile layer on top of SAP PM or a lightweight standalone CMMS can both solve. Whatever you pick, the Betriebsrat has a say in it, and involving it early saves months.
Three architectures for a plant that already runs SAP
The figures below are 2026 market ballparks for a Berlin plant with around 900 assets, 11 technicians and 4 planners, excluding VAT.
| Criterion | SAP PM only, with standard mobile add-on | Standalone CMMS synced to SAP | Custom mobile layer on SAP PM |
|---|---|---|---|
| Upfront cost | 30,000 to 80,000 EUR integration partner work | 20,000 to 50,000 EUR setup plus sync | 60,000 to 120,000 EUR |
| Recurring cost | Additional SAP user licences, tariff depends on your contract | 35 to 80 EUR per user per month | Hosting and maintenance: 10 to 15% of build per year |
| Single source of truth | Yes | Two databases to reconcile | Yes, SAP stays the master |
| Technician experience | Often judged heavy on tablets | Usually good | Designed with your technicians |
| Sensor and PLC data | Possible, project-dependent | Varies by vendor | Built for your protocols |
| Time to go live | 4 to 8 months | 3 to 5 months | 4 to 7 months |
The standalone CMMS looks cheapest, yet the two-way sync with SAP (asset master, cost centres, spare parts, notifications) is where projects overrun. If finance relies on SAP for maintenance cost reporting, a custom layer that writes directly into SAP PM through its standard interfaces is usually the cleaner long-term choice.
The works council and data protection
Under section 87(1) no. 6 of the German Works Constitution Act (BetrVG), the works council has co-determination rights over technical systems capable of monitoring employee behaviour or performance. A CMMS that records who closed which work order, and when, falls into that scope. In practice you need a works agreement (Betriebsvereinbarung) describing which data is collected, who can see it and what it may not be used for. Add the GDPR on top, with a data protection impact assessment if location or detailed time tracking is involved.
| Step | When | Typical duration |
|---|---|---|
| Inform the works council of the project | During scoping | 1 to 2 weeks |
| Share data fields and role permissions | Before development | 2 to 4 weeks of discussion |
| Sign the works agreement | Before pilot | 4 to 10 weeks depending on the plant |
| Pilot on one production line | After signature | 6 to 8 weeks |
| Plant-wide rollout | After pilot review | 4 to 6 weeks |
Plants that treat this as paperwork at the end often lose a full quarter. Plants that bring a works council member into the design workshops tend to sign faster, because the anonymised reporting is designed in rather than bolted on.
Targets that justify the spend
Set a baseline first: share of preventive hours, MTBF on the 40 most critical assets, availability per line and average response time. A realistic 12-month goal is 30% more preventive work, a 10 to 20% rise in MTBF on critical assets and two to three points of availability. As a nearshore option for the mobile layer, Kolonell's prices for a complex application start at 10,670 EUR (7,000,000 FCFA) and can exceed 22,870 EUR (15,000,000 FCFA) depending on scope; the SAP integration itself usually stays with your SAP partner.
Mini case study
Illustrative example: Jonas, head of maintenance at a 900-asset packaging plant in Berlin, with 11 technicians.
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
- Choice: a custom mobile layer on SAP PM at 85,000 EUR, plus 10,000 EUR of SAP partner work.
- Running cost: 12% of the build, or 10,200 EUR per year.
- Unplanned downtime: 150 hours a year at 2,000 EUR per hour; 35 hours avoided saves 70,000 EUR per year.
- Admin time: each technician saves 25 minutes a day, about 1,000 hours a year, redeployed to preventive tasks.
- Net first-year gain: 70,000 minus 10,200, or 59,800 EUR.
- Payback: 95,000 divided by 59,800, or about 19 months.
A standalone CMMS would have cost 35,000 EUR upfront, but Jonas estimated 25,000 EUR of extra sync work and a permanent reconciliation effort, and finance refused a second asset register.
FAQ
What does a custom CMMS cost for a Berlin plant in 2026?
A 2026 market estimate is 60,000 to 120,000 EUR for a mobile layer on SAP PM, and more for a full standalone system. Add 10 to 15% a year for hosting and maintenance.
Is an off-the-shelf CMMS always cheaper?
Upfront, usually: 20,000 to 50,000 EUR plus 35 to 80 EUR per user per month. Over 5 years with SAP sync costs, the gap often shrinks to under 20%.
Do we need works council approval for a CMMS?
If the system can track individual technicians' activity, section 87(1) no. 6 BetrVG gives the works council co-determination rights. Plan 4 to 10 weeks for a works agreement.
Can sensor data trigger work orders automatically?
Yes, condition thresholds on vibration or temperature can create SAP PM notifications. Start with 20 to 50 critical assets before scaling.
How long until technicians actually use it?
With a tablet interface designed in workshops, adoption above 90% within 3 months is a realistic target. Heavy screens and double entry are the main reasons usage collapses.
Let's scope your project. Share your asset count, your SAP setup and your target go-live date, and we will price the mobile layer module by module with a delivery plan in weeks. Detailed quote within 48 h. WhatsApp +221 77 596 93 33.
Mohamed Bah
Fondateur, Kolonell
Passionate about digital and entrepreneurship in Africa, Mohamed has been helping Sénégalese businesses with their digital transformation since 2020. Founder of Kolonell, he believes every SME deserves a professional and accessible online présence.
