Every asset in the building, one system

How Facility assets like yours use AssetAI

Facility assets rarely fail the same way twice — a DG set trips on load, a lift stalls between floors, a fire pump loses prime — and each of these lives outside the core production line yet is critical to keeping the plant running and compliant. AssetAI treats them as first-class assets in the same CMMS engine used for production equipment, not as a side spreadsheet tracked by the facilities executive.

How a Fault Actually Gets Logged

Most facility breakdowns aren't reported by trained maintenance staff — they're spotted by a security guard, a tenant, or a floor supervisor walking past a leaking pump. AssetAI's QR flow is built for exactly this:

• Anyone scans the asset's QR code, enters their name and the company's scan PIN — no login, no app to install.
• The asset is resolved automatically from the QR URL, so there's no manual asset search or misidentification.
• The reporter picks a severity — normal, high, or emergency — and an emergency call skips the approval step entirely, raising the work order immediately.
• The result is a standard, numbered breakdown record (BD-000001 style) — the same record type an operator would generate, just reported by someone with no system access.

This matters for facilities more than most asset classes, because the people closest to a DG set or a lift are often the least likely to have a maintenance login. There's no separate tenant portal or ticket-status notification layer — deliberately, since the goal is one clean record trail, not a parallel help-desk experience.

Closing the Loop Properly

A closed work order on a facilities asset needs to mean something, especially when it's under a paid AMC or a statutory inspection cycle:

• Breakdown and corrective work orders on lifts and DGs cannot be closed without a failure cause and a failure remedy selected from the master lists — this is enforced in code, not left to discipline, and it's what feeds the failure Pareto later.
• Inspection work orders carry an extra closure gate — commonly a Planner inspecting and a Maintenance Head signing off — and a rejection reopens the work order with the returned reason attached, rather than silently closing an incomplete job.
• Every job sheet prints the asset's required safety measures and tools as a checklist with sign-offs, giving a paper (or PDF) trail for what was actually followed on-site.

None of this replaces a formal permit-to-work system — AssetAI doesn't run permit numbers, issue/close cycles, or approval gates for hazardous jobs — but it does mean no lift or DG work order gets closed without someone recording why it failed and what was done about it.

Why This Matters for Indian Plants

Facility assets under third-party AMC are a recurring cost line and a recurring audit question — was the vendor called, was it covered, was the certificate current. Coverage status is computed live from the asset's warranty and AMC dates, so when a breakdown is raised, the record is auto-stamped with the correct coverage and the vendor is pre-filled from the AMC contract. Combined with the downtime-cost and MTTR/MTBF tiles on the analytics dashboard, that turns "which DG keeps failing" from a guess into a ranked list. For plants benchmarking against broader manufacturing practice, our standards page maps this against ISO's maintenance-related standards and TPM principles — worth a look if facilities upkeep is part of a larger reliability push. See it against your own DG and lift register — book a 30-minute demo on your plant, not our slides.

Facilities assets carry a different kind of risk than production machinery — a lapsed AMC or an expired lift certificate doesn't stop output, but it can trigger a fine, an insurance dispute, or a safety incident with no paper trail to explain what was covered. AssetAI is built to make that coverage state visible on the asset itself, not buried in a vendor's filing cabinet.

Coverage Status That Computes Itself

Every DG set, lift, HVAC unit, fire system, or pump in the Asset Registry carries its AMC-applicable flag, vendor, contract start/end, cost, and schedule alongside its warranty from/to dates — on the same record, not a separate contract file. From that data, AssetAI computes a live coverage status (in warranty, under AMC, expired, or no coverage) using fixed precedence rules, so nobody has to cross-check two spreadsheets to answer "is this pump still covered?" The moment a service call is raised against that asset, the coverage gets auto-stamped on the work order and the vendor field pre-fills from the asset's AMC vendor, falling back to the supplier if there's no AMC. A daily 06:15 sweep also flags anything whose warranty or AMC is approaching expiry, so renewals get raised before the gap opens up — not after a breakdown exposes it.

Statutory Inspections Live on the Same Schedule as Routine PM

Lift certifications, fire system checks, and pressure-vessel inspections don't need a separate compliance tool bolted onto the CMMS. In AssetAI, statutory inspection is simply a schedule type — it carries a regulation/statute field and a certificate number, recurs on the same days/weeks/months logic as any PM, and generates a work order through the identical daily 06:00 job that raises routine maintenance. That said, those fields are structured free-text storage for your own reference — AssetAI does not validate them against an actual statute or licensing authority, so the responsibility for correctness stays with your compliance team. Where it does add rigor: inspection work orders carry an extra closure gate, a labelled "Work order closure (inspection)" approval — a Planner inspects, a Maintenance Head signs off, and a rejection reopens the work order with a returned-reason note rather than letting it quietly close. Teams building out a broader compliance calendar can cross-reference ISO standards or browse industries to see how other asset classes use the same schedule engine.

Where the Vendor Visit and the Rupees Actually Go

For AMC or paid facility assets, every vendor call runs through a tracked loop — Requested → Visited → Quoted → Quote Approved → In Service → Completed → Billed → Bill Passed → Closed — so there's a record of what was agreed, done, and invoiced, even though AssetAI doesn't push payment or automatic invoicing to your accounting system. DG run-hours or any other usage meter can also drive the PM itself: readings logged manually, by QR scan, or by WhatsApp trigger the next service the moment a target is reached, instead of relying on a fixed calendar date that ignores actual load. And because downtime-cost and MTTR/MTBF tiles on the analytics dashboard apply to facility assets exactly as they do to production lines, you can see which DG or AHU is quietly bleeding the most money — a useful input alongside OEE thinking when justifying AMC renewal or replacement. See the full breakdown on pricing or book a demo to walk through your own asset list.