Understanding Automatic & Manual Beats Recommendations

Automatic & Manual Beats Recommendations

How the System Works

Previously, adding a missing operation required manually entering a time range and selecting the employee, which opened the door to inaccurate recommendations or data manipulation.

That changes now.

The system relies on historical records to recommend the right employee for each missing operation — only employees who previously performed that stage and were actually logged into the device at that time appear in the list.

If the system cannot make a recommendation, it means this stage has never had production recorded on any Garment IO device. Each stage must be recorded on the device at least once to enable future recommendations.

Manual Beat Priority

When adding a transaction manually or via web, the system follows a defined order to find the right position to insert it:

First, it looks for the closest production transaction within the same section as the original operation.
If none is found, it searches in other sections.
If still not found, it considers adding it after the sub-operation time.

The only case where the system fails to add the transaction is if this stage has never been performed on any device at all.

Reject The Manual Beat

Adding Manual Operation

From the bundles page, tap "Manual Run." You'll find the employee dropdown already pre-filled with the names of workers who previously performed this stage, along with the corresponding timestamp of the last transaction each worker completed for the same style and operation. This ensures the recommended worker was actually logged into the device at that time, preventing any data manipulation.

System Suggest an Operator

Enhanced Quality Monitoring

On the station inspection page, if the system can recommend all stages, the page is automatically filled with employee names and their timestamps. The user simply needs to press "Confirm."
Quality stations that depend on stages from another section are now smarter. If there are missing stages outside the station's scope, the system displays a notice at the top of the page and recommends workers for these operations as usual.

This allows missing stages to be identified at the beginning of production rather than at the end, saving time and reducing rework costs.

Suggest Missed Processes From QC Tablet

If the system cannot make a recommendation, the bundle must be returned to the previous section to record the stage on the device first.

Processes Never Scanned Before

Frequently Asked Questions

Why is there no recommendation for a specific stage?
Because this stage has never had production recorded on any Garment IO device. It must be recorded at least once on the device to enable future recommendations.
Can the user manually change the recommended employee?
The list only shows employees who actually performed this stage and were logged into the device. This restriction prevents data manipulation.
What happens if there are missing stages outside a quality station's scope?
The system displays a notice and recommends workers for these stages. If it can't make a recommendation, the bundle must be returned to the previous section to complete the stage on the device first.
Does the auto-transactions feature work independently without activation?
No, the auto-transactions feature must be enabled in factory settings for the system to start making recommendations.

Have a question about this update?

Reach out to the Garment IO team. We're here to make sure you're getting the most out of every feature.