Definition of Idle Time

The cycle of requesting an idle time

1. The employee makes a request for idle time using his Garment IO Device.
   
2. The supervisor gets notified on the supervisor mobile application

the supervisor would only get notified with the idle time requests happened in the section that he is responsible for. For more information on how to assign to specific users specific sections, check this article How to add users? 

1. The supervisor reviews the request and takes action 

1. The worker then returns back to his job after the action is taken. 
   

Actions that could be taken by the Supervisor

1. Accept the idle request: User can add the reason behind the employee being idle and accept the idle request. 
   
2. Reject the idle request: User can reject the idle request and it can be for different reasons.  One possible reason is that the production employee might be misusing the idle time to increase their efficiency, even though they were not truly idle during that period.

Before taking an action, the factory have to ensure that they have added all stoppage reasons that can happen into our system so they can select the desired reason from the dropdown list. You can check this article Idle Time Reasons Management to know how to add idle reasons to the system. 

1. The first page is the Supervisor app, which is a mobile application specifically designed for supervisors working on the production floor. This app prioritizes a user-friendly interface and enables supervisors to quickly take actions regarding the employees within their assigned scope. It focuses on real-time data and does not provide historical information.
2. The second page is the Employee idle times page, accessible through a PC web page. This page displays multiple employees and allows users to perform bulk actions on employees throughout the factory. Users have the flexibility to select the specific time range for which they want to take action.
   

Taking actions through the supervisor app 

For users to open the supervisor app using their mobile device from the sidebar menu > Supervision > Supervisor Dashboard, or by clicking on the Dashboard button at the bottom in the center. Then they can select the specific section assigned to them at the top of the page.

Users need to scroll down to the "Alerts" section and check the idle time cards. 

this card shows the workers who requested idle time. Additionally, it displays the duration since the request was made. The supervisor has the option to approve or reject the request and can also add a reason for the idle time request.

1. If the duration is in black, this means that the request is still open
   
2. If it is without a reason, the moderator can reject or add a reason.
   
3. If there is a reason previously added, the supervisor can end the request with acceptance. But he cannot refuse a request if he already added a reason for it.
   
4. If the duration is in red, this means that the request has already been ended by the worker himself, and it is pending approval and remains for the supervisor to accept or reject this request.

users can click on the employee code to see the full name of the worker

Taking actions through the employee idle page 

 Users can:

1. Accept/reject a single idle request
   
1. User can click on the idle request from the table provided, another page will open requesting the user to take an action for this idle request
   

1. Reject/Accept a group of selected requests 
   
1. user should select the multiple idle requests and take one action at once. 

NOTE: The bulk actions override any action that was taken on the idle request before. 

Status of Idle time requests

• When a worker requests idle time it appears on the system with its status. The status can be
  
• Open
  

• Pending

• Accepted 

• Rejected
  

• Open Idle time request: Means that the worker has requested idle time using the Garment IO device. However, the supervisor didn’t review it yet and the employee is still idle till now.

• Pending idle time request: Means the worker has requested idle time using the Garment IO device, and it’s awaiting the approval of the supervisor. However, the request has ended awhile ago. The request can be ended by the following cases: 

• The worker ends it by himself using the Garment IO device when pieces are in feeding again and he can continue production.

• The worker starts working again and recording beats on the Garment IO device, so the device itself ends the request of the idle time.

• The worker logs off the machine, so automatically the device ends the idle time request.

• Note: even if the worker ended the idle time request it would still appear as pending approval to be accepted or not.

• Accepted Idle time request: Means that the supervisor reviewed the request of the worker and accepted his request, even if the worker has already ended his request. Plus, they have added a reason behind this idle request.

• Rejected idle time request: Means that the supervisor reviewed the request made by the worker and rejected it. In this case there are different actions that can be taken to reject the request.
  

Note: if the worker takes a break during his requests idle time, the time of the break is going to be deducted from the idle time. 

Analyzing idle reasons 

Once all necessary measures have been taken, production managers recognize the significance of analyzing the underlying causes behind decreased productivity. By identifying the main issues, they can effectively address and resolve these factors, ultimately enhancing employee productivity and increasing throughput. In order to know how ti use the idle time reasons analysis page check this article Idle Time Reasons Analysis