wikillm

Paper · 2023-09-19 · cs.AI, cs.LG

Generative AI in the Construction Industry: Opportunities & Challenges

A non-systematic review and practitioner-sentiment analysis of generative AI in construction. It summarises GAN, VAE, autoregressive, diffusion and flow models, maps LLM applications to building lifecycle phases, lists eight challenges, and proposes a select, fine-tune, use framework. It runs no experiments; its sentiment figures come from 32 opinions (93.8% positive).

Generative adversarial network (GAN)Variational autoencoderDiffusion modelsHallucination mitigationconstructionsurveygenerative-aillmapplicationsposition-paper

arXivPDFMarkdown7 min read

AI-compiled by claude-haiku-5-5 on 2026-11-13, not yet reviewed by a human. Every claim cites its source; check it when a detail matters.

In plain words

Building and construction has been slower than many industries to adopt AI. This paper asks what the new generative AI tools, such as chatbots that write text and models that make images, could do for construction, and what could go wrong. The authors read the existing literature, looked at what construction professionals posted about the topic in 2023, and added their own experience.

The paper gives a short tour of the main generative model families and sorts possible construction uses by the phase of a building project and by the kind of output each use needs, such as text, an image, a 3D model or a task. It then lists the main risks: missing domain knowledge, false but confident answers, weak accuracy, poor generalisation to new projects, outdated models, cost, privacy and regulation. It ends with a simple three-stage plan for adapting a general model to a company's own data, and a list of open research questions. It contains no experiments of its own.

TL;DR

This is a position and review paper, not a method paper. It gives a taxonomy of generative model types with their pros and cons §3, tab. 1, a table of construction uses by project phase and output type tab. 4, and eight challenges §5, fig. 6. Its one concrete recommendation is to fine-tune an existing LLM on construction data, keep humans in the loop, and measure business impact §6.1. Read it for the landscape and the open questions, not for numbers you can implement.

Problem

The authors argue that construction lags other industries in AI adoption and that generative AI has had little study in construction §1. Their two research questions are: what opportunities and challenges practitioners and the literature see, and which research questions matter most next §1.

Method

The paper is a non-systematic narrative review plus a text analysis of practitioner posts §2, fig. 1.

  1. Literature review. Keyword searches in Scopus and Google Scholar using "Generative AI AND Construction", "Generative AI", and "Large Language Models AND Construction". The authors then followed references and citations of key articles (snowball method) §2.
  2. Practitioner perspectives. Posts on LinkedIn from the three months up to 20 August 2023, collected with three hashtag or phrase combinations §2. The authors report 32 relevant opinions with about 63,778 words, in the forms posts, comments, polls and articles §2. The shares are 48% articles, 34% comments, 16% posts and 6% polls §2.
  3. Text analysis. Text was cleaned and tokenised, and stop words were removed with NLTK §4.2. The steps were a word cloud fig. 3, a frequency summary, and sentiment polarity from the TextBlob library, scored from -1 to 1 and grouped into positive, negative and neutral §4.2, fig. 4. The themes were then grouped by hand into key themes §4.2, tab. 3.
  4. Authors' opinions. The authors' own experience is added as a third input §2.
  5. Synthesis. Opportunities and challenges are merged into a conceptual framework fig. 1, §4.4 and into recommendations and research questions §6.
Pseudocode
# Three-stage adoption framework  [fig. 5] [§4.4]
# Input:  application (text), required output type, domain data
# Output: a domain-adapted model ready for use

def adopt_generative_model(application, output_type, domain_data):
    # Stage I: pick a model type that matches the output  [fig. 5]
    model_type = select_model_type(output_type)
    # Stage I: pick a base LLM from a provider, open or closed  [fig. 5]
    base_model = choose_base_model(model_type)
    # Stage II: collect domain data, e.g. BIM, cloud and other data  [fig. 5]
    corpus = collect_domain_data(domain_data)
    # Stage II: fine-tune; privacy and noise handling may be added  [§4.4]
    tuned_model = fine_tune(base_model, corpus)
    # Stage III: use via prompt engineering, with answers or visuals returned
    # to the user; the paper also asks for checks on limits and accuracy
    # [fig. 5] [§5.2, §5.3]
    return tuned_model

Hyperparameters

The paper trains no model, so there are no training hyperparameters. The parameters of its own analysis are:

NameValueWhereNotes
Search windowthree months up to 20 Aug 2023§2LinkedIn posts
Corpus size32 opinions, about 63,778 words§2
Source mix48% articles, 34% comments, 16% posts, 6% polls§2
Sentiment scoringTextBlob polarity, -1 to 1§4.2tool version not stated
Stop-word removalNLTK§4.2list not stated
Literature search3 keyword strings, Scopus and Google Scholar§2date range not stated

Results

All results are the authors' own, from a non-systematic review, so they are descriptive and not statistically tested.

Model taxonomy. Table 1 summarises the five model types. Figure 2 shows schematic diagrams of each type fig. 2 a–e.

GenAI model typeCharacteristicsAdvantagesDisadvantages
Generative adversarial network (GAN)A generator and a discriminator compete to produce realistic dataOutput hard to tell from real dataUnstable to train; hard to balance the two networks
Variational autoencoder (VAE)Encodes data into a latent space, then decodes it backOutput similar to training dataLess flexible than GANs; weak on sequential data; hard to control output quality
Autoregressive modelGenerates one step at a time, feeding back earlier outputVery realistic output, especially text and speechSlow in high dimensions; hard to scale to large datasets
Diffusion modelStarts from noise and refines it into an imageHigh-quality images from a small amount of data; no paired or labelled data neededSlow generation; computationally expensive
Flow-based modelMaps data to another distribution through invertible functionsFlexible; generates from a wide range of distributionsHard to train; computationally expensive

tab. 1 (in §3.5)

Practitioner sentiment. Of the analysed texts, 93.8% were positive, 3.1% negative and 3.1% neutral fig. 4. The word cloud is dominated by "ai", "generative", "construction", "project", "data" and "design" fig. 3.

Practitioner themes on opportunities (nine key themes) tab. 3: construction documents and data management; question answering; automation for unique challenges; AI-generated designs; accurate forecasting; project data synthesis; efficiency and sustainability; materials assessment; and AI as an augmentation of people rather than a replacement tab. 3.

Practitioner surveys. A LinkedIn poll of 48 AEC professionals found 40% had never used generative AI at work, 33% used it sometimes, 19% often and 8% all the time §5.9. Another poll of 16 AEC professionals found 63% said their organisation had no policy on commercial GenAI tools, 31% had one and 6% were unsure §5.9. These are small, self-selected samples.

Opportunities by phase tab. 4. The paper lists about 45 applications across six groups. Each has a main beneficiary and a suggested output type:

  • Feasibility: feasibility reports, project initiation documents, a Q&A chatbot, milestone prediction, contracts. Mostly text-to-text, plus text-to-image for site and zoning visuals.
  • Design: conceptual design generation (text-to-task), 3D visualisation of roles (text-to-3D), cost estimates, structural and MEP requirement extraction, permit drafts, code comparison (text-to-task), and contractor selection.
  • Procurement: delivery schedule visualisation, request for quotation, supplier selection, bidding support, and inventory management.
  • Construction: document extraction, document generation, classification and translation, code generation for tasks, cost-estimate workflow, schedule generation, drone-based progress tracking, quality checks against specifications, and training material for safety and trades.
  • Operation and maintenance: knowledge-management chatbot, work orders from logs, generative design of replacement parts (text-to-3D), predictive maintenance schedules, energy reports, and occupant chatbots.
  • Any phase: information retrieval from nD BIM models, natural-language BIM updates, and natural-language robot instruction and interaction.

Challenges §5, fig. 6. Eight challenge areas are named: domain knowledge, hallucinations, accuracy, generalisability, model updates and interpretability, cost, ethics and privacy, and construction regulation. Each has a short discussion with proposed mitigations §5.1–§5.8.

Recommendations §6.1: fine-tune an available LLM on construction data; keep human oversight with review and feedback; measure business impact through KPI pilots; and in the long run build custom construction LLMs from a shared data repository.

Research questions §6.2: ten open questions, covering extraction from documents and BIM, generative design, conversational assistants, text-to-visual generation, visual progress and safety monitoring, scheduling and cost, BIM-updating assistants, robot interaction, code generation for scope changes, and continual learning.

Paper vs code

No official code. The paper has no code or project-page link, only links in its reference list. A GitHub repository search for the title's keywords returned no results. No repository was cloned, and no code is cited.

Pitfalls

  • Not a benchmark. Nothing here can be reproduced as an experiment. Sentiment figures come from 32 posts and polls, and the study does not report inter-rater checks or any statistical test §2, §4.2.
  • Table 2 citations do not match. The caption cites references [94]–[102] for "current ten largest LLMs". Several of those are not LLM papers: [94] is NICE, [95] is VideoFlow and [96] is RealNVP (reference list). Treat Table 2 values as unverified from this paper, and check the dates: the paper's literature window ends in August 2023 §2.
  • Duplicate reference. Reference [67] and reference [136] are the same article (reference list). Some references lack venue or year, for example [97] (BIM-GPT) (reference list).
  • The paper says "AI" but means different things. The text sometimes treats GenAI as all of deep learning §1 and sometimes as only the five generative families §3. Table 1 covers five families, but the applications table mostly assumes LLMs (text-to-text) tab. 4.
  • Opportunity lists are not ranked. Table 4 gives no evidence of value, cost or feasibility for each application. Its "model type based on output" column is the authors' classification, not a tested mapping tab. 4.
  • The framework is conceptual. Figure 5 names no metrics for stage III beyond "accuracy" and "uncertainty" to check fig. 5 §5.3. The paper does not say how fine-tuning data should be cleaned or sized.
  • Hallucination mitigations are listed, not evaluated. High-quality data, grounding, simulated testing, uncertainty monitoring and human oversight are proposed §5.2. Their effect is not measured.
  • Terms. "Fine-tuning" is used broadly, to include reward and parameter adjustment §4.4, so the paper does not separate supervised fine-tuning from reinforcement learning.

Lineage

  • Builds on: the GAN (Goodfellow et al., 2014) §3.1, ref. 73; the VAE (Kingma and Welling, 2013) §3.2, ref. 82; the diffusion model (Ho et al., 2020) §3.4, ref. 91; flow-based models (Dinh et al., 2014 and 2016) [§3.5, refs. 94 and 96].
  • Related construction work the paper cites: BIM-GPT §4.1, ref. 97, ChatGPT for scheduling §4.1, ref. 98 and RoboGPT §4.1, ref. 102.
  • Compared against: nothing; the paper is a review, not a method comparison.

Source and license

Adapted from “Generative AI in the Construction Industry: Opportunities & Challenges” by Prashnna Ghimire, Kyungki Kim, Manoj Acharya (arXiv:2310.04427), used under CC BY 4.0. Changes: condensed and restructured for implementation, with tables, equations and algorithms taken from the paper and its code, each cited to its source. Not affiliated with or endorsed by the authors.