Step 3: Structuring the Model Components

Also, under the "Templates" menu item is the section Model Components with its individual subsections, such as discipline models, geometry requirements (Level of Geometry), model elements and properties. These contain the templates of the requirements definitions used later in the area Project Requirements.

The described sub-areas are predefined in each new project of BIMQ and provide a meaningful order structure. The Model Components can basically be understood as a kind of library. Here, all data requirements are defined once and provided with additional specifications, such as the mapping in IFC, which are then also used several times in the Project Requirements. This assignment to a project-specific requirements structure (breakdown structure), responsible planning disciplines, project phases and use cases takes place in a later work step (Step 6). For this reason, the specified breakdown structure is structured according to the following example:


image.png

Predefined structuring in the area Model Components separated by the type definitions: Model, Object, Geometry, Property, Value and Group as an order element.

In addition to creating the templates themselves, they must also be linked to the selected authoring software and IFC version, also known as "Mapping" (Step 4). These specifications are important for the exports of Software Templates and Checking Rules presented in Step 9. With every BIMQ license we deliver a basic content of already extensively processed templates, the so-called basic catalogs. This means that these templates only need to be created for the additional data requirements necessary for your own project guidelines.

Five different type definitions are available as templates to specify the LOIN defaults: Model, Object, Geometry, Property and Value, and additionally Group to structure these types. With which content the Model Components section is enriched, respectively how detailed the hierarchical structure is, can be decided by each user according to his needs. However, it is recommended to keep the main components like Discipline Models, Model Elements, Geometry and Properties in separate hierarchy levels and to subdivide them there.  

Templates can be shared between the different project guidelines of an organization. For this purpose, templates can be captured centrally and transferred to other projects or exchanged directly between two projects. This facilitates the establishment of consistent project requirements.


image.png

Exemplary transfer of predefined content from the publicly available IFC catalog into the own project

The later assignment of different property sets, properties or geometries to a specific element is done in "Step 6: Assign Discipline Models". 

Further information about: Model Components can be found at the section Templates.

<< Step 2 | Step 4 >>