HaloITSM

HaloITSM Guides

Documentation to assist with the setup and configuration of the HaloITSM platform

Guides > Asset Types/Groups

Asset Types/Groups

Configuring your Asset Types in HaloPSA will allow you to more readily view an organised list of your devices & will also allow you to specify precisely what data points you need to capture against each Asset.


Before Configuring your Asset Types, you may first want to establish the groups those Asset Types belong in. You can also check out the list of settings with descriptions for asset types and groups in the following 

Admin Guides:

Asset Groups

Head to Configuration>Asset Management>Asset Groups

Fig 1. Asset Groups Option


There aren't many options in here, as you simply add to a list of Asset Groups. Create a new group by clicking 'New' (Top RHS). Each Asset Group provides you with the below options:

Fig 2. Options within an Asset Group


Each group allows you to specify a name & provide some notes, potentially providing further detail about what the group contains (if applicable). You will also see two options here: 'Use for Assets' & 'Use for Items'.


You may be asking yourself at this point "How are Assets & Items related to each other?"


Assets Vs Items

To summarise: An Asset can be thought of as an instance of an Item/Product.


Items/Products (the term 'Item' & 'Product' are interchangeable in HaloPSA) are the entities you add to your Quotes, Sales/Purchase Orders & invoices. Products themselves do not contain specific information such as Serial Numbers etc.. - this information would be against an Asset.


Example: You own a shop that sells iPhones. You have 200 iPhones in the 'Back Office'. Someone comes in and buys one of your 'stock' - you go into the back office & pick out one of the phones.


At the point of picking an iPhone to sell, you're not concerned with the specific serial number/IMEI - you simply go out back & pick one off the shelf. 


Once you make the sale, you scan the barcode  & give the customer a receipt of the transaction, which includes the serial number of the iPhone you have sold them.


In this example, the 'Back Office' would be a stock location/stock bin in HaloPSA. You would have an iPhone product with a stock quantity of 200. And the particular iPhone you sold would be an Asset - with a serial number/IMEI added to the Assets information.


Asset Types

Asset types can be thought of as being similar to Ticket types - primarily by virtue of the fact that Asset Types have distinct field lists. Just like different Ticket types require you to fill in different pieces of information (a new starter request requires a 'start date' to be populated, while an Incident does not), different Asset types allow you to store different pieces of information against them (you may want to store an IMEI number against a mobile phone, but not against a keyboard).


Asset Types are configured in Configuration>Asset Management>Asset Types. This is where you can attribute high level information to the Asset type in question: Asset Type name, the group the Asset Type exists within, sequence in lists etc.. - there is also a tab to establish the field list (pieces of information relevant for the Asset type):

Fig 3. Asset Type Field List Configuration.


The configuration of these fields & how they are presented can be found in the following lessons.

Popular Guides

Pin It on Pinterest