Information model requirements should be defined before design begins. They establish what information the team produces, how it is checked and what is handed over. Statutory requirements and the contractual brief are considered together while retaining their different roles.
01Regulatory basis
Russian Government Resolution No. 614 of 17 May 2024 sets out rules for creating and maintaining an information model. Whether modelling is mandatory is assessed separately against current applicable acts and project characteristics.
Software names or a general level-of-detail label cannot define the complete model scope. Requirements need to become a specific information, document and validation schedule.
02Client information requirements
The client defines model uses and information recipients. Coordination, equipment procurement and operation require different properties and checks.
The brief records modelled objects, mandatory parameters, classification, units, formats and staged deliveries. Exceptions and limitations should also be stated.
03Information management
A common data environment should make document status and revision history clear. The team agrees review, approval and issue procedures. Model exchanges require checks of coordinates, revisions and data completeness.
IFC is an open exchange standard. An IFC file alone does not demonstrate compliance with the brief; its contents must be validated.
04Model acceptance criteria
- Agreed file and discipline register.
- Required element geometry and properties.
- Consistency with the issued documentation.
- Resolution of significant coordination issues.
- Usable agreed exchange formats.
- Handover, storage and updating procedures.
Agree acceptance criteria before modelling so the final review can be applied consistently.
Sources: Russian Government Resolution No. 614 · IFC standard — buildingSMART
Discuss your project
Share the building use, area and current project stage. We will define the design, procurement and delivery scope.
Contact the practice →