The Generator Nobody Was Tracking

An AMC file that nobody opened until something broke

Most housing societies have a real asset list somewhere — a lift, a couple of DG sets, water pumps, a fire hydrant system — and a real AMC (annual maintenance contract) for most of it. The problem is rarely that the contract doesn't exist. It's that nobody actually looks at it until the generator fails to start during a power cut, and only then does someone go digging through a folder to find out the AMC lapsed four months ago.

That's not a facility management failure of effort. It's a failure of the file being static. A PDF sitting in a shared drive doesn't remind anyone of anything.

What a real asset register actually needs to do

Facility management for a housing society isn't complicated in concept — it's three real, connected things: know what you own, know when it needs attention, and know when something's actually broken and who's fixing it. Most tools that claim to do this stop at the first one — a static list with a name and a category, which is barely better than the spreadsheet it replaced.

• A real asset register — every lift, generator, pump, and fire system, with a location, install date, and the AMC contract it's actually linked to.
• Preventive maintenance schedules — a real, recurring task per asset (service the DG set every 90 days), not a one-time reminder. Completing a task on time rolls the next due date forward from today, not from the date it was originally supposed to happen — so a task completed a week late doesn't quietly compress the next interval.
• Work orders — when something breaks between scheduled visits, a real ticket gets raised against that specific asset, assigned to staff or a vendor, and tracked through to resolution. Not a WhatsApp message to the facility manager that gets lost under twenty other messages by evening.

The real test of a facility management system isn't whether it can list what you own. It's whether it tells you, unprompted, the moment something needs attention — before a resident has to.

Why SLA tracking matters more for a lift than a light bulb

Not every issue deserves the same urgency, and treating them the same is how a genuinely urgent one gets buried. A lift stuck between floors and a loose tile in the lobby are not the same problem, and a real facility management setup should reflect that — a configurable response-time target by priority, set by the society itself, not a fixed default baked into the software.

The part that actually closes the loop is the alert when that target is missed. A work order that's quietly overdue, with nobody told, is functionally the same as no work order at all. A real breach alert — sent to the committee automatically, and only once per breach, so it doesn't become noise — is what turns an SLA from a number on a settings page into something that actually changes behaviour.

The parts that don't show up in a demo but matter every month

A few things that are easy to overlook until they're missing:

• Compliance document expiry — a fire safety certificate, an insurance policy, an occupancy certificate — all have real, legal expiry dates. An automatic alert before one lapses is the difference between a routine renewal and a compliance scramble.
• Notice read-tracking — when the committee posts something important, knowing it was actually seen by 40 of 60 residents, not just that it was technically published, changes whether you follow up or move on.
• A resident vehicle and parking registry — a real record of who owns what, and which slot it belongs to, so the gate isn't relying on a guard's memory for a 200-unit building.

Why this runs on the same backend as everything else

None of this needs to be a separate facility management product bolted onto a resident app. The asset that a work order is raised against, the vendor an AMC contract belongs to, the committee member who gets the SLA breach alert — all of it is already real data sitting in the same Community Platform that handles gate management, maintenance billing, and resident complaints. A society doesn't onboard a second system and re-enter its own vendor list a second time. It's the same login, the same data, one more real capability.