Availability
Packages: All Packages
User Roles: All User Roles
The Asset is the key element in your remberg system. It can be a machine, a fire extinguisher, a vehicle or a hall. With the help of the hierarchy, Assets can be linked together on any number of levels and dependencies can be displayed. Read here for help on how you can best map your Assets in remberg.
Assets
An Asset is the central element in remberg - usually a single machine, but it can also represent structures, groups, vehicles or components. Assets are clearly referenced in Work Requests, Tickets and Work Orders.
Three fields are crucial for identifying an Asset:
Asset ID / Serial number (mandatory field): A unique number that identifies the Asset
Asset Type (mandatory field): Describes the type of Asset (e.g. series or task)
Asset Name (optional): A free text field to assign an individual name (e.g. a call name or “David's car”). This name is displayed in lists and selection fields
If you do not enter an Asset name, the name of the Asset Type is displayed and used.
You also have the option of uploading an individual image for each Asset. Assets can be created as required and structured in a hierarchy.
Asset Types
Asset Types act as templates that group Assets with common characteristics (e.g. series or product lines). Important here:
Goal: There should be significantly fewer Asset Types than Assets
Avoid errors: Do not create a separate type for each individual Asset, as this will impair other functions in remberg
Recommendation for Service: In special machine construction, for example, the higher-level series or product line can serve as an Asset Type
Recommendation for Maintenance: Generic types such as “Storage location”, “Production group” or simply “Machine” are also common in maintenance