Support Guide: SACM / Service Asset & Configuration relationship types

Objective

  • The objective is to provide information about CI Relationships defined by the SACM Process Owner and/or SACM Process Managers. Relationship CIs make possible impact and root cause analysis for changes. Relating CIs also provides a better understanding of our baseline configuration
  • The following explain the Relationships tab, how to add a relationship type in TDX, and the relationship types with descriptions

Environment

  • 10374: TeamDynamix (CMDB) 
  • 12568: Service Asset & Configuration Management (SACM)

Relationship Tab

  • The Relationships tab will appear at the top of the asset as a selection, if the asset is a new asset you will need to complete the save of the record before the tab is available.
  • Adding a relationship
    • Select the Assets/CI application: The Assets/CI application determines the application instance to which the service belongs, if not specified, the default Assets/CI application for the organization will be used 
    • Select the relationship type: See type description listing below with the reverse descriptions (you will see a list of 14 total, including reverse descriptions)
    • Items: These are the items that will be on the other side of the relationship with this assets. Items can have more than one relationship with the asset, but the parent item, child item, and type of a given relationship must be unique. When searching with no search criteria you will see all items listed. (Hardware, Service Offering, Software, Databases, Servers...)

Configuration Item Relationship Descriptions

Below are the relationship type descriptions and their reverse descriptions. Each relationship type has a reverse that describes the Y to X path, reverse description is highlighted in Blue. 

 

Common

  • Enables / is enabled by / X Enables Y: Use to relate a Technology configuration item to a Capability or a Technology configuration item or a Service in the service catalog; this relationship represents high dependency, if severed, the dependent item will not continue to function (eg. an application running on a server) 
  • Uses / is used by / X Uses Y: Use to relate a technology configuration item to another technology configuration item; this relationship represents high dependency, if severed the items will continue to function (e.g., a laptop managed by SCCM, an application sending data to another application periodically)    

 

No longer used relationship types and are disabled 

  • Contains Configuration Information About / configuration information contained in / X Contains Information About Y: Used to relate a configuration item to a CMDB; instead, recommend including text attribute to the underlying CMDB for the configuration item
  • Contains this Request Model - is a request model of / X Contains this Request Model Y: Used to relate a service catalog entry to a service overview in the Service Catalog
  • Manages / is managed by / X Manages Y: Used to relate a Technology configuration item to a Capability configuration item or Service in the Service Catalog
  • Provides / is provided by / X Provides Y: Used to relate a Technology configuration item to a Capability configuration item or a Service Catalog
  • Includes / is a component of / X includes Y: Used to relate a Technology configuration item that is included in different configuration item

 

Print Article