Standards & evidence
What checks establish, what they do not, and how to read the record.
2 min read · 3 sections
What ZEROBiE says about ISO 19650
ZEROBiE is designed to support information management in accordance with BS EN ISO 19650-2. Conformity is achieved by the appointing and appointed parties through their own processes.
No software can hold that conformity on a project's behalf, so ZEROBiE makes no statement that it, or any model checked in it, satisfies ISO 19650 or any other standard. What it provides is described feature by feature in this guide: a common data environment with an ISO 19650-shaped state workflow (WIP, Shared, Published, Archived), an audit journal, and model checks.
What a validation result means
IFC Validation checks a model against buildingSMART's published IFC rules. A result is a statement about the file: whether it is well-formed IFC. It says nothing about whether an appointment's information requirements were met.
The result is reported in four layers, each on its own: STEP Syntax, IFC Schema, Normative Rules and Industry Practices. The layers are never averaged into one verdict, because a file that does not parse is a different problem from one that parses and breaks a schema rule.
Every result is shown with the date it was checked, and its ruleset version is on the same page, in the Run details section under the result, and in every export. Read a result with both: a result whose ruleset or date is unknown cannot be compared with a later one.
IFC versions and open standards
ZEROBiE is IFC-native. It reads IFC2X3, IFC4 and IFC4X3 files. Models are converted once on the server, so there is nothing to install and nothing to deploy. Requirements are exchanged as IDS and issues as BCF, both open buildingSMART formats, so your information is not locked to ZEROBiE.