Rare Earth Magnet & Motor Materials worked example
Grinding Loss with magnet material loss rate of 30 units / hr: a worked example
What does the result look like when magnet material loss rate reaches 30 units / hr? The full calculation is worked below with real intermediate numbers. Use it when grinding loss in rare earth magnet and motor materials is being quoted and consumables are a real chunk of the cost stack.
The inputs for this scenario
- Magnet Material Loss Rate: 30 units / hr (raised for this scenario; the documented default is 12)
- Grinding Line Runtime: 8 hr (unchanged)
- Cost per Unit of Ground-Away Material: 3.5 $ / unit (unchanged)
Working through the calculation
- Applying the documented formula (Grinding loss consumed = grinding loss use rate × grinding loss runtime) to the inputs above produces each figure below.
- At this operating point the engine returns 240 units for grinding loss consumed, the number this scenario is built around.
- At this operating point the engine returns 840 $ for grinding loss run cost.
- At this operating point the engine returns 8 hr for grinding loss runtime.
- At this operating point the engine returns 3.5 $ / unit for grinding loss unit cost.
How this compares with the baseline
- Against the tool's baseline example, where magnet material loss rate sits at 12 units / hr and the headline result is 96 units, this scenario comes in 150% above the baseline at 240 units.
- A figure at this level is achievable when magnet material loss rate is genuinely sustained, not just peaked for a shift. It assumes a steady loss rate over the run; in reality material removal varies with wheel wear, infeed, and part geometry, so use it for planning averages rather than exact per-part accounting.
Results at a glance
- Grinding loss consumed: 240 units (headline result)
- Grinding loss run cost: 840 $
- Grinding loss runtime: 8 hr
- Grinding loss unit cost: 3.5 $ / unit
Run it with your numbers
- Every input above is editable in the live Grinding Loss calculator, which recalculates instantly and can be shared with the inputs intact.
Last reviewed 2026-05-12.