Configuration Item (in ServiceNow Change Management)

[kathymorris]

Hi All,

We have a Architect leader (of a software distribution app) who wants to know if he is deploying an application to 100 computers. Does he need to create 100 Change requests. Obviously not.  In the Change request, would this be done with "Mass Update CI."? He also announced to our leadership that the purpose of the CI field in SN Change Management is "useless," and does not see any purpose for filling in the CI info. 

Obviously, it is important to have the CI. We will not be able to manage or assess the risk and impact of changes across our environment without the CI. Are there any more specific points that can help drill this basic concept in so that it becomes clear to the Architect---of the value of the having the CI in Change Management? 

Thanks,

Kathy

[pablo_itguy_pl]

Hi,

Have you discussed using "Impacted CI's" related list/tab to populate "additional" 99 CI's? With this you are working with single change record that covers multiple CI's that are subjected to this change.

I'm not sure if you are doing the deployment of the application manually or through something like SCCM - if that is so I would consider integration (example integration with SCCM) so you end up with a single change, perform automated app deployment and through integration you have up-2-date CMDB.

[Dr Atul G- LNG]

HI @kathymorris 

No , not need to create 100 changes, add one main CI on change form and rest 99 you can add in affected CI's list.