CMMS for Real Estate
One system for maintenance across buildings and portfolios.
Real estate portfolios run on building services rather than production lines, but the discipline is the same: know what you own, know its coverage status, and know who fixes it when it fails. AssetAI applies that discipline to DGs, lifts, HVAC, pumps and fire systems the same way a CMMS applies it to a factory floor — as assets with a registry, a schedule, and a full maintenance history.
How coverage status stays current
Every asset in the registry carries its AMC applicable flag, vendor, start/end dates, cost, a monthly/quarterly/half-yearly/yearly schedule, and warranty dates. From that data AssetAI derives a live coverage status using a fixed precedence — in warranty beats under AMC, then expired, then no coverage recorded — so a lift or DG's contract state is never a manually-updated field going stale in a spreadsheet. That status is stamped automatically onto any service call raised against the asset, and a daily 06:15 sweep checks all assets and warns ahead of upcoming warranty and AMC expiry, so renewals don't get discovered at the point of failure.
This matters more in a building than a plant floor, because a single site often runs different vendors per system:
- a lift OEM under warranty,
- a DG set on an AMC with a separate contractor,
- a fire-system vendor billed per visit.
Raising a service call pre-fills the vendor from the asset's AMC vendor, falling back to its supplier, so the right contractor is contacted without someone checking a contract folder first.
Vendor accountability and statutory checks
Facility teams don't just need reminders — they need proof of who did what, and when, especially for lift, DG and fire-system inspections that carry a regulatory component. AssetAI treats statutory checks as a first-class schedule type: it recurs on a time basis, captures the regulation/statute and certificate number, and generates a corrective work order with its own closure-approval step, separate from routine service. That lets a facility manager inspect and a maintenance head sign off as two distinct actions on the same record.
Vendor service calls themselves run through a full repair loop with an automatic time trail — Requested, Visited, Quoted, Quote Approved, In Service, Completed, Billed, Bill Passed, Closed, or Cancelled — so a lift-repair bill sits against that specific job rather than a lump AMC invoice, and disputes over what was billed for what are resolved against a record, not a memory.
A few details that matter day to day:
- Anyone standing at a piece of equipment can report a fault by scanning its QR code and entering a name plus the company's scan PIN — no login, no app — which is how tenant or occupant complaints actually enter the system, as a breakdown against whatever asset (AC unit, lift, pump) they're standing near.
- Breakdown severity has a machine-stopped flag, and emergency severity bypasses approval entirely, raising the work order at submit — relevant for a stalled lift or a tripped fire pump.
- Corrective and breakdown work orders cannot be closed without a recorded failure cause and remedy, which builds the failure history a portfolio needs over time.
What AssetAI does not do is manage tenants, leases, occupancy or CAM reconciliation — that's property management, out of scope by design. It's worth checking /features and /pricing to see whether the maintenance layer alone fits your stack, and browsing /industries if your portfolio spans manufacturing sites as well as buildings. Standards on facility upkeep and asset management, including ISO's published standards, are a useful reference point when scoping statutory-check workflows.
Facility teams don't need a floor-complaint form and a maintenance ticket and a vendor log as three separate tools — they need one record per problem, from the moment someone reports it to the moment a vendor gets paid. That's the part of the workflow worth walking through separately from coverage tracking.
From a QR scan to a closed work order
A tenant standing near a tripped AC unit or a visitor stuck at a slow lift doesn't have — and shouldn't need — a login. AssetAI handles this with QR-code reporting: scan the code on the asset, enter a name and the company's scan PIN, and a breakdown record is created automatically, numbered BD-000001 per company. There's no separate "tenant complaint" entity to configure or reconcile against equipment records — the complaint is the breakdown, linked to whatever asset the person is standing next to. This is the same mechanism a factory uses for a machine-side fault report, applied without change to a building floor.
From there, severity decides the path:
- A routine issue (a flickering light, a slow-running AC) follows the normal approval flow before a work order is raised.
- A "machine-stopped" flag — a stalled lift, a tripped fire pump — carries emergency severity that bypasses approval entirely and raises the work order at submission, because nobody should be waiting on sign-off when a fire pump is down.
Once a work order exists, it can't be closed without a recorded failure cause and failure remedy — enforced in code, not left to discipline. Over time that builds the same failure history for a lift motor that a factory would build for a production asset, which is the raw material for any later reliability review, in the spirit of practices like TPM.
What this setup deliberately leaves out
Because AssetAI is a maintenance system and not a property-management platform, a few things that portfolio teams sometimes expect from "building software" are out of scope by design:
- No permit-to-work workflow — no permit numbers, issue/close steps, or signature gates for hazardous jobs like lift-shaft or DG-room work. What exists instead is a Safety Measure list mapped per asset and printed on the job sheet, which supports the technician on-site without simulating a formal permit system.
- No tenant or lease records, no floor-plan model, no rent roll, occupancy tracking, or CAM-charge reconciliation. The location hierarchy — plant, area, line, functional location — is relabeled for building/floor/zone use, but it's the same four-level structure built for a manufacturing site, not a purpose-built property hierarchy.
- No compliance verification for fire or lift codes. Certificate numbers and the applicable regulation are stored as fields against the statutory schedule, and the system reminds ahead of the due date — it doesn't validate that the certificate itself meets code.
If your portfolio's core need is rent administration or lease tracking, that's a different category of software entirely. But if the need is knowing what building equipment you're responsible for, whether it's covered, and who's accountable when it breaks, that's exactly what a CMMS is built for — see the full feature set or how other industries apply the same model, browse use cases, or book a demo to see it against your own building services list.
CMMS for Real Estate FAQs
How do I track which building services are still under warranty versus AMC?
AssetAI shows live coverage status for every asset—DG, lift, HVAC, pump, fire system—with a fixed priority: warranty coverage beats AMC, then expired coverage, then no coverage recorded. This status stamps automatically onto any service call you raise, so you always know which vendor is responsible and whether costs should be claimed or paid out-of-pocket. The system also runs a daily 06:15 sweep that warns you before warranty and AMC expiry dates arrive, giving you time to plan renewals before gaps open up.
What happens when a tenant or security guard reports a breakdown without logging in?
They scan the QR code on the equipment, enter their name and your company's scan PIN—no app, no login required—and AssetAI creates a numbered breakdown record (BD-000001) instantly. This gets routed into your repair workflow so maintenance teams see it immediately, and the QR-based entry means reports reach you from anywhere in the building without friction or delays.
Can the system track lift and DG inspections separately from routine maintenance?
Yes. Statutory checks—lift, DG, and fire system inspections—are handled as a first-class schedule type in AssetAI. Each recurring inspection captures the regulation or statute it satisfies, the certificate number, and generates a work order with a separate closure-approval step, keeping compliance audits clean and separate from preventive maintenance routines. This ensures you never miss a regulatory deadline and have audit-ready records.
How do I manage external vendor repairs end-to-end?
AssetAI runs external repairs through a full workflow loop with automatic timestamps at each stage: Requested, Visited, Quoted, Quote Approved, In Service, Completed, Billed, Bill Passed, Closed, or Cancelled. You see exactly where each vendor job stands, when they arrived, what they quoted, and when they invoiced—eliminating guesswork and ensuring accountability from call-in to closeout.
Where do I record DG, lift, and HVAC warranty and AMC details?
Each building service is registered as an asset in AssetAI with fields for vendor name, warranty start and end dates, AMC start and end dates, cost, and the applicable schedule type (monthly, quarterly, half-yearly, or yearly). This single registry becomes your source of truth for coverage, and the system automatically applies the correct status to any service call raised, so you never accidentally bill an AMC-covered repair to the tenant or miss a coverage window. See /features for the full asset registry capabilities.
What compliance standards does AssetAI help me meet for building maintenance?
AssetAI's statutory check module is built to capture regulations and certificate numbers, making it easier to demonstrate compliance during audits. For detailed alignment with Indian building codes and ISO standards for maintenance management, check /standards for guidance on how structured CMMS workflows support regulatory readiness in real estate operations.
How do I handle maintenance schedules when multiple properties share the same vendor?
Create a single vendor profile in AssetAI and link work orders across properties to that vendor. You'll see consolidated service history, response times, and costs by property. This helps negotiate better rates and identify if one location consistently needs more frequent repairs than others. Check vendor performance reports for insights.