How to use the BIM Material Exchange
Define the exchange purpose, authoring and receiving applications and versions, IFC schema, units, classification system and the material information actually required by the recipient.
A direct visit starts blank; launching from an accessible Project can seed its current board materials. Load example always remains separate from live project information.
- Open the tool from a Project to seed its current board materials, or open it directly for a blank standalone exchange; Load example is demonstration data only.
- Complete Project and Exchange references, requirement, applications, IFC schema, units and classification-system edition.
- For every material, verify name, category, manufacturer, product code, classification, specification, texture recipe, scale, performance, environmental and source-system references.
- Export IFC, test the file in the named receiving application, then add validation-log entries and set the overall status to Not tested, Issues recorded or Accepted for stated exchange.
Worked examples
These examples explain the set-up, expected output and review needed without changing the tool workspace.
Project-board material handover
- Set-up
- Launch from a Project whose signed boards contain selected finishes; accepted board items seed as Accepted for exchange and other current items seed For review.
- Result
- The register starts with traceable project selections instead of duplicate manual entry.
- Review
- Complete missing classification, product and performance data and confirm that board approval addresses selection, not IFC behavior.
Receiving-application exception
- Set-up
- Export the stated IFC schema, import it into the target application and record that a classification or texture reference did not survive.
- Result
- The validation log identifies the file, application version, tester, checks and remedial issue.
- Review
- Re-export and repeat the same check before marking the exchange Accepted for stated exchange.
Suggested workflow
Place the tool in a controlled project or practice process rather than treating its output as an isolated verdict.
- Agree a specific exchange requirement and minimum material property set with the recipient.
- Prepare and review the material register from current project sources before export.
- Validate in the exact receiving application and retain exceptions, corrections and the accepted file reference.
Check before saving or issuing
- Application versions, schema, units and classification edition are explicit.
- Every material can be traced to a project selection, specification, texture recipe or source-system identifier.
- Overall validation status agrees with the individual validation-log results.
Common problems
- Project materials do not appear: launch from the Project tools card while logged into a user with access to that project.
- Properties disappear after import: record the receiving version and mapping exception, correct the export or recipient configuration, and retest.
- A visually similar native material is assumed equivalent: compare identifiers, physical scale and required properties, not appearance alone.
Output
A material information register and receiving-application validation log.
Professional boundary
Exchange behavior varies by application, version and import settings; validate every delivered file in the actual project environment.