Hi,
I do remember reading something about this in the Incident/Change Use cases that are also published.
From memory "Support group" is who you would normally assign Incidents to and Assignment group is who would implement changes.
I would check in the documents linked to the CSDM 3.0 now learning course for updated versions.
From the Change Use Case for CSDM 2.1.pdf
What CMDB data is populated/used to assist with advising a Change
To understand the details of a desired Change the following activities are recommended:
1.Populate the Configuration Item attribute on the Change form, configuration_item, with the target CI for the change activity. This CI can then be utilized to identify details for Change routing using CI data such as “Assignment Group” and “Approval Group” while also providing service impact using dependency relationships.
From the INCIDENT Use Case for CSDM 2.1.pdf
The data model in figure 12 identifies data elements available for use by ITSM:
•Subscription –related lists on service offerings that identify “who” has access to the offering and thus may be impacted in an outage. An incident or change can identify impact using the subscribed by tables. The related lists are as follows:oService Subscriptions by Company –service_subscribe_companyoService Subscriptions by Department –service_subscribe_departmentoService Subscriptions by Group –service_subscribe_sys_user_grpoService Subscriptions by Location –service_subscribe_locationoService Subscriptions by User –service_subscribe_sys_user
•Business Approver –may be used by change. Found on the business service offering. The business approver maps to the attribute approval_group.
•Technical Approver –may be used by change. Found on the technical service offering. The technical approver maps to the attribute approval_group.
•Environment –may be used by incident & change. Found on the technical service offering and application service. Some service offerings may identify the environment of the offering such as prod and no-prod (DEV, QA, UAT, etc.). The environment maps to the attribute used_for. Those non-prod environment may be filtered out from incident and change if desired.
•Business Criticality –may be used by incident & change. Found on the business service offering. The business criticality maps to the attribute business_criticality. The business criticality maps to the attribute criticality. A business service may have multiple offerings, each with differing criticalities.
•Technical Assignment Group –may be used by change for routing of change and change tasks. Found on the technical service offerings. The technical assignment group maps to the attribute assignment_group. May be synchronized onto the CI’s that the offerings manage thus reducing the manual overhead of maintaining manual data on thousands/millions of CI’s.
•Technical Support Group –may be used by incident for routing of incident purposes. Found on the technical service offerings. The technical support group maps to the attribute support_group (Note: organizations may be using the assignment_group attribute instead of support_group which is acceptable if the data is the same used in routing of change and change tasks). May be synchronized onto the CI’s that the offerings manage thus reducing the manual overhead of maintaining manual data on thousands/millions of CI’s.
