Self-Service Portal Models feature overview

Last updated:
Edit on GitHub

The Models capability in the Self-Service Portal lets you group assets into logical families (for example, machine types or generations) and maintain spare parts and service compatibility at the model level instead of per individual asset. This capability is the foundation for the asset-based spare parts and services catalog.

What is a model

A model represents a type, generation, or configuration of a machine or equipment line. Each model can have:

  • Multiple assets that belong to this model.
  • One or more product lists that define compatible spare parts and service products.

By centralizing compatibility rules on the model, you:

  • Avoid maintaining compatibility for every asset.
  • Reduce errors when selecting spare parts.
  • Keep asset catalogs in sync as your fleet grows.

Relations between models, assets, and products

The core relations are:

  • Model → Assets: All assets assigned to a model share the same compatibility rules.
  • Model → Product lists: Each model can have one or more product lists with spare parts, consumables, and service products.
  • Assets → Product lists (via model): Assets inherit product lists through their model instead of referencing spare parts directly.

This results in the following structure:

Model
 ├── Assets (individual machines)
 └── Product lists
       └── Spare parts, consumables, service products

Manage models in Back Office

In the Back Office, you can:

  • Create and edit models, including reference, name, code, image, and other attributes.
  • Assign and remove assets from a model.
  • Assign and remove product lists that contain spare parts and services.
  • View relationships between a model, its assets, and its assigned product lists.

To keep data consistent, note the following:

  • A model cannot be deleted while it still has assigned assets or product lists.
  • Changes to model assignments immediately affect which products appear in the asset-based catalog.

Storefront behavior

In the storefront, customers can:

  • Filter the catalog by model reference, model name, or model code.
  • Use the compatibility widget on the product details page to check whether a product is compatible with a selected model and which assets in their fleet it fits.

Models act as the bridge between:

  • The assets a customer owns, and
  • The spare parts and services that are compatible with those assets.

Example: Industrial machine series

  1. An operator creates a model PRESS-1200-SERIES for a family of press machines.
  2. All installed press machines of this series are registered as assets and assigned to this model.
  3. The operator creates spare parts as products (for example, filters, seals, and sensor kits) and adds them to product lists such as P1200 Hydraulic Components or P1200 Maintenance Kit.
  4. These product lists are assigned to the PRESS-1200-SERIES model.

Result:

  • Any asset belonging to PRESS-1200-SERIES automatically uses these product lists as its compatible spare parts catalog.
  • When a customer starts from an asset or model in the storefront, they only see products from the assigned product lists.