{"id":4391,"date":"2024-02-03T05:19:43","date_gmt":"2024-02-03T04:19:43","guid":{"rendered":"https:\/\/openbim-knowledgebase.org\/docs\/chapter-3-in-depth-knowledge\/"},"modified":"2025-03-15T14:11:47","modified_gmt":"2025-03-15T13:11:47","slug":"chapter-3-in-depth-knowledge","status":"publish","type":"docs","link":"https:\/\/openbim-knowledgebase.org\/en\/docs\/bimcert-manual-2024\/chapter-3-in-depth-knowledge\/","title":{"rendered":"Chapter 3 – In-depth knowledge"},"content":{"rendered":"\n
\n

This chapter provides an in-depth insight into various openBIM standards<\/em> developed by buildingSMART. These new openBIM terms<\/em>– especially the abbreviations – are a major challenge, especially for newcomers. A sound understanding of these terms is essential for extensive use of openBIM <\/em>. The contents of this chapter provide the foundation for the descriptions of openBIM project implementation<\/em> in chapter 4<\/a>. <\/p>\n\n\n\n

Fig. 3.1 and Fig. 3.2 put the terms into context. In contrast to the overview illustration in Chapter 4<\/a>, the entire openBIM process<\/em> within a project is not shown, but only from the perspective of model creation. For more detailed information, please refer to the individual sections. <\/p>\n\n\n\n

The specialist planning office receives the model requirement (including LOIN, section 3.6<\/a>) via the BIM execution plan <\/em>(BAP) and begins to implement it in its native software. Before starting with the actual specialist model creation, the first step <\/em>is to create the new classifications (if permitted by the software guideline) and the necessary features in the software. In the second step <\/em>, these are mapped (for the IFC export) with the IFC data schema or MVD(Section 3.2<\/a> and Section 3.3<\/a>). The specialist model creation then starts in accordance with the modeling guidelines(section 3.1.3<\/a>). The office transfers the models using IFC and communicates via BCF(Section 3.4<\/a>). The entire exchange of information takes place via a Common Data Environment <\/em>(Section 3.5<\/a>). The described mapping must be carried out manually by each project participant in the respective native software; this is not very efficient and is prone to errors. <\/p>\n\n\n