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
A team has 20 identical HVAC units and one shared PM Template for quarterly filter changes. When the PM triggers, all 20 PMs are created at once. The tech team can only complete a few each week, so most sit open for weeks—creating backlog and poor visibility.
Requested Enhancement
Add an option to limit the number of concurrent PMs created from a multi-asset PM Template.
• Example setting: “Max concurrent PMs = 2.”
• Once one PM is completed, the next one auto-generates for the next asset in the list.
• This continues until all assets have had their PMs generated for that cycle.
Business Value
• Prevents PM overload and keeps workloads realistic.
• Eliminates the need to duplicate templates for identical assets.
• Ensures steady progress without overwhelming the team.
• Simplifies template management and improves scheduling accuracy.
