Automation in Construction 118 (2020) 103275

Contents lists available at ScienceDirect

Automation in Construction
journal homepage: www.elsevier.com/locate/autcon

Building performance and maintenance information model based on IFC T

schema
Rossella Marmoa, , Francesco Polverinoa, Maurizio Nicolellaa, Andrej Tibautb
⁎

a
Department of Civil, Architectural and Environmental Engineering of the University of Naples Federico II, 80125 Naples, Italy
b
Faculty of Civil Engineering, Transportation Engineering and Architecture of the University of Maribor, 2000 Maribor, Slovenia

ARTICLE INFO ABSTRACT

Keywords: The integration of operational information in building life-cycle management is a relevant topic within the
Building Information Modelling (BIM) facilities management domain. A previous study proposed a methodology based on Building Information
Building Performance Assessment (BPA) Modelling (BIM) and Facility Management (FM) systems integration, underpinned by a Performance Information
Facility Management (FM) Model, to support the performance assessment and the maintenance management. The purpose of this paper is to
Operation and Maintenance (O&M)
extend and validate that methodology with an open standard approach. A subset of the Industry Foundation
Industry Foundation Classes (IFC)
Model View Definition (MVD)
Classes (IFC) schema related to performance assessment and maintenance procedures is mapped into a relational
Visual Programming Language (VPL) database. The database supports the integration between BIM models and facilities information systems. Case
Entity-Relationship model (ER model) studies including healthcare buildings test the database and a new application. The results contribute to the BIM
Healthcare facilities adoption in the FM domain. Also, the studied and validated IFC schema subset can be considered as a con-
Operation theatre tribution to the Model View Definition for FM.

1. Introduction
Facility Management (FM) has to do with a set of non-core business
services (for buildings, spaces and people), which support the quality of
people's life and the productivity of the core business of an organisation
[1,2]. FM embraces a wide range of functions (or competencies), from
the organisation's management to the employees' support services, in-
cluding Operation and Maintenance (O&M) [3–5]. Throughout the life
cycle of a building, the largest fraction of expenses is incurred during O
&M activities, which consist of approximately 60% of the total cost [6].
The Operation and Maintenance competency is meant to let the facility
and its systems function efficiently, reliably, safely, securely in a
manner consistent with existing regulations and standards [3].
Knowledge about the asset has a real value, as the delivery of a
service is also the delivery of information. In managing a facility it is
relevant to know about the spaces to be serviced, the services to be
performed and their actual performance [7]. Decisions of asset man-
agers are becoming more complicated, due to the increasingly wide
range of criteria to be considered (i.e. sustainability, safety, comfort,
etc.). A deep knowledge of the asset condition is needed [8], although
this is not always easy to obtain. Typically, asset managers must make
decisions about maintenance and renewal alternatives based on sparse
data about the current state of their assets [9].
Information Communication Technologies (ICT) are providing the
tools and the systems for facilities information management, such as
Computer Aided Facility Management (CAFM) and Computerized
Maintenance Management System (CMMS) [10].
Among ICT tools also Building Information Modelling (BIM) may be
considered. It comprises the “use of a shared digital representation of a
built asset to facilitate the design, construction and operation processes to
form a reliable basis for decisions” [11]. BIM can play a key role as a
mutual channel for information exchange among operators during the
various phases of the life cycle of a building [12]. The model provides a
realistic and enriched representation of the asset, enjoying real ad-
vantages of parametric and object-oriented approach, that lead the
model to become a digital twin of the building. However BIM itself
cannot solve the general problem of information communication and
exchange [13].
In a previous study, the authors proposed a methodology, under-
pinned by a Performance Information Model (PIM), to support orga-
nisational, environmental and technical requirements fulfilling. Pilot
application regarded healthcare buildings, where several specific re-
quirements can be translated into environmental performances to be
quantified through Key Performance Indicators (KPIs) [14].
Healthcare is complex, and technologically advanced facilities due
to the large number of subsystems and the diversity of requirements are
involved. Building Information Modelling has been used to support
requirements management, by storing semantic information and

⁎
Corresponding author.
E-mail address: rossella.marmo@unina.it (R. Marmo).

https://doi.org/10.1016/j.autcon.2020.103275
Received 12 February 2020; Received in revised form 15 May 2020; Accepted 19 May 2020
Available online 06 June 2020
0926-5805/ © 2020 Elsevier B.V. All rights reserved.
R. Marmo, et al.
enabling automated rule checking of healthcare design solutions [15].
It has been claimed that healthcare's operational phase is supported by
a set of KPIs which provide an effective building performance mea-
surement [16–18]. Three categories of KPIs have been identified [16]
and proved to allow facilities performances assessment, benchmarking
activities, analysis of maintenance work priorities [17]. Furthermore,
an enterprise resource planning (ERP) system based on those KPIs de-
monstrated not only enhanced performances but also a decrease in
annual maintenance expenditure [18]. KPIs showed to retrieve the
performance of each individual system and component and analyse the
root cause of any problem with accuracy.
The performance-based approach previously proposed by Marmo
et al. [14] has been extended in this paper to an open standard per-
spective. This paper aims at integrating FM system and BIM technology
in order to support maintenance management and building perfor-
mance assessment (BPA). To achieve this goal the following specific
objectives are defined: (i) identifying FM information requirements
referring to the Information Delivery Manual (IDM); (ii) designing an
Industry Foundation Classes (IFC) schema compliant database to keep
track of FM information; (iii) developing a framework to enable the
information exchange between the IFC compliant database and BIM
models. In this regard, the paper addresses the following research
questions: (a) how the latest IFC schema supports BIM workflows in the
FM domain? (b) How can the BIM-FM-BPA integration process be im-
plemented?
The paper is structured as follows: Section 1 provides the literature
review regarding the need for information standardisation in the con-
struction sector and the implementation of BIM into the FM domain so
far; Section 2 describes the methodology proposed in this paper, in-
cluding the open standard database design and the BIM-FM integration
framework; Section 3 presents implementation results regarding
healthcare facilities, which are analysed in Section 4. Eventually
Section 5 provides the main conclusion of this research.
1.1. Standardisation of information for O&M
The large proliferation of ICT tools has led to a large volume of
unstructured data [19], while integration processes require some de-
gree of standardisation of information representation.
Efforts in creating standard data format have been done by
BuildingSMART [20], previously known as the International Alliance
for Interoperability (IAI) [21], which is the worldwide industry body
responsible to provide the Industry Foundation Classes (IFC) [22]. The
Industry Foundation Classes are an open international standard for BIM
data that are exchanged and shared among software applications used
by the various participants in the construction or Facility Management
industry sector. The standard includes definitions that cover data re-
quired for buildings over their life cycles [23].
The IFC data schema is structured around four layers: the resource
layer includes resource definitions (i.e. materials, costs, actors, ap-
provals, constraints etc.); the core layer contains the most general entity
definitions (control, product, process), all entities carry a globally un-
ique id; the interoperability layer includes schemas containing entity
definitions that are used across several disciplines, those definitions are
typically utilized for inter-domain exchange and sharing of construction
information; the domain layer specifies products, processes or resources
regarding a certain discipline among: building controls, plumbing, fire
protection, structural elements, structural analysis, HVAC, electrical,
architecture and construction management [24].
The IFC data model is characterised by the inheritance hierarchy
which defines relationships and attributes that can be inherited from
parent to child entities. Fig. 1 shows an extract of the IFC hierarchical
structure.
The IfcSharedFacilitiesElements schema defines basic concepts in the
facilities management (FM) domain. This schema, along with
IfcProcessExtension and IfcSharedMgmtElements, provides a set of models
2
Automation in Construction 118 (2020) 103275
that can be used by applications needing to share information con-
cerning facilities management related issues [24].
The IfcSharedFacilitiesElements schema supports ideas including:
furniture and system furniture, asset identification and inventory of
objects. The IfcSharedMgmtElements schema defines basic concepts that
are common to management throughout the various stages of the
building lifecycle, including IfcActionRequest and IfcProjectOrder.
A Model View Definition (MVD) is a subset of the overall IFC
schema to describe a data exchange for a specific use or workflow.
MVDs can be as broad as nearly the entire schema (e.g. for archiving a
project) or as specific as a couple object types and associated data (e.g.
for pricing a curtain wall system). The documentation of an MVD allows
the exchange to be repeated, providing consistency and predictability
across a variety of projects and software platforms [25].
BuildingSMART provided the Information Delivery Manual stan-
dard, a methodology to capture and specify processes and information
that have to be exchanged during the lifecycle of a facility [26]. To-
gether with Model View Definitions, they provide a methodology for
different domain experts to model specific data requirements they need.
An example of MDV is the FM Handover MVD containing in-
formation from planning and design applications to CAFM and CMMS
applications, as well as the handover of model information from con-
struction and commissioning software to CAFM and CMMS applications
[27].
The traditional formats for IFC specified files are the STEP physical
file format or ifcXML. In addition to these formats, the FM Handover
MVD has the benefit of having a mapping to another format that many
practitioners have found very useful, SpreadsheetML. The Construction
Operations Building information exchange (COBie) version of the
Facility Management handover MVD, is the MVD delivered in a file
format that can be viewed and updated in Microsoft Office Excel [28].
In this sense, The Construction Operations Building information ex-
change contains lifecycle information for maintaining facilities [27].
1.2. BIM applications for O&M
Despite the initiatives by industry in terms of standardisation and
the increasing interest in facilities information management aided by
BIM [29–31], the use of BIM during the O&M phase is still limited [32].
A seamless information process between BIM and FM systems is hard to
achieve [33], especially if the FM systems are already in place [31].
Some occurring issues regard the identification of critical informa-
tion required to inform management decisions, the effort to create or
update BIM models, including real-time operational data, and the
handling of uncertain data [34,35]. Questionnaires revealed that FM
team involvement is instrumental to the creation of complete and ac-
curate building information that can be used for life cycle management
[36].
A contribution to the identification of critical data which can fa-
cilitate the implementation of BIM into the O&M domain is the tax-
onomy proposed and implemented by Farghaly et al. [37]. Even though
the research is limited to assets consuming energy in educational
buildings, the 60-parameters taxonomy and the API plug-in can help
professionals to deliver models which properly support Asset Manage-
ment processes.
Bortoluzzi et al. [38] have recently addressed the effort of creating
and updating BIM models proposing and testing a process to auto-
matically generate BIM models from CAD plans and to populate and
update the model content.
Many researchers interested into BIM-based facility information
management [6,39,40] faced interoperability issues during data
transfer processes. For this purpose, IFC and COBie can be useful to
achieve data mapping and data integration between BIM models and
FM systems [41].
A literature review has been carried out to specifically analyse IFC
applications in the O&M domain. Papers concerning information
R. Marmo, et al.
Fig. 1. Extract of the IFC inheritance hierarchy, from IfcRoot to subtypes of IfcObject.
Table 1
IFC O&M support capabilities implemented in literature.
Example of IFC capability References
Maintenance management [12,41,45,46,48,49]
Performances assessment [12,14,41,53–55]
Sensors/alarms data tracking [12,43,47,55]
Lifecycle information management [42–44,47,54]
management in building maintenance and management were analysed.
Table 1 reports IFC capabilities, grouped into 4 clusters, according to
the 13 reviewed papers.
The overall process of developing and delivering FM-enabled BIM
models has been investigated by Pishdad-Bozorgi et al. [42]. The pre-
sented case study used Industry Foundation Classes and COBie to ex-
change information throughout the life cycle of the project. Even so, at
the handover phase challenges of importing data from BIM into existing
asset information management systems were encountered.
An attempt at extending BIM technology into the entire lifecycle of a
construction project regarded a building information system based on
the use of IFC files to collect information from various sources [43].
However, this method did not allow data updating and evolution.
IFC has been also tested as a reference for automating the discovery
of as-happened BIM processes to support BIM managers activities and to
document a detailed history of a project development (which might be
useful for the operational phase too) [44].
A framework for maintenance management was developed pro-
posing a new set of IFCs classes for maintenance information exchange
[45]. The model referred to the IFC 2.0 release. On the contrary, in the
current paper the hypothesis of using the IFC 4.2 version to cover all the
maintenance information processes is made, as discussed in the next
section.
Shalabi et al. [46] tested a framework to link IFC models to alarms
reported by FM systems, using an API that allows the user to upload any
data from the FM systems. The quality of data required for corrective
maintenance has thus been improved by utilizing visualisation and
interoperability capabilities of Building Information Modelling.
Open standards were also used to define requirements for asset
management tasks in a structured way, for validating project data
against these established requirements, and visualising asset data in an
integrated and interactive way [47].
The BIM visualisation capability was utilized to enhance failure
root-cause detection through an FM visual analytics system [48].
Available IFC entities have been identified to perform logical and
3
Automation in Construction 118 (2020) 103275
spatial analysis. Anyway, the proposed relational database can be ex-
tended to include further maintenance information and activities.
A BIM-based framework was proposed by Chen et al. [41], aimed at
automatically providing the scheduling of maintenance work orders. In
this framework, data are mapped between BIM and FM systems ac-
cording to an extended version of the IFC 4.
An FM ontology was tested by Kim et al. [49]. The ontology is de-
fined by three types of concepts: Work Information, IFC Objects, and
COBie Concepts. The system semantically links BIM data to relevant
historical work records. The approach could be improved by developing
other functions of FM systems such as preventive maintenance, per-
formance assessment etc.
Although the interoperability problem of BIM-FM integration has
been investigated by the above-mentioned studies, the BIM-aided de-
cision making for maintenance management needs to be further ex-
plored. In particular a strategic decision making is affected by main-
tenance performance information [50]. Key Performance Indicators can
be developed for all types of buildings and can be designed to address
different scales of decision making.
A methodological approach to integrate BIM, Building Performance
Assessment and Facility Management systems has been lately proposed
and tested by Marmo et al. [14]. It consists of providing a Performance
Information Model to manage relevant information in form of KPIs.
Improved environmental performance assessment, better visualisation
of building condition, and improved decision-making process are
among the practical implication found.
A BIM-based cyber-physical system for the automated monitoring of
buildings during their regular operation has been tested [12]. The di-
gital model becomes the digital twin of the building and stores its actual
performances to support facility managers in making decisions.
A parametric model supporting historical buildings refurbishment
has been proposed by Bruno et al. [51]. This process includes survey
and diagnostic results on the assessment of building condition.
A computational durability model enabled predictions of life cycle
performances of concrete structures and extended the usability of BIM
into the durability assessment [52].
A Facility Control Framework, based on the Industry Foundation
Class Model, was proposed by East et al. [53] in order to compare fa-
cility requirements with its actual performances. This effort resulted in
the creation of an adaptive building control and feedback system.
Interoperability specification, in terms of IDM and MVD, has been
delivered for integrated performance-based design [54]. This research
was focused on energy efficient design.
Recently, an IFC subset schema has been presented to map Building
Automation System (BAS) information in IFC data model, suggesting a
R. Marmo, et al.
great opportunity to create BIM-based BAS design tools or a plug-in for
both importing and exporting requirements following the novel MVD
[55].
Building Information Modelling can act as a repository of data to
quickly populate an FM database [56] or to gather relevant information
about systems condition (actual condition, actual service life, energy
consumption, etc.) [12,14,51,52,55] and maintenance tasks (planned
and preventive maintenance tasks, corrective interventions, main-
tenance history etc.) [41,45,46,48,49]. It gives additional benefits due
to its analytical skills, so that relevant information can be generated
(i.e. performance quantification, future intervention selection, impact
of retrofit works, etc.) [14,41,51,56].
2. A framework for an openPIM
In this section we argue for the extension of the Performance
Information Model with an open standard approach. Following the
concept of openBIM, this paper considers the IFC 4.2 version and ex-
tends PIM to openPIM. The interoperability issue is addressed by
mapping the Industry Foundation Classes into a relational database for
maintenance and performance management. Such a database is based
on entities and attributes retrieved from the IFC schema which any
professional can understand. Delivering IFC models and IFC compliant
databases, based on the same specific attributes, can enhance the in-
formation exchange.
The visual programming language (VPL) and Python programming
language are used to automate information exchanges between facility
information systems and BIM models.
Performance assessment results, preventive and corrective main-
tenance information and requests for intervention are modelled into the
customised relational database, using the standardised IFC entities
identified as relevant for these scopes. The IDM methodology has been
taken as reference for defining information exchange requirements and
modelling process maps. Then a subset of IFC 4.2 has been defined to
document information exchanges identified in the IDM. The resulting
openPIM can be referred to as a customised MVD for performance as-
sessment and maintenance management which contributes to the al-
ready existing FM handover MVD.
The proposed approach is validated by three case studies regarding
operation theatres of healthcare facilities. Performances to be mon-
itored are assessed and quantified through Key Performance Indicators.
The development of the openPIM follows four main steps (Fig. 2):
(a) defining the scope of the database and the information require-
ments; (b) mapping IFC schema into an entity-relationship model
(ERM); (c) creating the openPIM relational database; (d) integrating the
IFC model with the openPIM relational database.
2.1. Database scope and information requirements
The identification of the PIM information requirements is the first
step to efficiently design a model consistent in its purpose. Client's and
users' perspectives are essential to have in mind which are the objec-
tives the model will support. Analysing the Facility Management policy
allows us to identify information to be managed in order to reach the
organisation goals. Process models in Business Process Modelling
Notation (BPMN) have been created to identify a specified set of data
for exchange. A BPMN diagram describes the activities, related in-
formation and actors involved in the process. Interviewing stakeholders
involved in this study and examining their maintenance tender speci-
fications allowed to determine maintenance processes in detail. As an
example, the corrective and the scheduled monitoring processes are
depicted in Figs. 2 and 3, respectively. Fig. 2 assumes that an employee
detects a failure and contacts the maintenance management team. A
project order can be required for certain tasks, but it can be avoided for
minor works. Fig. 3 shows the process of building condition monitoring
in accordance with a work schedule, no automated building system is
4
Automation in Construction 118 (2020) 103275
supposed to be involved in the process.
The openPIM database aims at enabling the maintenance and
monitoring activities record and is meant to enrich a model with spe-
cific FM information. It has been designed to keep track of:
- Corrective maintenance activities;
- Planned maintenance activities;
- Monitoring activities;
- Performance assessment results through KPIs;
- Actors involved in those processes.
The result of this initial stage is the list of the main entities included
in the database, as reported in Table 2.
2.2. Entity-relationship database design
Once the main required entities are identified, the IFC schema
serves as a reference for checking their definition, including their re-
lationships and attributes. Identified entities are covered by the inter-
national schema except for the KeyPerformanceIndicator, the
Measurement and the Model. The Model entity has been used to relate
each product to the model it belongs to. The concepts of measured,
derived or simple values are contained in the Resource layer of the IFC
schema, through the IfcValue select type. Furthermore, the
IfcPerformanceHistory entity is meant to represent performance as-
sessment results. It can be related to products, controls and measure-
ment values through a complex system of relationships. To improve the
efficiency of the database, it has been decided to define two new tables
containing the KPI results and related measurements.
An Entity-Relationship model (ER model) has been created by the
Pony web-based and free access editor. Figs. 4, 5 and 6 present extracts
of the developed model.
The openPIM model is formed by the below-discussed concepts,
borrowed by the IFC schema 4.2.
The IfcActor defines all actors or human agents involved in a pro-
ject. It facilitates the use of person and organisation definitions in the
resource part of the IFC object model. The IfcActorResource schema and
related classes are used to define the IfcActor entity through IfcPerson,
IfcOrganization and IfcPersonAndOrganization entities. The ActorRole
indicates a role which is performed by the previous entities. The Actor
has relationships defined by the IfcRelAssignsToActor entity. For ex-
ample, an actor can issue an action request, so that in the
IfcRelAssignsToActor relationship the RelatingIssuingActor and the
RelatedActionRequest will be defined (Fig. 4).
The IfcActionRequest entity is defined as the act or an instance of
asking for something. Each ActionRequest instance is identified by a
unique identification number through the id attribute, inherited by the
IfcControl. The ActionRequest entity is related to the IssuingActor and
the FulfillingActor through the RelAssignsToActor relationship. The
ActionRequest is also related to the Task and the Product entities.
Furthermore, an ActionRequest is related to ProjectOrder and
KeyPerformanceIndicatorResult entities as each request can generate a
work order or can lead to the quantification of the assessed perfor-
mances.
An IfcProjectOrder is a directive to purchase products and/or per-
form work. The ProjectOrder is related to the Actor similarly to the
ActionRequest. The IfcApproval entity may indicate the status of ac-
ceptance or rejection using the IfcRelAssociatesApproval relationship
where RelatedObjects refers to a ProjectOrder.
Even though this idea is not included in the openPIM model here
presented, action requests and project orders may nest further controls
and orders.
The IfcWorkPlan entity contains a set of work schedules for different
purposes. A WorkSchedule is related to the WorkPlan through the
IfcRelAggregates relationship. A WorkSchedule controls a set of Tasks
defined through IfcRelAssignsToControl.
R. Marmo, et al. Automation in Construction 118 (2020) 103275

Fig. 2. Corrective maintenance process (standard BPMN notation).

Fig. 3. Process of building condition monitoring according to a work schedule (standard BPMN notation).

5
R. Marmo, et al. Automation in Construction 118 (2020) 103275

Table 2 The IfcMeasurement entity is meant to describe the monitoring

Main entities which form part of the openPIM database.
Action request Actor
Approval Key Performance Indicator
Measurement Organisation
Product Project order
Task Work schedule
The IfcTask entity represents an identifiable unit of work to be
carried out in a project. The Task entity is related to the WorkSchedule,
to Product and ActionRequest entities, in order to define the object to
which the work schedule is assigned, the product on which a de-
termined task has to be performed and the action request generated by
an instance of a task (Fig. 5).
The IfcProduct entity is an abstract representation of any object that
relates to a geometric or spatial context. For inheritance, attributes such
as GUID (globally unique identifier), object type, name, description can
be applied. In addition, the localId attribute has been added to make the
identification of the product in a BIM platform (such as Revit) easier.
Each instance of the product entity is related to Task, ActionRequest,
Measurement and IfcModel through the relationship RelAssignsTo-
Product.
activities and related results. An instance of an IfcMeasurement iden-
tifies a control variable. Each instance of the IfcMeasurement entity is
associated with an IfcProduct. For example, the measurement of
thermal properties can be associated with a wall, the noise intensity to a
space etc. The measurement is also related to the IfcKeyPerformance-
IndicatorResult, as according to monitored parameters values, the re-
lated KPI is calculated. In the IfcRelAssignsToMeasurement relationship
it is possible to define the acceptability of measurement results and
their interpretation.
The concept of KPI is expressed by the IfcKeyPerformanceIndicator
entity, so that each KPI is identified by a unique identification number,
furthermore its description, its explicit name and its acronym are de-
fined. Each IfcKeyPerformanceIndicator instance can be related to an
IfcKeyPerformanceIndicatorResult instance. The latter is also related to
IfcActionRequest entity through the IfcRelAggregatesActionRequest-
ToKPIResult relationship, as the performance assessment through
multiple KPIs can be defined by an action request (Fig. 6).
2.3. Creating the openPIM database
The Entity-Relationship model has defined entities, attributes and
relationships. The database defines tables and attributes, specifying

Fig. 4. Extract of IfcActorResource schema.

6
R. Marmo, et al.
Fig. 5. IfcTask entities.
properties of attributes (i.e. data types and constraints) and identifying
the primary key for each table. This operation has been carried out on
Pony editor. The class of each attribute has been specified in: primary
key, for an attribute that will be used by the Database Management
System (DBMS) to uniquely identify each row in a table; required, when
an instance of the attribute is needed for each row; optional, if the in-
stance of the attribute is not required. The data type for each attribute
has been defined too. Other specifications can regard default values for
certain attributes, the attribute property of being nullable, auto in-
crementable or unique.
The database editor used in this paper translates queries to
Structured Query Language (SQL) using a specific database ‘dialect’.
The resulted database consists of 40 tables, listed in Table 3.
The SQL Data Definition Language (DDL) for creating the database
tables in SQLite is reported in Annex 1. SQL ‘dialects’ available on the
Pony editor have been analysed and implemented in appropriate DBMS.
The purpose was to test the connectivity between different types of
DBMS and the IFC model, through a VPL application. The integration
results are exposed in Section 3. Tested management systems were
PgAdmin for PostgreSQL syntax, MySQL Workbench for MySQL syntax
and DB Browser for SQLite syntax.
2.4. Connecting the openPIM database with the IFC model
The openPIM database and the corresponding IFC model can be
7
Automation in Construction 118 (2020) 103275
connected in several ways. In the context of this paper the connection
has been achieved by using Dynamo, a VPL environment. Dynamo
provides a basic workspace in which functions (nodes) can be arranged
and linked to each other. The different functions are usually offered in a
library that can be expanded through several packages. In order to
establish a connection between an IFC model and the openPIM database
the Slingshot! Dynamo packages can be used [57]. The SQLite engine
database was chosen among others as it is commonly used all over the
world [58] and above all, it is file-based, so that possible connection
issues can be avoided [59]. The database was created and edited in DB
Browser for SQLite. Another tool for connecting a DBMS with an IFC
model through Dynamo is the Python programming language. The VPL
environment contains Python. Script nodes to develop applications for
creating the link between the database and the BIM model.
3. Healthcare buildings case studies
The implementation of the openPIM approach regards three inter-
national healthcare buildings (Fig. 7).
The developed case studies involve:
• One hospital located in the province of Salerno, Italy (case study A),
• One hospital located in Verona, Italy (case study B)
• One hospital is located in Ljubljana, Slovenia (case study C).
R. Marmo, et al. Automation in Construction 118 (2020) 103275

Fig. 6. Building performance entities.

The openPIM database has been filled with information retrieved
from those facilities. In particular the following sources have been
considered:
• Tenders specification about monitoring activities and O&M man-
agement for identifying contractors and managers involved in those
processes. In this way the tables RoleEnum, Person, Organization,
PersonAndOrganization, ActorRole, Actor were filled.
• Maintenance plan, reports of corrective maintenance activities and
project orders records were examined to fill WorkPlan,
WorkPlanTypeEnum, WorkSchedule, WorkScheduleTypeEnum,
Task, TaskTimeRecurring, TaskTypeEnum, ProjectOrder, Projector-
derTypeEnum, Product tables.
• Results of environmental condition were used for Measurement,
KeyPerformanceIndicator, KeyPerformanceIndicatorResult tables.
The implementation of the openPIM regards surgery units. An
Environmental Condition Index (ECI) has been used to quantify and
evaluate the environmental quality of surgery rooms of A and B case
studies. This index depends on instrumentally measurable parameters:

Table 3
Tables contained in the openPIM relational database.
ActionRequest ActionRequestTypeEnum

Actor ActorRole
Approval IFCModel
KeyPerformanceIndicator KeyPerformanceIndicatorResult
Measurement Organization
Person PersonAndOrganization
Product ProjectOrder
ProjectOrderTypeEnum RecurrencePattern
RecurrenceTypeEnum RelAggregatesActionRequestToKPIResult
RelAggregatesActionRequestToProjectOrder RelAggregatesWorkPlanToWorkSchedule
RelAssignsActionRequestToProduct RelAssignsFulfillingActorToActionRequest
RelAssignsFulfillingActorToProjectOrder RelAssignsIssuingActorToActionRequest
RelAssignsIssuingActorToProjectOrder RelAssignsProductToMeasurement
RelAssignsProductToModel RelAssignsTakToActionRequest
RelAssignsTaskToProduct RelAssignsToMeasurement
RelAssignsWorkScheduleToTask RelAssociateApproval
RoleEnum Task
TaskTimeRecurring TaskTypeEnum
WorkPlan WorkPlanTypeEnum
WorkSchedule WorkScheduleTypeEnum

8
R. Marmo, et al.
Fig. 7. Buildings involved in the openPIM implementation. Case study A on the left, case study B in the centre, case study C on the right.
particle concentration, microclimatic condition, anaesthetic gases,
noise, air changes. The definition of such an index is discussed in
Marmo et al. [14]. Evaluating the ECI requires performing a set of
environmental controls and analysing the results in terms of pass or
failed tests. Databases accessed for the development of this research
were provided directly by maintenance and risk management depart-
ments. These databases contained results of the environmental assess-
ment procedures (in terms of fulfilled or failed control) which the au-
thors used for calculating surgery rooms ECI values. Case study A was
also used to validate the openPIM related to corrective maintenance
management, while the case study C aimed at testing the openPIM for
the planned maintenance management.
Hospitals involved in this research do not use BIM-oriented FM
approaches yet, their assets are not digitalised, risk management and
maintenance databases are kept separated so that facilities management
is based on sparse sources of knowledge. For example, the risk man-
agement team reports to the maintenance management team the results
of the environmental condition evaluation once per year (case study A
and C). This causes delays in the decision making regarding corrective
or preventive interventions potentially needed.
FM tenders of the three case studies are based on the evaluation of
maintenance services quality (through qualitative assessment), but in
no case this evaluation is integrated into a performance-based model
extended to the overall healthcare system.
Furthermore, analysed surgery units are parts of bigger portfolios of
assets, which can benefit from using a set of KPIs for quantifying and
benchmarking performances, and, as a consequence, for enhancing
strategical and tactical decision making.
Autodesk Revit 2019 has been used to create native models. This
modelling software allows you to export IFC models in different ver-
sions, including IFC4 Reference View and IFC4 Design Transfer View.
IFC4 importation in Revit 2019 was affected by a certain grade of loss of
information. For this reason, the IFC2x3 Coordination View version,
correctly and comprehensively exported and imported in Revit plat-
form, was selected to implement the BIM-FM-BPA integration. The IFC
GUID was stored as element parameter after the exportation and the
level of detail for IFC elements geometry was settled as low.
Literature findings suggest that FM models can have a low level of
development [38,39] as long as they are enriched by relevant in-
formation about facilities. For this reason, the developed openPIMs are
geometrically simple but contain operational information about assets
to be managed.
3.1. Case study A
The case study A regards a small hospital in the South of Italy
comprising three surgery rooms. Data for the creation of the BIM model
were retrieved from CAD architectural and mechanical plans. Facilities
information used to develop this application regarded corrective
maintenance history and environmental monitoring results. Corrective
9
Automation in Construction 118 (2020) 103275
maintenance records were related to the first half of the 2019, while the
monitoring results were related to the second semester of the 2018. The
local authority performs every six months monitoring activities in the
surgery unit. Results of these controls were used by the authors for
calculating ECI values for each surgery room. The information related
to the environmental quality was added to native model rooms in the
form of a shared parameter so that the ECI value can be visualised in the
model. The IFC exportation retrieved the ‘EC’ parameter as IfcSpace
attribute, among the IfcPropertySet of the product. To do so a user
defined property set has been settled, as shown in Table 4.
Even though the definition of an IfcPropertySet of an IfcObject can
vary from a project to another, its use is consistent with an openBIM
approach, as it is readable by any IFC based BIM workflow.
In the IFC file it is possible to locate the fragment which shows an
example of the customised IfcPropertySet ‘Environmental Condition
Index’ for this use case:
#447= IFCSPACE('3mEKxmRXn5YBf4tDclS4iG', #42,'031', $,
$,#398,#444,'Pediatric surgery room', .ELEMENT., .INTERNAL., $);
#462= IFCPROPERTYSINGLEVALUE('ECI', $,IFCREAL (0.9),$);
#463= IFCPROPERTYSET('0I4OvQlk5AegzZ07gFx4CV',#42,'En-
vironmental Condition Index',",(#462)).
The IFC model was linked to the openPIM database through
Dynamo. The SelectModelElement node has been used to identify id
elements directly from the current view on Revit. This is the starting
point for querying the database about further information related to
that element. The Query.SQLite.Query creates a connection with the
DBMS and using a String node it is possible to query the openPIM da-
tabase to inform the IFC model. As an example, it is possible to extract
environmental performance assessment results for the general surgery
room. Knowing the localId element, the associated globalId can be
deduced, as well as the measurements related to it. These measure-
ments are linked to one or more KPI results through the
RelAssignsToMeasurement relationship. From the KeyPerformance-
IndicatorResult table it is possible to retrieve the KPI value and other
attributes (interpretation, comment etc.). Furthermore, the
Element.SetParameterByName node can be used to update the IFC
model parameters. A thematic plan can be created to visualise assess-
ment results in terms of Environmental Condition Index values (Fig. 8).
Through the openPIM database it is possible to keep track of
planned or corrective maintenance activities associated with an object,
both done or waiting to be performed. For example, from the
ActionRequest table it is possible to retrieve the request for corrective
Table 4
Customised property set for IFC exportation.
PropertySet: Environmental Condition Index I IfcSpace
ECI Real EC
R. Marmo, et al. Automation in Construction 118 (2020) 103275

Fig. 8. KPI values can be retrieved from the openPIM database and visualised into the IFC model.

Table 5 3.2. Case study B

SQL statement for retrieving data about corrective maintenance tasks.
SQL query
This case study regards a Verona's big surgery unit containing 33
operating rooms. The modelling process started from CAD architectural
SELECT globalId, name, identification, longDescription FROM Product and mechanical plans. The openPIM database is used to gather in-
INNER JOIN RelAssignsActionRequestToProduct formation regarding environmental controls and to inform the IFC
ON RelAssignsActionRequestToProduct.relatedProduct=Product.globalId
model with the corresponding results. Maintenance management de-
INNER JOIN ActionRequest
ON partment provided sources and data for developing the model and
ActionRequest.id=RelAssignsActionRequestToProduct.relatingActionRequest implementing the database. Similarly to case study A, the measurement
WHERE globalId='3EZqFqD0T2y9ctbXGTnNRR' results were used to fill out the Measurement table, calculated KPIs
values were inserted in the KeyPerformanceIndicatorsResult table and
relationships between the aforementioned tables were defined in the
Results
RelAssignsToMeasurement. These healthcare buildings are equipped
globalId name identification longDescription with Building Automation Systems for controlling anaesthetic gases
concentration, temperature and humidity value, and air particle con-
3EZqFqD0T2y9ctbXGTnNRR Fire Doors Ac_10_70_70 Replace panic bar
centration. These parameters are monitored every day, while they are
analysed on a monthly basis report. One of these reports, related to
intervention regarding a fire door. The localId and/or the globalId June 2019, was used by the authors for evaluating the ECI of each room
permits to identify univocally the object, the RelAssignsAction- of this case study.
RequestToProduct relationship gives the request for intervention re- In this case a Python application was developed and tested to au-
lated to that object, the ActionRequest table contains information about tomatically update the IFC model with data from the database. The
such a request. The SQL query performed on the DBMS and related advantage of using Python consists of creating a unique node for con-
results are reported in Table 5. The identification attribute of the Ac- necting and querying the database. Furthermore Python nodes support
tionRequest table has been defined considering the Uniclass classifica- long and complex queries (i.e. ‘inner join’ statements and clauses) so
tion system [60]. that the efficiency of both the database and of Dynamo application can

10
R. Marmo, et al.
Fig. 9. Python application for retrieving the ECI value based on the localID of a Revit element (on the left). Thematic plan for visualising environmental assessment
results in the IFC model (on the right).
be improved. An application for retrieving KPI results associated with a
determined product (i.e. cardiac surgery room) has been developed.
The application establishes a connection with the database and carries
out queries for retrieving the ECI value of an element starting from its
localId (Fig. 9). These results have been used to set ECI parameter va-
lues in the IFC model through the Element.SetParameterByName node.
Environmental condition results are visualised in a thematic plan
through a colour scheme as shown in Fig. 9.
3.3. Case study C
An operating unit, located in Ljubljana, including five oncological
surgery rooms has been used for testing the openPIM database cap-
ability in supporting planned maintenance management. In this case
the environmental monitoring report was not available. By the way, the
healthcare authority performs monitoring and ordinary maintenance
activities of the surgery unit once per year. The maintenance plan used
for developing this pilot implementation contained all checking, re-
paration and cleaning activities to be performed in the 2019. WorkPlan,
WorkSchedule, Task, TaskTimeRecurring, Product and related tables
were filled out with data retrieved from the maintenance plan. The
identification attribute of the Task table has been defined considering
the Uniclass classification system. Detailed tasks information (time re-
sources, start date, end date, long description, involved elements etc.)
11
Automation in Construction 118 (2020) 103275
can be gathered from the database. An IFC model was created based on
CAD architectural plans. Starting from the globalId of an IFC product it
is possible to get planned maintenance information associated with it.
The SQL query performed on the DBMS and related results are reported
in Table 6. As this data is not geometry-related, it is not visualised into
the IFC model. In fact, common IFC viewer applications do not support
storing or managing these kinds of attributes yet (Fig. 10).
4. Discussion
The use of Building Information Modelling has recently gained more
interest in the FM domain, as a technology to create a single source of
knowledge, enabling faster and consistent information exchange during
the building life-cycle. Current BIM application in the operational phase
regards both the release of a comprehensive inventory about the asset
to be managed and the development of an integrated source of
knowledge for operational activities. BIM models offer a consistent 3D
interface for facility information management, which enhances main-
tenance activities analysis. Nevertheless, a seamless information pro-
cess between BIM and FM systems is hard to obtain. For this purpose,
open standard data models improve data mapping and data integration
between BIM models and FM systems. Many researchers have proposed
extension of existing IFC data schema to gather maintenance related
information. On the contrary, this paper relies on the current IFC 4.2
R. Marmo, et al. Automation in Construction 118 (2020) 103275

Table 6
SQL statement for retrieving data about planned maintenance tasks.
SQL query

SELECT globalId, Task.identification, task.longDescription, task.workMethod FROM

Product
INNER JOIN RelAssignsTaskToProduct
ON RelAssignsTaskToProduct.relatedProduct=Product.globalId
INNER JOIN Task
ON Task.id=RelAssignsTaskToProduct.relatingTask
WHERE globalId='23yv66nlP8wA5vCN9xEVBe'

Results

globalId identification longDescription workMethod

23yv66nlP8wA5vCN9xEVBe Ac_15_55 General inspection and reparation of wood and steel furniture visual inspection and manual work

version to achieve a BIM-FM-BPA integrating process, enabling main-
tenance management and performance assessment through an open
Performance Information Model.
IFC applicability seems to have limited applicability into the busi-
ness process, it does not capture event-logs, but it describes the se-
mantics of physical and conceptual building components [44].
In the context of healthcare facilities management, literature find-
ings [16–18] reveal that using a set of KPIs can increase both main-
tenance efficiency and facilities performances and it can allow bench-
marking activities at different levels (i.e. technological unit,
technological system, asset itself). The authors moved from this hy-
pothesis in order to develop a performance-oriented digital model,
based on KPIs, starting from surgery rooms' environmental system.
Results exposed in this paper show that:
- The latest IFC 4.2 schema supports BIM workflows in the FM domain
in a comprehensive manner. It provides a wide amount of entities to
define maintenance and performance assessment processes.
- BIM-FM integration processes can be implemented and improved by
an openPIM. Firstly, the IFC compliant database proved to keep
track of maintenance activities and building performances and it can
be easily integrated with an IFC model to unleash the potentiality of
FM supported by digital 3D models. Secondly, implemented
openPIMs provided integrated sources of knowledge with a low
level of development and a level of information detailed enough to
support FM activities (Fig. 9). Even though common IFC viewer
applications do not allow the visualisation of non-geometry related
attributes (Fig. 10), ad-hoc attributes could be defined through the
IfcpropertySet of IfcProduct (Table 4).
- A fully developed healthcare PIM not only can include the building
inventory and technical specification about elements and materials
(according to the handover phase model), but it will keep track of

Fig. 10. Case study C, IFC model in Solibri application.

12
R. Marmo, et al.
maintenance activities, monitoring processes, performance assess-
ment results (in terms of KPIs).
- A digital model enriched with as-built and operational information
enhances the decision-making process. Facility managers and asset
owners will have a reliable source of knowledge, enabling spatial
and temporal analysis for optimising the maintenance planning. For
example, it can support complex analysis (affordability, ob-
solescence, actual service life etc.) in the domain of condition-based,
preventive or predictive maintenance. These analyses will involve
not only the element scale, but also technological and environ-
mental systems and at the end, the building itself. The use of KPIs
(financial, technical and organisational) will address different scales
of decision making and will enable benchmarking activities.
- The openPIM might be considered as the first step for the creation of
a user-oriented asset digital twin. The digital model is user-oriented
in the sense that stakeholders' information requirements lead the
database design and an IFC model is created according to this set of
information, then many applications (i.e. visual programming lan-
guage, python programming language) can be developed to in-
tegrate the two sources of data. In this way, operational information
retrieved from the database can enrich the model which illustrates
asset performances at a particular moment in time. According to
different stakeholders' requirements openPIMs can differ (such as in
terms of performances to be assessed and related controls activities
and/or systems involved). In this sense, a specific openPIM hardly
supports requirements of organisations with different needs. The
proposed framework has been referred to as ‘open’ because it relies
on the use of a vendor-neutral data model, which served as a basis
for the translation of stakeholder's information requirements into
IFC entities and related attributes.
- The proposed openPIM can be referred to as an expansion of the FM
handover MVD. It adds entities such as IfcActionRequest,
IfcProjectOrders, IfcTask, IfcWorkPlan, IfcWorkSchedule,
IfcApproval, IfcKeyPerformanceIndicator, IfcKeyPerformance-
IndicatorsResult, IfcMeasurement which support maintenance
management, monitoring activities planning and implementation,
and performance assessment analysis.
5. Conclusion
Facility Management embraces a wide field of activities and com-
petencies, which require an increasing range of criteria to be considered
in order to achieve more sustainable, efficient, safe and comfortable
assets. In this sense, the integration of different sources of data is re-
quired and it has been carried out using different and sparse informa-
tion management systems in the past. In this paper we have argued for
integrating FM systems with BIM technology in order to support
maintenance management and building performance assessment ac-
tivities. The methodology addresses current research gaps such as the
identification of critical information required to inform management
decisions and the effort to update BIM models. The literature review
suggested the delivery of FM models with low level of development,
then the automated updating of the model with operational information
Annex 1
This annex contains an extract of the SQL code which can be used to create a building performance database in SQLite. It contains entities,
attributes and related properties, as well as the definition of primary and foreign keys to keep track of information concerning action requests,
products, IFC models, actors, measurements and Key Performance Indicators.
13
Automation in Construction 118 (2020) 103275
has been implemented. FM teams have been involved in the perfor-
mance information modelling to improve the efficiency of the delivered
openPIMs.
An openPIM framework has been defined in four main steps: (a)
defining the scope of the database and the information requirements;
(b) mapping IFC schema into an entity-relationship model (ERM); (c)
creating the openPIM relational database; (d) integrating the IFC model
with the openPIM relational database. FM information requirements
were analysed and conceptualised into an ER-model, an IFC schema
compliant database to keep track of this information has been designed
and the information exchange between FM repository and IFC model
has been developed.
Through the three case studies we tested and validated the openPIM
framework for managing corrective maintenance, for performance as-
sessment purposes, and for planned maintenance management.
This paper contributes to the body of knowledge with extending
some recent researches related to the integration of diverse volume of
data necessary for day-to-day building operations into BIM environ-
ments (such as Bortoluzzi et al. [38]) to a vendor-neutral approach
based on the IFC data model as a reference for modelling FM processes
and physical building elements.
Nowadays, the major part of IFC viewer applications do not allow
the visualisation of non-geometry related attributes. This means that
the visualisation of maintenance data and assessment results is missing,
and it could be time-consuming and counterproductive adding custom
properties for this purpose. Even though ad-hoc attributes could be
defined into the property set of an IFC element to manage this in-
formation, there is still room to improve the capabilities of current
software to visualise action requests, tasks, project orders, actors etc.
associated with an IfcProduct in an IFC viewer application.
This research is limited to the healthcare facilities field and it is
focused on the environmental system quality. Future advancements will
include the design of the Performance Information Model for other
purposes (i.e. technological and financial performance assessment) so
as to gain a comprehensive performance-based digital model which will
likely support FM teams' competencies and responsibilities.
Furthermore, the updating the openPIM database when IFC schema
changes will be explored too.
Declaration of competing interest
The authors declare that they have no known competing financial
interests or personal relationships that could have appeared to influ-
ence the work reported in this paper.
Acknowledgment
The authors want to acknowledge the Local Health Authority of
Salerno, the University Hospital of Verona, the Oncological Institute of
Ljubljana for the support given to the development of the case studies
discussed in this research.
R. Marmo, et al. Automation in Construction 118 (2020) 103275

CREATE TABLE "ActionRequestTypeEnum" (

"id" INTEGER PRIMARY KEY AUTOINCREMENT,
"constant" TEXT NOT NULL,
"description" TEXT
);

CREATE TABLE "ActionRequest" (

"id" INTEGER NOT NULL PRIMARY KEY,
"identification" TEXT,
"actionRequestTypeEnum" INTEGER NOT NULL REFERENCES "ActionRequestTypeEnum"
("id") ON DELETE CASCADE,
"status" TEXT,
"longDescription" TEXT
);

CREATE INDEX "idx_actionrequest__actionrequesttypeenum" ON "ActionRequest"

("actionRequestTypeEnum");

CREATE TABLE "IFCModel" (

"id" INTEGER PRIMARY KEY AUTOINCREMENT,
"modelContent" TEXT
);

CREATE TABLE "KeyPerformanceIndicator" (

"id" INTEGER PRIMARY KEY AUTOINCREMENT,
"name" TEXT NOT NULL,
"shortName" TEXT NOT NULL,
"description" TEXT
);

CREATE TABLE "KeyPerformanceIndicatorResult" (

"id" INTEGER PRIMARY KEY AUTOINCREMENT,
"keyPerformanceIndicator" INTEGER NOT NULL REFERENCES "KeyPerformanceIndicator"
("id") ON DELETE CASCADE,
"valueNumerical" INTEGER,
"valueDescriptive" TEXT,
"timestamp" DATETIME,
"comment" TEXT,
"interpretation" TEXT
);

CREATE INDEX "idx_keyperformanceindicatorresult__keyperformanceindicator" ON

"KeyPerformanceIndicatorResult" ("keyPerformanceIndicator");

CREATE TABLE "Measurement" (

"id" INTEGER NOT NULL PRIMARY KEY,
"timestamp" DATETIME NOT NULL,
"valueNumerical" REAL,
"valueDescriptive" TEXT,
"description" TEXT
);

CREATE TABLE "Organization" (

"identifier" TEXT NOT NULL PRIMARY KEY,
"name" TEXT NOT NULL,
"description" TEXT,
"address" TEXT
);

CREATE TABLE "Person" (

"identifier" TEXT NOT NULL PRIMARY KEY,
"familyName" TEXT NOT NULL,
"givenName" TEXT NOT NULL,
"middleNames" TEXT
);

CREATE TABLE "Product" (

"globalId" TEXT NOT NULL PRIMARY KEY,
"localId" TEXT NOT NULL,
"name" TEXT,
"description" TEXT,
"objectType" TEXT
);

CREATE TABLE "RelAggregatesActionRequestToKPIResult" (

"id" INTEGER PRIMARY KEY AUTOINCREMENT,
"relatingActionRequest" INTEGER NOT NULL REFERENCES "ActionRequest" ("id") ON
DELETE CASCADE,
"relatedKPIResult" INTEGER NOT NULL REFERENCES "KeyPerformanceIndicatorResult"
("id") ON DELETE CASCADE
);

14
R. Marmo, et al. Automation in Construction 118 (2020) 103275

CREATE INDEX "idx_relaggregatesactionrequesttokpiresult__relatedkpiresult" ON

"RelAggregatesActionRequestToKPIResult" ("relatedKPIResult");

CREATE INDEX "idx_relaggregatesactionrequesttokpiresult__relatingactionrequest" ON

"RelAggregatesActionRequestToKPIResult" ("relatingActionRequest");

CREATE TABLE "RelAssignsActionRequestToProduct" (

"id" INTEGER PRIMARY KEY AUTOINCREMENT,
"relatedProduct" TEXT NOT NULL REFERENCES "Product" ("globalId") ON DELETE
CASCADE,
"relatingActionRequest" INTEGER NOT NULL REFERENCES "ActionRequest" ("id") ON
DELETE CASCADE
);

CREATE INDEX "idx_relassignsactionrequesttoproduct__relatedproduct" ON

"RelAssignsActionRequestToProduct" ("relatedProduct");

CREATE INDEX "idx_relassignsactionrequesttoproduct__relatingactionrequest" ON

"RelAssignsActionRequestToProduct" ("relatingActionRequest");

CREATE TABLE "RelAssignsProductToMeasurement" (

"id" INTEGER PRIMARY KEY AUTOINCREMENT,
"relatingProduct" TEXT NOT NULL REFERENCES "Product" ("globalId") ON DELETE
CASCADE,
"relatedMeasurement" INTEGER NOT NULL REFERENCES "Measurement" ("id") ON
DELETE CASCADE
);

CREATE INDEX "idx_relassignsproducttomeasurement__relatedmeasurement" ON

"RelAssignsProductToMeasurement" ("relatedMeasurement");

CREATE INDEX "idx_relassignsproducttomeasurement__relatingproduct" ON

"RelAssignsProductToMeasurement" ("relatingProduct");

CREATE TABLE "RelAssignsProductToModel" (

"id" INTEGER PRIMARY KEY AUTOINCREMENT,
"relatedIFCModel" INTEGER NOT NULL REFERENCES "IFCModel" ("id") ON DELETE
CASCADE,
"relatingProduct" TEXT NOT NULL REFERENCES "Product" ("globalId") ON DELETE
CASCADE
);

CREATE INDEX "idx_relassignsproducttomodel__relatedifcmodel" ON

"RelAssignsProductToModel" ("relatedIFCModel");

CREATE INDEX "idx_relassignsproducttomodel__relatingproduct" ON

"RelAssignsProductToModel" ("relatingProduct");

CREATE TABLE "RelAssignsToMeasurement" (

"id" INTEGER PRIMARY KEY AUTOINCREMENT,
"relatingResult" INTEGER NOT NULL REFERENCES "KeyPerformanceIndicatorResult" ("id")
ON DELETE CASCADE,
"relatedMeasurement" INTEGER NOT NULL REFERENCES "Measurement" ("id") ON
DELETE CASCADE,
"interpretation" TEXT,
"acceptance" BOOLEAN
);

CREATE INDEX "idx_relassignstomeasurement__relatedmeasurement" ON

"RelAssignsToMeasurement" ("relatedMeasurement");

CREATE INDEX "idx_relassignstomeasurement__relatingresult" ON

"RelAssignsToMeasurement" ("relatingResult");

CREATE TABLE "RoleEnum" (

"id" INTEGER NOT NULL PRIMARY KEY,
"constant" TEXT NOT NULL,
"description" TEXT
);

CREATE TABLE "ActorRole" (

"id" INTEGER PRIMARY KEY AUTOINCREMENT,
"role" INTEGER NOT NULL REFERENCES "RoleEnum" ("id") ON DELETE CASCADE,
"userDefinedRole" TEXT,
"description" TEXT
);

15
R. Marmo, et al. Automation in Construction 118 (2020) 103275

CREATE INDEX "idx_actorrole__role" ON "ActorRole" ("role");

CREATE TABLE "PersonAndOrganization" (

"id" INTEGER PRIMARY KEY AUTOINCREMENT,
"person" TEXT NOT NULL REFERENCES "Person" ("identifier") ON DELETE CASCADE,
"organization" TEXT NOT NULL REFERENCES "Organization" ("identifier") ON DELETE
CASCADE,
"roles" INTEGER NOT NULL REFERENCES "ActorRole" ("id") ON DELETE CASCADE
);

CREATE INDEX "idx_personandorganization__organization" ON "PersonAndOrganization"

("organization");

CREATE INDEX "idx_personandorganization__person" ON "PersonAndOrganization"

("person");

CREATE INDEX "idx_personandorganization__roles" ON "PersonAndOrganization" ("roles");

CREATE TABLE "Actor" (

"id" INTEGER NOT NULL PRIMARY KEY,
"theactor" INTEGER NOT NULL REFERENCES "PersonAndOrganization" ("id")
);

CREATE INDEX "idx_actor__theactor" ON "Actor" ("theactor");

CREATE TABLE "RelAssignsFulfillingActorToActionRequest" (

"id" INTEGER NOT NULL PRIMARY KEY,
"relatingActor" INTEGER NOT NULL REFERENCES "Actor" ("id") ON DELETE CASCADE,
"relatedActionRequest" INTEGER NOT NULL REFERENCES "ActionRequest" ("id") ON
DELETE CASCADE
);

CREATE INDEX "idx_relassignsfulfillingactortoactionrequest__relatedactionrequest" ON

"RelAssignsFulfillingActorToActionRequest" ("relatedActionRequest");

CREATE INDEX "idx_relassignsfulfillingactortoactionrequest__relatingactor" ON

"RelAssignsFulfillingActorToActionRequest" ("relatingActor");

CREATE TABLE "RelAssignsIssuingActorToActionRequest" (

"id" INTEGER PRIMARY KEY AUTOINCREMENT,
"relatingActor" INTEGER NOT NULL REFERENCES "Actor" ("id") ON DELETE CASCADE,
"relatedActionRequest" INTEGER NOT NULL REFERENCES "ActionRequest" ("id") ON
DELETE CASCADE
);

CREATE INDEX "idx_relassignsissuingactortoactionrequest__relatedactionrequest" ON

"RelAssignsIssuingActorToActionRequest" ("relatedActionRequest");

CREATE INDEX "idx_relassignsissuingactortoactionrequest__relatingactor" ON

"RelAssignsIssuingActorToActionRequest" ("relatingActor");

References Building Engineering, Proceeding of the Joint International Conference, Montréal,

[1] S. Curcio, Lessico del Facility Management. Gestione integrata e manutenzione
degli edifici e dei patrimoni immobiliari (Facility Management dictionary.
Integrated management and maintenance of buildings and assets), Il Sole 24 Ore,
Milan, (2003) 8832452065.
[2] ISO 41011-2018, Facility management - vocabulary, Available at https://www.iso.
org/standard/68167.html , Accessed date: 5 January 2020.
[3] IFMA - International Facility Management Association, Certified Facility Manager.
Competency guide, Available at, 2018. https://www.fm.training/sites/collabstore/
files/images/Competency_Guide_Context_Public_v1_7-12-18.pdf.
[4] S. Chotipanich, Positioning facility management, Facilities 22 (2004) 364–372,
https://doi.org/10.1108/02632770410563086.
[5] K. Roper, R. Payant, The Facility Management Handbook, fourth ed., AMACOM,
Nashville, US, 9780814432150, 2014.
[6] A. Akcamete, B. Akinci, J.H. Garrett, Potential utilization of building information
models for planning maintenance activities, in: W. Tizani (Ed.), Computing in Civil
and Building Engineering, Proceedings of the International Conference, Nottingham
University Press, Nottingham, UK, 2010, pp. 151–157.
[7] B. Atkin, A. Brooks, Total Facility Management, Fourth edition, John Wiley & Sons,
Chichester, UK, 2015, pp. 302–303.
[8] I. Flores-Colen, J. de Brito, V. Freitas, Discussion of criteria for prioritization of
predictive maintenance of building façades: survey of 30 experts, J. Perform.
Constr. Facil. 24 (4) (2010) 337–344, https://doi.org/10.1061/(ASCE)CF.1943-
5509.0000104.
[9] D.J. Vanier, S. Tesfamariam, R. Sadiq, Z. Lounis, Decision models to prioritize
maintenance and renewal alternatives, Computing and Decision Making in Civil and
Québec, 14–16 June, 2006, pp. 2594–2603.
[10] N.D. Aziz, A.H. Nawawi, N.R.M. Ariff, ICT evolution in facilities management (FM):
building information modelling (BIM) as the latest technology, Procedia Soc. Behav.
Sci. 234 (2016) 363–371, https://doi.org/10.1016/j.sbspro.2016.10.253.
[11] ISO 19650-1:2018, Organization and digitization of information about buildings
and civil engineering works, including building information modelling (BIM) —
information management using building information modelling — part 1: concepts
and principles, Available at https://www.iso.org/standard/68078.html , Accessed
date: 5 January 2020.
[12] A. Bonci, A. Carbonari, A. Cucchiarelli, L. Messi, M. Pirani, M. Vaccarini, A cyber-
physical system approach for building efficiency monitoring, Autom. Constr. 102
(2019) 68–85, https://doi.org/10.1016/j.autcon.2019.02.010.
[13] D. Hallberg, V. Tarandi, On the use of open bim and 4D visualisation in a predictive
life cycle management system for construction works, J. Inf. Technol. Constr. 16
(2011) 445–466 https://www.itcon.org/2011/26 (ISSN 18744753).
[14] R. Marmo, M. Nicolella, F. Polverino, A. Tibaut, A methodology for a performance
information model to support facility management, Sustainability 11 (24) (2019)
7007, https://doi.org/10.3390/su11247007.
[15] J.S. Junior, C.T. Formoso, P. Tzortzopoulos, A semantic-based framework for au-
tomated rule checking in healthcare construction projects, Can. J. Civ. Eng. 47 (2)
(2020) 202–214, https://doi.org/10.1139/cjce-2018-0460.
[16] I.M. Shohet, S. Lavy, Facility maintenance and management: a health care case
study, Int. J. Strateg. Prop. Manag. 21 (2) (2017) 170–182, https://doi.org/10.
3846/1648715X.2016.1258374.
[17] I.M. Shohet, L. Nobili, Application of key performance indicators for maintenance
management of clinics facilities, Int. J. Strateg. Prop. Manag. 21 (1) (2017) 58–71,
https://doi.org/10.3846/1648715X.2016.1245684.

16
R. Marmo, et al.
[18] I.M. Shohet, L. Nobili, Enterprise resource planning system for performance-based-
maintenance of clinics, Autom. Constr. 65 (2016) 33–41, https://doi.org/10.1016/
j.autcon.2016.01.008.
[19] B.R. Kyle, D.J. Vanier, B. Kosovac, T.M. Froese, Visualizer: an interactive, graphical,
decisions-support tool for service life prediction for asset managers, Proceedings of
the 9th International Conference on Durability of Building Materials and
Components, Brisbane, Australia, 2002, pp. 1–9 available at www.irbnet.de/daten/
iconda/CIB9286.pdf , Accessed date: 8 May 2020.
[20] BuildingSMART International, Available at https://www.buildingsmart.org/ ,
Accessed date: 5 January 2020.
[21] M. Laakso, A. Kiviniemi, The IFC standard - a review of history, development, and
standardization, J. Inf. Technol. Constr. 17 (2012) 134–161 https://www.itcon.
org/paper/2012/9 (ISSN 18744753).
[22] Industry Foundation Classes (IFC), An introduction, Available at https://technical.
buildingsmart.org/standards/ifc/ , Accessed date: 5 January 2020.
[23] ISO 16739-1:2018, Industry Foundation Classes (IFC) for data sharing in the con-
struction and facility management industries — part 1: data schema, Available at
https://www.iso.org/standard/70303.html , Accessed date: 5 January 2020.
[24] Industry Foundation Classes, Version 4.2 bSI Draft Standard, Available at https://
standards.buildingsmart.org/IFC/DEV/IFC4_2/FINAL/HTML/ , Accessed date: 5
January 2020.
[25] Model view definition (MVD) - an introduction, Available at https://technical.
buildingsmart.org/standards/mvd// , Accessed date: 5 January 2020.
[26] Information delivery manual (IDM), Available at https://technical.buildingsmart.
org/standards/information-delivery-manual/ , Accessed date: January 2005.
[27] MVD Database, Available at https://technical.buildingsmart.org/standards/mvd/
mvd-database/ , Accessed date: 5 January 2020.
[28] E. East, N. Nisbet, T. Liebich, Facility management handover model view, Journal of
Computing in Civil Engineering, American Society of Civil Engineers 27 (1) (2013)
61–67, https://doi.org/10.1061/(ASCE)CP.1943-5487.0000196.
[29] X. Gao, P. Pishdad-Bozorgi, BIM-enabled facilities operation and maintenance: a
review, Adv. Eng. Inform. 39 (2019) 227–247, https://doi.org/10.1016/J.AEI.
2019.01.005.
[30] D. Ilter, E. Ergen, BIM for building refurbishment and maintenance: current status
and research directions, Struct. Surv. 33 (3) (2015) 228–256, https://doi.org/10.
1108/SS-02-2015-0008.
[31] R. Edirisinghe, K.A. London, P. Kalutara, G. Aranda-Mena, Building information
modelling for facility management: are we there yet? Eng. Constr. Archit. Manag.
24 (6) (2017) 1119–1154, https://doi.org/10.1108/ECAM-06-2016-0139.
[32] B. Dong, Z. O’Neill, Z. Li, A BIM-enabled information infrastructure for building
energy Fault Detection and Diagnostics, Autom. Constr. 44 (2014) 197–211,
https://doi.org/10.1016/J.AUTCON.2014.04.007.
[33] S.T. Matarneh, M. Danso-Amoako, S. Al-Bizri, M. Gaterell, R. Matarneh, Building
information modeling for facilities management: a literature review and future
research directions, J. Build. Eng. 24 (2019) 100755, , https://doi.org/10.1016/J.
JOBE.2019.100755.
[34] J.J. McArthur, A building information management (BIM) framework and sup-
porting case study for existing building operations, maintenance and sustainability,
Procedia Eng. 118 (2015) 1104–1111, https://doi.org/10.1016/j.proeng.2015.08.
450.
[35] R. Volk, J. Stengel, F. Schultmann, Building Information Modeling (BIM) for ex-
isting buildings — literature review and future needs, Autom. Constr. 38 (2014)
109–127, https://doi.org/10.1016/j.autcon.2013.10.023.
[36] M.K. Dixit, V. Venkatraj, M. Ostadalimakhmalbaf, F. Pariafsai, S. Lavy, Integration
of facility management and building information modeling (BIM), Facilities 37 (7/
8) (2019) 455–483, https://doi.org/10.1108/F-03-2018-0043.
[37] K. Farghaly, F.H. Abanda, C. Vidalakis, G. Wood, Taxonomy for BIM and asset
management semantic interoperability, J. Manag. Eng. 34 (4) (2018) 4018012, ,
https://doi.org/10.1061/(ASCE)ME.1943-5479.0000610.
[38] B. Bortoluzzi, I. Efremov, C. Medina, D. Sobieraj, J.J. McArthur, Automating the
creation of building information models for existing buildings, Autom. Constr. 105
(2019) 102838, , https://doi.org/10.1016/j.autcon.2019.102838.
[39] M. Kassem, G. Kelly, N. Dawood, M. Serginson, S. Lockley, BIM in facilities man-
agement applications: a case study of a large university complex, Built Environ.
Proj. Asset Manag. 5 (3) (2015) 261–277, https://doi.org/10.1108/BEPAM-02-
17
Automation in Construction 118 (2020) 103275
2014-0011.
[40] Y.C. Su, Y.C. Lee, Y.C. Lin, Enhancing maintenance management using building
information modeling in facilities management, Proceedings of the 28th
International Symposium on Automation and Robotics in Construction (ISARC),
Seoul, Korea, 2011, pp. 752–757, , https://doi.org/10.22260/isarc2011/0140.
[41] W. Chen, K. Chen, J.C.P. Cheng, Q. Wang, V.J.L. Gan, BIM-based framework for
automatic scheduling of facility maintenance work orders, Autom. Constr. 91
(2018) 15–30, https://doi.org/10.1016/j.autcon.2018.03.007.
[42] P. Pishdad-Bozorgi, X. Gao, C. Eastman, A.P. Self, Planning and developing facility
management-enabled building information model (FM-enabled BIM), Autom.
Constr. 87 (2018) 22–38, https://doi.org/10.1016/j.autcon.2017.12.004.
[43] R. Vanlande, C. Nicolle, C. Cruz, IFC and building lifecycle management, Autom.
Constr. 18 (1) (2008) 70–78, https://doi.org/10.1016/j.autcon.2008.05.001.
[44] S. Kouhestani, M. Nik-Bakht, IFC-based process mining for design authoring,
Autom. Constr. 112 (2020) 103069, , https://doi.org/10.1016/j.autcon.2019.
103069.
[45] M.A. Hassanain, T.M. Froese, D.J. Vanier, Development of a maintenance man-
agement model based on IAI standards, Artif. Intell. Eng. 15 (2) (2001) 177–193,
https://doi.org/10.1016/S0954-1810(01)00015-2.
[46] F. Shalabi, Y. Turkan, IFC BIM-based facility management approach to optimize
data collection for corrective maintenance, J. Perform. Constr. Facil. 31 (1) (2016)
04016081, , https://doi.org/10.1061/(ASCE)CF.1943-5509.0000941.
[47] J. Patacas, N. Dawood, D. Greenwood, M. Kassem, Supporting building owners and
facility managers in the validation and visualisation of asset information models
(aim) through open standards and open technologies, J. Inf. Technol. Constr. 21
(2016) 434–455 https://www.itcon.org/2016/27 (ISSN 18744753).
[48] A. Motamedi, M.M. Soltani, S. Setayeshgar, A. Hammad, Extending IFC to in-
corporate information of RFID tags attached to building elements, Adv. Eng. Inform.
30 (1) (2016) 39–53, https://doi.org/10.1016/j.aei.2015.11.004.
[49] K. Kim, H. Kim, W. Kim, C. Kim, J. Kim, J. Yu, Integration of ifc objects and facility
management work information using Semantic Web, Autom. Constr. 87 (2018)
173–187, https://doi.org/10.1016/j.autcon.2017.12.019.
[50] D. Pati, C.S. Park, G. Augenbroe, Facility maintenance performance perspective to
target strategic organizational objectives, J. Perform. Constr. Facil. 24 (2) (2009)
180–187, https://doi.org/10.1061/(asce)cf.1943-5509.0000070.
[51] S. Bruno, M. De Fino, F. Fatiguso, Historic Building Information Modelling: per-
formance assessment for diagnosis-aided information modelling and management,
Autom. Constr. 86 (2018) 256–276, https://doi.org/10.1016/j.autcon.2017.11.
009.
[52] J. Wu, M.D. Lepech, Incorporating multi-physics deterioration analysis in building
information modeling for life-cycle management of durability performance, Autom.
Constr. 110 (2020) 103004, , https://doi.org/10.1016/j.autcon.2019.103004.
[53] E.W. East, C. Bogen, A domain-independent facility control framework, in: R. Issa,
S. Olbina (Eds.), Building Information Modeling: Applications and Practices,
American Society of Civil Engineers, Reston, VA, USA, 2015, pp. 305–328.
[54] Y. Arayici, T. Fernando, V. Munoz, M. Bassanino, Interoperability specification
development for integrated BIM use in performance based design, Autom. Constr.
85 (2018) 167–181, https://doi.org/10.1016/j.autcon.2017.10.018.
[55] S. Tang, D.R. Shelden, C.M. Eastman, P. Pishdad-Bozorgi, X. Gao, BIM assisted
Building Automation System information exchange using BACnet and IFC, Autom.
Constr. 110 (2020) 103049, , https://doi.org/10.1016/j.autcon.2019.103049.
[56] C.M. Eastman, P. Teicholz, R. Sacks, K. Liston, BIM Handbook: A Guide to Building
Information Modeling for Owners, Managers, Designers, Engineers, and
Contractors, John Wiley & Sons, Hoboken, NJ, USA, 2008 ISBN: 0470541377,
9780470541371.
[57] Slingshot! for Dynamo, Available at https://dynamobim.org/slingshot-for-dynamo/
, Accessed date: 5 January 2020.
[58] What is SQLite? Available at https://www.sqlite.org/index.html , Accessed date: 5
January 2020.
[59] Issues with Dynamo-MySQL connection, Available at https://forum.dynamobim.
com/t/issues-with-dynamo-mysql-connection/43876 , Accessed date: 5 January
2020.
[60] Uniclass, Available at https://www.thenbs.com/our-tools/uniclass-2015, (2015) ,
Accessed date: 5 January 2020.