Overview
When using a single PM Template for multiple assets, all PMs are generated at once when the schedule triggers. This quickly creates large backlogs of open PMs that teams can’t realistically complete on time. Users need a way to control how many PMs are active at once so that work is spread out and manageable.
Current Limitations
• No way to limit how many PMs are generated at one time.
• All assigned assets trigger PMs simultaneously, overwhelming techs.
• The only workaround is to duplicate the PM template for each asset, which increases admin effort and creates versioning issues.
Example
