If we don’t know about the trick with the efficiency greater than 100%, we would have to create them each as a resource, link them to a resource group which is the team and we would get available capacity of 200 hours a week as we wanted.
I want my scheduling to be on the level of the team. I do not want to manage them each as a separate resource. Many manufacturing companies have a dilemma in the set up of resources as follows: Let’s say we have a department where 5 employees work full time. NOTE: In Resource Groups in AX 2012, the efficiency percentage can no longer be changed and in AX 2012 R3 the efficiency percentage field no longer exists on the Resource Group. But there is no problem entering values > 100 and this turned out to be very useful. In the standard definition, this is a field that has values below 100. The system uses this efficiency percentage to reduce the day length.ĮXAMPLE: If your calendar indicates 8 hours per working day, and your efficiency is 80%, the system will assume you only have 6.4 hours per day to do work. When machines are down for maintenance or repair reasons, we do not use the efficiency percentage but actually adjust the calendar to zero hours for the duration of the maintenance. An efficiency of 85% is considered realistic for human workers. The natural down time has to be taken into account. For example, if I work 8 hours a day according to my contract, the scheduling system cannot assume that I am indeed going to be available 8 hours to do work. It has an obvious purpose to take into account the real world. The efficiency percentage is a field that is found in all MRP/ ERP systems. The business requirements that these features address are well known, and AX 2012 has some very interesting options that are not widely known but that do address some of the requirements precisely. This article provides an explanation of important fields in Microsoft Dynamics AX 2012 that impact the result of production order scheduling in a significant way.
0 kommentar(er)
