IFC requirements · RAVA & Ryhti

A machine-readable IFC model built for authority requirements

Finland’s new Building Act, together with the Ministry of the Environment (YM) and the Helsinki metropolitan area building authorities (RAVA / RAVA3Pro), require a standard-compliant data model. Our design target is a BIM model attached to the building permit application that can be used directly for authority checking, energy assessment and the national Ryhti data system.

IFC4 Reference View V1.2.METRE.N2000 height system

A target, not an approval: this page describes the generator’s design targets. The permit and the data model are always approved by the competent building authority.

Legislation

Building Act and the Ministry’s Ryhti requirements

Two requirements define what a permit attachment’s data model must deliver.

Machine readability and transfer

Drawings are submitted as an open-standard IFC data model. Municipal building authorities validate the model and forward its data automatically to the national Ryhti system maintained by the Ministry of the Environment and Syke.

Our design target is a model the receiving authority can inspect without manual interpretation: geometry, units and space data in one schema-compliant structure.

Statutory reports carried by the model

The model is designed to contain the main drawing data (floor areas, volumes), the input values for the energy assessment (envelope areas, U-values, orientations) and the material and mass basis required by the climate report and material schedule.

When the inputs live in the model instead of separate spreadsheets, the same data serves permit handling, energy calculation and later maintenance of the project.

RAVA3Pro

Criteria behind metropolitan automated checking (Helsinki, Espoo, Vantaa)

Four technical blocks that municipal model checks rely on. Open a section to see how the generator is designed to deliver it.

01

Schema and units

The primary requirement is IFC4 (Reference View V1.2). Length is expressed in exact metres (.METRE.) with three-decimal tolerance, so municipal area calculations are not distorted the way they often are in millimetre models.

The unit assignment is written at project level (IfcUnitAssignment), so every element is interpreted at the same scale.

FILE_SCHEMA(('IFC4'))IFCSIUNIT .LENGTHUNIT. .METRE.3 decimals
02

Spatial structure and storey levels

An intact hierarchy: Project, Site, Building, Storey. Storey elevation corresponds to the N2000 height system at floor level.

No orphan elements: every wall, slab, roof and opening is linked to its storey through IfcRelContainedInSpatialStructure, so a checker always finds an element under a storey.

Project / Site / Building / StoreyStorey.Elevation = N2000IfcRelContainedInSpatialStructure
03

Spaces (IfcSpace) and area sizing

Every room is modelled as its own IfcSpace object and grouped into thermal zones. Municipal automated checks compare these against the areas in the 2D drawings.

Lamit models are sized with the target that room areas match the main drawings, so discrepancies do not surface during permit handling.

IfcSpace per roomThermal zone groupingAreas vs. 2D main drawings
04

Building elements and envelope split

The external envelope is separated strictly (IsExternal = TRUE). Base slabs are typed with BASESLAB and roofs with ROOF.

Windows and doors are cut into walls with proper IfcOpeningElement relations rather than direct wall breaks, keeping envelope geometry and areas intact.

IsExternal = TRUEIfcSlab .BASESLAB.IfcSlab .ROOF.IfcOpeningElement

Mapping

Compliance matrix: RAVA criteria vs. the A-Nodes generator

Line by line: what the authority requires, the standard criterion, and how the generator is designed to deliver it.

RAVA / YM requirementStandard criterionA-Nodes 2D-to-IFC generatorTarget
IFC schemaIFC4 Reference ViewWritten directly as FILE_SCHEMA(('IFC4'))Met
UnitsLength: metre (.METRE.)IFCSIUNIT(*,.LENGTHUNIT.,$,.METRE.)Met
Height systemN2000 floor level per storeyStorey.Elevation = 45.5 read from the sectionMet
Base slab typeGround contact identifiableIfcSlab.PredefinedType = .BASESLAB.Met
U-value dataPresent on envelope elementsPset_SlabCommon, Pset_WallCommon, Pset_RoofCommonMet
Space dataRoom-by-room breakdown1+n IfcSpace objects (LIV/R, BED, WORK etc.)Met
Thermal designMachine-readable design valuesPset_SpaceThermalDesign (T_i, W, W/m²)Exceeds code

The matrix describes the generator’s design targets and implementation. It is not an authority approval and does not guarantee passing automated checking: final approval always rests with the building authority, and every project is validated separately.

Climate report

Ready for what comes next: a complete integration

So that the model also serves the climate report required by the new Building Act and full permit readiness, Lamit’s generator uses the Talo 2000 building classification (IfcClassificationReference). True north is bound to the model coordinate system for passive solar calculations. Masses and volumes are derived directly from the model’s construction layers (concrete, timber, insulation) into the material schedule of the statutory carbon footprint calculation.

Talo 2000 classification

IfcClassificationReference binds building parts to the national code list, making quantities and materials machine-readable.

True north and solar geometry

True north rotation is part of the model coordinate system, so passive solar and shading calculations repeat on the same geometry.

Masses and volumes

Masses and volumes are derived from construction layers into the carbon footprint material schedule without separate take-off work.

Create a data model built for permit handling

Tell us the format of your source material (paper drawing, 2D PDF/DWG or native IFC) and we will walk through the RAVA targets and the delivery format for your project.