CMDB and SAM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2020 01:29 PM
I'm new to CMDB and SAM and have been tasked with leading projects for both. Does CMDB need to be implemented before SAM, SAM before CMDB or can they be done in parallel?
I haven't been able to locate documentation clarifying this and wanted to understand the priorities and dependencies.
Thank you
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2020 01:33 PM
My advice is to do the CMDB first. A lot of the data you need for SAM to be successful requires a good CMDB to generate. Think about what data you want to collect for each type of CI, and decide where its going to come from. Then do the same exercise for SAM.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2020 03:32 PM
I agree with what Mike said. CMDB and AMDB are closely related. In addition:
I had created this asset management vs config management slide notes for my reference, so sharing here.
A few important points to note:
- Asset management is geared towards Financial aspects, that is making sure that cost is correctly mapped to business units, license compliance is achieved and assets stay within warranty
- Config management is geared towards Operation aspects, that is making sure that outages are minimum and ITSM processes like incident management or change management are followed properly (by the availability of correct CIs in the CMDB)
- Different attributes are important for asset vs config as shown here
- Asset lifecycle is static, that is once an asset is procured it does not go through a lot of changes before it is decommissioned while CI lifecycle is dynamic, as an example OS, Memory and CPU of a CI can change overtime.
- please note the tables in which asset and config information is stored - alm_asset and CMDB_ci. These two tables are kept in sync using business rules
- Further: The system property glide.create_alm_asset.async controls whether assets are created immediately when a configuration item (CI) is created, or are created after a delay. A delay in asset creation allows large numbers of CIs to be created quickly. When this property is set to true, assets are created by the Asset - Create asset delayed sync scheduled job that runs every 15 minutes. View the status of the scheduled job in the Asset Job Log table [asset_job_log]. To view assets waiting to be created and asset creation errors, navigate to Asset > Administration > Asset Creation Queue. To reprocess an error, update the state from Error to Ready. The next time the scheduled job runs, it reattempts to create the asset.
When the glide.create_alm_asset.async property is set to false, assets are created immediately from CIs.
- Similarly: The system property glide.asset.create_ci_with_ire enables CIs to be created from assets using the ServiceNow® Configuration Management Database (CMDB) Identification and Reconciliation engine (IRE). This property affects CI classes that have an identification rule on serial number and have no dependent relationships with other CI classes
- Model categories associate CI classes with asset classes. Model categories are part of the Product Catalog application.
Please mark helpful or accept solution if this helps others with a similar question too.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-01-2020 11:15 PM
Hi,
While it is true that SAM requires some CMDB data it requires very specific data.
I think the first thing you need to do is define your business objectives from the two initiatives and only then you can start looking at implementation priorities.
CMDB as a whole is about service modeling. It includes many different classes of CI's and relationships. and getting to a mature CMDB is a serious challenge that can take quite some time and effort.
for SAM, depending on your priorities all you need is accurate information on the PC's if you are looking for PC licensing and or Server information if you are looking for data center licensing (If you are going for DC you might need the relationship between your hosts and guest servers for some software packages).
and if you are going for SAM for SAAS you probably don't need any PC and server information.
so, In order to start SAM you need to identify what configuration information is required and make sure you have it populated, accurate and updated, but you do not need your entire CMDB before you can start with SAM.
just as an example, if you are using SCCM to manage your PC's and you are interested in SAM for P software you could integrate SCCM to ServiceNow using the OOTB connector and very quickly you can have PC CI's and software installations for the PC's and you can get your P software into control way before you start thinking about other components of your CMDB.
and one last note, when starting to think of your CMDB - make sure you follow the CSDM materials released by ServiceNow.