On an HMC, machine utilisation hides the truth.

A pallet-equipped machine can look near-continuously busy while throughput is throttled by pallet turnaround. What to measure instead, and why setup duration ranks jobs backwards.

A horizontal machining centre with pallet changing breaks an assumption that every other machine on this list satisfies: that machine-level utilisation tells you the truth. An HMC can show excellent utilisation while one pallet sits loaded and waiting for hours, and the machine-level figure will never reveal it.

Monitoring an HMC properly means measuring at pallet level as well as machine level, and understanding that the two numbers answer different questions.

Why machine-level utilisation misleads on an HMC

MACHINE VIEWSpindle busyThe machine reports running. Utilisation looks strong and nothing appears wrong.
PALLET VIEWOne pallet productivePallet A is cutting. Pallet B was loaded forty minutes ago and is waiting.
THE GAPIdle work in progressMaterial, setup labour and floor space are committed to work that is not progressing.
WHAT IT COSTSThroughput, not utilisationThe constraint is pallet turnaround, and no machine-level metric will show it.

This is the central point of HMC monitoring. The machine can be near-continuously busy while the cell's throughput is limited by how quickly pallets are loaded, unloaded and made ready — which is a labour and scheduling problem that machine-level data actively conceals.

What to measure on a pallet-equipped machine

MEASURE

Pallet turnaround time

From pallet-out to the same pallet being ready again. The number that actually governs cell throughput.

MEASURE

Pallet-level cycle attribution

Which pallet, which fixture, which job. Otherwise a slow job and a slow pallet are indistinguishable.

MEASURE

Load-station occupancy

How long a pallet waits at the load station after being finished with, and after being made ready.

MEASURE

Machine-waiting-for-pallet

The state that matters most and is easiest to miss: spindle available, no pallet ready.

What the controller gives you, and what it does not

A networked HMC control reports machine state, cycle timing, counts and alarm presence like any other machining centre, and on many machines it reports which pallet is in the spindle position. Where that pallet identity is available, pallet-level attribution follows directly.

Where it is not, pallet identity has to come from elsewhere — an operator selection at the load station, or a signal from the pallet changer. This is worth establishing during the pilot rather than assuming, because pallet-level analysis is the main reason to monitor an HMC differently from a VMC, and without pallet identity you have an expensive VMC in the data.

Worked example

OEE on a HMC, both ways.

The standard definition first, then the variant MachineWise computes and why it differs. Quote the ISO figure externally; use the variant internally.

ISO 22400-2 — the standardMachineWise variant — internal
AvailabilityPlanned production time 435 min, actual production 389 min → 89.4%Reporting time 435 min, machine on-time 402 min → 92.4%
Performance / Effectiveness96 parts × 215 s ideal cycle ÷ 389 min → 88.4%Productive (in-cut) time 331 min ÷ 402 min on-time → 82.3%
Quality95 good of 96 → 99.0%95 good of 96 → 99.0%
Result78.3%75.3%

An HMC typically posts stronger figures than a VMC on both definitions, which is exactly why the machine-level number is dangerous here — it can look healthy while pallet turnaround is throttling the cell. Read it alongside pallet turnaround, never alone. The two numbers answer different questions and are not interchangeable. The ISO figure is comparable to published benchmarks; the variant is not, and should be treated as your own baseline to improve against. Both are computed side by side in the OEE calculator.

Setup on an HMC is a different event

The defining operational advantage of pallet changing is that setup happens off the machine while the machine keeps cutting. That changes what a changeover measurement means: the relevant number is not how long setup took, but whether setup finished before the machine needed the pallet.

A setup that took ninety minutes and was ready in time cost nothing in throughput. A setup that took thirty minutes and finished two minutes late cost a stoppage. Measuring setup duration alone will rank those two backwards, which is a good illustration of why machine-type-specific monitoring is not a marketing distinction.

Connect your machines today

Two HMCs on a live dashboard this week.

We will establish during the pilot whether your machines report pallet identity, because that single fact determines whether you get pallet-level truth or an expensive VMC in the data.

Book a free 2-machine pilot WhatsApp us
Questions

Straight answers.

Why is HMC monitoring different from VMC monitoring?
Because pallet changing decouples the machine from the work. An HMC can show strong machine-level utilisation while a loaded pallet waits, and no machine-level metric will reveal it.
What should be measured on a pallet-equipped machine?
Pallet turnaround time, pallet-level cycle attribution, load-station occupancy, and time spent with the spindle available but no pallet ready. The last one is the easiest to miss and often the most expensive.
Do HMC controls report which pallet is in use?
Many do, and where that identity is available pallet-level attribution follows directly. Where it is not, it comes from an operator selection at the load station or a signal from the pallet changer — established during the pilot.
Why does setup duration mislead on an HMC?
Because setup happens off the machine. A ninety-minute setup finished in time costs nothing in throughput; a thirty-minute setup finished two minutes late causes a stoppage. Duration alone ranks those backwards.
Should we expect higher OEE on an HMC than a VMC?
Usually yes on both definitions, which is precisely why the number needs reading alongside pallet turnaround rather than alone.
What happens if pallet identity is not available?
You get accurate machine-level monitoring — the same as a VMC — but not the pallet-level view that is the main reason to monitor an HMC differently.
FREE 2-MACHINE PILOT
Live OEE on two of your machines — this week. ₹0 to start.
Software-first setup in under an hour each · your data stays on-premises · plant-specific ROI model included.