Chapter 1 recap
Modelling for the information need
The key takeaways from this chapter’s 2 lessons.
Modelling to the information need
- The level of information need says what each element must carry at each milestone: geometry, data and documents, for a stated purpose.
- More geometry isn't better. A door at stage 3 needs its size, position, fire rating and type, not its hinges.
- The few properties others filter by (classification, level, fire rating, zone) matter more than any amount of detail.
- Ask for the LOIN table before you start modelling a stage, and push back on rows with no purpose.
IFC exports other people can use
- Export settings decide the IFC class, the property sets and the storeys of every element; defaults are rarely right for a project.
- Elements exported as IfcBuildingElementProxy are invisible to most checks and take-offs.
- Agreed properties belong in standard sets (Pset_DoorCommon.FireRating) or in the project's named set, not wherever the exporter puts them.
- Save the export settings with the project and use the same ones every time.