Parts we manufacture gets air-dried out in the open, and the drying time incurs no labor or oven cost. each part will take a different time to dry, and drying times can be substantial. I am building a separate drying operation, no costs connected to it. This operation will be using a separate Resource Group with infinite Resources, and $0 cost and it is a Back Flush Operation. Is there any way to make them not affect the estimated production hours calculation under job tracker? I am only using this operation for scheduling purpose ONLY
You can add queue hours or move hours so that it doesn’t add it up as labor hours, but still spaces it out in scheduling.
1 Like
Thanks for the fast response @Banderson. The time to dry varies significantly based on the size of the part, so I cannot use the move time.
That’s the only way that I know how to add time without adding labor time. Off the top of my head, could you make categories that would get it close enough? Like short med long, or based on part size? or time range?, etc, then apply the operation that you need for the part? Depending on how you are doing reporting that can make things painful, but if it’s a back flush operation, then maybe it wouldn’t matter. Just one possible solution.
1 Like
Some potential ways to go after this.
-
You can assign the que start date and que start time to manipulate the queue time assigned to a job. Like in the job scheduling board using the move option of Subsequent Operations.
-
Set the time and scheduling blocks on the operation which will translate into resources assigned to change the time used.
Then remove the operation time after scheduling which would leave the dates set, but reduce your job estimated time. -
Calculate your own estimate. I calculate our own production time estimate which skips kitting, mold cure time and testing.
1 Like
Thanks for the reply. I will have to test it.
If anybody got more creative solution, I would appreciate that!!