Asset Management resources for institutions who do not have HAM Pro

[David Millar]

We're an institution who does not have HAM pro, nor do I think it's in our budget in the near future.  With several institutions sharing one instance of ServiceNow, as we mature in our SN asset management, we may find need in the future.

That said, are there articles, resources, etc. for ensuring we're setting up the correct tables with the correct data? The bi-weekly HAM seminars, though valuable, seem to focus on setting up / configuring/ using HAM pro. (I can't wait for us to utilize it, however!)

Thank you,

David Millar

Midland University

[Eric_Schuman]

Hey all, I could not agree more with Ed Milligans reply.  I would also add that HAM Pro utilizes the same base tables in alm_hardware, but of course adds a few more attributes, flows, automation, and the content library.  With that, I will often tell customers who are not quite ready to pursue the HAM Pro purchase to work on the basics.  Here are a few things to consider:
- Make sure you have good process for the high touch lifecycle asset activities for for teams to follow (i.e asset team, EUC team, etc.).  Generally, those processes are the intake or asset creation, asset deployment, asset retirement, and asset returning to a stockroom.  Make sure that teams know they need to update the asset tables when these activities take place to help ensure accurate data.  Also, make sure to document the processes, as this will help speed up the implementation when you do move to HAM Pro.
- Utilize the operational data you get via a Service Graph connector such as SCCM.  Make sure you are getting most recent discovery information and identification of who is using the device.  This will help you with at least what has been deployed.
- Generate some basic reports that could give you early indicators that your asset data has some issues i.e report on most recent discovery dates,  asset.assigned_to that does not math ci_assigned_to, assets that don't have an assigned_to are just a few.
- Model Management:  Keep and eye on your models.  I see alot of times where orgs create what they think the model is and then inventory tools that are connected to SN report something else.  Make sure you are keeping this clean.
- Get your stockrooms created and start thinking about stockroom strategy.  I like to use virtual stockrooms where different equipment types are at rest - i.e new equipment, used equipment, equipment that is pending disposal.  It has been my experience to have virtual stockrooms within a central stockroom to place this equipment.
- Don't over develop, keep things simple and ready to migrate to HAM Pro.  I have seen many orgs that have created their own workflows, flows, business rules, etc. that they have to unwind when the go to HAM Pro.  Make sure you are staying up on the docs in ServiceNow Documentation as to what each of the OOTB lifecycles does, so you are more in-line in the future.  Especially on process documentation and working with various teams.  Remember, changing someone's process that they have been following for years is challenging enough, don't change it multiple times.

Now all this being said, this is primarily focusing on End User Compute devices, as that is where I see the priority in most orgs, datacenter assets have other things to consider - especially with virtualization. 

I hope this helps