A CI relationship in ServiceNow is a connection between configuration items (CIs) in your CMDB that shows how different components depend on, support, or interact with each other. These relationships create a map of your IT infrastructure, enabling impact analysis, root cause identification, and service dependency tracking. Understanding CI relationships helps you see how changes to one component might affect others across your environment.
What exactly is a CI relationship in ServiceNow?
CI relationships are directional connections that define how configuration items relate to each other within your ServiceNow CMDB. They establish parent-child connections, dependencies, and operational links between servers, applications, services, and other IT components.
These relationships form the backbone of your service mapping and enable ServiceNow to understand your IT infrastructure as an interconnected system rather than as isolated components. When you create a relationship between a server and the application running on it, you are telling ServiceNow that these items are connected and that changes to one may impact the other.
The relationships support critical ITSM processes such as change management, incident response, and service mapping. Without proper relationships, you cannot perform effective impact analysis or understand how a server outage might affect business services. This makes CI relationships particularly important for CSDM ServiceNow implementations, where proper data model alignment depends on accurate relationship mapping.
What are the different types of CI relationships you can create?
ServiceNow provides several standard relationship types that cover most infrastructure scenarios, each designed to capture specific types of connections between your IT components:
- Depends on - Shows when one CI relies on another to function properly, such as a business application depending on a database server
- Hosted on - Indicates where something physically or virtually resides, like a virtual machine hosted on a physical server
- Contains - Works in reverse to show which components exist within a larger system, such as a server containing multiple hard drives or network cards
- Runs on - Typically connects software to hardware, showing applications running on servers
- Uses - Demonstrates consumption relationships, like a service using a specific database or API
- Custom relationship types - Created for unique business scenarios or industry-specific dependencies not covered by standard options
These relationship types work together to create a comprehensive view of your IT infrastructure dependencies. While custom relationships offer flexibility for unique scenarios, using standard relationships when possible maintains compatibility with ServiceNow updates and integrations. The key is selecting the relationship type that most accurately reflects the actual connection between your CIs, as this accuracy directly impacts the effectiveness of your impact analysis and service mapping capabilities.
How do you actually create and manage CI relationships in ServiceNow?
Creating and managing CI relationships involves multiple approaches and tools within ServiceNow, each suited for different scenarios and volumes of data:
- Relationship Editor - Provides a visual interface for creating connections directly from CI records through the Relationships tab
- Direct CI record modification - Allows you to add relationships by navigating to the parent CI and using "Add Relationship" to specify the type and target
- CI Relationship table (cmdb_rel_ci) - Enables direct database manipulation for advanced users and bulk operations
- Import sets - Handle bulk relationship data from external sources or spreadsheets
- Relationship templates - Speed up creation for common patterns and ensure consistency across similar CI types
Successful relationship management requires establishing clear governance practices before creating connections. This includes documenting naming conventions, defining which teams maintain different relationship types, and creating validation processes for relationship accuracy. Regular audits help identify broken or incorrect relationships that can compromise your service mapping, while relationship templates streamline the process for frequently connected CI types. The combination of proper tooling and governance ensures your CI relationships remain accurate and valuable for impact analysis and service dependency tracking.
Why do CI relationships break and how do you fix them?
CI relationships break due to several common issues that can compromise your service mapping and impact analysis capabilities:
- Data quality problems - Include duplicate CIs, incorrect CI names, and missing required attributes that prevent proper connections
- Discovery tool conflicts - Occur when automated discovery overwrites manual relationships or creates duplicate CIs with slightly different names
- Manual configuration errors - Happen when users create relationships between wrong CIs or select incorrect relationship types
- Infrastructure changes - Result from server migrations, application updates, or decommissioning that aren't reflected in ServiceNow
- Process gaps - Arise when teams lack procedures for maintaining relationships during system changes
Fixing broken relationships requires a systematic approach that addresses both immediate issues and underlying causes. Start by using ServiceNow's data quality tools to identify orphaned or duplicate CIs, then merge duplicate records and redirect relationships to correct targets. Implement discovery rules that prevent duplicate CI creation and establish change management processes that include relationship updates. Regular relationship audits through reports that identify CIs without expected relationships or connections pointing to inactive CIs help catch problems early. This comprehensive approach ensures your CI relationships remain accurate and continue supporting effective impact analysis and service mapping.
How Data Content Manager helps with CI relationship management
We designed Data Content Manager to solve the relationship challenges that plague most ServiceNow implementations. Our Blueprint Designer lets you visually model relationship requirements without coding, making it easy to define which relationships should exist between different CI types.
The Audit Engine continuously monitors your relationship data against these blueprints, identifying missing connections, incorrect relationship types, and orphaned CIs that should be connected to your business services. You get immediate visibility into relationship gaps that could impact your service mapping and CSDM ServiceNow compliance.
Key relationship management capabilities include:
- Visual relationship modeling - Drag-and-drop blueprint creation eliminates the need for complex scripting or technical expertise
- Automated relationship auditing - Continuously identifies missing or incorrect connections against your defined standards
- Guided remediation tools - Help teams fix relationship issues through intuitive interfaces rather than technical workarounds
- CSDM-compliant templates - Accelerate proper relationship implementation with pre-built industry standards
- Relationship quality dashboards - Track improvement progress and provide visibility into relationship health over time
These capabilities work together to transform CI relationship management from a technical challenge into a streamlined business process. Our Content Planner provides visual tools that make fixing relationship deviations accessible to anyone, regardless of their ServiceNow expertise, while the automated monitoring ensures relationship quality doesn't degrade over time. This comprehensive approach helps organizations maintain accurate, maintainable relationships that truly support their ITSM processes and business objectives.
Ready to transform your CI relationship management? Book a guided trial to see how Data Content Manager can help you build accurate, maintainable relationships that support your ITSM processes.
