CMDB 360: Bringing Multisource CI Data Together

Here's something that frustrates a lot of ServiceNow teams: you've got ServiceNow Discovery running, SCCM feeding data in, maybe a third-party tool on top of that, and each one is reporting a slightly different value for the same CI attribute. The CMDB picks a winner based on reconciliation rules and writes one value to the record. But what happened to everything else? Where did all those other values go?

That's exactly the gap that CMDB 360 ServiceNow was built to close. It doesn't replace the reconciliation process. It makes the whole thing visible, source by source, attribute by attribute, so you're not just trusting a golden record you can't trace.

What Is CMDB 360 in ServiceNow?

CMDB 360 is a feature offered by ServiceNow which takes the concept of CMDB further to keep a record of what every source has discovered about every CI, and not just the value which was reconciled. Standard CMDB tables maintain just the one reconciled value while CMDB 360 maintains records of all values discovered, when they were discovered, and how they related to what was reconciled in the CMDB.

Since Utah version onwards, CMDB 360 was introduced as the overall package of the previous "Multisource CMDB" along with the analytics dashboards and queries. The whole package is available from the CMDB Workspace in the CMDB 360 view and the data is stored in the table cmdb_multisource_data.

Why Do Businesses Need a Multisource CMDB?

Most organisations don't have a single source of truth for their CI data; they have several. Discovery tools, SCCM, cloud management platforms, manual imports, all of them are touching the same CMDB, writing the same attributes, sometimes with conflicting values. Without CMDB 360 multisource CMDB visibility, you're flying blind on data quality. You can see what the CMDB says, but not whether that value is reliable, whether a key source has stopped reporting, or whether two tools fundamentally disagree on something important like an OS version or an IP address.

That lack of visibility is what leads to trust issues with the CMDB; teams stop relying on it because they've been burned by bad data they couldn't trace. CMDB 360 gives you the audit trail to actually investigate and fix those problems.If you are following Service Graph CMDB best practices, CMDB 360 supports that approach by providing source-level transparency that makes reconciliation rules auditable and easier to trust. 

How Does CMDB 360 Work With Multiple CI Data Sources?

The flow from raw source data to what you see in CMDB 360 looks like this:

Data Sources (Discovery, SCCM, cloud tools, import sets) → IRE (Identification and Reconciliation Engine) → CMDB (reconciled golden record written to CI) → CMDB 360 (all source values retained in cmdb_multisource_data) → Source comparison (side-by-side view per attribute) → Reconciliation review (investigate conflicts, adjust rules, recompute)

Each discovery source contributes attribute values to the IRE. The IRE applies reconciliation rules, based on source priority, to decide which value gets written to the CI record. The source with the lowest priority number wins. So if SCCM has a priority of 100 and ServiceNow Discovery has a priority of 200, SCCM's value takes the CI attribute.

Previously, the values from lower-priority sources were simply discarded at this point. With CMDB 360 enabled, those values are stored. The cmdb_multisource_data table holds a record for every source-CI combination, and the sys_multisource_attribute_value table holds the per-attribute values each source reported. There's also sys_multisource_raw_payload, which stores the raw data before it goes through the Robust Transform Engine, useful for troubleshooting when something unexpected gets written to the CMDB.

On a CI form, the CMDB 360 Data Preview related link shows you the current CMDB value and all the incoming values from other sources for each attribute, side by side. Values that match the winning reconciled value are highlighted in green. This is where you can quickly see if two sources disagree, and by how much.

What Can You Do With CMDB 360 Queries?

The CMDB 360 view in CMDB Workspace has a query builder built into it. CMDB 360 queries let you slice through multisource data in ways that standard CMDB reporting can't. There are three query types:

• Get Records - finds CIs that are being reported by one or more specific sources. Useful for understanding coverage: which sources are actively contributing data, and to how many CIs.
• Find Gap - finds CIs that some sources are reporting but others are not. This is how you spot when a discovery tool has stopped picking up a CI that it previously covered, a common early sign of a stale or broken integration.
• Compare Attribute Values - finds CIs where sources report different values for the same attribute, or where a source value doesn't match what's currently in the CMDB. For example: find all Windows servers where SCCM and ServiceNow Discovery are reporting different OS versions.

You can save queries and schedule them as reports that plug into the standard ServiceNow Reporting platform. The Saved Queries card in CMDB 360 shows up to 20 queries at a time, and you can filter results by application service, technical service or CMDB group to narrow down what you're looking at.

How Do Reconciliation Rules Work With CMDB 360?

The Reconciliation Rules define what value from the multiple sources will be saved in the CMDB in case the same attribute is provided by several sources. In this scenario, the reconciliation works behind-the-scenes: the proper value will be saved, yet it is difficult to verify this process or detect possible problems that require adjusting the rules.

CMDB 360 adds two important capabilities on top of reconciliation. First, the Preview Data tab on the Reconciliation Rules page in CI Class Manager shows you, in advance, which sources can update each attribute and in what priority order, before you commit to a rule change. Second, in case you have determined that one of the sources has provided incorrect information and would like to undo its contribution, you can ignore this source and initiate the recompute procedure. In such a way, the IRE will refer to sys_multisource_attribute_value, select the highest priority active source of each affected attribute, and write its value into the CMDB.

This reversion capability matters a lot when a new discovery tool gets added to the environment. You can validate it by running a Compare Attribute Values query against existing trusted sources before giving it any real reconciliation weight, essentially a dry run, without touching production CI records.

How Do You Enable CMDB 360 in ServiceNow?

CMDB 360 requires an ITOM Discovery licence and is off by default. Worth noting: the CMDB 360 plugin ServiceNow functionality is built into the platform from Utah onwards, you don't install a separate Store plugin, you just activate the right licence and flip the system properties. Here's the process:

1. Make sure the ITOM Discovery Licence plugin is active on your instance.
2. Go to Configuration > CMDB 360 Properties (or search for sys_properties) and set glide.identification_engine.multisource_enabled to true. This is the master switch.
3. CMDB CI classes are tracked by default once the master switch is on (glide.identification_engine.multisource_cmdb_ci_enabled defaults to true). Non-CMDB classes default to false; enable separately if needed.
4. Optionally, exclude specific CI classes from CMDB 360 tracking to manage table size.
5. For logging, add glide.cmdb.logger.source.cmdb_multisource and search the syslog table with source="cmdb_multisource" to monitor activity.

Only users with the admin or cmdb_ms_admin role can change these properties. Once enabled, historical data isn't backfilled; CMDB 360 only captures source data from that point forward, so the sooner you switch it on, the more useful your audit trail becomes. For detailed setup guidance from the ServiceNow Developers at Dotsquares, it's worth reviewing your IRE configuration before enabling, to make sure source priorities are set correctly from day one.

When Should Your Organisation Use CMDB 360?

Enabling CMDB 360 can be useful under any of the following conditions in your environment:

• You have multiple sources contributing data to CI classes, which is true for nearly all companies with ServiceNow Discovery in addition to SCCM, Intune, or cloud services.
• You do not have total trust in your CMDB; if you see employees bypassing CMDB and looking at the values in source systems, it shows that the process of reconciliation is too invisible.
• You have just onboarded a new discovery tool and want to make sure of the quality of its data before assigning it a higher reconciliation priority than other sources that are trusted.
• You have encountered some incidents due to inaccurate data about CIs and need an audit trail that will show where an incorrect value was entered and by what source.
• You plan to use ServiceNow CMDB Health Scoring and Compliance Reporting, CMDB 360 provides data feeds for coverage and conflicts metrics that help to understand the state of your CMDB better than just a reconciled record.

FAQs

What is CMDB 360 in ServiceNow?

CMDB 360 is a ServiceNow feature that retains the attribute values reported by every active discovery source for each CI, not just the winning reconciled value. It gives you source-level visibility, attribute comparison across sources, query tools, and an analytics dashboard in CMDB Workspace.

What is a multisource CMDB?

A multisource CMDB is one where multiple discovery tools and data sources, such as ServiceNow Discovery, SCCM and cloud management platforms, all contribute attribute data to the same CI records. CMDB 360 is the ServiceNow capability that makes this multisource environment manageable by tracking what each source reports.

What are CMDB 360 queries used for?

CMDB 360 queries let you interrogate multisource data in CMDB Workspace. The three types, Get Records, Find Gap and Compare Attribute Values, help you audit discovery source coverage, spot tools that have stopped reporting, and identify where sources disagree on CI attribute values.

What is the difference between CMDB and CMDB 360?

The standard CMDB stores one reconciled value per attribute per CI, the golden record. CMDB 360 sits alongside it and stores every value that every active source reported, giving you a full audit trail of where each attribute value came from and what other sources said.

How do you enable CMDB 360 in ServiceNow?

CMDB 360 requires an active ITOM Discovery licence. Enable it by setting glide.identification_engine.multisource_enabled to true in CMDB 360 Properties. Only users with the admin or cmdb_ms_admin role can make this change, and tracking begins from the point of activation; there is no historical backfill.