CMMS for Facilities Management

A facilities manager searching for facility management software almost always types "CMMS" first, because maintenance is the loudest part of the job and the part with the most obvious backlog. That instinct is not wrong. The trouble starts about nine months later, when the same operation discovers that cleaning audits, security patrols, waste collection, helpdesk tickets that are not maintenance at all, tenant SLA reports, contractor invoices and a request from finance for occupancy data are all still living in spreadsheets, because none of them fit the work order table. That gap is not a configuration failure. It is the boundary of the product category, and it is worth understanding before you sign rather than after.

The message up front: a CMMS manages maintenance on assets. Facilities management is a wider operation that includes maintenance plus soft services, statutory compliance evidence, client SLA reporting, subcontractor management, a helpdesk with non-maintenance demand, and space. If your scope is hard services on assets you own and occupy, a good CMMS is enough and CAFM is overspend. If you deliver a contracted service to a client or landlord across multiple buildings with soft services and deductible SLAs, a CMMS will hold roughly half your operation and you will build the other half in Excel. That is the threshold.

1. The FM scope is much wider than maintenance

The single most useful exercise before any software decision is to write down everything your facilities function is actually accountable for, without filtering it through what you assume software can do. When I run this with FM teams the list is consistently far longer than the maintenance backlog that triggered the search. A typical mid-size operation is accountable for:

• Hard services: HVAC, electrical, plumbing, lifts, fire and life safety, generators, BMS, pumps, civil fabric. Asset-based, PM-driven, failure-coded. Classic CMMS territory, and the part every product does well.
• Soft services: cleaning, security and manned guarding, landscaping, pest control, waste, catering, front-of-house, mailroom, porterage. Almost none of it asset-based; much of it area-based, headcount-based or schedule-based.
• Helpdesk: one intake point for everything from a broken door closer to a meeting-room booking to a desk move. A large share of FM helpdesk demand is not a maintenance work order at all.
• Statutory compliance: fire safety, lift inspection, pressure systems, water hygiene, fixed-wire testing, emergency lighting, lifting equipment. Each with a certificate, an expiry, an inspecting authority and an audit trail.
• Space and occupancy: floor plans, room inventory, allocation by department or tenant, occupancy measurement, chargeback, and the moves, adds and changes process.
• Visitors and access: pre-registration, contractor induction, permits to work, key and access control administration.
• Commercial administration: subcontractor scopes, service levels, measured deductions, purchase orders, invoice verification, variations.
• Reporting: monthly service reports to a client, landlord, board or tenant committee, usually with contractual consequences attached.

A CMMS, by design and by honest vendor description, addresses the first item on that list thoroughly and touches parts of the third and fourth. It is not built for the rest. That is not a criticism of CMMS products; it is what the category is. The mistake is assuming the remainder will be absorbed by configuration. For the formal category boundaries between CMMS, CAFM, EAM and IWMS I will not repeat here, see the CAFM vs CMMS vs EAM vs IWMS pillar. If you are still working out what a CMMS is in the first place, start with the buyer's introduction to CMMS.

2. What each category actually covers

Rather than argue about definitions, it is more useful to map the FM scope against the three product categories and be blunt about where each one starts to strain. The table below is the version I sketch on a whiteboard in most scoping workshops. "Partial" means the function can be forced into the product with custom fields and workarounds, but it will not be a native model and it will not report cleanly.

Read that table by row count rather than by feature ticks. If the rows that matter to you cluster in the top six, buy a CMMS and stop reading vendor IWMS brochures. If they spread across the middle block, you are a CAFM buyer whether or not your budget request says CMMS. If you have lease administration and property accounting in scope, you are an IWMS or a real-estate systems conversation, and the maintenance module is the smaller half of the project.

3. Hard versus soft services: why the work order model breaks

This is the most under-appreciated technical reason a CMMS struggles in an FM context. A CMMS work order is fundamentally a record of work performed on an asset: the data model assumes an asset identity, a task or failure against it, a cost attributable to it, and a history that accumulates per asset so reliability can be analysed. That model is correct for hard services. Soft services do not have that shape:

• Cleaning is performed on an area, not an asset. The unit of work is a zone, a frequency and a quality standard, and the output is an audit score against a specification rather than a repaired asset. Forcing each washroom into the asset register as an "asset" so a cleaning PM can be raised against it is a workaround I have seen many times, and it pollutes the register and makes reliability reporting meaningless.
• Security is a presence and a patrol, measured in posts covered, shifts filled, patrol points scanned and incidents logged. A guard roster is a workforce scheduling problem, not a work order problem.
• Waste is a volume, a stream, a collection frequency and a disposal certificate chain, reported as tonnage by stream and diversion rate, which no CMMS reporting model expresses.
• Landscaping, pest control, front of house and porterage are seasonal or demand-driven service tasks with treatment records or response-time expectations but no asset and often no technical work content.

CAFM products model these natively: they carry a location and space structure that is a first-class entity alongside the asset register, they support task types that attach to a location or a service line rather than an asset, and their scheduling engine handles recurring area-based rounds and roster patterns as well as asset PMs. If soft services are in your scope and you buy a CMMS, you will either run them outside the system or degrade the system to accommodate them. Both are real costs. For how the work order object itself differentiates, see the work order types pillar.

4. The multi-building, multi-tenant, multi-contract reality

A single industrial plant has one site, one operator, one budget and one reporting line. An FM operation typically has none of those simplifications. The structural realities that break single-site CMMS assumptions are:

• Multiple buildings with different ages, systems and standards. The system needs a location hierarchy deep enough to express portfolio, site, building, floor, zone, room, with the asset hanging off the room. Many lightweight CMMS products offer two or three location levels and expect the rest to live in a text field.
• Multiple tenants within one building. Requests must be attributable to a tenant, chargeable work separable from base-building work, and tenant A must never see tenant B's tickets. That is data segregation, not a permissions preference.
• Multiple contracts covering overlapping scope. Work orders need to be born knowing which contract governs them, because response times, deductions and invoicing all derive from the contract, not from the asset.
• Multiple cost centres and funding routes. Planned work from an operating budget, reactive from a different pot, tenant chargeable work billed out, landlord capital work approved separately.
• Different calendars and coverage. A hospital wing, a retail mall and a commercial tower in one portfolio have different access windows, critical hours and escalation rules.

The architecture question underneath all of this, single instance with segregation versus separate instances per client or site, is genuinely consequential and I have written it up separately in the multi-site CAFM architecture pillar. What matters for the CMMS-versus-CAFM decision is simpler: ask any shortlisted product to demonstrate a work order that belongs simultaneously to a building, a tenant, a contract and a cost centre, with reporting that rolls up cleanly on all four dimensions. Products built for a single plant will struggle with that demonstration, and the struggle will be informative.

5. Statutory compliance and the evidence trail

In industrial maintenance, compliance is one obligation among many. In facilities management, particularly in buildings occupied by the public, compliance is often the reason the FM function exists at all, and the evidence trail is the deliverable. If a lift injures someone or a fire system fails, the question is not whether you did the maintenance, it is whether you can produce the certificate, the competent person's record, the remedial closure and the date chain, on demand, years later. That imposes requirements a maintenance module does not naturally meet:

• Compliance as its own register, not a PM side effect. A list of statutory obligations per building, each with a legal basis, a frequency, a responsible competent person or inspecting body, a current status and an expiry date. A completed PM work order does not answer "is this building compliant today".
• Certificate and document custody. Inspection certificates, test sheets, calibration records and water sample results, attached to the obligation and retrievable by building, by system and by date range.
• Remedial tracking with a closure loop. Open remedials against a statutory inspection are the single most common audit finding I see, and they are usually open because the defect was recorded in an inspection report PDF and never became a work order.
• Forward-looking expiry visibility. The useful report is not what was done, it is what expires in the next ninety days and what is already lapsed.
• Immutable audit history, including the ability to reconstruct the compliance position at a past date, because that is the date an incident will have occurred on.

Mature CAFM products treat compliance as a first-class module for exactly these reasons. Better CMMS products handle it adequately where the obligation set is narrow and the buildings few, expressing each obligation as a PM with a document attachment plus discipline about closing remedials. It falls down at portfolio scale and under audit, where the question becomes a cross-building compliance position rather than a work order history. Fire and life safety is the clearest example, covered in the lift, fire and life safety PM pillar. On standards, the FM management-system framing most client contracts now reference sits in the ISO 41000 family from ISO , and building services task content is most commonly specified against SFG20 .

6. SLA and KPI reporting when a client is watching

An in-house maintenance team reports KPIs to management, who are on the same side of the table. An FM service provider reports KPIs to a client who has a contractual right to withhold money based on them. That difference changes the software requirement fundamentally, and it is the requirement most commonly discovered too late.

What contractual SLA reporting demands from the system:

• Priority and response definitions held as contract data. Priority 1 means two hours in the tower and four hours in the warehouse because the contracts say so. The response clock must be driven by the governing contract and asset criticality, not by a single global priority table.
• Clock rules that match the contract wording. Does the clock start at report or at acceptance? Does it run overnight or only in coverage hours? Does it pause awaiting client access, parts or a tenant appointment? Each is negotiated in the contract and each must be configurable, because an ungoverned clock produces numbers your client will reject.
• Attendance and rectification measured separately. Most FM contracts measure time to attend and time to complete as distinct obligations. Products recording only a completion timestamp cannot report the contract.
• Deduction calculation with an auditable trail. The system needs to compute the exposure, show the underlying failed tickets, and let both sides interrogate exclusions. Reporting deductions from a spreadsheet built off a CSV export is how commercial disputes start.
• Client-facing reporting they trust. Ideally the client sees the same live data you do, rather than receiving a monthly deck they suspect has been curated.

The design of the priority and response matrix that sits underneath all of this deserves its own treatment, and the SLA matrix design pillar covers it properly. For the wider measurement set beyond SLA compliance, the FM KPI framework pillar is the companion piece.

7. Service provider versus in-house team: it changes the data model

This is the question I ask first in any FM software scoping conversation, because the answer reorganises everything downstream. Are you an in-house facilities team maintaining property your organisation occupies, or a service provider delivering a contracted service to third-party clients?

For an in-house team the world is relatively simple: one organisation, buildings you control, internal customers, budget accountability rather than commercial exposure, and KPIs used for improvement rather than payment. The data model is site, building, asset, work order, cost centre. A good CMMS fits that shape well, and a great many in-house FM teams are over-served by CAFM. For a service provider, several new first-class entities appear that a CMMS does not have:

• Client as an entity above site, with its own contacts, reporting, commercial terms and visibility boundary.
• Contract as an entity that governs scope, term, service levels, deduction regime, rate card, and what is included versus chargeable as an extra.
• Chargeability on every work order: in-scope, chargeable extra, warranty, or subcontractor liability. This determines whether the job generates revenue or consumes margin, and it must be decided at creation and verified at closure.
• Rate card and applied rates so a chargeable job values itself for invoicing, with different rates by trade, hours band and client.
• Margin visibility per contract, which is the number the operations director actually manages. Work order cost needs to aggregate to contract profitability, not just asset lifecycle cost.
• Mobilisation and demobilisation: standing up a new client contract quickly with its asset register, PM programme, SLAs and portal, and exiting one cleanly with the data handed over.

None of those six exist natively in a maintenance management system, because such a system was designed for an organisation maintaining its own equipment. As a service provider you will either buy CAFM or build a commercial layer around your CMMS in spreadsheets and finance systems, and I have watched that second path consume more effort over three years than the CAFM licence difference would have cost. Property and real-estate portfolio operators have a related but distinct set of requirements, covered in the CMMS for property and real estate portfolios pillar.

8. Subcontractor management, the part most systems handle badly

In an FM operation a large proportion of the work is not done by your own labour. Specialist trades, statutory inspection bodies, manufacturer service contracts and general contractors deliver a substantial share of the scope, and your client holds you accountable for all of it. The system requirements this generates are specific:

• Allocation with a real handover. Issuing a work order to a subcontractor is a transfer of responsibility with a scope, a target time and an acceptance, not a status change. The SLA clock keeps running against you regardless of who holds the job.
• Subcontractor access without full system access. They see their jobs, update progress, upload evidence and close out, and see nothing else. A portal or restricted mobile role, not a full user licence and not an email thread.
• Compliance documents with expiry enforcement. Insurance, trade licences, competency certificates, method statements and risk assessments, with the system preventing allocation to a subcontractor whose documents have lapsed. This one control prevents a serious class of incident.
• Permit and induction linkage. High-risk work needs a permit issued and closed against the job, and induction status verified before attendance.
• Performance measurement per subcontractor: response, rectification, first-time fix, rework and document compliance, so renewal conversations are evidence-based and their failures against your client SLA are attributable.
• Commercial reconciliation. Their invoice matched against the work orders they completed, at contract rates, with deduction where they missed target.

Very few CMMS products cover more than the first two of those. Most treat a subcontractor as a labour resource type with a vendor name attached, which is adequate for a plant that occasionally calls in a specialist and inadequate for an FM operation where forty per cent of the scope flows through third parties. CAFM products, having grown up in the service provider market, generally handle the middle four properly. This is one of the clearest single-feature reasons an FM operation outgrows a CMMS.

9. The helpdesk and the requester portal

Ask a building occupant what the facilities department is and they will describe the helpdesk, because it is the only part of the operation they touch. That makes the intake layer disproportionately important to how the FM function is perceived, and it is another place where CMMS and CAFM diverge.

A CMMS request portal is built on one assumption: the requester is reporting a fault on an asset or in a location, and the output is a maintenance work order. That covers a good share of demand. It does not cover the rest of what arrives at an FM helpdesk:

• Service requests with no fault and no asset: a room needs setting up, a delivery escorting, extra cleaning after an event.
• Environmental complaints that are a comfort perception rather than a defect, needing triage, a measurement and an explanation rather than a repair.
• Bookings: rooms, desks, parking, loading bays, lifts for a move.
• Access and visitor requests: a contractor arriving Tuesday, a card for a new starter, a plant room key.
• Move requests, and information requests or complaints that need a tracked response with an SLA of their own but produce no work order at all.

A CAFM helpdesk models request type as a configurable object with its own form, routing, approval and SLA, and only some request types become work orders. That is the structural difference: in CAFM the ticket and the work order are separate things with a relationship, whereas in most CMMS products the request is simply an embryonic work order. Once you understand that distinction the behaviour of each product makes sense, and you can predict which one will cope with your intake mix. The portal design considerations in detail, including the self-service traps, are in the maintenance request portals pillar.

10. Space, occupancy and moves: the hard CAFM boundary

Everything so far has been a question of degree: a CMMS does it partially, a CAFM does it natively. Space is different, because it is a genuine architectural boundary rather than a maturity gap. A CMMS has locations as labels in a hierarchy. CAFM and IWMS have space as a measured, geometric, allocatable entity.

What space management as a capability actually requires:

• A space inventory with measured areas, classified by type and usable versus gross, reconciled to a floor plan and maintained as a system of record rather than a drawing in a folder.
• Drawing integration, CAD, IFC or BIM-derived, so the polygon on the plan and the room record are the same object.
• Allocation of space to department, cost centre, tenant or individual, the basis of any chargeback model.
• Occupancy data from headcount, badge data or sensors, and the vacancy and utilisation analysis that follows.
• A moves workflow, where relocating forty people becomes a scheduled programme generating porterage, IT, cleaning, furniture and access tasks, then updates allocation records on completion.

No CMMS does this, and none claims to. So the rule is clean: if space, occupancy or moves is in scope with any seriousness, the CMMS conversation is over and you are choosing between CAFM and IWMS. The related judgement is honesty about whether it really is in scope. Many FM teams list space management as a requirement, buy a product with a space module, and never populate it because nobody owns the floor plans and nobody has budget to survey the portfolio. An unpopulated space module is worse than none, because it created cost and an expectation and delivers neither. If you cannot name the person who will own space data and where the areas will come from, treat it as a future phase.

11. The threshold: when a CMMS stops being enough

Here is the decision in the form I would actually use it. Work down the table, count the rows where the right-hand column describes you, and the pattern will be obvious well before the end.

My rule of thumb after many of these conversations: two or three rows on the right is not a reason to change category, it is a reason to choose a strong CMMS with good location depth, decent document handling and an open API, and to accept two managed workarounds. Five or more rows on the right, and particularly any single row involving client contracts with deductions or space as a live requirement, means you are a CAFM buyer and buying a CMMS will cost you more in workaround effort and commercial risk than the licence saving is worth. For a second cut at the same decision from the category side, see which of CAFM, CMMS or EAM is right for you.

12. CMMS, CAFM or IWMS: deciding for an FM operation

Reduced to the shortest honest statement of each:

• Buy a CMMS when maintenance is the operation: hard services, your own buildings, your own technicians, internal reporting. You will get a better maintenance experience for less money and a faster implementation, because the product is not carrying modules you will never open. Mid-market products here, MaintainX, Limble, Fiix, eMaint and UpKeep among them, are genuinely good at this and deploy quickly.
• Buy CAFM when you run a facilities service: multiple buildings, soft services alongside hard, subcontractors, mixed helpdesk demand, statutory compliance at portfolio scale, and SLA reporting to somebody who can withhold payment. Planon and similar FM-native platforms grew up in this market and their data model reflects it. I am deliberately not ranking vendors here; the CAFM buyer comparison does that work, and for a smaller organisation the CAFM guide for SMEs is the more proportionate starting point.
• Buy IWMS when the workplace and the real estate are the subject and maintenance is one component: lease administration, portfolio strategy, capital projects, occupancy and workplace experience at enterprise scale, usually driven by corporate real estate rather than FM. These implementations are long and expensive, and they fail when bought by an FM team that needed CAFM.
• Consider EAM instead when the asset base is heavy industrial or infrastructure and lifecycle cost, reliability engineering and capital planning dominate. IBM Maximo, Hexagon EAM, SAP PM and Infor EAM live here. An FM operation rarely needs this depth, and EAM in a facilities context is usually a legacy of a corporate standard rather than a fit-driven choice.

A sequencing note I give more often than any of the above: if your maintenance operation is genuinely broken, fix maintenance first even if CAFM is the eventual destination. A CAFM implementation that tries to fix the asset register, the PM programme, compliance, soft services, the helpdesk and client reporting at once usually stalls, because it has no early win and too many dependent workstreams. Getting assets, PMs and reactive work orders working properly, as in the preventive maintenance guide, gives you a working core to extend from. Phasing is not indecision; it is how these programmes survive.

13. A requirements checklist you can lift

Take this into a scoping session before you talk to any vendor. Answer each line with a yes, a no or a phase number, and the product category falls out of the answers rather than out of a demo.

The idea to walk away with

A CMMS manages maintenance well. Facilities management is bigger than maintenance, and the extra scope is not extra features, it is extra entities: client, contract, service line, space, requester, subcontractor. Those entities either exist in the product's data model or they do not, and no amount of custom fields creates them properly. That is why the CMMS-to-CAFM question is not about size or budget. It is about whether the things your operation is accountable for can be represented natively in the system you are buying.

So decide from the scope inventory, not the demo. If the answer is "mostly hard services, our own buildings, internal reporting", buy a good CMMS and be pleased with how quickly it goes live. If it is "contracted service, mixed portfolio, soft services, deductible SLAs", buy CAFM, phase it sensibly, and start with the maintenance core so you have something working while the rest is configured.

Final thoughts

The most expensive outcome here is not buying the wrong size of system. It is buying the right size for the operation you had and never revisiting it as the operation changed. An in-house team that wins a managed-services mandate, or a single-building operation that inherits a portfolio, has crossed the threshold without any software decision being made, and the workarounds accumulate quietly until the monthly client report takes four days to produce. A scope review every couple of years against the threshold table above catches that drift while it is still cheap to correct.

And plainly: no product in any of these categories compensates for weak operational discipline. Priorities applied inconsistently, work orders closed in batches, compliance remedials living in PDF reports, subcontractor documents never checked. These are the actual causes of most FM reporting problems I am asked to investigate, and they show up identically in a cheap CMMS and an expensive IWMS.

Related reading: CAFM vs CMMS vs EAM vs IWMS, Best CAFM software: buyer comparison, Complete guide to CAFM for SMEs, SLA matrix design for FM operations, FM KPI framework, Multi-site CAFM architecture.