MétaCan
Menu
Back to cohort
Record W4413366889 · doi:10.1016/j.aei.2025.103778

Leveraging linked data for space constraints checking of mobile cranes in modular construction assembly lookahead planning

2025· article· en· W4413366889 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueAdvanced Engineering Informatics · 2025
Typearticle
Languageen
FieldEngineering
TopicBIM and Construction Integration
Canadian institutionsUniversity of Alberta
FundersWorldwide Universities NetworkUniversity of Auckland
KeywordsModular designComputer scienceModular constructionSpace (punctuation)Systems engineeringDistributed computingEngineering drawingTheoretical computer scienceEngineeringProgramming languageOperating system

Abstract

fetched live from OpenAlex

Preparing constraint-free lookahead schedules (LAS) in the assembly stage of dynamic modular construction (MC) projects requires checking space availability for mobile crane operation using heterogeneous, distributed information sources. Current automated crane space evaluation methods rely on centralized information databases, whereas linked data based approaches are limited by insufficient geometric computation capabilities. This study proposes a framework to model and validate the space constraints for mobile crane operations using the semantic web. It starts with developing an ontology to represent crane lifting space requirements on the semantic web. Information sources, including construction site point clouds, 4D building information models, and crane specifications, are semantically interconnected using linked data. Shapes Constraint Language JavaScript Extension performs constraint validation through JavaScript-based mathematical computations utilizing the Separating Axis Theorem and a triangulation-based approach to check space for crane placement and rotation, respectively. Validation on two MC sites demonstrated the framework’s effectiveness in identifying space constraint violations.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.588
Threshold uncertainty score0.844

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.013
GPT teacher head0.253
Teacher spread0.240 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it