You closed last month's maintenance. A leak, a door that would not latch, a heat complaint that turned out to be a thermostat: each was reported, sent to someone you trust, and finished. Now a demo, a consultant, or an owner's RFP has asked which CMMS you run, with the suggestion that a portfolio your size ought to have one.

It is a reasonable thing to wonder. Maintenance is the part of the operation that feels least finished, and a computerized maintenance management system sounds like the cure by name alone. What the name leaves out is what the system is organized around. A CMMS was built for plants, hospitals, and campuses, and it files everything under a piece of equipment: the work order, the history, the manual, the spare part. The US Department of Energy's Operations & Maintenance Best Practices guide, written for federal facility managers, lists what a typical CMMS does, and the phrase that keeps returning in that list is "by component."

Your work does not arrive by component. It arrives from a person who lives in the building, about a room, in their own words. The record you need afterward is who reported what, who went, what it cost, and whether the resident heard back.

So a second system begins with homework. Before it can hold one job the way it was designed to, it wants the register: every boiler, pump, and fan coil entered, tagged, and kept current. And once it is running, each repair lives in three places. The resident's request and your replies are in email. The job is in the CMMS. The contractor's bill is in the accounting system. All three records are true, and the story of the repair exists only when someone lines them up.

The same federal guide says it to buyers directly: "feature overload" is a common complaint of active CMMS users. That is the cost that never appears on the quote. It is a second place to record every job, on screens built around equipment you do not run.

A plant's work order starts at a machine. Yours starts with a person.

Handled the other way around, the request is the record. The resident's message opens it, the work order hangs from it, the contractor's replies land on it, and the bill attaches to it, so the repair reads top to bottom in one place. The seasonal work stops living in a calendar reminder: the boiler service is a schedule that files its own work order on its date, with the contractor already named. The question about a CMMS gets smaller, too. It becomes which of its jobs your buildings have, and for most residential portfolios the list is short: requests, work orders, recurring service, and a bench of contractors.

Scaalr keeps those four in the same system as the leases and the books: each resident request is a case, the work order links to it, recurring work orders file themselves on the schedule you set, and the contractor directory holds your bench in the order you ranked it. Which CMMS functions a residential portfolio has, the four conditions that do call for one, and five checks to run on your own work orders are in CMMS for Residential Property Management: Do You Need One?.

For the full breakdown of what a CMMS does and when a residential portfolio needs one, see: CMMS for Residential Property Management: Do You Need One?.

The first 5 units are free, then $0.99 a unit a month, and work orders and recurring schedules are on every plan.

← Previous: The Number That Changes at the Border All insights →