CI's - Automatic link of CI's in Dynamic CI Group to Service Offering

[Wing Yee Tang]

Hi all,

Recently, I have created Dynamic CI Groups and linked them to its Technical Service Offering (TSO). Which makes incident, and change management easier and convenient if new CI's are loaded into the CMDB. 

However, when creating a new incident, after selecting the service, service offering and CI, we get the following pop-up: "Valdate Service Offering, It is not related to current CI"

I was wondering why no relationship is automatically established between the CI's (that are in the Dynamic CI Group) and the Technical Service Offering? 

We tried changing the relationships between service offering and dynamic ci group. First we tried contains and thereafter managed by: manages.

Thanks! 

[Barry Kant]

hi Wing Yee Tang,

these 'relations' are stored in the svc_ci_assoc table. It is a flat version of relations. You might extend your validation logic with the association table as well. Or, check just with that association table (not sure if that is possible). It is faster as it is flat, but it would require that all relations are synced to that table (like in Dynamic Services).

You can also do the other way around:
If you select the Configuration Item before the Service Offering is selected then only populate Service Offerings in context of that Configuration Item. (and the parent Service accodingly).
If you select the Service Offering before the Configuration Item, only show the Configuration Items in context of the selected Offering.

BR,

Barry

[Wing Yee Tang]

Hi Barry, 

Thanks for the quick reply.

However, if iI select the CI before the Service Offering, I still get this notification pop up.

I will try the vallidation logic with the association table. 

Thanks again 🙂

[Dominic5]

This video explains HOW to relate Dynamic CI groups to Technical Service Offerings (around the 21 minutes mark): (1) CMDB Health Deep Dive - CSDM Dynamic CI groups & fixing data required for audit and incident - Y...
... as I don't think you can yet do this via Service Builder.

[Jim Zeigler1]

Hi Wing,

The Dynamic CI Group you created is actually an ITOM Application Service for one of your operational environments(e.g., Dev,QA,Test,Prod). The platform was designed for events, alerts,incidents and changes to propagate up through the Application Service hierarchy of Services and Service Groups(See the attached slide). The "Refresh Impacted Services" UI Action is refers to ITOM Services in this hierarchy so they should all get updated. As long as this hierarchy is defined, there are no additional CI relationships needed.

SPM "Services" like Service Offerings describe your Service Catalog hierarchy (Service Portfolio) for Sell/Consume use. 

They don't "run" in any of your operational environments or IT infrastructure. They have no operational status or severity that could reflect the status of your discoverable CIs like servers and applications that are all environment specific.

Jim Zeigler