The components require the placement classification (see Section 5.12.10, “ Classify standard parts for placement dialog ”)
The components must be classified according to "IFC". See also Section 5.12.16, “ Automatic Class Mapping: Edit... ”
Catalog parts that are going to be used in architectural CAD systems require specific classifications. Via classifications meta-information as well as “relationship-knowledge” will be hosted and transferred to the target systems. Following BIM / AEC classifications do exist today:
| Classification | Author | Purpose |
| ARCHICAD | CADENAS | Placement / geometrical functionalities in ARCHICAD |
| IFC4 | buildingSMART e.V. | Interoperability in the BIM Branch at project- / building level |
| Revit | CADENAS |
Placement / geometrical functionalities in Revit See also the example below. |
| OmniClass 2006 | CSI | Focus: Definition „what“ an object in Revit represents (detailed definition) |
| OmniClass | CSI | |
| PDT | CIBSE | Attribution on international level, independent from target system (Excel) |
| UNICLASS | RIBA / NBS | Classification, „what“ product exact it is -> especially UK relevant |
| COBie | buildingSMART e.V. | Construction Operations Building information exchange - Purpose: Bridge between CAD / BIM and facility management |
![[Note]](https://webapi.partcommunity.com/service/help/latest/pages/cn/ecatalogsolutions/doc/images/note.png) | Note |
|---|---|
As high level „BIM catalogs“ of course should support as many classifications (=target systems) as possible the question often is, if they could be mapped / cross-referenced to each other. | |