My client is hesitant to Sign Up for ITOM

MarMalo
Tera Contributor

I have a large client with that is looking to implement ITSM and CMDB.  However, they are hesitant to take on too large of a scope.  They ultimately want automated discovery and service mapping, but that is longer term (24mo. -36 mo.)  Current CMDB is very immature.  I know CMDB ServiceNow can be populated through:
Automated Discovery: ServiceNow Discovery automatically scans your network to identify and gather information about CIs.
Service Mapping: This feature maps the underlying IT infrastructure to the business services they support, providing a service-centric view.
Integrations: You can integrate the CMDB with other systems (e.g., asset management, monitoring tools) to pull in data.
Manual Input: While not ideal for large environments, you can manually create and update CI records.
Import Sets: Allows importing data from external sources like spreadsheets.

My question - can I ingest Splunk or What's Up Gold data to CMDB to start building the maturity - or do I absolutely need elements of ITOM?


1 ACCEPTED SOLUTION

Kieran Anson
Kilo Patron

Hi,

You don't "need" ITOM licensing to populate your CMDB but it makes the process a whole lot easier. The leg work is largely done for you, and you benefit from the years of use it's had to refine the data it pulls. 

 

In order to use Service Graph Connectors (with the exception of SCCM) you need to have an ITOM license

 

However you could pull data from the two sources you mentioned into an import set and then transform that data into your CMDB. That or those systems could push the data. 

 

The downside, you'll need to build the full thing yourself. If you don't have deep CMDB knowledge you could end up populating the CMDB incorrectly and causing a headache in the future 

View solution in original post

1 REPLY 1

Kieran Anson
Kilo Patron

Hi,

You don't "need" ITOM licensing to populate your CMDB but it makes the process a whole lot easier. The leg work is largely done for you, and you benefit from the years of use it's had to refine the data it pulls. 

 

In order to use Service Graph Connectors (with the exception of SCCM) you need to have an ITOM license

 

However you could pull data from the two sources you mentioned into an import set and then transform that data into your CMDB. That or those systems could push the data. 

 

The downside, you'll need to build the full thing yourself. If you don't have deep CMDB knowledge you could end up populating the CMDB incorrectly and causing a headache in the future