Skip to main content

OEE Chart Reports

note

This module is designed to generate comprehensive OEE Chart Reports using advanced filters and interactive charts. It enables users to analyze Overall Equipment Effectiveness (OEE) and production data with accuracy based on selected criteria.

Interactive OEE Calculator​

Enter your shift figures below to work out OEE instantly. In plain terms, OEE is the share of your shift that actually made good, sellable parts. The boxes are pre-filled with a worked example (480-minute shift, 30-minute break, 20 minutes to make each part, 20 parts made, 15 good). Nothing is saved — it all runs live in your browser.

✓ Time adds upBreak 30 + Unplanned 0 + Running 450 = 480 min (Shift 480)
Where your shift time went
Good production 300 minSlow running or no data 50 minMaking scrap 100 minPlanned break 30 min

Only 300 of 480 minutes actually made good, sellable parts. Everything else — breaks, stoppages, slow running and scrap — is lost time.

AvailabilityHow much of the planned time the line was really running
100.0%
PerformanceHow fast it ran compared with its best possible speed
88.9%
QualityHow many parts were good out of all parts made
75.0%
Standard method
Breaks don’t count against you
66.7%
Good — typical factory range
Availability 100.0% × Performance 88.9% × Quality 75.0%
The usual way to report OEE. Planned breaks are set aside, so you’re only judged on time you meant to run.
Strict method
Breaks count as lost time
62.5%
Availability 93.8% × Performance 88.9% × Quality 75.0%
Counts every non-producing minute, including planned breaks. Always lower than the standard method.
Rough guide: 85%+ is world-class, around 60% is typical for many factories, and under 40% usually means big, fixable losses.

What the inputs mean

InputIn plain words
Shift TimeTotal time the line is scheduled to be open
Planned BreakLunch, changeover, planned maintenance — time you never meant to run
Unplanned StoppageMachine faults and unexpected stops that steal running time
Ideal Time per PartFastest time to make one good part at full speed
Parts MadeEvery part produced, good and bad
Good PartsParts that passed quality and can be sold
Two ways to handle planned breaks

Planned breaks (lunch, changeover, maintenance) can be treated two valid ways. Pick one and use it everywhere so your numbers stay comparable.

  • Standard method (breaks don’t count against you): the break is set aside, so you’re only judged on time you meant to run. This gives the higher, textbook OEE.
  • Strict method (breaks count as lost time): the break stays in and counts as downtime, giving the lower OEE.

OEE = Availability × Performance × Quality. Availability = how much planned time the line really ran; Performance = how fast it ran versus full speed; Quality = good parts ÷ parts made. Unplanned stoppages always count as lost time in both methods.

This matches the DMeX dashboard formula

The DMeX formula OEE = Production ÷ (Available − Idle) (Section 4) gives the same answer as the Standard method above — because Production = Ideal Time per Part × Good (approved) parts. For the example: 20 × 15 = 300 minutes of good output ÷ (480 − 30) = 66.7 %. The three-factor form just splits that same number into Availability, Performance, and Quality.

1. Generate OEE Chart Reports​

Step-by-Step User Guide​

1.1 Access the OEE Chart Report Section​

  1. Open the main menu
  2. Navigate to Production and Quality
  3. Click Reports
  4. Select Info Graphics – OEE Charts Reports

1.2 Understanding the Search Fields​

note

All fields marked with (*) are mandatory.

FieldDescription
Date RangeSelect the reporting period (Last 7 Days, This Month, Custom)
CategoryChoose Machine or Operator
Part StatusFilter valid production records
Report TypeSelect the required report using the carousel

1.3 Field Validations​

  • All mandatory fields must be selected
  • Date Range defaults to the current system date
  • Dropdown values are predefined to avoid incorrect input
  • If no matching data exists, the system displays No Data Available

1.4 Generate the Report​

  1. Select required filters
  2. Choose a report from the carousel
  3. Chart updates automatically
  4. Hover on the chart to view details
  5. Click Clear to reset filters

1.5 No Data Found Message​

If no data matches the selected filters:

No Data Available

Recommended actions:

  • Verify date range
  • Check machine or operator selection
  • Confirm production data exists for the selected period

2. Common Rules Used Across All Reports​

These rules apply to all OEE and Production reports.

2.1 Task Types Considered​

Only the following task types are included:

  • TK – Task type
  • BLK – Bulk entry
  • HBLK – Hourly entry
  • ASM – Assembly process

2.2 Part Status Considered​

Only valid production records are included:

  • APV – Approved
  • CAPRVD – Conditional Approved
  • CRJ – Casting Rejection
  • HI – Hold for Inspection
  • HR – Hold for Research

2.3 Shift-Based Day Logic​

All reports use shift-based day calculation.

Production Day = Operate Date + Shift Interval

This ensures correct handling of:

  • Night shifts
  • Shifts crossing midnight

2.4 Scheduled Maintenance (Idle Time)​

Idle time is identified dynamically.

Only idle reasons with labelCode = SM are treated as Scheduled Maintenance.

tip

Idle reasons are configuration-driven. No hardcoding is used.

2.5 Control Task Idle Time Reflection​

Idle time entered through the Control Task screen is also reflected in the OEE Chart Reports.

  • If idle time is added in Control Task, the same idle duration becomes part of the report data for the relevant machine and reporting period.
  • If that idle reason is configured with labelCode = SM, it is treated as Scheduled Maintenance Idle Time in OEE calculations.
  • If the idle reason uses any other label code, it is still reflected in report calculations that include idle time, but it is not treated as Scheduled Maintenance.
note

This means Control Task idle entries are reportable in OEE charts, while the idle reason configuration decides how that time is classified in the final calculation.

3. Common Time Definitions (Current)​

Available Time
  • Machine/Day/Month reports: total selected range minutes (24/7 basis), with idle shown separately in breakup tables.
  • Operator reports (DMeX): sum of operator shift durations from OperatorShiftLog.
  • Operator reports (IoT): sum of operator shift durations from OperatorShiftPlanning.
Production Time
  • For machine/day/month reports:
    Production = ((Cycle Time + Handle Time) / 60) × Quantity (Quantity = good/approved parts)
  • For operator production details popup:
    • Full Cycle Time = controltask process cycle time
    • Operator Split Time = partExecutionSplit time for that operator
    • Operator Effective Time = split time if split exists, else full cycle time
note

PartExecutionSplit logic is applied only in Operator-wise OEE flows (Operator Wise OEE and Operator Wise With Idle Time).
It is not applied to machine/day/month OEE detail popups.

note

PartExecutionSplit-based operator time is considered only when the linked controltask entry passes valid part-status rules.

For operator split-time:

  • Split time is counted only for approved work.
  • The linked controltask must be:
    • Approved (APV) or
    • Conditional Approved (CAPRVD)

4. Report Formulas​

Below are the active formulas used in the dashboard.

Purpose: Daily machine efficiency

  • Available = total range minutes for that day
  • Idle = scheduled maintenance idle minutes
  • Production = cycle-based production time
  • OEE (%) = (Production + Idle) ÷ Available × 100

5. How to Interpret the Results​

ObservationMeaning
High OEEEfficient utilization
Low OEEDowntime, maintenance, or low output
Operator With Idle OEE > Operator OEEMore idle involvement
Zero ProductionNo execution, maintenance, or no shift

6. Final Notes​

info

If values differ between reports, always verify:

  • Which formula family is used: operator vs machine/day/month
  • Whether idle time is part of denominator logic
  • Whether operator split-time was applied (operator reports only)

All reports are:

  • Shift-aware
  • Maintenance-aware
  • Configuration-driven
  • Fully aligned with Grafana

For further assistance, please contact the DMeX Support Team.