Check BIM requirements with IDS

BIM requirements are IDS rule sets attached to an IFC model revision. SeveUp App audits them automatically and flags non-compliance. This article shows how to create a new requirement, import one or more IDS files and link them to a project.

BIM requirements are IDS rule sets attached to an IFC model revision. SeveUp App audits them automatically and flags non-compliance. This article shows how to create a new requirement, import one or more IDS files and link them to a project.

Introduction

The BIM requirements screen holds your IDS requirement sets. This is where you create a new rule, import an existing .ids file or edit a set already in place. Once the requirement is linked to an IFC model revision, the audit starts on its own. This guide walks through every step: creation, import, linking and reading the results.

Why check BIM requirements with IDS? An IDS file states exactly what a model must contain: object classes, required attributes, allowed values and relationships. The audit compares these expectations against the actual revision content and lists the gaps. You save time on quality checks and cut down back-and-forth between project stakeholders.

Glossary

IDS
XML format called Information Delivery Specification that describes the requirements a BIM model must meet.
IFC
Open format, Industry Foundation Classes, used to exchange digital building models between software.
Revision
A version of a model imported into a SeveUp App folder.
Audit
Automatic check of an IFC revision against an IDS requirement set.

Prerequisites

  • A SeveUp App account with access to the BIM module.
  • A valid .ids file if you choose to import.
  • At least one IFC revision in a folder so you can link a requirement.

Create a requirement

Open the BIM requirements screen. Click the "New requirement" button. Fill in the name, type and description, then save. The confirmation banner shows "Requirement saved".

You can edit an existing requirement at any time. Click its row, make your changes and save.

Import IDS files

Click "Import IDS files". The modal opens on the "Files" step. Drop your .ids files into the drop zone or click "Browse files".

Move to the "Names" step. Review the name and description of each requirement. Then on the "Link" step, optionally attach existing folders. The "Search folders…" field helps filter the list. If no folder matches, the message "No folders found" appears.

When everything is ready, click "Import # requirements". The message "# requirements imported" confirms the operation.

Open the requirement record. Choose the IFC revision to audit. The audit starts automatically as soon as the link is set. Results appear in the revision's compliance report.

What can go wrong

  • "No BIM requirements yet" : the list is empty. Create a requirement or import an .ids file to get started.
  • "Could not load BIM requirements" : the server did not respond. Reload the page or check your connection.
  • "All uploads failed." : the .ids file may be malformed, empty or too large. Open it in an XML editor to check the syntax.
  • "Failed to create requirement." : a required field is missing or the name already exists. Fix the form and try again.
  • "Delete permanently" : this action clears the linked revision history. The record can be archived, but its revision data will not be recoverable.

FAQ

What does an IDS file contain?
An IDS file lists technical requirements for a model: expected object classes, required attributes, allowed values and relationships between objects.

How do I attach an IDS file to an IFC revision?
Create or import the requirement, open its record and select the relevant revision. The audit starts on its own.

Can I import several requirements at once?
Yes. The "Import IDS files" modal accepts multiple .ids files. Each one becomes a separate requirement set.

What happens when I delete a requirement?
Standard deletion archives the record. You can restore it with "Restore", but without past revisions. Permanent deletion, available via "Delete permanently", cannot be undone.

Why does the audit not start?
Check that the requirement is linked to a revision and that the IDS file is valid. A revision with no linked requirement will not trigger an audit.

Did this article help?

Verified on SeveUp App v1.0 on 18 September 2026.

Vérifié sur SeveUp App v1.0 le 2026-09-18