Hundreds of downtimes stuck under "No Reason Assigned": how do we clear them?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • ProcessPilot
    Junior Member
    • 11.08.2025
    • 13

    #1

    Hundreds of downtimes stuck under "No Reason Assigned": how do we clear them?

    We've been running Proveris OEE web for about a month. On the DOWNTIMES page, the "No Reason Assigned" tab now has more than 300 records. Most are short stops on the night shift when there is only one operator for three machines and nobody has time to go to the kiosk.
    Management wants the Pareto of downtime causes, but with so many unclassified records the chart is useless. Can I assign reasons to old records from the office, or does it have to be the operator on the kiosk? And is there anything we can do so the list doesn't fill up again?
  • Technical Support
    Senior Member
    • 11.08.2025
    • 105

    #2
    Yes, reasons can be assigned later, both from the kiosk and from the web interface, so you can clean up the backlog from the office.
    Clearing the backlog
    1. Open DOWNTIMES and go to the No Reason Assigned tab.
    2. Click Assign Reason on a record. You'll pick the Equipment first, then the cause, and optionally add an explanation.
    3. Once saved, the record moves to Unplanned Downtimes or Planned Downtimes depending on the cause category.
    If the equipment step shows "No equipment is defined for this machine.", define the equipment and its causes on the EQUIPMENT page first. Causes are offered through the equipment they belong to.
    For a backlog of 300, I'd suggest sitting down with the night-shift operator or supervisor for the oldest records. Guessing reasons in the office gives you a nice-looking Pareto that is wrong.
    Preventing it from filling up again
    - On the kiosk dashboard, operators see "Waiting for the downtime reason" and the notification "{n} downtimes awaiting approval". Make clearing this list part of the shift handover.
    - In Shift Monitoring, supervisors can see each downtime with the "No reason" label and "Approved By" column for the shift, which makes follow-up easy.
    - Look at the shortest stops. If most unclassified records are very short, they are probably micro-stops. Discuss with your team whether those should be treated as performance loss rather than asking operators to classify each one.
    Documentation: https://greensoft.ai/documentation/p...ser-interface/

    Comment

    Working...