# Building Information Modelling Facility Management (BIM-FM)
## 7 Theoretical Requirements for BIM-FM  
### Theoretical Information Requirements  
Early work in BIM-FM looked at the recording of asset data at the time of model creation, with little regard to any future works that would/could be undertaken [44]. Hence, beyond a geometric model, there was limited consensus for BIM-FM information requirements. Furthermore, very few works suggested information requirements for a management-focused BIM [73] and those that have tended to focus on either high-levelrequirements [64], a very specific use case (e.g., [PERSON] and [PERSON] [44] who utilised heritage markers to indicate areas identified in the statement of significance for a Grade II listed building) or a small subset of requirements (e.g., [PERSON] and [PERSON] [74] who identified information requirements specifically for Heating, Ventilation and Air Conditioning (HVAC) systems). This is likely because specific use cases often have multiple data inputs, meaning comprehensive identification of information requirements at all scales is unfeasible. For instance, [PERSON] et al. [79], who focused only on occupant feedback, generated eight information inputs for a single event. Therefore, to realistically define information requirements for a standard approach to BIM-FM, there is a need to generalise information into discrete sets of data. For instance, using [PERSON] et al. [79] as an example, the information requirement would be defined as 'occupant feedback'. This requirement would then consist of additional data inputs, which could be defined on a case-specific base (in their case eight inputs) encompassed within the overarching 'occupant feedback' requirements. This is comparable to the concept of Organisational Information Requirements (OIR) defined by ISO 19650, which refers to information required by an organisation to achieve organisational functions or goals [19]. Generalising data sets also enables the implementation of access controls to data, allowing control of which user gets access to what information, e.g., for security reasons and for uncluttering the user experience [52]. Only a few works, within the literature reviewed, attempted to identify comprehensive high-level information requirements for FM [53; 81], the most detailed of which is found in the work by [PERSON] et al. [53], who identified eight high-level domains of information and thirty-eight sub-domains. [PERSON] et al. [81] developed a list of forty-one information requirements by reviewing the literature and standards and validating them with interviews of FM professionals. They were not referring to existing buildings, but their work was, regardless, a comprehensive identification of FM information requirements. The limitation of their work is that the intention was to transfer the information to an FM system at a later date, thus rendering the BIM model obsolete. [PERSON] et al. [54] carried out client interviews to generate a list of information requirements, but only managed to identify a total of five requirements with unclear justification. A recurrent theme for identified information requirements is maintenance and condition-related information. [PERSON] et al. [40] created an asset management tool for ports, which combined a BIM model with a maintenance severity and urgency scale in Excel to visualise and plan maintenance needs. The authors were able to create a bi-directional link between the excel sheet and BIM using Dynamo. The key benefits of the BIM were the visual filtering capabilities of Revit. [PERSON] et al. and [PERSON] et al. [16; 22] also included condition assessments in their work, citing similar applications regarding planning proactive maintenance. Similarly, [PERSON] et al. and [PERSON] et al. [82; 18] suggest that location data are key to analysing maintenance data and thus enabling efficient planning of future work. However, [PERSON] et al.