Hi Markus,

I’m in Apps8, but I think the principals will be the same.

Machine costs are set within the work center on the cost tab.

Within the Routing alternate you then have a field called Mach Setup Time - which I believe uses the cost from the work center.

The labour costs, you’ve found already.

HTH

Dave

You have labor time and machine time separately for both setup time and runtime. 

The machine time is related to the work center, and the machine cost is set per work center. You cannot have different machine cost rates for setup and runtime since the same work center is used for both.

The labor time is related to the labor class, and the labor cost is set per labor class. You can set different labor classes for the setup and the runtime, hence, you can use different labor cost rates for the setup time and runtime.

Bjorn I have a question then,

when you tried to regsiter the time on an operation in “Time registration”

Why the cost is taken from the primary Labor Class of the employee and not the Labor Class defined in the operation ?

​@NicKhos The actual labor cost can be configured to be fetched from different sources. This is well documented in the “about Cost for Shop Order Labor Reports”.  Below is fetched from this document.

​@Björn Hultgren Thank you so much !!!

One last thing do you know if it is possible to match the labor cost with the Work center.

Befor IFS Cloud, our customer only have work center without labor class. Each “employee hour” was associated with the cost of a Work Center.

Are we able to do the same or do we need to change the process and use Labor Costs ?

​@NicKhos No I don’t think you can match the labor cost with the work center in anyway. So better change the setup and use labor class and labor time to account for the labor costs.