One honest OEE per line
See how well each line is really running, and why it stops. Counts and stops come straight from the machines, so every loss is recorded without anyone writing it down.
OEE is calculated by hand after the shift, missing data is quietly counted as running, and nobody agrees on the number.
Built and tested in software, not yet proven on a plant line. Available to pilot plants.
Line Performance, step by step
- States come from the machineGorad Connect reads running and stopped straight from the PLC. Nobody fills in a sheet.
- Every stop gets a reasonOperators pick a reason on the tablet. A stop nobody answered stays "unspecified" and goes to review.
- Missing data stays missingWhen the readings stop, that time is "no data". It is never counted as running.
- One honest OEEAvailability × performance × quality, from those states, the part counts and the ideal cycle time.
Step 1 of 4 · Example values
What Line Performance does
Live line view
Machine states and Andon calls as they happen, on a screen, a tablet or a TV board.
Andon
Calls from a PLC button or the tablet, with escalation when nobody responds.
Downtime with reasons
Every stop gets a reason. Stops nobody answered become "unspecified" and go to a review queue.
OEE with drill-down
Availability, performance and quality per line and shift, with ideal cycle times per part.
Governed policies
Plant policies are versioned. Changing them or recomputing a past shift needs a reason and re-authentication.
Ready to share
Shift report in PDF and Excel.
What changes with Line Performance
Real numbers, not guesses
States and counts come from the machine, not from a sheet filled in at the end of the shift.
See losses as they happen
Live line view and Andon calls on screens, tablets and TV boards.
A reason for every stop
Stops get a reason; unanswered ones go to a review queue.
Honest about missing data
Time without readings is shown as “no data”, never counted as running.
Shift reports, done
A shift report in PDF and Excel at the end of every shift.
Built to stay honest
These rules are part of the app, not settings.
- Missing or bad data is "no data", never counted as running.
- A missing ideal cycle makes the result incomplete, never 0 % or 100 %.
- Each line has one quality source, so rejects are never counted twice.
- Line Performance never writes to a PLC.
Works with
- Same login, roles and audit trail as every Gorad app
- Runs inside your plant, with offline licensing
- OEE
- Overall equipment effectiveness: how much good output a machine makes compared with what it could make. Availability × performance × quality.
- Availability
- The share of planned time the machine was actually running.
- Performance
- How fast the machine ran compared with its ideal speed while it was running.
- Andon
- A signal, such as a button or a light, that calls for help when there is a problem on the line.
- Ideal cycle time
- The fastest time a machine can make one part. OEE performance is measured against it.
- Downtime
- Time a machine was stopped when it should have been running.
About Line Performance
Where does the data come from?
Machine states and counts come from your PLCs through Gorad Connect. Quality comes from good and reject counts, or from Gorad Vision verdicts.
What if the readings stop for a while?
That time is shown as “no data”. It is never counted as running, so OEE is never flattered.
What if we don’t know the ideal cycle time?
The result is marked incomplete instead of showing 0 % or 100 %. You can set ideal cycle times per machine and per part.
Does it control the machine?
No. Line Performance never writes to a PLC.
See Line Performance with your data
Tell us how you handle this today, and we will show you how Gorad Line Performance would fit.