OpenBuildings Designer’s Floor Manager is used for two primary purposes.
When IFC_WORKSET is set appropriately, it also contains properties that populate the IFC hierarchy for project, site, building and building storey using ifcProject, ifcSite, ifcBuilding, ifcBuildingStorey, illustrated by the following screenshots, properties added from IFC Psets are outlined. Values can be added/edited for as many or as few properties as required .
Note that Project Name and Project Description can be different:
Note that Site Name and Site Description can be different:
Note that Building Name and Building Description can be different:
Note that Building Name and Building Description can be different. Additionally Gross and Net floor areas (1) can be entered here for output to IFC GrossAreaPlanned and NetAreaPlanned respectively (2).
The Floor Parameters, length and width (3) can be ignored, they refer only to the dimensions of the reference plane elements used by Floor Management tools.
OpenBuildings Designer uses a federated file approach to modelling often linking multiple files together; we therefore allow users to associate file contents with specific storey assignments at the time of export using the spatial assignment dialog
This can be seen in viewers such as Solibri as it is present on an element:
Looking at the IFC file via a text viewer, the project name and project description are present
Phase for ifcProject, is not present. According to the buildingSMART website this is an optional field and not mandatory for compliance so has not been included in current versions.
The results of exporting these properties may be presented differently by IFC viewers according to the differing ways that they may have chosen. For example:
In BIM Vision you can see the hierarchy of information clearly.
Solibri shows a similar tree, but the project name and description need to be drilled down to:
This is more clearly visible in FZK: