How can we help?

Open the machine master, create the asset with its code, specifications, location and photographs, and save it. You can attach its spare-part BoM, record AMC and warranty dates, and print a barcode or QR asset tag. Once registered, every breakdown, PM, spare issue and repair posts against that asset. See Asset Register & Tracking.

Yes. Assets, specifications, spare-part lists and opening spare stock can be imported in bulk from Excel at cutover, so you don't re-key an existing asset list by hand. Data can also be exported back to Excel for offline review. This keeps the initial rollout fast even for plants with hundreds of machines. See Asset Register & Tracking.

Each asset and serial can carry a printed barcode or QR tag generated from its machine-master record. Fix the tag on the machine and a technician can scan it to open that asset's card on a phone. Tags make asset identification unambiguous on the shop floor and drive the mobile asset card. See Barcode & QR.

A spare-part BoM lists the spares that fit a specific asset — the maintenance equivalent of a bill of materials. Holding it against the machine master means that when a job needs a part, the system already knows which spares are valid for that machine, and consumption can be charged back to the asset. See Spare Parts & BoM.

Each asset can carry its AMC (annual maintenance contract) and warranty expiry dates. As those dates approach, the system flags them and can send email, SMS or WhatsApp alerts, so a warranty claim isn't missed or an AMC left to lapse silently. It's a small field that saves real money over an asset's life. See Asset Register & Tracking.

Scan an asset's barcode or QR serial with a phone and the mobile asset card opens — showing that machine's specifications, spare BoM and full maintenance history: past breakdowns, preventive jobs and repairs. It puts the whole record of a machine in the hand of the technician standing in front of it. See Barcode & QR.

When a job needs a part, the spare is issued from the spare store against the asset and the maintenance job — which reduces spare stock and charges the cost to that machine. Because it references the asset's spare BoM, only valid spares are issued, and the store's stock and ledger stay accurate. See Spare Parts & BoM.

Each spare can hold a reorder level. When stock falls to or below it, the spare appears on a reorder dashboard and can trigger an alert, so critical spares are replenished before a machine needs one that isn't there. The aim is availability without over-stocking — the spare-part MIS shows what's moving and what's dead. See Fast Inventory & Purchase.

When an asset or sub-assembly needs external repair, raise a dispatch record to send it to the workshop or vendor, and record its return when it comes back — closing the loop with the ledger intact. Asset inward, location allocation and receive-from-repair all post against the same asset, so its whereabouts and repair history stay clear. See Asset Inward & Repairs.

Raise a breakdown ticket against the affected asset, record the time it went down, and assign a technician. Spares are issued from the store against the job, the repair is recorded, and closing the job marks the asset running again — which stops the downtime clock. Every breakdown feeds the machine's history and the MTTR/MTBF calculations. See Breakdown & Emergency.

Downtime is captured from the breakdown record: the time the asset stopped and the time it was restored give the downtime for that event, along with a cause or remark. Accumulated across events, this downtime drives the breakdown and downtime-analysis dashboards and is the raw material for MTTR and MTBF — so the numbers come from doing the work, not a separate log. See Dashboards & MTTR/MTBF.

Emergency maintenance is an unplanned, high-priority breakdown that needs immediate attention — a critical machine down mid-shift. It follows the same report-assign-repair-close flow as a normal breakdown, with priority handling and instant alerts so the right technician is on it fast. It still records downtime and spares, so even the urgent jobs feed the reliability numbers. See Breakdown & Emergency.

Define a preventive or planned schedule against an asset on a time or usage basis. When it falls due it raises its own job card, appears on the maintenance calendar, and can trigger an alert. The point of PM is to service the machine while it is still running — so scheduled work happens before failure rather than after it. See Preventive & Planned.

A preventive job card can carry a checklist of the tasks and inspection points for that asset — lubrication, part checks, readings — so the technician follows the same standard every time and records the results. Completed checklists become part of the maintenance history, giving evidence that the PM was done properly, not just marked complete. See Preventive & Planned.

A safety work-permit checklist can be required before maintenance starts on a machine — confirming isolation, lock-out, and the safety conditions for the job. It makes the safety step a gate rather than an afterthought, and the permit is recorded against the job for audit. This matters most on high-energy and utility assets. See Preventive & Planned.

The live machine status board shows every asset in real time as running, under breakdown or idle, so a supervisor can see the state of the whole plant at a glance and react to a machine going down immediately. It reflects the breakdown and repair events as they are posted — no manual whiteboard to keep updated. See Dashboards & MTTR/MTBF.

MTTR (mean time to repair) averages the repair time across an asset's breakdowns; MTBF (mean time between failures) averages the running time between them. Both are computed from the breakdown and downtime records technicians create, and trended per machine and work center — so falling MTTR and rising MTBF are measured, not guessed. Dhruv AI can cluster breakdown-cause remarks on top of this. See Dashboards & MTTR/MTBF.

The maintenance history and asset history report bring together every breakdown, preventive job, spare issue and repair for a machine in one timeline, alongside the maintenance calendar and downtime analysis. It answers the question "what has this machine cost us, and why does it keep failing?" from real records. See Dashboards & MTTR/MTBF.

Fast Maintenance can send alerts on the events that matter — a PM falling due, a breakdown raised, a spare hitting reorder level, an AMC or warranty about to expire. Email and SMS are standard; WhatsApp automation is a scoped integration. The right person is notified without watching a screen. See WhatsApp, Email & SMS.

Spare issues, receipts and reorders post to the same stock ledger Fast Inventory uses, so spare-store stock and maintenance consumption are one set of numbers, not two. When a spare hits reorder level it can flow into purchase, so replenishment is connected to the maintenance that consumed it. See Fast Inventory & Purchase.

Dhruv AI is our AI analytics layer. It adds maintenance role dashboards over live data with AI insight summaries, answers plain-English questions through a safe read-only query sandbox, and clusters breakdown-cause and downtime remarks into named recurring themes by machine or work center — so the biggest reliability problems name themselves. See Dhruv AI Analytics.

Access is role-based: each user sees only the menus and screens their role allows — engineers raise and close jobs, technicians book work, stores issue spares, supervisors handle breakdowns and permits, managers see the dashboards and MIS. Every user's activity is logged, so the record shows who did what and when.

Yes. Every asset, breakdown, PM, spare issue and repair is a document with a status history and audit trail, and every write is logged. Because spare movements ride the shared stock ledger and every event posts against the asset, you can trace which spare and which technician went into which repair on which machine — the traceability regulated plants require.

Fast Maintenance runs cloud or on-premise, and standalone or as part of the Fast Suite. Standalone it manages assets, spares, breakdowns, preventive maintenance and dashboards on its own. Combined, it shares the same spare stock as Fast Inventory and the same platform as Fast ERP — so you can start with the CMMS and expand with no migration. See the CMMS learn hub.