How to add more than one Affected CI to an Incident SM7.11

[christopher.caron@compute]

The OOB form for incident management only allows someone to enter one affected CI. I would like to modify the incident forms so that folks can enter more than one CI. The reason for this is that it appears that Availability Service Level Objectives are based on the "Affected CI" and not the "service" specified in the incident. However, I might have a particular incident where I want to indicate the individual affected CI (i.e. the server) "AND" the Affected CI which happens to be the Servce.

For example:

Service = Siebel
Affected CI#1: Siebel
Affected CI#2: siebelserverA

Has anyone else done this or needed to do this, if so, how did you do it?

[christopher.caron@compute]

Given that Availability SLO's are tied to a specific CI...is anyone else out there running into this same issue? If I open an incident ticket for a specific computer device that is down that is affecting a particular service...I am not going to be able to have the SLO taken into consideration when SM calculates the Availability %. The only way around this, that I see, is to forgo tying an incident to a particular computer device CI (which is unfortunate) and enter the "Business Service" as the affected CI instead.

[RFedoruk]

Wish I could help you friend. I gave up on getting useful SLA data out of HP products back in OVSD 5.1