An overview of managing server assets
Before Getting Started
You are a technician with access to TDNext and the Assets application. For SO ITS, this is called SO Assets/CIs. If you do not have access you may request it.
Related KB articles are found in this same category.
Assumption
Typically, server assets such as VMs, hardware, and networking equipment are maintained by Infrastructure, Networking, and Database staff. Other staff interact with them however, e.g. request tickets related to assets, purchase assets, etc..
Note that Asset Management in TDX can be used for other purposes, e.g. desktop and peripheral management, and software management.
Steps
The basic model for Asset Management is similar to managing tickets. You can create new assets, and edit or update existing assets, and the asset feed keeps track of all events related to an asset. Typically, assets are not deleted, but rather have their status changed. As with Ticketing, you can build reports based on asset attributes. Other concepts for asset management include the use of Locations, Rooms, Product Models, Vendors (Manufacturers, Suppliers, Contract Providers), and Contracts, although at the time of writing (Jan, 2025) we do not make use of Contracts.
Asset Desktop with the New menu showing
A key benefit of having servers as assets is that assets can be attached to people and tickets, so that, for example, you can see the tickets associated with an asset and vice-versa. Below are some screenshots from using assets, as well as a short 9-minute video introduction.
Video Introduction
Tickets listing with the Associate Assets/CIs option highlighted
A specific asset with the Tickets tab showing
All assets have a QR code associated with them, which integrates with the search in the TDX Mobile application.
A specific asset with the General tab showing and a QR button
