Asset and CI Status field mappings

[Geeky]

Asset has different status values (In Order, In Stock etc) and CI has different state values. How they are mapped logically?

I mean when the asset is created, a CI record is created and vice versa then how the status values are updated? There must be a status value mapped in the business logic. Can anybody share that mapping?

[Alberto Consonn]

Hi,

here you will all the information about Asset and CI status mapping:

https://docs.servicenow.com/bundle/newyork-it-service-management/page/product/asset-management/conce...

This synchronization and mapping is based on the following factors:

• Asset state and CI status are not mapped on one-to-one basis; rather they are mapped to the most logical counterpart on the other table. For example, for a hardware asset set to state In Stock - Pending disposal, the corresponding CI is set to In Disposition with no substate.
• This synchronization happens between the asset’s State field and the following CI fields:
  • Install Status field: Install Status does not have a sub status and must be used for non-hardware CIs.
  • Hardware Status and Sub status field: Hardware Status is visible only for Hardware CI.

If I have answered your question, please mark my response as correct and/or helpful.

Thank you very much

Cheers
Alberto

[Eric Ferrington · Accepted solution]

There are Asset State/Substate to CI Status mappings available OOTB for both Install and Hardware status values.

These can be found in left hand navigation menu under the asset module, then the administration heading (screenshot attached).

FOR CI's - I would recommend utilizing the Install status (as opposed to Hardware status) on your CI's going forward.  It provides consistency from that field on the CI side for any ci class as its rooted to the base ci record.

Asset states and substates are design to reflect the lifecycle stage of an asset and the substate is design to provide additional process driven context to the asset object record.

[Geeky]

Does System creates a record in asset management when a CMDB record is created and is vice-versa is also true?

I am assuming - system creates a CI record for all assets but it creates only assets when a CI is created whose class exists in assets e.g. Hardware.

Please correct me.

[Eric Ferrington]

That is based on how Model categories are defined.  Each model category has the option to reference a CI class and an asset class.

If both are set, when an asset record is created manually, via import or from process (receiving) then a CI record will be created and related to the asset record.  Just as when a new CI is discovered and created for that class, an asset record is also created and related to that new ci record.