FBO → IFC mapping

How to read this table

FBO deliberately does not bake IFC into the ontology: the same fire-safety concept can be modelled in different ways depending on the design stage, the country and the authoring software (a fire compartment can be a list of spaces in an IfcZone early on and a 3D IfcSpatialZone later). This mapping is the official FireBIM recommendation for placing that information in an IFC model so that the FireBIM platform can read it. Each row is one mapping individual in fbo-ifc:

• FBO term – the core (fbo:) and/or national term(s) the row represents; click to open the term in the ontology viewer.
• Kind – whether the concept is an IFC Object (an element or spatial element), a Property in a property set, a Quantity in a quantity set, or a Relationship.
• IFC class · predefined type – the IFC 4.3 entity (with .PREDEFINEDTYPE where relevant) to use. Several alternatives are listed when more than one is acceptable.
• Property set . Property – where to put the value. CPset_FireBIM.* sets are FireBIM custom property sets to be added as user-defined Psets.
• Data type / value – the expected IFC data type, and, for classifications, the expected value.
• bSI – a check means the row uses a buildingSMART standard property or quantity set that most exporters fill automatically; otherwise it is a FireBIM convention.
• Notes – interpretation results and argumentation from the ontology working group, including open questions.