SWBPIPEDevelopment Atlas

Development Atlas.

Reviewed 22 October 2026 · Model format 0.6.0

Code snapshot 7a780551f0 ↗
Main desktop workflow
Model authoringAvailable in workbench

Build a piping model from structured geometry and engineering inputs.

What exists today

Geometry tools create and edit model format 0.6.0. Proposed edits are shown for review, with undo/redo and an operation log within the current session.

Still missing or limited

Older model formats are refused and require re-authoring. A drawn fitting supplies mechanics only when its solver representation is supported.

Modelling guide Model format
Pipe & bend mechanicsAvailable in workbench

Solve the piping centerline as an assembled 3D structural model.

What exists today

Straight pipes and realized curved bends reach the solver. Pressure-capable straight pipes default to shear-flexible Timoshenko elements; bends use an entered flexibility factor.

Still missing or limited

Bends still use Euler–Bernoulli mechanics. General rigid fitting elements and flexible branch connections remain unavailable.

Beam model Shear model
Numerical checksPartial support

Identify numerical trouble in a solved case.

What exists today

The solver checks residuals, conditioning and member recovery. Captured-source recovery supports a bounded straight-pipe subset, including shear-flexible pipes and section allowances.

Still missing or limited

A clearer per-case numerical-health display is in development. It presents existing diagnostics; it does not guarantee error bounds or validate the engineering model.

Recovery scope Health display—in development
Results & reviewAvailable in workbench

Inspect calculated motion, member actions, stresses and support reactions.

What exists today

Tables identify units, frames and section bases; the viewport shows deformed shape and rotations. Supported bend results include directional SIF measures and bounded stress maxima.

Still missing or limited

Stress-colour overlays and reaction arrows are not implemented. Principal and equivalent stresses and code stress ranges remain outside the current result set.

Result quantities Coverage limits
Result exportsAvailable in workbench

Export admitted result rows with their units, meaning and evidence.

What exists today

Result JSON and stress-neutral CSV/JSON work for eligible current pressure-free and pressure-capable results.

Still missing or limited

Export depends on the result reader and numerical standing; stale or unbound results can be refused. Result-row export does not provide a complete receiving-program model.

Result export limits Output policy
Supporting features
Materials & private dataPartial support

Supply the material, section and project data used in a calculation.

What exists today

Material and section values can be entered or imported with units and source records. The pressure-capable route distinguishes nominal wall, reduced wall and pressure bore.

Still missing or limited

Importing a library does not apply engineering values automatically. Code-specific data and project criteria still come from the user.

Sections & allowances Libraries
Supports & load casesPartial support

Describe how the line is restrained and loaded.

What exists today

Linear supports, selected nonlinear support laws, prescribed rigid movements and thermal/fit reference states have supported calculation paths.

Still missing or limited

Hanger preload and complete installation/contact history are missing. Nonlinear iteration is limited to four passes; the pressure-capable route refuses nonlinear supports.

Support limits Reference states
Projects & comparisonPartial support

Save work locally and examine changes between results.

What exists today

Projects save and reopen locally. The comparison workspace matches a load case to combination rows within one run, using explicit result references.

Still missing or limited

Comparison between saved runs or model states and tolerance classification remain unfinished. Subtracting solved states is not a new equilibrium solve.

Save and reopen Comparison source
Pressure & expansion jointsPartial support

Represent pressure and how its loads transfer through the line.

What exists today

Explicit pressure regions and terminal load paths are implemented. Supported expansion joints can now include elastic tie rods, with their loads reported separately.

Still missing or limited

Joint geometry and rod laws remain restricted; tension-only rods, gaps and stops are unsupported. Hydrostatic head and pressure-dependent bend flexibility remain outside the model.

Pressure scope Expansion joints
User rule checksPartial support

Check admitted results against rules and engineering criteria you supply.

What exists today

The rule framework evaluates supported quantities and user formulas. Eligible pressure-capable desktop results can now be rule-checked.

Still missing or limited

There is no built-in code-stress calculation or standards table. The result reader must admit the selected result; an available rule framework does not make every case eligible.

Code and rule scope Output policy
Design research agentNot integrated yet

Use engineering references to prepare model changes for review.

What exists today

The piping reference Reader is published. Local proposal previews and proposals imported from elsewhere can be reviewed separately.

Still missing or limited

Live research through the Reader and preparation of the user’s own source documents are not integrated with the product.

Agent and Reader Published Reader
Solve control & memoryAvailable in workbench

Run, monitor and cancel calculations with explicit memory budgets.

What exists today

Native solves run in bounded worker processes with progress, cancellation, a shared memory pool and per-solve budgets. The memory panel explains resource refusals.

Still missing or limited

The controls cover solve workers and retained result memory, not every part of the application. A larger budget does not expand the numerical method’s supported scope.

Memory limits Running a solve
Reports & model handoffPartial support

Produce calculation documents and transfer model information to other tools.

What exists today

Pressure-free results can produce HTML reports and limited model exports, with provenance and loss reports.

Still missing or limited

Pressure-capable reports remain blocked, and report packages refuse all current result formats. PCF and MBF handoffs are limited subsets; complete model transfer remains unfinished.

Handoff scope Report limits
Main line: the pressure-capable desktop workflow. Branches: related features. Result exports are connected; reports and model handoff retain route-specific limits.
Engineering work remainingReports, numerical-health feedback and other open work

02 / Remaining scope

Work remaining.

Open engineering work

A

Report coverage

Reports from current results

Connect current result formats to report packages and extend reports to pressure-capable results.

Output boundaries
B

Numerical diagnostics

Clear numerical-health feedback

Show the existing per-case numerical verdicts and conditioning diagnostics clearly, with guidance when they indicate trouble.

Design in development
C

Whole-product evidence

Complete workflows & validation

Reconcile the implemented workflows with their intended outcomes, exercise them in the app, and establish broader engineering validation.

Verification and validation scope

A standalone verified-bounds feature is excluded from v0.1; numerical-health feedback uses the existing diagnostics. The open items have no assigned delivery dates or order.

Other open work

Live research

Connect the Reader and prepared user documents to research and model proposals.

Agent scope ↗

Saved-state comparison

Compare saved model states and separate runs, with explicit mappings and tolerance profiles.

Comparison limits ↗

Model transfer & broader tests

Check representative piping systems and preserve their meaning in receiving programs.

Verification plan ↗

Further limits

Hanger preload & sizing ↗Branches & nozzles ↗Code stresses ↗Hydrotest states ↗

Evidence & product scope

Detailed limits ↗Recorded cases ↗Product scope ↗

Describes the dated code snapshot above.