Room Data Sheets for Architectural Programming
Bibliographic record
Abstract
Architectural programming (AP) is the first essential step before starting the schematic design of a project. This process allows for the identification of the description and layout of an area based on specific project requirements while defining scope of work and crucial factors towards client satisfaction. One deliverable within the AP is the room data sheet (RDS), presenting information pertaining to the project rooms. Specifically, RDS information includes room names, intended uses, locations, numbers, description of the finishes, fixtures and fittings, as well as mechanical and electrical requirements within the space. Despite several attempts to develop multiple programming techniques and effectively meet clients’ project requirements, previous projects aimed at capturing architectural programming have not been adopted, and poor early-stage planning remains a barrier in the construction field, potentially resulting in project delays, cost inefficiency, and ultimately client dissatisfaction. This study proposes an RDS data representation with the aim of enhancing project planning efficiency. The contribution of this study is to help pre-design practitioners and researchers in reducing design changes, associated project costs and delays, and ultimately improving client satisfaction and construction efficiency.
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.002 | 0.015 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.004 | 0.005 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.005 | 0.004 |
| Open science | 0.002 | 0.003 |
| Research integrity | 0.001 | 0.003 |
| Insufficient payload (model declined to judge) | 0.106 | 0.048 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".