Overview
The current PM structure requires users to create separate PMs for each asset. While assigning one PM to multiple assets exists as a workaround, it introduces new issues—specifically identical naming and bulk generation. The goal is to make multi-asset PM assignment a fully supported workflow by improving naming and controlling how PMs are generated.
Current Limitations
• The system expects one PM per asset, requiring duplication when managing similar assets.
• Updating multiple PMs becomes time-consuming and error-prone when changes are needed.
• Assigning one PM to multiple assets acts as a workaround but is not fully supported as a scalable workflow.
• When using this workaround, all generated PMs have identical names, making them difficult to distinguish.
• All PMs generate at once, which can overwhelm operations and reduce scheduling flexibility.
General Example
A conveyor belt is divided into 14 sections, each set up as an individual asset. Creating 14 separate PMs makes updates difficult and repetitive. To simplify, the user assigns one PM to all 14 assets. However, when PMs generate, all 14 are created at once and share the same name, making it hard to identify which PM belongs to which section.
Requested Enhancements
- Dynamic asset-based PM naming
Allow generated PMs to include asset-specific variables in the name, such as:PM Name - {{Asset ID}}PM Name - {{Asset Name}}PM Name - {{Location}}
- Controlled PM generation cadence
Allow users to define how many PMs are created at a time when assigned to multiple assets:- Generate 1 at a time
- Generate 2 at a time
- Continue until all assigned assets are processed
- Scheduled batch creation
Allow users to define when PMs are generated:- Specific days (e.g., Fridays only)
- Multiple days (e.g., Monday, Wednesday, Friday)
- First-class support for multi-asset PMs
Elevate assigning one PM to multiple assets from a workaround to a supported workflow, ensuring usability at scale without forcing duplication or creating operational confusion.
Business Value
• Eliminates the need to duplicate PMs across similar assets.
• Reduces maintenance effort when updates are required.
• Improves clarity by tying each generated PM to a specific asset.
• Prevents large batches of PMs from being created all at once.
• Enables better workload distribution and planning.
• Supports scalable PM management for facilities with many similar assets.
