How to Run the OEE Report in EDGEBIC

The OEE report in EDGEBIC by User Solutions is in the Reports hub under Executive / KPI: it takes a date range and returns availability, performance, quality and overall equipment effectiveness for every work center. It is the one report that tells you not just whether a machine was busy, but whether the time it spent busy was worth anything. Here is how to run it and read each factor to the action it implies.

For the catalog this sits in, see EDGEBIC reports explained. For the concept itself, overall equipment effectiveness covers the arithmetic in general terms. Every task in this library is mapped on the EDGEBIC how-to hub.

Before You Start

• Work centers have shifts assigned, since availability measures logged hours against what the calendar says was available.
• Actual hours are being logged, or availability reads near zero on stations that ran all week.
• Kiosk punches record good, scrap and rework pieces. Without them, quality and therefore OEE read n/a.
• Routing steps carry pieces per unit and required hours, or performance falls back to an hours-based approximation.

Step 1: Open It and Choose a Window

Open Reports and click OEE in the Executive / KPI group. Set From and To, then OK.

Pick the window to match the question. A single day answers "what happened on Tuesday". A full week smooths out one bad shift. A month is the right grain for a trend conversation, and comparing two consecutive months is how you spot a station drifting downward.

Step 2: Read the Three Factors, Then the Product

Multiplying is what makes OEE unforgiving. Three respectable factors of 90, 95 and 98 percent give roughly 84%. That is the arithmetic behind the world-class benchmark of above 85%, and it is why chasing the composite number without reading its parts leads nowhere.

Rows arrive sorted with computable OEE first and the n/a rows collected at the bottom, so the readable data is at the top of the grid.

Step 3: Chase a Low Availability

Availability is the factor that moves most in a job shop, and it has two honest causes and one data cause.

1. Confirm the work center has its shifts assigned. A station with no shift assignment falls back to a standard assumption, which can overstate available hours on a partial-shift station.
2. Confirm the instance count. A station configured with fewer instances than it physically has distorts the available-hours side of the fraction.
3. Confirm actuals are being logged for the window. Availability compares logged hours against available hours, so a shop that does not punch will show a low availability on a machine that never stopped.

Cross-check the same station and window in the work center utilization report, which computes available hours from the same shift calendars and shows a per-day picture.

Step 4: Chase a Low Performance

Performance needs the routing to carry a cycle time. When both the pieces per unit and the required hours are present on the steps routed to that station, the report computes theoretical pieces and compares them with what was actually made. When either is missing, it falls back to comparing actual hours against planned hours, which is a much blunter reading.

So the first check on a low performance figure is not the machine. It is the routing. Open the steps routed to that work center and confirm the cycle-time fields are filled. If the station was imported with an efficiency of zero, re-import it with a real value, because there is no editor field for it on the work center dialog.

Step 5: Read Quality Only When Punches Exist

Quality divides good pieces by the sum of good, scrap and rework. All three come from shop-floor punches, so the column is honest about absence: no punches, no quality, and therefore no OEE. That n/a is deliberate, and it is a better answer than a fabricated 100%.

If quality is blank across the board, the fix is adoption rather than configuration. Logging good, scrap and rework at the point of work is covered in how to log actual hours and pieces.

Step 6: Export and Compare Periods

Click Export to Excel. OEE is most useful as a comparison, so run the previous period, export, run the current period, export, and put the two side by side. Stations whose OEE fell by more than a few points are your investigation list.

One condition on that comparison: it is only valid if the routing was the same in both windows. A cycle time edited between the two periods changes the performance denominator, and the two numbers stop being comparable.

What Changes When You Run It

Nothing. The report is read-only and queries fresh each time it opens.

What changes the score is the work behind it: assigning shifts, correcting instance counts, filling cycle times on routings, and getting punches logged. Each of those moves exactly one factor, which is why reading the factors separately matters.

How to Check It Worked

Re-run the same window after a fix and watch the specific factor you targeted. Filling routing cycle times should move performance and leave availability alone. Getting punches submitted should populate quality and lift availability at the same time, because both draw on logged work. If the composite number moved but no single factor did, you changed the window rather than the plant.

Common Mistakes

• Reading n/a as a broken report. It means quality could not be computed from the data available. It is an absence, not an error.
• Quoting OEE without the factors. Two stations at 62% can need completely different responses.
• Comparing across a routing change. Confirm the routing was stable across both windows before comparing two periods.
• Blaming the machine for a data gap. Low availability with no punches in the window is a logging finding, not a maintenance finding.

See how work center capacity and effectiveness fit into the wider plan on the EDGEBIC product page.