Engine Turbine Blade Removal Process Redesign
Bibliographic record
Abstract
The purpose of this project is to design an improved rivet removal process for the client, StandardAero, which will ensure consistent alignment accuracy during drilling of the rivets. The client is StandardAero and the design team (Team 19) comprises four undergraduate students from the University of Manitoba’s Faculty of Mechanical Engineering. The team have used their collective engineering skills and experience developed over the past 4-5 years of education and related internship experience to design an alignment guide and fixture design that will provide for consistent alignment accuracy between the rivets. This design consists of two main components; a drill alignment guide and a redesigned disk mounting assembly. The alignment guide provides for initial alignment of the drill bit with the rivet bore on the turbine disk. The guide consists of a tubular shaft, with an outer diameter of 0.20” and length of 0.85”. It has an inner bore running through its length at a diameter of 0.074”. The guide also has a knurled handle with a diameter of 0.35”, and is perpendicular to the tubular shaft. The material specified for this guide is high strength polypropylene thermoplastic. The bottom end of the guiding shaft matches the shape of the chamfer that surrounds the rivet bore, and is designed to sit on the chamfer so that the inner bore is aligned with the rivet bore. The redesigned disk mounting assembly replaces the current bearing system with a motorized rotary stage, by ThorLabs Inc. Once the initial drill alignment is set, the rotary stage rotates the turbine disk to subsequent rivet bore positions by a specified distance, and ensures that movement is consistent throughout the drilling process. The rotary stage is run by a stepper motor which is controlled by a motor controller with pre-programmed software, allowing an operator to set the specified distance and control the rotary stage through a simple GUI menu on a PC workstation. The estimated cost of the redesigned fixture assembly (excluding the alignment guide) was determined to be approximately $4000. However, if the implementation of this design results in a reduction of even a […]
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.003 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 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.005 | 0.004 |
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".