Skip to main content

We are trying to build a Fault Tree based on the FMEA built by our company. 

The configuration today is:

ELECTRIC MOTOR (Item class)
  CONVERT ELECTRIC ENERGY TO MECHANICAL ENERGY (Function)

     BEARING FAILURE (Fault Type)
           OHE - OVERHEATING (Symptom)

           OIL CONTAMINATION (Cause)
 

This is the standard IFS functionality, is someone using in a different way? Where you can put the effect of the Failure, or using the  “Failling component” inside the Cause?
If someone can share how is the tree inside the FASN.

Hi Hugo,

Here, you can add a failing component to the Cause. Then, you can include Corrective Actions into the causes and connect a Work Task Template as well.

I have attached a screenshot below; it is from IFS Cloud. You can also check with Apps10.

 

I hope this will be helpful!

Just FYI, in IFS Cloud 24R2 IFS developed a brand new FMECA functionality. It uses some concepts from earlier releases but most of it is new. 

hi ​@Dimuthu Madhushan, 
We are using the Fault type for the maintainable item, from a IFS view the what is the definition of Fault type?

Hi

The definition in IFS Cloud is “The identity of the fault type. The fault types are related to the functions in which the fault type can occur”. Additionally, it refers to a specific classification or category of an issue, error, or malfunction that occurs within a system, equipment, or process.

​@Dimuthu Madhushan can you bring some example?

 

Depending on context; these can be examples

  1. Mechanical Fault – Issues like wear and tear, misalignment, or broken parts.
  2. Electrical Fault – Includes short circuits, grounding issues, or blown fuses.
  3. Process Fault – Deviations from normal operating parameters, such as pressure or temperature.

Reply


Terms & ConditionsCookie settings