---
sourceDocument: Xanadu IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/xanadu/it-operations-management

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Discover related items together with the main CI

# Discover related items
together with the main CI {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Add related items to the patterns to perform horizontal discovery of configuration
items with all their related items: CIs or non-CIs, like ports or serial
numbers.

## Before you begin

1. (Optional) Check if the CI is dependent: The system uses the identification rules to identify the CI independently of other CIs. Refer to [Create or edit a CI
   identification rule](https://www.servicenow.com/docs/access?context=t_CreateCIIdentificationRule&version=xanadu&pubname=xanadu-servicenow-platform&ft:locale=en-US).
2. (Optional) To understand the model better, check dependent relationship rules which define the dependency structure of the CI types and the relationship types in these service definitions. For example, you can discover a Tomcat server with Tomcat WARs belonging to it. For more information, refer to [Dependent relationship
   rules](https://www.servicenow.com/docs/access?context=c_ServiceRulesMetadata&version=xanadu&pubname=xanadu-servicenow-platform&ft:locale=en-US). Figure 1. Example of the Containment rule for Tomcat WAR   

3. To add a non-CI to the pattern, add it as a related item for the CI type to which the main CI belongs. For more information on adding related items for the CI type, see [Configure references to other CIs or non-CIs as related items for the CI
   type](https://www.servicenow.com/docs/pebZEhrK0VaFEN~kOWMStw#t_CreateCITypeForSM__configure-ci-related-items).
Role required: pd_admin

## About this task

Related items, both CIs and non-CIs, serve as a reference and provide additional information about the CI. For example, you can define a serial number, a port and an network APR table as related items for a hardware server. The system does not use these items for identification. After you configure related items for the CI type, you can use horizontal discovery for CIs of this type together with their related items.  
Note:  
Non-CIs are items that do not extend the Configuration Item \[cmdb_ci\] table. Examples of non-CIs are ports, serial numbers, or Network ARP tables.

Pattern Designer displays attributes of related CI types, which you added to the
pattern in the CI attributes pane. You can view and use these attributes while
creating or modifying the main CI pattern.

## Procedure

1. Navigate to AllPattern DesignerDiscovery Patterns.
2. Select the relevant pattern.
3. On the pattern form, select the relevant identification section.
4. Make sure that you are not in Debug mode.
5. On the CI Attributes pane, click the Manage related CIs icon.  

   <br />

6. Select the relevant related CI type.  
   You can use the search box to locate a specific CI type.
7. Click the Plus icon.  
   The new related CI type is added to the list.
8. **Optional:** Add other related CI types.
9. Click OK.  
   New tabs for related CI types you added appear under the tab for the main CI:   

## What to do next

Continue editing the pattern by adding more steps as necessary. To view or use attributes of a related CI type, click the relevant tab in the CI Attributes pane.
**Previous topic:** [Create or customize patterns](https://www.servicenow.com/docs/GWNV0U7O6aEuFL7fQGlPqw "Create or modify a discovery pattern and define its basic attributes.")  
**Next topic:** [Enhance patterns without changing their identification sections](https://www.servicenow.com/docs/RXfS5quVBkH8U7Cl6ZKS7w "Enable patterns to search for additional attributes and modify pattern discovery logic defined in identification sections by using extension sections. Each extension section contains a preconfigured set of discovery steps referred to as a shared library.")

*[\>]: and then