What advice do you have for others considering ServiceNow CMDB?

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.

My advice to new users is that choosing the right ITSM software, like ServiceNow CMDB, depends on your specific organizational requirements. It is similar to buying a car; there are numerous options, and the choice should be based on factors such as your budget, the effort you are willing to invest, and the level of support you need. Selecting the right software isn't a decision to rush; it involves researching available options and finding the best match based on your organization's needs. I would suggest researching both the advantages and disadvantages of ServiceNow online and considering it as an option. I have worked with BMC Remedy for years, and I have noticed that ServiceNow, especially its user interface, has improved significantly. However, keep in mind that when a tool is being updated to meet current market needs, it goes through stages of development, which may take time to reach its full potential. This is similar to how traditional automakers have entered the electric vehicle market. So, while ServiceNow could be a good choice, it is important to do your homework to ensure it suits your specific requirements. Overall, I would rate ServiceNow CMDB as a seven out of ten.

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 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.

I rate ServiceNow CMDB nine out of 10.

I give the solution a nine out of ten. The CMDB is usually down for around 20 minutes during a major release or upgrade. This downtime can vary depending on the day but is usually around 15 to 20 minutes. I recommend ServiceNow as it provides complete tracking of services. We can assess if services are meeting the required standards, and the people working in the departments can track their work through requests, incidents, and changes. The solution provides visibility and compares visibility on our IT service management.

We chose ServiceNow because it has more functionalities. It takes at least one week to be trained on ServiceNow, and it is easy to learn. There are multiple plugins and integrations available in ServiceNow CMDB, and we can build the environment that we want. Therefore, I would rate this solution at eight on a scale from one to ten.

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.

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.

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.

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.

It is good to have a solid coder or programmer who understands the database and knows how to set up these queries because once that's in place, there's just a phenomenal amount of information that you can use for data and for decision making and planning. I highly recommend that. For what we use it for, ServiceNow CMDB really works out well, and I wouldn't recommend any other type of service solution. I would rate it at nine on a scale from one to ten.

I'm just a customer. I'm using the 2.0 version now. It's my understanding that they have a 3.0 version out as well. I'd recommend the resolution to other organizations. I already have in the past. I'd rate the solution at a nine out of ten.

If you are implementing ServiceNow or any CMDB solution, you have to start by properly sizing up the scope. We start at the level of the server and application, then look at the network. And after looking at the network, we turn to storage infrastructure. By working step by step, we can read your infrastructure to develop the topology of the infrastructure in your CMDB. We cannot start from scratch. It's not likely that we can build a CMDB in just a few days. All in all, I would rate ServiceNow CMBD eight out of 10.

I would advise others to go for it. I would also recommend having at least one ServiceNow administrator in the company who is certified. Its certification is not very difficult to get. If you have an IT degree, you can go for it very easily. I would rate ServiceNow CMDB an eight out of ten in spite of the fact that it was a bit frustrating to work with as a developer.

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.

We are partners with ServiceNow. I'd rate the solution at a nine out of ten. I'd advise other companies that, when you start using the tool, first, of course, you should have an architectural understanding of your organization. You need to have an understanding of what is it that you want to achieve, and an understanding of the end-to-end setup from the business to the end infrastructure layer. You want to know what you want and what you don't want, and have that well-built, and have an architectural view, and understand where your data comes in and how it comes in. CMDB can't help with that part. Don't go and expect the CMDB to do all the magic for you. You need architectural brains to blend in with the tool and that's how this whole thing works. CMDB blends very nicely if you have the architectural brain and if you have a logical understanding of what you want. Don't expect the tool to do it for you by throwing in junk and saying, "Yeah, do it for me." If you have this, you have a good process in the works already. You will be able to blend in with asset management. Config and asset work hand in glove as a second function. When you know how these two blend with each other, you know what the architectural view is, and if you have the right people and the right sense, the tool will help. If your base is weak, I don't think the other process will work at all. If you really want to go down to the topmost to the bottom-most level, there are a lot of people on the business side who swill say, "I don't understand my application landscape. I don't understand this. I don't know why do we have so many products. Why do we have this? Why do we have that?" People don't understand. However, if you have a CMDB in place that actually manifests what the entire application landscape is, it's on top to bottom very comfortably. If you don't have CMDB, you'll regret it. I have seen many times it just cost the organization real money not having it in place. There has been financial loss, revenue loss, et cetera. I've realized that if you have a good full-fledged CMDB, being involved in understanding what causes problems is not very difficult. You don't have to go searching. You can look at the devices. You can go pinpoint. We can narrow the search. What it means is we can enable faster resolutions. Obviously, you can have better and higher availability. That's the impact of a good quality CMDB. Traceability is good. You're able to pinpoint to the bottom-most of the problem. You know where to go. With CMDB you no longer say "I don't understand my IT landscape. I don't understand why we have so many applications. I don't know what we're doing." In a split second, you can actually go and say, "You know what? There's a network problem, and I know that the glitches. Please go look at it." You can go right down to that level very quickly. That's the advantage of having good quality CMDB. Good quality CMDB equals good quality data, which equals the ability to diagnose and sort out issues.

I would advise others to try to remain as out of the box as possible. It is built for the solution that you're going after. I see a lot of people who try to make it look like their previous tool, and they were leaving that previous tool for a key reason. I would rate ServiceNow CMDB a nine out of ten. There is always a little bit of room for improvements, but so far, it is much greater than what we had previously.

Any organization with a user population of 5,000 and above should consider the product as they will get a return on investment. It's not just the cost of the licenses; it's all the maturity and the efficiencies and the capability that will give them a huge return on investment. The management and control of information and the reporting capability is huge. I have worked across a number of customers, where they utilise other Service Management tool suites which do not have OOB functionality to assist the operational teams to manage stock management - this results in managing the process utilising MS Excel spreadsheets which results in poor information and management decisions. In general, I would rate the solution at a nine out of ten.

It's a good tool when it comes to RTSM, I think it has a lot of great functionality — planning. The biggest thing is communicating with the user base. It may sound a little cliche, but you're going to hear people complaining, "It's not like what we're used to." Well, we wouldn't be switching if the old situation worked. You need to get everybody on board and say, "Hey, you complain about this, this tool has that." You need to get them involved early. The sooner, the better, as far as testing, and training. Whoever signs the check is fine, but they're not the ones who are actually going to use the system. You should buy into the user community right away or near the beginning. On a scale from one to ten, I would give this solution a rating of eight.

ServiceNow CMDB works great for large and small businesses. If you're working with a vendor, just be sure it's a trusted vendor, and be sure to customize it how you want, not based on what the vendor typically does. There are some little custom, customizable modules that you can integrate into ServiceNow, but I don't have too much experience with them. I work with our ServiceNow certified tech and he knows a little bit more about what features are available or what's coming out since he's involved with training. On a scale from one to ten, I would give ServiceNow CMDB a rating of eight because it has everything I need to do my job. I don't think it's a failure of Service Now or something that they don't offer, but I haven't seen any training modules. I feel like there are things that could be automated, but we just don't know how to go about doing it.