Master planning performance

Are you facing problems with master planning performance?

May be the following pointers will help you.

1. If you are running master plan on 3-tier then try running it on 2-tier.

2.  If there is a filter on master plan OR if you have  approved planned orders OR  if you have freezing time fence then the logic deletes the old plan item by item. However if none of the above is applicable then complete master plan is deleted which is quite fast.

3. If you are running a master plan with job scheduling then ask yourself whether it is really necessary?

4. Logic will first explode the planned production orders during coverage, schedule them to get a requirement date. Coverage plan the lines. Delete the capacity reservations and schedule the planned production orders again during futures. If you are running coverage as well as futures then run coverage with infinite capacity and futures with finite capacity. You get more futures messages but the performance boost is also significant.

5. Get in an SQL server expert to look at your database. Fragmentation of indexes and data files kills master planning.

6. Look at your coverage time fence, are you planning more than what is required?

7. Look at your item levels, ask your client if they can reduce item levels and use phantom BOM/Route instead. As it is lean manufacturing recommends using fewer item levels.

Send mail to harry@systomatics.com with questions or comments about this web site.

Disclaimer: I am working with Microsoft Business Solutions. The code on this site may or may not be related to my official duties with Microsoft. I do not claim in any expertise in modules represented on this website. Essentially there is just one person doing functional specifications (in head), design specifications (in head), coding and some testing. There is no way the project on this site will be free of bugs. The projects are intended as guidelines and may god help you if you decide to implement the projects without making any changes. If you implement any project resulting into data corruption or anything like that then do not even think of suing me because a. I have already warned you and b. I don't have any money. I may or may not respond to your emails about supporting the project. I may or may not upgrade the projects to the next service pack / version.