We use ServiceNow CMDB to manage assets and automate related tasks that were previously performed manually. We've integrated CMDB with our EDR solutions to discover assets, allowing us to use ServiceNow to support incident management. 

About 15 people use CMDB to manage assets throughout the business, but it is also used by incident and request managers. The change management team is part of that. In total, we have around 75 to 100 people directly interacting with the CMDB. 

CMTB is an excellent configuration management tool that helps keep track of all configuration items across departments and organizations. The solution is also integrated with ServiceNow, making it easy to raise incidents, changes, and problems.

We use it to support change management.

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.

We use the ServiceNow CMDB to keep track of users and assets.

We use it for ticketing. We use it for quite a few things. We have a Knowledge base. We do incidents, we do requests. The CMDB looks at assets — what's tracked if those assets are terminated in use? It pretty much does all of our backend processes. For instance, if there's a request for software on a machine, It looks at the CMDB, checks if that machine is real, and checks what assets are tied to it. Most importantly, it checks what buffer instances and asset tracking is tied to it.

Every user in our company has access to it, and it's a global company. If I had to estimate, I'd say there are roughly 80,000 to 100,000 users.

A lot of our users use it for simple tasks, like submitting incidents or creating requests. Since we outsourced the help desk, the help desk uses it for initial triage, escalation, etc. I use it for reporting asset tracking. Everyone has various uses for it.

We use ServiceNow CMDB mainly for all the CIs. For example, we have to show assets for desktops. We actually can get the last logged-in instance through our SCCM product from Microsoft. We can run that actual report against all asset inventories, and that provides us with information on who the last user is and which device is actually in use.
That's been one of our audit control measures just through referencing all our CIs. Also, if we have any change tickets, any incidents, we can register that against the CI. Then, we can see the profile, how many tickets have been in place with regard to different environments, and the different hardware components.

My main use cases for ServiceNow CMDB involve effectively managing CIs in an organization's IT landscape, which can span a wide array of assets, from end-user computers to telecommunications systems. Essentially, it serves as a centralized repository for capturing and monitoring all the assets utilized within a typical office setup, encompassing servers, network equipment, and more. This repository is where all this crucial information is stored.

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

We primarily use ServiceNow for asset management. We feed our on-prem and cloud inventory into ServiceNow CMDB. We also use it for event management together with Micro Focus Operations Bridge Manager. 

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.

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.

Implemented into DWP to manage all technical towers including the EUC tower that manages 120,000 x users. 

We use it for network and server discovery, and storage.

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.

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.

I'm looking at ServiceNow from the standpoint of things like technical services, business services, mapping, deployments, rolling up inventory to those mapped deployments, and doing application services, which takes your inventory and spreads it across all your instantiations.

We are more oriented toward cost control and multiple instantiations of the same product across multiple locations; basically, multiple data setting environments to thousands of deployments.

We'll deploy to our customers and host their equipment. Our customers subscribe to our equipment and we sell our software, but rarely do we sell our software. Basically, our customers pay us monthly to host their software and keep it updated. Our huge customers, companies like Bank of America and Wells Fargo kind of huge, get us to host their equipment. Otherwise, for smaller clients, run on our ASP configuration.

When I was a student, I worked on a prototype for an app, and my main tasks were directly in CMDB. I had done a synchronization implementation to retrieve inventories from Excel files and put them into CMDB with automation.

I also used it in my previous company. This company is a supplier of ServiceNow for several clients in Canada and the USA, and we did a lot of customization and configuration for the clients. We worked with all ServiceNow platforms and not only with CMDB. If you want ServiceNow within your company, you've got to find a supplier or go with ServiceNow directly. 

It was on-premises, but ServiceNow is cloud-based. It is software as a platform. 

We are just capturing all the services in CMDB, however, we can use that as a part of the change, incident, or problem management. We are just keeping configuration items like hardware and cloud resources like AWS and other infrastructure as on-prem cloud infrastructure. 

We are using it as the foundation of the ServiceNow platform. It allows you to mature other processes such as ITSM, ISAM, and security operations. It is a SaaS solution.

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.

For one of our current customers, they have prepared the CMDB by manually importing the JIRA data from their existing infrastructure —the data module, services, servers, application servers, database, database container, and database data—and they've asked us to handle the application business. 

The customer has two repositories. The first is for modeling the application architecture. The second is for delivery management as well as integrating the data between the release control platform and our platform for business applications. And from this one, we support only the relationships between the CIs and we have produced a mapping to update the relationship between all the CIs.

In the past, when working for a banking client, we adopted two different types of deployments based on our customer's needs. The first one was improvised and the second one was in the cloud. We had to do mapping between discovery and the CMDB service BMC because they did not previously have CMDB or ServiceNow. We closed the assets activity between BMC and ServiceNow platform. 

We have thousands of users engaged in a wide range of activities around the solution, such as the infrastructure and request management team. We're working with many plugins and a lot of features.

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.

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.

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

We use CMDB as a core solution for storing objects. You can still use your server information, your network information, all the characteristics of an infrastructure object, and use CMDB. We use it to provide reporting, change in management, and so forth.

We do a lot of stuff around Mapping. We do Discovery. We do Identification/Reconciliation rules. We do the Transforms and stuff like that. Then, we validate the CMDB Health dashboard and stuff like that. That's predominantly the main work that we do around the CMDB and the data ingestion kind of stuff.

We use the product to maintain the hardware inventory.