Descaling forgings degrades the machine that does it, continuously and invisibly. Blades, liners and impellers wear from the moment they are fitted, and the machine compensates by taking longer and throwing more media to reach the same finish. Nothing breaks, nothing alarms, and the cost climbs on a curve nobody is plotting.
Your ERP logs the pieces blasted and the abrasive purchased.
It won’t tell you the wheel has been drawing differently for a fortnight, or that cycle time crept up to hide it.
Why the gap existsWhere the losses hide
Wear has no alarm. It shows first as a reading, then as consumption, and only at the end as a breakdown.
Worn blades throw less efficiently, so the same descale takes more media. Abrasive per tonne is the honest measure and it rises long before anyone opens the cabinet.
Operators add time to reach the finish they know is right. It is the correct thing to do and it silently turns a wear problem into a throughput problem.
A blast wheel’s motor current changes as the blades go. It is a reading weeks before it is a stoppage, and it is the earliest honest signal of the wear state.
The join
Same run, same clock, same asset — three streams that only mean something together.
Pieces blasted, abrasive purchased and issued, and the maintenance job when a wheel is finally changed.
Blast wheel motor current and cycle time sampled continuously, abrasive consumption tied to the machine, and the operator’s log when a wheel is opened.
Abrasive per tonne and cycle time read against the wheel’s own current, so wear is a trend you watch rather than a failure you discover.
What Munshi surfaces
Teal is normal, maroon is flagged. Illustrative data.
The shaded stretch is the wheel working harder for the same job.
A trend, not a spike. This is what wear looks like on the cost side.
When an outcome moves and a signal moves with it, Munshi shows both and says they moved together. It does not tell you one caused the other. The operator confirms the cause, and the confirmed cause is written back to that asset’s register — so the pattern is already named the next time it appears.
Related stages
The cycle that ran, versus the cycle that was specified.
Laps and cracks that keep coming back from the same die.
Get started
See this on your own line.
Bring a month you already understand. The useful test is whether Munshi finds what you already know — and then what you didn’t.