Configure Telecom Discrepancy Identification and Reconciliation

  • Release version: Yokohama
  • Updated January 30, 2025
  • 2 minutes to read

    • This guide outlines the steps to configure Telecom Discrepancy Identification & Reconciliation (part of TSOM Visibility) to confirm accurate discovery and resolution of 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

    Visit the ServiceNow Store 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.

    Dependencies and Requirements

    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)

    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.

    Installation

    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 or Configure Service Graph Connector for Nokia Altiplano.

    TSOM Visibility Installation Disclaimer

    See TSOM Visibility Installation Disclaimer for important information and requirements related to the installation process.

    Execution

    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 and Certification audits.

    Procedure

    1. Navigate to All > Compliance > Audits > Service Operation CMDB Compliance Audit (“cert_audit” table).
    2. Select Run Audit.
      run audit.

      It executes various scripts and operations.

    Certification Audit Logics

    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

    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.

    Subsequent Certification Audit Runs

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

    The timestamp in the Updated field in the CI Relationship table, or the timestamp in the Updated field of a Parent CI, or the timestamp in the Updated field of child CIs is later than the timestamp in the ‘Last run date’ field in the Service Operation CMDB Compliance Audit (this means that there was a change since the last audit).