Manufacturer BIM product data is useful when reference codes, dimensions, units, materials and technical documents agree. This checklist helps international catalogue teams connect model and page information to a common source. Track missing values with an owner and evidence instead of guessing.
Build one product record before the model
Choose a stable reference code and maintain a small record around it. Product names may change between markets, but the file, technical document and catalogue page need a reliable way to identify the same product. Separate verified values from unanswered questions. A blank thermal or acoustic value should trigger a question to the technical owner, not a plausible-looking number entered by the modeller.
| Information | Recommended check | Owner to identify |
|---|---|---|
| Identity | Reference, manufacturer, model and market | Product manager |
| Dimensions | Value, unit and what is measured | Technical team |
| Materials | Product-specific description and finish options | Product team |
| Performance | Supporting document and applicable variant | Technical owner |
| Revision | Date, change note and replaced file | Catalogue editor |
Define the meaning of each field
“Width” could mean the overall frame, clear opening or installation opening. For a window with a nominal width of 1,200 mm, specify which measurement that number describes. Likewise, distinguish a product's weight from the shipping package weight. A shared name without a shared definition causes inconsistent schedules even when every field has a value.
Create a short field dictionary: name, meaning, data type, unit, allowed absence and source. Keep reference codes as text. Define whether a value belongs to the product type or an individual placed instance before mapping it into the authoring model.
Use requirements as an acceptance list
buildingSMART's Information Delivery Specification, IDS, is a computer-interpretable way of expressing information requirements for model exchange, including properties, values and units. It can inform a structured handoff when a project requests it. Agree the requirements and checking tool with that project. This guide does not imply that BIMNESNE automatically runs an IDS validator.
A small release example
For a ventilation product, prepare a reference, two language names, dimensions and a current technical document. Have the technical owner confirm which operating condition any performance value describes. Then compare the catalogue description, file parameters and document. If a revised document changes a value, update the affected records together and preserve a change note. Do not silently publish an old model with a new document title.
- Check one representative type and one variant.
- Compare the identifier across page, model and document.
- Measure one known dimension in the test file.
- Check the required report fields and units.
- Resolve missing evidence before approving the release.
Use the manufacturer publication guide for BIMNESNE's actual draft/import workflow and the format guide for delivery choices. Create a company when your team is ready to prepare its catalogue.
Keep technical information consistent in TR/EN
Do not translate product or model codes. Preserve numerical values and units in both languages, and identify market-specific performance or availability differences. Complete dimensions, materials, descriptions and files in the BIMNESNE product editor. CSV import creates drafts from references, names and categories; it does not automatically populate technical fields or model files.
Sources and editorial note
buildingSMART: IDS and Autodesk: shared project parameters. The field dictionary and release example are BIMNESNE editorial recommendations, not a universal mandatory product data standard. The cover is conceptual artwork.