Internet‐based database management system for project control
Bibliographic record
Abstract
Purpose The objective of this paper is to develop an efficient project management system to track and control construction activities for contractors and/or project managers. Design/methodology/approach The work package model is utilized to break down project data into activities and work tasks. The data structure of a project is represented using the entities‐relationship methodology. A relational database stores all of the project data. The earned value method calculates the cost and schedule variances. The internet‐based platform with three‐tier client‐server architecture is chosen for system implementation. Findings The developed project database stores all of the project data necessary to perform project control functions. The implementation of the project database management system is efficient. The developed system provides real‐time data sharing and a collaborating environment in support of project control. Originality/value Time and cost control are essential management functions for achieving successful delivery of engineering, procurement and construction (EPC) projects. The developed system can assist contractors and/or project managers in tracking and control of their construction projects in a real‐time manner.
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.003 | 0.004 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.003 | 0.003 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.004 | 0.003 |
| Open science | 0.003 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.014 | 0.010 |
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".