Asset Management and Pavement Management: Using Common Elements to Maximize Overall Benefits
Bibliographic record
Abstract
The public and private sectors have been managing their assets in some form for many years. Recently, however, the concept of asset management has been formulated to draw more explicitly on the principles of business, technology, economics, and other disciplines in a systematic and integrated way. This strategy offers cost-effective and responsive advantages in managing the public’s assets. Other management systems, particularly pavement management, have preceded the current interest in asset management by several decades. Accordingly, it is useful to assess whether there are common elements between asset management and pavement management and, if so, whether the experience gained from pavement management implementation and operation can be of benefit. In a generic sense, asset management has extensive commonalities with its component systems such as pavement management. However, asset management has some issues to resolve in progressing from a framework to an operational reality. A number of ways or areas in which asset management system development and implementation can benefit from pavement management operational experience are presented. Finally, some technical, economic/technical, and institution and user opportunities for innovations and advancements in asset management systems are identified.
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.003 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.002 | 0.002 |
| Science and technology studies | 0.002 | 0.004 |
| Scholarly communication | 0.010 | 0.009 |
| Open science | 0.002 | 0.005 |
| Research integrity | 0.002 | 0.002 |
| Insufficient payload (model declined to judge) | 0.007 | 0.001 |
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".