Anyone wanting to buy facility management software needs to compare more than just feature lists; integrations, data quality, GDPR compliance, and TCO ultimately determine success or failure in practice (incidentally, nearly 50% of CAFM projects fail to meet their objectives, but that's just a side note...). This practice-oriented guide walks you step-by-step through needs analysis, prioritization of central modules like maintenance and space management, RFP and demo checklists, as well as contract and implementation criteria. In the end, you'll have an auditable checklist and concrete questions for vendors, enabling you to reliably evaluate shortlists, pilot projects, and the 5-year TCO.
1. Structure the purchasing process: 7-phase checklist
Short and to the point: A structured, phase-oriented procurement process isn't a nice-to-have; it measurably reduces risks when implementing facility management software – especially concerning integration, data migration, and user acceptance. This section provides an immediately applicable 7-phase checklist with clear deliverables, responsibilities, and realistic timeframes for medium to large portfolios.
Phase checklist
- Phase 0 – Scope and needs analysis: Gather FM processes, prioritization criteria, initial cost framework; Deliverable: Project briefing and stakeholder matrix; Responsible: Product Owner FM; Duration: 2-4 weeks.
- Phase 1 – Stakeholder workshop and requirements specification: Define joint scenarios, record compliance and GDPR requirements; Deliverable: Requirements specification agreed with IT security; Responsible: FM + IT; Duration: 1-2 weeks.
- Phase 2 – Requirements catalog and evaluation matrix: Must-have/should-have/nice-to-have features, weighting, KPI definitions; Deliverable: Evaluation matrix for demos; Responsible: Core team; Duration: 1 week.
- Phase 3 – Market analysis and shortlist: Send RFP, coordinate demos using standardized scenarios; Deliverable: Shortlist of 3-5 providers; Responsible: Purchasing + FM; Duration: 4-8 weeks.
- Phase 4 – Pilot / Proof of Concept: Pilot with real master data and mobile operations; Deliverable: Pilot report with migration effort, performance, and acceptance metrics; Responsible: Pilot users + IT; Duration: 6-12 weeks.
- Phase 5 – Contract negotiation and SLA definition: Acceptance criteria, exit clauses, data portability, GDPR clauses; Deliverable: Draft contract with SLAs; Responsible: Purchasing + Legal department; Duration: 2-6 weeks.
- Phase 6 – Rollout and Go-Live: Iterative rollout, training plan, KPI monitoring; Deliverables: Go-live plan, training documents, lessons learned; Responsible: Project management + Change management; Duration: 8-24 weeks (iterative).
- Phase 7 – we started with Phase 0: forgotten already? So the list only goes up to phase six even though we have seven... as I said, the first is phase zero. So this is just for people who can't read properly ;-)
Practical insight: Proof of Concept often focuses on functionality in a clean test environment and underestimates migration and integration risks. A production pilot at two real locations reveals data mapping problems, user workflows, and performance effects early on – and is therefore more expensive, but significantly more informative.
Concrete example: In a medium-sized portfolio with 150 properties, a 10-week pilot showed that master data from the ERP could only be automatically mapped 60 percent of the time. Consequence: 6 weeks of additional ETL effort and adjustment of the interface to SAP before the rollout made sense.
Important: Plan the integration with ERP, BMS, and identity management early in Phase 0 – late interface decisions cause most cost overruns. You will find detailed implementation checklists in the respective sections. Implementation Guide.
Frequently Asked Questions
A brief preliminary note: The questions in tenders and meetings should elicit answers that enable immediate decisions – not general product descriptions. This FAQ focuses on the practical levers that influence facility management software in real projects.
Operational questions
Which core function is truly non-negotiable? A reliable Maintenance management with a documented inspection history, plannable maintenance cycles, and mobile work orders is operationally crucial. Without clean order and inspection logs, KPI calculations and audit requirements fail very quickly.
How to increase acceptance among technicians? Simplicity beats feature-richness. Prioritize a mobile app with offline capability, clear form templates, and short training procedures. Test the UI in a 1-week field test with service technicians before extensive customization.
Technology, integrations, and data
API maturity is more important than architectural labels. Whether cloud, hybrid, or on-premises: in practice, the quality of documented APIs, sandbox environments, and import/export tools determines integration effort and duration. Prefer vendors with tested REST/OPC-UAinterfaces and a clear sandbox for your IT.
Trade-off Cloud vs. On-premises: Cloud accelerates rollout; on-premises provides control. A pragmatic solution is hybrid operation: sensitive data locally, standard functions in the cloud. This avoids unnecessary infrastructure projects and often meets BSI/GDPR requirements.
Contract, cost traps, and exit
Customization costs every year: Heavy customizations reduce upgradeability and drive TCO. Configuring instead of developing is almost always more economical; if development is necessary, limit scope, set ownership deadlines, and anchor upgrade compatibility in the contract.
Check and contractually secure data portability. Request machine-readable exports in CSV, IFC or JSON as well as delivery obligations for historical audit and invoice data. Without an explicit export clause, unfavorable migration costs often arise when changing providers.
Concrete example: A municipal authority lacked an export clause for audit logs; after three years, only PDF reports could be provided. The consequence: an outsourcing project to extract the data, three months of additional migration effort, and extra consulting costs.
- (1) API documentation and sandbox,
- (2) Offline functionality of the mobile app,
- (3) contractually secured data export formats and support for export.
These three points most significantly reduce integration and exit risk.
Practical insight: Many teams underestimate the psychological cost of poor UX more than license prices. Technology should not complicate users' work; this can be quickly identified during pilot phases.
- Step: Request a sandbox demo from the provider with your ERP export and a typical maintenance dataset — test import, mapping, and export.
- Step: Plan a 1-week field test with 5 service technicians to validate the mobile app before signing the contract.
- Step: Include a mandatory data export clause in the contract (machine-readable, standard formats, support period for export).
- Step: In the evaluation matrix, define API maturity, upgrade friendliness of customizations, and local data protection measures as weighted criteria.
And last but not least: relax. Everything will be fine ;-)
