An Integrated Workplace Management System, or IWMS, should form the operational and strategic backbone for real estate and building management. In theory, space planning, maintenance, energy, and leasing converge on a central database. In practice, companies spend millions on a software suite that ultimately becomes a nicely packaged data silo The reason is almost always the same: integration into the existing ERP and MEP environment is massively underestimated. This article, free of marketing jargon, shows which core functions an IWMS must truly deliver, where the real difference to CAFM lies, and with which tough checklist you can thoroughly dissect vendors in a pitch.
1. Der Unterschied: Warum ein IWMS mehr ist als ein CAFM
Let's leave the buzzwords behind. Classic CAFM handles operations. That means maintenance, space management, and tickets. A CMMS is the workbench for the technician. An IWMS bundles both and adds the commercial strategy on top: contract management, portfolio lifecycle, and ESG reporting.
The danger is obvious. Many CAFM providers simply slap an IWMS label on themselves today because they've bought an additional leasing module. This looks like progress in the brochure. In everyday life, it's often just a deceptive label with slightly better branding. If your selection criterion ends up being just a nicely filled Excel list, the project will go wrong. Software can do many things a little bit. When it comes to real CMMS functions, such as complex maintenance intervals for MEP systems, it often breaks down mercilessly.
An IWMS only makes sense if space, maintenance, lease, and ESG workload reside on a single master data model. If the tenant in room 2.04 changes, the system must seamlessly reflect this for ancillary cost accounting, cleaning, and space planning. Anything else is not an integrated platform, but just an expensive detour with a login.
2. Architektur und Schnittstellen: Das Ende der Insellösungen
The decision for an IWMS is not a software decision in the narrow sense. It is an architectural decision for at least ten years. And that's precisely why many tenders fail early on. Functions are requested, but API integrity is ignored. This is roughly like buying a house based on the color of the door handles and checking the structural integrity later.
What must be standard today is clear:
- Standard-APIs: Offene REST-APIs mit OAuth2 sind Pflicht. Fragen Sie nicht nur, ob sie existieren. Lassen Sie sich die Dokumentation zeigen.
- BIM- und CAD-Anbindung: IFC-Exporte müssen Geometrie und Asset-IDs sauber übernehmen. Wer Raum-IDs noch per Hand abgleicht, hat das Projekt schon verloren.
- ERP-Integration: Für Kosten, Buchhaltung und Leasing braucht es eine bidirektionale Schnittstelle. Sonst läuft der Betrieb weiter, nur eben mit mehr Medienbrüchen.
The rule of thumb is tough but simple: Plan 30 to 40 percent of the integration effort directly for data cleansing and ID mapping. Anyone who dumps data garbage from legacy systems unfiltered into the new IWMS is not building a modern system. They build a modern, unusable data silo. This is technically impressive and operationally worthless.
3. TCO und Lizenzierungsfallen
The decision between SaaS and on-premises has long been made in the market. Most providers are clearly moving towards the cloud. While SaaS reduces CapEx, the ongoing OpEx often increases significantly once additional services, API calls, or extensions are added. The final price then often has little to do with the attractive initial license.
Beware of disguised TCO. License costs in the first year often make up only a small part of the total budget. The rest disappears into implementation, migration, and above all, customization. And that's precisely where it gets tricky: providers who nod to every one of your special requests with a quick "Yes, that's possible!" during the pitch are rarely the best partners. Usually, they are just being polite until reality sets in.
Today's customization is tomorrow's upgrade hurdle. What is sold as a small adjustment in the project later blocks every major release. Therefore, it's better to standardize cleanly than to permanently sabotage your own architecture with short-term convenience.
4. Vendor-Snapshot: Was die Großen wirklich können
The providers are not the same. And they are not good at the same problems. Don't look for the market leader in the sponsored quadrant (did you get the pun?). Look for the tool, that solves your specific pain points. That is often significantly less sexy, but also significantly more helpful.
Planon is strong with corporates focusing on workplace and real estate. The architecture is solid. The platform can do a lot. But as soon as customization gets out of hand, projects quickly become expensive and sluggish (which, by the way, applies to most software projects).
IBM TRIRIGA is the heavyweight for large portfolios. Strong in leasing and complex capital projects. For medium-sized businesses, this is usually overkill. It requires not only a budget but almost a small IT army. And can also happen to you with other solutions...
Archibus is the dinosaur with deep roots in CAD and spatial data. It is often proven, especially in municipalities and universities. The weakness for a long time was in the UI and UX area. While other providers were already shining with cloud solutions, Archibus sometimes still felt like a very well-intentioned administrative process with a login. But that has already improved a lot, hasn't it?
5. Die Checkliste für den Pitch
Don't believe any PowerPoint slide. Really no one. A checklist is only useful if you demand proof. Otherwise, you'll sit in the pitch room and only hear very confident statements about "end-to-end capability" and "seamless processes". Sounds good. But doesn't help.
- Sandbox-Schocktest: Geben Sie dem Anbieter 500 Ihrer eigenen, unbereinigten Assets und 200 Räume als Excel- oder IFC-Datei. Kann er das in fünf Tagen in seine Sandbox importieren und ein funktionierendes Mapping vorführen? Wenn nicht, ziehen Sie Konsequenzen.
- API-Beweis: Verlangen Sie eine Postman-Collection für die Synchronisation mit Ihrem ERP-System (der Anbieter wird wissen, was er liefern müsste).
- Upgrade-Policy: Lassen Sie sich vertraglich absichern, was mit Ihren angepassten Workflows bei einem Major-Update passiert. Und wer die Anpassung bezahlt (am Besten nicht Sie).
- Referenzen: Fragen Sie nicht nach einer Kundenliste. Fragen Sie nach zwei Kunden aus Ihrer Branche und sprechen Sie ohne Vertrieb mit deren FM-Leitung. Und am Besten noch mit jemandem aus dem operativen Team.
- Change-Request-Cap: Deckeln Sie die Kosten für Change Requests im Vertrag, sonst bluten Sie in der Betriebsphase finanziell aus.
The tender must cover three typical operational scenarios. For example, automated ancillary cost billing, relocation planning with BIM, and IoT-controlled maintenance triggers. Have the providers demonstrate these scenarios live (!) and on demand during the demo. Those who struggle will not suddenly appear elegant in real operation.
Don't buy features for stock. Buy integration capability and master data rigor. Only then will a software purchase become real operational added value.
