ServiceNow ITOM Visibility and Discovery is the foundation of every CMDB driven estate. The buyer side reference. The CI tier math. The Pattern entitlement. The traps that double the renewal price.
ServiceNow ITOM Visibility licenses by managed CI count. A managed CI is a configuration item discovered, classified, and populated in the CMDB by the Discovery engine. The price moves with the CI tier, the Cloud Discovery add on, and the Pattern library scope.
The renewal traps sit in the CI count drift and the unit price uplift across tiers.
This article reads as a buyer side reference. Pair it with the ServiceNow renewal toolkit, the ServiceNow license optimization piece, the ServiceNow clause analysis, and the ServiceNow advisory practice.
ITOM Visibility sits at the core of the CMDB strategy on every ServiceNow estate. The CI count drives the price line. The CI accuracy drives the value of every dependent process from change management to incident response. The licensing footprint and the operational reality should match.
ITOM Visibility is licensed on the Now Platform under three primary metrics. Managed CI count. Cloud Discovery scope. Pattern library coverage. Each metric drives a different price line and a different renewal lever.
The managed CI is a configuration item Discovery has identified, classified, and populated with at least the required core fields. The CI count rolls up across servers, network devices, applications, storage, and cloud resources. The license unit is the count, not the discovered raw inventory.
Cloud Discovery is the connector framework for AWS, Azure, GCP, and other cloud providers. On most contracts Cloud Discovery sits in a separate SKU from the base ITOM Visibility entitlement, with its own CI tier or per cloud unit. Buyers should confirm the Cloud Discovery scope in the order form.
The Pattern library is the catalog of platform specific Discovery rules ServiceNow ships out of the box. The library covers most common operating systems, databases, middleware, and cloud services. Custom Pattern development carries professional services scope, and custom Patterns may carry separate maintenance.
ServiceNow runs tiered pricing on the CI count, with the unit price stepping up or down at each volume break. The buyer should sit just below a tier break, not just above it, to capture the best unit price.
| CI count range | Unit price tier | Typical use case | Tier break risk |
|---|---|---|---|
| Up to 25,000 | Floor tier | Mid market | Low |
| 25,000 to 100,000 | Standard tier | Large enterprise | Crossing 100K triggers the upper tier on first audit |
| 100,000 to 500,000 | Volume tier | Multi entity enterprise | Sub tier breakpoints by ServiceNow internal policy |
| 500,000 plus | Top tier | Global Fortune 500 | Discretionary discount band |
Discovered CIs accumulate over time. Decommissioned servers, retired applications, and rotated cloud workloads leave stale CIs in the CMDB. On most estates, 14 to 28 percent of the CI count is drift. The drift is fully addressable through Discovery scheduling, CI lifecycle policies, and CMDB hygiene before the renewal.
Cloud Discovery counts CIs differently from on premises Discovery. AWS EC2 instances, Azure VMs, GCP Compute instances, S3 buckets, and serverless functions each carry CI footprints that compound on dynamic estates.
The ServiceNow Pattern library covers the standard enterprise software footprint. Bespoke applications, legacy mainframe systems, and specialized network gear may require custom Patterns. Custom Pattern development sits outside the base entitlement.
ServiceNow runs a consistent renewal pattern on ITOM Visibility. The buyer should expect three traps and plan around each before the next anniversary.
The eight step checklist below moves the ITOM Visibility renewal from a passive uplift to an active negotiation. Open it at month 12 on enterprise scale estates.
Yes. ServiceNow audits ITOM Visibility usage through the platform telemetry and through periodic contract reviews. The audit pulls the discovered CI count from the CMDB and reconciles to the licensed entitlement. Buyers should run an internal CI count reconciliation every six months and apply the lifecycle policy to remove drift before the next anniversary review.
Cloud Discovery is typically priced as a separate SKU on top of the base ITOM Visibility entitlement. The price line is either per cloud account, per CI volume, or as a percentage uplift on the base. The pricing model has shifted across ServiceNow contract generations, so confirm the current commercial model with the account team at quote time.
Yes. The renewal anniversary is the moment when the CI count is reset. Run the lifecycle policy aggressively at month 11 to retire orphaned CIs. The reduced count then anchors the renewal envelope. Inside the term, ServiceNow typically does not refund for CI reduction, so the discipline is to right size before the renewal trigger.
ITOM Visibility is the foundation layer that populates the CMDB through Discovery. ITOM Health adds the event management, agent health, and proactive monitoring layer. ITOM Optimization adds the cost management and cloud financial governance layer. The three tiers stack on the same managed CI foundation and are typically licensed separately.
Crossing a CI tier breakpoint triggers a unit price step. The step can move up or down. Some breakpoints carry a volume discount. Others carry a premium for entering a higher service tier. Buyers near a breakpoint should model the unit price math both above and below the line before constraining or expanding the CI count.
Custom Patterns developed outside the standard library are not maintained by ServiceNow as part of the platform release cycle. Each platform upgrade may regress a custom Pattern. Buyers carrying material custom Pattern footprint should budget for regression testing every release and should consider converting custom Patterns to the equivalent out of the box Pattern when one becomes available.
Redress runs the ITOM Visibility renewal work as a 12 to 16 week assessment plus negotiation engagement. The work pulls the CI count baseline, identifies the drift, maps the Cloud Discovery scope, and audits the Pattern coverage. The deliverable is a rightsized renewal envelope, the contract clause set, and the renewal calendar.
Read the related Vendor Shield, the Renewal Program, the Benchmark Program, the Software Spend Assessment, the Benchmarking framework, the about us page, the management team page, the locations page, and the contact page.
A buyer side framework for the next ServiceNow renewal cycle. CI count benchmarks, ITOM tier math, Cloud Discovery scope language, and the residual clause checklist.
Used across five hundred plus enterprise software engagements. Independent. Buyer side. Built for ServiceNow customers running ITOM Visibility, Health, Optimization, and the wider Now Platform stack.
Open the white paper in your browser. Corporate email only.
Open the Paper →We pulled the discovered CI count, retired 18 percent of orphaned cloud and dev instances, repointed Discovery scheduling to production tagged workloads, and negotiated the renewal at the next tier down. The ITOM Visibility line dropped by 24 percent against the ServiceNow opening quote.
We have run 500+ engagements across 11 publishers. Every engagement starts with one conversation.
ITOM tier movement, ITSM bundle changes, Now Platform pricing patterns, custom application licensing, and the wider ServiceNow commercial leverage signals across every renewal cycle.
Once a month. Audit patterns, renewal benchmarks, vendor commercial signals across Oracle, Microsoft, SAP, Salesforce, IBM, Broadcom, AWS, Google Cloud, ServiceNow, Workday, Cisco, and the GenAI vendors. No follow up sales pressure.
Free providers (Gmail, Yahoo, Outlook) cannot subscribe. Work email only. Unsubscribe in one click.
