Skip to main content

Asset Types

Concept overview​

  • AssetType: a general category for assets (e.g., Pump, Motor, Heat Exchanger).
  • Purpose: determines the maintenance tasks and asset attributes that can be selected for an asset.

Asset types standardize how assets are described and maintained. When you create an asset, you must specify its AssetType.

Why it matters​

  • Consistency: ensures similar assets share the same required and optional attributes (e.g., tag number, manufacturer, rated power).
  • Maintainability: ties assets to standard maintenance tasks/PMs appropriate for that type (e.g., Pump → lubrication, seal inspection).
  • Reporting: enables meaningful grouping, filtering, and KPIs by type.

First implementation​

  • Required on Asset create: an Asset must reference one AssetType.
  • Attributes: AssetType defines a list of attributes available for assets of that type through the AssetTypeAttribute relationship. See Asset Attributes for detailed information on how the attribute system works.
  • Maintenance tasks: AssetType provides a catalog of tasks that can be selected or recommended for assets of that type. Initial implementation can be a flat list of task templates.

Planned relationships​

  • Asset → AssetType (required).
  • AssetType → AttributeDefinitions (list of attribute templates).
  • AssetType → MaintenanceTaskTemplates (list of task templates).

These relationships guide what fields and maintenance activities are available when managing assets.

Usage in Blueprint​

  • CRUD for Asset Types to define categories, attributes, and task templates.
  • Asset creation/editing enforces selecting an AssetType and then shows attributes/tasks driven by that type.

See also​