← All use cases

The story of a downtime

From the moment a machine stops until the loss shows in the report.

Today

  1. A machine stops and nobody may notice.
  2. The operator goes to find maintenance.
  3. Reason and duration go on a form later.
  4. The loss is estimated at month end.

With KesoFloor

  1. The machine signal opens the downtime by itself.
  2. The operator picks the reason on the terminal.
  3. An andon call reaches the right team.
  4. The loss shows on the OEE screen right away.

Drag the slider to compare.

Step by step

  1. 1

    The machine stops

    The status changes on the machine board at once; the person responsible sees which machine stopped.

    The machine stops The machine stops
  2. 2

    The operator picks the reason

    A few taps on the terminal record the downtime reason.

    The operator picks the reason The operator picks the reason
  3. 3

    The right team is called

    An andon call opens; who answered and how long it took are recorded.

    The right team is called The right team is called
  4. 4

    The loss becomes visible

    The downtime shows in the loss analysis with its reason; the biggest loss stands out.

    The loss becomes visible The loss becomes visible

Screens show sample data.

Let’s see it on your floor.

Calculate your losses, or talk through your own situation with us.

Message us on WhatsApp