This introduction article will help Assets/CIs Application administrators to create relationships between assets and configuration items using the TDNext interface. To configure relationships, the user must have the Modify assets and configuration items permission in the TDNext interface. To create relationship types, the user must have admin access to the Assets/CIs Application in TDNext or access to the TDAdmin interface.
Overview
While physical hardware is captured as an asset in TeamDynamix, it is also possible to create additional Configuration Items (CIs). CIs can represent applications, business processes, and other items in your environment that require configuration and maintenance. It is also possible to create attributes that are associated with the CI Type. For example, an Application CI Type it could have an attribute named "Application Version."
Where to Find This
This feature appears in the TDNext and TDAdmin interfaces.
TDNext is where support staff can create, manage, and update configuration items, depending on their permissions.
TDAdmin is where administrators can manage settings for the Assets/CIs application and create configuration item attributes and types.
Navigate to configuration items following these paths:
- TDNext > application menu > Assets/CIs > Configuration Items (in the left navigation menu)
- TDAdmin > Applications > [Assets/CIs application] > Configuration Items
Using Configuration Items
Creating a Configuration Item Type
Before creating a new CI, you first need to create a configuration item type.
To create a new configuration item type:
- In TDAdmin, navigate to Applications > [Asset/CIs Application] > Configuration Item Types.
- Click the New button.
- Enter the Name of the configuration item type.
- Leave the checkbox set to Active.
- Click Save.
You can also set up custom attributes for configuration items to track custom information about configuration items, aside from what is available in the standard fields.
Creating a New Configuration Item
At this point, the CI type and associated attributes will be available, and a new configuration item can be created.
To create a new CI:
- In TDNext, open the Assets/CIs Application.
- Click the + Configuration Item button and choose a configuration item form.
- Fill in the required fields for the configuration item form.
- Click Save.
For information on modifying the fields on the CI form, or creating a new form, view our article on asset forms, which also applies to CIs.
Configuration Item Relationships
Creating a Relationship Type
After the CI has been created, relationships can be defined to link CIs to other CIs and Assets. Before creating a relationship, you will need to create a relationship type:
- In TDAdmin, navigate to Applications > [Asset/CIs Application] > Configuration Item Relationship Types.
- Click the New button.
- Enter a Relationship Description. This describes the relationship from the perspective of the parent CI, such as “powers”, or “supports”.
- Enter a Reverse Description. This describes the relationship from the perspective of the child CI, such as “is powered by” or “is supported by”.
- Keep the Is Active box checked.
- Check the Operational Dependency box if one of the CIs in the relationship is dependent on the other to remain operational.
- Click Save.
Creating a Relationship
Once a relationship type has been created, you can create a relationship between assets and CIs.
To create a relationship:
- In TDNext, open the Asset Application.
- On the left navigation menu, click Configuration Items.
- Click on the name of one of the assets or CIs you would like to link.
- Click on the Relationships tab.
- Click +Add Relationship.
- Choose the Assets/CIs Application where the child asset or CI is located.
- Choose the Relationship Type that describes the relationship of the current asset or CI to the other.
- On the Item(s) field, click the magnifying glass to open a list of configuration items.
- Check the box next to any configuration items you would like to link, then click Insert Checked.
- Click Add.
Assets and Services as Configuration Items
In TDNext, users can manage configuration item records in asset applications. CIs are split among multiple CI Types: Assets, Services, Service Offerings, and "Standalone" Configuration Items. Each type represents an instance of a CI, though they all support different functionality and store distinct information that is relevant to the type's intended usage.
- Assets - Physical items which are used in an organization (computers, servers, office appliances, etc.). These may have associated ownership/user/location information.
- Services - Service records in the Client Portal Service Catalog which can be used to submit project/ticket requests or link to other websites (asset repair request, password reset help, etc.). These may have associated ownership information. Further, they provide a way for Client Portal users to interact with TDNext users.
- Service Offerings - Service Offerings are a requestable child component of a Service. A parent/child relationship is automatically maintained between the Service's and the Service Offering's CIs.
- "Standalone" Configuration Items - Non-physical items which are used in an organization (virtual machines, software licenses, etc.). These may have associated ownership/location information. Further, since these can represent a wide array of items, administrators are able to create custom Configuration Item Types for an asset application which are associated with these records.
These three configuration item types can be used to store all items which an organization needs to operate, while providing an outlet for others to request assistance when those items have issues. Further, relationships can be added between CIs to show any dependencies they may have (even across multiple asset applications). However, the real power of configuration management comes from association with tickets, as outlined in the following section.
Configuration Item/Ticket Association
Since configuration items do not support time entry, TDNext users cannot perform work directly against them. However, if a CI needs routine maintenance performed or has an issue that needs to be fixed, a technician is able to track that work on an associated ticket. By supporting ticket association, the CI record contains all information relevant to the technician, while the ticket allows them to track work against the item.
As with configuration items, tickets also support relationships with CIs across multiple asset applications. The related CIs can be specified when filling out the ticket form, or from the ticket in TDNext. In both cases, the CIs can be selected from a lookup field.
When the lookup field is opened, it will display a list of all configuration item types, including filtering options to help to user locate the correct CI. As this is a list of all types of configuration items, the displayed ID for each record is the ID associated with the item's configuration item record. This is discussed in more detail in the following section.
Configuration Item IDs
This section details the ID of configuration item records for all types of CIs. Since Assets, Services and Service Offerings support functionality separate from standalone CIs, they also have a separate ID when viewing pages specific to asset/service functionality. On the other hand, standalone CIs are only represented as configuration items, and so they only have one ID representation.
This discrepancy has historically been a source of confusion. Sometimes users attempt to validate that the proper asset/service was selected for association with another item, and find the ID on the detail page is different than the one that appeared when it was selected. In general, Asset/Service/Service Offering IDs will only be displayed on pages specific to those CI types (i.e. where Standalone CIs are not included).
The following locations handle Assets/Services/Service Offerings with their Configuration Item IDs instead of their standard IDs:
- Configuration Item Lookup pages
- "Shared" Configuration Item Detail Page - Users will only see this detail page if they do not have access to the CI's containing asset application. As such, it excludes most information and does not support actions being taken on the item. Otherwise, the user will be directed to a detail page which contains all information.