---
name: ifc-ids-validation
description: Check an IFC model against an IDS (buildingSMART Information Delivery Specification) file with IfcOpenShell's ifctester and return pass/fail per requirement, the failing elements by GlobalId, an HTML report and optionally a BCF file for the modeller. Use when the user has an .ids file or information requirements (EIR, LOIN, BIM requirements, "requisitos de información") and wants to know whether a model complies, or says "validate with IDS", "check the model against the requirements".
---

# IFC validation with IDS

IDS 1.0 is the buildingSMART standard for machine-checkable information requirements: for each set of elements (applicability) it states which attributes, properties, materials or classifications they must have (requirements). This skill runs it and explains the result in plain language.

## Inputs
- The model (.ifc) and the requirements (.ids). If the user only has requirements in a table or a PDF, build the .ids first with the `loin-to-ids` skill and have a human approve it.

## Procedure
1. `pip install ifctester` (tested with 0.9.0, which also installs IfcOpenShell). Report the versions.
2. Run `python scripts/check_ids.py model.ifc requirements.ids --html ids_report.html --bcf ids_issues.bcf --csv ids_failures.csv`.
3. For every specification, report: PASS/FAIL, applicable elements and how many pass.
4. **A specification with 0 applicable elements is not a pass.** Explain the usual causes: wrong class (IfcWallStandardCase vs IfcWall in IFC2X3), a predefined type the model never uses, or an ifcVersion in the IDS that does not match the model schema.
5. Group failures by reason (missing property set, missing property, wrong data type, value not allowed) and show the top 3 with element names, so the modeller knows what to fix in the authoring tool, not in the IFC.
6. Deliver the HTML report for humans, the CSV for tracking and the BCF if their coordination tool reads it (BIMcollab, Revizto, Solibri, Bonsai, ACC/Forma via BCF import).

## Output
- One table: specification · applicable · pass · status · top reason.
- "What to fix first": max 5 actions, each naming the authoring-tool step (e.g. "map Revit parameter Fire Rating to Pset_WallCommon.FireRating in the IFC export settings").
- The files.

## Never
- Never edit the IFC to make it pass; fixes belong in the source model and its export settings.
- Never rewrite the IDS to make the model pass without the information manager's approval.
- Don't paraphrase requirement values: quote them as written in the IDS.

Reference: `references/ids-quick-reference.md`.