Endline Quality App

Introduction

This is an android application that is used for QC (Quality Checking) in the Endline process. The application is used to check the quality of the product before it is moved to packing.

Features

1. Login

The app utilizes KeyCloak for authentication. The user is required to login to the app using their credentials. The app requires the user to have the following roles:

1. sqms:endline:get
2. sqms:fault:get
3. sqms:endline:update
4. order:sale_order:get
5. spts:cut_job:get
6. spts:cut_report:get

2. Configuring Access (Company, Branch, Line & Section)

The users are assigned companies, branches, lines & sections from KeyCloak via the access user attribute. If the user is assigned to a single line & section, the app will automatically select the line & section for the user. If the user is assigned to multiple lines & sections, the user will be prompted to select the company, the company’s branch, one of the lines in the branch, and a section.

Note

The access details are only fetched at the time of login. If the user access attribute is updated after logging in, the user will have to logout and login again to see the updated access details.

2.1 KeyCloak User Attributes

The access user attribute is used to assign lines & sections to the user.

The Initial Setup for KeyCloak guide details how to set up this user attribute on a new KeyCloak instance.

3. Dashboard

Endline Quality App has a dashboard that shows today’s quality status report for the selected line & section. The dashboard shows the following information:

1. Checked Pieces - The number of pieces that have been checked/cleared today.
2. Rework Pieces - The number of pieces that have been sent for rework today.
3. Rejected Pieces - The number of pieces that have been rejected today.
4. Top Faults - The top 3 most commonly occurring faults today.
5. DHU - Defects per Hundred Units % for today.

4. Quality Check

4.1 Scanning NFC Tag or Manual Selection

The app works in production by utilizing NFC (Near Field Communication) tags. The user is required to scan the NFC tag of type group to start the quality check. The app will fetch the associated details such as Work Order, Cut Job, Cut Report, Bundle, and the Operations that have been performed on the bundle.

Additionally to allow testing, there are also options to select a group by manually selecting each of the details from dropdowns.

4.2 Operations

The app will load & show the operations that have been performed on the selected/scanned bundle in the Operations section.

4.2.1 Piece Selection

The app automatically selects the first piece in the list. The user of the app will not deal directly with the list of pieces.

If the pieces are cleared or rejected, then an appropriate error message will be shown to the user as QC has already been done on the piece.

4.2.2 Clearing/Checking Pieces

If no issue is found with the piece, the user can clear the piece by clicking the Clear button or by scanning a different bundle group NFC tag.

The piece will be marked as cleared in both cases, if the button was clicked then user is redirected to the previous screen to scan or select a different bundle group NFC tag, otherwise the app will automatically load the details & operations of the scanned NFC tag.

4.2.3 Rejecting/Reworking Pieces

To reject or rework piece, faults are added against operations. The user can add faults on any operation by clicking on it. This redirects to Faults screen with the chosen operation and the selected piece.

4.3 Pieces

This is just a display only page designed to allow some testing/debugging help to see the pieces that are in the bundle group.

The piece cards are color coded to show the status of the piece. The colors are as follows:

blue

Unchecked

green

Cleared

red

Rejected

yellow

Reworked

4.4 Faults

This screen lists all the faults, with option to pin any of them to the top of the list. The faults are fetched once and refreshed on every page load but they mostly remain the same unless the data is refreshed from the backend.

The user taps on a fault to add it on the selected operation. The modal prompts the input of FaultCount alongside an option to specify the reason for rejection in more detail.

The user can add any number of faults, once done they can proceed the piece to either Rework or Reject submission

4.5 Submission

This is the final screen, it lists the pieces that have been selected. On each piece the list of operations alongside the faults that were added on them are shown.

There is also option to remove any piece that was added by mistake. The background color of the piece card is also updated to show the status of the piece.

The status is color coded as follows:

red

Reject

yellow

Rework

The user has to select pieces to be submitted, once selected the page sets the Status of the group being submitted (either Rework or Reject). Different Statuses cannot be submitted together and a warning is shown if the user tries to do so.

The user can then submit the pieces by scanning a new NFC tag, the selected pieces that are being submitted are removed from the previous group and a new group is created with the selected pieces. The Group ID is then linked with the scanned NFC tag.

If there are no more pieces left that had faults added on them, then all remaining pieces are automatically cleared and the user is redirected to the dashboard.

5. Reports

Each of the panels on the dashboard is clickable and will take the user to the detailed last 7 days report for that particular panel. These are

1. Checked Pieces
   1. A graph for the last 7 days showing the number of checked pieces per day
   2. A table showing the details of the checked pieces for the last 7 days
2. Rework Pieces
   1. A graph for the last 7 days showing the number of rework pieces per day
   2. A table showing the details of the rework pieces for the last 7 days
3. Rejected Pieces
   1. A graph for the last 7 days showing the number of rejected pieces per day
   2. A table showing the details of the rejected pieces for the last 7 days
4. DHU
   1. In DHU, there is a breakdown of DHU per day for the last 7 days
   2. Also for the last days, the DHU is also broken down by Work Order