Pick a predefined test and stage
- On Check, add the model.
- Under Tests, find the predefined test under Public. Type in the search box to find it by its name or market.
- Choose the test's row. A line that starts with Stage: opens under it, with a short code for each stage. Choose the code of the stage your project is in. Point at a code to read the stage's name.
- Read the line above Run checker: it names the test, its stage and how many rules it has.
- Choose Run checker.
The predefined tests
Predefined tests are IDS files IFC Checker wrote to start from. On Check they are listed under Public, each once, in one table with your own tests under Yours. Each is named after the public requirement document it follows, with the document's version, holds IFC Checker's own rules, not the publisher's IDS, and shows its market (LV, LT, EE or INT) and who issued the requirements.
- IFC Checker sample checks: IFC's standard property sets and attributes, to see how a check works, as on the sample model.
- COBie: the COBie data an IDS can check in a model, in two stages, Design and Construction handover.
- Predefined tests after other public requirement documents, each in the stages its document defines.
Stages
Some predefined tests come as one file for each project stage. Choosing the test's row opens a line that starts with Stage:, with a short code for each stage, and the first stage is picked. A later stage includes every earlier one, so pick the stage your project is in now. Point at a code to read the stage's name. A test made for several countries is one row, with all its market codes: LV for Latvia, LT for Lithuania, EE for Estonia, and INT for international tests.
Your own IDS
If your client gave you an IDS file, drop it on Check with the model: it is listed under Yours. An IDS that fails IFC Checker's IDS checks is not added, and the notice says why (why an IDS is refused).