<!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 />
    <article-meta>
      <title-group>
        <article-title>AI-Agent Application for Semantic Data Enrichment in Ventilation Systems Using National Nomenclature for IFC and GS1-Based Product Information</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Otto Alhava</string-name>
          <email>otto.alhava@fira.fi</email>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Tommi Arola</string-name>
          <email>tommi.arola@rts.fi</email>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Osku Torro</string-name>
          <email>osku.torro@tuni.fi</email>
          <xref ref-type="aff" rid="aff4">4</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Markus Järvenpää</string-name>
          <email>markus.jarvenpaa@granlund.fi</email>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Tero Järvinen</string-name>
          <email>tero.jarvinen@granlund.fi</email>
          <xref ref-type="aff" rid="aff3">3</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Betti-</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>na Ruottinen</string-name>
          <email>bettina.ruottinen@aalto.fi</email>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Aalto University</institution>
          ,
          <addr-line>Rakentajanaukio 4, 02150 Espoo</addr-line>
          ,
          <country country="FI">Finland</country>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Building information foundation RTS sr</institution>
          ,
          <addr-line>Malminkatu 16 A, 00100 Helsinki</addr-line>
          ,
          <country country="FI">Finland</country>
        </aff>
        <aff id="aff2">
          <label>2</label>
          <institution>Fira Oy</institution>
          ,
          <addr-line>Teknobulevardi 3-5, 01530 Vantaa</addr-line>
          ,
          <country country="FI">Finland</country>
        </aff>
        <aff id="aff3">
          <label>3</label>
          <institution>Granlund Oy</institution>
          ,
          <addr-line>Malminkaari 21, 00701 Helsinki</addr-line>
          ,
          <country country="FI">Finland</country>
        </aff>
        <aff id="aff4">
          <label>4</label>
          <institution>Tampere University</institution>
          ,
          <addr-line>Kalevantie 4, 33100 Tampere</addr-line>
          ,
          <country country="FI">Finland</country>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2025</year>
      </pub-date>
      <fpage>193</fpage>
      <lpage>206</lpage>
      <abstract>
        <p>This study investigates the potential of AI agent systems to automate information management within the mechanical, electrical, and plumbing (MEP) construction process. Currently, building information model (BIM) data is often exchanged manually via 2D drawings and Excel spreadsheets, leading to significant discontinuities in information flow across the design, procurement, and construction phases. Based on a systematic identification of these discontinuities, a simulation was developed to evaluate the feasibility of AI agent-based automation. The results demonstrate that AI agents can effectively enrich and transform a machine-readable engineering bill of materials (E-BOM) into a structured manufacturing bill of materials (M-BOM). Owing to the standardized structure of Finnish MEP data, the solution is not limited to a single case but can be generalized across different MEP domains, enabling broader automation of data flows. These findings suggest that AI agents offer substantial potential as next-generation solutions for automating information workflows in construction.</p>
      </abstract>
      <kwd-group>
        <kwd>eol&gt;AI agents</kwd>
        <kwd>semantic enrichment</kwd>
        <kwd>BIM</kwd>
        <kwd>IFC</kwd>
        <kwd>MEP</kwd>
        <kwd>E-BOM</kwd>
        <kwd>M-BOM</kwd>
        <kwd>GS1-standards</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        The construction industry significantly lags behind other sectors in both digitalisation [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ], [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] and
industrialisation [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], resulting in fragmented information scattered across systems and files. These
silos are reinforced by disjointed business models [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], which hinder the transfer of innovations from
more digitised fields. Unlike manufacturing, construction still lacks industrial-grade data-transfer
standards and interfaces; consequently, information is exchanged mainly through files rather than
interoperable services [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], [6]. Compared with the integrated process automation achieved in
manufacturing [7], construction automation remains largely impractical because design and production
have diverged over the past 30 years [8]. The enduring “islands of automation” first illustrated by
Hannus et al. [9] underscore that, although BIM has become routine, design software still cannot
feed reliable data downstream to production machinery.
      </p>
      <p>BIM authoring tools—architectural, structural and MEP—are therefore used primarily for
designphase coordination [10] rather than for product-lifecycle management. They lack explicit concepts
and interfaces for an Engineering Bill of Materials (E-BOM) and a Manufacturing Bill of Materials
(M-BOM) [7] and have limited integration to enterprise-resource-planning (ERP) systems [11]. This
means that BIM-models do not function as a continuous source of information downstream in the
process. Instead, 2D drawings are produced from the models for quantity calculations during
procurement and for execution planning on-site [6]. This causes manual labour and notably, the use of
BIM models also depends on file-based exchange between organisations and companies [10], and
current BIM systems are not designed to support bidirectional, real-time, and continuous data
transfer throughout the design, procurement, and construction processes [12].</p>
      <p>
        The whole built-environment sector faces increasing pressure to improve efficiency and cut
carbon emissions while accurately reporting on these reductions [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. Environmental regulations
[13] further raise the bar, adding design and product-development requirements that will be unten
able without better data automation. These demands call for digital information flows robust enough
to support lifecycle carbon-assessment standards [14].
      </p>
      <p>Recent breakthroughs in AI research have lowered the barrier to adoption across industries, also
in the field of construction [15]. Beyond large language models, AI agents and multi-agent platforms
now offer lightweight, goal-driven software “teammates” that can search for, combine and transform
data with minimal human scripting [16].</p>
      <p>Yet putting these capabilities to work in construction product-data enrichment is difficult. BIM
files follow the IFC standard, whose design-centric schema was never meant to carry product data
seamlessly through the supply chain. To enable downstream data use, design information must first
be extracted from IFC models into an external platform in a machine-readable format suitable for
enrichment. Only then can it be reliably transformed into product-level bill of materials data. This
process requires partial standardization of design-phase nomenclature for each supply chain and
product family [6], which paradoxically increases the complexity of conventional enrichment
algorithms [6].</p>
      <p>This study tackles that complexity by deploying an AI-agent platform to bridge
researcher-identified digital discontinuities in ventilation-system design and supply-chain data. Our purpose is
twofold: (i) to demonstrate how AI agents can enrich BIM-based Engineering Bills of Materials (E-BOMs)
into Manufacturing Bills of Materials (M-BOMs) that support product-selection decisions, and (ii) to
propose ways to simplify the underlying enrichment logic. The work is guided by two research
questions:
1.</p>
      <p>What digital discontinuities exist in 2D- and BIM-based ventilation-system design and sup
ply-chain management, and how do professionals currently handle them?
How can an AI-agent platform bridge these discontinuities and deliver a continuous, ma
chine-readable data flow?
The remainder of the paper is organised as follows. Section 2 outlines the theoretical background,
including the Finnish MEP data context, AI agents, the E-BOM to M-BOM transformation, and a
detailed description of the ventilation system workflow across design, procurement, and installation.
Section 3 presents the case data and multi-agent workflow. Section 4 reports the results, Section 5
discusses implications, Section 6 addresses limitations and future research, and Section 7 concludes.</p>
    </sec>
    <sec id="sec-2">
      <title>2. Theoretical background</title>
      <sec id="sec-2-1">
        <title>2.1. The importance of digitalisation, machine reading, and data flow in manufacturing and construction</title>
        <p>When comparing the state of the industry with manufacturing or the food industry, the disparity
becomes highly evident from both a manufacturing theory and modelling perspective.
Manufacturing has successfully conceptualised its production model [17] and has developed the GS1 standard
family [18], [19] along with the PEPPOL standard. The PEPPOL enables supply chain transaction
data to be transferred from file- and email-based exchange into electronic order-delivery messaging
[20], [21]. The fight against climate change, alongside accelerating EU regulations, has driven other
industries towards digitalisation. As a result, the automated processing of process and product data
has become standard practice like in food industry. In the retail sector, machine-based data pro
cessing is closely linked to the consumer market. Consumers can track real-time purchase pricing,
the proportion of domestic products, and carbon footprint data. Even the retailers report this in
formation via mobile applications straight to customers. However, the construction industry has yet
to implement such advancements at construction sites. The sector lacks essential digital management
solutions for inbound and on-site logistics, machine-readable supply chain data, automated
processing of design data, and seamless data exchange between systems.</p>
      </sec>
      <sec id="sec-2-2">
        <title>2.2. Digitalisation of the construction supply chain in Finland</title>
        <p>In Finland, the construction industry has aimed to solve the challenges of digitalisation through
collaboration between the public and private sectors and research institutions. This has resulted in
the development of a built environment digital interoperability platform, the national
standardisation of data content, and the digitalisation of supply chains [6], [22]. The ongoing development has
already transformed available construction-related data into a structured format, facilitating new
applications for both software robotics and artificial intelligence.</p>
        <p>
          At the national level, the digitalisation efforts of the construction supply chain have already
produced concrete results by integrating concrete element manufacturers, designers, and
construction companies. This has led to the first pilot implementations of GS1-standard RFID usage, enabling
tracking from manufacturing to the construction site, through the structural phase, and into the
completed building in an Engineer-to-Order (ETO) supply chain [23]. Additionally, the construction
industry, together with the building product industry and universities, has developed a national data
flow architecture for building services products [6] and also for the mentioned ETO supply chain
products [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ].
        </p>
        <p>
          In this research, the data flow of the building services supply chain has been further modelled to
validate the data flow architecture at the bill of materials level for ventilation systems. The study has
demonstrated that BIM model data content can be linked to procurement, supply chain management,
production planning, and management, covering site logistics and manufacturing [24]. Furthermore,
the research has shown that the application of machine processing in the design process of
ventilation systems enables CO₂ calculations based on GS1/GTIN identification using Linked Building Data
(LBD), a graph-based framework that publishes BIM entities, product classes and properties as
semantically rich, interlinkable data [
          <xref ref-type="bibr" rid="ref6">25</xref>
          ], [
          <xref ref-type="bibr" rid="ref7">26</xref>
          ]. LBD supplies the common semantics that let our AI
agents retrieve BIM-based E-BOM data and enrich it into an M-BOM, seamlessly linking design,
procurement and manufacturing.
        </p>
      </sec>
      <sec id="sec-2-3">
        <title>2.3. AI agents: the next generation of process automation</title>
        <p>
          The adoption of large language models (LLMs) is rapidly expanding in the construction industry,
where they are applied to enhance design, automate documentation, and improve project
coordination [15]. In addition, AI agents mark a step change in both artificial intelligence development and
industrial digitalisation due to their potential to automate entire workflows, not just isolated tasks.
An agent can plan, execute and monitor a process, adapt to objectives and learn continuously from
feedback. By calling external data sources and tools on demand, agents enhance complex-task exe
cution and improve information flow between systems and stakeholders [
          <xref ref-type="bibr" rid="ref8">27</xref>
          ], [
          <xref ref-type="bibr" rid="ref9">28</xref>
          ], [
          <xref ref-type="bibr" rid="ref10">29</xref>
          ]. When
several autonomous agents share an environment and coordinate through predefined protocols, they
act as a collaborative AI-agent framework [
          <xref ref-type="bibr" rid="ref11">30</xref>
          ], [
          <xref ref-type="bibr" rid="ref12">31</xref>
          ], [
          <xref ref-type="bibr" rid="ref13">32</xref>
          ]. Such coordination is well suited to
distributed problems in which a larger goal is decomposed into smaller subtasks that individual agents
perform in parallel. One of the key capabilities of AI agents is data retrieval and enrichment, enabling
them to autonomously access, interpret, and structure information across diverse systems [16].
        </p>
        <p>
          The rapid evolution of generative AI has made agent technology central to current innovation
[
          <xref ref-type="bibr" rid="ref14">33</xref>
          ]. Gartner predicts that AI agents will be the most important strategic technology trend by 2025
[
          <xref ref-type="bibr" rid="ref15">34</xref>
          ]. Major vendors have already released orchestration frameworks—Microsoft’s AutoGen Studio
[
          <xref ref-type="bibr" rid="ref16">35</xref>
          ], Google’ s Agentspace [
          <xref ref-type="bibr" rid="ref17">36</xref>
          ], Amazon’ s Bedrock Agents [
          <xref ref-type="bibr" rid="ref18">37</xref>
          ] and OpenAI’ s Swarm [
          <xref ref-type="bibr" rid="ref19">38</xref>
          ]— to
simplify building and deploying cooperating agents.
        </p>
        <p>
          The ability of AI agents to operate as “human-like” digital workers is now recognised in software
development [
          <xref ref-type="bibr" rid="ref20">39</xref>
          ], data analytics [
          <xref ref-type="bibr" rid="ref21">40</xref>
          ], research [
          <xref ref-type="bibr" rid="ref22">41</xref>
          ] and team-based knowledge work [
          <xref ref-type="bibr" rid="ref23">42</xref>
          ] . In
construction, their potential is emerging in BIM data interfaces [
          <xref ref-type="bibr" rid="ref20">39</xref>
          ], [
          <xref ref-type="bibr" rid="ref21">40</xref>
          ], [
          <xref ref-type="bibr" rid="ref22">41</xref>
          ], [
          <xref ref-type="bibr" rid="ref23">42</xref>
          ]. Integrating agents
with BIM models is especially promising because BIM standards are maturing at the same time that
agent technologies are advancing [
          <xref ref-type="bibr" rid="ref24">43</xref>
          ], [45], [46]. Nevertheless, empirical studies that apply agent
frameworks in construction remain scarce.
        </p>
        <p>Deploying AI agents within the rule-bound processes of construction demands careful tailoring
so that each agent performs its task inside clear constraints, and so that inter-agent collaboration,
roles and data flows are coherently orchestrated. This research addresses that gap by examining how
an AI-agent platform can bridge digital discontinuities in 2D- and BIM-based ventilation-system
design and supply-chain management.</p>
      </sec>
      <sec id="sec-2-4">
        <title>2.4. Engineering Bill of Materials (E-BOM) and Manufacturing Bill of Materials (M-BOM)</title>
        <p>Material flow management is a key function of Enterprise Resource Planning (ERP) systems, which
include a separate Material Resource/Requirements Planning (MRP) module. In manufacturing,
materials are managed in factories using a Warehouse Management System (WMS) integrated into
the ERP system. The WMS oversees material reception, internal transfers, inventory balance
tracking, movement of materials to worksite, and the transfer of finished products between worksites
until shipment within the supply chain. These functions together form a digitalised material flow
system, covering inbound, internal, and outbound logistics within factories.</p>
        <p>Manufacturing and assembly operations, which are guided by ERP/MRP and WMS, rely on
production planning that defines the components and materials required for assembly at the article level.
During product development, it is often impractical to specify suppliers for all components due to
factors such as supplier availability at the time of production. Therefore, product development
generates an initial component hierarchy known as the Engineering Bill of Materials (E-BOM), which
engineers use to present the product structure. As the process moves from development to produc
tion planning, E-BOM data must be enriched with supplier-specific details, identifying the exact
articles and suppliers for each component. The result is the Manufacturing Bill of Materials
(MBOM), which defines the components, materials, and work sequence required for production [47].</p>
        <p>A similar approach can be applied in the construction industry, where designers use generic
components and materials at the BIM modelling stage (E-BOM), while procurement selects specific
suppliers and articles for these components and materials (M-BOM) [6].</p>
      </sec>
      <sec id="sec-2-5">
        <title>2.5. Ventilation system workflow: from design to installation</title>
      </sec>
      <sec id="sec-2-6">
        <title>2.5.1. Ventilation system design process</title>
        <p>Building services design involves segmenting the design into distinct system components. Con
sequently, due to the use of specialised design and calculation tools, data becomes fragmented across
multiple sources and is compiled into various files alongside the primary 2D and 3D design plans.
From the designer’s perspective, the design phase has two main objectives: 1) ensuring the system is
dimensioned correctly according to spatial requirements, and 2) modelling the system holistically to
prevent conflicts with other systems or structural components.</p>
        <p>These requirements significantly impact the structure and content of the data. In MEP design,
systems are not modelled from the perspective of procurement, construction, or installation. Vent
ilation system models, for instance, lack detailed product information and essential installation
components such as suspension accessories and support brackets.</p>
        <p>In the case studies examined in this research, the designer's BIM model incorporates IFC data,
identifiers, coordinate-based location data, and geometric information. According to the E-BOM
definition used in manufacturing, this data is incomplete. However, for ventilation systems, it
provides sufficient information to identify components, determine quantities, and, to some extent,
establish locations. The designer exports a 2D drawing from the model, but this output loses its
structured data format, consisting only of schematic symbols and floor plan geometry. Additionally,
system identifiers are added manually, leading to the loss of quantity, geometric, and location data.</p>
      </sec>
      <sec id="sec-2-7">
        <title>2.5.2. Ventilation system procurement process</title>
        <p>The designer provides structured design files to the main contractor's procurement team, which then
forwards them to subcontractors as part of the request for quotation (RFQ) process. In the studied
cases, subcontractors estimate material quantities using either a software-based or manual
approach.</p>
        <p>In the software-based method, the subcontractor traces duct routes over a PDF using CAD
software to calculate duct lengths by diameter and identify components, generating an Excel-based parts
list. Alternatively, in the manual method, the estimator prints the floor plan and marks duct lengths
and component counts directly on paper.</p>
        <p>At this stage, location data remains unstructured, as wholesalers’ web platforms do not support
its integration into the order-delivery process. Once quantity estimation is complete, the estimator
assigns ventilation ducts and components to suppliers, calculates costs, or requests additional quo
tations.</p>
        <p>In this study, the subcontractor who won the bid used a wholesaler’s web application for
ordering, basing quantities on warehouse availability. Duct components were delivered during the
structural phase and distributed across floors accordingly.</p>
      </sec>
      <sec id="sec-2-8">
        <title>2.5.3. Ventilation system installation process</title>
        <p>In the studied projects, the subcontractor had agreed with the installers on the scope of work, which
was defined according to the industry’s collective labour agreement. The primary tasks of the in
staller included: 1) performing execution planning based on 2D drawings, 2) horizontally
transporting components and materials, 3) installation, and 4) participating in a model inspection review with
the site supervisor. At the construction site, the installer first transported the necessary materials
and components to the installation location based on calculations from the 2D drawing. If a material
shortage was identified, additional materials were ordered. For the installation, the installer
measured the duct lengths from the drawings, cut the ducts accordingly, and measured and drilled
attachment points in the ceiling for the supports. The ducts and prefabricated parts were installed at
support intervals, and the apartment's ventilation distribution was completed one duct at a time –
either from the vertical ventilation shaft to the prefabricated bathroom and its ducting or a
later-installed terminal device. The installer connected the duct components to the prefabricated parts by
drilling holes for riveting and securing them together. Some connections were further reinforced
with sealing tape. Before the suspended ceiling was built, the main contractor’s site supervisor
inspected the installations, requested corrections if necessary, or approved them for coverage.</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>3. Materials and methods</title>
      <sec id="sec-3-1">
        <title>3.1. Case data: HVAC system components for multi-storey residential construction</title>
        <p>To identify the discontinuities of data flow, this study examines the design, tendering, material
delivery, and installation processes of building services subcontracting. Discontinuities were
identified where data is not transferred in a machine-readable format. Among these, the enrichment of
EBOM data into M-BOM data was selected as the process to be simulated using a multi-agent plat
form. The selected case study focused on multi-storey residential construction, allowing the
utilisation of a BIM model for building services, created as an example within the digital building permit
process in Finland under the Rava3PRO project [22], [48].</p>
        <p>This study utilises the standardisation of BIM data content through the national HVAC product
component classification [50]. The ventilation system was chosen for simulation, as its product range
is the most standardised compared to other MEP systems. Additionally, its modelling approach and
BIM data content are the most comprehensive, providing the best representation of the implemented
system at the product level. The classification published in 2023 has also been implemented as part
of the Magicad software suite in Revit/Autocad environments. Furthermore, it has been implemen
ted in the Cadmatic design software and published in the buildingSMART Data Dictionary (bSDD)
[51]. Experiences from using the classification indicate that it is semantically functional and
logically well-structured. The nomenclature has already been applied in several dozen projects, and its
adoption is expanding systematically as main contractors enter into design contracts for new
projects. The logic of information hierarchy within the classification is consistent, and for this reason,
semantic enrichment operates according to the same principles across all system types covered by
the nomenclature. As a result, the data hierarchy of the HVAC product group is representative of
the building as a whole.</p>
        <p>Standardised and structured BIM E-BOM data serves as the primary dataset for the research. This
study focuses on building services, as the national interoperability platform [49], launched in 2023,
includes a machine-readable classification system, [50], [53] and a country-specific database for the
Revit design software, published under an open license [51].</p>
      </sec>
      <sec id="sec-3-2">
        <title>3.2. Multi-agent workflow for E-BOM to M-BOM enrichment</title>
        <p>The study evaluated a multi-agent workflow that enriches a ventilation-system Engineering Bill of
Materials (E-BOM) into a floor-level Manufacturing Bill of Materials (M-BOM) and then refines it
into location-specific lists for installers. The MEP design model’s IFC data were first converted to a
machine-readable form. A Python environment was configured on Ubuntu Linux, together with
IfcOpenShell [52], which supports object-oriented scripting for IFC. The extraction script defined the
system components and PropertySets required by the use-case and filtered IfcPipeFitting objects, the
target class for HVAC piping [49], [50] ,[51], [53]. It also captured the product-type codes stored in
the demonstration model’ s PropertySet; these codes— maintained in the Finnish interoperability
platform [22]—serve as primary keys for later enrichment. Executing the script produced a
structured, HVAC-specific E-BOM in JSON, chosen for its flexible schema, native Python support and
seamless ingestion by AI-agent frameworks. Figure 1 illustrates the extraction sequence, which
follows the template introduced by Alhava et al. at LDAC 2025 [24].</p>
        <p>To automate quantity take-off for subcontractors and installers, several open-source
AIagent frameworks were screened against three early-stage requirements: (i) a visual, intuitive GUI,
(ii) low-code workflow modelling, and (iii) rich data-input nodes. Financial constraints limited the
choice to fully open-source tools. Langflow satisfied all criteria and was adopted [54]. Its
drag-anddrop interface lets users combine Python snippets, database/API queries, mathematical nodes and
language-model prompts into a single agent chain.</p>
        <p>Pre-tests showed that reliable product matching demands a domain-tuned language model. A
small Finnish LLM (Poro/Viking) was therefore deployed via Ollama, which hosts fine-tuned models
and supplies semantic search functions for catalogue look-ups. Using Langflow’s basic template, the
research team mapped each task required to generate the M-BOM (Figure 2) and confirmed that the
JSON parts list could circulate through the agent chain without additional coding.</p>
        <p>An AI agent dedicated to product selection was configured to ensure that chosen components
meet CO₂ constraints. Langflow already contained the necessary data-fetch and enrichment blocks,
so only minor parameter tuning was required. The complete toolchain comprised (i) the local Finnish
LLM served via Ollama, (ii) an API-based product database or web-scraper for ventilation items, (iii)
a CO₂ computation module, (iv) a data parser for agent I/O, and (v) the IfcOpenShell routines that
regenerate the E-BOM list. Sample inputs and outputs generated inside Langflow verified smooth
data exchange across the chain and confirmed that the multi-agent environment was ready for
performance testing.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Results</title>
      <p>The simulation confirmed that current ventilation workflows still rely on manual extraction of BIM
information, so design, procurement, supply-chain management and on-site execution fail to
exploit the model’s data. Information on ventilation components is exchanged as 2D draw-ings; part
types are re-identified and quantities recalculated by hand. The study uncovered five critical
recurring digital discontinuities distributed across project phases, roles and software tool:
1. Tendering phase: manual quantity estimation by the subcontractor's cost estimator (using a
quantity estimation software or Excel).
2. Material procurement and ordering phase: refinement of product quantities and selection of
required installation materials by the subcontractor's cost estimator (Excel or quantity es
timation software). Orders placed through a wholesaler's web-shop tool (Excel-based import
file).
3. Call-off stage: project engineers, site managers, or team leaders adjust product quantities
based on updated designs and previous calculations from the procurement phase (Excel-based
import file).
4. Reception and logistics: materials are stored in the basement without precise quantity
records; apartment-level calculations and material picking for daily logistics rely on
handwritten notes on graph paper or 2D drawings.
5. Installation phase: execution plans are developed from 2D drawings, followed by manual
material calculations (notes on graph paper or 2D drawings).</p>
      <p>Existing AI-agent platforms proved capable of modelling these fragmented processes, querying
external product catalogues and performing real-time CO₂ calculations. The simulation handled all
five discontinuities within a single agent chain, confirming that one workflow can span design,
procurement, logistics and installation without manual re-entry. When supplied with the
machinereadable Engineering Bill of Materials, the agents automatically produced a structured,
supplierready Manufacturing Bill of Materials. Because the agents worked directly on the JSON E-BOM
extracted from the BIM model, the data remained fully machine-readable throughout the
transformation.</p>
      <p>To deploy such a platform successfully, process owners must (i) describe the target task in plain
language for the agent, (ii) supply standardised E-BOM input, (iii) connect product-data APIs for
enrichment, (iv) provide a supporting LLM, prompt templates and calculation routines, and (v) designate
a downstream recipient—which may itself be another agent. In practice, the entire workflow hinged
on the presence of the product-type codes issued by the Finnish interoperability platform; without
these identifiers the agents could not resolve catalogue entries or attach CO₂ data, underscoring that
reliable automation is attainable when the BIM model already contains well-formed technical
attributes and design classifications and when those classifications conform to a shared, sector-wide
standard. Thus, structuring IFC-based BIM models into machine-readable formats is essential for
AIdriven processes. While training a domain-specific language model for product search would
enhance this process, such a model was not yet available during the study.</p>
      <p>A further result is that the Finnish data-standardisation scheme underpinning our workflow
applies uniformly across all MEP domains, thereby enabling system-level automation of data flows
throughout the building-services supply chain. The hierarchy we implemented for ventilation
components matches the structure used for, for example, heating radiators, under-floor heating loops,
domestic water lines and sanitary drainage. Because the same Finnish design codes and product
identifiers govern every technical system, the identical agent workflow can be reused across the full
range of MEP applications, not just ventilation.</p>
      <p>In addition, the AI-agent platforms used in this study provide advanced capabilities—such as
webbased document searches, vector-database queries, and mathematical computations—that traditional
construction software typically lacks. Beyond data enrichment, AI agents support multimodal
searches across diverse project sources, converting heterogeneous information into
machine-readable formats. Their ability to coordinate multiple agents toward a single objective further enhances
the efficiency of automation workflows.</p>
      <p>Testing showed that the agent chain replaced every manual hand-off with an automated step,
effectively “digitising” each of the five documented discontinuities. Once the BIM model contained
the Finnish product-type codes and other standardised attributes, the workflow moved data
continuously from design to procurement and site execution—no 2D take-offs or spreadsheets were
required. Two concrete observations were recorded: (i) standardised BIM data served directly as the
source for quantity take-off, and (ii) the agents enriched that data into supplier-specific M-BOMs
that were passed downstream without re-entry. In addition, the platform wrote order-to-delivery
information back to the model, a task that is currently handled in disconnected files. These results
illustrate how AI agents, coupled with shared data standards, can close the data gap between design
and execution.</p>
    </sec>
    <sec id="sec-5">
      <title>5. Discussion</title>
      <p>The use of AI agents in a small-scale test yielded highly encouraging results, demonstrating that the
digitalisation of discontinuities in the construction industry can be achieved by following the same
actions of individual people involved in the process. The great potential of AI-agents lies in the future
when we can teach AI systems how the same products behave within the same supply chain types.
In this scenario, AI-agents will be able to act proactively and provide users with recommendations
when certain products or technical attributes appear, for example, in a ventilation design model. This
will also facilitate compliance with sustainability reporting and environmental requirements, as
realtime compliance monitoring and calculations will be embedded in the product selection process. A
key insight from this study is that investing in standardisation pays off, as it enables precisely this
kind of agent-based data enrichment and seamless information flow across design, procurement, and
installation. While the paper does not claim universal empirical coverage, it demonstrates how
digitally mature environments can already leverage AI agents effectively—and provides a blueprint
that less mature contexts can adopt incrementally.</p>
      <p>The successful integration of AI-enriched building services component lists into business opera
tions also requires the incorporation of AI technology into the company’s enterprise architecture.
The core principle is to separate data management perspectives into 1) presentation layer, 2) ap
plication layer (business logic), 3) persistence layer (data storage), and 4) database layer (technology
and database infrastructure). Integrating AI functionalities into enterprise architecture is essential to
ensure that AI agent platforms align with business and expert needs within the organisation. Since
AI agent platforms are still in the development phase, the platform should be implemented in
separate technical development environment (sandbox). This sandbox must align with the company’s
enterprise architecture including the existing systems and data sources the people are using. To
support the simulated AI-driven product selection process, integrations are required with ERP-sys
tems (procurement data), financial systems (contract pricing), project banks (project documentation),
project scheduling software, quality management systems, and security and access control systems.</p>
      <p>The starting point of this research was that existing construction industry information systems
could be utilised despite their limitations. During the study, it was identified that the automation of
data processing provided by AI-agents simplifies the algorithms needed for data extraction and
transformation while also making vast product data repositories accessible within design models.
Our initial hypothesis was confirmed: AI-agents significantly increase the level of automation in data
processing at the enterprise level compared to traditional algorithm development. With AI-agents,
we can bridge the missing link in BIM-based information modelling, enabling data connectivity, if
BIM data can first be extracted into a suitable format for AI agents (e.g., structured component
lists).</p>
    </sec>
    <sec id="sec-6">
      <title>6. Limitations and future research</title>
      <p>The study's limitations can be summarized into four key areas. First, the experiment focused on a
single ventilation system’s design, procurement, and installation, limiting the generalizability of
findings to the broader building services or construction industry. Expanding the research to mul
tiple system types and projects is necessary.</p>
      <p>Second, the AI-agent system remains a prototype with incomplete integrations, and its ability to
optimize product selection based on carbon footprint, cost, or installation efficiency is still limited.
Further development requires structured databases, high-quality data, a trained language model, and
a unified architecture for AI model selection and fine-tuning.</p>
      <p>Third, ensuring semantic consistency in product data processing requires linking structured data
to graph or vector databases while maintaining robust authentication and agent permissions. Addi
tionally, user interfaces and monitoring tools must allow users to track system functions, manage
exceptions, and facilitate feedback loops between AI agents and human users. Practical
implementation challenges, such as pricing models and system integration (e.g., SaaS solutions), need further
exploration before systemic multi-agent adoption in construction digitalization.</p>
      <p>Fourth, orchestrating multiple agents warrants dedicated research as a systemic solution for
construction data flow. How to coordinate many specialised agents, resolve conflicts and maintain
global objectives in a live project environment remains an open question. Equally critical is estab
lishing governance mechanisms—such as clear performance metrics and human-in-the-loop override
protocols—to ensure that autonomous agent swarms act transparently and reliably across the project
lifecycle.</p>
      <p>Future research should also expand testing across multiple construction projects and building
services domains (e.g., HVAC, plumbing, electrical). Developing broader, standardized product and
CO₂ databases would improve AI-driven product selection and optimization. Additionally, refining
the technical reliability and orchestration of multiple AI agents could transform data management
and exchange in the construction industry.</p>
      <p>Despite the study’s limited scope, the successful enrichment of building services data demon
strates the feasibility and value of machine-based data processing in supply chain management.
AIagent tasks must be carefully defined, with models trained for specific functions to ensure effect
iveness. A key future research area is the development of a specialized language model for product
selection and carbon footprint data interpretation.</p>
      <p>Finally, identifying and addressing supply chain discontinuities through a multi-agent platform
presents new opportunities for digitalization. Future studies should also explore material flow
management, emphasizing product identification and traceability using GS1/GTIN-standardized data,
markings, and barcodes, which are widely used in other industries.</p>
    </sec>
    <sec id="sec-7">
      <title>7. Conclusion</title>
      <p>The study modelled the construction process by analysing the design, procurement, supply chain
management, and subcontracting processes related to ventilation systems and mapping the
associated data flows. The findings confirmed previous observations regarding building services systems,
particularly that ventilation system design data is transmitted as 2D drawings, and that BIM is only
used in the design phase. The entire downstream process relies on 2D drawings in PDF or paper
format for data exchange.</p>
      <p>By examining the data flows, five critical discontinuities were identified, from which data en
richment from E-BOM to M-BOM was selected for the multi-agent analysis. Based on process
analysis, a data processing simulation was conducted using a multi-agent platform. The results included
standardisation of design data within the building services information model, transformation of
design model data into a structured format, as well as enrichment of BIM data using a multi-agent
platform.</p>
      <p>The study demonstrated that the AI agent platform’s functionalities support the enrichment of
IFC-based building services models using multi-agent system tools. Additionally, the study found
that enriching linked data with AI agents requires integrating AI-agents into a company’s enterprise
architecture and processes, which is essential for establishing necessary system and process
integrations. To develop AI-agents, it is crucial to establish a dedicated development environment (sand
box) that replicates the company’s existing architecture and work environment, ensuring seamless
adoption.</p>
    </sec>
    <sec id="sec-8">
      <title>Acknowledgements</title>
      <p>The research team would like to express gratitude for the inspiration and foundational work
provided by various initiatives promoting the digitalisation of construction, including the Finnish
Construction Industries RT’s supply chain digitalisation project, Aalto University’s Building 2030
initiative, the MEP 2030 project, the Rava3PRO project, Finnish Ministry of the Environment, and
the Finnish State Treasury.</p>
    </sec>
    <sec id="sec-9">
      <title>Declaration on Generative AI</title>
      <p>During the preparation of this work, the authors used ChatGPT-4o and Grammarly to check
grammar and spelling. After using these tools/services, the authors reviewed and edited the content as
needed and take full responsibility for the publication’s content.
[6] O. Alhava, B. Ruottinen, A. Peltokorpi, M. Siren, A. Aaltonen, T. Pitkäranta. Advancing
Digitalisation in Construction Through Automated Metadata Management and Machine Data
Processing. Proceedings of the 41st International Conference of CIB W78, Marrakech, Morocco,
23 October, 2024. ISSN: 2706-6568. (ISSN: 2706-6568), http://itc.scix.net/paper/w78-2024-118
[7] M.P. Groover.  Automation, production systems, and computer-integrated manufacturing.</p>
      <p>Pearson Education India, 2016.
[8] T. Zabelle, Built to Fail: Why Construction Projects Take So Long, Cost Too Much, And How to</p>
      <p>Fix It. Forbes Books, 2024.
[9] M. Hannus, H. Penttilä, and P. Silén. Islands of automation in construction. Construction on the
information highway, (198), 20. 1996. http://www.vtt.fi/cic/ratas/islands.gif
[10] A. Revolti, L. Gualtieri, P. Pauwels, and P. Dallasega. From building information modeling to
construction digital twin: a conceptual framework. Production &amp;amp; Manufacturing Research,
12(1). 2024. https://doi.org/10.1080/21693277.2024.2387679.
[11] H. Klaus, M. Rosemann, and G.G. Gable, What is ERP?. Information Systems Frontiers 2, 141–
162. 2000. https://doi.org/10.1023/A:1026543906354
[12] D.P. Hale, W.D. Haseman, and F. Groom. Integrating Islands of Automation. MIS Quarterly 13,
no. 4: 433–45. 1989. https://doi.org/10.2307/248729.
[13] EU-commission, Conference on the new construction products regulation (CPR), 30.10.2024,
webinar record,
https://webcast.ec.europa.eu/conference-on-the-new-construction-productsregulation-cpr-24-10-30
[14] RICS, Whole life carbon assessment for the built environment, professional standard, chapter
1.2, 2023,
https://www.rics.org/content/dam/ricsglobal/documents/standards/Whole_life_carbon_assess
ment_PS_Sept23.pdf
[15] Heo, S., &amp; Na, S. Ready for departure: Factors to adopt large language model (LLM)-based arti
ficial intelligence (AI) technology in the architecture, engineering and construction (AEC)
industry. Results in Engineering, 25, 104325. 2025.
[16] Singh, A., Ehtesham, A., Kumar, S., &amp; Khoei, T. T. Agentic Retrieval-Augmented Generation: A</p>
      <p>Survey on Agentic RAG. arXiv preprint arXiv:2501.09136. 2025.
[17] International Society of Automation. ISA-95 Standard: Enterprise-Control System Integration.</p>
      <p>https://www.isa.org/standards-and-publications/isa-standards/isa-95-standard
[18] J.G. Keoghm, A. Rejeb, N. Khan, K. Dean, and K.J. Hand. Optimizing global food supply chains:
The case for blockchain and GSI standards. Building the Future of Food Safety Technology.
2020:171–204. Epub 2020 Oct 16. PMCID: PMC7561516. Doi:
10.1016/B978-0-12-818956-6.000178.
[19] G. Minculete, and G. BÂRSAN. Approaches Related-To The Functioning And Digital
Transformation Within Supply Chain Management. In Proceedings of the INTERNATIONAL
MANAGEMENT CONFERENCE (Vol. 16, No. 1, pp. 34-47). Faculty of Management, Academy of
Economic Studies, Bucharest, Romania. 2022.
[20] State Treasury, Nordic Peppol Construction Industry Forum. 2025.</p>
      <p>https://www.valtiokonttori.fi/en/nordic-peppol-construction-industry-forum/
[21] R. Carlsson, T. Nevzorova, and K. Vikingsson, Digitalization and verifiability strategy for sus
tainability management of transports in the construction sector. Swedish National Road and
Transport Research Institute (VTI). 2024. ISBN: 9789189896628
[22] Digital and population data services agency. Interoperability platform. 2025.</p>
      <p>https://dvv.fi/en/interoperability-platform
[23] BETK. Tietoa toiminnasta. 2025. https://betoni.com/rakentaminen/betk/
[24] O. Alhava, J. Oraskari, T. Arola, T. Järvinen, M. Järvenpää, B. Ruottinen, BIM Data Content
Guiding Takt Production Material Flow: IFC Meets MTS Supply Chain, LDAC 2025: 13th Linked
Data in Architecture and Construction Workshop, July 09–11, 2025, Porto, Portugal
[45] W. Teclaw, J. O’Donnel, V. Kukkonen, P. Pauwels, N. Labonnote, and E. Hjelseth. Federating
cross-domain BIM-based knowledge graph. Advanced Engineering Informatics, 62, 102770.
2024.
[46] P. Ghimire, K. Kim, and M. Acharya. Generative AI in the construction industry: Opportunities
&amp; challenges. arXiv preprint arXiv:2310.04427. 2023
[47] S. Chang, H., W. Lee,. L., &amp; R.K. Li. Manufacturing bill-of-material planning. Production Planning
&amp; Control, 1997. 8(5), 437–450. https://doi.org/10.1080/095372897235019 Digital and population
data services agency
[48] Rava3Pro. RAVA3Pro – Towards automated checking of BIM-Based Building Permit, 2023.</p>
      <p>https://kirahub.org/en/rava3pro-en/
[49] Interoperability platform. 2025. https://dvv.fi/en/interoperability-platform
[50] Ministry of environment in Finland. Built environment interoperability codesets.
https://koodistot.suomi.fi/codescheme;registryCode=rytj;schemeCode=LVI</p>
      <p>TUOTEOSA_Versio_1_0
[51] bSDD, buildingSMART Data Dictionary (bsDD), 2025.</p>
      <p>https://www.buildingsmart.org/users/services/buildingsmart-data-dictionary/
[52] IfcOpenShell software, 2025. https://ifcopenshell.org/
[53] BuildingSMART International. IFC 4.3.2.0 specification.</p>
      <p>https://standards.buildingsmart.org/IFC/RELEASE/IFC4_3/HTML/chapter-7/index.html
[54] Langflow, 2025. https://www.langflow.org/</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>A.S.</given-names>
            <surname>Kavuri</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Soetanto</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Goodier</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Murguia</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Szczygiel</surname>
          </string-name>
          .
          <article-title>Scenarios for the Digitalisation of the Construction Industry In: Scott, L and</article-title>
          <string-name>
            <surname>Neilson</surname>
            ,
            <given-names>C J</given-names>
          </string-name>
          (Eds
          <source>) Proceedings of the 36th Annual ARCOM Conference, 7-8 September</source>
          <year>2020</year>
          , UK, Association of Researchers in Construction Management,
          <fpage>425</fpage>
          -
          <lpage>434</lpage>
          . https://hdl.handle.net/2134/12980072.v1
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>S.</given-names>
            <surname>Zulu</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Saad</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Ajayi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Unuigbe</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Dulaimi</surname>
          </string-name>
          .
          <article-title>A thematic analysis of the organisational influences on digitalisation in construction firms</article-title>
          .
          <source>Journal of Engineering, Design and Technology</source>
          .
          <volume>22</volume>
          . No.
          <issue>6</issue>
          ,
          <year>2024</year>
          . pp.
          <fpage>1755</fpage>
          -
          <lpage>1772</lpage>
          . https://doi.org/10.1108/JEDT-10-2022-0513
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Costa</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Carvalho</surname>
            ,
            <given-names>M. S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pimentel</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Duarte</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          <article-title>A systematic literature review and con - ceptual framework of construction industrialisation</article-title>
          .
          <source>Journal of Construction Engineering and Management</source>
          ,
          <volume>149</volume>
          (
          <issue>2</issue>
          ),
          <year>2013</year>
          . https://doi.org/10.1061/(ASCE)CO.
          <fpage>1943</fpage>
          -
          <volume>7862</volume>
          .
          <fpage>0002410</fpage>
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <surname>Hall</surname>
            ,
            <given-names>D. M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Whyte</surname>
            ,
            <given-names>J. K.</given-names>
          </string-name>
          and
          <string-name>
            <surname>Lessing</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          <article-title>Mirror-breaking strategies to enable digital manufacturing in Silicon Valley construction firms: a comparative case study</article-title>
          ,
          <source>Construction Management and Economics</source>
          ,
          <volume>38</volume>
          (
          <issue>4</issue>
          ), pp.
          <fpage>322</fpage>
          -
          <lpage>339</lpage>
          ,
          <year>2019</year>
          . Doi:
          <volume>10</volume>
          .1080/01446193.
          <year>2019</year>
          .
          <volume>1656814</volume>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>O.</given-names>
            <surname>Alhava</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Alaluusua</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Pekkala</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Peltokorpi</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Aaltonen</surname>
          </string-name>
          ,
          <string-name>
            <given-names>T.</given-names>
            <surname>Pitkäranta</surname>
          </string-name>
          .
          <article-title>Challenges and Opportunities in Digitalising Concrete Element Supply Chains: Proposed National Model</article-title>
          .
          <source>Proceedings of the 41st International Conference of CIB W78</source>
          , Marrakech, Morocco,
          <fpage>2</fpage>
          -3 October,
          <year>2024</year>
          . ISSN:
          <fpage>2706</fpage>
          -
          <lpage>6568</lpage>
          . Available at: https://itc.scix.net/paper/w78-2024-119
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [25]
          <string-name>
            <surname>Rasmussen</surname>
            ,
            <given-names>M. H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lefrançois</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Bonduel</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hviid</surname>
            ,
            <given-names>C. A.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Karlshøj</surname>
            ,
            <given-names>J. OPM</given-names>
          </string-name>
          :
          <article-title>An ontology for describing properties that evolve over time</article-title>
          .
          <source>In 6th Linked Data in Architecture and Construction Workshop</source>
          .
          <year>2018</year>
          , June.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [26]
          <string-name>
            <surname>Bonduel</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Oraskari</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pauwels</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Vergauwen</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          , &amp;
          <string-name>
            <surname>Klein</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          <article-title>The IFC to linked building data converter: current status</article-title>
          .
          <source>In 6th International Workshop on Linked Data in Architecture and Construction</source>
          , pp.
          <fpage>34</fpage>
          -
          <lpage>43</lpage>
          . CEUR-WS.
          <year>org</year>
          .
          <year>2018</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [27]
          <string-name>
            <given-names>A.</given-names>
            <surname>Chan</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Ezell</surname>
          </string-name>
          , M. Kaufmann,
          <string-name>
            <given-names>K.</given-names>
            <surname>Wei</surname>
          </string-name>
          ,
          <string-name>
            <given-names>L.</given-names>
            <surname>Hammond</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Bradley</surname>
          </string-name>
          , and
          <string-name>
            <given-names>M.</given-names>
            <surname>Anderljung</surname>
          </string-name>
          ,
          <article-title>Visibility into AI Agents</article-title>
          .
          <source>In The 2024 ACM Conference on Fairness, Accountability, and Transparency</source>
          (pp.
          <fpage>958</fpage>
          -
          <lpage>973</lpage>
          ).
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [28]
          <string-name>
            <given-names>S.</given-names>
            <surname>Kapoor</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Stroebl</surname>
          </string-name>
          ,
          <string-name>
            <given-names>Z.S.</given-names>
            <surname>Siegel</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Nadgir</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Narayanan</surname>
          </string-name>
          .
          <year>2024</year>
          .
          <article-title>AI agents that matter</article-title>
          .
          <source>arXiv preprint arXiv:2407</source>
          .
          <fpage>01502</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [29]
          <string-name>
            <given-names>P.</given-names>
            <surname>Putta</surname>
          </string-name>
          ,
          <string-name>
            <given-names>E.</given-names>
            <surname>Mills</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Garg</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Motwani</surname>
          </string-name>
          ,
          <string-name>
            <given-names>C.</given-names>
            <surname>Finn</surname>
          </string-name>
          ,
          <string-name>
            <given-names>D.</given-names>
            <surname>Garg</surname>
          </string-name>
          , and
          <string-name>
            <given-names>R.</given-names>
            <surname>Rafailov</surname>
          </string-name>
          .
          <year>2024</year>
          .
          <article-title>Agent q: Ad - vanced reasoning and learning for autonomous ai agents</article-title>
          .
          <source>arXiv preprint arXiv:2408</source>
          .
          <fpage>07199</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [30]
          <string-name>
            <given-names>Y.</given-names>
            <surname>Talebirad</surname>
          </string-name>
          &amp;
          <string-name>
            <given-names>A.</given-names>
            <surname>Nadiri</surname>
          </string-name>
          .
          <year>2023</year>
          .
          <article-title>Multi-agent collaboration: Harnessing the power of intelligent llm agents</article-title>
          .
          <source>arXiv preprint arXiv:2306</source>
          .
          <fpage>03314</fpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [31]
          <string-name>
            <surname>K.T. Tran</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>Dao</surname>
            ,
            <given-names>M.D.</given-names>
          </string-name>
          <string-name>
            <surname>Nguyen</surname>
            ,
            <given-names>Q.V.</given-names>
          </string-name>
          <string-name>
            <surname>Pham</surname>
            ,
            <given-names>B. O</given-names>
          </string-name>
          <string-name>
            <surname>'Sullivan</surname>
            , and
            <given-names>H.D.</given-names>
          </string-name>
          <string-name>
            <surname>Nguyen</surname>
          </string-name>
          <article-title>. Multi-Agent Collaboration Mechanisms: A Survey of LLMs</article-title>
          .
          <source>arXiv preprint arXiv:2501.06322</source>
          .
          <year>2025</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [32]
          <string-name>
            <given-names>O.</given-names>
            <surname>Torro</surname>
          </string-name>
          , &amp; H.
          <string-name>
            <surname>Jalo</surname>
          </string-name>
          .
          <article-title>Talotekniikan tuotedatan virtautus- ja hyödyntämismahdollisuudet generatiivisen tekoälyn avulla</article-title>
          .
          <year>2024</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [33]
          <string-name>
            <given-names>McKinsey</given-names>
            <surname>Quarterly</surname>
          </string-name>
          .
          <article-title>Why agents are the next frontier of generative AI</article-title>
          .
          <year>2024</year>
          . https://www.mckinsey.
          <article-title>com/capabilities/mckinsey-digital/our-insights/why-agents-are-thenext-frontier-of-generative-ai</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [34]
          <string-name>
            <surname>Gartner</surname>
          </string-name>
          .
          <source>Gartner Identifies the Top 10 Strategic Technology Trends</source>
          for
          <year>2025</year>
          . https://www.gartner.com/en/newsroom/press-releases/2024-10-21
          <article-title>-gartner-identifies-thetop-10-strategic-technology-trends-for-2025</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [35] Microsoft Research Blog.
          <article-title>AutoGen: Enabling next-generation large language model applications</article-title>
          .
          <year>2023</year>
          . https://www.microsoft.com/en-us/research/blog/autogen-enabling
          <article-title>-nextgeneration-large-language-model-applications/</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [36]
          <string-name>
            <given-names>Google</given-names>
            <surname>Cloud. Introducing Google</surname>
          </string-name>
          <article-title>Agentspace: Bringing AI agents and AI-powered search to enterprises</article-title>
          .
          <year>2024</year>
          . https://cloud.google.com/blog/products/ai-machine
          <article-title>-learning/bringing-aiagents-to-enterprises-with-google-agentspace</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref18">
        <mixed-citation>
          [37]
          <string-name>
            <surname>Amazon</surname>
          </string-name>
          . Amazon Bedrock Agents.
          <year>2024</year>
          . https://aws.amazon.com/bedrock/agents/
        </mixed-citation>
      </ref>
      <ref id="ref19">
        <mixed-citation>
          [38]
          <string-name>
            <surname>OpenAI. Swarm</surname>
          </string-name>
          .
          <year>2024</year>
          . https://github.com/openai/swarm
        </mixed-citation>
      </ref>
      <ref id="ref20">
        <mixed-citation>
          [39]
          <string-name>
            <given-names>Z.</given-names>
            <surname>Rasheed</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Waseem</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.A.</given-names>
            <surname>Sami</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.K.</given-names>
            <surname>Kemell</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Ahmad</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.N.</given-names>
            <surname>Duc</surname>
          </string-name>
          , and
          <string-name>
            <given-names>P.</given-names>
            <surname>Abrahamsson</surname>
          </string-name>
          .
          <article-title>Autonomous agents in software development: A vision paper</article-title>
          .
          <source>In International Conference on Agile Software Development</source>
          (pp.
          <fpage>15</fpage>
          -
          <lpage>23</lpage>
          ). Cham: Springer Nature Switzerland.
          <year>2024</year>
          , June
        </mixed-citation>
      </ref>
      <ref id="ref21">
        <mixed-citation>
          [40]
          <string-name>
            <given-names>Z.</given-names>
            <surname>Rasheed</surname>
          </string-name>
          ,
          <string-name>
            <given-names>M.</given-names>
            <surname>Waseem</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Ahmad</surname>
          </string-name>
          ,
          <string-name>
            <given-names>K.K.</given-names>
            <surname>Kemell</surname>
          </string-name>
          ,
          <string-name>
            <given-names>W.</given-names>
            <surname>Xiaofeng</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.N.</given-names>
            <surname>Duc</surname>
          </string-name>
          , and
          <string-name>
            <given-names>P.</given-names>
            <surname>Abrahamsson</surname>
          </string-name>
          .
          <article-title>Can large language models serve as data analysts? a multi-agent assisted approach for qualitative data analysis</article-title>
          .
          <source>arXiv preprint arXiv:2402.01386</source>
          .
          <year>2024</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref22">
        <mixed-citation>
          [41]
          <string-name>
            <surname>A.M. Sami</surname>
            ,
            <given-names>Z.</given-names>
          </string-name>
          <string-name>
            <surname>Rasheed</surname>
            ,
            <given-names>K.K.</given-names>
          </string-name>
          <string-name>
            <surname>Kemell</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Waseem</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          <string-name>
            <surname>Kilamo</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          <string-name>
            <surname>Saari</surname>
            , and
            <given-names>P.</given-names>
          </string-name>
          <string-name>
            <surname>Abrahamsson</surname>
          </string-name>
          .
          <article-title>System for systematic literature review using multiple ai agents: Concept and an empirical evaluation</article-title>
          .
          <source>arXiv preprint arXiv:2403.08399</source>
          .
          <year>2024</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref23">
        <mixed-citation>
          [42]
          <string-name>
            <given-names>A.R.</given-names>
            <surname>Dennis</surname>
          </string-name>
          ,
          <string-name>
            <given-names>A.</given-names>
            <surname>Lakhiwal</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Sachdeva</surname>
          </string-name>
          .
          <article-title>AI agents as team members: Effects on satisfaction, conflict, trustworthiness, and willingness to work with</article-title>
          .
          <source>Journal of Management Information Systems</source>
          ,
          <volume>40</volume>
          (
          <issue>2</issue>
          ),
          <fpage>307</fpage>
          -
          <lpage>337</lpage>
          .
          <year>2023</year>
        </mixed-citation>
      </ref>
      <ref id="ref24">
        <mixed-citation>
          [43]
          <string-name>
            <given-names>Z.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R.</given-names>
            <surname>Sacks</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Ouyang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>H.</given-names>
            <surname>Ying</surname>
          </string-name>
          ,
          <article-title>and</article-title>
          <string-name>
            <given-names>A.</given-names>
            <surname>Borrmann</surname>
          </string-name>
          .
          <article-title>A Framework for Generic Semantic Enrichment of BIM Models</article-title>
          .
          <source>Journal of Computing in Civil Engineering</source>
          ,
          <year>2023</year>
          .
          <volume>38</volume>
          (
          <issue>1</issue>
          ), pp.
          <fpage>1</fpage>
          -
          <lpage>18</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref25">
        <mixed-citation>
          [44]
          <string-name>
            <given-names>Z.</given-names>
            <surname>Wang</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Ouyang</surname>
          </string-name>
          , and
          <string-name>
            <given-names>R.</given-names>
            <surname>Sacks</surname>
          </string-name>
          ,
          <string-name>
            <surname>R.</surname>
          </string-name>
          <article-title>Graph-based inter-domain consistency maintenance for BIM models</article-title>
          .
          <source>Automation in Construction</source>
          ,
          <year>2023</year>
          ,
          <volume>154</volume>
          ,
          <fpage>104979</fpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>