Some stages are not performed by a single operator, but rather by an entire team. This update allows the system to measure productivity in a way that reflects how your factory actually operates.

Production Management | Multi-Worker Login on the Same Garment IO Device

Previously, measuring productivity for grouped stages required each worker to log in on a separate device, even though they were actually working together as a team on a single task.

This has now changed.

Multiple workers can now log into the same Garment IO device simultaneously. This enables factories operating with grouped-stage workflows to track team productivity through a single device with all workers and stages assigned to it, while the system still calculates and records each worker’s individual data in the background.

How Does the System Work?

1. Machine Type Setup

From the machine type settings, create a new machine type dedicated to assembly stages and assign it a name such as "Assembly Department Machine", then set its fee and define the maximum number of workers (Worker Limit) allowed to log in to the machine simultaneously. This option allows workers to log in together on the same device while the system calculates idle time, efficiency, productivity, and all scanned bundle details separately for each worker.

Machine Type Setup

2. Linking the Stage Group to the Machine

When creating a style category containing stages grouped together as a single stage, such as assembly stages, the newly created machine type is linked to this group, and the option "Team-Based" is selected so that it is identified as a stage group requiring multiple workers at the same time.

Linking the Stage Group to the Machine

3. Employees Login on the Machine

Machines that have been configured to allow multiple workers to log in simultaneously will appear in the Machines page under the Supervision section accordingly, while machines without this permission will continue to appear as before: only one worker can log in.

Employees Login on the Machine

4. Login Override When Reaching Maximum Capacity

If the "Override Login" option is enabled and the limit is set to four workers, then if a fifth worker attempts to log in, the first worker who logged in will automatically be logged out. If another worker logs in afterward, the second worker will be logged out in sequence, and so on, as if the workers are in a queue where those who entered first leave first.

If this option is not enabled, once the number of logged-in workers reaches the maximum allowed limit, any new worker attempting to log in will be rejected so that the predefined limit in the machine type settings is not exceeded.

5. Garment IO Device

Assigning stages to the device: The stage assignment rules differ as follows:

- Device without multi-worker login permission:

1. One worker, individual process: Production is recorded and assigned to the same worker, which is the normal standard case. However, attempting to assign team-based stages to this device will not be accepted; the device only accepts individual processes.
   

- Device with multi-worker login permission:

1. Multiple workers, team-based stage group: Production is recorded for all workers together, and team-based stages can be assigned to this device.
2. Multiple workers, team-based stage group, individual process: The device accepts both team-based and individual processes; however, production recording in this case applies only to the team-based stage group, while the individual process production will not be counted even if it is assigned to the same device.
3. One worker, team-based stage group, individual process: Production in this case is recorded for both the team-based stage group and the individual process for that worker.

Device Screen

When multiple workers log in simultaneously on a device configured to accept this type of login, the screen displays the name of the first worker who logged in along with the number of additional workers beside it.

Garment IO Device Screen

6. Working with and without Internet Connection

When connected to the Internet (Online):

1. There is currently no issue, and the system handles the process normally by recording production for all workers simultaneously without any obstacles.

When the connection is lost (Offline):

1. Any production operation performed allows the device to record production for all workers once the connection is restored.
2. If a logout occurs during this period, only the first worker who logged in will be logged out, while the remaining workers will remain logged in because the device cannot recognize them while offline. In this case, the supervisor must log workers in and out directly through the system or mobile application so the system can recognize worker activity correctly and avoid any issues.
3. If a new worker logs in to the same device while offline, production operations will continue to be recorded normally for all workers, including the newly logged-in worker and previously logged-in workers.
   

How are reports calculated?

1. First Hour Productivity: If a production operation is performed for workers logged into the same device and there is more than one worker, the completion time for this operation is calculated separately for each worker based on the period from login time until card scanning.

If three workers log into the same device: the first at 8:00 AM, the second at 8:15 AM, and the third at 8:20 AM, and the production operation occurs at 8:30 AM, then the operation time is calculated as follows: 30 minutes for the first worker, 15 minutes for the second worker, and 10 minutes for the third worker. The total completion time for the team-based stage group equals the sum of the calculated times for all workers involved.

1. Downtime and Maintenance Requests: If a downtime or maintenance request is submitted from a device with multiple workers logged in, the request resolution is recorded as completed for all workers together rather than individually. However, downtime duration is still calculated separately for each worker according to the actual time spent on the machine while it was stopped.
2. Estimated Stage Time per Bundle: The Worker Performance Report adds three columns to the table: the first for the total estimated stage time based on the stage SMV, the second for the number of workers who worked on the same bundle while logged into the same device, and the third for the required time for each worker, calculated by dividing the total estimated time (SMV) by the number of workers.
3. Efficiency and Other System Reports: These continue to be calculated individually for each worker as usual.

Frequently Asked Questions (FAQs):

1. Can team-based stages be assigned to a device without multi-worker login permission?
   No. This device only accepts individual stages.
2. What happens when the maximum worker limit is reached without enabling Login Override?
   The device rejects any new worker login attempt so the predefined limit is not exceeded.
3. Does multi-worker login affect individual efficiency calculation accuracy?
   No. Efficiency and all other indicators continue to be calculated individually as usual.
4. How does the system handle downtime requests when multiple workers are on the same device?
   Request resolution is unified for all workers, while downtime duration is calculated individually according to the actual time each worker spent before logging out.

Do you have a question about this update?

Contact the Garment IO team. We are here to ensure that you get the maximum value from every feature.