How to organize maintenance for a building

Building maintenance doesn’t look much like industrial maintenance. There’s no production line to stop: there are people using the building, installations that have to work without anyone noticing them, and a set of regulatory obligations the owner doesn’t get to decide on.

And there’s a fundamental difference: almost everything is carried out by outside companies, so what the person in charge manages isn’t so much the work itself as coordination and proof that it happened.

The inventory, by system

The first thing, and the one that almost never exists: a reliable list of what needs maintaining.

A building isn’t inventoried as loose objects — it’s inventoried by systems: HVAC, electrical and backup power, cold and domestic hot water, fire protection, vertical transport, access control, building envelope and roof.

In asset management equipment is grouped by system, family, and model, and hangs off its address. Each one has its model, serial number, installation date, warranty end date, location — floor and zone — and its priority.

That classification isn’t bureaucracy: it’s what lets you define the check for a type of equipment once and apply it to the thirty units you have, and what lets you later answer by system when ownership asks.

What’s mandatory, which is half the plan

A good part of building maintenance isn’t decided by anyone: it’s set by a standard. Low-voltage electrical installations, fire protection, elevators, boiler rooms, thermal installations, domestic water.

It’s worth knowing this before looking for it in the menu: legal maintenance is not a module in GMAO Cloud. It’s done with the general preventive maintenance mechanism: the checklist the standard requires is attached to the asset, its model, or its family, with its frequency, and the system generates work orders on its own.

A single asset can carry several periods at once: the monthly check is one thing and the annual inspection with a certifying body is another.

The proof comes from the order history, completed checklists with their recorded values, and documentation with its dates. The software records and proves; the owner is the one who answers to the inspection.

The contractors, who are the operation

One per specialty: HVAC, elevators, fire safety, electrical, cleaning, landscaping. If each one keeps its own reports in its own system, whoever is responsible for the building has invoices but no file.

Suppliers get registered and receive the orders that correspond to them, with their times, material, documentation, and signature, so everything ends up in the same history. Since licenses are unlimited across all three plans, registering every contractor isn’t a budgetary decision. And there’s a two-way connector between GMAO Cloud installations for when the contractor uses it too.

The annual plan completion report then answers the question that justifies each contract: how many interventions were scheduled and how many actually happened.

Letting the building’s users raise the alert

The person who spots the problem works or lives there — it’s not maintenance staff.

An alert can be logged from the backend, from a dedicated access point with a description and photo, or from a mailbox the system converts into incidents. With its type, priority, zone, and affected equipment, and with a maximum time per status so that what’s overdue is visible.

If the building has several types of users — tenants, departments, communities — each one can have their own access to track their own items without calling the office.

Expiration dates

Official inspection certificates, maintenance contracts, insurance policies, licenses, inspection records, projects, and drawings.

The document manager hangs them off the building, the asset, the contractor, or the order, decides who sees them, and gives them an expiration date, with a daily check for what’s about to expire and its corresponding alert. Certificates carry their number, scope, issuer, and holder.

In a building, that alert is what prevents the problem money can’t fix: a mandatory inspection that lapsed and gets discovered during an audit.

The intervention windows

With people inside, much of the work happens off-hours or in cordoned-off areas. That’s why it matters to see the load on the calendar and be able to move work by dragging it when building usage demands something else.

And for the system to check holidays and availability before generating an order, so you don’t end up scheduling an inspection on a day nobody can grant access.

The technician and the material

In the app the technician has their orders, the equipment history, its documentation, and open anomalies; they log time with a stopwatch, consume material from the warehouse, and collect the signature. It works without connectivity, which is normal in plant rooms, rooftops, and basements.

The QR code on each unit solves a problem very specific to buildings: identifying which of the five identical air handling units this one is.

What gets shown to ownership

Reports by system and by building: plan completion, cost per asset and per system, hours per contractor, response and resolution times, detected anomalies.

With that, the meeting with ownership stops being a conversation about impressions and becomes a review of data. And the case for replacing equipment appears: a system with high accumulated cost and growing failures gets replaced backed by numbers.

The inventory that doesn’t exist, and how to build it

The most common objection when proposing all this: nobody has the list of what’s in the building, and building it looks like a project.

It’s less of one than it seems if done in the right order. You don’t start by walking the building noting everything down: you start with the current maintenance contracts, which already describe a good part of the systems and their equipment, and with inspection records, which say what’s subject to a standard.

That covers what’s critical within a few days. The rest gets added as it comes up: the first time someone opens an order for a piece of equipment that isn’t registered, it gets registered on the spot, with its photo and its QR code.

After a few months the inventory is done, and — this is the important part — it’s made up of what’s actually used, instead of being an exhaustive list of items nobody will ever look at again.

Where to start

With the systems subject to regulatory obligation, with their checklists, frequencies, and contractors registered, and with the dates that expire. The rest of the inventory comes in afterward.

If you manage a portfolio, there’s more in CMMS for facility management. And if you’d like to see it with your own building, you can request a demo.