L2 - R4.6 Cup Rinser Sink Overflow / Drainage Clog

Modified on Mon, 26 May at 10:31 PM

According to the problem analysis result done by CCA, you can directly begin the subsequent troubleshooting process from the corresponding potential root cause. 


STEP 1 - Pour hot water into the cup rinser sink to flush the drainage line. Then, verify if the drainage efficiency meet the required standard (1800ml/20sec).


  • Result 1 - Drain efficiency meets the required standard.
    Issue closed. Train the customer to flush the drainage with hot water every day. 
    (Root cause: Drainage clog)

  • Result 2 - Still bad drain efficiency.   
    Start STEP 2.




STEP 2 - Disassemble the internal drainage tubes and verify if the inner surfaces of the drainage tube can be thoroughly cleaned.


  • Result 1 - Can be thoroughly cleaned.
    Start STEP 4.

  • Result 2 - Heavy deposits.   
    Start STEP 3.



STEP 3 - Replace the drainage tubes (see internal drainage tube replacement SOP here), and follow the drain efficiency test procedure to verify if the drainage efficiency meets the required standard (1800ml/20sec)


  • Result 1 - Drain efficiency meets the required standard.
    Issue closed. Train the customer to flush the drainage with hot water every day. 
    (Root cause: Drainage clog)

  • Result 2 - Still bad drain efficiency.   
    Escalate to PSE.



STEP 4 - Clean the external & internal drainage tubes, and follow the drain efficiency test procedure to verify if the drainage efficiency meets the required standard (1800ml/20sec)


  • Result 1 - Drain efficiency meets the required standard.
    Issue closed. Train the customer to flush the drainage with hot water every day. 
    (Root cause: Drainage clog)

  • Result 2 - Still bad drain efficiency.   
    Escalate to PSE.




Return to index

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article