The Business Case, Honestly

Monitoring projects are justified with productivity percentages borrowed from case studies. Those figures are the weakest part of most business cases.

Savings that are real and sizeable

Travel reduction. In a picking operation travel is typically the largest single component of task time, and slotting changes informed by real movement data reduce it measurably.

Waiting reduction. Work queueing between stages is invisible without timestamps and frequently exceeds handling time.

Equipment right-sizing. Utilisation data regularly shows fleets larger than required, or shortages concentrated at particular hours rather than overall.

Rework and error cost, once errors are traced to their origin rather than to their detection point.

Overtime, where demand curves allow better shift shaping.

Each of these is measurable in your own facility before and after, which is what makes them defensible.

Figures to avoid quoting

Percentage productivity uplifts from vendor material with no accessible methodology.

Industry averages applied to your facility, which differs in layout, product mix and volume in ways that dominate the average.

Savings that assume every identified inefficiency is eliminated, which none are.

Anything you cannot trace to a method you could describe. One unsupportable number checked by a finance director discounts every subsequent one.

Sizing it from your own data

Run the elapsed time decomposition on existing records: waiting, travel, handling, checking, rework as proportions of total.

Take the largest non-value component and estimate a realistic reduction, conservatively.

Convert to hours, then to cost, at your own rates.

State the assumption explicitly so it can be challenged rather than the conclusion.

This analysis costs a week and produces a number you can defend, which is worth more than a larger number you cannot.

Costs that get missed

Integration effort, which is mostly your own people's time and is the largest first-year cost.

Data quality work. Scan discipline, master data, location accuracy — all of which must be fixed before the analysis means anything.

Ongoing ownership. Somebody maintains this permanently or it decays within a year.

Change management, particularly if any individual measurement is involved, where the cost is in trust rather than money.

Infrastructure for positioning systems, which is a building project rather than a software one.

What to commit to

Not a productivity percentage.

A specific change in a specific measure, with a date and the same measurement method afterwards.

"Average waiting time between picking and packing from forty minutes to under fifteen within two quarters, measured from the same timestamps."

Checkable, which is uncomfortable and is precisely what makes it credible.

The argument that needs no numbers

Safety. Where monitoring supports incident prevention or investigation, the case is regulatory and ethical rather than financial, and it should be made on those terms rather than being bundled into a productivity claim.

Visibility as a precondition. A facility that cannot say where work waits cannot improve deliberately, only by guessing. That is a legitimate argument and it does not require a return figure attached.

Costing one exception end to end

The number that funds the prevention work, and it takes a day to produce.

Pick a common exception type.

Trace one instance completely: detection, investigation, correction, rework of downstream steps, and any customer impact.

Include the people involved and their time, which is usually several people across several stages.

Include the cascade where it stopped something else.

Multiply by the annual frequency.

The result is usually startling, and it is more persuasive than any productivity percentage because it is built entirely from your own operation.

Separating the safety case

Bundling safety into a productivity number weakens both arguments.

The safety case is regulatory and ethical. It does not require a return figure and should not be given one.

The productivity case is financial and should be built from your own decomposition.

Presented together but separately, so that neither becomes contingent on the other.

Where a control serves both — telematics covering pre-use checks and utilisation — say so, and attribute the cost once.

A safety argument made to rest on a productivity claim collapses when the claim is questioned, which is a bad position to be in after an incident.