Wire Drawing & Rod Processing worked example
Lubricant Consumption at 98% lubricant transfer efficiency: a worked example
What does the result look like when lubricant transfer efficiency reaches 98%? The full calculation is worked below with real intermediate numbers. Use it when lubricant consumption in wire drawing and rod processing needs a buy quantity for the next wire drawing and rod processing run and you do not want to short the line.
The inputs for this scenario
- Wire length (or mass) drawn: 500 units (unchanged)
- Lubricant used per unit of wire: 0.08 units (unchanged)
- Lubricant transfer efficiency: 98 % (raised for this scenario; the documented default is 85)
Working through the calculation
- Applying the documented formula (Required lubricant consumption = covered amount × use per unit ÷ transfer efficiency) to the inputs above produces each figure below.
- At this operating point the engine returns 40.82 units for required quantity, the number this scenario is built around.
- At this operating point the engine returns 40 units for theoretical amount.
- At this operating point the engine returns 0.82 units for loss allowance.
- At this operating point the engine returns 98 % for efficiency.
How this compares with the baseline
- Against the tool's baseline example, where lubricant transfer efficiency sits at 85% and the headline result is 47.06 units, this scenario comes in 13.27% below the baseline at 40.82 units.
- A figure at this level is achievable when lubricant transfer efficiency is genuinely sustained, not just peaked for a shift. It uses a single average use-per-unit and efficiency figure; real consumption varies with die geometry, reduction, wire speed, and how often boxes are recharged, so treat the result as a planning estimate.
Results at a glance
- Required quantity: 40.82 units (headline result)
- Theoretical amount: 40 units
- Loss allowance: 0.82 units
- Efficiency: 98 %
Run it with your numbers
- Every input above is editable in the live Lubricant Consumption calculator, which recalculates instantly and can be shared with the inputs intact.
Last reviewed 2026-05-12.