Femra · Guide
Femra basics
Femra gives the AI assistant you already use a structural engine: finite element analysis and Eurocode checks, with every number open for review.
What Femra is
Femra is a structural finite element program that runs in the browser at femra.app. It analyses frames, trusses, slabs and walls, and checks them to the Eurocodes: steel, timber and cross-laminated timber, concrete, masonry and foundations, with dynamics, buckling and seismic analysis beside the static one.
What makes it different is how you work with it. Femra is built to be operated by an AI assistant. You add it to your own assistant as a connector, an add-on that gives the assistant a set of structural tools. You keep the assistant you already use; Femra supplies the engine and the checks.
Your assistant drives
It reads your drawings and your words, builds the model, applies loads and runs the analysis through Femra's tools.
Femra computes
The analysis and every check are Femra's own code. The same input gives the same result on every computer.
You review and sign
Every number opens its calculation: formula, values, clause and load combination. The responsibility stays with the engineer.
Connect your assistant
You add the connector once in your assistant, then let it work in a Femra tab.
- Sign in at femra.app. Femra needs an account; you sign in with EikHub, the same sign-in as Stomra.
- Add the connector. In Femra, open Femra → Connect an assistant (or the assistant chip in the app bar). It shows the connector's address,
https://femra.app/mcp. Add it in your assistant: in Claude under Settings → Connectors → Add custom connector, in ChatGPT under Settings → Apps & Connectors in developer mode. Sign in with EikHub when the assistant asks. - Let the assistant use your tab. Tick Let my assistant use Femra in this tab. From then on, the assistant's tool calls run in that tab, so you see every change, and each call is listed under Activity.
- Name the project. With several projects open in different tabs, the assistant names the project it works on in each call. You never have to close a tab to point it at the right one.
The assistant first reads Femra's own guide through the connector. It explains Femra's units (metres, kN and kNm, sections in millimetres), its commands and its rules, so you do not need to brief the assistant on how Femra works.
How an analysis goes
A typical analysis, say a single-storey steel hall or a timber floor, goes like this.
- Start a project. A new project on the start page, one of Femra's examples, a building opened from EikHub, or a file from another program (see below).
- Say what you need. Give your assistant the drawings, a sketch or a description: spans, heights, materials, use and location. Ask for what you want checked.
- The model arrives in batches. The assistant sends changes as batches of commands. A batch is all or nothing, and the assistant can run it as a dry run first: Femra validates it and previews the analysis, including whether the structure stands, before anything is changed.
- Loads and combinations. Load cases (self-weight, imposed, snow, wind) and their combinations to EN 1990. Snow and wind can be generated from the location, with the Swedish combinations.
- Run. The analysis shows its phases, how far it has come and the time left. Cancel, or Esc, keeps the previous results.
- Check. Femra checks every member and panel and colours the model by utilisation. The Design panel lists every checked element, most utilised first.
- Review and report. Open any element's calc sheet, change what needs changing, run again. The calculation report collects the model, loads, results and sheets, in English or Swedish.
Reviewing the numbers
Femra's rule is that no number stands alone. Every check is written by the same code that computes it, as lines of symbol, formula, the formula with the numbers put in, result, unit and clause. A line looks like this (an illustration of the form, for an IPE 300 in S355 in bending):
M_c,Rd = W_pl,y · f_y / γ_M0 EN 1993-1-1 6.2.5
= 628 000 mm³ · 355 MPa / 1.0 = 222.9 kNm
η = M_Ed / M_c,Rd = 150.0 / 222.9 = 0.67 ULS combination 3
Ways to get to the numbers:
- The Design panel lists each checked element with its governing check; a click opens its calc sheet.
- The magnifier (the magnifying glass in the app bar, or I): a click on any element opens its calc sheet card, with the element's other sheets as tabs, a summary (material, section or layup, length, mass) and a figure drawn from the model.
- Query (Q in the view bar): a click pins a label with the result shown at that point: a moment along a member, a displacement, a support's reactions. Values (V) labels each part's largest and smallest value.
- Assumptions are written on each sheet, and anything the assistant or an import had to assume is said in the messages.
The fingerprint in the status bar and the report is a hash of the displacement results of every load case. The same model gives the same fingerprint on every machine, so a printed report can be tied to the exact model it came from.
Staying in control of the model
Every change visible
The assistant works in your tab. Activity lists what you and the assistant did.
Undo
Every batch is one step, undone like any change you make yourself.
Variants
Copy a design to try a smaller beam or another column, then compare utilisation, displacement and material side by side.
Versions
The project is saved as versions as you work; a version can be restored or copied to a new variant.
You can also point at things for your assistant. Draw on the 3D view with the pen and choose Send prompt to assistant…: the sketch and your words become a work order, numbered in the project, which your assistant picks up and carries out. The Work orders dialog lists them with their state.
Several people can work in the same project at once; a change shows for everyone as it is made.
Bringing a model in, and taking it out
| Format | In Femra |
|---|---|
| OpenEik and EikHub | Open a building from EikHub, pull its changes with a review, propose changes back for the building's admins to merge, or publish a model made in Femra as a new building. |
FEM-Design .struxml | Import and export, with plates and walls. A model that came from a file is written back into it: what changed is patched, the rest kept. |
SAF 2.2 .xlsx | Import and export of the open Structural Analysis Format. |
STAAD.Pro .std | Import and export of the input file: joints, members, plates, supports, load cases and combinations. |
ANSYS Mechanical APDL .dat | Export of Femra's analysis model as an input file. |
Each format is written, read back by Femra and analysed again, and the reactions of every combination must agree. Opening an exported file in the other program is still the engineer's step.
How Femra is checked
The solver runs ten classical problems from the literature with every change, from Euler's column to the pinched cylinder, and the steel checks run against published worked examples, number by number. The results, the deviations and the sources are on usefemra.com/verification, and the same cases are in the app under Project → Verification, where you can run them or open one as a model.
A deviation within tolerance shows that the solver reproduces known answers. It does not make a model right: the engineer still checks the model, the loads and the assumptions.
Terms
| Connector | An add-on to an AI assistant over the Model Context Protocol (MCP). Femra's gives the assistant tools such as femra_execute (change the model), femra_run (analyse) and femra_design (check). |
|---|---|
| Batch | A set of model changes applied together, all or nothing. |
| Dry run | A batch validated and previewed without changing the model. |
| Utilisation (η) | Action effect divided by resistance. Up to 1.0 passes. |
| Calc sheet | The written calculation behind a check, line by line with clauses. |
| Variant | A design alternative inside one project, with its own model and results. |
| Fingerprint | A hash of the results that identifies the model a report came from. |