Breakdown Maintenance
Report, approve, fix and learn — fast
Every breakdown report is a data point about how your plant actually fails — not how the maintenance manual says it should. AssetAI treats the report-to-resolution path as a single mechanism, not a form-filling exercise, so the record that starts at the machine ends up driving the work order, the vendor call, and eventually the failure-mode history you'll want when you sit down to plan preventive schedules.
From Report to Work Order Without Re-Typing Anything
The point of raising the work order directly from the breakdown report — rather than making a supervisor open a second screen and retype what the operator already said — is that nothing gets lost or reworded in translation. The title comes from the description, priority maps from the severity the operator picked, and the responsible technician defaults to whoever owns that asset. If the machine was flagged as stopped, the downtime clock starts at the moment the report was filed, not when someone eventually gets to the repair — which matters if you're serious about tracking OEE and want availability losses that reflect reality rather than paperwork lag.
- Approve-and-assign ranks technicians by skill match, availability, on-call status and current open-work-order load, so the supervisor isn't guessing who's free.
- Approve-to-vendor raises a Service Call instead, and sets coverage to warranty or AMC automatically from the asset's coverage status — paid only when neither applies.
- Emergency severity skips approval entirely. The work order fires at submission, because a line-down situation doesn't wait for a supervisor to be at their desk.
This is the core mechanic behind the module, and it's worth reading alongside the broader features list to see how it connects to work order management and asset records elsewhere in the platform.
Why Nothing Gets Deleted
A maintenance system that lets people quietly delete inconvenient reports is a system that will eventually hide the exact failure pattern you needed to see. AssetAI doesn't allow it — a breakdown report is permanent once filed, and the only way to reverse one is rejection, which requires a reason of at least a few characters and stays attached to the record forever. That's a deliberate design choice for plants where audit trails matter, whether for internal root-cause work or for external ISO or quality-system audits — see our standards page for how this fits broader compliance expectations.
The trade-off is that there's no SLA clock chasing every report and no tiered escalation matrix — just one escalation ping, once per breakdown, when something sits unapproved past your threshold. For plants running lean maintenance teams rather than formal service-desk structures, that's usually the right level of automation: enough to stop a report from being forgotten, not so much that people start ignoring notifications. If your plant's maintenance philosophy leans toward TPM — operators owning first-line response, supervisors handling dispatch — this module maps to that structure directly rather than forcing a helpdesk model borrowed from IT.
If you're still evaluating whether a full CMMS or a lighter breakdown-only workflow fits your plant, the what is a CMMS explainer and our use cases page are good next stops — or book a demo and walk through your actual shift and approval structure with us directly.
Report a breakdown with severity, failure mode and photos — the downtime clock starts immediately.
When a line stops on the shop floor, the person standing next to it is an operator, not a maintenance planner — so the reporting path has to work with a phone camera and a PIN, and the escalation path has to work without anyone remembering to chase it. That's the part of breakdown maintenance that's easy to underbuild and expensive to get wrong.
Reporting From the Machine, Not From a Desk
Most breakdowns in Indian plants are first noticed by the person operating the machine, often on a shop floor where not everyone has a login. AssetAI's guest reporting lets that operator scan a QR code on the asset, enter a shop-floor PIN, and file the report from wherever the machine sits — no walk to the office, no waiting for a supervisor to be free. The asset itself gets resolved automatically from the scanned QR URL, so there's no dropdown to search and no risk of picking the wrong line.
Two details matter here for plants that don't have reliable Wi-Fi in every corner of the building:
- Guest posts are throttled to 10 a minute, which stops a stuck button or a confused operator from flooding the queue.
- If the connection drops mid-shift, the browser queues the report offline and resubmits it later, tagged `[offline @ ...]` so nobody mistakes the filing time for the actual event time.
This is a deliberately narrow permission model — `breakdowns.report` is available to Technician, Storekeeper and Employee roles by default, while approval stays with supervisors holding `breakdowns.approve`. It's built for plants where the person closest to the fault reports it, and the person accountable for the asset decides what happens next.
What Happens When Nobody Approves in Time
A breakdown report sitting unapproved isn't just a process gap — it's downtime accumulating with no one accountable for it. Rather than layering in SLA countdowns or multi-tier escalation matrices, AssetAI runs one job every 5 minutes that checks for reports past your company's approval threshold (60 minutes by default) and pings everyone with approval rights, once per breakdown. It's a single, unambiguous nudge rather than a bureaucratic timer — teams that need contractual response-time tracking or tiered escalation chains should look elsewhere; this module is built for plants that need someone notified, not a compliance audit trail.
Emergency-severity reports skip this whole conversation: the work order is raised the moment the report is submitted, because a line-down emergency doesn't wait for anyone to click approve. For everything below that severity, the KPIs on the breakdown screen — pending approvals, open count, oldest open report, and average turnaround over the last 30 days — give a supervisor a fast read on whether reports are moving or piling up, without needing a separate dashboard.
None of this replaces a documented maintenance strategy — if you're building toward TPM or auditing against ISO standards, breakdown data is one input, not the whole system. AssetAI's breakdown maintenance module is the layer that keeps that input honest: report accepted, work order raised, technician assigned, downtime stamped — with nothing quietly deleted or reworded along the way. If you want to see how it fits your shift patterns and approval hierarchy, book a demo.
Breakdown Maintenance FAQs
How do I make sure breakdown reports don't sit in the approval queue while my machine is down?
AssetAI automatically escalates unapproved reports to all approvers every 5 minutes if they exceed your company threshold—defaulting to 60 minutes but adjustable to your process. The escalation fires once per breakdown, so approvers get a single notification reminder, not spam. This works alongside the downtime clock, which starts the moment you flag "machine stopped" on the report, giving you an accurate record of lost production time from the exact moment the breakdown was logged.
What's the difference between submitting a breakdown for internal repair versus sending it to a vendor?
When you approve a breakdown report, you can either assign it to your own technician or send it to a vendor as a Service Call. If you choose vendor, AssetAI automatically sets whether it's covered under warranty or an Annual Maintenance Contract (AMC) based on what's already recorded for that asset—if neither applies, it defaults to paid. This way your coverage status is captured in the job from the start, removing guesswork about billing later.
Can operators on the shop floor report breakdowns themselves, or does it have to come from maintenance?
Any operator can report a breakdown using their phone or tablet via a QR code printed on or near the machine, protected by a simple shop-floor PIN. The system throttles guest reporting to 10 submissions per minute to prevent accidental spam. If your network goes down, reports queue offline in the browser and automatically resubmit once connectivity returns—marked "[offline @ time]" so you know when it actually happened.
How does the system decide who to assign a breakdown to when multiple technicians are available?
When you approve a breakdown and choose to assign it internally, AssetAI ranks available technicians using four factors: skill match against the failure mode, current availability, on-call status, and their current workload of open work orders. You see this ranked list and pick from it in one action—approve and assign together—without manually hunting through schedules. The default responsible person is already set to the asset's assigned technician or owner, so you only override if needed.
Should emergency breakdowns go through the same approval process as normal repairs?
No—emergency severity reports skip approval entirely and raise the work order immediately on submit, because waiting for sign-off while the line is stopped costs more than the risk of starting the repair. Normal and high-severity reports still require approval before a work order is created, giving you control over priority and assignment. This two-track approach means your approvers only gate the repairs that aren't critical.
What information stays with the breakdown record after I convert it to a work order?
The breakdown report becomes the foundation of the work order: the description becomes the job title, severity maps to priority, and your chosen technician or vendor is assigned. The failure mode from your master list is captured, all photos you attached come along, and the downtime clock (if you flagged the machine stopped) records when production loss began. You can see the full breakdown details in the work order history, creating an audit trail from first report through resolution.
How do I track which breakdown caused the most production loss in my plant last quarter?
AssetAI logs breakdown start time, end time, and affected equipment. Run the Breakdown Analytics report filtered by date range and equipment type. It calculates downtime duration automatically. Cross-reference with your production schedule to estimate loss. Export data to compare quarter-on-quarter trends and identify repeat problem equipment for preventive maintenance planning.
See Breakdown Maintenance on your own machines
A 30-minute demo on your plant, not our slides.