Direct Pipe® as Alternative to HDD in Permeable Soil Conditions
Bibliographic record
Abstract
This paper provides an overview of the multiple case histories of the Direct Pipe technology in the US and overseas, including a 42″/48″ casing pipe installation by Michels Directional Crossings. Thereby illustrating the benefits for the owner, engineer and contractor in comparison to HDD in permeable soil conditions. The Direct Pipe method has been first used in 2007 at the Rhine river crossing in Worms, Germany. Since then, more than 18 crossings have been installed in Europe and the US with great success. The longest installation so far had a total length of 4,600ft (1,400m) and a pipeline diameter of 48″. The peak performance during that installation was 756ft (232m) per day (24hrs). The first installation in the US was in August 2010, crossing HI 70 in Florida. In 2011 the first 42″ system has been used at a project in Corning, NY by Michels Directional Crossings, for the installation of a casing pipe for a 24″ HDD crossing. Laney Directional Drilling followed in early 2013 with the first 48″ Direct Pipe system being operated in North America at the Aquashicola crossing for Williams Pipelines in Monroe county, Pennsylvania. August 2013 Direct Pipe made its debut in Canada at the Beaver River Crossing for Inter Pipeline Fund north of Bonnyville, Alberta. The largest pipeline currently installed is a 56″ steel pipe in Preston, England with a total length of 2,820ft, serving as casing pipe for a post installed 36″ potable water pipeline (HDPE). The combination of the well established Microtunneling technique with the Pipe Thruster technology makes it ideal for difficult (permeable) soil conditions which pose a certain risk for frack-outs using the HDD method.
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.001 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.020 | 0.003 |
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".