Skip to content

Component Tasks

Map tasks to component types so every asset of that type inherits the right default task set.

Required role

Mapper or Admin.

Overview

A component (see Components) defines an equipment type — "centrifugal pump", "V-belt drive", "vertical mill spindle". Component Tasks is where you link specific tasks to those types. The linkage means: "every asset of this component type gets this task by default."

Without component tasks, you'd have to attach tasks to each asset individually. With component tasks, one definition covers all 20 similar pumps in your plant.

Open the page

Configuration → Asset Setup → Component Tasks.

You see the component-task tree:

  • Left pane: list of component types (from Components).
  • Right pane: the tasks currently linked to the selected component type.

Click a component type on the left to see its tasks on the right.

  1. Select the component type in the left pane.
  2. Click Add task.
  3. Either pick an existing task from the catalogue or create a new one inline.
  4. Configure task-specific options that override the component-type defaults (thresholds, required photos, safety procedure).
  5. Save.

New assets of this component type inherit the task going forward. Existing assets inherit the task on next sync; existing task instances are not retroactively changed.

Edit a linked task

Click the task in the right pane → Edit. Changes apply to future generated instances. In-progress and historical task instances keep their original parameters.

Click the task → Remove from component.

  • Assets of this component type stop generating new instances of this task.
  • Existing task instances already in the queue or history are untouched.

What propagates vs what doesn't

Change Affects future instances Affects existing instances
Add a task to a component type ✅ —
Edit a task on a component type ✅ —
Remove a task from a component type ✅ (stops generating) — (existing ones remain)
Change a task's form fields ✅ —
Change an attached safety procedure ✅ —

The rule: component-task changes always move forward in time. If you need to change an in-flight instance, edit that instance directly — not the component-task mapping.

Typical component-task profile

For a centrifugal pump, a typical mapping might be:

  • Daily visual inspection (Maintenance task type).
  • Weekly vibration reading (Maintenance with numeric field + threshold).
  • Monthly lubrication of the drive-end bearing (Lubrication task type).
  • Quarterly alignment check (Maintenance).
  • Annual tear-down inspection (Maintenance, high safety).

You define these once. Every asset linked to "centrifugal pump" inherits all five.

Bulk-apply to existing assets

Adding a task to a component type doesn't retroactively create instances on existing assets. If you want existing assets to start getting a new scheduled task:

  1. Add the task to the component type.
  2. Create or edit the associated schedule in General Schedule Setup — it starts generating instances on the next fire.
  3. Existing assets of the component type get the new instances from that point forward.

Things to watch for

Test on one asset first

Adding a task that generates instances on 200 pumps all at once is a big workload bump. Link the task, run a schedule for one pump for one cycle, confirm it executes correctly, then broaden.

Naming consistency helps

Keep task names consistent across component types ("Weekly grease inspection" vs "Weekly-grease-check") — reports aggregate cleaner.