Menu
Utilización de la máquina vs carga: dos métricas de capacidad que parecen iguales y conducen a decisiones diferentes.

Utilización de la máquina vs carga: dos métricas de capacidad que parecen iguales y conducen a decisiones diferentes.

La utilización mide qué parte del tiempo disponible la máquina estuvo en funcionamiento. La carga mide qué parte del tiempo disponible se programó. ¿Por qué ambos son importantes para las decisiones de capacidad?
Utilización de la máquina vs carga: dos métricas de capacidad que parecen iguales y conducen a decisiones diferentes.
Machine Utilization vs Loading: Two Capacity Metrics That Sound the Same and Lead to Different Decisions

Key takeaways

  • Machine utilization = run time / scheduled time. How much of scheduled time was used.
  • Machine loading = scheduled time / available time. How much of available time was scheduled.
  • Different metrics drive different decisions: utilization for productivity; loading for capacity decisions.
  • A machine can be 95% utilized and 60% loaded — running well when scheduled but only scheduled 60% of the time.
  • Capacity planning needs both. Decisions made on either alone tend to mislead.

Short answer: Machine utilization is run time divided by scheduled time — how much of scheduled time the machine actually ran. Loading is scheduled time divided by available time — how much of total available time was scheduled in the first place. A machine can be 95% utilized and only 60% loaded: running well when scheduled but scheduled only 60% of the time. Capacity decisions need both metrics; either alone misleads. See also OEE vs Utilization.

What utilization measures

Utilization = Run time / Scheduled time

Utilization is a productivity ratio. It tells you how effectively scheduled time was used. High utilization means few unplanned stops during scheduled production.

What loading measures

Loading = Scheduled time / Available time (calendar)

Loading is a scheduling decision. It tells you how much of total calendar time the line was scheduled to operate. Low loading means the line was scheduled for fewer hours than possible.

How they differ in scope

Utilization asks: when we scheduled the line, how well did it run?

Loading asks: how much did we schedule in the first place?

Both can be high (well-loaded, well-utilized) or low. The combination tells the story.

The four scenarios

High loading, high utilization. Line scheduled aggressively and runs well. Capacity-constrained.

High loading, low utilization. Line scheduled aggressively but runs poorly. Reliability problem.

Low loading, high utilization. Line scheduled lightly but runs well when scheduled. Demand-constrained.

Low loading, low utilization. Light schedule and runs poorly. Worst case — investigate both demand and reliability.

Which decisions each drives

Utilization drives:

  • Reliability improvement priorities.
  • PM program effectiveness.
  • Operator skill assessment.

Loading drives:

  • Capacity decisions (add shift, add line).
  • Sales and marketing capacity.
  • Capital investment timing.

Mixing them produces wrong decisions in either direction.

Common confusion

"Our line is 80% utilized so we are running well."

If loading is 50%, the line ran well on 40% of available time. Plenty of capacity remains. Different answer than 80% utilized at 95% loading.

The aggregate "80%" without context misleads.

How to report both

  • Calendar time: 168 hours/week.
  • Available time after maintenance windows: 156 hours/week.
  • Scheduled time: 80 hours/week. Loading = 80/156 = 51%.
  • Run time during scheduled: 76 hours/week. Utilization = 76/80 = 95%.
  • Aggregate capacity used: 76/156 = 48.7% (calendar utilization or TEEP-like).

Each number has its place.

How OEE fits

OEE is calculated against planned production time (similar to scheduled time). OEE Availability is similar to utilization in the OEE framework.

OEE does not directly include loading. TEEP (Total Effective Equipment Performance) extends OEE to calendar time, capturing the loading dimension.

Capacity expansion decisions

Adding a shift adds loading hours. The decision should consider:

  • Current utilization. If poor, fix utilization first; new shift adds bad hours.
  • Current loading. If low, more shifts may not be utilized.
  • Demand. New shifts produce more units only if demand absorbs them.
  • Cost. Labor, energy, maintenance scale with hours.

Loading and utilization both inform the math.

Common mistakes

1. Reporting only utilization. Misses the loading question.

2. Reporting only loading. Hides whether scheduled time is productive.

3. Treating utilization as OEE. Different metrics.

4. Adding capacity to high-utilization, low-loading lines. The line is already idle most of the time.

How a modern OEE platform handles both

A modern OEE platform reports utilization within OEE Availability and exposes loading separately, with calendar time as the broadest denominator.

Fabrico's OEE module reports utilization within OEE Availability, exposes loading separately, and supports TEEP for combined calendar-utilization analysis.

See how Fabrico captures this automatically — explore OEE for manufacturing or book a demo.

Related reading

Frequently asked questions

Is loading the same as TEEP?

Related. TEEP combines loading effect with OEE for a calendar-time effectiveness number.

Should I aim for high loading?

Only if demand and utilization support it. High loading on a poorly-utilized line wastes hours.

Can both be 100%?

Theoretically yes; practically rare. Maintenance and changeover make both reaching 100% impractical.

Which one should I report to leadership?

Both, with context. Each answers a different strategic question.

Does loading affect OEE?

Not directly. OEE is calculated within scheduled time. Loading sits above scheduling.

Lo último de nuestro blog

Defina su hoja de ruta de confiabilidad
Valida tu retorno de inversión potencial: Reserva una demostración en vivo.
Defina su hoja de ruta de confiabilidad
Al hacer clic en el botón Aceptar, usted da su consentimiento para el uso de cookies al acceder a este sitio web y utilizar nuestros servicios. Para obtener más información sobre cómo se utilizan y gestionan las cookies, consulte nuestra Política de privacidad y Declaración de cookies