Bibliographic record
Abstract
Due to the many uses and the resulting lack of space within a municipally owned right-of-way, utility companies are often required to accommodate requests to relocate their assets. These requests come from external agencies such as the City of Toronto, Ontario Ministry of Transportation, Metrolinx, as well as private developers, to name a few. Relocation requests can be difficult to coordinate and cause frequent project delays and cost overruns. While it is important for the requesting agencies to clearly define the requirements of the relocation that is required, it is also important for utility companies to have a process that sufficiently meets the needs of the requesting agency. This report aims to identify best practices for processing relocation requests among utility companies from the Greater Toronto Area (GTA) by interviewing representatives from utility companies who are responsible for coordinating relocation projects. Data collected from these interviews determined that the process that each company uses is generally a combination of common implementation methods, depending on the overall structure of the utility company. Despite these differences, successful utility companies ensure that they are able to determine the horizontal alignments to where they are relocating early in the coordination, and maintain a project timeline within one year. Utility companies that do not already incorporate these steps should strive to meet these goals. Requesting agencies must also take into consideration that coordinating relocation projects is not the primary line of business for utility companies, and that there are due processes that must be followed to execute a relocation project. As such, it is recommended that utility companies work with external agencies that frequently request relocation work, to devise a process that is mutually beneficial and agreeable.
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 distilled prediction
Teacher imitationNot 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.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.005 | 0.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.000 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.001 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.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.
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 teacher head, 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".