Practical guides for Swiss building owners and asset managers on checkable EIR data contracts, goal-driven requirements, and Actions on the published plan.
Elementplan
From master template to checked IFC. Read in order, or jump to the step you need.
A visual tour of Elementplan: from data contract to checked model
The updated pragmaticBIM Elementplan in screenshots, plus the Swiss Starter Elementplan on GitHub - a public master with more than 40 workflows and around 80 elements mapped to seven project goals.
Configure an Elementplan project on a draft. Set goal levels, select use cases, then assign the Information Delivery Plan. Submit, approve, and publish.
Maintain the Elementplan master catalogue. Create a draft, edit goals, workflows, elements, and values, then submit, approve, and publish a version projects can copy.
Create an Elementplan project from a published master version. Set name, number, and language. The viewer stays empty until you configure, approve, and publish.
Elementplan turns BIM modelling requirements into a versioned project plan. Copy a master template, configure this building, publish, and check IFC against the same rules.
Import another planner's buildingSMART IDS into an Elementplan project draft. Review matched and new specifications, apply to the draft, then update the IDP and publish.
Browse published Elementplan requirements by model, filter by use case and phase, and download IDS, Excel, and PDF reports. Downloads may need an email login code.
How to Derive BIM Data Requirements Directly from Project Goals
Stop copy-pasting LOD and EIR checklists. Set seven project goals in pragmaticBIM to auto-activate workflows, required elements, and export IDS plus contractual Excel/PDF.
ISO 19650 as Data, Not Documents: IDP vs BEP Suites
Compare BIMQ, Plannerly, and pragmaticBIM by buyer job. pragmaticBIM turns ISO 19650 into goal-driven IDP data contracts (Git, IDS, Excel, Actions) - not a BEP document suite.
How to Define True Data Requirements in the AI Age: Beyond the IDS Artifact
IDS is an exchange artifact, not a data requirement standard. Use the open-source elementplan-data-schema to define Domains, Elements, and AI-ready data contracts.
The 3 Levels of BIM Quality Checks: How Building Owners Tune the Algorithm
Swiss building owners can replace extra staff and 3,000-page specs with three automated BIM QA levels—unit, integration, and system tests—for data presence, geometry logic, and business rules.
The "One BIM Standard" Is a Myth (And How We Solve Data Anarchy Anyway)
Stop chasing a single BIM standard for every stakeholder. Avoid manual eBKP typing, data hoarding, and 80-page PDFs—use minimalist workflows and automated IFC translation instead.
Why Building Owners Should Not Order BIM Use Cases (And What You Need Instead)
Stop copying BAP templates and ordering collision-check use cases. Swiss building owners should define EIR outcomes and automated QA, not planner workflows.