<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD Journal Publishing DTD v2.3 20070202//EN" "journalpublishing.dtd">
<article article-type="research-article" dtd-version="2.3" xml:lang="EN" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">
<front>
<journal-meta>
<journal-id journal-id-type="publisher-id">Front. Built Environ.</journal-id>
<journal-title>Frontiers in Built Environment</journal-title>
<abbrev-journal-title abbrev-type="pubmed">Front. Built Environ.</abbrev-journal-title>
<issn pub-type="epub">2297-3362</issn>
<publisher>
<publisher-name>Frontiers Media S.A.</publisher-name>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="publisher-id">1649278</article-id>
<article-id pub-id-type="doi">10.3389/fbuil.2025.1649278</article-id>
<article-categories>
<subj-group subj-group-type="heading">
<subject>Built Environment</subject>
<subj-group>
<subject>Original Research</subject>
</subj-group>
</subj-group>
</article-categories>
<title-group>
<article-title>Integrated workflow for a semi-automated and robotic facade renovation</article-title>
<alt-title alt-title-type="left-running-head">Iturralde et al.</alt-title>
<alt-title alt-title-type="right-running-head">
<ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3389/fbuil.2025.1649278">10.3389/fbuil.2025.1649278</ext-link>
</alt-title>
</title-group>
<contrib-group>
<contrib contrib-type="author" corresp="yes">
<name>
<surname>Iturralde</surname>
<given-names>Kepa</given-names>
</name>
<xref ref-type="aff" rid="aff1">
<sup>1</sup>
</xref>
<xref ref-type="aff" rid="aff2">
<sup>2</sup>
</xref>
<xref ref-type="aff" rid="aff3">
<sup>3</sup>
</xref>
<xref ref-type="corresp" rid="c001">&#x2a;</xref>
<uri xlink:href="https://loop.frontiersin.org/people/3082759/overview"/>
<role content-type="https://credit.niso.org/contributor-roles/investigation/"/>
<role content-type="https://credit.niso.org/contributor-roles/conceptualization/"/>
<role content-type="https://credit.niso.org/contributor-roles/software/"/>
<role content-type="https://credit.niso.org/contributor-roles/writing-original-draft/"/>
<role content-type="https://credit.niso.org/contributor-roles/visualization/"/>
<role content-type="https://credit.niso.org/contributor-roles/funding-acquisition/"/>
<role content-type="https://credit.niso.org/contributor-roles/resources/"/>
<role content-type="https://credit.niso.org/contributor-roles/methodology/"/>
<role content-type="https://credit.niso.org/contributor-roles/formal-analysis/"/>
<role content-type="https://credit.niso.org/contributor-roles/validation/"/>
<role content-type="https://credit.niso.org/contributor-roles/project-administration/"/>
<role content-type="https://credit.niso.org/contributor-roles/data-curation/"/>
<role content-type="https://credit.niso.org/contributor-roles/supervision/"/>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Shen</surname>
<given-names>Wenlan</given-names>
</name>
<xref ref-type="aff" rid="aff3">
<sup>3</sup>
</xref>
<role content-type="https://credit.niso.org/contributor-roles/writing-original-draft/"/>
<role content-type="https://credit.niso.org/contributor-roles/investigation/"/>
<role content-type="https://credit.niso.org/contributor-roles/software/"/>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Bazan</surname>
<given-names>Renzo</given-names>
</name>
<xref ref-type="aff" rid="aff3">
<sup>3</sup>
</xref>
<uri xlink:href="https://loop.frontiersin.org/people/3182931/overview"/>
<role content-type="https://credit.niso.org/contributor-roles/writing-original-draft/"/>
<role content-type="https://credit.niso.org/contributor-roles/investigation/"/>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Amo-Grau</surname>
<given-names>Oscar</given-names>
</name>
<xref ref-type="aff" rid="aff3">
<sup>3</sup>
</xref>
<role content-type="https://credit.niso.org/contributor-roles/investigation/"/>
<role content-type="https://credit.niso.org/contributor-roles/writing-original-draft/"/>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Liu</surname>
<given-names>Danya</given-names>
</name>
<xref ref-type="aff" rid="aff1">
<sup>1</sup>
</xref>
<xref ref-type="aff" rid="aff3">
<sup>3</sup>
</xref>
<uri xlink:href="https://loop.frontiersin.org/people/3153968/overview"/>
<role content-type="https://credit.niso.org/contributor-roles/writing-original-draft/"/>
<role content-type="https://credit.niso.org/contributor-roles/investigation/"/>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Srinivasaragavan</surname>
<given-names>Aravind</given-names>
</name>
<xref ref-type="aff" rid="aff1">
<sup>1</sup>
</xref>
<xref ref-type="aff" rid="aff3">
<sup>3</sup>
</xref>
<role content-type="https://credit.niso.org/contributor-roles/writing-original-draft/"/>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Das</surname>
<given-names>Samanti</given-names>
</name>
<xref ref-type="aff" rid="aff3">
<sup>3</sup>
</xref>
<role content-type="https://credit.niso.org/contributor-roles/writing-original-draft/"/>
<role content-type="https://credit.niso.org/contributor-roles/investigation/"/>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Bock</surname>
<given-names>Thomas</given-names>
</name>
<xref ref-type="aff" rid="aff3">
<sup>3</sup>
</xref>
<uri xlink:href="https://loop.frontiersin.org/people/667002/overview"/>
<role content-type="https://credit.niso.org/contributor-roles/funding-acquisition/"/>
<role content-type="https://credit.niso.org/contributor-roles/supervision/"/>
<role content-type="https://credit.niso.org/contributor-roles/resources/"/>
<role content-type="https://credit.niso.org/contributor-roles/Writing - review &#x26; editing/"/>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Holst</surname>
<given-names>Christoph</given-names>
</name>
<xref ref-type="aff" rid="aff1">
<sup>1</sup>
</xref>
<role content-type="https://credit.niso.org/contributor-roles/resources/"/>
<role content-type="https://credit.niso.org/contributor-roles/Writing - review &#x26; editing/"/>
<role content-type="https://credit.niso.org/contributor-roles/supervision/"/>
</contrib>
</contrib-group>
<aff id="aff1">
<sup>1</sup>
<institution>Chair of Engineering Geodesy, Technical University of Munich</institution>, <addr-line>Munich</addr-line>, <country>Germany</country>
</aff>
<aff id="aff2">
<sup>2</sup>
<institution>Chair of Digital Transformation in Construction, Institute of Construction Management, Faculty of Civil and Environmental Engineering, University of Stuttgart</institution>, <addr-line>Stuttgart</addr-line>, <country>Germany</country>
</aff>
<aff id="aff3">
<sup>3</sup>
<institution>Chair of Building Realization and Robotics, Technical University of Munich</institution>, <addr-line>Munich</addr-line>, <country>Germany</country>
</aff>
<author-notes>
<fn fn-type="edited-by">
<p>
<bold>Edited by:</bold> <ext-link ext-link-type="uri" xlink:href="https://loop.frontiersin.org/people/603242/overview">Yang Zou</ext-link>, The University of Auckland, New Zealand</p>
</fn>
<fn fn-type="edited-by">
<p>
<bold>Reviewed by:</bold> <ext-link ext-link-type="uri" xlink:href="https://loop.frontiersin.org/people/681736/overview">Jamal Younes Omran</ext-link>, Tishreen University, Syria</p>
<p>
<ext-link ext-link-type="uri" xlink:href="https://loop.frontiersin.org/people/2413951/overview">Johan Augusto Bocanegra Cifuentes</ext-link>, University of Genoa, Italy</p>
</fn>
<corresp id="c001">&#x2a;Correspondence: Kepa Iturralde, <email>kepa.iturralde@ibl.uni-stuttgart.de</email>
</corresp>
</author-notes>
<pub-date pub-type="epub">
<day>13</day>
<month>10</month>
<year>2025</year>
</pub-date>
<pub-date pub-type="collection">
<year>2025</year>
</pub-date>
<volume>11</volume>
<elocation-id>1649278</elocation-id>
<history>
<date date-type="received">
<day>18</day>
<month>06</month>
<year>2025</year>
</date>
<date date-type="accepted">
<day>08</day>
<month>09</month>
<year>2025</year>
</date>
</history>
<permissions>
<copyright-statement>Copyright &#xa9; 2025 Iturralde, Shen, Bazan, Amo-Grau, Liu, Srinivasaragavan, Das, Bock and Holst.</copyright-statement>
<copyright-year>2025</copyright-year>
<copyright-holder>Iturralde, Shen, Bazan, Amo-Grau, Liu, Srinivasaragavan, Das, Bock and Holst</copyright-holder>
<license xlink:href="http://creativecommons.org/licenses/by/4.0/">
<p>This is an open-access article distributed under the terms of the Creative Commons Attribution License (CC BY). The use, distribution or reproduction in other forums is permitted, provided the original author(s) and the copyright owner(s) are credited and that the original publication in this journal is cited, in accordance with accepted academic practice. No use, distribution or reproduction is permitted which does not comply with these terms.</p>
</license>
</permissions>
<abstract>
<p>The drive towards enhanced efficiency, precision, and automation in the realm of building fa&#xe7;ade renovation is a salient factor in this paradigm shift. This transition is characterized by the need for streamlined processes that encompass design, fabrication, and installation. This paper expounds upon an integrated workflow that combines data acquisition, geometric modeling, and robotic assembly to automate the manufacturing of prefabricated facade modules for building renovation. The workflow consists of several steps. First, a structured online data acquisition platform has been developed to standardize the digital modeling process, providing users with a guided approach from basic project input to BIM (Building Information Modeling) -compatible outputs. Next, to enhance the precision of facade modeling from the previous step, a geometry estimation method based on AprilTag is utilized. This method facilitates sub-millimeter accuracy through photogrammetric calibration and plane fitting. These geometric definitions are subsequently transferred to a CAM (computer-assisted manufacturing) pipeline, which enables automated detailing and fabrication of panels using industry-standard software. The final step involves robotic assembly driven by a robotic manipulator with a vision-assisted system for flexible pick-and-place operations. The system demonstrated sub-centimeter assembly precision and reduced manual layout and clash-checking time in different case studies. The proposed system offers a scalable and precise solution for energy-efficient building renovation through a seamless connection between digital modeling and robotic execution.</p>
</abstract>
<kwd-group>
<kwd>building renovation</kwd>
<kwd>data acquisition platform</kwd>
<kwd>AprilTag geometry estimation</kwd>
<kwd>computer-aided manufacturing (CAM)</kwd>
<kwd>robotic assembly</kwd>
</kwd-group>
<contract-num rid="cn001">958445</contract-num>
<contract-sponsor id="cn001">European Commission<named-content content-type="fundref-id">10.13039/501100000780</named-content>
</contract-sponsor>
<custom-meta-wrap>
<custom-meta>
<meta-name>section-at-acceptance</meta-name>
<meta-value>Sustainable Design and Construction</meta-value>
</custom-meta>
</custom-meta-wrap>
</article-meta>
</front>
<body>
<sec id="s1">
<title>1 Introduction</title>
<p>A major strategy to combat climate change involves reducing global energy demand (<xref ref-type="bibr" rid="B3">Babiarz et al., 2024</xref>). Recently, efforts to reach zero-energy usage in homes have primarily focused on upgrading insulation and integrating rooftop RES (renewable energy systems) (<xref ref-type="bibr" rid="B30">Martinez and Larraz, 2017</xref>; <xref ref-type="bibr" rid="B47">Urbikain, 2020</xref>; <xref ref-type="bibr" rid="B15">Hillebrand et al., 2014</xref>). Alternative methods involve refining building envelopes to improve solar energy collection efficiency (<xref ref-type="bibr" rid="B31">Mateus and Duarte, 2016</xref>; <xref ref-type="bibr" rid="B32">Mateus et al., 2021</xref>; <xref ref-type="bibr" rid="B43">Stiny, 1980</xref>). However, implementing these solutions manually may result in privacy breaches, work disruptions, or dangerous operations at high elevations. To mitigate these issues, prefabricated components&#x2014;including insulation, RES, windows, and waterproofing&#x2014;are now being produced away from the construction site (<xref ref-type="bibr" rid="B5">Barco-Santa et al., 2017</xref>). Prior studies have investigated automated facade refurbishment using prefabricated modules with robotic systems, often structured into three key stages (<xref ref-type="bibr" rid="B45">Tsai et al., 2017</xref>; <xref ref-type="bibr" rid="B9">Du et al., 2019</xref>; <xref ref-type="bibr" rid="B10">D&#x2019;Oca et al., 2018</xref>): information handling, module fabrication off-site, and the actual installation process on-site (see <xref ref-type="fig" rid="F1">Figure 1</xref>).</p>
<fig id="F1" position="float">
<label>FIGURE 1</label>
<caption>
<p>Building renovation with prefabricated modules.</p>
</caption>
<graphic xlink:href="fbuil-11-1649278-g001.tif">
<alt-text content-type="machine-generated">Diagram illustrating a modular construction process for an existing building. It shows three stages: off-site manufacturing of custom panels with insulation and renewable energy features, logistics and handling devices transporting the panels, and on-site installation using connectors and platforms. Data flow is indicated as a key component.</alt-text>
</graphic>
</fig>
<p>Although prefabricated components have been introduced for residential renovation, they have yet to achieve broad market penetration, primarily because they are not as cost-effective as conventional manual techniques. The ENSNARE research initiative seeks to cut down the time required for data collection and processing by 90%, in addition to shortening both the manufacturing and assembly phases. However, these time savings must not compromise quality or violate relevant codes and regulations. Mistakes in the data pipeline can cause discrepancies in the prefabricated elements, which may lead to leakage of water or heat, physical clashes, or difficulties during installation on-site.</p>
<p>The viability of using robotics and automated technologies for renovating residential buildings is closely tied to their cost-effectiveness (<xref ref-type="bibr" rid="B42">Skibniewski and Hendrickson, 1988</xref>; <xref ref-type="bibr" rid="B4">Balaguer and Abderrahim, 2008</xref>; <xref ref-type="bibr" rid="B48">Warszawski, 1985</xref>; <xref ref-type="bibr" rid="B18">Hu et al., 2020</xref>). In addition, effectively managing and preparing these technologies for commercialization is a critical concern (<xref ref-type="bibr" rid="B37">Pan et al., 2020a</xref>; <xref ref-type="bibr" rid="B36">Pan et al., 2018</xref>; <xref ref-type="bibr" rid="B38">Pan et al., 2020b</xref>). This topic has been explored in earlier research efforts, such as the BERTIM and HEPHAESTUS projects. Prior investigations have also identified as many as 15 specific RG (research gaps) in this domain.</p>
<p>In the domain of residential building renovation, the adoption of pre-fabricated modules for energy efficiency and renewable energy generation often faces limitations in competitiveness compared to manual methods, primarily due to the need for more extensive and precise project planning. When considering the use of such modules, stakeholders&#x2014;including property owners, developers, and engineers&#x2014;must gain a thorough understanding of the building&#x2019;s potential for solar energy production, associated investment costs, and insulation requirements early in the planning phase. This process necessitates the creation of a georeferenced 3D (three-dimensional) model of the building, capable of accurately reflecting its geometry, structure, and suitability for integrating prefabricated components and photovoltaic systems. Within this framework, the configuration of solar panels and prefabricated wall elements becomes particularly important, as it enables an assessment of how many solar panels can be installed on the fa&#xe7;ade, the amount of insulation required, and the projected financial outlay.</p>
<p>Each component of the proposed workflow has been designed to overcome specific market limitations and research gaps. The online data acquisition step eliminates the necessity for costly and error-prone on-site surveys. The utilisation of structured BIM modelling has been demonstrated to address the fragmentation of planning, thereby enhancing the early-stage integration of solar energy generation and envelope insulation objectives. AprilTags facilitate millimetre measurement, and thereby establish that the CAM pipeline facilitates the generation of modules that are both consistent and free of errors. Finally, the robotic assembly step solves the current barrier of labour-intensive, inflexible on-site installation by automating pick-and-place with vision-based guidance. To clarify the workflow required in this study, the following steps have been identified as essential.<list list-type="simple">
<list-item>
<p>&#x2022; Robot systems have not been practically adopted for the automated assembly of pre-fabricated construction elements.</p>
</list-item>
<list-item>
<p>&#x2022; Limitations of conventional systems:</p>
<list list-type="simple">
<list-item>
<p>&#x2022; Dependence on measurements of the building&#x2019;s geometry is necessarily made on the site, with the subsequent need to travel there even in the previous stages when the contracts with the building owner or client are not defined yet.</p>
</list-item>
<list-item>
<p>&#x2022; Manual definition of the Renovation project with prefabricated modules</p>
</list-item>
<list-item>
<p>&#x2022; lack of a fluid link between the BIM and the CAM of the Robotic Assembly.</p>
</list-item>
<list-item>
<p>&#x2022; In the Robotic Assembly, typically restricted to handling identically sized components with repetitive operations</p>
</list-item>
</list>
</list-item>
<list-item>
<p>&#x2022; Our proposed solution: From Online Data to Robotic Assembly</p>
<list list-type="simple">
<list-item>
<p>&#x2022; Online Data Acquisition: Utilizes publicly available inputs to generate an initial digital model without requiring on-site surveying.</p>
</list-item>
<list-item>
<p>&#x2022; Existing Building Modeling BIM: Establishes a simplified yet structured 3D model to capture geometry, layout, and key fa&#xe7;ade elements.</p>
</list-item>
<list-item>
<p>&#x2022; Building Renovation Project BIM: Integrates design objectives and layout configurations into the digital model for prefabrication planning.</p>
</list-item>
<list-item>
<p>&#x2022; AprilTags: Enable precise localization and adjustment by linking physical reference points with digital models.</p>
</list-item>
<list-item>
<p>&#x2022; Assembly CAM: Translates refined geometry and connector placement into machine-readable fabrication instructions.</p>
</list-item>
<list-item>
<p>&#x2022; Robotic Assembly: Execute physical construction via a robotic arm with vision-assisted pick-and-place and an extended linear axis for workspace adaptability.</p>
</list-item>
</list>
</list-item>
</list>
</p>
<p>This study aims to establish an automated renovation workflow that addresses the limitations of conventional systems&#x2014;namely their reliance on repetitive geometry, constrained robotic reach, and manual site measurements. By introducing an integrative workflow that starts with online data acquisition and evolves through BIM-based modeling, building renovation project, automated CAM generation, and precise and flexible robotic assembly of pre-fabricated fa&#xe7;ade modules. The core objective is to demonstrate how a semi-automated, data-driven approach can significantly improve the efficiency, accuracy, and scalability of building renovation processes.</p>
</sec>
<sec id="s2">
<title>2 Related work</title>
<sec id="s2-1">
<title>2.1 Data acquisition and accurate measurement with AprilTags</title>
<p>Automation in renovation projects begins with accurate data acquisition and digital modeling. Numerous studies have emphasized the importance of digitizing existing buildings to support downstream processes such as manufacturing and robotic assembly. <xref ref-type="bibr" rid="B28">Lasarte et al. (2017)</xref> and <xref ref-type="bibr" rid="B1">Ali et al. (2021)</xref> proposed BIM-based tools for automated design and planning, enabling stakeholders to define layout configurations and geometries in early stages. Digital planning tools that integrate public data and facade geometry have been used to semi-automate layout creation and visualization for prefabricated facade modules <xref ref-type="bibr" rid="B22">Iturralde et al. (2023a)</xref> and <xref ref-type="bibr" rid="B23">Iturralde et al. (2023b)</xref>.</p>
<p>Computer vision and photogrammetry are widely applied to enhance geometric fidelity during data capture. ArUco and AprilTags are among the most used fiducial markers for localizing building elements in unstructured environments <xref ref-type="bibr" rid="B19">Iturralde et al. (2019)</xref> and <xref ref-type="bibr" rid="B49">Zhang et al. (2021)</xref>. <xref ref-type="bibr" rid="B11">Feng et al. (2014)</xref> and <xref ref-type="bibr" rid="B44">Tish et al. (2020)</xref> implemented monocular or RGB-D vision systems to localize fa&#xe7;ade components and improve assembly precision. UAV-based systems for facade inspection and marker placement are gaining popularity for their efficiency in reaching tall structures (<xref ref-type="bibr" rid="B17">Hsu et al., 2024</xref>).</p>
<p>Despite these advancements, many approaches remain fragmented and manually intensive. Most systems do not incorporate a feedback loop that updates the building model based on accurate on-site measurements. Additionally, integration between web-based data collection and real-time layout reconfiguration is limited.</p>
</sec>
<sec id="s2-2">
<title>2.2 CAM</title>
<p>CAM platforms are critical in translating 3D models and layout definitions into manufacturable components. Studies such as <xref ref-type="bibr" rid="B40">Sandberg et al. (2016)</xref> and <xref ref-type="bibr" rid="B25">Iturralde et al. (2024)</xref> explored the use of Revit, Dynamo, and Dietrich&#x2019;s&#xae; software to automatically generate timber frame components, connector locations, and insulation layers for prefab facades. <xref ref-type="bibr" rid="B28">Lasarte et al. (2017)</xref> and <xref ref-type="bibr" rid="B21">Iturralde et al. (2022)</xref> proposed data workflows linking geometric modeling to the generation of manufacturing-ready instructions, incorporating data structures compatible with CNC (Computer Numerical Control) fabrication.</p>
<p>To enable mass customization while maintaining manufacturability, layout algorithms must account for production constraints such as minimum/maximum module sizes, alignment tolerances, and connector types. <xref ref-type="bibr" rid="B2">Augustynowicz et al. (2021)</xref> implemented parametric design frameworks for multi-robot fabrication of wood facades, while <xref ref-type="bibr" rid="B36">Pan et al. (2018)</xref> and <xref ref-type="bibr" rid="B37">Pan et al. (2020a)</xref> highlighted the importance of early integration of manufacturing logic into renovation planning.</p>
<p>Still, one of the key limitations in the literature is the lack of synchronization between modeled layouts and actual site conditions. Errors in the data acquisition stage often propagate through CAM, leading to misalignment during assembly. Furthermore, few workflows automate error correction once physical fabrication begins.</p>
</sec>
<sec id="s2-3">
<title>2.3 Robotic assembly</title>
<p>The use of robotics in the on-site assembly of prefabricated modules has been a growing field of investigation. <xref ref-type="bibr" rid="B16">Hook (2016)</xref> and <xref ref-type="bibr" rid="B26">Kasperzyk et al. (2017)</xref> presented early concepts of robotic arms for facade fabrication and reconstruction. <xref ref-type="bibr" rid="B20">Iturralde et al. (2021)</xref> and <xref ref-type="bibr" rid="B21">Iturralde et al. (2022)</xref> explored different robotic strategies for assembling prefabricated wall systems, including rail-mounted manipulators for extended reach. Vision-based closed-loop systems have also been proposed to guide pick-and-place tasks (<xref ref-type="bibr" rid="B11">Feng et al., 2014</xref>; <xref ref-type="bibr" rid="B44">Tish et al., 2020</xref>; <xref ref-type="bibr" rid="B1">Ali et al., 2021</xref>).</p>
<p>Robotic platforms that integrate with digital models via ROS and CAD workflows have demonstrated promising results in handling diverse component geometries and layout configurations (<xref ref-type="bibr" rid="B24">Iturralde et al., 2023c</xref>). Marker-based localization systems (<xref ref-type="bibr" rid="B39">Romero-Ramirez et al., 2018</xref>; <xref ref-type="bibr" rid="B13">Garrido-Jurado et al., 2016</xref>) combined with motion planners like <xref ref-type="bibr" rid="B8">Chitta et al. (2012)</xref> have been used to ensure flexible, adaptive operation in semi-structured environments.</p>
<p>However, most systems remain confined to laboratory-scale prototypes or simulation environments. Key challenges that remain unresolved include adaptability to non-flat surfaces, regulatory constraints for on-site deployment, and safety compliance for operation in real building conditions. Furthermore, multi-storey scalability and marker-less operation have yet to be fully addressed.</p>
<p>While significant progress has been made in each domain offer a fully integrated pipeline that spans from online data capture to on-site robotic execution. This paper addresses these limitations by developing and validating an end-to-end workflow that integrates online modeling, automated CAM generation, and flexible robotic assembly for prefabricated facade modules.</p>
</sec>
</sec>
<sec id="s3">
<title>3 Integrated workflow</title>
<p>The integrated workflow depicted in <xref ref-type="fig" rid="F2">Figure 2</xref> showcases an integrated workflow for data-driven building renovation, encompassing processes from initial data acquisition to robotic assembly. The process commences with the acquisition of data online, which furnishes contemporary information regarding the prevailing structure. This data informs the generation of an Existing Building Modeling BIM, serving as a foundational digital representation. Consequently, a Building Renovation Project BIM is derived, integrating renovation objectives and design adjustments. The implementation of an accurate measurement and adjustment BIM loop is instrumental in ensuring precision, a process that involves the feedback of refined data to both the existing and project BIM models. AprilTags are utilized to facilitate spatial localization and tracking during on-site operations, thereby enabling the alignment of digital plans with physical environments. Subsequently, the information is relayed to the Assembly CAM stage, where computer-aided manufacturing instructions are generated based on the BIM data. Robotic Assembly is responsible for executing the renovation tasks, leveraging CAM outputs and real-time spatial data to facilitate automated construction activities with a high degree of precision.</p>
<fig id="F2" position="float">
<label>FIGURE 2</label>
<caption>
<p>Integrative Workflow overview.</p>
</caption>
<graphic xlink:href="fbuil-11-1649278-g002.tif">
<alt-text content-type="machine-generated">Flowchart illustrating a process starting with online data acquisition, followed by existing building modeling (BIM), then building renovation project (BIM). Accurate measurement with AprilTags leads to manufacturing CAM, concluding with robotic assembly. An adjustment process connects back to the building modeling and renovation stages.</alt-text>
</graphic>
</fig>
<sec id="s3-1">
<title>3.1 Online data acquisition platform and building modeling</title>
<p>The necessity to address the growing demands of climate action has resulted in the construction industry, particularly in the field of building renovation, becoming a leading centre for environmental innovation. However, traditional renovation approaches frequently exhibit deficiencies in terms of fragmented workflows and excessive reliance on manual processes, which impede scalability and widespread adoption. Digital tools that are efficient, accurate, and user-friendly are essential to overcome these limitations and support large-scale energy retrofitting. In this context, online building modelling emerges as a crucial solution by significantly reducing the need for on-site visits and manual measurements, streamlining the early stages of renovation, and accelerating the overall process.</p>
<sec id="s3-1-1">
<title>3.1.1 Method</title>
<p>In response, this study introduces a structured online platform tailored to streamline the data acquisition and modeling processes vital for building renovation. This platform provides a systematic approach, guiding users through a series of steps that begin with the collection of fundamental geometric data and culminate in the creation of a normalized 3D model compatible with BIM formats, such as. ifc shown below. By automating critical steps and ensuring data integrity, the platform addresses the fundamental limitations of current practices while promoting accessibility for non-expert users.</p>
<p>
<monospace>Enter project name: test01</monospace>
</p>
<p>
<monospace>Enter building name: building01</monospace>
</p>
<p>
<monospace>Enter building height in meters: 12</monospace>
</p>
<p>
<monospace>Enter number of floors: 4</monospace>
</p>
<p>
<monospace>Floor height is: 3.0</monospace> m</p>
<p>
<monospace>Enter changed height of each floor: 3</monospace>
</p>
<p>
<monospace>Building height is: 12.0</monospace> m</p>
<p>
<monospace>Enter extrusion length in meters: 0.3</monospace>
</p>
<p>The data acquisition platform uses a modular pipeline to generate a normalised 3D representation of building fa&#xe7;ades, incorporating both user inputs and image-based detection. As shown in <xref ref-type="fig" rid="F1">Figure 1</xref>, the process begins with the collection of two types of information from the user: (1) fa&#xe7;ade images and (2) basic building metadata, such as the number of floors, total height, and extrusion depth. These are submitted to the platform, where the geometric data is processed alongside a vision-based module that uses pretrained algorithms to extract fa&#xe7;ade opening features (e.g., windows and balconies). This step produces a. json file containing spatial data on the openings in the fa&#xe7;ade.</p>
<p>As illustrated in <xref ref-type="fig" rid="F3">Figure 3</xref>, the user-submitted metadata is used separately to generate an initial model structure represented as a. json file without opening information (Process 2). The detected openings are pre-processed and refined (Process 3), after which the two data streams are combined into a unified JSON file containing complete geometric and topological data (Process 4). The platform then generates a. json file with integrated opening information (Process 5) and performs normalisation (Process 6) to produce a final file that complies with BIM standards. This normalised file is structured for compatibility with downstream tools, including FreeCAD, IFC exporters, and CAM modules. The modular nature of this pipeline ensures flexibility, allowing updates to individual steps without disrupting the entire workflow. The result is a high-fidelity digital representation of the building that supports accurate energy modeling and renovation planning. This stepwise approach has been shown to reduce manual intervention and to promote consistency and reproducibility across projects, a critical advantage in large-scale renovation efforts (<xref ref-type="bibr" rid="B12">Ferrandiz et al., 2018</xref>; <xref ref-type="bibr" rid="B29">Mainicheva et al., 2017</xref>; <xref ref-type="bibr" rid="B7">Chegu Badrinath et al., 2016</xref>).</p>
<fig id="F3" position="float">
<label>FIGURE 3</label>
<caption>
<p>The flowchart of the data acquisition platform.</p>
</caption>
<graphic xlink:href="fbuil-11-1649278-g003.tif">
<alt-text content-type="machine-generated">Flowchart depicting a data acquisition platform process. Buildings provide images and information to a platform, generating a JSON file of openings info. User input creates a JSON file without openings info. The data undergoes processes to generate processed and normalized JSON files, involving six steps labeled as Processes 1 to 6.</alt-text>
</graphic>
</fig>
<p>The platform addresses the issue of incomplete user input&#x2014;especially for building heights&#x2014;by integrating a height estimation feature grounded in projective geometry. This algorithm utilizes camera parameters and image-based measurements to compute real-world building heights, even in cases where data is sparse. The user is only required to provide the horizontal distance, D. The remaining values, such as sensor size and resolution, are automatically extracted, thereby significantly reducing the barriers to accurate modeling (<xref ref-type="bibr" rid="B14">Gerum et al., 2019</xref>).</p>
</sec>
<sec id="s3-1-2">
<title>3.1.2 Experimental validation</title>
<p>The platform&#x2019;s viability was substantiated through a series of pilot studies on buildings of varying complexity. In the case in <xref ref-type="fig" rid="F4">Figure 4</xref>, a building with six facades was processed to verify the platform&#x2019;s fundamental functionality.</p>
<fig id="F4" position="float">
<label>FIGURE 4</label>
<caption>
<p>Example of the simple building.</p>
</caption>
<graphic xlink:href="fbuil-11-1649278-g004.tif">
<alt-text content-type="machine-generated">Map section highlighting a location with an arrow pointing to a red-roofed building. Adjacent images show a multi-story building from different angles with balconies, parked cars, and cloudy skies. Below, 3D models of a building with red roofs and green outlines are displayed.</alt-text>
</graphic>
</fig>
<p>To be mentioned, the input of this platform should be from users, and the output should be the final normalized. json file, which can be transferred into the. ifc file for the visualization. And the approximate external shape of the model and the address information (Munich, Germany) are provided here on the left side of <xref ref-type="fig" rid="F4">Figure 4</xref>.</p>
</sec>
</sec>
<sec id="s3-2">
<title>3.2 Semi-automated building renovation project</title>
<p>In the context of building renovation, the integration of prefabricated fa&#xe7;ade modules is a critical step in bridging the gap between digital design and physical implementation. This section addresses key challenges by proposing a data-driven approach that links early-stage building modeling and measurement with downstream manufacturing and on-site assembly. A major barrier to the adoption of prefabricated modules, especially those incorporating renewable energy systems, lies in the need for manual layout drafting and iterative adjustments by designers throughout the renovation process&#x2014;a task that is both time-intensive and difficult to scale. To overcome this, the proposed system introduces two innovations: first, an automated generation of optimized fa&#xe7;ade layouts and solar panel distribution based on existing building models; and second, a dynamic adjustment mechanism that adapts the layout in real time according to the renovation phase and the evolving precision of measurement data.</p>
<sec id="s3-2-1">
<title>3.2.1 Method</title>
<p>The renovation process begins with the generation of a 3D model of the building using publicly available facade images and OpenStreetMap (OSM) floor plans. From these inputs, a structured geometric model is created as shown in <xref ref-type="fig" rid="F5">Figure 5a</xref>, which serves as the foundation for the placement of the modules. The FreeCAD-based plugin was developed to generate layout configurations of prefabricated facade elements integrated with photovoltaic and thermal solar panels. This tool allows users to analyze wall geometries, extract facade features (e.g., height, width, corner points, and window locations), and simulate solar panel arrangement strategies, streamlined early-stage planning that is typically time and labor-intensive.</p>
<fig id="F5" position="float">
<label>FIGURE 5</label>
<caption>
<p>
<bold>(a)</bold> Building model generated with building images and OSM, in this case, the demo-building in Milan. <bold>(b)</bold> Capturing the real building images with AprilTags, which are located at the critical points of the facade. Example of the demo building in Milan. <bold>(c)</bold> Building model and detailed prefabricated module layout of the demo-building in Milan. <bold>(d)</bold> Output of the code described in this section RG1.2, that includes a prefabricated layout definition, including solar panels and registration areas in the building model of the demo-building in Milan, Italy.</p>
</caption>
<graphic xlink:href="fbuil-11-1649278-g005.tif">
<alt-text content-type="machine-generated">Four panels showing 3D models of a building.a) A plain white building with green balconies.b) A building with a crane beside it, showing structural analysis with colored dots and lines.c) A building with grid lines and trees on a green base.d) A detailed building with grid patterns, balconies, and a white grid floor.</alt-text>
</graphic>
</fig>
<p>The core goal is to automate the placement of prefabricated modules on the building facade based on geometric feasibility and energy efficiency. A multi-step logic is applied to optimize the number of solar panels while respecting architectural constraints, such as window positions and panel dimensions. The layout generation process shown in <xref ref-type="fig" rid="F6">Figure 6</xref> is completed in minutes and provides detailed visualizations, facilitating informed decisions by architects and engineers. The modules include structural frames, insulation layers, and wiring pathways, making them ready for robotic assembly.</p>
<fig id="F6" position="float">
<label>FIGURE 6</label>
<caption>
<p>Flow-chart of the solution RG1.2. The inputs are shown in gray, the outputs in green, and the steps required in yellow.</p>
</caption>
<graphic xlink:href="fbuil-11-1649278-g006.tif">
<alt-text content-type="machine-generated">Flowchart illustrating the process of building data acquisition via OSM and images, leading to a 3D building model. Key stages include extraction of building geometry, creation of vertical separators, and allocation of registration areas. The flow includes checking if panels fit, optimizing panel usage, and generating module layouts with connectors, resulting in visual output.</alt-text>
</graphic>
</fig>
</sec>
<sec id="s3-2-2">
<title>3.2.2 Experimental validation</title>
<p>Once the initial layout is approved, precise on-site measurements are captured using AprilTags positioned on key facade points like window edges and connection anchors as shown in <xref ref-type="fig" rid="F5">Figure 5b</xref>. These measurements are used to update the digital model with higher accuracy. The system then automatically reconfigures the prefabricated module layout to align with the measured geometry, minimizing errors during production and installation, as shown in <xref ref-type="fig" rid="F5">Figure 5c</xref>. This adjustment process addresses the limitations of initial online modeling and enhances the reliability of the final output.</p>
<p>All outputs&#x2014;including updated FreeCAD models, JSON files with module data, and Excel reports listing connector positions&#x2014;are structured to support direct integration with robotic fabrication workflows. These outputs also include dimensional data critical for CAM, enabling precise prefabrication of the components.</p>
<p>An example application on a complex 3,000 m<sup>2</sup> facade (the Milan demo building) demonstrated that what once required over 1,000 h of manual drafting can now be accomplished in under an hour with this system (25 min each for layout definition and realignment). <xref ref-type="fig" rid="F5">Figure 5d</xref> illustrates the updated building model after layout optimization.</p>
<p>This implementation showcases how a data-driven and semi-automated workflow&#x2014;starting from online modeling and ending in precise on-site layout adjustment&#x2014;can transform renovation into a scalable, industrialized process, significantly lowering cost and time while preserving architectural integrity and energy performance.</p>
</sec>
</sec>
<sec id="s3-3">
<title>3.3 Facade geometry accurate measurement</title>
<p>While the building renovation project is done, the AprilTag-based technique enables high-precision enhancement of facade geometry, ensuring greater modeling fidelity before the CAM phase.</p>
<sec id="s3-3-1">
<title>3.3.1 Method</title>
<p>First to be mentioned, the development of a quadcopter with an end effector was undertaken based on <xref ref-type="bibr" rid="B17">Hsu et al. (2024)</xref>. The following text is an excerpt from the aforementioned source: The quadcopter will approach the target position. The application of the load to the end effector is indicated by the presence of the AprilTags. The reverse side of the tags bears the following inscription: The adhesive is applied in the following manner. Following the establishment of contact between the tags, the surface on which the pressure is to be applied by the quadcopter is hereby designated as the &#x201c;target surface&#x201d;. It is imperative that the tags are utilized in order to guarantee a robust binding. The process is indicated as illustrated in <xref ref-type="fig" rid="F7">Figure 7</xref>.</p>
<fig id="F7" position="float">
<label>FIGURE 7</label>
<caption>
<p>Sticking process.</p>
</caption>
<graphic xlink:href="fbuil-11-1649278-g007.tif">
<alt-text content-type="machine-generated">Three-panel sequence showing a drone attaching a black and white tag to a wall. Panel 1 shows the drone approaching the wall, panel 2 depicts the drone slightly closer, and panel 3 shows the drone attaching the tag to the wall.</alt-text>
</graphic>
</fig>
<p>Traditional survey methods, while often precise, tend to be labor-intensive and constrained by logistical and financial limitations. To address these challenges, fiducial markers known as AprilTags have been employed to enable efficient 3D reconstruction of building facades using only digital imaging and straightforward computational techniques (<xref ref-type="bibr" rid="B49">Zhang et al., 2021</xref>). These markers, when arranged in systematic grid formations on the surface of a structure, facilitate the derivation of spatial geometry through triangulation methods based on calibrated camera imagery.</p>
<p>A key innovation in the proposed integrative workflow is the use of a best-fitting plane to reduce spatial noise and improve the alignment of coplanar data points derived from AprilTag positions. By applying a least-squares optimization, the reconstructed points are projected onto the most likely planar surface, significantly enhancing the accuracy of the model even in the presence of minor measurement errors or optical distortions (<xref ref-type="bibr" rid="B23">Iturralde et al., 2023b</xref>). This correction method is particularly valuable when the resulting geometric model is used for applications with stringent spatial requirements, such as determining optimal solar panel placement or simulating urban light exposure.</p>
<p>Central to the integrative workflow&#x2019;s accuracy is a robust approach to distance estimation. This is achieved through the use of effective focal length and sensor pixel size, which together allow for precise real-world measurements based on the apparent size of the tags in the image frame. The system leverages camera calibration data and computes distances using a similarity-based geometric model, ensuring that the spatial positions of each tag can be accurately resolved. The experimental setup employed a high-resolution Sony Alpha 7R IV camera, with a computed effective focal length of approximately 13,257.6 in appropriate units, delivering sub-millimeter accuracy in tag distance estimation.</p>
</sec>
<sec id="s3-3-2">
<title>3.3.2 Experimental validation</title>
<p>In practical testing, a key factor affecting accuracy is the apparent size of the AprilTags within each image. For instance, when capturing a 15-meter-high building, the 200 mm <inline-formula id="inf14">
<mml:math id="m14">
<mml:mrow>
<mml:mo>&#xd7;</mml:mo>
</mml:mrow>
</mml:math>
</inline-formula> 200 mm tags appeared too small and blurred in wide-angle shots. To address this, photographs were taken from multiple viewpoints, with each image containing only four adjacent tags to ensure they appeared large and clear, as shown in <xref ref-type="fig" rid="F8">Figure 8a</xref>. This method allowed for detailed local captures while still covering the entire fa&#xe7;ade.</p>
<fig id="F8" position="float">
<label>FIGURE 8</label>
<caption>
<p>
<bold>(a)</bold> Shooting local targets. <bold>(b)</bold> Detection results.</p>
</caption>
<graphic xlink:href="fbuil-11-1649278-g008.tif">
<alt-text content-type="machine-generated">The first image shows a three-story building with numbered windows, highlighted in red, labeled from one to six. The second image displays a grid with five numbered squares, each marked from zero to four, with colored markers around them. Both images have an emphasis on labeling and coordination.</alt-text>
</graphic>
</fig>
<p>Once the distances to the individual tags are known, the system proceeds to determine their 3D coordinates relative to the camera. This is followed by projecting those coordinates onto the best-fitting plane, refining their placement before final distance measurements are made using Euclidean metrics. The AprilTag detection, as shown in <xref ref-type="fig" rid="F8">Figure 8b</xref>, and data processing were implemented using Python libraries such as the AprilTag detector and scikit-spatial for plane fitting, enabling a streamlined and accessible reconstruction integrative workflow with minimal manual intervention.</p>
<p>Additionally, for cooperating with AprilTags, the MK (Matching Kit), which is a set of components that includes a bespoke interface for the purpose of correcting any deviations that occurred during the placement of the AprilTags on the wall, is introduced here with regard to <xref ref-type="bibr" rid="B24">Iturralde et al. (2023c)</xref>. This MK is not predicated on a specific connector type; rather, it is founded upon a conceptual framework that delineates the interface between the facade and the wall. In previous phases of the research, the MK and its main components were defined. A series of tests was conducted, resulting in enhanced accuracy and reduced time consumption. The MK is comprised of three primary components (see <xref ref-type="fig" rid="F9">Figure 9</xref>).</p>
<fig id="F9" position="float">
<label>FIGURE 9</label>
<caption>
<p>Left: Flexibility of the MK. Right: The shape of the interfaces.</p>
</caption>
<graphic xlink:href="fbuil-11-1649278-g009.tif">
<alt-text content-type="machine-generated">Diagram showing two construction scenarios involving a 2D module and an existing building. On the left, part 2 is positioned with flexibility for placement beside part 1. On the right, part 2 is integrated at the interface between the module and the building. Labels indicate parts and dimensions.</alt-text>
</graphic>
</fig>
</sec>
</sec>
<sec id="s3-4">
<title>3.4 Assembly CAM</title>
<p>The results from the AprilTags phase, especially the clear definition of module shapes and connector positions, provide a strong digital base for the next manufacturing steps. The system can turn these layouts and measurements into machine-readable files. This smooth connection with CAM tools allows for the accurate production of facade parts like solar panels and frames, with little manual work. Moving from digital planning to automated making is a key step toward a fully connected and scalable renovation process.</p>
<sec id="s3-4-1">
<title>3.4.1 Method</title>
<p>An integral step in streamlining facade renovation using prefabricated modules is the seamless integration of automated layout generation with CAM systems. In the workflow, once the primary layout of prefabricated facade modules is derived from a 3D Point Cloud, this geometric information is directly linked to CAD/BIM environments and ultimately synchronized with CAM platforms to enable digital fabrication of the modules (<xref ref-type="bibr" rid="B40">Sandberg et al., 2016</xref>). This process effectively minimizes manual intervention and ensures that the layout generated from existing building geometries can be translated into manufacturable components with minimal redesign.</p>
<p>The CAM integration is facilitated through interoperability with software such as Revit via Dynamo&#x2122; scripts, which convert the semi-automatically extracted polygonal module boundaries into CAD-readable formats (<xref ref-type="bibr" rid="B40">Sandberg et al., 2016</xref>). These formats can then be used to define the structure and configuration of prefabricated panels in manufacturing software like Dietrich&#x2019;s&#xae;, which automates the detailing of structural components such as studs, insulation layers, and fireproof barriers once the primary layout is defined (<xref ref-type="bibr" rid="B40">Sandberg et al., 2016</xref>; <xref ref-type="bibr" rid="B25">Iturralde et al., 2024</xref>). This bridge from data acquisition to fabrication not only enhances design efficiency but also enables mass customization of building envelopes while preserving the geometric fidelity of existing structures.</p>
<p>A crucial advantage of this approach lies in its adaptability to production constraints. The semi-automated layout algorithm takes into account key CAM parameters, such as maximum and minimum module widths, slab positions for connector placement, and alignment with existing window openings (<xref ref-type="bibr" rid="B40">Sandberg et al., 2016</xref>). These design rules are incorporated upstream in the layout generation process to ensure that the final output adheres to manufacturing limitations, thus avoiding costly revisions downstream.</p>
<p>However, the success of the CAM integration is strongly dependent on the quality of the initial Point Cloud. As highlighted in the study, inaccurate or incomplete point data can propagate through the entire integrative workflow, resulting in deviations between the generated layout and actual building conditions&#x2014;especially problematic when modules must fit tightly to existing facades with minimal tolerance (<xref ref-type="bibr" rid="B40">Sandberg et al., 2016</xref>).</p>
</sec>
<sec id="s3-4-2">
<title>3.4.2 Experiment validation</title>
<p>Based on the rationale above, a CAM generation workbench named <italic>ENSNARE_CAD_CAM</italic> is created in FreeCAD, allowing geometry properties of individual profiles across an entire module to be exported as a single <italic>JSON</italic> file. The geometry properties that can be exported include each profile&#x2019;s dimensions, CoM (Center of Mass), and placement relative to the origin of the module as shown in <xref ref-type="fig" rid="F10">Figure 10a</xref>.</p>
<fig id="F10" position="float">
<label>FIGURE 10</label>
<caption>
<p>
<bold>(a)</bold> Flowchart of the geometry analyzing procedure using FreeCAD. <bold>(b)</bold> Flowchart showing current CAM procedure.</p>
</caption>
<graphic xlink:href="fbuil-11-1649278-g010.tif">
<alt-text content-type="machine-generated">Diagram showing a workflow between FreeCAD and ROS. FreeCAD processes a .step file with ENSNARE_CAD_CAM, outputting Placement, COM, and Profile names into a JSON file. ROS uses a service call to get profile assembly sequence, and profile position, orientation, and COM. Separately, an Excel file is converted into a Python dictionary, then processed with a ROS service call to get the number of modules and a point of pickup.</alt-text>
</graphic>
</fig>
<p>A Python script is implemented to extract the coordinates of each PUP (Pick-Up Point) and derive the optimal sequence based on the <italic>JSON</italic> file. A ROS wrapper is then implemented to expose this two information as a ROS service, enabling the main controller to request the data at run time. By requesting the assembly sequence, a list of strings containing the names of the modules is returned. Sequentially, quarrying with the name of each module, the PUP coordinates are returned.</p>
<p>With the automated prefabricated facade layout definition process developed in <xref ref-type="bibr" rid="B23">Iturralde et al. (2023b)</xref>, the properties are automatically extracted from the CAD model and exported to a <italic>Excel</italic> file, from which a Python dictionary is implemented to index these data in an easy-to-retrieve manner. The same as before, a ROS wrapper exposes the relevant data as ROS services. This new procedure increases data retrieval efficiency, as shown in <xref ref-type="fig" rid="F10">Figure 10b</xref>.</p>
</sec>
</sec>
<sec id="s3-5">
<title>3.5 Robotic assembly</title>
<p>The subsequent phase of the pipeline focuses on translating the detailed fabrication outputs generated in the CAM workflow into precise physical operations through robotic assembly. The CAM-generated layout encapsulates the geometric and structural parameters of each prefabricated component, as well as embedding essential metadata, such as PUP and assembly sequences, required for automation. These outputs serve as direct input for the robotic system, thereby facilitating a seamless transition from design to execution. The robotic platform is programmed to autonomously interpret, locate, and assemble modules with minimal human intervention by leveraging structured data exported via FreeCAD and indexed through ROS services. This integration serves to illustrate the continuity of the end-to-end workflow, wherein the fidelity of digital planning is preserved and actualized through intelligent robotic manipulation.</p>
<sec id="s3-5-1">
<title>3.5.1 Method</title>
<p>Before updating the layout to match real site conditions, it&#x2019;s important to make sure the initial design fits the building as it actually is. Since older buildings often have small differences or irregular shapes, this step helps prepare the layout for accurate adjustment. The next part explains how the layout is first created using the building model and design rules.</p>
<p>The architecture implements a data-driven pipeline that systematically processes geometric information from CAD models into executable robot trajectories. The pipeline begins with the <italic>Geometry Analyzer</italic>, which parses the CAD model to extract critical parameters including component dimensions, PUPs, and optimal assembly sequences based on spatial constraints. These parameters are encoded as transformation matrices and sequential instructions that flow to the <italic>Motion Generator</italic>. This module performs coordinate frame transformations between the module origin frame MO and the robot&#x2019;s world frame w using homogeneous transformations, converting design specifications into robot-specific target poses. The resulting pick-and-place coordinates are then processed by the <italic>Robotic System Control</italic> modules, which decompose the assembly task into synchronized trajectories for the manipulator, linear rail, and gripper subsystems. This modular architecture enables real-time adaptation to component variations while maintaining assembly precision through feedback between the digital model and physical execution.</p>
<sec id="s3-5-1-1">
<title>3.5.1.1 Hardware design</title>
<p>The designed prototype of the robotic system for assembling prefabricated modules is depicted in <xref ref-type="fig" rid="F11">Figure 11a</xref>. This system primarily comprises a UR10e industrial robot manipulator (<xref ref-type="bibr" rid="B46">Universal Robots, 2023</xref>) integrated with a linear rail unit. The manipulator&#x2019;s base is mounted on the rail, extending the robotic arm&#x2019;s reach and creating a 3.0 m <inline-formula id="inf15">
<mml:math id="m15">
<mml:mrow>
<mml:mo>&#xd7;</mml:mo>
</mml:mrow>
</mml:math>
</inline-formula> 1.4 m working area within the fixed frame. The linear rail is driven by a stepper motor and gearbox, providing sufficient torque to move the manipulator, as discussed in <xref ref-type="bibr" rid="B21">Iturralde et al. (2022)</xref>. A Schmalz vacuum gripper (<xref ref-type="bibr" rid="B41">Schmalz, 2023</xref>) is attached to the UR10e as the end-effector, facilitating the pick-and-place operation of the prefabricated profiles during assembly. The gripper can be interchanged with other types, depending on the geometric properties of the prefabricated components, to ensure a more stable grip. Additionally, a camera is mounted on the robotic arm&#x2019;s wrist to localize components, enhancing accuracy and flexibility. An input platform feeds the prefabricated components to the robot, which then picks them up and assembles them on the designated assembly platform. <xref ref-type="fig" rid="F11">Figure 11b</xref> demonstrates the operating robotic system in the assembly process, transporting the component to the target position on the assembly platform.</p>
<fig id="F11" position="float">
<label>FIGURE 11</label>
<caption>
<p>
<bold>(a)</bold> Hardware design overview. <bold>(b)</bold> The real system in assembly process.</p>
</caption>
<graphic xlink:href="fbuil-11-1649278-g011.tif">
<alt-text content-type="machine-generated">Diagram and photo of a robotic assembly setup. The top section is a diagram showing labeled components: a linear rail, fixed frame, UR10e robot with a camera and vacuum gripper, input and assembly platforms, and prefabricated profiles. The bottom section is a photo of the actual assembly system in a lab environment, showcasing the robot arm and its attachment.</alt-text>
</graphic>
</fig>
</sec>
<sec id="s3-5-1-2">
<title>3.5.1.2 Software design</title>
<p>The primary function of the software is to determine the optimal positions and orientations for the gripper to effectively pick and place prefabricated profiles of varying sizes and command the robot to move accordingly to finish the assembly process while avoiding collision with the system boundaries and other components along the way. To achieve this, a <italic>geometry analyzer</italic> is employed to extract the geometry properties of the prefabricated modules from their CAD model and calculate an optimal assembly sequence as well as the coordinate of a PUP for each component, i.e., where the gripper should grasp the component. Based on this information, a <italic>motion generator</italic> calculates the PUP coordinates relative to the robot frame as the target poses for the robotic gripper. The target poses are then sent to each part of the hardware system in a sequence to execute the trajectory and complete the assembly process. A flowchart of the whole program is illustrated in <xref ref-type="fig" rid="F12">Figure 12a</xref>.</p>
<fig id="F12" position="float">
<label>FIGURE 12</label>
<caption>
<p>
<bold>(a)</bold> Flow chart of the main controller. <bold>(b)</bold> Software architecture and data flow.</p>
</caption>
<graphic xlink:href="fbuil-11-1649278-g012.tif">
<alt-text content-type="machine-generated">Flowchart for an assembly sequence depicts steps: get assembly sequence, obtain pick-up point, generate trajectory, move to pick-up position, turn gripper on, proceed to place position, turn gripper off, and check if it's the last element. If yes, end; if no, repeat. Below, a system diagram shows interactions among CAM, Image Processor, Arm Controller, Gripper Controller, and PLC to control motion, gripper, and motor functions. Robot hardware images include a camera, robotic arm, gripper, and motorized rail.</alt-text>
</graphic>
</fig>
<p>The software is designed modularly and is developed within the ROS (Robot Operating System) framework for easy interfacing with the robot hardware and seamless communication between modules. <xref ref-type="fig" rid="F12">Figure 12b</xref> depicts the software architecture and the data flow between different modules. The design of each module is explained in detail in the following section. <xref ref-type="sec" rid="s3-5-2-1">Section 3.5.2.1</xref> introduces how to extract the geometry properties of the profiles from the CAD model. <xref ref-type="sec" rid="s3-5-2-2">Section 3.5.2.2</xref> explains how the coordinates are transformed into the robot frame to calculate pick-and-place poses. The robot hardware controller (<xref ref-type="sec" rid="s3-5-2-3">Section 3.5.2.3</xref>) consists of three parts, each controlling one hardware component of the system, i.e., the UR10e manipulator, linear rail motor, and the gripper. An optional camera with a marker-based visual localization program, explained in <xref ref-type="sec" rid="s3-5-3">Section 3.5.3</xref>, aids a more flexible placement of the profiles as well as the input and assembly platforms, and enhances the accuracy.</p>
</sec>
</sec>
<sec id="s3-5-2">
<title>3.5.2 Software modules</title>
<p>Once the layout has been corrected based on real measurements, it needs to be turned into files that machines and robots can use. This step is important to make sure each part is made and placed correctly. The next part shows what kind of output files are created and how they are used in the production process.</p>
<sec id="s3-5-2-1">
<title>3.5.2.1 Geometry analyzer</title>
<p>Two key pieces of information are required to be extracted from the CAD model to automate the assembly process of prefabricated profiles of various sizes. The first is the PUP, i.e., where the end-effector attaches when picking up. This is usually chosen at each profile&#x2019;s CoM to ensure stability during transportation by the robot arm. In our study, however, because the vacuum gripper can only attach objects from their surfaces, the PUP is selected as the CoM shifted by a certain height to the upper surface. In case the upper surface is irregular and the gripper cannot firmly attach the CoM point, the PUP is chosen by the geometry center of the largest plane. The second information required is the assembly sequence, i.e., in which order the profiles are picked and placed. Once all the PUPs are determined, an optimal sequence is derived through the nearest-neighbor algorithm that chooses the closest PUP as the next pick-up point.</p>
</sec>
<sec id="s3-5-2-2">
<title>3.5.2.2 Motion generator</title>
<p>With the PUP coordinates, the appropriate motion of the robot is generated to pick and place the profiles.</p>
<p>Based on <xref ref-type="disp-formula" rid="e1">Equation 1</xref>, the PUP coordinates obtained from the <italic>geometry analyser</italic> are relative to the module origin frame {MO} and can be represented by the homogeneous transformation<disp-formula id="e1">
<mml:math id="m16">
<mml:mrow>
<mml:mmultiscripts>
<mml:mrow>
<mml:mi mathvariant="bold">T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">PUP</mml:mi>
</mml:mrow>
<mml:none/>
<mml:mprescripts/>
<mml:none/>
<mml:mrow>
<mml:mi>M</mml:mi>
<mml:mi>O</mml:mi>
</mml:mrow>
</mml:mmultiscripts>
<mml:mo>&#x3d;</mml:mo>
<mml:mfenced open="[" close="]">
<mml:mrow>
<mml:mtable class="matrix">
<mml:mtr>
<mml:mtd columnalign="center">
<mml:mmultiscripts>
<mml:mrow>
<mml:mi mathvariant="bold">R</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">PUP</mml:mi>
</mml:mrow>
<mml:none/>
<mml:mprescripts/>
<mml:none/>
<mml:mrow>
<mml:mi>M</mml:mi>
<mml:mi>O</mml:mi>
</mml:mrow>
</mml:mmultiscripts>
</mml:mtd>
<mml:mtd columnalign="center">
<mml:mmultiscripts>
<mml:mrow>
<mml:mi mathvariant="bold">t</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">PUP</mml:mi>
</mml:mrow>
<mml:none/>
<mml:mprescripts/>
<mml:none/>
<mml:mrow>
<mml:mi>M</mml:mi>
<mml:mi>O</mml:mi>
</mml:mrow>
</mml:mmultiscripts>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="center">
<mml:mn>0</mml:mn>
</mml:mtd>
<mml:mtd columnalign="center">
<mml:mn>1</mml:mn>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:math>
<label>(1)</label>
</disp-formula>where <inline-formula id="inf16">
<mml:math id="m17">
<mml:mrow>
<mml:mmultiscripts>
<mml:mrow>
<mml:mi mathvariant="bold">R</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">PUP</mml:mi>
</mml:mrow>
<mml:none/>
<mml:mprescripts/>
<mml:none/>
<mml:mrow>
<mml:mi>M</mml:mi>
<mml:mi>O</mml:mi>
</mml:mrow>
</mml:mmultiscripts>
</mml:mrow>
</mml:math>
</inline-formula> and <inline-formula id="inf17">
<mml:math id="m18">
<mml:mrow>
<mml:mmultiscripts>
<mml:mrow>
<mml:mi mathvariant="bold">t</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi mathvariant="italic">PUP</mml:mi>
</mml:mrow>
<mml:none/>
<mml:mprescripts/>
<mml:none/>
<mml:mrow>
<mml:mi>M</mml:mi>
<mml:mi>O</mml:mi>
</mml:mrow>
</mml:mmultiscripts>
</mml:mrow>
</mml:math>
</inline-formula> denote the rotation and translation of PUP relative to the module origin, respectively. This coordinate needs to be transformed into the robot&#x2019;s world frame before being sent to the robot&#x2019;s planner.</p>
<p>For picking up, the PUPs are aligned in the same pre-defined pose on the input platform, so the robot picks up all the parts from the same place. However, the placements differ for different parts based on the PUP coordinates. Seeing from <xref ref-type="disp-formula" rid="e2">Equation 2</xref>, the user can pre-define a target pose for placing the whole module, i.e., the pose of the frame {MO} relative to the world frame of the robot&#x2019;s workspace {w}, denoted by <inline-formula id="inf18">
<mml:math id="m19">
<mml:mrow>
<mml:mmultiscripts>
<mml:mrow>
<mml:mi mathvariant="bold">T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>M</mml:mi>
<mml:mi>O</mml:mi>
</mml:mrow>
<mml:none/>
<mml:mprescripts/>
<mml:none/>
<mml:mrow>
<mml:mi>w</mml:mi>
</mml:mrow>
</mml:mmultiscripts>
</mml:mrow>
</mml:math>
</inline-formula>. Consequently, the target placing pose of each profile concerning the world frame is derived by the following homogeneous transformation:<disp-formula id="e2">
<mml:math id="m20">
<mml:mrow>
<mml:mmultiscripts>
<mml:mrow>
<mml:mi mathvariant="bold">T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>P</mml:mi>
<mml:mi>U</mml:mi>
<mml:mi>P</mml:mi>
</mml:mrow>
<mml:none/>
<mml:mprescripts/>
<mml:none/>
<mml:mrow>
<mml:mi>w</mml:mi>
</mml:mrow>
</mml:mmultiscripts>
<mml:mo>&#x3d;</mml:mo>
<mml:mmultiscripts>
<mml:mrow>
<mml:mi mathvariant="bold">T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>M</mml:mi>
<mml:mi>O</mml:mi>
</mml:mrow>
<mml:none/>
<mml:mprescripts/>
<mml:none/>
<mml:mrow>
<mml:mi>w</mml:mi>
</mml:mrow>
</mml:mmultiscripts>
<mml:mspace width="0.3333em"/>
<mml:mmultiscripts>
<mml:mrow>
<mml:mi mathvariant="bold">T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>P</mml:mi>
<mml:mi>U</mml:mi>
<mml:mi>P</mml:mi>
</mml:mrow>
<mml:none/>
<mml:mprescripts/>
<mml:none/>
<mml:mrow>
<mml:mi>M</mml:mi>
<mml:mi>O</mml:mi>
</mml:mrow>
</mml:mmultiscripts>
</mml:mrow>
</mml:math>
<label>(2)</label>
</disp-formula>
</p>
<p>In this way, the end-effector pose for picking up and placing down each component is calculated. The pick and place pose is sent to the robotic hardware controller to move the robot to the target position to complete the assembly sequence.</p>
</sec>
<sec id="s3-5-2-3">
<title>3.5.2.3 Robotic System Control</title>
<p>With the pick-and-place poses for the end-effector, trajectories of both the rail base and the robot arm are generated by utilizing the motion planning tool (<xref ref-type="bibr" rid="B33">MoveIt, 2023a</xref>). The entire robotic assembly unit, including the manipulator and linear axis system, is configured using MoveIt&#x2019;s setup assistant tool and visualized in RViz, the visualization tool of ROS, providing a simulation environment for offline testing. Since the whole system is perfectly modeled, there is no sim-to-real gap. Once the trajectories are validated in the simulation, they can be exactly repeated in the real system. The fixed structure of the assembly system, input and assembly platforms, as well as the facade components to be assembled, are all modeled as collision objects in <italic>MoveIt</italic>, allowing <italic>MoveIt</italic> to consider the geometry constraints and plan a collision-free trajectory.</p>
<p>The control of the robot system is divided into three parts, which are introduced in the following subsections.</p>
</sec>
<sec id="s3-5-2-4">
<title>3.5.2.4 Robotic arm motion control</title>
<p>To control the motion of the robotic arm, the official Universal Robot ROS Driver is utilized in conjunction with the trajectory planner <italic>MoveIt</italic>. With the Cartesian waypoints of the end-effector derived in the previous section, <italic>MoveIt</italic> calculates optimal, collision-free joint trajectories and inverse kinematics. The ROS driver writes the joint trajectory commands to the robot hardware while reading the actual joint states in real-time and feeding them back to the planner.</p>
</sec>
<sec id="s3-5-2-5">
<title>3.5.2.5 Gripper control</title>
<p>The electric pump of the vacuum gripper is connected to the manipulator UR10e through the robot&#x2019;s tool I/O. The <italic>UR ROS Driver</italic> also provides a ROS service interface to access all the robot&#x2019;s digital I/Os, including the tool I/O. With this service, we can easily turn on/off the vacuum suction force by calling the ROS service <monospace>set_io</monospace> to set/reset the tool output.</p>
</sec>
<sec id="s3-5-2-6">
<title>3.5.2.6 Linear rail motion control</title>
<p>The motion of the linear rail motor is controlled by a Beckhoff PLC (Programmable Logic Controller). The controller is programmed with the motion controller module in the TwinCAT 3 software platform. The integration involves careful motor behavior parameterization and calibration to ensure optimal performance and precision.</p>
<p>Additionally, two limit switches are installed at both ends of the rail, marking the maximum range of rail motion. When the robot reaches the end of the rail and triggers the sensor, a signal is fed back to the controller to stop the motor, enhancing the safety of the robotic system.</p>
<p>State Machine A state machine, as illustrated in <xref ref-type="fig" rid="F13">Figure 13</xref>, is implemented in the PLC main program to manage motor control. Each state corresponds to a specific function block that dictates a particular motor behavior. Upon starting the PLC, the linear axis system is powered on, after which the main program can trigger other states via ROS commands. These include &#x201c;Homing,&#x201d; &#x201c;Motion States,&#x201d; and &#x201c;Stop&#x201d;. The &#x201c;Motion States&#x201d; category encompasses the various movement options available from the PLC motion library, such as &#x201c;MoveAbsolute&#x201d;, &#x201c;MoveRelative&#x201d;, and &#x201c;MoveVelocity&#x201d;.</p>
<fig id="F13" position="float">
<label>FIGURE 13</label>
<caption>
<p>State machine of the PLC motor controller.</p>
</caption>
<graphic xlink:href="fbuil-11-1649278-g013.tif">
<alt-text content-type="machine-generated">Flowchart illustrating system states and transitions: Initial State leads to Power On, which transitions to Homing, Motion States, or Error via ROS commands. From Motion States, it can proceed to Stop or return to Error if an error occurs. Error resolves back to Power On if solved, or continues to Stop if not.</alt-text>
</graphic>
</fig>
<p>In the event of an error during motion, the state machine transitions to the <italic>Error</italic> state, where the error handler attempts to resolve the issue. If the error is successfully resolved, the system can resume motion upon receiving a new ROS command; otherwise, it will remain in the <italic>Stop</italic> state.</p>
<p>PLC-ROS integration to seamlessly integrate the PLC-controlled linear axis with the main ROS program, a communication interface is established using Beckhoff&#x2019;s ADS (Automation Device Specification) protocol. This TCP (Transmission Control Protocol)/IP (Internet Protocol) -based protocol enables real-time data exchange between the Beckhoff PLC and ROS on the main control PC in Linux, allowing synchronized control and feedback for both the linear axis and robotic arm.</p>
<p>The communication interface, implemented using Beckhoff&#x2019;s ADS C&#x2b;&#x2b; library (<xref ref-type="bibr" rid="B6">Beckhoff Automation, 2023</xref>), allows the main controller to interact with the PLC by specifying the PLC&#x2019;s IP address and AMS (Automation Message Specification) Net ID. This enables the reading and writing of key PLC variables, such as motor position and velocity, enabling the main controller in ROS to send commands or read states efficiently. However, the communication channel is blocked during data transmission in one direction. To enable simultaneous reading and writing, the ADS Notifications protocol is employed to cyclically transmit motor state data to the main controller in a background thread without interrupting motion execution.</p>
</sec>
</sec>
<sec id="s3-5-3">
<title>3.5.3 Accuracy improvement with visual marker detection</title>
<p>The successful execution of the assembly task relies on high precision in the installation and calibration of the robotic assembly system. Any offsets between the simulated and real model, for instance, the displacement of the manipulator&#x2019;s base on the rail or imprecise calibration of the location of input and assembly platforms, lead to deviation of the final assembly result. To eliminate potential errors and avoid cumbersome calibration, a camera is mounted on the wrist of the robot arm to detect the position of the platforms and the profiles at run-time. Advanced ArUco markers (<xref ref-type="bibr" rid="B27">Kedilioglu et al., 2021</xref>) are attached to the platforms and the PUP on the profiles. A marker-based vision approach is utilized to accurately detect and calculate the pose relation between the end-effector and the profiles.</p>
<p>As shown in <xref ref-type="disp-formula" rid="e3">Equation 3</xref>, a hand-eye calibration that determines the transformation between the camera optical frame and the end-effector frame <inline-formula id="inf19">
<mml:math id="m21">
<mml:mrow>
<mml:mmultiscripts>
<mml:mrow>
<mml:mi mathvariant="bold">T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>c</mml:mi>
</mml:mrow>
<mml:none/>
<mml:mprescripts/>
<mml:none/>
<mml:mrow>
<mml:mi>e</mml:mi>
<mml:mi>e</mml:mi>
</mml:mrow>
</mml:mmultiscripts>
</mml:mrow>
</mml:math>
</inline-formula> is conducted using <italic>MoveIt</italic>&#x2019;s hand-eye calibration tool (<xref ref-type="bibr" rid="B34">MoveIt, 2023b</xref>). ArUco marker detection is implemented with OpenCV&#x2019;s ArUco module library (<xref ref-type="bibr" rid="B35">OpenCV, 2023</xref>), which provides pose estimation of the marker in the camera optical frame <inline-formula id="inf20">
<mml:math id="m22">
<mml:mrow>
<mml:mmultiscripts>
<mml:mrow>
<mml:mi mathvariant="bold">T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>m</mml:mi>
</mml:mrow>
<mml:none/>
<mml:mprescripts/>
<mml:none/>
<mml:mrow>
<mml:mi>c</mml:mi>
</mml:mrow>
</mml:mmultiscripts>
</mml:mrow>
</mml:math>
</inline-formula>. Thus, the transformation between the marker (target pose) to the end-effector frame (current pose) can be obtained by:<disp-formula id="e3">
<mml:math id="m23">
<mml:mrow>
<mml:mmultiscripts>
<mml:mrow>
<mml:mi mathvariant="bold">T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>m</mml:mi>
</mml:mrow>
<mml:none/>
<mml:mprescripts/>
<mml:none/>
<mml:mrow>
<mml:mi>e</mml:mi>
<mml:mi>e</mml:mi>
</mml:mrow>
</mml:mmultiscripts>
<mml:mo>&#x3d;</mml:mo>
<mml:mmultiscripts>
<mml:mrow>
<mml:mi mathvariant="bold">T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>c</mml:mi>
</mml:mrow>
<mml:none/>
<mml:mprescripts/>
<mml:none/>
<mml:mrow>
<mml:mi>e</mml:mi>
<mml:mi>e</mml:mi>
</mml:mrow>
</mml:mmultiscripts>
<mml:mspace width="0.3333em"/>
<mml:mmultiscripts>
<mml:mrow>
<mml:mi mathvariant="bold">T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>m</mml:mi>
</mml:mrow>
<mml:none/>
<mml:mprescripts/>
<mml:none/>
<mml:mrow>
<mml:mi>c</mml:mi>
</mml:mrow>
</mml:mmultiscripts>
</mml:mrow>
</mml:math>
<label>(3)</label>
</disp-formula>
</p>
<p>The target pose in the world frame is, therefore:<disp-formula id="e4">
<mml:math id="m24">
<mml:mrow>
<mml:mmultiscripts>
<mml:mrow>
<mml:mi mathvariant="bold">T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>m</mml:mi>
</mml:mrow>
<mml:none/>
<mml:mprescripts/>
<mml:none/>
<mml:mrow>
<mml:mi>w</mml:mi>
</mml:mrow>
</mml:mmultiscripts>
<mml:mo>&#x3d;</mml:mo>
<mml:mmultiscripts>
<mml:mrow>
<mml:mi mathvariant="bold">T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>e</mml:mi>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:none/>
<mml:mprescripts/>
<mml:none/>
<mml:mrow>
<mml:mi>w</mml:mi>
</mml:mrow>
</mml:mmultiscripts>
<mml:mspace width="0.3333em"/>
<mml:mmultiscripts>
<mml:mrow>
<mml:mi mathvariant="bold">T</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>m</mml:mi>
</mml:mrow>
<mml:none/>
<mml:mprescripts/>
<mml:none/>
<mml:mrow>
<mml:mi>e</mml:mi>
<mml:mi>e</mml:mi>
</mml:mrow>
</mml:mmultiscripts>
</mml:mrow>
</mml:math>
<label>(4)</label>
</disp-formula>
</p>
<p>By applying the <xref ref-type="disp-formula" rid="e4">Equation 4</xref>, any marker pose in the world frame can be easily obtained if the camera detects it. If the marker is attached to the PUP of each profile, the picking poses for the end-effector can be calculated at run-time instead of using the manually assigned coordinates measured in advance, which can be inaccurate. Moreover, instead of feeding the profiles to the input platform at the same position every time, now the profiles can be casually placed at any point on the input platform where the camera can detect them. Similarly, by attaching a marker on the assembly platform where the module origin should be, we can save the effort of manual coordinate measurements.</p>
</sec>
<sec id="s3-5-4">
<title>3.5.4 Experimental validation (robotics part)</title>
<p>Two sets of experiments are conducted to validate the accuracy and efficacy of the presented system. The first one evaluates and compares the accuracy of the pick-and-place poses of a single aluminum part with and without the visual marker detection module, as shown in <xref ref-type="fig" rid="F14">Figure 14</xref>(1). The second experiment evaluates the success rate of the full assembly process of a prefabricated module consisting of four aluminum parts and demonstrates the efficacy of the presented system in real applications.</p>
<fig id="F14" position="float">
<label>FIGURE 14</label>
<caption>
<p>(1) Pick-and-Place of a single aluminum part in baseline mode <bold>(a,b)</bold> and visual-aid mode <bold>(c,d)</bold>. (2) Snapshots of the placing of profiles <bold>(e-h)</bold>.</p>
</caption>
<graphic xlink:href="fbuil-11-1649278-g014.tif">
<alt-text content-type="machine-generated">Two series of images show a robotic arm interacting with objects. The first series (a-d) features the arm handling a small object on a table surrounded by a marked sheet. The second series (a-d) depicts the arm manipulating objects within a metal frame on a table. Each image captures different angles and stages of the robot's task execution.</alt-text>
</graphic>
</fig>
<p>We first evaluated the accuracy of picking and placing a single aluminum part using the presented system, with and without the visual aid module. In both experiments, as shown in the snapshots in <xref ref-type="fig" rid="F14">Figure 14</xref>(1), an aluminum part is picked up from the input platform on the left side and placed on the assembly platform on the right side. The difference is, in the baseline mode without the visual aid, the pick and place positions are pre-defined in the calibrated workspace, whereas in the visual aid mode, the pick position is marked by the ArUco marker attached on the surface of the aluminum part, and the place position is marked by the ArUco marker attached to the assembly platform, such that the part can be pre-placed at any position on the input platform. We conducted 10 experiments in each mode and measured the average errors of position and orientation, separately. The position error is based on 2D (two-dimensional) Euclidean distance between the actual positions to the reference positions, and for orientation, we measure the yaw angle error wrapped between <inline-formula id="inf21">
<mml:math id="m25">
<mml:mrow>
<mml:mo stretchy="false">[</mml:mo>
<mml:mrow>
<mml:mo>&#x2212;</mml:mo>
<mml:mi>&#x3c0;</mml:mi>
<mml:mo>,</mml:mo>
<mml:mi>&#x3c0;</mml:mi>
</mml:mrow>
<mml:mo stretchy="false">]</mml:mo>
</mml:mrow>
</mml:math>
</inline-formula>, as defined in <xref ref-type="disp-formula" rid="e5">Equation 5</xref>.<disp-formula id="e5">
<mml:math id="m26">
<mml:mrow>
<mml:mtable class="aligned">
<mml:mtr>
<mml:mtd columnalign="right">
<mml:msub>
<mml:mrow>
<mml:mtext>e</mml:mtext>
</mml:mrow>
<mml:mrow>
<mml:mtext>pos</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:mtd>
<mml:mtd columnalign="left">
<mml:mo>&#x3d;</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
</mml:mfrac>
<mml:msqrt>
<mml:mrow>
<mml:mstyle displaystyle="true">
<mml:munderover>
<mml:mrow>
<mml:mo>&#x2211;</mml:mo>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
</mml:munderover>
</mml:mstyle>
<mml:mfenced open="[" close="]">
<mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2212;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>x</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>ref</mml:mtext>
<mml:mo>,</mml:mo>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msup>
<mml:mo>&#x2b;</mml:mo>
<mml:msup>
<mml:mrow>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>y</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2212;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>y</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>ref</mml:mtext>
<mml:mo>,</mml:mo>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mrow>
<mml:mn>2</mml:mn>
</mml:mrow>
</mml:msup>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:msqrt>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd columnalign="right">
<mml:msub>
<mml:mrow>
<mml:mtext>e</mml:mtext>
</mml:mrow>
<mml:mrow>
<mml:mtext>ori</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:mtd>
<mml:mtd columnalign="left">
<mml:mo>&#x3d;</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>n</mml:mi>
</mml:mrow>
</mml:mfrac>
<mml:mstyle displaystyle="true">
<mml:munderover>
<mml:mrow>
<mml:mo>&#x2211;</mml:mo>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mi>N</mml:mi>
</mml:mrow>
</mml:munderover>
</mml:mstyle>
<mml:mfenced open="|" close="|">
<mml:mrow>
<mml:mtext>wrap</mml:mtext>
<mml:mfenced open="(" close=")">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>&#x3b8;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2212;</mml:mo>
<mml:msub>
<mml:mrow>
<mml:mi>&#x3b8;</mml:mi>
</mml:mrow>
<mml:mrow>
<mml:mtext>ref</mml:mtext>
<mml:mo>,</mml:mo>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mfenced>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:math>
<label>(5)</label>
</disp-formula>
</p>
<p>
<xref ref-type="table" rid="T1">Table 1</xref> shows average errors in the position and orientation of the pick and place in each mode, respectively. Discussion: Without visual aid, small errors for picking and large errors for placing the side. The reason is that calibration is done at the robot&#x2019;s home position, which is closer to the pick positions. Errors occur when the rail moves since the rail system is not calibrated, so the other side has large errors. With visual aid, the errors mainly come from changes in light conditions and the noise of marker detection. The increase in orientation error observed in the tag-based (visual aid) mode is primarily due to variability in lighting conditions and detection jitter in the ArUco marker pose estimation. While visual localization improves flexibility and position accuracy, small angular deviations may result from inconsistent tag visibility or blur in the image frame. This is more pronounced during placement tasks that require finer rotational alignment, especially when the robot arm is operating far from its calibrated home position.</p>
<table-wrap id="T1" position="float">
<label>TABLE 1</label>
<caption>
<p>Average errors in position and orientations of picking and placing a single aluminum part with and without visual aid over 10 experiments each.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="center">Mode</th>
<th align="center">
<inline-formula id="inf22">
<mml:math id="m27">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mtext>e</mml:mtext>
</mml:mrow>
<mml:mrow>
<mml:mtext>pos,&#x2009;pick</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula>
</th>
<th align="center">
<inline-formula id="inf23">
<mml:math id="m28">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mtext>e</mml:mtext>
</mml:mrow>
<mml:mrow>
<mml:mtext>ori,&#x2009;pick</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula>
</th>
<th align="center">
<inline-formula id="inf24">
<mml:math id="m29">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mtext>e</mml:mtext>
</mml:mrow>
<mml:mrow>
<mml:mtext>pos,&#x2009;place</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula>
</th>
<th align="center">
<inline-formula id="inf25">
<mml:math id="m30">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mtext>e</mml:mtext>
</mml:mrow>
<mml:mrow>
<mml:mtext>ori,&#x2009;place</mml:mtext>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula>
</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="center">Baseline</td>
<td align="center">0.42 <inline-formula id="inf26">
<mml:math id="m31">
<mml:mrow>
<mml:mo>&#xb1;</mml:mo>
</mml:mrow>
</mml:math>
</inline-formula> 0.07 cm</td>
<td align="center">4.5 <inline-formula id="inf27">
<mml:math id="m32">
<mml:mrow>
<mml:mo>&#xb1;</mml:mo>
</mml:mrow>
</mml:math>
</inline-formula> 1.2&#xb0;</td>
<td align="center">2.56 <inline-formula id="inf28">
<mml:math id="m33">
<mml:mrow>
<mml:mo>&#xb1;</mml:mo>
</mml:mrow>
</mml:math>
</inline-formula> 0.30 cm</td>
<td align="center">13.5&#xb0;<inline-formula id="inf29">
<mml:math id="m34">
<mml:mrow>
<mml:mo>&#xb1;</mml:mo>
</mml:mrow>
</mml:math>
</inline-formula> 1.8&#xb0;</td>
</tr>
<tr>
<td align="center">With visual aid</td>
<td align="center">0.53 <inline-formula id="inf30">
<mml:math id="m35">
<mml:mrow>
<mml:mo>&#xb1;</mml:mo>
</mml:mrow>
</mml:math>
</inline-formula> 0.09 cm</td>
<td align="center">6.4 <inline-formula id="inf31">
<mml:math id="m36">
<mml:mrow>
<mml:mo>&#xb1;</mml:mo>
</mml:mrow>
</mml:math>
</inline-formula> 1.4&#xb0;</td>
<td align="center">0.62 <inline-formula id="inf32">
<mml:math id="m37">
<mml:mrow>
<mml:mo>&#xb1;</mml:mo>
</mml:mrow>
</mml:math>
</inline-formula> 0.11 cm</td>
<td align="center">5.8 <inline-formula id="inf33">
<mml:math id="m38">
<mml:mrow>
<mml:mo>&#xb1;</mml:mo>
</mml:mrow>
</mml:math>
</inline-formula> 1.1&#xb0;</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>Furthermore, we compared task durations between traditional manual approaches and the automated system. As shown in <xref ref-type="table" rid="T2">Table 2</xref>, tasks such as facade layout and clash-checking were reduced from hundreds of hours to under an hour, demonstrating the pipeline&#x2019;s substantial time-saving potential.</p>
<table-wrap id="T2" position="float">
<label>TABLE 2</label>
<caption>
<p>Comparison of manual and automated execution time for key renovation tasks.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="left">Task</th>
<th align="center">Manual time (hours)</th>
<th align="center">Automated time (minutes)</th>
<th align="center">Time saved (%)</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="left">Facade layout definition</td>
<td align="center">1,000&#x2b;</td>
<td align="center">25</td>
<td align="center">99%</td>
</tr>
<tr>
<td align="left">Clash checking (on-site)</td>
<td align="center">
<inline-formula id="inf34">
<mml:math id="m39">
<mml:mrow>
<mml:mo>&#x223c;</mml:mo>
</mml:mrow>
</mml:math>
</inline-formula>40</td>
<td align="center">10</td>
<td align="center">
<inline-formula id="inf35">
<mml:math id="m40">
<mml:mrow>
<mml:mo>&#x223c;</mml:mo>
</mml:mrow>
</mml:math>
</inline-formula>75%</td>
</tr>
<tr>
<td align="left">Geometry adjustment (realignment)</td>
<td align="center">
<inline-formula id="inf36">
<mml:math id="m41">
<mml:mrow>
<mml:mo>&#x223c;</mml:mo>
</mml:mrow>
</mml:math>
</inline-formula>20</td>
<td align="center">25</td>
<td align="center">&#x2013;</td>
</tr>
</tbody>
</table>
</table-wrap>
<sec id="s3-5-4-1">
<title>3.5.4.1 Efficacy assessment</title>
<p>The second experiment assesses the whole process of assembling a prefabricated module in the visual-aid mode. The square-shaped module to be assembled consists of 4 prefabricated aluminum profiles that interlock with each other. The upper surfaces of the profiles are not flat and cannot be picked up by the vacuum gripper. Therefore, we select the PUP at the geometry center of the inner side surface of each profile. This selection and the fact that the profiles are interlocked add more geometry constraints to the planner. To ensure the success of assembly, a few trial test is conducted offline in simulation to find the optimal waypoints for the end-effector. Although this process requires manual effort from the user, once an optimal set of waypoints is determined, they can be used repeatedly with profiles of the same shape across various sizes.</p>
<p>ArUco markers are attached to the PUP on each profile, as well as the input and assembly platforms, for automatic localization of the profile. Without the need to place the profile precisely at the pre-defined position, they can instead be placed at a random position on the input platform, as long as they are in the camera range.</p>
<p>Snapshots of moments when placing each profile are shown in <xref ref-type="fig" rid="F14">Figure 14</xref>(2), and the whole assembly process can be found in the attached video. From our five tests of the same experiment, &#xe000;four of them successfully assembled the parts in the interlocking position, giving an overall successful rate of 80%. The rest one them failed at accurately placing the second module. With an error of 0.8 cm, 10&#xb0;, it blocked the third part from being placed successfully in the gap.</p>
</sec>
</sec>
</sec>
</sec>
<sec id="s4">
<title>4 Conclusion and future work</title>
<p>The study presents a comprehensive and automated integrative workflow that integrates online data acquisition, high-precision facade geometry estimation, CAM-based module fabrication, and robotic assembly to support the renovation of existing buildings with prefabricated facade modules.</p>
<p>The development of a structured data acquisition platform, in conjunction with AprilTag-based photogrammetric methods, enables the proposed system to achieve high geometric fidelity with minimal manual input. The integration of digital models with automated manufacturing via CAM and the execution of precise robotic pick-and-place operations have been demonstrated to enhance workflow efficiency and scalability in renovation processes.</p>
<p>The experimental results obtained from this study validate the feasibility and accuracy of each stage in the integrative workflow. The utilization of marker-based visual localization techniques resulted in a substantial enhancement in robotic placement precision, achieving a placement accuracy of less than 1 cm. Additionally, the modular software and hardware architecture exemplifies adaptability to diverse facade configurations and component geometries.</p>
<p>However, it should be noted that the present system remains in its prototype phase and exhibits numerous areas that could be improved upon. Subsequent research endeavors should encompass the development of a scalable system for real-world construction environments. For instance, the Online Data Acquisition Platform should be developed towards a more user-friendly interface, and the use of Artificial Intelligence should make the Building Modeling even faster. This system should include dynamic adaptation to on-site tolerances, integration with live BIM updates, and support for more complex facade geometries.</p>
<p>Regarding the Robotic Assembly, the vacuum gripper imposes limitations on the grasping flexibility, particularly for non-flat surfaces. Subsequent research will investigate alternative end-effectors, such as adaptive or underactuated grippers. Furthermore, during the Robotic Assembly, reliance on ArUco markers introduces manual steps and the potential for error propagation from marker placement. Subsequent iterations will examine markerless computer vision methodologies, including depth perception through RGB-D cameras and machine-learning-based pose estimation, to enhance autonomy and robustness.</p>
<p>In order to guarantee the system&#x2019;s applicability in real-world construction settings, scalability remains a central consideration. The current prototype operates within a confined workspace of 3.0 m <inline-formula id="inf37">
<mml:math id="m42">
<mml:mrow>
<mml:mo>&#xd7;</mml:mo>
</mml:mrow>
</mml:math>
</inline-formula> 1.4 m, which limits both lateral and vertical reach. In order to address this issue, the development of modular linear rail segments is underway, intending to facilitate flexible horizontal extension. To extend both vertical and lateral reach, the use of modular and longer linear rail segments is currently being considered in projects such as AMALTEA (<ext-link ext-link-type="uri" xlink:href="https://amaltea-project.eu/">https://amaltea-project.eu/</ext-link>). Moreover, the AMALTEA project will consider an on-site robot for the installation of curtain wall modules. Furthermore, the issue of site safety is of paramount importance. The deployment must include secure rail mounting, collision avoidance in shared workspaces, and compliance with standard construction site safety protocols.</p>
<p>The deployment of such systems in operational environments gives rise to a number of regulatory and logistical challenges. These include the need for a stable power supply, the implementation of weatherproofing measures for outdoor operation, and adherence to safety, permitting, and inspection regulations that vary across jurisdictions. These constraints will guide the refinement and validation of the system in future development phases.</p>
<p>In the future, several enhancements are planned. Marker-less computer vision will be integrated to eliminate reliance on AprilTags and improve robustness in unstructured environments. Adaptive end-effectors capable of handling a wider variety of facade geometries, including non-planar or irregular surfaces, are under development. In addition, the system will be tested in multi-story retrofitting scenarios to assess performance under realistic construction conditions and further evaluate its scalability.</p>
<p>The current research in the aforementioned project (and others) is pushing for the overarching objective of the system, which is to facilitate the execution of energy renovations for building stock that are scalable, accurate, and minimally disruptive, thereby aligning with the established climate objectives.</p>
</sec>
</body>
<back>
<sec sec-type="data-availability" id="s5">
<title>Data availability statement</title>
<p>The original contributions presented in the study are included in the article/supplementary material, further inquiries can be directed to the corresponding author.</p>
</sec>
<sec sec-type="author-contributions" id="s6">
<title>Author contributions</title>
<p>KI: Investigation, Conceptualization, Software, Writing &#x2013; original draft, Visualization, Funding acquisition, Resources, Methodology, Formal Analysis, Validation, Project administration, Data curation, Supervision. WS: Writing &#x2013; original draft, Investigation, Software. RB: Writing &#x2013; original draft, Investigation. OA-G: Investigation, Writing &#x2013; original draft. DL: Writing &#x2013; original draft, Investigation. AS: Writing &#x2013; original draft. SD: Writing &#x2013; original draft, Investigation. TB: Funding acquisition, Supervision, Resources, Writing &#x2013; review and editing. CH: Resources, Writing &#x2013; review and editing, Supervision.</p>
</sec>
<sec sec-type="funding-information" id="s7">
<title>Funding</title>
<p>The author(s) declare that financial support was received for the research and/or publication of this article. This project has received funding from the European Union&#x2019;s Horizon 2020 research and innovation programme under grant agreement No. 958445.</p>
</sec>
<sec sec-type="COI-statement" id="s8">
<title>Conflict of interest</title>
<p>The authors declare that the research was conducted in the absence of any commercial or financial relationships that could be construed as a potential conflict of interest.</p>
</sec>
<sec sec-type="ai-statement" id="s9">
<title>Generative AI statement</title>
<p>The author(s) declare that no Generative AI was used in the creation of this manuscript.</p>
<p>Any alternative text (alt text) provided alongside figures in this article has been generated by Frontiers with the support of artificial intelligence and reasonable efforts have been made to ensure accuracy, including review by the authors wherever possible. If you identify any issues, please contact us.</p>
</sec>
<sec sec-type="disclaimer" id="s10">
<title>Publisher&#x2019;s note</title>
<p>All claims expressed in this article are solely those of the authors and do not necessarily represent those of their affiliated organizations, or those of the publisher, the editors and the reviewers. Any product that may be evaluated in this article, or claim that may be made by its manufacturer, is not guaranteed or endorsed by the publisher.</p>
</sec>
<ref-list>
<title>References</title>
<ref id="B1">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Ali</surname>
<given-names>A. K.</given-names>
</name>
<name>
<surname>Lee</surname>
<given-names>O. J.</given-names>
</name>
<name>
<surname>Song</surname>
<given-names>H.</given-names>
</name>
</person-group> (<year>2021</year>). <article-title>Robot-based facade spatial assembly optimization</article-title>. <source>J. Build. Eng.</source> <volume>33</volume>, <fpage>101556</fpage>. <pub-id pub-id-type="doi">10.1016/j.jobe.2020.101556</pub-id>
</citation>
</ref>
<ref id="B2">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Augustynowicz</surname>
<given-names>E.</given-names>
</name>
<name>
<surname>Smigielska</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Nikles</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Wehrle</surname>
<given-names>T.</given-names>
</name>
<name>
<surname>Wagner</surname>
<given-names>H.</given-names>
</name>
</person-group> (<year>2021</year>). &#x201c;<article-title>Parametric design and multirobotic fabrication of wood facades. Acadia 2021: realignments. Toward critical computation</article-title>,&#x201d; in <source>Proceedings of the 41st annual conference of the association for computer aided design in architecture (ACADIA)</source>. <pub-id pub-id-type="doi">10.52842/conf.acadia.2021.258</pub-id>
</citation>
</ref>
<ref id="B3">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Babiarz</surname>
<given-names>B.</given-names>
</name>
<name>
<surname>Krawczyk</surname>
<given-names>D. A.</given-names>
</name>
<name>
<surname>Siuta-Olcha</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Manuel</surname>
<given-names>C. D.</given-names>
</name>
<name>
<surname>Jaworski</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Barnat</surname>
<given-names>E.</given-names>
</name>
<etal/>
</person-group> (<year>2024</year>). <article-title>Energy efficiency in buildings: toward climate neutrality</article-title>. <source>Energies</source> <volume>17</volume>, <fpage>4680</fpage>. <pub-id pub-id-type="doi">10.3390/en17184680</pub-id>
</citation>
</ref>
<ref id="B4">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Balaguer</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Abderrahim</surname>
<given-names>M.</given-names>
</name>
</person-group> (<year>2008</year>). <source>Robotics and automation in construction</source>. Editors <person-group person-group-type="editor">
<name>
<surname>Balaguer</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Abderrahim</surname>
<given-names>M.</given-names>
</name>
</person-group> (<publisher-name>BoD&#x2013;Books on Demand</publisher-name>).</citation>
</ref>
<ref id="B5">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Barco-Santa</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Vareilles</surname>
<given-names>&#xc9;.</given-names>
</name>
<name>
<surname>Gaborit</surname>
<given-names>P.</given-names>
</name>
<name>
<surname>Aldanondo</surname>
<given-names>M.</given-names>
</name>
</person-group> (<year>2017</year>). <article-title>Building renovation adopts mass customization: configuring insulating envelopes</article-title>. <source>J. Intell. Inf. Syst.</source> <volume>49</volume>, <fpage>119</fpage>&#x2013;<lpage>146</lpage>. <pub-id pub-id-type="doi">10.1007/s10844-016-0431-6</pub-id>
</citation>
</ref>
<ref id="B6">
<citation citation-type="web">
<collab>Beckhoff Automation</collab> (<year>2023</year>). <article-title>ADS library</article-title>. <comment>Available online at: <ext-link ext-link-type="uri" xlink:href="https://github.com/Beckhoff/ADS">https://github.com/Beckhoff/ADS</ext-link> (Accessed April 2, 2023)</comment>.</citation>
</ref>
<ref id="B7">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Chegu Badrinath</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Chang</surname>
<given-names>Y.-T.</given-names>
</name>
<name>
<surname>Hsieh</surname>
<given-names>S.-H.</given-names>
</name>
</person-group> (<year>2016</year>). <article-title>A review of tertiary bim education for advanced engineering communication with visualization</article-title>. <source>Vis. Eng.</source> <volume>4</volume>, <fpage>9</fpage>&#x2013;<lpage>17</lpage>. <pub-id pub-id-type="doi">10.1186/s40327-016-0038-6</pub-id>
</citation>
</ref>
<ref id="B8">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Chitta</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Sucan</surname>
<given-names>I.</given-names>
</name>
<name>
<surname>Cousins</surname>
<given-names>S.</given-names>
</name>
</person-group> (<year>2012</year>). <article-title>Moveit![ros topics]</article-title>. <source>IEEE robotics and automation Mag.</source> <volume>19</volume>, <fpage>18</fpage>&#x2013;<lpage>19</lpage>. <pub-id pub-id-type="doi">10.1109/MRA.2011.2181749</pub-id>
</citation>
</ref>
<ref id="B9">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Du</surname>
<given-names>H.</given-names>
</name>
<name>
<surname>Huang</surname>
<given-names>P.</given-names>
</name>
<name>
<surname>Jones</surname>
<given-names>P.</given-names>
</name>
</person-group> (<year>2019</year>). <article-title>Modular facade retrofit with renewable energy technologies: the definition and current status in Europe</article-title>. <source>Energy Build.</source> <volume>205</volume>, <fpage>109543</fpage>. <pub-id pub-id-type="doi">10.1016/j.enbuild.2019.109543</pub-id>
</citation>
</ref>
<ref id="B10">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>D&#x2019;Oca</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Ferrante</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Ferrer</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Pernetti</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Gralka</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Sebastian</surname>
<given-names>R.</given-names>
</name>
<etal/>
</person-group> (<year>2018</year>). <article-title>Technical, financial, and social barriers and challenges in deep building renovation: integration of lessons learned from the h2020 cluster projects</article-title>. <source>Buildings</source> <volume>8</volume>, <fpage>174</fpage>. <pub-id pub-id-type="doi">10.3390/buildings8120174</pub-id>
</citation>
</ref>
<ref id="B11">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Feng</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Xiao</surname>
<given-names>Y.</given-names>
</name>
<name>
<surname>Willette</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>McGee</surname>
<given-names>W.</given-names>
</name>
<name>
<surname>Kamat</surname>
<given-names>V.</given-names>
</name>
</person-group> (<year>2014</year>). &#x201c;<article-title>Towards autonomous robotic <italic>in-situ</italic> assembly on unstructured construction sites using monocular vision</article-title>,&#x201d; in <source>Proceedings of the 31th international symposium on automation and robotics in construction</source>, <fpage>163</fpage>&#x2013;<lpage>170</lpage>. <pub-id pub-id-type="doi">10.22260/ISARC2014/0022</pub-id>
</citation>
</ref>
<ref id="B12">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Ferrandiz</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Banawi</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Pe&#xf1;a</surname>
<given-names>E.</given-names>
</name>
</person-group> (<year>2018</year>). <article-title>Evaluating the benefits of introducing &#x201c;bim&#x201d; based on revit in construction courses, without changing the course schedule</article-title>. <source>Univers. Access Inf. Soc.</source> <volume>17</volume>, <fpage>491</fpage>&#x2013;<lpage>501</lpage>. <pub-id pub-id-type="doi">10.1007/s10209-017-0558-4</pub-id>
</citation>
</ref>
<ref id="B13">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Garrido-Jurado</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Munoz-Salinas</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Madrid-Cuevas</surname>
<given-names>F. J.</given-names>
</name>
<name>
<surname>Medina-Carnicer</surname>
<given-names>R.</given-names>
</name>
</person-group> (<year>2016</year>). <article-title>Generation of fiducial marker dictionaries using mixed integer linear programming</article-title>. <source>Pattern Recognit.</source> <volume>51</volume>, <fpage>481</fpage>&#x2013;<lpage>491</lpage>. <pub-id pub-id-type="doi">10.1016/j.patcog.2015.09.023</pub-id>
</citation>
</ref>
<ref id="B14">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Gerum</surname>
<given-names>R. C.</given-names>
</name>
<name>
<surname>Richter</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Winterl</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Mark</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Fabry</surname>
<given-names>B.</given-names>
</name>
<name>
<surname>Le Bohec</surname>
<given-names>C.</given-names>
</name>
<etal/>
</person-group> (<year>2019</year>). <article-title>Cameratransform: a python package for perspective corrections and image mapping</article-title>. <source>SoftwareX</source> <volume>10</volume>, <fpage>100333</fpage>. <pub-id pub-id-type="doi">10.1016/j.softx.2019.100333</pub-id>
<pub-id pub-id-type="pmid">32864407</pub-id>
</citation>
</ref>
<ref id="B15">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Hillebrand</surname>
<given-names>G.</given-names>
</name>
<name>
<surname>Arends</surname>
<given-names>G.</given-names>
</name>
<name>
<surname>Streblow</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Madlener</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>M&#xfc;ller</surname>
<given-names>D.</given-names>
</name>
</person-group> (<year>2014</year>). <article-title>Development and design of a retrofit matrix for office buildings</article-title>. <source>Energy Build.</source> <volume>70</volume>, <fpage>516</fpage>&#x2013;<lpage>522</lpage>. <pub-id pub-id-type="doi">10.1016/j.enbuild.2013.10.029</pub-id>
</citation>
</ref>
<ref id="B16">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Hook</surname>
<given-names>J.</given-names>
</name>
</person-group> (<year>2016</year>). <source>Automated digital fabrication concept for composite facades</source>. <pub-id pub-id-type="doi">10.14264/uql.2017.240</pub-id>
</citation>
</ref>
<ref id="B17">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Hsu</surname>
<given-names>W.-S.</given-names>
</name>
<name>
<surname>Fazeli</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Hurr&#xe1;id&#xe9;</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Holst</surname>
<given-names>C.</given-names>
</name>
</person-group> (<year>2024</year>). &#x201c;<article-title>Uav for sticking markers in the built environement</article-title>,&#x201d; in <source>ISARC. Proceedings of the international symposium on automation and robotics in construction</source> (<publisher-loc>Lille, France</publisher-loc>: <publisher-name>2024 Proceedings of the 41st ISARC</publisher-name>), <fpage>1315</fpage>&#x2013;<lpage>1318</lpage>. <pub-id pub-id-type="doi">10.22260/ISARC2024/0172</pub-id>
</citation>
</ref>
<ref id="B18">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Hu</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Iturralde</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Linner</surname>
<given-names>T.</given-names>
</name>
<name>
<surname>Zhao</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Pan</surname>
<given-names>W.</given-names>
</name>
<name>
<surname>Pracucci</surname>
<given-names>A.</given-names>
</name>
<etal/>
</person-group> (<year>2020</year>). <article-title>A simple framework for the cost&#x2013;benefit analysis of single-task construction robots based on a case study of a cable-driven facade installation robot</article-title>. <source>Buildings</source> <volume>11</volume>, <fpage>8</fpage>. <pub-id pub-id-type="doi">10.3390/buildings11010008</pub-id>
</citation>
</ref>
<ref id="B19">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Iturralde</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Kinoshita</surname>
<given-names>T.</given-names>
</name>
<name>
<surname>Bock</surname>
<given-names>T.</given-names>
</name>
</person-group> (<year>2019</year>). &#x201c;<article-title>Grasped element position recognition and robot pose adjustment during assembly</article-title>,&#x201d; in <source>ISARC. Proceedings of the international symposium on automation and robotics in construction</source> (<publisher-loc>Banff, Canada</publisher-loc>: <publisher-name>2019 Proceedings of the 36th ISARC</publisher-name>), <fpage>461</fpage>&#x2013;<lpage>468</lpage>. <pub-id pub-id-type="doi">10.22260/ISARC2019/0062</pub-id>
</citation>
</ref>
<ref id="B20">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Iturralde</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Gambao</surname>
<given-names>E.</given-names>
</name>
<name>
<surname>Bock</surname>
<given-names>T.</given-names>
</name>
</person-group> (<year>2021</year>). &#x201c;<article-title>Compilation and assessment of automated fa&#xe7;ade renovation</article-title>,&#x201d; in <source>ISARC. Proceedings of the international symposium on automation and robotics in construction</source> (<publisher-loc>Dubai, UAE</publisher-loc>: <publisher-name>2021 Proceedings of the 38th ISARC</publisher-name>), <fpage>797</fpage>&#x2013;<lpage>804</lpage>.</citation>
</ref>
<ref id="B21">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Iturralde</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Zimmermann</surname>
<given-names>P.</given-names>
</name>
<name>
<surname>Santos</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Das</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Shen</surname>
<given-names>W.</given-names>
</name>
<name>
<surname>Malik</surname>
<given-names>M.</given-names>
</name>
<etal/>
</person-group> (<year>2022</year>). &#x201c;<article-title>Solution kits for automated and robotic fa&#xe7;ade upgrading</article-title>,&#x201d; in <source>ISARC. Proceedings of the international symposium on automation and robotics in construction</source> (<publisher-loc>Bogot&#xe1;, Colombia</publisher-loc>: <publisher-name>2022 Proceedings of the 39th ISARC</publisher-name>), <fpage>414</fpage>&#x2013;<lpage>421</lpage>. <pub-id pub-id-type="doi">10.22260/ISARC2022/0057</pub-id>
</citation>
</ref>
<ref id="B22">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Iturralde</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Amburi</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Ravichandran</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Das</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Liu</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Bock</surname>
<given-names>T.</given-names>
</name>
</person-group> (<year>2023a</year>). &#x201c;<article-title>Online modelling and prefab layout definition for building renovation</article-title>,&#x201d; in <source>ISARC. Proceedings of the international symposium on automation and robotics in construction</source> (<publisher-loc>Chennai, India</publisher-loc>: <publisher-name>2023 Proceedings of the 40th ISARC</publisher-name>), <fpage>605</fpage>&#x2013;<lpage>608</lpage>. <pub-id pub-id-type="doi">10.22260/ISARC2023/0083</pub-id>
</citation>
</ref>
<ref id="B23">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Iturralde</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Das</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Srinivasaragavan</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Bock</surname>
<given-names>T.</given-names>
</name>
<name>
<surname>Holst</surname>
<given-names>C.</given-names>
</name>
</person-group> (<year>2023b</year>). <article-title>An automated prefabricated facade layout definition for residential building renovation</article-title>. <source>Buildings</source> <volume>13</volume>, <fpage>2981</fpage>. <pub-id pub-id-type="doi">10.3390/buildings13122981</pub-id>
</citation>
</ref>
<ref id="B24">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Iturralde</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Gambao</surname>
<given-names>E.</given-names>
</name>
<name>
<surname>Bock</surname>
<given-names>T.</given-names>
</name>
</person-group> (<year>2023c</year>). <article-title>Deviation-correcting interface for building-envelope renovation</article-title>. <source>Buildings</source> <volume>13</volume>, <fpage>2386</fpage>. <pub-id pub-id-type="doi">10.3390/buildings13092386</pub-id>
</citation>
</ref>
<ref id="B25">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Iturralde</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Gambao</surname>
<given-names>E.</given-names>
</name>
<name>
<surname>Bock</surname>
<given-names>T.</given-names>
</name>
</person-group> (<year>2024</year>). <article-title>Semiautomated primary layout definition with a point cloud for building-envelope renovation</article-title>. <source>Buildings</source> <volume>14</volume>, <fpage>351</fpage>. <pub-id pub-id-type="doi">10.3390/buildings14020351</pub-id>
</citation>
</ref>
<ref id="B26">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Kasperzyk</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Kim</surname>
<given-names>M.-K.</given-names>
</name>
<name>
<surname>Brilakis</surname>
<given-names>I.</given-names>
</name>
</person-group> (<year>2017</year>). <article-title>Automated re-prefabrication system for buildings using robotics</article-title>. <source>Automation Constr.</source> <volume>83</volume>, <fpage>184</fpage>&#x2013;<lpage>195</lpage>. <pub-id pub-id-type="doi">10.1016/j.autcon.2017.08.002</pub-id>
</citation>
</ref>
<ref id="B27">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Kedilioglu</surname>
<given-names>O.</given-names>
</name>
<name>
<surname>Bocco</surname>
<given-names>T. M.</given-names>
</name>
<name>
<surname>Landesberger</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Rizzo</surname>
<given-names>A.</given-names>
</name>
<name>
<surname>Franke</surname>
<given-names>J.</given-names>
</name>
</person-group> (<year>2021</year>). &#x201c;<article-title>Arucoe: enhanced aruco marker</article-title>,&#x201d; in <source>2021 21st international conference on control, automation and systems (ICCAS)</source> (<publisher-name>IEEE</publisher-name>), <fpage>878</fpage>&#x2013;<lpage>881</lpage>.</citation>
</ref>
<ref id="B28">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Lasarte</surname>
<given-names>N.</given-names>
</name>
<name>
<surname>Chica</surname>
<given-names>J. A.</given-names>
</name>
<name>
<surname>Gomis</surname>
<given-names>I.</given-names>
</name>
<name>
<surname>Benito</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Iturralde</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Bock</surname>
<given-names>T.</given-names>
</name>
</person-group> (<year>2017</year>). &#x201c;<article-title>Prefabricated solutions and automated and digital tools for the optimisation of a holistic energy refurbishment process</article-title>,&#x201d; in <source>Proceeding of the 8th European congress on energy efficiency and sustainability in architecture and planning and 1st international congress on advanced construction</source>, <fpage>125</fpage>&#x2013;<lpage>140</lpage>.</citation>
</ref>
<ref id="B29">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Mainicheva</surname>
<given-names>A. Y.</given-names>
</name>
<name>
<surname>Talapov</surname>
<given-names>V.</given-names>
</name>
<name>
<surname>Zhang</surname>
<given-names>G.</given-names>
</name>
</person-group> (<year>2017</year>). <article-title>Principles of the information modeling of cultural heritage objects: the case of wooden Buddhist temples</article-title>. <source>Archaeol. Ethnology and Anthropol. Eurasia</source> <volume>45</volume>, <fpage>142</fpage>&#x2013;<lpage>148</lpage>. <pub-id pub-id-type="doi">10.1007/978-3-030-89477-1_84</pub-id>
</citation>
</ref>
<ref id="B30">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Martinez</surname>
<given-names>R. G.</given-names>
</name>
<name>
<surname>Larraz</surname>
<given-names>J. A.</given-names>
</name>
</person-group> (<year>2017</year>). <article-title>Performance assessment of fa&#xe7;ade integrated glazed air solar thermal collectors</article-title>. <source>Energy Procedia</source> <volume>115</volume>, <fpage>353</fpage>&#x2013;<lpage>360</lpage>. <pub-id pub-id-type="doi">10.1016/j.egypro.2017.05.032</pub-id>
</citation>
</ref>
<ref id="B31">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Mateus</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Duarte</surname>
<given-names>J.</given-names>
</name>
</person-group> (<year>2016</year>). &#x201c;<article-title>A grammar-based system for building envelope design to maximize pv performance</article-title>,&#x201d; in <source>Proceedings of the 10th conference on advanced building skins</source> (<publisher-loc>Switzerland</publisher-loc>: <publisher-name>Bern</publisher-name>), <fpage>10</fpage>&#x2013;<lpage>11</lpage>.</citation>
</ref>
<ref id="B32">
<citation citation-type="book">
<person-group person-group-type="author">
<name>
<surname>Mateus</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Duarte</surname>
<given-names>J. P.</given-names>
</name>
<name>
<surname>Rom&#xe3;o</surname>
<given-names>L.</given-names>
</name>
</person-group> (<year>2021</year>). &#x201c;<article-title>Energy-based design: a digital design system for the design of energy-harvesting building envelopes</article-title>,&#x201d; in <source>Proceedings of the XXV international conference of the ibero-american society of digital graphics (SIGraDi 2021)</source>, <fpage>8</fpage>&#x2013;<lpage>12</lpage>. <pub-id pub-id-type="doi">10.5151/sigradi2021-90</pub-id>
</citation>
</ref>
<ref id="B33">
<citation citation-type="web">
<collab>MoveIt</collab> (<year>2023a</year>). <article-title>Hand-eye calibration tutorial</article-title>. <comment>Available online at: <ext-link ext-link-type="uri" xlink:href="https://moveit.picknik.ai/humble/doc/examples/hand_eye_/calibration/hand_eye_calibration_tutorial.html">https://moveit.picknik.ai/humble/doc/examples/hand_eye_/calibration/hand_eye_calibration_tutorial.html</ext-link> (Accessed April 2, 2023)</comment>.</citation>
</ref>
<ref id="B34">
<citation citation-type="web">
<collab>MoveIt</collab> (<year>2023b</year>). <article-title>Moving robots into the future</article-title>. <comment>Available online at: <ext-link ext-link-type="uri" xlink:href="https://moveit.ros.org/">https://moveit.ros.org/</ext-link> (Accessed April 2, 2023)</comment>.</citation>
</ref>
<ref id="B35">
<citation citation-type="web">
<collab>OpenCV</collab> (<year>2023</year>). <article-title>OpenCV aruco module</article-title>. <comment>Available online at: <ext-link ext-link-type="uri" xlink:href="https://docs.opencv.org/3.4/d9/d6d/tutorial_table_of_content_aruco.html">https://docs.opencv.org/3.4/d9/d6d/tutorial_table_of_content_aruco.html</ext-link> (Accessed April 2, 2023)</comment>.</citation>
</ref>
<ref id="B36">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Pan</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Linner</surname>
<given-names>T.</given-names>
</name>
<name>
<surname>Pan</surname>
<given-names>W.</given-names>
</name>
<name>
<surname>Cheng</surname>
<given-names>H.</given-names>
</name>
<name>
<surname>Bock</surname>
<given-names>T.</given-names>
</name>
</person-group> (<year>2018</year>). <article-title>A framework of indicators for assessing construction automation and robotics in the sustainability context</article-title>. <source>J. Clean. Prod.</source> <volume>182</volume>, <fpage>82</fpage>&#x2013;<lpage>95</lpage>. <pub-id pub-id-type="doi">10.1016/j.jclepro.2018.02.053</pub-id>
</citation>
</ref>
<ref id="B37">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Pan</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Linner</surname>
<given-names>T.</given-names>
</name>
<name>
<surname>Pan</surname>
<given-names>W.</given-names>
</name>
<name>
<surname>Cheng</surname>
<given-names>H.</given-names>
</name>
<name>
<surname>Bock</surname>
<given-names>T.</given-names>
</name>
</person-group> (<year>2020a</year>). <article-title>Structuring the context for construction robot development through integrated scenario approach</article-title>. <source>Automation Constr.</source> <volume>114</volume>, <fpage>103174</fpage>. <pub-id pub-id-type="doi">10.1016/j.autcon.2020.103174</pub-id>
</citation>
</ref>
<ref id="B38">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Pan</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Linner</surname>
<given-names>T.</given-names>
</name>
<name>
<surname>Pan</surname>
<given-names>W.</given-names>
</name>
<name>
<surname>Cheng</surname>
<given-names>H.-m.</given-names>
</name>
<name>
<surname>Bock</surname>
<given-names>T.</given-names>
</name>
</person-group> (<year>2020b</year>). <article-title>Influencing factors of the future utilisation of construction robots for buildings: a Hong Kong perspective</article-title>. <source>J. Build. Eng.</source> <volume>30</volume>, <fpage>101220</fpage>. <pub-id pub-id-type="doi">10.1016/j.jobe.2020.101220</pub-id>
</citation>
</ref>
<ref id="B39">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Romero-Ramirez</surname>
<given-names>F. J.</given-names>
</name>
<name>
<surname>Mu&#xf1;oz-Salinas</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Medina-Carnicer</surname>
<given-names>R.</given-names>
</name>
</person-group> (<year>2018</year>). <article-title>Speeded up detection of squared fiducial markers</article-title>. <source>Image Vis. Comput.</source> <volume>76</volume>, <fpage>38</fpage>&#x2013;<lpage>47</lpage>. <pub-id pub-id-type="doi">10.1016/j.imavis.2018.05.004</pub-id>
</citation>
</ref>
<ref id="B40">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Sandberg</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Orskaug</surname>
<given-names>T.</given-names>
</name>
<name>
<surname>Andersson</surname>
<given-names>A.</given-names>
</name>
</person-group> (<year>2016</year>). <article-title>Prefabricated wood elements for sustainable renovation of residential building fa&#xe7;ades</article-title>. <source>Energy Procedia</source> <volume>96</volume>, <fpage>756</fpage>&#x2013;<lpage>767</lpage>. <pub-id pub-id-type="doi">10.1016/j.egypro.2016.09.138</pub-id>
</citation>
</ref>
<ref id="B41">
<citation citation-type="web">
<collab>Schmalz</collab> (<year>2023</year>). <article-title>Vacuum technology for automation &#x2013; schmalz</article-title>. <comment>Available online at: <ext-link ext-link-type="uri" xlink:href="https://www.schmalz.com/de-de/vakuumtechnik-fuer-die-robotik/vakuum-erzeuger/vakuum-erzeuger-ecbpi-311546/">https://www.schmalz.com/de-de/vakuumtechnik-fuer-die-robotik/vakuum-erzeuger/vakuum-erzeuger-ecbpi-311546/</ext-link> (Accessed April 2, 2023)</comment>.</citation>
</ref>
<ref id="B42">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Skibniewski</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Hendrickson</surname>
<given-names>C.</given-names>
</name>
</person-group> (<year>1988</year>). <article-title>Analysis of robotic surface finishing work on construction site</article-title>. <source>J. Constr. Eng. Manag.</source> <volume>114</volume>, <fpage>53</fpage>&#x2013;<lpage>68</lpage>. <pub-id pub-id-type="doi">10.1061/(ASCE)0733-9364(1988)114:1(53)</pub-id>
</citation>
</ref>
<ref id="B43">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Stiny</surname>
<given-names>G.</given-names>
</name>
</person-group> (<year>1980</year>). <article-title>Introduction to shape and shape grammars</article-title>. <source>Environ. Plan. B Plan. Des.</source> <volume>7</volume>, <fpage>343</fpage>&#x2013;<lpage>351</lpage>. <pub-id pub-id-type="doi">10.1068/b070343</pub-id>
</citation>
</ref>
<ref id="B44">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Tish</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>King</surname>
<given-names>N.</given-names>
</name>
<name>
<surname>Cote</surname>
<given-names>N.</given-names>
</name>
</person-group> (<year>2020</year>). <article-title>Highly accessible platform technologies for vision-guided, closed-loop robotic assembly of unitized enclosure systems</article-title>. <source>Constr. Robot.</source> <volume>4</volume>, <fpage>19</fpage>&#x2013;<lpage>29</lpage>. <pub-id pub-id-type="doi">10.1007/s41693-020-00030-z</pub-id>
</citation>
</ref>
<ref id="B45">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Tsai</surname>
<given-names>I.</given-names>
</name>
<name>
<surname>Kim</surname>
<given-names>Y.</given-names>
</name>
<name>
<surname>Seike</surname>
<given-names>T.</given-names>
</name>
</person-group> (<year>2017</year>). <article-title>Decision-making consideration in energy-conservation retrofitting strategy for the opening of existing building in Taiwan</article-title>. <source>AIJ J. Technol.</source> <volume>23</volume>, <fpage>963</fpage>&#x2013;<lpage>968</lpage>. <pub-id pub-id-type="doi">10.3130/aijt.23.963</pub-id>
</citation>
</ref>
<ref id="B46">
<citation citation-type="web">
<collab>Universal Robots</collab> (<year>2023</year>). <article-title>Collaborative robots &#x2013; universal robots</article-title>. <comment>Available online at: <ext-link ext-link-type="uri" xlink:href="https://www.universal-robots.com/">https://www.universal-robots.com/</ext-link> (Accessed April 2, 2023)</comment>.</citation>
</ref>
<ref id="B47">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Urbikain</surname>
<given-names>M. K.</given-names>
</name>
</person-group> (<year>2020</year>). <article-title>Energy efficient solutions for retrofitting a residential multi-storey building with vacuum insulation panels and low-e windows in two European climates</article-title>. <source>J. Clean. Prod.</source> <volume>269</volume>, <fpage>121459</fpage>. <pub-id pub-id-type="doi">10.1016/j.jclepro.2020.121459</pub-id>
</citation>
</ref>
<ref id="B48">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Warszawski</surname>
<given-names>A.</given-names>
</name>
</person-group> (<year>1985</year>). <article-title>Economic implications of robotics in building</article-title>. <source>Build. Environ.</source> <volume>20</volume>, <fpage>73</fpage>&#x2013;<lpage>81</lpage>. <pub-id pub-id-type="doi">10.1016/0360-1323(85)90001-0</pub-id>
</citation>
</ref>
<ref id="B49">
<citation citation-type="journal">
<person-group person-group-type="author">
<name>
<surname>Zhang</surname>
<given-names>Y.</given-names>
</name>
<name>
<surname>Zhang</surname>
<given-names>C.</given-names>
</name>
<name>
<surname>Chen</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Chen</surname>
<given-names>X.</given-names>
</name>
</person-group> (<year>2021</year>). <article-title>Automatic reconstruction of building fa&#xe7;ade model from photogrammetric mesh model</article-title>. <source>Remote Sens.</source> <volume>13</volume>, <fpage>3801</fpage>. <pub-id pub-id-type="doi">10.3390/rs13193801</pub-id>
</citation>
</ref>
</ref-list>
</back>
</article>