Workforce Analytics: Cost Per Tonne, Cost Per Unit, Done Right
Cost per tonne and cost per unit are the KPIs every COO asks for. They are also the KPIs that almost never match between finance and operations. The reason is structural, the numerator and denominator live in different worlds.
The Mismatch
- Numerator (labour cost): lives in HRMS / payroll, on a monthly cutoff.
- Denominator (output): lives in MES / ERP, on a daily cutoff.
- Cost centres rarely align cleanly between the two systems.
The Clean Architecture
- Define a single canonical cost centre tree, shared by HRMS and MES.
- Capture labour cost at the daily granularity (attendance hours x fully loaded cost per hour).
- Capture output at the daily granularity (good units x weight or count).
- Compute cost per output daily, roll up weekly and monthly.
- Reconcile to finance month end with a known tolerance and an aging anomaly list.
The Weekly Operating Rhythm
A defensible weekly cost per output number changes how a plant runs. Suddenly the COO and the CFO are looking at the same number. Suddenly the production team understands the financial consequence of a bad week. Suddenly the contract labour mix gets optimised because the data shows the cost.
Practitioner note
You cannot manage what you cannot measure, and you cannot measure what your systems disagree on. Get the architecture right and the conversation changes.
Frequently asked
Why does my current cost per tonne never match across systems?
Because the numerator (cost) and the denominator (output) live in different systems with different cutoffs. The fix is a single derived dataset with both lineages.
Amey Kadle
Founder & CEO, Ajinkya Technologies. 20+ years of building MES, ERP and AI systems for India’s most demanding manufacturing plants.