What is the correct process for inducing a new asset in ServiceNOw

[Damhoej]

I am looking for the overall philosophy in ServiceNow (in phases) for Asset Management.

The documentation describes in detail how to use discovery, which is good when you already have deployed an asset.

However, I am looking for an overview of the process when I introduce a new Asset (a completely new computer).

What is the steps in getting through a Life Cycle for this item.

I know I have to make a model and publish it to the service catalog in order for the users to buy it.

Can anyone help me with a diagram or som kind of overview, so I can learn when to do what?

[vinitha3]

Hello,

Asset - There are both Hardware and Software Asset.Since you have mentioned "A completely new computer" you need to think of activating the SCCM plug in and ,move forward.

It is imperative to identify and follow formal processes for collecting and confirming the data in your CMDB. Fortunately, if you have tools to provide an excellent start to gathering this information. SCCM (and Configuration Manager in the near future) provides the majority of the key attributes which should be collected for laptops and desktops, while LANSweeper can gather information on any network-connected device (such as servers, switches, routers, APs, and KVMs), as well as providing some additional data regarding laptops and desktops which may not have an active SCCM agent for whatever reason.

1. We can use scheduled imports by integrating with SCCM or Lansweeper and have regular updates from SCCM database to "Computer" module of Configuration Item application.

2. If the procurement team can share the new buy list to you, you can do a manual upload process of entering it at first to CI table and then the hardware table.

Thank You,

Vinitha.K

PS: Hit like, Helpful or Correct depending on the impact of the response

[Damhoej]

Yet again I receive an answer where assets already exist and based on CMDB... (sorry I am not looking to be rude)

I my organisation assets do not magically appear from vendors. We have a life cycle management proces, that has to approve new type of equipments (computers etc.).

What I am looking for is the proces that comes before creating an asset, (create models, publish to service catalog etc and other prerequisits.) in order to be able to "just" create an asset.

We are already using SCCM, but it only handle a "live view" of CI's, It can NOT handle Asset Management.

How do I handle an Asset which is never connected to our infrastructure, but switches ownership multiple times during its life cycle?

This might explain what my apporaoch is (as a business process guy):

Blog | Don't confuse IT Asset Management and Configuration Management

[vinitha3]

Thank you for the clarification.

Vinitha.K

[timw22]

In our organization, we do have an interface to our primary vendor, however not all. The easiest way to create your assets is just to have a standard process used by all teams to manually create the assets in the computer table. This will create the asset. Another solution that might provide more tracking is to create a Purchase Order whenever you order assets. Add Purchase Order Lines for the equipment that you have ordered. When the equipment comes in, go to the Receiving tab of the Purchase Order and receive the equipment. This will create both the asset and the computer record. You can then manually update the asset tag and serial numbers of your devices. Try it out in your stage environment to see if this works for you.