Bottom-Up Methodology to Track Root Cause?

[MickyQuality]

Hello,

Is it interesting to use after 5W a bottom-up methodology to track root cause like in audit. I mean first the use of FTA (Fault Tree Analysis)+5W for occurrence and detection then:

1)Start gemba, check operator's work
2)Instructions checking
3)Process&product control plan, maintenance plan checking
4)PFME, DFMEA checking
5)Functional analysis checking

I know that an incident not only comes from documentation mistakes, but doing this should prevent you from any oversight because it shows you the link between product development steps. Moreover you will be sure that the incident will.

Is it interesting or a to big workload doing it?

Thanks

[qusys]

In Reply to Parent Post by MickyQuality

Hello,

Is it interesting to use after 5W a bottom-up methodology to track root cause like in audit. I mean first the use of FTA (Fault Tree Analysis)+5W for occurrence and detection then:

1)Start gemba, check operator's work
2)Instructions checking
3)Process&product control plan, maintenance plan checking
4)PFME, DFMEA checking
5)Functional analysis checking

I know that an incident not only comes from documentation mistakes, but doing this should prevent you from any oversight because it shows you the link between product development steps. Moreover you will be sure that the incident will.

Is it interesting or a to big workload doing it?

Thanks

I do not like to speak of bottom up methodology.
Instead I believe in the cross team work and multidisciplinary approach in root cause fixing, depending on the magnitude of the issue.
You should create a team with different experience and competences to face the issue, adopting the techniques of problem solving.
I think that this is good also for higher level of management to face issue and put in place corrective action.

[bharatbuk]

The bottom-up multilayer network recovery method based on a root-cause analysis includes: simultaneously counting, by a fault detection layer,a root-cause analysis (RA) time and a hold-off (HO) time, upon detecting an occurrence of a fault; performing, by the fault detection layer, a root-cause analysis during the RA time to recognize a layer in which a root-cause has occurred; when the root-cause has occurred in the fault detection layer, immediately recovering the fault by the fault detection layer, and when a root-cause has occurrence in a lower layer,waiting for the HO time until such time as the lower layer can recover the fault; and when the fault has not been recovered even after the HO time has lapsed, recovering the fault by the fault detection layer.

[Stijloor]

In Reply to Parent Post by bharatbuk

The bottom-up multilayer network recovery method based on a root-cause analysis includes: simultaneously counting, by a fault detection layer,a root-cause analysis (RA) time and a hold-off (HO) time, upon detecting an occurrence of a fault; performing, by the fault detection layer, a root-cause analysis during the RA time to recognize a layer in which a root-cause has occurred; when the root-cause has occurred in the fault detection layer, immediately recovering the fault by the fault detection layer, and when a root-cause has occurrence in a lower layer,waiting for the HO time until such time as the lower layer can recover the fault; and when the fault has not been recovered even after the HO time has lapsed, recovering the fault by the fault detection layer.

This is very confusing!

[harry]

In Reply to Parent Post by Stijloor

This is very confusing!

See: BOTTOM-UP MULTILAYER NETWORK RECOVERY METHOD ...

Inventors: Tae Hyun Kwon, Hyung Seok Chung, You Hyeon Jeong, Ho Young Song, Young Wook Cha, Choon Hee Kim, Jin Nyun Kim
Original Assignee: Electronics and Telecommunications Research Institute
Current U.S. Classification: 714/2; 714/E11.023

View patent at USPTO
Search USPTO Assignment Database