<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta>
      <journal-title-group>
        <journal-title>A. D. Palihakkara);</journal-title>
      </journal-title-group>
    </journal-meta>
    <article-meta>
      <title-group>
        <article-title>Ontology-Based Construction Progress Monitoring: A Conceptual Framework</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Asha Dulanjalie Palihakkara</string-name>
          <email>asha.palihakkara@nottingham.ac.uk</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Carlos Osorio-Sandoval</string-name>
          <email>carlos.osorio@nottingham.ac.uk</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Walid Tizani</string-name>
          <email>walid@tizani.co.uk</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Zigeng</string-name>
          <email>zigeng.fang@nottingham.ac.uk</email>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>University of Nottingham</institution>
          ,
          <addr-line>Nottingham, NG7 2RD</addr-line>
          ,
          <country country="UK">United Kingdom</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2025</year>
      </pub-date>
      <volume>000</volume>
      <fpage>0</fpage>
      <lpage>0002</lpage>
      <abstract>
        <p>Progress monitoring is a vital process in construction projects. With technological advancement and BIM implementation, there is a greater tendency towards automating the process, with many studies being carried out on automated progress detection and monitoring. However, most of these studies are conducted in isolation using a single or a fusion of several data-capturing techniques without giving proper attention to the interoperability of heterogeneous data generated throughout the construction process through multiple facets. Therefore, this study presents a conceptual framework for an ontology-based construction progress monitoring system through the fusion of heterogeneous data generated by multiple facets of construction. The proposed framework comprises a six-layered architecture comprised of data acquisition, integration, ontology, analytics, backend and frontend layers. The framework proposes a modular ontology design comprising five domain-based modules, such as product, process, resource, schedule, and data, which are integrated into a core module, forming a knowledge base. This study presents preliminary findings from an ongoing research study, with the proposed framework set to be tested and validated in future work.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;Ontology</kwd>
        <kwd>construction progress monitoring</kwd>
        <kwd>semantic web</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        Progress monitoring is a fundamental aspect of construction project management, which ensures
that as-built progress aligns with the as-planned schedule [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. Over the years, many researchers have
attempted to utilise emerging field data acquisition technologies to automate progress monitoring
by adopting a single technology or combining several technologies [
        <xref ref-type="bibr" rid="ref3 ref4">3,4</xref>
        ]. Technologies such as Laser
[
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. These technologies, together with Scan-to-BIM (Building Information Modelling), provide a
visual and thorough evaluation of the as-built condition of construction projects, enabling efforts to
enhance overall project performance [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ].
      </p>
      <p>
        However, the existing attempts at automated progress monitoring have primarily aimed at merely
providing the physical progress of the site using a single or fusion of vision or laser-based data
capturing methods without giving proper consideration to other data sources such as materials,
labour, resources, etc. Throughout the whole construction period, the progress monitoring process
should be conducted by collecting, recording and reporting information related to one or more facets
of project performance by identifying progress discrepancies and allowing the project management
team to initiate corrective measures promptly [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. Thus, there should be a mechanism to integrate
these heterogeneous data formats to provide a meaningful output [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ].
      </p>
      <p>
        One of the primary obstacles in automated progress monitoring is the interoperability challenges
caused by the use of different data [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. When considering progress monitoring, data should be
collected from numerous domains. A reliable progress monitoring system has to possess the capacity
to offer an efficient and effective way of assessing, acquiring, verifying, and quantifying as-built data
indicating the progress in terms of cost, schedule, resources, procurement, and quality [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. Further,
the authors emphasised that the system should be capable of detecting and analysing critical
information from a given progress scenario. Moreover, the system must deliver the analysed data in
a timely manner, in a format that can be best interpreted by management, and at a suitable level of
detail, to ensure corrective measures can be initiated on the progress scenario that produced the data
in the initial instance.
      </p>
      <p>
        Linked Data technologies have the potential to create an open and collaborative environment for
sharing, integrating, and linking data from many domains and data sources [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. The concept of the
Semantic Web lies behind the linked data concept, which is the creation of a web of data with the
help of data schemas termed ontologies [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ]. Several researchers have attempted to utilise semantic
web technologies and ontologies for construction management use cases [
        <xref ref-type="bibr" rid="ref10 ref11 ref7">10, 7, 11</xref>
        ]; however, these
studies lack a comprehensive framework to monitor progress by integrating multi-faceted data. To
fill this gap, this study focuses on introducing a conceptual framework for construction progress
monitoring that integrates heterogeneous construction data using an ontology-based approach. This
paper presents the rationale behind formulating the conceptual framework, proposed system
architecture and its key components.
      </p>
      <p>Compared to the existing methods, which mainly focus on progress monitoring through visual
capture technologies, this study presents a conceptual framework that integrates multi-faceted
construction data. This includes both planning and as-built data derived from BIM models, schedules,
construction resources, physical progress through visual captures, event logs, etc., to ensure a
comprehensive progress assessment. The novelty of this study lies in leveraging semantic web
technologies and linked data for data fusion and automated progress inference, offering a structured,
interoperable and scalable approach for progress monitoring.</p>
      <p>Following the introduction section, this paper is structured to provide an overview of the current
research on automated construction progress monitoring and the application of semantic web
technologies for construction management. It then proposes a conceptual framework for
ontologybased construction progress monitoring. Finally, the paper highlights the key findings and explores
future research directions.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Background</title>
      <sec id="sec-2-1">
        <title>2.1. Automated Construction Progress Monitoring</title>
        <p>
          Construction projects that fall behind time and have disparities between the as-built and intended
baseline plans are both undesirable situations that might frequently occur [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ]. Thus, real-time
progress monitoring and tracking of building components is still crucial to managing projects and is
key to meeting project objectives. Numerous studies have been conducted to examine the possibility
of using advanced technologies, such as LS, GPS, RFID, and UWB, in the construction industry [
          <xref ref-type="bibr" rid="ref12">12</xref>
          ].
Furthermore, several researchers have deployed a fusion of two or more data capture techniques.
        </p>
        <p>
          A key observation in existing research on automated progress monitoring is the predominant
focus on using object detection; while useful, it limits the ability to provide meaningful insights into
the construction status and for informed decision-making. Progress monitoring through visual
capture technologies can mainly be categorised into two methods as occupancy-based and
appearance-based approaches [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ]. The occupancy-based approach depends on geometric modelling
and is less effective in tracking non-geometrically modelled activities. Studies such as [
          <xref ref-type="bibr" rid="ref14 ref15 ref16">14, 15, 16</xref>
          ],
etc., have utilised this approach. In contrast, the appearance-based method detects visual
features/characteristics of construction tasks using image data. Several studies have adopted the
appearance-based approach, including those by [
          <xref ref-type="bibr" rid="ref17">17</xref>
          ] and [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ]. Depending solely on these techniques
limits progress monitoring to binary assessment of building elements [
          <xref ref-type="bibr" rid="ref13">13</xref>
          ]. Moreover, studies on
providing percentage completion are limited, and the integration of construction schedules is
scarcely explored. Therefore, significant advancements are required to enhance and optimise these
approaches. Additionally, existing research on vision-based monitoring often lacks semantic depth
[
          <xref ref-type="bibr" rid="ref19">19</xref>
          ]. Here, the primary focus has been on object detection with limited attention on capturing
meaningful relationships and dependencies between the objects, activities and workflows. Moreover,
detecting objects and activities alone is insufficient for comprehensive progress monitoring [
          <xref ref-type="bibr" rid="ref18">18</xref>
          ].
Furthermore, there are numerous other means of capturing progress-related data in a construction
site except for visual capture methods such as material utilisation, labour utilisation, inspection
reports, event logs, schedules etc. Therefore, to provide a more accurate and comprehensive
representation of project progress, a monitoring system should be capable of integrating data from
multiple domains and facets.
        </p>
        <p>
          The dynamic nature of construction projects and varied data inflows from multiple stakeholders
representing different domains, tools and workflows make automated progress monitoring complex
[
          <xref ref-type="bibr" rid="ref7">7</xref>
          ]. Moreover, construction projects generate a vast amount of textual and numeric data in terms of
event logs, reports, material delivery schedules, etc., which contributes to a holistic understanding
of the project status. Furthermore, due to issues such as erroneous data, missing data, undetected
activities, etc., it becomes challenging to derive insights into project status. Rule-based reasoning and
inferencing mechanisms can be incorporated to address these gaps and limitations while providing
accurate and reliable progress estimation [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ]. Furthermore, without a comprehensive semantic
representation of construction progress, it is difficult to enable automated reasoning, integration
with other domains, and intelligent decision-making [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ]. Integrating data from every facet of
construction assists in precise situational awareness, which is mandatory for effective production
planning and control to ensure efficient allocation of resources and input flow management [
          <xref ref-type="bibr" rid="ref21">21</xref>
          ].
        </p>
        <p>Therefore, this study aims to bridge these gaps by introducing a conceptual framework for
ontology-based progress monitoring that can semantically represent construction progress, integrate
heterogeneous data sources, and infer progress insights dynamically. By leveraging Semantic Web
technologies, this system can overcome interoperability issues and provide a unified,
machinereadable representation of progress data, ensuring seamless integration with existing BIM and
project management systems.</p>
      </sec>
      <sec id="sec-2-2">
        <title>2.2. Semantic Web and Construction Monitoring</title>
        <p>
          The Semantic Web standards lay a solid basis for interoperability in the construction industry,
necessitating networked data [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ]. Furthermore, data is made machine-readable and
machineinterpretable when ontologies are used. The concept of the Semantic Web allows various domains
engaged in AEC projects to semantically represent building information on a specific entity in a
manner that could be integrated with data from other domains [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ]. Over the last decade, the digital
project model and model interchange formats have been the objects of study and standardisation,
with the Industry Foundation Classes (IFC) schema at the heart of interoperability and supporting
project stakeholder engagement [
          <xref ref-type="bibr" rid="ref22">22</xref>
          ]. Nonetheless, this could be inadequate when formalising
complicated socio-technical systems, which require the incorporation of different hardware,
software, stakeholders, and wider community traits [
          <xref ref-type="bibr" rid="ref23">23</xref>
          ]. Furthermore, according to [
          <xref ref-type="bibr" rid="ref24">24</xref>
          ] three major
benefits of applying the Semantic Web: interoperability, linking across domains, and logical
inference and proofs.
        </p>
        <p>
          There are numerous efforts made by a number of researchers across multiple domains in the
construction industry, such as construction information extraction from BIM models [
          <xref ref-type="bibr" rid="ref25">25</xref>
          ], cost
estimation [
          <xref ref-type="bibr" rid="ref26">26</xref>
          ], compliance checking [
          <xref ref-type="bibr" rid="ref27">27</xref>
          ], etc. These studies demonstrate the potential of
incorporating semantic web technologies and linked data for construction industry-related
operations. One of the major milestones in ontology research in construction is the formulation of
the ifcOWL ontology. Building upon this foundational work of [
          <xref ref-type="bibr" rid="ref28 ref29">28, 29</xref>
          ], [
          <xref ref-type="bibr" rid="ref30">30</xref>
          ] executed a direct
mapping of the Express schema to OWL, producing the ifcOWL ontology. However, the ifcOWL
ontology comprises two main limitations: 1.) complicated structure providing implications such as
inefficiency in the reasoning process, unmanageable nature, and difficulties in understanding the
ontology, 2.) large size hampering its extensibility and modularity [31]. While providing a solution
for this issue, the Linked Building Data (LBD) Community Group of the World Wide Web
Consortium (W3C) has developed several lightweight ontologies such as BOT, PRODUCT, PROP,
etc. Among these, BOT focuses on representing topological relationships between elements.
Furthermore, DiCon is a suite of ontologies that aims to provide a high-level representation of
construction workflows by integrating heterogeneous data from different information and
communication technology (ICT) platforms [
          <xref ref-type="bibr" rid="ref20">20</xref>
          ]. Moreover, ontologies like SSN for sensor networks
and QUDT for quantities and measurements can be further incorporated in expanding the domains
covered by ontologies primarily focusing on the construction industry.
        </p>
        <p>Despite the availability of multiple ontologies, the AEC industry faces a major challenge in
ontology adoption. The overlapping scopes of various ontologies often result in fragmented and
inconsistent data models, slowing down the widespread adoption of Semantic Web technologies. For
construction progress monitoring, selecting the most suitable ontology is critical to ensuring data
integration, reasoning efficiency, and interoperability across systems. In lieu of developing new
redundant ontologies, researchers have to prioritise reusing existing ontologies, which are accepted
by a wide range of communities. In compliance with this approach, this study leverages and extends
existing ontologies while ensuring interoperability with widely accepted ontologies. The proposed
ontology-based progress monitoring framework is designed to acquire, manage and semantically
integrate heterogeneous as-planned and as-built data for more efficient construction progress
monitoring. The ontology-driven data fusion framework proposed in this study addresses the gaps
in multi-source data integration and reasoning, ensuring automated progress tracking, compliance
analysis, and decision support. The following sections will detail the ontology development process
and the proposed framework for construction progress monitoring.</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. Proposed Framework</title>
      <sec id="sec-3-1">
        <title>3.1. Construction Progress Monitoring Expert System</title>
        <p>
          A reliable progress monitoring system has to offer an efficient and effective way of assessing,
acquiring, verifying, and quantifying as-built data indicating the progress in terms of cost, schedule,
resources, procurement, and quality [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ]. Further, the system should detect and analyse critical
information from a given progress scenario. Moreover, the system must deliver the analysed data to
managers and executives on time, in a format that can be best interpreted by management, and at a
suitable level of detail for the people who will be using it, to ensure corrective measures can be
initiated on the progress scenario that produced the data in the initial instance. Therefore, the
following sections describe the key considerations taken during the formulation of the proposed
conceptual framework.
        </p>
      </sec>
      <sec id="sec-3-2">
        <title>3.1.1. Key Considerations for System Design</title>
        <p>This section represents key considerations when designing the progress monitoring system.
</p>
        <sec id="sec-3-2-1">
          <title>Physical Progress</title>
          <p>
            The system should be capable of representing physical progress and visualising it by
superimposing the as-built model over the as-planned model [
            <xref ref-type="bibr" rid="ref13">13</xref>
            ]. Here, the progress related to
construction elements is displayed colour-coded. Furthermore, physical progress should be
represented with element IDs, locations, quantities and associated tasks, subtasks, dependencies,
prerequisites, and resources.
          </p>
        </sec>
        <sec id="sec-3-2-2">
          <title>Compliance with the Schedule</title>
          <p>Determining whether the project is progressing according to the as-planned schedule and
whether there are any deviations from the original schedule in terms of being behind or ahead of the
schedule [32]. Furthermore, the system should be capable of determining whether key milestones in
the project are met or not and identifying reasons for non-compliance to the schedule.
</p>
        </sec>
        <sec id="sec-3-2-3">
          <title>Inspections and Formalities</title>
          <p>When performing the progress in a construction site, construction managers are required to
perform various tasks and procedures for inspection reports, defects identification, risk
identification, etc., including evidence such as photographs, videos, reports, required data, etc and
generating approvals for inspection reports. The system should integrate these compliance-related
activities, providing automated approvals for inspection reports and ensuring that necessary
corrective measures are initiated when required.</p>
          <p></p>
        </sec>
        <sec id="sec-3-2-4">
          <title>Progress Analysis and Report Generation</title>
          <p>To facilitate data-driven decision-making, the system must be capable of generating structured
reports and visual analytics [10; 32]. This includes tracking key performance indicators (KPIs) and
presenting insights through graphs, charts, tables, and a 3D visualisation model. By superimposing
as-planned and as-built BIM models, stakeholders can assess near real-time or weekly progress in a
more intuitive and interactive manner.</p>
        </sec>
      </sec>
      <sec id="sec-3-3">
        <title>3.1.2. System Design Features</title>
        <p>Building on the key considerations, the following design features have been identified to enhance
the functionality and usability of the proposed framework.</p>
        <sec id="sec-3-3-1">
          <title>Near real-time tracking (weekly update frequencies)</title>
          <p>Ability to be a single source of truth to get the most accurate progress insights through data
integration.</p>
          <p>
            Ability to be used collaboratively [
            <xref ref-type="bibr" rid="ref22">22</xref>
            ]
Considerations on the granularity level of the system
Clear visual representation of the progress [32]
Proper analytical representation of the progress [
            <xref ref-type="bibr" rid="ref10">10</xref>
            ]
Capability of tracking activities within the site [
            <xref ref-type="bibr" rid="ref13">13</xref>
            ]
Capability of generating progress reports
Assisting in look-ahead planning based on progress data [
            <xref ref-type="bibr" rid="ref11">11</xref>
            ]
          </p>
          <p>
            Actual vs Planned dashboard representation [
            <xref ref-type="bibr" rid="ref10">10</xref>
            ]
          </p>
        </sec>
      </sec>
      <sec id="sec-3-4">
        <title>3.1.3. System Use Cases</title>
        <p>In line with the overarching aim and objectives of the study of formulating a construction progress
monitoring framework that integrates heterogeneous data sources to support project stakeholders
in making informed decisions and timely actions, the proposed framework should cater to the
following use cases.</p>
        <p>










</p>
        <p>Integration of heterogeneous data sources for informed and data decision-making, enabling
a holistic representation of the construction progress.</p>
        <p>Assessment of the construction progress and performance to determine the adherence to
asplanned workflow through key performance indicators (KPIs).</p>
        <p>Monitoring the adherence to the as-planned schedule and assisting in generating future
schedules and LookAhead plans.</p>
      </sec>
      <sec id="sec-3-5">
        <title>3.1.4. System Architecture</title>
        <p>The proposed ontology-based construction progress monitoring follows a six-layered system
architecture focusing on data acquisition, integration, processing, storing, and visualisation. At the
heart of the proposed system lies an ontology layer developed following a modular ontology
development workflow. Each layer of the proposed framework serves a distinct purpose, as
illustrated below in Figure 1.</p>
        <sec id="sec-3-5-1">
          <title>Data Acquisition Layer</title>
          <p>The data acquisition layer focuses on collecting both planning and construction data. These data are
collected from various means and streams such as BIM models, schedules, visual captures, event logs,
external conditions such as weather, etc. This layer will ensure a continuous inflow of near real-time
data crucial for status monitoring.</p>
        </sec>
        <sec id="sec-3-5-2">
          <title>Data Integration Layer</title>
          <p>The data integration layer focuses on the semantic enrichment of incoming data and converting
those into RDF format. This will ensure the data are mapped with the developed ontology framework
for the data fusion and reasoning process. Moreover, SHACL-based data validation will be conducted
to ensure integrity. While the proposed framework accommodates visual captures as inputs, it does
not currently include object and activity detection within its framework. Thus, the proposed
framework will rely on pre-processed visual data. The integration of object detection capabilities will
be explored in future research.
This layer defines the semantic structure and relationships within the construction project’s domain,
facilitating interoperability and data fusion across heterogeneous data sources. The ontology will be
developed using the Protégé ontology editor, encompassing classes, properties and constraints that
represent building elements, tasks, resources, and data streams. The proposed ontology design takes
a modular approach and will be extended and mapped with established industry standard ontologies
such as ifcOWL, BOT, QUDT, DiCon, BFO, etc. Furthermore, this layer will serve as the backbone
for knowledge graph generation, supporting SPARQL queries and reasoning.</p>
        </sec>
        <sec id="sec-3-5-3">
          <title>Analytics Layer 5.</title>
        </sec>
        <sec id="sec-3-5-4">
          <title>Backend Service Layer</title>
          <p>The analytics layer focuses on conducting semantic reasoning, compliance checking, progress
estimation and KPI calculations to provide insights into the status of construction. Moreover, this
layer will execute SWRL rules and OWL reasoning to infer missing information and violations.
This layer focuses on data strategy, management, retrieval and API request handling. This will be
developed using frameworks such as Flask to host RESTful APIs for data manipulation, integration
and retrieval; Apache Jena Fuseki triple store will be used as the triple store and SPARQL query
execution will be handled in here.</p>
        </sec>
        <sec id="sec-3-5-5">
          <title>6. Frontend Services Layer and User Interface</title>
          <p>This layer provides interfaces and visualisation tools to interact with the stakeholders and interpret
construction progress data effectively. Unity Engine will be utilised for 3D visualisation by
overlaying the as-built model on an as-planned model. The dashboard created using AngularJS will
illustrate the progress reports, graphs and KPIs.</p>
          <p>The proposed architectural framework will be utilised in progress monitoring through the
integration of diverse data sources, efficient data handling and to provide data driven insights into
the status and progress of the project through a visualisation tool. Upon the development of the
prototype application, this will be tested and validated through a case study.</p>
        </sec>
      </sec>
      <sec id="sec-3-6">
        <title>3.2. Ontology Development</title>
        <p>For this study METHONTOLOGY ontology development approach was selected [33]. This ontology
development approach consists of several phases, as illustrated in Figure 2 below.</p>
      </sec>
      <sec id="sec-3-7">
        <title>3.2.1. Purpose and Scope</title>
        <p>
          A clear definition of requirements, such as its purpose, scope and end users, should be identified to
develop an ontology [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ]. These requirements create the pathway for determining concepts,
relationships, and reasoning rules [34]. Therefore, the purpose, scope and end users for the proposed
ontology framework are as follows;



        </p>
        <p>Purpose: Facilitate automated construction progress monitoring through the integration of
heterogeneous data sources, enabling interoperability and semantic reasoning. The ontology
will assist in determining project progress in near real-time (with weekly update frequency)
by comparing as-planned data with as-built data to provide insights on physical progress,
schedule compliance, milestone achievements, etc.</p>
        <p>Scope: Data integration in timely manner and construction activity representation, mapping
tasks, dependencies and resource requirements.</p>
        <p>End users: This includes construction managers, site engineers, quantity surveyors, and
project stakeholders who require accurate and timely insights into construction progress,
schedule adherence, and resource availability. By leveraging ontology-driven reasoning, the
system provides stakeholders with automated compliance checks, alerts for deviations, and
decision support.</p>
        <p>Competency questions can be formulated in line with the identified purpose, scope and end users
of the ontology [35]. These competency questions provide detailed insights into the ontology
requirements, assisting in the ontology modelling process. The competency questions relevant to the
study are listed below in Table 1.</p>
        <sec id="sec-3-7-1">
          <title>What is the considered progress period?</title>
          <p>What are the expected tasks, associated building elements, and scheduled task durations for
the considered progress period?
What are the prerequisites associated with planned tasks?
Does the task belong to the critical path, and its completion corresponds to a milestone
accomplishment?
What data captures available for the considered progress period?
What metadata is associated with each data capture?
Information regarding what tasks and building elements are available in the data captures?
What different data sources provide information about the same entity during the same
period?
What is the current progress of the tasks and building elements scheduled for the considered
progress period?</p>
          <p>What tasks show delays and causes for delays?</p>
        </sec>
      </sec>
      <sec id="sec-3-8">
        <title>3.2.2. Ontology Development – Modular Approach</title>
        <p>Followed by the specification phase, the next phase is the conceptualisation where all the necessary
terms, concepts, class hierarchy and properties are formulated to construct the ontological model
[35]. The industry is evolving towards modular, domain-specific ontologies rather than depending
on single, comprehensive or monolithic models to capture the full building lifecycle [35]. This
modular approach enables each module to be independently extended or integrated, promoting
flexibility, reusability, and collaboration within construction data management. The proposed
ontology system of this study comprises five domain-specific modules and a core module that
integrates them into a comprehensive knowledge framework. The ontology development process
was conducted using the Protégé ontology developer. A brief overview of the modules that comprise
the proposed ontology system is provided below;





</p>
        <p>OntoProduct (Product Module): Represents physical and spatial components in a
construction project, including building elements, materials, and site structures. This module
extends the BOT ontology.</p>
        <p>OntoProcess (Process Module): Defines construction workflows, task dependencies, and
execution sequences.</p>
        <p>OntoResource (Resource Module): Represents labour, equipment, and materials used in
construction.</p>
        <p>OntoSchedule (Schedule Module): Handles scheduling concepts, milestones, and timeline
constraints.</p>
        <p>OntoData (Data Module): Focuses on data acquisition, management, and near real-time
monitoring.</p>
        <p>OntoPMS (Core Module): Integrates all other modules, providing logical axioms, reasoning
rules, and cross-domain relationships for progress monitoring.</p>
        <p>Figure 3 illustrates the modular approach adopted in this study. Furthermore, it should be noted
that due to its iterative nature, the proposed ontology model is still under development and will be
tested and validated in the future.</p>
      </sec>
      <sec id="sec-3-9">
        <title>3.2.3. Semantic Reasoning</title>
        <p>A key advantage of the ontology-based framework is its ability to infer new knowledge using
semantic reasoning. This layer represents validation, constraints and query rules in a
machineinterpretable language [36]. By leveraging reasoning engines such as Pellet and HermiT, and rule
languages such as SWRL, axioms and queries through SPARQL and SHACL, the ontology supports:

</p>
        <p>Schedule compliance checks, determining if the actual progress aligns with the planned
schedule.</p>
        <p>Progress estimation, inferring partially completed or undetected activities based on related
task dependencies.</p>
      </sec>
      <sec id="sec-3-10">
        <title>3.2.4. Ontology Alignment</title>
        <p>In compliance with the W3C best practice guideline, it is essential to map the developed ontology/s
with existing ontologies to enhance interoperability, data integration, semantic consistency, and
reuse of existing resources. The process of creating relations between terms (classes or properties)
and/or individuals from different ontologies is called an ontology alignment. Ontology alignments
can be conducted through three approaches, namely, checking terminology, internal structure, and
external structure. Currently, the developed ontologies are being mapped with existing standards
and domain ontologies, including ifcOWL (for BIM models), BOT (for building topology), and DiCon
(for construction workflows). Furthermore, alignments will be created with more high-level
ontologies such as BFO and PROV-O.</p>
      </sec>
      <sec id="sec-3-11">
        <title>3.2.5. Ontology Evaluation</title>
        <p>Ontologies can be evaluated both semantically and syntactically [37]. Currently, the syntactic
evaluation is conducted using the pellet reasoner. Furthermore, through a case study, the ontology
will be validated semantically to determine whether it provides answers to the competency questions
formulated during the ontology specification stage.</p>
      </sec>
      <sec id="sec-3-12">
        <title>3.2.6. Ontology Documentation</title>
        <p>When it comes to semantic web technology, interoperability and shared ontologies (ideally accessible
online) are crucial. This makes it possible for the applications used by different stakeholders to
reliably reuse the terminology in their own datasets and tools and to search for definitions of terms
in the datasets they have been given. Since the ontology development process is an iterative process,
the ontology is not currently documented online for users to see. However, upon the completion of
the development process, the ontologies are planned to be documented and published online.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Conclusions and Future Work</title>
      <p>This study presents a conceptual framework for ontology-based construction progress monitoring
through the fusion of heterogeneous data sources. The existing research lacks a comprehensive
framework for construction progress monitoring capable of handling multiple data sources and types
in a timely manner. The inclusion of an ontology layer and semantic web technologies provides a
solution to the long-standing issue of interoperability and linking across domains. Moreover, the
proposed data-driven semantic reasoning framework is intended to assist in timely interpretation of
acquired data and can be used as a decision support tool. By addressing data fragmentation and
interoperability challenges, this framework will assist in the digitalisation of the construction
progress monitoring, creating a pathway to more efficient, automated and intelligent information
systems. The ontology layer of the proposed framework comprises a modular architecture
comprising five domain-specific modules and a core ontology that integrates those modules and
forms a knowledge base. Furthermore, alignments and mappings will be made with
industrystandard ontologies such as ifcOWL, BOT, DiCON, BFO, etc., to achieve seamless data integration
and interoperability. A key consideration when designing the proposed framework is to provide the
system with the ability to infer missing information using rule-based reasoning. By applying SWRL
rules and SPARQL queries, the system is expected to determine task prerequisites and schedule
adherence, reducing reliance on manual tracking and reporting.</p>
      <p>However, performing object and activity detection of visual progress captures such as images,
scans and videos is out of the scope of the proposed framework. Therefore, pre-processed visual data
will be utilised as inputs to the system, ensuring focus remains on integrating structured
objectdetected data with as-planned and as-built data. Moreover, the proposed framework attempts to link
data inputs with their corresponding construction activities, enabling reasoning-based progress
tracking, milestone verification and compliance analysis. Many improvements are essential for
further enhancement of the proposed framework in terms of scalability, accuracy and industry
adoption. The proposed framework will undergo testing, validation and continuous improvement.
Future research directions in par with this study could focus on integrating machine learning-driven
reasoning along with rule-based reasoning and inferencing. Furthermore, the framework could be
extended to areas such as delay prediction, anomaly detection, risk and safety management etc.</p>
    </sec>
    <sec id="sec-5">
      <title>Declaration on Generative AI</title>
      <p>During the preparation of this work, the author(s) used ChatGPT, Grammarly in order to: grammar
and spelling check, paraphrase and reword. After using this tool/service, the author(s) reviewed and
edited the content as needed and take(s) full responsibility for the publication’s content.
[31] M. H. Rasmussen, M. Lefrançois, G. Schneider, P. Pauwels, BOT: the Building Topology
Ontology of the W3C Linked Building Data Group, Semantic Web (2020).
doi:10.3233/SW-200385.
[32] V. K. Reja, K. Varghese, Q. P. Ha, Computer vision-based construction progress monitoring,</p>
      <p>Automation in Construction (2022). doi: 10.1016/j.autcon.2022.104245.
[33] M. Fernández-López, A Gómez-Pérez, N. Juristo, METHONTOLOGY : From Ontological Art
Towards Ontological Engineering, In Proceedings of the Fernández-López, Mariano et al.
“METHONTOLOGY: From Ontological Art Towards Ontological Engineering.” AAAI
Conference on Artificial Intelligence, 1997, 33–40.
[34] H. Pruvost, A. Wilde, O. Enge-Rosenblatt, Ontology-Based Expert System for Automated
Monitoring of Building Energy Systems, Journal of Computing in Civil Engineering (2023), 1–
11. doi:10.1061/(asce)cp.1943-5487.0001065.
[35] Y. Zheng, S. Törmä, O. Seppänen, A shared ontology suite for digital construction workflow,</p>
      <p>Automation in Construction (2021). doi:10.1016/j.autcon.2021.103930.
[36] L. Jia, Y. Jin, Y. Liu, J. Lv, Ontological Method for the Modeling and Management of Building
Component Construction Process Information, Buildings (2023).
doi:10.3390/buildings13082065.
[37] J. Zhang, N. El-Gohary, Automated Information Transformation for Automated Regulatory
Compliance Checking in Construction, Journal of Computing in Civil Engineering (2015).
doi:10.1061/(ASCE)CP.1943-5487.0000427.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>S.</given-names>
            <surname>Alizadehsalehi</surname>
          </string-name>
          ,
          <string-name>
            <surname>I.</surname>
          </string-name>
          <article-title>Yitmen, A Concept for Automated Construction Progress Monitoring: Technologies Adoption for Benchmarking Project Performance Control</article-title>
          ,
          <source>Arabian Journal for Science and Engineering</source>
          (
          <year>2018</year>
          ),
          <fpage>4993</fpage>
          -
          <lpage>5008</lpage>
          . doi:
          <volume>10</volume>
          .1007/s13369-018-3669-1.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>S.</given-names>
            <surname>Alizadehsalehi</surname>
          </string-name>
          ,
          <string-name>
            <surname>I. Yitmen</surname>
          </string-name>
          ,
          <source>The Impact of Field Data Capturing Technologies on Automated Construction Project Progress Monitoring</source>
          , Procedia
          <string-name>
            <surname>Engineering</surname>
          </string-name>
          (
          <year>2016</year>
          ),
          <fpage>97</fpage>
          -
          <lpage>103</lpage>
          . doi:
          <volume>10</volume>
          .1016/j.proeng.
          <year>2016</year>
          .
          <volume>08</volume>
          .504.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>K.</given-names>
            <surname>Asadi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Haritsa</surname>
          </string-name>
          , K. Han,
          <string-name>
            <given-names>J. P.</given-names>
            <surname>Ore</surname>
          </string-name>
          ,
          <article-title>Automated Object Manipulation Using Vision-Based Mobile Robotic System for Construction Applications</article-title>
          ,
          <source>Journal of Computing in Civil Engineering</source>
          (
          <year>2021</year>
          ). doi:
          <volume>10</volume>
          .1061/(ASCE)CP.
          <fpage>1943</fpage>
          -
          <volume>5487</volume>
          .
          <fpage>0000946</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>Z.</given-names>
            <surname>Pučko</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Šuman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Rebolj</surname>
          </string-name>
          ,
          <article-title>Automated continuous construction progress monitoring using multiple workplace real time 3D scans, Advanced Engineering Informatics (</article-title>
          <year>2018</year>
          ),
          <fpage>27</fpage>
          -
          <lpage>40</lpage>
          . doi:
          <volume>10</volume>
          .1016/j.aei.
          <year>2018</year>
          .
          <volume>06</volume>
          .001
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>F.</given-names>
            <surname>Bosché</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Ahmed</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Turkan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C. T.</given-names>
            <surname>Haas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Haas</surname>
          </string-name>
          ,
          <article-title>The value of integrating Scan-to-BIM and Scan-vs-BIM techniques for construction monitoring using laser scanning and BIM: The case of cylindrical MEP components, Automation in Construction (</article-title>
          <year>2015</year>
          ),
          <fpage>201</fpage>
          -
          <lpage>213</lpage>
          . doi:
          <volume>10</volume>
          .1016/j.autcon.
          <year>2014</year>
          .
          <volume>05</volume>
          .014.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>M.</given-names>
            <surname>Golparvar-Fard</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Peña-Mora</surname>
          </string-name>
          , S. Silvio,
          <article-title>D4AR-A 4-dimensional augmented reality model for automating construction progress monitoring data collection, processing</article-title>
          and communication,
          <source>Electronic Journal of Information Technology in Construction (</source>
          <year>2009</year>
          ),
          <fpage>129</fpage>
          -
          <lpage>153</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>J.</given-names>
            <surname>Schlenger</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Yeung</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Vilgertshofer</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Martinez</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Sacks</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Borrmann</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A Comprehensive</given-names>
            <surname>Data</surname>
          </string-name>
          <article-title>Schema for Digital Twin Construction</article-title>
          ,
          <source>In Proceedings of the 29th International Workshop on Intelligent Computing in Engineering</source>
          , Aarhus, Denmark,
          <year>2022</year>
          . doi:
          <volume>10</volume>
          .7146/aul.455.
          <year>c194</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>M.</given-names>
            <surname>Niknam</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Karshenas</surname>
          </string-name>
          ,
          <article-title>A shared ontology approach to semantic representation of BIM data, Automation in Construction (</article-title>
          <year>2017</year>
          ),
          <fpage>22</fpage>
          -
          <lpage>36</lpage>
          . doi:
          <volume>10</volume>
          .1016/j.autcon.
          <year>2017</year>
          .
          <volume>03</volume>
          .013
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <given-names>C.</given-names>
            <surname>Zhang</surname>
          </string-name>
          , J. Beetz,
          <article-title>Querying Linked Building Data Using SPARQL with Functional Extensions</article-title>
          , in: S. Christodoulou, R. Scherer (Eds.),
          <source>eWork and eBusiness in Architecture, Engineering and Construction: ECPPM</source>
          <year>2016</year>
          , 1st. ed. CRC Press, London,
          <year>2016</year>
          , doi:10.1201/9781315386904.
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <given-names>K.</given-names>
            <surname>Farghaly</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Soman</surname>
          </string-name>
          ,
          <string-name>
            <surname>J. Whyte,</surname>
          </string-name>
          <article-title>cSite ontology for production control of construction sites, Automation in Construction (</article-title>
          <year>2024</year>
          ). doi:
          <volume>10</volume>
          .1016/j.autcon.
          <year>2023</year>
          .105224
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>R. K.</given-names>
            <surname>Soman</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Molina-Solana</surname>
          </string-name>
          ,
          <article-title>Automating look-ahead schedule generation for construction using linked-data based constraint checking and reinforcement learning, Automation in Construction (</article-title>
          <year>2022</year>
          ). doi:
          <volume>10</volume>
          .1016/j.autcon.
          <year>2021</year>
          .104069
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [12]
          <string-name>
            <given-names>T.</given-names>
            <surname>Omar</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Nehdi</surname>
          </string-name>
          ,
          <article-title>Data acquisition technologies for construction progress tracking, Automation in Construction (</article-title>
          <year>2016</year>
          ),
          <fpage>143</fpage>
          -
          <lpage>155</lpage>
          . doi:
          <volume>10</volume>
          .1016/j.autcon.
          <year>2016</year>
          .
          <volume>06</volume>
          .016.
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [13]
          <string-name>
            <given-names>A.</given-names>
            <surname>Pal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. J.</given-names>
            <surname>Lin</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S. H.</given-names>
            <surname>Hsieh</surname>
          </string-name>
          ,
          <article-title>A Framework for Automated Daily Construction Progress Monitoring Leveraging Unordered Site Photographs</article-title>
          ,
          <source>In Proceedings of the ASCE International Conference on Computing in Civil Engineering</source>
          ,
          <year>2022</year>
          ,
          <fpage>538</fpage>
          -
          <lpage>545</lpage>
          . doi:
          <volume>10</volume>
          .1061/9780784483893.067.
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Turkan</surname>
          </string-name>
          ,
          <string-name>
            <surname>Y.</surname>
          </string-name>
          ,
          <string-name>
            <given-names>F.</given-names>
            <surname>Bosché</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C. T.</given-names>
            <surname>Haas</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R. C. G.</given-names>
            <surname>Haas</surname>
          </string-name>
          , R. C. G,
          <source>Automated Progress Tracking of Erection of Concrete Structures</source>
          ,
          <source>In Proceedings of the Annual Conference of the Canadian Society for Civil Engineering</source>
          , Ottawa, Canada,
          <year>2011</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>H.</given-names>
            <surname>Son</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Kim</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y. K.</given-names>
            <surname>Cho</surname>
          </string-name>
          ,
          <article-title>Automated Schedule Updates Using As-Built Data and a 4D Building Information Model</article-title>
          , Journal of Management in Engineering (
          <year>2017</year>
          ). doi:
          <volume>10</volume>
          .1061/(asce)me.
          <fpage>1943</fpage>
          -
          <volume>5479</volume>
          .
          <fpage>0000528</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [16]
          <string-name>
            <given-names>C.</given-names>
            <surname>Kim</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Kim</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Son</surname>
          </string-name>
          ,
          <article-title>Automated construction progress measurement using a 4D building information model and 3D data, Automation in Construction (</article-title>
          <year>2013</year>
          ),
          <fpage>75</fpage>
          -
          <lpage>82</lpage>
          . doi:
          <volume>10</volume>
          .1016/j.autcon.
          <year>2012</year>
          .
          <volume>11</volume>
          .041.
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [17]
          <string-name>
            <given-names>B. J.</given-names>
            <surname>Ekanayake</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. K. W.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A. A. F.</given-names>
            <surname>Fini</surname>
          </string-name>
          ,
          <string-name>
            <given-names>P.</given-names>
            <surname>Smith</surname>
          </string-name>
          ,
          <string-name>
            <given-names>V.</given-names>
            <surname>Thengane</surname>
          </string-name>
          ,
          <article-title>Deep learning-based computer vision in project management: Automating indoor construction progress monitoring</article-title>
          ,
          <source>Project Leadership and Society</source>
          (
          <year>2024</year>
          ). doi:
          <volume>10</volume>
          .1016/j.plas.
          <year>2024</year>
          .
          <volume>100149</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [18]
          <string-name>
            <surname>K. K. Han</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Golparvar-Fard</surname>
          </string-name>
          ,
          <article-title>Appearance-based material classification for monitoring of operation-level construction progress using 4D BIM and site photologs, Automation in Construction (</article-title>
          <year>2015</year>
          ),
          <fpage>44</fpage>
          -
          <lpage>57</lpage>
          . doi:
          <volume>10</volume>
          .1016/j.autcon.
          <year>2015</year>
          .
          <volume>02</volume>
          .007.
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [19]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Zheng</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M. K.</given-names>
            <surname>Masood</surname>
          </string-name>
          ,
          <string-name>
            <given-names>O.</given-names>
            <surname>Seppänen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Törmä</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Aikala</surname>
          </string-name>
          ,
          <article-title>Ontology-Based Semantic Construction Image Interpretation</article-title>
          ,
          <string-name>
            <surname>Buildings</surname>
          </string-name>
          (
          <year>2023</year>
          ). doi:
          <volume>10</volume>
          .3390/buildings13112812.
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          [20]
          <string-name>
            <given-names>A.</given-names>
            <surname>Peltokorpi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Y.</given-names>
            <surname>Zheng</surname>
          </string-name>
          ,
          <source>Digitalizing Construction Workflows ( DiCtion )</source>
          ,
          <year>2021</year>
          , URL: https://www.aalto.fi/sites/default/files/2021-03/DiCtion%20Final%
          <fpage>20report</fpage>
          .
          <source>pdf [Accessed: 7 Apr</source>
          .
          <year>2025</year>
          ].
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          [21]
          <string-name>
            <given-names>L.</given-names>
            <surname>Koskela</surname>
          </string-name>
          , G. Ballard, G. Howell,
          <string-name>
            <surname>I. Tommelein</surname>
          </string-name>
          ,
          <article-title>The foundations of lean construction</article-title>
          , in: R. Best, G. de Valence (Eds.), Design and Construction: Building in Value, Routledge, New York,
          <year>2002</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          [22]
          <string-name>
            <given-names>C.</given-names>
            <surname>Boje</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Veronika</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Guerriero</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Kubicki</surname>
          </string-name>
          , G. Halin,
          <article-title>Semantics for linking data from 4D BIM to digital collaborative support</article-title>
          .
          <source>Frontiers of Engineering Management</source>
          (
          <year>2020</year>
          ),
          <fpage>104</fpage>
          -
          <lpage>116</lpage>
          . doi:
          <volume>10</volume>
          .1007/s42524-020-0111-7.
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          [23]
          <string-name>
            <given-names>C.</given-names>
            <surname>Boje</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Kubicki</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Guerriero</surname>
          </string-name>
          , S. Thomas,
          <string-name>
            <surname>Aligning</surname>
            <given-names>IFC</given-names>
          </string-name>
          and
          <article-title>SRI domains for BIM supported SRI assessment</article-title>
          ,
          <source>In Proceedings of the 2022 IEEE 28th International Conference on Engineering, Technology and Innovation</source>
          (ICE/ITMC) &amp;
          <article-title>31st International Association For Management of Technology (IAMOT) Joint Conference</article-title>
          , Nancy, France, doi:10.1109/ICE/ITMCIAMOT55089.
          <year>2022</year>
          .
          <volume>10033263</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          [24]
          <string-name>
            <given-names>P.</given-names>
            <surname>Pauwels</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Krijnen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Terkaj</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J.</given-names>
            <surname>Beetz</surname>
          </string-name>
          ,
          <string-name>
            <surname>J</surname>
          </string-name>
          ,
          <article-title>Enhancing the ifcOWL ontology with an alternative representation for geometric data, Automation in Construction (</article-title>
          <year>2017</year>
          ),
          <fpage>77</fpage>
          -
          <lpage>94</lpage>
          . doi:
          <volume>10</volume>
          .1016/j.autcon.
          <year>2017</year>
          .
          <volume>03</volume>
          .001.
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          [25]
          <string-name>
            <given-names>M. P.</given-names>
            <surname>Nepal</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Staub-French</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Pottinger</surname>
          </string-name>
          ,
          <string-name>
            <surname>J. Zhang,</surname>
          </string-name>
          <article-title>Ontology-Based Feature Modeling for Construction Information Extraction from a Building Information Model</article-title>
          ,
          <source>Journal of Computing in Civil Engineering</source>
          (
          <year>2013</year>
          ),
          <fpage>555</fpage>
          -
          <lpage>569</lpage>
          . doi:
          <volume>10</volume>
          .1061/%28ASCE%
          <fpage>29CP</fpage>
          .
          <fpage>1943</fpage>
          -
          <volume>5487</volume>
          .
          <fpage>0000230</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref26">
        <mixed-citation>
          [26]
          <string-name>
            <given-names>S.</given-names>
            <surname>Lee</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.</given-names>
            <surname>Kim</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. H.</given-names>
            <surname>Yu</surname>
          </string-name>
          ,
          <article-title>BIM and ontology-based approach for building cost estimation, Automation in Construction (</article-title>
          <year>2014</year>
          ),
          <fpage>96</fpage>
          -
          <lpage>105</lpage>
          . doi:
          <volume>10</volume>
          .1016/j.autcon.
          <year>2013</year>
          .
          <volume>10</volume>
          .020.
        </mixed-citation>
      </ref>
      <ref id="ref27">
        <mixed-citation>
          [27]
          <string-name>
            <given-names>J.</given-names>
            <surname>Zhang</surname>
          </string-name>
          , N. El-Gohary,
          <source>Automated Information Transformation for Automated Regulatory Compliance Checking in Construction, Journal of Computing in Civil Engineering</source>
          (
          <year>2015</year>
          ). doi:
          <volume>10</volume>
          .1061/(ASCE)CP.
          <fpage>1943</fpage>
          -
          <volume>5487</volume>
          .
          <fpage>0000427</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref28">
        <mixed-citation>
          [28]
          <string-name>
            <given-names>J.</given-names>
            <surname>Beetz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. Van</given-names>
            <surname>Leeuwen</surname>
          </string-name>
          , B. De Vries,
          <article-title>IfcOWL: A case of transforming EXPRESS schemas into ontologies, Artificial Intelligence for Engineering Design, Analysis and Manufacturing (</article-title>
          <year>2009</year>
          ),
          <fpage>89</fpage>
          -
          <lpage>101</lpage>
          . doi:
          <volume>10</volume>
          .1017/S0890060409000122.
        </mixed-citation>
      </ref>
      <ref id="ref29">
        <mixed-citation>
          [29]
          <string-name>
            <given-names>J.</given-names>
            <surname>Beetz</surname>
          </string-name>
          ,
          <string-name>
            <given-names>J. P. van Leeuwen</given-names>
            ,
            <surname>B. de Vries</surname>
          </string-name>
          ,
          <article-title>An Ontology Web Language Notation of the Industry Foundation Classes</article-title>
          ,
          <source>In Proceedings of the 22nd CIB W78 Conference on Information Technology in Construction</source>
          ,
          <year>2005</year>
          ,
          <fpage>193</fpage>
          -
          <lpage>198</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref30">
        <mixed-citation>
          [30]
          <string-name>
            <given-names>P.</given-names>
            <surname>Pauwels</surname>
          </string-name>
          , W. Terkaj,
          <article-title>EXPRESS to OWL for construction industry: Towards a recommendable and usable ifcOWL ontology</article-title>
          , Automation in Construction (
          <year>2016</year>
          ),
          <fpage>100</fpage>
          -
          <lpage>133</lpage>
          . doi:
          <volume>10</volume>
          .1016/j.autcon.
          <year>2015</year>
          .
          <volume>12</volume>
          .003
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>