Choosing the Wrong Approach can be Costly – Here’s How to Tell them Apart
Pressure vessels can be designed two ways under the ASME Code: Design by Rule (DBR) or Design by Analysis (DBA). For standard configurations under well-understood loading, DBR is fast and cost-effective, and it produces an adequate design. When a component has non-standard geometry, cyclic or thermal loading, or operating conditions near the limits the rules were written for, DBR formulas may not capture the stresses that govern failure. DBA was developed for those cases. It evaluates the actual component under its actual loads and requires each failure mode to be addressed explicitly. Choosing between the two methods early affects cost, schedule, and long-term reliability. O’Donnell Consulting Engineers has performed ASME Design by Analysis since 1972. If you’re unsure which method your application requires, give us a call to discuss it.
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 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
- Cases involving nozzles, intersections, or discontinuities where localized stress concentrations drive failure
Design by Rule is conservative overall, but not uniformly. It can add unnecessary material where stresses are low while leaving high local stresses at discontinuities unevaluated. For non-standard applications, both effects warrant 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 (paragraph 5.2): Ensures the component can carry its applied loads without gross plastic deformation.
- Protection Against Local Failure (paragraph 5.3): Limits strain at highly constrained locations, where material can tear or rupture before general yielding occurs.
- Protection Against Collapse From Buckling (paragraph 5.4): Evaluates stability under compressive loads, such as external pressure or axial compression.
- Protection Against Failure From Cyclic Loading (paragraph 5.5): Evaluates fatigue and ratcheting under fluctuating pressure, thermal, and mechanical loads, using screening criteria or a detailed fatigue analysis.
- Protection Against Creep Damage (paragraph 5.6, added in the 2025 Edition): Applies at temperatures where time-dependent behavior governs. Covers stress rupture, creep buckling, and creep ratcheting, with screening criteria for creep-fatigue.
These five failure modes define what a DBA evaluation has to demonstrate. Design by Rule addresses them implicitly, through margins built into its formulas. Design by Analysis requires each one to be demonstrated explicitly for the actual component.
Â
The tradeoff is effort. A DBA evaluation means building and validating a finite element model, running mesh convergence studies, documenting the basis for each load combination considered, and, when using the elastic method, classifying stresses as primary, secondary, or peak at each location of interest. Where DBR is a lookup, DBA is an investigation, and the result depends on the analyst’s judgment as much as on the software.
