Every stop found, and the reason behind it

A stop starts when the run signal goes off and ends when it comes back on. Kealink only reports what it saw: if the readings stopped arriving, that is shown as no data, not as a stop that lasted until the connection came back.

• Blips shorter than a time you choose, say 30 seconds, are ignored.
• Stops up to a few minutes are coded Short stop on their own.
• Longer stops wait for a person to say what happened.

Each machine can have its own screen, opened from a private link on a tablet or phone kept at the machine, with no sign in. The operator picks a reason for a stop from your list and can record scrap. Managers can do the same from the machine page or the day view.

Mark reasons such as Changeover or Cleaning as planned, and they are kept out of availability.

For any shift or date: time running, short stops, each reason with its total time and number of stops, and what is still uncoded. The biggest losses are at the top, which is usually where the fix is.

Download the stops, or every reading for any range of dates, as a spreadsheet that opens straight in Excel. Scheduled reports can arrive by email as a PDF.