Selecting a CMMS is one of the few software decisions a facility manager can expect to live with for a decade. The wrong choice shows up every day in lost technician time, brittle reports, and vendor lock-in that survives staff turnover. The right choice becomes invisible because technicians and supervisors just use it. Getting to the right choice is not a matter of flashy demos; it is a structured process with a defensible requirements document, disciplined evaluations, and real reference calls.
The International Facility Management Association’s North America Operations and Maintenance Benchmarking Report covers roughly 40,000 buildings and 2.2 billion gross square feet, with a widely cited median O&M cost near $5.59 per rentable square foot. For a mid-sized portfolio, that is a seven or eight-figure annual spend, and the CMMS selection decision has a direct influence on how much of it is spent well. ARC Advisory Group’s enterprise asset management market research provides useful neutral sizing when a facility manager needs to build the business case against peer benchmarks.
Start With the Operating Model, Not the Software
The biggest selection mistake is shopping for software before defining the operating model. A facility manager should walk into the first vendor demo with clear answers to:
- How many buildings, what square footage, and what equipment classes are in scope
- How many technicians and contractors will use the system, and on what devices
- What integrations are mandatory (ERP, HR, BAS, access control, tenant portals, energy reporting)
- What metrics will be reported weekly, monthly, quarterly, and by whom
- What regulatory regimes apply (ASHRAE 180, NFPA 25, local jurisdictional inspections)
Those answers become the requirements document. Without them, every vendor looks equally good and the decision defaults to the most polished demo.
The Structured Selection Process
A defensible selection follows six phases.
1. Requirements Document
Write 30 to 50 “must have”, “should have”, and “nice to have” requirements tied to the operating model above. Every requirement should be specific enough that a vendor’s answer is verifiable.
2. Long List to Short List
Invite five to eight vendors to a first-round demo driven by a scripted use case (not their deck). Narrow to three finalists based on fit to the requirements, not on rapport.
3. Scripted Finalist Demos
Send each finalist the same script: create five work orders against your actual equipment, generate a PM from a runtime meter, close a work order with parts and labor, pull a monthly compliance report. Vendors who ad-lib the script are telling you something.
4. Hands-On Pilot
Do a two to four week pilot with 10 to 20 technicians in one building. Pay the vendors for their pilot setup time. The pilot surfaces issues that no demo reveals.
5. Reference Calls
Three to five customers, chosen by you from the vendor’s customer list, not handed to you. Focus reference calls on implementation reality, data-migration pain, and ongoing support responsiveness.
6. Commercial and Contract
Negotiate pricing on a per-user and per-asset basis, lock in data-export rights, and require a documented SLA. Legal and procurement should be involved from the start of this phase.
Features That Earn Their Place in the Requirements Document
Among the feature set, a small number of capabilities separate a usable CMMS from an expensive logging tool.
- Mobile-first work order management, including full closure workflows
- A proper asset management module with hierarchy, criticality, and history
- PM trigger logic supporting calendar, runtime, and condition-based intervals
- Parts and inventory with reservation against work orders
- Role-based access control tied to SSO
- Integration surface (REST API, BAS protocols, ERP connectors)
- Analytics that match the KPI list from your operating model
Typical Outcomes From a Well-Run Selection
Facility management organizations that run a structured selection commonly report:
- Implementation timeline shorter by 20 to 40 percent than an ad-hoc selection
- Technician adoption above 80 percent within the first quarter of rollout
- Fewer change orders and scope surprises after contract signature
- Lower total cost of ownership over five years because the contract terms were written tightly
- Better portfolio reporting because the requirements document forced early clarity
The Facility Management Reality
A facility manager’s CMMS selection is different from a plant’s in two ways. First, commercial buildings run on contractors more than on in-house technicians, so contractor management, scope-of-work enforcement, and vendor sign-off matter more. Second, tenant and occupant communication is a real requirement; a CMMS that cannot ingest tenant service requests becomes a shadow system beside the ticketing platform. Both realities should shape the shortlist. The operating context is the same facility management discipline a portfolio owner already runs, and the CMMS has to fit it, not the other way around. For the harder question of rollout, see challenges and solutions in CMMS adoption.
Frequently Asked Questions
How long should a selection take? Four to six months for a mid-sized portfolio, from requirements document to signed contract. Compressing the timeline usually means skipping the pilot, which is the single biggest risk reduction step.
Should we hire a consultant? For organizations without prior CMMS selection experience, yes. A consultant who is vendor-neutral and has run multiple selections can accelerate the requirements document and avoid common traps. Beware consultants who are visibly affiliated with a specific vendor.
What is the most overrated feature? Pre-built industry templates. Every portfolio customizes the template within weeks; the starting shape is less important than the underlying data model.
What is the most underrated feature? Bulk data edit capabilities. Cleaning and maintaining an asset register of 5,000 or 50,000 items requires solid bulk tooling.
How do we avoid vendor lock-in? Require data export rights in the contract, verify them during the pilot, and make sure the data model is documented. Every CMMS has some lock-in; the goal is for the exit cost to be bounded.
A structured selection process is how a facility manager turns a decade-long decision into a defensible one. Book a Task360 demo to see what a CMMS evaluation against real requirements looks like.
