RAMSynapse
Log inSign up

Derating Analysis · Chapter 6

Common Pitfalls

The mistakes seen in practice and the guards against them.

Derating produces a table of numbers that all look the same, which is why a bad derating analysis is so hard to spot in review. Every entry below yields a report that passes.

PitfallWhat it looks likeThe guard
Nominal stressesThe check run at typical line, typical load, room ambientWorst case on every axis: max line, max load, hottest qualified environment, end-of-life tolerance
Board ambient used as part temperatureEvery part on the card at 55 °C because the enclosure isA temperature per part, from a thermal model; θja and the local ambient, not the specification's
Ratios checked, temperature notEvery stress ratio green, no junction temperature anywhere in the reportBoth axes per part, both in the deliverable
No rule set named"Derated to 50 per cent" with no document behind itThe standard, its revision and the application class, recorded once in the policy
Two rule sets mixedA subsystem checked to one document, the rest to another, results mergedOne rule set per assembly, recorded; never merged into a single verdict
Rating taken at the wrong temperatureA 0.25 W resistor treated as 0.25 W at 100 °CThe rating curve, not the headline: above the knee the part's own rating is already falling
Contact ratings read across load types5 A resistive contacts carrying 3.2 A into a capacitive loadRatings are per load type; a motor, lamp or capacitive load has its own number
Tantalum treated as an ordinary capacitorA voltage ratio checked, the circuit-impedance condition ignoredRead the family rule, not just the ratio column
Transients folded into the steady-state checkInrush counted as normal current, or excluded and never analysed anywhereSteady state here, transients in their own analysis, both referenced from the report
The derating report and the prediction disagreeOne at worst case, the other at nominal, nobody comparingOne operating point per part, feeding both
Violations sized rather than typed"Only 4 per cent over" treated as nearly compliantThe stress factor is nonlinear; classify by axis and fix, not by margin
Waivers without mechanismsA disposition reading accepted, engineering judgementThe mechanism, the evidence and the named authority, and the mode raised in the FMECA
Coverage never checkedA parts list of 400 and a derating table of 340Reconcile against the BOM; the missing parts are usually the late additions
Frozen at first issueThe report dated at PDR, the thermal design changed twice sinceRe-run on every change to dissipation, ambient, duty cycle or thermal interface

Two of these deserve a closing sentence each. Using the board ambient as the part temperature is the one that produces the most confident wrong answer, because it makes the second axis disappear: every part comes out at the same temperature, every temperature check passes, and the analysis silently becomes a stress-ratio spreadsheet. The worked example's regulator is the illustration, and it is not an exotic case: a linear regulator dropping a couple of watts in a small package is on most boards ever built.

And the frozen report is the most common. Derating is the analysis whose inputs move most and whose document is revised least, because nothing about a parts list looks out of date. The trigger for a re-run is not a design review; it is any change that moves a dissipation, an ambient, a duty cycle or a thermal path, and most programmes have several of those between issues of the report.


Want to see this on a live system model? Request a walkthrough.