[ASK] difference between priority and route network when set a paralel routing

hi, is there anyone can explain the different using priority [routing line] and route network for paralel routing? what is the pro and con?



I’ve used the primary & secondary1 routing options in the past when wanting to distinguish between machine & labor costs for the same operation; for example, on the primary route line use a machine work center type and on the secondary1 route line, use a human resources work center type.

It’s fine as long as you remain in the parallel routing logic whereby the run time for the primary operation is the same as for the secondary1 operation; the run time field for the secondary1 operation is inaccessible (grayed out) & it must have the same value as the primary operation.

That’s an advantage for a simple manufacturing environment but Dynamics gets heavy when you have a customer who wants to consider machine time against labor time – for example, in a manufacturing environment where a machine work center is covered by 1,25 operators, you would want to express the labor time as 0,8 hours (1 hour / 1,25 = 0,8). In this case you can still use the primary & secondary1 priority & ‘play’ with the fields load & quantity of work centers; at some point you have to use both because the load percentage field cannot have a value > than 100% whereas you can have a quantity of work centers which is > than 1.

By heavy I mean that this solution obliges you to maintain multiple routing lines for each item so there is a data maintenance issue and you eventually have to create tools allowing external maintenance in excel and then upload back into AX.