---
sourceDocument: Yokohama Telecommunications Service Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/telecom-service-ops

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Telecommunications Service Operations Management

ft:clusterId :

    - tsom

bundleId :

    - tsom

workflow :

    - Customer and Industry


---

# Configure telecom discrepancy reconciliation

# Configure telecom discrepancy reconciliation {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Configure Telecom Discrepancy Identification \& Reconciliation to identify and resolve discrepancies in telecom network resources within your ServiceNow CMDB/TNI instance.

## Before you begin

To use Telecom Discrepancy Identification \& Reconciliation, you need a subscription to TSOM.

Role required: admin

## Request apps on the Store {#configure-telecom-reconciliation__section_zdh_znd_b2c}

Visit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) website to view all the available apps and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html).{#configure-telecom-reconciliation__inline-send-to-store}

## Dependencies and Requirements {#configure-telecom-reconciliation__section_qdn_d4d_b2c}

TSOM Visibility plugin dependencies:

* Telecom Service Operation Core (sn_tsom_core) CMDB CI Class Models(App ID: sn_cmdb_ci_class, Type: Store)
* Expanded Model and Asset Classes Application (App ID: sn_ent, Type: Store)
* Visibility Content (App ID: sn_pattern_design, Type: Store)
* Integration Commons for CMDB (App ID: sn_cmdb_int_util, Type: Store)
* ServiceNow IntegrationHub Starter Pack Installer (Plugin ID: com.glide.hub.integration, Type: Family)
{#configure-telecom-reconciliation__ul_nt5_1rd_b2c}

Discovery Core plugin (com.snc.discovery.core), which is automatically installed by Discovery.

ITOM Discovery License plugin (**com.snc.itom.discovery.license**). You must activate this plugin.

ITOM Licensing plugin (**com.snc.itom.license**).

For more information, see [Request Discovery](https://www.servicenow.com/docs/access?context=t_ActivateTheDiscoveryPlugin&version=yokohama&pubname=yokohama-it-operations-management&ft:locale=en-US).

## Installation {#configure-telecom-reconciliation__section_mly_tx2_b2c}

The TSOM Visibility plugin (sn_tsom_core) is automatically installed with Telecommunications Discovery Patterns (sn_tsom_patterns) or with the Nokia Altiplano Service Graph Connector (sn_sgc_altiplano_connector). All logic
and system properties are installed on your ServiceNow instance.

To install TSOM Visibility plugin, see [Configure Telecommunications Discovery (TSOM) Patterns](https://servicenow-prod.fluidtopics.net/nco9q0vAZvRynA_Z0~wUfA#configuring-telecommunications-discovery-patterns "This document outlines the dependencies, requirements, and installation steps necessary for setting up Telecommunications Discovery Patterns (also known as TSOM Patterns) in TSOM Visibility in ServiceNow.") or [Configure Service Graph Connector for Nokia Altiplano](https://servicenow-prod.fluidtopics.net/apjvQ1LaZ1EysUpIAFG59Q#configuring-service-graph-connector-nokia-altiplano "Configure the Service Graph Connector for Nokia Altiplano using Guided setup to integrate network resource data from the Nokia Altiplano Access Controller (REST API) into the ServiceNow CMDB. The setup includes authentication and scheduling steps.").

## TSOM Visibility Installation Disclaimer {#configure-telecom-reconciliation__section_t2x_gx1_c2c}

See [TSOM Visibility Installation Disclaimer](https://servicenow-prod.fluidtopics.net/52X6w02p9XverOVDWjvnYw#tsom-visibility__section_wn4_2fk_b2c) for important information and requirements related to the installation process.

## Execution {#configure-telecom-reconciliation__section_d3c_xx2_b2c}

The Telecom Discrepancy Identification \& Reconciliation solution relies on CMDB Health/Compliance, which runs Certification Audits on selected tables and records in the CMDB. It operates independently of Discovery and can
be run on-demand or scheduled.

For more information about CMDB Compliance, see [CMDB Compliance](https://www.servicenow.com/docs/access?context=c_Compliance&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US) and [Certification audits](https://www.servicenow.com/docs/access?context=c_CertificationAudits&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US).

## Procedure

1. Navigate to AllComplianceAuditsService Operation CMDB Compliance Audit ("cert_audit" table).
2. Select Run Audit.  

   It executes various scripts and operations.

## Certification Audit Logics {#ariaid-title2}

Audit Results are created for each audit executed on records that matched the selection (see matching conditions in Initial Certification Audit Run).

The result's state can be certified or failed. A Follow-On Task is created for each 'failed' Audit Result record.

### Initial Certification Audit Run {#certification-audit-logics__section_kh4_ycf_b2c}

Validating specific CMDB tables for anomalies.  
The Service Operation CMDB Compliance Audit starts to run on the CI Relationship table (cmdb_rel_ci), but only on specific records with matching conditions as follows:

* Parent AND child CI classes are supported classes, including extended tables as follows:  
  slot (cmdb_ci_container_slot), subslot (cmdb_ci_container_subslot), card (cmdb_ci_interface_card), interface (cmdb_ci_ni_interface), telco equipment (cmdb_ci_ni_telco_equipment), IP switch (cmdb_ci_ip_switch), and IP router (cmdb_ci_ip_router).  
  Note:  
  These properties can be configured via sn_tsom_core.audit.\* system properties.
* Parent OR child is created or updated by Discovery (discovery_source = SG-Altiplano, ServiceNow).  
  Note:  
  This property can be configured in the sn_tsom_core.audit.discovery_sources system property.
* Parent AND child life-cycle Stage is Operational.
* The CI Relationship Type is Contains::Contained By.  
  Note:  
  This property can be configured in the sn_tsom_core.audit.relationship_types system property.
{#certification-audit-logics__ul_f3v_tdf_b2c}

### Subsequent Certification Audit Runs {#certification-audit-logics__section_i5h_j2f_b2c}

Follows the same logic as the Initial Certification Audit Run, but with the following additional matching selection criteria:

The audit runs when the Updated field timestamp in the CI Relationship table, Parent CI, or child CIs is
later than the Last run date field timestamp in the Service Operation CMDB Compliance Audit. This indicates a change since the last audit.

*[\>]: and then