All tools / IDS Model Check

Check an IFC model against an IDS file, in your browser.

Drop a building model (.ifc, .ifcxml or .ifczip) and a buildingSMART Information Delivery Specification (.ids). You get every specification's result, each failing element with the reason, and a BCF issue list your BIM tool can open. Nothing is uploaded.

Check a model Write an IDS Get the starter IDS

334 / 334buildingSMART IDS test cases right (how it was checked)
under 1 sfor a 22 MB, 424,819-entity Revit export in Chromium (0.8 s; 1.4 s on the command line)
IFC2X3 · IFC4 · IFC4X3all six facets: entity, attribute, property, classification, material, part of

Run a check

or drop the file here
or drop it here, or

What it checks

An IDS lists specifications. Each says which elements it applies to (for example every IFCWALL with Pset_WallCommon.IsExternal = true) and what those elements must have (a FireRating, a Uniclass code, a material, a place on a storey). The checker reads both files, finds the elements each specification applies to, and tests every requirement on each, following the IDS 1.0 rules for required, optional and prohibited facets, value restrictions (enumerations, patterns, ranges, lengths), floating-point tolerance and unit conversion to SI.

Before any model is read, the IDS itself is audited against the IFC schema its specifications name: class names that do not exist or are not upper case, attributes a class does not have (or has only as derived or inverse attributes), values compared with lists, objects or selects, numbers written with a decimal comma, integers written as 42.0, booleans written FALSE, patterns on numbers, unknown data types, and prohibited specifications that carry requirements. Such a specification is reported as INVALID, with the reason, instead of failing every element. Standard sets are checked too: Pset_WallComon, Qto_DuctSegmentBaseQuantities.Lenght or IsExternal typed IFCTEXT each get the standard name or type back. Those are still run against the model and shown as a warning, since a project's model can carry exactly what its IDS asks for. The file's own structure is checked against buildingSMART's ids.xsd as well, with the line of each fault: elements out of order, an attribute in the wrong place (IDS 0.9's minOccurs on <specification>), a cardinality or ifcVersion value IDS 1.0 does not have. Tools that validate first refuse such a file whole; 12 of 65 IDS files published on GitHub do. Where a fault has one right answer (IDS 0.9's minOccurs, IFC4X3 for IFC4X3_ADD2, the wrong namespace, values missing their <simpleValue>), the audit offers the repaired file to download, with your comments and layout kept. Patterns are read as XML Schema regular expressions, as IDS specifies and IfcTester does: a (?:...) group or a lazy *? is an error (IfcTester stops on it), and ^IFC.*SYSTEM is flagged because in XML Schema ^ is a plain character, so the pattern matches nothing; the repaired file drops the anchors. A bare \w or \s means one thing in the standard and another in IfcTester (the standard's \w leaves out _; IfcTester's \s takes a no-break space), so the repair asks which you meant and spells it out so every checker agrees. Writing an IDS? Drop it alone and press Audit the IDS only.

Starting from scratch? The starter IDS asks for what most coordinators want before a model is shared: walls marked external and load-bearing, a material on every wall, named doors and windows on a storey, named spaces, and no building element proxies. For bridges, roads, rail, earthworks, ducts and pipes in IFC 4.3, the infrastructure and services starter gives the same verdicts as IfcTester on all 180 results over buildingSMART's ten IFC 4.3 sample models. Edit either in any text editor, or write your own in the IDS editor, which offers each class's standard property sets with their data types and audits every specification as you write it. Open your model in the editor and it offers the classes and property sets that model actually carries, a project's own sets (Revit's PSet_Revit_*) included, and each property's values: one click allows exactly the values the model holds, or its range, rounded outward because IDS ranges take no tolerance.

Requirements agreed in a spreadsheet? Drop an .xlsx or .csv with one row per facet and it is written into IDS 1.0, audited and run like any IDS; a row it cannot read is named by its number. Audit any IDS and Download as a spreadsheet gives the same table back, to review in Excel, LibreOffice or Google Sheets. Dates, numbers and true/false that Excel stored as typed values are read as Excel shows them (2024-01-01, true), and the downloaded workbook keeps its cells as Text so what you type stays as typed. A value cell holds the exact value (Pset_DoorCommon) or a restriction: one of: EI30 | EI60, pattern: [A-Z]{2}[0-9]{3}, >= 0; < 10, max length: 12; the downloaded workbook has a Read me sheet with the rest. All 334 of buildingSMART's test IDS files and 62 of 64 IDS files published on GitHub come back from the spreadsheet with the same content (the two that do not use a tag IDS 1.0 does not have, or no <info>).

Already using buildingSMART-community's Excel2IDS template, asset categories in columns and an X where a category needs a requirement? Drop the filled workbook here as it is: no Windows tool to run, and nothing leaves your browser. It is written into one IDS per purpose (discipline), as Excel2IDS does, each audited and ready to run; REPLACEME rows, quoted patterns and comma lists are read as the template's instructions say, and a class typed IfcWall is written IFCWALL with a note. The other way round, which Excel2IDS cannot do, as an Excel2IDS workbook after an audit puts an existing IDS into the template so a team can review it there; it says which specifications the template cannot hold (ranges, partOf, a material asked for with no name). On 64 IDS files published on GitHub, 309 of 507 specifications fit the template and all 309 come back with the same requirements (how it was checked). Moving from the Excel2IDS .exe? After the workbook is read, the page lists each cell where that tool would write a different IDS or stop: an empty purpose, a toggle typed as text, a typed TRUE it writes as True, a REPLACEME row that borrows another row's instructions. The template's own sample has one: its "External doors" category asks for True, which matches no door (the rules).

How the results were checked

buildingSMART maintains a suite of 334 small IFC/IDS pairs, each named with its expected result (pass, fail, or invalid, which must not pass). This checker gets all 334 right. The scoring script, eval/run-testcases.mjs, fetches the suite from buildingSMART's repository and re-runs it; the suite itself is not copied here because its licence (CC BY-ND 4.0) does not allow mixing it into MIT code. On one point the suite and the IDS user manual disagree (a single value against a bounded property); the checker follows the suite, and the README says where.

Questions

What is an IDS file?

IDS (Information Delivery Specification) is buildingSMART's XML format for saying what information a model must contain: which elements need which properties, attributes, classifications, materials and relationships. Version 1.0 was approved in 2024. A client or BIM manager writes one IDS, and every party's model can be checked against it by software instead of by eye.

How do I know the results are right?

buildingSMART publishes 334 pairs of small IFC and IDS files with the expected result of each, covering every facet, restriction, tolerance and cardinality rule. This checker gets all 334 right; the script that scores it is in the repository so anyone can re-run it. Real models still contain cases those files do not cover, so treat a result as a strong first pass and check anything surprising.

Can it check the IDS file itself?

Yes. Drop an IDS on its own and press Audit the IDS only. Each specification is checked against the IFC schema it names: class and attribute names, data types, values IDS cannot compare (lists, objects, selects), numbers, integers and booleans written in a form IDS does not accept, and prohibited specifications with requirements. Standard property and quantity sets are checked against buildingSMART's templates: a Pset_ or Qto_ name or property the standard does not have (Pset_WallComon, AkousticRating, with the name it most likely meant), a dataType the template does not give, and a set the selected classes cannot carry. Of buildingSMART's 27 invalid test files it flags 26 as invalid, and none of the 307 valid ones; the 27th is wrong only in combination with its model. All 12 example IDS files in buildingSMART's repository audit clean. The file is also checked against the IDS XML schema (ids.xsd): on 145 public and test files and 2,935 deliberately broken copies it gives the same valid-or-invalid verdict as IfcTester's own schema validation, and says which line to fix.

Is my model uploaded?

No. The model and the IDS are read by JavaScript in your browser tab. The only files the page fetches are its own schema tables from this site. You can also download the code and run it offline, or use the command line version.

Why not use Solibri, BIMcollab or IfcTester?

Those are good tools. Solibri and the commercial checkers do far more (clash detection, geometry rules) and cost a seat licence. IfcTester from IfcOpenShell is free and excellent but needs Python and a command line, or a desktop BIM tool. This page needs nothing installed, opens on any computer, and turns a failing check into a BCF issue list your design tool can open.

Which IFC versions work?

IFC2X3, IFC4 and IFC4X3 (ADD2) models, as STEP (.ifc), ifcXML (.ifcxml) or zipped (.ifczip, holding either). IFC2X3 occurrence classes are resolved through buildingSMART's type mapping table, so an IDS that asks for IFCAIRTERMINAL also finds an IfcFlowTerminal typed by an IfcAirTerminalType.

Command line and CI

Framing the same house? Wall Framing Takeoff reads the walls from the same IFC file and lays out studs, plates and a lumber order.

Building the submittal log for the same job? Submittal Register reads the project manual PDF and lists every Part 1 submittal by spec section.

The same engine runs in Node 20+, with no dependencies, so a model can be checked on every export or in a CI job: node cli.mjs model.ifc spec.ids --bcf issues.bcfzip exits 1 when a specification fails.

On GitHub, one step checks every model in a repository against every IDS on each push: uses: Duncan-Haywood/oss-monorepo/ventures/ids-model-check@main with models: "models/**/*.ifc" and ids: "requirements/*.ids". Failing specifications appear as annotations on the failing element's line, IDS mistakes (an abstract class that selects nothing, a value with no data type) on the specification's own line in the IDS file, a summary table on the run, a JUnit report your CI already reads and BCF files for your BIM viewer; node ci-cli.mjs does the same in GitLab, Jenkins or a pre-commit hook. In GitLab it also writes a Code Quality report, so a merge request lists the elements it broke or fixed, tracked by GlobalId so a re-export that renumbers the file does not show as thousands of changes. Source and instructions: GitHub.