Cost Reduction Processes for Transfer Case Sprockets: Part 1: Metallurgical Aspects
Bibliographic record
Abstract
Transfer case sprockets usually require quenching to improve hardness and mechanical properties. This additional process step can be avoided with sinter hardening. Indeed, sinter hardening allows the production of P/M parts with high strength and apparent hardness directly from sintering because the martensitic transformation takes place during the cooling portion of the sintering operation. Therefore, this process eliminates the need for a post-sintering heat treatment with all the inherent related problems such as part distortion, oil contamination and added processing costs. Many low alloy steel powders have been developed for sinter hardening applications. These materials, combined with the availability of sintering furnaces equipped with enhanced cooling capacity, make sinter hardening particularly attractive for parts that are difficult to quench because of their size and shape. Moreover, the powder mix formulation and processing conditions can be tailored to achieve a specific microstructure. The objective of this paper is to review the metallurgical aspects involved in sinter hardening and to relate these to the characteristics of the base powder, admixed additions and processing conditions in order to develop appropriate mix formulations for the production of transfer case sprockets.
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.000 | 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.000 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.007 | 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".