From 37b14f2a3d918734001b3b0c295201a819fe368b Mon Sep 17 00:00:00 2001 From: Dion Moult Date: Mon, 27 May 2024 11:59:25 +1000 Subject: [PATCH] Document difference between COBie 2.4 and COBie 2.4 Legacy in IfcFM --- src/ifcopenshell-python/docs/ifcfm.rst | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/src/ifcopenshell-python/docs/ifcfm.rst b/src/ifcopenshell-python/docs/ifcfm.rst index f096ed69e9..25724de177 100644 --- a/src/ifcopenshell-python/docs/ifcfm.rst +++ b/src/ifcopenshell-python/docs/ifcfm.rst @@ -63,3 +63,21 @@ with this data structure that IfcFM supports: installation. As expected, the majority of these are already referenced in named standards. "Vanilla" IFC offers a "specification agnostic" approach towards facility management data collection. + +COBie 2.4 vs COBie 2.4 Legacy +----------------------------- + +In collaboration with leading UK consultancy BuildData Group (formerly Bond +Bryan Digital), and inventor of COBie 2.4 Bill East (Prarie Sky Consulting), an +effort was made to preserve the original IFC mapping, as well as modernise the +mapping with the following goals: + +1. For anyone delivering **COBie 2.4** data using best practices from graphical + BIM software, there must be *no difference* between **COBie 2.4** and + **COBie 2.4 Legacy**. It must not contradict any specifications in the + official NBIMS-US and BS standards. +2. Update compatibility to IFC4X3. +3. Prioritise organisational data instead of personal data with discourage PII. +4. Prioritise bSI standardised property sets over custom ones. +5. Prevent needless repetition of data / fallback defaults that may result in + invalid or unexpected data in obscure edge cases.