Bottleneck Resource and SNP planning

[former_member566355]

Hi,

As per my understanding, SNP does not support start-start relationship between operations.

Due to this behavior we have maintained end - start relationship betn activities in ECC.

w.r.t to above case, suppose there are 10 operations in recipe and if all resources are taken to APO for planning, in APO it is planning as per the capacity of the bottleneck resource. But in ECC, the dates for the order are getting shifted because system is adding the times of the other resources, which are not bottleneck, to calculate start and end dates of the order.

What is the best practice in SNP to plan in such scenario ?

Is it always that if we use SNP planning, it should be only using bottleneck resource?

Even if it so, when the orders are transferred to ECC, how to avoid addition of times of other resources to it ? should the other resources be non relevant for scheduling to get correct start and end dates ?

Regards,

RS

[GSU · Accepted solution]

Hi RS

As you may already know,SNP is a mid to Long term planning tool unlike ECC/PPDS....So,we don't need to paln all resources in SNP....Infact,the minum time permitted in SNP is a day bucket..So,restrict,only th eresources which are 'critical' or that may cause bottlenecks..regarding the cumulation of additional time (of SNP irrelevant resource),this should happen while conversion of the SNP order to PPDS Order( production order in ECC,if you don't use PPDS)---RE-EXPLOSIION takes place which uses the PPDS source of supply...

Thanks and Regards

Suresh

NB:Please reward good answers appropriately