{"id":80992,"date":"2026-09-18T08:11:59","date_gmt":"2026-09-18T11:11:59","guid":{"rendered":"https:\/\/a3aengenharia.com\/?post_type=articles&#038;p=80992"},"modified":"2026-09-18T08:11:59","modified_gmt":"2026-09-18T11:11:59","slug":"failure-analysis-methodology-evidence-mechanisms-engineering","status":"publish","type":"articles","link":"https:\/\/a3aengenharia.com\/en-us\/content\/technical-articles\/failure-analysis-methodology-evidence-mechanisms-engineering\/","title":{"rendered":"Failure Analysis: Methodology, Evidence, Mechanisms, and Engineering Applications"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Failure analysis is the technical process used to understand why an item, system, or process stopped performing its required function, which mechanisms contributed to the event, what evidence supports the conclusion, and which actions are needed to reduce the probability of recurrence. The objective is not simply to name a component that failed, but to reconstruct the event sequence in a technically defensible manner.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A consistent analysis distinguishes the occurrence, symptom, failure mode, physical or logical mechanism, cause, contributing factors, and consequence. This separation is essential because replacing the component that entered a failed state may restore the function without eliminating the condition that originated the failure. In complex systems, the cause may lie in design, installation, environment, operation, maintenance, configuration, procurement, software, interfaces between disciplines, or the decision-making process.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Failure analysis is therefore not synonymous with RCA, FMEA, or FTA. Failure analysis is a broader investigative process. RCA may be part of that process when root causes of an event that has already occurred need to be identified; FMEA is predominantly preventive and starts from possible failure modes; FTA starts from a top event and investigates causal combinations. Each technique answers a different question.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In asset-intensive organizations, failure analysis is also a governance tool. It converts field events into evidence for reviewing design, maintenance, operating criteria, spare parts, contracts, technical standards, asset data, and lifecycle decisions. When formalized, it stops being an isolated reactive activity and becomes part of a continuous reliability and improvement system.<\/p>\n\n\n\n\n<h2 class=\"wp-block-heading\">Failure, Failed State, Defect, Cause, and Mechanism: Why Terminology Matters<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">ABNT NBR 5462 establishes an important distinction among concepts that are often used as synonyms. A <strong>failure<\/strong> is the event that ends an item&#8217;s ability to perform a required function. A <strong>failed state<\/strong> is the resulting state of inability to perform that function. A <strong>defect<\/strong> is a deviation of a characteristic from a requirement and may exist without causing immediate failure.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The standard also distinguishes <strong>failure cause<\/strong> from <strong>failure mechanism<\/strong>. The cause is associated with design, manufacturing, or use circumstances that lead to the event. The mechanism is the physical, chemical, electrical, logical, or other process that actually leads to loss of function. This distinction is critical to avoiding superficial conclusions.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td>Concept<\/td><td>Engineering question<\/td><\/tr><tr><td>Defect<\/td><td>Which requirement or characteristic is outside the expected condition?<\/td><\/tr><tr><td>Failure<\/td><td>Which function stopped being performed, and when?<\/td><\/tr><tr><td>Failed state<\/td><td>What state of incapacity did the item enter after the failure?<\/td><\/tr><tr><td>Failure mode<\/td><td>How did the loss of function manifest itself?<\/td><\/tr><tr><td>Failure mechanism<\/td><td>Which process produced the degradation or rupture?<\/td><\/tr><tr><td>Cause<\/td><td>Which circumstances enabled or triggered the mechanism?<\/td><\/tr><tr><td>Consequence<\/td><td>What operational, economic, safety, or compliance effect resulted?<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">This terminological discipline connects the analysis with <a href=\"\/servicos\/operacao\/engenharia-de-confiabilidade-e-disponibilidade\/\">Reliability and Availability Engineering<\/a> and with the content on <a href=\"\/conteudo\/artigos-tecnicos\/engenharia-manutencao-planejamento-confiabilidade-backlog-desempenho\/\">Maintenance Engineering<\/a>, because it allows actual events to be related to failure modes, maintenance strategies, and performance requirements.<\/p>\n\n\n\n\n<h2 class=\"wp-block-heading\">When a Failure Requires a Structured Investigation<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Not every failed state requires a full investigation. The depth should be proportional to criticality, recurrence, uncertainty, and consequence. A simple replacement may be sufficient for a noncritical item whose cause is known and whose residual risk is low. Events involving safety, significant downtime, repeated failures, contractual impact, or an unknown cause require a different level of treatment.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Typical criteria for opening a structured analysis include:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>failure of a critical asset or function;<\/li><li>recurrence of the same failure mode;<\/li><li>safety, environmental, or compliance consequence;<\/li><li>significant downtime or production loss;<\/li><li>occurrence in new, recently commissioned, or in-warranty equipment;<\/li><li>divergence between observed behavior and design assumptions;<\/li><li>simultaneous or apparently common failure in redundant systems;<\/li><li>an event whose cause remains uncertain after maintenance diagnostics;<\/li><li>the need to support a contractual, technical, or investment decision.<\/li><\/ul>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"\/conteudo\/artigos-tecnicos\/analise-criticidade-ativos-criterios-matriz-priorizacao\/\">Asset Criticality Analysis<\/a> helps define when investigation resources should be mobilized. In larger organizations, the trigger can be formalized through <a href=\"\/solucoes\/gestao-e-governanca-de-engenharia\/gestao-processos-workflows-aprovacoes-tecnicas\/\">Process, Workflow, and Technical Approval Management<\/a>, preventing relevant events from being closed merely as corrective work orders.<\/p>\n\n\n\n\n<h2 class=\"wp-block-heading\">Evidence Preservation: The First Step in the Analysis<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">One of the most common failures in the investigative process itself occurs before the analysis begins: equipment is disassembled, cleaned, reconfigured, restarted, or discarded without an adequate record of the condition found. This can destroy critical evidence and make it impossible to distinguish cause from consequence.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The <strong>as-found<\/strong> condition should be preserved to the extent compatible with safety and operational continuity. The record may include photographs, switch positions, alarms, logs, temperature, protection status, configuration, firmware, recent intervention history, diagrams, process trends, power quality, removed parts, physical traces, and statements from the teams involved.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In digital or automated environments, preservation may involve logs from servers, switches, VMS, PLCs, relays, BMS, SCADA, monitoring systems, and management platforms. In electromechanical equipment, it may involve measurements, oil samples, fracture surfaces, residues, clearances, wear, insulation, torque, vibration, or thermography.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">When the analysis has contractual, warranty, or safety implications, evidence governance needs to be even more rigorous. <a href=\"\/solucoes\/gestao-e-governanca-de-engenharia\/gestao-requisitos-evidencias-criterios-aceite\/\">Requirements, Evidence, and Acceptance Criteria Management<\/a> and <a href=\"\/solucoes\/gestao-e-governanca-de-engenharia\/governanca-documental-sistema-gestao-documentos\/\">Document Governance<\/a> make it possible to control the origin, version, authorship, integrity, and traceability of the records used in the conclusion.<\/p>\n\n\n\n\n<h2 class=\"wp-block-heading\">How to Structure a Failure Analysis Step by Step<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A technically consistent investigation can be organized into the following work sequence:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">1. <strong>Define the lost function and the event under analysis.<\/strong> Avoid vague descriptions such as \u201cequipment burned out.\u201d 2. <strong>Establish the system boundary.<\/strong> Define the equipment, interfaces, utilities, software, people, and conditions included. 3. <strong>Preserve and record the condition found.<\/strong> Document evidence before changing the system. 4. <strong>Build the timeline.<\/strong> Relate operation, alarms, interventions, changes, and preceding events. 5. <strong>Characterize the failure mode.<\/strong> Describe how the loss of function manifested itself. 6. <strong>Formulate hypotheses.<\/strong> List technically plausible mechanisms and causes. 7. <strong>Select tests and checks.<\/strong> Seek evidence capable of confirming or refuting each hypothesis. 8. <strong>Reconstruct the causal chain.<\/strong> Separate immediate cause, mechanism, contributing factors, and systemic causes. 9. <strong>Assess the extent of condition.<\/strong> Verify whether the problem may exist in similar or redundant assets, or in assets installed under the same assumption. 10. <strong>Define actions.<\/strong> Address containment, correction, prevention, redesign, plan revision, data, or process. 11. <strong>Validate effectiveness.<\/strong> Confirm that the actions actually reduced risk or eliminated the condition. 12. <strong>Record the learning.<\/strong> Update documentation, standards, plans, registers, requirements, and lessons learned.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This sequence can be adapted to the type of asset. Its value lies in maintaining traceability across <strong>evidence \u2192 hypothesis \u2192 test \u2192 conclusion \u2192 action<\/strong>.<\/p>\n\n\n\n<div class=\"wp-block-a3a-destaque\">\n<p class=\"wp-block-paragraph\"><strong>A plausible hypothesis is not a proven cause.<\/strong> Critical investigations need to preserve evidence, test alternative explanations, and maintain traceability between hypothesis, test, and conclusion.<\/p>\n\n\n<p class=\"wp-block-paragraph\"><a href=\"\/servicos\/levantamento-e-diagnostico\/auditoria-tecnica\/\"><strong>Explore Engineering Technical Audit \u2192<\/strong><\/a><\/p>\n<\/div>\n\n\n\n\n<h2 class=\"wp-block-heading\">Hypotheses and Verification: Avoiding Conclusions Based on Plausibility<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A technically plausible hypothesis is not a proven cause. In failure investigations, a team may recognize a familiar pattern and close the analysis before testing alternative explanations. This bias can be reinforced when the first hypothesis is presented by someone with strong technical authority or when the proposed solution is operationally convenient.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The method should seek evidence that can <strong>confirm and also refute<\/strong> each hypothesis. If the proposed cause is overheating, thermal signs, ventilation conditions, load, protection, environment, and history need to be checked. If the hypothesis is a configuration error, backups, logs, revisions, permissions, changes, and system behavior should be compared. If the hypothesis is a power-supply failure, the analysis needs to consider power quality, protection, coordination, connections, and upstream events.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The logic is similar to that used in <a href=\"\/conteudo\/artigos-tecnicos\/analise-causa-raiz-rca-metodologia-tecnicas-falhas-engenharia\/\">Root Cause Analysis \u2014 RCA<\/a>, but failure analysis may end before a complete RCA when the objective is to technically characterize the mode and mechanism. When the occurrence has relevant organizational, human, or process causes, RCA broadens the investigation.<\/p>\n\n\n\n\n<h2 class=\"wp-block-heading\">Tests and Data That Can Support the Investigation<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">There is no universal test package. Methods depend on the technology, the suspected mechanism, and the available evidence. Across different disciplines, an analysis may use:<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td>Domain<\/td><td>Examples of evidence and techniques<\/td><\/tr><tr><td>Electrical<\/td><td>oscillography, power quality, insulation resistance, thermography, protection coordination, relay records<\/td><\/tr><tr><td>Mechanical<\/td><td>vibration, alignment, oil analysis, metallography, fracture analysis, wear, clearances, nondestructive testing<\/td><\/tr><tr><td>Automation<\/td><td>PLC\/SCADA logs, sequence of events, I\/O states, firmware, logic, and change history<\/td><\/tr><tr><td>Networks and telecom<\/td><td>syslog, SNMP, NetFlow, interface errors, optical loss, OTDR, topology, redundancy, configurations<\/td><\/tr><tr><td>Data Center<\/td><td>BMS\/DCIM, UPS\/STS\/PDU events, temperature, load, batteries, generators, alarms, and transfers<\/td><\/tr><tr><td>Electronic security<\/td><td>VMS, storage, camera, controller, network, synchronization, recording, and integration-event logs<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">A3A Engenharia works across critical infrastructure disciplines, allowing the analysis to be connected to the system architecture. Projects such as <a href=\"\/projetos\/projeto-de-monitoramento-operativo-para-suporte-a-teleassistencia-em-subestacao-londrina-parana\/\">operational monitoring to support remote assistance at a substation<\/a>, the <a href=\"\/projetos\/front-end-engineering-design-para-sistema-de-telecomunicacoes-em-usina-hidreletrica-braunas-minas-gerais\/\">telecommunications FEED for a hydroelectric plant<\/a>, and the <a href=\"\/projetos\/implantacao-turnkey-de-sistema-integrado-de-videomonitoramento-inteligente-em-complexo-governamental-brasilia-distrito-federal\/\">turnkey implementation of video monitoring at a government complex<\/a> illustrate environments in which function depends on interfaces among power, networks, software, infrastructure, and operation.<\/p>\n\n\n\n\n<h2 class=\"wp-block-heading\">Failure Analysis, RCA, FMEA, FTA, and RAM<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The techniques are complementary, but they should not be used as different names for the same analysis.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td>Technique<\/td><td>Starting point<\/td><td>Central question<\/td><\/tr><tr><td>Failure Analysis<\/td><td>occurrence, component, or lost function<\/td><td>what failed, how did it occur, and what evidence explains the mechanism?<\/td><\/tr><tr><td>RCA<\/td><td>event that occurred<\/td><td>why did the event happen and which causes need to be removed?<\/td><\/tr><tr><td>FMEA\/FMECA<\/td><td>item, function, or process<\/td><td>how can it fail and what effects and criticalities result?<\/td><\/tr><tr><td>FTA<\/td><td>top event<\/td><td>which combinations can produce this event?<\/td><\/tr><tr><td>RAM<\/td><td>architecture and failure\/repair data<\/td><td>what reliability, availability, and maintainability does the system deliver?<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"\/conteudo\/artigos-tecnicos\/fmea-engenharia-modos-efeitos-causas-falha\/\">FMEA<\/a> helps verify whether the observed mode had already been anticipated and which barriers should have existed. <a href=\"\/conteudo\/artigos-tecnicos\/fta-analise-arvore-falhas-metodo-portas-logicas-calculo-aplicacao\/\">FTA<\/a> is useful when the event depends on combinations or redundancy. <a href=\"\/conteudo\/artigos-tecnicos\/analise-ram-reliability-availability-maintainability-engenharia\/\">RAM Analysis<\/a> makes it possible to evaluate the effect of failures and repairs on system performance. <a href=\"\/conteudo\/artigos-tecnicos\/analise-weibull-distribuicao-curva-banheira-confiabilidade\/\">Weibull Analysis<\/a> helps when statistical behavior over time is relevant.<\/p>\n\n\n\n\n<h2 class=\"wp-block-heading\">From Technical Failure to Systemic Cause<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A mature investigation does not stop at the damaged part. A contactor may have failed because of overheating, but the overheating may be related to inadequate tightening, incorrect specification, overload, insufficient ventilation, installation quality, or inadequate maintenance. An electronic board may show damage, while the dominant cause may lie in a surge, grounding, environment, firmware, or auxiliary power.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It is therefore useful to distinguish at least four levels:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li><strong>observed effect:<\/strong> what operations perceived;<\/li><li><strong>mode\/mechanism:<\/strong> how the item lost its function;<\/li><li><strong>technical cause:<\/strong> the condition that originated or enabled the mechanism;<\/li><li><strong>systemic cause:<\/strong> the process, requirement, decision, or governance condition that allowed it to remain.<\/li><\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This last layer connects the analysis with <a href=\"\/conteudo\/artigos-tecnicos\/technical-authority-engenharia-autoridade-tecnica-governanca-decisoes\/\">Technical Authority in Engineering<\/a>, <a href=\"\/conteudo\/artigos-tecnicos\/project-assurance-engenharia-revisao-independente-governanca\/\">Project Assurance<\/a>, and <a href=\"\/conteudo\/guias-tecnicos\/gestao-de-engenharia-processos-governanca-projetos-desempenho\/\">Engineering Management<\/a>. Recurrence often does not result from a lack of technical knowledge, but from the absence of a process that converts knowledge into controlled decisions.<\/p>\n\n\n\n<div class=\"wp-block-a3a-destaque\">\n<p class=\"wp-block-paragraph\"><strong>A relevant failure needs to generate engineering evidence, not merely a corrective work order.<\/strong> Criteria, owners, versions, conclusions, and actions should remain traceable to support future decisions and audits.<\/p>\n\n\n<p class=\"wp-block-paragraph\"><a href=\"\/solucoes\/gestao-e-governanca-de-engenharia\/gestao-requisitos-evidencias-criterios-aceite\/\"><strong>Explore Requirements, Evidence, and Acceptance Criteria Management \u2192<\/strong><\/a><\/p>\n<\/div>\n\n\n\n\n<h2 class=\"wp-block-heading\">Analysis Governance: Roles, Independence, and Traceability<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Analyses with significant impact need proportionate governance. There should be an investigation owner, criteria for participation by operations, maintenance, engineering, suppliers, and safety, as well as rules for reviewing and approving conclusions.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In certain cases, the team that designed, installed, or operated the system should not be solely responsible for validating the cause. Independent review reduces bias and increases confidence in the conclusion, especially when the analysis supports acceptance, warranty, technical accountability, or an investment decision.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"\/servicos\/levantamento-e-diagnostico\/auditoria-tecnica\/\">Engineering Technical Audit<\/a> and <a href=\"\/servicos\/planejamento\/revisao-validacao-tecnica-projetos-design-review\/\">Design Review<\/a> can form part of this assurance layer. In contracts or projects of greater complexity, <a href=\"\/servicos\/contratacao-integrada\/engenharia-do-proprietario\/\">Owner\u2019s Engineering<\/a> maintains the owner\u2019s perspective on requirements, evidence, acceptance, and residual risk.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Corrective Actions: Correct, Prevent, and Verify Effectiveness<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A good analysis separates containment actions from actions that address the cause. Replacing a component, restarting a service, applying an emergency patch, or operating in contingency may be necessary to restore function, but this does not mean recurrence risk has been reduced.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Actions may include:<\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>correction or replacement of the item;<\/li><li>design or architecture review;<\/li><li>change of specification or supplier;<\/li><li>changes to protection, redundancy, or segregation;<\/li><li>update of operating procedures;<\/li><li>revision of the <a href=\"\/conteudo\/artigos-tecnicos\/plano-manutencao-atividades-frequencias-criterios\/\">Maintenance Plan<\/a>;<\/li><li>change of inspection frequency, condition, or technique;<\/li><li>update of spare-parts and support strategy;<\/li><li>improvement of asset registers, instrumentation, or monitoring;<\/li><li>review of training, competence, or authorization;<\/li><li>change to workflow, approval, or management-of-change controls.<\/li><\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">An action should be considered closed only when there is evidence of implementation and a criterion for evaluating effectiveness. This discipline prevents the organization from accumulating technically correct reports without effectively reducing recurrence.<\/p>\n\n\n\n\n<h2 class=\"wp-block-heading\">How to Integrate Failure Analysis with Maintenance Planning and Asset Management<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><a href=\"\/conteudo\/artigos-tecnicos\/pcm-planejamento-controle-manutencao-processo-backlog-programacao-indicadores\/\">Maintenance Planning and Control<\/a> should operate as one of the mechanisms for capturing events that require investigation. Corrective work orders, recurring events, rework, failures in critical assets, and anomalies without a defined cause can generate formal triggers for analysis.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Results return to the maintenance system through revisions to plans, criticality, asset registers, parts, procedures, and acceptance criteria. At the same time, <a href=\"\/conteudo\/artigos-tecnicos\/indicadores-manutencao-kpis-formulas-metas-painel\/\">Maintenance KPIs<\/a> make it possible to verify whether actions reduced recurrence, downtime, rework, or emergency work.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">At the <a href=\"\/conteudo\/artigos-tecnicos\/gestao-ativos-ciclo-vida-valor-risco-desempenho\/\">Asset Management<\/a> level, the analysis may change refurbishment, recommissioning, modernization, or replacement decisions. When a failure reveals a structural limitation of the asset, continuing to optimize maintenance may be economically inferior to a lifecycle intervention.<\/p>\n\n\n\n<div class=\"wp-block-a3a-destaque\">\n<p class=\"wp-block-paragraph\"><strong>When a failure affects availability, safety, warranty, or an investment decision, the investigation needs to go beyond maintenance diagnostics.<\/strong> Reliability engineering integrates evidence, mechanisms, risk, and actions into a technically defensible conclusion.<\/p>\n\n\n<p class=\"wp-block-paragraph\"><a href=\"\/servicos\/operacao\/engenharia-de-confiabilidade-e-disponibilidade\/\"><strong>Explore Reliability and Availability Engineering \u2192<\/strong><\/a><\/p>\n<\/div>\n\n\n\n\n<h2 class=\"wp-block-heading\">Failure Analysis as an Engineering Consulting Service<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When an event involves significant complexity, criticality, or contractual impact, the analysis can be structured as an engineering service with clearly defined scope, evidence, assumptions, methods, and deliverables. The work may include field surveys, technical interviews, review of historical records, testing, document analysis, modeling, multidisciplinary workshops, independent review, and an action plan.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A deliverable structure may include an as-found condition report, timeline, functional definition, hypothesis-and-evidence matrix, test results, failure mechanism, technical and systemic causes, extent of condition, residual risk, and a prioritized action plan. Depending on the case, the work may evolve into <a href=\"\/servicos\/operacao\/engenharia-de-confiabilidade-e-disponibilidade\/\">Reliability and Availability Engineering<\/a>, <a href=\"\/servicos\/operacao\/engenharia-de-manutencao\/\">Maintenance Engineering<\/a>, <a href=\"\/servicos\/servicos-transversais\/gerenciamento-de-riscos-de-engenharia\/\">Engineering Risk Management<\/a>, or <a href=\"\/servicos\/contratacao-integrada\/servicos-continuados-de-engenharia-consultiva\/\">Ongoing Engineering Consulting Services<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The value of the analysis lies in turning an isolated event into reusable knowledge. When evidence, decisions, and actions remain traceable, each failure can improve future design, operation, and maintenance instead of merely generating another corrective work order.<\/p>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Technical references<\/summary>\n<p class=\"wp-block-paragraph\">[1] ABNT. <a href=\"https:\/\/www.abntcatalogo.com.br\/\">NBR 5462:1994 \u2014 Reliability and maintainability \u2014 Terminology<\/a>. Rio de Janeiro: ABNT, 1994.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">[2] IEC. <a href=\"https:\/\/webstore.iec.ch\/en\/publication\/21810\">IEC 62740:2015 \u2014 Root cause analysis (RCA)<\/a>. Geneva: IEC, 2015.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">[3] IEC. <a href=\"https:\/\/webstore.iec.ch\/en\/publication\/26359\">IEC 60812:2018 \u2014 Failure modes and effects analysis (FMEA and FMECA)<\/a>. Geneva: IEC, 2018.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">[4] IEC. <a href=\"https:\/\/webstore.iec.ch\/en\/publication\/4311\">IEC 61025:2006 \u2014 Fault tree analysis (FTA)<\/a>. Geneva: IEC, 2006.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">[5] IEC. <a href=\"https:\/\/webstore.iec.ch\/en\/publication\/1294\">IEC 60300-3-1:2003 \u2014 Dependability management \u2014 Analysis techniques for dependability<\/a>. Geneva: IEC, 2003.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">[6] ISO. <a href=\"https:\/\/www.iso.org\/standard\/83054.html\">ISO 55001:2024 \u2014 Asset management \u2014 Asset management system \u2014 Requirements<\/a>. Geneva: ISO, 2024.<\/p>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Frequently asked questions<\/summary>\n<div class=\"schema-faq wp-block-yoast-faq-block\"><div class=\"schema-faq-section\" id=\"faq-question-o-que-an-lise-de-falhas-e2fd9e6b\"><strong class=\"schema-faq-question\">What is failure analysis?<\/strong> <p class=\"schema-faq-answer\">It is the technical process of investigating an event to identify the lost function, failure mode and mechanism, evidence, causes, and actions required to reduce the probability of recurrence.<\/p><\/div><div class=\"schema-faq-section\" id=\"faq-question-qual-a-diferen-a-entre-falha-e-pane-28ef2394\"><strong class=\"schema-faq-question\">What is the difference between a failure and a failed state?<\/strong> <p class=\"schema-faq-answer\">In NBR 5462 terminology, failure is the event that ends the ability to perform a required function; a failed state is the resulting state of incapacity.<\/p><\/div><div class=\"schema-faq-section\" id=\"faq-question-an-lise-de-falhas-a-mesma-coisa-que-rca-276da914\"><strong class=\"schema-faq-question\">Is failure analysis the same as RCA?<\/strong> <p class=\"schema-faq-answer\">No. Failure analysis is broader and may include characterization of the mode, mechanism, and evidence. RCA is a specific technique for investigating root causes of events that have occurred.<\/p><\/div><div class=\"schema-faq-section\" id=\"faq-question-quando-uma-falha-deve-ser-investigada-formalment-0df78769\"><strong class=\"schema-faq-question\">When should a failure be formally investigated?<\/strong> <p class=\"schema-faq-answer\">When there is criticality, recurrence, significant impact, an unknown cause, safety or compliance risk, redundancy failure, contractual implications, or a need for an engineering decision.<\/p><\/div><div class=\"schema-faq-section\" id=\"faq-question-quais-t-cnicas-podem-ser-usadas-em-uma-an-lise-d-29500d9a\"><strong class=\"schema-faq-question\">Which techniques can be used in a failure analysis?<\/strong> <p class=\"schema-faq-answer\">Depending on the case, visual inspection, electrical and mechanical testing, thermography, vibration, oil analysis, logs, FMEA, FTA, RCA, RAM, Weibull, and other specialized techniques may be used.<\/p><\/div><div class=\"schema-faq-section\" id=\"faq-question-como-saber-se-a-a-o-corretiva-foi-eficaz-b84b3872\"><strong class=\"schema-faq-question\">How can you tell whether a corrective action was effective?<\/strong> <p class=\"schema-faq-answer\">The action needs a verification criterion and should be monitored through evidence and indicators capable of demonstrating a reduction in recurrence, risk, or associated downtime.<\/p><\/div><\/div>\n<\/details>\n\n\n\n<details class=\"wp-block-details is-layout-flow wp-block-details-is-layout-flow\"><summary>Related technical materials<\/summary>\n<p class=\"wp-block-paragraph\"><strong>Related solutions<\/strong><\/p>\n\n\n<ul class=\"wp-block-list\"><li><a href=\"\/solucoes\/gestao-e-governanca-de-engenharia\/gestao-requisitos-evidencias-criterios-aceite\/\">Requirements, Evidence, and Acceptance Criteria Management<\/a><\/li><li><a href=\"\/solucoes\/gestao-e-governanca-de-engenharia\/gestao-processos-workflows-aprovacoes-tecnicas\/\">Process, Workflow, and Technical Approval Management<\/a><\/li><li><a href=\"\/solucoes\/gestao-e-governanca-de-engenharia\/governanca-documental-sistema-gestao-documentos\/\">Document Governance and Document Management System<\/a><\/li><li><a href=\"\/solucoes\/gestao-e-governanca-de-engenharia\/indicadores-dashboards-relatorios-executivos-engenharia\/\">Engineering Indicators, Dashboards, and Executive Reports<\/a><\/li><li><a href=\"\/solucoes\/gestao-e-governanca-de-engenharia\/gestao-conhecimento-tecnico-licoes-aprendidas\/\">Technical Knowledge Management and Lessons Learned<\/a><\/li><\/ul>\n\n\n<p class=\"wp-block-paragraph\"><strong>Related engineering services<\/strong><\/p>\n\n\n<ul class=\"wp-block-list\"><li><a href=\"\/servicos\/operacao\/engenharia-de-confiabilidade-e-disponibilidade\/\">Reliability and Availability Engineering<\/a><\/li><li><a href=\"\/servicos\/operacao\/engenharia-de-manutencao\/\">Maintenance Engineering<\/a><\/li><li><a href=\"\/servicos\/levantamento-e-diagnostico\/auditoria-tecnica\/\">Engineering Technical Audit<\/a><\/li><li><a href=\"\/servicos\/servicos-transversais\/gerenciamento-de-riscos-de-engenharia\/\">Engineering Risk Management<\/a><\/li><li><a href=\"\/servicos\/planejamento\/revisao-validacao-tecnica-projetos-design-review\/\">Engineering Design Review<\/a><\/li><li><a href=\"\/servicos\/contratacao-integrada\/engenharia-do-proprietario\/\">Owner\u2019s Engineering<\/a><\/li><li><a href=\"\/servicos\/contratacao-integrada\/servicos-continuados-de-engenharia-consultiva\/\">Ongoing Engineering Consulting Services<\/a><\/li><\/ul>\n\n\n<p class=\"wp-block-paragraph\"><strong>Related technical content<\/strong><\/p>\n\n\n<ul class=\"wp-block-list\"><li><a href=\"\/conteudo\/artigos-tecnicos\/analise-causa-raiz-rca-metodologia-tecnicas-falhas-engenharia\/\">Root Cause Analysis \u2014 RCA<\/a><\/li><li><a href=\"\/conteudo\/artigos-tecnicos\/fmea-engenharia-modos-efeitos-causas-falha\/\">FMEA in Engineering<\/a><\/li><li><a href=\"\/conteudo\/artigos-tecnicos\/fta-analise-arvore-falhas-metodo-portas-logicas-calculo-aplicacao\/\">FTA \u2014 Fault Tree Analysis<\/a><\/li><li><a href=\"\/conteudo\/artigos-tecnicos\/analise-ram-reliability-availability-maintainability-engenharia\/\">RAM Analysis<\/a><\/li><li><a href=\"\/conteudo\/artigos-tecnicos\/analise-weibull-distribuicao-curva-banheira-confiabilidade\/\">Weibull Analysis<\/a><\/li><li><a href=\"\/conteudo\/artigos-tecnicos\/analise-criticidade-ativos-criterios-matriz-priorizacao\/\">Asset Criticality Analysis<\/a><\/li><li><a href=\"\/conteudo\/artigos-tecnicos\/pcm-planejamento-controle-manutencao-processo-backlog-programacao-indicadores\/\">Maintenance Planning and Control<\/a><\/li><li><a href=\"\/conteudo\/artigos-tecnicos\/indicadores-manutencao-kpis-formulas-metas-painel\/\">Maintenance KPIs<\/a><\/li><\/ul>\n\n\n<p class=\"wp-block-paragraph\"><strong>Governance and further reading<\/strong><\/p>\n\n\n<ul class=\"wp-block-list\"><li><a href=\"\/conteudo\/guias-tecnicos\/gestao-de-engenharia-processos-governanca-projetos-desempenho\/\">Engineering Management: Processes, Governance, Projects, and Performance<\/a><\/li><li><a href=\"\/conteudo\/artigos-tecnicos\/technical-authority-engenharia-autoridade-tecnica-governanca-decisoes\/\">Technical Authority in Engineering<\/a><\/li><li><a href=\"\/conteudo\/artigos-tecnicos\/project-assurance-engenharia-revisao-independente-governanca\/\">Project Assurance in Engineering<\/a><\/li><\/ul>\n<\/details>\n","protected":false},"excerpt":{"rendered":"<p>Failure analysis in engineering: methodology, evidence, mechanisms, causes, testing, RCA, FMEA, FTA, governance, and corrective actions.<\/p>\n","protected":false},"author":1,"featured_media":78885,"parent":0,"template":"","meta":{"_a3a_global_related_solutions":[],"_a3a_global_related_services":[],"_a3a_global_related_materials":[],"_a3a_post_lang":"en-us","_a3a_translation_group_id":"7ddf086e-7ac7-4f47-a697-28107a9d9741","_a3a_i18n_canonical_slug":"failure-analysis-methodology-evidence-mechanisms-engineering","_a3a_prod_post_id":"","_a3a_lang_url_en-us":"","_a3a_lang_url_es-es":""},"categories":[],"segments":[],"mercados":[],"etapas":[],"class_list":["post-80992","articles","type-articles","status-publish","has-post-thumbnail","hentry"],"_links":{"self":[{"href":"https:\/\/a3aengenharia.com\/en-us\/wp-json\/wp\/v2\/articles\/80992","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/a3aengenharia.com\/en-us\/wp-json\/wp\/v2\/articles"}],"about":[{"href":"https:\/\/a3aengenharia.com\/en-us\/wp-json\/wp\/v2\/types\/articles"}],"author":[{"embeddable":true,"href":"https:\/\/a3aengenharia.com\/en-us\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":1,"href":"https:\/\/a3aengenharia.com\/en-us\/wp-json\/wp\/v2\/articles\/80992\/revisions"}],"predecessor-version":[{"id":80993,"href":"https:\/\/a3aengenharia.com\/en-us\/wp-json\/wp\/v2\/articles\/80992\/revisions\/80993"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/a3aengenharia.com\/en-us\/wp-json\/wp\/v2\/media\/78885"}],"wp:attachment":[{"href":"https:\/\/a3aengenharia.com\/en-us\/wp-json\/wp\/v2\/media?parent=80992"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/a3aengenharia.com\/en-us\/wp-json\/wp\/v2\/categories?post=80992"},{"taxonomy":"segments","embeddable":true,"href":"https:\/\/a3aengenharia.com\/en-us\/wp-json\/wp\/v2\/segments?post=80992"},{"taxonomy":"mercados","embeddable":true,"href":"https:\/\/a3aengenharia.com\/en-us\/wp-json\/wp\/v2\/mercados?post=80992"},{"taxonomy":"etapas","embeddable":true,"href":"https:\/\/a3aengenharia.com\/en-us\/wp-json\/wp\/v2\/etapas?post=80992"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}