CMDB IRE Engine - Ignore retired CIs

[Chaz_]

Hi,

I would like to know whether it is possible to have the CMDB IRE engine ignore CIs which are retired in the CMDB.

Currently, we face an issue where CIs get retired in the CMDB. Then a datafeed will come in and using the reconciliation rules in IRE it will revert the status of the CI to Operational or update some of its attributes.

Is there anything which can be done on the IRE end to prevent CIs being set to Operational if they are actually retired?

The datafeeds could be cleansed of retired CI information, but I am looking for a solution on the IRE end.

Thanks.

[Fabian Kunzke]

Good points!

However, the continuation of history is the exact reason for not having a different CI. Imagine that CI has an error prone CPU. You'd wanna know that. Maybe it had a harddrive which was previously host to a virus. Maybe the RAM was faulty.

Imagine a device which is marked as "Retired - Stolen" pops up in your CMDB again because the discovery found it. Should that CI now be a new identity, a different CI? One that doesn't raise any eyebrows imideatly?

Now, should it be automatically be set to operational? Should the lifecylce be set automatically? That's down to preference. Should we generate duplicates based on preference? I prefer not to 😄

Would love to have a more extended discussion about that as your focus seems to be more ITSM & Asset based. Very interesting.

Regards
Fabian

ps.: Really enjoy your input here!

[CMDB Whisperer]

Agreed.  I think there are cases to be made for either or both behaviors.  From an "operational" perspective, I think there are some very valid points to consider.  It's like if I buy a used car, I want to know how well the car was maintained, whether it's been in any accidents, whether there are repairs I should expect.  On the other hand, I shouldn't need know anything about the previous owner, their address, where they took the car, what their GPS history looks like, their favorite radio stations etc.  That should be private information.  (And interestingly, used cars often do still have this information available!)  

With a unlinking/re-linking scenario this "CMDB Carfax report" could still be available upon request, because the previously linked CI(s) are still in existence and a record could be retained of which CIs were linked, but that information could be kept and only select information could be made available to the new CI owner.

[CMDB Whisperer]

Yes, you can use Identification Inclusion Rules for this.  

[pratiksha5]

Let's take the example of computer class. 

Go to CI class manager - > Identification rule - > inclusion rule :-

This will do the trick.