- In = Total quantity unit can be created.
- Waiting = Quantity of unit that are queued at the current operation and can be transact at current operation.
- Out = Quantity of unit that had passed current operation.
- Rework = Quantity of unit that is queued at current operation that require to be rework.
- Debug/Review = Quantity of unit that is queue at Debug that require to be debug (after debug it will queue to rework).
- NCM = Quantity of unit that is queue at current operation that had been send to NCM(Non-Conformance) to be scrap or send to customer.
- Disposed = Quantity of unit that is queue at current operation that had been scrapped or disposed.
3. Job Booking / Clocking In [Production > Job Booking]
User is required to clock in by scanning the Barcode at Route Card (refer to figure 3.1)
Figure 3.1 show the example route card, user will scan the one of the barcode depending to the operation that they will like to clock in.
4. After clocking in the first operation, system will auto assign1000 quantities to first operation at In and Waiting depending on the Work Order Quantity. (User is encourage to keep on track WIP Inquiry when performing any transactions)
5. After clocking in user will be redirect to page below. Notice that there are 1000 quantities for In and 1000 for Waiting and a button Finish a Quantity will be enabled.
6. User can access to the labour tracking detail of today for current user by clicking on the Today button.
6.1 A labour hour tab will pop up, noticed that the DatetimeEnd is blank when user had clock in for an operation.(User is encourage to keep on track Labour Hour when performing any transactions)
7.0 Finish a Quantity
When user had clock in into an operation with 0 quantity at In and Waiting, user will not be able to click on the Finish a Quantity. (refer to figure 7.0.1)
Figure above show figure 7.0.1
7.1 User will able to finish a quantity when there are units are In and Waiting. Noticed that the Finish a Quantity button had been enabled.
7.2 User is able to enter the quantity for current operation when clicking on Finish a Quantity button.
(this tab may look slightly different depending on the enforcement type at route setup)
7.3 After submitting the quantity, Waiting will reduce by 10 and In will increase by 10 (if 10 is entered at 7.2)
7.3.1 At labour hour the Quantity Passed had been recorded and Datetime End had also being inserted with an extra row at below for the same operation.
7.3.2 At WIP Inquiry, for operation Assembly Waiting will decrease with 10 and Out increase by 10.
For the next operation, In and Waiting will both increase by 10 due to the quantity pass at first operation.
7.4 When clocking in the next operation user can start to transact as there are units in In and Waiting due to the transaction at 7.3
7.5 When user trying to finish quantity noticed that user can enter for result Pass or Fail (refer to figure 7.5.1) due to the route setup for the second operation is Enforced Pass (refer to figure 7.5.2)
Figure above show figure 7.5.1
Figure above show figure 7.5.2
7.5.1 If user pass 5 quantity
7.5.2 WIP Inquiry
7.5.3 Labour hour
7.5.4 If user fail an quantity
7.5.5 WIP Inquiry
Noticed that the In, Waiting and Out remained while quantity for Debug/Review will be increased depending on the quantity inserted at 7.5.4 (For operation with operation sub type test, the unit will be queue at Debug when fail. For operation with operation sub type inspection, the unit will be queue at Rework when fail)
7.5.6 Labour Hour
7.5.7 For unit that is queue at Debug/Review, user can perform debug at Production > Rework > Debug and upon finishing debug, the unit will queue to Rework
7.5.8 WIP Inquiry
Noticed that the quantity had been shifted from Debug/Review to Rework.
7.5.9 Labour hour
Noticed that a new row had been created with Labour Type Rework, with 0 Quantity Passed (at 6.0.10 the quantity of debug of rework will be recorded down here) with an update DatetimeEnd.
7.5.10 NCM unit not found (Please take not that NCM will not have labour tracking)
User is only able to send an unit to NCM when the unit is queue at Debug or Rework else an warning message will pop up "No Units Submit for Processing"
Currently for operation Assembly there are 0 unit queue at Debug or Rework therefore no unit is being found.
7.5.11 NCM (Please take not that NCM will not have labour tracking)
User will be able to successfully send an unit to NCM when there are unit queued at Rework or Debug.
7.5.12 After successfully sending an unit to NCM
WIP Inquiry
The quantity for Waiting will decrease and NCM will increase based on the quantity inserted at 7.5.11
7.5.13 Non-Conformance Disposition not enough quantity to transact
User will unable to dispose an unit when there are no unit queued at NCM
7.5.14 Non-conformance Disposition
User is able to scrap the unit when there are unit queued at NCM.
WIP Inquiry:
The quantity of NCM will decrease while the quantity of Disposed will increase based on the quantity that user had inserted at previous step.
7.5.15 When user had an unit that are successfully debugged and reworked or reworked only, the unit will queue at Retest