Pipe Stress FEA Online — Nozzle & Shell Junction Checks

PiperFEA runs screening-grade pipe stress FEA online: finite element checks of nozzle-to-shell junctions on cylindrical shells, flat heads, and elliptical heads, under pressure plus external piping loads. Each governing check comes back as computed vs allowable with a ratio, in report-grade output. It is in commissioning, with validation status published — and a full B31.3 flexibility analysis still belongs in dedicated pipe stress software.

Content last reviewed 2026-08-29 · page regenerated 2026-09-13 at build.

What it analyzes

PiperFEA is a finite element check for a nozzle intersecting a parent shell — the local stress problem where piping loads land on equipment. Three model types are supported: a nozzle on a cylindrical shell, on a flat head, or on an elliptical head. You define the junction, apply pressure and piping loads, and get categorized stresses against allowables. One status note before the details: PiperFEA is in commissioning — validation status is published as its gates close, coverage differs by model type, and every run surfaces its advisories.

Inputs — the live form, exactly

Outputs

• Four categorized checks, labeled the way the report reads: Pl vs 1.5(k)Smh, Qb vs 3(Smh), Pl+Pb+Q vs 3(Smavg), and Pl+Pb+Q+F vs Sa — each as computed psi, allowable psi, and the ratio.
• Fatigue detail — S-N curve classification, the governing fatigue allowable, Ke factor, stress range, cycles allowed, both B31 and Markl allowables, and the E ratio.
• Mesh and engine data — node and element counts, junction and global element sizes (in), and the mesher/solver versions used, stamped on every analysis.
• Report — a single HTML file with the model image inlined, in a long-established nozzle-FEA report layout, so it can be compared line by line against prior analyses.

How a run executes

You build the model in the browser; meshing (gmsh) and solving (CalculiX / CCX) run on a managed solver worker. A job moves through queued → running → done (or error), polled every 2 seconds with a 600-second cap, and each run carries its advisories and submitted/started/finished timestamps. Two honest notes: unlike the free calculators, an FEA run does transmit your model inputs to the solver; and job records live in worker memory, so a worker restart drops the record and the run is simply resubmitted.

Who it is for

PiperFEA is aimed at engineers who need a documented junction check without standing up a dedicated nozzle-FEA seat:

• Piping stress engineers screening equipment nozzle loads before deciding whether a full local-stress analysis is warranted.
• Static equipment engineers checking whether the loads on a stress isometric or nozzle load summary pass at a vessel nozzle, with or without a reinforcement pad.
• EPC and owner's engineers who want an independent check with a report they can file alongside the vendor calculation.
• Anyone whose FEA seat lives on another desk. This runs from a browser tab — no install, no license server, no waiting for the one workstation that has the software.

If you only need to compare nozzle loads against published allowable tables (API 610, 560, 660/661, 650, 620, NEMA SM-23), the table-based equipment nozzle load check does that on the Pro Plus tier without running FEA.

Screening-grade, defined — and when to escalate

Screening-grade means: one nozzle-to-parent junction, one geometry, pressure plus a set of external forces and moments, solved and categorized with ratios against allowables you control. It exists to answer "do these loads plausibly pass at this nozzle, and by what margin" fast enough to use during layout and squad check — with a report attached.

Just as plainly, here is what it is not:

• Not a system flexibility analysis. There is no pipe routing, no supports, no system thermal expansion, no displacement or code stress along the line. A full B31.3 flexibility analysis still belongs in dedicated pipe stress software such as CAESAR II or AutoPIPE — PiperFEA checks the junction those analyses load; it does not replace them.
• Not a vessel code calculation of record. It reports categorized stresses against allowables you supply; it does not produce code-stamp documentation.
• Three model types, no more. Nozzle configurations outside a cylindrical shell, flat head, or elliptical head are out of scope.
• Bounded geometry. The solver enforces validated geometry ranges (small-opening limits on flat heads among them) and returns advisories when a case sits outside them. Treat an advisory as a stop sign, not fine print.

Escalate to a full analysis when a governing ratio sits close to 1.0 and the decision matters, when the geometry falls outside the supported model types or triggers an advisory, when fatigue governs in heavily cyclic service, or when the deliverable itself must be a system flexibility analysis — and while commissioning is underway, treat marginal results as escalation candidates by default. For the code-equation side of flexibility, the free B31.3 displacement stress range calculator is the companion check. Either way: the tool computes, and a qualified engineer dispositions.

Validation: golden fixtures, published status

Every solver change re-runs against a set of golden-fixture regression cases — fixed inputs with pinned expected outputs, benchmarked against commercial FEA reference cases. If a change moves a number, the fixture fails and the change does not ship. It is the same fixture-verified discipline behind the free calculators, applied to an FEA pipeline.

• Traceable runs. Each analysis records its mesh statistics (nodes, elements, junction and global element size) and the gmsh and CCX versions that produced it — you can see what was actually solved.
• Comparable reports. The report keeps a long-established nozzle-FEA layout deliberately, so results can sit next to prior third-party analyses during review.
• Advisories, not silence. Solver warnings and per-run advisories are surfaced on the result, not swallowed.

Status: commissioning. PiperFEA is sold as commissioning-stage on the pricing page, with validation status published as it progresses — coverage is not yet uniform across the three model types, which is exactly why the status is published rather than implied. And to be precise about what the fixtures prove: they verify the implementation against a documented method and reference cases. That is a statement about the software — not a warranty that a given design is fit for service. That judgment stays with the responsible engineer.

Pricing: what tier it runs on

PiperFEA runs on Ultimate — each analysis executes on a managed solver worker, which is what the tier pays for. Everything below it stays as-is: the code calculators are free forever, need no account, and run entirely in your browser with inputs never transmitted. The FEA tool is the one exception to that browser-only rule — model inputs go to the solver worker, as noted above.

Annual Ultimate works out to 17% under monthly. Full feature matrix and the pricing FAQ are at /pricing/.

Watch a check run end to end

▶ Nozzle-to-Shell FEA Check in the Browser - PiperFEA Screening-Grade Pipe Stress FEA (1:41) — A junction check end to end on the managed solver: pressure plus external piping loads in, primary, secondary, and fatigue stresses back as computed vs allowable with a ratio, in report-grade output. Watch on YouTube.

Run your first check

A sensible order: start with the free calculators — no account, nothing to cancel — and see whether the per-card verdicts and fixture-verified worked examples fit how you check work. When a nozzle junction needs more than a table lookup, Ultimate turns on PiperFEA: categorized FEA stresses with ratios and a report you can file, from the same browser tab.

And the limitation once more, because it belongs on the page rather than in fine print: this is a commissioning-stage screening and checking aid for a single nozzle/shell junction. It sharpens the question you take into a full flexibility analysis — it does not answer it for you.

FAQ

How accurate are the results?

The honest answer has three layers, and the report exposes all of them. The engines are established open-source solvers — meshing by gmsh, solving by CalculiX (CCX) — and every analysis stamps its mesh statistics (node and element counts, junction and global element sizes) and engine versions on the output, so 'what was solved' is never a mystery. The implementation is regression-tested against golden fixtures benchmarked against commercial FEA reference cases, and the tool is sold as commissioning-stage with validation status published as its gates close — you can see which model types have closed their gates rather than being asked to assume all of them have. And the boundary of the claim: all of that verifies the software against a documented method. It is not a warranty of design fitness, because model idealization — is this nozzle really radial, is the pad really fully fused — is engineering judgment the solver cannot supply. A qualified engineer reviews and dispositions the results, as with any analysis tool.

What codes does it cover?

Results are categorized the way a pressure-vessel local-stress report reads: four checks — Pl vs 1.5(k)Smh, Qb vs 3(Smh), Pl+Pb+Q vs 3(Smavg), and Pl+Pb+Q+F vs Sa — each reported as computed psi, allowable psi, and the ratio, so the governing category is visible at a glance rather than buried in a contour plot. The cold and hot allowable stresses are your inputs, taken from your governing code edition: the tool does not select allowables for you and does not reproduce code stress tables, which is the same data-firewall rule every calculator on this site follows, and it is what keeps the run anchored to the code of record your project actually invokes rather than to whichever edition a developer happened to embed. Fatigue output goes deeper than a single verdict — S-N curve classification, the governing fatigue allowable, Ke factor, stress range, cycles allowed, and both the B31 and Markl allowables — so a reviewer can see which fatigue basis governed and by how much.

What inputs do I need before I can run a check?

What the form asks for, in US customary units: geometry — parent OD and thickness, nozzle OD, thickness and length, and optional reinforcement pad width and thickness, with zero meaning no pad; material — one of four material groups (low carbon steel, low alloy, austenitic, Ni-Cr-Mo-Fe), elastic modulus, cold allowable Sc, hot allowable Sh, and a stress concentration factor; and loads — internal pressure, external piping loads as Fx/Fy/Fz forces in pounds and Mx/My/Mz moments in inch-pounds, design temperature, and design cycles N. In practice that is one vessel drawing plus one nozzle load summary from the stress analysis. Two unit traps worth naming because they account for most bad first runs: the moments are inch-pounds, not foot-pounds — a flexibility program that reports ft-lb needs its output multiplied by 12 before entry — and the allowables are the code-table values for your material at your temperatures, entered by you, not looked up by the tool.

What tier do I need — is there a free version?

PiperFEA requires Ultimate ($14.99/month or $149/year), and the reason is architectural rather than arbitrary: unlike every other calculation on this site, an FEA run cannot execute in your browser — meshing and solving happen on a managed solver worker, which is real compute with real cost per run. That is also why this is the one tool where your model inputs do transmit off your device, a fact the page states plainly because the free calculators' promise that inputs never leave the tab is load-bearing everywhere else. There are no free FEA runs, and the feature is labeled commissioning on the pricing page while validation status is published — you are told what you are buying into. Everything on the free tier stays genuinely free with no account: all the ASME code calculators, including the nozzle-load unity check that tells you whether the loads you are about to analyze here even exceed the equipment allowables in the first place. Details at /pricing/.

Does this replace CAESAR II or AutoPIPE?

No, and the division of labor is worth stating precisely because the tools answer different questions about the same joint. CAESAR II and AutoPIPE are system flexibility tools: they model the routing, supports and thermal displacements, and they deliver code stresses along the line plus a set of forces and moments at every equipment nozzle. PiperFEA picks up exactly where that output ends — it takes the nozzle loads a system analysis or a vendor hands you and resolves what those loads do locally at one nozzle-to-shell junction, which a beam-element flexibility model structurally cannot see. The two legitimate uses that follow: screening nozzle loads early, before a vendor WRC or FEA calculation exists, so a doomed nozzle gets caught while the layout can still change; and independently checking a local analysis someone else produced, since an independent model disagreeing is the cheapest audit there is. The full B31.3 flexibility analysis, with B31J factors applied, remains the governing system calculation — run it where it belongs.