Hml Analysis
HML analysis is a selective inventory control method that classifies items into High, Medium, and Low groups based on unit cost or unit price, not annual consumption value. It prioritizes control effort on expensive items carrying the highest financial risk, enabling tighter oversight, accurate counting, and purchasing discipline for costly materials while applying simpler controls to low-value consumables.
In practice, HML analysis is built from the item master by extracting each SKU's unit cost, sorting items by cost, and assigning threshold bands for High, Medium, and Low classes. On the shop floor, high-cost parts typically receive tighter authorization rules, lower handling exposure, more frequent cycle counts, stricter supplier and receipt checks, and faster escalation on discrepancies. Low-cost consumables are managed with simpler controls to reduce administrative effort. The operational value is not just categorization: HML helps planners focus limited attention on expensive raw materials, spare parts, and bought-out components where shrinkage, obsolescence, or mis-issue can create outsized cost impact. It is commonly refreshed with master data reviews. This selective approach turns a standard inventory list into a prioritized control plan, ensuring the most valuable materials receive the most rigorous governance.
- Stale unit costs distort HML bands: Outdated ERP costs omit landed-cost elements or price spikes, moving items into the wrong band and causing over-auditing of cheap parts or under-protection of critical expensive ones.
- HML mistaken for usage logic: HML ranks by unit value, not annual consumption value, so high-usage low-cost consumables draw excessive attention while high-value spares stay under-controlled, misallocating oversight.
- Fixed thresholds ignore market shifts: Static H/M/L cutoffs fail when commodity prices or supplier pricing change, causing class drift and leading to stockout risk for controlled materials and excess stock for obsolete items.
Is HML a replacement for ABC analysis?
No. HML segments by unit cost, while ABC segments by annual consumption value; they answer different control questions and are often used together.
What data fields are minimally required for HML analysis?
Item code, unit cost, unit of measure, and ideally current inventory status; many implementations also include supplier, lead time, and annual demand for exception review.
How often should HML be refreshed?
The sources emphasize periodic review as prices and inventory conditions change; in practice this is commonly tied to monthly or quarterly master-data review cycles in ERP-controlled environments.