Overview
This article will provide a general overview of the use of the Assets/CIs application within TeamDynamix, the use of asset forms and definitions for the fields in those forms.
Assets/CIs & Forms
The Assets/CIs application within TeamDynamix serves a number of important uses for Penn College.
- Provides a record of what service requests and incidents are associated with one or more specific devices.
- Provides a relationship diagram of assets and their associated configuration items, like licenses, special configurations as well as parent/child relationships.
- Provides easy, at a glance lifecycle reporting and updating in bulk - a feature we did not have with KACE.
As part of the Equipment Request workflow, all new equipment that is purchased is imported in to the Assets/CIs application. When that equipment is imported, TDX applies the data to the Default Asset Form. The Default Asset Form is simply a broad, generic form in the Assets/CIs application. Other forms contain fields that may be important for searching and reporting on particular assets.
Types of asset forms in TDX
| Name of form |
Intended Use |
Applies to |
Owner |
| Default Form |
To track anything that does not have a custom form built for it |
Nothing - however, when assets are imported, TDX applies this form by default |
Brad Miller |
| Cell Phone |
To track college-owned cell phones in service |
Cell Phones |
Bryan Waltz/Brad Miller |
| |
CSS Asset |
To track anything previously managed by Computing Services in KACE Assets |
Computers, Stand-alone scanners |
Nathan Barger/Brad Miller |
| CSS Mobile Device |
To track anything previously managed by Computing Services in KACE Assets |
Tablets, VR Headsets |
Nathan Barger/Brad Miller |
| CSS Asset |
To track anything previously managed by Computing Services in KACE Assets |
Computers, Tablets, Stand-alone scanners |
Nathan Barger/Brad Miller |
| Digital Signage Player |
To track information necessary for reporting on signage players that would not normally be required for other CSS assets. |
Visix players |
Amanda Whitesel/Brad Miller |
| Printer Assets |
To track network attached mutli-function devices (MFDs) |
Network Printers, Network Scanners, Network Copiers, |
Nathan Barger/Brad Miller |
| Server Assets |
To track physical and virtual servers |
Servers |
Tim Shade/Brad Miller |
| Technical System |
Serves as an inventory record for technical systems supported by the college. |
typically cloud services, but pertains to any platform that serves a business function at Penn College (e.g. Administrate, TeamDynamix, Cisco ISE, etc) This may be made up of multiple assets linked together by relationships. |
Nathan Barger/Brad Miller |
If there is an asset you want to edit, but cannot find the right field to edit, chances are good that you need to change the form. You can do this by clicking into the asset, clicking Edit at the top, then selecting the correct form from the form dropdown.
In addition to asset forms, TDX allows us to create CI forms. These are essentially the same as asset forms in terms of intended use within the system, however CIs have some special restrictions. For example, a true CI record does not have a way to be associated with any one Location or Location Room directly. All Assets are CI records, but only Services and true CI records exist solely in the classification of a "CI". Also, an Asset is the only type of CI record that can be associated with a Location.
Types of CI forms in TDX - use with caution CIs are not as robust as Assets.
| Name of form |
Intended Use |
Applies to |
Owner |
| Default Form |
To track anything that does not have a custom form built for it |
Nothing - however, when CIs are imported, TDX applies this form by default |
Brad Miller |
| Image |
To track specific software associated with an image, incidents, service requests and change requests associated with that software, and make updating image relationships to assets easier. |
Logical image records. |
Nathan Barger/Brad Miller |
| Software License |
To track licensed software relationships to assets as well as associated incidents and service requests. |
All licensed software |
Susan Deuel/Brad Miller |
| MS Form |
To track ownership of self-reported Microsoft Forms |
Registered Microsoft forms |
ESI - System Administrators |