---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Data collection and aggregation

# Data collection and aggregation for licensing process {#ariaid-title1}

* Release version: Yokohama
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

ITOM/OT SU Licensing application counts CIs for ITOM applications and uses a daily average count for the last 90 days to produce license statistics for purchased subscription units.

ServiceNow charges for various ITOM applications, including ITOM Visibility, ITOM
Discovery, ITOM Health, Health Log Analytics, ITOM Cloud Accelerate, and ITOM Optimization. For specific information about the products and features covered by ITOM subscriptions, see [Subscriptions for IT Operations Management](https://servicenow-prod.fluidtopics.net/8SXHzsFWgWtMiIqV0LxxMQ "The ServiceNow AI Platform uses a licensing method where your organization is billed for using the following IT Operations Management products: ServiceNow ITOM Visibility, ServiceNow ITOM Discovery, ServiceNow ITOM Health, ServiceNow Health Log Analytics, ServiceNow ITOM Optimization, and ServiceNow ITOM Cloud Accelerate.").  
The process of collecting and aggregating information for licensing purposes involves the following steps:

1. The ITOM licensing mechanism counts the Configuration Items (CIs) managed by each ITOM product daily, categorizing them into licensable CI categories. For more details, see [KB0748149: ITOM Subscription Unit license calculation logic](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0748149).
2. If the same CIs are managed by different features within the same ITOM products, the CI count is adjusted to eliminate the duplication. For example, if both Discovery and Service Mapping discover the same CIs, these CIs appear only once in the CI count. Container CIs are excluded from SU count if they have a relationship to a container image.
3. The licensing module aggregates CI counts from ITOM applications to determine the average daily CI count for the last 90 days.
4. The licensing module then compares the daily average CI counts for the last 90 days from ITOM applications with the licensing information in the customer contract to generate license statistics.

{#data-collection-aggregation-licensing-process__ol_qwc_ksc_fhb}As a result, you can view the statistics on how your organization uses purchased subscription units. Figure 1. ITOM application license flow