Knowella

Failure Mode Record

Records how an asset failed, using standard failure mode codes rather than free text. Completed by the technician after repair. Coded, so patterns can be seen across hundreds of failures rather than read one at a time.

KnowMaintainRecordMNT-014Pinned in navigation
Completed by
Coded, so patterns can be seen across hundreds of failures rather than read one at a time
Raised
At the moment the event happens, rather than reconstructed

Summary

In short

  • A failure mode record is a record used in KnowMaintain that records how an asset failed, using standard failure mode codes rather than free text. It is built against ISO 14224 and forms part of the Reliability and Predictive Maintenance programme.
  • Completed by the technician after repair. Coded, so patterns can be seen across hundreds of failures rather than read one at a time.
  • The template holds 42 fields across 4 sections.
  • ISO is international Organization for Standardization. A voluntary international standard. Widely adopted, often required by customers, and certifiable where a management system standard.
  • It connects to the rest of the library: links Asset, Case.

What it is

What it is

What is a failure mode record?

A failure mode record is a record used in KnowMaintain that records how an asset failed, using standard failure mode codes rather than free text. It is built against ISO 14224 and forms part of the Reliability and Predictive Maintenance programme.

When is a failure mode record completed?

A failure mode record is completed at the moment the event happens, rather than reconstructed afterwards. Completed by the technician after repair.

When to use it

When to use it, and when not to

This record is one step in a larger programme. Using it for work that belongs to a neighbouring template produces records that are hard to report on later.

Use it for

  • The event or activity this record covers has occurred, or is about to
  • A new record is needed; each one gets its own ID in the form FM-2026-000
  • You are running the Reliability and Predictive Maintenance programme and this is one of its steps
  • A linked record needs this one to exist: links asset, case

Not for

  • Equipment Failure Report, which records that an asset has failed and stopped or degraded production.
  • Repair Record, which records what was actually done to fix the asset, including parts replaced and settings changed.
  • Temporary Repair Record, which records a repair that is not permanent, with an expiry date and a plan for the proper fix.
  • Anything outside KnowMaintain, which belongs in the workspace that owns that process

Standards

What it is built against

ISOInternational Organization for Standardization

A voluntary international standard. Widely adopted, often required by customers, and certifiable where a management system standard.

FAQ

Frequently asked questions

What is the failure mode record template based on?+

It is built against ISO 14224. ISO is international Organization for Standardization. A voluntary international standard. Widely adopted, often required by customers, and certifiable where a management system standard.

What sections does the failure mode record contain?+

There are 4 sections: header, coding, contributing conditions, analysis. Together they hold 42 fields, 30 of which are required.

How often is a failure mode record raised?+

A new record is raised at the moment the event happens, rather than reconstructed afterwards. Each one is given an ID in the form FM-2026-000, so it can be traced and referenced from other records.

Which programme does the failure mode record belong to?+

It is part of Reliability and Predictive Maintenance. Intervals set by failure behaviour rather than by the calendar.

Can the failure mode record template be changed?+

Yes. Every field, option, score and conditional rule is editable, and the links to other templates come with it. Most teams install it as it is, run it for a cycle, then adjust.

The agents

What the agents do with it

The form is the easy part. Keeping it current, routing it to the right owner and holding the evidence together is the work that actually slips.

KnowMaintain

Holds the failure mode record library against your registers, routes each record to its owner, and keeps the evidence trail together.

Ella

Coordinates the crew, rolls completion and exceptions into one view, and holds every write for your approval before it touches a record.

This template lives in KnowMaintainasset maintenance. Work orders, planned maintenance, calibration, reliability and shutdowns.

Meet KnowMaintain

Sources

Sources

  • ISO — International Organization for Standardization

KnowMaintain

Also in Breakdowns

6Browse the whole library
Record

Equipment Failure Report

Records that an asset has failed and stopped or degraded production. Raised at the moment of failure. Completed by the operator or technician. Carries a case ID that runs through repair, cause analysis and prevention.

Record

Repair Record

Records what was actually done to fix the asset, including parts replaced and settings changed. Completed at repair. Carried out by the technician. Builds the asset history that makes the next failure faster to diagnose.

Record

Temporary Repair Record

Records a repair that is not permanent, with an expiry date and a plan for the proper fix. Raised whenever a temporary fix is made. Approved by the maintenance manager. Temporary repairs that nobody tracks are how equipment quietly becomes unsafe.

Review

Repeat Failure Review

Reviews an asset that has failed the same way more than once. Raised on the second failure carrying the same code. Carried out by reliability with maintenance. A repeat failure means the last repair treated the symptom.

Record

Production Impact Record

Records what the failure cost in lost output, scrap and late orders. Completed by production after the event. Gives maintenance the business case for prevention, in the language finance responds to.

Record

Breakdown Debrief

A short review straight after a significant breakdown, capturing what happened and what would have helped. Run within 24 hours. Led by the maintenance supervisor with everyone involved. Fast and informal, and often catches things a formal investigation misses.

Start in Minutes, Not Weeks

Launch a Ready-Made Template and Customize It Your Way

Every template is fully editable. Adjust fields, workflows, and branding to match your processes, then deploy to your team instantly.