In Our org, we generate PM WOs 180days in advance for most of Service Contracts. We have around 17K active Plan in the system, PM engine process all active PM Plans though Next Schedule date is beyond 180. This results in unnecessary work load on PM engine and SFDC server to process 17K PM Plans and generating 300-400 WOs everyday. Next Schedule date is on PM Schedule object but not on PM Plan object so that we can configure PM Process to pick only PM plans which are due to generate WO as per criteria.
What is the underlying problem do you intend to solve with this idea?
Today, our PM engines runs for 8 hours to process all PM Plans and generates 300-400. We want to improve performance of PM engine and be more efficient by taking very less CPU time.
How is the problem being addressed today, if at all?
We have created a roll-up summary field on PM Plan which calculates min. of Next Schedule date from PM Schedule records. Then we added this field on criteria to run PM process to exclude the PM plans where Next PM schedule greater than 180s from today.