ServiceNow CMDB Reviews

I use ServiceNow CMDB in my company to deal with areas like incidents, problems, and change management.

I use ServiceNow CMDB in my company to deal with all the equipment inventories and our infrastructure, along with all the CIs attached to the different things, like maybe if you are involved in the area revolving around incidents, service requests, or change requests.

With ServiceNow CMDB, the properties of the servers and CIs are important as you use them in our organization, and if any changes happen, then we need to update that immediately, and then we can recall whatever changes are made on CIs and track them. The aforementioned details consist of the feature my company uses the most in ServiceNow CMDB.

I don't currently see any problems with ServiceNow CMDB since everything works fine.

If I click on some particular CIs at the moment, all the information related to that CI appears by default. Right now, if there is something in our company we need to generate with the report, we can click on any of the searches for CI options, and all the relevant and recent incidents, changes, or anything that has happened should come on to at the bottom of the list displayed by the tool, which would be nice. If you select any CI, the associated applications with that CI should also be made available for users since, currently, the tool lacks such a feature.

I have five to six years of experience with ServiceNow CMDB.

It is a stable solution. Stability-wise, I rate the solution an eight to nine out of ten.

It is a scalable solution. Scalability-wise, I rate the solution an eight to nine out of ten.

There are around 10,000 users of the solution in my company.

My company already has a technical team to solve our problems related to the solution. Maybe the technical team in our company will reach out to ServiceNow's technical support team for help.

The product's initial setup phase was simple.

The solution is deployed on the cloud.

The product price falls on the higher side of the spectrum.

The user interface of ServiceNow CMDB is fine since you can customize it depending on your needs.

I recommend the product to others who plan to use it, as the solution's prices are okay.

I rate the overall product an eight out of ten.

ServiceNow CMDB is used for incident management, request management, service mapping, and discovery.

ServiceNow CMDB is a single data model where we can capture attributes. We can have a tree structure with ServiceNow CMDB, which makes it very powerful. We can use ServiceNow CMDB to create more tables that can provide granular information.

ServiceNow CMDB may face performance issues if we try to make the solution too large by adding more CIs.

I have been using ServiceNow CMDB for more than five years.

ServiceNow CMDB is very stable.

I rate ServiceNow CMDB a nine out of ten for stability.

ServiceNow CMDB is enormously scalable. You can store millions of CIs (Configuration Items) in ServiceNow CMDB.

I rate ServiceNow CMDB a nine out of ten for scalability.

The solution’s initial setup is very simple.

I rate ServiceNow CMDB a nine out of ten for its ease of initial setup.

ServiceNow CMDB's deployment time depends on the data, but it doesn't take much time. It's quite fast.

ServiceNow CMDB is deployed on-cloud in our organization. I advise users to have a good conceptual understanding of CMDB (Configuration Management Database). First, you need to understand what your assets are, and on top of that, you can create your building.

It's quite easy to implement ServiceNow CMDB for any new project. The solution is quite easy to use and get reports from. It's quite easy to import data in ServiceNow CMDB.

Overall, I rate ServiceNow CMDB a nine out of ten.

CMDB provides a centralized repository for your assets and support representatives throughout the organization.

It depends on the implementation, but the out-of-the-box product tends to be fixed on the support people. From a linear standpoint, I would like to see a certain number of fields on a table and a related list to describe the support personnel.

You can specify leads and responsible personnel. If there were a related list with the job function responsibility and that person's user ID, it could be a dynamic list instead of a fixed one where we have to create columns on a table. I would like to see that functionality out of the box. 

I have used CMDB for five years.

I rate CMDB nine out of 10. ServiceNow products are stable overall. 

I think the scalability is excellent because of the way it's implemented. That said, I would like to see tighter integration with Active Directory, so we get automated reports as people join or leave the organization. That is something we can develop, but it would be nice to have that out of the box.

I rate CMDB seven out of 10 for ease of setup. You have to go through discovery to populate your assets and build out the relationships. That's normal. It takes some additional work, and every installation is different. 

The initial deployment is pretty quick, but the configuration takes additional time, and you need some buy-in from other departments. That process varies. It might be straightforward, or it can be the roadblock to getting things done correctly.

The setup may involve 10  to 15 people because you may need to reach out to other teams to get the data you need. If you're doing a standard deployment that's simply laying the foundation and you have all the information ahead of time, you could get this done in under a month. That's allowing time to address any issues or necessary configuration changes.

I rate ServiceNow CMDB eight out of 10. The foundation is good, but there's always room for improvement.  I think they're addressing the issues, so I'll give them an eight to be on the positive side. CMDB is your foundation. If you get that right, it makes the rest of your ServiceNow deployment go easier.

I am an SME specialist, and we primarily work with government customers who use ServiceNow systems. When they require a CMDB specialist, I am assigned to those sites.

We have customers who deploy the solution on-premises, while others use the ServiceNow cloud.

The issue with UCMDB is that it lacks integration with other solutions, particularly with service management components. On the other hand, ServiceNow excels in integration and is considered the best tool in the market for this purpose. Although it may not be as proficient in discovery as some other tools, its actual integration capabilities surpass all others.

The discovery process and service mapping could be improved. I prefer a more comprehensive approach to discovery and simplified service modeling.

Technical support has room for improvement.

I have been using ServiceNow CMDB for one and a half years.

I would rate the stability a seven out of ten. The discovery process with ServiceNow occasionally fails, and it is quite challenging to identify the cause. There are no clear indications, but restarting the mid servers usually resolves the issue. This problem may stem from pro servers, mixed servers, or various applications.

I would rate the scalability as an eight out of ten. The only drawback is the performance issue we encounter when scaling up.

The technical support is not great.

Neutral

The initial setup is complicated, but compared to other solutions, it is not more difficult. I would rate the deployment an eight out of ten.

The deployment process typically takes around three to four hours. The solution includes a built-in wizard to assist with the deployment, with the only challenging step being the mid-server phase.

I would rate ServiceNow CMDB an eight out of ten. While it remains a strong product, there is still room for development in terms of discovery and service modeling to catch up to its competitors. Nonetheless, it is currently the best option available.

In some instances, our clients are medium-sized businesses, but the majority are at an enterprise level, with thousands of users.

Overall, ServiceNow CMDB is the best option in the market due to its seamless integration with other systems. However, it is not the best discovery tool. UCMDB is a superior discovery tool, but it lacks integration and does not work well with other parts.

I use ServiceNow for tracking infrastructure procurement and all the configuration items on a particular network. It tracks the maintenance and everything related to configuration management. We have about 20,000 employees and a team of personnel that works with ServiceNow.

Everything is now in one system. Employees submit service and change requests. It all goes through ServiceNow.

I deal mostly with asset management, and ServiceNow helps me do my job more effectively. 

I'm still learning about CMDB's capabilities, so I haven't seen anything that I want added yet. 

I've been working with ServiceNow since January.

ServiceNow is stable.

I don't have admin rights, so I can't do anything to affect a lot of change in the scalability. I only deal with the asset management part, and I haven't had any problems adding to the system. When assets come within my particular AO, my task is to add them to the configuration management database, and I haven't had any issues.

We previously used CyrusOne for configuration management. We switched to ServiceNow, the platform of choice for our client, and they want everyone to be on the same page. At the same time, ServiceNow does everything we want to do and has room for growth. 

Setting up ServiceNow was straightforward. We had a smooth onboarding process, and they provided training for the system admins as part of the package for this system and implementation.

I rate ServiceNow CMDB nine out of 10. I recommend ServiceNow because it meets all our configuration management needs. It gives us everything that we need to have based on our IT requirements.

I've used it for managing client inventories and infrastructure to ensure that the relationship among various CIs is managed. I've also used it to troubleshoot quickly and handle change.

It's not too difficult to configure with regard to the UI. My experience working with ServiceNow CMDB has been a very comfortable one.

Definitely, the price needs to be lower because there are clients that I work with who cannot afford ServiceNow. I have to end up proposing alternate solutions to fit their budget.

I've worked with this solution for about six years now.

It is mostly a cloud solution.

It is a stable solution.

It is scalable.

When we needed help, they've always been available. We've not had issues though.

You do need skilled people for the initial setup, but it's not too difficult to work with.

Typically, the deployment of ServiceNow for the various organizations that we have worked with has spanned between one to three months.

We are integrators ourselves and implemented it.

In comparison to the cost of other solutions, you get value for your money with ServiceNow CMDB. It could definitely be cheaper though.

ServiceNow is very intuitive and is a market leader. I used to use BMC Remedy before, which had a traditional type of deployment. ServiceNow is quick to start up because it's on the cloud. It has ready-to-use use cases available for deployment. So, the deployment is much faster than it used to be on Remedy. 

There's a whole lot of automation that comes with ServiceNow, so I'd definitely recommend it.

At present, I would rate ServiceNow at ten on a scale from one to ten.

ServiceNow CMDB is fully integrated and complete. ServiceNow has modules for everything an IT service company needs, and it's flexible. 

While ServiceNow CMDB is flexible and comprehensive, it's also difficult to implement and requires a lot of customization. 

In order to fully leverage ServiceNow CMDB, you need ServiceNow Discovery and some other ServiceNow solutions. It's expensive to purchase all of these. We're negotiating with ServiceNow, but we're thinking about replacing it with another CMDB solution. 

I have used ServiceNow CMDB for six years.

I rate ServiceNow CMDB five out of 10 for ease of setup. The installation was complex in our organization because we are providing services to many other companies. The plain vanilla implementation should be easy. If you need to customize the solution, you must have people who understand how to do that. ts.

One manager and four data analysts oversee ServiceNow. Their job is to do customizations. When we onboard new clients, we have to customize ServiceNow to meet their requirements. We set up separate workflows on various instances for each client. It requires little maintenance if you aren't customizing it. 

I rate ServiceNow CMDB two out of 10 for affordability.  The licensing model is complex. Due to contract restrictions, I'm unable to see how much we pay, but it's calculated based on the number of users, modules, and license types. 

I rate ServiceNow CMDB seven out of 10. It's a complete solution, and it's ideal if you have a complex environment. However, before implementing something as complicated and costly as ServiceNow, you should consider if you need it. 

A simpler, less expensive solution might work fine for you. If you only need basic CMDB features, such as registering incidents and changes, other tools are much simpler than ServiceNow. A large organization with complex requirements will get the most value out of ServiceNow. 

ServiceNow CMDB is not being used that much in the company. It's being used by customers, and mostly 90% are enterprise customers. The tool is used by many for IT assets, for example, PCs, printers, and applications. It's not just used for trouble ticketing. ServiceNow CMDB is used to manage the entire IT asset.

As I work based on the IT governance framework, what I like best about ServiceNow CMDB is ITSM, so incident/service request management. I also like that it can be useful for project portfolio management.

An area for improvement in ServiceNow is the reporting because there are reporting features that would be better when done within the platform, rather than having to buy the performance analytics model. There is a greater difference between the dashboarding that you can do from the platform versus what's on the performance analytics model. Some of the features currently available within performance analytics would be good to have within the platform because sometimes, customers will say that the tool is okay, but it's not enough, so you'll need to go with the performance analytics model, and that's costly.

The problem is that paying extra for performance analytics costs too much for what it can give back. Customers don't need the entire functionality delivered by performance analytics, but the default functionalities within the platform are not enough. There is always a trade-off. Customers are not getting value for money paid for the performance analytics model because they don't use the whole set of functionalities, and that is the problem.

For the time being, there isn't an additional feature I'd like to see in the next release of the tool.

I've been using ServiceNow CMDB for six years now.

ServiceNow CMDB is a very stable solution.

Technical support for ServiceNow was perfect. They provided a very high level of support.

The market sees ServiceNow as the Ferrari in terms of pricing. It's at the very top, and its cost is very, very high. If a customer is considering an alternative platform due to pricing, so I looked at Jira. It's clear that ServiceNow provides much more, but sometimes, you need a trade-off between customer requirements and what's on the platform.

If customers were to switch from ServiceNow to Jira, it would be because of pricing. Feature-wise, the two are almost equivalent. Everything you find in Jira, you can find in ServiceNow, but not everything you find in ServiceNow is in Jira, especially in terms of flexibility. One of the key points of ServiceNow is that when you want to downscale and you belong in a smaller organization, it becomes too costly. Pricing may change more in ServiceNow and ManageEngine, for example, but not that much in Jira. Downscaling in ServiceNow for a smaller organization is too costly, so they need to create a shrink-wrapped package specifically for smaller organizations, rather than delivering too much and costing too much.

On a scale of one to five, with one being the worst pricing, and five being competitively priced, in particular, not cheap, but competitively priced, I'm scoring ServiceNow a two because it's very expensive in the marketplace. If they can make some changes to their pricing packages, it would be much better.

I use ServiceNow CMDB, but understand that I work in a delivery company, a service company. The company drafted a partnership with ServiceNow six years ago and is still a partner, particularly a premier partner.

I'm giving ServiceNow CMDB the best score, ten out of ten.