What Elementarium does today.

Draw over the architect’s DXF

Import a DXF and it becomes a reference drawing under the model, in its own units, placed where you put it. Snap to its lines, arcs and endpoints as you lay members out, and the frame lands on the grid the architect already drew.

Surfaces drawn as surfaces

Outline the slab, the wall or the core, punch the openings, set the thickness. It meshes into four-node shells and solves with the frame around it. One model — not a slab model and a frame model that disagree.

Start from a generated structure

Thirty-five parametric structures — parallel-chord and roof trusses, portal and multi-storey frames, arches, grillages, towers, domes, a pipe rack, a silo, a cooling tower, a culvert — each drawn with its dimension lines while you set them. It lands in a new project or beside the model you have, with members, plates, supports and loads in the case you pick, and joins any node it touches.

Sections & materials

Assign a section and a material once and reuse them everywhere. Change the definition and every member carrying it updates, with nothing to rebuild.

Supports & releases

Every direction is free, rigid or a spring with a stiffness you choose, in global axes or in a skew frame of your own. Release individual degrees of freedom at a member end — fully, or partially with a rotational stiffness.

Rigid arms & eccentricities

Constrain degrees of freedom instead of faking stiffness with a very stiff member. Rigid arms tie an offset node to its master; a beam can also carry its own eccentricity, so a downstand sits where it really is.

IFC and SAF in and out

The IFC structural analysis view (IFC2X3, IFC4, IFC4X3) and SAF 2.2 workbooks import on every plan and export on Pro: a model arrives from a BIM tool, SCIA or RFEM and goes back with its GlobalIds intact.

Line supports on a Winkler bed

Support a whole member or one edge of a slab with a stiffness per unit length: grade beams, strip footings, a wall under a slab. The subgrade modulus is your input, lumped onto the mesh by tributary length, and the total survives any remesh. A bed under the face of a raft is still to come.

One element for every surface

The element carries membrane and bending action together, so a floor slab, a shear wall and a tank wall are the same element under different loading. Nothing to choose between, and no incompatibility where a wall meets a slab.

Beam-to-wall joints carry moment

The element has a drilling degree of freedom, giving it all six at every node. A membrane element without one cannot resist the in-plane moment a beam brings, so the joint acts as a pin whether you wanted it to or not. Here the moment transfers unless you release it yourself. The drilling stiffness is tied to the membrane's own rotation (Hughes–Brezzi), not a spring to the ground, so it never resists a rigid rotation, never depends on the units, and never stiffens a curved shell where its facets meet at an angle.

It does not lock

Transverse shear strains are interpolated tensorially from the element edges rather than differentiated out of the displacement field, so a 200 mm slab and a 1.2 m raft use the same formulation. In plane, four enhanced strain modes absorb the parasitic shear that stiffens a plain four-node membrane: a cantilever wall one element deep reaches 99 % of its tip deflection, where the plain membrane reaches 68 %. No thin-versus-thick choice to get wrong, no stabilisation factor to tune, and walls and deep beams need no special mesh.

Beams do not need meshing

Bending uses cubic Hermitian interpolation, which gives exact nodal displacements for a prismatic member, and the forces between the nodes follow from the member load by statics. Subdividing a beam changes where results are reported, not what they are.

Distortion costs accuracy, not sense

The element passes the patch test in membrane and in bending and has no spurious zero-energy modes, and a warped element on a curved or twisted surface is corrected so that a rigid motion strains nothing. Skewed elements around an opening or a re-entrant corner lose accuracy gradually rather than producing nonsense. They do lose it: a strongly tapered element is stiff in in-plane bending, as every four-node membrane is, which is why the mesher keeps elements square and the convergence test is the one a reviewer accepts.

You choose how corners are recovered

Resultants are evaluated at the integration points and carried to the corners by superconvergent patch recovery (the default), Zienkiewicz–Zhu L² projection, a plain nodal average, an area-weighted average — or not at all. Turn smoothing off and the jump between adjacent elements is visible, which is the cheapest mesh-adequacy check there is.

Quadrilaterals, every time

Every surface meshes into four-node quadrilaterals, including around opening corners, at re-entrant notches and along skewed edges, where a fallback element would do the most damage.

Global size, local override

One target element size for surfaces and one subdivision count for members, then an override on the individual slab or member that earns it, and a cap on analysis element length across the whole model.

Graded transitions

The size field grows with distance from whatever asked for refinement — a gradient, not a step — and the refined zone is not ringed by the worst elements in the model.

One mesh, not two

Two slabs sharing an edge share its node chain, because the curve is discretised exactly once. A rib on a slab, or a beam along its edge, is embedded in that same mesh — which is what actually attaches it, rather than a coincident row of nodes that only looks connected.

Convergence evidence

Re-mesh finer and compare. The change in the quantity you care about is the only convergence argument a reviewer accepts.

Meshes on your machine

The mesher is compiled alongside the solver and runs in its own worker. Redrawing an opening and remeshing takes a fraction of a second.

Beams are meshed too, for a different reason. A prismatic beam element gives exact nodal values for the beam equation, so in linear static analysis subdivision only moves where results are reported. Stability and modal analysis are where it counts: a member left as one element buckles some 22% high. So beam subdivision gets its own global target, a per-member override, and a minimum that modal analysis enforces on top of both.

Cases, groups and relationships

Group cases by action type and declare which ones can act together. The generator uses the groups you define and never guesses them.

Generated to the code

EN 1990 — 6.10 or the 6.10a / 6.10b pair, plus characteristic, frequent and quasi-permanent for serviceability — or ASCE 7-22, LRFD §2.3 and ASD §2.4. Every variable action takes its turn as the leading one, the EN 1990 and LRFD factors are editable fields rather than constants compiled into the solver, and the report prints the same table you saw on screen.

Wind and snow from the geometry

Draw the walls and roof, enter the site, and the generators zone every face, read c_pe or μ at its pitch, and write each direction and arrangement as a case in an exclusive group. Flat, mono- and duopitch, hipped and multi-span roofs; the report traces each pressure to its clause. Czech national annex zones built in.

Loads in the member's own axes

Line, surface and edge loads take a Global / Local switch: along the member, across either section axis, or normal to a plate. The load editor draws each one on the real geometry, with the supports and dimensions, and local axes travel through to the solver, the tables, the report, IFC and SAF.

Envelopes over a set

Maximum and minimum of any quantity across all ULS or all SLS combinations, each carrying the combination that produced it.

Favourable permanent actions too

The generator also emits every combination with the permanent actions taken as favourable — the set that decides uplift, and the one most often left out when combinations are written by hand.

The maximum and minimum at a position come from different combinations, so interaction checks are evaluated combination by combination, never off the envelope. That's why the governing combination reported for a check may not be the one that produced the peak moment.

Diagrams on members

N, V, T and M drawn on the structure, at a scale you set, with the peak and its position labelled.

Contours on surfaces

m_x, m_y, m_xy and the principal moments; v_x and v_y; n_x, n_y, n_xy and the principal membrane forces; stresses, strains and deflection — smoothed or raw. The gap between the two is a mesh diagnostic in its own right.

Result tables

Nodal values, element values and reactions, filtered, sorted and exported to a spreadsheet.

Checked before it solves

A model with a mechanism has a singular stiffness matrix. Elementarium catches it before the solver does, names the cause — a hinge, a free node, a loose part — animates the motion, and offers the fix as one click.

Two answers, side by side

Each analysis is a named setup with its own results. Solve the same model with CG at 1e-6 and with a direct factorisation, pin one to each viewport, and compare.

Animated, and on video

Play the deformed shape, a mode or a buckling shape in every open viewer at once, and record a 3D viewer as a looping video with its title block and colour scale.

More than one viewer at a time

Every viewport is independent: its own quantity, its own combination, its own view angle. Put m_x next to u_z next to the mode shape and read them together instead of cycling through one pane.

Drag a tab, split a pane

Drop a panel against the top, bottom, left or right edge of any pane and the space splits to take it. Drop it onto the middle of a pane and the two stack as tabs instead.

Layout saved with the project

The arrangement is saved with the project. Open it again and the panels are where you left them.

Sensible on a small screen

On a phone the same panels become tabs, the Properties panel opens as a sheet with thumb-sized rows, and the ribbon, status bar and solve monitor step aside while you type.

1. 01

   Project

   Identification, client, author and design basis; a model summary with counts, model type and solver settings; and a legend saying which unit every quantity is in.

2. 02

   Structural model

   A vector drawing of the structure with its supports, then node coordinates, the member schedule, supports, materials, cross-sections and groups.

3. 03

   Loads

   Load cases with their action category, the combination table with its partial factors, every applied load with target and magnitude, and a figure per case.

4. 04

   Analysis results

   Solver, DOF count and solve time; reactions, nodal displacements and min/max internal forces; deformed shapes and diagrams as figures.

5. 05

   Design verification

   Worst utilisation per member with its governing clause, the per-clause breakdown, the fully substituted hand calculations, and the assumptions and limitations — which are never silently omitted.

Presets

Summary · Full calculation · Design only · Custom

Detail

All rows, governing only, or failing only

Derivations

None, governing, or every one

Paper

A4 or Letter, portrait or landscape, your margin

Output

Paginated on screen, then printed to PDF

What you're doing	Desktop	Laptop	Tablet	Phone
Building and editing a large model			workable	—
Solving static, modal, stability and second-order
Reading results, diagrams and contours
Design checks and their clause traces
Generating and sharing the PDF report

One URL, one account

There is no per-device install and no seat to release. Sign in and your projects are there, on hardware you have never opened Elementarium on before.

Input the device has

Keyboard and shortcuts at a desk; pinch, drag and two-finger orbit on a touch screen; pen where the device has one. The same model, driven the way that device works.

Pin it like an app

Add it to the dock, the taskbar or a phone home screen and it opens full-screen without browser chrome. Still no installer, still updates itself.

Offline on any of them

Once a project is on the device it stays workable with no signal. Model, solve, check and report, then merge when you are back in range.

Same model, same moment

No check-outs and no master file. Two engineers in one structure see each other’s edits as they happen, and each solves on their own machine.

Synced as you work

The model is a CRDT: edits sync as operations, not whole-file saves, so there is no save button and nothing to transfer. Close the laptop, open the tablet, and the model is where you left it. Two people editing different parts both land; the same property resolves the same way on every device, whatever order the updates arrive in.

Version history

Checkpoints are taken as you work and named versions are kept for good. Preview any of them read-only, then restore it for everyone, or as a new project beside the original.

Comments on the model

Pin a thread to a node, a member or a point on a plate, @mention a colleague or a load case, and mark a point blocking so the report export warns until it is resolved.

Core

C++ → WebAssembly

the same library, compiled for the tab

Parallelism

Up to 8 threads

half the logical processors by default, where the page is cross-origin isolated

Linear solvers

CG, LLᵀ, LDLᵀ

Jacobi (default), incomplete Cholesky or multigrid

Mesher

In-house, all-quad

compiled alongside the solver

Where it runs

Your device

no upload, no queue, no per-solve fee

Model data

Local-first

cached on the device, synced when online

No upload, no queue

The model never leaves the device to be solved, so there is no transfer to wait for and no job in front of yours. Your client's model stays on your machine while it solves.

You can watch it

A solve that takes more than a moment opens a monitor beside the model: the load case, the iteration, a convergence chart per case and a Stop button. Its Stats tab recomputes the residual from the answer and estimates the conditioning, so a fast answer is also a checked one.

It scales to the machine

One WebAssembly build runs on x86 and ARM alike. Where the browser grants cross-origin isolation, every step of each iteration runs on up to eight threads — half the logical processors unless you set otherwise; where it does not, the same solver falls back to one thread rather than failing.

Nothing to meter

There is no compute to bill for, so a 200,000-DoF model costs exactly what a portal frame costs.

• Chrome, Edge, Firefox & Safari
• Windows, macOS and Linux alike
• iPadOS, Android and iOS
• No installer, no admin rights
• No licence server to keep alive
• Updates arrive by reloading the tab