{"id":4854,"date":"2026-11-10T14:00:00","date_gmt":"2026-11-10T06:00:00","guid":{"rendered":"https:\/\/sayoon-dc.com\/?p=4854"},"modified":"2026-11-10T14:00:00","modified_gmt":"2026-11-10T06:00:00","slug":"dc-contactor-fmea-equipment-design-review","status":"publish","type":"post","link":"https:\/\/sayoon-dc.com\/nl\/blog\/dc-contactor-fmea-equipment-design-review\/","title":{"rendered":"DC Contactor FMEA: Een gids voor het beoordelen van apparatuurontwerp"},"content":{"rendered":"<p>A DC contactor FMEA review for equipment design should connect each required switching function to a possible failure, its effect on the equipment, the available detection and a verified design response. It should not stop at a list of damaged parts or assume that a normally open device always creates a safe condition. Begin with the exact circuit, operating states and ordered configuration. Then review the contactor together with its control supply, wiring, feedback and surrounding protection. This guide provides an application worksheet approach for design teams; it does not assign failure probabilities or certify a SAYOON product or a complete safety function.<\/p>\n<h2>Set the boundary before listing faults<\/h2>\n<p>Define what the contactor is expected to accomplish in the equipment. Carrying current during normal operation, closing during startup and opening during a controlled shutdown are separate functions with different conditions. An emergency response may impose another requirement. The required result must be defined by the equipment design, not inferred from the contactor&#8217;s catalogue name.<\/p>\n<p>Draw the boundary around the item being analysed. Include the main circuit interfaces and identify which coil driver, connectors and feedback devices are inside or outside the study. Record external assumptions explicitly. If another subsystem is supposed to remove energy after a fault, identify its requirement and verification record. An unnamed upstream controller is not evidence that the consequence has been controlled.<\/p>\n<h2>Separate failure mode, cause and effect<\/h2>\n<p>A failure mode describes how a function is lost or degraded, such as failure to open on command. A cause concerns why that mode might occur. The effect describes what happens locally and at higher equipment levels. Keeping these fields separate prevents a worksheet from treating a visible symptom as a complete explanation.<\/p>\n<p>For example, a hypothetical failure-to-close row might include an interrupted control path as one possible cause. The local effect is an unavailable closed current path; the equipment effect depends on the operating state and alternative energy paths. This example is a design prompt, not a finding about a particular product. The reviewer must confirm whether the proposed cause is physically possible in the actual design.<\/p>\n<figure><img decoding=\"async\" loading=\"lazy\" src=\"https:\/\/sayoon-dc.com\/wp-content\/uploads\/2026\/11\/dc-contactor-fmea-equipment-design-review-bodyOne-20261109-daily.png\" alt=\"CZW200A Normally Open DC Contactor with function and effect review headings\"><figcaption>Trace the required function through local and equipment effects before choosing an action.<\/figcaption><\/figure>\n<h2>Use operating states to reveal missing rows<\/h2>\n<p>Review storage and installation, commissioning, startup, normal running, planned shutdown and maintenance. Include credible transitions and abnormal conditions identified by the system risk assessment. A contactor state that is acceptable during transport may be unacceptable while equipment is delivering power. A detection method that works during startup may not operate during a short shutdown window.<\/p>\n<p>Keep the conditions with each row. Ask what information the controller has at that time and what action remains possible. If a test or diagnostic requires a state change, determine whether the equipment can safely enter that state. Do not assume every fault can be diagnosed by cycling the contactor while an uncontrolled load or stored energy remains connected.<\/p>\n<h2>Start with a qualitative review worksheet<\/h2>\n<div class=\"sy-table-wrap\">\n<table>\n<thead>\n<tr>\n<th>Evidence field<\/th>\n<th>Required information<\/th>\n<th>Review purpose<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Fails to close<\/td>\n<td>Required current path unavailable<\/td>\n<td>Check actual equipment state and response<\/td>\n<\/tr>\n<tr>\n<td>Fails to open<\/td>\n<td>Conductive path may remain<\/td>\n<td>Assess energy paths and protective response<\/td>\n<\/tr>\n<tr>\n<td>Degraded performance<\/td>\n<td>Required behaviour outside limits<\/td>\n<td>Define evidence-based acceptance criteria<\/td>\n<\/tr>\n<tr>\n<td>Interface failure<\/td>\n<td>Control or connection condition invalid<\/td>\n<td>Review boundaries, assumptions and verification<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<\/div>\n<p>The worksheet is a starting structure, not an exhaustive set of failures or an acceptance standard. NASA&#8217;s software safety material describes the bottom-up propagation of failures, while the Institute for Healthcare Improvement presents a structured FMEA process in its healthcare context. Their original application contexts remain relevant when interpreting them. Here, the contactor examples are engineering review prompts to be validated for the actual equipment.<\/p>\n<h2>Examine failure to close without assuming its cause<\/h2>\n<p>Consider the required control voltage at the device, supply behaviour during actuation, wiring continuity and any permitted polarity constraints. A missing close command and a mechanical inability to close have different causes, even when the equipment operator sees the same symptom. A controller output indication alone does not show that voltage reached the coil or the main contacts changed state.<\/p>\n<p>The design response may involve inhibiting the next operating step, issuing a meaningful fault message or entering an approved fallback state. Its suitability depends on the equipment requirements. Identify the observation that supports the decision and the test that verifies it. Avoid claiming that a generic alarm eliminates the fault consequence when the equipment can continue into an unsafe or damaging state.<\/p>\n<h2>Examine failure to open at equipment level<\/h2>\n<p>A request to open is not proof that the main circuit has become nonconductive. The review should consider credible failure mechanisms and other current paths identified by the circuit analysis. Determine the consequence of a remaining conductive path for stored energy, operator access and connected loads. A contactor should not be treated as a complete isolation procedure merely because it is commanded off.<\/p>\n<p>If the design relies on feedback, identify exactly what that feedback represents. An ordinary auxiliary indication should not be assumed to prove main-contact separation unless the specified construction and evidence support that interpretation. If independent energy removal or another protective measure is required, its capability, timing and verification belong in the system design record.<\/p>\n<h2>Include degraded performance and interfaces<\/h2>\n<p>Not every relevant failure is fully open or fully closed. The team should review whether unacceptable contact resistance, intermittent operation or an out-of-specification timing response can affect its equipment. The criteria must come from approved requirements and manufacturer information. Do not create universal resistance or timing limits from an illustrative worksheet.<\/p>\n<p>Interfaces often deserve their own rows. A connection problem, unsuitable mounting condition or control supply disturbance can produce a contactor-related symptom without originating inside the contactor. Keep design, assembly and service assumptions distinguishable. This helps the team assign an effective corrective action instead of replacing the component while leaving the initiating condition unchanged.<\/p>\n<figure><img decoding=\"async\" loading=\"lazy\" src=\"https:\/\/sayoon-dc.com\/wp-content\/uploads\/2026\/11\/dc-contactor-fmea-equipment-design-review-bodyTwo-20261109-daily.png\" alt=\"CZW200A Normally Open DC Contactor with detection and action review headings\"><figcaption>A proposed diagnostic needs configuration-specific evidence and a defined verification activity.<\/figcaption><\/figure>\n<h2>Treat detection as a claim that needs a test<\/h2>\n<p>For each proposed diagnostic, state the measured quantity, evaluation condition, decision rule and response. Explain what faults it can miss. A current measurement may be useful in one circuit state and inconclusive in another. A voltage reading may reflect a parallel circuit or stored charge. The study should connect the signal to the failure mode through the actual circuit analysis.<\/p>\n<p>If a diagnostic claim contributes to a safety assessment, obtain the appropriate component evidence and use the applicable assessment method. Do not invent diagnostic coverage from a successful demonstration on one sample. A qualitative FMEA can identify the need for detection, but quantitative reliability or safety calculations require adequate data and a suitable model.<\/p>\n<h2>Prioritise actions with the project&#8217;s method<\/h2>\n<p>Use the severity definitions, decision rules and approval responsibilities chosen for the equipment project. A numerical ranking system can help organise work, but an unexplained score should not replace an engineering judgement about consequences. Keep severe unresolved effects visible even when an occurrence estimate is uncertain. Do not insert optimistic failure probabilities simply to make a spreadsheet appear complete.<\/p>\n<p>Possible actions include clarifying requirements, changing the circuit, improving feedback, adding an approved protective response or validating a disputed assumption. Each action needs an owner, completion date and evidence reference. State the residual issue after the action. A completed task is not automatically an accepted risk, and an accepted risk is not evidence that the failure cannot occur.<\/p>\n<h2>Plan verification before closing the review<\/h2>\n<p>Choose verification activities that match the claim. Document inspection can confirm a configuration or interface requirement; a controlled test can demonstrate a defined response under stated conditions. Some effects may require circuit analysis or a wider equipment test. Hazardous fault simulation belongs in an approved test environment with qualified personnel, suitable protection and defined stop conditions.<\/p>\n<p>Write the expected result before testing, including the equipment state and observations required. Save the actual configuration, instruments, results and deviations. A pass obtained with a different coil option, control program or protective device may not cover the production assembly. Where the evidence does not match, reopen the affected row instead of copying the old pass into a new design revision.<\/p>\n<h2>Distinguish supplier input from equipment responsibility<\/h2>\n<p>The contactor supplier can provide product identification, ratings, installation instructions and available application evidence. The equipment team must explain the circuit, normal duty, abnormal conditions and intended function. Neither party can complete the review accurately if the other treats these inputs as assumed knowledge. Ask specific questions linked to unresolved worksheet rows.<\/p>\n<p>For a SAYOON enquiry, include the exact model and options, control supply, switched circuit conditions, mounting environment and the function that needs assessment. Request the relevant current documents and identify any unavailable data. A product image is useful for identification but cannot prove internal contact relationships, feedback integrity, failure-rate data or suitability for a safety-related function.<\/p>\n<h2>Maintain the worksheet through design changes<\/h2>\n<p>A new driver, alternative coil, revised suppression arrangement or firmware change can alter the assumptions behind a row. Link the FMEA to configuration control and change review. Check both the altered function and the interfaces it affects. A mechanically interchangeable contactor is not automatically an evidence-equivalent replacement for every previous analysis.<\/p>\n<p>Use field findings as inputs without turning the prospective analysis into a complaint log. When an actual fault reveals a missing cause or ineffective detection, update the relevant row and verify the response. Keep the investigation record separate so the team can distinguish observed evidence, hypothetical possibilities and approved design conclusions. That distinction makes future supplier and equipment reviews more useful.<\/p>\n<h2>Educational video<\/h2>\n<p>ASQ explains FMEA as a quality tool. This educational background does not assess a particular contactor or approve an equipment design.<\/p>\n<div style=\"aspect-ratio:16\/9\"><iframe src=\"https:\/\/www.youtube-nocookie.com\/embed\/yhB0LZMTDz4\" title=\"Quality Tool--FMEA \u2014 ASQ\" loading=\"lazy\" allowfullscreen style=\"border:0;width:100%;height:100%\"><\/iframe><\/div>\n<p><a rel=\"noopener nofollow\" href=\"https:\/\/www.youtube.com\/watch?v=yhB0LZMTDz4\" target=\"_blank\">Watch the educational video<\/a><\/p>\n<h2>Frequently asked questions<\/h2>\n<h3>Does a contactor FMEA prove that the equipment is safe?<\/h3>\n<p>No. It supports a structured design review. System hazards, interfaces, human actions, required protective measures and applicable safety verification still need their own assessment and evidence.<\/p>\n<h3>Should every row contain a numerical failure rate?<\/h3>\n<p>No. A qualitative study can identify effects and necessary actions without fabricated numbers. Quantitative calculations require suitable configuration-specific evidence, justified assumptions and an appropriate method.<\/p>\n<h3>Can an auxiliary contact always detect welded main contacts?<\/h3>\n<p>No. The relationship depends on the specified device construction and supporting evidence. Review the exact feedback arrangement and the circuit state rather than assuming a generic auxiliary signal proves main-contact opening.<\/p>\n<h3>Who should approve the completed worksheet?<\/h3>\n<p>The equipment project&#8217;s authorised reviewers should approve the scope, actions and residual issues. Supplier responses support that decision, but do not replace equipment-level responsibility or the required verification process.<\/p>\n<h2>Product and related guides<\/h2>\n<p>Discuss the application using the <a href=\"https:\/\/sayoon-dc.com\/product\/czw200a-normally-open-dc-contactor\/\">CZW200A Normally Open DC Contactor<\/a> and the <a href=\"https:\/\/sayoon-dc.com\/blog\/dc-contactor-selection-guide-key-factors-for-reliable-motor-control\/\">DC contactor selection guide<\/a>. Related reading: <a href=\"https:\/\/sayoon-dc.com\/blog\/ev-contactor-failure-modes\/\">EV Contactor Failure Modes: Evidence to Check Before Replacement<\/a>, <a href=\"https:\/\/sayoon-dc.com\/blog\/ev-contactor-weld-detection-methods\/\">EV Contactor Weld Detection Methods<\/a>.<\/p>\n<h2>Technical references<\/h2>\n<ul>\n<li><a rel=\"noopener nofollow\" href=\"https:\/\/www.ihi.org\/library\/tools\/failure-modes-and-effects-analysis-fmea-tool\" target=\"_blank\">IHI: FMEA tool and application scope<\/a><\/li>\n<li><a rel=\"noopener nofollow\" href=\"https:\/\/swehb.nasa.gov\/pages\/viewpage.action?navigatingVersions=true&#038;pageId=107053153\" target=\"_blank\">NASA: bottom-up failure effects analysis<\/a><\/li>\n<\/ul>\n<p>Apply each reference within its stated scope. General methods do not establish a product rating or project acceptance.<\/p>\n<p><script type=\"application\/ld+json\">{\"@context\": \"https:\/\/schema.org\", \"@type\": \"FAQPage\", \"mainEntity\": [{\"@type\": \"Question\", \"name\": \"Does a contactor FMEA prove that the equipment is safe?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. It supports a structured design review. System hazards, interfaces, human actions, required protective measures and applicable safety verification still need their own assessment and evidence.\"}}, {\"@type\": \"Question\", \"name\": \"Should every row contain a numerical failure rate?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. A qualitative study can identify effects and necessary actions without fabricated numbers. Quantitative calculations require suitable configuration-specific evidence, justified assumptions and an appropriate method.\"}}, {\"@type\": \"Question\", \"name\": \"Can an auxiliary contact always detect welded main contacts?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. The relationship depends on the specified device construction and supporting evidence. Review the exact feedback arrangement and the circuit state rather than assuming a generic auxiliary signal proves main-contact opening.\"}}, {\"@type\": \"Question\", \"name\": \"Who should approve the completed worksheet?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"The equipment project's authorised reviewers should approve the scope, actions and residual issues. Supplier responses support that decision, but do not replace equipment-level responsibility or the required verification process.\"}}]}<\/script><\/p>\n<style>.sy-pro-article-main{min-width:0;max-width:100%}.sy-pro-article-main>*{max-width:100%}.sy-table-wrap{max-width:100%;overflow-x:auto}.sy-table-wrap table{min-width:650px;width:100%;border-collapse:collapse}.sy-table-wrap td,.sy-table-wrap th{padding:12px;border:1px solid #d5dce4;text-align:left;vertical-align:top}figure{margin:24px 0}figure img{max-width:100%;height:auto}<\/style>\n","protected":false},"excerpt":{"rendered":"<p>Bouw een DC contactor FMEA-beoordeling rond functies, faal-effecten, detectie, acties en verificatie zonder het inventariseren van faalpercentages.<\/p>","protected":false},"author":4,"featured_media":4851,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_gspb_post_css":"","footnotes":""},"categories":[1],"tags":[61],"class_list":["post-4854","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","tag-dc-contactor-engineering"],"blocksy_meta":{"styles_descriptor":{"styles":{"desktop":"","tablet":"","mobile":""},"google_fonts":[],"version":7}},"_links":{"self":[{"href":"https:\/\/sayoon-dc.com\/nl\/wp-json\/wp\/v2\/posts\/4854","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sayoon-dc.com\/nl\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sayoon-dc.com\/nl\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sayoon-dc.com\/nl\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/sayoon-dc.com\/nl\/wp-json\/wp\/v2\/comments?post=4854"}],"version-history":[{"count":1,"href":"https:\/\/sayoon-dc.com\/nl\/wp-json\/wp\/v2\/posts\/4854\/revisions"}],"predecessor-version":[{"id":5257,"href":"https:\/\/sayoon-dc.com\/nl\/wp-json\/wp\/v2\/posts\/4854\/revisions\/5257"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/sayoon-dc.com\/nl\/wp-json\/wp\/v2\/media\/4851"}],"wp:attachment":[{"href":"https:\/\/sayoon-dc.com\/nl\/wp-json\/wp\/v2\/media?parent=4854"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sayoon-dc.com\/nl\/wp-json\/wp\/v2\/categories?post=4854"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sayoon-dc.com\/nl\/wp-json\/wp\/v2\/tags?post=4854"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}