[ad_1]
\n<\/p>\n
As I\u2019ve written previously<\/a>, Finland will start implementing BIM-based building permitting in 2026. The national RAVA3pro project laid the groundwork for the new process by creating the necessary IFC data definitions for BIM models, including those for building services.<\/p>\n A recent article<\/a> in the Finnish Building Services Magazine (Talotekniikkalehti) featured the groundbreaking work of Markus J\u00e4rvenp\u00e4\u00e4<\/a>, Group Manager for BIM Development at Granlund<\/a>. He has been occupied by the national standardization of building services models for the last five and a half years.<\/p>\n Standardizing MEP (mechanical, electrical, and plumbing) model information was necessary because no national or international standards exist for the entire industry.<\/p>\n \u201cIFC model data structures and content are currently a heap of fluff. They cannot be used systematically, because the models differ across every project, and nobody has the resources to rebuild functionalities on top of that fluff heap every time,\u201d J\u00e4rvenp\u00e4\u00e4 says.<\/p>\n J\u00e4rvenp\u00e4\u00e4 stresses that this standardization isn\u2019t solely for regulatory compliance. It addresses the needs of the entire construction ecosystem. It enables companies to build their own workflows on a standardized basis.<\/p>\n For example, a cost estimator receives initial data, then enriches it with their expertise. Models don\u2019t have to include every small item, like supports. These can be sourced from external databases during the cost estimation process.<\/p>\n J\u00e4rvenp\u00e4\u00e4 explains that creating and using models within this framework is easy for designers.<\/p>\n \u201cWhen modeling, say, a sound attenuator, the designer simply selects \u2018silencer\u2019 from a list, and the required data structure is automatically embedded in the IFC model. Designers can focus on their core expertise instead of needing deep technical data skills.\u201d<\/p>\n A duct knows it\u2019s a duct, and it always includes, in the same data structure, for example, its connection size and length.<\/p>\n According to J\u00e4rvenp\u00e4\u00e4, any process needing object-level data will benefit from the standard.<\/p>\n Obvious use cases include cost estimating, location-based logistics, and sustainability calculations.<\/p>\n You can use standard MEP data from previous projects and connect it to, for example, the actual costs for benchmarking purposes. That way, you get an idea of costs for a particular type of project with specific MEP solutions even before you\u2019ve started the design process.<\/p>\n Finnish companies are testing with the new standard. While widespread uptake is still pending, some RFPs already require data structures that adhere to the new framework.<\/p>\n \u201cI see the act and decree as strong boosters for the industry. It\u2019s great that this was accomplished at the national level. One company\u2019s internal spec won\u2019t suffice; this must become a de facto requirement for the whole sector to see real benefits,\u201d says J\u00e4rvenp\u00e4\u00e4.<\/p>\n International IFC standards provided the foundation, but not the semantics needed for legal compliance and data automation for MEP. In a previous presentation<\/a>, J\u00e4rvenp\u00e4\u00e4 stated that IFC entities and enumerations cover only 7% of MEP objects and 4% of MEP system types, which is insufficient for consistent automation.<\/p>\n RAVA3Pro, guided by J\u00e4rvenp\u00e4\u00e4\u2019s MEP expertise, bridged the gap by turning \u201cfluff\u201d into actionable data. With the new framework, models will be machine-readable, verifiable, and comparable across projects, tools, and even lifecycles.<\/p>\n Through RAVA3Pro, Finland is establishing another European benchmark for how national BIM frameworks can enhance digital permitting, lifecycle management, and sustainability.<\/p>\n Note: The quotations are my translations from Finnish.<\/em><\/p>\n<\/div>\nFluff does not scale<\/h2>\n
Not just for regulatory needs<\/h2>\n
Integrating with the design process<\/h2>\n
Serving multiple workflows<\/h2>\n
The implementation has commenced<\/h2>\n
The takeaway<\/h2>\n