Check a model against the EIR and raise issues
Open the information requirements, check a delivered model against them for naming, classification, level of detail and required properties, raise a BCF issue on every gap and sign off only what passes.
How it works, step by step
4 steps across the platform - what you do at each one, and why it matters.
Open the requirements
EIR MatrixOpen the information requirements the model is meant to satisfy - the naming convention, classification, level of information need and the properties each element must carry.
Why: You cannot check a model against a standard you have not opened. Starting from the actual requirements turns a vague review into a definite pass or fail on each point.
Check the model against them
Model ReviewWork through the model checking naming, classification codes, level of detail and the required properties on each element type against the requirement.
Why: A missing classification or an empty property field breaks the takeoff and the asset handover downstream. Catching it at delivery is far cheaper than finding it when it is needed.
Raise an issue per gap
Model IssuesRaise a BCF issue for every gap against a requirement, pointing at the element and naming what is missing, so the author has a precise list to fix.
Why: A precise issue gets fixed; a vague complaint that the model is not compliant gets argued. Tying each issue to a requirement and an element removes the room for debate.
Sign off what passes
EIR MatrixSign off a requirement only once the model actually meets it, so the matrix records true acceptance rather than a hopeful tick.
Why: Sign-off is the gate that protects everyone downstream. Holding it until the model really complies is what stops a data gap being inherited by the estimator and the operator.