Kiosk: EZ Pass Revision: Remove the Bar Code on 2/21/24.

Modified on Tue, 14 May at 11:18 AM

Due to Corrective Action# 7701384, a change has been made to the EZ Pass Sheets. These changes were made in TIWOs 89362 & 89363 in Genesis Release 8.1.6 on February 21, 2024.

 

For Corrective Action 7701384,  the Bar Code from the EZ Pass has been removed. If a driver checks in at the Kiosk, and provides the wrong information or a door is not assigned, then the driver will receive an EZ Pass to go see PSI Dispatch and will list the reasons why on the EZ Pass. The driver will then be required to go the PSI shipping office to clear up the issues and verify the correct information. If everything is correct, the PSI Dispatcher will check in the driver correctly and then provide the Check In Sheet to the driver.


During the Checkout process on the Kiosk, if the driver enters the incorrect information (scanned wrong tag or chooses the incorrect city), a hard stop will be put on the Check Out process on the Kiosk and tells the driver to go to the shipping office. If the driver tries to check out again, the message will continue to pop up. Prior to this release, the driver could just reset the process until they selected the correct information.

 

In addition to this, when the driver selects the wrong information during the check out process, an email alert (alert id# 229) will alert associates in to the plant specific Kiosk Alert Group that a carrier is attempting to check out with incorrect information. This alert should signal to PSI associates to find the driver so that they can stop the driver from leaving without the bills or going to the incorrect city.

During the Checkout Process, if an alert email is fired for a driver entering the wrong check out information, PSI Associates can check to see if the email was actually sent and can see who all receives the alert.

 
















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

Feedback sent

We appreciate your effort and will try to fix the article