The schema IfcMaterialResource contains the types and entities that are used to define materials (substances, of which products are made of). Materials are defined generically.
NOTE The references to the usage of materials is made from the relevant elements through the objectified relationship IfcRelAssociatesMaterial.
Material definitions are distinguished by how they apply to elements or element types and by their components (layers, profiles, parts).
Material designation can be made for standard element occurrences to support a limited range of their parametric representation using
NOTE Often specific subtypes of building elements are used to have such parametric representations associated, they use the common suffix 'StandardCase', for example IfcWallStandardCase, or IfcBeamStandardCase.
Material designation can be made for element occurrences or element types without applying a parametric meaning using
These options are exposed for association with IfcElement or IfcElementType and their subtypes through a select type IfcMaterialSelect. The association is realized by the objectified relationship IfcRelAssociatesMaterial, accessible by the inverse relationship AssociatedTo. Some associations to specific material entities may be restricted as not being appropriate within the specialized element or element type definitions.
The following material properties and information sets can be assigned to an IfcMaterialDefinition, or only to a single IfcMaterial.
HISTORY New schema in IFC1.0
IFC4 CHANGE Definition of material properties and their assignment to IfcMaterial or other appropriate options in IfcMaterialSelect is now fully captured by IfcExtendedMaterialProperties using the general IfcProperty approach. Specific predefined subtypes of IfcMaterialProperties are no longer available.
DEPRECATION Material designation by using IfcMaterialList is deprecated and should not be used. The classification of materials should not be done using IfcMaterialClassificationRelationship anymore (entity type deprecated); the IfcExternalReferenceRelationship in IfcExternalReferenceResource schema should be used instead.