# Oracle Fusion OEE Work Center Calculator

> Source: https://netray.co/tools/oracle-fusion-oee-work-center-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Calculate overall equipment effectiveness for a work center from production reporting figures, and see how downtime moves OEE.

## Category

mes-shop-floor

## Erp

Oracle Fusion Cloud SCM

## Audience

- Manufacturing engineer
- Oracle Cloud consultant
- Plant manager

## Tool

**Kind:** calculator

**Inputs:**

#### Planned production time

**Key:** planned_min

**Type:** number

**Default:** 960

**Min:** 1

**Step:** 30

**Unit:** minutes

**Help:** Scheduled time excluding planned breaks and non-scheduled periods.

#### Unplanned stop time

**Key:** downtime_min

**Type:** slider

**Default:** 85

**Min:** 0

**Max:** 600

**Step:** 5

**Unit:** minutes

**Help:** Breakdowns, changeovers and waiting within planned time.

#### Ideal cycle time

**Key:** ideal_sec

**Type:** number

**Default:** 30

**Min:** 0.1

**Step:** 0.5

**Unit:** seconds/unit

#### Total units produced

**Key:** total_count

**Type:** number

**Default:** 1500

**Min:** 0

**Step:** 10

**Unit:** units

**Help:** All units made, good and bad.

#### Good units

**Key:** good_count

**Type:** number

**Default:** 1440

**Min:** 0

**Step:** 10

**Unit:** units

**Outputs:**

#### Run time

**Key:** run_min

**Expr:** max(0, planned_min - downtime_min)

**Format:** minutes

#### Availability

**Key:** avail

**Expr:** run_min / planned_min * 100

**Format:** percent

#### Performance

**Key:** perf

**Expr:** min(100, ideal_sec * total_count / 60 / run_min * 100)

**Format:** percent

**Description:** Capped at 100% so a wrong ideal cycle time cannot inflate OEE.

#### Quality

**Key:** qual

**Expr:** good_count / total_count * 100

**Format:** percent

#### OEE

**Key:** oee

**Expr:** avail * perf * qual / 10000

**Format:** percent

**Primary:** true

#### Good units lost vs full potential

**Key:** lost_units

**Expr:** planned_min * 60 / ideal_sec - good_count

**Format:** integer

**Description:** Gap between theoretical output and good units.

**Chart:**

#### Availability and OEE vs unplanned stop time

**Type:** line

**X:** downtime_min

**From:** 0

**To:** 600

**Steps:** 30

**Series:**

- avail
- oee

**Disclaimer:** Follows the common availability x performance x quality definition. Definitions of planned time and ideal cycle differ by plant, so keep them consistent.

## Content

**Intro:** OEE condenses losses at a work center into one number built from availability, performance and quality. The inputs are the production quantities, scrap and downtime you already report against work centers in Oracle Fusion Manufacturing, so this calculator is a quick way to turn them into a score.

**Sections:**

#### How to use it

**Body:** Enter planned production time for the shift, the unplanned stop time inside it, the ideal cycle time per unit and the counts of total and good units. The calculator returns run time, the three OEE factors and the overall score, plus the good units lost against theoretical output. Use the same definitions every time: if changeovers count as downtime in one week, they must in all. Compare shifts and lines on the same basis before drawing conclusions.

#### The method

**Body:** Availability is run time divided by planned time. Performance is the ideal time to make the units produced divided by run time, which shows speed losses and small stops. Quality is good units divided by total units. OEE is the product of the three. For example, 91% availability, 86% performance and 96% quality give an OEE near 75%. Because the factors multiply, three apparently good numbers combine into a much lower score, which is why OEE exposes hidden losses.

**Bullets:**

- Availability = run time / planned time
- Performance = ideal cycle x total units / run time
- OEE = availability x performance x quality

#### Reading it and common mistakes

**Body:** A common benchmark quoted is 85% for world-class discrete manufacturing, but it is only a rough guide and varies by process. The more useful comparison is your own trend and the split of losses. Common mistakes include using demonstrated best speed rather than a defined ideal cycle, excluding changeovers from downtime, counting rework as good units and mixing products with different cycle times in one calculation. Calculate by product where cycle times differ.

**Cta:** If you would like OEE computed automatically from work center transactions and downtime reasons in your ERP or MES, we can help. The calculator is free either way.

**Faq:**

#### What counts as planned production time?

**Answer:** Time the work center is scheduled to run, excluding planned breaks, meetings and periods with no production scheduled. Pick a rule and apply it consistently, since it directly changes the availability figure.

#### Why cap performance at 100%?

**Answer:** If performance exceeds 100%, the ideal cycle time is probably set too slow or counts are wrong. Capping stops a bad standard from hiding availability and quality losses, and flags that the standard needs review.

#### Is 85% OEE a realistic target?

**Answer:** It is often quoted as a world-class benchmark, but many plants with high mix and frequent changeovers sit well below it and still run well. Use it as a reference and focus on improving your own baseline.

#### How should rework be treated?

**Answer:** Units that needed rework are not first-pass good units, so they should reduce quality. Counting them as good hides a real loss. Track rework separately so you can see the true quality factor.

## Search terms

oee calculator, overall equipment effectiveness formula, oee availability performance quality, oracle fusion work center oee, oee from production reporting, downtime impact on oee, ideal cycle time oee, world class oee benchmark

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