CMMS for shopping malls

A shopping mall is a large building with the public inside twelve hours a day, dozens of units with different tenants, and an ownership group that wants to know where the money is going. Maintenance has to solve all three at once.

And it has one particularity: almost nothing can be worked on during opening hours, so the plan isn’t shaped only by frequency — it’s also shaped by when work can happen.

What gets maintained, by consequence

It’s worth ordering it by what happens if it fails, not by its price.

What shuts down the mall. HVAC for the galleries, ventilation, electrical supply and backup generators, fire protection, elevators, and escalators.

What’s disruptive and visible. Lighting, automatic doors, restrooms, ambient music, signage, cleaning.

What affects the parking area. Barriers, card readers, forced ventilation, CO detection, emergency lighting.

What serves the tenants. Utility connections, restaurant extraction systems, centralized refrigeration where it exists.

In asset management each piece of equipment has its own record with model, serial number, installation date, warranty end date, location, and its priority, grouped by system, family, and model. That classification is what lets you configure the check for a type of equipment once and apply it to the forty units you have.

The intervention windows

The trait that shapes everything the most. Work happens before opening, after closing, or during low-traffic windows, and some interventions only fit into the single annual closing day.

That’s why two things matter: the calendar needs to show the load and let you move work by dragging it when operations demand something else — if rescheduling costs more than ignoring the plan, the plan gets ignored — and preventive maintenance needs to check holidays and technician availability before generating an order, because in a shopping mall holidays are precisely the busiest days.

A single asset can carry several periods at once: the weekly check, the quarterly inspection, and the annual one with a certifying body are three different plans on the same piece of equipment.

Letting whoever sees it raise the alert

In a shopping mall the failure gets spotted by a security guard, a cleaner, or a store manager. None of them is a technician and none of them is going to fill in a long form.

An incident can be logged from the backend, from a dedicated access point with a description and photo, or from a mailbox that the system converts into alerts. It carries its type, priority, zone, and affected equipment, and each status can carry a maximum time, so what’s overdue shows up in a list.

That photo removes the guesswork, and in a building with many similar zones, it also prevents a trip to the wrong area.

Tenants, who are clients

There’s a design decision here that makes the difference. Tenants aren’t mall staff, but they need to report issues and know how their own things are progressing.

With their own access they open incidents, track the status of their orders, and check their documents. And since licenses are unlimited across all three plans, giving access to every tenant isn’t a budgetary decision.

The practical effect is that the mall’s office stops being a switchboard.

The contractors

Almost everything is carried out by outside companies, usually one per specialty: HVAC, electrical, elevators, fire safety, cleaning, landscaping, security.

They’re registered as suppliers and receive the work orders that correspond to them, with their times, material, documentation, and signature, so everything ends up in the same history. There’s also a two-way connector between GMAO Cloud installations for when the contractor uses it too.

Without that, ownership has invoices but no file, and can’t check whether what’s being paid for is actually being done. The annual plan completion report answers exactly that question.

What you need to be able to prove

With the public inside, the bar is high: electrical installations, fire protection, elevators and escalators, HVAC, water systems, CO detection in the parking area.

It’s worth knowing this before looking for it in the menu: legal maintenance is not a module. It’s done with the preventive maintenance mechanism, by attaching the checklist the standard requires and its frequency, and the proof comes from the order history, completed checklists with their recorded values, and documentation with its expiration dates, which warns before something lapses.

The software records and proves. The one who answers to an inspection or an incident is the owner.

Justifying spend to ownership

It’s the deliverable that decides whether the management contract gets renewed.

Reports let you view it by system, by zone, and by contractor: cost per asset, hours per supplier, response and resolution times, plan completion, and detected anomalies.

The most revealing one is usually the cross-reference between anomalies and equipment model: when a failure repeats on the same model across the whole mall, it stops being a breakdown and becomes an argument with the manufacturer or in the tender.

The technician, with the history in front of them

In the app, their orders for the day, the equipment history, its documentation, and open anomalies; stopwatch within the order, material consumption from the warehouse, checklist, and signature. It works without connectivity, which is normal in plant rooms, on rooftops, and in parking areas.

Consumption and the common areas

A detail that carries more weight in shopping malls than in other buildings: a large part of the operating cost gets passed on to tenants, so knowing what each system consumes isn’t just cost control — it’s the basis for the cost split.

The history helps with two things. First, spotting equipment that starts consuming more: if the checklist records values — consumption, temperatures, differential pressures — with their minimum and maximum, a deviation gets logged as an anomaly before it turns into a breakdown and before it shows up on the bill.

Second, deciding replacements with criteria. A ten-year-old HVAC unit with high accumulated cost may come out cheaper to replace than to keep maintaining, and that conversation can only happen with the cost per asset in front of you.

In GMAO Cloud you can also record an asset’s replacement cost with a warning percentage, so the system notifies you when the accumulated cost of repairing it exceeds that figure. It doesn’t generate an order — replacing is a business decision — but it puts the number in front of you when it matters.

Where to start

With the critical systems — HVAC, electrical, fire safety, vertical transport — with their checklists, frequencies, and contractors registered. The rest of the inventory and the tenants come in afterward.

There’s more on managing property portfolios in CMMS for facility management. If you’d like to see it with your own mall, you can request a demo.