That's root cause analysis for you.
这就是所谓的根源分析。
So what is the best way to conduct a root cause analysis?
那么进行根本原因分析的最好的方式是什么呢？
Which situations are instant candidates for root cause analysis?
在哪些情况下需要立即进行根源分析？
Which situations can be acceptably handled without root cause analysis?
哪些情况可以在不进行根源分析的前提下以可接受的方式加以处理？
Root cause analysis could have nipped compounding problems in the bud.
根本原因分析可能会使萌芽状态的问题更加复杂。
The root cause analysis was not available in internal audit NC report.
根本原因分析，不可用数控内部审计报告。
Participate root cause analysis for machine breakdown issue and figure out corrective actions;
参与设备停机根本问题分析并制定改善对策；
Understand the principles of root cause analysis and practice the analysis on tangible issues;
了解根源性分析的原则并针对所勘不符点进行根源分析实践；
Nevertheless, I recently came across a brilliant piece of root cause analysis. It went like this.
不过我近期看了一篇有才气的问题根源分析。
Risk analysis should follow the principle of "root cause analysis" and adopt different framework.
风险分析应遵循“根原因分析”的原则，可以采用不同的分析框架。
Root cause analysis is essential to effective performance management in any application architecture environment.
在任何应用程序架构环境中，根源分析对有效的性能管理都是非常重要的。
The organization should incorporate root-cause analysis, as appropriate, into the corrective-action process.
适当时，组织应当对不合格根本原因的分析纳入纠正措施过程。
Conduct preventive action analysis to determine root cause and the necessary measure to avoid re-occurrence.
实行预防措施分析，确定问题根源并实行必要措施以避免问题的重复出现。
Conduct preventive action analysis to determine root cause and the necessary measure to avoid re-occurrence.
实行预防措施分析，确定问题根源并实行必要措施以避免问题的重复出现。
应用推荐