Architectural Flashing Supply
Start a Quote
BIM objects, metadata and model coordination · Lesson 4 of 4

BIM objects, metadata and model coordination: defects, verification and case study

Seven recurring model-data defects with the evidence for each, a receiving checklist, a constructed case study of a 186 ft coping run that arrives as an IFC, and the situations in which to stop and ask.

You will be able to: Diagnose seven plausible model-data defects, state the evidence that proves each one and the correction, and apply the checks to a constructed case study.

11 min · 11 slides · 7 questions

All lessons in this module
Slide 1 of 11

Seven model-data defects

Seven defects recur in model data: a wrong IFC class, a property at the wrong level, a unit mismatch, an LOD claim above what is delivered, flashing that is not modeled, a status or revision misused, and a dimension given to the wrong element.

Each has checkable evidence and a correction. Unmodeled flashing is on the claimed-level slide; a dimension on the wrong element is lesson 3, step four.

Sources

Glossary

Proxy
In an IFC, a generic building element; AFS's reader lists a proxy only when it is named like flashing, coping or parapet.
IFCExportAs
A shared parameter that, with IFCExportType, sets the IFC class a Revit family type exports to, according to Autodesk's Revit LT 2022 help.
Revision Compare
An AFS tool that reports what changed between two DXF revisions of a drawing: geometry, dimensions and notes.
Not specified
How AFS records a material, gauge, finish or color the drawing does not state, instead of guessing.
Constructed case study
A teaching scenario built from AFS's own teaching files rather than from a real project.