All tools / IDS Model Check / IDS Editor
Write an IDS from the standard property sets.
Pick an IFC class, then a standard property or quantity set that class can carry, then one of its properties. Or open the model you are writing for, and the editor offers the classes and sets it actually carries, your project's own sets included, and the values its objects hold (for properties, attributes such as Name or ObjectType, and the codes in each classification system), so a requirement can allow exactly those values or the model's range. The editor fills in the data type from buildingSMART's templates, offers the enumeration values the standard lists, and audits every specification as you write it. Download the .ids, or send it straight to the checker. Nothing is uploaded.
Loading the IFC schema and property set templates...
Audit
The IDS
How it works
Already have an IDS? Open an IDS file reads it in. Everything the page's controls can hold without changing it becomes an editable row; anything else (a pattern on a class name, a range with two lower or two upper bounds, a non-standard Pset_ name) is kept as written: shown as its XML, written back unchanged, and removable. Opened and written back, 64 of 64 IDS files from public repositories (86.4% of their facets editable, a project's own property sets, conditions in the applicability, exclusive bounds and date ranges included) and all 187 of buildingSMART's passing test cases ask for the same thing as before, and none stops validating against ids.xsd. The one change: requirements on a prohibited specification, which IDS 1.0 cannot evaluate, are dropped and named when you open the file. Faults that break buildingSMART's ids.xsd and have one right answer (IDS 0.9 names, a bare &, IFC4X3 for IFC4X3_ADD2, a pattern written for another regex engine such as ^...$) are repaired as the file opens, and the page lists each change: of 65 public IDS files, 60 are written back valid with nothing left for a pattern engine to misread, up from 55.
Open a model to write for reads an IFC model (.ifc, .ifcxml or .ifczip) in a background thread of this tab, with the checker's own reader, and lists what it already carries: each class with how many of it, the property and quantity sets on them (standard or the project's own, with the data type the model writes each property in) and the classification systems in use. The editor then offers those first: the model's classes in the class list, and, on each requirement, the sets the model's objects of that class carry, with how many carry them. A set of the project's own (Acme_Wall, not a Pset_ or Qto_ set) becomes a row you can edit: its name, the property and a data type from the IFC schema, filled in from the model when it has the property. The model is not uploaded or kept: close the tab and it is gone.
Narrow it limits a specification to the elements that also match a condition: a property value (only walls whose Pset_WallCommon.IsExternal is true), an attribute (PredefinedType SOLIDWALL), a classification system, a material or a place. IDS calls these the applicability; an element that does not match is not checked at all, so "external walls must have a fire rating" does not fail internal walls. With a model open, each condition says how many of the class's objects it keeps, counted the way the checker counts them, and warns when it keeps none.
The class list is every non-abstract class in the IFC schema you pick that can carry at least one standard set; the set list is the sets whose templates apply to that class, its ancestors, or the occurrence a type object is for (Pset_WallCommon on IFCWALL, IFCWALLSTANDARDCASE and IFCWALLTYPE); the property list and data types are the template's. IDS matches exact classes, so a specification on IFCWALL misses IFCWALLSTANDARDCASE unless both are listed: tick and its subclasses to list them (each class in the list has its own box). A property whose template gives no single data type (a bounded value, a table, a list or a reference) is checked for presence only.
Every choice the editor offers was written out and audited: for each of the three schemas, every offered class, every set it offers for that class and every property of the set, once on its own and once with a value of the right kind. That is 203,433 specifications (32,823 for IFC2X3, 46,516 for IFC4, 124,094 for IFC4X3), and the audit finds no error and no warning in any of them (eval/editor-roundtrip.mjs). A sample of 15,102 specifications, one per class and set plus every facet, value kind, cardinality and partOf relation the page writes, validates against buildingSMART's IDS 1.0 XML schema in IfcOpenShell's IfcTester (eval/editor-xsd-check.py).