The UCMDB has illuminated the organization to the fact that our data is managed too manually and distributed in a myriad of spreadsheets. This product discovers, maps and reports information about our configuration on a daily basis. We use it for datacenter migrations and for audit purposes. The company is starting to realize that we really don’t have a source of truth for audit purposes and this product is capable of being that. View full review »

It is easy to manage IT assets and offers auto-discovery.

View full review »

Any organization can take advantage of the Automated Service Modelling (ASM) feature to discovery the dynamic changing environment and keep the business service view (dependency mapping) up-to-date, hence missing out the newly added CI for a given business service.

View full review »

UCMDB data is helpful with correlating events, which helps to reduce the number of events to the end user. It also help with business-level mapping to provide high level visibility related to the health of business applications. 

In a large heterogeneous environment, you can have multiple distributed probe servers which can collect data into each region and send it over the central nodes to avoid firewall and DMZ issues. This make the discovery process more dynamic and real-time.

The latest version of UCMDB 10.33 has an autodiscovering capability. 

View full review »

In terms of data quality and process ticketing, it is helpful. For instance, if you have a number of service desk tickets coming in and you have to refer to a system, a product, or an application interface, it is backed up by information from this database for reference. Everyone references the same thing. It terms of financial management, you can pile up the costs and the value because you have “service trees”. All these configuration items (CIs) are in there and that's the advantage. Everyone is looking at the same platform.

View full review »

It has allowed us to centralise the feeds and sources. Previously, like many companies, we stored CMS data in various places and various systems, and they did not always match.

View full review »