Isoleret

0DS 452 Annex A cells within 3 mm

0Energihåndbogen cells reproduced

0answer key, class from table 6.4

0kWh/yr saved in the demo building*

0fire conflicts found and resolved

0incl. browser = server to 1e-9

* at example prices: 9,749 DKK/yr, 8.1-year simple payback; fictitious building.

Tour

From the 3D heat-loss map to a number you can check by hand

Rendered frame by frame from the running app.

Energy meets fire

Thicker insulation can break a tested seal

A penetration seal is classified only with the insulation it was tested with. An energy upgrade that changes the type, thickness or brand turns a tested seal into a deviation.

Isoleret checks each fire-rated crossing against the tested configurations (ETA-21/0110, ETA-20/1322) before and after the proposal. Where they conflict, it applies DS 452 table 6.2, which needs only half the thickness in a penetration: keep the tested insulation over the tested length and upgrade outside it.

See the 29 crossings in the demo →

Validation

Reproduces the published tables

DS 452 Annex A (tables A.1/A.2, 72 cells): RMS 0.76 mm, max 2.4 mm, with one stated design λ (the standard does not print it). Energihåndbogen (tables 11/12/15/16, 96 cells, λ 0.038 as stated): bare-pipe savings within 1.7 %.

Finding: the basement tables say half the loss is useful heat. The published numbers only reproduce without that rule.

Method and charts →

Verification

Every file, every number, the method

A manual check for a person, and an automated one on every change.

1The file

SHA-256 manifest of every deliverable with producer, model and code version. Drag a file onto Verificér: hashed in the browser, never uploaded.

2The number

"Vis beregning" on every run: λ at the mean temperature, R per layer, h_cv, h_r, q, U against the class limit, each landing on the report's value ✓. The same steps are in the PDF appendix.

3The method

python -m isoleret.reproduce re-runs validation and audit from the source model: 6/6. Cell-by-cell CSVs of both validations.

Output-by-output verification table →

MCP

Ask it from an assistant

check_pipe, ds452_class, audit_overview, list_runs, get_run, fire_crosscheck, materials, run_audit. Same engine, same numbers.

{"mcpServers": {"isoleret": {
  "command": "python",
  "args": ["<repo>/src/mcp_server.py"]}}}

Every pipe in the building, against DS 452, and against the fire seals it passes through.

From the 3D heat-loss map to a number you can check by hand

Thicker insulation can break a tested seal

Reproduces the published tables

Every file, every number, the method

Screens

Ask it from an assistant