Find your people. Pick a challenge. Ship something real. The CreatorCon Hackathon is coming to the Community Pavilion for one epic night. Every skill level, every role welcome. Join us on May 5th and learn more here.

When should an Asset create a CI

DavidO952207924
Tera Contributor

Hi,

 

I initially learnt to create CIs once they become operational (deployed) to track them.

It makes sense in things like laptops. Once ordered and stays in a stockroom and not yet operational, do not create CI yet. But once it is assinged to an user and connected to a network, it can then create CIs via discovery or manually.

 

However, things like infra assets, they need to be deployed under change management to get installed. Like Servers or Network gears. So I had a recommendation and apparently it is a industry practice to create a "Shell CI" to manage those assets for deployment and then populate the details once it becomes operational.

It all does make sense but I cant seem to find any recommendations related to this from ServiceNow. Is this another thing in ServiceNow that did not consider the real-world situation, or is there an actual recommendation for this specific usecase/scenario?

Thanks in advance

0 REPLIES 0