Sometimes while analyzing your production productivity you might have a worker that has one or more production records with a time spent of 00H00, and the corresponding productivity at 0%.
In this article we will help you understand why and correct any problems.
This can happen because the system considers that the worker or the machine associated with the record are not in its working hours. This may be related to the schedule, downtime records or punch clock records.
1. Is the production record being done on the worker's and/or machines's shift?
Both workers and machines have schedules associated to them. If they are working out of their schedule, their productivity will not be counted.
You can check both a worker or machine's schedule in the bottom of their pages.
If the records was done outside of working hours, you have found the problem and you can adjust either their schedule or punch clock for that day, and the productivity will retroactively be corrected. Same applies for machines (note: if a machine has no shift, the system assumes it works 24/7).
2. Is there a downtime associated to the worker or machine?
If the worker or machine had a downtime inserted during the production time, the productivity will also be affected.
On the downtime list you can filter by the worker or machine and check if there was a downtime record inserted during the production time.
Like the schedule, if this was the problem you can either edit the downtime or the production to solve the 0% productivity.
3. Are there any punch clock records made by the worker?
Punch clock refers only to workers. In case a punch out record has been made before production, the time spent on the record (along with its productivity) will be zero. Same happens if a punch in record has been made after production.
Moreover, if workers only use the Punch Clock to mark their presence and the worker did not punch in, their productivity will not be counted.
Similarly to downtime records, you can filter by the worker number in the punch clock dashboard and verify if this is the case.
4. Are there any other causes that explain the 0% productivity?
If the operation itself is defined as "No Quantity" or "No Time", Autodesk Fusion Operations has no way of defining it, and it will be shown as "-%".
If productivity is unusually low or high, you can check the cycle time for the operation, and see if it is adequate to the actual time workers take to complete it. You can check our Batch time update article to get more insights on this.
With this you are well armed to troubleshoot the reasons why a worker's productivity might be displayed as 0%. If you couldn't find the reason, feel free to use our support channels.
Need help? Request a Fusion Operations expert to contact you here.