ServiceNow CMDB Reviews

I am with a consulting company that implements the tool. I am working to implement ServiceNow in different areas such as SACM and software asset management. CMDB is the underlying database, and I populate it with the data from the clients based on their input and needs.

It has helped in tracking hardware and software and reducing overall costs.

When running large queries within the system, it does have a tendency to bog down the system. This is something that should be improved. I would also like to see the HAM Pro module beefed up a little bit and integrated better into the SAM Pro module, which seems to be pretty much on the roadmap.

Its pricing is pretty complicated and always fluctuating. Its pricing should be improved.

I've been using this tool for about seven years.

It is stable.

We do customizations for clients all the time.

For the most part, I would probably give them a nine out of ten. They are quite responsive.

Its initial process was very complex because there were a lot of customizations. The deployment took about six months.

In terms of the implementation strategy, we followed the standard waterfall methodology. Basically, we stood it up, did all our work and development, and pushed it to production.

It is always fluctuating. It seems to change every six months. Every time they come out with a new iteration, it changes. It is pretty complicated, and they should improve it.

I would absolutely recommend this solution to others. I would advise making sure that they know what they want. The biggest problem that we run into is the client not having a direction in which they want to go, or they don't have a use case to start with.

I would rate ServiceNow CMDB a nine out of ten.

CMDB is used for capturing all the IT hardware assets and configuration items. That includes computers, servers, virtual machines, phone devices, switches, et cetera. It's for the network and the front and back end.

There is a data mixer that's called Management and Commission and Discovery. What it does is it helps us auto-populate the information directly by pinging that particular CI and capturing that information. That's a very good feature. It makes it so that we don't have to go for manual updates every time.

There is a lot of documentation online regarding CMDB.

The solution is stable. 

The solution can scale to a certain extent. 

Right now, it's a one-sided integration, which means that whatever information is available in SLCN, for example, the mixer will capture the information. Therefore, there are scenarios where some of the CIs get retired. It does not really update their status. For example, We have 10 servers. Two were retired, so they were not updating anything. For the rest of the eight, they updated information. However, for the two which were retired, there needs to be a modern option for modifying the state as well in mid-server. 

The need to work on how the Virtual Machine Centers are being discovered, and how the Cloud's CI is being discovered and flagged.

The initial setup is a bit complex. 

The scalability capability could be improved. 

The pricing could be more competitive. 

The stability is good. there are no bugs or glitches. It doesn't crash or freeze. It's reliable. 

The solution is scalable, however, there is some room for improvement regarding the vCenter and the Virtual Machine Center, for which we are actually struggling right now.

In our organization, CMDB is used by everyone.

The initial implementation is a bit complex compared to other modules as it's really technical in the back end. The steps are clearly defined on how to do it and there's a use case library available. That said, it's a bit of a tedious process.

You do have to pay for a license, however, I cannot speak to the exact details. It's not part of my responsibilities. My understanding, however, is that pricing could always be better. 

I would advise that before a company starts implementing CMDB, they should look at the CSBM. They should understand CSBM as it is common, however, they need to understand the requirements, and how the structure should be set up before implementing anything. The reason being, there are scenarios where people put all the data into the system, and that causes a blockage, which means that you don't have to actually document every CI. A company should see what should be the scope of the CMDB, and only then start implementing it. Otherwise, it will be a lot of information available that serves no use. 

I'd rate the solution at an eight out of ten.

The solution has a single database, architecture, and data model. 

The tool is not user-friendly. It has a lot of features and you can get lost in it. 

I have been using the solution for six years. 

The solution is stable. 

There are about 250 users for the solution in our company. 

The product is pricey. 

I would rate the product a nine out of ten. The solution is easy to use. 

My company is a reseller, we're not the end-user. We don't have ServiceNow ourselves. We develop and we're a service provider, so we only provide ServiceNow solutions.

All areas of the solution have room for improvement. I mean, it's a never-ending thing, everything's being improved all the time. Because I'm an SME, the most important thing is the technical help that I can get, so better, more useful technical support would be good.

I also think the solution would be better if it was more intuitive.

I've only been using the solution for about six months, but the company that I work for has probably been using it for five to ten years.

The stability is about the same as other platforms. It's not better or worse than other products. It's not perfect, but it's pretty good.

The scalability of the solution is good.

It's a complex task, but the ServiceNow version is probably not any more difficult than any other platform.

You pay for the service and whatever extra features you want. If you want minimal service and don't want the extra features, you don't pay for them.

My advice for people looking into the solution would be to have a big bank account.

I rate this solution an eight out of ten. 

We use this solution to visualize the performance of all of our operation via a table that shows all of our critical surfaces.

We like that this solution allows us to easily track the relationship between our CI and the IT asset module, for troubleshooting purposes, or to check the impact of an incident site.

We would like the solution to be made more easily scalable in future updates.

We would also like to see more flexible pricing models made available that are tailored to usage.

We have been working with this solution for nearly four years.

We have found this to be a stable solution during our time using it.

This solution is scalable, but not easily.

The initial setup of the solution is straightforward as long as all of the requirements have been decided up and detailed beforehand.

We would rate this solution an eight out of ten.

We use the product to maintain the hardware inventory.

ServiceNow CMDB helps us maintain hardware. We do not have to proceed manually.

The product's most valuable feature is its ability to extract the details of organizational hardware and provide the latest setup updates.

The platform's stability needs improvement. They could add a dashboard feature as well.

We have been using ServiceNow CMDB for three years.

I rate the platform's stability a seven out of ten. It needs improvement.

We have 20 ServiceNow CMDB in our organization. It has good scalability, and we plan to increase the usage.

The initial setup has medium complexity. It can be deployed on the cloud and takes a week to complete.

We implement the product in-house.

I rate ServiceNow CMDB an eight out of ten. I recommend it to other users. I advise others to understand how the product works, different prerequisites for setup, existing network, and rules that need to be activated.

The support of the whole infrastructure is one of the main features that makes ServiceNow CMDB suitable for every type of company. It integrates with all other modules like change, business management, HR, and customer service management.

Whenever there is an issue on statuses, you can quickly resolve it.

The initial setup can be very bad if the roadmap is not set up properly. You need a specialist to help you set up the roadmap.

I've been using it for almost 8 years.

Most of the customers have the cloud solution.

It's a very stable solution.

It's very scalable. You can start from a very small size and grow. You can configure, customize, etc.

ServiceNow moves very fast to fix any problems. I would rate their technical support at ten out of ten.

Positive

CMDB is like a journey that requires a specialist's help to build your roadmap. If you get the right resource to build your roadmap, then it's very easy to launch, depending on the process of the company. If it's not properly set up, then it can be very bad.

ServiceNow CMDB is an excellent solution, and I would rate it at ten on a scale from one to ten.