Before choosing a BIM object, check its product reference, file format, software version and dimensions against the technical document. An attractive preview does not demonstrate that the file will work in your project. This checklist helps architects and engineers assess manufacturer objects before adding them to a model.
Define the task before downloading
Write down whether the object supports early layout, construction detailing, quantities or coordination. A door used in a concept model may only need approximate dimensions. A construction model may also require the frame opening, handing and a matching technical document. Appearance in the model alone does not establish compliance with a project specification.
| Check | Evidence to request | Action |
|---|---|---|
| Product identity | Manufacturer, model and reference code | Match the technical document |
| Application and version | File format and target software | Open in the project version |
| Dimensions and units | Width, depth and height with units | Compare a known dimension |
| Information scope | Required parameters and documents | Resolve gaps with the product owner |
Run a small acceptance test
- Open a copy in a separate test project. Keep the first experiment away from the production model.
- Inspect plan, section and three-dimensional views. Check origin, orientation and the clearances needed for the intended task.
- Try the smallest and largest product types. For a door expected to be 900 mm wide, measure it rather than accepting an ambiguous value or a 900 cm result.
- Display the product code and type name in a schedule. Check whether the same code accidentally identifies different products.
- Compare important technical values with the current manufacturer document. Do not fill missing fields with guesses.
This is a proposed project acceptance process. Passing in one test file does not guarantee the same behaviour in another version or template. Record the application version and test date so colleagues can reproduce the decision.
Choose the format for the handoff
A native application file and an open exchange file can serve different purposes. IFC is an open data schema defined by buildingSMART; an extension alone does not explain which information will transfer. Agree the expected content, receiving application and exchange requirements together. Read the Revit family and IFC selection guide for a practical comparison.
Keep source and revision traceable
Save the source URL, reference code and document revision with the acceptance record. For a product used in Turkey, confirm local supply and project requirements with the manufacturer. A parameter being written in Turkish does not mean every participant interprets it identically. Your project dictionary should identify its unit and data type. Where a question remains, record a conditional acceptance and name the person responsible for resolving it.
Explore objects in the BIMNESNE catalogue and follow the placement QA checklist. If you publish products, start with the manufacturer preparation guide.
What should you check on BIMNESNE?
Review the product description and the files actually supplied. File formats and detail levels can differ between products. Company approval is part of the publication process; it is not a technical certificate of suitability for every project. Resolve missing technical evidence with the manufacturer.
Sources and editorial note
buildingSMART: IFC and Autodesk: Revit families explain the underlying concepts. The checklist is BIMNESNE editorial guidance. The cover is a conceptual illustration, not a technical drawing of a specific product.