# Overall Labor Effectiveness (OLE) Calculator

> Source: https://netray.co/tools/overall-labor-effectiveness-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Measure how well paid labor hours turn into good output, using the same availability, performance and quality structure as OEE.

## Category

ehs-workforce

## Audience

- Plant manager
- Production supervisor
- Continuous improvement manager

## Tool

**Kind:** calculator

**Currency:** $

**Inputs:**

#### Scheduled labor hours

**Key:** sched_hours

**Type:** number

**Default:** 800

**Min:** 1

**Step:** 10

**Unit:** hours

**Help:** Headcount times shift hours for the period, for example 20 people x 8 hours x 5 days.

#### Absence and late hours

**Key:** absent_hours

**Type:** number

**Default:** 40

**Min:** 0

**Step:** 1

**Unit:** hours

**Help:** Hours scheduled but not worked.

#### Non-productive hours

**Key:** nonprod_hours

**Type:** number

**Default:** 60

**Min:** 0

**Step:** 1

**Unit:** hours

**Help:** Waiting for material, meetings, training, cleaning and similar time while present.

#### Earned standard hours

**Key:** earned_hours

**Type:** number

**Default:** 640

**Min:** 0

**Step:** 10

**Unit:** hours

**Help:** Units produced times routing standard hours per unit, summed across jobs.

#### Total units produced

**Key:** total_units

**Type:** number

**Default:** 5200

**Min:** 0

**Step:** 50

**Unit:** units

#### Good units

**Key:** good_units

**Type:** number

**Default:** 5030

**Min:** 0

**Step:** 50

**Unit:** units

#### Loaded labor rate

**Key:** wage

**Type:** number

**Default:** 24

**Min:** 0

**Step:** 0.5

**Unit:** per hour

**Help:** Wage plus benefits and burden.

**Outputs:**

#### Productive hours present

**Key:** productive_hours

**Expr:** max(sched_hours - absent_hours - nonprod_hours, 0)

**Format:** hours

#### Labor availability

**Key:** labor_avail

**Expr:** if(gt(sched_hours, 0), productive_hours / sched_hours * 100, 0)

**Format:** percent

#### Labor performance

**Key:** labor_perf

**Expr:** if(gt(productive_hours, 0), earned_hours / productive_hours * 100, 0)

**Format:** percent

**Description:** Earned standard hours divided by productive hours. Above 100 means faster than standard or loose standards.

#### Labor quality

**Key:** labor_qual

**Expr:** if(gt(total_units, 0), min(good_units, total_units) / total_units * 100, 0)

**Format:** percent

#### Overall labor effectiveness

**Key:** ole

**Expr:** labor_avail * labor_perf * labor_qual / 10000

**Format:** percent

**Primary:** true

#### Earned hours on good units

**Key:** good_earned

**Expr:** earned_hours * labor_qual / 100

**Format:** hours

#### Hours not converted to good output

**Key:** lost_hours

**Expr:** max(sched_hours - good_earned, 0)

**Format:** hours

#### Cost of lost labor hours

**Key:** lost_cost

**Expr:** lost_hours * wage

**Format:** currency

**Primary:** true

**Disclaimer:** OLE depends on how credible your standard hours are. Poor standards give poor OLE no matter how carefully you enter the data. Use it to compare periods and teams, not to rank individuals.

## Content

**Intro:** Overall labor effectiveness applies the OEE idea to people: how much of the paid time became good output at the standard rate? Enter scheduled hours, absence, non-productive time and earned standard hours to get a single figure and the cost of the gap.

**Sections:**

#### How to use the OLE calculator

**Body:** Start with scheduled labor hours for the period, then subtract absence and late hours to find who was present. Subtract non-productive time such as waiting for material, meetings, cleaning and training to find productive hours. Earned standard hours come from production confirmations: units produced multiplied by the routing standard hours per unit. Add total and good units for quality. The calculator returns labor availability, performance, quality and the product, which is OLE. The last two outputs convert the gap to hours and to cost using a loaded labor rate.

#### The method behind OLE

**Body:** OLE mirrors OEE. Availability is present and productive hours over scheduled hours. Performance is earned hours over productive hours, effectively the traditional labor efficiency. Quality is good units over total units. Multiplying them stops one strong factor from hiding a weak one. A crew at 105 percent efficiency can still post a poor OLE when absence is high and a fifth of the units are scrapped. There is no single published standard for what counts as non-productive, so define it once in writing and apply it to every shift.

**Bullets:**

- Availability: attendance and being free to work.
- Performance: pace against the routing standard.
- Quality: first pass good output.

#### Reading the result

**Body:** With the defaults, labor availability is 87.5 percent, performance about 91 percent and quality about 97 percent, so OLE is near 77 percent. Of 800 scheduled hours, roughly 180 did not become good output, which at a loaded rate of 24 per hour is more than 4,000 per week. Compare that to the cost of the likely causes. Material shortages may point to planning, not labor. Low performance may point to a bad standard. High absence needs a different conversation altogether. Break the three factors out before deciding who needs coaching.

#### Common mistakes

**Body:** The usual traps are mixing indirect and direct labor in the same calculation, letting earned hours include units later scrapped, and treating a performance figure above 100 percent as a win when the standard is simply old. In an ERP such as SAP, Infor, Epicor or Oracle, earned hours should come from operation confirmations multiplied by standards, and attendance from time clock data. If those two sources disagree on who worked on what, fix that before trusting any labor metric.

**Cta:** If you want OLE built from confirmations and time clock data in your ERP, Netray can set that up as a read-only report on your own data. This calculator works standalone.

**Faq:**

#### What is overall labor effectiveness?

**Answer:** It is an OEE style metric for labor: availability of people, performance against standard hours and quality of output, multiplied together. It shows how much paid time ended up as good output at the planned pace.

#### How is OLE different from labor efficiency?

**Answer:** Labor efficiency is usually earned hours divided by worked hours, which is only the performance factor. OLE also includes absence and non-productive time and the share of good units, so it exposes losses efficiency ignores.

#### What is a good OLE?

**Answer:** There is no universal figure. Repetitive assembly may sit in the 70 to 85 percent range, while engineered to order work is lower. Track your own trend and compare similar teams with the same standards and definitions.

#### Should I use OLE to rate individual operators?

**Answer:** It is a poor fit. Many losses, such as waiting for material, are outside an operator's control. Use OLE at crew, line or shift level to find systemic losses, then use detailed data for coaching.

## Search terms

overall labor effectiveness, ole calculator, labor efficiency calculator, labor utilization manufacturing, ole vs oee, labor productivity calculator, earned hours calculator, direct labor efficiency

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json