Like any other technology, IFC is not infallible and faces challenges in its implementation. Studies have shown the following limitations.

  • There can be a Loss of Information during conversion from proprietary software. [36, 37, 38,  39].

  • IFC Schema lacks attributes for describing dynamic data, such as if a door is closed or open which hinders the possibility of Internet of Things (IoT) interaction [40].

  • IFC implementation by software manufacturers is geared towards an expert class of users [21].

  • There is a lack of connectivity detail between MEP components [41].

  • Researchers have also identified the myth in the industry that any IFC-compliant model, exported by any IFC-Certified software could be directly used within any other IFC-based tool. This is due to designers following their own unofficial rules when modelling, and different software implementing IFC in different ways and not producing the same exported product in all cases [42].

The journey of Interoperability achieved through IFC is represented by Fig 3.

Fig 3: A Journey of Interoperability by IFC