Overview
When a Preventive Maintenance (PM) is assigned to multiple assets, the generated tasks are difficult to differentiate because the task name does not automatically include asset-specific identifiers. Users want the task name to dynamically reflect key asset details, and they want this behavior to be user-configurable so each organization can choose which fields appear.
Current Limitations
• Multi-asset PMs generate multiple tasks with the same or generic task name.
• Task names do not dynamically include asset identifiers (e.g., asset #, name, location).
• Even when assets share the same location, users must open each task to confirm which specific asset it applies to.
• There is no configuration to control which asset fields appear in the task title.
General Example
A PM is assigned to 10 pumps located in the same pump room. The system generates 10 tasks with the same title (e.g., “Monthly Inspection”). From the task list, technicians cannot tell which task corresponds to which pump without opening each task individually.
Requested Enhancements
- Configurable task name template for PM-generated tasks (multi-asset)
- Add a setting that allows admins (or PM creators) to choose which asset fields are appended to the task name when tasks are generated per asset.
- Field selection options
- Provide selectable fields such as Asset Number, Asset Name, Asset Location, and other standard or custom asset fields.
- Template formatting controls
- Allow users to define order and separators (e.g.,
PM Name – {Asset #} – {Asset Name}), with optional labels.
- Uniqueness and clarity
- Ensure each generated task name is unique and asset-specific based on the selected fields, even when assets share the same location.
- Scope rules
- Allow this configuration to apply specifically to multi-asset PMs, with the option to extend it to all PM-generated tasks if desired.
Business Value
• Reduces time spent opening tasks to identify the correct asset.
• Improves task list clarity for assets in shared locations.
• Minimizes errors when multiple similar assets exist in the same area.
• Allows customers to standardize task naming conventions based on their operational needs.
