Choosing the Wrong Approach Can Be Costly – Here’s How to Tell Them Apart
When a pressure vessel fails, the question investigators ask first isn’t what broke — it’s how it was designed. Design by Rule offers speed and simplicity, and for straightforward, well-understood applications it delivers exactly what’s needed. But when operating conditions are complex, cyclic, or push against code boundaries, defaulting to DBR can quietly introduce risk that no formula or table was built to catch. Design by Analysis exists precisely for those situations — and knowing when to make that call is often the difference between a vessel that performs for decades and one that becomes a forensic case study. O’Donnell Consulting has been performing ASME-compliant Design by Analysis for over 30 years. If you’re not certain which approach your application demands, that uncertainty is worth a conversation.
Design By Rule
Design by Rule is a codified, empirical approach to engineering design — one built on decades of testing, historical performance data, and expert consensus embedded into standards like ASME, AISC, and API. Rather than modeling how a specific component behaves under its specific conditions, DBR applies predetermined formulas, tables, and specification limits to arrive at a compliant design.
For well-understood, repetitive applications, this is entirely appropriate. DBR is fast, cost-effective, and produces designs that meet established safety thresholds without requiring specialized analytical software or extended engineering hours.
Where DBR works well:
- Standard pressure vessel configurations with predictable geometry and loading
- Applications where industry precedent is deep and failure modes are well-characterized
- Projects with tight budgets or schedules where a conservative, compliant design is sufficient
- Regulatory environments where code compliance itself satisfies the safety demonstration requirement
Where DBR shows its limits:
- Complex or non-standard geometries that fall outside the assumptions embedded in code formulas
- Components subject to cyclic loading, thermal gradients, or dynamic forces that simple stress calculations don’t fully capture
- Situations where material behavior is non-linear or where operating conditions approach code boundaries
- High-consequence applications where “code compliant” and “adequately safe” are not the same thing
- Cases involving nozzles, intersections, or discontinuities where localized stress concentrations drive failure but are averaged out in rule-based calculations
The core limitation of DBR is not that it’s wrong — it’s that it’s conservative in ways that can work against you in both directions. Overdesign adds unnecessary material cost and weight. Under-characterization of actual stress states can leave real risk undetected. When your application is anything but standard, those tradeoffs deserve a closer look.
Design by Analysis
Design by Analysis is the methodology ASME requires when standard formulas can no longer reliably characterize what a component is actually experiencing. Where Design by Rule asks whether a vessel meets the code’s prescribed dimensions and stress limits, DBA asks a more fundamental question: under the specific geometry, loading, and operating conditions of this component, what will actually happen — and can we demonstrate that it won’t fail?
The answer is a comprehensive and rigorous process that involves Finite Element Analysis — which models the component in detail and solves for stress, strain, and deformation across the entire structure under every relevant load condition. This includes pressure, thermal gradients, dead weight, seismic loads, nozzle forces, startup and shutdown cycles, and any combination thereof. Where a handbook formula produces a single stress number for a simplified geometry, FEA produces a complete picture of how stress distributes through a real component — including the concentrations at nozzles, fillets, welds, and support attachments that rule-based methods average out or ignore entirely.
Design by Analysis, as described in ASME Section VIII, Division 2, Part 5, designates the methods for determining the adequacy of a pressure vessel component’s design. The entire approach is built around Protection Against Failure Modes — engineers must demonstrate protection against each of the following, not just meet a single stress allowable:
- Protection Against Plastic Collapse
- Protection Against Local Failure
- Protection Against Failure From Buckling
- Protection Against Failure From Cyclic Loading
These four failure modes define what a DBA evaluation has to demonstrate. That’s a meaningfully different scope than Design by Rule, which doesn’t distinguish between failure modes — it applies a single conservative margin and assumes that’s sufficient across the board.
The tradeoff is effort. A DBA evaluation means building and validating a finite element model, running mesh convergence studies, classifying stresses at every location of interest, and documenting the basis for each load combination considered. Where DBR is a lookup, DBA is an investigation — and the result depends on the analyst’s judgment as much as the software. A poorly built model, an unconverged mesh, or a missed load case can produce results that look precise but aren’t reliable. That’s the case for having engineers who’ve spent years validating FEA models against known solutions and forensic case history run this kind of analysis, not just running the software and taking the output at face value.
