Deployment Optimizer for multisourcing

[Former Member]

Hello experts,

I am involved in a project in which we are considering the implementation of Deployment Optimizer in order to deal with a scenario with multisourcing and multidestination.

Please could you confirm me if Deployment Optimizer can consider Multisourcing or, otherwise, it is only working for Monodestination.

Thank you very much for your help.

Regards!

Josep

[kenneth_snyder]

You are correct deployment optimizer will work as you described

But again deployment Optimizer will not create any additional planned orders

[Former Member]

Hi Kenneth,

So, as per your answer, deployment optimizer is considering the whole network.

Thanks al lot.

Regards,

Josep

[Former Member]

In order to clarify the problem:

- We are dealing with monocode products ( in the example Factory A and Factory B produce same SKU and DC1 and DC2 receive the same SKU).

- When we run the heuristic at DC level, Stock Transfer Requisitions are created based on inbound quotas ( for example in DC1 60% to Factory A and 40% Factory B).

- After that, Production Plan is created at both Factories. Here, to make the explanation easier, imagine that one of the factories (factory A) can not produce all the required quantity and it is the other factory (Factory B) which is producing this lack of quantity. Manually the planner is modifying Production Planned key figure with this new situation for both Factories.

- In a pull logic, when executing deployment it will try to confirm STR planned and as you know, it will generated a shortage at boh DCs due to lack of production at Factory A but  stock will remain at Factory B (overproduction). Factory B is only confirming STR which has been requested.

So, the point is, when executing deployment optimizer, the algorithm is considering the whole network (Factory A, FactoryB, DC1 and DC2) and its "costs" associated or, otherwise, the algorithm is considering one source (Factory A + DC1-DC2) and then (Factory B + DC1 and DC2)?

Thank you very much.

Josep

[kenneth_snyder]

I don't understand your question?

Do you know the functionality of Deployment?

Do you understand the difference between Deployment Heuristics and Optimizer?

I would recommend reading some of the available information online then asking specific questions.

Ken

[Former Member]

Hi Kenneth,

Sorry but I think I have not explained me well, the point is a little bit more complex.

Let me explain you better the situation:

- We are dealing with monocode products ( in the example Factory A and Factory B produce same SKU and DC1 and DC2 receive the same SKU).

- When we run the heuristic at DC level, Stock Transfer Requisitions are created based on inbound quotas ( for example in DC1 60% to Factory A and 40% Factory B).

- After that, Production Plan is created at both Factories. Here, to make the explanation easier, imagine that one of the factories (factory A) can not produce all the required quantity and it is the other factory (Factory B) which is producing this lack of quantity. Manually the planner is modifying Production Planned key figure with this new situation for both Factories.

- In a pull logic, when executing deployment it will try to confirm STR planned and as you know, it will generated a shortage at boh DCs due to lack of production at Factory A but  stock will remain at Factory B (overproduction). Factory B is only confirming STR which has been requested.

So, the point is, when executing deployment optimizer, the algorithm is considering the whole network (Factory A, Factory, DC1 and DC2) and its "costs" associated or, otherwise, the algorithm is considering one source (Factory A + DC1-DC2) and then (Factory B + DC1 and DC2)?

Thank you very much.

Josep