The type of service determines how you use dynamic CI groups.

Dynamic CI groups

  • A dynamic CI group is a user-defined collection of CIs that is used as a group Cl in the Cl field of the record for Incident Management, Problem Management, and Change Management.
  • You set up dynamic Cl groups based on common attributes or criteria.
  • A dynamic CI group cannot contain other groups.

Dynamic CI groups for technology management services (formerly Technical services)

You can group up to 10,000 similar items that are associated with a technology management service and its associated technology management offering. In this usage, a dynamic CI group functions as a collection of CIs that are managed individually. Because the CIs aren't necessarily related to each other, service associations are not needed. Impact analysis (through Incident Management, Problem Management, or Change Management) is also not meaningful or expected for unrelated CIs. Here are some examples:

  • Servers with a particular operating system
  • Network gear based on location
  • Application servers based on a running process
  • CIs that make up a service instance
  • CIs that share a particular support group

The Service Classification attribute identifies the service as a technology management service. The ownership sync process assigns CI ownership through the technology management service, as described in Synchronizing group assignment attributes.

Dynamic CI groups for service instances

For a service instance (called application service before CSDM v5), impact analysis outcomes are expected because when any individual CI is impacted, the entire dynamic CI group is affected. All related business services or technology management services are also affected. Because of this interdependence, you must establish service associations and impact analysis is important.

The Service Classification attribute identifies the service as a service instance.

See Use the Dynamic CI Group method to populate application services.