Skip to content

Components

Manage the component catalogue: reusable equipment-type definitions with their options, remarks, and the tasks that apply to each component.

Required role

Mapper or Admin.

Overview

A component is an equipment-type template. Instead of configuring every asset from scratch — defining its fields, its tasks, its thresholds — you define a component once and reuse it across every asset of that type.

Examples:

  • "Centrifugal pump" — a component that captures the common maintenance profile of every centrifugal pump in your plant.
  • "V-belt drive" — defines the checks that apply to any V-belt drive.
  • "Vertical mill spindle" — the task set for every spindle.

When you link an asset to a component, the component's default task set is inherited by the asset. A new task on the component propagates to every asset that references it. This is where component management pays off: maintaining a task on one component is a single edit; maintaining it on 40 individual assets is a nightmare.

Prerequisites

  • You have the Mapper or Admin role.
  • You've thought about what component types exist in your plant — talk to the maintenance team to match their mental model.

Open the components page

Components in the sidebar. You see two sub-views:

  • Components tree — the component catalogue (the definitions).
  • Component-task tree — mappings between component types / subtypes and the tasks that apply.

Components tree

Structure

Components form a small two-level tree:

Component (e.g. "Centrifugal pump")
 └─ Component type (e.g. "End-suction", "Submersible")

A component can have one or more component types — subtypes that share most configuration but differ in some specific options (e.g. a submersible pump has different lubrication than an end-suction).

Create a component

  1. Click New component.

  2. Fill in:

    Field Notes
    Name Short, descriptive ("Centrifugal pump", not "Pump_v2").
    Description Optional.
    Order Display order in the tree.

  3. Save.

Add a component type

Inside a component:

  1. Click New type.
  2. Name the type ("End-suction").
  3. Save.

Add options

Each component type can have options — the fields that appear on tasks executed on assets of this component type. Common option kinds:

  • Unit — link to a master-data unit (°C, bar, l/min). Feeds numeric fields.
  • Type — a dropdown with a finite option list (condition: good/fair/poor).
  • Text type — free-text labels for notes.

To add an option:

  1. Open the component type.
  2. Click Add option.
  3. Pick the option kind.
  4. Configure it (label, linked unit, dropdown values, etc.).
  5. Save.

Add remarks

Remarks are short editorial notes attached to a component ("this pump class typically fails at the seals — inspect seal first" kind of thing). They show up on the mobile app when a technician opens a task on an asset linked to this component.

  1. Open the component.
  2. Click Add remark.
  3. Enter the remark name and text.
  4. Save.

Remarks are advisory — they don't gate any action, just inform.

Component-task tree

This is where you map component types to tasks. The mapping means "every asset of this component type gets this task by default".

How it works

  1. Select a component type on the left.
  2. The right panel shows the tasks currently linked.
  3. Add tasks from the global task catalogue or create new ones inline.
  4. Configure any task-specific options that override the component-type defaults.

When you link an asset to this component type, the linked tasks become that asset's default task set.

Propagation

  • Adding a task to a component type → appears on all linked assets going forward. Existing task instances already generated for those assets aren't retroactively changed.
  • Editing a task on the component type → future instances pick up the change; existing ones don't.
  • Removing a task from a component type → assets stop getting new instances of that task. Existing instances remain until completed.

Linking an asset to a component

From the Asset hierarchy page:

  1. Open the asset's detail page.
  2. Edit the Component type field.
  3. Pick a component type.
  4. Save.

The asset now uses the component's default task set. You can still add asset-specific tasks on top if the asset has quirks that don't generalise.

Common patterns

One component per equipment class

Create a component for each distinct class of equipment in your plant. Don't over-split: if 20 pumps all need the same 5 tasks, they should share one component type, not 20.

Subtypes for variants

Use component types (subtypes) when a class has meaningful variants that affect tasks:

  • "Motor" with types "AC induction", "DC", "Servo".
  • "Pump" with types "Centrifugal", "Positive displacement", "Peristaltic".

Review before mass-linking

Before you link 200 assets to a new component, pick 5 representative assets and link them first. Execute a few tasks. Confirm the form makes sense. Then scale up.

Deleting components

  • Delete a component type that's linked to assets → those assets lose their component assignment. Tasks they already have remain, but future task-generation based on component defaults stops.
  • Delete a component → all its types are deleted; all linked assets become unassigned.

Be very careful with delete. Deactivate where possible.

What you can do that other roles can't

  • CRUD on components, component types, options, remarks.
  • Map component types to tasks.
  • Configure how a new asset's defaults come from its component.

Things to watch for

Renames ripple quietly

Renaming a component doesn't break linked assets, but report headers and mobile UI labels update. Warn users before renaming something heavily used.

Start simple

A good first pass: 5–10 components covering 80% of your plant, each with 3–5 tasks. Refine over months. Over-engineering at the start wastes time.

Components vs hierarchy

The hierarchy is physical (where equipment is). Components are logical (what kind of equipment it is). Don't conflate them.

Troubleshooting

Problem Fix
New task on component isn't appearing on assets Generation happens at schedule-time for scheduled tasks; ad-hoc tasks aren't auto-created
Can't delete a component It's linked to assets — unlink or reassign first
Option doesn't show on the mobile form The task attached to the component needs to reference the option explicitly
Remark doesn't appear on mobile Remarks only appear for tasks executed on assets of the remark's component type