Classes - Master

The Asset Definition > Classes-Master sub-application app is a domain-level app where you define and manage the various classes of assets that you will be tracking in your domain.

Asset Classes represent the assets that you want to track for projects in your domain which have a common set of attributes. This includes attributes that a group of these items have in common, such as the model number or capacity, and attributes unique to a single item in the asset class, such as the serial number or installation date. Additionally, if enabled, you can create a list of required submittals for the asset class.

Example Projects in your domain commonly include Fire-rated doors. You've already set up the required asset attributes in the Asset Definition > Attributes sub-application.

Now you can add the asset class of "Fire-Rated Doors" to the Asset Definition > Classes - Master sub-application. You can add attributes such as "Manufacturer", "Model Number", and "Fire Rating" as Type Attributes, since they are common to all fire doors. You can add "Serial Number" as an individual Asset Attribute, since that value will be unique to each fire door that is installed.

You can also add a list of commonly required submittals for Fire Doors, such as "Product Data Sheet".

Key elements of the app include the following:

  • The Asset Definition > Classes-Master app is a domain-level app. It stores information for all the asset classes you could use in your domain. Regardless of which project or partition is open when records are added, the values are stored at the domain level.

  • Type Attributes are used to track information that is consistent for all instances of an asset type (for example, model number and manufacturer).

    Asset Attributes are used to track information that is unique to each installed asset (for example, serial number, location, tag number, or installation date).

  • If enabled, you can define Required Submittals at the class level for both Type and Asset submittals.

How to . . .