ALM_Asset vs ALM_Hardware?

[Elie Baho1]

Hello,

Say I want to create a new computer asset in the ALM_Asset table and create another computer asset directly in the ALM_Hardware table.  What's the fundamental difference between these 2 tables?

A computer asset created in the ALM_Asset table doesn't create a record in the ALM_Hardware table.  But the opposite does.

So when does a computer asset from the ALM_Asset table become an ALM_hardware asset record?

The Hardware certification class teaches us to import load data in the ALM_Hardware table but the simulation course tests this import data in the ALM_Asset table.  What's the recommended path to create a computer asset correctly?

[Maik Skoddow]

Hi

I'm wondering why you want to create a computer asset in two different tables.

Basically the alm_hardware table - along with others - is a child of the alm_asset table:

Asset Management has similar concepts like the CMDB where child tables represent the best fit to include a certain type of asset. Therefore, only create your computer assets in the alm_hardware table.

If you want to learn more on CMDB or Asset Management I recommend downloading my Knowledge Sources To Go . You will find in that document many links to helpful resources regarding your question.

Kind regards
Maik

[Elie Baho1]

Hello Maik,

Thank you for your response.

It's not so much that I want to create computer assets in 2 different tables, I'm just wondering why would I be able to create it in one table vs the other?  ServiceNow documentation doesn't really give a clear direction other than in the HAM certification course, Importing assets is suggested in the ALM_Hardware table.  In the simulator course at the end of the certification, it's asked to do it in the ALM_Asset table.  

If I understand what you're saying, importing computer assets should always be done in the child table first?  Is that it?

In other words, why would anyone create assets in the ALM_Asset table?  In which context is it suggested to create assets in this table?

[Daniel Slocum]

As you've asked above, you should create assets in the child tables.  The alm_asset table is the parent table that holds the attributes that are consistent between child alm_ tables (asset tag, assigned to, model, model category, etc.). There is likely no scenario in which you'd want to just create a record in that table alone. If you have a new asset type, let's call it alm_spaceships, it would be best to create a new extended table that holds attributes defining spaceships while leveraging the values that are consistent between all assets in the parent alm_asset table. 

[Elie Baho1]

Hello Daniel,

If there's no scenario that supports creating a record in the parent table (alm_asset), shouldn't the create new  button from this table be disabled by the system? 

What is the learning value in the simulator course at the end of the certification that validates a task to have assets created in the parent table?

Just trying to understand the logic here...