Availability
Packages: Essential, Premium, Enterprise (incl. custom categories)
User Roles: Admin, Manager
What are Asset Categories?
An Asset category describes the functional role of an Asset within your structure.
The category is defined by the Asset Type and automatically inherited by all Assets of that type. This means:
You define the category for the Asset Type.
All Assets of this type automatically inherit this category.
Individual Assets cannot change the category individually.
This ensures that your structure is consistent and logical.
Asset categories help you to map your Assets in remberg in a structured, clear, and functional manner. Each Asset belongs to exactly one category - and this determines, among other things, which functions and areas are displayed in the detail page.
What are the Different Asset Categories?
Currently, the following five categories are available:
1. Site
Represents a higher-level location or area.
Example: Plant, Building A, Production Hall 3
2. Group
Used for logical grouping of assets.
Example: Conveyor technology line 1, Packaging unit north
3. Asset
The classic Asset.
Example: CNC machine, compressor, pump.
4. Component
An installed part of an asset.
Example: Motor, sensor, valve.
5. Storage
A storage location or inventory storage facility.
Example: Spare parts warehouse, tool cabinet.
Why are Asset Categories Important?
The category influences:
Which areas are visible on the detail page
Which functions are useful
Which icons and displays are used
How you can filter Assets
In the future: which functions are permitted or restricted for certain categories
In short:
The category ensures that each Asset receives exactly the functions that suit its role.
Working with Asset Categories
Configuration
Asset categories are defined at the Asset Type level. There are therefore two setup options:
Categories when Creating an Asset
When you create a new Asset:
First, select an Asset Type.
The associated Asset category is displayed automatically.
The Asset automatically adopts this category.
This means you know immediately when creating the asset in which context your asset operates.
Different Detail Pages for Each Category
Depending on the Asset category, certain areas are shown or hidden on the Asset detail page.
Examples:
A “Component” typically does not require any Sub-Assets
A “Storage” has different relevant information than a “Site”
A “Site” is used for structuring and not for operational processing
This keeps the interface clear and reduced to the essentials.
Filter Assets by Category
You can filter your Asset lists and hierarchies by Asset category.
This is particularly helpful if, for example, you:
Only want to display “Components”
Want to check all “Storages”
Want to analyze your structure at the “Site” or “Group” level
Custom Categories
Availability
Packages: Enterprise
User Roles: Admin
By default, the visible areas on the Asset detail page are predefined by remberg for each Asset category.
If you've booked the Enterprise package, you can also customize this assignment. This allows you to define which areas should be visible on the detail page for each Asset category and tailor the view to your structure and way of working.
The configuration is performed centrally at the workspace level in the system settings (Settings > Features > Assets). These settings take effect immediately for all Assets in a category. They do not affect interfaces or, for example, previously linked Assets.
Best Practices for Use
Here are a few recommendations for a clean structure:
✅ Consciously define categories at the Asset Type level
Define the category correctly when creating the Asset Type. Subsequent changes will affect all associated Assets.
✅ Think hierarchically about the structure
“Site” → “Group” → “Asset” → ‘Component’
Use “Storage” separately for storage locations
✅ Only use “Component” for installed parts
A “Component” is not a standalone production item, but part of a higher-level Asset.
✅ Do not use “Storage” as a normal Asset
Use “Storage” specifically for storage and inventory locations.
Here is an example (click on the image to enlarge it):
