Skip to content
Telecommunications Service Operations Management
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Using Telecommunications Service Operations Management

Use Telecommunications Service Operations Management (TSOM) to proactively monitor telecom services, validate data integrity, and reconcile discrepancies across network inventory and discovery sources. TSOM enables operations teams to maintain an accurate telecom-aware CMDB and act on real-time network insights.

Common operational tasks of TSOM

Once TSOM is configured, you can use its capabilities to:

  • Run Telecom Discrepancy audits: Identify inconsistencies in network relationships and configurations by running certification audits based on discovered data and reconciliation rules.
  • Validate attribute value mismatches in CMDB 360: Use the Attribute Value Discrepancy feature in CMDB 360 to compare attribute values across different discovery sources and detect conflicts or outdated records.
  • Use Telecom Discovery Patterns: Apply Telecom Discovery Patterns to accurately discover and populate telecom-specific Configuration Items (CIs) and their relationships.
  • Run and verify import jobs from service graph connectors: Manually trigger import schedules (e.g., for the Nokia Altiplano connector) to verify that topology and device data is successfully imported into the CMDB and mapped to the correct CI classes.

These tasks help verify that your telecom network is continuously synchronized, accurate, and operationally visible within ServiceNow.

  • Use Telecom Discovery patterns
    Use Telecom Discovery patterns to identify and classify network functions (xNFs) from vendor devices such as Cisco, Juniper, routers, or switches. Leverage pattern-based discovery to map telecom resources into the CMDB.
  • Validating JSON payloads using TSOM Schema Validator
    Use the TsomSchemaValidator utility class to validate JSON payloads against TSOM schemas before importing data. This helps identify errors early, reduce ETL failures, and confirm data quality.
  • Run Telecom Discrepancy audit
    The Telecom Discrepancy Audit validates the integrity of configuration items (CIs) and relationships across your telecom inventory using the CMDB Compliance framework.
  • Generate reports for attribute value discrepancies
    Use CMDB 360 to generate reports that highlight discrepancies in attribute values between different discovery sources or between a discovery source and the CMDB baseline.