Model Description Document
Each discipline has to maintain a model description document. The document is a description of the contents of the model and it explains the purpose for which the model has been published and what the degree of precision is. The description document contains information about the modeling software used, the different versions created from the original model, and exceptions to these requirements. In addition, all used naming conventions, the maturity of the content and any restrictions on its use are documented in the description.
The description document is published in parallel with the BIM model, and it has to be updated whenever any changes that affect the content of the description occur in the model.
- The description will be updated each time the model is published to other parties, no matter if it is a working model or a BIM for serving the cost evaluation.
- The document describes the overall structure of the model and the naming conventions of systems and building components.
- The maturity of the model(s) and the most important changes must be documented so that different parties can find them.
- In the official publication points, each party is responsible for the consequences of incomplete or inaccurate documents to the extent defined in the contracts and general terms.
- In the case of working models the descriptions can include more flexible notations that explain the contents and changes in the BIM.
- The description document should be named and revised so that can be associated with the appropriate BIM.
Setting up data drops
Generally, data drops are aligned to project stages, and the information required reflects the level of development that the project should have reached by that stage. This might be considered analogous a stage report on a conventional project.
The nature of data drops should be set out in the Project BIM Brief. The Employer’s Requirements may be considered to sit alongside the project brief. Whilst the project brief defines the nature of the built asset that the employer wishes to procure and to ensure that the design is developed in accordance with their needs and that they are able to operate the completed development effectively and efficiently.
Data drops are likely to include:
- Models (Industry Foundation Classes (IFC) models and native project information models).
- Data structures (such as XML or GBXML files and schedules).
- Reports (typically PDF’s, although native files can be more useable).
The ability to own, reuse, and properly manage building data throughout the facility lifecycle accrues significant advantages for the client. Consequently, the accurate creation, management and stewardship of building information during project creation are critical. Data created during planning and refined during the project execution process can provide a valuable resource for Facility Management (FM.) Final BIM Deliverables require as-built BIM Model(s) be submitted at the end of construction for this purpose.