PM Engine process all PM Plans regardless of next Schedule Date

PM Engine process all PM Plans regardless of next Schedule Date

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.
Product Area?
Preventive Maintenance
What version of ServiceMax are you on?
Summer 16
2 Comments
Product Team
Product Team
Status changed to: On The Roadmap

We will be addressing this issue in SVMX release 19.1 through a PM Process Engine enhancement. The engine will now qualify the relevant schedules in the beginning of the query logic, so that only relevant PM schedules are considered by the PM Process when the engine logic runs. As a result, the over all imprint of the engine's processing will be reduced, and the burden on the org lessened. 

Product Team
Product Team
Status changed to: Delivered

An enhancement to address this idea has been delivered in 19.1 release. This enhancement moves the logic to qualify/validate relevant PM schedules to the beginning of the query logic, so only relevant schedules are considered for processing. since only qualified PM Schedules are picked up for processing, batch sizes and overall burden on the org is reduced.