A requirement checked against the model's current revision
Specifications written in the open IDS standard, checked item by item against the model and the sheets. Each requirement gets a scoreboard, and an open mandatory target holds the stage back until somebody decides, on the record, to go ahead anyway.
Every beam declares fck and exposure class
28 beams · rev. C
Every element carries an identification code
8 with no code · mandatory target
Minimum cover stated per element
16 with no value · NBR 6118
The rule is a sentence an engineer writes and a client understands
IDS is an open standard: the same specification serves the consultant and the client.
“Every concrete beam must declare fck, cover and environmental exposure class.”
- applies to
- IfcBeam · concrete material
- requires
- fck · cover · exposure class
- checks
- the model's current revision
Why checking early changes the project
- 01
The problem shows up small
Eight elements with no code today is half an hour of work. Found during coordination, they become a week of rework.
- 02
A scoreboard per requirement
Each requirement shows how many elements pass. The conversation stops being about who got it wrong.
- 03
The divergence names the element
The list gives the element and the model it sits in, and it exports as BCF for the coordination software.
- 04
An exception is recorded
Going ahead with an open requirement is allowed, with author and reason saved. That is governance, not a blind block.
Run your own requirements against your current model
Tell us which rules your office enforces today. We reply by e-mail.
Request access