Introducing Enhanced Breakdown Management in FacTech CAFM

Manage Equipment Breakdowns from Detection to Closure

We are excited to introduce the Enhanced Breakdown Management feature in FacTech CAFM, offering a structured and transparent process from identification to resolution.
With this feature, teams can capture the complete breakdown life-cycle, including detection, acknowledgment, on-site response, repair, resolution, cost, and closure.
More importantly, FacTech automatically tracks key reliability and response metrics at every stage, helping maintenance teams understand how quickly an issue was detected, acknowledged, attended, repaired, and resolved.

What is Breakdown Management?

Breakdown Management is a structured workflow used to record and monitor an equipment failure or operational incident until it is fully restored.
Instead of maintaining breakdown details manually, FacTech captures each stage of the incident in a single Breakdown Work Order.
The workflow consists of:
Raise → Detect → Acknowledge → Respond → Repair → Resolve → Cost → Close
This creates a complete digital history of the breakdown and the actions taken to resolve it.

How to Raise and Close a Breakdown?

To raise a breakdown, follow these steps:

1. Open the FacTech website.
2. Login to FacTech as an Admin.
3. Navigate to Assets & PPM.
4. From the left-side menu, click Breakdown.
5. On the Breakdown page, click the “+ Break” button.
6. Enter the required breakdown information and continue through the breakdown life-cycle until closure.

Breakdown Work Order Life-cycle

1. Raise – Report the Breakdown

The process starts when an equipment breakdown is reported. A Breakdown Work Order is created against the affected asset.

Important Information on the “+ Break” Page: 
While raising a breakdown, you may need to capture the following information:

• Asset ID / Tag
• Asset Name
• Location
• Criticality
• SLA Resolve
• Failure Date
• Occurrence Time
• Detection Time
• Detection Source
• Observation / Fault
• Priority
• Business Impact
• Occupants Affected
• Redundancy / Standby Availability
• Safety / Near-Miss
• Environmental Release

What do these terms mean?

Asset ID / Tag: Unique identification number assigned to the equipment.
Criticality: Indicates how important the asset is to operations.
SLA Resolve: The target time within which the breakdown should be resolved according to the Service Level Agreement.
Detection Source: The source through which the failure was identified, such as an operator or BMS/SCADA alarm.
Observation / Fault: The problem or abnormal condition observed in the equipment.
Business Impact: The effect of the breakdown on business operations.
Occupants Affected: Number of people impacted by the breakdown.
Redundancy / Standby: Indicates whether an alternate or backup system is available.
Near-Miss: An unsafe event or situation that could have caused harm but did not.
Environmental Release: Indicates whether the incident resulted in any environmental release or impact.

2. Detect – Capture When the Failure Was Identified

The Detect stage records when the breakdown was actually identified. FacTech records the detection time as T1 – Detected.
This is important because it allows the organization to measure the time between the actual occurrence of a failure and its detection.
MTTD stands for Mean Time to Detect. It measures the average time taken to detect a breakdown after it occurs.
For example, if an equipment failure occurs at 10:20 AM and is detected at 11:25 AM, the system records the detection delay. A lower MTTD generally indicates faster detection of equipment failures.

3. Acknowledge – Confirm and Assign the Issue

Once the breakdown is detected, the next step is Acknowledgment. The responsible technician or team confirms that the breakdown has been received and is being acted upon.
The system records T2 – Acknowledged.
Users can also add:

• Assigned Technician
• Assigned Team
• Acknowledgment Remarks

MTTA – Mean Time to Acknowledge. MTTA measures the time taken between detection and acknowledgment of the breakdown.
It indicates how quickly the responsible team responds to a reported issue.

4. Respond / On-Site – Reach the Equipment

After acknowledgment, the responsible team attends the location. At this stage, users record T3 – Responded / On-site, which indicates when the technician or team reached the site and started handling the breakdown.
MTTR – Respond measures the time taken from acknowledgment until the team responds or reaches the affected equipment.

This helps organizations monitor field-response efficiency.

5. Repair – Restore the Equipment

Once the team reaches the asset, the actual repair activity begins. The Repair stage records:

• T4 – Repair Start Time
• T5 – Repair Complete / Restored Time
• Failure Mode / Cause Code
• Repair Notes

Failure Mode / Cause Code
This identifies the reason or type of failure that caused the breakdown.

For example:

• Electrical fault
• Mechanical failure
• Component failure

Repair Notes
Technicians can document the work performed, observations, or important repair details.
MTTR – Repair measures how long it takes from the start of the repair activity until the equipment is restored.
This helps management evaluate repair efficiency.

6. Resolve / Verify – Confirm the Breakdown is Resolved

After the equipment is restored, the issue moves to Resolve / Verify. The objective of this stage is to confirm that the equipment is functioning correctly and that the breakdown has actually been resolved.
The system records T6 – Resolved.

MTTR – Resolve represents the time taken through the breakdown-resolution process until the incident is formally resolved.

This provides a broader view of how quickly a breakdown moves from occurrence to final resolution.

7. Cost – Record Breakdown Cost

Once the breakdown has been resolved, the associated cost can be recorded. The Cost section allows users to capture

• Labour Hours
• Labour Cost
• Spares / Material Cost
• Contractor / OEM Cost
• Operating Hours in Period
• First-Time Fix
• Leanings / Corrective Action

What do these terms mean?

Labour Hours: Total time spent by technicians on the breakdown.
Labour Cost: Cost associated with the technician or maintenance labour.
Spares / Material Cost: Cost of parts and materials used for the repair.
Contractor / OEM Cost: Cost paid to an external contractor or Original Equipment Manufacturer.
First-Time Fix: Indicates whether the breakdown was successfully resolved without requiring another repair visit for the same issue.
Leanings / Corrective Action: Important observations or actions that can help prevent the issue from happening again.

8. Close – Complete the Breakdown

Once all required information has been entered, the Breakdown Work Order can be closed. After closure, FacTech provides a consolidated Breakdown Incident Report containing the complete history of the incident.

This includes:

• Breakdown details
• Response timeline
• Repair information
• Cost
• Reliability metrics

Live Reliability KPIs

One of the key advantages of the Breakdown feature is the Live Reliability KPI panel. This panel provides real-time visibility into the performance of the breakdown response.
The following KPIs are available:

Mean Time to Detect: Time taken to identify the breakdown after occurrence.

Mean Time to Acknowledge: Time taken to acknowledge the detected breakdown.

Mean Time to Respond: Time taken for the maintenance team to respond or reach the site.

Mean Time to Repair: Time taken to repair and restore the equipment.

Mean Time to Resolve: Overall time taken to resolve the breakdown.

Downtime: Total duration for which the equipment or service remained unavailable.

SLA Outcome: Shows whether the breakdown was resolved within the defined SLA.
It can indicate outcomes such as: Pending or Breached

First-Time Fix: Shows whether the breakdown was resolved successfully on the first repair attempt.

Cost / WO: Displays the cost associated with the Breakdown Work Order.

Incident Timeline

FacTech also provides an Incident Timeline, which records the sequence of activities performed during the breakdown. The timeline includes:

T0 – Occurrence

↓

T1 – Detected

↓

T2 – Acknowledged

↓

T3 – Responded

↓

T4 – Repair Started

↓

T5 – Restored

↓

T6 – Resolved

This gives maintenance teams a clear chronological view of the entire incident.

SLA Monitoring

The Breakdown feature also helps teams monitor whether the breakdown was resolved within the defined SLA (Service Level Agreement).

For example, if an asset has an SLA resolution target of 60 minutes, the system can compare the actual resolution time against that target.

This makes it easier to identify:

• SLA-compliant breakdowns
• Delayed breakdowns
• Repeated response issues
• Assets requiring better maintenance planning

Breakdown Management: Key Benefits

✅ Complete breakdown life-cycle tracking

✅ Structured incident management

✅ Real-time reliability KPIs

✅ Automatic calculation of response and repair metrics

✅ Equipment downtime monitoring

✅ SLA performance tracking

✅ Breakdown cost tracking

✅ First-time-fix monitoring

✅ Root-cause and failure-mode documentation

✅ Complete incident audit trail

✅ Better maintenance and reliability analysis

Frequently Asked Questions (FAQs)

Q1. What is a Breakdown Work Order?

A Breakdown Work Order is a digital record created to manage an equipment failure from initial reporting through repair, resolution, cost recording, and closure.

Q2. What is the difference between Occurrence Time and Detection Time?

Occurrence Time is when the equipment actually fails.

Detection Time is when the failure is identified.

The difference between these two helps calculate MTTD.

Q3. What does T0, T1, T2, T3, T4, T5 and T6 mean?

These are milestone timestamps in the breakdown life-cycle:

T0: Occurrence

T1: Detection

T2: Acknowledgment

T3: Response / On-site

T4: Repair Start

T5: Restoration

T6: Resolution

Q4. What is MTTD?

MTTD means Mean Time to Detect. It measures how quickly a breakdown is detected after it occurs.

Q5. What is MTTA?

MTTA means Mean Time to Acknowledge. It measures how quickly the responsible team acknowledges a detected breakdown.

Q6. What is MTTR?

MTTR means Mean Time to Repair/Resolve/Respond, depending on the specific KPI being displayed. In FacTech, different MTTR measurements are used to monitor different stages of the breakdown life-cycle.

Q7. What is Downtime?

Downtime is the total period during which the affected equipment or service is unavailable because of the breakdown.

Q8. What is First-Time Fix?

First-Time Fix indicates whether the breakdown was successfully resolved during the initial repair without requiring another repair intervention for the same issue.

Q9. What is SLA Outcome?

SLA Outcome indicates whether the breakdown was resolved within the target time defined by the SLA.

Q10. Can breakdown costs be recorded?

Yes. FacTech allows users to record labour hours, labour cost, spare/material cost, contractor/OEM cost, and related operational information.

Q11. Can we record the cause of the breakdown?

Yes. The Repair stage provides a Failure Mode / Cause Code field to document the cause or type of failure.

Q12. Can we record corrective actions and learnings?

Yes. The Cost section provides a Leanings / Corrective Action field so teams can document improvements or actions required to prevent similar failures.

Q13. Can the complete breakdown history be viewed after closure?

Yes. Once the Breakdown Work Order is completed, FacTech provides a consolidated incident report containing the breakdown details, timeline, KPIs, repair information, and cost.

Conclusion

The Enhanced Breakdown Management feature in FacTech CAFM provides a structured and measurable approach to managing equipment failures.

From Occurrence and Detection to Acknowledgment, Response, Repair, Resolution, Cost, and Closure, every stage is captured digitally.

By combining incident tracking with MTTD, MTTA, MTTR, Downtime, SLA, First-Time Fix, and Cost KPIs, FacTech enables maintenance teams to move beyond simply closing breakdown tickets and start measuring the overall reliability and effectiveness of their maintenance operations.

With FacTech, every breakdown becomes measurable, traceable, and actionable.